[kmail2] [Bug 277454] new messages in ignored thread sometimes not marked as ignored

2016-10-04 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=277454

--- Comment #7 from Graeme Hewson  ---
I'm not currently experiencing the problem in 5.1.3.

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


[kmail2] [Bug 300916] Reply to a mailing list message sends reply to the list unconditionally instead of the sender

2016-10-04 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=300916

Graeme Hewson  changed:

   What|Removed |Added

 CC||b...@wormhole.me.uk

--- Comment #9 from Graeme Hewson  ---
I have this problem in 5.1.3, with messages from the mailing list going into
their own folder.

I found that in the Folder Properties dialogue, Mailing List tab, the Post to
List address had been set automatically. When I removed this address, replies
to private mail went to the correct address.

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


[Akonadi] [Bug 333035] Supposable timing problem causes duplicate mails after filtering

2016-09-26 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=333035

--- Comment #7 from Graeme Hewson  ---
I'm using POP3, I should have said.

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


[Akonadi] [Bug 333035] Supposable timing problem causes duplicate mails after filtering

2016-09-26 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=333035

--- Comment #6 from Graeme Hewson  ---
I'm still seeing something like this in 5.1.3.

Sometimes I'll see a message in my inbox that should have been filtered to
another folder. The unread count for the target folder is 0. If I open the
target folder, the unread count is set to 1, and the same message as in my
inbox is present. I then go back to my inbox and manually filter the message
(Ctrl+J). Now there are two copies of the message in the target folder.

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


[akregator] [Bug 202370] closing tab sets focus to search instead of content

2016-09-26 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=202370

--- Comment #12 from Graeme Hewson  ---
I confirm the bug is still present in Akgregator 5.1.3.

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


[kmail2] [Bug 318961] False outbox unread count = 1 after message sent

2016-09-26 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=318961

Graeme Hewson  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Graeme Hewson  ---
I haven't seen the problem recently, not since using 5.0 or later?

Marking invalid.

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


[kmail2] [Bug 319792] Folder Sender Identity not used when sending to mailing list

2016-09-26 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=319792

Graeme Hewson  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---
Version|4.10.2  |5.1.3

--- Comment #4 from Graeme Hewson  ---
The bug is still present in 5.1.3.

Note that Message / Mailing List is now Message / {name of mailing list}.

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


[kmail2] [Bug 369322] New: Folder / Mailing List Management menu item duplicate of Folder Properties

2016-09-25 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369322

Bug ID: 369322
   Summary: Folder / Mailing List Management menu item duplicate
of Folder Properties
   Product: kmail2
   Version: 5.1.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@wormhole.me.uk

As per summary. The Folder / Mailing List Management menu item seems to be
unnecessary as it's identical to Folder / Folder Properties.

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


[kmail2] [Bug 319823] Problems with Mailing List preferred handler = browser

2016-09-25 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=319823

Graeme Hewson  changed:

   What|Removed |Added

Version|4.10.2  |5.1.3
 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #4 from Graeme Hewson  ---
Updating Version and Status fields.

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


[kmail2] [Bug 319823] Problems with Mailing List preferred handler = browser

2016-09-25 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=319823

--- Comment #3 from Graeme Hewson  ---
I confirm the problems are still present in Kubuntu 16.04, which uses kmail2
version 5.1.3 (and I'm using kmail2 within kontact version 5.1.3).

I see that a handler _is_ invoked if the URI scheme is mailto. Further, the
kmail handler is invoked only if the email address is at the top of the list of
URIs; if a URL is at the top, nothing happens when Invoke Handler is clicked.
Further still, the "Preferred handler" setting is ignored; if it's set to
Browser, and an email address is at the top of the list of URIs, nevertheless
clicking Invoke Handler brings up a kmail2 composer window.

I would expect that if the preferred handler is set to Browser, then clicking
Invoke Handler opens the browser wherever the URL is in the list (assuming
there is a URL in the list, of course). And similarly for preferred handler =
KMail.

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


[kontact] [Bug 360525] Crash in kmail within kontact

2016-03-23 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360525

--- Comment #1 from Graeme Hewson  ---
See also bug 360908

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kontact] [Bug 360525] New: Crash in kmail within kontact

2016-03-14 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360525

Bug ID: 360525
   Summary: Crash in kmail within kontact
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@wormhole.me.uk

Application: kontact (5.0.3)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-30-generic x86_64
Distribution: Ubuntu 15.10

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

Clicked on an email in the message list after marking another message unread.

The crash can be reproduced sometimes.

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

Thread 6 (Thread 0x7fbd975ef700 (LWP 20232)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbdb99a848b in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fbdb99a84c9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fbdb51276aa in start_thread (arg=0x7fbd975ef700) at
pthread_create.c:333
#4  0x7fbdba89ae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fbd5401b700 (LWP 20233)):
#0  0x7fbdba88f88d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fbdb44aa1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbdb44aa2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbdbb3d029b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fbdbb37675a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fbdbb1943d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fbdbb1992be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fbdb51276aa in start_thread (arg=0x7fbd5401b700) at
pthread_create.c:333
#8  0x7fbdba89ae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fbd4bbc6700 (LWP 20234)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbd5317a4da in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7fbd53179c17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7fbdb51276aa in start_thread (arg=0x7fbd4bbc6700) at
pthread_create.c:333
#4  0x7fbdba89ae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fbd4b18d700 (LWP 20235)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbdb96b65b4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fbdb99d8341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fbdb51276aa in start_thread (arg=0x7fbd4b18d700) at
pthread_create.c:333
#4  0x7fbdba89ae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fbd4a98c700 (LWP 20236)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fbdb96b75e3 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7fbdb99d8341 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7fbdb51276aa in start_thread (arg=0x7fbd4a98c700) at
pthread_create.c:333
#4  0x7fbdba89ae9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fbd9f3b6880 (LWP 20230)):
[KCrash Handler]
#6  KJS::Identifier::add (r=0x1) at ../../../src/kjs/identifier.h:149
#7  KJS::Identifier::Identifier (rep=0x1, this=0x7ffc0b6e25c0) at
../../../src/kjs/identifier.h:52
#8  KJS::PropertyMap::getPropertyNames (this=this@entry=0x49534c8,
propertyNames=..., mode=mode@entry=KJS::PropertyMap::IncludeDontEnumProperties)
at ../../../src/kjs/property_map.cpp:724
#9  0x7fbd38ae5f24 in KJS::JSObject::getOwnPropertyNames (this=0x49534c0,
propertyNames=..., mode=KJS::PropertyMap::IncludeDontEnumProperties) at
../../../src/kjs/object.cpp:727
#10 0x7fbd38adb40e in KJS::ObjectObjectFuncImp::callAsFunction
(this=0x5e5e180, exec=0x7ffc0b6e4a10, args=...) at
../../../src/kjs/object_object.cpp:331
#11 0x7fbd38b01dff in KJS::JSObject::call (args=..., thisObj=0x2ea00c0,
exec=0x7ffc0b6e4a10, this=) at ../../../src/kjs/object.h:689
#12 KJS::Machine::runBlock (exec=exec@entry=0x7ffc0b6e4a10, codeBlock=...,
parentExec=parentExec@entry=0x7ffc0b6e4d50) at codes.def:1233
#13 0x7fbd38ae1e08 in KJS::FunctionImp::callAsFunction (this=0x54ef2c0,
exec=0x7ffc0b6e4d50, thisObj=, args=...) at
../../../src/kjs/function.cpp:174
#14 0x7fbd38b01dff in KJS::JSObject::call (args=..., 

[kmail] [Bug 95064] Duplicates messages in imap folder after filtering

2015-12-22 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=95064

--- Comment #93 from Graeme Hewson  ---
See comment 87. This bug report was filed against Kmail version 1, which is
unmaintained, so it's been closed. "UNRESOLVED UNMAINTAINED" would be more
accurate. :-(

I suggest you find a more recent report for the problem (there are several),
e.g., bug 283682. Note this was filed against Akonadi, which is the component
which does the filtering.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[akregator] [Bug 356472] New: Bad shortcut for Next Unread Article

2015-12-10 Thread Graeme Hewson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356472

Bug ID: 356472
   Summary: Bad shortcut for Next Unread Article
   Product: akregator
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@wormhole.me.uk

(Akregator version 5.0.2, but this isn't currently selectable in the bug
tracker)

The default shortcut for Next Unread Article is "+,=". Obviously this is meant
to mean "+" or "=", but what it actually means is the user has to press "+" and
then "=" to advance to the next unread article.

Workaround is to define a custom shortcut.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs