[plasmashell] [Bug 367633] Plasmashell memory leak with PIM Events Plugin

2016-08-27 Thread Filippe via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=367633

--- Comment #2 from Filippe  ---
Created attachment 100806
  --> https://bugs.kde.org/attachment.cgi?id=100806&action=edit
Console output of plasmashell

Here is console output.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 367633] New: Plasmashell memory leak with PIM Events Plugin

2016-08-21 Thread Filippe via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=367633

Bug ID: 367633
   Summary: Plasmashell memory leak with PIM Events Plugin
   Product: plasmashell
   Version: 5.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: gasinv...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.3)

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.5.4-1-default x86_64
Distribution: "openSUSE Tumbleweed (20160812) (x86_64)"

-- Information about the crash:
Enabling PIM Events Plugin in plasma calendar widget causes plasmashell to
consume all available memory and then crash.
Seems like this occurs only with google tasks enabled in calendar selection.
Sorry for my english.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f60eadc9900 (LWP 2664))]

Thread 16 (Thread 0x7f5ff67ea700 (LWP 2695)):
#0  0x7f60e43f8a7d in read () at /lib64/libc.so.6
#1  0x7f60dbcb8f75 in  () at /usr/lib64/nvidia/tls/libnvidia-tls.so.352.79
#2  0x7f60e0ac0d00 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f60e0a7db26 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f60e0a7dff4 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f60e0a7e16c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f60e4d27aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f60e4ccf76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f60e4af53b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7f60e4afa2d8 in  () at /usr/lib64/libQt5Core.so.5
#10 0x7f60e3bff474 in start_thread () at /lib64/libpthread.so.0
#11 0x7f60e44053ed in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f5feefec700 (LWP 2694)):
#0  0x7f60e3c0509f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f60e4afb18b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f60e8aa13f5 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f60e8aa1cea in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f60e4afa2d8 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f60e3bff474 in start_thread () at /lib64/libpthread.so.0
#6  0x7f60e44053ed in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f5ff4a5c700 (LWP 2687)):
#0  0x7f60e3c0509f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f60e4afb18b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f60e8aa13f5 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f60e8aa1cea in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f60e4afa2d8 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f60e3bff474 in start_thread () at /lib64/libpthread.so.0
#6  0x7f60e44053ed in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f5ff5fe9700 (LWP 2686)):
#0  0x7f60e43fca1d in poll () at /lib64/libc.so.6
#1  0x7f60e0a7e056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f60e0a7e16c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f60e4d27aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f60e4ccf76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f60e4af53b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f60e7ea11e5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f60e4afa2d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f60e3bff474 in start_thread () at /lib64/libpthread.so.0
#9  0x7f60e44053ed in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f5ffe77e700 (LWP 2684)):
#0  0x7f60e3c0509f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f60e4afb18b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2  0x7f60e8aa13f5 in  () at /usr/lib64/libQt5Quick.so.5
#3  0x7f60e8aa1cea in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7f60e4afa2d8 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f60e3bff474 in start_thread () at /lib64/libpthread.so.0
#6  0x7f60e44053ed in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f5fffdfb700 (LWP 2683)):
#0  0x7f60e43f8a7d in read () at /lib64/libc.so.6
#1  0x7f60dbcb8f75 in  () at /usr/lib64/nvidia/tls/libnvidia-tls.so.352.79
#2  0x7f60e0ac0d00 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f60e0a7db26 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f60e0a7dff4 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f60e0a7e16c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f60e4d27aeb in
QEventDispatcherG

[kjots] [Bug 312938] Add an akonadi imap kjots feature

2016-03-07 Thread Filippe via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=312938

Filippe  changed:

   What|Removed |Added

 CC||gasinv...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwalletmanager] [Bug 358469] New: kwalletmanager5 resets Auto Allow setting

2016-01-24 Thread Filippe via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=358469

Bug ID: 358469
   Summary: kwalletmanager5 resets Auto Allow setting
   Product: kwalletmanager
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: gasinv...@gmail.com

If "Prompt on Open" in kwalletrc is set to true, opening (even without changing
any settings) kwalletmanager5 causes deletion of [Auto Allow] section.

Reproducible: Always

Steps to Reproduce:
1. Check "Prompt when application acceses a wallet" setting.
2. Select "always allow" when prompted to give access to wallet for a program.
3. Open kwalletmanager.
4. Re-login and launch that program again.

Actual Results:  
Access request appeares again.

-- 
You are receiving this mail because:
You are watching all bug changes.