[Bug 280102] KMail doesn't handle HTML anchors (regression from kde 4.4)

2012-09-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=280102

--- Comment #7 from Laurent Montel mon...@kde.org ---
Ok I confirm it.
Don't know why for the moment.

-- 
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


[Bug 307300] Kontakt and Kmail aren'nt starting

2012-09-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=307300

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org
 Resolution|--- |UNMAINTAINED

--- Comment #1 from Laurent Montel mon...@kde.org ---
kmail 1 unmaintained

-- 
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


[Bug 206695] kmail extendible attach files

2012-09-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=206695

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 CC||mon...@kde.org
   Version Fixed In||4.10

--- Comment #4 from Laurent Montel mon...@kde.org ---
Fixed in 4.10

-- 
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


[Bug 307309] New: It is not possible to chose the identity for accepting invitations

2012-09-24 Thread S . Burmeister
https://bugs.kde.org/show_bug.cgi?id=307309

Bug ID: 307309
  Severity: normal
   Version: 4.9.1
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: It is not possible to chose the identity for accepting
invitations
Classification: Unclassified
OS: Linux
  Reporter: sven.burmeis...@gmx.net
  Hardware: Other
Status: UNCONFIRMED
 Component: general
   Product: kmail2

If receives an invitation kmail shows buttons for accept, deny etc. Clicking on
any of those sends an email without any further notice and uses the standard
identity, not necessarily the identity the invitation was send to.

It would be better if kmail would either always use the identity the invitation
was send to.

Alternatively kmail could check whether the identity the invitation was send to
matches the identity the reply it going to be send with and ask the user if
they do not match.

Reproducible: Always

-- 
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


[Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders

2012-09-24 Thread Jarkko Sakkinen
https://bugs.kde.org/show_bug.cgi?id=284172

--- Comment #7 from Jarkko Sakkinen jarkko.sakki...@iki.fi ---
I do not experience this issue anymore with KDE 4.9 (kubuntu 12.04 +
backports).

-- 
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


[Bug 307309] It is not possible to chose the identity for accepting invitations

2012-09-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=307309

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #1 from Laurent Montel mon...@kde.org ---
I confirm it.
Will look at if I can fix it

-- 
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


[Bug 284172] Kmail does not correctly recognize some IMAP-Inbox-Folders

2012-09-24 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=284172

Myriam Schweingruber myr...@kde.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||4.9
 Resolution|--- |WORKSFORME

--- Comment #8 from Myriam Schweingruber myr...@kde.org ---
(In reply to comment #7)
 I do not experience this issue anymore with KDE 4.9 (kubuntu 12.04 +
 backports).

Thank you for the feedback, please feel free to reopen should this be
reappearing with 4.9 or later.

-- 
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


[Bug 295013] Filter From: is not in addressbook does not work

2012-09-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=295013

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||mon...@kde.org
   Version Fixed In||4.9.2
 Resolution|--- |FIXED

--- Comment #1 from Laurent Montel mon...@kde.org ---
Fixed in 4.9.2

-- 
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


[Bug 264437] Allow directly editing an added addressbook entry

2012-09-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=264437

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||4.10
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdep
   ||im/98ddc66cb69840f3906acc0f
   ||ef3748d2949ab413

--- Comment #1 from Laurent Montel mon...@kde.org ---
Git commit 98ddc66cb69840f3906acc0fef3748d2949ab413 by Montel Laurent.
Committed on 24/09/2012 at 13:53.
Pushed by mlaurent into branch 'master'.

Fix Bug 264437 - Allow directly editing an added addressbook entry

FIXED-IN: 4.10

M  +10   -5libkdepim/addemailaddressjob.cpp

http://commits.kde.org/kdepim/98ddc66cb69840f3906acc0fef3748d2949ab413

-- 
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


[Bug 264437] Allow directly editing an added addressbook entry

2012-09-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=264437

Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 CC||mon...@kde.org

-- 
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


[Bug 288364] Retrieving Folder Contents hanging without showing content

2012-09-24 Thread Frits Spieker
https://bugs.kde.org/show_bug.cgi?id=288364

Frits Spieker s.pa...@spiekerbros.com changed:

   What|Removed |Added

 CC||s.pa...@spiekerbros.com

--- Comment #28 from Frits Spieker s.pa...@spiekerbros.com ---
Same problem here. Fresh install of 4.9.1 (OpenSuSE 12.2 64bit).

Firing up kontact from the terminal shows:

kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2292 
kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2293 
kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2294 
kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2295 
kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2296 
kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2297 
kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2298 
kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2299 
kontact(23366) MessageList::Core::ModelInvariantRowMapper::modelRowsRemoved:
Could not find invariant to invalidate at current row  2300

-- 
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


[Bug 288364] Retrieving Folder Contents hanging without showing content

2012-09-24 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=288364

Myriam Schweingruber myr...@kde.org changed:

   What|Removed |Added

 CC|myr...@kde.org  |
Version|4.7 |4.9.1

-- 
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


[Bug 288364] Retrieving Folder Contents hanging without showing content

2012-09-24 Thread MK
https://bugs.kde.org/show_bug.cgi?id=288364

MK bugs...@kkk-web.de changed:

   What|Removed |Added

 CC|bugs...@kkk-web.de  |

-- 
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


[Bug 307329] New: Kontact fails to Start

2012-09-24 Thread Jacky Alcine
https://bugs.kde.org/show_bug.cgi?id=307329

Bug ID: 307329
  Severity: crash
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact fails to Start
Classification: Unclassified
OS: Linux
  Reporter: jacky.alc...@thesii.org
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.5)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-31-generic-pae i686
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
I installed this version of Kubuntu on a 64-bit machine (its 32-bit). I
upgraded from KMail to KMail and wham! Doesn't work.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb217d980 (LWP 8295))]

Thread 4 (Thread 0xafb76b40 (LWP 8296)):
#0  0xb775f424 in __kernel_vsyscall ()
#1  0xb398696b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0xb60901bc in __pthread_cond_wait (cond=0xb5f3fa30, mutex=0xb5f3fa18) at
forward.c:139
#3  0xb580e263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb580e37f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb3982d4c in start_thread (arg=0xafb76b40) at pthread_create.c:308
#6  0xb60828ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 3 (Thread 0xaf255b40 (LWP 8297)):
#0  0xb3984dc8 in __pthread_mutex_lock (mutex=0xae900550) at
pthread_mutex_lock.c:92
#1  0xb60903d4 in pthread_mutex_lock (mutex=0xae900550) at forward.c:182
#2  0xb38ef3d0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb38aff85 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb38b0201 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb63d28e7 in QEventDispatcherGlib::processEvents (this=0xae900468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb639e50d in QEventLoop::processEvents (this=0xaf255270, flags=...) at
kernel/qeventloop.cpp:149
#7  0xb639e7a9 in QEventLoop::exec (this=0xaf255270, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb628794c in QThread::exec (this=0x8d5bc98) at thread/qthread.cpp:501
#9  0xb6287a3b in QThread::run (this=0x8d5bc98) at thread/qthread.cpp:568
#10 0xb628ade0 in QThreadPrivate::start (arg=0x8d5bc98) at
thread/qthread_unix.cpp:298
#11 0xb3982d4c in start_thread (arg=0xaf255b40) at pthread_create.c:308
#12 0xb60828ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 2 (Thread 0xac045b40 (LWP 8316)):
#0  0xb38afb7e in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb38b0042 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb38b0201 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb63d28e7 in QEventDispatcherGlib::processEvents (this=0xab700468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0xb639e50d in QEventLoop::processEvents (this=0xac045240, flags=...) at
kernel/qeventloop.cpp:149
#5  0xb639e7a9 in QEventLoop::exec (this=0xac045240, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb628794c in QThread::exec (this=0x959cd30) at thread/qthread.cpp:501
#7  0xb637bb5d in QInotifyFileSystemWatcherEngine::run (this=0x959cd30) at
io/qfilesystemwatcher_inotify.cpp:248
#8  0xb628ade0 in QThreadPrivate::start (arg=0x959cd30) at
thread/qthread_unix.cpp:298
#9  0xb3982d4c in start_thread (arg=0xac045b40) at pthread_create.c:308
#10 0xb60828ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb217d980 (LWP 8295)):
[KCrash Handler]
#7  0xb775f424 in __kernel_vsyscall ()
#8  0xb5fc61cf in __GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0xb5fc9815 in __GI_abort () at abort.c:91
#10 0xb627f616 in qt_message_output (msgType=QtFatalMsg, buf=0xa4af060 Fatal
Error: Accessed global static 'KernelPrivate *sInstance()' after destruction.
Defined at ../../mailcommon/mailkernel.cpp:48) at global/qglobal.cpp:2276
#11 0xb627fa4b in qt_message (msgType=QtFatalMsg, msg=0xad9b71c4 Fatal Error:
Accessed global static '%s *%s()' after destruction. Defined at %s:%d,
ap=0xbfa35764 Ms\233\255Cs\233\255\244q\233\255\060) at
global/qglobal.cpp:2322
#12 0xb627fb68 in qFatal (msg=0xad9b71c4 Fatal Error: Accessed global static
'%s *%s()' after destruction. Defined at %s:%d) at global/qglobal.cpp:2505
#13 0xad94f894 in MailCommon::Kernel::self() () from
/usr/lib/libmailcommon.so.4
#14 0xad93d25e in MailCommon::FolderCollection::writeConfig() const () from
/usr/lib/libmailcommon.so.4
#15 0xad93dd63 in MailCommon::FolderCollection::~FolderCollection() () from
/usr/lib/libmailcommon.so.4
#16 0xad93de22 in MailCommon::FolderCollection::~FolderCollection() () from
/usr/lib/libmailcommon.so.4
#17 0xad93b6f1 

[Bug 300869] Addressbook messaging entries doesn't follow the RFC

2012-09-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=300869

--- Comment #9 from Laurent Montel mon...@kde.org ---
a dnd direct doesn't use createVcard and co it copy directly data.
So don't know how to fix it.

-- 
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


[Bug 307329] Kontact fails to Start

2012-09-24 Thread Jekyll Wu
https://bugs.kde.org/show_bug.cgi?id=307329

Jekyll Wu adap...@gmail.com changed:

   What|Removed |Added

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

--- Comment #1 from Jekyll Wu adap...@gmail.com ---


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

-- 
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


[Bug 294752] kmail crashes on exit

2012-09-24 Thread Jekyll Wu
https://bugs.kde.org/show_bug.cgi?id=294752

Jekyll Wu adap...@gmail.com changed:

   What|Removed |Added

 CC||jacky.alc...@thesii.org

--- Comment #9 from Jekyll Wu adap...@gmail.com ---
*** Bug 307329 has been marked as a duplicate of this bug. ***

-- 
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


[Bug 307336] New: Filename is messed up when dropping file from Nepomuk searchresult into composer window

2012-09-24 Thread Elias Probst
https://bugs.kde.org/show_bug.cgi?id=307336

Bug ID: 307336
  Severity: normal
   Version: 4.9.1
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Filename is messed up when dropping file from Nepomuk
searchresult into composer window
Classification: Unclassified
OS: Linux
  Reporter: m...@eliasprobst.eu
  Hardware: Other
Status: NEW
 Component: composer
   Product: kmail2

When adding files from a Nepomuk search (e.g. from Dolphin) via drag'n'drop to
a new mail, the filename contains the full URL which is URL encoded and all %
signs are replaced by an underscore.

→ Open Dolphin
→ Click on search
→ Enter a searchterm
→ Open KMail
→ Compose a new mail
→ Drag'n'drop a file from the search results to the composer window
→ Select Add file as attachment

The name of the attached file looks like this:
file_3A_2F_2F_2Fhome_2Felias_2Fdmidecode.txt

When doing this with a file from a regular Dolphin view, the filename looks
correct.

-- 
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


[Bug 307339] New: adding event to groupware linked calendar

2012-09-24 Thread Otter
https://bugs.kde.org/show_bug.cgi?id=307339

Bug ID: 307339
  Severity: crash
   Version: 4.9.1
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: adding event to groupware linked calendar
Classification: Unclassified
OS: Linux
  Reporter: otter...@gmail.com
  Hardware: openSUSE RPMs
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.9.1)
KDE Platform Version: 4.9.1 release 561
Qt Version: 4.8.3
Operating System: Linux 3.1.10-1.16-desktop x86_64
Distribution: openSUSE 12.1 (x86_64)

-- Information about the crash:
I had added an event to the local calendar and was copying it to a linked
egroupware calendar.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f81650ab760 (LWP 2727))]

Thread 4 (Thread 0x7f814cb94700 (LWP 2744)):
#0  0x7f815cde6e6c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f816186bf52 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x7f816186bf89 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x7f815cde2f05 in start_thread () from /lib64/libpthread.so.0
#4  0x7f81625ae10d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f814c27b700 (LWP 2748)):
#0  0x7f81625a4ff3 in poll () from /lib64/libc.so.6
#1  0x7f815c8d3ae8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f815c8d3fa9 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8162d1e666 in QEventDispatcherGlib::processEvents
(this=0x7f81440008c0, flags=optimized out) at
kernel/qeventdispatcher_glib.cpp:426
#4  0x7f8162cee162 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f8162cee3b7 in QEventLoop::exec (this=0x7f814c27ae00, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f8162bec687 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f8162bef6ec in QThreadPrivate::start (arg=0x64a260) at
thread/qthread_unix.cpp:338
#8  0x7f815cde2f05 in start_thread () from /lib64/libpthread.so.0
#9  0x7f81625ae10d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f80f7df0700 (LWP 16299)):
#0  0x7f81625a4ff3 in poll () from /lib64/libc.so.6
#1  0x7f815c8d3ae8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f815c8d3fa9 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f8162d1e666 in QEventDispatcherGlib::processEvents
(this=0x7f80f8c0, flags=optimized out) at
kernel/qeventdispatcher_glib.cpp:426
#4  0x7f8162cee162 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f8162cee3b7 in QEventLoop::exec (this=0x7f80f7defdd0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f8162bec687 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f8162ccdc0f in QInotifyFileSystemWatcherEngine::run (this=0x5865ff0)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x7f8162bef6ec in QThreadPrivate::start (arg=0x5865ff0) at
thread/qthread_unix.cpp:338
#9  0x7f815cde2f05 in start_thread () from /lib64/libpthread.so.0
#10 0x7f81625ae10d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f81650ab760 (LWP 2727)):
[KCrash Handler]
#6  0x7f80e7308b69 in ~QPointer (this=optimized out, __in_chrg=optimized
out) at
/usr/src/debug/kdepim-4.9.1/build/calendarviews/eventviews/agenda.moc:409
#7  EventViews::Agenda::endItemAction (this=0x2064bf0) at
/usr/src/debug/kdepim-4.9.1/calendarviews/eventviews/agenda/agenda.cpp:1251
#8  0x7f80e730a465 in EventViews::Agenda::eventFilter_mouse
(this=0x2064bf0, object=0x8eb75c0, me=optimized out) at
/usr/src/debug/kdepim-4.9.1/calendarviews/eventviews/agenda/agenda.cpp:700
#9  0x7f80e7303ef9 in EventViews::Agenda::eventFilter (this=0x2064bf0,
object=0x8eb75c0, event=optimized out) at
/usr/src/debug/kdepim-4.9.1/calendarviews/eventviews/agenda/agenda.cpp:501
#10 0x7f8162cef7b8 in
QCoreApplicationPrivate::sendThroughObjectEventFilters (this=optimized out,
receiver=0x8eb75c0, event=0x7fff750c1fd0) at kernel/qcoreapplication.cpp:1025
#11 0x7f81637090af in notify_helper (e=0x7fff750c1fd0, receiver=0x8eb75c0,
this=0x63c350) at kernel/qapplication.cpp:4553
#12 QApplicationPrivate::notify_helper (this=0x63c350, receiver=0x8eb75c0,
e=0x7fff750c1fd0) at kernel/qapplication.cpp:4529
#13 0x7f816370e783 in QApplication::notify (this=optimized out,
receiver=0x8eb75c0, e=0x7fff750c1fd0) at kernel/qapplication.cpp:4100
#14 0x7f816444e246 in KApplication::notify (this=0x7fff750c2cd0,
receiver=0x8eb75c0, event=0x7fff750c1fd0) at
/usr/src/debug/kdelibs-4.9.1/kdeui/kernel/kapplication.cpp:311
#15 0x7f8162cef62c in QCoreApplication::notifyInternal
(this=0x7fff750c2cd0, receiver=0x8eb75c0, event=0x7fff750c1fd0) at
kernel/qcoreapplication.cpp:915
#16 0x7f816370a0b2 in sendEvent 

[Bug 307341] New: virtuoso-t and kmail2 crashed at startup

2012-09-24 Thread Marcus Menzel
https://bugs.kde.org/show_bug.cgi?id=307341

Bug ID: 307341
  Severity: crash
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: virtuoso-t and kmail2 crashed at startup
Classification: Unclassified
OS: Linux
  Reporter: flarel...@gmx.de
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.5)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-31-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
starting kontact after freshly started kubuntu12.04

- Unusual behavior I noticed:
virtuoso-t was crashing at startup of KDE 4.8.5 (Kubuntu packaged)

The crash does not seem to be reproducible.

-- 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 0x7f587b6d37c0 (LWP 2846))]

Thread 4 (Thread 0x7f585ea6e700 (LWP 2847)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7f5877ec9dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f5877ec9f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f587338de9a in start_thread (arg=0x7f585ea6e700) at
pthread_create.c:308
#4  0x7f5878bfb4bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()

Thread 3 (Thread 0x7f585e155700 (LWP 2848)):
#0  0x7f5878befb03 in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f5872ec1036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5872ec1164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5879370426 in QEventDispatcherGlib::processEvents
(this=0x7f58580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f587933fc82 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f587933fed7 in QEventLoop::exec (this=0x7f585e154dc0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f587923efa7 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f5879241fcb in QThreadPrivate::start (arg=0x1ca42f0) at
thread/qthread_unix.cpp:298
#8  0x7f587338de9a in start_thread (arg=0x7f585e155700) at
pthread_create.c:308
#9  0x7f5878bfb4bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x in ?? ()

Thread 2 (Thread 0x7f580f34e700 (LWP 2855)):
#0  0x7f5878befb03 in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f5872ec1036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5872ec1164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5879370426 in QEventDispatcherGlib::processEvents
(this=0x7f58080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f587933fc82 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f587933fed7 in QEventLoop::exec (this=0x7f580f34dd90, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f587923efa7 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7f587931f9ff in QInotifyFileSystemWatcherEngine::run (this=0x27cbff0)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x7f5879241fcb in QThreadPrivate::start (arg=0x27cbff0) at
thread/qthread_unix.cpp:298
#9  0x7f587338de9a in start_thread (arg=0x7f580f34e700) at
pthread_create.c:308
#10 0x7f5878bfb4bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x in ?? ()

Thread 1 (Thread 0x7f587b6d37c0 (LWP 2846)):
[KCrash Handler]
#6  activateInitialPluginModule (this=0x1aad3d0) at
../../../kontact/src/mainwindow.cpp:320
#7  Kontact::MainWindow::activateInitialPluginModule (this=0x1aad3d0) at
../../../kontact/src/mainwindow.cpp:315
#8  0x0040410a in KontactApp::newInstance (this=0x7fff7f5ea710) at
../../../kontact/src/main.cpp:147
#9  0x7f587aa79ba2 in KUniqueApplicationAdaptor::newInstance
(this=0x1c4d1d0, asn_id=..., args=...) at
../../kdeui/kernel/kuniqueapplication.cpp:442
#10 0x7f587aa79c24 in qt_static_metacall (_a=0x7fff7f5e99d0, _id=optimized
out, _o=optimized out, _c=optimized out) at ./kuniqueapplication_p.moc:58
#11 KUniqueApplicationAdaptor::qt_static_metacall (_o=optimized out,
_c=optimized out, _id=optimized out, _a=0x7fff7f5e99d0) at
./kuniqueapplication_p.moc:52
#12 0x7f587aa79d6b in KUniqueApplicationAdaptor::qt_metacall
(this=0x1c4d1d0, _c=QMetaObject::InvokeMetaMethod, _id=optimized out,
_a=0x7fff7f5e99d0) at ./kuniqueapplication_p.moc:102
#13 0x7f5875ac137b in 

[Bug 280102] KMail doesn't handle HTML anchors (regression from kde 4.4)

2012-09-24 Thread Tom Collins
https://bugs.kde.org/show_bug.cgi?id=280102

--- Comment #8 from Tom Collins ltski...@gmail.com ---
Thanks for checking it out.

-- 
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


[Bug 307360] New: Kontact Time Tracker Crash

2012-09-24 Thread Thomas Anderson
https://bugs.kde.org/show_bug.cgi?id=307360

Bug ID: 307360
  Severity: crash
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact Time Tracker Crash
Classification: Unclassified
OS: Linux
  Reporter: twanderso...@gmail.com
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.5)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-30-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed: opened the timetracker
component of KDE. Firefox was also open.

-- 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 0x7fbc502277c0 (LWP 2211))]

Thread 3 (Thread 0x7fbc335f9700 (LWP 2218)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7fbc4ca22dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fbc4ca22f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fbc47ee6e9a in start_thread (arg=0x7fbc335f9700) at
pthread_create.c:308
#4  0x7fbc4d7544bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()

Thread 2 (Thread 0x7fbc32ce0700 (LWP 2219)):
#0  0x7fbc47ee8f69 in __pthread_mutex_lock (mutex=0x7fbc2c000a60) at
pthread_mutex_lock.c:92
#1  0x7fbc47a555a1 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fbc47a1a150 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fbc4dec9426 in QEventDispatcherGlib::processEvents
(this=0x7fbc2c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7fbc4de98c82 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7fbc4de98ed7 in QEventLoop::exec (this=0x7fbc32cdfdc0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7fbc4dd97fa7 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7fbc4dd9afcb in QThreadPrivate::start (arg=0x2627b90) at
thread/qthread_unix.cpp:298
#8  0x7fbc47ee6e9a in start_thread (arg=0x7fbc32ce0700) at
pthread_create.c:308
#9  0x7fbc4d7544bd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x in ?? ()

Thread 1 (Thread 0x7fbc502277c0 (LWP 2211)):
[KCrash Handler]
#6  0x7fbbdc5d5d81 in timetrackerstorage::rawevents (this=0x43d5e20) at
../../ktimetracker/timetrackerstorage.cpp:321
#7  0x7fbbdc5f54dd in historydialog::listallevents (this=0x44aa480) at
../../ktimetracker/historydialog.cpp:102
#8  0x7fbbdc5f6bdc in historydialog::historydialog (this=0x44aa480,
parent=optimized out) at ../../ktimetracker/historydialog.cpp:82
#9  0x7fbbdc5d239a in EditTaskDialog::on_edittimespushbutton_clicked
(this=0x44b40e0) at ../../ktimetracker/edittaskdialog.cpp:103
#10 0x7fbbdc5cdbde in EditTaskDialog::qt_metacall (this=0x44b40e0,
_c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=optimized out) at
moc_edittaskdialog.cpp:91
#11 0x7fbc4deae489 in QMetaObject::activate (sender=0x42ecd70, m=optimized
out, local_signal_index=optimized out, argv=0x7fff8bc7b1d0) at
kernel/qobject.cpp:3566
#12 0x7fbc4ef23c72 in QAbstractButton::clicked (this=optimized out,
_t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:220
#13 0x7fbc4ec61a4e in QAbstractButtonPrivate::emitClicked (this=optimized
out) at widgets/qabstractbutton.cpp:548
#14 0x7fbc4ec62d8b in QAbstractButtonPrivate::click (this=0x44aba80) at
widgets/qabstractbutton.cpp:541
#15 0x7fbc4ec62ffc in QAbstractButton::mouseReleaseEvent (this=0x42ecd70,
e=0x7fff8bc7baa0) at widgets/qabstractbutton.cpp:1123
#16 0x7fbc4e8e4144 in QWidget::event (this=0x42ecd70, event=0x7fff8bc7baa0)
at kernel/qwidget.cpp:8362
#17 0x7fbc4e893894 in notify_helper (e=0x7fff8bc7baa0, receiver=0x42ecd70,
this=0x2623b50) at kernel/qapplication.cpp:4559
#18 QApplicationPrivate::notify_helper (this=0x2623b50, receiver=0x42ecd70,
e=0x7fff8bc7baa0) at kernel/qapplication.cpp:4531
#19 0x7fbc4e8990bf in QApplication::notify (this=optimized out,
receiver=0x42ecd70, e=0x7fff8bc7baa0) at kernel/qapplication.cpp:4102
#20 0x7fbc4f5cd3f6 in KApplication::notify (this=0x7fff8bc7ee80,
receiver=0x42ecd70, event=0x7fff8bc7baa0) at
../../kdeui/kernel/kapplication.cpp:311
#21 0x7fbc4de99e9c in QCoreApplication::notifyInternal
(this=0x7fff8bc7ee80, receiver=0x42ecd70, event=0x7fff8bc7baa0) at
kernel/qcoreapplication.cpp:876
#22 0x7fbc4e894862 in sendEvent (event=optimized out, receiver=optimized
out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QApplicationPrivate::sendMouseEvent (receiver=0x42ecd70,

[Bug 287140] editing a new time-planing item crashes Kontact

2012-09-24 Thread Jekyll Wu
https://bugs.kde.org/show_bug.cgi?id=287140

Jekyll Wu adap...@gmail.com changed:

   What|Removed |Added

 CC||twanderso...@gmail.com

--- Comment #16 from Jekyll Wu adap...@gmail.com ---
*** Bug 307360 has been marked as a duplicate of this bug. ***

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


[Bug 307360] Kontact Time Tracker Crash

2012-09-24 Thread Jekyll Wu
https://bugs.kde.org/show_bug.cgi?id=307360

Jekyll Wu adap...@gmail.com changed:

   What|Removed |Added

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

--- Comment #1 from Jekyll Wu adap...@gmail.com ---


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

-- 
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