[kwin] [Bug 449840] Sometimes overview stops accepting keyboard input

[Tom Mittelstädt]

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

Tom Mittelstädt  changed:

   What|Removed |Added

   Platform|Manjaro |unspecified

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

[kwin] [Bug 449840] Sometimes overview stops accepting keyboard input

[Tom Mittelstädt]

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

--- Comment #27 from Tom Mittelstädt  ---
Count me in. Same configuration as in #c25
Reproducible nothing works but hitting escape or clicking a window.

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

[kwin] [Bug 449840] Sometimes overview stops accepting keyboard input

[Tom Mittelstädt]

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

Tom Mittelstädt  changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

--- Comment #26 from Tom Mittelstädt  ---
*** Bug 465237 has been marked as a duplicate of this bug. ***

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

[kwin] [Bug 465237] Present Windows: "searching" by typing the title does not work anymore

[Tom Mittelstädt]

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

Tom Mittelstädt  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #2 from Tom Mittelstädt  ---
Same as 449840, always reproducable.

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

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

[kwin] [Bug 465237] Present Windows: "searching" by typing the title does not work anymore

[Tom Mittelstädt]

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

--- Comment #1 from Tom Mittelstädt  ---
Prior to that update it was also possible to select a window in that overview
using the arrow keys and hitting return. The arrow keys are ignored as well as
any other input from the keyboard.

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

[kwin] [Bug 465237] New: Present Windows: "searching" by typing the title does not work anymore

[Tom Mittelstädt]

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

Bug ID: 465237
   Summary: Present Windows: "searching" by typing the title does
not work anymore
Classification: Plasma
   Product: kwin
   Version: 5.25.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tom-kde.b...@monster-box.de
  Target Milestone: ---

Prior to upgrading the present windows effekt to the version that blurs the
background and shows the "search" box it was possible to immideatly type some
keys and a filter to all shown windows was applied that allowed you to select
the searched window by hitting return.
This doesn't work anymore.
After running resent windows typing any keys does not do anything. The "Search"
box does not receive input even after clicking into it and giving it focus.

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

[kmail2] [Bug 360963] Select identity and "From" automatically on reply in dependence of the answered mail.

[Tom Mittelstädt]

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

Tom Mittelstädt  changed:

   What|Removed |Added

Version|5.1 |5.18.1
 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #5 from Tom Mittelstädt  ---
Still reproducible in  5.18.1

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

[Akonadi] [Bug 365080] Silent broken state after deleting a single item of a event series / server answer HTTP 400

[Tom Mittelstädt]

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

Tom Mittelstädt  changed:

   What|Removed |Added

Summary|broken state after deleting |Silent broken state after
   |a single item of a event|deleting a single item of a
   |series  |event series / server
   ||answer HTTP 400

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

[Akonadi] [Bug 365080] broken state after deleting a single item of a event series

[Tom Mittelstädt]

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

--- Comment #13 from Tom Mittelstädt  ---
(In reply to Erik Quaeghebeur from comment #11)
> In case a developer does take on this bug (do not rely on that), would you
> be able and willing to provide them with a test account on your server?

of course :)

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

[Akonadi] [Bug 365080] broken state after deleting a single item of a event series

[Tom Mittelstädt]

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

--- Comment #12 from Tom Mittelstädt  ---
Created attachment 116874
  --> https://bugs.kde.org/attachment.cgi?id=116874=edit
radicale-debug-log

The radicale log for the described event.

Compared to all other dates/timestaps EXDATE seems to be missing some
information?


BEGIN:VEVENT
DTSTAMP:20181212T103753Z
CREATED:20181212T103753Z
UID:1a20e267-e8b4-492a-a98d-776c96f82bcc
LAST-MODIFIED:20181212T103753Z
SUMMARY:test-entry
RRULE:FREQ=WEEKLY;COUNT=5;BYDAY=WE
EXDATE;VALUE=DATE:20181226
DTSTART;TZID=Europe/Berlin:20181212T13
DTEND;TZID=Europe/Berlin:20181212T14
TRANSP:OPAQUE
END:VEVENT

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

[Akonadi] [Bug 365080] broken state after deleting a single item of a event series

[Tom Mittelstädt]

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

--- Comment #10 from Tom Mittelstädt  ---
Sorry for spamming; I've overlooked the reason in the server logs for the 400
answer:

WARNING: Bad PUT request on '/tom/Privat/1544608970.R271.ics': Failed to store
item '1544608970.R271.ics' in collection 'tom/Privat': can't compare
offset-naive and offset-aware datetimes

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

[Akonadi] [Bug 365080] broken state after deleting a single item of a event series

[Tom Mittelstädt]

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

--- Comment #9 from Tom Mittelstädt  ---
Fresh KDE Neon installed from current iso
$ sudo apt update && sudo apt dist-upgrade -y && sudo apt install korganizer -y
&& sudo systemctl reboot -i
$ akonadictl --version
akonadictl 5.9.3

KOrganizer > Add DAV-Groupware ressource > Credentials (check) > manual > add
CalDAV > address (https://.../radicale/) > use global credentials > discover
collections > OK

Add the event series described in #4

The behaviour is the same as in #4

So I took a look into the server logs and I guess I found kinda "reason":

see "logs-adding-event"-attachment

So the dav ressource tries to make a PUT request for the event series that is
answered with 400 Bad Request, gets an 404 response and is freezing in this
state until the event that caused that 400 answer is deleted.

see "logs-during-ressource-restart"-attachment

I'm not sure if this is a bug in the ressource or in radicale, but the
ressource should not fail silently if there is an error.

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

[Akonadi] [Bug 365080] broken state after deleting a single item of a event series

[Tom Mittelstädt]

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

--- Comment #8 from Tom Mittelstädt  ---
Created attachment 116872
  --> https://bugs.kde.org/attachment.cgi?id=116872=edit
logs-during-ressource-restart

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

[Akonadi] [Bug 365080] broken state after deleting a single item of a event series

[Tom Mittelstädt]

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

--- Comment #7 from Tom Mittelstädt  ---
Created attachment 116871
  --> https://bugs.kde.org/attachment.cgi?id=116871=edit
logs-adding-event

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

[Akonadi] [Bug 365080] broken state after deleting a single item of a event series

[Tom Mittelstädt]

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

--- Comment #6 from Tom Mittelstädt  ---
>  Hmm, I know that something was fixed between and 5.9.3.
> But I can understand that you may not be able to update.

I'm going to set up a KDE Neon VM (to get a more recent version and to have a
"clean" system for testing purposes) and call back (as I stopped using
KOrganizer 2 years ago/use it only read-only for the PIM Event Plugin) as it
regularly "silently" messed up my work calendars).

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

[Akonadi] [Bug 365080] broken state after deleting a single item of a event series

[Tom Mittelstädt]

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

Tom Mittelstädt  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #4 from Tom Mittelstädt  ---
The issue with the broken state after deletion seems to be fixed, however the
removed item of the series is not synced anymore at all if it was removed
within KOrganizer.

The other way round (deleting an item of a series in e.g. on my phone)
everything works fine.


But there seems to be a new incarnation of that issue:

 1. Add a new event to a dav ressource (in my case a self hosted 
Radicale instance):
e.g. 12.12.2018 13:00-14:00,
 repeat weekly, 
 end after 5 times, 
 excluding 26.12.2018.
 2. Sync that ressource. It does not show "broken" but stays in 
   "Online, Running (0%)" forever.

The ressource stops syncing anything.

State in the Akonadi Console for this ressource is:

ResourceScheduler: Online
 current task: 2 ChangeReplay 
 queue 0 is empty
 queue 1 is empty
 queue 2 is empty
 queue 3 is empty
 queue 4 1 tasks:
  10 SyncAll 

A way to recover from this is to toggle the ressource offline in akonadi, abort
the activity, delete the event series in korganizer, toggle the ressource
online again in the akonadi console. Afterwards the ressource syncs fine again.


Akonadi/KOrganzier 5.8.3

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

[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers

[Tom Mittelstädt]

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

Tom Mittelstädt  changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

--- Comment #17 from Tom Mittelstädt  ---
Short note: After a Radicale update the issue was resolved here. It works with
v1.1.2 and later but I'm not quite sure which version-change included that fix.

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

[Akonadi] [Bug 360989] crash on archiving mails

[Tom Mittelstädt]

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

Tom Mittelstädt  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Tom Mittelstädt  ---
The issue is not reproducable anymore in recent versions.

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

[plasma-nm] [Bug 388028] Network-Applet: upstream/downstream values swapped

[Tom Mittelstädt]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Since a recent update the values aren't swapped anymore.

Plasma v5.12.4 Frameworks v5.44.0 Qt v5.9.1

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

[plasmashell] [Bug 388028] New: Network-Applet: upstream/downstream values swapped

[Tom Mittelstädt]

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

Bug ID: 388028
   Summary: Network-Applet: upstream/downstream values swapped
   Product: plasmashell
   Version: 5.11.4
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Monitor
  Assignee: notm...@gmail.com
  Reporter: tom-kde.b...@monster-box.de
  Target Milestone: 1.0

Created attachment 109446
  --> https://bugs.kde.org/attachment.cgi?id=109446=edit
Network Applet Screenshot

The shown values for up- and downstream in the network applet are swapped (see
attached screenshot). Downstream should be 183, upstream 17.

The graph is correct.

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

[krunner] [Bug 381989] New: Krunner crash while typing

[Tom Mittelstädt]

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

Bug ID: 381989
   Summary: Krunner crash while typing
   Product: krunner
   Version: 5.10.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: tom-kde.b...@monster-box.de
  Target Milestone: ---

Application: krunner (5.10.3)

Qt Version: 5.7.1
Frameworks Version: 5.35.0
Operating System: Linux 4.10.0-26-generic x86_64
Distribution: Ubuntu 17.04

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

Krunner crashes from time while typing (esp. numbers for a calculation)

The crash can be reproduced sometimes.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6c7c8a98c0 (LWP 3069))]

Thread 20 (Thread 0x7f6c15ffb700 (LWP 8286)):
#0  0x7f6c75f29510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6c78845b4b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f6c51ad2240 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f6c51ad6478 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f6c51ad13bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f6c51ad4289 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f6c78844c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f6c75f236da in start_thread (arg=0x7f6c15ffb700) at
pthread_create.c:456
#8  0x7f6c78151d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 19 (Thread 0x7f6c167fc700 (LWP 8285)):
#0  0x7f6c75f29510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6c78845b4b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f6c51ad2240 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f6c51ad6478 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f6c51ad13bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f6c51ad64d2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f6c51ad13bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f6c51ad64d2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f6c51ad13bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f6c51ad64d2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f6c51ad13bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f6c51ad4289 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7f6c78844c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f6c75f236da in start_thread (arg=0x7f6c167fc700) at
pthread_create.c:456
#14 0x7f6c78151d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 18 (Thread 0x7f6c16ffd700 (LWP 8284)):
#0  0x7f6c75f29510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6c78845b4b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f6c51ad2240 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f6c51ad6478 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f6c51ad13bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f6c51ad64d2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f6c51ad13bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f6c51ad64d2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f6c51ad13bd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  

[korganizer] [Bug 381635] New: Broken layout: Month view does not follow font metrics

[Tom Mittelstädt]

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

Bug ID: 381635
   Summary: Broken layout: Month view  does not follow font
metrics
   Product: korganizer
   Version: 5.4.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: monthview
  Assignee: kdepim-b...@kde.org
  Reporter: tom-kde.b...@monster-box.de
  Target Milestone: ---

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

The month view does not follow the metrics of the configured font. It seems as
if it uses fixed px values. As a result the layout is rendered way too small
and text is truncated.

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

[kmail2] [Bug 368535] Messageviewer: Line pitch too small on high dpi settings

[Tom Mittelstädt]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

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

--- Comment #5 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
seems to be fixed in 5.4.3

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

[kontact] [Bug 312927] kontact summary sorts events by some unknown order; should sort by time

[Tom Mittelstädt]

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

--- Comment #12 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Still present in kontact 5.4.3.

Sort order seems to be something like:

Today   16:00
Today   09:00
Tomorrow15:00
Tomorrow10:00

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

[Discover] [Bug 370906] Discover crash immediately after system update

[Tom Mittelstädt]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

--- Comment #6 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Happens here too with the same stacktrace as in #4

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

[kmail2] [Bug 368535] Messageviewer: Line pitch too small on high dpi settings

[Tom Mittelstädt]

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

--- Comment #4 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Additional info: If the message is signed or encrypted (i.e. the
signed/encryption frame is rendered) the line pitch (only within the box) seems
to be fine

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

[kmail2] [Bug 368535] Messageviewer: Line pitch too small on high dpi settings

[Tom Mittelstädt]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

Version|5.1.3   |5.2.3

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

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

[Tom Mittelstädt]

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

--- Comment #18 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
it is still broken in 5.2.3

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

[Akonadi] [Bug 325224] CalDav doesn't read server items

[Tom Mittelstädt]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

--- Comment #65 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
The DAV-Ressource (and KOrganizer, too) seems to be fairly unmaintained.

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

[kmail2] [Bug 368535] Messageviewer: Line pitch too small on high dpi settings

[Tom Mittelstädt]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

  Component|misc|UI

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

[kwin] [Bug 372753] Crash on activating present-windows

[Tom Mittelstädt]

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

--- Comment #2 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Unfortunately I'm unaware of the default input method systems in kubuntu.
I didn't installed an input method system myself.

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

[kwin] [Bug 372753] New: Crash on activating present-windows

[Tom Mittelstädt]

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

Bug ID: 372753
   Summary: Crash on activating present-windows
   Product: kwin
   Version: 5.7.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tom-kde.b...@monster-box.de
  Target Milestone: ---

Application: kwin_x11 (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.8.0-27-generic x86_64
Distribution: Ubuntu 16.10

-- Information about the crash:
kwin crashed on activating the present-window effect. This happens from time to
time.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f63773ff940 (LWP 1593))]

Thread 6 (Thread 0x7f6355035700 (LWP 18909)):
#0  0x7f6376f00ea3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6374d82caf in qt_safe_select (nfds=19,
fdread=fdread@entry=0x7f6348000a78, fdwrite=fdwrite@entry=0x7f6348000d08,
fdexcept=fdexcept@entry=0x7f6348000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f6374d84754 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f6348000f98, writefds=0x7f6348000d08, readfds=0x7f6348000a78,
nfds=, this=0x7f63480008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f63480008e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f6374d84c6a in QEventDispatcherUNIX::processEvents
(this=0x7f63480008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f6374d2f0fa in QEventLoop::exec (this=this@entry=0x7f6355034c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f6374b54d43 in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f636f605c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f6374b59c68 in QThreadPrivate::start (arg=0x56527e4559b0) at
thread/qthread_unix.cpp:341
#9  0x7f63704a770a in start_thread (arg=0x7f6355035700) at
pthread_create.c:333
#10 0x7f6376f0b0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f6357fff700 (LWP 12933)):
#0  0x7f6376f00ea3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6374d82caf in qt_safe_select (nfds=17,
fdread=fdread@entry=0x7f634c000a78, fdwrite=fdwrite@entry=0x7f634c000d08,
fdexcept=fdexcept@entry=0x7f634c000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f6374d84754 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f634c000f98, writefds=0x7f634c000d08, readfds=0x7f634c000a78,
nfds=, this=0x7f634c0008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f634c0008e0,
flags=..., flags@entry=..., timeout=timeout@entry=0x0) at
kernel/qeventdispatcher_unix.cpp:196
#4  0x7f6374d84c6a in QEventDispatcherUNIX::processEvents
(this=0x7f634c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607
#5  0x7f6374d2f0fa in QEventLoop::exec (this=this@entry=0x7f6357ffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f6374b54d43 in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f636f605c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f6374b59c68 in QThreadPrivate::start (arg=0x56527e80ff40) at
thread/qthread_unix.cpp:341
#9  0x7f63704a770a in start_thread (arg=0x7f6357fff700) at
pthread_create.c:333
#10 0x7f6376f0b0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f6354834700 (LWP 1722)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6373eee574 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f6373eee5b9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f63704a770a in start_thread (arg=0x7f6354834700) at
pthread_create.c:333
#4  0x7f6376f0b0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f635739f700 (LWP 1713)):
#0  0x7f6376f00ea3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6374d82caf in qt_safe_select (nfds=15,
fdread=fdread@entry=0x7f6344000a78, fdwrite=fdwrite@entry=0x7f6344000d08,
fdexcept=fdexcept@entry=0x7f6344000f98, orig_timeout=orig_timeout@entry=0x0) at
kernel/qcore_unix.cpp:75
#2  0x7f6374d84754 in QEventDispatcherUNIX::select (timeout=0x0,
exceptfds=0x7f6344000f98, writefds=0x7f6344000d08, readfds=0x7f6344000a78,
nfds=, this=0x7f63440008c0) at
kernel/qeventdispatcher_unix.cpp:320
#3  QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f63440008e0,
flags=..., 

[kmail2] [Bug 368535] Messageviewer: Line pitch too small on high dpi settings

[Tom Mittelstädt via KDE Bugzilla]

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

--- Comment #3 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Created attachment 101329
  --> https://bugs.kde.org/attachment.cgi?id=101329=edit
pdf-print

this affects printing, too

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

[kmail2] [Bug 351816] Kmail 15.08 Message Body does not follow the Font DPI settings.

[Tom Mittelstädt via KDE Bugzilla]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

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

[plasmashell] [Bug 369041] New: Some notifications do not disappear automatically

[Tom Mittelstädt via KDE Bugzilla]

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

Bug ID: 369041
   Summary: Some notifications do not disappear automatically
   Product: plasmashell
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: tom-kde.b...@monster-box.de
CC: mklape...@kde.org

libkf5notifications5 Version: 5.18.0-0ubuntu1

There are some notifications (eg. those that are triggered by Opera) that do
not disappear automatically but stay visible until they get clicked.
Others disappear after a few seconds.

Actually it would be nice if there would be the possibility to configure the
notifications in terms of duration, stickiness etc on a per process base (like
snarl on windows).

Reproducible: Always

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

[kmail2] [Bug 368535] New: Messageviewer: Line pitch too small on high dpi settings

[Tom Mittelstädt via KDE Bugzilla]

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

Bug ID: 368535
   Summary: Messageviewer: Line pitch too small on high dpi
settings
   Product: kmail2
   Version: 5.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-b...@kde.org
  Reporter: tom-kde.b...@monster-box.de

The line pitch in the messageviewer is (way) too small in a high dpi
environment:

System dpi setting: 166
Font:  Noto Mono 10pt
Leading in messageviewer: only 1-2px(!) (screenshot attached)

Using 10pt font size I'd expect a line pitch of 12-15pt to make thinks easily
readable.
However the lines are partly overlapping.



Reproducible: Always

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

[kmail2] [Bug 366801] New: kmail crash during mail encryption

[Tom Mittelstädt via KDE Bugzilla]

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

Bug ID: 366801
   Summary: kmail crash during mail encryption
   Product: kmail2
   Version: 5.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: tom-kde.b...@monster-box.de

Application: kmail (5.1.3)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-35-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

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

After writing an email kmail asked if i want to encrypt the message as the gpg
key is known. during this process kmail crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbc7f130980 (LWP 25999))]

Thread 29 (Thread 0x7fbbb6a23700 (LWP 20665)):
#0  0x7fbca0965e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbc9707139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbc970714ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbca14a8a9b in QEventDispatcherGlib::processEvents
(this=0x7fbbac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fbca144fdea in QEventLoop::exec (this=this@entry=0x7fbbb6a22c40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fbca126c8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fbca127184e in QThreadPrivate::start (arg=0x53a86b0) at
thread/qthread_unix.cpp:331
#7  0x7fbc975926fa in start_thread (arg=0x7fbbb6a23700) at
pthread_create.c:333
#8  0x7fbca0971b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 28 (Thread 0x7fbbd541d700 (LWP 27499)):
#0  QListData::begin (this=0x7fbbc40030d0) at
../../include/QtCore/../../src/corelib/tools/qlist.h:108
#1  QList::constBegin (this=0x7fbbc40030d0) at
../../include/QtCore/../../src/corelib/tools/qlist.h:302
#2  QTimerInfoList::timerWait (this=0x7fbbc40030d0, tm=...) at
kernel/qtimerinfo_unix.cpp:386
#3  0x7fbca14a7e7e in timerSourcePrepareHelper (timeout=0x7fbbd541ca84,
src=) at kernel/qeventdispatcher_glib.cpp:127
#4  timerSourcePrepare (source=, timeout=0x7fbbd541ca84) at
kernel/qeventdispatcher_glib.cpp:160
#5  0x7fbc9707092d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fbc970712cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fbc970714ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fbca14a8a9b in QEventDispatcherGlib::processEvents
(this=0x7fbbc40034f0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#9  0x7fbca144fdea in QEventLoop::exec (this=this@entry=0x7fbbd541cc40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#10 0x7fbca126c8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#11 0x7fbca127184e in QThreadPrivate::start (arg=0x2f05970) at
thread/qthread_unix.cpp:331
#12 0x7fbc975926fa in start_thread (arg=0x7fbbd541d700) at
pthread_create.c:333
#13 0x7fbca0971b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 27 (Thread 0x7fbbbf3cd700 (LWP 26152)):
#0  0x7fbca0965e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbc9707139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbc970714ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbca14a8a9b in QEventDispatcherGlib::processEvents
(this=0x7fbbb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fbca144fdea in QEventLoop::exec (this=this@entry=0x7fbbbf3ccc40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fbca126c8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fbca127184e in QThreadPrivate::start (arg=0x2e20760) at
thread/qthread_unix.cpp:331
#7  0x7fbc975926fa in start_thread (arg=0x7fbbbf3cd700) at
pthread_create.c:333
#8  0x7fbca0971b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 26 (Thread 0x7fbbb700 (LWP 26149)):
#0  0x7fbca0965e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fbc9707139c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbc970714ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbca14a8a9b in QEventDispatcherGlib::processEvents
(this=0x7fbbb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7fbca144fdea in QEventLoop::exec (this=this@entry=0x7fbbbfffec40,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7fbca126c8a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7fbca127184e 

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

[Tom Mittelstädt via KDE Bugzilla]

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

--- Comment #15 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Does this also fixes the issues with dovecot (2.2.10)?
at the moment (kmail2 5.1.3) I have the sames issues as in #1. A workaround is
to restart kmail completely and right afterwards the manage sieve functionality
works once.

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

[Akonadi] [Bug 365080] New: broken state after deleting a single item of a event series

[Tom Mittelstädt via KDE Bugzilla]

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

Bug ID: 365080
   Summary: broken state after deleting a single item of a event
series
   Product: Akonadi
   Version: 16.04
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-b...@kde.org
  Reporter: tom-kde.b...@monster-box.de

The dav ressource falls into a offline/broken state if I delete a single item
of a event series.

Reproducible: Always

Steps to Reproduce:
1. Add an event series to the dav ressource (radicale server in this case) with
start date, end date and some exceptions
2. delete an occurence of the event of the series in the agenda-view of
korganizer
3. the dav resource falls into offline/broken state. the only way to recover
this is to delete the ressource and re-add it.

Actual Results:  
the dav ressource is offline/broken permanently

Expected Results:  
well.. this is obvious. the dav ressource should not fall into a
not-recoverable state.

critical, as all changes made to the ressource are not synced to the server
after that fail, which can lead to data loss.

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

[korganizer] [Bug 362921] Display of events which span more than one day looks curious in the week view

[Tom Mittelstädt via KDE Bugzilla]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

--- Comment #3 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Happens here exactly in the described way, too.

korganizer 5.1.3

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

[korganizer] [Bug 364968] New: show event location in agenda view if there is enough free space

[Tom Mittelstädt via KDE Bugzilla]

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

Bug ID: 364968
   Summary: show event location in agenda view if there is enough
free space
   Product: korganizer
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: agendaview (weekview)
  Assignee: korganizer-de...@kde.org
  Reporter: tom-kde.b...@monster-box.de

Korganizer's agenda view should show the event location if there is enough free
space in a block.

Reproducible: Always

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

[kdelibs] [Bug 180051] [KDE4] Need a way to have default printer settings

[Tom Mittelstädt via KDE Bugzilla]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

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

[plasmashell] [Bug 363644] New: crash after activating a window

[Tom Mittelstädt via KDE Bugzilla]

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

Bug ID: 363644
   Summary: crash after activating a window
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: tom-kde.b...@monster-box.de
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-23-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
after activating a window plasma circled through all windows at the current
workspace for 20 times before it crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1c65075900 (LWP 7531))]

Thread 41 (Thread 0x7f1c4e790700 (LWP 7533)):
#0  0x7f1c5f791e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1c63856c62 in poll (__timeout=-1, __nfds=1, __fds=0x7f1c4e78fbc0)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x247e6c0, cond=cond@entry=0x247e700,
vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459
#3  0x7f1c638588d7 in xcb_wait_for_event (c=0x247e6c0) at
../../src/xcb_in.c:693
#4  0x7f1c50f10629 in QXcbEventReader::run (this=0x248c0a0) at
qxcbconnection.cpp:1253
#5  0x7f1c5fe8784e in QThreadPrivate::start (arg=0x248c0a0) at
thread/qthread_unix.cpp:331
#6  0x7f1c5ef746fa in start_thread (arg=0x7f1c4e790700) at
pthread_create.c:333
#7  0x7f1c5f79db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 40 (Thread 0x7f1c47dfa700 (LWP 7535)):
#0  0x7f1c5c52724d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f1c5c5274ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1c600bea9b in QEventDispatcherGlib::processEvents
(this=0x7f1c48e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#3  0x7f1c60065dea in QEventLoop::exec (this=this@entry=0x7f1c47df9ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#4  0x7f1c5fe828a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#5  0x7f1c6272a3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f1c5fe8784e in QThreadPrivate::start (arg=0x257a770) at
thread/qthread_unix.cpp:331
#7  0x7f1c5ef746fa in start_thread (arg=0x7f1c47dfa700) at
pthread_create.c:333
#8  0x7f1c5f79db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 39 (Thread 0x7f1c3cd26700 (LWP 7537)):
#0  0x7f1c5c56bac9 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f1c5c526939 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1c5c5272cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1c5c5274ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1c600bea9b in QEventDispatcherGlib::processEvents
(this=0x7f1c380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f1c60065dea in QEventLoop::exec (this=this@entry=0x7f1c3cd25ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f1c5fe828a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f1c6272a3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f1c5fe8784e in QThreadPrivate::start (arg=0x27fc070) at
thread/qthread_unix.cpp:331
#9  0x7f1c5ef746fa in start_thread (arg=0x7f1c3cd26700) at
pthread_create.c:333
#10 0x7f1c5f79db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 38 (Thread 0x7f1c36e2a700 (LWP 7538)):
#0  0x7f1c5c56bae4 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f1c5c526dc9 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1c5c527340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1c5c5274ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1c600bea9b in QEventDispatcherGlib::processEvents
(this=0x7f1c38c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f1c60065dea in QEventLoop::exec (this=this@entry=0x7f1c36e29ca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f1c5fe828a4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f1c6272a3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f1c5fe8784e in QThreadPrivate::start (arg=0x2b1c280) at
thread/qthread_unix.cpp:331
#9  0x7f1c5ef746fa in start_thread (arg=0x7f1c36e2a700) at
pthread_create.c:333
#10 0x7f1c5f79db5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 37 (Thread 

[i18n] [Bug 362875] Translation of "Writing Data Project" is wrong: should be "Daten werden geschrieben"

[Tom Mittelstädt via KDE Bugzilla]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

--- Comment #6 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
"beschrieben" finde ich sprachlich am zutreffensten.

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

[kmail2] [Bug 360963] Select identity and "From" automatically on reply in dependence of the answered mail.

[Tom Mittelstädt via KDE Bugzilla]

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

--- Comment #2 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Does not work at all in 5.1.3

The selected identity is always the last one I've selected manually.

expected behavior: I have one account "account@domain" and an alias for it
"account\+*@domain".

If I receive a mail for "account+project123@domain" I'd like kmail to
automatically select the "account@domain" identity and use
"account+project123@domain" as from/sender.

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

[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

[Tom Mittelstädt via KDE Bugzilla]

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

--- Comment #111 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Metko exactly describes  the behavior here.

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

[kwin] [Bug 358850] KWin crash after closing window from Present Windows

[Tom Mittelstädt via KDE Bugzilla]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

--- Comment #3 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Same happens here from time to time, too.

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

[kmail2] [Bug 328246] Manage Sieve scripts feature broken

[Tom Mittelstädt via KDE Bugzilla]

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

Tom Mittelstädt <tom-kde.b...@monster-box.de> changed:

   What|Removed |Added

 CC||tom-kde.b...@monster-box.de

--- Comment #9 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
Still present in kmail2 5.1.3

sieve scripts are only discovered if kmail is freshly startet exactly one time.
If I access the dialog a second time kmail tries forever to get the script
list.
it works again after a kmail-restart

Same if the syntax check detects an error. the whole sieve management part
becomes unresponsive and does simply nothing until kmail is restarted

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

[kmail2] [Bug 360486] segfault while moving local folders to imap

[Tom Mittelstädt via KDE Bugzilla]

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

--- Comment #1 from Tom Mittelstädt <tom-kde.b...@monster-box.de> ---
happens here too moving imap to imap (accidentially)

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