[Bug 296246] New: When offline (on purpose) and marking a message to send, kmail asks to go online (and misspells word too). STOP ASKING.

2012-03-17 Thread Brendan Barry
https://bugs.kde.org/show_bug.cgi?id=296246

Bug ID: 296246
  Severity: normal
   Version: 4.8
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: When offline (on purpose) and marking a message to
send, kmail asks to go online (and misspells word
too). STOP ASKING.
Classification: Unclassified
OS: Linux
  Reporter: mailingl...@endosquid.com
  Hardware: Other
Status: UNCONFIRMED
 Component: general
   Product: kmail2

When offline (on purpose) and marking a message to send, kmail asks to go
online (and misspells word too). STOP ASKING PLEASE.

I work offline often, because I have sketchy net access. I set Kmail to be
offline. Then I go through 100 emails at a time and reply, so when I am back
online, I can send them.

Kmail apparently needs to ask me EVERY TIME if I want to go online, and does so
with a misspelled question:

"The mail dispatcher is offline, mails can not be send. Do you want to make it
online ?"

The word usage should be "sent".

Need a check box to disable this. I do not want to go online, and when I do, I
will make sure to let Kmail know!

Who ruined my poor kmail? It's so bad now...

-- 
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 281227] KMail2 4.7's "Find messages ..." reproducibly fails to search: "Unknown error. (Unable to create persistent search)"

2012-03-17 Thread Robin Green
https://bugs.kde.org/show_bug.cgi?id=281227

Robin Green  changed:

   What|Removed |Added

 CC||gree...@greenrd.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 296241] New: Find Messages in All Recipients returns no results

2012-03-17 Thread Robin Green
https://bugs.kde.org/show_bug.cgi?id=296241

Bug ID: 296241
  Severity: normal
   Version: 4.7
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Find Messages in All Recipients returns no results
Classification: Unclassified
OS: Linux
  Reporter: gree...@greenrd.org
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: filtering
   Product: kmail2

If I search for To contains linux-ker...@vger.kernel.org, I get plenty of
results as expected. But if I search for All Recipients contains
linux-ker...@vger.kernel.org, I get zero results.

-- 
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 292446] Stop button never enabled in "Find Messages" dialog

2012-03-17 Thread Robin Green
https://bugs.kde.org/show_bug.cgi?id=292446

Robin Green  changed:

   What|Removed |Added

 CC||gree...@greenrd.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 286043] possible data loss due to filtering (headers or body of email get lost)

2012-03-17 Thread András Manţia
https://bugs.kde.org/show_bug.cgi?id=286043

--- Comment #15 from András Manţia  ---
Milian, did you see this bug recently? It is very unclear for me what goes on,
and some of the comments seems to be unrelated (well, they might looks similar,
but they only confirm the result, not the possible cause).
All reporters seeing it: try to reproduce the bug, as right now I can't see
anything like this. Also me clear about what filter runs for the messages that
get lost (use the filter log from KMail), what kind of mailbox types you use
(for inbox and for the destination, e.g imap/maildir/mixedmaildir/mbox - in
case of mixedmaildir if it is a maildir or mbox) and if the mail is *really*
gone from your hard driver (or from the IMAP server in case of IMAP). 
The best would be to have a reproducible way for the 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 296216] Crash when changing folder or folder view

2012-03-17 Thread Andreas Karrenbauer
https://bugs.kde.org/show_bug.cgi?id=296216

--- Comment #1 from Andreas Karrenbauer  
---
Created attachment 69696
  --> https://bugs.kde.org/attachment.cgi?id=69696&action=edit
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) "release 481" using Qt 4.8.0

- What I was doing when the application crashed:
Advancing to the next unread feed in Akregator

-- Backtrace (Reduced):
#13 0x7f1fb2bee558 in QByteArray::realloc (this=0x7f1f38002188,
alloc=65504) at tools/qbytearray.cpp:1452
#14 0x7f1fb2bee679 in QByteArray::resize (this=0x7f1f38002188, size=32768)
at tools/qbytearray.cpp:1420
#15 0x7f1fadea5986 in reserve (bytes=2, this=0x7f1f38006c20) at
../../src/corelib/tools/qringbuffer_p.h:158
#16 QAbstractSocket::writeData (this=, data=0x7f1f2c2f164c
"\021", size=2) at socket/qabstractsocket.cpp:2315
#17 0x7f1fb2c7c82f in QIODevice::write (this=0x7f1f38001f00,
data=0x7f1f2c2f164c "\021", maxSize=) at io/qiodevice.cpp:1370

-- 
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 296216] Crash when changing folder or folder view

2012-03-17 Thread Andreas Karrenbauer
https://bugs.kde.org/show_bug.cgi?id=296216

Andreas Karrenbauer  changed:

   What|Removed |Added

 CC||andreas.karrenbauer@uni-kon
   ||stanz.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 295484] filtering removes email's content

2012-03-17 Thread András Manţia
https://bugs.kde.org/show_bug.cgi?id=295484

András Manţia  changed:

   What|Removed |Added

 CC||aman...@kde.org

--- Comment #10 from András Manţia  ---
I tried to reproduce the bug with today's master, but with no luck. The filter
code in master should be the same as in 4.8.1 and also the akonadi server
should be relatively the same as 1.7.1 (with some nepomuk related changes). 
What I tried:
- create rules for spamassasin and bogofilter with the anti-spam wizard. I
changed them to move the spam to a specific folder instead of Local Mail/trash.
- check that rules apply both to imap (disconnected) and POP3 accounts (local
mail folder)
- send spam to these addresses: spam was caught, marked and move to the spam
folder. The mails were not destroyed, only some headers added.
- send not-spam (including html mail and mails with attachment) to the
accounts. I checked that extra headers were added by the spam filter, but
still, the mail structure was not destroyed, I could read it and access the
attachment.

The only problem I noticed was the spam mails multiplying in the spam folder
after they were moved there, but that is another bug.

So what did I do wrong? How can I really reproduce the bug?
For the reporters, try to enable the folter log and post what filters are
running on the mails that get destroyed. You could also start akonadi from a
console after enabling the debug info for the filter agent and akonadi with
kdebugdialog (enable for libakonadi, akonadi_mailfilter_agent and restart with
"akonadictl restart").
The akonadiconsole's debugger for the mailfilter agent could also help to see
what is going on, just don't forget to disable the debugger when not needed, as
it slows down the operations.

-- 
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 296238] New: Change link name "Complete Story"

2012-03-17 Thread Frederik Schwarzer
https://bugs.kde.org/show_bug.cgi?id=296238

Bug ID: 296238
  Severity: wishlist
   Version: 1.6.5
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Change link name "Complete Story"
Classification: Unclassified
OS: Linux
  Reporter: schwar...@kde.org
  Hardware: Other
Status: NEW
 Component: general
   Product: akregator

The link "Complete Story" should be renamed in times where the vast majority of
feeds sends the complete story. Something like "Open Website" might be more
appropriate.

-- 
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 293284] After adding a CalDav resource to akonadi I get the following error message: Unknown error. (Unable to fetch from backend)

2012-03-17 Thread dotred
https://bugs.kde.org/show_bug.cgi?id=293284

dotred  changed:

   What|Removed |Added

 CC||erasmocapo...@tiscali.it

--- Comment #6 from dotred  ---
Same problem here.
Kubuntu 11.10 with KDE 4.8.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 296226] New: Kontact crashed on startup

2012-03-17 Thread Elias Probst
https://bugs.kde.org/show_bug.cgi?id=296226

Bug ID: 296226
  Severity: crash
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact crashed on startup
Classification: Unclassified
OS: Linux
  Reporter: m...@eliasprobst.eu
  Hardware: Compiled Sources
Status: NEW
 Component: general
   Product: kontact

Application: kontact (4.8.0)
KDE Platform Version: 4.8.1 (4.8.1) (Compiled from sources)
Qt Version: 4.8.0
Operating System: Linux 3.2.6-gentoo x86_64
Distribution: "Gentoo Base System release 2.0.3"

-- Information about the crash:
- What I was doing when the application crashed:
I started Kontact and it crashed during startup, before any window showed up.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7fc2baac4760 (LWP 6091))]

Thread 3 (Thread 0x7fc2a0ae1700 (LWP 6092)):
#0  pthread_cond_wait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7fc2b729ede4 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/qt4/libQtWebKit.so.4
#2  0x7fc2b2904c4c in start_thread (arg=0x7fc2a0ae1700) at
pthread_create.c:301
#3  0x7fc2b7fdffcd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7fc2a01e0700 (LWP 6093)):
#0  g_main_context_query (context=0x644470, max_priority=2147483647,
timeout=0x7fc2a01dfcf8, fds=, n_fds=1) at gmain.c:2864
#1  0x7fc2b194f486 in g_main_context_iterate (context=0x644470, block=1,
dispatch=1, self=) at gmain.c:3071
#2  0x7fc2b194f9a4 in g_main_context_iteration (context=0x644470,
may_block=1) at gmain.c:3152
#3  0x7fc2b9401916 in QEventDispatcherGlib::processEvents (this=0x644390,
flags=) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7fc2b93d17a2 in QEventLoop::processEvents (this=,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7fc2b93d1a55 in QEventLoop::exec (this=0x7fc2a01dfe20, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7fc2b92cf098 in QThread::exec (this=) at
thread/qthread.cpp:501
#7  0x7fc2b92d170b in QThreadPrivate::start (arg=0x643cb0) at
thread/qthread_unix.cpp:298
#8  0x7fc2b2904c4c in start_thread (arg=0x7fc2a01e0700) at
pthread_create.c:301
#9  0x7fc2b7fdffcd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7fc2baac4760 (LWP 6091)):
[KCrash Handler]
#6  0x7fc2b7f3ba55 in *__GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x7fc2b7f3cd55 in *__GI_abort () at abort.c:92
#8  0x7fc2b92c7904 in qt_message_output (msgType=,
buf=) at global/qglobal.cpp:2252
#9  0x7fc2b92c7a9d in qt_message(QtMsgType, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7fc2577646b0 "Fatal
Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d",
ap=0x7fff9f31f4a0) at global/qglobal.cpp:2298
#10 0x7fc2b92c7c35 in qFatal (msg=) at
global/qglobal.cpp:2481
#11 0x7fc257710d31 in operator-> (this=) at
/var/tmp/portage/kde-base/kmail-4.8.1/work/kmail-4.8.1/mailcommon/mailkernel.cpp:48
#12 0x7fc257710d99 in MailCommon::Kernel::self () at
/var/tmp/portage/kde-base/kmail-4.8.1/work/kmail-4.8.1/mailcommon/mailkernel.cpp:64
#13 0x7fc2576ff680 in MailCommon::FolderCollection::writeConfig
(this=0x1604ff0) at
/var/tmp/portage/kde-base/kmail-4.8.1/work/kmail-4.8.1/mailcommon/foldercollection.cpp:209
#14 0x7fc2576ffb21 in MailCommon::FolderCollection::~FolderCollection
(this=0x1604ff0, __in_chrg=) at
/var/tmp/portage/kde-base/kmail-4.8.1/work/kmail-4.8.1/mailcommon/foldercollection.cpp:82
#15 0x7fc2576ffbb9 in MailCommon::FolderCollection::~FolderCollection
(this=0x1604ff0, __in_chrg=) at
/var/tmp/portage/kde-base/kmail-4.8.1/work/kmail-4.8.1/mailcommon/foldercollection.cpp:84
#16 0x7fc2576dcc3c in
QtSharedPointer::ExternalRefCount::deref
(d=0x1468e90, value=0x1604ff0) at
/usr/include/qt4/QtCore/qsharedpointer_impl.h:342
#17 0x7fc2576ff24d in QMap >::freeData (x=0x144d7c0,
this=) at /usr/include/qt4/QtCore/qmap.h:651
#18 0x7fc2b7f3e3b1 in __run_exit_handlers (status=255,
listp=0x7fc2b828b4c8, run_list_atexit=true) at exit.c:78
#19 0x7fc2b7f3e405 in *__GI_exit (status=6091) at exit.c:100
#20 0x7fc2b9882a7f in KCmdLineArgs::isSet (this=0x2bcd410, _opt=) at
/var/tmp/portage/kde-base/kdelibs-4.8.1-r1/work/kdelibs-4.8.1/kdecore/kernel/kcmdlineargs.cpp:1510
#21 0x0040340d in KontactApp::newInstance (this=0x7fff9f320b80) at
/var/tmp/portage/kde-base/kontact-4.8.1/work/kontact-4.8.1/kontact/src/main.cpp:129
#22 0x7fc2b9e7fa52 in KUniqueApplicationAdaptor::newInstance
(this=0x7ec560, asn_id=, args=...) at
/var/tmp/portage/kde-base/kdelibs-4.8.1-r1/work/kdelibs-4.8.1/kdeui/kernel/kuniqueapplication.cpp:442
#23 0x7fc2b9e7fad4 in KUniqueApplicationAdaptor::qt_static_metacall
(_o=, _c=, _id=,
_a=0

[Bug 284224] maildir resource does not become AgentBase::Broken when started without a valid maildir path

2012-03-17 Thread Ed Tomlinson
https://bugs.kde.org/show_bug.cgi?id=284224

Ed Tomlinson  changed:

   What|Removed |Added

 CC||e...@aei.ca

--- Comment #6 from Ed Tomlinson  ---
Think this bug is not 100% fixed in 4.8.1.  You can generate it by trying to
add a new maildir.  Kmail will post a message that the resource is broken.  If
you type in a full mairdir path, for a new maildir directory, it will let you
proceed.

-- 
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 296216] New: Crash when changing folder or folder view

2012-03-17 Thread kuede
https://bugs.kde.org/show_bug.cgi?id=296216

Bug ID: 296216
  Severity: crash
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Crash when changing folder or folder view
Classification: Unclassified
OS: Linux
  Reporter: kur...@gmx.ch
  Hardware: openSUSE RPMs
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.0)
KDE Platform Version: 4.8.1 (4.8.1) "release 481"
Qt Version: 4.8.0
Operating System: Linux 3.1.9-1.4-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

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

kontact is crashing after upgrade from 4.8.0 to 4.8.1 every now and then. It is
not only switching folders but also selecting e-mails (mostly unread) or also
changing sorting (received, importance etc.). It seems to happen more often
when contacting the remote inboxes (pop or IMAP) is slow. Backtrace below
should be from switching sorting (where the importance sorting doesn't seem to
work.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7f4c66042760 (LWP 15354))]

Thread 5 (Thread 0x7f4c4db4b700 (LWP 15355)):
#0  0x7f4c5ded3e6c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f4c62862c12 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x7f4c62862c49 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x7f4c5decff05 in start_thread () from /lib64/libpthread.so.0
#4  0x7f4c6355410d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f4c4d232700 (LWP 15356)):
#0  0x7f4c5ded201e in pthread_mutex_lock () from /lib64/libpthread.so.0
#1  0x7f4c5d9c0f44 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f4c63cc1956 in QEventDispatcherGlib::processEvents
(this=0x7f4c480008c0, flags=) at
kernel/qeventdispatcher_glib.cpp:426
#3  0x7f4c63c91682 in QEventLoop::processEvents (this=,
flags=...) at kernel/qeventloop.cpp:149
#4  0x7f4c63c918d7 in QEventLoop::exec (this=0x7f4c4d231e20, flags=...) at
kernel/qeventloop.cpp:204
#5  0x7f4c63b92537 in QThread::exec (this=) at
thread/qthread.cpp:501
#6  0x7f4c63b9555b in QThreadPrivate::start (arg=0x830ca0) at
thread/qthread_unix.cpp:298
#7  0x7f4c5decff05 in start_thread () from /lib64/libpthread.so.0
#8  0x7f4c6355410d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f4bf2321700 (LWP 17711)):
#0  0x7f4c5ded41eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f4c63b959cf in wait (time=3, this=0xe92c10) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=, mutex=0xe92b88, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f4c63b88ddf in QThreadPoolThread::run (this=0xea6230) at
concurrent/qthreadpool.cpp:141
#4  0x7f4c63b9555b in QThreadPrivate::start (arg=0xea6230) at
thread/qthread_unix.cpp:298
#5  0x7f4c5decff05 in start_thread () from /lib64/libpthread.so.0
#6  0x7f4c6355410d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f4bf303b700 (LWP 17717)):
[KCrash Handler]
#10 0x7f4c634efa38 in malloc_consolidate () from /lib64/libc.so.6
#11 0x7f4c634f0bf3 in _int_malloc () from /lib64/libc.so.6
#12 0x7f4c634f383e in malloc () from /lib64/libc.so.6
#13 0x7f4c63b97558 in QByteArray::realloc (this=0x7f4be8001c58,
alloc=65504) at tools/qbytearray.cpp:1452
#14 0x7f4c63b97679 in QByteArray::resize (this=0x7f4be8001c58, size=32768)
at tools/qbytearray.cpp:1420
#15 0x7f4c5ee6e986 in reserve (bytes=2, this=0x7f4be8002e70) at
../../src/corelib/tools/qringbuffer_p.h:158
#16 QAbstractSocket::writeData (this=, data=0x7f4bf303a64c
"\021", size=2) at socket/qabstractsocket.cpp:2315
#17 0x7f4c63c2582f in QIODevice::write (this=0x7f4be8005600,
data=0x7f4bf303a64c "\021", maxSize=) at io/qiodevice.cpp:1370
#18 0x7f4c571afb25 in ?? () from /usr/lib64/libsopranoclient.so.1
#19 0x7f4c571b6cba in ?? () from /usr/lib64/libsopranoclient.so.1
#20 0x7f4c571b8803 in ?? () from /usr/lib64/libsopranoclient.so.1
#21 0x7f4c5b72764c in ?? () from /usr/lib64/libnepomuk.so.4
#22 0x7f4c5b713eb3 in ?? () from /usr/lib64/libnepomuk.so.4
#23 0x7f4c5b7147bc in ?? () from /usr/lib64/libnepomuk.so.4
#24 0x7f4c5b72a7e3 in Nepomuk::Resource::property(QUrl const&) const ()
from /usr/lib64/libnepomuk.so.4
#25 0x7f4c0495b0ca in ?? () from /usr/lib64/libmessagecore.so.4
#26 0x7f4c63b88d12 in QThreadPoolThread::run (this=0x1d83550) at
concurrent/qthreadpool.cpp:107
#27 0x7f4c63b9555b in QThreadPrivate::start (arg=0x1d83550) at
thread/qthread_unix.cpp:298
#28 0x7f4c5decff05 in start_thread () from /lib64/libpthread.so.0
#29 0x7f4c6355410d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f4c66042760 (LWP 15354)):
[KCrash Handler]
#6  0x7f4c634add95 in raise () from /lib64/libc.so.6
#7  0x7f

[Bug 296034] Crash while changing folder

2012-03-17 Thread Jeff Smith
https://bugs.kde.org/show_bug.cgi?id=296034

--- Comment #1 from Jeff Smith  ---
Created attachment 69691
  --> https://bugs.kde.org/attachment.cgi?id=69691&action=edit
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

- What I was doing when the application crashed:

Simply changing folders. Acutally, completely random. Happens when chaning
folders, scrolling through a folder...it seems to happen displaying an email in
the preview pane. I have noticed that if a folder is empy and Kmail retrieves
mail, the first mail that gets into folder starts to display in the preview
pane and then it crashes. Its really annoying!

-- Backtrace (Reduced):
#10 0xb622a1cb in qMalloc (size=65536) at global/qmalloc.cpp:55
#11 0xb623405a in QByteArray::realloc (this=0x917ab34, alloc=65516) at
tools/qbytearray.cpp:1452
#12 0xb6234177 in QByteArray::resize (this=0x917ab34, size=32768) at
tools/qbytearray.cpp:1420
#13 0xb3d79f82 in reserve (bytes=2, this=0x917aa88) at
../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:158
#14 QAbstractSocket::writeData (this=0x917a974, data=0xac62becc "\021", size=2)
at socket/qabstractsocket.cpp:2315

-- 
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 296034] Crash while changing folder

2012-03-17 Thread Jeff Smith
https://bugs.kde.org/show_bug.cgi?id=296034

Jeff Smith  changed:

   What|Removed |Added

 CC||jdsmi...@msn.com

-- 
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 296201] New: Cannot open initial 2nd mail item, after moving to trash initial 1st item of the list

2012-03-17 Thread Frans Leerink
https://bugs.kde.org/show_bug.cgi?id=296201

Bug ID: 296201
  Severity: normal
   Version: 4.7
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Cannot open initial 2nd mail item, after moving to
trash initial 1st item of the list
Classification: Unclassified
OS: Linux
  Reporter: f.leer...@xs4all.nl
  Hardware: openSUSE RPMs
Status: UNCONFIRMED
 Component: general
   Product: kmail2

Hello,
In the incoming mail list I cannot open the initial 2nd item, after 
moving to trash the 1st item of the list.
To read the initial 2nd item I have to select first an other mail item 
and than reselect the initial 2nd item.
I read my mail on a separate screen. 


HOW TO CREATE THIS PROBLEM
1. Read 1st mail item of the list, return to the list and move 1st item 
to trash
2. Select initial 2nd item for reading on seperate screen
3.


WHAT HAPPENED
At the end of step 1 the 1 st mail item of list is moved to trash and 
deleted from the list
In step 2 system does not display, the selected, initial 2nd item on 
separate screen


WHAT SHOULD HAVE HAPPENED
That in step 2 the initial 2nd item is displayed on the separate screen


REMARKS
To overcome this problem I have first to select an other item of the 
list (without reading) and than reselect the initial 2nd item

-- 
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 296199] New: Kontact crash on startup

2012-03-17 Thread Sabariel
https://bugs.kde.org/show_bug.cgi?id=296199

Bug ID: 296199
  Severity: crash
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: Kontact crash on startup
Classification: Unclassified
OS: Linux
  Reporter: mia.hom...@eregion.de
  Hardware: openSUSE RPMs
Status: UNCONFIRMED
 Component: general
   Product: kontact

Application: kontact (4.8.0)
KDE Platform Version: 4.8.1 (4.8.1) "release 481"
Qt Version: 4.8.0
Operating System: Linux 3.1.9-1.4-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

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

starting kontact.

note: i closed kontact before this after getting several confusing error
messages from akonadi, mostly "unknown error"

The crash can be reproduced some of the time.

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

Thread 3 (Thread 0x7f5997386700 (LWP 9143)):
#0  0x7f59a7a48e6c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f59ac3d7c12 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x7f59ac3d7c49 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x7f59a7a44f05 in start_thread () from /lib64/libpthread.so.0
#4  0x7f59ad0c910d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f5996a85700 (LWP 9144)):
#0  0x7f59ad0bfff3 in poll () from /lib64/libc.so.6
#1  0x7f59a7535a98 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f59a7535f59 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f59ad836956 in QEventDispatcherGlib::processEvents
(this=0x7f5998c0, flags=) at
kernel/qeventdispatcher_glib.cpp:426
#4  0x7f59ad806682 in QEventLoop::processEvents (this=,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7f59ad8068d7 in QEventLoop::exec (this=0x7f5996a84e20, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7f59ad707537 in QThread::exec (this=) at
thread/qthread.cpp:501
#7  0x7f59ad70a55b in QThreadPrivate::start (arg=0x63bc50) at
thread/qthread_unix.cpp:298
#8  0x7f59a7a44f05 in start_thread () from /lib64/libpthread.so.0
#9  0x7f59ad0c910d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f59afbbc760 (LWP 9141)):
[KCrash Handler]
#6  QString (other=) at /usr/include/QtCore/qstring.h:725
#7  KontactInterface::Plugin::identifier (this=0x8040608) at
/usr/src/debug/kdepimlibs-4.8.1/kontactinterface/plugin.cpp:101
#8  0x7f59af7da42f in activateInitialPluginModule (this=0x802450) at
/usr/src/debug/kdepim-4.8.1/kontact/src/mainwindow.cpp:320
#9  Kontact::MainWindow::activateInitialPluginModule (this=0x802450) at
/usr/src/debug/kdepim-4.8.1/kontact/src/mainwindow.cpp:315
#10 0x004043fa in KontactApp::newInstance (this=0x7fff5d9ba9f0) at
/usr/src/debug/kdepim-4.8.1/kontact/src/main.cpp:147
#11 0x7f59aef64e12 in KUniqueApplicationAdaptor::newInstance
(this=0x7e6030, asn_id=, args=...) at
/usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kuniqueapplication.cpp:442
#12 0x7f59aef64e94 in qt_static_metacall (_a=0x7fff5d9b9c80, _id=, _o=, _c=) at
/usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:58
#13 KUniqueApplicationAdaptor::qt_static_metacall (_o=,
_c=, _id=, _a=0x7fff5d9b9c80) at
/usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:52
#14 0x7f59aef64fdb in KUniqueApplicationAdaptor::qt_metacall
(this=0x7e6030, _c=QMetaObject::InvokeMetaMethod, _id=,
_a=0x7fff5d9b9c80) at
/usr/src/debug/kdelibs-4.8.1/build/kdeui/kuniqueapplication_p.moc:102
#15 0x7f59aa208f6b in QDBusConnectionPrivate::deliverCall (this=0x62c6e0,
object=0x7e6030, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:947
#16 0x7f59aa20a13d in QDBusConnectionPrivate::activateCall (this=0x62c6e0,
object=0x7e6030, flags=337, msg=...) at qdbusintegrator.cpp:857
#17 0x7f59aa20aa9b in QDBusConnectionPrivate::activateObject
(this=0x62c6e0, node=..., msg=..., pathStartPos=) at
qdbusintegrator.cpp:1423
#18 0x7f59aa20ab8b in QDBusActivateObjectEvent::placeMetaCall
(this=0x7f7ae0) at qdbusintegrator.cpp:1537
#19 0x7f59ad820926 in QObject::event (this=0x7fff5d9ba9f0, e=) at kernel/qobject.cpp:1204
#20 0x7f59ae21ed84 in QApplication::event (this=0x7fff5d9ba9f0, e=0x7f7ae0)
at kernel/qapplication.cpp:2532
#21 0x7f59ae21ae84 in notify_helper (e=0x7f7ae0, receiver=0x7fff5d9ba9f0,
this=0x63d180) at kernel/qapplication.cpp:4550
#22 QApplicationPrivate::notify_helper (this=0x63d180, receiver=0x7fff5d9ba9f0,
e=0x7f7ae0) at kernel/qapplication.cpp:4522
#23 0x7f59ae21fd03 in QApplication::notify (this=0x7fff5d9ba9f0,
receiver=0x7fff5d9ba9f0, e=0x7f7ae0) at kernel/qapplication.cpp:4411
#24 0x7f59aef5f656 in KApplication::notify (this=0x7fff5d9ba9f0,
receiver=0x7fff5d9ba9f0, event=0x7f7ae0) at
/usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311
#25 0x7f

[Bug 288040] kmail2 fails to remove duplicate mails from folder

2012-03-17 Thread Mark Fraser
https://bugs.kde.org/show_bug.cgi?id=288040

Mark Fraser  changed:

   What|Removed |Added

 CC||k...@mfraz.orangehome.co.uk

--- Comment #8 from Mark Fraser  ---
I've recently upgraded to Kubuntu 11.10 and KDE 4.8. Trying to sort my emails
out, I found that I have multiple copies of some emails in a few folders.
Trying "remove duplicate mails" doesn't work.

-- 
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 278020] KMail cannot send e-mail via SMTP

2012-03-17 Thread Mark Fraser
https://bugs.kde.org/show_bug.cgi?id=278020

Mark Fraser  changed:

   What|Removed |Added

 CC||k...@mfraz.orangehome.co.uk

-- 
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 283988] Akregator crashed when i tried to close a tab

2012-03-17 Thread Galeffi Christian
https://bugs.kde.org/show_bug.cgi?id=283988

--- Comment #33 from Galeffi Christian  ---
Created attachment 69688
  --> https://bugs.kde.org/attachment.cgi?id=69688&action=edit
New crash information added by DrKonqi

kontact (4.7.2) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4

Still crash when clossing tab

-- Backtrace (Reduced):
#7  0x7faddca3784e in KParts::StatusBarExtension::statusBar() const () from
/usr/lib64/libkparts.so.4
#8  0x7faddca37d54 in KParts::StatusBarExtension::~StatusBarExtension() ()
from /usr/lib64/libkparts.so.4
#9  0x7faddca38109 in KParts::StatusBarExtension::~StatusBarExtension() ()
from /usr/lib64/libkparts.so.4
#10 0x7fadde0f9465 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQtCore.so.4
#11 0x7fadde0fea09 in QObject::~QObject() () from /usr/lib64/libQtCore.so.4

-- 
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 283988] Akregator crashed when i tried to close a tab

2012-03-17 Thread Galeffi Christian
https://bugs.kde.org/show_bug.cgi?id=283988

Galeffi Christian  changed:

   What|Removed |Added

 CC||c...@gallochri.com

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