[kontact] [Bug 437111] New: Kontact crashed on quit

[Matthias Nagel]

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

Bug ID: 437111
   Summary: Kontact crashed on quit
   Product: kontact
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: matthias.h.na...@gmail.com
  Target Milestone: ---

Application: kontact (5.16.3 (20.12.3))

Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.10.1-gentoo-r1 x86_64
Windowing system: X11
Distribution: Gentoo/Linux

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

Nothing in particular, just closing the application. It is sometimes
reproducible (estimate: 1 out of 20).

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fe6f6a57ec0
(LWP 1853))]
[KCrash Handler]
#6  0x7fe65110e321 in KMReaderMainWin::~KMReaderMainWin()
(this=this@entry=0x7fe67c02a490, __in_chrg=,
__vtt_parm=) at
/var/tmp/portage/kde-apps/kmail-20.12.3/work/kmail-20.12.3/src/kmreadermainwin.cpp:115
#7  0x7fe65110e409 in KMReaderMainWin::~KMReaderMainWin()
(this=0x7fe67c02a490, __in_chrg=, __vtt_parm=) at
/var/tmp/portage/kde-apps/kmail-20.12.3/work/kmail-20.12.3/src/kmreadermainwin.cpp:117
#8  0x7fe709aa4d8f in QObject::event(QEvent*)
(this=this@entry=0x7fe67c02a490, e=e@entry=0x7fe67c06c370) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:1301
#9  0x7fe70a4b57c3 in QWidget::event(QEvent*)
(this=this@entry=0x7fe67c02a490, event=event@entry=0x7fe67c06c370) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:9080
#10 0x7fe70a5c9734 in QMainWindow::event(QEvent*)
(this=this@entry=0x7fe67c02a490, event=event@entry=0x7fe67c06c370) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/widgets/qmainwindow.cpp:1341
#11 0x7fe70accfedb in KMainWindow::event(QEvent*)
(this=this@entry=0x7fe67c02a490, ev=ev@entry=0x7fe67c06c370) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.80.0/work/kxmlgui-5.80.0/src/kmainwindow.cpp:913
#12 0x7fe70ad19fb7 in KXmlGuiWindow::event(QEvent*) (this=0x7fe67c02a490,
ev=0x7fe67c06c370) at
/var/tmp/portage/kde-frameworks/kxmlgui-5.80.0/work/kxmlgui-5.80.0/src/kxmlguiwindow.cpp:109
#13 0x7fe70a473d3f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55f6cdd183f0, receiver=receiver@entry=0x7fe67c02a490,
e=e@entry=0x7fe67c06c370) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3632
#14 0x7fe70a47c950 in QApplication::notify(QObject*, QEvent*)
(this=0x7ffeaf399a20, receiver=0x7fe67c02a490, e=0x7fe67c06c370) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3156
#15 0x7fe709a79817 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x7fe67c02a490, event=0x7fe67c06c370) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1063
#16 0x7fe709a7c340 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55f6cdd08f90) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1817
#17 0x7fe709acee73 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55f6cdd92b50) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#18 0x7fe7003e1c7c in g_main_dispatch (context=0x7fe6f0005000) at
../glib-2.66.7/glib/gmain.c:3325
#19 g_main_context_dispatch (context=context@entry=0x7fe6f0005000) at
../glib-2.66.7/glib/gmain.c:4043
#20 0x7fe7003e1ef8 in g_main_context_iterate
(context=context@entry=0x7fe6f0005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
../glib-2.66.7/glib/gmain.c:4119
#21 0x7fe7003e1f8f in g_main_context_iteration (context=0x7fe6f0005000,
may_block=may_block@entry=1) at ../glib-2.66.7/glib/gmain.c:4184
#22 0x7fe709acec20 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55f6cdd8e230, flags=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:423
#23 0x7fe709a78663 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffeaf399900, flags=..., flags@entry=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x7fe709a805a0 in QCoreApplication::exec() () at

[kdeconnect] [Bug 433390] New: KDE Connect crashs after login to KDE

[Matthias Nagel]

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

Bug ID: 433390
   Summary: KDE Connect crashs after login to KDE
   Product: kdeconnect
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: matthias.h.na...@gmail.com
  Target Milestone: ---

Application: kdeconnectd (1.4.0)

Qt Version: 5.15.2
Frameworks Version: 5.77.0
Operating System: Linux 5.10.1-gentoo-r1 x86_64
Windowing system: X11
Distribution: Gentoo/Linux

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

I had logged in and were waiting for all daemons and helper programs to finish
starting.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE Connect-Dienst (kdeconnectd), signal: Segmentation fault
Content of s_kcrashErrorMessage: (null)
[KCrash Handler]
#6  0x7f1cd75f702a in
std::__atomic_base::load
(__m=std::memory_order_relaxed, this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/include/g++-v9/bits/atomic_base.h:740
#7  std::atomic::load
(__m=std::memory_order_relaxed, this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/include/g++-v9/atomic:519
#8 
QAtomicOps::loadRelaxed
(_q_value=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#9  QBasicAtomicPointer::loadRelaxed
(this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#10 QtSharedPointer::ExternalRefCountData::getAndRef
(obj=obj@entry=0x557ec6eacde0) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/tools/qsharedpointer.cpp:1396
#11 0x7f1cd8a53ebe in QWeakPointer::QWeakPointer (ptr=0x557ec6eacde0, this=0x7ffe99dfc3a0) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:679
#12 QPointer::QPointer (p=0x557ec6eacde0, this=0x7ffe99dfc3a0)
at /usr/include/qt5/QtCore/qpointer.h:62
#13 NotifyByPopupPrivate::sendNotificationToServer (this=0x557ec7040880,
notification=notification@entry=0x557ec6eacde0, notifyConfig_nocheck=...,
update=update@entry=false) at
/var/tmp/portage/kde-frameworks/knotifications-5.77.0/work/knotifications-5.77.0/src/notifybypopup.cpp:224
#14 0x7f1cd8a55e0d in NotifyByPopup::notify (notifyConfig=...,
notification=0x557ec6eacde0, this=0x557ec703f180) at
/var/tmp/portage/kde-frameworks/knotifications-5.77.0/work/knotifications-5.77.0/src/notifybypopup.cpp:125
#15 NotifyByPopup::notify (this=0x557ec703f180, notification=0x557ec6eacde0,
notifyConfig=...) at
/var/tmp/portage/kde-frameworks/knotifications-5.77.0/work/knotifications-5.77.0/src/notifybypopup.cpp:110
#16 0x7f1cd8a5601a in
NotifyByPopupPrivateoperator()
(__closure=0x557ec7041550, watcher=) at
/var/tmp/portage/kde-frameworks/knotifications-5.77.0/work/knotifications-5.77.0/src/notifybypopup.cpp:373
#17 QtPrivate::FunctorCall,
QtPrivate::List, void,
NotifyByPopupPrivate::queryPopupServerCapabilities()::
>::call (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#18
QtPrivate::Functor,
1>::call, void> (arg=,
f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#19
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List, void>::impl (which=1,
r=, ret=, a=,
this_=0x557ec7041540) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#20
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x557ec7041540, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:436
#21 0x7f1cd779c071 in QtPrivate::QSlotObjectBase::call (a=0x7ffe99dfc640,
r=0x557ec703f180, this=0x557ec7041540) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#22 doActivate (sender=0x557ec703da90, signal_index=3,
argv=0x7ffe99dfc640) at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:3886
#23 0x7f1cd779621f in QMetaObject::activate (sender=,
m=m@entry=0x7f1cd7adf5e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe99dfc640)
at
/var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:3946
#24 0x7f1cd7ac111f in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158
#25 0x7f1cd7ac1220 in QDBusPendingCallWatcherPrivate::_q_finished
(this=) at
/var/tmp/portage/dev-qt/qtdbus-5.15.2/work/qtbase-everywhere-src-5.15.2/src/dbus/qdbuspendingcall.cpp:494
#26 QDBusPendingCallWatcher::qt_static_metacall (_o=,
_c=, _id=, _a=) at
.moc/moc_qdbuspendingcall.cpp:86
#27 0x7f1cd7793ffc in QObject::event (this=0x557ec703da90,
e=0x557ec6fa9530) at

[kmail2] [Bug 411147] IMAP resource permanently offline "Cannot read password. User denied access to wallet"

[Matthias Nagel]

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

--- Comment #1 from Matthias Nagel  ---
This is the debug console output of akonadi, if I try to toggle the
online/offline state:

org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f29f01e1070) )
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7f29f01e1070) identified as
"AgentBaseChangeRecorder - 94879028254112"
org.kde.pim.imapresource: online= false
org.kde.pim.imapresource: online= true
org.kde.kgapi: Bad request, Google replied ' "{\n  \"error\":
\"invalid_grant\",\n  \"error_description\": \"Bad Request\"\n}" '
org.kde.pim.imapresource: online= false

The interesting line is from "org.kde.kgapi". As a workaround I changed the
authentication method from Google to PLAIN and now it works again. This seems
to be a regression in libkgapi.

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

[kmail2] [Bug 411147] New: IMAP resource permanently offline "Cannot read password. User denied access to wallet"

[Matthias Nagel]

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

Bug ID: 411147
   Summary: IMAP resource permanently offline "Cannot read
password. User denied access to wallet"
   Product: kmail2
   Version: 5.11.3
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: matthias.h.na...@gmail.com
  Target Milestone: ---

After upgrading to version 5.1.3 (kde-apps/kmail-19.04.3 in Gentoo) the IMAP
resource for my Gmail IMAP account is permanently offline. When I try to
restart the akonadi resource, try to toggle the online/offline state, I get the
error

"Cannot read password. User denied access to wallet."

Then the resource turns offline again.

I already have tried to re-enter the password in the settings. I also tried to
entirely delete the IMAP resource and re-create it again, in case there is some
odd configuration error. The error remains.

Interestingly, this only happens with Gmail. I have three other IMAP accounts
at different providers that all work and use Kwallet as the password storage.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.60.0
Qt Version: 5.12

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

[kile] [Bug 403857] New: Kile segfaults if adding source file from sub-directory to a project

[Matthias Nagel]

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

Bug ID: 403857
   Summary: Kile segfaults if adding source file from
sub-directory to a project
   Product: kile
   Version: 2.9.92
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: michel.lud...@kdemail.net
  Reporter: matthias.h.na...@gmail.com
  Target Milestone: ---

Application: kile (2.9.92)

Qt Version: 5.11.1
Frameworks Version: 5.52.0
Operating System: Linux 4.19.8-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
1) Create a kile project
2) Add a subdirectory to the project folder (in my case it is ./figures/)
3) Put a (La)TeX source file into the subdirectory (in my case I have each
TIKZ-figure in a seperate file in ./figures/)
4) Try to add this file to the project

KILE segfaults

Please note: It does not matter how you try to add the file to the project.
Menubar > Project > Add files, or open the file in editor and then right click
on the tab header in the editor and then select "Add to project" from the
context menu, or right click on the file in the directory view at the right and
select "Add to project" from the context menu. It always segfaults.

The crash can be reproduced every time.

-- Backtrace:
Application: Kile (kile), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8754594880 (LWP 11166))]

Thread 17 (Thread 0x7f87037fe700 (LWP 11182)):
#0  0x7f874ce9f57c in futex_wait_cancelable (private=,
expected=0, futex_word=0x5609a1f2fcf8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5609a1f2fca8,
cond=0x5609a1f2fcd0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5609a1f2fcd0, mutex=0x5609a1f2fca8) at
pthread_cond_wait.c:655
#3  0x7f87227f116b in cnd_wait (mtx=0x5609a1f2fca8, cond=0x5609a1f2fcd0) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x5609a1f32a70) at
../mesa-18.2.8/src/util/u_queue.c:256
#5  0x7f87227f0e97 in impl_thrd_routine (p=) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:87
#6  0x7f874ce9896a in start_thread (arg=0x7f87037fe700) at
pthread_create.c:463
#7  0x7f8753b481af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f8703fff700 (LWP 11181)):
#0  0x7f874ce9f57c in futex_wait_cancelable (private=,
expected=0, futex_word=0x5609a1f2fcf8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5609a1f2fca8,
cond=0x5609a1f2fcd0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5609a1f2fcd0, mutex=0x5609a1f2fca8) at
pthread_cond_wait.c:655
#3  0x7f87227f116b in cnd_wait (mtx=0x5609a1f2fca8, cond=0x5609a1f2fcd0) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x5609a1f32860) at
../mesa-18.2.8/src/util/u_queue.c:256
#5  0x7f87227f0e97 in impl_thrd_routine (p=) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:87
#6  0x7f874ce9896a in start_thread (arg=0x7f8703fff700) at
pthread_create.c:463
#7  0x7f8753b481af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f870cff9700 (LWP 11180)):
#0  0x7f874ce9f57c in futex_wait_cancelable (private=,
expected=0, futex_word=0x5609a1f2fcf8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5609a1f2fca8,
cond=0x5609a1f2fcd0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5609a1f2fcd0, mutex=0x5609a1f2fca8) at
pthread_cond_wait.c:655
#3  0x7f87227f116b in cnd_wait (mtx=0x5609a1f2fca8, cond=0x5609a1f2fcd0) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x5609a1f32650) at
../mesa-18.2.8/src/util/u_queue.c:256
#5  0x7f87227f0e97 in impl_thrd_routine (p=) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:87
#6  0x7f874ce9896a in start_thread (arg=0x7f870cff9700) at
pthread_create.c:463
#7  0x7f8753b481af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f870d7fa700 (LWP 11179)):
#0  0x7f874ce9f57c in futex_wait_cancelable (private=,
expected=0, futex_word=0x5609a1f2fcf8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5609a1f2fca8,
cond=0x5609a1f2fcd0) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5609a1f2fcd0, mutex=0x5609a1f2fca8) at
pthread_cond_wait.c:655
#3  0x7f87227f116b in cnd_wait (mtx=0x5609a1f2fca8, cond=0x5609a1f2fcd0) at
../mesa-18.2.8/src/../include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x5609a1f302d0) at

[kmail2] [Bug 215663] Composer/HTML mode: indentation increase doesn't work

[Matthias Nagel]

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

Matthias Nagel  changed:

   What|Removed |Added

 CC||matthias.h.na...@gmail.com

--- Comment #9 from Matthias Nagel  ---
Please rename the command/tool tip as suggested. Something like
"Increase/Decrease List Level" sounds good. This should be an easy, quick fix
and helps to reduce the confusion.

Additionally, one might consider to enable the command if and only if the
cursor is placed inside a list and deactivate the command otherwise. This would
force the user to create a list first and could lessen confusion further.

Nonetheless, there should be also a feature to create left (and right)
indention without a blocklist. There are two other feature requests that are
loosely related, see bugs #341961 and #362493.

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

[kmail2] [Bug 362493] quoting with blockquote

[Matthias Nagel]

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

Matthias Nagel  changed:

   What|Removed |Added

 CC||matthias.h.na...@gmail.com

--- Comment #1 from Matthias Nagel  ---
I am in support of this feature.

If this feature is implemented, I would prefer to have  not only
for replying or relaying other mails but also to be able to insert custom
 with the tool bar.

I often discuss 3rd party literature via mail and having a feature like this
would help to distinguish between my own text and the citation.

There is a loosely related feature request that asks for real left indention of
paragraphs without unintentionally creating a bullet list. See bug #341961.

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

[kmail2] [Bug 341961] Feature request: Real increase/ decrease indend

[Matthias Nagel]

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

Matthias Nagel  changed:

   What|Removed |Added

   Platform|Fedora RPMs |Gentoo Packages
Version|4.14.2  |5.9.1

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

[kmail2] [Bug 341961] Feature request: Real increase/ decrease indend

[Matthias Nagel]

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

Matthias Nagel  changed:

   What|Removed |Added

 CC||matthias.h.na...@gmail.com

--- Comment #1 from Matthias Nagel  ---
Using the command "increase indent" from the menu bar intentionally creates a
bullet list. The name is misleading. It should be something like
"Increase/decrease nested list level". See this bug #215663.

Nonetheless, I support this feature request. Real indention is actually a
missing feature. For example, I often discuss 3rd party literature via mail and
having a feature like this would help to distinguish between my own text and
citations.

However, I would not use the HTML tag  but prefer something like 

[plasmashell] [Bug 373393] Plasmashell crashes with signal 11 (SIGSEGV)

[Matthias Nagel]

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

Matthias Nagel <matthias.h.na...@gmail.com> changed:

   What|Removed |Added

Version|5.7.5   |5.8.3

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

[plasmashell] [Bug 373393] Plasmashell crashes with signal 11 (SIGSEGV)

[Matthias Nagel]

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

--- Comment #2 from Matthias Nagel <matthias.h.na...@gmail.com> ---
Created attachment 102977
  --> https://bugs.kde.org/attachment.cgi?id=102977=edit
Backtrace #2

This crash still happens with 5.8.3-r4. I uploaded a fresh back trace.

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

[plasmashell] [Bug 373393] New: Plasmashell crashes with signal 11 (SIGSEGV)

[Matthias Nagel]

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

Bug ID: 373393
   Summary: Plasmashell crashes with signal 11 (SIGSEGV)
   Product: plasmashell
   Version: 5.7.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: matthias.h.na...@gmail.com
  Target Milestone: 1.0

Created attachment 102672
  --> https://bugs.kde.org/attachment.cgi?id=102672=edit
Backtrace

Plasmashell crashes with SIGSEGV after some random time, usually within the
first half hour after login.

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

[kactivitymanagerd] [Bug 362757] kactivitymanagerd crashes with segfault (usually during or shortly after login)

[Matthias Nagel]

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

--- Comment #11 from Matthias Nagel <matthias.h.na...@gmail.com> ---
Given the new insight that the X server causes the exit, shall I still report
upstream at https://bugreports.qt.io/ or report at http://bugs.freedesktop.org
and file a bug against the X server?

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

[kactivitymanagerd] [Bug 362757] kactivitymanagerd crashes with segfault (usually during or shortly after login)

[Matthias Nagel]

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

--- Comment #8 from Matthias Nagel <matthias.h.na...@gmail.com> ---
Created attachment 102620
  --> https://bugs.kde.org/attachment.cgi?id=102620=edit
Backtrace #5

kde-plasma/kactivitymanagerd-5.7.5

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

[kactivitymanagerd] [Bug 362757] kactivitymanagerd crashes with segfault (usually during or shortly after login)

[Matthias Nagel]

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

Matthias Nagel <matthias.h.na...@gmail.com> changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #7 from Matthias Nagel <matthias.h.na...@gmail.com> ---
Anybody working on this? I still see the crashes. I will upload a new backtrace
of a fresh core dump from this day.

No, no errors in .xsession-errors, fresh user home directory, no legacy stuff
from KDE 4 or anything like this. Just a crashing activitymanager

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

[kontact] [Bug 372034] Kontact crashes with segmentation fault when a mail from the message list is selected

[Matthias Nagel]

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

--- Comment #2 from Matthias Nagel <matthias.h.na...@gmail.com> ---
Some snippet from .xsession-error:

kontact:
/var/tmp/portage/x11-libs/libdrm-2.4.70/work/libdrm-2.4.70/nouveau/pushbuf.c:727:
nouveau_pushbuf_data: Assertion »kref« failed.
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
[1105/184917:ERROR:gles2_cmd_decoder.cc(2109)]
[.CommandBufferContext.RenderWorker-0x1a44370]GL ERROR :GL_OUT_OF_MEMORY :
ScopedTextureBinder::dtor: <- error from previous GL command
[1105/184917:ERROR:gles2_cmd_decoder.cc(4471)] Error: 5 for Command
kCopySubTextureCHROMIUM
[1105/184917:ERROR:gles2_cmd_decoder.cc(3579)]   GLES2DecoderImpl: Trying to
make lost context current.
KCrash: Application 'kontact' crashing...

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

[plasma-nm] [Bug 372086] New: Make configuration option for LZO compression of OpenVPN connection tri-state

[Matthias Nagel]

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

Bug ID: 372086
   Summary: Make configuration option for LZO compression of
OpenVPN connection tri-state
   Product: plasma-nm
   Version: 5.8.3
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: lu...@kde.org
  Reporter: matthias.h.na...@gmail.com
CC: jgrul...@redhat.com
  Target Milestone: ---

The graphical editor has a checkbox to either enable or disable the LZO
compression of OpenVPN connections. This option is translats to "comp-lzo=no"
or "comp-lzo=yes" respectively in the corresponding configuration file under
/etc/NetworkManager/. At the level of OpenVPN this corresponds to the equally
named option.

Howerver, this option is tri-state and can be left unconfigured which has a
different meaning than "yes" or "no". See man page of OpenVPN.

If at the client side either "comp-lzo=no" or "comp-lzo=yes" and at the server
side the configuration is left unspecified under certain conditions the
connection can be successfully established but become useless due to LZO errors

Nov 03 21:09:56 nm-openvpn[17410]: OpenVPN 2.3.12 x86_64-pc-linux-gnu [SSL
(OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Oct 30 2016
Nov 03 21:09:56 nm-openvpn[17410]: library versions: OpenSSL 1.0.2j  26 Sep
2016, LZO 2.08
Nov 03 21:09:57 nm-openvpn[17410]: NOTE: the current --script-security setting
may allow this configuration to call user-defined scripts
Nov 03 21:09:57 nm-openvpn[17410]: NOTE: UID/GID downgrade will be delayed
because of --client, --pull, or --up-delay
Nov 03 21:09:57 nm-openvpn[17410]: Attempting to establish TCP connection with
[AF_INET]193.197.62.25:1194 [nonblock]
Nov 03 21:09:58 nm-openvpn[17410]: TCP connection established with
[AF_INET]193.197.62.25:1194
Nov 03 21:09:58 nm-openvpn[17410]: TCPv4_CLIENT link local: [undef]
Nov 03 21:09:58 nm-openvpn[17410]: TCPv4_CLIENT link remote:
[AF_INET]193.197.62.25:1194
Nov 03 21:09:59 nm-openvpn[17410]: WARNING: 'comp-lzo' is present in local
config but missing in remote config, local='comp-lzo'
Nov 03 21:09:59 nm-openvpn[17410]: [openvpn.scc.kit.edu] Peer Connection
Initiated with [AF_INET]193.197.62.25:1194
Nov 03 21:10:01 nm-openvpn[17410]: TUN/TAP device tap0 opened
Nov 03 21:10:01 nm-openvpn[17410]:
/usr/libexec/nm-openvpn-service-openvpn-helper --debug 0 17403 --bus-name
org.freedesktop.NetworkManager.openvpn.Connection_1 --tap -- tap0 1500 1592
141.3.200.95 255.255.255.0 init
Nov 03 21:10:01 nm-openvpn[17410]: GID set to nm-openvpn
Nov 03 21:10:01 nm-openvpn[17410]: UID set to nm-openvpn
Nov 03 21:10:01 nm-openvpn[17410]: Initialization Sequence Completed
Nov 03 21:10:01 nm-openvpn[17410]: Bad LZO decompression header byte: 255
Nov 03 21:10:01 nm-openvpn[17410]: Bad LZO decompression header byte: 255
Nov 03 21:10:01 nm-openvpn[17410]: Bad LZO decompression header byte: 255
Nov 03 21:10:01 nm-openvpn[17410]: Bad LZO decompression header byte: 51


This behaviour is expected and reproducible.

If one edits the configuration file under /etc/NetworkManager/ manually be
means of a text editor and removes the "comp-lzo=" directive from the
configuration file, everything works as expected. However, as soon as one opens
the connection in the graphical connection editor again, the "comp-lzo"
directive is re-inserted into the configuration file and set to whatever the
checkbox state is in. After that the OpenVPN connection does not work and one
must edit the configuration file again.

Proposed solution: Make the checkbox tri-state.

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

[kontact] [Bug 372034] Kontact crashes with segmentation fault when a mail from the message list is selected

[Matthias Nagel]

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

--- Comment #1 from Matthias Nagel <matthias.h.na...@gmail.com> ---
This is the dmesg output:

[   61.624346] nouveau :01:00.0: kontact[1214]: Unknown handle 0x0017
[   61.624355] nouveau :01:00.0: kontact[1214]: validate_init
[   61.624359] nouveau :01:00.0: kontact[1214]: validate: -2
[   64.845955] nouveau :01:00.0: kontact[1214]: Unknown handle 0x0014
[   64.845966] nouveau :01:00.0: kontact[1214]: validate_init
[   64.845971] nouveau :01:00.0: kontact[1214]: validate: -2

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

[kontact] [Bug 372034] Kontact crashes with segmentation fault when a mail from the message list is selected

[Matthias Nagel]

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

Matthias Nagel <matthias.h.na...@gmail.com> changed:

   What|Removed |Added

Summary|Kontact crashes with|Kontact crashes with
   |segmentation fault when a   |segmentation fault when a
   |mail from the message list  |mail from the message list
   ||is selected

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

[kontact] [Bug 372034] New: Kontact crashes with segmentation fault when a mail from the message list

[Matthias Nagel]

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

Bug ID: 372034
   Summary: Kontact crashes with segmentation fault when a mail
from the message list
   Product: kontact
   Version: 5.3.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: matthias.h.na...@gmail.com
  Target Milestone: ---

Created attachment 102012
  --> https://bugs.kde.org/attachment.cgi?id=102012=edit
Backtrace

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.4.26-gentoo x86_64
Distribution (Platform): Gentoo Packages

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

Select a mail from the message list. Kontact tries to show the mail in the
preview window below the message list. Kontact crashes.

After that I experience a lot of display flicker and disturbances across the
whole desktop and other applications (for example in Firefox). Plasma Desktop
effects do not work as expected anymore. Therefore I believe the bug is somehow
related to the graphics stack.

The crash can be reproduced sometimes.

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

[plasmashell] [Bug 363543] New: Gtk-WARNING: Theme directory [...] of theme breeze has no size field

[Matthias Nagel via KDE Bugzilla]

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

Bug ID: 363543
   Summary: Gtk-WARNING: Theme directory [...] of theme breeze has
no size field
   Product: plasmashell
   Version: 5.6.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Theme - Breeze
  Assignee: visual-des...@kde.org
  Reporter: mh-na...@web.de
CC: plasma-b...@kde.org

I use KDE Apps 15.12.3, KF 5.22.0 and Plasma 5.6.4, especially Breeze GTK
5.6.5. If I start an application that is based on GTK, e.g. Gimp, Firefox, the
.xsession-error file is filled with error messages like

Gtk-WARNING: Theme directory [...] of theme breeze has no size field

More precisely there are

Gtk-WARNING **: Theme directory actions/48 of theme breeze has no size field
Gtk-WARNING **: Theme directory categories/16 of theme breeze has no size field 
Gtk-WARNING **: Theme directory categories/22 of theme breeze has no size field 
Gtk-WARNING **: Theme directory categories/48 of theme breeze has no size field 
Gtk-WARNING **: Theme directory devices/48 of theme breeze has no size field

However, the particular directories depend on the specific GTK-based
application.

Gentoo Bug mainters ask me to report this bug upstream (Bug report at Gentoo:
https://bugs.gentoo.org/show_bug.cgi?id=583898)

Reproducible: Always

Steps to Reproduce:
1. Use Breeze as a GTK theme
2. Start some GTK-based application
3. Look at ~/.xsession-error

Actual Results:  
~/.xsession-error is filled with errors about missing size information for
icons from the Breeze theme

Expected Results:  
No error messages.

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

[kdepim] [Bug 362317] Some dialogs from various KDE PIM applications 16.04. freeze when being opened

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #5 from Matthias Nagel <mh-na...@web.de> ---
Created attachment 98857
  --> https://bugs.kde.org/attachment.cgi?id=98857=edit
xsession-errors after kontact tried to open the confirmation dialog to delete
emails

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

[korgac] [Bug 362317] Some dialogs from various KDE PIM applications 16.04. freeze when being opened

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #4 from Matthias Nagel <mh-na...@web.de> ---
Created attachment 98826
  --> https://bugs.kde.org/attachment.cgi?id=98826=edit
Backtrace of frozen kmail2 while attempting to show dialog to discard mail

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

[korgac] [Bug 362317] Some dialogs from various KDE PIM applications 16.04. freeze when being opened

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #3 from Matthias Nagel <mh-na...@web.de> ---
The same bug causes an "infinite" loop. A started to compose a new email and
now want to discard it, i.e. close the composer window without sending it. A
dialog pops up that is supposed to ask me if I am sure, but unfortunately this
dialog is affected by this bug, too. Hence, korgac/kmail2 freezes and the only
solution is to kill the process. Unfortunately, on the next start the new email
and the composer window are still there and restored. So at the moment, there
is no way to close the composer window. (Workaround: Send the email to some
dummy email address instead of the intended receiver in order to satisfy
kmail2.)

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

[kactivitymanagerd] [Bug 362757] kactivitymanagerd crashes with segfault (usually during or shortly after login)

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #4 from Matthias Nagel <mh-na...@web.de> ---
Created attachment 98818
  --> https://bugs.kde.org/attachment.cgi?id=98818=edit
Backtrace #4

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

[kactivitymanagerd] [Bug 362757] kactivitymanagerd crashes with segfault (usually during or shortly after login)

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #3 from Matthias Nagel <mh-na...@web.de> ---
Created attachment 98817
  --> https://bugs.kde.org/attachment.cgi?id=98817=edit
Backtrace #3 (fresh and empty user profile)

This backtrace was taken from a core dump that was generated during the first
login of a freshly created user with an empty home directory.

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

[kactivitymanagerd] [Bug 362757] kactivitymanagerd crashes with segfault (usually during or shortly after login)

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #2 from Matthias Nagel <mh-na...@web.de> ---
Created attachment 98816
  --> https://bugs.kde.org/attachment.cgi?id=98816=edit
Backtrace #2

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

[kactivitymanagerd] [Bug 362757] kactivitymanagerd crashes with segfault (usually during or shortly after login)

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #1 from Matthias Nagel <mh-na...@web.de> ---
Created attachment 98815
  --> https://bugs.kde.org/attachment.cgi?id=98815=edit
Backtrace #1

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

[kactivitymanagerd] [Bug 362757] New: kactivitymanagerd crashes with segfault (usually during or shortly after login)

[Matthias Nagel via KDE Bugzilla]

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

Bug ID: 362757
   Summary: kactivitymanagerd crashes with segfault (usually
during or shortly after login)
   Product: kactivitymanagerd
   Version: 5.6.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: mh-na...@web.de
CC: plasma-b...@kde.org

activitymanagerd 5.6.3 crashes with segmentation fault

Reproducible: Sometimes

Steps to Reproduce:
1. Login, wait and see if core dump is generated ;-)

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

[korgac] [Bug 362317] Some dialogs from various KDE PIM applications 16.04. freeze when being opened

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #2 from Matthias Nagel <mh-na...@web.de> ---
Created attachment 98626
  --> https://bugs.kde.org/attachment.cgi?id=98626=edit
Backtrace of frozen korgac

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

[korgac] [Bug 362317] Some dialogs from various KDE PIM applications 16.04. freeze when being opened

[Matthias Nagel via KDE Bugzilla]

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

--- Comment #1 from Matthias Nagel <mh-na...@web.de> ---
Created attachment 98625
  --> https://bugs.kde.org/attachment.cgi?id=98625=edit
Screenshot of frozen korgac

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

[korgac] [Bug 362317] New: Some dialogs from various KDE PIM applications 16.04. freeze when being opened

[Matthias Nagel via KDE Bugzilla]

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

Bug ID: 362317
   Summary: Some dialogs from various KDE PIM applications 16.04.
freeze when being opened
   Product: korgac
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: korganizer-de...@kde.org
  Reporter: mh-na...@web.de

i have installed the KDE PIM suite version 16.04.0 on two different boxes. The
first box is a clean install (no upgrade from a former KDE 4 installation), the
second box is an upgrade and the home profiles are populated with config files
from a previous KDE 4 installation. This crash only occurs on the box that has
been upgraded, but there it occurs always, reproducibly and steadily.

Several dialogs from various KDE PIM applications make the whole application
crash/freeze when those dialogs are shown. The respective dialogs are not
rendered properly but only the outer frame is drawn and the background is still
visible. (See attached screen shot.) The dialog cannot be closed, the
application is frozen and after some time-out the another dialog pops up with
the message "The application [...] does not respond. Kill or wait longer?".

The affected dialogs are the reminder dialog of korgac, the delete confirmation
dialog of kmail2, the delete confirmation dialog of akregator, the color
configuration dialog for subscribed calenders within korganizer, the new
calender wizard of korganizer and probably some more I have not found yet. The
behaviour is always reproducible. 

The attached backtrace was taken from korgac diretly after login while korgac
was hanging infinitely. (Same situation as depicted in screenshot.)

Reproducible: Always

Steps to Reproduce:
1a. Wait for korgac reminder dialog to pop up, or
1b. delete an email in kmail2, or
1c. delete a news feed in akregator, or
1d. configure a color of a subscribed calendar in korganzizer 
2. The following dialog is not rendered properly and freezes the application

Actual Results:  
Application freezes and must be killed.

Expected Results:  
A correctly rendered dialog.

I appointed a "grave" for severity and not only "crash", because of the
plurality of dialogs that are affected. At the moment each component of the PIM
suite seems to be affected and is unusable.

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