[kmail2] [Bug 376981] kmail no longer displays mails

2021-05-13 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=376981

Christian Trippe  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #2 from Christian Trippe  ---
I did not have that probelm for quite some time now. Therefore closing the bug.

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

[kontact] [Bug 357139] Kontact crashed when choosing "configure completion" in kmail composer

2020-12-17 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=357139

Christian Trippe  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Christian Trippe  ---
I can no longer reproduce it

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

[gwenview] [Bug 417218] Crash when doing operations on pictures

2020-02-09 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=417218

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB

2020-01-11 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=389848

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[frameworks-baloo] [Bug 411706] Baloo File Indexing crashed after boot and login

2019-09-08 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=411706

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[Akonadi] [Bug 406623] New: akonadi maildir resource crash cannot be reported via DrKonqi

2019-04-17 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=406623

Bug ID: 406623
   Summary: akonadi maildir resource crash cannot be reported via
DrKonqi
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-b...@kde.org
  Reporter: christiande...@web.de
  Target Milestone: ---

SUMMARY
If the akondadi maildir resource crashes, DrKonqi is started. However you can
only get the backtrace but are not able to report the crash via DrKonqi.

STEPS TO REPRODUCE
1. Let akonadi maildir resource crash
2. DrKonqi starts
3. Button to report the bug is gray and the text above says "you cannot report
the bug as the application akonadi maildir resource has no address to report
the bug. (translated back from German)



SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.4
KDE Frameworks Version: 5.56
Qt Version: 5.12.2
Akonadi 19.03.80

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

[Akonadi] [Bug 406621] New: akonadi maildir resource sometimes crashes when changing folders

2019-04-17 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=406621

Bug ID: 406621
   Summary: akonadi maildir resource sometimes crashes when
changing folders
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-b...@kde.org
  Reporter: christiande...@web.de
  Target Milestone: ---

Sometimes the akonadi maildir resource crashes.  As far as I have observed it,
it only happens when I change to mail in another folder. However it does not
always happen and so far I was not able to find exact steps to reproduce it.
However it happens quite regularly for me.

This is using the th 19.03.80 version of KDE applications.

Backtrace is attached

Linux/KDE Plasma: 5.15.4
KDE Frameworks Version: 5.56
Qt Version: 5.12.2
Akonadi 19.03.80

ADDITIONAL INFORMATION

Application: akonadi_maildir_resource (akonadi_maildir_resource), signal:
Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb12be1f900 (LWP 17409))]

Thread 4 (Thread 0x7fb1132f0700 (LWP 17462)):
[KCrash Handler]
#6  0x7fb12880c0e0 in raise () from /lib64/libc.so.6
#7  0x7fb12880d6c1 in abort () from /lib64/libc.so.6
#8  0x7fb128e3be83 in ?? () from /usr/lib64/libstdc++.so.6
#9  0x7fb128e41dd8 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x7fb128e41e23 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x7fb1291c193b in qTerminate () at global/qglobal.cpp:3192
#12 0x7fb1291e596b in QThreadPrivate::start (arg=0x55e74a3d8c80) at
thread/qthread_unix.cpp:373
#13 0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0
#14 0x7fb1288ce81f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fb113af1700 (LWP 17459)):
#0  0x7fb1288c407b in poll () from /lib64/libc.so.6
#1  0x7fb1243ca129 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fb1243ca23c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fb12941b87b in QEventDispatcherGlib::processEvents
(this=0x55e74a3bc6a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7fb1293bcaaa in QEventLoop::exec (this=this@entry=0x7fb113af0c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7fb1291e403a in QThread::exec (this=) at
thread/qthread.cpp:531
#6  0x7fb12a103d55 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7fb1291e57e2 in QThreadPrivate::start (arg=0x7fb12a37bd80) at
thread/qthread_unix.cpp:361
#8  0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0
#9  0x7fb1288ce81f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fb118b94700 (LWP 17434)):
#0  0x7fb1288c407b in poll () from /lib64/libc.so.6
#1  0x7fb11f512387 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fb11f513fba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fb11b9897d8 in QXcbEventQueue::run (this=0x55e74a348300) at
qxcbeventqueue.cpp:228
#4  0x7fb1291e57e2 in QThreadPrivate::start (arg=0x55e74a348300) at
thread/qthread_unix.cpp:361
#5  0x7fb12620d569 in start_thread () from /lib64/libpthread.so.0
#6  0x7fb1288ce81f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fb12be1f900 (LWP 17409)):
#0  0x7fb126214c34 in pthread_getspecific () from /lib64/libpthread.so.0
#1  0x7fb1243f1dd0 in g_thread_self () from /usr/lib64/libglib-2.0.so.0
#2  0x7fb1243ca22d in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fb12941b87b in QEventDispatcherGlib::processEvents
(this=0x55e74a327e80, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7fb1293bcaaa in QEventLoop::exec (this=this@entry=0x7fffb7ae3e00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7fb1293c5cb0 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1363
#6  0x7fb12b366b4d in Akonadi::ResourceBase::init(Akonadi::ResourceBase*)
() from /usr/lib64/libKF5AkonadiAgentBase.so.5
#7  0x55e748e20271 in ?? ()
#8  0x7fb1287f6f4a in __libc_start_main () from /lib64/libc.so.6
#9  0x55e748e200fa in ?? ()
[Inferior 1 (process 17409) detached]

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

[kmahjongg] [Bug 377476] kmahjongg crashes during start

2019-03-28 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=377476

Christian Trippe  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Christian Trippe  ---
I also can no longer reproduced the issue with

kmahjongg-18.12.3 (Version 0.9)
KDE Frameworks 5.55.0
Qt 5.12.1 (kompiliert gegen 5.12.1)

-> Closing as FIXED

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

[kontact] [Bug 403359] Kontact crashes when closing email window

2019-01-20 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=403359

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[frameworks-baloo] [Bug 367480] Crash inside Baloo::PostingCodec::decode

2018-12-30 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=367480

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[dolphin] [Bug 401916] New: Dolphin crashed when copying files to a mobile phone which is connected via kde-connect

2018-12-08 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=401916

Bug ID: 401916
   Summary: Dolphin crashed when copying files to a mobile phone
which is connected via kde-connect
   Product: dolphin
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: christiande...@web.de
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (18.11.90)

Qt Version: 5.11.2
Frameworks Version: 5.52.0
Operating System: Linux 4.12.14-lp150.12.25-default x86_64
Distribution: "openSUSE Leap 15.0"

-- Information about the crash:
1.) I connected a mobile phone to my computer via kde-connect
2.) Choosed file-browsing
3.) Dolphin openend
4.) Made a split view in dolphin and opened the folder which a contained the
files I wanted to transfer to the mobile phone
5.) Started copying the files via drag & drop
6.) dolphin crashed

So far this only happend once.

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

Thread 4 (Thread 0x7f03bcb3c700 (LWP 2303)):
#0  0x7f03df1f3b68 in read () from /lib64/libc.so.6
#1  0x7f03d1b74a90 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f03d1b2fcb7 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f03d1b30170 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f03d1b302dc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f03d936e3cb in QEventDispatcherGlib::processEvents
(this=0x556104df03a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x7f03d931270a in QEventLoop::exec (this=this@entry=0x7f03bcb3bcb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#7  0x7f03d913daaa in QThread::exec (this=) at
thread/qthread.cpp:525
#8  0x7f03d91489cb in QThreadPrivate::start (arg=0x556104e22440) at
thread/qthread_unix.cpp:367
#9  0x7f03d41e8559 in start_thread () from /lib64/libpthread.so.0
#10 0x7f03df20281f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f03c5439700 (LWP 2302)):
#0  0x7f03df1f807b in poll () from /lib64/libc.so.6
#1  0x7f03d1b301c9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f03d1b302dc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f03d936e3cb in QEventDispatcherGlib::processEvents
(this=0x55610479b710, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f03d931270a in QEventLoop::exec (this=this@entry=0x7f03c5438c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f03d913daaa in QThread::exec (this=) at
thread/qthread.cpp:525
#6  0x7f03d97b7b75 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f03d91489cb in QThreadPrivate::start (arg=0x7f03d9a2fd60) at
thread/qthread_unix.cpp:367
#8  0x7f03d41e8559 in start_thread () from /lib64/libpthread.so.0
#9  0x7f03df20281f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f03c7cc0700 (LWP 2301)):
#0  0x7f03df1f807b in poll () from /lib64/libc.so.6
#1  0x7f03d0866387 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f03d0867fba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f03cac8fbd9 in QXcbEventReader::run (this=0x556104735fb0) at
qxcbconnection.cpp:1391
#4  0x7f03d91489cb in QThreadPrivate::start (arg=0x556104735fb0) at
thread/qthread_unix.cpp:367
#5  0x7f03d41e8559 in start_thread () from /lib64/libpthread.so.0
#6  0x7f03df20281f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f03df960900 (LWP 2300)):
[KCrash Handler]
#6  0x7f03dd909c06 in std::__atomic_base::operator--
(this=0x76400babababa89) at /usr/include/c++/7/bits/atomic_base.h:304
#7  QAtomicOps::deref (_q_value=...) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:271
#8  QBasicAtomicInteger::deref (this=0x76400babababa89) at
/usr/include/qt5/QtCore/qbasicatomic.h:115
#9  QSharedDataPointer::~QSharedDataPointer
(this=0x55610524f8d0, __in_chrg=) at
/usr/include/qt5/QtCore/qshareddata.h:89
#10 KFileItem::~KFileItem (this=0x55610524f8d0, __in_chrg=) at
/usr/src/debug/kio-5.52.0-lp150.234.1.x86_64/src/core/kfileitem.h:47
#11 0x7f03dd9c61b5 in QList::node_destruct (this=0x556105457930,
n=) at /usr/include/qt5/QtCore/qlist.h:452
#12 QList::erase (this=0x556105457930, it=...) at
/usr/include/qt5/QtCore/qlist.h:536
#13 0x7f03dd9c66ca in KCoreDirListerCache::reinsert
(this=this@entry=0x7f03ddc28280 <(anonymous
namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>, item=...,
oldUrl=...) at
/usr/src/debug/kio-5.52.0-lp150.234.1.x86_64/src/core/kcoredirlister_p.h:309
#14 0x7f03dd9bbbed in KCoreDirListerCache::processPendingUpdates
(this=this@entry=0x7f03ddc28280 <(anonymous

[konqueror] [Bug 236356] changing font size changes the displayed content

2018-11-06 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=236356

Christian Trippe  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Christian Trippe  ---
I can no longer reproduce it, alsow with khtml.

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

[kontact] [Bug 400494] Kontact crashes - clicking other news-feed URL in Akregator while internal webview is opened

2018-11-01 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=400494

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[kwebkitpart] [Bug 337774] konqueror crashed on build.opensuse.org

2018-11-01 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=337774

Christian Trippe  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #5 from Christian Trippe  ---
I can no longer reproduce the problem. Closing as FIXED

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

[kde] [Bug 395121] New: kcminit crashes during start of plasmashell

2018-06-07 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=395121

Bug ID: 395121
   Summary: kcminit crashes during start of plasmashell
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: christiande...@web.de
  Target Milestone: ---

Application: kdeinit5 ()

Qt Version: 5.11.0
Frameworks Version: 5.46.0
Operating System: Linux 4.4.132-53-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
After my last update of KDE Frameworks und Plasma Workspace kcminit crashes
every time during plasmashell start.

The crash can be reproduced every time.

-- Backtrace:
Application: KCMInit (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2b6f410900 (LWP 2588))]

Thread 3 (Thread 0x7f2b58341700 (LWP 2595)):
#0  0x7f2b6d4ec30d in poll () from /lib64/libc.so.6
#1  0x7f2b69e35314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f2b69e3542c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f2b6da60b9b in QEventDispatcherGlib::processEvents (this=0x13a1430,
flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f2b6da0cc6b in QEventLoop::exec (this=this@entry=0x7f2b58340c80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f2b6d85c98a in QThread::exec (this=) at
thread/qthread.cpp:522
#6  0x7f2b6401d805 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f2b6d8673df in QThreadPrivate::start (arg=0x7f2b6428bd40) at
thread/qthread_unix.cpp:367
#8  0x7f2b6bb69724 in start_thread () from /lib64/libpthread.so.0
#9  0x7f2b6d4f4e8d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f2b5a3df700 (LWP 2589)):
#0  0x7f2b6d4ec30d in poll () from /lib64/libc.so.6
#1  0x7f2b6e88e3c2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f2b6e88ffaf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f2b5c7c0839 in QXcbEventReader::run (this=0x13544b0) at
qxcbconnection.cpp:1384
#4  0x7f2b6d8673df in QThreadPrivate::start (arg=0x13544b0) at
thread/qthread_unix.cpp:367
#5  0x7f2b6bb69724 in start_thread () from /lib64/libpthread.so.0
#6  0x7f2b6d4f4e8d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f2b6f410900 (LWP 2588)):
[KCrash Handler]
#6  QMapData::findNode (this=0x4545454545454545, akey=...)
at /usr/include/qt5/QtCore/qmap.h:284
#7  0x7f2b642b243d in QMap::constFind (akey=...,
this=0x13a2a20) at /usr/include/qt5/QtCore/qmap.h:869
#8  QMap::find (akey=..., this=0x13a2a20) at
/usr/include/qt5/QtCore/qmap.h:876
#9  KEntryMap::findEntry (this=this@entry=0x13a2a20, group=..., key=...,
flags=...) at /usr/src/debug/kconfig-5.46.0/src/core/kconfigdata.cpp:74
#10 0x7f2b642b24d4 in KEntryMap::getEntry (this=this@entry=0x13a2a20,
group=..., key=..., defaultValue=..., flags=..., flags@entry=...,
expand=expand@entry=0x7ffc414f7d5f) at
/usr/src/debug/kconfig-5.46.0/src/core/kconfigdata.cpp:224
#11 0x7f2b642a7b48 in KConfigPrivate::lookupData (this=0x13a2a00,
group=..., key=key@entry=0x7f2b57509e07 "cursorTheme", flags=...,
flags@entry=..., expand=expand@entry=0x7ffc414f7d5f) at
/usr/src/debug/kconfig-5.46.0/src/core/kconfig.cpp:1005
#12 0x7f2b642b64cb in KConfigGroup::readEntry
(this=this@entry=0x7ffc414f7e30, key=key@entry=0x7f2b57509e07 "cursorTheme",
aDefault=...) at /usr/src/debug/kconfig-5.46.0/src/core/kconfiggroup.cpp:687
#13 0x7f2b574f85cb in X11Backend::kcmInit (this=0x13bf270) at
/usr/src/debug/plasma-desktop-5.12.90/kcms/input/backends/x11/x11_backend.cpp:127
#14 0x7f2b574eff84 in kcminit_mouse () at
/usr/src/debug/plasma-desktop-5.12.90/kcms/input/kcm/configcontainer.cpp:31
#15 0x7f2b5d5218d7 in KCMInit::runModule (this=this@entry=0x7ffc414f8200,
libName=..., service=...) at
/usr/src/debug/plasma-workspace-5.12.90/startkde/kcminit/main.cpp:87
#16 0x7f2b5d5221c1 in KCMInit::runModules (this=this@entry=0x7ffc414f8200,
phase=phase@entry=0) at
/usr/src/debug/plasma-workspace-5.12.90/startkde/kcminit/main.cpp:129
#17 0x7f2b5d522526 in KCMInit::KCMInit (this=0x7ffc414f8200, args=...) at
/usr/src/debug/plasma-workspace-5.12.90/startkde/kcminit/main.cpp:171
#18 0x7f2b5d5233a5 in kdemain (argc=1, argv=) at
/usr/src/debug/plasma-workspace-5.12.90/startkde/kcminit/main.cpp:241
#19 0x004087b0 in launch (argc=argc@entry=1, _name=0x12e57e1
"kcminit_startup", args=, args@entry=0x0, cwd=cwd@entry=0x0,
envc=envc@entry=0, envs=, envs@entry=0x0,
reset_env=reset_env@entry=false, tty=tty@entry=0x0,
avoid_loops=avoid_loops@entry=false,
startup_id_str=startup_id_str@entry=0x40b1b3 "0") at
/usr/src/debug/kinit-5.46.0/src/kdeinit/kinit.cpp:705
#20 0x004052bc in main (argc=5, argv=) at

[plasmashell] [Bug 392746] New: Plasma crashes when changing layout from folder-view to desktop

2018-04-04 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=392746

Bug ID: 392746
   Summary: Plasma crashes when changing layout from folder-view
to desktop
   Product: plasmashell
   Version: 5.12.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: christiande...@web.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.12.4)

Qt Version: 5.10.0
Frameworks Version: 5.44.0
Operating System: Linux 4.4.120-45-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
Have Plasma configured to use folder view as layout.
(The name of the following items are guessed from German)

1.) RIght click on the background
2.) Choose configure desktop
3.) Change layout to desktop (Arbeitsfläche)
4.) Confirm -> Plasma crashes

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7fd2c1dec700 (LWP 3542)):
#0  0x7fd3743148b4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fd3742d2950 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fd3742d3230 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fd3742d342c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fd37a3b0fbb in QEventDispatcherGlib::processEvents (this=0x655b830,
flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7fd37a35ca4b in QEventLoop::exec (this=this@entry=0x7fd2c1debc60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7fd37a19a14a in QThread::exec (this=) at
thread/qthread.cpp:522
#7  0x7fd37d9de3c8 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7fd37a19ee0f in QThreadPrivate::start (arg=0x66e54d0) at
thread/qthread_unix.cpp:376
#9  0x7fd379064724 in start_thread () from /lib64/libpthread.so.0
#10 0x7fd379aa4e8d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7fd2c71bc700 (LWP 3040)):
#0  0x7fd379a9c30d in poll () from /lib64/libc.so.6
#1  0x7fd3742d3314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd3742d342c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd37a3b0fbb in QEventDispatcherGlib::processEvents (this=0x3f41480,
flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fd37a35ca4b in QEventLoop::exec (this=this@entry=0x7fd2c71bbc40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fd37a19a14a in QThread::exec (this=) at
thread/qthread.cpp:522
#6  0x7fd2c85e3887 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7fd37a19ee0f in QThreadPrivate::start (arg=0x3f344f0) at
thread/qthread_unix.cpp:376
#8  0x7fd379064724 in start_thread () from /lib64/libpthread.so.0
#9  0x7fd379aa4e8d in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fd2d6d3e700 (LWP 2917)):
#0  0x7fd379a9833d in read () from /lib64/libc.so.6
#1  0x7fd374313750 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd3742d2e49 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd3742d32a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7fd3742d342c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7fd37a3b0fbb in QEventDispatcherGlib::processEvents (this=0x2770460,
flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fd37a35ca4b in QEventLoop::exec (this=this@entry=0x7fd2d6d3dc20,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#7  0x7fd37a19a14a in QThread::exec (this=) at
thread/qthread.cpp:522
#8  0x7fd37de48b82 in ?? () from /usr/lib64/libQt5Quick.so.5
#9  0x7fd37a19ee0f in QThreadPrivate::start (arg=0x276c740) at
thread/qthread_unix.cpp:376
#10 0x7fd379064724 in start_thread () from /lib64/libpthread.so.0
#11 0x7fd379aa4e8d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fd361df5700 (LWP 2900)):
#0  0x7fd3790690ff in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fd37fd2dc8b in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7fd37fd2dcb9 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7fd379064724 in start_thread () from /lib64/libpthread.so.0
#4  0x7fd379aa4e8d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fd363c58700 (LWP 2898)):
#0  0x7fd379a9833d in read () from /lib64/libc.so.6
#1  0x7fd374313750 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fd3742d2e49 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fd3742d32a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7fd3742d342c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7fd37a3b0fbb in 

[Akonadi] [Bug 384822] Mail filter with no longer work

2017-11-22 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=384822

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Christian Trippe <christiande...@web.de> ---
Seems to be fixed with Applications 17.11.80

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

[Akonadi] [Bug 384822] New: Mail filter with no longer work

2017-09-18 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=384822

Bug ID: 384822
   Summary: Mail filter with  no longer work
   Product: Akonadi
   Version: 5.6.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Mail Filter Agent
  Assignee: kdepim-b...@kde.org
  Reporter: christiande...@web.de
  Target Milestone: ---

I have several mail filters for a pop3 account. All the mails are downloaded to
one local folder. If one now selects all these mails and chooses "Apply all
filters manually" the mails where a filter with criteria "To"=... match get
moved to the correct destination folder, however mails where a filter with
criteria "List-Post"=... applies, stay in the original folder.

This used to work with previous kmail/akonadi versions. The problem persists
already since quite some time, so I unfortunatelly cannot point to the last
working release.

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

[Akonadi] [Bug 382530] Regression: Manually applying filters no longer works

2017-07-29 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=382530

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Christian Trippe <christiande...@web.de> ---
Not sure what changed after the latest update from openSUSE repos. But I can no
longer reproduce the problem. -> Seems to be fixed.

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

[Akonadi] [Bug 382530] New: Regression: Manually applying filters no longer works

2017-07-19 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=382530

Bug ID: 382530
   Summary: Regression: Manually applying filters no longer works
   Product: Akonadi
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Mail Filter Agent
  Assignee: kdepim-b...@kde.org
  Reporter: christiande...@web.de
  Target Milestone: ---

Set up some filters that do not apply automatically un incoming mails (my
personal workaround for the duplicate messages due to filtering problems) but
configure them to be applied for manual filtering

Then select a couple of mails, go to the contect menu and select "manually
apply all filters"

result -> Nothing happens
expected result -> filters should be applied an mails moved to the correct 
folders as specified in the filters


I am not 100% sure when this behaviour started, but at least with kmail/akonadi
form the 17.04.03 release and I am quite certain that it alreadywas present
with 17.04.02.

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

[kontact] [Bug 362817] Kontact crash on open addressbook from the email window

2017-05-05 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=362817

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

--- Comment #7 from Christian Trippe <christiande...@web.de> ---
I hid the bug today several times in the same way as described comment 6 under
kmail/kontact from the KDE Application 17.04.0 release.

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

[kmahjongg] [Bug 377476] New: kmahjongg crashes during start

2017-03-10 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=377476

Bug ID: 377476
   Summary: kmahjongg crashes during start
   Product: kmahjongg
   Version: 0.9
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: christiande...@web.de
CC: kde-games-b...@kde.org
  Target Milestone: ---

Application: kmahjongg (0.9)

Qt Version: 5.8.0
Frameworks Version: 5.31.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:

When I start KMahjongg it always crashes and DrKonqi appears. Backtrace is
attached.

The crash can be reproduced every time.

-- Backtrace:
Application: KMahjongg (kmahjongg), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f96c8486780 (LWP 13447))]

Thread 3 (Thread 0x7f96afd3a700 (LWP 13457)):
#0  0x7f96c49aa51d in read () from /lib64/libc.so.6
#1  0x7f96be785670 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f96be744e49 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f96be7452a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f96be74542c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f96c52a78ab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f96c52576ab in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f96c509f9aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f96c0c07d15 in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x7f96c50a4019 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#10 0x7f96c058b734 in start_thread () from /lib64/libpthread.so.0
#11 0x7f96c49b6d3d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f96b451d700 (LWP 13454)):
#0  0x7f96c49ae49d in poll () from /lib64/libc.so.6
#1  0x7f96be4e43e2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f96be4e5fcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f96b6a77c29 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f96c50a4019 in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f96c058b734 in start_thread () from /lib64/libpthread.so.0
#6  0x7f96c49b6d3d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f96c8486780 (LWP 13447)):
[KCrash Handler]
#6  0x7f96c5817440 in QPMCache::insert(QString const&, QPixmap const&, int)
() from /usr/lib64/libQt5Gui.so.5
#7  0x7f96c7eb1692 in KMahjonggBackground::getBackground (this=0x1accb20)
at /usr/src/debug/libkmahjongg-16.12.2/kmahjonggbackground.cpp:219
#8  0x0042f805 in GameView::updateBackground
(this=this@entry=0x1b29510) at
/usr/src/debug/kmahjongg-16.12.2/src/gameview.cpp:934
#9  0x004313fc in GameView::resizeEvent (this=0x1b29510,
event=) at /usr/src/debug/kmahjongg-16.12.2/src/gameview.cpp:872
#10 0x7f96c5f4fd7f in QWidget::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#11 0x7f96c60303ae in QFrame::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#12 0x7f96c62219d3 in QGraphicsView::viewportEvent(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#13 0x7f96c5259111 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib64/libQt5Core.so.5
#14 0x7f96c5f0c195 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#15 0x7f96c5f130f0 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#16 0x7f96c5259245 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#17 0x7f96c5f48b82 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool,
bool) () from /usr/lib64/libQt5Widgets.so.5
#18 0x7f96c5f4c793 in QWidgetPrivate::show_helper() () from
/usr/lib64/libQt5Widgets.so.5
#19 0x7f96c5f4f3c7 in QWidget::setVisible(bool) () from
/usr/lib64/libQt5Widgets.so.5
#20 0x7f96c5f4c740 in QWidgetPrivate::showChildren(bool) () from
/usr/lib64/libQt5Widgets.so.5
#21 0x7f96c5f4c7af in QWidgetPrivate::show_helper() () from
/usr/lib64/libQt5Widgets.so.5
#22 0x7f96c5f4f3c7 in QWidget::setVisible(bool) () from
/usr/lib64/libQt5Widgets.so.5
#23 0x7f96c5f4c740 in QWidgetPrivate::showChildren(bool) () from
/usr/lib64/libQt5Widgets.so.5
#24 0x7f96c5f4c7af in QWidgetPrivate::show_helper() () from
/usr/lib64/libQt5Widgets.so.5
#25 0x7f96c5f4f3c7 in QWidget::setVisible(bool) () from
/usr/lib64/libQt5Widgets.so.5
#26 0x00413f06 in main (argc=1, argv=) at
/usr/src/debug/kmahjongg-16.12.2/src/main.cpp:72

Reported using DrKonqi

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

[kmail2] [Bug 376981] kmail no longer displays mails

2017-02-28 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=376981

--- Comment #1 from Christian Trippe <christiande...@web.de> ---
As additional info this seems to be caused by duplicated messages in one folder
(which get created via bug 322126). As soon as on tries to display such a
duplicated message the content of this message will never be displayed. After
such an attempt also no other message will get displayed until kmail is
restarted.

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

[kmail2] [Bug 376981] New: kmail no longer displays mails

2017-02-27 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=376981

Bug ID: 376981
   Summary: kmail no longer displays mails
   Product: kmail2
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: christiande...@web.de
  Target Milestone: ---

After the upgrade to KDE Application 16.12 kmail no longer displays mails for
certain local folders for me.

When waiting long enough I get the following error dislpayed:

Unable to fetch item from backend (collection -1) : Unable to retrieve item
from resource: Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken.

Any hint on how to debug this further is appreciated.

I even completely rebuild the akonadi-database. However I am back at the same
behaviour after a few days of usage.

Marking the bug as major, as mails are no longer displayed, making kmail
unusable.

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

[kontact] [Bug 373145] Kontact (kontact), KMail, signal: Segmentation fault

2017-02-21 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=373145

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[kmail2] [Bug 364967] Kmail message list does not remember rightmost column width

2016-11-02 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=364967

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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

[kscreenlocker] [Bug 370206] KScreenlocker not unlockable after switching to new session

2016-10-10 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370206

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


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

2016-10-10 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370422

Bug ID: 370422
   Summary: kscreenlocker crashes when unlocking the session after
resume from s2ram
   Product: kscreenlocker
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: christiande...@web.de
CC: bhus...@gmail.com, mgraess...@kde.org

Starting with plasma 5.8 I cannot unlock my laptop after resume from suspend
(s2ram). After typing the password and unlocking the session, the locked screen
reappears after a few a few seconds. I did not have the problem with plasma
5.7.x

Switching the another virtual terminal (Ctrl+Alt+F1), I find the following in
~/.xsession-errors-:0

UnmapNotify: 134217739
UnmapNotify: 134217739
KCrash: Application 'kscreenlocker_greet' crashing...
CreateNotify: 134217731
CreateNotify: 134217735
CreateNotify: 134217737
CreateNotify: 134217739
CreateNotify: 134217741
MapNotify: 134217739
uhoh! duplicate!
uhoh! duplicate!
CreateNotify: 134217743
powerdevil: ACTIVE SESSION PATH CHANGED: "/"

Unlocking with loginctl unlock-session 1 from such a terminal successfully
unlocks the session.

The crash is always reproducible.

Reproducible: Always

Steps to Reproduce:
1. Suspend your laptop via lidclose
2. open the lid, the laptop resumes
3. Enter password and unlock

Actual Results:  
The lockscreen comes back.

Expected Results:  
Login to the running plasma session.

If you give me some hints, I can try to produce a proper backtrace.

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


[Akonadi] [Bug 322871] mail filters do not work for incoming messages if the destination folder of the pop3 resource is not the inbox

2016-09-26 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=322871

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #6 from Christian Trippe <christiande...@web.de> ---
Works fine now with kmail/akonadi from KDE Applications 16.04.3.

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


[kdepim] [Bug 258214] Choosing Completion Order from the context menu of the recipient field crashed kontact

2016-09-25 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=258214

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 Status|NEEDSINFO   |REOPENED
 Resolution|WAITINGFORINFO  |---

--- Comment #11 from Christian Trippe <christiande...@web.de> ---
The crash is still reproducible with the steps in comment 2 with kmail from KDE
Applications 16.04.3.

Updated backtrace
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6d655b17c0 (LWP 15476))]

Thread 24 (Thread 0x7f6ca79a1700 (LWP 16366)):
#0  0x7ffdae4fdb41 in clock_gettime ()
#1  0x7f6d62277c7d in clock_gettime () from /lib64/libc.so.6
#2  0x7f6d62c1d8f1 in qt_clock_gettime (ts=0x7f6ca79a0ba0, clock=1) at
tools/qelapsedtimer_unix.cpp:109
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:164
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:173
#5  0x7f6d62d7d609 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f6cc8014b40) at kernel/qtimerinfo_unix.cpp:91
#6  0x7f6d62d7db85 in QTimerInfoList::timerWait (this=0x7f6cc8014b40,
tm=...) at kernel/qtimerinfo_unix.cpp:388
#7  0x7f6d62d7ed4e in timerSourcePrepareHelper (timeout=0x7f6ca79a0c54,
src=) at kernel/qeventdispatcher_glib.cpp:132
#8  timerSourcePrepare (source=, timeout=0x7f6ca79a0c54) at
kernel/qeventdispatcher_glib.cpp:165
#9  0x7f6d598b04ad in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f6d598b0d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#11 0x7f6d598b0f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#12 0x7f6d62d7ef7b in QEventDispatcherGlib::processEvents
(this=0x7f6cc8003ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#13 0x7f6d62d2e8cb in QEventLoop::exec (this=this@entry=0x7f6ca79a0e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#14 0x7f6d62b7506a in QThread::exec (this=) at
thread/qthread.cpp:507
#15 0x7f6d62b79899 in QThreadPrivate::start (arg=0x6aba900) at
thread/qthread_unix.cpp:344
#16 0x7f6d5b5c70a4 in start_thread () from /lib64/libpthread.so.0
#17 0x7f6d6226b02d in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7f6cad571700 (LWP 15566)):
#0  0x7f6d62262bfd in poll () from /lib64/libc.so.6
#1  0x7f6d598b0e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6d598b0f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6d62d7ef7b in QEventDispatcherGlib::processEvents
(this=0x7f6cbc003350, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f6d62d2e8cb in QEventLoop::exec (this=this@entry=0x7f6cad570e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7f6d62b7506a in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f6d62b79899 in QThreadPrivate::start (arg=0x265ded0) at
thread/qthread_unix.cpp:344
#7  0x7f6d5b5c70a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7f6d6226b02d in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7f6cadd72700 (LWP 15563)):
#0  0x7f6d598f2cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f6d598b0d55 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f6d598b0f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f6d62d7ef7b in QEventDispatcherGlib::processEvents
(this=0x7f6cb8003ed0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f6d62d2e8cb in QEventLoop::exec (this=this@entry=0x7f6cadd71e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#5  0x7f6d62b7506a in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f6d62b79899 in QThreadPrivate::start (arg=0x383cf00) at
thread/qthread_unix.cpp:344
#7  0x7f6d5b5c70a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7f6d6226b02d in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7f6caedc2700 (LWP 15532)):
#0  0x7f6d598f2cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f6d598b078e in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f6d598b0df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f6d598b0f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f6d62d7ef7b in QEventDispatcherGlib::processEvents
(this=0x7f6cb0003260, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f6d62d2e8cb in QEventLoop::exec (this=this@entry=0x7f6caedc1e10,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#6  0x7f6d62b7506a in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f6d62b79899 in QThreadPrivate::start (arg=0x2a26f00) at
thread/qthread_unix.cpp:344
#8  0x7f6d5b5c70a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f6d6226b02d in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7f6caf5

[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-27 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager

2016-05-18 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360037

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

2016-04-17 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361132

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


[kontact] [Bug 361605] kmail crash on double click email

2016-04-15 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361605

--- Comment #4 from Christian Trippe <christiande...@web.de> ---
Thanks for the quick fix and for the hint about kdepim-addons. Installing this
missing packages also "fixes" the crash for me.

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


[kontact] [Bug 361605] kmail crash on double click email

2016-04-15 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361605

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

--- Comment #1 from Christian Trippe <christiande...@web.de> ---
I see the same crash in openSUSE. It also happens with standalone kmail, so I
guess this might be the better product. I am not sure if this is related but
starting with kmail 16.03.90 where also the header in the normal mail view is
missing and cannot be chosen from the menu.

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


[drkonqi] [Bug 355807] Dialog to mark report as related does nothing

2016-03-22 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355807

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


[kwin] [Bug 360828] Maximized windows go below the panel

2016-03-21 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360828

--- Comment #2 from Christian Trippe <christiande...@web.de> ---
Created attachment 98017
  --> https://bugs.kde.org/attachment.cgi?id=98017=edit
result of xprop and clicking on the panel

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


[kwin] [Bug 360828] New: Maximized windows go below the panel

2016-03-21 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360828

Bug ID: 360828
   Summary: Maximized windows go below the panel
   Product: kwin
   Version: 5.6.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: christiande...@web.de

Since the update to plasma 5.6 full screen windows go below the panel although
it is set to "always visible". Please note that this is with a single monitor
setup!

This did not happen with plasma 5.5.x. Not sure if kwin is the correct
component or it should better be reported against plasmashell.



Reproducible: Always

Steps to Reproduce:
1. Set panel to "always visible"
2. open some window, e.g. konsole
3. click on the maximize button

Actual Results:  
window goes below the panel, e.g uses the full screen

Expected Results:  
Window should cover the whole screen except the panel

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


[plasma-nm] [Bug 359842] Shared connection asks for root password on every reconnect.

2016-03-19 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359842

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


[systemsettings] [Bug 359945] Touchpad scroll delta is limited by max. 10

2016-03-05 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359945

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


[kmail2] [Bug 356431] no address autocompletion

2016-02-14 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356431

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


[kjots] [Bug 359380] New: Kjots plugin for kontact not available

2016-02-14 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359380

Bug ID: 359380
   Summary: Kjots plugin for kontact not available
   Product: kjots
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: steve...@gmail.com
  Reporter: christiande...@web.de

With the move of kjots to Frameworks 5 and out of the main kdepim I noticed
that the kontact plugin for kjots is missing.

It would be great if this could be brought back. Not sure if this qualifies as
a bug or is rather a wishlist. 

Otherwise thanks a lot for bringing kjots back in the KF5 world!

Reproducible: Always

Steps to Reproduce:
1. Have kontact and kjots build on KF5 installed
2. kjots can be started as stand alone application
3. kjots is not available from within kontact

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


[korgac] [Bug 358152] New: korganizer reminder tool crashes at akonadi/kontact start

2016-01-17 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358152

Bug ID: 358152
   Summary: korganizer reminder tool crashes at akonadi/kontact
start
   Product: korgac
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: christiande...@web.de

Application: korgac (5.1.1)

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

-- Information about the crash:
Starting a new session for my user and then starting kontact often causes a
crash in the korganizer reminder tool, which makes DrKonqi appear.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KOrganizer-Erinnerungsmodul (korgac), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ffbc35e5800 (LWP 1447))]

Thread 5 (Thread 0x7ffba7bf0700 (LWP 1455)):
#0  0x7ffbbd29cc1d in poll () from /lib64/libc.so.6
#1  0x7ffbb6bbd422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7ffbb6bbf00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7ffba991b3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ffbbdbab32f in QThreadPrivate::start (arg=0xfab140) at
thread/qthread_unix.cpp:331
#5  0x7ffbb62ea0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7ffbbd2a504d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7ffb9d331700 (LWP 1464)):
#0  0x7ffbb5e0fcf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7ffbb5dcde4a in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ffbb5dcdf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ffbbd8b in QEventDispatcherGlib::processEvents
(this=0x7ffb980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ffbbdd84d53 in QEventLoop::exec (this=this@entry=0x7ffb9d330dd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ffbbdba661a in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7ffbbdbab32f in QThreadPrivate::start (arg=0x103afe0) at
thread/qthread_unix.cpp:331
#7  0x7ffbb62ea0a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7ffbbd2a504d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7ffb9cb30700 (LWP 1465)):
#0  0x7ffbbd2b161f in __libc_enable_asynccancel () from /lib64/libc.so.6
#1  0x7ffbbd298ce2 in read () from /lib64/libc.so.6
#2  0x7ffbb5e0eb60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7ffbb5dcd999 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7ffbb5dcddf8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7ffbb5dcdf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7ffbbd8b in QEventDispatcherGlib::processEvents
(this=0x7ffb98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7ffbbdd84d53 in QEventLoop::exec (this=this@entry=0x7ffb9cb2fdd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7ffbbdba661a in QThread::exec (this=) at
thread/qthread.cpp:503
#9  0x7ffbbdbab32f in QThreadPrivate::start (arg=0x1026590) at
thread/qthread_unix.cpp:331
#10 0x7ffbb62ea0a4 in start_thread () from /lib64/libpthread.so.0
#11 0x7ffbbd2a504d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ffb97fff700 (LWP 2210)):
#0  0x7ffbbd29cc1d in poll () from /lib64/libc.so.6
#1  0x7ffbb5dcde64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ffbb5dcdf7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ffbbd8b in QEventDispatcherGlib::processEvents
(this=0x7ffb8c004130, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7ffbbdd84d53 in QEventLoop::exec (this=this@entry=0x7ffb97ffedd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7ffbbdba661a in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7ffbbdbab32f in QThreadPrivate::start (arg=0xfb35b0) at
thread/qthread_unix.cpp:331
#7  0x7ffbb62ea0a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7ffbbd2a504d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ffbc35e5800 (LWP 1447)):
[KCrash Handler]
#6  QVector::reserve (this=0x13e1980,
asize=asize@entry=0) at /usr/include/qt5/QtCore/qvector.h:366
#7  0x7ffbc21b9d54 in KCalCore::Calendar::setupRelations (this=0x10da230,
forincidence=...) at /usr/src/debug/kcalcore-15.12.1/src/calendar.cpp:1032
#8  0x7ffbc21f88ac in KCalCore::MemoryCalendar::addIncidence
(this=0x10da230, incidence=...) at
/usr/src/debug/kcalcore-15.12.1/src/memorycalendar.cpp:305
#9  0x7ffbc2b9ce9d in Akonadi::CalendarBasePrivate::internalInsert
(this=this@entry=0x1083860, item=...) at
/usr/src/debug/akonadi-calendar-15.12.1/src/calendarbase.cpp:158
#10 0x7ffbc2baac53 in 

[korgac] [Bug 358152] korganizer reminder tool crashes at akonadi/kontact start

2016-01-17 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358152

--- Comment #1 from Christian Trippe <christiande...@web.de> ---
This is with korganizer 15.12.1 but if I remember correctly this happened also
with previous releases. This version is unfortunately not available in
bugzilla.

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


[drkonqi] [Bug 356822] Can not add similar issues

2016-01-11 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356822

Christian Trippe <christiande...@web.de> changed:

   What|Removed |Added

 CC||christiande...@web.de

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


[systemsettings] [Bug 357862] New: systemsettings crashed after changing the hotkey for spectacle

2016-01-11 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357862

Bug ID: 357862
   Summary: systemsettings crashed after changing the hotkey for
spectacle
   Product: systemsettings
   Version: 5.5.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: christiande...@web.de

Application: systemsettings5 (5.5.3)

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

-- Information about the crash:
I changed the shortcut "print" to launch spectacle. I guess I also tried to
press the key after applying the change. Then systemsettings crashed.

This bug is probably a duplicate of bug 346335. However drkonqi did not allow
me to add this information to the bug report or suggest this bug as a duplicate
(probably due to bug 356822).

-- Backtrace:
Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc402138780 (LWP 7685))]

Thread 3 (Thread 0x7fc3efb9a700 (LWP 7686)):
#0  0x7fc3fde65c1d in poll () from /lib64/libc.so.6
#1  0x7fc3fac3f422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fc3fac4100f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fc3f1eef3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fc3fe55d32f in QThreadPrivate::start (arg=0x222c9b0) at
thread/qthread_unix.cpp:331
#5  0x7fc3fa3c90a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc3fde6e04d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fc3dd5d6700 (LWP 7688)):
#0  0x7fc3fde65c1d in poll () from /lib64/libc.so.6
#1  0x7fc3f9eace64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fc3f9ead19a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#3  0x7fc3de112426 in ?? () from /usr/lib64/libgio-2.0.so.0
#4  0x7fc3f9ed1f65 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7fc3fa3c90a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fc3fde6e04d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc402138780 (LWP 7685)):
[KCrash Handler]
#6  QString (other=, this=this@entry=0x7ffd687aa720) at ../../src/corelib/tools/qstring.h:877
#7  QLabel::text (this=0x0) at widgets/qlabel.cpp:322
#8  0x7fc401890fd1 in ShortcutEditWidget::setKeySequence (this=0x2bcfea0,
activeSeq=...) at /usr/src/debug/kxmlgui-5.18.0/src/kshortcuteditwidget.cpp:187
#9  0x7fc3fe76873f in call (a=0x7ffd687aa890, r=0x7fc3fc34d580 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>, this=0x2f78720) at
../../src/corelib/kernel/qobject_impl.h:124
#10 QMetaObject::activate (sender=0x7fc3fc34d580 <(anonymous
namespace)::Q_QGS_s_instance::innerFunction()::holder>, signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffd687aa890) at kernel/qobject.cpp:3698
#11 0x7fc3fe7692e7 in QMetaObject::activate (sender=,
m=m@entry=0x7fc3fc34c9c0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd687aa890)
at kernel/qobject.cpp:3578
#12 0x7fc3fc1333b4 in KGlobalAccel::globalShortcutChanged (this=, _t1=_t1@entry=0x29c4b40, _t2=...) at
/usr/src/debug/kglobalaccel-5.18.0/build/src/moc_kglobalaccel.cpp:159
#13 0x7fc3fc137366 in KGlobalAccelPrivate::_k_shortcutGotChanged
(this=0x27aa810, actionId=..., keys=...) at
/usr/src/debug/kglobalaccel-5.18.0/src/kglobalaccel.cpp:462
#14 0x7fc3fe768cc6 in QMetaObject::activate (sender=0x313afd0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffd687aaa40) at kernel/qobject.cpp:3713
#15 0x7fc3fe7692e7 in QMetaObject::activate (sender=,
m=m@entry=0x7fc3fc34cb40 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd687aaa40)
at kernel/qobject.cpp:3578
#16 0x7fc3fc1407b7 in OrgKdeKGlobalAccelInterface::yourShortcutGotChanged
(this=, _t1=..., _t2=...) at
/usr/src/debug/kglobalaccel-5.18.0/build/src/kglobalaccel_interface.moc:264
#17 0x7fc3fc140a2d in OrgKdeKGlobalAccelInterface::qt_static_metacall
(_o=_o@entry=0x313afd0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=0, _a=_a@entry=0x7ffd687aac80) at
/usr/src/debug/kglobalaccel-5.18.0/build/src/kglobalaccel_interface.moc:154
#18 0x7fc3fc142da3 in OrgKdeKGlobalAccelInterface::qt_metacall
(this=0x313afd0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffd687aac80) at
/usr/src/debug/kglobalaccel-5.18.0/build/src/kglobalaccel_interface.moc:250
#19 0x7fc3ff09bda4 in QDBusConnectionPrivate::deliverCall (this=0x2282200,
object=0x313afd0, msg=..., metaTypes=..., slotIdx=6) at qdbusintegrator.cpp:979
#20 0x7fc3fe769ac6 in QObject::event (this=0x313afd0, e=) at
kernel/qobject.cpp:1239
#21 0x7fc400280e7c in QApplicationPrivate::notify_helper

[kontact] [Bug 357139] New: Kontact crashed when choosing "configure completion" in kmail composer

2015-12-25 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357139

Bug ID: 357139
   Summary: Kontact crashed when choosing "configure completion"
in kmail composer
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: christiande...@web.de

Application: kontact (5.1)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
1.)Open kontact with kmail included.
2.) Open the kmail composer
3.) RIght click in the address field
4.) Choose "configure completion" (guessed from German "Vervollständigung
einrichten ..."
5.) kontact crashes (sometimes but not always)

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 0x7fe54ccb9800 (LWP 7990))]

Thread 25 (Thread 0x7fe52edb3700 (LWP 7991)):
#0  0x7fe549900c1d in poll () from /lib64/libc.so.6
#1  0x7fe5430a3422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fe5430a500f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fe530f02c29 in QXcbEventReader::run (this=0xfe8420) at
qxcbconnection.cpp:1214
#4  0x7fe54a20e55f in QThreadPrivate::start (arg=0xfe8420) at
thread/qthread_unix.cpp:331
#5  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7fe5275ef700 (LWP 7992)):
#0  0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe5474644a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe5474644c9 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7fe4e2d0b700 (LWP 7993)):
#0  postEventSourcePrepare (s=0x7fe4dc0012d0, timeout=0x7fe4e2d0ac14) at
kernel/qeventdispatcher_glib.cpp:248
#1  0x7fe5424624ad in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fe542462d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe542462f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fe54a43fa5b in QEventDispatcherGlib::processEvents
(this=0x7fe4dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7fe54a3e6a63 in QEventLoop::exec (this=this@entry=0x7fe4e2d0add0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7fe54a20984a in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7fe54a20e55f in QThreadPrivate::start (arg=0x11796b0) at
thread/qthread_unix.cpp:331
#8  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7fe4dbfff700 (LWP 7994)):
#0  0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe5471704cd in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe547492da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7fe4db7fe700 (LWP 7995)):
#0  0x7fe542c8405f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fe5471714a3 in ?? () from /usr/lib64/libQt5WebKit.so.5
#2  0x7fe547492da1 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#4  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7fe4ca4f4700 (LWP 7996)):
#0  0x7fe549900c1d in poll () from /lib64/libc.so.6
#1  0x7fe542462e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fe542462f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fe54a43fa5b in QEventDispatcherGlib::processEvents
(this=0x7fe4c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fe54a3e6a63 in QEventLoop::exec (this=this@entry=0x7fe4ca4f3dd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fe54a20984a in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fe54a20e55f in QThreadPrivate::start (arg=0x15cc760) at
thread/qthread_unix.cpp:331
#7  0x7fe542c800a4 in start_thread () from /lib64/libpthread.so.0
#8  0x7fe54990904d in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fe4c9cf3700 (LWP 7997)):
#0  0x7fe5424a4d14 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fe5424628e9 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fe542462df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7fe542462f7c in g_main_context_iteration