[Bug 279297] Not all new mails are downloaded
https://bugs.kde.org/show_bug.cgi?id=279297 --- Comment #16 from Christian Trippe 2011-09-20 04:42:33 --- (In reply to comment #14) > The problem did not occur prior to KDE 4.7.0, right? Yes, I have never seen this with kmail2 prior to 4.7.0. And thanks for your work on the bug! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282374] New: "Kmail folders" and "Local folders" sets appear both in folders collection
https://bugs.kde.org/show_bug.cgi?id=282374 Summary: "Kmail folders" and "Local folders" sets appear both in folders collection Product: kmail2 Version: 4.7 Platform: openSUSE RPMs OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: folders AssignedTo: kdepim-bugs@kde.org ReportedBy: tibi...@kde.org Version: 4.7 (using KDE 4.7.1) OS:Linux Since upgrading to kmail2, both "KMail folders" and "Local folders" folder collections (inbox, outbox, draft, trash etc.) appear in the main folder collection of kmail. I can see in the Akonadi configuration where the "Local folders" are coming from. Trying to remove them has no result, as they automatically reappear. There is no immediately evident source/reason for "KMail folders" to appear too and no evident way to remove them. This is confusing and useless. Reproducible: Always Steps to Reproduce: Update to kmail2 in a user directory that already contains KDE 4.6.5 configuration data (and user used to use kmail1). Look at default folder collections (before adding any other configuration). Actual Results: Both "KMail folders" and "Local folders" appear. None of these are removable. Expected Results: Only one of these two should appear. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282245] namespaces configuration still required
https://bugs.kde.org/show_bug.cgi?id=282245
--- Comment #5 from Cristian Tibirna 2011-09-20 00:39:40 ---
openssl s_client -connect @@@:# -quiet
* OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS AUTH=PLAIN
AUTH=LOGIN] merlin.giref.ulaval.ca IMAP4rev1 2004.357 at Mon, 19 Sep 2011
20:12:38 -0400 (EDT)
A LOGIN ctibirna **
A OK [CAPABILITY IMAP4REV1 LITERAL+ IDLE NAMESPACE MAILBOX-REFERRALS BINARY
UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User
ctibirna authenticated
B NAMESPACE
* NAMESPACE (("" "/")("#mhinbox" NIL)("#mh/" "/")) (("~" "/")) (("#shared/"
"/")("#ftp/" "/")("#news." ".")("#public/" "/"))
B OK NAMESPACE completed
The LIST command returned the full list of all files contained in my user home
directory, including all hidden files and contents of hidden (dot) directories.
This is absolutely huge, 80K lines, it can take anywhere from 15s to receive on
local (fast) network, and up to many minutes, depending on server load. This is
why I don't paste that here. The format returned is absolutely standard. For
example:
- for directories:
* LIST (\NoSelect) "/" imap-mail/WORK/ATTIC
- for files:
* LIST (\NoInferiors \UnMarked) "/" imap-mail/WORK/ATTIC/fvwm
At the end, as expected:
C OK LIST completed
The LSUB command returns whatever filename I had put in ~/.mailboxlist on the
server in order to try to work around the issue. E.g.:
D LSUB "" *
* LSUB () "/" imap-mail/WORK/ATTIC/fvwm
D OK LSUB completed
Worthy notices:
- as you can see, this is a rather old (and presumably very well known) server
software. It is the UW imapd, which was the "de facto" testing implementation
for the imap protocol, I guess.
- this exactly same server works perfectly with kmail1
- once one worked around this particular problem, many many other issues
appear:
- unuseable slowliness,
- akonadi full blocking,
- server-side access locking (probably throught DoS; no other clients can
access the mailboxes other than read-only)
- deleted messages reappear at next kmail2 restart etc.
Thanks for your attention.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- 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 282245] namespaces configuration still required
https://bugs.kde.org/show_bug.cgi?id=282245 --- Comment #4 from Cristian Tibirna 2011-09-20 00:16:00 --- Sorry for writing to your directly, Kevin. Unfortunately, I was forced to realize that the bug I reported was the least of my problems with this version of KMail. Once I worked around the first configuration blocking (by using serverside subscription), I discovered that: - the akonadi ressource for this server was unuseably slow (takes 15 to 20 minutes to upgrade a 12 message folder) - while updating this ressource, akonadi blocks completely; - it seems to block even the "Local folders ressource"; - messages deleted reappear in the folder after restart - often deleting is not possible (move to trash is grayed out) - the "Del" shortcut gets confused _after a while_ and refuses to act, with a popup message that says all of a sudden that it is confused because double assignment (this despite me not doing anything at all with the computer in the last 2 hours) - worst of all, if this ressource is active in akonadi, no other imap client can access the corresponding imap server other than read-only. These widespread failures seem to manifest only As I depend on my e-mail for 80% of my daily activity, and since I only have one machine to work with, and since I can't stand thunderbird, I will be forced for now to go back to kmail1, which works marvelously. Sorry for this. I will add anyways the information you required to the bugreport. Thanks a lot for your attention. On September 19, 2011 05:45:48 Kevin Ottens wrote: > https://bugs.kde.org/show_bug.cgi?id=282245 > > > > > > --- Comment #3 from Kevin Ottens 2011-09-19 05:45:48 --- > Any chance you could at least telnet the server and give me the output of > the NAMESPACE command? > > The "script" would be connecting using telnet then: > A LOGIN username password > B NAMESPACE > > I'm interested in the output of B. > Optionnally that would be nice if you could also give me the output of: > C LIST "" * > D LSUB "" * > > That said those two will likely contain private data, feel free to change > folders names if needed but not anything else. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282371] New: crash on mail filtering (sent mail)
https://bugs.kde.org/show_bug.cgi?id=282371 Summary: crash on mail filtering (sent mail) Product: kmail2 Version: 4.8 pre Platform: Archlinux Packages OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: m...@milianw.de Application: kmail (4.8 pre) KDE Platform Version: 4.7.1 (4.7.1) Qt Version: 4.7.4 Operating System: Linux 3.0-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I wrote an email, pressed send and kmail crashed. I have lots of filters, some also apply to outgoing/sent email like this one, which is probably related looking at the bt. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f5870b10780 (LWP 25311))] Thread 6 (Thread 0x7f5854888700 (LWP 25312)): #0 0x7f586a066613 in select () from /lib/libc.so.6 #1 0x7f586adf64a1 in ?? () from /usr/lib/libQtCore.so.4 #2 0x7f586ad2dbc5 in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f586aaa3da0 in start_thread () from /lib/libpthread.so.0 #4 0x7f586a06c7dd in clone () from /lib/libc.so.6 #5 0x in ?? () Thread 5 (Thread 0x7f5853e8e700 (LWP 25334)): #0 0x7f586aaa7b04 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f5863e535ba in ?? () from /usr/lib/libQtWebKit.so.4 #2 0x7f5863e536a9 in ?? () from /usr/lib/libQtWebKit.so.4 #3 0x7f586aaa3da0 in start_thread () from /lib/libpthread.so.0 #4 0x7f586a06c7dd in clone () from /lib/libc.so.6 #5 0x in ?? () Thread 4 (Thread 0x7f5853575700 (LWP 25335)): #0 0xff60017b in ?? () #1 0x7f5853574b60 in ?? () #2 0x7fff781ff7e7 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 3 (Thread 0x7f584b873700 (LWP 6342)): #0 0x7f586aaa7e7b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f586ad2dfde in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f586ad2297f in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f586ad2dbc5 in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f586aaa3da0 in start_thread () from /lib/libpthread.so.0 #5 0x7f586a06c7dd in clone () from /lib/libc.so.6 #6 0x in ?? () Thread 2 (Thread 0x7f58517ff700 (LWP 6343)): #0 0x7f586aaa7e7b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f586ad2dfde in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #2 0x7f586ad2297f in ?? () from /usr/lib/libQtCore.so.4 #3 0x7f586ad2dbc5 in ?? () from /usr/lib/libQtCore.so.4 #4 0x7f586aaa3da0 in start_thread () from /lib/libpthread.so.0 #5 0x7f586a06c7dd in clone () from /lib/libc.so.6 #6 0x in ?? () Thread 1 (Thread 0x7f5870b10780 (LWP 25311)): [KCrash Handler] #6 0x7f586708baab in QBasicAtomicInt::ref (this=0x64007000750020) at /usr/include/QtCore/qatomic_x86_64.h:121 #7 0x7f586708d2aa in QString::QString (this=0x7fff7805eff0, other=...) at /usr/include/QtCore/qstring.h:729 #8 0x7f58670d4545 in MailCommon::MailFilter::identifier (this=0x1505930) at /home/milian/projects/kde4/kdepim/mailcommon/mailfilter.cpp:112 #9 0x7f586f8891e6 in KMFilterActionCommand::execute (this=0x7e37ff0) at /home/milian/projects/kde4/kdepim/kmail/kmcommands.cpp:1338 #10 0x7f586f881a99 in KMCommand::slotPostTransfer (this=0x7e37ff0, result=KMCommand::OK) at /home/milian/projects/kde4/kdepim/kmail/kmcommands.cpp:267 #11 0x7f586f88abf3 in KMCommand::qt_metacall (this=0x7e37ff0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7fff7805f190) at /home/milian/projects/.build/kde4/kdepim/kmail/kmcommands.moc:88 #12 0x7f586f88bfd6 in KMFilterActionCommand::qt_metacall (this=0x7e37ff0, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x7fff7805f190) at /home/milian/projects/.build/kde4/kdepim/kmail/kmcommands.moc:1230 #13 0x7f586ae275ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #14 0x7f586f88ac7c in KMCommand::messagesTransfered (this=0x7e37ff0, _t1=KMCommand::OK) at /home/milian/projects/.build/kde4/kdepim/kmail/kmcommands.moc:103 #15 0x7f586f882066 in KMCommand::slotJobFinished (this=0x7e37ff0) at /home/milian/projects/kde4/kdepim/kmail/kmcommands.cpp:377 #16 0x7f586f88ac1d in KMCommand::qt_metacall (this=0x7e37ff0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x7fff7805f310) at /home/milian/projects/.build/kde4/kdepim/kmail/kmcommands.moc:90 #17 0x7f586f88bfd6 in KMFilterActionCommand::qt_metacall (this=0x7e37ff0, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fff7805f310) at /home/milian/projects/.build/kde4/kdepim/kmail/kmcommands.moc:1230 #18 0x7f586ae275ea in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /u
[Bug 254750] Crash when MDN request acknowledged [KMMessage::headerField, KMMessage::identityUoid, KMMessage::createMDN]
https://bugs.kde.org/show_bug.cgi?id=254750 --- Comment #4 from Joshua J. Kugler 2011-09-19 22:25:07 --- Created an attachment (id=63785) --> (http://bugs.kde.org/attachment.cgi?id=63785) New crash information added by DrKonqi kmail (1.13.6) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2 I received an e-mail that requested a delivery notification. I clicked "ignore" and KMail crashed. -- Backtrace (Reduced): #8 0x00f75810 in KMMessage::createMDN (this=0xb13c4f0, a=KMime::MDN::ManualAction, d=KMime::MDN::Displayed, allowGUI=true, m=...) at ../../kmail/kmmessage.cpp:1141 #9 0x0103e9bf in KMReaderWin::slotTouchMessage (this=0x8a8e8d8) at ../../kmail/kmreaderwin.cpp:1889 #10 0x01048003 in KMReaderWin::qt_metacall (this=0x8a8e8d8, _c=QMetaObject::InvokeMetaMethod, _id=37, _a=0xbfe16a6c) at ./kmreaderwin.moc:210 [...] #13 0x005392f7 in QTimer::timeout (this=0x8a8e960) at .moc/release-shared/moc_qtimer.cpp:134 #14 0x004f23ee in QTimer::timerEvent (this=0x8a8e960, e=0xbfe16f8c) at kernel/qtimer.cpp:271 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 254750] Crash when MDN request acknowledged [KMMessage::headerField, KMMessage::identityUoid, KMMessage::createMDN]
https://bugs.kde.org/show_bug.cgi?id=254750 Joshua J. Kugler changed: What|Removed |Added CC||jos...@joshuakugler.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282309] After update, Kontact "is running on another display" and then shuts down
https://bugs.kde.org/show_bug.cgi?id=282309 --- Comment #2 from Karel Vorster 2011-09-19 22:14:59 --- Hi I have just spent 3 hours rebuilding a new home directory. Kontact is no longer crashing - like I said. Now, no email text in the body is shown. I can not send any mail, and can not check my settings online - "See what the server supports" button, as it crashes immediately. FIX THIS SOFTWARE!!! On 9/18/11, Christophe Giboudeaux wrote: > https://bugs.kde.org/show_bug.cgi?id=282309 > > > Christophe Giboudeaux changed: > >What|Removed |Added > > Status|UNCONFIRMED |RESOLVED > Resolution||FIXED > > > > > --- Comment #1 from Christophe Giboudeaux 2011-09-18 > 20:52:12 --- >> the error report stating that Kontact was already running on another >> display > > This is fixed in kdepim > 4.6 (run kontact --version to know which version > you > currently run) > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > --- You are receiving this mail because: --- > You reported the bug. > -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 279297] Not all new mails are downloaded
https://bugs.kde.org/show_bug.cgi?id=279297 Thomas McGuire changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 --- Comment #15 from Thomas McGuire 2011-09-19 22:05:42 --- BTW, I wrote a mail to the kdepim mailing list, if anyone is interested in following the discussion there. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 279297] Not all new mails are downloaded
https://bugs.kde.org/show_bug.cgi?id=279297 --- Comment #14 from Thomas McGuire 2011-09-19 21:51:04 --- Ok, I tried to reproduce it, and to my surprise, I could reproduce pretty reliable. Then I updated, and could no longer reproduce. I used git bisect to search the commit that fixed it, which seems to be https://projects.kde.org/projects/kde/kdepim-runtime/repository/revisions/069f2897d372618e0428604b6954408b17ffb6bd. I am not 100% sure yet though. The problem did not occur prior to KDE 4.7.0, right? If you happen to build from source, you can try building kdepim-runtime from the current git master and see if that fixes the problems for you too. I have not investigated the actual problem yet. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 203251] column size kmail list
https://bugs.kde.org/show_bug.cgi?id=203251 --- Comment #13 from Tom Schumm 2011-09-19 20:51:28 --- I'm still experiencing this any time it takes more than a second or two to fetch my message list. I am using IMAP. My dist is Ubuntu. kontact --version Qt: 4.7.2 KDE Development Platform: 4.6.2 (4.6.2) Kontact: 4.4.10 kmail --version Qt: 4.7.2 KDE Development Platform: 4.6.2 (4.6.2) KMail: 1.13.6 Any hopes for a fix or workaround? It's driving me nuts. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 97372] frame around patches doesn't include whole content
https://bugs.kde.org/show_bug.cgi?id=97372 Mikolaj Machowski changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #6 from Mikolaj Machowski 2011-09-19 19:36:57 --- Yep. Lines are now broken. Thanks. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 249986] folder list randomly sorted
https://bugs.kde.org/show_bug.cgi?id=249986 FiNeX changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #4 from FiNeX 2011-09-19 19:15:42 --- Thanks for the feedback! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 207559] Message structure should become integral part of message display
https://bugs.kde.org/show_bug.cgi?id=207559 --- Comment #3 from Jeffery MacEachern 2011-09-19 18:46:17 --- (In reply to comment #2) > Jeffery: I think your suggestion is bug 275737. That's correct. Thank you. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 273612] Local Folders: Unknown error. (There is no transaction in progress.)
https://bugs.kde.org/show_bug.cgi?id=273612 Mark Gannon changed: What|Removed |Added CC||m...@truenorth.nu --- Comment #6 from Mark Gannon 2011-09-19 18:35:49 --- I'm also experiencing this issue. I'm running an up to date Gentoo system with KDE 4.7.1. The problem usually turns up overnight. First thing in the morning when I manually check my mail, I get an KDE error message (which I can't access right now). When I restart Akonadi using the system tray "Akonadi Tray" to restart the service I'm again able to access email. After having done the above, the Akonadi Server Report Shows: Akonadi Server Self-Test Report === Test 1: SUCCESS Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/markg/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL [QSQLITE3] Name=/home/markg/.local/share/akonadi/akonadi.db [Debug] Tracer=null [QMYSQL] StartServer=false ServerPath= Name=akonadi Host=localhost User= Password= Options= [QPSQL] Name=akonadi Host= User= Password= Port=5432 Test 2: SUCCESS Akonadi is not running as root Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system. Test 3: SKIP MySQL server executable not tested. Details: The current configuration does not require an internal MySQL server. Test 4: SKIP MySQL server error log not tested. Details: The current configuration does not require an internal MySQL server. Test 5: SKIP MySQL server configuration not tested. Details: The current configuration does not require an internal MySQL server. Test 6: SUCCESS akonadictl found and usable Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully. Result: Akonadi 1.6.0 Test 7: SUCCESS Akonadi control process registered at D-Bus. Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational. Test 8: SUCCESS Akonadi server process registered at D-Bus. Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational. Test 9: ERROR Nepomuk search service not registered at D-Bus. Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 10: SKIP Protocol version check not possible. Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements. Test 11: SUCCESS Resource agents found. Details: At least one resource agent has been found. Directory listing of '/usr/share/akonadi/agents': akonotesresource.desktop birthdaysresource.desktop calendarsearchagent.desktop contactsresource.desktop davgroupwareresource.desktop icalresource.desktop imapresource.desktop invitationsagent.desktop kabcresource.desktop kcalresource.desktop kdeaccountsresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mboxresource.desktop microblog.desktop mixedmaildirresource.desktop mtdummyresource.desktop nepomukcalendarfeeder.desktop nepomukcontactfeeder.desktop nepomukemailfeeder.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop openxchangeresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/local/share:/usr/share' Test 12: SUCCESS No current Akonadi server error log found. Details: The Akonadi server did not report any errors during its current startup. Test 13: ERROR Previous Akonadi server error log found. Details: The Akonadi server reported errors during its previous startup. The log can be found in /home/markg/.local/share/akonadi/akonadiserver.error.old. File content of '/home/markg/.local/share/akonadi/akonadiserver.error.old': Database error: DataStore::beginTransaction Last driver error: "QMYSQL: Unable to begin transaction" Last database error: "MySQL server has gone away" Database error: DataStore::beginTransaction Last driver error: "QMYSQL: Unable to begin transaction" Last database error: "MySQL server has gone away" Database error: DataStore::beginTransaction Last driver error: "QMYSQL: Unable to begin transaction" Last database error: "MySQL server has gone away" Database error: DataStore::beginTransaction Last driver error: "QMYSQL: Unable to begin transaction" Last database error: "MySQL server has gone away" Database error: DataStore::beginTransaction Last driver error: "
[Bug 279297] Not all new mails are downloaded
https://bugs.kde.org/show_bug.cgi?id=279297 Thomas McGuire changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WAITINGFORINFO | -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 279297] Not all new mails are downloaded
https://bugs.kde.org/show_bug.cgi?id=279297 --- Comment #13 from Thomas McGuire 2011-09-19 17:55:57 --- So it doesn't seem to be related to filters or expiry/trash, hmm. Will to try reproduce myself, for a bit, but honestly I am a bit out of ideas here... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 147740] Unknown key for signature despite key being there and signature being good
https://bugs.kde.org/show_bug.cgi?id=147740 Lukas Schneiderbauer changed: What|Removed |Added CC||lukas.schneiderbauer@gmail. ||com --- Comment #6 from Lukas Schneiderbauer 2011-09-19 17:27:10 --- Same problem here, with kmail 4.7.1, when verifiing the signature from an encrypted email. The same key appears green, if the email is not encrypted. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 266031] wallet error when starting Kontact
https://bugs.kde.org/show_bug.cgi?id=266031 Dimitrios Glentadakis changed: What|Removed |Added CC||dgl...@gmail.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 207559] Message structure should become integral part of message display
https://bugs.kde.org/show_bug.cgi?id=207559 Ian Turner changed: What|Removed |Added CC||vec...@vectro.org --- Comment #2 from Ian Turner 2011-09-19 16:27:23 --- Jeffery: I think your suggestion is bug 275737. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 275737] Height of "Show Message Structure" pane is not remembered
https://bugs.kde.org/show_bug.cgi?id=275737 Ian Turner changed: What|Removed |Added CC||vec...@vectro.org --- Comment #3 from Ian Turner 2011-09-19 16:18:48 --- At a minimum, if remembering the size is difficult, the default should be set considerably smaller. As a start, the default size should never be larger than the amount of space needed to actually display the message structure (sometimes by default it can be 10X this limit) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 263587] BCC addresses shows bcc's to "To:" recipient
https://bugs.kde.org/show_bug.cgi?id=263587 --- Comment #27 from John King 2011-09-19 16:16:40 --- (In reply to comment #24) > ...and everything works as expected with non gmail addresses. I think we > should > close it with upstream I've now tested it with 1&1 smtp server and Demon (UK) smtp server as well as Gmail, sending in each case to non-gmail addresses. In all cases the To: recipient can see the BCC addresses, and in some cases the BCC recipients can see all the BCC addresses. This did not happen with Kmail1. This behaviour could give us some problems as most people on our membership lists specifically request to be sent BCC as they do not want their email addresses to be open to everybody. Is there any information I can provide that could help nail the bug? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 180162] Message Structure Viewer Shouldn't Appear by Default
https://bugs.kde.org/show_bug.cgi?id=180162 Ian Turner changed: What|Removed |Added CC||vec...@vectro.org --- Comment #1 from Ian Turner 2011-09-19 16:16:23 --- I think this is fixed in KDE 4.7. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 281532] pressing Tab in subject entry box inserts a tab
https://bugs.kde.org/show_bug.cgi?id=281532 --- Comment #8 from Maarten ter Huurne 2011-09-19 16:09:10 --- In the context menu there is an option "Allow Tabulations". That option is enabled by default; after disabling it, pressing tab will change focus as expected. Unfortunately the disabling of that setting is not preserved in the next compose dialog. Actually, I think there is no point in having that setting at all, it should just be disabled all the time. I hope there is a way in Qt or KDE to configure the input field in that way. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 281532] pressing Tab in subject entry box inserts a tab
https://bugs.kde.org/show_bug.cgi?id=281532 Maarten ter Huurne changed: What|Removed |Added CC||maar...@treewalker.org --- Comment #7 from Maarten ter Huurne 2011-09-19 16:01:42 --- This worked fine until I upgraded from KDE 4.7.0 to 4.7.1. So I think it is a recent regression. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 259358] Re-ordering folders via drag & drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 Andreas Schneider changed: What|Removed |Added Version|2.0.90 |4.7 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 277767] Wrong folders order
https://bugs.kde.org/show_bug.cgi?id=277767 Andreas Schneider changed: What|Removed |Added CC||a...@cryptomilk.org -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282355] New: Conflict on mail filters, marking message as read.
https://bugs.kde.org/show_bug.cgi?id=282355 Summary: Conflict on mail filters, marking message as read. Product: kdepim Version: 4.7 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libkdepim AssignedTo: kdepim-bugs@kde.org ReportedBy: maednol...@mail.ru Version: 4.7 (using KDE 4.7.1) OS:Linux Conflict message box appears on filter processing message, when filter try to mark message as read and move ot to another folder. Reproducible: Didn't try Steps to Reproduce: 1. Create a filter, that moves message to some folder and mark it as read. 2. Send self a message conforming the filter. Actual Results: Conflict box is show. It suggest to choose from left (time 0:00:00 flags \SEEN) and right (real name, and no flag \SEEN). Expected Results: Message should be just placed to the target folder, marked as seen. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282344] Kmail2 crash after import of dir (Fedora16 Alpha)
https://bugs.kde.org/show_bug.cgi?id=282344 didier.ga...@free.fr changed: What|Removed |Added Summary|Kmail2 planté après |Kmail2 crash after import |importation de dossier |of dir (Fedora16 Alpha) |(Fedora16 Alpha)| -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282342] KMail crashes after reading account
https://bugs.kde.org/show_bug.cgi?id=282342 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel 2011-09-19 13:58:15 --- 4.7.0 is too old. Please update. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 274799] akonadi_imap_resource hangs while syncing Inbox
https://bugs.kde.org/show_bug.cgi?id=274799 Kevin Funk changed: What|Removed |Added CC||k...@electrostorm.net -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282056] Frequent kmail2 SIGSEGV crashes after filtering new mail.
https://bugs.kde.org/show_bug.cgi?id=282056 Steve Vialle changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Steve Vialle 2011-09-19 13:41:47 --- Apperars to be solved in git build, no issues with mail filtering as yet. (archlinux aur/kmail-git) Cheers :-) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282344] Kmail2 planté après importation de dossier (Fedora16 Alpha)
https://bugs.kde.org/show_bug.cgi?id=282344 Torgny Nyblom changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution||WAITINGFORINFO --- Comment #2 from Torgny Nyblom 2011-09-19 13:26:09 --- In English please. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282344] Kmail2 planté après importation de dossier (Fedora16 Alpha)
https://bugs.kde.org/show_bug.cgi?id=282344 --- Comment #1 from2011-09-19 13:06:30 --- Version 4.7.0 (4.7.00) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282344] New: Kmail2 planté après importation de dossier (Fedora16 Alpha)
https://bugs.kde.org/show_bug.cgi?id=282344 Summary: Kmail2 planté après importation de dossier (Fedora16 Alpha) Product: kmail2 Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: didier.ga...@free.fr Application: kmail (4.7.0 ) KDE Platform Version: 4.7.00 (4.7.0) Qt Version: 4.8.0 Operating System: Linux 3.1.0-0.rc6.git0.0.fc16.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: -Importation de dossier KMail (importer les messages et la structure des dossiers de KMail) : OK -Clic dans le dossier "KMail-Import" provoque le plantage de KMail The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f536a6b2880 (LWP 3825))] Thread 4 (Thread 0x7f535e33a700 (LWP 3828)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x003f9c7b877c in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3f9d17cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x003f9c7b88a9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x003f79407d11 in start_thread (arg=0x7f535e33a700) at pthread_create.c:305 #4 0x003f78ceb66d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f535da29700 (LWP 3829)): #0 0x003f78ce2bd3 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003f7c844fa8 in g_main_context_poll (n_fds=1, fds=0x7f53580013e0, priority=, timeout=7987, context=0x7f53580009a0) at gmain.c:3402 #2 g_main_context_iterate (context=0x7f53580009a0, block=, dispatch=1, self=) at gmain.c:3084 #3 0x003f7c84546c in g_main_context_iteration (context=0x7f53580009a0, may_block=1) at gmain.c:3152 #4 0x003f839a65f6 in QEventDispatcherGlib::processEvents (this=0x7f53580008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003f83976a22 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x003f83976c77 in QEventLoop::exec (this=0x7f535da28d00, flags=...) at kernel/qeventloop.cpp:204 #7 0x003f838789f7 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x003f8387b9db in QThreadPrivate::start (arg=0x2017110) at thread/qthread_unix.cpp:298 #9 0x003f79407d11 in start_thread (arg=0x7f535da29700) at pthread_create.c:305 #10 0x003f78ceb66d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f531452c700 (LWP 3848)): #0 0x003f78ce2bd3 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003f7c844fa8 in g_main_context_poll (n_fds=1, fds=0x7f530c00af60, priority=, timeout=-1, context=0x7f530c0009a0) at gmain.c:3402 #2 g_main_context_iterate (context=0x7f530c0009a0, block=, dispatch=1, self=) at gmain.c:3084 #3 0x003f7c84546c in g_main_context_iteration (context=0x7f530c0009a0, may_block=1) at gmain.c:3152 #4 0x003f839a65f6 in QEventDispatcherGlib::processEvents (this=0x7f530c0008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003f83976a22 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x003f83976c77 in QEventLoop::exec (this=0x7f531452bd00, flags=...) at kernel/qeventloop.cpp:204 #7 0x003f838789f7 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x003f8387b9db in QThreadPrivate::start (arg=0x267bea0) at thread/qthread_unix.cpp:298 #9 0x003f79407d11 in start_thread (arg=0x7f531452c700) at pthread_create.c:305 #10 0x003f78ceb66d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f536a6b2880 (LWP 3825)): [KCrash Handler] #6 QFontEngineFT::loadFlags (this=, set=0x0, format=, flags=, hsubpixel=@0x7fff9af52f2f, vfactor=@0x7fff9af52f28) at text/qfontengine_ft.cpp:800 #7 0x003f870bb6a4 in QFontEngineFT::getPointInOutline (this=0x27bab70, glyph=689, flags=0, point=4, xpos=0x7fff9af530c0, ypos=0x7fff9af530bc, nPoints=0x7fff9af52f88) at text/qfontengine_ft.cpp:1968 #8 0x003f838dd41d in Get_Anchor (gpi=, an=0x1d94988, glyph_index=, x_value=0x7fff9af530c0, y_value=0x7fff9af530bc) at ../3rdparty/harfbuzz/src/harfbuzz-gpos.c:759 #9 0x003f838e1545 in Lookup_MarkBasePos (nesting_level=1, context_length=65535, flags=, buffer=0x1d62ec0, st=0x1d55630, gpi=0x7fff9af53140) at ../3rdparty/harfbuzz/src/harfbuzz-gpos.c:2302 #10 GPOS_Do_Glyph_Lookup (gpi=, lookup_index=, buffer=0x1d62ec0, context_length=65535, nesting_level=1) at ../3rdparty/harfbuzz/s
[Bug 282342] New: KMail crashes after reading account
https://bugs.kde.org/show_bug.cgi?id=282342 Summary: KMail crashes after reading account Product: kmail2 Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: cannewil...@googlemail.com Application: kmail (4.7.0 ) KDE Platform Version: 4.7.00 (4.7.0) Qt Version: 4.7.4 Operating System: Linux 2.6.40.4-5.fc15.i686.PAE i686 Distribution: "Fedora release 15 (Lovelock)" -- Information about the crash: - What I was doing when the application crashed: I have a new 4.7 KMail. Akonadi Resources tells me that the resources are all ready, and I can see my accounts being sync'd there. However, when I start KMail, it appears to check then crash The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb7833780 (LWP 9195))] Thread 3 (Thread 0xb66d7b70 (LWP 9202)): #0 0x00a05424 in __kernel_vsyscall () #1 0x4669d14c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172 #2 0x50947aa0 in WTF::TCMalloc_PageHeap::scavengerThread (this=0x50ebf220) at wtf/FastMalloc.cpp:2378 #3 0x50947b80 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x50ebf220) at wtf/FastMalloc.cpp:1497 #4 0x46699a2e in start_thread (arg=0xb66d7b70) at pthread_create.c:305 #5 0x465d834e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 2 (Thread 0xb5daeb70 (LWP 9203)): #0 0x00a05424 in __kernel_vsyscall () #1 0x465cdc3e in __GI___poll (fds=0xb5400df0, nfds=1, timeout=3936) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x4678eaac in g_poll (fds=0xb5400df0, nfds=1, timeout=3936) at gpoll.c:132 #3 0x4677fc36 in g_main_context_poll (n_fds=1, fds=0x4669c5d0, priority=, timeout=, context=0xb54004e8) at gmain.c:3405 #4 g_main_context_iterate (context=0xb54004e8, block=1182329472, dispatch=1, self=0xb5400d78) at gmain.c:3087 #5 0x4678006f in g_main_context_iteration (context=0xb54004e8, may_block=1) at gmain.c:3155 #6 0x4d6d1db7 in QEventDispatcherGlib::processEvents (this=0xb5400468, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x4d6a299e in QEventLoop::processEvents (this=0xb5dae270, flags=...) at kernel/qeventloop.cpp:149 #8 0x4d6a2bf1 in QEventLoop::exec (this=0xb5dae270, flags=...) at kernel/qeventloop.cpp:201 #9 0x4d5a446c in QThread::exec (this=0x992e368) at thread/qthread.cpp:498 #10 0x4d5a455c in QThread::run (this=0x992e368) at thread/qthread.cpp:565 #11 0x4d5a73a4 in QThreadPrivate::start (arg=0x992e368) at thread/qthread_unix.cpp:331 #12 0x46699a2e in start_thread (arg=0xb5daeb70) at pthread_create.c:305 #13 0x465d834e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 1 (Thread 0xb7833780 (LWP 9195)): [KCrash Handler] #7 operator== (value=0, this=0x73006d) at /usr/include/QtCore/qbasicatomic.h:70 #8 data (this=0xa15bb74) at /usr/include/QtCore/qsharedpointer_impl.h:565 #9 parent (this=0xa15bb60) at /usr/src/debug/kdepim-4.7.0/libkdepim/progressmanager.h:61 #10 KPIM::StatusbarProgressWidget::slotProgressItemCompleted (this=0x9299d40, item=0xa15bb60) at /usr/src/debug/kdepim-4.7.0/libkdepim/statusbarprogresswidget.cpp:161 #11 0x4249331d in KPIM::StatusbarProgressWidget::qt_metacall (this=0x9299d40, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0xbff126f8) at /usr/src/debug/kdepim-4.7.0/i686-redhat-linux-gnu/libkdepim/statusbarprogresswidget.moc:90 #12 0x4d6a9e3e in metacall (argv=0xbff126f8, idx=30, cl=QMetaObject::InvokeMetaMethod, object=0x9299d40) at kernel/qmetaobject.cpp:237 #13 QMetaObject::metacall (object=0x9299d40, cl=QMetaObject::InvokeMetaMethod, idx=30, argv=0xbff126f8) at kernel/qmetaobject.cpp:232 #14 0x4d6b7dca in QMetaObject::activate (sender=0x94cb380, m=0x424be040, local_signal_index=2, argv=0xbff126f8) at kernel/qobject.cpp:3278 #15 0x4248d416 in KPIM::ProgressManager::progressItemCompleted (this=0x94cb380, _t1=0xa15bb60) at /usr/src/debug/kdepim-4.7.0/i686-redhat-linux-gnu/libkdepim/progressmanager.moc:272 #16 0x4248d861 in KPIM::ProgressManager::slotTransactionCompleted (this=0x94cb380, item=0xa15bb60) at /usr/src/debug/kdepim-4.7.0/libkdepim/progressmanager.cpp:218 #17 0x4248e3d5 in KPIM::ProgressManager::qt_metacall (this=0x94cb380, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0xbff12838) at /usr/src/debug/kdepim-4.7.0/i686-redhat-linux-gnu/libkdepim/progressmanager.moc:246 #18 0x4d6a9e3e in metacall (argv=0xbff12838, idx=15, cl=QMetaObject::InvokeMetaMethod, object=0x94cb380) at kernel/qmetaobject.cpp:237 #19 QMetaObject::metacall (object=0x94cb380, cl=QMetaObject::InvokeMetaMethod, idx=15, argv=0xbff12838) at kernel/qmetaobject.cpp:232 #20 0x4d6b7dca in QMetaObject::activate (sender=0xa15bb60, m=0x424be050, local_signal_index=2, argv=0xbff12838) at kernel/qobject.cpp:3278 #21 0x4248ce66 in KPIM::ProgressI
[Bug 282337] New: akonadi agent crashed on trying to get mail from unreachable IMAP server
https://bugs.kde.org/show_bug.cgi?id=282337 Summary: akonadi agent crashed on trying to get mail from unreachable IMAP server Product: Akonadi Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: robby.engelm...@igfs-ev.de CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_imap_resource (4.7) KDE Platform Version: 4.7.00 (4.7.0) Qt Version: 4.7.2 Operating System: Linux 2.6.38-11-generic i686 Distribution: Ubuntu 11.04 -- Information about the crash: - What I was doing when the application crashed: akonadi agent crashed on trying to get mail from unreachable IMAP server within a local network. I open the settings dialogue of that ressouce and tried to autodetect encryption capabilities of the imap server. After that an error message said, that the server is not reachable. I clicked to OK and shortly after that I saw that crash. The crash can be reproduced some of the time. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0xb76d1930 (LWP 2003))] Thread 4 (Thread 0xb6136b70 (LWP 2718)): #0 0x0074f416 in __kernel_vsyscall () #1 0x051b5f76 in __poll (fds=0x8a05200, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x07d0184b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x07cf11af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x07cf1524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x00aca577 in QEventDispatcherGlib::processEvents (this=0x8a04af8, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x00a9c289 in QEventLoop::processEvents (this=0xb6136290, flags=...) at kernel/qeventloop.cpp:149 #7 0x00a9c522 in QEventLoop::exec (this=0xb6136290, flags=...) at kernel/qeventloop.cpp:201 #8 0x009a62a0 in QThread::exec (this=0x8a02808) at thread/qthread.cpp:492 #9 0x00a7dfdb in QInotifyFileSystemWatcherEngine::run (this=0x8a02808) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x009a8da2 in QThreadPrivate::start (arg=0x8a02808) at thread/qthread_unix.cpp:320 #11 0x00514e99 in start_thread (arg=0xb6136b70) at pthread_create.c:304 #12 0x051c473e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 3 (Thread 0xb45d6b70 (LWP 2720)): #0 0x0066ed41 in clock_gettime (clock_id=1, tp=0xb45d6020) at ../sysdeps/unix/clock_gettime.c:116 #1 0x009fedd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x00acb4f2 in updateCurrentTime (this=0x89d793c, tm=...) at kernel/qeventdispatcher_unix.cpp:339 #4 QTimerInfoList::timerWait (this=0x89d793c, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x00ac9d32 in timerSourcePrepareHelper (src=, timeout=0xb45d60fc) at kernel/qeventdispatcher_glib.cpp:136 #6 0x00ac9dcd in timerSourcePrepare (source=0x89d7908, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #7 0x07ceffd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x07cf0e63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x07cf1524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x00aca577 in QEventDispatcherGlib::processEvents (this=0x8b7ab70, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x00a9c289 in QEventLoop::processEvents (this=0xb45d62b0, flags=...) at kernel/qeventloop.cpp:149 #12 0x00a9c522 in QEventLoop::exec (this=0xb45d62b0, flags=...) at kernel/qeventloop.cpp:201 #13 0x009a62a0 in QThread::exec (this=0x895e680) at thread/qthread.cpp:492 #14 0x00364c52 in KIMAP::SessionThread::run (this=0x895e680) at ../../kimap/sessionthread.cpp:166 #15 0x009a8da2 in QThreadPrivate::start (arg=0x895e680) at thread/qthread_unix.cpp:320 #16 0x00514e99 in start_thread (arg=0xb45d6b70) at pthread_create.c:304 #17 0x051c473e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xb6937b70 (LWP 2754)): #0 0x0066ed41 in clock_gettime (clock_id=1, tp=0xb6937020) at ../sysdeps/unix/clock_gettime.c:116 #1 0x009fedd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x00acb4f2 in updateCurrentTime (this=0x8a10304, tm=...) at kernel/qeventdispatcher_unix.cpp:339 #4 QTimerInfoList::timerWait (this=0x8a10304, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x00ac9d32 in timerSourcePrepareHelper (src=, timeout=0xb69370fc) at kernel/qeventdispatcher_glib.cpp:136 #6 0x00ac9dcd in timerSourcePrepare (source=0x8a102d0, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #7 0x07ceffd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x07cf0e63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x07cf1524 in g_main_context_iteration () from /lib/i386-linux-gnu/libgli
[Bug 275209] pipethrough filter causes message duplication
https://bugs.kde.org/show_bug.cgi?id=275209 --- Comment #10 from Luis Silva 2011-09-19 10:54:31 --- Further information on this. Starting akonadi from a terminal I get the following output when clicking on one of the duplicate messages in kmail: void Nepomuk::Query::QueryServiceClient::close() 4721 FLAGS (\Seen) akonadi_imap_resource_2(27513)/kdepimlibs (kimap) KIMAP::StoreJob::handleResponse: We asked for UID but the server didn't give it back, resultingFlags not stored. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 275209] pipethrough filter causes message duplication
https://bugs.kde.org/show_bug.cgi?id=275209 --- Comment #9 from Luis Silva 2011-09-19 10:01:33 --- Ouuupppss! Last famous words... There is indeed still message duplication, which may be related to the previous comment. However, I have one more observation. Duplication only seems to happen for messages on an exchange/outlook based server. Could this issue be related to the particular server implementation? (In reply to comment #8) > Messages are not being duplicated any more. However, the changes as a result > of > the pipethrough filters are not being propagated to the server (I am using > disconnected IMAP). The result is that new messages that go through a > pipethrough filter are being fetched and filtered at every sync, over and over > again. > -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 279790] messages are still visible after filtering the inbox
https://bugs.kde.org/show_bug.cgi?id=279790 --- Comment #2 from Fabio Rossi 2011-09-19 08:41:46 --- The problem is that the issue is not reproducible but happens randomly. Right now I'm using kmail 4.7.1, I'll post here news if I see again the problem. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 275209] pipethrough filter causes message duplication
https://bugs.kde.org/show_bug.cgi?id=275209 --- Comment #8 from Luis Silva 2011-09-19 08:36:44 --- Messages are not being duplicated any more. However, the changes as a result of the pipethrough filters are not being propagated to the server (I am using disconnected IMAP). The result is that new messages that go through a pipethrough filter are being fetched and filtered at every sync, over and over again. (In reply to comment #7) > I just recompiled master and it seems that the issue is solved. I'll give it a > few more days trial and mark this bug as RESOLVED if nothing bad happens. > Thanks. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282186] Account settings for the trash folder do not show the path of the folder just the name
https://bugs.kde.org/show_bug.cgi?id=282186 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel 2011-09-19 07:21:14 --- confirmed but not easy to fix it. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282236] Composer: Formatting shortcuts erroneously activate formatting
https://bugs.kde.org/show_bug.cgi?id=282236 --- Comment #3 from Laurent Montel 2011-09-19 07:19:46 --- Git commit 62e866979d37fc8159b2141052af7f828d519ec1 by Montel Laurent. Committed on 19/09/2011 at 09:17. Pushed by mlaurent into branch 'KDE/4.7'. Fix Bug 282236 - Composer: Formatting shortcuts erroneously activate formatting FIXED-IN: 4.7.2 BUG: 282236 (cherry picked from commit c200bf630aea5be26d757351a58219b9088d0d5a) M +4-0kmail/kmcomposewin.cpp http://commits.kde.org/kdepim/62e866979d37fc8159b2141052af7f828d519ec1 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282236] Composer: Formatting shortcuts erroneously activate formatting
https://bugs.kde.org/show_bug.cgi?id=282236 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.7.2 Resolution||FIXED --- Comment #2 from Laurent Montel 2011-09-19 07:18:27 --- Git commit c200bf630aea5be26d757351a58219b9088d0d5a by Montel Laurent. Committed on 19/09/2011 at 09:17. Pushed by mlaurent into branch 'master'. Fix Bug 282236 - Composer: Formatting shortcuts erroneously activate formatting FIXED-IN: 4.7.2 BUG: 282236 M +4-0kmail/kmcomposewin.cpp http://commits.kde.org/kdepim/c200bf630aea5be26d757351a58219b9088d0d5a -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 282236] Composer: Formatting shortcuts erroneously activate formatting
https://bugs.kde.org/show_bug.cgi?id=282236 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel 2011-09-19 07:02:36 --- I confirm it. Will fix it -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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
