[kdelibs] [Bug 212268] Writing a HTML message it produces paragraphs without margins.

[Mike Goodwin]

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

--- Comment #4 from Mike Goodwin  ---
Possibly related: https://bugs.kde.org/show_bug.cgi?id=358476

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

[kdelibs] [Bug 212268] Writing a HTML message it produces paragraphs without margins.

[Mike Goodwin]

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

Mike Goodwin  changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

--- Comment #3 from Mike Goodwin  ---
This bug is absolutely still valid and has been for some 10 years..


It makes sending/receiving HTML emails a chore in the workplace because if you
use KMail to do it, your emails look like they're written by a child. (i.e.
unprofessional)


Example Business email:

---
Hi Mark,

Thanks for sending me that info


Regards,

- Mike



Becomes:


Hi Mark,
Thanks for sending me that info
Regads,
- Mike



When read by any modern client (for me Outlook, Roundcube, Rainloop and Gmail
all render Kmail's sent HTML like this)

There are also numerous reports on the forums about this issue.


Is there any way we can get this bug to the right place to finally gain some
traction? It's really the only thing left in my personal list of wants that
KMail needs for me to use it exclusively (right now if I'm not sending TEXT
email, I have to go use rainloop if I want properly formatted emails). I'm
truly baffled as to how this is still a bug.


Here's an updated list of possibly related software versions that the bug can
be bumped to:


kdepim-addons-18.08.3-1.fc29.x86_64
kdepim-runtime-libs-18.08.3-1.fc29.x86_64
kf5-libkdepim-18.08.3-1.fc29.x86_64
kdepim-apps-libs-18.08.3-1.fc29.x86_64
kf5-kmailtransport-akonadi-18.08.3-1.fc29.x86_64
kdepim-runtime-18.08.3-1.fc29.x86_64
kmail-libs-18.08.3-1.fc29.x86_64
kf5-libkdepim-akonadi-18.08.3-1.fc29.x86_64
kf5-kmailtransport-18.08.3-1.fc29.x86_64
kdepimlibs-4.14.10-29.fc29.x86_64
kdepimlibs-gpgme-4.14.10-29.fc29.x86_64
kdepimlibs-kxmlrpcclient-4.14.10-29.fc29.x86_64
kdepim-common-17.12.3-2.fc29.x86_64
kmail-account-wizard-18.08.3-1.fc29.x86_64
kdepimlibs-akonadi-4.14.10-29.fc29.x86_64
kmail-18.08.3-1.fc29.x86_64

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

[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0

[Mike Goodwin]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

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

[plasmashell] [Bug 386259] New: Plasma crashes in wayland when mousing-over application menu

[Mike Goodwin]

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

Bug ID: 386259
   Summary: Plasma crashes in wayland when mousing-over
application menu
   Product: plasmashell
   Version: 5.10.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: m...@mgoodwin.net
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.39.0
Operating System: Linux 4.13.9-300.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

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

Using the application menu while in a wayland session. 

It seems to be reproducible by:

1. Assigning an application menu plasmoid to a panel.
2. Click the button to open menu
3. Mouse over from top to bottom the items like "multimedia," "internet," etc. 
4. Plasma will crash with this backtrace

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

Thread 13 (Thread 0x7f3b6700 (LWP 16272)):
[KCrash Handler]
#6  0x7f3c26c1aea0 in wl_proxy_create_wrapper (proxy=0x0) at
src/wayland-client.c:2038
#7  0x7f3b7f9cf2c1 in dri2_wl_create_window_surface () at
/lib64/libEGL_mesa.so.0
#8  0x7f3b7f9bc857 in _eglCreateWindowSurfaceCommon () at
/lib64/libEGL_mesa.so.0
#9  0x7f3c080fca7d in
QtWaylandClient::QWaylandEglWindow::updateSurface(bool) () at
/usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so
#10 0x7f3c080faff5 in
QtWaylandClient::QWaylandGLContext::makeCurrent(QPlatformSurface*) () at
/usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so
#11 0x7f3c29550e3e in QOpenGLContext::makeCurrent(QSurface*) () at
/lib64/libQt5Gui.so.5
#12 0x7f3c2d780544 in QSGRenderThread::invalidateOpenGL(QQuickWindow*,
bool, QOffscreenSurface*) () at /lib64/libQt5Quick.so.5
#13 0x7f3c2d787e2b in QSGRenderThread::event(QEvent*) () at
/lib64/libQt5Quick.so.5
#14 0x7f3c2d7870b7 in QSGRenderThread::processEventsAndWaitForMore() () at
/lib64/libQt5Quick.so.5
#15 0x7f3c2d78748a in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5
#16 0x7f3c28976176 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#17 0x7f3c27048609 in start_thread () at /lib64/libpthread.so.0
#18 0x7f3c27d17e6f in clone () at /lib64/libc.so.6

Thread 12 (Thread 0x7f3b4cad9700 (LWP 16271)):
#0  0x7f3c270523ad in __lll_lock_wait () at /lib64/libpthread.so.0
#1  0x7f3c2704b153 in pthread_mutex_lock () at /lib64/libpthread.so.0
#2  0x7f3b7f9c0a25 in eglSwapInterval () at /lib64/libEGL_mesa.so.0
#3  0x7f3c080fc1f6 in
QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) () at
/usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so
#4  0x7f3c29550822 in QOpenGLContext::swapBuffers(QSurface*) () at
/lib64/libQt5Gui.so.5
#5  0x7f3c2d782583 in QSGRenderThread::syncAndRender() () at
/lib64/libQt5Quick.so.5
#6  0x7f3c2d787448 in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5
#7  0x7f3c28976176 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f3c27048609 in start_thread () at /lib64/libpthread.so.0
#9  0x7f3c27d17e6f in clone () at /lib64/libc.so.6

Thread 11 (Thread 0x7f3b31cee700 (LWP 29763)):
#0  0x7f3c2704ec3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3c2897681b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f3c2d787028 in QSGRenderThread::processEventsAndWaitForMore() () at
/lib64/libQt5Quick.so.5
#3  0x7f3c2d78748a in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5
#4  0x7f3c28976176 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f3c27048609 in start_thread () at /lib64/libpthread.so.0
#6  0x7f3c27d17e6f in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7f3b325ef700 (LWP 29760)):
#0  0x7f3c2704ec3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f3c2897681b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f3c2d787028 in QSGRenderThread::processEventsAndWaitForMore() () at
/lib64/libQt5Quick.so.5
#3  0x7f3c2d78748a in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5
#4  0x7f3c28976176 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f3c27048609 in start_thread () at /lib64/libpthread.so.0
#6  0x7f3c27d17e6f in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f3b4dedb700 (LWP 29753)):
#0  0x7f3c2704ec3b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  

[konversation] [Bug 386022] New: Konversation segfaults when closed from system tray

[Mike Goodwin]

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

Bug ID: 386022
   Summary: Konversation segfaults when closed from system tray
   Product: konversation
   Version: 1.7.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: m...@mgoodwin.net
  Target Milestone: ---

Application: konversation (1.7.2)

Qt Version: 5.9.2
Frameworks Version: 5.39.0
Operating System: Linux 4.13.6-300.fc27.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

Messing around with settings, then I wanted to close konversation from the tray
menu after the "are you sure you want to close" dialog, it closed then drkonqi
appeared 

- Custom settings of the application:

Colors, layout.. you name it.

-- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
27return SYSCALL_CANCEL (nanosleep, requested_time, remaining);
[Current thread is 1 (Thread 0x7f9e43267940 (LWP 19238))]

Thread 2 (Thread 0x7f9e1fa07700 (LWP 19365)):
#0  0x7f9e3b4bdc0b in __GI___poll (fds=0x7f9e18026180, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f9e33e23ed9 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f9e18026180, timeout=, context=0x7f9e18000be0)
at gmain.c:4187
#2  0x7f9e33e23ed9 in g_main_context_iterate
(context=context@entry=0x7f9e18000be0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3881
#3  0x7f9e33e23fec in g_main_context_iteration (context=0x7f9e18000be0,
may_block=1) at gmain.c:3947
#4  0x7f9e3c31047b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f9e3c2c1aea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f9e3c12402a in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f9e3c727c85 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#8  0x7f9e3c128036 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f9e398b0609 in start_thread (arg=0x7f9e1fa07700) at
pthread_create.c:465
#10 0x7f9e3b4ca1bf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f9e43267940 (LWP 19238)):
[KCrash Handler]
#6  0x556b7488f6c0 in  ()
#7  0x7f9e41c040a6 in
qDeleteAll::const_iterator>(QList::const_iterator,
QList::const_iterator) (end=..., begin=...) at
/usr/include/qt5/QtCore/qalgorithms.h:320
#8  0x7f9e41c040a6 in qDeleteAll
>(QList const&) (c=...) at
/usr/include/qt5/QtCore/qalgorithms.h:328
#9  0x7f9e41c040a6 in NotifyByAudio::~NotifyByAudio() (this=0x556b71330d40,
__in_chrg=) at
/usr/src/debug/kf5-knotifications-5.39.0-1.fc27.x86_64/src/notifybyaudio.cpp:46
#10 0x7f9e41c04149 in NotifyByAudio::~NotifyByAudio() (this=0x556b71330d40,
__in_chrg=) at
/usr/src/debug/kf5-knotifications-5.39.0-1.fc27.x86_64/src/notifybyaudio.cpp:48
#11 0x7f9e3c2efb68 in QObjectPrivate::deleteChildren() () at
/lib64/libQt5Core.so.5
#12 0x7f9e3c2f09c8 in QObject::~QObject() () at /lib64/libQt5Core.so.5
#13 0x7f9e41bde189 in
KNotificationManagerSingleton::~KNotificationManagerSingleton()
(this=, __in_chrg=) at
/usr/src/debug/kf5-knotifications-5.39.0-1.fc27.x86_64/src/knotificationmanager.cpp:61
#14 0x7f9e41bde189 in (anonymous
namespace)::Q_QGS_s_self::Holder::~Holder() (this=,
__in_chrg=) at
/usr/src/debug/kf5-knotifications-5.39.0-1.fc27.x86_64/src/knotificationmanager.cpp:67
#15 0x7f9e3b3ebb88 in __run_exit_handlers (status=0, listp=0x7f9e3b78f6f8
<__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at exit.c:83
#16 0x7f9e3b3ebbda in __GI_exit (status=) at exit.c:105
#17 0x7f9e3b3d1041 in __libc_start_main (main=0x556b6e4d64a0 ,
argc=1, argv=0x7ffc220c7938, init=, fini=,
rtld_fini=, stack_end=0x7ffc220c7928) at ../csu/libc-start.c:342
#18 0x556b6e4e6cba in _start ()

Reported using DrKonqi

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

[konversation] [Bug 386020] New: Zoom (ctrl + scroll) changes font from configured to default

[Mike Goodwin]

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

Bug ID: 386020
   Summary: Zoom (ctrl + scroll) changes font from configured to
default
   Product: konversation
   Version: 1.7.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ircview
  Assignee: argo...@gmail.com
  Reporter: m...@mgoodwin.net
CC: konversation-de...@kde.org
  Target Milestone: ---

Title basically says it all. In my case I have a monospace font configured, and
when I scroll with ctrl+wheel it changes the font from monospace to the default
font which is sans. 

Platform: Fedora 27
Qt Version: 5.9.2
Konversation: 1.7.2

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

[plasmashell] [Bug 366062] Icons for Electron apps are too large in the System Tray

[Mike Goodwin]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

--- Comment #18 from Mike Goodwin <m...@mgoodwin.net> ---
This has been an ongoing problem for quite some time.

Currently, on Fedora 25, 26, 27, The following apps that I use are affected
causing my tray to look horrendous:

1. RocketChat+ - Electron
2. Riot - Electron
3. Wire - Electron
4. Keepass <- This one is NOT electron. (mono)

Please fix this.

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

[kmail2] [Bug 385033] New: Kmail fails to start (unknown condition)

[Mike Goodwin]

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

Bug ID: 385033
   Summary: Kmail fails to start (unknown condition)
   Product: kmail2
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: m...@mgoodwin.net
  Target Milestone: ---

Application: kmail (5.5.1)

Qt Version: 5.7.1
Frameworks Version: 5.36.0
Operating System: Linux 4.12.13-300.fc26.x86_64 x86_64
Distribution: "Fedora release 26 (Twenty Six)"

-- Information about the crash:
This happens when I attempt to start kmail from the application menu, and
immediately a drkonqi window appears.

Using Fedora 26

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f91f7e9d940 (LWP 25117))]

Thread 21 (Thread 0x7f9196ffd700 (LWP 25148)):
#0  0x7f91f96df89c in srb_callback () at
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#1  0x7f91f96e011f in srbchannel_rwloop () at
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#2  0x7f91fb5ca7f8 in pa_mainloop_dispatch () at /lib64/libpulse.so.0
#3  0x7f91fb5cabce in pa_mainloop_iterate () at /lib64/libpulse.so.0
#4  0x7f91fb5cac50 in pa_mainloop_run () at /lib64/libpulse.so.0
#5  0x7f91fb5d8ab9 in thread () at /lib64/libpulse.so.0
#6  0x7f91f96f0078 in internal_thread_func () at
/usr/lib64/pulseaudio/libpulsecommon-10.0.so
#7  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#8  0x7f921a328bbf in clone () at /lib64/libc.so.6

Thread 20 (Thread 0x7f91977fe700 (LWP 25147)):
#0  0x7f921627fe0a in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f920da58172 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f920da1f38e in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#3  0x7f920d9f9fab in
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f920d9f6828 in base::MessageLoop::RunHandler() () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f920da1326b in base::RunLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#6  0x7f920da2af66 in base::Thread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#7  0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#8  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#9  0x7f921a328bbf in clone () at /lib64/libc.so.6

Thread 19 (Thread 0x7f9197fff700 (LWP 25146)):
#0  0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f920e1a7ea0 in cc::SingleThreadTaskGraphRunner::Run() () at
/lib64/libQt5WebEngineCore.so.5
#2  0x7f920da2a9a1 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#5  0x7f921a328bbf in clone () at /lib64/libc.so.6

Thread 18 (Thread 0x7f91ad7fa700 (LWP 25145)):
#0  0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f920da29725 in
base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*)
() at /lib64/libQt5WebEngineCore.so.5
#2  0x7f920da29c07 in base::SequencedWorkerPool::Worker::Run() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f920da2a9a1 in base::SimpleThread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#6  0x7f921a328bbf in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f91acff9700 (LWP 25144)):
#0  0x7f921627f90b in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f920da1f409 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () at /lib64/libQt5WebEngineCore.so.5
#2  0x7f920da1f437 in base::WaitableEvent::Wait() () at
/lib64/libQt5WebEngineCore.so.5
#3  0x7f920d9f9f5b in
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#4  0x7f920d9f6828 in base::MessageLoop::RunHandler() () at
/lib64/libQt5WebEngineCore.so.5
#5  0x7f920da1326b in base::RunLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#6  0x7f920da2af66 in base::Thread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#7  0x7f920da2706b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#8  0x7f921627936d in start_thread () at /lib64/libpthread.so.0
#9  

[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.

[Mike Goodwin]

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

--- Comment #9 from Mike Goodwin <m...@mgoodwin.net> ---
By the way I'm on:

Plasma 5.8.5
kf5 5.29
kdepim 16.08

And will continue to be on the latest of what rdieter is doing with Fedora 25+

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

[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.

[Mike Goodwin]

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

--- Comment #8 from Mike Goodwin <m...@mgoodwin.net> ---
I still have this bug I just don't login to this bug tracker very often, and I
worked around it so I stopped being annoyed by it. 

If you configure an IDLE account and disable "Interval mail checking" it
basically stops working after it times out, and doesn't reconnect the IDLE
session. 

Thus, I have interval mail checking set at about 20 minutes and that seems to
mostly work ok.

However, My phone using K9 _always_ receives mail instantly via IDLE (because I
can hear the alert) and it takes a substantial amount of time for Kmail to show
the same notification on my computer (both of mine) 

I'm pretty sure most of the time It's just waiting the 20 minutes to check of
I'm between checking intervals, so IDLE is probably doing nothing for me still.

I'd be willing to work with anyone but I'm not sure where else to progress the
bug on my own. I clearly have a configuration and server that is prone to this
issue, but again other clients like K9 work flawlessly.

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

[plasmashell] [Bug 374349] New: Plasma crashes (and restarts) when restarting Atom text editor

[Mike Goodwin]

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

Bug ID: 374349
   Summary: Plasma crashes (and restarts) when restarting Atom
text editor
   Product: plasmashell
   Version: 5.8.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: m...@mgoodwin.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.15-300.fc25.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

I updated some atom plugins, and it asked me to restart atom, so I pressed the
"restart atom" button, and the restart of atom caused plasma to crash and
restart itself.

The crash can be reproduced sometimes.

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

Thread 28 (Thread 0x7f8a050f3700 (LWP 24629)):
#0  0x7fcb23806460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcb250c305a in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7fcb28d238c5 in QSGRenderThread::processEventsAndWaitForMore() ()
from /lib64/libQt5Quick.so.5
#3  0x7fcb28d241ba in QSGRenderThread::run() () from
/lib64/libQt5Quick.so.5
#4  0x7fcb250c29da in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7fcb238006ca in start_thread () from /lib64/libpthread.so.0
#6  0x7fcb244b5f7f in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f8a058f4700 (LWP 24628)):
#0  0x7fcb244a5bed in read () from /lib64/libc.so.6
#1  0x7fcb192510d1 in pa_read () from
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#2  0x7fcb19aea33e in pa_mainloop_prepare () from /lib64/libpulse.so.0
#3  0x7fcb19aeadb0 in pa_mainloop_iterate () from /lib64/libpulse.so.0
#4  0x7fcb19aeae70 in pa_mainloop_run () from /lib64/libpulse.so.0
#5  0x7fcb19af8e99 in thread () from /lib64/libpulse.so.0
#6  0x7fcb19280178 in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-9.0.so
#7  0x7fcb238006ca in start_thread () from /lib64/libpthread.so.0
#8  0x7fcb244b5f7f in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f8a06afd700 (LWP 24627)):
#0  0x7fcb244aa01d in poll () from /lib64/libc.so.6
#1  0x7fcb1d24f156 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fcb1d24f26c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fcb252b073b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7fcb2526173a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7fcb250be5f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7fcb2832c4e5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7fcb250c29da in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7fcb238006ca in start_thread () from /lib64/libpthread.so.0
#9  0x7fcb244b5f7f in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f8a077fe700 (LWP 5280)):
#0  0x7fcb23806460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcb250c305a in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7fcb28d238c5 in QSGRenderThread::processEventsAndWaitForMore() ()
from /lib64/libQt5Quick.so.5
#3  0x7fcb28d241ba in QSGRenderThread::run() () from
/lib64/libQt5Quick.so.5
#4  0x7fcb250c29da in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7fcb238006ca in start_thread () from /lib64/libpthread.so.0
#6  0x7fcb244b5f7f in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7f8a07fff700 (LWP 3528)):
#0  0x7fcb23806460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcb250c305a in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7fcb28d238c5 in QSGRenderThread::processEventsAndWaitForMore() ()
from /lib64/libQt5Quick.so.5
#3  0x7fcb28d241ba in QSGRenderThread::run() () from
/lib64/libQt5Quick.so.5
#4  0x7fcb250c29da in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7fcb238006ca in start_thread () from /lib64/libpthread.so.0
#6  0x7fcb244b5f7f in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7fca2cff8700 (LWP 3511)):
#0  0x7fcb23806460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcb250c305a in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7fcb28d238c5 in QSGRenderThread::processEventsAndWaitForMore() ()

[plasmashell] [Bug 372509] Second monitor settings are reset on every boot

[Mike Goodwin]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

--- Comment #2 from Mike Goodwin <m...@mgoodwin.net> ---
Also seeing this on F24 now that we've updated to 5.8.3 (in updates-testing) 

In my case, I am using a laptop that is connected to an external monitor, where
I normally keep the laptop's panel disabled and only use the external monitor.
When I login now after the update, it's either (what looks like) a "new
activity" screen (i.e. default wallpaper, no panel) or a blank (black) screen
where I can only access krunner using alt+space

For me this has made using KDE impossible.

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

[plasmashell] [Bug 371858] Occasional wrong desktop at startup

[Mike Goodwin]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

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

[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #15 from Mike Goodwin <m...@mgoodwin.net> ---
@cher...@aip.de 

If you're using Fedora, I persuaded rdeiter to patch it at the package level.
In which case, you won't see it in Fedora.

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

[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

--- Comment #8 from Mike Goodwin <m...@mgoodwin.net> ---
Also seeing this on 1080p https://bugs.kde.org/show_bug.cgi?id=364431#c13 (my
comment with screenshot from the original bug)

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

[braindump] [Bug 363834] seg fault when tried to open Braindump

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

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

[frameworks-kxmlgui] [Bug 286146] Window size/geometry not always restored on TwinView

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #60 from Mike Goodwin <m...@mgoodwin.net> ---
I can confirm that this bug still persists in fedora, and I spent a great deal
of time trying to figure out what was wrong. 

I am confirming on the basis that I previous thought that the window sizes
would not save at all, until I saw this bug and attempted to move the window
first to the leftmost screen (I have three screens in a horizontal
configuration) 

When I drag the window to the leftmost screen _and only the leftmost_, it does
in fact persist the window size. 

This is extremely annoying. 

If at all useful, I also have a nvidia card if this turns out to be nvidia
driver related, as bizarre as that sounds.

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

[frameworks-kxmlgui] [Bug 286146] Window size/geometry not always restored on TwinView

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

--- Comment #59 from Mike Goodwin <m...@mgoodwin.net> ---
I can confirm that this bug still persists in fedora, and I spent a great deal
of time trying to figure out what was wrong. 

I am confirming on the basis that I previous thought that the window sizes
would not save at all, until I saw this bug and attempted to move the window
first to the leftmost screen (I have three screens in a horizontal
configuration) 

When I drag the window to the leftmost screen _and only the leftmost_, it does
in fact persist the window size. 

This is extremely annoying.

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

[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #12 from Mike Goodwin <m...@mgoodwin.net> ---
... And it gets even stranger. There are lots of possibilities here so as I try
them all I try to report back here.

ONLY "Default' also crashes, so:

1. "Default" - crashes

2. "Default" + "roundcube" (Literal contents are '/* empty script */') with
roundcube enabled crashes. 

3. "Default" + "~roundcube~" ( same as above but roundcube is now disabled )
does not crash. 

In other words, it seems like the problem is more or less "Default script
crashes unless a second AND disabled script is present"

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

[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #11 from Mike Goodwin <m...@mgoodwin.net> ---
Created attachment 99280
  --> https://bugs.kde.org/attachment.cgi?id=99280=edit
sieve scripts and config that crashes kmail

Hmm, I did some more testing. This is turning out to seem like a very specific
edge case.

I made a new blank script called "test". So now I have 

1. Default (has real scripts) - enabled
2. roundcube (blank) - disabled
3. test (blank) - enabled

This combination doesn't crash.  Nor does 1-disabled, 2-enabled, 3-enabled; or
1-enabled, 2-disabled, 3-disabled. 

Only 1-enabled, 2-enabled, 3-(n/a or disabled) crashes.

The literal contents of the sieve scripts are attached. I confirmed that it
crashed kmail before I tarred them directly from my kolab server. Hopefully
that helps. 

I only noticed this because I upgraded from F23 to F24 today. I didn't see this
crash in 4.x version of kmail

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

[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #10 from Mike Goodwin <m...@mgoodwin.net> ---
Version 5.1.3
Using:
  KDE Frameworks 5.22.0
  Qt 5.6.0 (built against 5.6.0)
  The xcb windowing system

$ rpm -qa | egrep "kmail|kdepim"
kdepim-libs-15.12.3-1.fc24.x86_64
kdepimlibs-kxmlrpcclient-4.14.10-13.fc24.x86_64
kmail-15.12.3-1.fc24.x86_64
kdepimlibs-akonadi-4.14.10-13.fc24.x86_64
kdepim-runtime-15.12.3-1.fc24.x86_64
kdepimlibs-4.14.10-13.fc24.x86_64
kmail-libs-15.12.3-1.fc24.x86_64
kdepim-runtime-libs-15.12.3-1.fc24.x86_64
kdepim-common-15.12.3-1.fc24.x86_64
kf5-kmailtransport-15.12.3-1.fc24.x86_64
kdepimlibs-gpgme-4.14.10-13.fc24.x86_64

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

[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #8 from Mike Goodwin <m...@mgoodwin.net> ---
I can enable both in roundcube

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

[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #6 from Mike Goodwin <m...@mgoodwin.net> ---
I see that the built-in kmail sieve script editor has a syntax checker (now
that I can get to it), and it is reporting "No errors found" for both scripts.

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

[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #5 from Mike Goodwin <m...@mgoodwin.net> ---
Some findings:

1. Neither script causes the problem when enabled separately/individually. 
2. When both are enabled is when the crash happens, only then. 
3. Related problem: 
 a. When using the checkbox action to disable/enable scripts, selecting or
unselecting either one results in the message "Sieve operation failed The
server responded: script errors:" 
 b. After clicking ok, the circular refreshing icon is perpetually present.
You must restart the client for that to go away
 c. Checking the result of the action with roundcube separately, you can
see that it actually carried the enable/disable action before erroring out
(i.e. the script that was unchecked/checked is enabled/disabled)

I do not believe there to be errors in the scripts as they were generated with
roundcube. If you know of a way to syntax check or lint sieve scripts, that
would be useful.

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

[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #4 from Mike Goodwin <m...@mgoodwin.net> ---
Yes I do.

Two separate scripts. One named "roundcube" (because that is the default
created by kolab/roundcube on setup" and a separate one I named "Default" that
I currently use. 

Default mostly contains stuff like:

# rule:[kde-lists-fpo]
if header :contains "list-id" "kde.lists.fedoraproject.org"
{
fileinto "Mailing Lists/Fedora/kde";
stop;
}

While roundcube empty (but contains a header comment)

I see where this is going so I'll try and do some more sleuthing with regard to
a specific rule, or maybe the empty file and report back if I find anything.

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

[kmail2] [Bug 363723] Kmail crashes when "Server supports sieve" enabled

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

Summary|Kmail crashes on start  |Kmail crashes when "Server
   ||supports sieve" enabled

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

[kmail2] [Bug 363723] Kmail crashes on start

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #2 from Mike Goodwin <m...@mgoodwin.net> ---
Noticing the sieve remarks in the last thread, I turned off sieve support for
my kolab server account and have not been able to reproduce the bug again. I
restarted kontact and kmail ten times each to confirm. 

After enabling sieve again, both crash 1-2 seconds after the main window
renders. 

Changing something from my initial report, it does not *ALWAYS* crash, but does
so 90% of the time. Every once in a while it starts normally and functions
properly...

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

[kontact] [Bug 363722] Kontact does not run in Fedora 24 beta

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Mike Goodwin <m...@mgoodwin.net> ---


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

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

[kmail2] [Bug 363723] Kmail crashes on start

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #1 from Mike Goodwin <m...@mgoodwin.net> ---
*** Bug 363722 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 363723] New: Kmail crashes on start

[Mike Goodwin via KDE Bugzilla]

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

Bug ID: 363723
   Summary: Kmail crashes on start
   Product: kmail2
   Version: 5.1.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: m...@mgoodwin.net

Application: kmail (5.1.3)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.5-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

Starting kmail from the launcher

- Unusual behavior I noticed:

Kmail and kontact seem to be segfaulting on launch

OS is upgraded Fedora KDE 23 to 24 beta

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f920f4a2940 (LWP 31793))]

Thread 22 (Thread 0x7f9167fff700 (LWP 31835)):
#0  0x7f92236b3f69 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f922eba6276 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f922eba1922 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f922eba543f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0
#5  0x7f922df907cd in clone () from /lib64/libc.so.6

Thread 21 (Thread 0x7f917d202700 (LWP 31832)):
#0  0x7f92226c6b64 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7f9222681f70 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7f922268296b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f9222682b5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f922edd369b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f922ed7a8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f922eba03f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f922eba543f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0
#9  0x7f922df907cd in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7f917ebfd700 (LWP 31830)):
#0  0x7f922df84c4d in poll () from /lib64/libc.so.6
#1  0x7f9222682a46 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f9222682b5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f922edd369b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f922ed7a8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f922eba03f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f922eba543f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0
#8  0x7f922df907cd in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7f917f3fe700 (LWP 31820)):
#0  0x7f92226c6b49 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7f922268247c in g_main_context_check () from /lib64/libglib-2.0.so.0
#2  0x7f92226829e4 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f9222682b5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f922edd369b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f922ed7a8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f922eba03f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f922eba543f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0
#9  0x7f922df907cd in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7f917700 (LWP 31819)):
#0  0x7f92236b3bc0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f92277b48a3 in JSC::GCThread::gcThreadMain() () from
/lib64/libQt5WebKit.so.5
#2  0x7f9227af0934 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQt5WebKit.so.5
#3  0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0
#4  0x7f922df907cd in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7f9194bc6700 (LWP 31818)):
#0  0x7f92236b3bc0 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f92277b48a3 in JSC::GCThread::gcThreadMain() () from
/lib64/libQt5WebKit.so.5
#2  0x7f9227af0934 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQt5WebKit.so.5
#3  0x7f92236ae5ba in start_thread () from /lib64/libpthread.so.0
#4  0x7f922df907cd in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7f91953c7700 (LWP 31817)):
#0  0x7f92236b3bc0 in 

[kontact] [Bug 363722] New: Kontact does not run in Fedora 24 beta

[Mike Goodwin via KDE Bugzilla]

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

Bug ID: 363722
   Summary: Kontact does not run in Fedora 24 beta
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: m...@mgoodwin.net

Application: kontact (5.1.3)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.5.5-300.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

Opened kontact from the application menu, application segfaults and presents
drkonqi

The crash can be reproduced every time.

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

Thread 28 (Thread 0x7f5ace422700 (LWP 16109)):
#0  0x7f5ba3574f69 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5ba9b88276 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f5ba9b83922 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f5ba9b8743f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f5ba356f5ba in start_thread () from /lib64/libpthread.so.0
#5  0x7f5ba8f727cd in clone () from /lib64/libc.so.6

Thread 27 (Thread 0x7f5acf02c700 (LWP 16107)):
#0  0x7f5ba3574f69 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5ba9b88276 in QWaitCondition::wait(QMutex*, unsigned long) () from
/lib64/libQt5Core.so.5
#2  0x7f5ba9b83922 in QThreadPoolThread::run() () from
/lib64/libQt5Core.so.5
#3  0x7f5ba9b8743f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#4  0x7f5ba356f5ba in start_thread () from /lib64/libpthread.so.0
#5  0x7f5ba8f727cd in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7f5acf82d700 (LWP 16106)):
#0  0x7f5ba8f628cd in read () from /lib64/libc.so.6
#1  0x7f5ba23867a0 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0
#2  0x7f5ba2343524 in g_main_context_check () from /lib64/libglib-2.0.so.0
#3  0x7f5ba23439e4 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#4  0x7f5ba2343b5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#5  0x7f5ba9db569b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f5ba9d5c8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7f5ba9b823f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7f5ba9b8743f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#9  0x7f5ba356f5ba in start_thread () from /lib64/libpthread.so.0
#10 0x7f5ba8f727cd in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7f5adb7fe700 (LWP 16090)):
#0  0x7f5ba2387b60 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7f5ba2343080 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7f5ba234396b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f5ba2343b5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f5ba9db569b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f5ba9d5c8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f5ba9b823f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f5ba9b8743f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f5ba356f5ba in start_thread () from /lib64/libpthread.so.0
#9  0x7f5ba8f727cd in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7f5adbfff700 (LWP 16088)):
#0  0x7f5ba9c33276 in QElapsedTimer::clockType() () from
/lib64/libQt5Core.so.5
#1  0x7f5ba9c332c9 in QElapsedTimer::isMonotonic() () from
/lib64/libQt5Core.so.5
#2  0x7f5ba9db378e in QTimerInfoList::repairTimersIfNeeded() () from
/lib64/libQt5Core.so.5
#3  0x7f5ba9db3803 in QTimerInfoList::timerWait(timespec&) () from
/lib64/libQt5Core.so.5
#4  0x7f5ba9db4b8e in timerSourcePrepare(_GSource*, int*) () from
/lib64/libQt5Core.so.5
#5  0x7f5ba2342f7d in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#6  0x7f5ba234396b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#7  0x7f5ba2343b5c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#8  0x7f5ba9db569b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#9  0x7f5ba9d5c8ca in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#10 0x7f5ba9b823f3 in QThread::exec() () from /lib64/libQt5Core.so.5
#11 0x7f5ba9b8743f in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#12 0x7f5ba356f5ba in start_thread () from 

[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

--- Comment #5 from Mike Goodwin <m...@mgoodwin.net> ---
Is there any resolution to this? I'm seeing this on my kolab cyrus-imapd server
as well. 

Seems to be server related as gmail still receives IDLE events

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

[kmail2] [Bug 290787] KMail shown "Unknown" date when Date field exist

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #16 from Mike Goodwin <m...@mgoodwin.net> ---
Sorry, I always forget that there's no edit here like github. I wanted to
include:

Fedora 23:

# rpm -qa | grep "kmail\|akonadi"
kmail-libs-4.14.10-10.fc23.x86_64
baloo-akonadi-4.14.3-5.fc23.x86_64
akonadi-mysql-1.13.0-20.fc23.x86_64
akonadi-1.13.0-20.fc23.x86_64
kdepimlibs-akonadi-4.14.10-8.fc23.x86_64
kmail-4.14.10-10.fc23.x86_64

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

[kmail2] [Bug 290787] KMail shown "Unknown" date when Date field exist

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

--- Comment #15 from Mike Goodwin <m...@mgoodwin.net> ---
Absolutely, I specifically noticed this when sorting my email by "Date/Time of
Most Recent in Subtree" because i've been dealing with mailing lists lately.
Once I did that all the "Unknowns" came right to the top where I didn't want
them to be.

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #155 from Mike Goodwin <m...@mgoodwin.net> ---
I just got hit by this Duplicated 17,000 messages, all did was hit the
"apply all filters on folder" button, and then noticed that my phone was
freaking out due to all the dupes. 

kmail-libs-4.14.10-10.fc23.x86_64
baloo-akonadi-4.14.3-5.fc23.x86_64
akonadi-mysql-1.13.0-20.fc23.x86_64
akonadi-1.13.0-20.fc23.x86_64
kdepimlibs-akonadi-4.14.10-8.fc23.x86_64
kmail-4.14.10-10.fc23.x86_64

On Fedora 23. 

Not happy, rest of the day is going to be fixing this mess

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

[korganizer] [Bug 328655] Exception on recurring event on CalDAV calendar makes whole event series disappear

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

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

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

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

[plasma-nm] [Bug 361874] New: Meaning of plasma-nm icon when a bridge is active

[Mike Goodwin via KDE Bugzilla]

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

Bug ID: 361874
   Summary: Meaning of plasma-nm icon when a bridge is active
   Product: plasma-nm
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: m...@mgoodwin.net
CC: lu...@kde.org

Created attachment 98419
  --> https://bugs.kde.org/attachment.cgi?id=98419=edit
plasma-nm icon with blue highlight

Perhaps not a bug but I couldn't find any documentation on what the meaning of
the attached icon is. 

It happened after I implemented a bridge for libvirt. My connection works fine,
and I have two bridges (one for NAT and one for Bridge networking in
virt-manager/libvirt) 

I briefly trying to understand the QML for org.kde.plasma.networkmanagement but
failed.

Can someone explain what this is trying to convey? 

Am I missing documentation for this behavior somewhere?

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

[plasma-nm] [Bug 357816] NM applet icon when connected to WiFi & VPN is the same as disconnected

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[Mike Goodwin via KDE Bugzilla]

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

--- Comment #5 from Mike Goodwin <m...@mgoodwin.net> ---
This affects me on Fedora 23 host/guest scenario with a F23 KDE Plasma 5 guest.
GNOME guest of the same type works correctly. I can essentially confirm what
@OlafLostViking has written.

I am particularly interested in this because I use virt-manager/kvm/libvirt as
a replacement for VMware/VirtualBox and I consider it a basic guest
functionality.

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

[plasmashell] [Bug 356864] Plasma cannot adapt to VM host window

[Mike Goodwin via KDE Bugzilla]

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

Mike Goodwin <m...@mgoodwin.net> changed:

   What|Removed |Added

 CC||m...@mgoodwin.net

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