[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-07-03 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=381644

--- Comment #28 from Harald Sitter  ---
*** Bug 372730 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-07-03 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=381644

Harald Sitter  changed:

   What|Removed |Added

 CC||k...@sedrubal.de

--- Comment #27 from Harald Sitter  ---
*** Bug 359405 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-06-27 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=381644

Harald Sitter  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
   Version Fixed In||5.16.1
  Latest Commit||https://commits.kde.org/drk
   ||onqi/c2775e7335a13f2d2a4da6
   ||7e2488aa8c71708cf8

--- Comment #26 from Harald Sitter  ---
Git commit c2775e7335a13f2d2a4da67e2488aa8c71708cf8 by Harald Sitter.
Committed on 27/06/2019 at 11:38.
Pushed by sitter into branch 'Plasma/5.16'.

force the backtracewidget into loading state when the generator is loading

Summary:
this specifically unsets the m_highlighter which absolutely must not be
present when in loading state (or more specifically: when receiving lines
as-they-appear as opposed to the finished backtrace).
also assert that the widget has no highlighter when loading lines

the highlighter design is fairly wonky, it actually highlights off of the
qtextdocument, but to highlight it needs to know the actual parsed trace
Line entities and they are of course no longer present because the
document only has a text blob. to bridge that disconnect the highlighter
needs to match up the textual lines to the Line entities by their index.
naturally this is a potential bundle of segfault sources when the two
sources no longer align.

unfortunately that is exactly what could happen:
technically speaking drkonqi has two instances of backtracewidget. one
in the main dialog and one in the report dialog. they both use the same
generator though. so what happened was a confusion over which state the
widget needs to be in vis a vis the generator. if the first widget already
loaded a backtrace the generator would be in Loaded state and so would the
widget (i.e. it'd have a highlighter). if the user then proceeds to the
report dialog and they'd get a new widget with a reload button. if the user
then would use the reload button the new widget would be fine, it would
trigger a "reload". the old widget however would not know anything about
the reload and continue to be in Loaded state with a highlighter attached.
as the generator now sends lines to the old and the new widget, the old
widget would receive the lines with a highlighter attached.
bang! the (new) lines disalign with the Line entities in the highlighter
and all hell breaks loose.

this quite possibly fixes all occurrences of the #381644 crasher, but I
wouldn't exclude other points of frailty. as mentioned, the way the
highlighter's connecting textual lines to Line entities is fairly
fragile in of itself.

CHANGELOG: No longer crashes when reloading backtraces under certain
circumstances
FIXED-IN: 5.16.1

Test Plan:
- killall -SEGV dolphin
- open drkonqi
- go to backtrace tab
- let backtrace
- click report bug
- proceed to backtrace page
- click reload
- no crashy

Reviewers: #plasma

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D21801

M  +6-0src/backtracewidget.cpp

https://commits.kde.org/drkonqi/c2775e7335a13f2d2a4da67e2488aa8c71708cf8

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-06-21 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=381644

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||frmdst...@protonmail.com

--- Comment #25 from Wolfgang Bauer  ---
*** Bug 408993 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-06-14 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=381644

--- Comment #24 from Harald Sitter  ---
*** Bug 372108 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-06-14 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||me.noob+yeeke...@gmail.com

--- Comment #23 from Christoph Feck  ---
*** Bug 408107 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-05-30 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||giecr...@stegny.2a.pl

--- Comment #22 from Christoph Feck  ---
*** Bug 407482 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-05-25 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=381644

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

--- Comment #21 from John Scott  ---
Dr. Konqi crashed trying to get a new backtrace for Plasma, and I think my
crash might be related.

Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff3e4952840 (LWP 1312))]h

Thread 4 (Thread 0x7ff3d963a700 (LWP 1348)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x56438d1bb908) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x56438d1bb8b8,
cond=0x56438d1bb8e0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x56438d1bb8e0, mutex=0x56438d1bb8b8) at
pthread_cond_wait.c:655
#3  0x7ff3d9c1ce63 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7ff3d9c1cbb7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7ff3e8bd7fa3 in start_thread (arg=) at
pthread_create.c:486
#6  0x7ff3e93944cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7ff3e1b60700 (LWP 1316)):
#0  __GI___libc_read (nbytes=16, buf=0x7ff3e1b5fb10, fd=7) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=7, buf=0x7ff3e1b5fb10, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7ff3e8029aa0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff3e7fe3c0f in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff3e7fe40e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff3e7fe425c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7ff3e989b87b in QEventDispatcherGlib::processEvents
(this=0x7ff3d4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#7  0x7ff3e984927b in QEventLoop::exec (this=this@entry=0x7ff3e1b5fd30,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#8  0x7ff3e9698ec6 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#9  0x7ff3ea6d5545 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7ff3e96a2aa7 in QThreadPrivate::start (arg=0x7ff3ea755d60) at
thread/qthread_unix.cpp:367
#11 0x7ff3e8bd7fa3 in start_thread (arg=) at
pthread_create.c:486
#12 0x7ff3e93944cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7ff3e3b8e700 (LWP 1313)):
#0  0x7ff3e9389819 in __GI___poll (fds=0x7ff3e3b8dc78, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff3e7f70cf7 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7ff3e7f7291a in xcb_wait_for_event () from
/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7ff3e44f6d79 in QXcbEventReader::run (this=0x56438ce0b300) at
qxcbconnection.h:409
#4  0x7ff3e96a2aa7 in QThreadPrivate::start (arg=0x56438ce0b300) at
thread/qthread_unix.cpp:367
#5  0x7ff3e8bd7fa3 in start_thread (arg=) at
pthread_create.c:486
#6  0x7ff3e93944cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7ff3e4952840 (LWP 1312)):
[KCrash Handler]
#6  0x56438cd0a6e9 in BacktraceLine::type (this=0x56438dcfc308) at
./src/parser/backtraceline.h:59
#7  GdbHighlighter::highlightBlock (this=this@entry=0x7ff3dc00b290, text=...)
at ./src/gdbhighlighter.cpp:80
#8  0x7ff3e9d49f39 in QSyntaxHighlighterPrivate::reformatBlock
(this=this@entry=0x7ff3dc00a2d0, block=...) at text/qsyntaxhighlighter.cpp:201
#9  0x7ff3e9d4a0f8 in QSyntaxHighlighterPrivate::reformatBlocks
(this=0x7ff3dc00a2d0, from=, charsRemoved=,
charsAdded=14) at text/qsyntaxhighlighter.cpp:182
#10 0x7ff3e9873906 in QMetaObject::activate (sender=0x56438d007be0,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3771
#11 0x7ff3e9f7640a in QTextDocument::contentsChange
(this=this@entry=0x56438d007be0, _t1=, _t2=,
_t3=) at .moc/moc_qtextdocument.cpp:383
#12 0x7ff3e9d084f1 in QTextDocumentPrivate::finishEdit
(this=0x56438d022b00) at text/qtextdocument_p.cpp:1217
#13 0x7ff3e9d08751 in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1201
#14 QTextDocumentPrivate::endEditBlock (this=) at
text/qtextdocument_p.cpp:1184
#15 0x7ff3ea3a03f5 in QWidgetTextControlPrivate::append
(this=0x56438d0084e0, text=..., format=format@entry=Qt::AutoText) at
widgets/qwidgettextcontrol.cpp:3136
#16 0x7ff3ea3a049e in QWidgetTextControl::append (this=,
text=...) at widgets/qwidgettextcontrol.cpp:3142
#17 0x7ff3ea37cd89 in QTextEdit::append (this=, text=...) at
widgets/qtextedit.cpp:2626
#18 0x56438ccf9160 in BacktraceWidget::backtraceNewLine (this=, line=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:436
#19 0x7ff3e9873a43 in 

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-02-10 Thread Volker Kuhlmann
https://bugs.kde.org/show_bug.cgi?id=381644

Volker Kuhlmann  changed:

   What|Removed |Added

 CC||list0...@paradise.net.nz

--- Comment #20 from Volker Kuhlmann  ---
openSUSE Leap 15.0
drkonqi crash when trying to report a plasmashell crash

Backtrace:

Application: drkonqi (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f96255de8c0 (LWP 11785))]

Thread 3 (Thread 0x7f9609b89700 (LWP 11789)):
#0  0x7f961cd40819 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f961cd410fb in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f961cd412dc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f9621500c0b in QEventDispatcherGlib::processEvents
(this=0x7f9604000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f96214a909a in QEventLoop::exec (this=this@entry=0x7f9609b88ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f96212d84da in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7f9622b7e985 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f96212dd0ce in QThreadPrivate::start (arg=0x7f9622deed60) at
thread/qthread_unix.cpp:368
#8  0x7f961f078559 in start_thread () from /lib64/libpthread.so.0
#9  0x7f9620bdb81f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f96136b1700 (LWP 11786)):
#0  0x7f9620bd107b in poll () from /lib64/libc.so.6
#1  0x7f961bfba387 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f961bfbbfba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f9616469029 in QXcbEventReader::run (this=0x55d7a928d000) at
qxcbconnection.cpp:1330
#4  0x7f96212dd0ce in QThreadPrivate::start (arg=0x55d7a928d000) at
thread/qthread_unix.cpp:368
#5  0x7f961f078559 in start_thread () from /lib64/libpthread.so.0
#6  0x7f9620bdb81f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f96255de8c0 (LWP 11785)):
[KCrash Handler]
#6  BacktraceLine::type (this=) at
/usr/src/debug/drkonqi5-5.12.5-lp150.1.1.x86_64/src/parser/backtraceline.h:59
#7  GdbHighlighter::highlightBlock (this=this@entry=0x7f960c00a900, text=...)
at /usr/src/debug/drkonqi5-5.12.5-lp150.1.1.x86_64/src/gdbhighlighter.cpp:80
#8  0x7f9621bd5458 in QSyntaxHighlighterPrivate::reformatBlock
(this=this@entry=0x55d7a93a9560, block=...) at text/qsyntaxhighlighter.cpp:203
#9  0x7f9621bd55f0 in QSyntaxHighlighterPrivate::reformatBlocks
(this=0x55d7a93a9560, from=, charsRemoved=,
charsAdded=15) at text/qsyntaxhighlighter.cpp:184
#10 0x7f96214d804a in QMetaObject::activate
(sender=sender@entry=0x55d7a9545360, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff80e01cb0)
at kernel/qobject.cpp:3766
#11 0x7f96214d8757 in QMetaObject::activate
(sender=sender@entry=0x55d7a9545360, m=m@entry=0x7f96220c1f00
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff80e01cb0)
at kernel/qobject.cpp:3628
#12 0x7f9621dedf5a in QTextDocument::contentsChange
(this=this@entry=0x55d7a9545360, _t1=, _t2=,
_t3=) at .moc/moc_qtextdocument.cpp:383
#13 0x7f9621b941e1 in QTextDocumentPrivate::finishEdit
(this=0x55d7a970f370) at text/qtextdocument_p.cpp:1217
#14 0x7f9621b9441c in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1201
#15 0x7f9621bc0304 in QTextCursor::endEditBlock
(this=this@entry=0x7fff80e01d58) at text/qtextcursor.cpp:2510
#16 0x7f96224038dc in QWidgetTextControlPrivate::append
(this=0x55d7a93d2350, text=..., format=format@entry=Qt::AutoText) at
widgets/qwidgettextcontrol.cpp:3133
#17 0x7f962240394e in QWidgetTextControl::append (this=,
text=...) at widgets/qwidgettextcontrol.cpp:3139
#18 0x7f96223ee0a9 in QTextEdit::append (this=, text=...) at
widgets/qtextedit.cpp:2603
#19 0x55d7a7f31340 in BacktraceWidget::backtraceNewLine (this=, line=...) at
/usr/src/debug/drkonqi5-5.12.5-lp150.1.1.x86_64/src/backtracewidget.cpp:316
#20 0x7f96214d814c in QtPrivate::QSlotObjectBase::call (a=0x7fff80e01f20,
r=0x55d7a96b1fe0, this=0x55d7a9626940) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
#21 QMetaObject::activate (sender=sender@entry=0x55d7a93ab1a0,
signalOffset=, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7fff80e01f20) at kernel/qobject.cpp:3749
#22 0x7f96214d8757 in QMetaObject::activate
(sender=sender@entry=0x55d7a93ab1a0, m=m@entry=0x55d7a81b35c0
,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff80e01f20)
at kernel/qobject.cpp:3628
#23 0x55d7a7f7dc85 in BacktraceGenerator::newLine
(this=this@entry=0x55d7a93ab1a0, _t1=...) at
/usr/src/debug/drkonqi5-5.12.5-lp150.1.1.x86_64/build/src/drkonqi_autogen/EWIEGA46WW/moc_backtracegenerator.cpp:201
#24 0x55d7a7f3553a in BacktraceGenerator::slotReadInput

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2019-01-08 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||zingaburga+kdebugs@hotmail.
   ||com

--- Comment #19 from Christoph Feck  ---
*** Bug 402003 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-12-27 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||fintenc...@gmail.com

--- Comment #18 from Christoph Feck  ---
*** Bug 362776 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-11-20 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||obe...@web.de

--- Comment #17 from Christoph Feck  ---
*** Bug 400734 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-11-01 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

--- Comment #16 from Christoph Feck  ---
*** Bug 400550 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-11-01 Thread Alexander Potashev
https://bugs.kde.org/show_bug.cgi?id=381644

Alexander Potashev  changed:

   What|Removed |Added

 CC||aspotas...@gmail.com

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-10-01 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #15 from Christoph Feck  ---
*** Bug 399036 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-09-12 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #14 from Christoph Feck  ---
*** Bug 398424 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-07-18 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||bizy...@zoho.com

--- Comment #13 from Christoph Feck  ---
*** Bug 396049 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-07-18 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||jonay.sant...@gmail.com

--- Comment #12 from Christoph Feck  ---
*** Bug 372550 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-07-18 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||swampy1...@msn.com

--- Comment #11 from Christoph Feck  ---
*** Bug 395962 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-07-18 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||kamika...@web.de

--- Comment #10 from Christoph Feck  ---
*** Bug 392115 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-07-18 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||agan...@gmail.com

--- Comment #9 from Christoph Feck  ---
*** Bug 395852 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-05-16 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

--- Comment #8 from Christoph Feck  ---
*** Bug 393667 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-03-07 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||ken20...@ukr.net

--- Comment #7 from Christoph Feck  ---
*** Bug 391534 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2018-01-29 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||m...@dennis-irrgang.com

--- Comment #6 from Christoph Feck  ---
*** Bug 389229 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2017-12-19 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||arca...@ivanov.biz

--- Comment #4 from Christoph Feck  ---
*** Bug 387139 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2017-09-13 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||premislaus1...@gmail.com

--- Comment #3 from Christoph Feck  ---
*** Bug 384238 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2017-09-12 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||wibl...@gmail.com

--- Comment #2 from Christoph Feck  ---
*** Bug 384400 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2017-06-26 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

 CC||marian.trenkwal...@gmail.co
   ||m

--- Comment #1 from Christoph Feck  ---
*** Bug 272540 has been marked as a duplicate of this bug. ***

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

[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report

2017-06-26 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=381644

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

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