[kontact] [Bug 369780] New: tweaking settings = crashes
https://bugs.kde.org/show_bug.cgi?id=369780 Bug ID: 369780 Summary: tweaking settings = crashes Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Was once again trying to change my identity and common folders attached to it - Custom settings of the application: down to 5 identities, about 8 IMAP account, and 2 gmail and one local And 100+ filters The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff82e40f7c0 (LWP 3043))] Thread 27 (Thread 0x7ff76f98c700 (LWP 3484)): #0 0x7ff8243d003f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff8186b186b in () at /usr/lib64/libQt5Script.so.5 #2 0x7ff8186b1899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7ff8243cc0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff82b05602d in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7ff771b13700 (LWP 3356)): #0 0x7ff82bb91bc0 in () at /usr/lib64/libQt5Core.so.5 #1 0x7ff823bae8f1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff823baedf8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff823baef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff82bb91d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff82bb38d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff82b95a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7ff82b95f32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff8243cc0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff82b05602d in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7ff7728f9700 (LWP 3121)): #0 0x7ff823b7fec0 in pthread_getspecific@plt () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff823bd4400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff823badecc in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff823baed25 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff823baef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff82bb91d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff82bb38d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7ff82b95a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7ff82b95f32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7ff8243cc0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7ff82b05602d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7ff7737fe700 (LWP 3083)): #0 0x7ff82ba10770 in QElapsedTimer::clockType() () at /usr/lib64/libQt5Core.so.5 #1 0x7ff82ba107a9 in QElapsedTimer::isMonotonic() () at /usr/lib64/libQt5Core.so.5 #2 0x7ff82bb9072e in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib64/libQt5Core.so.5 #3 0x7ff82bb90953 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff82bb91b5e in () at /usr/lib64/libQt5Core.so.5 #5 0x7ff823bae4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #6 0x7ff823baed80 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7ff823baef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #8 0x7ff82bb91d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7ff82bb38d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7ff82b95a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #11 0x7ff82b95f32f in () at /usr/lib64/libQt5Core.so.5 #12 0x7ff8243cc0a4 in start_thread () at /lib64/libpthread.so.0 #13 0x7ff82b05602d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7ff773fff700 (LWP 3082)): #0 0x7ff823bae4b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7ff823baed80 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff823baef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff82bb91d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff82bb38d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff82b95a61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff82b95f32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff8243cc0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff82b05602d in clone () at /lib64/li
[kontact] [Bug 369753] New: Too many filter/account leads Kontact/Kmail to crash
https://bugs.kde.org/show_bug.cgi?id=369753 Bug ID: 369753 Summary: Too many filter/account leads Kontact/Kmail to crash Product: kontact Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Application: kontact (5.2.3) Qt Version: 5.5.1 Operating System: Linux 4.1.31-30-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Trying once again to change settings either on identity (adding aliases) or add/modify filters - Custom settings of the application: 8 IMAP account, 2 Gmail account, one local, 5 identity and about 40 aliases The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f85360227c0 (LWP 1873))] Thread 26 (Thread 0x7f8479a1c700 (LWP 2551)): #0 0x7f852bfe303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f85202c486b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f85202c4899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f852bfdf0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f8532c6902d in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f847a7fc700 (LWP 2483)): #0 0x7fff23483b26 in clock_gettime () #1 0x7f8532c75c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f85336237d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f85337a33b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f85337a3945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f85337a4b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f852b7c14ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f852b7c1d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f852b7c1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f85337a4d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f853374bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f853356d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f853357232f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f852bfdf0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f8532c6902d in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f847affd700 (LWP 2385)): #0 0x7f852b7c0ee0 in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #1 0x7f852b7c1d25 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f852b7c1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f85337a4d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f853374bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f853356d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f853357232f in () at /usr/lib64/libQt5Core.so.5 #7 0x7f852bfdf0a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7f8532c6902d in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f847b7fe700 (LWP 2383)): #0 0x7fff23483b26 in clock_gettime () #1 0x7f8532c75c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f85336237d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f85337a33b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f85337a3945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f85337a4b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f852b7c14ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7f852b7c1d80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7f852b7c1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7f85337a4d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f853374bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7f853356d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7f853357232f in () at /usr/lib64/libQt5Core.so.5 #13 0x7f852bfdf0a4 in start_thread () at /lib64/libpthread.so.0 #14 0x7f8532c6902d in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f847bfff700 (LWP 2374)): #0 0x7fff23483b26 in clock_gettime () #1 0x7f8532c75c7d in clock_gettime () at /lib64/libc.so.6 #2 0x7f85336237d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f85337a33b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7f85337a3945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7f85337a4b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f852b7c14ad in g_
[kontact] [Bug 369246] New: Kontact/Kmail crashes when updating filter
https://bugs.kde.org/show_bug.cgi?id=369246 Bug ID: 369246 Summary: Kontact/Kmail crashes when updating filter Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Might be related to #198419 ? I've Kontact/Kmail 5.2.3 Whenever trying to add a filter or go to filter settings and modify it, then Kontact crashes. I've deleted filters and re-created it all, but still crashes I have 8 mailboxes, and all filter applies to either all or some All actions in filters are to move email to folder on receiving Also have Bogo spam filter added in the list, even though it never worked, really (have to select and remove my spam manually) Éric, annoyed. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 198419] kontact crashes when creating filter in kmail
https://bugs.kde.org/show_bug.cgi?id=198419 Eric changed: What|Removed |Added CC||eric.v...@msg4.us -- You are receiving this mail because: You are watching all bug changes.
[bangarang] [Bug 367132] New: Keyboard Technical Support Service Toll Free 1(888) 990-8801.
https://bugs.kde.org/show_bug.cgi?id=367132 Bug ID: 367132 Summary: Keyboard Technical Support Service Toll Free 1(888) 990-8801. Product: bangarang Version: unspecified Platform: Other URL: https://answers.launchpad.net/ubuntu/+source/alsa-driv er/+question/350108 OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jamboar...@gmail.com Reporter: ericae...@outlook.com Dial now toll free number 1(888) 990-8801. We provide solutions for all keyboard like HP, Dell, Asus, Lenovo, toshiba, Apple, Mac, We provide support service for, keyboard setting, laptop keyboard not working, keyboard not working, keyboard help, keyboard support, imac keyboard not working, keyboard troubleshooting, keyboard problems, laptop keys not working, how to use a keyboard, keyboard error, imac wireless keyboard not working, how to type special characters, computer keyboard support, wireless keyboard driver, help with keyboard, help keyboard ,why is my keyboard not working, keyboard not working on laptop, my keyboard is not working, keyboard buttons not working, keyboard and mouse not working, open keyboard settings, keys not working on keyboard keyboard wont work, mouse and keyboard not working, numbers on keyboard not working, keyboard configuration. Technical Support services avalable 24*7 at 1(888) 990-8801 toll free. We do provide support service for keyboard letters not working, usb keyboard not working, keyboard not typing letters, pc keyboard not working, keyboard issues,laptop keyboard not working, keyboard not working, keyboard help, keyboard support, imac keyboard not working, keyboard troubleshooting, keyboard problems, laptop keys not working, how to use a keyboard, keyboard error, imac wireless keyboard not working, how to type special characters, computer keyboard support, wireless keyboard driver, help with keyboard, help keyboard , keyboard not working laptop, keyboard disabled, laptop keyboard not typing, keyboard not typing, keyboard not working at all, keyboard not responding laptop, laptop mouse and keyboard not working, laptop keyboard not typing letters, some keys not working on acer laptop, samsung notebook keyboard not working, keyboard some keys not working laptop, keyboard of laptop not working, computer keyboard problems and solutions, wireless keyboard does not work, laptop keyboard will not work, keypad on keyboard not working, keyboard on phone not working Call on 1(888) 990-8801 to get tech support services. for any type of help reagrding keyboard stopped typing,@ some keys not working,@ letters on keyboard not working,@ laptop keyboard not working,@ keyboard not working,@ keyboard help, keyboard support,@ imac keyboard not working,@ keyboard troubleshooting, keyboard problems,@ laptop keys not working,@ how to use a keyboard, keyboard error,@ imac wireless keyboard not working,@ how to type special characters, computer keyboard support,@ wireless keyboard driver,@ help with keyboard, help keyboard ,@ Hp, Dell some keyboard keys not working,@ how to fix keyboard, disable laptop keyboard,@ go to keyboard settings, user error, @ keyboard on laptop not working,@ keyboard doesn t work,@ keyboard not responding, how to fix laptop keyboard, my mouse is not working, why is my keyboard not working, keyboard not working on laptop, my keyboard is not working, keyboard buttons not working,@ keyboard and mouse not working,@ open keyboard settings, keys not working on keyboard,@ keyboard wont work, mouse and keyboard not working,@ numbers on keyboard not working,@ keyboard configuration. Technical Support services avalable 24*7 at 1(888) 990-8801. We provide technical support services for keyboard letters not working, usb keyboard not working, keyboard not typing letters, pc keyboard not working, keyboard issues,laptop keyboard not working, keyboard not working, keyboard help, keyboard support, imac keyboard not working, keyboard troubleshooting,@ keyboard problems,@ laptop keys not working,@ how to use a keyboard,@ keyboard error,@ imac wireless keyboard not working,@ how to type special characters, @ computer keyboard support, wireless keyboard driver, help with keyboard, help keyboard ,laptop keyboard not typing, keyboard not typing, keyboard not working at all,@ keyboard not responding laptop, @ laptop mouse and keyboard not working,@ laptop keyboard not typing letters,@ some keys not working on acer laptop, samsung notebook keyboard not working, keyboard some keys not working laptop, keyboard of laptop not working, computer keyboard problems and solutions, wireless keyboard does not work, laptop keyboard will not work, keypad on keyboard not working, keyboard on phone not working Dial now tech support service number toll free number 1(888) 990-8801. for any help reagrding keyboard
[akunambol] [Bug 367123] New: Contact HP Printer Support (888) 990-8801
https://bugs.kde.org/show_bug.cgi?id=367123 Bug ID: 367123 Summary: Contact HP Printer Support(888) 990-8801 Product: akunambol Version: unspecified Platform: Other URL: https://login.launchpad.net/+emails OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ricca...@kde.org Reporter: ericae...@outlook.com Are you facing technical problems with your HP printer and looking for HP printer support phone number or HP printer support phone number don’t worry you are at the right place. You just need to connect with our HP printer technology expert through our toll free number (888) 990-8801. HP printer Support Phone Number 1(888) 990-8801 #HP printer support. When you dial our #HP printer support telephone number you’ll be connected with one of our printer technology experts and s/he will help you to get rid of your technical problem with Hewlett Packard Printer. Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, In case they’re unable to fix it they’ll be sharing a new #HP printer support phone number of their senior level technicians. #hp printer troubleshooting #hp help and support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, hp printer technical support, #contact hp printer support #hp support for printers #hp printer contact number, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, Hp printer customer support phone number, hp printer tech support phone number, hp printer phone number, contact hp printer support, hp tech support, hp printer support phone number, hp printer technical support, #hp printer phone support #install hp printer #hp laptop s
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #16 from eric --- Can someone test if this issue only happens on a 32bit system? I have two systems, both are 32bit and both have this issue. One other person also has a 32bit system and also has this issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 eric changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696
--- Comment #15 from eric ---
Created attachment 99291
--> https://bugs.kde.org/attachment.cgi?id=99291&action=edit
Backtrace of kaddressbook after applying patch in comment 13
I've patched akonadi using the diff in the commit you linked to in comment 13
and recompiled.
It still crashes. I've attached the backtrace of this crash.
The output on konsole between start and crash:
Recreating ksycoca file
("/tmp/test/.cache/ksycoca5_C_3hIv+tPrC1WaYX0kkAsoimmSnJQ=", version 303)
Menu "applications-kmenuedit.menu" not found.
Saving
ATTENTION: default value of option vblank_mode overridden by environment.
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree: 7 QSet(7)
org.kde.akonadi.ETM: collection: "Personal Contacts"
org.kde.akonadi.ETM: Fetch job took 187 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Personal Contacts"
org.kde.akonadi.ETM: Fetch job took 35 msec
org.kde.akonadi.ETM: was item fetch job: items: 0
org.kde.akonadi.ETM: GEN true false true
org.kde.akonadi.ETM: collection: QVector()
org.kde.akonadi.ETM: Subtree: 7 QSet(7)
org.kde.akonadi.ETM: Fetch job took 359 msec
org.kde.akonadi.ETM: was collection fetch job: collections: 1
org.kde.akonadi.ETM: first fetched collection: "Personal Contacts"
KCrash: Application 'kaddressbook' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
QSocketNotifier: Invalid socket 43 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 21 and type 'Read', disabling...
QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
QSocketNotifier: Invalid socket 26 and type 'Read', disabling...
QSocketNotifier: Invalid socket 31 and type 'Read', disabling...
QSocketNotifier: Invalid socket 33 and type 'Read', disabling...
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #12 from eric --- I've added 2 new attachments made after I've compiled akonadi and kdepim with debugging info turned on. I've never done this before, so tell me if there is something I should do. I still see some ?? in the backtrace... those are related to Qt libraries. Tell me if you also need those for debugging. This is how I have tested: 1) Create a new homedir of the user "test" (rm -rf /tmp/test && sudo -u test mkdir /tmp/test); 2) Log in to KDE as user "test"; 3) Start konsole; 4) Start kaddressbook from konsole; 5) Create a new contact with a birthday, this will result in a crash; 6) Start korganizer from konsole; 7) Create a new event, this will result in a crash; -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #11 from eric --- Created attachment 99279 --> https://bugs.kde.org/attachment.cgi?id=99279&action=edit Backtrace of korganizer when trying to create new event -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 eric changed: What|Removed |Added Attachment #97344|0 |1 is obsolete|| Attachment #98479|0 |1 is obsolete|| --- Comment #10 from eric --- Created attachment 99278 --> https://bugs.kde.org/attachment.cgi?id=99278&action=edit Backtrace of kaddressbook after adding contact with birthday -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #8 from eric --- Tested this again after a big upgrade and still the same behaviour. This time: KDE-applications 16.04.1, KDE-frameworks 5.22.0 and KDE-plasma 5.6.4. The output just before the crash: org.kde.akonadi.ETM: GEN true false true org.kde.akonadi.ETM: collection: QVector() Segmentation fault (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 Eric changed: What|Removed |Added CC||ekis...@gmail.com --- Comment #57 from Eric --- Running into this issue here as well. Setup - two monitors: 1) Primary -> DisplayPort (RIGHT monitor) 2) Secondary -> HDMI (LEFT monitor) Logout or reboot always resets both monitors' resolution to 1920x1080 and resets both monitors' coordinates in System Settings -> Display Configuration to "on top of each other". Disabling KScreen 2 fixed these issues but produces new ones: a) Primary display setting is lost (reverts to "No Primary Display") b) Position information is reversed: DisplayPort monitor is now on the left and HDMI monitor on the right This now happens on each logout or reboot. After disabling KScreen 2, it *is* kind of an improvement but manual display configuration intervention is still required on each login, which is a pain. Sysinfo: --- KDE Plasma Version: 5.6.3 KDE Frameworks Version: 5.21.0 Qt Version: 5.6.0 Kernel Version: 4.4.9-300.fc23.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362782] New: Crash when click shutdown
https://bugs.kde.org/show_bug.cgi?id=362782 Bug ID: 362782 Summary: Crash when click shutdown Product: kwin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: eric.linjial...@gmail.com When clink Power/session > shutdown, the crash notification will appear with the '30 second left' alert. Executable: kwin_x11 PID: 30430 Signal: Aborted (6) Time: 5/7/16 15:10:42 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 362624] New: Time out crash everytime I open Kmail
https://bugs.kde.org/show_bug.cgi?id=362624 Bug ID: 362624 Summary: Time out crash everytime I open Kmail Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Application: kontact (4.14.10) KDE Platform Version: 4.14.18 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 4.1.21-14-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: "just" simply opening the application Kmail - Custom settings of the application: Most files (including the DB) are symlinked to a different partition on a different ssd, I have 6 main email imap account, and a lot of filters (that randomly works) and a Bogofilter that is as unreliable as kmail alltogether The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1ebed08800 (LWP 2490))] Thread 4 (Thread 0x7f1ea2093700 (LWP 2491)): #0 0x7f1eb626503f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1ebb3eceb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f1ebb3ecee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f1eb62610a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f1ebc1dcfed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f1e61790700 (LWP 2492)): #0 0x7f1eb626503f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1ebb15fb3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f1ebb414a06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f1eb62610a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f1ebc1dcfed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f1e5234f700 (LWP 2496)): #0 0x7f1ebc1d4bbd in poll () at /lib64/libc.so.6 #1 0x7f1eb5c94e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1eb5c94f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1ebc9d3fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f1ebc9a5d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f1ebc9a6045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f1ebc8a34df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f1ebc8a5bbf in () at /usr/lib64/libQtCore.so.4 #8 0x7f1eb62610a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f1ebc1dcfed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f1ebed08800 (LWP 2490)): [KCrash Handler] #6 0x7f1ebc12d0a7 in raise () at /lib64/libc.so.6 #7 0x7f1ebc12e458 in abort () at /lib64/libc.so.6 #8 0x7f1ebc89b6d4 in qt_message_output(QtMsgType, char const*) () at /usr/lib64/libQtCore.so.4 #9 0x7f1ebc89b859 in () at /usr/lib64/libQtCore.so.4 #10 0x7f1ebc89c064 in qFatal(char const*, ...) () at /usr/lib64/libQtCore.so.4 #11 0x7f1e576d9d84 in MailCommon::Kernel::self() () at /usr/lib64/libmailcommon.so.4 #12 0x7f1e57721fd0 in MailCommon::FolderCollection::writeConfig() const () at /usr/lib64/libmailcommon.so.4 #13 0x7f1e577227d2 in MailCommon::FolderCollection::~FolderCollection() () at /usr/lib64/libmailcommon.so.4 #14 0x7f1e57722849 in MailCommon::FolderCollection::~FolderCollection() () at /usr/lib64/libmailcommon.so.4 #15 0x7f1e57721104 in () at /usr/lib64/libmailcommon.so.4 #16 0x7f1ebc12fb19 in __run_exit_handlers () at /lib64/libc.so.6 #17 0x7f1ebc12fb65 in () at /lib64/libc.so.6 #18 0x7f1e576da457 in MailCommon::Kernel::emergencyExit(QString const&) () at /usr/lib64/libmailcommon.so.4 #19 0x7f1e576daa17 in MailCommon::Kernel::createDefaultCollectionDone(KJob*) () at /usr/lib64/libmailcommon.so.4 #20 0x7f1ebc9bb0fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #21 0x7f1ebce3b132 in KJob::result(KJob*) () at /usr/lib64/libkdecore.so.5 #22 0x7f1ebce3b170 in KJob::emitResult() () at /usr/lib64/libkdecore.so.5 #23 0x7f1eb828cde9 in () at /usr/lib64/libakonadi-kde.so.4 #24 0x7f1ebc9bb0fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #25 0x7f1ebce3b132 in KJob::result(KJob*) () at /usr/lib64/libkdecore.so.5 #26 0x7f1ebce3b170 in KJob::emitResult() () at /usr/lib64/libkdecore.so.5 #27 0x7f1eb8286623 in () at /usr/lib64/libakonadi-kde.so.4 #28 0x7f1ebc9bb0fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #29 0x000
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #7 from eric --- I forgot to say that I'm now using KDE-applications 16.04.0 and still having this problem. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #6 from eric --- The birthday resource is already added on a newly created homedir of a test user. I always do a 'rm -rf /home/testuser /tmp/akonadi-testuser*' before login as testuser and testing kaddressbook. Adding a contact with a birthday crashes kaddressbook when there is a birthday resource. After this crash: - kaddressbook will crash immediately after start; - korganizer will crash when showing the to-do view or creating new event or to-do; - korganizer will not crash in the calendar view, the birthday of the new contact is visible; - akonadiconsole will crash when choosing the browser tab; - configuring the birthday resource in akonadiconsole will crash the configure dialog But no crash will happen when I remove the birthday resource first before adding a contact with a birthday... of course this way I will not be able to see the birthday in korganizer's calendar view. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 335852] Multiple tabs session restore fails
https://bugs.kde.org/show_bug.cgi?id=335852 --- Comment #9 from Eric --- Hi all, I'm sorry for my low level in linux. But I'd like to use the 'restore multi-tab session' in okular, and I'm not clear about the steps to add or use that option. Could you explain in few and easy steps please?, I don't know where should I put those files. Thank you -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 335852] Multiple tabs session restore fails
https://bugs.kde.org/show_bug.cgi?id=335852 Eric changed: What|Removed |Added CC||ericlsanchezmu...@gmail.com --- Comment #8 from Eric --- Hi all, I'm sorry for my low level in linux. But I'd like to use the 'restores multy-tab session' in okular, and I'm not clear about the steps to add or use that option. Could you explain in few and easy steps please?, I don't know where should I put those files. Thank you -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 --- Comment #35 from Eric --- After the 73 new packages to install, 1 source package. It keep telling me that I need to Package 'libKF5AkonadiPrivate-devel' has source package 'akonadi-server'. Resolving package dependencies... The following source package is going to be installed: akonadi-server 1 source package to install. I'm not even sure how my Kmail have been working so far, even if so-so ? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 Eric changed: What|Removed |Added CC||eric.v...@msg4.us --- Comment #34 from Eric --- For the past few months, Kmail keep doing that. In fact, since the first day I gave Kmail a try I've had different problems with it. It's unfriendly and take up so much storage space ! Anyway, when I start it it keep saying that error message, I close it, reopen it, and then it kinda work, at least it doesn't repeat the same error message, it just work badly, like not filtering incoming messages, or freezing on refreshing an imap account, etc ... I have 7 main email addresses in 7 imap account, with all the aliases, and all including local folder are simlinked to a separate drive. I've zypper kdepim just now, and it says: Problem: kdepim-15.12.3-18.5.src requires kalarmcal-devel, but this requirement cannot be provided So I zypper Kalarmcal and it says: Problem: kalarmcal-15.12.3-15.1.src requires libKF5AkonadiPrivate-devel >= 1.72.43, but this requirement cannot be provided So I zypper si libKF5AkonadiPrivate-devel and it says: The following 73 NEW packages are going to be installed: Mesa-libEGL-devel Mesa-libGL-devel boost-devel cmake damageproto-devel extra-cmake-modules fixesproto-devel gcc gcc-c++ gcc48 gcc48-c++ glibc-devel kbproto-devel kf5-filesystem libQt5Core-devel libQt5DBus-devel libQt5Gui-devel libQt5Network-devel libQt5Sql-devel libQt5Test-devel libQt5Widgets-devel libQt5Xml-devel libX11-devel libXau-devel libXdamage-devel libXext-devel libXfixes-devel libXxf86vm-devel libasan0 libatomic1 libboost_atomic1_54_0 libboost_chrono1_54_0 libboost_graph1_54_0 libboost_graph_parallel1_54_0 libboost_locale1_54_0 libboost_log1_54_0 libboost_math1_54_0 libboost_mpi1_54_0 libboost_python1_54_0 libboost_random1_54_0 libboost_regex1_54_0 libboost_serialization1_54_0 libboost_signals1_54_0 libboost_test1_54_0 libboost_timer1_54_0 libboost_wave1_54_0 libdrm-devel libecpg6 libibverbs1 libitm1 libpq5 libqt5-qtbase-common-devel libstdc++-devel libstdc++48-devel libtsan0 libxcb-devel libxcb-res0 libxcb-screensaver0 libxcb-xevie0 libxcb-xf86dri0 libxcb-xinerama0 libxcb-xprint0 libxcb-xtest0 libxcb-xvmc0 libxshmfence-devel linux-glibc-devel openmpi-libs postgresql94-devel pthread-stubs-devel sqlite3-devel xextproto-devel xf86vidmodeproto-devel xproto-devel The following source package is going to be installed: akonadi-server 73 new packages to install, 1 source package. Hopefully that will solve it all !! Eric -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #4 from eric --- Created attachment 98479 --> https://bugs.kde.org/attachment.cgi?id=98479&action=edit Backtrace of kaddressbook crash This crash still happen with: - KDE Framework 5.21.0 - KDE Applications 15.12.3 - KDE Plasma 5.6.3 - Qt 5.6.0 - Linux 4.5.1 32bit (is 32bit the problem? Maybe the devs are using 64bit computers) There is some improvement: In the past, adding a contact with a birthday in kaddressbook used to crash kaddressbook and korganizer's to-do and even view, but now korganizer's event view does not crash anymore. This is the last thing I see in the console when kaddressbook/korganizer crash: ASSERT failure in QVector::at: "index out of range", file /usr/include/qt/QtCore/qvector.h, line 419 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361651] kaddressbook crashes continuously after importing a vcf card
https://bugs.kde.org/show_bug.cgi?id=361651 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #1 from eric --- This looks like https://bugs.kde.org/show_bug.cgi?id=358696 Kaddressbook crashes immediately after adding or importing a contact that has a birthday or anniversary date. If you remove the "BDAY" or "ANNIVERSARY" line in a vcf card, importing it will not result in a crash. After this crash, kaddressbook will always crash the next time it is executed. Korganizer will also always crash when it is in the "To-do View" (View > To-do List) or when adding a new to-do (Actions > New To-do...). Korganizer will not crash when in the calendar view (View > Month). Korganizer's "Event View" and create new event also used to crash, but is not doing that anymore... so there is some improvement. These crashes only happen when the "Birthday and Anniversaries" calendar is enabled in korganizer. Kaddressbook is almost useless without the possibility to have contacts that have a birthday or anniversary date. The frustrating part is that it is unconfirmed and not many other people complain about the same problem. I've tried everything I can think of, but so far without a success: - switching between MySQL (MariaDB) and SQLite; - creating a complete new user; - creating the homedir in /tmp (maybe it has issues with BtrFS); - raising the stacksize (ulimit -s); - changing locales (LC_*) to en_US, C or leave them empty I'm currently using: - KDE Framework 5.21.0 - KDE Applications 15.12.3 - KDE Plasma 5.6.3 - Qt 5.6.0 - Linux 4.5.1 32bit (is 32bit the problem? Maybe the devs are using 64bit computers) Other bugreport that may have the same issue as this one: https://bugs.kde.org/show_bug.cgi?id=360746 (crash after sync) https://bugs.kde.org/show_bug.cgi?id=359610 https://bugs.kde.org/show_bug.cgi?id=358696 (crash after adding contact with birthday) https://bugs.kde.org/show_bug.cgi?id=357361 (crash after sync) https://bugs.kde.org/show_bug.cgi?id=357228 (crash after sync) https://bugs.kde.org/show_bug.cgi?id=353482 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 360524] New: Filter overload
https://bugs.kde.org/show_bug.cgi?id=360524 Bug ID: 360524 Summary: Filter overload Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Application: kontact (4.14.10) KDE Platform Version: 4.14.17 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I was running my "all filter" and moving a folder from current to archives, looks like Kmail was not able to manage the load. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5651e76800 (LWP 1911))] Thread 5 (Thread 0x7f563522c700 (LWP 1912)): #0 0x7f56493d003f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f564e556eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f564e556ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f56493cc0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f564f346fed in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f55f4929700 (LWP 1913)): #0 0x7f56493d003f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f564e2c9b3d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f564e57ea06 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f56493cc0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f564f346fed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f55e5021700 (LWP 2061)): #0 0x7f564f33ebbd in poll () from /lib64/libc.so.6 #1 0x7f5648dffe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f5648dfff7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f564fb3bfde in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #4 0x7f564fb0dd4f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #5 0x7f564fb0e045 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #6 0x7f564fa0b4df in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x7f564fa0dbbf in ?? () from /usr/lib64/libQtCore.so.4 #8 0x7f56493cc0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f564f346fed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f55dd4f4700 (LWP 18832)): #0 0x7f56493d003f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f55ec61486b in ?? () from /usr/lib64/libQtScript.so.4 #2 0x7f55ec6148a9 in ?? () from /usr/lib64/libQtScript.so.4 #3 0x7f56493cc0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f564f346fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5651e76800 (LWP 1911)): [KCrash Handler] #6 0x7f564f2970a7 in raise () from /lib64/libc.so.6 #7 0x7f564f298458 in abort () from /lib64/libc.so.6 #8 0x7f564fa036d4 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/libQtCore.so.4 #9 0x7f564fa03859 in ?? () from /usr/lib64/libQtCore.so.4 #10 0x7f564fa04064 in qFatal(char const*, ...) () from /usr/lib64/libQtCore.so.4 #11 0x7f55eb132cb8 in ?? () from /usr/lib64/libkmailprivate.so.4 #12 0x7f55eb131d1d in ?? () from /usr/lib64/libkmailprivate.so.4 #13 0x7f55eb136a62 in ?? () from /usr/lib64/libkmailprivate.so.4 #14 0x7f55eb136c68 in ?? () from /usr/lib64/libkmailprivate.so.4 #15 0x7f55eb05f085 in KMKernel::dumpDeadLetters() () from /usr/lib64/libkmailprivate.so.4 #16 0x7f55eb060877 in ?? () from /usr/lib64/libkmailprivate.so.4 #17 0x7f565128d2d0 in KCrash::defaultCrashHandler (sig=6) at /usr/src/debug/kdelibs-4.14.17/kdeui/util/kcrash.cpp:307 #18 #19 0x7f564f2970a7 in raise () from /lib64/libc.so.6 #20 0x7f564f298458 in abort () from /lib64/libc.so.6 #21 0x7f564fa036d4 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/libQtCore.so.4 #22 0x7f564fa03859 in ?? () from /usr/lib64/libQtCore.so.4 #23 0x7f564fa04064 in qFatal(char const*, ...) () from /usr/lib64/libQtCore.so.4 #24 0x7f55ea9a7d84 in MailCommon::Kernel::self() () from /usr/lib64/libmailcommon.so.4 #25 0x7f55ea9effd0 in MailCommon::FolderCollection::writeConfig() const () from /usr/lib64/libmailcommon.so.4 #26 0x7f55ea9f07d2 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib64/libmailcommon.so.4 #27 0x7f55ea9f0849 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib64/libmailcommon.so.4 #28 0x7f55ea9ef104 in ?? () from /usr/lib64/libm
[kde] [Bug 360018] New: KDE crashes on login from FreeNX
https://bugs.kde.org/show_bug.cgi?id=360018 Bug ID: 360018 Summary: KDE crashes on login from FreeNX Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ebelc...@eacbelcher.net Application: kdeinit5 () Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-xen x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was logging in using a NX client. I simply installed NX and FreeNX from OpenSUSE for my version OpenSUSE 42 Setup NX as I've done in the past and tried logging in using the client from another machine The crash can be reproduced every time. -- Backtrace: Application: KCMInit (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f16c24b2780 (LWP 13298))] Thread 2 (Thread 0x7f16ad04c700 (LWP 13300)): #0 0x7f16c05febbd in poll () at /lib64/libc.so.6 #1 0x7f16c1923422 in () at /usr/lib64/libxcb.so.1 #2 0x7f16c192500f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f16af3a13c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f16c097532f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f16be0280a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f16c0606fed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f16c24b2780 (LWP 13298)): [KCrash Handler] #6 0x7f16af15b2dc in XIFreeDeviceInfo () at /usr/lib64/libXi.so.6 #7 0x7f16a5f7365f in () at /usr/lib64/qt5/plugins/kcm_input.so #8 0x7f16a5f76761 in kcminit_mouse () at /usr/lib64/qt5/plugins/kcm_input.so #9 0x7f16af84fdd9 in () at /usr/lib64/libkdeinit5_kcminit_startup.so #10 0x7f16af85069c in () at /usr/lib64/libkdeinit5_kcminit_startup.so #11 0x7f16af850ca3 in () at /usr/lib64/libkdeinit5_kcminit_startup.so #12 0x7f16af851dfb in kdemain () at /usr/lib64/libkdeinit5_kcminit_startup.so #13 0x004085a8 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 --- Comment #3 from eric --- Created attachment 97344 --> https://bugs.kde.org/attachment.cgi?id=97344&action=edit Trace of addressbook right after adding a contact with a birthday. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #2 from eric --- This still happens with KF-5.19.0 and akonadi/korganizer/kaddressbook-15.12.2. Kaddressbook will crash after creating/importing a contact with a birthday and/or anniversary, when contact has no birthday or anniversary no crash will happen. After this crash kaddressbook and korganizer are not usable anymore, because kaddressbook will always crash when started, and korganizer will crash when selecting the to-do or event view or when adding a new to-do or event. Korganizer is only usable when it is only used for viewing the monthly/weekly/daily calendar. This all is tested on a completely empty (newly created) home directory and also tested with both the MySQL (MariaDB) and SQLite3 database engines. Other information: Qt-5.5.1, Glibc-2.22, the system is 32bits and the filesystem is BtrFS with zlib compression. The backtrace is said to be unusable, but I'll attach anyway. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 359607] New: Kmail crashes after I changed (moved) the mail folders (in this case the local-mail)
https://bugs.kde.org/show_bug.cgi?id=359607 Bug ID: 359607 Summary: Kmail crashes after I changed (moved) the mail folders (in this case the local-mail) Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: eric.v...@msg4.us Application: kontact (4.14.10) KDE Platform Version: 4.14.17 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I renamed the symlink that link to the local-folder on a different partition I renamed it wrong, Opening Kontact got me an error message (can't fetch information) I changed/corrected my error - Custom settings of the application: all /.local; /.kde4; /.config; are symlink to the separat "emails" partition on a differnent drive The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9a0f701800 (LWP 2236))] Thread 5 (Thread 0x7f99f2ab8700 (LWP 2237)): #0 0x7f9a06c5b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9a0bde1eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f9a0bde1ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f9a06c570a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f9a0cbd1fed in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f99b21b5700 (LWP 2238)): #0 0x7f9a06c5b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9a0bb54b3d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x7f9a0be09a06 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x7f9a06c570a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f9a0cbd1fed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f99a307b700 (LWP 2243)): #0 0x7f9a0668a017 in g_main_context_release () from /usr/lib64/libglib-2.0.so.0 #1 0x7f9a0668ae0e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9a0668af7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9a0d3c6fde in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #4 0x7f9a0d398d4f in QEventLoop::processEvents(QFlags) () from /usr/lib64/libQtCore.so.4 #5 0x7f9a0d399045 in QEventLoop::exec(QFlags) () from /usr/lib64/libQtCore.so.4 #6 0x7f9a0d2964df in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x7f9a0d298bbf in ?? () from /usr/lib64/libQtCore.so.4 #8 0x7f9a06c570a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7f9a0cbd1fed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f999b7fe700 (LWP 2272)): #0 0x7f9a06c5b03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f99a9eb886b in ?? () from /usr/lib64/libQtScript.so.4 #2 0x7f99a9eb88a9 in ?? () from /usr/lib64/libQtScript.so.4 #3 0x7f9a06c570a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f9a0cbd1fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f9a0f701800 (LWP 2236)): [KCrash Handler] #6 0x7f9a0cb220a7 in raise () from /lib64/libc.so.6 #7 0x7f9a0cb23458 in abort () from /lib64/libc.so.6 #8 0x7f9a0d28e6d4 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/libQtCore.so.4 #9 0x7f9a0d28e859 in ?? () from /usr/lib64/libQtCore.so.4 #10 0x7f9a0d28f064 in qFatal(char const*, ...) () from /usr/lib64/libQtCore.so.4 #11 0x7f99a824bd84 in MailCommon::Kernel::self() () from /usr/lib64/libmailcommon.so.4 #12 0x7f99a8293fd0 in MailCommon::FolderCollection::writeConfig() const () from /usr/lib64/libmailcommon.so.4 #13 0x7f99a82947d2 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib64/libmailcommon.so.4 #14 0x7f99a8294849 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib64/libmailcommon.so.4 #15 0x7f99a8293104 in ?? () from /usr/lib64/libmailcommon.so.4 #16 0x7f9a0cb24b19 in __run_exit_handlers () from /lib64/libc.so.6 #17 0x7f9a0cb24b65 in exit () from /lib64/libc.so.6 #18 0x7f99a824c457 in MailCommon::Kernel::emergencyExit(QString const&) () from /usr/lib64/libmailcommon.so.4 #19 0x7f99a824ca17 in MailCommon::Kernel::createDefaultCollectionDone(KJob*) () from /usr/lib64/libmailcommon.so.4 #20 0x7f9a0d3ae0fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #21 0x7f9a0d82e132 in KJob::result (this=this@entry=0x9
[kontact] [Bug 353482] Akonadi will not load in PMI files.
https://bugs.kde.org/show_bug.cgi?id=353482 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #12 from eric --- The crash happens when a contact is imported that has a birthday or anniversary. After this import kaddressbook will crash immediately and the next times it is started and korganizer will crash when adding a new to-do or event. This crash doesn't happen when a contact that is added has no birthday or anniversary. This crash also doesn't happen when the "birthday and anniversaries" calendar is disabled _before_ adding the contact (this can be done in korganizer or akonadiconsole). Probably same issue: https://bugs.kde.org/show_bug.cgi?id=358696 https://bugs.kde.org/show_bug.cgi?id=353326 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 354728] Korganizer crash wenn make a new event
https://bugs.kde.org/show_bug.cgi?id=354728 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #1 from eric --- More of the same issue: Kaddressbook will crash immediately and at every restart after adding a new contact that has a birthday or anniversary. Adding a contact without a birthday or anniversary will not make kaddressbook crash. See: https://bugs.kde.org/show_bug.cgi?id=358696 After adding this contact with a birthday or anniversary, korganizer will also crash when adding a new to-do or event. See: https://bugs.kde.org/show_bug.cgi?id=353326 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 357228] KAddressbook crashes on startup with configured CardDav
https://bugs.kde.org/show_bug.cgi?id=357228 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #1 from eric --- I have the same issue. Kaddressbook will crash immediately and at every restart after adding a new contact that has a birthday or anniversary. Adding a contact without a birthday or anniversary will not make kaddressbook crash. See: https://bugs.kde.org/show_bug.cgi?id=358696 After adding this contact with a birthday or anniversary, korganizer will also crash when adding a new to-do or event. See: https://bugs.kde.org/show_bug.cgi?id=353326 -- You are receiving this mail because: You are watching all bug changes.
[kdepimlibs] [Bug 353326] Korganizer crashed when trying to add a new event.
https://bugs.kde.org/show_bug.cgi?id=353326 --- Comment #5 from eric --- Does kaddressbook still crash when the vCard (a few postings above this one) is imported _after_ first removing the "BDAY" line in the vCard-file (and maybe also other lines with a date)? There are similar reports about synchronizing/importing contacts from different sources or adding a new contact manually that results in a crash. See for example my bug report: https://bugs.kde.org/show_bug.cgi?id=358696 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 358696] New: KF5's kaddressbook crashes when adding a contact that has a birthday
https://bugs.kde.org/show_bug.cgi?id=358696 Bug ID: 358696 Summary: KF5's kaddressbook crashes when adding a contact that has a birthday Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Birthdays Resource Assignee: kdepim-b...@kde.org Reporter: pro...@gmx.net When adding/importing a contact that has a birthday, kaddressbook will crash immediately and the next times it is started. This is with Framework-5.18, Akonadi-15.12.1 and Kaddressbook-15.12.1. Reproducible: Always Steps to Reproduce: 1. Do 'rm -rf akonadi*' in ~/.kde4, ~/.local/share and ~/.config (or create new user) 2. Let akonadi create a new database 3. Start kaddressbook and create a new contact with a birthday Actual Results: Kaddressbook will immediately crash after the contact is created and it will crash the next times it is started. Expected Results: No crash. This crash only happens when the "Birthdays and Anniversaries" calendar is enabled. This can be checked in korganizer. Without this calendar, kaddressbook will not crash when adding a new contact with a birthday... but it will start crashing when this calendar is enabled later (for example when "Birthdays and Anniversaries" is added as a new calendar in korganizer). -- You are receiving this mail because: You are watching all bug changes.
[kdepimlibs] [Bug 353326] Korganizer crashed when trying to add a new event.
https://bugs.kde.org/show_bug.cgi?id=353326 eric changed: What|Removed |Added CC||pro...@gmx.net --- Comment #4 from eric --- This still happens with korganizer and kaddresssbook, both version 15.12.1. KDE-5.18 Qt-5.5.1 After importing new *.vcf files: Korganizer crashes when trying to add a new event or after I click on the 'To-Do List' view; Kaddressbook crashes immediately after startup. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356389] baloo file indexing daemon crash when download with firefox
https://bugs.kde.org/show_bug.cgi?id=356389 --- Comment #2 from eric --- (In reply to Vishesh Handa from comment #1) > Could you please provide a backtrace? > > Perhaps you could start baloo manually via gdb? First kill `baloo_file` and > then start it via `gdb baloo_file` and then 'start'. When it crashes, type > `backtrace` to obtain the backtrace. hello thanks for answer, i've try it but no backtrace file created, crash corrupt all answer of the system, unable to create report bug file and there is nothing in ksystemlog border crash is not reported if i start baloo in konsole and i create a folder uname i can see the crash line text but nothing else, now i'm tired about that i have disinstall baloo and suppress all folders. My system now is working fine i can't see speed difference for find folder in my ssd disk so may be a stable baloo_file will be released for my system. My kubuntu 14.10 wasn't corrupt eveything was working fine so new plasma may be the problem. regards (sorry for my bad english) -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356389] New: baloo file indexing daemon crash when download with firefox
https://bugs.kde.org/show_bug.cgi?id=356389 Bug ID: 356389 Summary: baloo file indexing daemon crash when download with firefox Product: Baloo Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: m...@vhanda.in Reporter: cloudmas...@openmailbox.org CC: pinak.ah...@gmail.com baloo daemon crash all time if i start to download a file in firefox, i have try other addon for download but same result i can't find more details in files debugging there is only one line for explain baloo file indexing daemon crash, someone as the same thing? kubuntu 15.10 amd 64 all packages up to date firefox 42.0 -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 350485] Baloo File Indexing Daemon crashing...
https://bugs.kde.org/show_bug.cgi?id=350485 eric changed: What|Removed |Added CC||cloudmas...@openmailbox.org -- You are receiving this mail because: You are watching all bug changes.
