[frameworks-kholidays] [Bug 383896] Israel's holidays are not displayed

2018-12-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383896

--- Comment #7 from e...@orbsky.homelinux.org ---
Yep the problem still presists.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 401850] excessive DNS usage DOS's router

2018-12-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=401850

kdeb...@caseyconnor.org changed:

   What|Removed |Added

 CC||kdeb...@caseyconnor.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 401850] New: excessive DNS usage DOS's router

2018-12-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=401850

Bug ID: 401850
   Summary: excessive DNS usage DOS's router
   Product: akregator
   Version: 5.8.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kdeb...@caseyconnor.org
  Target Milestone: ---

I have recently experienced intermittent network dropouts. I believe I traced
the issue to Akregator making a large number of DNS queries, but I'm not
qualified to assess that.

I run dd-wrt on an ancient Linksys router. The status page for the router shows
~80 open connections with Firefox running. I start Akregator and the refreshing
of the feeds causes this number to reach 1024 connections in a few seconds
(sometimes I need to do a manual refresh of the feeds to reach this many.)
Inspection of the connections list on the router shows numerous TIME_WAIT
sockets to google IPs (Example IPs: 172.217.3.211 and 216.58.195.83). I use
google nameservers (75.75.75.75) so I conjectured that Akregator is making
numerous DNS calls. 1024 is the "IP Filter Maximum Ports" value for the router,
so the router is rendered unusable until the TIME_WAITs time out.

I'm sure a more modern or differently-configured router could handle this
better, but given that I've used the same feeds and same router for years with
Akregator, it seems like something has changed recently. Also, I have only 103
feeds (~620 unread articles), and it seems odd to use >1000 DNS calls to
refresh those feeds (and pull no new articles in.)

I thus wondered if there is some accidental over-usage of DNS going on, but I
will stop speculating. I don't know if the finger points to Akregator or some
underlying OS issue.

I recently upgraded from 18.04 to 18.10, and the net issues seem to have
started after that, but to be honest I upgraded several weeks ago and only
noticed the net issues in the last week, so I can't be sure of the association.

KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1
Linux  4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux

-- 
You are receiving this mail because:
You are the assignee for the bug.

[frameworks-kholidays] [Bug 383896] Israel's holidays are not displayed

2018-12-06 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=383896

--- Comment #6 from Allen Winter  ---
(In reply to JanKusanagi from comment #4)

> 
> The feature is not gone, there's just a bug with this particular locale.
> The feature works perfectly fine for most other countries/locales.
> 
> I'll add that "Victory Day", the only Gregorian-based event in the Israel
> holiday file, is handled correctly, so it's not like parsing the file fails.

"Perfectly fine"? really?  where? how?
I'm not seeing any Jewish holidays when I load the Israel holiday file.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[frameworks-kholidays] [Bug 383896] Israel's holidays are not displayed

2018-12-06 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=383896

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #5 from Allen Winter  ---
This comment is about KOrganizer and not the digital clock plasmoid that can
also show holidays.

We had a plugin for KOrganizer in the KDE4 days for a Jewish holidays and what
made it special was that it knew the Hebrew calendar.  Indeed we never ported
that to KDE5. 

In KDE5 days, we have holidays for Israel in English and translated to Hebrew.
for the locales en-us and he.  It should know about the Hebrew calendar too.

When testing in KOrganizer, however, I don't see the religious holidays for
Israeli calendar .  I do see the one holiday "Victory day" on the Gregorian
calendar.

For people wanting to see the Jewish holidays and don't want to load the Israel
holidays, then it makes sense to try and restore the Jewish holidays KOrganizer
plugin.  except that doesn't work for the digital clock plasmoid.

Summary:
 - restore KOrganizer Jewish holidays plugin
 - figure out why religious holidays from the Israel calendar don't show up in
KOrganizer (should they? or should that function belong to the Jewish holidays
plugin?)
  - what to do in digital clock about all this

I am the kholidays maintainer and former KOrganizer maintainer but my memory of
all this is kinda fuzzy.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395910] KMail segfaults upon exit

2018-12-06 Thread Øystein Olsen
https://bugs.kde.org/show_bug.cgi?id=395910

--- Comment #5 from Øystein Olsen  ---
Based on the backtrace and given the correct bug number, I can see that this is
an unrelated bug.

Now, I do not use kontact and I do exactly the same as described in this bug.
Start kmail, then exit through the system tray icon (or Ctrl+Q). The
segmentation fault happens without ever opening an email in a subwindow. 

Two different users found a bug with an exact matching description. How were we
supposed to figure out that this was an unrelated bug and find the correct one,
which has completely different description?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 401780] Add option to disable emails from automatically opening URLs

2018-12-06 Thread Ben Daines
https://bugs.kde.org/show_bug.cgi?id=401780

--- Comment #2 from Ben Daines  ---
Sure looks to be the same.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[frameworks-kholidays] [Bug 383896] Israel's holidays are not displayed

2018-12-06 Thread JanKusanagi
https://bugs.kde.org/show_bug.cgi?id=383896

JanKusanagi  changed:

   What|Removed |Added

 CC||jan-b...@gmx.co.uk

--- Comment #4 from JanKusanagi  ---
(In reply to Shimi from comment #2)
> was actually one of the "Linux" features I showed
> off to friends as lacking in their corporate operating systems. Now it is
> gone :(

The feature is not gone, there's just a bug with this particular locale.
The feature works perfectly fine for most other countries/locales.

I'll add that "Victory Day", the only Gregorian-based event in the Israel
holiday file, is handled correctly, so it's not like parsing the file fails.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[frameworks-kholidays] [Bug 383896] Israel's holidays are not displayed

2018-12-06 Thread Shimi
https://bugs.kde.org/show_bug.cgi?id=383896

--- Comment #3 from Shimi  ---
(In reply to Shimi from comment #2)

> I would like to emphasize that this is not sure Israel's holidays as can be

Sorry: "this is not only about Israel's holidays" is what I meant to write.
Sorry about spam. Not sure how this got typed :)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[frameworks-kholidays] [Bug 383896] Israel's holidays are not displayed

2018-12-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=383896

k...@shimi.net changed:

   What|Removed |Added

 CC||k...@shimi.net

--- Comment #2 from k...@shimi.net ---
(In reply to Luigi Toscano from comment #1)
> This is still valid. Reported on IRC and confirmed by a quick check with
> kholidays 5.52 (now in Frameworks).

I'm the reporter on IRC.

I would like to emphasize that this is not sure Israel's holidays as can be
understood from the title of this bug. Right, they're "assigned" to "Israel",
but in fact all Israel's holidays are in fact the Jewish holidays, celebrated
by all Jews across the world. We're talking about Passover, Hannukah etc. So
whenever someone, Jewish or not, wants to know when is Hannukah this year
(which is a different day every year on the Gregorian calendar) - they
basically can't do that with Plasma 5.

I would ALSO like to emphasize, that this is A REGRESSION. This worked
perfectly in KDE 4, and was actually one of the "Linux" features I showed off
to friends as lacking in their corporate operating systems. Now it is gone :(

-- 
You are receiving this mail because:
You are the assignee for the bug.

[frameworks-kholidays] [Bug 383896] Israel's holidays are not displayed

2018-12-06 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=383896

Luigi Toscano  changed:

   What|Removed |Added

 CC||luigi.tosc...@tiscali.it
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Luigi Toscano  ---
This is still valid. Reported on IRC and confirmed by a quick check with
kholidays 5.52 (now in Frameworks).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 401829] New: KMail crashes every time while closing

2018-12-06 Thread Szega
https://bugs.kde.org/show_bug.cgi?id=401829

Bug ID: 401829
   Summary: KMail crashes every time while closing
   Product: kmail2
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kop98...@freemail.hu
  Target Milestone: ---

Application: kmail (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-42-generic x86_64
Distribution: Ubuntu 18.04.1 LTS

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

- Unusual behavior I noticed:
Seg Fault.

Using QtCurve widget style with transparent app background causes the crash.
If I select any other style, KMail exits normally.
(Could be related: Double Commander-qt also doing this)

The crash can be reproduced every time.

-- 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 0x7f1349b43b80 (LWP 2586))]

Thread 7 (Thread 0x7f127590b700 (LWP 2647)):
#0  0x7f133c5199f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f132dc83fb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f133c5199f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f132dc83f68, cond=0x7f132dc83f90) at pthread_cond_wait.c:502
#2  0x7f133c5199f3 in __pthread_cond_wait (cond=0x7f132dc83f90,
mutex=0x7f132dc83f68) at pthread_cond_wait.c:655
#3  0x7f132d98d5f4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f132d98d639 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f133c5136db in start_thread (arg=0x7f127590b700) at
pthread_create.c:463
#6  0x7f1346c2388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f12de7fc700 (LWP 2606)):
#0  0x7f133c519ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f12de7fb7e0, expected=0, futex_word=0x7f12d4004c30) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f133c519ed9 in __pthread_cond_wait_common (abstime=0x7f12de7fb880,
mutex=0x7f12d4004be0, cond=0x7f12d4004c08) at pthread_cond_wait.c:533
#2  0x7f133c519ed9 in __pthread_cond_timedwait (cond=0x7f12d4004c08,
mutex=0x7f12d4004be0, abstime=0x7f12de7fb880) at pthread_cond_wait.c:667
#3  0x7f13313e9652 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f13313bf799 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f13313bfcfb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f13313b85eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f133c5136db in start_thread (arg=0x7f12de7fc700) at
pthread_create.c:463
#8  0x7f1346c2388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f12deffd700 (LWP 2605)):
#0  0x7f133c519ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f12deffc7e0, expected=0, futex_word=0x7f12d4004c34) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f133c519ed9 in __pthread_cond_wait_common (abstime=0x7f12deffc880,
mutex=0x7f12d4004be0, cond=0x7f12d4004c08) at pthread_cond_wait.c:533
#2  0x7f133c519ed9 in __pthread_cond_timedwait (cond=0x7f12d4004c08,
mutex=0x7f12d4004be0, abstime=0x7f12deffc880) at pthread_cond_wait.c:667
#3  0x7f13313e9652 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f13313bf799 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f13313bfcfb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f13313b85eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f133c5136db in start_thread (arg=0x7f12deffd700) at
pthread_create.c:463
#8  0x7f1346c2388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f12df7fe700 (LWP 2604)):
#0  0x7f133c5199f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f12df7fd738) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f133c5199f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f12df7fd6e8, cond=0x7f12df7fd710) at pthread_cond_wait.c:502
#2  0x7f133c5199f3 in __pthread_cond_wait (cond=0x7f12df7fd710,
mutex=0x7f12df7fd6e8) at pthread_cond_wait.c:655
#3  0x7f13313b0999 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f13313b09c7 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f133138b4db in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f1331387da8 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f13313a477b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f13313bc4d6 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  

[kmail2] [Bug 397174] akonadi crashed while archiving inbox to tar.bz2

2018-12-06 Thread Alexander Miroshnichenko
https://bugs.kde.org/show_bug.cgi?id=397174

Alexander Miroshnichenko  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 397174] akonadi crashed while archiving inbox to tar.bz2

2018-12-06 Thread Alexander Miroshnichenko
https://bugs.kde.org/show_bug.cgi?id=397174

--- Comment #2 from Alexander Miroshnichenko  ---
There are no more crash with kmail 5.9.3 (KDE Apps 18.08.3)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 401826] New: kmail crashes when close print preview window

2018-12-06 Thread Alexander Miroshnichenko
https://bugs.kde.org/show_bug.cgi?id=401826

Bug ID: 401826
   Summary: kmail crashes when close print preview window
   Product: kmail2
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: alexmin...@gmail.com
  Target Milestone: ---

Application: kmail (5.9.3)

Qt Version: 5.11.1
Frameworks Version: 5.52.0
Operating System: Linux 4.18.20.a-hardened x86_64
Distribution: "Gentoo Base System release 2.6"

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

- select a mesage
- open print preview window
- close window
- kmail crashes

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

Thread 35 (Thread 0x6b936cebb700 (LWP 17437)):
#0  0x6b94cdc4a83a in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x6b94c2fdc7a7 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x6b94c2fddd07 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x6b94c2fdddf2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x6b94c2fe2e71 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x6b94c2fe420f in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x6b94c2feee31 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x6b94cdc4396a in start_thread () from /lib64/libpthread.so.0
#8  0x6b94d8454f5f in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x6b936700 (LWP 17432)):
#0  0x6b94cdc4a83a in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x6b94c2fdc7a7 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x6b94c2fddd07 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x6b94c2fdddf2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x6b94c2fe2e71 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x6b94c2fe43f9 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x6b94c2feee31 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x6b94cdc4396a in start_thread () from /lib64/libpthread.so.0
#8  0x6b94d8454f5f in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x6b94667fc700 (LWP 17431)):
#0  0x6b94cdc4a83a in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x6b94c2fdc7a7 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x6b94c2fddd07 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x6b94c2fdddf2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x6b94c2fe2e71 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x6b94c2fe43f9 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x6b94c2feee31 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x6b94cdc4396a in start_thread () from /lib64/libpthread.so.0
#8  0x6b94d8454f5f in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x6b936ec5d700 (LWP 17430)):
#0  0x6b94cdc4a83a in pthread_cond_timedwait () from /lib64/libpthread.so.0
#1  0x6b94c2fdc7a7 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x6b94c2fddd07 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x6b94c2fdddf2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x6b94c2fe2e71 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x6b94c2fe420f in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x6b94c2feee31 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5

[akregator] [Bug 399299] Akregator crashes when middle click on a link

2018-12-06 Thread Vladimir
https://bugs.kde.org/show_bug.cgi?id=399299

--- Comment #6 from Vladimir  ---
(In reply to Jonathan Marten from comment #4)
> Same backtrace as bug 371511.
> 
> Claimed to be fixed a couple of Qt releases ago, but reported still present
> with Qt 5.11.  The patch at bug 371511 comment #4 has worked for me for a
> long time.

You have disappeared somewhere. You will have to send your code as 'at least
something' in order to get a working Akregator faster. Sent the code on your
behalf. If you are against it, let me know here:
https://bugreports.qt.io/browse/QTBUG-72260

P.S. Vote, please, so that we can quickly use Akregator out of the box. Dear
Karel Kozlík, you too, please.

Link 1: https://bugreports.qt.io/browse/QTBUG-72260
Link 2: https://bugs.kde.org/show_bug.cgi?id=401638

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 401419] [18.12 beta + RC]Kontact crashed on trying to open an unread email

2018-12-06 Thread Robby Engelmann
https://bugs.kde.org/show_bug.cgi?id=401419

Robby Engelmann  changed:

   What|Removed |Added

Version|unspecified |GIT (master)
Summary|Kontact crashed on trying   |[18.12 beta + RC]Kontact
   |to open an unread email |crashed on trying to open
   ||an unread email

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 398577] closing a message subwindow crashes Kontact

2018-12-06 Thread Juha Tuomala
https://bugs.kde.org/show_bug.cgi?id=398577

--- Comment #12 from Juha Tuomala  ---
Is this problem in kontact or in kmail? I use only kmail and it's very prone to
crash since last updates.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore

2018-12-06 Thread Bart
https://bugs.kde.org/show_bug.cgi?id=395711

--- Comment #18 from Bart  ---
(In reply to Aurélien Murith from comment #15)
> In fact, it works as long as you read your message in the main window, but
> if you open it in a separate window by double-clicking on it, the bug is
> still present.

In my machine even in main window not working correctly :/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 401780] Add option to disable emails from automatically opening URLs

2018-12-06 Thread Jonathan Marten
https://bugs.kde.org/show_bug.cgi?id=401780

Jonathan Marten  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||j...@keelhaul.me.uk
 Status|REPORTED|CONFIRMED

--- Comment #1 from Jonathan Marten  ---
Is this as described in
https://www.kde.org/info/security/advisory-20181128-1.txt?
If so, it is fixed in KDE Applications 18.12.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.