[Akonadi] [Bug 317418] New: Korganizer crashed when adding a KDE Calendar (traditional)
https://bugs.kde.org/show_bug.cgi?id=317418 Bug ID: 317418 Summary: Korganizer crashed when adding a KDE Calendar (traditional) Classification: Unclassified Product: Akonadi Version: 4.9 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: KResource compat bridges Assignee: kram...@kde.org Reporter: sayeed...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_kcal_resource (4.9) KDE Platform Version: 4.9.5 Qt Version: 4.8.3 Operating System: Linux 3.5.0-26-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: 1. Clicked the mouse on the "Finish" button which was the final step in adding a calendar. The crash can be reproduced every time. -- Backtrace: Application: ACTIVITIES > 2013 03 26 23 37 25 of type KDE Calendar (traditional) (akonadi_kcal_resource), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57cb10c780 (LWP 3098))] Thread 2 (Thread 0x7f57b01b3700 (LWP 3101)): #0 0x7f57c7f2c303 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f57c61bad84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f57c61baea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f57ca5a1c16 in QEventDispatcherGlib::processEvents (this=0x7f57a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f57ca5722bf in QEventLoop::processEvents (this=this@entry=0x7f57b01b2dd0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f57ca572548 in QEventLoop::exec (this=0x7f57b01b2dd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f57ca473b10 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f57ca5529af in QInotifyFileSystemWatcherEngine::run (this=0x14155d0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f57ca476aec in QThreadPrivate::start (arg=0x14155d0) at thread/qthread_unix.cpp:338 #9 0x7f57c6a95e9a in start_thread (arg=0x7f57b01b3700) at pthread_create.c:308 #10 0x7f57c7f37cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f57cb10c780 (LWP 3098)): [KCrash Handler] #6 0x7f57c9c7cc14 in KCal::Incidence::relatedTo (this=this@entry=0x1d9c6a0) at ../../kcal/incidence.cpp:518 #7 0x7f57c9c7de42 in KCal::Incidence::~Incidence (this=0xfca140, __in_chrg=) at ../../kcal/incidence.cpp:201 #8 0x7f57c9c81a39 in KCal::Todo::~Todo (this=0xfca140, __in_chrg=) at ../../kcal/todo.cpp:105 #9 0x00412379 in release (this=0x1126230) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:145 #10 ~shared_count (this=0x219b4b0, __in_chrg=) at /usr/include/boost/smart_ptr/detail/shared_count.hpp:305 #11 ~shared_ptr (this=0x219b4a8, __in_chrg=) at /usr/include/boost/smart_ptr/shared_ptr.hpp:164 #12 ~Payload (this=0x219b4a0, __in_chrg=) at /usr/include/akonadi/itempayloadinternals_p.h:285 #13 Akonadi::Payload >::~Payload (this=0x219b4a0, __in_chrg=) at /usr/include/akonadi/itempayloadinternals_p.h:285 #14 0x7f57cabea066 in ~clone_ptr (this=0x1cf0560, __in_chrg=) at ../../akonadi/item_p.h:48 #15 ~TypedPayload (this=0x1cf0560, __in_chrg=) at ../../akonadi/item_p.h:119 #16 _Destroy (__pointer=0x1cf0560) at /usr/include/c++/4.7/bits/stl_construct.h:95 #17 __destroy (__last=, __first=0x1cf0560) at /usr/include/c++/4.7/bits/stl_construct.h:105 #18 _Destroy (__last=, __first=) at /usr/include/c++/4.7/bits/stl_construct.h:128 #19 _Destroy (__last=0x1cf0570, __first=) at /usr/include/c++/4.7/bits/stl_construct.h:155 #20 ~vector (this=0x144f2a8, __in_chrg=) at /usr/include/c++/4.7/bits/stl_vector.h:403 #21 ~ItemPrivate (this=0x144f260, __in_chrg=) at ../../akonadi/item_p.h:203 #22 Akonadi::ItemPrivate::~ItemPrivate (this=0x144f260, __in_chrg=) at ../../akonadi/item_p.h:204 #23 0x7f57cab497a4 in node_destruct (to=0x1c7eb68, from=0x1c7eb68, this=) at /usr/include/qt4/QtCore/qlist.h:431 #24 free (data=0x1c7eb50, this=) at /usr/include/qt4/QtCore/qlist.h:757 #25 QList::~QList (this=, __in_chrg=) at /usr/include/qt4/QtCore/qlist.h:732 #26 0x7f57cabff661 in ~ItemModifyJobPrivate (this=0x2207be0, __in_chrg=) at ../../akonadi/itemmodifyjob_p.h:30 #27 Akonadi::ItemModifyJobPrivate::~ItemModifyJobPrivate (this=0x2207be0, __in_chrg=) at ../../akonadi/itemmodifyjob_p.h:30 #28 0x7f57cac04198 in Akonadi::Job::~Job (this=0x2159820, __in_chrg=) at ../../akonadi/job.cpp:254 #29 0x7f57cabfba49 in Akonadi::ItemModifyJob::~ItemModifyJob (this=0x2159820, __in_chrg=) at ../../akonadi/itemmodifyjob.cpp:135 #30 0x7f57ca588468 in QObject::event (this=0x2159820, e=) at kernel/qobject.cpp:1176 #31 0x7f57c88e7e9c in QApplicationPrivate::not
[kaddressbook] [Bug 299663] "Apply" button in the contact form is missing in the current version of KDE Kontact
https://bugs.kde.org/show_bug.cgi?id=299663 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed --- 1. It may be worth noting that the "Apply" button is available in Korganizer (Events, To Do, and Journal). 2. However, it was removed in the Kaddressbook after KDE version 4.3.2. If it continues to be available in Korganizer why was it removed from the contact entry form in Kaddressbook in versions after 4.3.2? This appears to be a regression. 3. The "Apply" button is useful for the following reasons: 3.1. It enables intermediate saving of data that has been entered into the contact form of the Kaddressbook without having to close the entry in order to save the data that has been already entered. 4. It will be a good idea to reinstate the "Apply" button in version 4.10. -- 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
[kaddressbook] [Bug 314474] Cannot edit multiple entries in Kaddressbook simultaneously
https://bugs.kde.org/show_bug.cgi?id=314474 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed --- 1. This bug is always reproducible. -- 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
[kaddressbook] [Bug 314474] New: Cannot edit multiple entries in Kaddressbook simultaneously
https://bugs.kde.org/show_bug.cgi?id=314474 Bug ID: 314474 Summary: Cannot edit multiple entries in Kaddressbook simultaneously Classification: Unclassified Product: kaddressbook Version: 4.9 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sayeed...@gmail.com CC: to...@kde.org 1. In KDE version 4.3.2, it was possible to open and edit multiple contact entries in Kaddressbook simultaneously. This is not possible in version 4.9. As a matter of fact, when on contact entry is opened for editing, Kaddressbook becomes gray and it is no longer possible to have access to any other contact entry. Will it be possible to open and edit multiple contact entries in version 4.10? 2. This feature is absolutely necessary for the following reasons: 2.1. Some times it becomes necessary to view more than one contact entry (for example, in order to compare them). 2.2. Some times it becomes necessary to view and copy information from one contact entry for use in creating or editing another contact entry. 2.3. The inability to open and edit multiple contact entries simultaneously makes the use of Kaddressbook much more difficult and much less efficient. 3. One wonders why versions of Kaddressbook after version 4.3.2 have regressed in this matter. -- 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
[kaddressbook] [Bug 312282] kaddressbook does not provide a column displaying the list of contacts in the address book
https://bugs.kde.org/show_bug.cgi?id=312282 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #7 from K. A. Sayeed --- 1. I do not recall doing anything to collapse the middle column. It came up with two columns to begin with. 2. I tried to get three columns by selecting "Three columns" in the view menu. It did not show three columns. 3. However, I followed your suggestion and managed to obtain the middle column by expanding the inner border between the existing two columns. This seems to have worked somehow. 4. Thank you for your suggestion and for taking steps to resolve the issue in version 4.10. I hope the fix works. 5. Incidentally, the current KAddressbook has still to catch up with an earlier version, namely, 4.3.2, in terms of features and display in areas such as categories (hierarchy not displayed as clearly as in version 4,3,2,) and the "Apply" button which is missing in versions after 4.3.2. -- 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
[kaddressbook] [Bug 312282] kaddressbook does not provide a column displaying the list of contacts in the address book
https://bugs.kde.org/show_bug.cgi?id=312282 --- Comment #4 from K. A. Sayeed --- Created attachment 76798 --> https://bugs.kde.org/attachment.cgi?id=76798&action=edit 1. The attachment is the screenshot requested by Laurent Montel 1. It can be seen from the attached screenshot that the column listing all the contacts in the address book is missing even though the screenshot indicates that 3 columns have been selected for display. -- 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 312282] New: kaddressbook does not provide a column displaying the list of contacts in the address book
https://bugs.kde.org/show_bug.cgi?id=312282 Bug ID: 312282 Summary: kaddressbook does not provide a column displaying the list of contacts in the address book Classification: Unclassified Product: kaddressbook Version: 4.9 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sayeed...@gmail.com CC: to...@kde.org 1. Normally, Kaddressbook should display a column in which the list of contacts is displayed. 2. In version 4.9.3., no such list is displayed. 3. Even though three columns were selected in the view menu, only two columns are displayed. NEITHER of the two columns contains the list of contacts in the address book. 4. This renders the Kaddressbook almost USELESS. Reproducible: Always Steps to Reproduce: 1. Start the Kadressbook. 2. Select an address book in the column titled "Address Books". 3. Select 3 columns from the view menu. 4. Observe the display. 5. Note that you get only two columns, One of them is titled "Address Books" and the other contains the details of a contact entry in the selected address book Actual Results: 1. Only two columns are displayed, One of them is titled "Address Books" and the other contains the details of a contact entry in the selected address book. 2. THERE IS NO COLUMN SHOWING THE LIST OF CONTACTS IN THE ADDRESS BOOK Expected Results: 1. Three columns must be shown. 2. The middle (second column) must provide a complete list of all the contacts contained in the selected address book. -- 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 307509] New: KMail failed when an event notification received by mail was being accepted
https://bugs.kde.org/show_bug.cgi?id=307509 Bug ID: 307509 Severity: crash Version: 4.8.5 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KMail failed when an event notification received by mail was being accepted Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.5) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-31-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: 1. Accepting an event notification that was received by mail and was contained in the KMail inbox. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2ad31217c0 (LWP 2814))] Thread 5 (Thread 0x7f2ab3ec1700 (LWP 2815)): #0 0x7f2ad045f0bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f2ac8d498cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2ac8d0eba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2ac8d0efd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2ac8d0f49a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2ab3ec698b in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #6 0x7f2ac8d309e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f2acdf3be9a in start_thread (arg=0x7f2ab3ec1700) at pthread_create.c:308 #8 0x7f2ad046c4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 4 (Thread 0x7f2ab36c0700 (LWP 2816)): #0 0x7f2ad0460b03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f2ac8d0f036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2ac8d0f49a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2ab6cea406 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f2ac8d309e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2acdf3be9a in start_thread (arg=0x7f2ab36c0700) at pthread_create.c:308 #6 0x7f2ad046c4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 3 (Thread 0x7f2ab1a1c700 (LWP 2934)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f2ac5402dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f2ac5402f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f2acdf3be9a in start_thread (arg=0x7f2ab1a1c700) at pthread_create.c:308 #4 0x7f2ad046c4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 2 (Thread 0x7f2a9ea8a700 (LWP 2935)): #0 0x7f2ad0460b03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f2ac8d0f036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2ac8d0f164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2ad0df7426 in QEventDispatcherGlib::processEvents (this=0x7f2aa80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f2ad0dc6c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f2ad0dc6ed7 in QEventLoop::exec (this=0x7f2a9ea89dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f2ad0cc5fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f2ad0cc8fcb in QThreadPrivate::start (arg=0x19266a0) at thread/qthread_unix.cpp:298 #8 0x7f2acdf3be9a in start_thread (arg=0x7f2a9ea8a700) at pthread_create.c:308 #9 0x7f2ad046c4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 1 (Thread 0x7f2ad31217c0 (LWP 2814)): [KCrash Handler] #6 0x7f2ad03b0445 in __GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f2ad03b3bab in __GI_abort () at abort.c:91 #8 0x7f2ad03a910e in __assert_fail_base (fmt=, assertion=0x7f2abe6783d0 "! ((comp_parts.dtstamp.is_utc==1)^ (match_parts.dtstamp.is_utc==1))", file=0x7f2abe678398 "/build/buildd/libical-0.48/src/libicalss/icalclassify.c", line=, function=) at assert.c:94 #9 0x7f2ad03a91b2 in __GI___assert_fail (assertion=0x7f2abe6783d0 "! ((comp_parts.dtstamp.is_utc==1)^ (match_parts.dtstamp.is_utc==1))", file=0x7f2abe678398 "/build/buildd/libical-0.48/src/libicalss/icalclassify.c", line=778, function=0x7f2abe678414 "icalclassify") at assert.c:103 #10 0x7f2abe67095c in icalclassify (c=0x5c6bc10, match=0x5c90b20, user=0x7f2ac24c294c "") at /build/buildd/libical-0.48/src/libicalss/icalclass
[Bug 301840] Kmail failed when the user clicked the mouse on the "...... by clicking here" phrase in order to "activate formatted HTML display"
https://bugs.kde.org/show_bug.cgi?id=301840 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com Summary|Kmail failed when I clicked |Kmail failed when the user |the mouse on the ".. by |clicked the mouse on the |clicking here" phrase in|".. by clicking here" |order to "activate |phrase in order to |formatted HTML display" |"activate formatted HTML ||display" -- 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 301840] New: Kmail failed when I clicked the mouse on the "...... by clicking here" phrase in order to "activate formatted HTML display"
https://bugs.kde.org/show_bug.cgi?id=301840 Bug ID: 301840 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail failed when I clicked the mouse on the ".. by clicking here" phrase in order to "activate formatted HTML display" Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: 1. The user was reading a message in HTML format in Kmail. 2. The raw HTML code was shown as stated in the following note at the start of the message: 2.1. "Note: This is an HTML message. For security reasons, only the raw HTML code is shown. If you trust the sender of this message then you can activate formatted HTML display for this message by clicking here." 3. The user clicked on the "by clicking here" phrase which was highlighted in blue in order to activate formatted HTML display . 4. At this point Kmail failed and the KDE Crash Reporting Assistant was invoked. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa7311cc7c0 (LWP 1981))] Thread 4 (Thread 0x7fa70ee58700 (LWP 2317)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fa7234bddec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fa7234bdf19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fa72bfefe9a in start_thread (arg=0x7fa70ee58700) at pthread_create.c:308 #4 0x7fa72e5204bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7fa70e557700 (LWP 2318)): #0 0x7fa726dc9f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa726dca124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa72eeab426 in QEventDispatcherGlib::processEvents (this=0x7fa7080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #3 0x7fa72ee7ac82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #4 0x7fa72ee7aed7 in QEventLoop::exec (this=0x7fa70e556dc0, flags=...) at kernel/qeventloop.cpp:204 #5 0x7fa72ed79fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #6 0x7fa72ed7cfcb in QThreadPrivate::start (arg=0x2145400) at thread/qthread_unix.cpp:298 #7 0x7fa72bfefe9a in start_thread (arg=0x7fa70e557700) at pthread_create.c:308 #8 0x7fa72e5204bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 2 (Thread 0x7fa70ca3c700 (LWP 2383)): #0 0x7fa72bff305d in __pthread_mutex_unlock_usercnt (mutex=, decr=) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7fa6c00081d0) at pthread_mutex_unlock.c:290 #2 0x7fa726e05591 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa726dc9713 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa726dc9f1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fa726dca124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fa72eeab426 in QEventDispatcherGlib::processEvents (this=0x7fa6c00071f0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x7fa72ee7ac82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #8 0x7fa72ee7aed7 in QEventLoop::exec (this=0x7fa70ca3bd90, flags=...) at kernel/qeventloop.cpp:204 #9 0x7fa72ed79fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #10 0x7fa72ee5a9ff in QInotifyFileSystemWatcherEngine::run (this=0x271af20) at io/qfilesystemwatcher_inotify.cpp:248 #11 0x7fa72ed7cfcb in QThreadPrivate::start (arg=0x271af20) at thread/qthread_unix.cpp:298 #12 0x7fa72bfefe9a in start_thread (arg=0x7fa70ca3c700) at pthread_create.c:308 #13 0x7fa72e5204bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #14 0x in ?? () Thread 1 (Thread 0x7fa7311cc7c0 (LWP 1981)): [KCrash Handler] #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x86ea5a0, hm=..., sc=, rp=..., pu=, db=..., contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:827 #7 0x7fa72d555709 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x86ea5a0, _c=, _id=, _a=) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #8 0x7fa72ee95446 in QObject::event (this=0x86ea5a0, e=) at kernel/qobject.cpp:1195 #9 0x7fa72f39e894 in notify_helper (e=
[Bug 300639] Kmail failed when an e-mail message in HTML format was being read.
https://bugs.kde.org/show_bug.cgi?id=300639 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com Summary|Kmail failed when an e-mail |Kmail failed when an e-mail |message that in HTML |message in HTML format was |format was being read. |being read. -- 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 300639] New: Kmail failed when an e-mail message that in HTML format was being read.
https://bugs.kde.org/show_bug.cgi?id=300639 Bug ID: 300639 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail failed when an e-mail message that in HTML format was being read. Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: 1. Reading an e-mail message in Kmail which was in HTML format. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd53f5cb7c0 (LWP 1838))] Thread 4 (Thread 0x7fd51d258700 (LWP 2237)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fd5318bcdec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fd5318bcf19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fd53a3eee9a in start_thread (arg=0x7fd51d258700) at pthread_create.c:308 #4 0x7fd53c91f4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7fd51c957700 (LWP 2238)): #0 0x7fd5351c88b0 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fd5351c8f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd5351c9124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd53d2aa426 in QEventDispatcherGlib::processEvents (this=0x7fd5180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fd53d279c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fd53d279ed7 in QEventLoop::exec (this=0x7fd51c956dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fd53d178fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7fd53d17bfcb in QThreadPrivate::start (arg=0x1d00510) at thread/qthread_unix.cpp:298 #8 0x7fd53a3eee9a in start_thread (arg=0x7fd51c957700) at pthread_create.c:308 #9 0x7fd53c91f4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 2 (Thread 0x7fd4d6cde700 (LWP 2359)): #0 0x7fd53c913b03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fd5351c8ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd5351c9124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd53d2aa426 in QEventDispatcherGlib::processEvents (this=0x7fd4d002aaf0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fd53d279c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fd53d279ed7 in QEventLoop::exec (this=0x7fd4d6cddd90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fd53d178fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7fd53d2599ff in QInotifyFileSystemWatcherEngine::run (this=0x2227ea0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fd53d17bfcb in QThreadPrivate::start (arg=0x2227ea0) at thread/qthread_unix.cpp:298 #9 0x7fd53a3eee9a in start_thread (arg=0x7fd4d6cde700) at pthread_create.c:308 #10 0x7fd53c91f4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fd53f5cb7c0 (LWP 1838)): [KCrash Handler] #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x3037340, hm=..., sc=, rp=..., pu=, db=..., contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:827 #7 0x7fd53b954709 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x3037340, _c=, _id=, _a=) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #8 0x7fd53d294446 in QObject::event (this=0x3037340, e=) at kernel/qobject.cpp:1195 #9 0x7fd53d79d894 in notify_helper (e=0x7fd4c0007c60, receiver=0x3037340, this=0x17c07f0) at kernel/qapplication.cpp:4559 #10 QApplicationPrivate::notify_helper (this=0x17c07f0, receiver=0x3037340, e=0x7fd4c0007c60) at kernel/qapplication.cpp:4531 #11 0x7fd53d7a2713 in QApplication::notify (this=0x7fffeef82910, receiver=0x3037340, e=0x7fd4c0007c60) at kernel/qapplication.cpp:4420 #12 0x7fd53efd6b46 in KApplication::notify (this=0x7fffeef82910, receiver=0x3037340, event=0x7fd4c0007c60) at ../../kdeui/kernel/kapplication.cpp:311 #13 0x7fd53d27ae9c in QCoreApplication::notifyInternal (this=0x7fffeef82910, receiver=0x3037340, event=0x7fd4c0007c60) at kernel/qcoreapplication.cpp:876 #14 0x7fd53d27ec6a in sendEvent (event=0x7fd4c0007c60, receiver=0x3037340) at ../../includ
[Bug 300255] New: When a newly created contact is saved to an address book an endlessly repeating error message is displayed.
https://bugs.kde.org/show_bug.cgi?id=300255 Bug ID: 300255 Severity: critical Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: When a newly created contact is saved to an address book an endlessly repeating error message is displayed. Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. When a newly created contact is saved, the following endlessly repeating error message is displayed in the bottom right hand corner of the screen: 1.1. "CONTACTS -> ASSORTED -> 02 ->->2: Request for saving the address bookfailed. Probably locked by another application.". 2. Please note that "CONTACTS -> ASSORTED -> 02" is the name of one of the three address books that was created by the user in KDE Kontact. 3. No request was made to the application by the user to save the aforementioned address book nor was any new contact created in the said address book. The new contact was created in an entirely different address book in KDE Contact . 4. The aforementioned error message continues to repeat until the system is restarted. 5. Also, please note that the newly created contact was NOT shown in the list of contacts contained in the address book in which it was created. 6. This problem happens some times and not some other times. Nevertheless, it does happen quite frequently. Reproducible: Sometimes Steps to Reproduce: 1. Create a new contact in an address book. 2. Save the new contact. Actual Results: 1. The error message mentioned above is repeatedly displayed by the system. 2. The newly created contact is nowhere to be found. Expected Results: 1. There should be no error message. 2. The newly created contact must be found in the address book in which it was created. -- 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 299653] An error is reported every time the mouse is clicked on a local folder
https://bugs.kde.org/show_bug.cgi?id=299653 --- Comment #3 from K. A. Sayeed --- I did nothing unusual before it. I did not delete, move, or create a folder before clicking on a folder with the mouse. I just clicked the mouse randomly on a folder in Kmail and it results in an error message. I did it just now to verify it before I responded to your query by clicking on various folders. The error message is displayed for each click on a different folder. On 9 May 2012 08:12, Laurent Montel wrote: > https://bugs.kde.org/show_bug.cgi?id=299653 > > Laurent Montel changed: > > What|Removed |Added > > > CC||mon...@kde.org > > --- Comment #2 from Laurent Montel --- > what do you do before it ? > Removed folder ? etc. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. > -- 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 299895] On sending a message, the system puts out an error message stating that the local folder did not exist.
https://bugs.kde.org/show_bug.cgi?id=299895 --- Comment #4 from K. A. Sayeed --- I am absolutely sure that the send folders and all the required folders are indeed correctly identified for each identity. I have double checked this once again after receiving your message and found this to be correct. As a matter of fact, both received and sent messages were put into the appropriate folders by Kmail whenever messages were received or sent. On 12 May 2012 17:17, Laurent Montel wrote: > https://bugs.kde.org/show_bug.cgi?id=299895 > > Laurent Montel changed: > > What|Removed |Added > > > CC||mon...@kde.org > > --- Comment #3 from Laurent Montel --- > Are you sure that you send folder is correctly defined in identity ? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. > -- 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 300135] New: KDE Crash Handler reported a failure when the user restarted the system
https://bugs.kde.org/show_bug.cgi?id=300135 Bug ID: 300135 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KDE Crash Handler reported a failure when the user restarted the system Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: 1. The user was trying to attach some files to an e-mail message that was being sent using Kmail. 2. Since the Kmail attachment function could not find the files (these files were existing files that were displayed by Dolphin), the system was restarted in order to resolve the failure of Kmail to find existing files that needed to be attached to the e-mail message. - Unusual behavior I noticed: 1. The user was attempting to attach files (that did exist in a folder) to an e-mail message. However, the system did not display these files in the attachment dialog box even though it should have displayed them. The user tried to resolve this problem by restarting the system. After the user clicked on the restart button the system shut down application windows and then dispayed the KDE Crash Handler dialog box. 2. Also, the computer system was unusually slow. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3f0e0727c0 (LWP 1852))] Thread 5 (Thread 0x7f3ef1c30700 (LWP 1861)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f3f0a86bdec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f3f0a86bf19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f3f05d32e9a in start_thread (arg=0x7f3ef1c30700) at pthread_create.c:308 #4 0x7f3f0b59d4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f3ef142f700 (LWP 1862)): #0 0x7fff67dff70e in ?? () #1 0x7fff67dff959 in ?? () #2 0x7f3f0409615d in __GI_clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:116 #3 0x7f3f0bc3abb4 in do_gettime (frac=0x7f3ef142ebe8, sec=0x7f3ef142ebe0) at tools/qelapsedtimer_unix.cpp:123 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #5 0x7f3f0bd12b8d in QTimerInfoList::updateCurrentTime (this=0x7f3eec002860) at kernel/qeventdispatcher_unix.cpp:343 #6 0x7f3f0bd12841 in timerSourceCheckHelper (src=) at kernel/qeventdispatcher_glib.cpp:150 #7 timerSourceCheckHelper (src=) at kernel/qeventdispatcher_glib.cpp:144 #8 0x7f3f05865a33 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f3f05865f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f3f05866124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f3f0bd12426 in QEventDispatcherGlib::processEvents (this=0x7f3eec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #12 0x7f3f0bce1c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #13 0x7f3f0bce1ed7 in QEventLoop::exec (this=0x7f3ef142edc0, flags=...) at kernel/qeventloop.cpp:204 #14 0x7f3f0bbe0fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #15 0x7f3f0bbe3fcb in QThreadPrivate::start (arg=0xc39490) at thread/qthread_unix.cpp:298 #16 0x7f3f05d32e9a in start_thread (arg=0x7f3ef142f700) at pthread_create.c:308 #17 0x7f3f0b59d4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #18 0x in ?? () Thread 3 (Thread 0x7f3e97c46700 (LWP 2412)): #0 0x7f3f05d3605d in __pthread_mutex_unlock_usercnt (mutex=, decr=) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7f3e9a60) at pthread_mutex_unlock.c:290 #2 0x7f3f058a1591 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3f0586589b in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3f05865f6a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3f05866124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3f0bd12426 in QEventDispatcherGlib::processEvents (this=0x7f3e98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x7f3f0bce1c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f3f0bce1ed7 in QEventLoop::exec (this=0x7f3e97c45d90, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f3f0bbe0fa7 in QThread::exec (this=) at thread/qthread.cpp:50
[Bug 300087] New: Custom field is not automatically created when a new contact is created.
https://bugs.kde.org/show_bug.cgi?id=300087 Bug ID: 300087 Severity: major Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: Custom field is not automatically created when a new contact is created. Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. A custom field created in an existing contact in an address book is NOT automatically created in a new contact after the new contact is created EVEN THOUGH the "Use field for all contacts" box was PREVIOUSLY checked in the existing contact. Reproducible: Always Steps to Reproduce: 1. Select an existing contact in an Address book. 2. Open it in the "edit" mode. 3. Click the mouse on the "Custom fields" tab. 4. Click the mouse on the "Add" button to create a custom field. 5. Enter a custom field name and check the "Use field for all contacts" box. 6. Close the existing contact. 7. Now create a new contact by clicking on the "New Contact" button or by using the menu. 8. Click the mouse on the "Custom fields" tab of the new contact. 9. Examine the custom fields to determine if the previously created custom field (see step 5) exists in the newly created contact. Actual Results: 1. No custom field was displayed. Expected Results: 1. Every custom field for which the "Use field for all contacts" box was checked in any and every existing contact must be displayed, must be intelligible, and must be usable in a NEW CONTACT whenever a new contact is created. 1. The Operating System in use is Kubuntu 12.04. 2. The KDE PIM was installed automatically during the OS installation process. 3. Other problems relating to custom fields in the address book have been reported earlier. -- 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 299943] New: Inability to open more than one Contact entry in the edit mode.
https://bugs.kde.org/show_bug.cgi?id=299943 Bug ID: 299943 Severity: major Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: Inability to open more than one Contact entry in the edit mode. Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. It is not possible to edit two or more Contact entries contained in the Address Book of KDE Kontact. 2. Once an Contact entry is being edited, if another entry needs to opened for reference or for copying and pasting into, the application does not allow it. 3. It is also not possible to edit or create entries in the Calendar, To-Do, Kmail, and Journal modules of the KDE Kontact application. 3. This is a REGRESSION from KDE Kontact, version 4.3.2, in which it was possible, not only to open more than one contact entry, but also to open or create entires in the Calendar, Journal, To-Do, and Kmail modules of KDE Kontact. Reproducible: Always Steps to Reproduce: 1. Create a new Contact entry or open an existing one for editing. 2. Now try to do any work in any other module such as Kmail or Journal. Actual Results: 1. Cannot do any work in any other module or to open another contact entry in the Address Book. Expected Results: 1. It should have been possible to open either another Contact Entry or to do work in the Journal, To-do, Kmail, or Calendar modules. 1. It is extremely inefficient to be restricted to only one module at a time. In many situations, it is necessary to open a Contact entry in the edit mode in order to make changes based on information obtained from other modules and vice versa. 2. The subsequent Akonadi server and related architectural and software engineering changes should have built and improved upon the existing functionality. Instead, it has only reduced the functionality and capability of the KDE PIM and thus reduced the efficiency that was once offered to the user in pre-Akonadi versions such as 4.3.2. -- 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 299895] On sending a message, the system puts out an error message stating that the local folder did not exist.
https://bugs.kde.org/show_bug.cgi?id=299895 --- Comment #2 from K. A. Sayeed --- 1. Please also note that the sent messages are also stored in the "outbox" folder under "Local Folders" even though the message has already been sent and is contained in the "Sent" folder as well as in the "Inbox" of the recipient. -- 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 299895] On sending a message, the system puts out an error message stating that the local folder did not exist.
https://bugs.kde.org/show_bug.cgi?id=299895 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed --- 1. Please note the the folder named "Local Folders" does exist and contains several sub-folders. -- 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 299895] New: On sending a message, the system puts out an error message stating that the local folder did not exist.
https://bugs.kde.org/show_bug.cgi?id=299895 Bug ID: 299895 Severity: normal Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: On sending a message, the system puts out an error message stating that the local folder did not exist. Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kmail2 1. An e-mail message was sent (please note that the message was sent successfully): 2. Immediately thereafter, the following error message was displayed for a short time at the bottom right hand corner of the screen: 2.1. "Local folders: Error opening. This folder is missing.". 3. In reality, the "Local folders" do exist and the messsage was in the Sent folder which is a subfolder of Local Folders. Reproducible: Always Steps to Reproduce: 1. Open KDE Kontact. 2. Send an e-mail message using KMail. Actual Results: 1. The following error message is displayed momentarily at the bottom right hand corner of the screen: 2.1. "Local folders: Error opening. This folder is missing.". Expected Results: 1. There should be no error message -- 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 299853] Alphabetical custom field names created in an address book in KDE Kontact are replaced by the coresponding key created by the application.
https://bugs.kde.org/show_bug.cgi?id=299853 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed --- 1. The numerous problems pertaining to KDE Kontact that have been reported recently did not exist before the Akonadi server and related architectural changes were introduced into KDE. 2. Perhaps it might be a good idea to compare and contrast the pre- and post-Akonadi stability, reliability, and features of the KDE PIM in order to restore it to its pre-Akonadi state or better. -- 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 299853] New: Alphabetical custom field names created in an address book in KDE Kontact are replaced by the coresponding key created by the application.
https://bugs.kde.org/show_bug.cgi?id=299853 Bug ID: 299853 Severity: critical Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: Alphabetical custom field names created in an address book in KDE Kontact are replaced by the coresponding key created by the application. Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. After an entirely new contact has been created in an address book in KDE Kontact with alphabetical custom field names, the alphabetic field name gets replaced by the corresponding alphanumeric key created by the application. This happens after the system is shut down and restarted a few times. 2. It is not possible for a user to use the custom field once it has been replaced with a random alphanumeric key which is unitelligible to the user. Reproducible: Sometimes Steps to Reproduce: 1. Create a contact entry in an address book with custom fields. 2. Shut down the computer system and then restart it. 3. Open the contact entry that was created in step 1. 4. Check the custom field names using the edit button for the Custom fields. 5. If the field names remain alphabetic, then repeat steps 2, 3, and 4 a few times until the alphabetic field names are replaced by an alphanumeric string. 6. Now check the key field using the Advanced button of the Edit dialog box for custom field names. 7. It will be noticed that the alphanumeric string in the custom field name correponds to the alphanumeric string in the key field. Actual Results: 1. Alphabetic custom field name is replaced by an unintelligible alphanumeric string. Expected Results: 1. Custom field names created by the user should NEVER be changed by the software. 1. This problem never occured with KDE Kontact 4.3.2. 2. It might be instructive to examine the design of KDE 4.3.2 in order to correct this and other problems that have been reported with the current version of KDE Kontact. -- 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 299822] New: KDE Kontact crashed when a calendar was about to be imported
https://bugs.kde.org/show_bug.cgi?id=299822 Bug ID: 299822 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KDE Kontact crashed when a calendar was about to be imported Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-24-generic x86_64 Distribution: Ubuntu 12.04 LTS -- Information about the crash: - What I was doing when the application crashed: 1. A calendar (std.ics) was about to be imported - Unusual behavior I noticed: 1. The following error message was reported during system startup: 1.1. "System Notification Helper: An application has crashed on your system (now or in the past).". -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0959afb7c0 (LWP 1949))] Thread 5 (Thread 0x7f093d6b9700 (LWP 1952)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f09562f4dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f09562f4f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f09517bbe9a in start_thread (arg=0x7f093d6b9700) at pthread_create.c:308 #4 0x7f09570264bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 4 (Thread 0x7f093ceb8700 (LWP 1953)): #0 0x7f095701ab03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f09512eeff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f09512ef124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f095779b426 in QEventDispatcherGlib::processEvents (this=0x7f09380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f095776ac82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f095776aed7 in QEventLoop::exec (this=0x7f093ceb7dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f0957669fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f095766cfcb in QThreadPrivate::start (arg=0x12fd970) at thread/qthread_unix.cpp:298 #8 0x7f09517bbe9a in start_thread (arg=0x7f093ceb8700) at pthread_create.c:308 #9 0x7f09570264bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 3 (Thread 0x7f08df56a700 (LWP 2267)): #0 0x7f095701ab03 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f09512eeff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f09512ef124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f095779b426 in QEventDispatcherGlib::processEvents (this=0x7f08d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f095776ac82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f095776aed7 in QEventLoop::exec (this=0x7f08df569d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f0957669fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f095774a9ff in QInotifyFileSystemWatcherEngine::run (this=0x1d61b60) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f095766cfcb in QThreadPrivate::start (arg=0x1d61b60) at thread/qthread_unix.cpp:298 #9 0x7f09517bbe9a in start_thread (arg=0x7f08df56a700) at pthread_create.c:308 #10 0x7f09570264bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7f08ef11c700 (LWP 2378)): #0 0x7f09517bdf69 in __pthread_mutex_lock (mutex=0x7f08e80026e0) at pthread_mutex_lock.c:92 #1 0x7f095132a561 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f09512ee555 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f09512eef1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f09512ef124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f095779b426 in QEventDispatcherGlib::processEvents (this=0x7f08e80071f0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f095776ac82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f095776aed7 in QEventLoop::exec (this=0x7f08ef11bd90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f0957669fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f095774a9ff in QInotifyFileSystemWatcherEngine::run (this=0x38807c0) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f095766cfcb in QThreadPrivate::start (arg=0x3880
[Bug 299740] Entries made in an Address Book in KDE Kontact disappear after the system is shut down and started later
https://bugs.kde.org/show_bug.cgi?id=299740 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed --- 1. On further examination, it was found that this problem (the failure to retain information entered in the Address Book after shutdown and starting the system later) HAPPENS EVERY TIME. 2. Furthermore, it happens after a duplicate entry in the address book was created using the "Copy Contact" and "Paste" feature and then edited to create an entirely different entry. The edited contact disappears after the system is shut down and then started again. 3. These and other failures of KDE Kontact began to occur after the adoption of the Akonadi architecture. Version 4.3.2. of the KDE Kontact, which was the version before the Akonadi architecture was adopted was quite reliable, stable, richer in features, and never had any of these failures. -- 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 299740] New: Entries made in an Address Book in KDE Kontact disappear after the system is shut down and started later
https://bugs.kde.org/show_bug.cgi?id=299740 Bug ID: 299740 Severity: critical Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: Entries made in an Address Book in KDE Kontact disappear after the system is shut down and started later Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. An entry made in the Address Book of the KDE Kontact and committed is no longer found after the system was shut down and started later. Reproducible: Sometimes Steps to Reproduce: 1. Create a contact entry in an Address book of KDE Kontact. 2. Commit the entry. 3. Shut down the computer system. 5. Start the computer system. 6. Check the address book for the contact entry that was previously made. Actual Results: 1. Some times the contact entry disappears. Expected Results: 1. Any contact that has been made and commited should always be in the Address book. 1. The KDE Kontact application in question was installed by the Kubuntu 12.04 installer. -- 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 299704] New: Importing of contacts into an address book results in the replacement of custom field names with alphanumeric strings
https://bugs.kde.org/show_bug.cgi?id=299704 Bug ID: 299704 Severity: normal Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: Importing of contacts into an address book results in the replacement of custom field names with alphanumeric strings Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. Contacts were imported into the current address book (in the latest version of KDE Kontact) from another address book using the ".vcf" format. 2. On examination of the imported contacts, it was found that the alphabetic custom field names were replaced by alphanumeric strings. For example, the field name "CREATION TIME:" was replaced by "2c80efe1-5e2f-4702-a1a9-17b9fc980395". Reproducible: Sometimes Steps to Reproduce: 1. Import the contacts from an existing address book using the "Import Vcard" menu item into an address book in the current address book. 2. Select a contact entry and open it in edit mode. 3. Examine the custom field names in the contact entry. 3. Actual Results: The alphabetic custom field names were replaced by alphanumeric strings. Expected Results: The alphabetic custom field names should remain the same. 1. The computer system was using Kubuntu 12.04. 2. The KDE Kontact was installed by the Kubuntu 12.04 installer. 3. The addresses were imported from KDE Kontact running on Ubuntu 11.10. -- 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 299665] New: Menu item for sending a contact in an Address book is missing
https://bugs.kde.org/show_bug.cgi?id=299665 Bug ID: 299665 Severity: major Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: Menu item for sending a contact in an Address book is missing Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. The "Send Contact" menu item in the drop down menu in the address book is missing. Reproducible: Always Steps to Reproduce: 1. Select an Address Book. 2. Select a contact in the Address Book. 3. Click the right mouse button on the selected contact. 4. Search the drop down menu for the menu item "Send Contact". Actual Results: 1. The "Send Contact" menu item is missing. Expected Results: 1. The "Send Contact" menu item must be displayed. 1. The "Send Contact" menu item enabled sending the contact information to other parties directly by e-mail.. 2. This was a very useful function that existed in Kontact 4.3.2. It is missing in the current version of KDE Kontact. 3. It needs to be reinstated. -- 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 299664] New: Alphabetic sorting of custom fields in the contact entry form
https://bugs.kde.org/show_bug.cgi?id=299664 Bug ID: 299664 Severity: wishlist Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: Alphabetic sorting of custom fields in the contact entry form Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. User created custom fields in the entry form for contacts in the address book of KDE Kontact needs need to be sorted alphabetically while entering data in the contact form. This will enable ease of location. Reproducible: Always Steps to Reproduce: 1. Open a new contact in the address book of KDE Kontact. 2. Create a few custom fields in the custom fields section of the contact form 3. Try to sort these fields alphabetically using the field names. Actual Results: 1. Sorting is not possible. Expected Results: 1. It should be possible to sort the custom fields using the field names. 1. Alphabetic sorting of the custom fields when entering information into Contact application of KDE Kontact needs to be introduced in order to alphabetically locate custom fields when entering information. This makes location easier and faster particularly when there are many custom fields. -- 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 299663] New: "Apply" button in the contact form is missing in the current version of KDE Kontact
https://bugs.kde.org/show_bug.cgi?id=299663 Bug ID: 299663 Severity: major Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: "Apply" button in the contact form is missing in the current version of KDE Kontact Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. The "Apply" button that is used to commit information entered into the contact form in the Address Book of the Contacts module of KDE Kontact is missing. Reproducible: Always Steps to Reproduce: 1. Click on the "New Contact" button to open a contact form 2. Look at the bottom right hand corner of the contact form for the "Apply" button. Actual Results: 1. The "Apply" button is missing. Expected Results: 1. The "Apply" button should be visible in bottom right hand corner of the contact form. 1. This is a very useful function. It is missing in the current version of KDE Kontact. It enabled the saving of contact information entered into the Contact application of KDE Kontact without having to close the contact form in order to save the information already entered and then opening it again in order to enter more information. 2. The lack of the "Apply" button makes the creation of contacts in the address book extremely inefficient. 3. The said "Apply" button needs to be reinstated. -- 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 299653] An error is reported every time the mouse is clicked on a local folder
https://bugs.kde.org/show_bug.cgi?id=299653 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed --- 1. The aforementioned error message is reported twice for each click on a local mail directory. -- 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 299653] New: An error is reported every time the mouse is clicked on a local folder
https://bugs.kde.org/show_bug.cgi?id=299653 Bug ID: 299653 Severity: major Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: An error is reported every time the mouse is clicked on a local folder Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: folders Product: kmail2 1. The following error is reported each time the mouse is clicked on a local folder: 1.1.. "Local Folder: Maildir "for collection" is invalid". Reproducible: Always Steps to Reproduce: 1. Click a mouse on a mail directory contained in the Local Folder. Actual Results: 1. The following error is reported each time the mouse is clicked on a local folder: 1.1.. "Local Folder: Maildir "for collection" is invalid". Expected Results: 1. There should be no such error message. 1, The mail directory bearing the name "for collection" was not created by the user. 2. It is not clear from where the Kmail module of KDE Kontact is getting this directory name. -- 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 299588] New: Failure of copy and paste functions when performed on an address book in the Contacts module of KDE Kontact
https://bugs.kde.org/show_bug.cgi?id=299588 Bug ID: 299588 Severity: major Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: Failure of copy and paste functions when performed on an address book in the Contacts module of KDE Kontact Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. When an entry is copied using the "Copy Contact" function and then pasted back into the same address book using the "Paste:" function in order to create a duplicate entry, no duplicate is created. Reproducible: Sometimes Steps to Reproduce: 1. Select an entry in the address book. 2. Copy it using the "Copy Contact" function. 3. Paste it back into the same address book using the "Paste:" function. Actual Results: 1. A duplicate entry is not created. Expected Results: 1. A duplicate entry should be created. 1. This seems to be a random failure. -- 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 299585] New: Failure of Nepomuk Semantic Desktop installed by the Kubuntu 12.04 Installer
https://bugs.kde.org/show_bug.cgi?id=299585 Bug ID: 299585 Severity: major Version: 4.8.x Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Failure of Nepomuk Semantic Desktop installed by the Kubuntu 12.04 Installer Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kontact 1. Frequently get the following error message: 1.1. "Nepomuk Semantic Desktop needs the Virtuoso RDF server to store its data. Installing the Virtuoso Soprano plugin is mandatory for using Nepomuk.". 1.2. If the Nepomuk Semantic Desktop needed any additional components for its proper functioning, these should have been provided during the installation of Kubuntu 12.04. -- 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 299481] A periodically repeated error message that reports that a request for saving an address book failed
https://bugs.kde.org/show_bug.cgi?id=299481 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed --- 1. This bug has been found to be reproducible by following the steps outlined in the bug report. -- 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 299481] New: A periodically repeated error message that reports that a request for saving an address book failed
https://bugs.kde.org/show_bug.cgi?id=299481 Bug ID: 299481 Severity: major Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: A periodically repeated error message that reports that a request for saving an address book failed Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. When a contact in the Contact module of KDE Kontact was copied and pasted into the same address book, the following error message was repeatedly displayed: 1.1. " Address Book: Request for saving the address book failed. Probably locked by another application" Reproducible: Didn't try Steps to Reproduce: 1. Copy and paste a contact address into the same address book. 2. 3. Actual Results: As described in the "Details" section above. Expected Results: 1. There should be no error message. 1. Kubuntu Linux 12.04 was the operating system being used. 2. KDE Kontact was provided with the Linux distribution. 3. The error message continued to be repeated even after KDE Kontact was closed and restarted. -- 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 299418] New: A duplicate contact address in the Contacts application of KDE Kontact disappears after it has been copied and pasted into the same address book
https://bugs.kde.org/show_bug.cgi?id=299418 Bug ID: 299418 Severity: major Version: unspecified Priority: NOR CC: to...@kde.org Assignee: kdepim-bugs@kde.org Summary: A duplicate contact address in the Contacts application of KDE Kontact disappears after it has been copied and pasted into the same address book Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Other Status: UNCONFIRMED Component: general Product: kaddressbook 1. An existing contact in the address book of the Contact application of KDE Kontact was copied and pasted into the same address book in order to edit it to create a similar contact. 2. A short while (about 5 seconds) after pasting, it disappears spontaneously. Reproducible: Always Steps to Reproduce: 1. Copy a contact from an address book in the Contacts application of KDE Kontact. 2. Paste it into the same address book. 3. Wait for about 5 seconds and observe the pasted contact. Actual Results: 1. The copied contact disappears. Expected Results: 1. The copied contact must remain permanently in the address book so that it can be used as a template and edited in order to create a different contact entry of similar content in the same address book. 1. The computer system uses Kubuntu 12.04. 2.This is a serious problem because it reduces the efficiency of the address book. 3. Previous versions of KDE Kontact did not have this problem. 4. Furthermore, in previous versions of KDE Kontact it ws possible to mail a contact without having to export it first (see version 4.3.2.). This feature seems to have also disappeared in the current version. 5. Also, in previous versions of KDE Kontact (see version 4.3.2), the contact form had an "Apply" button which was extremely useful in saving information without closing the form. This feature has disappeared from the current version. 6. In summary, the current KDE Kontact seems to have regressed in relation to previous versions instead progressing and becoming more stable and having richer functionality. This is very unfortunate. -- 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 298695] Numerous Problems with KDE Kontact
https://bugs.kde.org/show_bug.cgi?id=298695 --- Comment #2 from K. A. Sayeed --- Created attachment 70617 --> https://bugs.kde.org/attachment.cgi?id=70617&action=edit New crash information added by DrKonqi kontact (4.7.3) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4 - What I was doing when the application crashed: 1. Recording a KDE Kontact journal entry received by e-mail into the Kontact Journal application by clicking the appropriate button at the bottom of the e-mail message. 2. This is identical to the two other crashes reported earlier. -- Backtrace (Reduced): #6 0x7f01e72813a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f01e7284b0b in __GI_abort () at abort.c:92 #8 0x7f01e7279d4d in __GI___assert_fail (assertion=0x7f01d9c93150 "! ((comp_parts.dtstamp.is_utc==1)^ (match_parts.dtstamp.is_utc==1))", file=, line=777, function=) at assert.c:81 #9 0x7f01d9c8aeb6 in icalclassify () from /usr/lib/libicalss.so.0 #10 0x7f01dce781d2 in KCalCore::ICalFormat::parseScheduleMessage (this=, cal=, messageText=) at ../../kcalcore/icalformat.cpp:598 -- 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 298695] Numerous Problems with KDE Kontact
https://bugs.kde.org/show_bug.cgi?id=298695 --- Comment #1 from K. A. Sayeed --- Created attachment 70616 --> https://bugs.kde.org/attachment.cgi?id=70616&action=edit New crash information added by DrKonqi kontact (4.7.3) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4 - What I was doing when the application crashed: 1. Recording a KDE Kontact journal entry received by e-mail into the Kontact Journal application by clicking the appropriate button at the bottom of the e-mail message. -- Backtrace (Reduced): #6 0x7f4c013c13a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f4c013c4b0b in __GI_abort () at abort.c:92 #8 0x7f4c013b9d4d in __GI___assert_fail (assertion=0x7f4bf3dd3150 "! ((comp_parts.dtstamp.is_utc==1)^ (match_parts.dtstamp.is_utc==1))", file=, line=777, function=) at assert.c:81 #9 0x7f4bf3dcaeb6 in icalclassify () from /usr/lib/libicalss.so.0 #10 0x7f4bf6fb81d2 in KCalCore::ICalFormat::parseScheduleMessage (this=, cal=, messageText=) at ../../kcalcore/icalformat.cpp:598 -- 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 298695] Numerous Problems with KDE Kontact
https://bugs.kde.org/show_bug.cgi?id=298695 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.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
[Bug 298695] New: Numerous Problems with KDE Kontact
https://bugs.kde.org/show_bug.cgi?id=298695 Bug ID: 298695 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Numerous Problems with KDE Kontact Classification: Unclassified OS: Linux Reporter: sayeed...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.7.3) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-17-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: 1. Recording a KDE Kontact journal entry received by e-mail into the Kontact Journal application by clicking the appropriate button at the bottom of the e-mail message. - Unusual behavior I noticed: 1. Could not use a template that I had just created in the using "Manage Templates" function in the KDE Kontact application. I go the following message: 1.1. "Error loading template file '/home/sayeednm/.kde/share/apps/korganizer/templates/Journal/Form -> Call -> Voice Recorded -> 2012 04 23 14 24 58'." 2. Important Functions that are missing in recent versions of KDE Kontact: 2.1. Sending contact information from the Contact application of KDE Kontact by e-mail. 2.1.1. This was a very useful function that existed in Kontact 4.3.2. It is missing in subsequent versions of KDE Kontact. It needs to be reinstated. 2.2. The "Apply" button in the Contact application of KDE Kontact: 2.2.1. This was a very useful function that existed in Kontact 4.3.2. It is missing in subsequent versions of KDE Kontact. It enabled the saving of contact information entered into the Contact application of KDE Kontact without having to close the contact form in order to save the information already entered and then opening it again in order to enter more information. This method is extremely inefficient. The said "Apply" button needs to be reinstated. 2.3. Alphabetic sorting of the custom fields when entering information into Contact application of KDE Kontact: 2.3.1. This capability needs to be introduced in order to alphabetically locate custom fields when entering information. This makes location easier and faster particularly when there are many custom fields. -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0x7ffbc1f807a0 (LWP 3866))] Thread 4 (Thread 0x7ffba5b34700 (LWP 3868)): #0 0x7ffbb9bcf1fd in pthread_mutex_unlock () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7ffbb90fdf9a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffbb90fe792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffbacb16516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7ffbb91232b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ffbb9bcbefc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7ffbbf4e359d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x in ?? () Thread 3 (Thread 0x7ffb9c0a9700 (LWP 3869)): #0 0x7ffbb9bd004c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7ffbbe7d3c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7ffbbe7d3d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7ffbb9bcbefc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7ffbbf4e359d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x in ?? () Thread 2 (Thread 0x7ffb9b7a8700 (LWP 3870)): #0 0x7ffbbf4f17b0 in pthread_mutex_unlock () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7ffbb90fcfe4 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffbb90fddfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffbb90fe429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffbc091ff3e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7ffbc08f3cf2 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7ffbc08f3ef7 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7ffbc080b27f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7ffbc080dd05 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7ffbb9bcbefc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7ffbbf4e359d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x in ?? () Thread 1 (Thread 0x7ffbc1f807a0 (LWP 3866)): [KCrash Handler] #6 0x7ffbbf4363a5 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7ffbbf439b0b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7ffbbf42ed4d in __assert_fail () from /lib
[Bug 282767] New: MIssing features
https://bugs.kde.org/show_bug.cgi?id=282767 Summary: MIssing features Product: kontact Version: 4.4.10 Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: contacts AssignedTo: to...@kde.org ReportedBy: sayeed...@gmail.com CC: kdepim-bugs@kde.org Version: 4.4.10 (using KDE 4.6.0) OS:Linux 1. This version of KDE PIM (4.6.X) is a BACKWARD step from version 4.3.2. which had the following features: 1.1. The ability to open, edit, and create multiple contact entries concurrently. 1.2. The ability to save a partially edited version of a contact entry by using the "Apply" button. 1.3. The ability to e-mail a contact entry to another party. 1.4. The ability to use other Kontact modules such as Kmail, Calendar, To do, etc while editing or creating a contact entry without having to close the entry first. 1.5. Much better "custom fields" interface in the Contacts module. 2. This version of KDE PIM has NONE of the above features which version 4.3.2 had. IT IS A REGRESSIVE VERSION AND ITS USEFULNESS IS GREATLY REDUCED AS A RESULT. These features need to be REINSTATED in all future versions. 2.3. One would expect that a newer design and architecture would provide a richer set of features, greater ease of use, and more flexibility, NONE OF THESE HAVE BEEN ACHIEVED IN THE LATEST VERSION (4.6.X) Reproducible: Always Steps to Reproduce: Not applicable. Actual Results: Not applicable. Expected Results: Not applicable. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282742] New: KDE PIM crashed when saving a new entry in the Contacts module of Kontact
https://bugs.kde.org/show_bug.cgi?id=282742 Summary: KDE PIM crashed when saving a new entry in the Contacts module of Kontact Product: kontact Version: 4.4.10 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application: kontact (4.4.10) KDE Platform Version: 4.6.2 (4.6.2) Qt Version: 4.7.2 Operating System: Linux 2.6.38-11-generic x86_64 Distribution: Ubuntu 11.04 -- Information about the crash: - What I was doing when the application crashed: 1. I was saving a new contact that I had created. 2. OTHER COMMENTS: 2.1. This version of KDE PIM (4.6) is a BACKWARD step from version 4.3.2. which had the following features: 2.1.1. The ability to open, edit, and create multiple contact entries concurrently. 2.1.2. The ability to save a partially edited version of a contact entry by using the "Apply" button. 2.1.3. The ability to e-mail a contact entry to another party. 2.1.4. The ability to use other Kontact modules such as Kmail, Calendar, To do, etc while editing or creating a contact entry without having to close the entry first. 2.1.5. Much better "custom fields" interface in the Contacts module. 2.2. This version of KDE PIM has NONE of the above features which version 4.3.2. had. IT IS A REGRESSIVE VERSION AND ITS USEFULNESS IS GREATLY REDUCED AS A RESULT. These features need to be REINSTATED in to all future versions. 2.3. One would expect that a newer design and architecture would provide a richer set of features, greater ease of use, and more flexibility, NONE OF THESE HAVE BEEN ACHIEVED IN THE LATEST VERSION (4.6.X) -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f03f798d7a0 (LWP 1827))] Thread 2 (Thread 0x7f03e233a700 (LWP 1842)): #0 0x7f03f4ddcf03 in __poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f03ee809104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f03ee8099f2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f03e2a7ec44 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f03ee8303e4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f03eecd4d8c in start_thread (arg=0x7f03e233a700) at pthread_create.c:304 #6 0x7f03f4dea04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 1 (Thread 0x7f03f798d7a0 (LWP 1827)): [KCrash Handler] #6 QMetaObject::changeGuard (ptr=0x34d0738, o=0x0) at kernel/qobject.cpp:471 #7 0x7f03f62fc9ce in operator= (this=0x34d0470, action=0x30f9ca0, action_e=QAction::Trigger, self=true) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:68 #8 QMenuPrivate::activateAction (this=0x34d0470, action=0x30f9ca0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1098 #9 0x7f03f6ca1e8d in KMenu::mouseReleaseEvent (this=0x210abd0, e=) at ../../kdeui/widgets/kmenu.cpp:458 #10 0x7f03f5f09cc8 in QWidget::event (this=0x210abd0, event=0x7fff175f93a0) at kernel/qwidget.cpp:8259 #11 0x7f03f62fdb8b in QMenu::event (this=0x210abd0, e=0x7fff175f93a0) at widgets/qmenu.cpp:2415 #12 0x7f03f5eb89f4 in QApplicationPrivate::notify_helper (this=0x1cf6880, receiver=0x210abd0, e=0x7fff175f93a0) at kernel/qapplication.cpp:4462 #13 0x7f03f5ebddc3 in QApplication::notify (this=, receiver=0x210abd0, e=0x7fff175f93a0) at kernel/qapplication.cpp:4023 #14 0x7f03f6bdb866 in KApplication::notify (this=0x7fff175fb9c0, receiver=0x210abd0, event=0x7fff175f93a0) at ../../kdeui/kernel/kapplication.cpp:311 #15 0x7f03f54f949c in QCoreApplication::notifyInternal (this=0x7fff175fb9c0, receiver=0x210abd0, event=0x7fff175f93a0) at kernel/qcoreapplication.cpp:731 #16 0x7f03f5eb9a1d in sendEvent (receiver=0x210abd0, event=0x7fff175f93a0, alienWidget=0x0, nativeWidget=0x210abd0, buttonDown=0x7f03f699c218, lastMouseReceiver=..., spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #17 QApplicationPrivate::sendMouseEvent (receiver=0x210abd0, event=0x7fff175f93a0, alienWidget=0x0, nativeWidget=0x210abd0, buttonDown=0x7f03f699c218, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3122 #18 0x7f03f5f3b3e4 in QETWidget::translateMouseEvent (this=0x210abd0, event=) at kernel/qapplication_x11.cpp:4492 #19 0x7f03f5f39ab7 in QApplication::x11ProcessEvent (this=0x7fff175fb9c0, event=0x7fff175f9cf0) at kernel/qapplication_x11.cpp:3680 #20 0x7f03f5f62842 in x11EventSourceDispatch (s=0x1cfe330, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #21 0x7f03ee808bcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f03ee8093a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
[Bug 275022] New: KDE Kontact failed when I clicked on the "Apply" button after editing an entry in the To Do function
https://bugs.kde.org/show_bug.cgi?id=275022 Summary: KDE Kontact failed when I clicked on the "Apply" button after editing an entry in the To Do function Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application: kontact (4.4.8) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.2 Operating System: Linux 2.6.32-32-generic x86_64 Distribution: Ubuntu 10.04.2 LTS -- Information about the crash: 1. KDE Kontact failed when I clicked on the "Apply" button after editing an entry in the To Do function 2. The Crash Reporting Assistant started automatically after KDE Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x7f6e3d14483c in KOIncidenceEditor::slotManageTemplates (this=0x390bfd0) at ../../korganizer/koincidenceeditor.cpp:187 #6 0x7f6e3d146568 in KOIncidenceEditor::qt_metacall (this=0x390bfd0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff708c06a0) at ./koincidenceeditor.moc:139 #7 0x7f6e3d149010 in KOTodoEditor::qt_metacall (this=0x274f830, _c=QMetaObject::InvokeMetaMethod, _id=43751568, _a=0x21dcd0) at ./kotodoeditor.moc:71 #8 0x7f6e62dabe3f in QMetaObject::activate (sender=0x390bfd0, m=, local_signal_index=, argv=0x21dcd0) at kernel/qobject.cpp:3293 #9 0x7f6e636f13f5 in KDialog::slotButtonClicked (this=0x390bfd0, button=2) at ../../kdeui/dialogs/kdialog.cpp:902 #10 0x7f6e3d145395 in KOIncidenceEditor::slotButtonClicked (this=0x390bfd0, button=0) at ../../korganizer/koincidenceeditor.cpp:123 #11 0x7f6e636f33f9 in KDialog::qt_metacall (this=0x390bfd0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff708c09b0) at ./kdialog.moc:190 #12 0x7f6e637bacf0 in KPageDialog::qt_metacall (this=0x274f830, _c=QMetaObject::InvokeMetaMethod, _id=43751568, _a=0x21dcd0) at ./kpagedialog.moc:70 #13 0x7f6e3d1462c0 in KOIncidenceEditor::qt_metacall (this=0x274f830, _c=QMetaObject::InvokeMetaMethod, _id=43751568, _a=0x21dcd0) at ./koincidenceeditor.moc:113 #14 0x7f6e3d149010 in KOTodoEditor::qt_metacall (this=0x274f830, _c=QMetaObject::InvokeMetaMethod, _id=43751568, _a=0x21dcd0) at ./kotodoeditor.moc:71 #15 0x7f6e62dabe3f in QMetaObject::activate (sender=0x3c3bf88, m=, local_signal_index=, argv=0x21dcd0) at kernel/qobject.cpp:3293 #16 0x7f6e62db115e in QSignalMapper::mapped (this=0x274f830, _t1=2) at .moc/release-shared/moc_qsignalmapper.cpp:101 #17 0x7f6e62db2372 in QSignalMapper::map (this=0x3c3bf88, sender=0x3a6eff0) at kernel/qsignalmapper.cpp:266 #18 0x7f6e62db25f0 in QSignalMapper::qt_metacall (this=0x3c3bf88, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff708c0b40) at .moc/release-shared/moc_qsignalmapper.cpp:87 #19 0x7f6e62dabe3f in QMetaObject::activate (sender=0x3a6eff0, m=, local_signal_index=, argv=0x21dcd0) at kernel/qobject.cpp:3293 #20 0x7f6e627ed5f2 in QAbstractButton::clicked (this=0x274f830, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206 #21 0x7f6e6250786b in QAbstractButtonPrivate::emitClicked (this=0x3c1e460) at widgets/qabstractbutton.cpp:546 #22 0x7f6e6250870b in QAbstractButtonPrivate::click (this=0x3c1e460) at widgets/qabstractbutton.cpp:539 #23 0x7f6e6250897c in QAbstractButton::mouseReleaseEvent (this=0x3a6eff0, e=0x7fff708c1490) at widgets/qabstractbutton.cpp:1121 #24 0x7f6e621a8582 in QWidget::event (this=0x3a6eff0, event=0x7fff708c1490) at kernel/qwidget.cpp:7998 #25 0x7f6e6215222c in QApplicationPrivate::notify_helper (this=0x71be40, receiver=0x3a6eff0, e=0x7fff708c1490) at kernel/qapplication.cpp:4300 #26 0x7f6e62158ecb in QApplication::notify (this=0x7fff708c21a0, receiver=0x3a6eff0, e=0x7fff708c1490) at kernel/qapplication.cpp:3865 #27 0x7f6e63781a16 in KApplication::notify (this=0x7fff708c21a0, receiver=0x3a6eff0, event=0x7fff708c1490) at ../../kdeui/kernel/kapplication.cpp:302 #28 0x7f6e62d9906c in QCoreApplication::notifyInternal (this=0x7fff708c21a0, receiver=0x3a6eff0, event=0x7fff708c1490) at kernel/qcoreapplication.cpp:704 #29 0x7f6e621580ae in QCoreApplication::sendEvent (receiver=0x3a6eff0, event=0x7fff708c1490, alienWidget=0x3a6eff0, nativeWidget=0x390bfd0, buttonDown=, lastMouseReceiver=, spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #30 QApplicationPrivate::sendMouseEvent (receiver=0x3a6eff0, event=0x7fff708c1490, alienWidget=0x3a6eff0, nativeWidget=0x390bfd0, buttonDown=, lastMouseReceiver=, spontaneous=true) at kernel/qapplication.cpp:2965 #31 0x7f6e621d7f65 in QETWidget::translateMouseEvent (this=0x390bfd0, event=) at kernel/qapplication_x11.cpp:4368 #32 0x7f6e621d68ac in QApplication::x11ProcessEvent (this=, event=0x7fff708c1db0) at k
[Bug 252501] Unable to obtain access to KDE PIM 4.5 or KDE PIM 4.5.1 for installation on computer system using the Linux, Ubuntu, 10.04, operating system.
https://bugs.kde.org/show_bug.cgi?id=252501 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed 2010-09-28 09:41:15 --- (In reply to comment #0) > Version: 4.5 pre (using KDE 4.5.1) > OS:Linux > > 1. KDE PIM 4.5 or KDE PIM 4.5.1 is supposed to have solved (as suggested by > Mr. > Tobias Koenig, KDE) some of the severe deficiencies contained in KDE PIM > 4.4.2, > Address Book, etc., applications which, incidentally, were not found in the > earlier version of KDE PIM. > > 2. KDE PIM 4.5 or KDE PIM 4.5.1 is neither available for installation using > >the Linux -> Ubuntu -> Synaptic Package Manager nor is it available for > download > from the KDE PIM web site (http://pim.kde.org/). > > 3. The Linux -> Ubuntu -> Synaptic Package Manager only provides KDE PIM > 4.4.2, > which is deficient in many respects. > > 4. The KDE PIM web site neither provides any downloads of KDE PIM 4.5 or KDE > PIM 4.5.1 nor does it indicate any other sites from which these may be > downloaded. > > Reproducible: Always > > Steps to Reproduce: > 1. Using Linux -> Ubuntu -> Synaptic Package Manager: > > 1.1. Start Linux -> Ubuntu -> Synaptic Package Manager. > > 1.2. Search for KDE PIM using the Synaptic Package Manager. > > 1.3. ExaminE the search results. > > 2. Using KDE PIM web site: > > 2.1. Go to KDE PIM web site. > > 2.2. Search for KDE PIM download button or other means for downloading KDE PIM > 4.5. > > 2.3. Evaluate the search results. > > Actual Results: > Unable to obtain access to KDE PIM 4.5 or KDE PIM 4.5.1 for installation on a > computer system. > > Expected Results: > The ability to obtain access to KDE PIM 4.5 or KDE PIM 4.5.1 for installation > on a computer system. > > OS: Linux (x86_64) release 2.6.32-24-generic > Compiler: cc -- 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 252501] New: Unable to obtain access to KDE PIM 4.5 or KDE PIM 4.5.1 for installation on computer system using the Linux, Ubuntu, 10.04, operating system.
https://bugs.kde.org/show_bug.cgi?id=252501 Summary: Unable to obtain access to KDE PIM 4.5 or KDE PIM 4.5.1 for installation on computer system using the Linux, Ubuntu, 10.04, operating system. Product: kontact Version: 4.5 pre Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: summary AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Version: 4.5 pre (using KDE 4.5.1) OS:Linux 1. KDE PIM 4.5 or KDE PIM 4.5.1 is supposed to have solved (as suggested by Mr. Tobias Koenig, KDE) some of the severe deficiencies contained in KDE PIM 4.4.2, Address Book, etc., applications which, incidentally, were not found in the earlier version of KDE PIM. 2. KDE PIM 4.5 or KDE PIM 4.5.1 is either available for installation using the Linux -> Ubuntu -> Synaptic Package Manager nor is it available for download from the KDE PIM web site (http://pim.kde.org/). 3. The Linux -> Ubuntu -> Synaptic Package Manager only provides KDE PIM 4.4.2, which is deficient in many respects. 4. The KDE PIM web site neither provides any downloads of KDE PIM 4.5 or KDE PIM 4.5.1 nor does it indicate any other sites from which these may be downloaded. Reproducible: Always Steps to Reproduce: 1. Using Linux -> Ubuntu -> Synaptic Package Manager: 1.1. Start Linux -> Ubuntu -> Synaptic Package Manager. 1.2. Search for KDE PIM using the Synaptic Package Manager. 1.3. ExaminE the search results. 2. Using KDE PIM web site: 2.1. Go to KDE PIM web site. 2.2. Search for KDE PIM download button or other means for downloading KDE PIM 4.5. 2.3. Evaluate the search results. Actual Results: Unable to obtain access to KDE PIM 4.5 or KDE PIM 4.5.1 for installation on a computer system. Expected Results: The ability to obtain access to KDE PIM 4.5 or KDE PIM 4.5.1 for installation on a computer system. OS: Linux (x86_64) release 2.6.32-24-generic Compiler: cc -- 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 251167] New: Several IMPORTANT features MISSING from the "kaddressbook" of KDE Kontact application, version 4.4.2
https://bugs.kde.org/show_bug.cgi?id=251167 Summary: Several IMPORTANT features MISSING from the "kaddressbook" of KDE Kontact application, version 4.4.2 Product: kaddressbook Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com CC: to...@kde.org Version: unspecified (using KDE 4.4.2) OS:Linux 1. Several IMPORTANT features which were available in the older KDE Kontact application (namely,"kaddressbook") that were packaged with Linux -> Ubuntu -> Version 9.10 are MISSING in the KDE Kontact application packaged with Linux -> Ubuntu -> Version 10.04. Some of the missing features are as follows: 1.1. The ability to categorise the address book entry (that is, categorise an entry as, for example, "manufacturer", "client", "colleague", etc.), 1.2. The ability to create custom fields. 1.3. The ability to apply changes to an address book entry without having to close the entry. 1.4. The ability to copy an address book entry and paste it as a duplicate entry in the address book for subsequent use as a template to create similar entries. 1.5. The ability to select the type of entry, such as "organization", "reverse name with Comma", etc., has been SEVERELY curtailed. 2. Many other features are missing thus rendering the current address book (namely, version 4.4.2) very INFERIOR compared to the previous version. 3. These are SERIOUS DEFICIENCIES in the product. Reproducible: Always Steps to Reproduce: 1. Just start KDE Kontact and try to find or use the aforementioned features. You will find that they do not exist in KDE -> Kontact -> kaddressbook -> version 4.4.2. Actual Results: 1. The features are no longer available. Expected Results: 1. The features should have been available and, even better, further enhanced in the newer version. OS: Linux (x86_64) release 2.6.32-24-generic Compiler: cc -- 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 251160] Double clicking with the left mouse button on a URL in the Address Book does not open the corresponding web page.
https://bugs.kde.org/show_bug.cgi?id=251160 K. A. Sayeed changed: What|Removed |Added CC||sayeed...@gmail.com --- Comment #1 from K. A. Sayeed 2010-09-13 23:38:46 --- 1, Please note that the problem has occurred in the KDE Kontact package installed with the Synaptic Package Manager provided with Linux, Ubuntu, Version 10.04 -- 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 251160] New: Double clicking with the left mouse button on a URL in the Address Book does not open the corresponding web page.
https://bugs.kde.org/show_bug.cgi?id=251160 Summary: Double clicking with the left mouse button on a URL in the Address Book does not open the corresponding web page. Product: kaddressbook Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com CC: to...@kde.org Version: unspecified (using KDE 4.4.2) OS:Linux 1. In the version of KDE Kontact that was packaged with Linux, Ubuntu, 9.10, double clicking on the URL in a contact in the Address Book opened the corresponding web page. 2. On the Other hand, in the version of KDE Kontact (version KDE 4.4.2), double clicking on the URL in a contact in the Address Book did NOTHING whatsoever. Reproducible: Always Steps to Reproduce: 1. Start KDE Kontact (version 4.4.2 packaged with Linux, Ubunto, version 10.04). 2. Click on the icon "Contact" shown on the left side of the screen. 3. Select an entry in the Address Book which has a URL for a working web site (Example: The URL for "Google"). 4. Double click on the URL. 5. Observe what happens. Actual Results: 1. Nothing happens. 2. No web page is opened. Expected Results: 1. The web page corresponding to the selected URL must be opened. 1. The information given in the preceding sections should be sufficient. -- 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 235478] New: KDE Kontact failed when a journal entry was being mailed to other recipients.
https://bugs.kde.org/show_bug.cgi?id=235478 Summary: KDE Kontact failed when a journal entry was being mailed to other recipients. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: What I was doing when the application crashed: 1. INFORMATION OF THE EVENTS LEADING TO THE FAILURE: 1.1. A journal entry was opened for editing. 1.2. The journal entry was completed and when it was being mailed KDE Kontact failed. 2. INFORMATION ON THE COMPUTER SYSTEM: 2.1. The computer system was using an AMD Athlon 32 bit processor with 512 MB of Direct Access Memory (DAM). 2.2. The operating system (OS) was LInux, Ubuntu, version 9.10, 32 bit. 3. INFORMATION ON OTHER APPLICATIONS RUNNING ON THE SYSTEM WHEN THE FAILURE OCCURRED: 3.1. File browser. 3.2. Firefox web browser. 3.3. Firefox web browser library. 3.4. Gnome Text Editor (GEdit). 3.5. Open Office Work Sheet (spreadsheet) 3.5. Gnome Desktop. 4. OTHER COMMENTS: 4.1. It will be a good idea to program a SEARCH UTILITY for searching for similar bug reports in the Bug Report Possible Duplicates List -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QHash::findNode (this=0x9d6af98, ak...@0xbfb2f1f4, ahp=0x0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:857 #7 0x00ba9727 in QHash::contains (this=0xa7a0c30, sender=0x9093ee0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:847 #8 QSignalMapper::map (this=0xa7a0c30, sender=0x9093ee0) at kernel/qsignalmapper.cpp:267 #9 0x00ba98ee in QSignalMapper::map (this=0xa7a0c30) at kernel/qsignalmapper.cpp:257 #10 0x00baa12b in QSignalMapper::qt_metacall (this=0xa7a0c30, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb2f358) at .moc/release-shared/moc_qsignalmapper.cpp:81 #11 0x00ba6263 in QMetaObject::activate (sender=0x9093ee0, from_signal_index=29, to_signal_index=30, argv=0xbfb2f358) at kernel/qobject.cpp:3113 #12 0x00ba66d8 in QMetaObject::activate (sender=0x9093ee0, m=0x18210a4, from_local_signal_index=2, to_local_signal_index=3, argv=0xbfb2f358) at kernel/qobject.cpp:3207 #13 0x0163acc1 in QAbstractButton::clicked (this=0x9093ee0, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #14 0x01363549 in QAbstractButtonPrivate::emitClicked (this=0x9cbc6d8) at widgets/qabstractbutton.cpp:543 #15 0x013651a4 in QAbstractButtonPrivate::click (this=0x9cbc6d8) at widgets/qabstractbutton.cpp:536 #16 0x01365431 in QAbstractButton::mouseReleaseEvent (this=0x9093ee0, e=0xbfb2f950) at widgets/qabstractbutton.cpp:1115 #17 0x01003012 in QWidget::event (this=0x9093ee0, event=0xbfb2f950) at kernel/qwidget.cpp:7549 #18 0x013633ee in QAbstractButton::event (this=0x9093ee0, e=0xbfb2f1f4) at widgets/qabstractbutton.cpp:1077 #19 0x0140d66d in QPushButton::event (this=0x9093ee0, e=0xbfb2f950) at widgets/qpushbutton.cpp:662 #20 0x00fadf54 in QApplicationPrivate::notify_helper (this=0x887ec80, receiver=0x9093ee0, e=0xbfb2f950) at kernel/qapplication.cpp:4056 #21 0x00fb6033 in QApplication::notify (this=0xbfb31334, receiver=0x9093ee0, e=0xbfb2f950) at kernel/qapplication.cpp:3758 #22 0x00523bfa in KApplication::notify (this=0xbfb31334, receiver=0x9093ee0, event=0xbfb2f950) at ../../kdeui/kernel/kapplication.cpp:302 #23 0x00b906cb in QCoreApplication::notifyInternal (this=0xbfb31334, receiver=0x9093ee0, event=0xbfb2f950) at kernel/qcoreapplication.cpp:610 #24 0x00fb4f6e in QCoreApplication::sendSpontaneousEvent (receiver=0x9093ee0, event=0xbfb2f950, alienWidget=0x9093ee0, nativeWidget=0xa7b08c0, buttonDown=0x1828aa0, lastMouseReceiver=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #25 QApplicationPrivate::sendMouseEvent (receiver=0x9093ee0, event=0xbfb2f950, alienWidget=0x9093ee0, nativeWidget=0xa7b08c0, buttonDown=0x1828aa0, lastMouseReceiver=...) at kernel/qapplication.cpp:2924 #26 0x010237c0 in QETWidget::translateMouseEvent (this=0xa7b08c0, event=0xbfb30f9c) at kernel/qapplication_x11.cpp:4409 #27 0x01022c4b in QApplication::x11ProcessEvent (this=0xbfb31334, event=0xbfb30f9c) at kernel/qapplication_x11.cpp:3428 #28 0x0104f502 in x11EventSourceDispatch (s=0x8876868, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #29 0x019b9e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #30 0x019bd730 in ?? () from /lib/libglib-2.0.so.0 #31 0x019bd863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #32 0x00bbb02c in QEventDispatcherGlib::processEvents (this=0x88559f8, flags=...) at kernel
[Bug 235022] New: KDE Kontact failedwhen a journal entry was being mailed out. The mail was not sent by KDE Kontact.
https://bugs.kde.org/show_bug.cgi?id=235022 Summary: KDE Kontact failedwhen a journal entry was being mailed out. The mail was not sent by KDE Kontact. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: 1. INFORMATION OF THE EVENTS LEADING TO THE FAILURE: 1.1. A journal entry was opened for editing. 1.2. The journal entry was completed and when it was being mailed KDE Kontact failed. 2. INFORMATION ON THE COMPUTER SYSTEM: 2.1. The computer system was using an AMD Athlon 32 bit processor with 512 MB of Direct Access Memory (DAM). 2.2. The operating system (OS) was LInux, Ubuntu, version 9.10, 32 bit. 3. INFORMATION ON OTHER APPLICATIONS RUNNING ON THE SYSTEM WHEN THE FAILURE OCCURRED: 3.1. File browser. 3.2. Firefox web browser. 3.3. Firefox web browser library. 3.4. Gnome Text Editor (GEdit). 3.5. Open Office Work Sheet (spreadsheet) 3.5. Gnome Desktop. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QHash::findNode (this=0xaf6e288, ak...@0xbfb34924, ahp=0x0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:857 #7 0x01b46727 in QHash::contains (this=0xb2ce578, sender=0xb074aa8) at ../../include/QtCore/../../src/corelib/tools/qhash.h:847 #8 QSignalMapper::map (this=0xb2ce578, sender=0xb074aa8) at kernel/qsignalmapper.cpp:267 #9 0x01b468ee in QSignalMapper::map (this=0xb2ce578) at kernel/qsignalmapper.cpp:257 #10 0x01b4712b in QSignalMapper::qt_metacall (this=0xb2ce578, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfb34a88) at .moc/release-shared/moc_qsignalmapper.cpp:81 #11 0x01b43263 in QMetaObject::activate (sender=0xb074aa8, from_signal_index=29, to_signal_index=30, argv=0xbfb34a88) at kernel/qobject.cpp:3113 #12 0x01b436d8 in QMetaObject::activate (sender=0xb074aa8, m=0x17860a4, from_local_signal_index=2, to_local_signal_index=3, argv=0xbfb34a88) at kernel/qobject.cpp:3207 #13 0x0159fcc1 in QAbstractButton::clicked (this=0xb074aa8, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #14 0x012c8549 in QAbstractButtonPrivate::emitClicked (this=0xaecdbe8) at widgets/qabstractbutton.cpp:543 #15 0x012ca1a4 in QAbstractButtonPrivate::click (this=0xaecdbe8) at widgets/qabstractbutton.cpp:536 #16 0x012ca431 in QAbstractButton::mouseReleaseEvent (this=0xb074aa8, e=0xbfb35080) at widgets/qabstractbutton.cpp:1115 #17 0x00f68012 in QWidget::event (this=0xb074aa8, event=0xbfb35080) at kernel/qwidget.cpp:7549 #18 0x012c83ee in QAbstractButton::event (this=0xb074aa8, e=0xbfb34924) at widgets/qabstractbutton.cpp:1077 #19 0x0137266d in QPushButton::event (this=0xb074aa8, e=0xbfb35080) at widgets/qpushbutton.cpp:662 #20 0x00f12f54 in QApplicationPrivate::notify_helper (this=0x9f78c80, receiver=0xb074aa8, e=0xbfb35080) at kernel/qapplication.cpp:4056 #21 0x00f1b033 in QApplication::notify (this=0xbfb36a64, receiver=0xb074aa8, e=0xbfb35080) at kernel/qapplication.cpp:3758 #22 0x00660bfa in KApplication::notify (this=0xbfb36a64, receiver=0xb074aa8, event=0xbfb35080) at ../../kdeui/kernel/kapplication.cpp:302 #23 0x01b2d6cb in QCoreApplication::notifyInternal (this=0xbfb36a64, receiver=0xb074aa8, event=0xbfb35080) at kernel/qcoreapplication.cpp:610 #24 0x00f19f6e in QCoreApplication::sendSpontaneousEvent (receiver=0xb074aa8, event=0xbfb35080, alienWidget=0xb074aa8, nativeWidget=0xae8c1f8, buttonDown=0x178daa0, lastMouseReceiver=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #25 QApplicationPrivate::sendMouseEvent (receiver=0xb074aa8, event=0xbfb35080, alienWidget=0xb074aa8, nativeWidget=0xae8c1f8, buttonDown=0x178daa0, lastMouseReceiver=...) at kernel/qapplication.cpp:2924 #26 0x00f887c0 in QETWidget::translateMouseEvent (this=0xae8c1f8, event=0xbfb366cc) at kernel/qapplication_x11.cpp:4409 #27 0x00f87c4b in QApplication::x11ProcessEvent (this=0xbfb36a64, event=0xbfb366cc) at kernel/qapplication_x11.cpp:3428 #28 0x00fb4502 in x11EventSourceDispatch (s=0x9f701b0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #29 0x06cb1e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #30 0x06cb5730 in ?? () from /lib/libglib-2.0.so.0 #31 0x06cb5863 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #32 0x01b5802c in QEventDispatcherGlib::processEvents (this=0x9f4f9f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #33 0x00fb3be5 in QGuiEventDispatcherGlib::processEvents (this=0x9f4f9f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #34 0x01b2bc79 in QEventL
[Bug 233523] New: KDE Kontact failed when a journal and an address book entry were both open for editing at the same time.
https://bugs.kde.org/show_bug.cgi?id=233523 Summary: KDE Kontact failed when a journal and an address book entry were both open for editing at the same time. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: 1. INFORMATION OF THE EVENTS LEADING TO THE FAILURE: 1.1. A journal entry was opened for editing. 1.2. Shortly thereafter, an address book was opened for editing. 1.3. Both entries were then open at the same time. 1.4. An attempt was made to copy information from the addresss book entry. 1.5. KDE Kontact failed at this point. 2. INFORMATION ON THE COMPUTER SYSTEM: 2.1. The computer system was using an AMD Athlon 32 bit processor with 512 MB of Direct Access Memory (DAM). 2.2. The operating system (OS) was LInux, Ubuntu, version 9.10, 32 bit. 3. INFORMATION ON OTHER APPLICATIONS RUNNING ON THE SYSTEM WHEN THE FAILURE OCCURRED: 3.1. File browser. 3.2. Firefox web browser. 3.3. Firefox web browser library. 3.4. Gnome Text Editor (GEdit). 3.5. Open Office Work Sheet (spreadsheet) 3.5. Gnome Desktop. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QCoreApplication::notifyInternal (this=0xbf8fd5b4, receiver=0x0, event=0xbf8fc27c) at kernel/qcoreapplication.cpp:594 #7 0x00ff4475 in QCoreApplication::sendEvent (this=0x8e68358, event=0xbf8fc27c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #8 QWidget::event (this=0x8e68358, event=0xbf8fc27c) at kernel/qwidget.cpp:7845 #9 0x00f9ef54 in QApplicationPrivate::notify_helper (this=0x85e9e28, receiver=0x8e68358, e=0xbf8fc27c) at kernel/qapplication.cpp:4056 #10 0x00fa65ca in QApplication::notify (this=0xbf8fd5b4, receiver=0x8e68358, e=0xbf8fc27c) at kernel/qapplication.cpp:4021 #11 0x003fbbfa in KApplication::notify (this=0xbf8fd5b4, receiver=0x8e68358, event=0xbf8fc27c) at ../../kdeui/kernel/kapplication.cpp:302 #12 0x00d496cb in QCoreApplication::notifyInternal (this=0xbf8fd5b4, receiver=0x8e68358, event=0xbf8fc27c) at kernel/qcoreapplication.cpp:610 #13 0x00ff4475 in QCoreApplication::sendEvent (this=0x8791f08, event=0xbf8fc27c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #14 QWidget::event (this=0x8791f08, event=0xbf8fc27c) at kernel/qwidget.cpp:7845 #15 0x013a3633 in QFrame::event (this=0x8791f08, e=0xbf8fc27c) at widgets/qframe.cpp:559 #16 0x01412b24 in QStackedWidget::event (this=0x8791f08, e=0xbf8fc27c) at widgets/qstackedwidget.cpp:289 #17 0x00f9ef54 in QApplicationPrivate::notify_helper (this=0x85e9e28, receiver=0x8791f08, e=0xbf8fc27c) at kernel/qapplication.cpp:4056 #18 0x00fa65ca in QApplication::notify (this=0xbf8fd5b4, receiver=0x8791f08, e=0xbf8fc27c) at kernel/qapplication.cpp:4021 #19 0x003fbbfa in KApplication::notify (this=0xbf8fd5b4, receiver=0x8791f08, event=0xbf8fc27c) at ../../kdeui/kernel/kapplication.cpp:302 #20 0x00d496cb in QCoreApplication::notifyInternal (this=0xbf8fd5b4, receiver=0x8791f08, event=0xbf8fc27c) at kernel/qcoreapplication.cpp:610 #21 0x00ff4475 in QCoreApplication::sendEvent (this=0x873e860, event=0xbf8fc27c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #22 QWidget::event (this=0x873e860, event=0xbf8fc27c) at kernel/qwidget.cpp:7845 #23 0x01411e24 in QSplitter::event (this=0x873e860, e=0xbf8fc27c) at widgets/qsplitter.cpp:1338 #24 0x00f9ef54 in QApplicationPrivate::notify_helper (this=0x85e9e28, receiver=0x873e860, e=0xbf8fc27c) at kernel/qapplication.cpp:4056 #25 0x00fa65ca in QApplication::notify (this=0xbf8fd5b4, receiver=0x873e860, e=0xbf8fc27c) at kernel/qapplication.cpp:4021 #26 0x003fbbfa in KApplication::notify (this=0xbf8fd5b4, receiver=0x873e860, event=0xbf8fc27c) at ../../kdeui/kernel/kapplication.cpp:302 #27 0x00d496cb in QCoreApplication::notifyInternal (this=0xbf8fd5b4, receiver=0x873e860, event=0xbf8fc27c) at kernel/qcoreapplication.cpp:610 #28 0x00ff4475 in QCoreApplication::sendEvent (this=0x875ee40, event=0xbf8fc27c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #29 QWidget::event (this=0x875ee40, event=0xbf8fc27c) at kernel/qwidget.cpp:7845 #30 0x00f9ef54 in QApplicationPrivate::notify_helper (this=0x85e9e28, receiver=0x875ee40, e=0xbf8fc27c) at kernel/qapplication.cpp:4056 #31 0x00fa65ca in QApplication::notify (this=0xbf8fd5b4, receiver=0x875ee40, e=0xbf8fc27c) at kernel/qapplication.cpp:4021 #32 0x003fbbfa in KApplication::notify (this=0xbf8fd5b4, receiver=0x875ee40, event=0xbf8fc27c) at ../../kdeui/kernel/kapplication.
[Bug 227763] New: KDE Kmail application crashed when an e-mail message was being opened for reading.
https://bugs.kde.org/show_bug.cgi?id=227763 Summary: KDE Kmail application crashed when an e-mail message was being opened for reading. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: 1. Before the crash occurred, I had just started composing an e-mail message which I terminated. 2. I then went to the messages listed in the Inbox and clicked the mouse on an e-mail message therein. 3. KDE Kontact crashed immediately thereafter. 3. I was running KDE Kontact on Ubuntu Linux 9.10, 64 bit version using the standard desktop (not the KDE Desktop). The CPU is an Intel Core 2 Duo unit. The motherboard is model no. P5B made by Asus with 2.0 GB of memory. 3. The following applications were running on the computer system when the crash occurred: 5.1. Gnome File Browser. 5.2. Kmail in KDE Kontact. 5.3. Gnome Text Editor. 5.4. Firefox. 5.5. Firefox Library. 5.6. Open Office Worksheet (ODS). -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 KMail::MessageListView::Widget::getSelectionStats (this=0x2839a30, selectedSernums=..., selectedVisibleSernums=, allSelectedBelongToSameThread=, includeCollapsedChildren=) at ../../kmail/messagelistview/widget.cpp:580 #6 0x7f009eb64c1e in KMMainWidget::updateMessageActions (this=0x28e4070) at ../../kmail/kmmainwidget.cpp:4274 #7 0x7f009eb7b7bd in KMMainWidget::qt_metacall (this=0x28e4070, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffd58e8c40) at ./kmmainwidget.moc:367 #8 0x7f00be485ddc in QMetaObject::activate (sender=0x2d03710, from_signal_index=, to_signal_index=, argv=0x0) at kernel/qobject.cpp:3113 #9 0x7f00be47fd83 in QObject::event (this=0x2d03710, e=0xe2) at kernel/qobject.cpp:1075 #10 0x7f00bed90efc in QApplicationPrivate::notify_helper (this=0x21f1a00, receiver=0x2d03710, e=0x7fffd58e9240) at kernel/qapplication.cpp:4056 #11 0x7f00bed981ce in QApplication::notify (this=0x7fffd58e95a0, receiver=0x2d03710, e=0x7fffd58e9240) at kernel/qapplication.cpp:4021 #12 0x7f00bf9c7ab6 in KApplication::notify (this=0x7fffd58e95a0, receiver=0x2d03710, event=0x7fffd58e9240) at ../../kdeui/kernel/kapplication.cpp:302 #13 0x7f00be470c2c in QCoreApplication::notifyInternal (this=0x7fffd58e95a0, receiver=0x2d03710, event=0x7fffd58e9240) at kernel/qcoreapplication.cpp:610 #14 0x7f00be49b862 in QCoreApplication::sendEvent (this=0x21e8be0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #15 QTimerInfoList::activateTimers (this=0x21e8be0) at kernel/qeventdispatcher_unix.cpp:572 #16 0x7f00be49925d in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:165 #17 0x7f00b7ceabce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #18 0x7f00b7cee598 in ?? () from /lib/libglib-2.0.so.0 #19 0x7f00b7cee6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #20 0x7f00be4991a6 in QEventDispatcherGlib::processEvents (this=0x21bdcb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #21 0x7f00bee254be in QGuiEventDispatcherGlib::processEvents (this=0x288ecd0, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #22 0x7f00be46f532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #23 0x7f00be46f904 in QEventLoop::exec (this=0x7fffd58e94e0, flags=) at kernel/qeventloop.cpp:201 #24 0x7f00be471ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #25 0x00403f47 in main (argc=, argv=) at ../../../kontact/src/main.cpp:218 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
[Bug 224397] New: KDE Kontact failed when a journal entry was being saved
https://bugs.kde.org/show_bug.cgi?id=224397 Summary: KDE Kontact failed when a journal entry was being saved Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: 1. Before the crash occurred, I had created a new template for a journal entry. 2. I then saved a journal entry that I had created. 3. I was running KDE Kontact on Ubuntu Linux 9.10, 64 bit version using the standard desktop (not the KDE Desktop). The CPU is an Intel Core 2 Duo unit. The motherboard is model no. P5B made by Asus with 2.0 GB of memory. 3. The following applications were running on the computer system when the crash occurred: 5.1. Gnome File Browser. 5.2. Journal in KDE Kontact. 5.3. Gnome Text Editor. 5.4. Firefox -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x006064a0 in QString::shared_null () #6 0x7f21130dd94f in KOIncidenceEditor::slotManageTemplates (this=0x1fc0590) at ../../korganizer/koincidenceeditor.cpp:187 #7 0x7f21130df483 in KOIncidenceEditor::qt_metacall (this=0x1fc0590, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff89f31990) at ./koincidenceeditor.moc:133 #8 0x7f21130e3460 in KOJournalEditor::qt_metacall (this=0x0b0, _c=QMetaObject::InvokeMetaMethod, _id=-144, _a=0x1dbbc90) at ./kojournaleditor.moc:65 #9 0x7f213aa6bddc in QMetaObject::activate (sender=0x1fc0590, from_signal_index=, to_signal_index=, argv=0x1dbbc90) at kernel/qobject.cpp:3113 #10 0x7f213bf22315 in KDialog::slotButtonClicked (this=0x1fc0590, button=2) at ../../kdeui/dialogs/kdialog.cpp:893 #11 0x7f21130de3c5 in KOIncidenceEditor::slotButtonClicked (this=0x1fc0590, button=0) at ../../korganizer/koincidenceeditor.cpp:123 #12 0x7f213bf246b9 in KDialog::qt_metacall (this=0x1fc0590, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff89f31ca0) at ./kdialog.moc:184 #13 0x7f213bfd8a10 in KPageDialog::qt_metacall (this=0x0b0, _c=QMetaObject::InvokeMetaMethod, _id=-144, _a=0x1dbbc90) at ./kpagedialog.moc:64 #14 0x7f21130df1e0 in KOIncidenceEditor::qt_metacall (this=0x0b0, _c=QMetaObject::InvokeMetaMethod, _id=-144, _a=0x1dbbc90) at ./koincidenceeditor.moc:107 #15 0x7f21130e3460 in KOJournalEditor::qt_metacall (this=0x0b0, _c=QMetaObject::InvokeMetaMethod, _id=-144, _a=0x1dbbc90) at ./kojournaleditor.moc:65 #16 0x7f213aa6bddc in QMetaObject::activate (sender=0x1cc0cc8, from_signal_index=, to_signal_index=, argv=0x1dbbc90) at kernel/qobject.cpp:3113 #17 0x7f213aa6e90e in QSignalMapper::mapped (this=0x0b0, _t1=2) at .moc/release-shared/moc_qsignalmapper.cpp:95 #18 0x7f213aa6fb00 in QSignalMapper::map (this=0x1cc0cc8, sender=0xb169e0) at kernel/qsignalmapper.cpp:266 #19 0x7f213aa6fd70 in QSignalMapper::qt_metacall (this=0x1cc0cc8, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff89f31e30) at .moc/release-shared/moc_qsignalmapper.cpp:81 #20 0x7f213aa6bddc in QMetaObject::activate (sender=0xb169e0, from_signal_index=, to_signal_index=, argv=0x1dbbc90) at kernel/qobject.cpp:3113 #21 0x7f213b9788e7 in QAbstractButton::clicked (this=0x0b0, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #22 0x7f213b6da41b in QAbstractButtonPrivate::emitClicked (this=0x1c12560) at widgets/qabstractbutton.cpp:543 #23 0x7f213b6dc02b in QAbstractButtonPrivate::click (this=0x1c12560) at widgets/qabstractbutton.cpp:536 #24 0x7f213b6dc275 in QAbstractButton::mouseReleaseEvent (this=0xb169e0, e=0x7fff89f32550) at widgets/qabstractbutton.cpp:1115 #25 0x7f213b3c59c0 in QWidget::event (this=0xb169e0, event=0x7fff89f32550) at kernel/qwidget.cpp:7549 #26 0x7f213b376efc in QApplicationPrivate::notify_helper (this=0xb483c0, receiver=0xb169e0, e=0x7fff89f32550) at kernel/qapplication.cpp:4056 #27 0x7f213b37e011 in QApplication::notify (this=, receiver=0xb169e0, e=0x7fff89f32550) at kernel/qapplication.cpp:3758 #28 0x7f213bfadab6 in KApplication::notify (this=0x7fff89f34470, receiver=0xb169e0, event=0x7fff89f32550) at ../../kdeui/kernel/kapplication.cpp:302 #29 0x7f213aa56c2c in QCoreApplication::notifyInternal (this=0x7fff89f34470, receiver=0xb169e0, event=0x7fff89f32550) at kernel/qcoreapplication.cpp:610 #30 0x7f213b37d8e0 in QCoreApplication::sendSpontaneousEvent (receiver=0xb169e0, event=0x7fff89f32550, alienWidget=0xb169e0, nativeWidget=0x1fc0590, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/cor
[Bug 221596] New: KDE Kontact failed when a To Do item corresponding to a reminder posted by the KOrganizer Reminder Daemon was being closed after it was edited.
https://bugs.kde.org/show_bug.cgi?id=221596 Summary: KDE Kontact failed when a To Do item corresponding to a reminder posted by the KOrganizer Reminder Daemon was being closed after it was edited. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: 1. Before the crash occurred, several reminders were posted by the KOrganizer Reminder Daemon. 2. I then edited a To Do item corresponding to one of the reminders posted by the KOrganizer Reminder Daemon. 3. I then commenced saving the edited To Do item at which time KDE Kontact failed and the Crash Reporting Assistant was automatically invoked. 4. I was running KDE Kontact on Ubuntu Linux 9.10, 64 bit version using the standard desktop (not the KDE Desktop). The CPU is an Intel Core 2 Duo unit. The motherboard is model no. K5B made by Asus with 2.0 GB of memory. 5. The following applications were running on the computer system when the crash occurred: 5.1. Gnome File Browser. 5.2. To Do function in KDE Kontact. 5.3. Gnome Text Editor. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 QHash::findNode (this=0x2552c78, akey=, ahp=0x0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:857 #6 0x7f765250db14 in QHash::contains (this=0x2585db8, sender=0x20f27a0) at ../../include/QtCore/../../src/corelib/tools/qhash.h:847 #7 QSignalMapper::map (this=0x2585db8, sender=0x20f27a0) at kernel/qsignalmapper.cpp:267 #8 0x7f765250dd70 in QSignalMapper::qt_metacall (this=0x2585db8, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fffa1170d40) at .moc/release-shared/moc_qsignalmapper.cpp:81 #9 0x7f7652509ddc in QMetaObject::activate (sender=0x20f27a0, from_signal_index=, to_signal_index=, argv=0x20f27a0) at kernel/qobject.cpp:3113 #10 0x7f76534168e7 in QAbstractButton::clicked (this=0x2552c78, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #11 0x7f765317841b in QAbstractButtonPrivate::emitClicked (this=0x1c1bec0) at widgets/qabstractbutton.cpp:543 #12 0x7f765317a02b in QAbstractButtonPrivate::click (this=0x1c1bec0) at widgets/qabstractbutton.cpp:536 #13 0x7f765317a275 in QAbstractButton::mouseReleaseEvent (this=0x20f27a0, e=0x7fffa1171460) at widgets/qabstractbutton.cpp:1115 #14 0x7f7652e639c0 in QWidget::event (this=0x20f27a0, event=0x7fffa1171460) at kernel/qwidget.cpp:7549 #15 0x7f7652e14efc in QApplicationPrivate::notify_helper (this=0xf90680, receiver=0x20f27a0, e=0x7fffa1171460) at kernel/qapplication.cpp:4056 #16 0x7f7652e1c011 in QApplication::notify (this=, receiver=0x20f27a0, e=0x7fffa1171460) at kernel/qapplication.cpp:3758 #17 0x7f7653a4bab6 in KApplication::notify (this=0x7fffa1173380, receiver=0x20f27a0, event=0x7fffa1171460) at ../../kdeui/kernel/kapplication.cpp:302 #18 0x7f76524f4c2c in QCoreApplication::notifyInternal (this=0x7fffa1173380, receiver=0x20f27a0, event=0x7fffa1171460) at kernel/qcoreapplication.cpp:610 #19 0x7f7652e1b8e0 in QCoreApplication::sendSpontaneousEvent (receiver=0x20f27a0, event=0x7fffa1171460, alienWidget=0x20f27a0, nativeWidget=0x2079300, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #20 QApplicationPrivate::sendMouseEvent (receiver=0x20f27a0, event=0x7fffa1171460, alienWidget=0x20f27a0, nativeWidget=0x2079300, buttonDown=, lastMouseReceiver=) at kernel/qapplication.cpp:2924 #21 0x7f7652e81a0e in QETWidget::translateMouseEvent (this=0x2079300, event=) at kernel/qapplication_x11.cpp:4409 #22 0x7f7652e80aa9 in QApplication::x11ProcessEvent (this=, event=0x7fffa1172f90) at kernel/qapplication_x11.cpp:3550 #23 0x7f7652ea9d0c in x11EventSourceDispatch (s=, callback=, user_data=) at kernel/qguieventdispatcher_glib.cpp:146 #24 0x7f764bd6ebce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #25 0x7f764bd72598 in ?? () from /lib/libglib-2.0.so.0 #26 0x7f764bd726c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #27 0x7f765251d1a6 in QEventDispatcherGlib::processEvents (this=0xf5ccb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #28 0x7f7652ea94be in QGuiEventDispatcherGlib::processEvents (this=0x2552c78, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #29 0x7f76524f3532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #30 0x7f76524f3904 in QEventLoop::exec (this=0x7fffa11
[Bug 221574] New: KDE Kontact failed while e-mail messages in a Kmail folder were being examined.
https://bugs.kde.org/show_bug.cgi?id=221574 Summary: KDE Kontact failed while e-mail messages in a Kmail folder were being examined. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: 1. Before the crash occurred, I had copied some folders from one Kmail directory to another Kmail directory that I had just created. 2. I then opened the one of the directories that I had just copied. KDE Kontact then failed and the the KDE Crash reporting program was automatically invoked. 3. I was running KDE Kontact on Ubuntu Linux 9.10, 64 bit version using the standard desktop (not the KDE Desktop). The CPU is an Intel Core 2 Duo unit. The motherboard is model no. K5B made by Asus with 2.0 GB of memory. 4. The following applications were running on my computer system when the crash occurred: 4.1. Gnome File Browser. 4.2. KMail in KDE Kontact. 4.3. Gnome Text Editor. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x033e5da0 in ?? () #6 0x7f9b5073029a in KMReaderWin::parseMsg (this=0x27c8b70, aMsg=0x2d9c430) at ../../kmail/kmreaderwin.cpp:1681 #7 0x7f9b5071deda in KMReaderWin::displayMessage (this=0x27c8b70) at ../../kmail/kmreaderwin.cpp:1605 #8 0x7f9b5071e0b4 in KMReaderWin::updateReaderWin (this=0x27c8b70) at ../../kmail/kmreaderwin.cpp:1545 #9 0x7f9b50729f9d in KMReaderWin::qt_metacall (this=0x27c8b70, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff53b57380) at ./kmreaderwin.moc:168 #10 0x7f9b6c05dddc in QMetaObject::activate (sender=0x27c8c18, from_signal_index=, to_signal_index=, argv=0x1) at kernel/qobject.cpp:3113 #11 0x7f9b6c057d83 in QObject::event (this=0x27c8c18, e=0x7fff53b56ad0) at kernel/qobject.cpp:1075 #12 0x7f9b6c968efc in QApplicationPrivate::notify_helper (this=0x1b485b0, receiver=0x27c8c18, e=0x7fff53b57980) at kernel/qapplication.cpp:4056 #13 0x7f9b6c9701ce in QApplication::notify (this=0x7fff53b57ce0, receiver=0x27c8c18, e=0x7fff53b57980) at kernel/qapplication.cpp:4021 #14 0x7f9b6d59fab6 in KApplication::notify (this=0x7fff53b57ce0, receiver=0x27c8c18, event=0x7fff53b57980) at ../../kdeui/kernel/kapplication.cpp:302 #15 0x7f9b6c048c2c in QCoreApplication::notifyInternal (this=0x7fff53b57ce0, receiver=0x27c8c18, event=0x7fff53b57980) at kernel/qcoreapplication.cpp:610 #16 0x7f9b6c073862 in QCoreApplication::sendEvent (this=0x1b3fd40) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #17 QTimerInfoList::activateTimers (this=0x1b3fd40) at kernel/qeventdispatcher_unix.cpp:572 #18 0x7f9b6c07125d in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:165 #19 0x7f9b658c2bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #20 0x7f9b658c6598 in ?? () from /lib/libglib-2.0.so.0 #21 0x7f9b658c66c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #22 0x7f9b6c0711a6 in QEventDispatcherGlib::processEvents (this=0x1b14cb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #23 0x7f9b6c9fd4be in QGuiEventDispatcherGlib::processEvents (this=0x2d9c430, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #24 0x7f9b6c047532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #25 0x7f9b6c047904 in QEventLoop::exec (this=0x7fff53b57c20, flags=) at kernel/qeventloop.cpp:201 #26 0x7f9b6c049ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #27 0x00403f47 in main (argc=, argv=) at ../../../kontact/src/main.cpp:218 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
[Bug 219513] New: KDE Kontact failed when clicking on a message that was just sent.
https://bugs.kde.org/show_bug.cgi?id=219513 Summary: KDE Kontact failed when clicking on a message that was just sent. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: I had just sent a message and saved it from the Sent folder in Kmail to the file browser in Ubuntu Linux. I then clicked on the same message in the Sent folder a second time. KDE Kontact then crashed. I was running KDE Kontact on Ubuntu Linux 9.10, 64 bit version. The CPU is an Intel Core 2 Duo unit. The motherboard is model no. K5B made by Asus. The following applications were running on my computer system: 1. Gnome File Browser. 2. KDE Kontact. 3. Firefox. 4. Thunderbird. 5. Openoffice.org Calc. 6. Gnome Text Editor. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x7fb60813cbc1 in KMail::MessageListView::Widget::viewStartDragRequest (this=) at ../../kmail/messagelistview/widget.cpp:776 #6 0x7fb60818726d in KMail::MessageListView::Core::View::mouseMoveEvent (this=0x1295420, e=) at ../../kmail/messagelistview/core/view.cpp:2074 #7 0x7fb623893822 in QWidget::event (this=0x1295420, event=0x7fff4589b0e0) at kernel/qwidget.cpp:7534 #8 0x7fb623bef2a6 in QFrame::event (this=0x1295420, e=0x7fff4589b0e0) at widgets/qframe.cpp:559 #9 0x7fb623d2221b in QAbstractItemView::viewportEvent (this=0x1295420, event=0x7fff4589b0e0) at itemviews/qabstractitemview.cpp:1476 #10 0x7fb623d59420 in QTreeView::viewportEvent (this=0x1295420, event=0x7fff4589b0e0) at itemviews/qtreeview.cpp:1266 #11 0x7fb622f23f47 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=, receiver=0x162e340, event=0x7fff4589b0e0) at kernel/qcoreapplication.cpp:726 #12 0x7fb623844ecc in QApplicationPrivate::notify_helper (this=0xfb3670, receiver=0x162e340, e=0x7fff4589b0e0) at kernel/qapplication.cpp:4052 #13 0x7fb62384c011 in QApplication::notify (this=, receiver=0x162e340, e=0x7fff4589b0e0) at kernel/qapplication.cpp:3758 #14 0x7fb62447bab6 in KApplication::notify (this=0x7fff4589d000, receiver=0x162e340, event=0x7fff4589b0e0) at ../../kdeui/kernel/kapplication.cpp:302 #15 0x7fb622f24c2c in QCoreApplication::notifyInternal (this=0x7fff4589d000, receiver=0x162e340, event=0x7fff4589b0e0) at kernel/qcoreapplication.cpp:610 #16 0x7fb62384b8e0 in QCoreApplication::sendSpontaneousEvent (receiver=0x162e340, event=0x7fff4589b0e0, alienWidget=0x162e340, nativeWidget=0xfb7970, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #17 QApplicationPrivate::sendMouseEvent (receiver=0x162e340, event=0x7fff4589b0e0, alienWidget=0x162e340, nativeWidget=0xfb7970, buttonDown=, lastMouseReceiver=) at kernel/qapplication.cpp:2924 #18 0x7fb6238b1a0e in QETWidget::translateMouseEvent (this=0xfb7970, event=) at kernel/qapplication_x11.cpp:4409 #19 0x7fb6238b0aa9 in QApplication::x11ProcessEvent (this=, event=0x7fff4589cc10) at kernel/qapplication_x11.cpp:3550 #20 0x7fb6238d9d0c in x11EventSourceDispatch (s=, callback=, user_data=) at kernel/qguieventdispatcher_glib.cpp:146 #21 0x7fb61c79ebbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #22 0x7fb61c7a2588 in ?? () from /lib/libglib-2.0.so.0 #23 0x7fb61c7a26b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #24 0x7fb622f4d1a6 in QEventDispatcherGlib::processEvents (this=0xf7fcb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #25 0x7fb6238d94be in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x7fb622f23532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #27 0x7fb622f23904 in QEventLoop::exec (this=0x7fff4589cf40, flags=) at kernel/qeventloop.cpp:201 #28 0x7fb622f25ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x00403f47 in main (argc=, argv=) at ../../../kontact/src/main.cpp:218 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
[Bug 219504] New: KDE Kontact crashed when I was adding addresses from the address book to a message that I was drafting in Kmail
https://bugs.kde.org/show_bug.cgi?id=219504 Summary: KDE Kontact crashed when I was adding addresses from the address book to a message that I was drafting in Kmail Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: KDE Kontact crashed when I was adding addresses from the address book to a message that I was drafting in Kmail. I was running KDE Kontact on Ubuntu Linux 9.10, 64 bit version. The CPU is an Intel Core 2 Duo unit. The motherboard is made by Asus. The following applications were running on my computer system: 1. Gnome File Browser. 2. KDE Kontact. 3. Firefox. 4. Thunderbird. 5. Openoffice.org Calc. 6. Gnome Text Editor. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 QBasicAtomicInt::ref (this=0x28ea440, item=0x2a61520) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #6 QString (this=0x28ea440, item=0x2a61520) at /usr/include/qt4/QtCore/qstring.h:712 #7 RecipientItem::key (this=0x28ea440, item=0x2a61520) at ../../kmail/recipientspicker.h:68 #8 RecipientsCollection::getEquivalentItem (this=0x28ea440, item=0x2a61520) at ../../kmail/recipientspicker.cpp:226 #9 0x7f88fea1c88b in RecipientsPicker::updateList (this=0x37c75c0) at ../../kmail/recipientspicker.cpp:606 #10 0x7f88fea1eeb2 in RecipientsPicker::setRecipients (this=, recipients=) at ../../kmail/recipientspicker.cpp:559 #11 0x7f88fea163a9 in SideWidget::pickRecipient (this=0x381b8b0) at ../../kmail/recipientseditor.cpp:851 #12 0x7f88fea17f04 in SideWidget::qt_metacall (this=0x381b8b0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff5072d4f0) at ./recipientseditor.moc:498 #13 0x7f891e193ddc in QMetaObject::activate (sender=0x267b140, from_signal_index=, to_signal_index=, argv=0xfff8b8e4) at kernel/qobject.cpp:3113 #14 0x7f891f0a08e7 in QAbstractButton::clicked (this=0x28ea440, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #15 0x7f891ee0241b in QAbstractButtonPrivate::emitClicked (this=0x27532d0) at widgets/qabstractbutton.cpp:543 #16 0x7f891ee0402b in QAbstractButtonPrivate::click (this=0x27532d0) at widgets/qabstractbutton.cpp:536 #17 0x7f891ee04275 in QAbstractButton::mouseReleaseEvent (this=0x267b140, e=0x7fff5072dc10) at widgets/qabstractbutton.cpp:1115 #18 0x7f891eaed9c0 in QWidget::event (this=0x267b140, event=0x7fff5072dc10) at kernel/qwidget.cpp:7549 #19 0x7f891ea9eefc in QApplicationPrivate::notify_helper (this=0x135b4f0, receiver=0x267b140, e=0x7fff5072dc10) at kernel/qapplication.cpp:4056 #20 0x7f891eaa6011 in QApplication::notify (this=, receiver=0x267b140, e=0x7fff5072dc10) at kernel/qapplication.cpp:3758 #21 0x7f891f6d5ab6 in KApplication::notify (this=0x7fff5072fb30, receiver=0x267b140, event=0x7fff5072dc10) at ../../kdeui/kernel/kapplication.cpp:302 #22 0x7f891e17ec2c in QCoreApplication::notifyInternal (this=0x7fff5072fb30, receiver=0x267b140, event=0x7fff5072dc10) at kernel/qcoreapplication.cpp:610 #23 0x7f891eaa58e0 in QCoreApplication::sendSpontaneousEvent (receiver=0x267b140, event=0x7fff5072dc10, alienWidget=0x267b140, nativeWidget=0x25c58c0, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #24 QApplicationPrivate::sendMouseEvent (receiver=0x267b140, event=0x7fff5072dc10, alienWidget=0x267b140, nativeWidget=0x25c58c0, buttonDown=, lastMouseReceiver=) at kernel/qapplication.cpp:2924 #25 0x7f891eb0ba0e in QETWidget::translateMouseEvent (this=0x25c58c0, event=) at kernel/qapplication_x11.cpp:4409 #26 0x7f891eb0aaa9 in QApplication::x11ProcessEvent (this=, event=0x7fff5072f740) at kernel/qapplication_x11.cpp:3550 #27 0x7f891eb33d0c in x11EventSourceDispatch (s=, callback=, user_data=) at kernel/qguieventdispatcher_glib.cpp:146 #28 0x7f89179f8bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #29 0x7f89179fc588 in ?? () from /lib/libglib-2.0.so.0 #30 0x7f89179fc6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #31 0x7f891e1a71a6 in QEventDispatcherGlib::processEvents (this=0x1327cb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #32 0x7f891eb334be in QGuiEventDispatcherGlib::processEvents (this=0x28ea440, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #33 0x7f891e17d532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #34 0x7f891e17d904
[Bug 219137] New: KDE Kontact crashed when I was moving an e-mail message from the Sent folder to the Archives Folder
https://bugs.kde.org/show_bug.cgi?id=219137 Summary: KDE Kontact crashed when I was moving an e-mail message from the Sent folder to the Archives Folder Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: This is a duplicate of Bug ID no. 218874. I would like to take this opportunity to suggest the following improvements to Kmail: 1. When manually saving an an e-mail message while it is being composed, the compose window should remain open. Currently, the only option is to "Save as Draft" and when doing the entire compose window is shut down, One has to then go to Drafts folder to open the message that was being drafted and then resume composing. This is very inefficient. 2. I hope that you will be able to provide a method of manually saving the message being composed without the compose window being closed. You may be aware that this is possible in Thunderbird. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x7f46572fabc1 in KMail::MessageListView::Widget::viewStartDragRequest (this=) at ../../kmail/messagelistview/widget.cpp:776 #6 0x7f465734526d in KMail::MessageListView::Core::View::mouseMoveEvent (this=0x20f2b50, e=) at ../../kmail/messagelistview/core/view.cpp:2074 #7 0x7f4672a51822 in QWidget::event (this=0x20f2b50, event=0x7fff8a17e790) at kernel/qwidget.cpp:7534 #8 0x7f4672dad2a6 in QFrame::event (this=0x20f2b50, e=0x7fff8a17e790) at widgets/qframe.cpp:559 #9 0x7f4672ee021b in QAbstractItemView::viewportEvent (this=0x20f2b50, event=0x7fff8a17e790) at itemviews/qabstractitemview.cpp:1476 #10 0x7f4672f17420 in QTreeView::viewportEvent (this=0x20f2b50, event=0x7fff8a17e790) at itemviews/qtreeview.cpp:1266 #11 0x7f46720e1f47 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=, receiver=0x274dab0, event=0x7fff8a17e790) at kernel/qcoreapplication.cpp:726 #12 0x7f4672a02ecc in QApplicationPrivate::notify_helper (this=0x14be6b0, receiver=0x274dab0, e=0x7fff8a17e790) at kernel/qapplication.cpp:4052 #13 0x7f4672a0a011 in QApplication::notify (this=, receiver=0x274dab0, e=0x7fff8a17e790) at kernel/qapplication.cpp:3758 #14 0x7f4673639ab6 in KApplication::notify (this=0x7fff8a1806b0, receiver=0x274dab0, event=0x7fff8a17e790) at ../../kdeui/kernel/kapplication.cpp:302 #15 0x7f46720e2c2c in QCoreApplication::notifyInternal (this=0x7fff8a1806b0, receiver=0x274dab0, event=0x7fff8a17e790) at kernel/qcoreapplication.cpp:610 #16 0x7f4672a098e0 in QCoreApplication::sendSpontaneousEvent (receiver=0x274dab0, event=0x7fff8a17e790, alienWidget=0x274dab0, nativeWidget=0x1708690, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #17 QApplicationPrivate::sendMouseEvent (receiver=0x274dab0, event=0x7fff8a17e790, alienWidget=0x274dab0, nativeWidget=0x1708690, buttonDown=, lastMouseReceiver=) at kernel/qapplication.cpp:2924 #18 0x7f4672a6fa0e in QETWidget::translateMouseEvent (this=0x1708690, event=) at kernel/qapplication_x11.cpp:4409 #19 0x7f4672a6eaa9 in QApplication::x11ProcessEvent (this=, event=0x7fff8a1802c0) at kernel/qapplication_x11.cpp:3550 #20 0x7f4672a97d0c in x11EventSourceDispatch (s=, callback=, user_data=) at kernel/qguieventdispatcher_glib.cpp:146 #21 0x7f466b95cbbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #22 0x7f466b960588 in ?? () from /lib/libglib-2.0.so.0 #23 0x7f466b9606b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #24 0x7f467210b1a6 in QEventDispatcherGlib::processEvents (this=0x148acb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #25 0x7f4672a974be in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x7f46720e1532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #27 0x7f46720e1904 in QEventLoop::exec (this=0x7fff8a1805f0, flags=) at kernel/qeventloop.cpp:201 #28 0x7f46720e3ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x00403f47 in main (argc=, argv=) at ../../../kontact/src/main.cpp:218 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
[Bug 219129] New: KDE Kontact crashed when I was using Firefox.
https://bugs.kde.org/show_bug.cgi?id=219129 Summary: KDE Kontact crashed when I was using Firefox. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: I was using Firefox and working in a web site when the KDE Crash Reporting Assistant popped up. About 30 minutes before I started using Firefox, I had saved an e-mail message from Kmail to the Ubuntu Linux File System. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 KMail::MessageListView::Widget::getSelectionStats (this=0x20589d0, selectedSernums=..., selectedVisibleSernums=, allSelectedBelongToSameThread=, includeCollapsedChildren=) at ../../kmail/messagelistview/widget.cpp:580 #6 0x7f53a268dc1e in KMMainWidget::updateMessageActions (this=0x2059590) at ../../kmail/kmmainwidget.cpp:4274 #7 0x7f53a26a47bd in KMMainWidget::qt_metacall (this=0x2059590, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff8c96f120) at ./kmmainwidget.moc:367 #8 0x7f53bd5c9ddc in QMetaObject::activate (sender=0x23f7230, from_signal_index=, to_signal_index=, argv=0x0) at kernel/qobject.cpp:3113 #9 0x7f53bd5c3d83 in QObject::event (this=0x23f7230, e=0x1) at kernel/qobject.cpp:1075 #10 0x7f53bded4efc in QApplicationPrivate::notify_helper (this=0x18a7620, receiver=0x23f7230, e=0x7fff8c96f720) at kernel/qapplication.cpp:4056 #11 0x7f53bdedc1ce in QApplication::notify (this=0x7fff8c96fa80, receiver=0x23f7230, e=0x7fff8c96f720) at kernel/qapplication.cpp:4021 #12 0x7f53beb0bab6 in KApplication::notify (this=0x7fff8c96fa80, receiver=0x23f7230, event=0x7fff8c96f720) at ../../kdeui/kernel/kapplication.cpp:302 #13 0x7f53bd5b4c2c in QCoreApplication::notifyInternal (this=0x7fff8c96fa80, receiver=0x23f7230, event=0x7fff8c96f720) at kernel/qcoreapplication.cpp:610 #14 0x7f53bd5df862 in QCoreApplication::sendEvent (this=0x189fae0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #15 QTimerInfoList::activateTimers (this=0x189fae0) at kernel/qeventdispatcher_unix.cpp:572 #16 0x7f53bd5dd25d in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:165 #17 0x7f53b6e2ebbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #18 0x7f53b6e32588 in ?? () from /lib/libglib-2.0.so.0 #19 0x7f53b6e326b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #20 0x7f53bd5dd1a6 in QEventDispatcherGlib::processEvents (this=0x1873cb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #21 0x7f53bdf694be in QGuiEventDispatcherGlib::processEvents (this=0x2047120, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #22 0x7f53bd5b3532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #23 0x7f53bd5b3904 in QEventLoop::exec (this=0x7fff8c96f9c0, flags=) at kernel/qeventloop.cpp:201 #24 0x7f53bd5b5ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #25 0x00403f47 in main (argc=, argv=) at ../../../kontact/src/main.cpp:218 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
[Bug 219103] New: KDE Kontact crashed while I was trying to save a message from Kmail to the Ubuntu file browser.
https://bugs.kde.org/show_bug.cgi?id=219103 Summary: KDE Kontact crashed while I was trying to save a message from Kmail to the Ubuntu file browser. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: 1. KDE Kontact crashed and it could not be restarted. I had to restart Ubuntu Linux in order to restart KDE Kontact. This happenned at least three times before your bug reporting software was automatically invoked. 2. I am using Ubuntu Linux 9.10, 64 bit, using an Intel Core 2 Duo CPU on an Asus K5B motherboard. I do not find such crashes ocurring when I use any version of Thunbderbird for processing mail including saving e-mail messages to the Ubuntu File browser. 3. There seem to be other serious problems with Kmail in particular. For example, it is not possible to save an e-mail message from Kmail to the Ubuntu Linux file browser without also saving attachments at the same time. It should be possible to separate messages and attachments thereto. Even after unchecking the "inline" feature and checking the "hide" feature in Kmail, the attachments coninue to be saved in the message itself. 4. I would like to use Kmail and other KDE Kontact applications because of the integrated architecture and various features. For example, the ability to select the format of the time displayed in Kmail is a VERY USEFUL and IMPORTANT feature. On the other hand, there are many features missing or that need to be improved. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x7f15ebb3c612 in KMail::MessageListView::Widget::getSelectionStats (this=0x1dc2eb0, selectedSernums=..., selectedVisibleSernums=, allSelectedBelongToSameThread=, includeCollapsedChildren=) at ../../kmail/messagelistview/widget.cpp:580 #6 0x7f15eb9ffc1e in KMMainWidget::updateMessageActions (this=0x1dc1670) at ../../kmail/kmmainwidget.cpp:4274 #7 0x7f15ebb3f4a7 in KMail::MessageListView::Widget::viewMessageListContextPopupRequest (this=0x1dc2eb0, selectedItems=..., globalPos=...) at ../../kmail/messagelistview/widget.cpp:608 #8 0x7f15ebb8d0e6 in KMail::MessageListView::Core::View::mousePressEvent (this=0x1a39180, e=) at ../../kmail/messagelistview/core/view.cpp:2015 #9 0x7f160bcf09a6 in QWidget::event (this=0x1a39180, event=0x7fffe253a7c0) at kernel/qwidget.cpp:7545 #10 0x7f160c04c2a6 in QFrame::event (this=0x1a39180, e=0x7fffe253a7c0) at widgets/qframe.cpp:559 #11 0x7f160c17f21b in QAbstractItemView::viewportEvent (this=0x1a39180, event=0x7fffe253a7c0) at itemviews/qabstractitemview.cpp:1476 #12 0x7f160c1b6420 in QTreeView::viewportEvent (this=0x1a39180, event=0x7fffe253a7c0) at itemviews/qtreeview.cpp:1266 #13 0x7f160b380f47 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=, receiver=0x1dcf080, event=0x7fffe253a7c0) at kernel/qcoreapplication.cpp:726 #14 0x7f160bca1ecc in QApplicationPrivate::notify_helper (this=0x17584f0, receiver=0x1dcf080, e=0x7fffe253a7c0) at kernel/qapplication.cpp:4052 #15 0x7f160bca9011 in QApplication::notify (this=, receiver=0x1dcf080, e=0x7fffe253a7c0) at kernel/qapplication.cpp:3758 #16 0x7f160c8d8ab6 in KApplication::notify (this=0x7fffe253c6e0, receiver=0x1dcf080, event=0x7fffe253a7c0) at ../../kdeui/kernel/kapplication.cpp:302 #17 0x7f160b381c2c in QCoreApplication::notifyInternal (this=0x7fffe253c6e0, receiver=0x1dcf080, event=0x7fffe253a7c0) at kernel/qcoreapplication.cpp:610 #18 0x7f160bca88e0 in QCoreApplication::sendSpontaneousEvent (receiver=0x1dcf080, event=0x7fffe253a7c0, alienWidget=0x1dcf080, nativeWidget=0x175a170, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #19 QApplicationPrivate::sendMouseEvent (receiver=0x1dcf080, event=0x7fffe253a7c0, alienWidget=0x1dcf080, nativeWidget=0x175a170, buttonDown=, lastMouseReceiver=) at kernel/qapplication.cpp:2924 #20 0x7f160bd0ea0e in QETWidget::translateMouseEvent (this=0x175a170, event=) at kernel/qapplication_x11.cpp:4409 #21 0x7f160bd0daa9 in QApplication::x11ProcessEvent (this=, event=0x7fffe253c2f0) at kernel/qapplication_x11.cpp:3550 #22 0x7f160bd36d0c in x11EventSourceDispatch (s=, callback=, user_data=) at kernel/qguieventdispatcher_glib.cpp:146 #23 0x7f1604bfbbbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #24 0x7f1604bff588 in ?? () from /lib/libglib-2.0.so.0 #25
[Bug 218874] New: KDE Kontact crashed when I was moving a message from the Sent folder to the Archives folder.
https://bugs.kde.org/show_bug.cgi?id=218874 Summary: KDE Kontact crashed when I was moving a message from the Sent folder to the Archives folder. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: I had just sent an e-mail message and I wanted to archive it. KDE Kontact crashed when I was moving the message from the Sent folder to the folder called Archives that I had previously created. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x7f43bcd70bc1 in KMail::MessageListView::Widget::viewStartDragRequest (this=) at ../../kmail/messagelistview/widget.cpp:776 #6 0x7f43bcdbb26d in KMail::MessageListView::Core::View::mouseMoveEvent (this=0x1d951d0, e=) at ../../kmail/messagelistview/core/view.cpp:2074 #7 0x7f43d8cc8822 in QWidget::event (this=0x1d951d0, event=0x73e75920) at kernel/qwidget.cpp:7534 #8 0x7f43d90242a6 in QFrame::event (this=0x1d951d0, e=0x73e75920) at widgets/qframe.cpp:559 #9 0x7f43d915721b in QAbstractItemView::viewportEvent (this=0x1d951d0, event=0x73e75920) at itemviews/qabstractitemview.cpp:1476 #10 0x7f43d918e420 in QTreeView::viewportEvent (this=0x1d951d0, event=0x73e75920) at itemviews/qtreeview.cpp:1266 #11 0x7f43d8358f47 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=, receiver=0x1d8e800, event=0x73e75920) at kernel/qcoreapplication.cpp:726 #12 0x7f43d8c79ecc in QApplicationPrivate::notify_helper (this=0x14c8180, receiver=0x1d8e800, e=0x73e75920) at kernel/qapplication.cpp:4052 #13 0x7f43d8c81011 in QApplication::notify (this=, receiver=0x1d8e800, e=0x73e75920) at kernel/qapplication.cpp:3758 #14 0x7f43d98b0ab6 in KApplication::notify (this=0x73e77840, receiver=0x1d8e800, event=0x73e75920) at ../../kdeui/kernel/kapplication.cpp:302 #15 0x7f43d8359c2c in QCoreApplication::notifyInternal (this=0x73e77840, receiver=0x1d8e800, event=0x73e75920) at kernel/qcoreapplication.cpp:610 #16 0x7f43d8c808e0 in QCoreApplication::sendSpontaneousEvent (receiver=0x1d8e800, event=0x73e75920, alienWidget=0x1d8e800, nativeWidget=0x14c6e10, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #17 QApplicationPrivate::sendMouseEvent (receiver=0x1d8e800, event=0x73e75920, alienWidget=0x1d8e800, nativeWidget=0x14c6e10, buttonDown=, lastMouseReceiver=) at kernel/qapplication.cpp:2924 #18 0x7f43d8ce6a0e in QETWidget::translateMouseEvent (this=0x14c6e10, event=) at kernel/qapplication_x11.cpp:4409 #19 0x7f43d8ce5aa9 in QApplication::x11ProcessEvent (this=, event=0x73e77450) at kernel/qapplication_x11.cpp:3550 #20 0x7f43d8d0ed0c in x11EventSourceDispatch (s=, callback=, user_data=) at kernel/qguieventdispatcher_glib.cpp:146 #21 0x7f43d1bd3bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #22 0x7f43d1bd7588 in ?? () from /lib/libglib-2.0.so.0 #23 0x7f43d1bd76b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #24 0x7f43d83821a6 in QEventDispatcherGlib::processEvents (this=0x1494cb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #25 0x7f43d8d0e4be in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x7f43d8358532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #27 0x7f43d8358904 in QEventLoop::exec (this=0x73e77780, flags=) at kernel/qeventloop.cpp:201 #28 0x7f43d835aab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x00403f47 in main (argc=, argv=) at ../../../kontact/src/main.cpp:218 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
[Bug 218753] New: The crash occurred when the address book was being opened while composing an e-mail message in Kmail.
https://bugs.kde.org/show_bug.cgi?id=218753 Summary: The crash occurred when the address book was being opened while composing an e-mail message in Kmail. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: The crash occurred when the address book was being opened while composing an e-mail message in Kmail. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 QBasicAtomicInt::deref (this=0x3fb5b78, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:133 #6 QString::operator= (this=0x3fb5b78, other=...) at tools/qstring.cpp:1132 #7 0x7f1e18220a49 in RecipientItem::setRecipientType (this=0x4006830) at ../../kmail/recipientspicker.cpp:153 #8 RecipientsPicker::updateList (this=0x4006830) at ../../kmail/recipientspicker.cpp:610 #9 0x7f1e18222eb2 in RecipientsPicker::setRecipients (this=, recipients=) at ../../kmail/recipientspicker.cpp:559 #10 0x7f1e1821a3a9 in SideWidget::pickRecipient (this=0x2c72b20) at ../../kmail/recipientseditor.cpp:851 #11 0x7f1e1821bf04 in SideWidget::qt_metacall (this=0x2c72b20, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff06e153b0) at ./recipientseditor.moc:498 #12 0x7f1e3308dddc in QMetaObject::activate (sender=0x2c74b50, from_signal_index=, to_signal_index=, argv=0x3a3b09a) at kernel/qobject.cpp:3113 #13 0x7f1e33f9a8e7 in QAbstractButton::clicked (this=0x3fb5b78, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #14 0x7f1e33cfc41b in QAbstractButtonPrivate::emitClicked (this=0x2c74bc0) at widgets/qabstractbutton.cpp:543 #15 0x7f1e33cfe02b in QAbstractButtonPrivate::click (this=0x2c74bc0) at widgets/qabstractbutton.cpp:536 #16 0x7f1e33cfe275 in QAbstractButton::mouseReleaseEvent (this=0x2c74b50, e=0x7fff06e15ad0) at widgets/qabstractbutton.cpp:1115 #17 0x7f1e339e79c0 in QWidget::event (this=0x2c74b50, event=0x7fff06e15ad0) at kernel/qwidget.cpp:7549 #18 0x7f1e33998efc in QApplicationPrivate::notify_helper (this=0x25ecc00, receiver=0x2c74b50, e=0x7fff06e15ad0) at kernel/qapplication.cpp:4056 #19 0x7f1e339a0011 in QApplication::notify (this=, receiver=0x2c74b50, e=0x7fff06e15ad0) at kernel/qapplication.cpp:3758 #20 0x7f1e345cfab6 in KApplication::notify (this=0x7fff06e179f0, receiver=0x2c74b50, event=0x7fff06e15ad0) at ../../kdeui/kernel/kapplication.cpp:302 #21 0x7f1e33078c2c in QCoreApplication::notifyInternal (this=0x7fff06e179f0, receiver=0x2c74b50, event=0x7fff06e15ad0) at kernel/qcoreapplication.cpp:610 #22 0x7f1e3399f8e0 in QCoreApplication::sendSpontaneousEvent (receiver=0x2c74b50, event=0x7fff06e15ad0, alienWidget=0x2c74b50, nativeWidget=0x291f7c0, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #23 QApplicationPrivate::sendMouseEvent (receiver=0x2c74b50, event=0x7fff06e15ad0, alienWidget=0x2c74b50, nativeWidget=0x291f7c0, buttonDown=, lastMouseReceiver=) at kernel/qapplication.cpp:2924 #24 0x7f1e33a05a0e in QETWidget::translateMouseEvent (this=0x291f7c0, event=) at kernel/qapplication_x11.cpp:4409 #25 0x7f1e33a04aa9 in QApplication::x11ProcessEvent (this=, event=0x7fff06e17600) at kernel/qapplication_x11.cpp:3550 #26 0x7f1e33a2dd0c in x11EventSourceDispatch (s=, callback=, user_data=) at kernel/qguieventdispatcher_glib.cpp:146 #27 0x7f1e2c8f2bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #28 0x7f1e2c8f6588 in ?? () from /lib/libglib-2.0.so.0 #29 0x7f1e2c8f66b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #30 0x7f1e330a11a6 in QEventDispatcherGlib::processEvents (this=0x25b9cb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #31 0x7f1e33a2d4be in QGuiEventDispatcherGlib::processEvents (this=0x3fb5b78, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #32 0x7f1e33077532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #33 0x7f1e33077904 in QEventLoop::exec (this=0x7fff06e17930, flags=) at kernel/qeventloop.cpp:201 #34 0x7f1e33079ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #35 0x00403f47 in main (argc=, argv=) at ../../../kontact/src/main.cpp:218 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. ___
[Bug 218748] New: The crash occurred while an e-mail message was being read and/or saved in Kmail.
https://bugs.kde.org/show_bug.cgi?id=218748 Summary: The crash occurred while an e-mail message was being read and/or saved in Kmail. Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: An e-mail message was just saved in the Ubuntu File Browser and it was being examined there when Kontact crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 KMail::MessageListView::Widget::getSelectionStats (this=0x2ade360, selectedSernums=..., selectedVisibleSernums=, allSelectedBelongToSameThread=, includeCollapsedChildren=) at ../../kmail/messagelistview/widget.cpp:580 #6 0x7f46379ffc1e in KMMainWidget::updateMessageActions (this=0x2adbbd0) at ../../kmail/kmmainwidget.cpp:4274 #7 0x7f4637a167bd in KMMainWidget::qt_metacall (this=0x2adbbd0, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff25b5d530) at ./kmmainwidget.moc:367 #8 0x7f4657353ddc in QMetaObject::activate (sender=0x2e69f20, from_signal_index=, to_signal_index=, argv=0x0) at kernel/qobject.cpp:3113 #9 0x7f465734dd83 in QObject::event (this=0x2e69f20, e=0x31) at kernel/qobject.cpp:1075 #10 0x7f4657c5eefc in QApplicationPrivate::notify_helper (this=0x2262f60, receiver=0x2e69f20, e=0x7fff25b5db30) at kernel/qapplication.cpp:4056 #11 0x7f4657c661ce in QApplication::notify (this=0x7fff25b5de90, receiver=0x2e69f20, e=0x7fff25b5db30) at kernel/qapplication.cpp:4021 #12 0x7f4658895ab6 in KApplication::notify (this=0x7fff25b5de90, receiver=0x2e69f20, event=0x7fff25b5db30) at ../../kdeui/kernel/kapplication.cpp:302 #13 0x7f465733ec2c in QCoreApplication::notifyInternal (this=0x7fff25b5de90, receiver=0x2e69f20, event=0x7fff25b5db30) at kernel/qcoreapplication.cpp:610 #14 0x7f4657369862 in QCoreApplication::sendEvent (this=0x225bda0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #15 QTimerInfoList::activateTimers (this=0x225bda0) at kernel/qeventdispatcher_unix.cpp:572 #16 0x7f465736725d in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:165 #17 0x7f4650bb8bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #18 0x7f4650bbc588 in ?? () from /lib/libglib-2.0.so.0 #19 0x7f4650bbc6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #20 0x7f46573671a6 in QEventDispatcherGlib::processEvents (this=0x222fcb0, flags=) at kernel/qeventdispatcher_glib.cpp:327 #21 0x7f4657cf34be in QGuiEventDispatcherGlib::processEvents (this=0x28bdaa0, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #22 0x7f465733d532 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #23 0x7f465733d904 in QEventLoop::exec (this=0x7fff25b5ddd0, flags=) at kernel/qeventloop.cpp:201 #24 0x7f465733fab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #25 0x00403f47 in main (argc=, argv=) at ../../../kontact/src/main.cpp:218 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
[Bug 218604] New: KDE Kontact crashed when I was editing an entry in its To Do function
https://bugs.kde.org/show_bug.cgi?id=218604 Summary: KDE Kontact crashed when I was editing an entry in its To Do function Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sayeed...@gmail.com Application that crashed: kontact Version of the application: 4.3.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: KDE Kontact just shut down and the bug reporting application was automatically invoked. It had to be restarted. On restarting a window popped up. It stated that the application was still running and if Kontact was restarted it would result in loss of data. It, however, restarted without losso data. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 0x7fd72828094c in KOIncidenceEditor::slotManageTemplates (this=0x4779610) at ../../korganizer/koincidenceeditor.cpp:187 #6 0x7fd728282483 in KOIncidenceEditor::qt_metacall (this=0x4779610, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff58d95100) at ./koincidenceeditor.moc:133 #7 0x7fd728285030 in KOTodoEditor::qt_metacall (this=0x3904c00, _c=QMetaObject::InvokeMetaMethod, _id=-144, _a=0x45cab00) at ./kotodoeditor.moc:65 #8 0x7fd7523deddc in QMetaObject::activate (sender=0x4779610, from_signal_index=, to_signal_index=, argv=0x45cab00) at kernel/qobject.cpp:3113 #9 0x7fd753895315 in KDialog::slotButtonClicked (this=0x4779610, button=2) at ../../kdeui/dialogs/kdialog.cpp:893 #10 0x7fd7282813c5 in KOIncidenceEditor::slotButtonClicked (this=0x4779610, button=0) at ../../korganizer/koincidenceeditor.cpp:123 #11 0x7fd7538976b9 in KDialog::qt_metacall (this=0x4779610, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff58d95410) at ./kdialog.moc:184 #12 0x7fd75394ba10 in KPageDialog::qt_metacall (this=0x3904c00, _c=QMetaObject::InvokeMetaMethod, _id=-144, _a=0x45cab00) at ./kpagedialog.moc:64 #13 0x7fd7282821e0 in KOIncidenceEditor::qt_metacall (this=0x3904c00, _c=QMetaObject::InvokeMetaMethod, _id=-144, _a=0x45cab00) at ./koincidenceeditor.moc:107 #14 0x7fd728285030 in KOTodoEditor::qt_metacall (this=0x3904c00, _c=QMetaObject::InvokeMetaMethod, _id=-144, _a=0x45cab00) at ./kotodoeditor.moc:65 #15 0x7fd7523deddc in QMetaObject::activate (sender=0x34d5678, from_signal_index=, to_signal_index=, argv=0x45cab00) at kernel/qobject.cpp:3113 #16 0x7fd7523e190e in QSignalMapper::mapped (this=0x3904c00, _t1=2) at .moc/release-shared/moc_qsignalmapper.cpp:95 #17 0x7fd7523e2b00 in QSignalMapper::map (this=0x34d5678, sender=0x1f540e0) at kernel/qsignalmapper.cpp:266 #18 0x7fd7523e2d70 in QSignalMapper::qt_metacall (this=0x34d5678, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff58d955a0) at .moc/release-shared/moc_qsignalmapper.cpp:81 #19 0x7fd7523deddc in QMetaObject::activate (sender=0x1f540e0, from_signal_index=, to_signal_index=, argv=0x45cab00) at kernel/qobject.cpp:3113 #20 0x7fd7532eb8e7 in QAbstractButton::clicked (this=0x3904c00, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200 #21 0x7fd75304d41b in QAbstractButtonPrivate::emitClicked (this=0x3608880) at widgets/qabstractbutton.cpp:543 #22 0x7fd75304f02b in QAbstractButtonPrivate::click (this=0x3608880) at widgets/qabstractbutton.cpp:536 #23 0x7fd75304f275 in QAbstractButton::mouseReleaseEvent (this=0x1f540e0, e=0x7fff58d95cc0) at widgets/qabstractbutton.cpp:1115 #24 0x7fd752d389c0 in QWidget::event (this=0x1f540e0, event=0x7fff58d95cc0) at kernel/qwidget.cpp:7549 #25 0x7fd752ce9efc in QApplicationPrivate::notify_helper (this=0x15744f0, receiver=0x1f540e0, e=0x7fff58d95cc0) at kernel/qapplication.cpp:4056 #26 0x7fd752cf1011 in QApplication::notify (this=, receiver=0x1f540e0, e=0x7fff58d95cc0) at kernel/qapplication.cpp:3758 #27 0x7fd753920ab6 in KApplication::notify (this=0x7fff58d97be0, receiver=0x1f540e0, event=0x7fff58d95cc0) at ../../kdeui/kernel/kapplication.cpp:302 #28 0x7fd7523c9c2c in QCoreApplication::notifyInternal (this=0x7fff58d97be0, receiver=0x1f540e0, event=0x7fff58d95cc0) at kernel/qcoreapplication.cpp:610 #29 0x7fd752cf08e0 in QCoreApplication::sendSpontaneousEvent (receiver=0x1f540e0, event=0x7fff58d95cc0, alienWidget=0x1f540e0, nativeWidget=0x4779610, buttonDown=, lastMouseReceiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #30 QApplicationPrivate::sendMouseEvent (receiver=0x1f540e0, event=0x7fff58d95cc0, alienWidget=0x1f540e0, nativeWidget=0x4779610, buttonDown=, lastMouseReceiver=) at kernel/qapplication.cpp:2924 #31 0x7fd752d56a0e in QETWidget::trans
