[kdenlive] [Bug 352489] 15.13 git master: MLT processing threads>1 causes (re)positioning playhead to not work any longer

2018-05-16 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=352489

Eric Fontaine  changed:

   What|Removed |Added

 CC||ericrfonta...@hotmail.com

--- Comment #16 from Eric Fontaine  ---
I'm noting this happens on my machine too (arch linux kdenlive 18.04.1 mlt
6.8.0 on intel i7-6500U), and the workaround of reducing MLT thread count to 1
works.

I'm also noting that I can't step through individual frames with right or left
keyboard buttons when I have >1 thread, but I can with only 1 thread.  I
suspect this is related to this issue.

I'm also noting that on demanding multi-track videos, that with >1 thread I
notice that pressing spacebar to initiate playback will result in playback
playing like half a second and then restarting playback a few times (similar to
how a CD player would loop when stuck on a bad disc).  However on the same
video with only 1 thread, the playback won't experience that multiple false
start looping problem, but will instead simply take a little bit longer to get
rolling.  I'm thinking while this might be related to the issue of the playhead
not working properly...(maybe the multiple threads send conflicting information
about the progress of processing of the start frame, which confuses the
playhead cursor).  I can't find this issue in the issue tracker...so I'm
mentioning it here cause I think might be the same underlying issue.

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

[dolphin] [Bug 394303] Crash when deleting something in /var folder (for which I don't believe Trash is setup for)

2018-05-15 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=394303

--- Comment #1 from Eric Fontaine  ---
hmm...I can't reproduce now.  I opened /var/videos folder again, and this time
deleted the same file, and kde does move it to my home's trash folder.

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

[dolphin] [Bug 394303] New: Crash when deleting something in /var folder (for which I don't believe Trash is setup for)

2018-05-15 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=394303

Bug ID: 394303
   Summary: Crash when deleting something in /var folder (for
which I don't believe Trash is setup for)
   Product: dolphin
   Version: 18.04.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: ericrfonta...@hotmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (18.04.1)

Qt Version: 5.10.1
Frameworks Version: 5.46.0
Operating System: Linux 4.16.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

Opened dolphin and navigated to /var/videos (which is a folder when I save a
bunch of videos).  Then pressed delete on keyboard.

- Custom settings of the application:

As I mentioned, I don't actually have trash setup for that folder.  If I were
to use mate's file manager, then the same action of pressing delete will delete
those files permanently.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff5ab236800 (LWP 20982))]

Thread 3 (Thread 0x7ff588f14700 (LWP 20985)):
#0  0x7ff5aaaf7934 in read () from /usr/lib/libc.so.6
#1  0x7ff59b6feed1 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7ff59b6b8ff8 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7ff59b6b94c6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7ff59b6b963e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7ff5a4cf3264 in QEventDispatcherGlib::processEvents
(this=0x7ff58b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7ff5a4c9e96c in
QEventLoop::exec(QFlags) () at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7ff5a4acda09 in QThread::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7ff5a4ad285e in QThreadPrivate::start(void*) () at
thread/qthread_unix.cpp:376
#9  0x7ff5a013c075 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7ff5aab0653f in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7ff591403700 (LWP 20984)):
#0  0x7ff5aaaf7934 in read () from /usr/lib/libc.so.6
#1  0x7ff59b6feed1 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7ff59b6b8ff8 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7ff59b6b94c6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7ff59b6b963e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7ff5a4cf3264 in QEventDispatcherGlib::processEvents
(this=0x7ff584000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7ff5a4c9e96c in
QEventLoop::exec(QFlags) () at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7ff5a4acda09 in QThread::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7ff5a511fb56 in QDBusConnectionManager::run (this=0x7ff5a5395080
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#9  0x7ff5a4ad285e in QThreadPrivate::start(void*) () at
thread/qthread_unix.cpp:376
#10 0x7ff5a013c075 in start_thread () from /usr/lib/libpthread.so.0
#11 0x7ff5aab0653f in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7ff5ab236800 (LWP 20982)):
[KCrash Handler]
#6  0x7ff5aa774fcf in KStandardItem::setDataValue(QByteArray const&,
QVariant const&) () from /usr/lib/libdolphinprivate.so.5
#7  0x7ff5aa775582 in KStandardItem::setIcon(QString const&) () from
/usr/lib/libdolphinprivate.so.5
#8  0x7ff5aae2f63a in ?? () from /usr/lib/libkdeinit5_dolphin.so
#9  0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaa7b0,
r=0x7ff5ab09e070, this=0x55d6ecdc5aa0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#10 QMetaObject::activate(QObject*, int, int, void**) () at
kernel/qobject.cpp:3750
#11 0x7ff5aae56190 in ?? () from /usr/lib/libkdeinit5_dolphin.so
#12 0x7ff5aae24949 in ?? () from /usr/lib/libkdeinit5_dolphin.so
#13 0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaa8c0,
r=0x7ff5ab09e070, this=0x55d6ec982fd0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#14 QMetaObject::activate(QObject*, int, int, void**) () at
kernel/qobject.cpp:3750
#15 0x7ff5a90a82fd in ?? () from /usr/lib/libKF5KIOCore.so.5
#16 0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaab80,
r=0x7ff5a9313400, this=0x55d6ed10e720) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
#17 QMetaObject::activate(QObject*, int, int, void**) () at
kernel/qobject.cpp:3750
#18 0x7ff5a66386ed in KJob::result(KJob*, KJob::QPrivateSignal)

[plasmashell] [Bug 393912] The Activities switcher steal the focus after I switch using meta+tab and after that it does not autohide

2018-05-08 Thread Eric Francis
https://bugs.kde.org/show_bug.cgi?id=393912

Eric Francis  changed:

   What|Removed |Added

 CC||aird...@gmail.com

--- Comment #1 from Eric Francis  ---
I've also run into this on PCLinuxOS, Plasma 5.12.4 (not sure if I've updated
to 5.12.5 yet, though I know I've seen this for a couple minor releases at
least).

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

[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14

2018-05-01 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=387454

Eric Hameleers  changed:

   What|Removed |Added

 CC||al...@slackware.com

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

[systemsettings] [Bug 393598] New: Crash while searching in system settings

2018-04-27 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=393598

Bug ID: 393598
   Summary: Crash while searching in system settings
   Product: systemsettings
   Version: 5.12.4
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: etyr...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.12.4)

Qt Version: 5.10.0
Frameworks Version: 5.45.0
Operating System: Linux 4.15.17-65.current x86_64
Distribution: "Solus"

-- Information about the crash:
- What I was doing when the application crashed: Was searching in system
settings.  Crash happened while typing in search box.

The crash does not seem to be reproducible.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
[KCrash Handler]
#6  0x7f7cb49a8440 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#7  0x7f7cb3dce015 in  () at /usr/lib/libQt5Quick.so.5
#8  0x7f7cb3dcdc9d in QQuickItemPrivate::filterKeyEvent(QKeyEvent*, bool)
() at /usr/lib/libQt5Quick.so.5
#9  0x7f7cb3dda1e5 in QQuickItemPrivate::deliverKeyEvent(QKeyEvent*) () at
/usr/lib/libQt5Quick.so.5
#10 0x7f7cb3dda535 in QQuickItem::event(QEvent*) () at
/usr/lib/libQt5Quick.so.5
#11 0x7f7cb5384cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#12 0x7f7cb538c48e in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#13 0x7f7cb49a84d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#14 0x7f7cb3de57f8 in QQuickWindowPrivate::deliverKeyEvent(QKeyEvent*) ()
at /usr/lib/libQt5Quick.so.5
#15 0x7f7cb3de9cbf in QQuickWindow::keyReleaseEvent(QKeyEvent*) () at
/usr/lib/libQt5Quick.so.5
#16 0x7f7cb4d9d095 in QWindow::event(QEvent*) () at /usr/lib/libQt5Gui.so.5
#17 0x7f7cb3df41f5 in QQuickWindow::event(QEvent*) () at
/usr/lib/libQt5Quick.so.5
#18 0x7f7cb5384cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#19 0x7f7cb538c48e in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#20 0x7f7cb49a84d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#21 0x7f7cb40739fc in QQuickWidget::keyReleaseEvent(QKeyEvent*) () at
/usr/lib/libQt5QuickWidgets.so.5
#22 0x7f7cb53c3b48 in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#23 0x7f7cb407519b in QQuickWidget::event(QEvent*) () at
/usr/lib/libQt5QuickWidgets.so.5
#24 0x7f7cb5384cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#25 0x7f7cb538da34 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#26 0x7f7cb49a84d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#27 0x7f7cb53e11c4 in  () at /usr/lib/libQt5Widgets.so.5
#28 0x7f7cb5384cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#29 0x7f7cb538c48e in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#30 0x7f7cb49a84d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#31 0x7f7cb4d8dc80 in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() at /usr/lib/libQt5Gui.so.5
#32 0x7f7cb4d92ca5 in
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
() at /usr/lib/libQt5Gui.so.5
#33 0x7f7cb4d6a84b in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#34 0x7f7ca8fb in  () at /usr/lib/libQt5XcbQpa.so.5
#35 0x7f7cb49a671a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#36 0x7f7cb49af9b4 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#37 0x0040c976 in  ()
#38 0x7f7cb5d5800a in __libc_start_main () at /usr/lib/libc.so.6
#39 0x0040c9fa in _start ()

Reported using DrKonqi

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

[kopete] [Bug 393372] kopete-18.04.0: build error: invalid use of incomplete type ‘class Buffer’

2018-04-24 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=393372

Eric Hameleers  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #5 from Eric Hameleers  ---
The patch solves one occurrence of build failure but uncovers further errors.

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

[kopete] [Bug 393372] kopete-18.04.0: build error: invalid use of incomplete type ‘class Buffer’

2018-04-24 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=393372

--- Comment #4 from Eric Hameleers  ---
Created attachment 11
  --> https://bugs.kde.org/attachment.cgi?id=11&action=edit
Build log of kopete 18.04.0 evidencing further compilation errors

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

[kopete] [Bug 393372] kopete-18.04.0: build error: invalid use of incomplete type ‘class Buffer’

2018-04-22 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=393372

Eric Hameleers  changed:

   What|Removed |Added

 CC||al...@slackware.com

--- Comment #2 from Eric Hameleers  ---
Exact same issue here on Slackware, using KDE Frameworks 5.45.0, Plasma 5.12.4
and Applications 18.04.0 on top of Qt 5.9.5.

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

2018-04-21 Thread Eric Depagne
https://bugs.kde.org/show_bug.cgi?id=283682

Eric Depagne  changed:

   What|Removed |Added

 CC|e...@depagne.org|

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

[krita] [Bug 392508] pop-up pallete color picker bug

2018-04-08 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=392508

--- Comment #6 from Eric  ---
Also, I had that bug in Krita 3.3.3 too. Is it still supported? Should I report
that bug specially for Krita 3?

I see it's a little quiet here. I don't know if it's helpful but if I remember
correctly when I launch Krita for the first time (without preferences) that bug
does not occur. 
So it isn't really a solution to delete prefs every time I launch the app.

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

[kdenlive] [Bug 392745] New: transition properties combo-boxes unreadable dark text on black backgrounds

2018-04-04 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=392745

Bug ID: 392745
   Summary: transition properties combo-boxes unreadable dark text
on black backgrounds
   Product: kdenlive
   Version: 17.12.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: ericrfonta...@hotmail.com
  Target Milestone: ---

Created attachment 111834
  --> https://bugs.kde.org/attachment.cgi?id=111834&action=edit
transition properties

make them unreadable on arch linux w/ mate.

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

[krita] [Bug 392508] pop-up pallete color picker bug

2018-04-02 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=392508

--- Comment #4 from Eric  ---
Is there any way to fix that bug?

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

[kdenlive] [Bug 392625] New: "Disable Effect" button very small

2018-04-01 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=392625

Bug ID: 392625
   Summary: "Disable Effect" button very small
   Product: kdenlive
   Version: 17.12.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: ericrfonta...@hotmail.com
  Target Milestone: ---

Created attachment 111777
  --> https://bugs.kde.org/attachment.cgi?id=111777&action=edit
disable effect button too small

See attachment of an example of an effects property view.  The "Disable Effect"
button is too small such that can only read "le".  I don't remember this
happening on kdenlive on my computer in the past.  I'm on Mate Desktop, with
most up-to-date repos.

about->Kdenlive->libraries says:

KDE Frameworks 5.44.0
Qt 5.10.1 (built against 5.10.1)
The xcb windowing system

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

[krita] [Bug 392589] New: Driving color picker

2018-03-31 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=392589

Bug ID: 392589
   Summary: Driving color picker
   Product: krita
   Version: 4.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Color Selectors
  Assignee: krita-bugs-n...@kde.org
  Reporter: erykpoc...@outlook.com
  Target Milestone: ---

Created attachment 111764
  --> https://bugs.kde.org/attachment.cgi?id=111764&action=edit
shows place where I clicked and where the actual color is

My scenario is simple.
I press right mouse button on canvas to show color picker but when i choose a
color it randomly changes. 
That mini circle in color picker usually drives for 2-3 seconds before it stops
at the edge. 
I had that problem in Krita 3.3.3 and I still have that in krita 4.

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

[plasmashell] [Bug 391269] New: Make plasma animations non-blocking

2018-03-01 Thread Eric Mesa
https://bugs.kde.org/show_bug.cgi?id=391269

Bug ID: 391269
   Summary: Make plasma animations non-blocking
   Product: plasmashell
   Version: 5.11.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ericsbinarywo...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Currently I am copying and pasting 2 files totaling 10BG using Dolphin from a
folder locally onto a folder on an NFS share. Plasma has gone into disk sleep
and is completely unresponsive. The mouse works, as does any program. But I
cannot click on any plasma components - the "start menu", the task switch, the
activity switcher, and other components all do nothing.

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

[kmymoney] [Bug 390773] Can't create new record using existing beneficiaire

2018-02-23 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=390773

--- Comment #6 from Eric  ---
Thanks Thomas! 
Sorry for the misunderstanding ;-) 
It works using the keyboard. 
Thanks again. 
Eric 

- Mail original -

De: "Thomas Baumgart"  
À: "eric piffaut"  
Envoyé: Vendredi 23 Février 2018 07:34:46 
Objet: [kmymoney] [Bug 390773] Can't create new record using existing
beneficiaire 

https://bugs.kde.org/show_bug.cgi?id=390773 

Thomas Baumgart  changed: 

What |Removed |Added 
 
Status|REOPENED |RESOLVED 
Resolution|--- |DUPLICATE 

--- Comment #5 from Thomas Baumgart  --- 
As I mentioned before, this has been fixed in the source code and will be 
available in version 5.0.1. Workaround is to use the keyboard (arrow keys and 
Enter) to select the existing payee instead of the mouse. This should avoid the 
crash. 

*** This bug has been marked as a duplicate of bug 390264 ***

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

[kmymoney] [Bug 390773] Can't create new record using existing beneficiaire

2018-02-22 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=390773

Eric  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #4 from Eric  ---
I'm using KMyMoney V5.0.0 under Ubuntu Bionic Beaver / Gnome 3.26.2 64bit
KMyMoney crash each time I want to add a record using an existing beneficiaire
so what we are doing everytime using this software...

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

[kmymoney] [Bug 390773] Can't create new record using existing beneficiaire

2018-02-22 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=390773

--- Comment #2 from Eric  ---
Dear Thomas, 

Bug still exist. It's probably not the same ticket... 
I can't crate any record based on an existing beneficiaire. I can only do that
with new beneficiaire. 

Thaks for your help. 

Kind regards, 

Eric 

- Mail original -

De: "Thomas Baumgart"  
À: "eric piffaut"  
Envoyé: Mardi 20 Février 2018 15:24:50 
Objet: [kmymoney] [Bug 390773] Can't create new record using existing
beneficiaire 

https://bugs.kde.org/show_bug.cgi?id=390773 

Thomas Baumgart  changed: 

What |Removed |Added 
 
Resolution|--- |DUPLICATE 
Status|UNCONFIRMED |RESOLVED 

--- Comment #1 from Thomas Baumgart  --- 
Although you don't experience a crash, the fix is the same. 

*** This bug has been marked as a duplicate of bug 390264 ***

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

[konqueror] [Bug 192932] Konqueror: Add an option to disable the use of favicons as icons in the taskbar

2018-02-21 Thread Eric Forgeot
https://bugs.kde.org/show_bug.cgi?id=192932

Eric Forgeot  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #8 from Eric Forgeot  ---
Go to https://www.mozilla.org/
Now Konqueror has a firefox icon!!

;)

Honestly, this "feature" is annoying as hell...
No other browser is doing this. They all "protect" and advert for their brand
by displaying it in the taskbar. And the Konqueror icon is good-looking, what a
pity!

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

[kmymoney] [Bug 390773] New: Can't create new record using existing beneficiaire

2018-02-20 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=390773

Bug ID: 390773
   Summary: Can't create new record using existing beneficiaire
   Product: kmymoney
   Version: 5.0.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: eric.piff...@laposte.net
  Target Milestone: ---

I have try with 2 differents databases but have exactly save problem :
If I create a new beneficiare I can crate a new record one time
If I try to use an existing beneficiaire, I got immediatly a message to let me
know I have to save or cancel operation without any possibility to put an
amount or any additional information. In any case it cancel and never save.
Please let me know if you need more information.

Regards,
Eric

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

[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too

2017-12-28 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=336043

Eric Hameleers  changed:

   What|Removed |Added

 CC||al...@slackware.com

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

[kstars] [Bug 387929] The dates of the equinoxes and solstices given in kstars by the calculator tool are wrong

2017-12-15 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=387929

--- Comment #2 from Eric  ---
The winter solstice in 2017 is scheduled for December 21 at 16:29 UTC (or 16:27
according to the IMCCE). What I do not understand is why Kstars tells me that
it is scheduled for December 21 at 22:19 UTC? I tested kstars on two different
computers.

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

[kstars] [Bug 387929] New: The dates of the equinoxes and solstices given in kstars by the calculator tool are wrong

2017-12-15 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=387929

Bug ID: 387929
   Summary: The dates of the equinoxes and solstices given in
kstars by the calculator tool are wrong
   Product: kstars
   Version: 2.8.8
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: bilbohobbi...@orange.fr
  Target Milestone: ---

Created attachment 109385
  --> https://bugs.kde.org/attachment.cgi?id=109385&action=edit
Results provided by IMCCE (https://promenade.imcce.fr/en/pages4/439.html) vs
provided by Kstars

The dates of the equinoxes and solstices given in kstars by the calculator tool
are wrong.
1- It seems that there is a lag of one year. 2018 in kstars => 2017 for the
IMCCE (Institute for Celestial Mechanics and Computation of Ephemerides,
official service that "manages" the time in France, see presentation here :
https://www.imcce.fr/institut/presentation/)
2 even with the lag of a year, there are differences of several minutes between
the different results.

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

[kstars] [Bug 387831] New: weird behaviour of "what's interesting" window

2017-12-12 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=387831

Bug ID: 387831
   Summary: weird behaviour of "what's interesting" window
   Product: kstars
   Version: 2.8.8
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: bilbohobbi...@orange.fr
  Target Milestone: ---

The window of "what's interesting" tool opens normally, but as soon as you
click on the sky map, it goes in the background of the main window, as shown in
the video. After a few manipulations, I manage to put "what's interesting" in
the foreground, but some buttons (those below) are unusable. I close the
windows of "What's interesting", I restart the tool, and there, miracle,
everything works normally ...
the problem seems to come from the fact that at startup, the tool opens a
second window. When we close these windows and restart the tool, it does not
open additional windows and then works properly. 

I made a screencast of the bug available here : https://youtu.be/C-6B_T8LQlA

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

[kstars] [Bug 387678] New: compute in calculator tool makes kstars crash

2017-12-07 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=387678

Bug ID: 387678
   Summary: compute in calculator tool makes kstars crash
   Product: kstars
   Version: 2.8.8
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: bilbohobbi...@orange.fr
  Target Milestone: ---

Created attachment 109240
  --> https://bugs.kde.org/attachment.cgi?id=109240&action=edit
gdb result

That's how I proceed with kstars: In the menu bar, tools> calculator, then in
the calculator module, I choose solar system, conjunctions. I set the dates as
of 1st January 2018 00:00 until 1st January 2019 00:00. I choose between the
planets and the moon, a gap of 10 degrees max, I leave conjunction and I ask to
calculate. From there, every time, the software crashes completely and I have
to restart it

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

[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

2017-11-13 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=386892

Eric Fontaine  changed:

   What|Removed |Added

 CC||ericrfonta...@hotmail.com

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

[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

2017-11-13 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=386892

--- Comment #2 from Eric Fontaine  ---
Created attachment 108855
  --> https://bugs.kde.org/attachment.cgi?id=108855&action=edit
New crash information added by DrKonqi

plasmashell (5.11.3) using Qt 5.9.2

I've just reproduced the crash, and this time am using the crash reporting
assistant.

(Note again I'm on fresh install of Parabola Linux, the FOSS-only version of
Arch)

-- Backtrace (Reduced):
#5  0x7fd62018cc81 in wl_proxy_create_wrapper () at
/usr/lib/libwayland-client.so.0
#6  0x7fd60258185a in  () at /usr/lib/libEGL_mesa.so.0
#7  0x7fd60256e6df in  () at /usr/lib/libEGL_mesa.so.0
#8  0x7fd602bba722 in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so
#9  0x7fd602bb8bce in  () at
/usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so

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

[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

2017-11-13 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=386892

--- Comment #1 from Eric Fontaine  ---
I can reproduce with these following steps:

1. Right click panel
2. select "Panel Settings"
3. press the "+ Add Widgets" button

at this point the background wallpaper flickers (although all my other
applications that are up don't seem to be affected).

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

[plasmashell] [Bug 386892] New: Segfault on fresh install of parabola (Arch) linux with kde plasa wayland

2017-11-13 Thread Eric Fontaine
https://bugs.kde.org/show_bug.cgi?id=386892

Bug ID: 386892
   Summary: Segfault on fresh install of parabola (Arch) linux
with kde plasa wayland
   Product: plasmashell
   Version: 5.11.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: ericrfonta...@hotmail.com
  Target Milestone: 1.0

Created attachment 108853
  --> https://bugs.kde.org/attachment.cgi?id=108853&action=edit
backtrace

I right clicked on panel and tried to add wiget, then screen briefly flashed,
and the error reporter appeared and produced the attached kcrash.txt

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

[marble] [Bug 386766] New: Download maps does not work

2017-11-11 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=386766

Bug ID: 386766
   Summary: Download maps does not work
   Product: marble
   Version: 1.9 (KDE 4.14)
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: econrad...@gmail.com
  Target Milestone: ---

Created attachment 108807
  --> https://bugs.kde.org/attachment.cgi?id=108807&action=edit
Download dialogue (T) Install (B) 100% download, must cancel

In version 1.9.1 (Windows/Qt): the download maps function is not able to load
the map that has been downloaded.

To recreate the problem:
1) In the File menu, select the "Download Maps..." dialog.
2) Select an available map (I chose Mercury) and select "Install"
3) Download progresses and reaches 100%, but the only option is Cancel

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

[marble] [Bug 365061] Marble could not download maps

2017-11-11 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=365061

Eric  changed:

   What|Removed |Added

 CC||econrad...@gmail.com

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

[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.

2017-11-11 Thread Eric Depagne
https://bugs.kde.org/show_bug.cgi?id=341143

Eric Depagne  changed:

   What|Removed |Added

 CC|e...@depagne.org|

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

[ksmserver] [Bug 382662] Leave screen dark

2017-10-14 Thread Eric L .
https://bugs.kde.org/show_bug.cgi?id=382662

Eric L.  changed:

   What|Removed |Added

 CC||ewl+...@lavar.de

--- Comment #3 from Eric L.  ---
Created attachment 108358
  --> https://bugs.kde.org/attachment.cgi?id=108358&action=edit
dark leave screen

I have the same issue since I upgraded from f25 to f26, it did an update from
plasma 5.9.5 to 5.10.5. Additionally I tried to autoremove packages, which I
had to roll-back because it removed too many packages. I can provide more
information if someone says what is required.

But first would be necessary to understand where the style of this leave screen
is defined: I couldn't find any hint on the Internet where it might come from.

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

[plasma-nm] [Bug 377029] Crash in connection editor when importing openvpn connection

2017-10-02 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=377029

--- Comment #3 from Eric Hameleers  ---
(In reply to Jan Grulich from comment #2)
> Ping? Can you please provide requested information?

IN my original post I already mentioned "Even with gdb I do not get a useful
backtrace".

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

[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar

2017-09-20 Thread Eric Donkersloot
https://bugs.kde.org/show_bug.cgi?id=376245

--- Comment #14 from Eric Donkersloot  ---
I tried both workarounds listed in this bug report:

1. Setting the cursor size to a fixed value (36)
2. Create ~/.icons/default/index.theme and set the cursor theme like in KDE

But they both have no effect. I've posted the output of "qdbus org.kde.KWin
/KWin supportInformation" again here: https://paste.kde.org/pjoxuk9ej/w7hv2v

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

[systemsettings] [Bug 372451] mouse cursor is small in titlebar, large elsewhere

2017-09-14 Thread Eric Donkersloot
https://bugs.kde.org/show_bug.cgi?id=372451

Eric Donkersloot  changed:

   What|Removed |Added

 CC||eric.donkersl...@gmail.com

--- Comment #12 from Eric Donkersloot  ---
I can reproduce this bug, both with Qt and GTK applications running on X11.

Output of qdbus org.kde.KWin /KWin supportInformation

https://paste.kde.org/p9abxm9fw/7ptqql

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

[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar

2017-09-14 Thread Eric Donkersloot
https://bugs.kde.org/show_bug.cgi?id=376245

--- Comment #12 from Eric Donkersloot  ---
Is this a duplicate of bug #372451 ?

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

[frameworks-kglobalaccel] [Bug 384597] Shift+alt+[arrow keys] and Shift+Meta+[arrow keys] shortcuts broken in 5.38.0

2017-09-14 Thread Eric Donkersloot
https://bugs.kde.org/show_bug.cgi?id=384597

--- Comment #15 from Eric Donkersloot  ---
upgraded kglobalaccel (5.38.0-1 -> 5.38.1-1)

Fixed, thanks!

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

[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar

2017-09-12 Thread Eric Donkersloot
https://bugs.kde.org/show_bug.cgi?id=376245

--- Comment #11 from Eric Donkersloot  ---
Output ofqdbus org.kde.KWin /KWin supportInformation

https://paste.kde.org/p9abxm9fw/7ptqql

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

[kwin] [Bug 376245] Mouse cursor changes size when pointer on Kwin window title bar

2017-09-12 Thread Eric Donkersloot
https://bugs.kde.org/show_bug.cgi?id=376245

Eric Donkersloot  changed:

   What|Removed |Added

 CC||eric.donkersl...@gmail.com

--- Comment #10 from Eric Donkersloot  ---
Same issue here:

Lenovo Thinkpad X1 Carbon (2560x1440)
DPI settings desktop: 168
SDDM settings: ServerArguments=-nolisten tcp -dpi 168
Plasma: 5.10.5
KDE Frameworks: 5.38.0
Arch Linux

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

[frameworks-kwindowsystem] [Bug 384597] Shift+alt+[arrow keys] and Shift+Meta+[arrow keys] shortcuts broken in 5.38.0

2017-09-12 Thread Eric Donkersloot
https://bugs.kde.org/show_bug.cgi?id=384597

Eric Donkersloot  changed:

   What|Removed |Added

 CC||eric.donkersl...@gmail.com

--- Comment #7 from Eric Donkersloot  ---
I can confirm this one (running Arch Linux as well)

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

[gwenview] [Bug 313309] gv crashed when going full screen

2017-09-09 Thread Eric W
https://bugs.kde.org/show_bug.cgi?id=313309

--- Comment #4 from Eric W  ---
No idea... That is old and alas, for my workflow I have switched
over to Mac and Photoshop etc for my image work

Sorry...

--Eric


Nate Graham wrote:
>
> https://bugs.kde.org/show_bug.cgi?id=313309
>
> Nate Graham  changed:
>
>What|Removed |Added
> 
>  Resolution|--- |WAITINGFORINFO
>  CC||pointedst...@zoho.com
>  Status|UNCONFIRMED |NEEDSINFO
>
> --- Comment #3 from Nate Graham  ---
> Is this reproducible with KF5 versions of Gwenview?

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

[okular] [Bug 314755] "Color options" from "Print Dialog -> Properties -> Advanced" override "Color options" from "Print Dialog -> Options -> Options"

2017-07-22 Thread Eric L .
https://bugs.kde.org/show_bug.cgi?id=314755

--- Comment #4 from Eric L.  ---
Sorry for the noise, could this bug be related to
https://bugs.kde.org/show_bug.cgi?id=198795 ?

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

[okular] [Bug 314755] "Color options" from "Print Dialog -> Properties -> Advanced" override "Color options" from "Print Dialog -> Options -> Options"

2017-07-22 Thread Eric L .
https://bugs.kde.org/show_bug.cgi?id=314755

Eric L.  changed:

   What|Removed |Added

 CC||ewl+...@lavar.de

--- Comment #3 from Eric L.  ---
This issue does still exist in okular-16.08.3-1.fc25.x86_64 respectively:

$ rpm -qa | grep print
libfprint-0.6.0-3.fc24.x86_64
kde-print-manager-libs-16.12.3-1.fc25.x86_64
kde-print-manager-16.12.3-1.fc25.x86_64
libchromaprint-1.2-4.fc24.x86_64
fprintd-0.7.0-2.fc25.x86_64
gutenprint-cups-5.2.11-2.fc24.x86_64
system-config-printer-udev-1.5.7-10.fc25.x86_64
gutenprint-5.2.11-2.fc24.x86_64
redhat-lsb-printing-4.1-33.fc25.x86_64
gutenprint-libs-5.2.11-2.fc24.x86_64
system-config-printer-libs-1.5.7-10.fc25.noarch
fprintd-pam-0.7.0-2.fc25.x86_64
(not sure which one might be exactly relevant)

Let me know if I can do anything to help solve this long standing issue, it
seems easy to reproduce though.

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

[neon] [Bug 381904] Impossible to unlock screen (Kde neon 5.10.3)

2017-07-17 Thread eric
https://bugs.kde.org/show_bug.cgi?id=381904

eric  changed:

   What|Removed |Added

 CC||pro...@gmx.net

--- Comment #10 from eric  ---
Same problem here on ArchLinux 32bit after updating to kscreenlocker-5.10.3.
But many other packages are also updated. The last working version was 5.10.2.

After entering the password to unlock, the screenlocker screen disappears and I
get a black screen where I can see and move the mouse pointer around. Nothing
can be typed or clicked.

I've checked the password with '/usr/lib/kscreenlocker_greet --testing'.

To unlock I use (more or less the same method as in comment #1):
loginctl unlock-sessions && killall -9 kscreenlocker_greet

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

[kontact] [Bug 360524] Filter overload

2017-07-10 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=360524

--- Comment #2 from Eric  ---
Hi Denis,
Thks for your feedback.
I've been away from home since February, didn't check my Kontact nore 
did have any opportunity to update it.
I need to plan this update as it will be very complicated,
I will have to re-setup all the simlink to the partition where my email 
database is installed (different HDD) and that takes a long annoying 
time (compared to Thunderbird which does it with one click)

By the time I come back home this will be closed.

I will re-open one if necessary

Have a great day !
Éric

Le 2017-06-23 16:29, Denis Kurz a écrit :
> https://bugs.kde.org/show_bug.cgi?id=360524
> 
> Denis Kurz  changed:
> 
>What|Removed |Added
> 
>  CC||kde...@posteo.de
>  Resolution|--- |WAITINGFORINFO
>  Status|UNCONFIRMED |NEEDSINFO
> 
> --- Comment #1 from Denis Kurz  ---
> This bug has never been confirmed for a KDE PIM version that is based 
> on KDE
> Frameworks, except possibly a Technology Preview version 5.0.x. Those
> Framework-based versions differ significantly from the old 4.x series.
> Therefore, I plan to close it in around two or three months. In the 
> meantime,
> it is set to WAITINGFORINFO to give reporters the opportunity to check 
> if it is
> still valid. As soon as someone confirms it for a recent version (at 
> least 5.1,
> ideally even more recent), I'll gladly reopen it.
> 
> Please understand that we lack the manpower to triage bugs reported for
> versions almost two years beyond their end of life.

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

[partitionmanager] [Bug 380296] New: crash when commiting delete then new partation on removable media after removal and re-attaching

2017-05-28 Thread Eric S
https://bugs.kde.org/show_bug.cgi?id=380296

Bug ID: 380296
   Summary: crash when commiting delete then new partation on
removable media after removal and re-attaching
   Product: partitionmanager
   Version: unspecified
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: andr...@stikonas.eu
  Reporter: subscri...@blackbrook.org
  Target Milestone: ---

Application: partitionmanager (3.0.0)

Qt Version: 5.8.0
Frameworks Version: 5.33.0
Operating System: Linux 4.8.6-1-CHAKRA x86_64
Distribution: "Chakra"

-- Information about the crash:
- What I was doing when the application crashed:
I unmounted a partition on removable media (SD drive)
then deleted a partition
then added a new partion
then I ejected  the media (having forgotten to "Apply")
I reinserted the media, and hit apply. 
Clearly this was wrong, but partition manager should not crash.

-- Backtrace:
Application: KDE Partition Manager (partitionmanager), signal: Segmentation
fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f32433b9d00 (LWP 18520))]

Thread 3 (Thread 0x7f321fc3c700 (LWP 18798)):
#0  0x7f323f5b9dbd in read () from /usr/lib/libc.so.6
#1  0x7f322b072191 in pa_read () from
/usr/lib/pulseaudio/libpulsecommon-9.0.so
#2  0x7f322b702a1e in pa_mainloop_prepare () from /usr/lib/libpulse.so.0
#3  0x7f322b703490 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#4  0x7f322b703550 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#5  0x7f322b711799 in ?? () from /usr/lib/libpulse.so.0
#6  0x7f322b0a1a28 in ?? () from /usr/lib/pulseaudio/libpulsecommon-9.0.so
#7  0x7f323c625444 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f323f5c71af in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f3228f6b700 (LWP 18522)):
#0  0x7f323f5b in poll () from /usr/lib/libc.so.6
#1  0x7f3238f431e5 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f3238f43322 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f323fedaf2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f323fe855da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f323fca99a4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f323e16ca25 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f323fcae568 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f323c625444 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f323f5c71af in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f32433b9d00 (LWP 18520)):
[KCrash Handler]
#4  0x7f3242f1510b in PartWidget::paintEvent(QPaintEvent*) () from
/usr/lib/libkpmcore.so.4
#5  0x7f32407b9d48 in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#6  0x7f32407729bc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#7  0x7f324077a3e6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#8  0x7f323fe87188 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#9  0x7f32407b2b7a in QWidgetPrivate::sendPaintEvent(QRegion const&) ()
from /usr/lib/libQt5Widgets.so.5
#10 0x7f32407b31c1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/usr/lib/libQt5Widgets.so.5
#11 0x7f32407b3e8c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5
#12 0x7f32407b3d79 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5
#13 0x7f32407b2d31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/usr/lib/libQt5Widgets.so.5
#14 0x7f32407b3e8c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5
#15 0x7f32407b3d79 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5
#16 0x7f32407b2d31 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from
/usr/lib/libQt5Widgets.so.5
#17 0x7f32407b3e8c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*,
QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
QWidgetBackingStore*) () from /usr/lib/libQt5Widgets.so.5
#18 0x7f32407b3d79 

[keditbookmarks] [Bug 303830] Warn if keditbookmarks is not installed

2017-04-04 Thread Eric Kincl
https://bugs.kde.org/show_bug.cgi?id=303830

Eric Kincl  changed:

   What|Removed |Added

 CC||e...@kincl.net

--- Comment #7 from Eric Kincl  ---
It's 2017 and this is still a problem on KDE 5.  (Using the KDE Neon distro at
that.)

There isn't even a console error that gets thrown, just... nothing.  I've been
ripping my hair out trying to figure out what the problem was and I finally
found this buried in Google.  A simple error message would be very beneficial.

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

[kwin] [Bug 377440] New: KWIN crashes when starting saved VBOX client with two screens.

2017-03-09 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=377440

Bug ID: 377440
   Summary: KWIN crashes when starting saved VBOX client with two
screens.
   Product: kwin
   Version: 5.8.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ebelc...@eacbelcher.net
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.49-16-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
Starting VBOX saved client from a shortcut on the desktop.
VirtualBox Graphical User Interface
Version 5.1.14 r112924 (Qt5.6.1)

Symptom have only started occuring in the last few weeks after some OpenSUSE
updates. Virtual Box version has been installed and stable since the release of
this version.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f457c988940 (LWP 2474))]

Thread 7 (Thread 0x7f44c0d65700 (LWP 2632)):
#0  0x7f457c0fdb03 in select () at /lib64/libc.so.6
#1  0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f45797d20c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f45797d2527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f4579781fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f45741ae9c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f45795c19e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f457c104d3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f4552ffe700 (LWP 2585)):
#0  0x7f457c3cb0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f457875793b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f4578757969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f457c104d3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f454179e700 (LWP 2584)):
#0  0x7f457c3cb0af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4550ed7533 in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f4550ed6d57 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f457c104d3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f4553fff700 (LWP 2554)):
#0  0x7f457c0fdb03 in select () at /lib64/libc.so.6
#1  0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f45797d20c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f45797d2527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f4579781fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f45741ae9c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f45795c19e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f457c104d3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f4561864700 (LWP 2514)):
#0  0x7f457c0fdb03 in select () at /lib64/libc.so.6
#1  0x7f45797d0849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f45797d20c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f45797d2527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f4579781fdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f45795bcf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f457338f1d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f45795c19e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f457c104d3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f45630b7700 (LWP 2510)):
#0  0x7f457c0fc49d in poll () at /lib64/libc.so.6
#1  0x7f457b2833e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f457b284fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f4563d67839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f45795c19e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f457c3c6734 in start_thread () at /lib64/libpthread.so.0
#6  0x000

[kwin] [Bug 377321] New: KWIN crashes sometimes when opening VBOX client

2017-03-06 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=377321

Bug ID: 377321
   Summary: KWIN crashes sometimes when opening VBOX client
   Product: kwin
   Version: 5.8.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ebelc...@eacbelcher.net
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.49-16-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
On starting a VirtualBox client (Windows 10) with two screens, one window will
sometimes fail during startup. Disabling and restarting the second screen
resolves the symptom.

VirtualBox Graphical User Interface
Version 5.1.14 r112924 (Qt5.6.1)
NAME="openSUSE Leap"
VERSION="42.2"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.2"
PRETTY_NAME="openSUSE Leap 42.2"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.2"
BUG_REPORT_URL="https://bugs.opensuse.org";
HOME_URL="https://www.opensuse.org/

The problem is a reasonably new one, 4-6 weeks and I believe due to a OpenSUSE
patch. VBOX has remained at the above version since it was released.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f52d37b1940 (LWP 2670))]

Thread 7 (Thread 0x7f5217ce5700 (LWP 2847)):
#0  0x7f52d2f26b03 in select () at /lib64/libc.so.6
#1  0x7f52d05f9849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f52d05fb0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f52d05fb527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f52d05aafdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f52cafd79c8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f52d03ea9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f52b1ffc700 (LWP 2773)):
#0  0x7f52d31f40af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f52cf58093b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f52cf580969 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f529871e700 (LWP 2772)):
#0  0x7f52d31f40af in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f52a398e533 in  () at /usr/lib64/dri/radeonsi_dri.so
#2  0x7f52a398dd57 in  () at /usr/lib64/dri/radeonsi_dri.so
#3  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#4  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f52b2ffd700 (LWP 2749)):
#0  0x7f52d05fb1f9 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#1  0x7f52d05fb527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#2  0x7f52d05aafdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#4  0x7f52cafd79c8 in  () at /usr/lib64/libQt5Qml.so.5
#5  0x7f52d03ea9e9 in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#7  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f52b3fff700 (LWP 2702)):
#0  0x7f52d2f26b03 in select () at /lib64/libc.so.6
#1  0x7f52d05f9849 in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () at /usr/lib64/libQt5Core.so.5
#2  0x7f52d05fb0c3 in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () at /usr/lib64/libQt5Core.so.5
#3  0x7f52d05fb527 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f52d05aafdb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f52d03e5f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f52ca1b81d5 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f52d03ea9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f52d31ef734 in start_thread () at /lib64/libpthread.so.0
#9  0x7f52d2f2dd3d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f52b9ee0700 (LWP 2671)):
#0  0x7f52d2f2549d in poll () at /lib64/libc.so.6
#1  0x7f52d20ac3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x7f52d20adfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f52bab90839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x00

[plasma-nm] [Bug 377029] Crash in connection editor when importing openvpn connection

2017-02-28 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=377029

Eric Hameleers  changed:

   What|Removed |Added

 CC||al...@slackware.com

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

[plasma-nm] [Bug 377029] New: Crash in connection editor when importing openvpn connection

2017-02-28 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=377029

Bug ID: 377029
   Summary: Crash in connection editor when importing openvpn
connection
   Product: plasma-nm
   Version: 5.9.2
  Platform: Slackware Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: editor
  Assignee: jgrul...@redhat.com
  Reporter: al...@slackware.com
  Target Milestone: ---

When using the Plasma 5 connection editor to import an existing openvpn
connection, I get consistent crash after selecting the .ovpn file and clicking
"OK". Even with gdb I do not get a useful backtrace but when using gdb I
noticed that the crash occurs when the "copying certificate" window is drawn. I
get the window borders but not the window content.

In the same Plasma 5 desktop session I can however start the GTK-based
nm-applet and successfully import that same .ovpn definition file. The
resulting OpenVPN entry is also visible in the Plasma 5 widget and can
successfully be used. 

System: Slackware-current 64bit (post-14.2) with Plasma 5.9.2, KF 5.31.0 and Qt
5.7.1. Using NetworkManager 1.6.0 and NetworkManager-openvpn 1.2.8.
The OpenVPN .ovpn file I tried to import is any one from
https://www.privateinternetaccess.com/openvpn/openvpn.zip

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

[kontact] [Bug 376654] Crashes on restart

2017-02-23 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=376654

--- Comment #2 from Eric  ---
Hi Christophe,
I'm sorry that the bug report system is unable to find a bug that 
appears every other day and reported with the same title from the same 
person

That's why I HAVE to create a new one each time.

I can feel your frustration, please consider mine.

It's also unfortunate that KDE is not suggesting Kmail/Kontact update, 
even though I zypper patch AND Zypper up every other day if not every 
day

I will do a manual specific update of the package, hopping it won't 
smash all my simlinks, it took me ages to find them all and simlink them 
one by one

Thks again for your support !
Eric
A long time user still novice ;)


On 2017-02-22 22:39, Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=376654
> 
> Christoph Feck  changed:
> 
>What|Removed |Added
> 
>  Resolution|--- |INVALID
>  Status|UNCONFIRMED |RESOLVED
> 
> --- Comment #1 from Christoph Feck  ---
> Already reported, and I am not going to search it again.
> 
> Please update your software, we already released KMail 5.3 and KMail 
> 5.4.

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

[kontact] [Bug 376654] New: Crashes on restart

2017-02-18 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=376654

Bug ID: 376654
   Summary: Crashes on restart
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.38-47-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
zypper patch and zypper up then reboot 
- Custom settings of the application:
all folder seemlinked to a safe side hard 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 0x7f4b4ca3e7c0 (LWP 3274))]

Thread 22 (Thread 0x7f4a957fa700 (LWP 3812)):
#0  0x7f4b4221fd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4b421dde0e in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4b421ddf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4b4a1c0d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f4b4a167d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4b49f8961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f4b49f8e32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f4b429fb0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f4b4968502d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f4a967fc700 (LWP 3808)):
#0  0x7fffda4ddb26 in clock_gettime ()
#1  0x7f4b49691c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f4b4a03f7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f4b4a1bf3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f4b4a1bf945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4b4a1c0b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f4b421dd4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f4b421ddd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f4b421ddf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f4b4a1c0d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f4b4a167d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f4b49f8961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f4b49f8e32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f4b429fb0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f4b4968502d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f4a96ffd700 (LWP 3806)):
#0  0x7f4b49f86bfa in QMutex::lock() () at /usr/lib64/libQt5Core.so.5
#1  0x7f4b4a1c0cb5 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f4b421dd4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4b421ddd80 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f4b421ddf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f4b4a1c0d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f4b4a167d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f4b49f8961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f4b49f8e32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f4b429fb0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4b4968502d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f4a977fe700 (LWP 3802)):
#0  0x7f4b4967cbfd in poll () at /lib64/libc.so.6
#1  0x7f4b421dde64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4b421ddf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4b4a1c0d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f4b4a167d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4b49f8961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f4b49f8e32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f4b429fb0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f4b4968502d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f4a97fff700 (LWP 3801)):
#0  0x7fffda4ddb26 in clock_gettime ()
#1  0x7f4b49691c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f4b4a03f7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f4b4a1bf3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f4b4a1bf945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4b4a1c0b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f4b421dd4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f4b421d

[kontact] [Bug 375870] New: Crashes on reboot

2017-02-01 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=375870

Bug ID: 375870
   Summary: Crashes on reboot
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
after update, restart computer, start Kontact, it crashes
- Custom settings of the application:
many profiles, many email account, many many filter that no longer works, and
all akonadi folder are simlinked to a different 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 0x7ff3b8ccb7c0 (LWP 2064))]

Thread 22 (Thread 0x7ff309ffb700 (LWP 2598)):
#0  0x7ffe5e341b26 in clock_gettime ()
#1  0x7ff3b591ec7d in clock_gettime () at /lib64/libc.so.6
#2  0x7ff3b62cc7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7ff3b644c3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7ff3b644c945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff3b644db5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7ff3ae46a4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7ff3ae46ad80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7ff3ae46af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7ff3b644dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7ff3b63f4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7ff3b621661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7ff3b621b32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7ff3aec880a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7ff3b591202d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7ff30affd700 (LWP 2594)):
#0  0x7ff3b5905cd9 in read () at /lib64/libc.so.6
#1  0x7ff3ae4abb60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff3ae46a999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff3ae46adf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7ff3ae46af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7ff3b644dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7ff3b63f4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7ff3b621661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7ff3b621b32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7ff3aec880a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7ff3b591202d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7ff30b7fe700 (LWP 2593)):
#0  0x7ff3b5909bfd in poll () at /lib64/libc.so.6
#1  0x7ff3ae46ae64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7ff3ae46af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7ff3b644dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7ff3b63f4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff3b621661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7ff3b621b32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7ff3aec880a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7ff3b591202d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7ff30bfff700 (LWP 2587)):
#0  0x7ffe5e341b26 in clock_gettime ()
#1  0x7ff3b591ec7d in clock_gettime () at /lib64/libc.so.6
#2  0x7ff3b62cc7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7ff3b644c3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7ff3b644c945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff3b644db5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7ff3ae46a4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7ff3ae46ad80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7ff3ae46af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7ff3b644dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7ff3b63f4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7ff3b621661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7ff3b621b32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7ff3aec880a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7ff3b591202d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7ff318ff9700 (LWP 2585)):
#0  0x7ff

[kontact] [Bug 375771] New: Crashes on settings change

2017-01-30 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=375771

Bug ID: 375771
   Summary: Crashes on settings change
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
writing a "reply all" using a different "from" than the one in the original
email, so far so good, then decided to change the "sent folder" to match the
new profile ... and crash.
- Custom settings of the application:
Many profiles, many accounts, and every foldr are simlinked to a different
partition on a different disk

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 0x7feac23e17c0 (LWP 2587))]

Thread 26 (Thread 0x7fea05f8c700 (LWP 2700)):
#0  0x7feabf0345ff in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7feabf01bcc2 in read () at /lib64/libc.so.6
#2  0x7feab7bc1b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7feab7b80999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7feab7b80df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7feab7b80f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7feabfb63d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7feabfb0ad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7feabf92c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x7feabf93132f in  () at /usr/lib64/libQt5Core.so.5
#10 0x7feab839e0a4 in start_thread () at /lib64/libpthread.so.0
#11 0x7feabf02802d in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7fea06be8700 (LWP 2697)):
#0  0x7feabf01fbfd in poll () at /lib64/libc.so.6
#1  0x7feab7b80e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7feab7b80f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7feabfb63d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7feabfb0ad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7feabf92c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7feabf93132f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7feab839e0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7feabf02802d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7fea077fe700 (LWP 2629)):
#0  0x7ffe48c56b26 in clock_gettime ()
#1  0x7feabf034c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7feabf9e27d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7feabfb623b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7feabfb62945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7feabfb63b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7feab7b804ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7feab7b80d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7feab7b80f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7feabfb63d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7feabfb0ad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7feabf92c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7feabf93132f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7feab839e0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7feabf02802d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7fea07fff700 (LWP 2628)):
#0  0x7ffe48c56b26 in clock_gettime ()
#1  0x7feabf034c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7feabf9e27d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7feabfb623b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7feabfb62945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7feabfb63b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7feab7b804ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7feab7b80d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7feab7b80f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7feabfb63d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7feabfb0ad53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7feabf92c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7feabf93132f in  () at /usr/lib64/libQt5Core.so.5
#13 

[dolphin] [Bug 375753] New: crash on file transfer

2017-01-30 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=375753

Bug ID: 375753
   Summary: crash on file transfer
   Product: dolphin
   Version: 15.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: eric.v...@msg4.us
  Target Milestone: ---

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
moving some files from one partition to another.
A bulk move, about 20 files, from my local SDD to a remote NAS partition

The crash can be reproduced sometimes.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efe12bb57c0 (LWP 9098))]

Thread 3 (Thread 0x7efdeff62700 (LWP 9119)):
#0  0x7efe12462bfd in poll () at /lib64/libc.so.6
#1  0x7efe0749ae64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7efe0749af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7efe0c7a4d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7efe0c74bd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7efe0c56d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7efe0c57232f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7efe080200a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7efe1246b02d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7efdfbb67700 (LWP 9103)):
#0  0x7efe12462bfd in poll () at /lib64/libc.so.6
#1  0x7efe0545f422 in  () at /usr/lib64/libxcb.so.1
#2  0x7efe0546100f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7efdfdebc3c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7efe0c57232f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7efe080200a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7efe1246b02d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7efe12bb57c0 (LWP 9098)):
[KCrash Handler]
#6  0x7efe119886a4 in KNotification::flags() const () at
/usr/lib64/libKF5Notifications.so.5
#7  0x7efe119a5dd7 in  () at /usr/lib64/libKF5Notifications.so.5
#8  0x7efe119ab525 in  () at /usr/lib64/libKF5Notifications.so.5
#9  0x7efe0c77dcc6 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7efe0e023e75 in  () at /usr/lib64/libphonon4qt5.so.4
#11 0x7efe0c77eac6 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#12 0x7efe0d8c4e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#13 0x7efe0d8c9cc8 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Widgets.so.5
#14 0x7efe0c74de95 in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#15 0x7efe0c750057 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#16 0x7efe0c7a58f3 in  () at /usr/lib64/libQt5Core.so.5
#17 0x7efe0749ac84 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#18 0x7efe0749aed8 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x7efe0749af7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#20 0x7efe0c7a4d6c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#21 0x7efe0c74bd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#22 0x7efe0c7538f6 in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#23 0x7efe1278e427 in kdemain () at /usr/lib64/libkdeinit5_dolphin.so
#24 0x7efe123a7b25 in __libc_start_main () at /lib64/libc.so.6
#25 0x004007ee in _start ()

Reported using DrKonqi

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

[kontact] [Bug 375587] New: crashes on reboot

2017-01-26 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=375587

Bug ID: 375587
   Summary: crashes on reboot
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
restart (zypper + reboot)
- Custom settings of the application:
All folder simlinked to a separate disk.
Many account, many profile, many-many filter that most no longer works for
ages, neither did the spam filter

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 0x7f93aad6d7c0 (LWP 4713))]

Thread 24 (Thread 0x7f92f05e9700 (LWP 4754)):
#0  0x7f93a79abbfd in poll () at /lib64/libc.so.6
#1  0x7f93a050ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f93a050cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f93a84efd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f93a8496d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f93a82b861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f93a82bd32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f93a0d2a0a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f93a79b402d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f92f0dea700 (LWP 4752)):
#0  0x7ffcad595b26 in clock_gettime ()
#1  0x7f93a79c0c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f93a836e7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f93a84ee3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f93a84ee945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f93a84efb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f93a050c4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f93a050cd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f93a050cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f93a84efd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f93a8496d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f93a82b861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f93a82bd32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f93a0d2a0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f93a79b402d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f92f1ffb700 (LWP 4750)):
#0  0x7f93a054ecf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f93a050c387 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f93a050cd80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f93a050cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f93a84efd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f93a8496d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f93a82b861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f93a82bd32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f93a0d2a0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f93a79b402d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f92f27fc700 (LWP 4748)):
#0  0x7ffcad595b26 in clock_gettime ()
#1  0x7f93a79c0c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f93a836e7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f93a84ee3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f93a84ee945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f93a84efb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f93a050c4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f93a050cd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f93a050cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f93a84efd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f93a8496d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f93a82b861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f93a82bd32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f93a0d2a0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f93a79b402d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f92f2ffd700 (LWP 4746)):
#0  0x7ffcad595b26 in clock_gettime ()
#1  0x7f93a79c0c7d i

[kontact] [Bug 375511] New: Crashes on reboot

2017-01-24 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=375511

Bug ID: 375511
   Summary: Crashes on reboot
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
zypper patch + zypper up + reboot 
- Custom settings of the application:
all folder are simlinked to an external partition
Many profile, many account, many-many filters.
Most filters no longer work and spam filter never did

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 0x7f62bc9077c0 (LWP 1900))]

Thread 22 (Thread 0x7f62057fa700 (LWP 2420)):
#0  0x7f62b9e4fccf in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5
#1  0x7f62ba089cc5 in  () at /usr/lib64/libQt5Core.so.5
#2  0x7f62b20a64ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f62b20a6d80 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f62b20a6f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f62ba089d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f62ba030d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f62b9e5261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f62b9e5732f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f62b28c40a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f62b954e02d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f62067fc700 (LWP 2417)):
#0  0x7fff8aeafb26 in clock_gettime ()
#1  0x7f62b955ac7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f62b9f087d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f62ba0883b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f62ba088945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f62ba089b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f62b20a64ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f62b20a6d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f62b20a6f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f62ba089d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f62ba030d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f62b9e5261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f62b9e5732f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f62b28c40a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f62b954e02d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f6206ffd700 (LWP 2415)):
#0  0x7fff8aeafb26 in clock_gettime ()
#1  0x7f62b955ac7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f62b9f087d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f62ba0883b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f62ba088945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f62ba089b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f62b20a64ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f62b20a6d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f62b20a6f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f62ba089d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f62ba030d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f62b9e5261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f62b9e5732f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f62b28c40a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f62b954e02d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f62077fe700 (LWP 2411)):
#0  0x7f62b955a5ff in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7f62b9541cc2 in read () at /lib64/libc.so.6
#2  0x7f62b20e7b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f62b20a6999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f62b20a6df8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f62b20a6f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#6  0x7f62ba089d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#7  0x7f62ba030d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f62b9e5261a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x0

[kontact] [Bug 375259] New: crashes on any new action

2017-01-18 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=375259

Bug ID: 375259
   Summary: crashes on any new action
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
entering a new agenda entry
- Custom settings of the application:
all Akonady and Kontact folders are simlinked to a safer partition on a
separate disk, many account, many profile, many-many filters

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2c9738a7c0 (LWP 10683))]

Thread 33 (Thread 0x7f2bc4a3a700 (LWP 22785)):
#0  0x7f2c8cb29f8d in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f2c94b0cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#2  0x7f2c94ab3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#3  0x7f2c948d561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#4  0x7f2c948da32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f2c8d3470a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f2c93fd102d in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f2bd464c700 (LWP 22732)):
#0  0x7f2c93fc4ccd in read () at /lib64/libc.so.6
#1  0x7f2c8cb6ab60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f2c8cb2 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f2c8cb29df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f2c8cb29f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f2c94b0cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f2c94ab3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f2c948d561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f2c948da32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f2c8d3470a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f2c93fd102d in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f2bd4e4d700 (LWP 22730)):
#0  0x7ffd99501b26 in clock_gettime ()
#1  0x7f2c93fddc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f2c9498b7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f2c94b0b3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f2c94b0b945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2c94b0cb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f2c8cb294ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f2c8cb29d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f2c8cb29f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f2c94b0cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f2c94ab3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f2c948d561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f2c948da32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f2c8d3470a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f2c93fd102d in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7f2bd705d700 (LWP 22728)):
#0  0x7ffd99501b26 in clock_gettime ()
#1  0x7f2c93fddc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f2c9498b7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f2c94b0b3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f2c94b0b945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2c94b0cb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f2c8cb294ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f2c8cb29d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f2c8cb29f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f2c94b0cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f2c94ab3d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f2c948d561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f2c948da32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f2c8d3470a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f2c93fd102d in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f2bd685c700 (LWP 22678)):
#0  0x7ffd99501b26 in clock_gettime ()
#1  0x7f2c93fddc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f2c9498b7d6 in 

[kontact] [Bug 375018] New: Crashes on reboot

2017-01-13 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=375018

Bug ID: 375018
   Summary: Crashes on reboot
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Moved emails from inbox to folders as the filters doesn't do it anymore
- Custom settings of the application:
Many identity, many profile, many-many filters, and all akonady/kontact folders
symlinked to a different partition (for crash-proof and space management)

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 0x7f9b4d60c7c0 (LWP 4879))]

Thread 24 (Thread 0x7f9a96dee700 (LWP 4919)):
#0  0x7ffc28ffbb26 in clock_gettime ()
#1  0x7f9b4a25fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f9b4ac0d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f9b4ad8d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9b4ad8d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9b4ad8eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f9b42dab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f9b42dabd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f9b42dabf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f9b4ad8ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f9b4ad35d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f9b4ab5761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f9b4ab5c32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f9b435c90a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f9b4a25302d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f9a975ef700 (LWP 4917)):
#0  0x7ffc28ffbb26 in clock_gettime ()
#1  0x7f9b4a25fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f9b4ac0d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f9b4ad8d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9b4ad8d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9b4ad8eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f9b42dab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f9b42dabd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f9b42dabf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f9b4ad8ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f9b4ad35d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f9b4ab5761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f9b4ab5c32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f9b435c90a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f9b4a25302d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7f9aa0df0700 (LWP 4915)):
#0  0x7f9b4a24abe9 in poll () at /lib64/libc.so.6
#1  0x7f9b42dabe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f9b42dabf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f9b4ad8ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f9b4ad35d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9b4ab5761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f9b4ab5c32f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f9b435c90a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f9b4a25302d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f9aa15f1700 (LWP 4913)):
#0  0x7ffc28ffbb26 in clock_gettime ()
#1  0x7f9b4a25fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f9b4ac0d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f9b4ad8d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9b4ad8d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9b4ad8eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f9b42dab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f9b42dabd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f9b42dabf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f9b4ad8ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f9b4ad35d53 in
QEventLoop::exec(QFlags) () at
/usr/

[kontact] [Bug 374644] New: Crashes while changing settings

2017-01-06 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=374644

Bug ID: 374644
   Summary: Crashes while changing settings
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Changing defalt send-email folder adress
- Custom settings of the application:
many accounts, many identity and aliases, many-many filters, and all main
Kontact/Akonady folders are simlinked to a (safe) different partition on a
different hard 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 0x7f9229da87c0 (LWP 14135))]

Thread 27 (Thread 0x7f90ec9b3700 (LWP 14214)):
#0  0x7ffeee977b26 in clock_gettime ()
#1  0x7f92269fbc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f92273a97d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f92275293b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9227529945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f922752ab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f921f5474ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f921f547d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f921f547f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f922752ad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f92274d1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f92272f361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f92272f832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f921fd650a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f92269ef02d in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f916d93b700 (LWP 14213)):
#0  0x7f921fd6903f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f921401b86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f921401b899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f921fd650a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f92269ef02d in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f916e491700 (LWP 14210)):
#0  0x7f92269e6bfd in poll () at /lib64/libc.so.6
#1  0x7f921f547e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f921f547f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f922752ad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f92274d1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f92272f361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f92272f832f in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f921fd650a4 in start_thread () at /lib64/libpthread.so.0
#8  0x7f92269ef02d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f916f7fe700 (LWP 14175)):
#0  0x7ffeee977b26 in clock_gettime ()
#1  0x7f92269fbc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f92273a97d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f92275293b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9227529945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f922752ab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f921f5474ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f921f547d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f921f547f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f922752ad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f92274d1d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f92272f361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f92272f832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f921fd650a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f92269ef02d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f916700 (LWP 14173)):
#0  0x7ffeee977b26 in clock_gettime ()
#1  0x7f92269fbc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f92273a97d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f92275293b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9227529945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f922752ab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x000

[kontact] [Bug 374643] New: Crashes while changing defalut settings

2017-01-06 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=374643

Bug ID: 374643
   Summary: Crashes while changing defalut settings
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Changing the "sent email" box address for one of my accounts
- Custom settings of the application:
Many accounts, many identity, many-many 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 0x7f648bcc97c0 (LWP 13967))]

Thread 27 (Thread 0x7f634e836700 (LWP 14102)):
#0  0x7ffec0afbb26 in clock_gettime ()
#1  0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f64892ca7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f648944bb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f64814684ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f6481468d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f6481468f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f648944bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f64893f2d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f648921932f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f648891002d in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f63cf7be700 (LWP 14101)):
#0  0x7f6481c8a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f6475f3c86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f6475f3c899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f648891002d in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f63d4dea700 (LWP 14081)):
#0  0x7ffec0afbb26 in clock_gettime ()
#1  0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f64892ca7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f648944bb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f64814684ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f6481468d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f6481468f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f648944bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f64893f2d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f648921932f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f648891002d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f63d55eb700 (LWP 14047)):
#0  0x7f6488903ccd in read () at /lib64/libc.so.6
#1  0x7f64814a9b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f6481468999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f6481468df8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f6481468f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f648944bd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f64893f2d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f648921461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f648921932f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f6481c860a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f648891002d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f63d5dec700 (LWP 14046)):
#0  0x7ffec0afbb26 in clock_gettime ()
#1  0x7f648891cc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f64892ca7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f648944a3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f648944a945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f648944bb5

[kontact] [Bug 374642] New: Crashes while changing account settings

2017-01-06 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=374642

Bug ID: 374642
   Summary: Crashes while changing account settings
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was changing the trashbox settings and the expiring settings for one of my
accounts
- Custom settings of the application:
many accounts, many identity, many-many 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 0x7fea0ae807c0 (LWP 2637))]

Thread 26 (Thread 0x7fe94d659700 (LWP 13897)):
#0  0x7fea00e4103f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fe9f50f386b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fe9f50f3899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fea07ac702d in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7fe94ce58700 (LWP 3502)):
#0  0x7ffcfe7e5b26 in clock_gettime ()
#1  0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fea084817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fea08602b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fea0061f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fea0061fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fea0061ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fea08602d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fea085a9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fea083d032f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fea07ac702d in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7fe94fde8700 (LWP 2705)):
#0  0x7ffcfe7e5b26 in clock_gettime ()
#1  0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fea084817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fea08602b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fea0061f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fea0061fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fea0061ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fea08602d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fea085a9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fea083d032f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fea07ac702d in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7fe9505e9700 (LWP 2678)):
#0  0x7fea07abaccd in read () at /lib64/libc.so.6
#1  0x7fea00660b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fea0061f999 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fea0061fdf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fea0061ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7fea08602d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7fea085a9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7fea083cb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7fea083d032f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fea00e3d0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fea07ac702d in clone () at /lib64/libc.so.6

Thread 22 (Thread 0x7fe950dea700 (LWP 2676)):
#0  0x7ffcfe7e5b26 in clock_gettime ()
#1  0x7fea07ad3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fea084817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fea086013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fea08601945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#

[kontact] [Bug 374471] New: Reboot crash everytime

2017-01-02 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=374471

Bug ID: 374471
   Summary: Reboot crash everytime
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-44-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
zypper patch + zypper up + reboot
- Custom settings of the application:
Simlinks to a different partition, many profiles, many many filters (most
filters stoped working a while ago, and spam filter never worked)

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 0x7f7d948587c0 (LWP 3548))]

Thread 22 (Thread 0x7f7ce57fa700 (LWP 4050)):
#0  0x7ffde4139b26 in clock_gettime ()
#1  0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f7d91e597d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d91fdab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d89ff74ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f7d89ff7d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f7d89ff7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f7d91fdad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f7d91f81d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f7d91da832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f7d9149f02d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f7ce67fc700 (LWP 4043)):
#0  0x7ffde4139b26 in clock_gettime ()
#1  0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f7d91e597d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d91fdab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d89ff74ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f7d89ff7d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f7d89ff7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f7d91fdad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f7d91f81d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f7d91da832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f7d9149f02d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f7ce6ffd700 (LWP 4041)):
#0  0x7ffde4139b26 in clock_gettime ()
#1  0x7f7d914abc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f7d91e597d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f7d91fd93b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f7d91fd9945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d91fdab5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d89ff74ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f7d89ff7d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f7d89ff7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f7d91fdad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f7d91f81d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f7d91da361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f7d91da832f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f7d8a8150a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f7d9149f02d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f7ce77fe700 (LWP 4033)):
#0  0x7f7d8a039d10 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f7d89ff78e9 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f7d89ff7df8 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7d89ff7f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7d91fdad8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x0

[kontact] [Bug 373772] New: Crash after upload

2016-12-17 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=373772

Bug ID: 373772
   Summary: Crash after upload
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-41-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
reboot after zypper patch + zypper up

- Custom settings of the application:
Many profiles, many email account, many many 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 0x7f97756807c0 (LWP 3627))]

Thread 22 (Thread 0x7f96ba7fc700 (LWP 4157)):
#0  0x7ffd3c9bbb26 in clock_gettime ()
#1  0x7f97722d3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f9772c817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f9772e013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9772e01945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9772e02b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f976ae1f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f976ae1fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f976ae1ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f9772e02d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f9772da9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f9772bcb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f9772bd032f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f976b63d0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f97722c702d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f96bb7fe700 (LWP 4155)):
#0  0x7ffd3c9bbb26 in clock_gettime ()
#1  0x7f97722d3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f9772c817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f9772e013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9772e01945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9772e02b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f976ae1f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f976ae1fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f976ae1ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f9772e02d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f9772da9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f9772bcb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f9772bd032f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f976b63d0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f97722c702d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f96bbfff700 (LWP 4153)):
#0  0x7ffd3c9bbb26 in clock_gettime ()
#1  0x7f97722d3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f9772c817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f9772e013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9772e01945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9772e02b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f976ae1f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f976ae1fd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f976ae1ff7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f9772e02d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f9772da9d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f9772bcb61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f9772bd032f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f976b63d0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f97722c702d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f96d4ff9700 (LWP 4149)):
#0  0x7ffd3c9bbb26 in clock_gettime ()
#1  0x7f97722d3c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f9772c817d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f9772e013b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f9772e01945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f9772e02b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f976ae1f4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.

[kontact] [Bug 373516] New: Crash on start

2016-12-10 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=373516

Bug ID: 373516
   Summary: Crash on start
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.36-38-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Restarted the computer after update (zypper patch + zypper up + reboot)
- Custom settings of the application:
Many accounts, many profile, many-many 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 0x7ff14715d7c0 (LWP 3476))]

Thread 22 (Thread 0x7ff08bfff700 (LWP 3974)):
#0  0x7fff3ec94b26 in clock_gettime ()
#1  0x7ff143db0c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7ff14475e7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7ff1448de3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7ff1448de945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff1448dfb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7ff13c8fc4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7ff13c8fcd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7ff13c8fcf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7ff1448dfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7ff144886d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7ff1446a861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7ff1446ad32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7ff13d11a0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7ff143da402d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7ff0997fa700 (LWP 3971)):
#0  0x7ff1448dfd8d in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#1  0x7ff144886d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#2  0x7ff1446a861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#3  0x7ff1446ad32f in  () at /usr/lib64/libQt5Core.so.5
#4  0x7ff13d11a0a4 in start_thread () at /lib64/libpthread.so.0
#5  0x7ff143da402d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7ff099ffb700 (LWP 3970)):
#0  0x7ff143db05ff in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7ff143d9bbf2 in poll () at /lib64/libc.so.6
#2  0x7ff13c8fce64 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7ff13c8fcf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7ff1448dfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7ff144886d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7ff1446a861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7ff1446ad32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7ff13d11a0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7ff143da402d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7ff09a7fc700 (LWP 3966)):
#0  0x7fff3ec94b26 in clock_gettime ()
#1  0x7ff143db0c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7ff14475e7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7ff1448de3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7ff1448de945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7ff1448dfb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7ff13c8fc4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7ff13c8fcd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7ff13c8fcf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7ff1448dfd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7ff144886d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7ff1446a861a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7ff1446ad32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7ff13d11a0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7ff143da402d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7ff09affd700 (LWP 3965)):
#0  0x7fff3ec94b26 in clock_gettime ()
#1  0x7ff143db0c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7ff14475e7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7ff1448de3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7ff1448de945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so

[neon] [Bug 373138] kmail complains about missing libgpgme-pthread.so.11

2016-12-05 Thread Eric BURGHARD
https://bugs.kde.org/show_bug.cgi?id=373138

Eric BURGHARD  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Eric BURGHARD  ---
I confirmed this is resolved from today update (dev/stable).

Thanks a lot guys. You definitively rock !

I don't understand those criticism towards kontact. I was just annoyed the
whole week by the ergonomy and search functionality of thunderbird.

Thanks a lot for the time you are dedicating making kde always better.

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

[kontact] [Bug 373324] New: crashes at opening

2016-12-05 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=373324

Bug ID: 373324
   Summary: crashes at opening
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Restart the computer after last update (zypper patch + zypper up + reboot)

- Custom settings of the application:
Many email account, many profile and aliases, many-many filters

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 0x7fad243a27c0 (LWP 1919))]

Thread 22 (Thread 0x7fac6d7fa700 (LWP 2423)):
#0  0x7fad19b83cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fad19b414b9 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fad19b41d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fad19b41f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fad21b24d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fad21acbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fad218f232f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fad20fe902d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7fac6e7fc700 (LWP 2421)):
#0  0x7fffb5de8b26 in clock_gettime ()
#1  0x7fad20ff5c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fad219a37d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fad21b233b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fad21b23945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fad21b24b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fad19b414ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fad19b41d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fad19b41f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fad21b24d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fad21acbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fad218f232f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fad20fe902d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7fac6effd700 (LWP 2420)):
#0  0x7fad19b83d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7fad19b41759 in g_main_context_query () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fad19b41dcf in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fad19b41f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fad21b24d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fad21acbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fad218f232f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fad20fe902d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7fac6f7fe700 (LWP 2414)):
#0  0x7fffb5de8b26 in clock_gettime ()
#1  0x7fad20ff5c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fad219a37d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fad21b233b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fad21b23945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fad21b24b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fad19b414ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fad19b41d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fad19b41f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fad21b24d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fad21acbd53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fad218ed61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fad218f232f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fad1a35f0a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fad20fe902d in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7fac6700 (LWP 2413)):
#

[kmahjongg] [Bug 373245] New: kmahjongg starts new game or demo without warning

2016-12-04 Thread Eric Forgeot
https://bugs.kde.org/show_bug.cgi?id=373245

Bug ID: 373245
   Summary: kmahjongg starts new game or demo without warning
   Product: kmahjongg
   Version: 0.8
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: eforg...@yahoo.fr
CC: kde-games-b...@kde.org
  Target Milestone: ---

If during the play we click on "new" or type "d" (instead of "f", for turning
the board), the kmahjongg will start a new game or demo without warning, it
means loosing the current play. Especially the "d" key is close to the "f" one,
which means possible mistake and game restart without notice.

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

[kontact] [Bug 373230] New: overloaded with options

2016-12-03 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=373230

Bug ID: 373230
   Summary: overloaded with options
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Starting the program

- Custom settings of the application:
Many-many firlters, for about 10 email account (12 profiles + xxx alias in 8
email account)

Filters doesn't work anymore, and I gave up even trying to set it up
again-again-agian
Spam filter never worked, I gave up trying
Sorting and labelling email never worked, I gave up

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 0x7f5d3b8557c0 (LWP 1887))]

Thread 22 (Thread 0x7f5c857fa700 (LWP 2398)):
#0  0x7f5d31036d14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f5d30ff4538 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f5d30ff4d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f5d30ff4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f5d38fd7d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f5d38f7ed53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f5d38da061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f5d38da532f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f5d318120a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f5d3849c02d in clone () at /lib64/libc.so.6

Thread 21 (Thread 0x7f5c867fc700 (LWP 2395)):
#0  0x7ffd3455eb26 in clock_gettime ()
#1  0x7f5d384a8c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f5d38e567d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5d38fd63b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f5d38fd6945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5d38fd7b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f5d30ff44ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f5d30ff4d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f5d30ff4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f5d38fd7d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f5d38f7ed53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f5d38da061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f5d38da532f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f5d318120a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f5d3849c02d in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f5c86ffd700 (LWP 2394)):
#0  0x7ffd3455eb26 in clock_gettime ()
#1  0x7f5d384a8c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f5d38e567d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5d38fd63b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f5d38fd6945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5d38fd7b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f5d30ff44ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f5d30ff4d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f5d30ff4f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f5d38fd7d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f5d38f7ed53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7f5d38da061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7f5d38da532f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7f5d318120a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7f5d3849c02d in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f5c877fe700 (LWP 2390)):
#0  0x7ffd3455eb26 in clock_gettime ()
#1  0x7f5d384a8c7d in clock_gettime () at /lib64/libc.so.6
#2  0x7f5d38e567d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f5d38fd63b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f5d38fd6945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f5d38fd7b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f5d30ff44ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f5d30ff4d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7f5d30ff4f7c in g_main_context_iteration () at
/usr/lib64/li

[neon] [Bug 373138] New: kmail complains about missing libgpgme-pthread.so.11

2016-12-01 Thread Eric BURGHARD
https://bugs.kde.org/show_bug.cgi?id=373138

Bug ID: 373138
   Summary: kmail complains about missing libgpgme-pthread.so.11
   Product: neon
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Packages Dev Edition [stable]
  Assignee: neon-b...@kde.org
  Reporter: eburg...@free.fr
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

libgpgme11-1.8.0-neon0+16.04+build4 is installed and does not contains
libgpgme-pthread.so.11

kmail version is 4:16.08.2+p16.04+git20161118.0531-0

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

[frameworks-baloo] [Bug 358548] baloo_file_extractor high CPU and memory usage

2016-11-29 Thread Eric Forgeot
https://bugs.kde.org/show_bug.cgi?id=358548

Eric Forgeot  changed:

   What|Removed |Added

 CC||eforg...@yahoo.fr

--- Comment #11 from Eric Forgeot  ---
I've upgraded my Linuxmint 17.3 to linuxmint 18, installed the new KDE plasme
(based on qt5) and cleaned my previous KDE settings. 

KDE5 looks so great, but it is very unresponsive because of baloo which eat
most of the CPU. It took up to 10 seconds to open a new window in konsole for
example. At first I've removed the file search for my home folder, and it
seemed to be ok. I've waited a couple of days then rebooted the computer. Then
baloo started to eat most of the CPU and it lasted for most than 30 minutes but
it was so annoying because I couldn't use the computer (15 seconds for a new
tab on firefox)

Then I've completely disabled the file search in ~/.config/baloofilerc and now
everything is very responsive and fine.

(my computer is quite powerful, quadcore with 8 GB ram and ssd hard drive)


Baloo should just NOT be enabled by default on KDE.

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

[kscreenlocker] [Bug 370422] kscreenlocker crashes when unlocking the session after resume from s2ram

2016-11-24 Thread Eric Hameleers
https://bugs.kde.org/show_bug.cgi?id=370422

Eric Hameleers  changed:

   What|Removed |Added

 CC||al...@slackware.com

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

[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

2016-11-11 Thread Eric Chamberland
https://bugs.kde.org/show_bug.cgi?id=356457

--- Comment #26 from Eric Chamberland  ---
(In reply to Eric Chamberland from comment #25)
> FWIW, the svn version of valgrind didn't produced any blockSane assertion
> last night, but since it was randomly happening, we have to let go some days
> to see if this bug is definitely not occurring again.
> 
> Thanks,
> 
> Eric

Everything is fine since 21 days now.  I think this can be "closed".

Eric

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

[kontact] [Bug 372319] New: Move an email to an event

2016-11-10 Thread Eric
https://bugs.kde.org/show_bug.cgi?id=372319

Bug ID: 372319
   Summary: Move an email to an event
   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
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.5.1
Operating System: Linux 4.1.34-33-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Creating an event in my calendar based on an email I just received
- Custom settings of the application:
Many email accounts

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd14fc0c7c0 (LWP 3145))]

Thread 30 (Thread 0x7fd076791700 (LWP 12733)):
#0  0x7fff6aecdb26 in clock_gettime ()
#1  0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd14d20d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd14d38eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd1453ab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fd1453abd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fd1453abf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fd14d38ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fd14d335d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fd14d15c32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fd14c85302d in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7fd08b7fe700 (LWP 11234)):
#0  0x7fff6aecdb26 in clock_gettime ()
#1  0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd14d20d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd14d38eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd1453ab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fd1453abd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fd1453abf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fd14d38ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fd14d335d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fd14d15c32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fd14c85302d in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7fd08bfff700 (LWP 11229)):
#0  0x7fff6aecdb26 in clock_gettime ()
#1  0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd14d20d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd14d38eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd1453ab4ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7fd1453abd80 in  () at /usr/lib64/libglib-2.0.so.0
#8  0x7fd1453abf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#9  0x7fd14d38ed8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7fd14d335d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#11 0x7fd14d15761a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x7fd14d15c32f in  () at /usr/lib64/libQt5Core.so.5
#13 0x7fd145bc90a4 in start_thread () at /lib64/libpthread.so.0
#14 0x7fd14c85302d in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7fd091687700 (LWP 11227)):
#0  0x7fff6aecdb26 in clock_gettime ()
#1  0x7fd14c85fc7d in clock_gettime () at /lib64/libc.so.6
#2  0x7fd14d20d7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7fd14d38d3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7fd14d38d945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fd14d38eb5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7fd1453ab4ad in g_main_context_prepare () at
/usr/lib64

[kdenlive] [Bug 371630] Kdenlive Causes Full System Lockup

2016-10-25 Thread Eric Mesa
https://bugs.kde.org/show_bug.cgi?id=371630

--- Comment #7 from Eric Mesa  ---
Can't actually do that as Fedora's mlt package apparently doesn't have melt.

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

[kdenlive] [Bug 371630] Kdenlive Causes Full System Lockup

2016-10-25 Thread Eric Mesa
https://bugs.kde.org/show_bug.cgi?id=371630

--- Comment #6 from Eric Mesa  ---
Worked on a new file today and it once again locked up the system. I'm going to
try running melt on its own to see if that works. If you have any other
suggestions, let me know.

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

[kdenlive] [Bug 371630] Kdenlive Causes Full System Lockup

2016-10-24 Thread Eric Mesa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371630

--- Comment #5 from Eric Mesa  ---
Created attachment 101761
  --> https://bugs.kde.org/attachment.cgi?id=101761&action=edit
This file worked OK

This file worked fine. Rendered OK - did not hang the comptuer. It's not
exactly the same as I couldn't make it the same, I also simplified the opening
by pre-rendering it, but I'm attaching the file in case looking at this one and
the other helps you see what was causing the hang.

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


[kdenlive] [Bug 371630] Kdenlive Causes Full System Lockup

2016-10-24 Thread Eric Mesa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371630

--- Comment #4 from Eric Mesa  ---
One more thing before this gets too spammy (if it's not already there) - I was
able to render a 47 second file from the Canon Rebel T6s without any effects on
it - without a hard crash. 

So to recap:
1) Doesn't appear to simply be the video file
2) Even in the Kdenlive Alpha Appimage - with the same kdenlive file it hard
crashes.

Right now it seems to my mind (someone who's technical, but not when it comes
to coding a non-linear video editor) that the most likely culprit seems to be
the kdenlive file.

I'm going to attempt to recreate it as best as I can (obviously, I won't be
able to get the cut points exact) and see if that fixes the issue.

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


[kdenlive] [Bug 371630] Kdenlive Causes Full System Lockup

2016-10-24 Thread Eric Mesa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371630

--- Comment #3 from Eric Mesa  ---
Created attachment 101759
  --> https://bugs.kde.org/attachment.cgi?id=101759&action=edit
The file that keeps dead-locking the system

On the off chance that you can discover something by seeing the kdenlive file,
here it is.

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


[kdenlive] [Bug 371630] Kdenlive Causes Full System Lockup

2016-10-24 Thread Eric Mesa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371630

Eric Mesa  changed:

   What|Removed |Added

Version|16.08.1 |16.08.2

--- Comment #2 from Eric Mesa  ---
I don't know what this tells you, but I ran the new alpha App Image you guys
posted today and had the same issue - crash on a render. So I bumped up the
version number. 

On the theory that it's maybe a corrupt kdenlive file or something like that -
basically, I had a template already set up with the way I wanted things, but it
was from the older version of kdenlive. Also, an asset had been deleted and I
was using a placeholder asset. So maybe something's borked on there? So I'm
going to try rendering one of the Canon Rebel T6s files from the same hard
drive in a brand new kdenlive file and see what happens.

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


[kdenlive] [Bug 371630] Kdenlive Causes Full System Lockup

2016-10-24 Thread Eric Mesa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371630

--- Comment #1 from Eric Mesa  ---
Some extra comments I was thinking of:

1) Might not be the hard drive that has those clips, maybe it's because they're
clips that came from a Canon Rebel T6s. I've been able to use it in the past
without issue, but perhaps something in one of the dependencies for Kdenlive
has changed. 

2) Just experienced the lockup on Rendering twice - same file.

3) I'm using Nvidia proprietary drivers - latest RPMFusion RPMs

4) Info on one of the video files based on VLC:
Video codec: H264 part 10 avc1
Frame rate: 29.9
1920x1080 resolution

5) I had to switch to the gstreamer backend instead of VLC backend in KDE and
the video file doesn't play. But I think based on when I had top running that
Kdenlive calls ffmpeg

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


[kdenlive] [Bug 371630] New: Kdenlive Causes Full System Lockup

2016-10-24 Thread Eric Mesa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371630

Bug ID: 371630
   Summary: Kdenlive Causes Full System Lockup
   Product: kdenlive
   Version: 16.08.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Video Display & Export
  Assignee: j...@kdenlive.org
  Reporter: ericsbinarywo...@gmail.com

Fedora 24
KDE 5.26
QT 5.6.1
MLT 6.2.0
AMD 8 Core
24GB RAM

Recently started having an issue with Kdenlive. As far as I can tell it's only
involving raw footage on a particular hard drive (although that could be a red
herring). I had top running the other day after dealing with this issue and
trying to debug it. CPU usage that top said was due to Kdenlive went past 100%
and then it locked up.

I can't control-alt-F# to any other terminal. I can't activate num lock or caps
lock. The mouse doesn't move. The screen doesn't update. The fan on the CPU
remains full speed. I waited 10 minutes - it did not unlock itself.


I don't know if this is relevant, but I have the following in the terminal when
I run kdenlive:
$ kdenlive
QXcbConnection: XCB error: 8 (BadMatch), sequence: 14744, resource id:
136315231, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 14767, resource id:
136315231, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 26607, resource id:
136315231, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 26630, resource id:
136315231, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 28354, resource id:
136315231, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 28377, resource id:
136315231, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 28402, resource id:
136315231, major code: 130 (Unknown), minor code: 3
QXcbConnection: XCB error: 8 (BadMatch), sequence: 28429, resource id:
136315231, major code: 130 (Unknown), minor code: 3


Reproducible: Always

Steps to Reproduce:
1. Load up video
2. Scrub through video or sometimes while creating the audio preview
3. Entire system locks up

Actual Results:  
Entire system locks up

Expected Results:  
System not to lock up

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


[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

2016-10-21 Thread Eric Chamberland via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356457

--- Comment #25 from Eric Chamberland  ---
FWIW, the svn version of valgrind didn't produced any blockSane assertion last
night, but since it was randomly happening, we have to let go some days to see
if this bug is definitely not occurring again.

Thanks,

Eric

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


[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

2016-10-20 Thread Eric Chamberland via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356457

--- Comment #24 from Eric Chamberland  ---
Created attachment 101660
  --> https://bugs.kde.org/attachment.cgi?id=101660&action=edit
valgrind launched with -v -v -v -d -d -d

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


[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

2016-10-20 Thread Eric Chamberland via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356457

--- Comment #23 from Eric Chamberland  ---
Thanks Joost for these informations: In fact, we will upgrade the os when
possible...

This morning, I have 4 (different) failing tests.

I launched 3.11.0 with -v -v -v -d -d -d, please see valgrind_with_vvvddd.txt.

I will extract the svn version and next night we will see if the error is still
there...

Thanks,
Eric

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


[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

2016-10-19 Thread Eric Chamberland via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356457

--- Comment #21 from Eric Chamberland  ---
Finally I got not 6 but 8 failing tests (wrote the report before they all
completed...)

I have 7 different libraries where valgrind hangs:

#1:
--17999-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit_valgrind/COMPILE_AUTO/GIREF/lib/libgiref_dev_ChampsUtil.so
blockSane: fail -- redzone-hi

#2:
--17515-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit_valgrind/COMPILE_AUTO/GIREF/lib/libgiref_dev_Contact.so
blockSane: fail -- redzone-hi

#3:
--26315-- Reading syms from
/usr/local/valgrind-3.11.0/lib64/valgrind/memcheck-amd64-linux
--26315--object doesn't have a dynamic symbol table
blockSane: fail -- redzone-hi


#4:
--21183-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit_valgrind/COMPILE_AUTO/GIREF/lib/libgiref_opt_Interface.so
blockSane: fail -- redzone-hi

#5:
--2349-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit_valgrind/COMPILE_AUTO/GIREF/lib/libgiref_opt_Adaptation.so
blockSane: fail -- redzone-hi

#6:
--2929-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit_valgrind/COMPILE_AUTO/GIREF/lib/libgiref_opt_Geometrie.so
blockSane: fail -- redzone-hi

#7:
--19038-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit_valgrind/COMPILE_AUTO/GIREF/lib/libgiref_dev_LecteurDeclaration.so
blockSane: fail -- redzone-hi

#8:
--31828-- Reading syms from
/pmi/cmpbib/compilation_BIB_gcc-4.5.1_64bit_valgrind/COMPILE_AUTO/GIREF/lib/libgiref_dev_LecteurDeclaration.so
blockSane: fail -- redzone-hi

I launched a test 165 minutes ago with the #define DEBUG_MALLOC (but not the
svn version) and it is not terminated... but has passed all the libraries
loading phase...  :/

Eric

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


[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

2016-10-19 Thread Eric Chamberland via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356457

--- Comment #18 from Eric Chamberland  ---
Some other informations:

Distribution:  openSUSE 12.3
Kernel: cat /proc/version
Linux version 3.7.10-1.45-desktop (geeko@buildhost) (gcc version 4.7.2 20130108
[gcc-4_7-branch revision 195012] (SUSE Linux) ) #1 SMP PREEMPT Tue Dec 16
20:27:58 UTC 2014 (4c885a1)

g++: g++ (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012]

when launching the 2200 tests, we run at most 12 at the same time.  ie, we
almost never run a test "alone"... so there is some concurrency for the
resources

I just tried relaunching a faulty test, but I am unable to reproduce.

Looking at /var/log/messages, I found just one entry like this:

2016-10-19T03:37:51.503636-04:00 melkor kernel: [1032084.013381] userif-3: sent
link up event.
2016-10-19T03:37:51.503655-04:00 melkor kernel: [2920320.962816]
memcheck-amd64-[26315]: segfault at 1c04 ip 38055b90 sp
39553ed8 error 4 in memcheck-amd64-linux[3800+21f000]

which corresponds to one of the 6 failling tests of last night.

Eric



Eric

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


[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

2016-10-19 Thread Eric Chamberland via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356457

--- Comment #17 from Eric Chamberland  ---
(copied from valgrind-users list following Julian Seward request)

Hi,

I recently upgraded to valgrind 3.11.0 (was 3.8.1 before).
I also upgraded Intel MKL to the 2015 version.

We use valgrind since 2011-10-27 to test our code nightly with about 2200
tests.

Since this upgrade, some tests (not always the same) have the same trouble (see
full log in attachment):


...
blockSane: fail -- redzone-hi

valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)'
failed.

host stacktrace:
...



I would like some help to debug this.

It is quite annoying since for the same test, the problem appear or disappear
from one day over another...

Today we got the problem on 6 tests (on 2200), yesterday, only 1 test failed,
before yesterday, none failed

Thanks for any insights or clues!

Eric

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


[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

2016-10-19 Thread Eric Chamberland via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356457

Eric Chamberland  changed:

   What|Removed |Added

 CC||eric.chamberl...@gmail.com

--- Comment #16 from Eric Chamberland  ---
Created attachment 101649
  --> https://bugs.kde.org/attachment.cgi?id=101649&action=edit
Valgrind output for a bugging test.

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


[filelight] [Bug 370932] File light scans into "do not scan" folders that end with a /

2016-10-15 Thread Eric S via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370932

Eric S  changed:

   What|Removed |Added

Summary|File light scans into "do   |File light scans into "do
   |not scan" folders   |not scan" folders that end
   ||with a /

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


[filelight] [Bug 370932] File light scans into "do not scan" folders

2016-10-15 Thread Eric S via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370932

--- Comment #1 from Eric S  ---
Actually I just discovered the problem. All the folders listed in my Do not
scan list ended with a /. E.g. /home/ericjs/stuff/. I tried deleting and
re-adding a folder, and it was added without a terminating /, like
"/home/ericjs/stuff". Rescanning resulted in this directory properly being
ignored. I'm pretty sure these folders had a terminating / because that is how
a previous version of Filelight created them (I certainly wouldn't have added
such a slash myself). So this would seem to be a backwards compatibility issue.

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


[filelight] [Bug 370932] New: File light scans into "do not scan" folders

2016-10-15 Thread Eric S via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370932

Bug ID: 370932
   Summary: File light scans into "do not scan" folders
   Product: filelight
   Version: 1.21
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: subscri...@blackbrook.org

Folders that I have listed in "Do not scan these folders:" in the configuration
show up in my scan. 

Reproducible: Always




I'm pretty sure this used to work. I can't tell you what version as I haven't
run it in a while.

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


[amarok] [Bug 369667] Playback on VLC Backend skips songs near the end; Gstreamer backend fails to find MP3 playback

2016-10-05 Thread Eric Mesa via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369667

--- Comment #4 from Eric Mesa  ---
For GStreamer, I was missing Ugly. I'd tried to solve it before making the bug
by trying a

dnf install gstreamer*, but there was a packaging change that made some
packages still in the repositories no longer valid because they were now
included in other packages. So Gstreamer backend is now working for me.

If you'd like to help with VLC, you can keep the ticket open while we figure
that out. If not, at least Gstreamer is now working and you may close the bug.

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


[krusader] [Bug 369844] "Detailed view" does not display files but "brief view" does

2016-10-04 Thread Eric McCrate via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369844

--- Comment #4 from Eric McCrate  ---
Thank you, and i am proud to be of assistance.
i love Linux, Krusader, and really great things forward. Reminds me of the
early days starting with my Apple II.
Microsoft really sucks these days  too many bugs in it

On Tue, Oct 4, 2016 at 7:12 PM, Alex Bikadorov via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=369844
>
> --- Comment #3 from Alex Bikadorov  ---
> Hahaha, oh wow. This is what happened: you removed every column in the
> detailed
> view and the header disappeared. Now this is the default setting and I
> myself
> found no way to get the header back.
>
> Quick workaround: Close Krusader and delete the config file
>
> /home//.kde4/share/config/krusaderrc
> (or similar)
>
> But this shouldn't be possible - we have to fix this. Thanks for reporting!
>
> >  Platform Version 4.14.16
> I meant the version of Krusader. But its not important anymore.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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


[krusader] [Bug 369844] "Detailed view" does not display files but "brief view" does

2016-10-04 Thread Eric McCrate via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369844

--- Comment #2 from Eric McCrate  ---
Hello,
Thank you for the response
version:

Platform Version 4.14.16

with "adjusting headings"  removed column headings in one panel and somehow
cloned the panel to second area, so ho heading area available in detailed
view, and then no files displayed.

can not reset to original after this.

change to brief view and files are displayed.

this happened once but detailed view is no longer able to display any
files., even after leaving program, and reloading.

screen below:

[image: Inline image 1]

On Tue, Oct 4, 2016 at 4:12 PM, Alex Bikadorov via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=369844
>
> Alex Bikadorov  changed:
>
>What|Removed |Added
> 
> 
>  CC||
> alex.bikado...@kdemail.net
>
> --- Comment #1 from Alex Bikadorov  ---
> > Actual Results: no files displayed
> No files at all? Always? Quite strange cause this is the default view.
>
> A bit of information is missing here, please be more specific:
> * which version are you referring to?
> * with "adjusting headings" you mean resizing a column?
> * this happens for every panel/every tab?
> * under each panel is an info bar for the selection ("x out of y"), is this
> number correct or changing?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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


[krusader] [Bug 369844] New: "Detailed view" does not display files but "brief view" does

2016-10-03 Thread Eric McCrate via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369844

Bug ID: 369844
   Summary: "Detailed view" does not display files but "brief
view" does
   Product: krusader
   Version: unspecified
  Platform: Mint (Debian based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: ericmccr...@gmail.com

"detailed view" lost file display after adjusting headings and can not be reset
to original settings.
 no files are displayed in this view. When switching to "brief view" all files
are displayed.
Also, Heading panel is not displayed in "Detailed View"

Reproducible: Always

Steps to Reproduce:
1. open Krusader
2. select menu "View"
3.Select "Detailed View"

Actual Results:  
no files displayed

Expected Results:  
files should display

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


[kontact] [Bug 369780] New: tweaking settings = crashes

2016-10-03 Thread Eric via KDE Bugzilla
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

<    5   6   7   8   9   10   11   12   >