[akregator] [Bug 138506] Wish: Manually managed item folders
https://bugs.kde.org/show_bug.cgi?id=138506 Shai changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Shai --- "More than 5 years"... 14 and counting... I don't use Akregator regularly these days, so I no longer need this feature. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 322459] Subject line not right-aligned when RTL (BiDi regression)
https://bugs.kde.org/show_bug.cgi?id=322459 Shai changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #10 from Shai --- Still as reported, with KMail 5.2.3, Using KDE Frameworks 5.25.0 and Qt 5.6.1 on Debian Testing. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 361435] New: Crash while going thrugh unread articles
https://bugs.kde.org/show_bug.cgi?id=361435 Bug ID: 361435 Summary: Crash while going thrugh unread articles Product: akregator Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: s...@platonix.com Application: akregator (4.14.2) KDE Platform Version: 4.14.2 Qt Version: 4.8.7 Operating System: Linux 4.0.0-2-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: Opened a feed with very many unread articles, and started going over them. At some point, when moving (with KB -- right arrow, "next article"), akregator crashed. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 GetAt (nIndex=, this=0x3be9aa0) at ../../../../akregator/plugins/mk4storage/metakit/src/univ.inl:54 #7 c4_Column::ReleaseSegment (this=0x3be9aa0, index_=) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:116 #8 0x7f4a02a98d6d in c4_Column::ReleaseAllSegments (this=this@entry=0x3be9aa0) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:124 #9 0x7f4a02a98dc1 in c4_Column::SetLocation (this=this@entry=0x3be9aa0, pos_=pos_@entry=-228961430, size_=size_@entry=125) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:142 #10 0x7f4a02aa5c03 in c4_SaveContext::CommitColumn (this=this@entry=0x7ffd46207400, col_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:819 #11 0x7f4a02aa1895 in c4_FormatB::Commit (this=0x24c86f0, ar_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:775 #12 0x7f4a02aa5cdd in c4_SaveContext::CommitSequence (this=this@entry=0x7ffd46207400, seq_=..., selfDesc_=selfDesc_@entry=false) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:841 #13 0x7f4a02aa269a in c4_FormatV::Commit (this=0x24c4790, ar_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:1174 #14 0x7f4a02aa5cdd in c4_SaveContext::CommitSequence (this=this@entry=0x7ffd46207400, seq_=..., selfDesc_=selfDesc_@entry=true) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:841 #15 0x7f4a02aa62aa in c4_SaveContext::SaveIt (this=this@entry=0x7ffd46207400, root_=..., spacePtr_=spacePtr_@entry=0x24c7170, rootWalk_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:709 #16 0x7f4a02aa6619 in c4_Persist::Commit (this=0x24c7170, full_=) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:933 #17 0x7f4a02aa66c1 in c4_Persist::Commit (this=, full_=) at ../../../../akregator/plugins/mk4storage/metakit/src/persist.cpp:935 #18 0x7f4a02aab51e in c4_Storage::Commit (this=, full_=full_@entry=false) at ../../../../akregator/plugins/mk4storage/metakit/src/store.cpp:361 #19 0x7f4a02ab0d7f in Akregator::Backend::FeedStorageMK4Impl::commit (this=0x208c860) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:181 #20 0x7f4a02ab6dd5 in Akregator::Backend::StorageMK4Impl::commit (this=0x1f9fe00) at ../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:178 #21 0x7f4a02ab633a in Akregator::Backend::StorageMK4Impl::slotCommit (this=0x1f9fe00) at ../../../../akregator/plugins/mk4storage/storagemk4impl.cpp:283 #22 0x7f4a1bab038c in QMetaObject::activate (sender=sender@entry=0x9e9b6f0, m=m@entry=0x7f4a1bdfe540 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #23 0x7f4a1bab96ba in timeout (this=0x9e9b6f0) at .moc/release-shared/qtimer.moc:96 #24 QSingleShotTimer::timerEvent (this=0x9e9b6f0) at kernel/qtimer.cpp:317 #25 0x7f4a1bab4953 in QObject::event (this=0x9e9b6f0, e=) at kernel/qobject.cpp:1253 #26 0x7f4a1c4ba7bc in QApplicationPrivate::notify_helper (this=this@entry=0x1cf0e80, receiver=receiver@entry=0x9e9b6f0, e=e@entry=0x7ffd46207b10) at kernel/qapplication.cpp:4570 #27 0x7f4a1c4c12d8 in QApplication::notify (this=this@entry=0x7ffd46207f70, receiver=receiver@entry=0x9e9b6f0, e=e@entry=0x7ffd46207b10) at kernel/qapplication.cpp:4356 #28 0x7f4a1d2381aa in KApplication::notify (this=0x7ffd46207f70, receiver=0x9e9b6f0, event=0x7ffd46207b10) at ../../kdeui/kernel/kapplication.cpp:311 #29 0x7f4a1ba9b36d in QCoreApplication::notifyInternal (this=0x7ffd46207f70, receiver=0x9e9b6f0, event=event@entry=0x7ffd46207b10) at kernel/qcoreapplication.cpp:955 #30 0x7f4a1baccffb in sendEvent (event=0x7ffd46207b10, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #31 QTimerInfoList::activateTimers (this=0x1cf61a0) at kernel/qeventdispatcher_unix.cpp:621 #32 0x7f
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 Shai changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #9 from Shai --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #8 from Shai --- (In reply to S Clark from comment #4) > Perhaps this bug should just read "Read articles should not be removed by > the unread filter while the article is selected"? That's a compromise, not an ideal solution. The ideal solution is akregator 4.x behavior -- the "unread" filter is not applied continuously, but only upon selection of a folder (or, of course, changing of filter). This means if you enter a feed and have 3 unread items, once you've read them all, you see 3 read items. -- 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
[kmail2] [Bug 339090] Filters on mailing lists get confused if the mail has more recipients
https://bugs.kde.org/show_bug.cgi?id=339090 --- Comment #12 from Shai --- Thanks for the quick fix. -- 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
[kmail2] [Bug 339090] Filters on mailing lists get confused if the mail has more recipients
https://bugs.kde.org/show_bug.cgi?id=339090 --- Comment #9 from Shai --- The X-Bugzilla-URL header which should have matched rule C is at line 61 in the file. -- 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
[kmail2] [Bug 339090] Filters on mailing lists get confused if the mail has more recipients
https://bugs.kde.org/show_bug.cgi?id=339090 --- Comment #7 from Shai --- Created attachment 88735 --> https://bugs.kde.org/attachment.cgi?id=88735&action=edit the filter I tried to apply -- 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
[kmail2] [Bug 339090] Filters on mailing lists get confused if the mail has more recipients
https://bugs.kde.org/show_bug.cgi?id=339090 --- Comment #6 from Shai --- Created attachment 88734 --> https://bugs.kde.org/attachment.cgi?id=88734&action=edit mail which was not filtered correctly Hi, This is the automatic message I got for your latest comment on this bug. It was supposed to go into the "kde-devel" folder, because it comes from the KDE bugzilla. But even trying to apply the filter manually, I get these results (pasted from Filter Log Viewer) [03:38:37] Evaluating filter rules: (match any of the following) "List-Id" "" "List-Id" "" "X-Bugzilla-URL" "http://bugs.kde.org/"; "List-Id" "" "List-Id" "" [03:38:37] 0 = "List-Id" "" () [03:38:37] 0 = "List-Id" "" () [03:38:37] 0 = "X-Bugzilla-URL" "http://bugs.kde.org/"; () [03:38:37] 0 = "List-Id" "" () [03:38:37] 0 = "List-Id" "" () Note how in the log, the headers all appear empty. X-Bugzilla-URL, specifically, looks fine in the message itself. Exported filter will be added shortly. -- 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
[kmail2] [Bug 339090] Filters on mailing lists get confused if the mail has more recipients
https://bugs.kde.org/show_bug.cgi?id=339090 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #1 from Shai --- This was first reported as a Debian bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761252 Additional info I have posted there: Filter processing fails to read the "List-Id" header. I see messages with list-ids, and the Filter Log Viewer shows the relevant rule not matched because the List-Id header is (falsely) empty. I also see the "From" header reported as empty by the filters, but the "X-Spambayes-Classification" header -- added by another filter -- is read correctly. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 147707] feed archiving: "disable archiving" does not work
https://bugs.kde.org/show_bug.cgi?id=147707 --- Comment #4 from Shai --- (In reply to comment #2) > Sorry to ask this after such a long time but can you still confirm this? > > Please note that old articles are only deleted once every hour. They will > not be removed instantly. Sorry about the delay in responding -- yes, I still see this behavior. In particular, one of the feeds that prompted this bug seems to still retain all the articles since its change of address, in mid 2009. It has been marked as "disable archiving" since before 2007. I am currently with akregator 4.11.3, still from Debian. -- 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
[kmail2] [Bug 322459] Subject line not right-aligned when RTL (BiDi regression)
https://bugs.kde.org/show_bug.cgi?id=322459 Shai changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #8 from Shai --- Finally got around to it -- it's a little hard since one cannot run a 4.11 KMail in a 4.10 KDE session, and there's essentially no documentation available on starting up an own-compiled-KDE session (there used to be some, I think, but now it's gove, presumably out-of-date as well). So I hope what I did was right -- used the .xssession, kde-env-master an kde-env-user files from kdesrc-build, prefixed PATH and LD_LIBRARY_PATH with ~/kde4/bin and ~/kde4/lib respectively, pointed DISPLAY at a freshly-started Xephyr, and ran startkde. I know this setting isn't perfect, because I couldn't get the keyboard layout switching to work. Anyway, under this environment, as Christoph said -- the clear-text-mark now behaves well, but the subject-line alignment is still wrong until the window is resized. Thus, reopening. -- 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
[Akonadi] [Bug 322923] resource failed to save downloaded mails
https://bugs.kde.org/show_bug.cgi?id=322923 --- Comment #1 from Shai --- Sorry for spamming, forgot to mention here: bug 273445 may be related. -- 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
[Akonadi] [Bug 322923] New: resource failed to save downloaded mails
https://bugs.kde.org/show_bug.cgi?id=322923 Bug ID: 322923 Summary: resource failed to save downloaded mails Classification: Unclassified Product: Akonadi Version: 1.9.2 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: s...@platonix.com This was reported as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718214. I am the original submitter. Essentially: A session left for ~8 hours suddenly started spewing "Unable to store downloaded mails. Append failed" messages, and stopped storing downloaded mails. Restarting akonadi server helped, with tons of error messages in the restart command output (posted on the Debian bug). Reproducible: Didn't try -- 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
[kmail2] [Bug 312302] KMail2 crashes while forwarding mail
https://bugs.kde.org/show_bug.cgi?id=312302 --- Comment #9 from Shai --- Created attachment 81370 --> https://bugs.kde.org/attachment.cgi?id=81370&action=edit New crash information added by DrKonqi kmail (4.10.5) on KDE Platform 4.10.5 using Qt 4.8.5 - What I was doing when the application crashed: I was trying to forward a mail that is a daily digest from kde-pim. Messages are inside it as many attahcments, and I suppose some of them have attachments of their own. - Custom settings of the application: These messages go through a filter that changes the connected identity and transport. -- Backtrace (Reduced): #6 0x7fb0c6e1f0b4 in KMime::Content::parent (this=0x61b6570) at ../../kmime/kmime_content.cpp:952 #7 0x7fb0c6e23bc7 in KMime::Content::addContent (this=this@entry=0xd4dece0, c=c@entry=0x61b6570, prepend=prepend@entry=false) at ../../kmime/kmime_content.cpp:582 #8 0x7fb0c5712c7e in TemplateParser::TemplateParser::createMultipartMixed (this=this@entry=0x7fff34c2f5c0, ac=..., textPart=textPart@entry=0xd8ce1b0) at ../../templateparser/templateparser.cpp:1298 #9 0x7fb0c5715dbf in TemplateParser::TemplateParser::addProcessedBodyToMessage (this=this@entry=0x7fff34c2f5c0, plainBody=..., htmlBody=...) at ../../templateparser/templateparser.cpp:1275 #10 0x7fb0c57179b6 in TemplateParser::TemplateParser::processWithTemplate (this=, tmpl=...) at ../../templateparser/templateparser.cpp:1187 -- 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
[kmail2] [Bug 312302] KMail2 crashes while forwarding mail
https://bugs.kde.org/show_bug.cgi?id=312302 Shai changed: What|Removed |Added CC||s...@platonix.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
[kmail2] [Bug 322459] Subject line not right-aligned when RTL (BiDi regression)
https://bugs.kde.org/show_bug.cgi?id=322459 --- Comment #3 from Shai --- Yes, address lines changed alignment properly as they always have (there's a different problem there -- the "clear text" mark is in the field and it hides the first 1-2 characters, but that's the same as KMail1). -- 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
[kmail2] [Bug 322461] New: quoting broken in plaintext part of HTML messages
https://bugs.kde.org/show_bug.cgi?id=322461
Bug ID: 322461
Summary: quoting broken in plaintext part of HTML messages
Classification: Unclassified
Product: kmail2
Version: 4.10.5
Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: s...@platonix.com
When KMail composes an HTML reply to a message, it also sends a plain-text
version (as it should). In this version, quoting is broken. This matters mostly
in two scenarios:
1) Mailing lists and their archives
2) A two-way exchange, when I prefer plaintext. Even if I "reply using HTML if
present", I still see incoming messages first as plaintext. So if the plaintext
in my reply to them has broken quoting, I will see broken quoting in their next
reply to me.
Reproducible: Always
Steps to Reproduce:
0. In Composer, set "options->Formatting(HTML)" to on -- or check the
configuration option "reply using HTML if present"
1. Reply using HTML, quoting the original message
2. Open your reply message, and look at its plaintext version
Actual Results:
Missing any quotation mark, except for a header "This and that said". If
replies are interweaved with original text, no way to tell which is which.
Expected Results:
Quotation marks (">" or whatever the quote mark is) on quoted lines.
This may or may not be a duplicate of #321424 -- I cannot be sure what, exactly
is reported there.
#316917 and #317227 are related.
--
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
[kmail2] [Bug 322459] Subject line not right-aligned when RTL (BiDi regression)
https://bugs.kde.org/show_bug.cgi?id=322459 --- Comment #1 from Shai --- Created attachment 81148 --> https://bugs.kde.org/attachment.cgi?id=81148&action=edit A message with Hebrew subject and text In the attached screenshot is a message with Hebrew subject and text, as it is displayed when entered naturally. The subject line (red) is left-aligned, which is wrong; the body text (blue) is right-aligned, which is 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
[kmail2] [Bug 322459] New: Subject line not right-aligned when RTL (BiDi regression)
https://bugs.kde.org/show_bug.cgi?id=322459 Bug ID: 322459 Summary: Subject line not right-aligned when RTL (BiDi regression) Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: s...@platonix.com When writing an RTL subject line in a new message, the subject line control stays left-aligned -- but it should be right-aligned; text in the message body does get the correct alignment automatically. Surprisingly, if the composer window is resized, the subject is then aligned correctly; but it should align correctly already when the subject is typed in. Reproducible: Always Steps to Reproduce: 0. Have an RTL language available for use (Arabic and Hebrew are the most common ones, AFAIK). 1. Start composing a new mail 2. Write an RTL subject 3. For comparison, also write an RTL (plaintext) body. Actual Results: Subject line is left-aligned even with RTL content Expected Results: Subject line should set its alignment according to its directionality As noted, resizing the composer window appears to update alignment. Note that directionality is set correctly automatically; the problem is only with alignment. An image showing the problem will be attached shortly (why can't I add it now...?) This is a regression from KMail1. -- 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
[kmail2] [Bug 317227] reply is composed in HTML although quotation is plain text
https://bugs.kde.org/show_bug.cgi?id=317227 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #11 from Shai --- When a stored message has both plaintext and HTML parts, a user can pick which part to look at (easily, if they enable the message structure pane); I expected (hoped, I should say -- there was no real reason to expect) that the format of the reply will be set according to the part I am looking at when I hit "reply". That is, reply in plain-text if I'm looking at the plaintext, reply in HTML to the HTML. a) Any chance? b) Assuming "yes", would you consider that a partial solution to this ticket, or should I open a new wish? Thanks, Shai. -- 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
[kmail2] [Bug 322455] New: status filter "unread" unusable
https://bugs.kde.org/show_bug.cgi?id=322455 Bug ID: 322455 Summary: status filter "unread" unusable Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: s...@platonix.com When the status filter on the message list is set to "Unread", every message whose status changes to "read" is immediately removed from the list (except when messages are threaded and the message has an unread child). This may seem to make sense, but is in fact surprising and unwelcome; the fact that a message I am looking at is already gone from the list, and if I press right-arrow (next message) then left arrow (prev message) I won't get back to it, is a real hindrance. Reproducible: Always Steps to Reproduce: 0. In the settings->Configure Kmail->Misc->Folders check "mark selected message as read after" and set a small number of seconds (I use 2). 1. Choose a mail folder with unread messages. 2. Change filter status to "Unread" 3. Navigate the message list, preferably using the right-left arrows, to read the messages in the preview pane Actual Results: Every thread you go through is removed from the list, and then you can't go back to it. Expected Results: Filtering should be applied when the filter is set, but messages should not be removed automatically after that (except when deleted or moved, of course, but that isn't really "automatically"). This is a regression from KMail1, which had the correct behavior. -- 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
[kmail2] [Bug 310899] Resource KMail Folders is broken. This resource is now online
https://bugs.kde.org/show_bug.cgi?id=310899 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #6 from Shai --- I seem to be seeing something very similar -- though, no crashes or hangs so far, and there appears to be a workaround -- switching to another folder and coming back allows me to view the message where an error was triggered. I see this several times in every session of work, since I moved to kmail2 with the introduction of kmail 4.10.5 into Debian unstable. I reported it also there: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717101 Thanks, Shai. -- 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
https://bugs.kde.org/show_bug.cgi?id=288364 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #21 from Shai 2012-01-26 13:35:58 --- I sometimes see this. Simple workaround: Switch to an empty folder (e.g. outbox), then switch back. But yes, annoying as hell. -- 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 284403] Latest 11.10 Ubuntu
https://bugs.kde.org/show_bug.cgi?id=284403 --- Comment #2 from Shai 2012-01-26 13:27:59 --- (In reply to comment #1) > ... down-arrow and up-arrow would alternate ... That's right and left, of course. -- 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 284403] Latest 11.10 Ubuntu
https://bugs.kde.org/show_bug.cgi?id=284403 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #1 from Shai 2012-01-26 13:24:22 --- I ran into a version of this too; in a threaded folder, down-arrow and up-arrow would alternate between navigating on a thread and folding/unfolding it, with problems navigating between threads. I found a workaround -- go to settings -> Configure KMail -> Appearance -> Message List and change the Default Theme to Classic; then things work fine. While you're at it, you should probably change the bug title to something that describes the problem rather than the environment. (KMail 4.7.3 on KDE 4.7.4 from Ubuntu 11.10). -- 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 292454] New: Configuration of custom headers writes wrong section header in config file
https://bugs.kde.org/show_bug.cgi?id=292454 Summary: Configuration of custom headers writes wrong section header in config file Product: kmail2 Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@platonix.com Version: 4.7 (using KDE 4.7.4) OS:Linux After migration from KMail 1 (kde 4.6, Ubuntu), where I had my custom header set. The behavior I saw was: "Configure KMail..." -> composer -> headers => shows no headers. If I add a header, it appears to put it in the list of headers, but if the settings dialog is closed and reopened then the header is missing again; and of course, it does not show up in messages sent. When I checked the kmail2rc file, I found this section in it: [Mime #] name= value= When I compared this to the old kmailrc, I saw that the section header is wrong -- there, it was "[Mime #0]" (notice added "0"). I closed Kontact, fixed the file by manually editing it and now it works as advertised. Reproducible: Didn't try Steps to Reproduce: (a guess, based on my experience -- haven't really tried it) (steps a-b optional, presumably created broken config file) a. Use kmail 1, define a custom Mime header b. Migrate to KMail2 Now you have a config file with an invalid "[Mime #]" section. 1. Settings -> Configre KMail -> choose Composer component -> Choose "headers" tab 2. Add a header. 3. Confirm the change and close the configuration dialog Actual Results: The header is not added; when you reopen the configuration dialog, it isn't there, and it isn't added to sent messages. Expected Results: The header is added -- shows up in configuration dialog and added to messages. OS: Linux (x86_64) release 3.0.0-15-generic Compiler: gcc Workaround: Fix configuration file manually -- 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 259574] conflict resolution box appears a lot
https://bugs.kde.org/show_bug.cgi?id=259574 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #41 from Shai 2012-01-25 11:54:58 --- Same here on Kubuntu Oneiric: kmail 4:4.7.4+git111222-0ubuntu0.1 As far as I'm concerned, this should be marked critical; "cannot use spam filtering" is almost exactly equal to "cannot use kmail". Also, looking at Comment #9 - not being able to leave on server is a showstopper. Also, looking at Comment #9 - bug was not a showstopeer for 4.6 or 4.7 -- maybe finally make it one for 4.8? Also, I may be able to help; any pointers? Thanks, Shai. -- 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 291104] New: Crash while updating a saved search
https://bugs.kde.org/show_bug.cgi?id=291104 Summary: Crash while updating a saved search Product: kmail2 Version: unspecified Platform: Debian unstable OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@platonix.com Application: kmail (1.13.7) KDE Platform Version: 4.6.5 (4.6.5) Qt Version: 4.7.4 Operating System: Linux 3.1.0-1-686-pae i686 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: Trying to refresh a saved search in a folder. - Unusual behavior I noticed: The search folder was showing an unreasonable number of unread messages, and indeed when I clicked it, it didn't have the right parameters. I should note that KMail had been open for several days (one session) prior to this. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb201b710 (LWP 18228))] Thread 2 (Thread 0xacff2b70 (LWP 21925)): #0 0xb55d3524 in __pthread_mutex_unlock_usercnt (mutex=0xcb421c4, decr=) at pthread_mutex_unlock.c:52 #1 0xb5b90c86 in pthread_mutex_unlock (mutex=0xcb421c4) at forward.c:184 #2 0xb3c8773c in g_main_context_prepare () from /lib/libglib-2.0.so.0 #3 0xb3c88613 in ?? () from /lib/libglib-2.0.so.0 #4 0xb3c88ce4 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0xb5ea8637 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #6 0xb5e7933d in QEventLoop::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #7 0xb5e79581 in QEventLoop::exec(QFlags) () from /usr/lib/libQtCore.so.4 #8 0xb5d7c85b in QThread::exec() () from /usr/lib/libQtCore.so.4 #9 0xb5e59e7d in QInotifyFileSystemWatcherEngine::run() () from /usr/lib/libQtCore.so.4 #10 0xb5d7f6c3 in QThreadPrivate::start(void*) () from /usr/lib/libQtCore.so.4 #11 0xb55cfc39 in start_thread (arg=0xacff2b70) at pthread_create.c:304 #12 0xb5b8398e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb201b710 (LWP 18228)): [KCrash Handler] #7 KMail::MessageListView::Widget::getSelectionStats (this=0xbcf7c28, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbfe340ef, includeCollapsedChildren=true) at ../../kmail/messagelistview/widget.cpp:607 #8 0xb6ed0208 in KMail::MessageListView::Pane::getSelectionStats (this=0x95d24c8, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbfe340ef, includeCollapsedChildren=true) at ../../kmail/messagelistview/pane.cpp:668 #9 0xb6d9ead7 in KMMainWidget::updateMessageActions (this=0x98a84b0) at ../../kmail/kmmainwidget.cpp:4261 #10 0xb6db3acd in KMMainWidget::qt_metacall (this=0x98a84b0, _c=QMetaObject::InvokeMetaMethod, _id=21, _a=0xbfe341d4) at ./kmmainwidget.moc:375 #11 0xb5e806cd in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4 #12 0xb5e8f4d0 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #13 0xb5ede505 in QTimer::timeout() () from /usr/lib/libQtCore.so.4 #14 0xb5e96d46 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4 #15 0xb5e92434 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #16 0xb60f6904 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #17 0xb60fbc92 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #18 0xb7573511 in KApplication::notify (this=0xbfe34aac, receiver=0x9a42c40, event=0xbfe346dc) at ../../kdeui/kernel/kapplication.cpp:311 #19 0xb5e7a31e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #20 0xb5eaa708 in QTimerInfoList::activateTimers() () from /usr/lib/libQtCore.so.4 #21 0xb5ea7c32 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/libQtCore.so.4 #22 0xb3c88252 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #23 0xb3c88a30 in ?? () from /lib/libglib-2.0.so.0 #24 0xb3c88ce4 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #25 0xb5ea85d7 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #26 0xb61abb9a in QGuiEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQtGui.so.4 #27 0xb5e7933d in QEventLoop::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #28 0xb5e79581 in QEventLoop::exec(QFlags) () from /usr/lib/libQtCore.so.4 #29 0xb5e7dcda in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #30 0xb60f4784 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #31 0x0804a5f2 in main (argc=) at ../../kmail/main.cpp:158 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are th
[Bug 215397] Hebrew Messages are Displayed with Jumpy Margins
https://bugs.kde.org/show_bug.cgi?id=215397 --- Comment #19 from Shai 2011-02-06 09:49:25 --- Sounds like a problem in your fonts configuration... try to select the same font using something like xfontsel; my guess is that you don't really have that font (in that size), and KDE is doing some funky font replacement. -- 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 215397] Hebrew Messages are Displayed with Jumpy Margins
https://bugs.kde.org/show_bug.cgi?id=215397 --- Comment #17 from Shai 2011-02-02 12:26:58 --- If you use the appearance tab to change the font, then, assuming "use custom fonts" is checked, look at the font selected for "message body". If it is not checked, you are using fonts selected at the desktop level; under KDE, this is controlled with the System Settings (Appearance -> Fonts). -- 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 215397] Hebrew Messages are Displayed with Jumpy Margins
https://bugs.kde.org/show_bug.cgi?id=215397 --- Comment #15 from Shai 2011-02-02 11:12:27 --- Shlomi, As noted above, the font in these images is not monospaced. Please find what font you are really using. The control choosing the font in the second image chooses only the font for the message header, not the message body, as far as I've seen. This may be worth its own 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 215397] Hebrew Messages are Displayed with Jumpy Margins
https://bugs.kde.org/show_bug.cgi?id=215397 --- Comment #11 from Shai 2011-02-02 10:42:34 --- Shlomi, can you please post an updated screenshot? By your comment #2, the one you posted originally no longer shows the current problem, and in fact, that one doesn't even use a monospaced font. -- 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 215397] Hebrew Messages are Displayed with Jumpy Margins
https://bugs.kde.org/show_bug.cgi?id=215397 --- Comment #8 from Shai 2011-02-01 23:34:31 --- Created an attachment (id=56767) --> (http://bugs.kde.org/attachment.cgi?id=56767) Shlomi's message rendered correctly Hi, I just checked, and the problem is not reproduced here. The font selected, as indicated in the picture, is Bitstream Vera Sans Mono 12 -- the very one Shlomi complained about. This is KMail 1.13.5 using KDE 4.4.5 on Debian unstable. -- 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 255981] Contacts not synced when file is updated on disk
https://bugs.kde.org/show_bug.cgi?id=255981 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #1 from Shai 2010-12-21 22:16:37 --- Hi, I'm not one of the KDE-PIM developers, just trying to help figure things out, because I ran into this report and it looks a little weird. How are the two computers "sharing a local directory"? Is it on a network storage? USB Storage? Assuming your text-editor description is based on trying and not just extrapolating from your experiences with Akonadi clients: Was the text-editor used from the same computer as the misbehaving Akonadi? Hope this helps, Shai. -- 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 234080] kaddressbook does not store contacts to vcf
https://bugs.kde.org/show_bug.cgi?id=234080 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #7 from Shai 2010-12-21 22:08:25 --- Following up from bug #259067: I experienced the same error as the original poster, with the new vCard file resource (local std.vcf file not being updated, while addressbook keeps being updated in the Akonadi cache only). Deleting the addressbook (in kaddressbook, not the file itself) and re-creating it with the same type from the same file seems to have solved the problem. I suspect a real bug exists, though I don't know how to help reproduce it (I tried to repeat the actions that led to this state, that is, copy some other file over std.vcf when Akonadi is down, and it did not reproduce). -- 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 259067] Address book seems to have been emptied (though copies exist)
https://bugs.kde.org/show_bug.cgi?id=259067 --- Comment #6 from Shai 2010-12-14 07:39:46 --- I copied a full std.vcf_X onto std.vcf, and all seems well (except for that little part where new contacts aren't saved). I'll check up on the different types of address books -- thanks for the tip. But still -- besides the great support you've given me here -- I suspect there's a problem with the vcard file Akonadi resource. Don't you want to investigate it? Thanks again, Shai. -- 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 259067] Address book seems to have been emptied (though copies exist)
https://bugs.kde.org/show_bug.cgi?id=259067 --- Comment #4 from Shai 2010-12-13 19:34:03 --- The relevant name is "std.vcf". In its details, it says Identifier: akonadi_vcard_resource_1 Type: VCard File Capabilities: Resource MimeTypes: text/directory Other names are "Local Folders" (maildir), "std.ics" (ical calendar file), "Mail Dispatcher Agent" and "Nepomuk Contact Feeder". I presume none of them is relevant. Thanks, Shai. -- 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 259067] Address book seems to have been emptied (though copies exist)
https://bugs.kde.org/show_bug.cgi?id=259067 --- Comment #2 from Shai 2010-12-12 23:13:53 --- I don't think it's a migration issue -- I'm on Debian Sid, and I'm pretty sure the move from 4.3 to 4.4 was long before the last month. How can I tell if it's a native resource? It doesn't say "compatibility" or "kresource" anywhere in the Akonadi dialogs for it, doesn't that mean it's native? (I just tried, btw, and when I add a new contact, it is not added to the file. The file is touched, but not modified. The new contact is saved in the Akonadi database. Seems related, but probably a separate 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 259067] New: Address book seems to have been emptied (though copies exist)
https://bugs.kde.org/show_bug.cgi?id=259067 Summary: Address book seems to have been emptied (though copies exist) Product: kaddressbook Version: unspecified Platform: Debian unstable OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@platonix.com CC: to...@kde.org Version: unspecified (using KDE 4.4.5) OS:Linux Hi, I've been using KDE SC 4.4 from Debian unstable, without mocking with addressbook definitions and resources as far as I can remember. Today I suddenly discovered that my address book was empty. a little investigation shows this (I hope the lines are kept): ~$ ls -l .kde/share/apps/kabc/std.vcf* -rw-r--r-- 1 shai shai 0 Dec 7 01:56 .kde/share/apps/kabc/std.vcf -rw-r--r-- 1 shai shai 27541 Nov 8 09:28 .kde/share/apps/kabc/std.vcf_1 -rw-r--r-- 1 shai shai 0 Nov 23 02:02 .kde/share/apps/kabc/std.vcf_2 -rw-r--r-- 1 shai shai 27541 Nov 17 09:54 .kde/share/apps/kabc/std.vcf_3 -rw-r--r-- 1 shai shai 27541 Oct 21 02:39 .kde/share/apps/kabc/std.vcf_4 -rw-r--r-- 1 shai shai 27541 Nov 5 23:46 .kde/share/apps/kabc/std.vcf_5 -rw-r--r-- 1 shai shai 27541 Nov 13 09:56 .kde/share/apps/kabc/std.vcf_6 -rw-r--r-- 1 shai shai 0 Dec 5 01:09 .kde/share/apps/kabc/std.vcf_7 And this is a little odd, because I'm using kaddressbook, not kab or kabc as far as I understand. I probably got things very wrong here -- please help me investigate and specify things better. Since Akonadi, I'm no longer very clear on where I should be looking for stuff. I just don't want my address book gone. Thanks, Shai. Reproducible: Didn't try Actual Results: Address book appears empty Expected Results: There should be quite a lot of addresses -- 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 223245] KMail crash dragging multiple emails from one folder to another [MessageList::Core::Item::parent, MessageList::Core::Model::index, MessageList::Core::Item::parent, QModelIndex::parent]
https://bugs.kde.org/show_bug.cgi?id=223245 --- Comment #25 from Shai 2010-08-15 00:56:25 --- Now that I've restarted, I see that this has already happened to me before. What's more, what also happened before is that ~2 weeks' worth of mail has become unread, regardless of whether it was marked read or even replied-to. I don't know about other people's workflows, but for me this is a data-loss 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 223245] KMail crash dragging multiple emails from one folder to another [MessageList::Core::Item::parent, MessageList::Core::Model::index, MessageList::Core::Item::parent, QModelIndex::parent]
https://bugs.kde.org/show_bug.cgi?id=223245 --- Comment #24 from Shai 2010-08-15 00:41:26 --- Created an attachment (id=50566) --> (http://bugs.kde.org/attachment.cgi?id=50566) New crash information added by DrKonqi Like one of the dupes, I was deleting a thread from my maildir inbox (that is, moving the thread to the trash -- which is also a maildir). -- 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 218753] The crash occurred when the address book was being opened while composing an e-mail message in Kmail.
https://bugs.kde.org/show_bug.cgi?id=218753 --- Comment #5 from Shai 2010-07-20 15:15:26 --- (In reply to comment #1) > According to bug 215575, this issue could be fixed already on KDE SC 4.3.3+. > - Could you check it ? In as much as #237698, #240030 and #245199 are really dupes of this one, they seem to answer this question in the negative. BTW -- the link to this bug shows up stricken-through in other bugs, as if it had been resolved. This is wrong. A bug in bugs.kde.org? Thanks, Shai. -- 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 243398] New: KMail crashed when deleting a discussion
https://bugs.kde.org/show_bug.cgi?id=243398 Summary: KMail crashed when deleting a discussion Product: kmail Version: 1.13.3 Platform: Debian unstable OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@platonix.com Application: kmail (1.13.3) KDE Platform Version: 4.4.4 (KDE 4.4.4) Qt Version: 4.6.3 Operating System: Linux 2.6.32-5-686 i686 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: Most of the discussion was unread when this happened. It's a POP3 account. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb2670710 (LWP 2949))] Thread 6 (Thread 0xaddffb70 (LWP 8341)): #0 0xb7709424 in __kernel_vsyscall () #1 0xb4662482 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179 #2 0xb5909114 in __pthread_cond_timedwait (cond=0xaa13208, mutex=0xaa131f0, abstime=0xaddff320) at forward.c:152 #3 0xaea3dbcf in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 5 (Thread 0xae798b70 (LWP 8342)): #0 0xb590928b in pthread_mutex_lock (mutex=0x1) at forward.c:182 #1 0xb3e0be91 in ?? () from /lib/libglib-2.0.so.0 #2 0xb3e0c1b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0xb66c60cf in QEventDispatcherGlib::processEvents (this=0xa520478, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #4 0xb6698b49 in QEventLoop::processEvents (this=0xae798280, flags=) at kernel/qeventloop.cpp:149 #5 0xb6698f9a in QEventLoop::exec (this=0xae798280, flags=...) at kernel/qeventloop.cpp:201 #6 0xb659b619 in QThread::exec (this=0x9a2a160) at thread/qthread.cpp:487 #7 0xaea8b94a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so #8 0xb659dfae in QThreadPrivate::start (arg=0x9a2a160) at thread/qthread_unix.cpp:248 #9 0xb465d955 in start_thread (arg=0xae798b70) at pthread_create.c:300 #10 0xb58fc10e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 4 (Thread 0xaa588b70 (LWP 8345)): #0 0xb7709424 in __kernel_vsyscall () #1 0xb58ee916 in *__GI___poll (fds=0xb5972ff4, nfds=1, timeout=333) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xae8e89bf in ?? () from /usr/lib/xine/plugins/1.28/xineplug_ao_out_alsa.so Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 3 (Thread 0xa9d87b70 (LWP 8346)): #0 0xb7709424 in __kernel_vsyscall () #1 0xb4661f7f in __pthread_cond_wait (cond=0xaa2b760, mutex=0xaa2b748) at pthread_cond_wait.c:153 #2 0xb59090bd in __pthread_cond_wait (cond=0xaa2b760, mutex=0xaa2b748) at forward.c:139 #3 0xaea4e7f6 in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 2 (Thread 0xa8b96b70 (LWP 8347)): #0 0xb7709424 in __kernel_vsyscall () #1 0xb58f5291 in select () at ../sysdeps/unix/syscall-template.S:82 #2 0xaea67358 in xine_usec_sleep () from /usr/lib/libxine.so.1 #3 0x in ?? () Thread 1 (Thread 0xb2670710 (LWP 2949)): [KCrash Handler] #6 0xb49f0e8a in MessageList::Core::Item::parent (this=0xbfa03b84) at ../../messagelist/core/item.cpp:417 #7 0xb61c4d82 in QModelIndex::parent (this=0x8db5f38, index=...) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:389 #8 QTreeView::indexRowSizeHint (this=0x8db5f38, index=...) at itemviews/qtreeview.cpp:2818 #9 0xb61c55d9 in QTreeViewPrivate::itemHeight (this=0x8e169e0, item=57) at itemviews/qtreeview.cpp:3239 #10 0xb61c5942 in QTreeViewPrivate::updateScrollBars (this=0x8e169e0) at itemviews/qtreeview.cpp:3502 #11 0xb61c5be5 in QTreeView::updateGeometries (this=0x8db5f38) at itemviews/qtreeview.cpp:2746 #12 0xb4a2dee6 in MessageList::Core::View::updateGeometries (this=0x2) at ../../messagelist/core/view.cpp:179 #13 0xb4a0e1c0 in MessageList::Core::ModelPrivate::viewItemJobStepInternal (this=0x8ddfc50) at ../../messagelist/core/model.cpp:3848 #14 0xb4a0ea3e in MessageList::Core::ModelPrivate::viewItemJobStep (this=0x8ddfc50) at ../../messagelist/core/model.cpp:3965 #15 0xb4a10a51 in MessageList::Core::Model::qt_metacall (this=0x8ddaf28, _c=QMetaObject::InvokeMetaMethod, _id=26, _a=0xbfa0401c) at ./model.moc:90 #16 0xb669f80a in QMetaObject::metacall (object=0x8ddaf28, cl=QMetaObject::InvokeMetaMethod, idx=26, argv=0xbfa0401c) at kernel/qmetaobject.cpp:237 #17 0xb66ae1db in QMetaObject::activate (sender=0x8ddfc6c, m=0xb67ae724, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295 #18 0xb67007e7 in QTimer::timeout (this=0x8ddfc6c) at .moc/release-shared/moc_qtimer.cpp:134 #19 0xb66b60be in QTimer::timerEvent (this=0x8ddfc6c, e=0xbfa04550) at kernel/qtimer.cpp:271 #20 0xb66aac84 in QObject::event (this=0x8ddfc6c, e=0x8ddaf28) at kernel/qobject.cpp:1212 #21 0xb5be35cc in QApplicationPrivate::notify_help
[Bug 237774] Regression: Subject line direction change no longer implies alignment change
https://bugs.kde.org/show_bug.cgi?id=237774 Shai changed: What|Removed |Added Keywords||regression, rtl --- Comment #1 from Shai 2010-05-16 00:45:16 --- Added keywords -- 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 237774] New: Regression: Subject line direction change no longer implies alignment change
https://bugs.kde.org/show_bug.cgi?id=237774
Summary: Regression: Subject line direction change no longer
implies alignment change
Product: kmail
Version: 1.13.3
Platform: Debian testing
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: s...@platonix.com
Version: 1.13.3 (using KDE 4.4.3)
OS:Linux
Installed from:Debian testing/unstable Packages
I use KMail to write all my mails; this includes some that are in Hebrew.
In KDE3, writing direction was auto-detected, which was very good. Whenever I
started to write text in Hebrew, be it in the message text, a subject line or
even a recipient, the field or paragraph (as appropriate; henceforth F/P) would
become RTL, and all was good.
In KDE4 up to and including 4.3.5, writing detection was not auto-detected, but
pressing ctrl-right-shift would still make a F/P RTL. This includes both text
directionality and alignment; when ctrl-right-shift was pressed, any existing
text would hop to the right side, and if there was no text yet, the cursor
would jump to the right.
Now, in 4.4.3 (Debian unstable went directly from 4.3.5 to 4.4.3), this still
works for the message text, but it no longer works correctly for the subject
line. Now, the text directionality is changed to RTL, but the text stays
aligned to the left.
I am talking about the message composer window, of course.
To summarize, again:
Scenario 1:
What I do: Start new message. Put focus on subject line. While subject line is
still empty, Press ctrl-right-shift.
What I expect to see: Cursor hopping to the right side of the subject line
field.
What I see instead: Nothing. It looks like the key press didn't do anything
(although in fact it did).
Scenario 2:
What I do: Start new message. Put some Hebrew text in subject line, and have
cursor at end of text. Press ctrl-right-shift.
What I expect to see: Text hopping to the right side of the subject line field,
and cursor repositioned at its end (that is, on its left side).
What I see instead: Cursor hopping the left side of the text, which is also the
left side ("beginning") of the field. It is quite subtle, and maybe easily
overlooked, in which case, again, the user thinks the key-press achieved
nothing.
Note 1 on scenario 2: Changes in the text can be seen in case the text contains
characters of mixed directionality (that is, both LTR and RTL characters) or if
it is all RTL and ends in punctuation.
Note 2 on scenario 2: In case anybody wants to check this and needs Hebrew text
to paste, here's some: שורת נושא עברית
--
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 237698] New: KMail crashed while selecting addressees for message
https://bugs.kde.org/show_bug.cgi?id=237698 Summary: KMail crashed while selecting addressees for message Product: kmail Version: 1.13.3 Platform: Debian unstable OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@platonix.com Application: kmail (1.13.3) KDE Platform Version: 4.4.3 (KDE 4.4.3) Qt Version: 4.6.2 Operating System: Linux 2.6.32-3-686 i686 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: I wanted to write a message to many recipients. From the message composition window, I pushed the "select" button, and selected a few addresses. Then I realized I want the addresses to be BCC, so I canceled the picker, changed to "BCC", and pressed "select" again. KMail crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 QBasicAtomicInt::deref (this=0xa800734, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:132 #7 QString::operator= (this=0xa800734, other=...) at tools/qstring.cpp:1281 #8 0xb6f2631a in RecipientItem::setRecipientType (this=0x9b27a98) at ../../kmail/recipientspicker.cpp:184 #9 RecipientsPicker::updateList (this=0x9b27a98) at ../../kmail/recipientspicker.cpp:703 #10 0xb6f29be8 in RecipientsPicker::setRecipients (this=0x9b27a98, recipients=...) at ../../kmail/recipientspicker.cpp:644 #11 0xb6f1f8a5 in SideWidget::pickRecipient (this=0xabf0260) at ../../kmail/recipientseditor.cpp:852 #12 0xb6f210d3 in SideWidget::qt_metacall (this=0xabf0260, _c=QMetaObject::InvokeMetaMethod, _id=32, _a=0xbfab0518) at ./recipientseditor.moc:528 #13 0xb67fcaea in QMetaObject::metacall (object=0xabf0260, cl=3062943560, idx=32, argv=0xbfab0518) at kernel/qmetaobject.cpp:237 #14 0xb680b0b5 in QMetaObject::activate (sender=0x98958d8, m=0xb6675584, local_signal_index=2, argv=0xbfab0518) at kernel/qobject.cpp:3293 #15 0xb6466279 in QAbstractButton::clicked (this=0x98958d8, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206 #16 0xb6145369 in QAbstractButtonPrivate::emitClicked (this=0xabf1428) at widgets/qabstractbutton.cpp:546 #17 0xb61461b4 in QAbstractButtonPrivate::click (this=0xabf1428) at widgets/qabstractbutton.cpp:539 #18 0xb614646e in QAbstractButton::mouseReleaseEvent (this=0x98958d8, e=0xbfab0d14) at widgets/qabstractbutton.cpp:1121 #19 0xb5d9ce78 in QWidget::event (this=0x98958d8, event=0xbfab0d14) at kernel/qwidget.cpp:7998 #20 0xb614520e in QAbstractButton::event (this=0x98958d8, e=0xa501801) at widgets/qabstractbutton.cpp:1080 #21 0xb61ef712 in QPushButton::event (this=0x98958d8, e=0xbfab0d14) at widgets/qpushbutton.cpp:679 #22 0xb5d3ebec in QApplicationPrivate::notify_helper (this=0x912eb68, receiver=0x98958d8, e=0xbfab0d14) at kernel/qapplication.cpp:4300 #23 0xb5d460f7 in QApplication::notify (this=0xbfab15a0, receiver=0x98958d8, e=0xbfab0d14) at kernel/qapplication.cpp:3865 #24 0xb766b7da in KApplication::notify (this=0xbfab15a0, receiver=0x98958d8, event=0xbfab0d14) at ../../kdeui/kernel/kapplication.cpp:302 #25 0xb67f78eb in QCoreApplication::notifyInternal (this=0xbfab15a0, receiver=0x98958d8, event=0xbfab0d14) at kernel/qcoreapplication.cpp:704 #26 0xb5d45052 in QCoreApplication::sendEvent (receiver=0x98958d8, event=0xbfab0d14, alienWidget=0x0, nativeWidget=0x98958d8, buttonDown=0xb6683918, lastMouseReceiver=..., spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #27 QApplicationPrivate::sendMouseEvent (receiver=0x98958d8, event=0xbfab0d14, alienWidget=0x0, nativeWidget=0x98958d8, buttonDown=0xb6683918, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2965 #28 0xb5dd009c in QETWidget::translateMouseEvent (this=0x98958d8, event=0xbfab1160) at kernel/qapplication_x11.cpp:4368 #29 0xb5dcf5ab in QApplication::x11ProcessEvent (this=0xbfab15a0, event=0xbfab1160) at kernel/qapplication_x11.cpp:3379 #30 0xb5dfd6f2 in x11EventSourceDispatch (s=0x91319a8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #31 0xb3f6a2f5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #32 0xb3f6dfd8 in ?? () from /lib/libglib-2.0.so.0 #33 0xb3f6e1b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #34 0xb68232f5 in QEventDispatcherGlib::processEvents (this=0x90fbc20, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #35 0xb5dfd255 in QGuiEventDispatcherGlib::processEvents (this=0x90fbc20, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #36 0xb67f5f09 in QEventLoop::processEvents (this=0xbfab1454, flags=) at kernel/qeventloop.cpp:149 #37 0xb67f635a in QEventLoop::exec (this=0xbfab1454, flags=...) at kernel/qeventloop.cpp:201 #38 0xb67fa4ef in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #39 0xb5d3ec87 in QApplication::exec () at kernel/qapplication.cpp:3579 #40 0x0804aafe in main (argc=3, argv=0xb
[Bug 219842] Markers for range selections not updated - sorting changes selected message
https://bugs.kde.org/show_bug.cgi?id=219842 --- Comment #10 from Shai 2010-04-07 13:27:07 --- (In reply to comment #9) > I think that both issues are sympthoms of the same bug. The selected message > changes when sorting because the selection points to a specific row in a list > - > and not to a specific message. I do not understand. That is, assuming the selection "points" to a row by keeping its index in the current sort order, it is natural that the selection will change with the ordering. However, I don't see how that facilitates the situation where one row is highlighted while another is actually selected, or, at least, serves as the basis for a group selection. -- 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 219842] Markers for range selections not updated - sorting changes selected message
https://bugs.kde.org/show_bug.cgi?id=219842 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #8 from Shai 2010-04-04 18:37:33 --- Hmm. I think this bug confuses two different misbehaviors. In one of them -- #224984, #220884, #228682, #232264 and #232916 -- the selected message just changes when the ordering changes. In the other one -- #219842 (this) and #221759 -- the issue is a separation between two notions of "selected message", such that the display is wrong. Note that #221759 doesn't even have an order change, in the strict sense -- it's the ordered set that is changed. I should note that "my" report -- #232916 is a copy of a Debian bug that I filed -- may warrant raising the severity of this bug, as it shows a situation where the change in message selection is "spontaneous", that is, it happens as a result of the passage of time, and not in response to a user action. -- 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 230934] First search became weird, then kmail went down
https://bugs.kde.org/show_bug.cgi?id=230934 --- Comment #2 from Shai 2010-03-16 20:21:36 --- Funny. I reproduced that bug perfectly well on my other machine which runs OpenSuSE (like the reporter's), but my Debian seems unaffected. -- 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 230934] New: First search became weird, then kmail went down
https://bugs.kde.org/show_bug.cgi?id=230934 Summary: First search became weird, then kmail went down Product: kmail Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@platonix.com Application that crashed: kmail Version of the application: 1.12.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.32-trunk-686 i686 Distribution: Debian GNU/Linux unstable (sid) What I was doing when the application crashed: I have a folder where I dump several mailing lists, and a search to extract one of them. I knew that this search found 26 unread messages out of ~200. Today I glanced at it, and it only showed one unread, and claimed to have only two in total. I tried to look at its details to investigate, and KMail crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0xb3648700 (LWP 12947))] Thread 6 (Thread 0xaf819b70 (LWP 2493)): #0 0xb783a424 in __kernel_vsyscall () #1 0xb4d273d2 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179 #2 0xb5c0b864 in __pthread_cond_timedwait (cond=0xa7b9718, mutex=0xa7b9700, abstime=0xaf819350) at forward.c:152 #3 0xaf91ead3 in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 5 (Thread 0xae108b70 (LWP 2494)): #0 0xb783a424 in __kernel_vsyscall () #1 0xb5bf0b27 in *__GI___poll (fds=0x8b478f8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb3f9804b in g_poll () from /lib/libglib-2.0.so.0 #3 0xb3f8b20b in ?? () from /lib/libglib-2.0.so.0 #4 0xb3f8b503 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0xb68b705f in QEventDispatcherGlib::processEvents (this=0x8283c30, flags=...) at kernel/qeventdispatcher_glib.cpp:409 #6 0xb688a83a in QEventLoop::processEvents (this=0xae1082e0, flags=...) at kernel/qeventloop.cpp:149 #7 0xb688ac82 in QEventLoop::exec (this=0xae1082e0, flags=...) at kernel/qeventloop.cpp:201 #8 0xb6798309 in QThread::exec (this=0x8d74568) at thread/qthread.cpp:487 #9 0xaf96b48a in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so #10 0xb679b5e2 in QThreadPrivate::start (arg=0x8d74568) at thread/qthread_unix.cpp:188 #11 0xb4d23585 in start_thread (arg=0xae108b70) at pthread_create.c:300 #12 0xb5bfe29e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 4 (Thread 0xac174b70 (LWP 2497)): #0 0xb783a424 in __kernel_vsyscall () #1 0xb5bef3cb in read () from /lib/i686/cmov/libc.so.6 #2 0xaf9ec972 in ?? () from /usr/lib/libasound.so.2 #3 0xaf9e984d in snd_ctl_read () from /usr/lib/libasound.so.2 #4 0xaf9e5c64 in snd_hctl_handle_events () from /usr/lib/libasound.so.2 #5 0xaf9f18c1 in snd_mixer_handle_events () from /usr/lib/libasound.so.2 #6 0xac2d6b51 in ?? () #7 0xae4079f4 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 3 (Thread 0xab7ffb70 (LWP 2498)): #0 0xb783a424 in __kernel_vsyscall () #1 0xb4d270a5 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:122 #2 0xb5c0b80d in __pthread_cond_wait (cond=0xae4160c0, mutex=0xae4160a8) at forward.c:139 #3 0xaf92f6ca in ?? () from /usr/lib/libxine.so.1 #4 0x in ?? () Thread 2 (Thread 0xaa5ffb70 (LWP 2499)): #0 0xb783a424 in __kernel_vsyscall () #1 0xb5bf7591 in select () from /lib/i686/cmov/libc.so.6 #2 0xaf947df4 in xine_hexdump () from /usr/lib/libxine.so.1 #3 0x in ?? () Thread 1 (Thread 0xb3648700 (LWP 12947)): [KCrash Handler] #6 0xb6f89c63 in KMail::MessageListView::Widget::getSelectionStats (this=0x855d6d0, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbfa7c4bf, includeCollapsedChildren=) at ../../kmail/messagelistview/widget.cpp:580 #7 0xb6f82266 in KMail::MessageListView::Pane::getSelectionStats (this=0x859ce48, selectedSernums=..., selectedVisibleSernums=..., allSelectedBelongToSameThread=0xbfa7c4bf, includeCollapsedChildren=true) at ../../kmail/messagelistview/pane.cpp:622 #8 0xb6e331ac in KMMainWidget::updateMessageActions (this=0x8550698) at ../../kmail/kmmainwidget.cpp:4274 #9 0xb6e4c6d2 in KMMainWidget::qt_metacall (this=0x8550698, _c=QMetaObject::InvokeMetaMethod, _id=21, _a=0xbfa7c598) at ./kmmainwidget.moc:367 #10 0xb68a1303 in QMetaObject::activate (sender=0x89061f0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #11 0xb68a1f42 in QMetaObject::activate (sender=0x89061f0, m=0xb697dd84, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #12 0xb68dcb37 in QTimer::timeout (this=0x89061f0) at .moc/release-shared/moc_qtimer.cpp:128 #13 0xb68a765e in QTimer::timerEvent (this=0x89061f0, e=
[Bug 215397] Hebrew Messages are Displayed with Jumpy Margins
https://bugs.kde.org/show_bug.cgi?id=215397 Shai changed: What|Removed |Added CC||s...@platonix.com --- Comment #3 from Shai 2009-12-30 01:21:57 --- I have failed to reproduce the bug on KDE 4.3.85 (4.4 beta 2) compiled from clean KDE sources (revision 1066139). It may have to do with some specific selection of fonts, or a Mandriva patch. I'm working on Debian, in case it is relevant. -- 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 207197] New: kmail crash sending queued messages after new folder creation
https://bugs.kde.org/show_bug.cgi?id=207197 Summary: kmail crash sending queued messages after new folder creation Product: kmail Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@platonix.com Application that crashed: kmail Version of the application: 1.12.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.30-1-686 i686 Distribution: Debian GNU/Linux unstable (sid) What I was doing when the application crashed: I don't expect this to be trivially reproducible, but here goes... What I did before the crash: I had created a new subfolder of my inbox, copied several messages into it. Some of them were unread or new, so I marked the originals as read. Then I moved to my outbox. I have filters which try to redirect some of the mails I receive to another account on the same machine, and usually these mails are not sent immediately but just accumulate in the outbox. I had about 7-8 of them. Of these, I viewed three, turning them from "unread" to "read", and then selected "Send queued messages". During the sending operation, kmail crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0xb73fc68b in KMReaderWin::parseMsg (this=0xa05ae48, aMsg=0xac99740) at ../../kmail/kmreaderwin.cpp:1678 #7 0xb73eaa0b in KMReaderWin::displayMessage (this=0xa05ae48) at ../../kmail/kmreaderwin.cpp:1605 #8 0xb73eac20 in KMReaderWin::updateReaderWin (this=0xa05ae48) at ../../kmail/kmreaderwin.cpp:1545 #9 0xb73f7647 in KMReaderWin::qt_metacall (this=0xa05ae48, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf89fed8) at ./kmreaderwin.moc:168 #10 0xb7063b33 in QMetaObject::activate (sender=0xa05aea0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #11 0xb7064782 in QMetaObject::activate (sender=0xa05aea0, m=0xb713fde4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #12 0xb709f177 in QTimer::timeout (this=0xa05aea0) at .moc/release-shared/moc_qtimer.cpp:128 #13 0xb7069e9e in QTimer::timerEvent (this=0xa05aea0, e=0xbf8a035c) at kernel/qtimer.cpp:261 #14 0xb705ebcf in QObject::event (this=0xa05aea0, e=0xbf8a035c) at kernel/qobject.cpp:1074 #15 0xb668e814 in QApplicationPrivate::notify_helper (this=0x9cd00e0, receiver=0xa05aea0, e=0xbf8a035c) at kernel/qapplication.cpp:4056 #16 0xb669697e in QApplication::notify (this=0xbf8a0678, receiver=0xa05aea0, e=0xbf8a035c) at kernel/qapplication.cpp:3603 #17 0xb7df24ad in KApplication::notify (this=0xbf8a0678, receiver=0xa05aea0, event=0xbf8a035c) at ../../kdeui/kernel/kapplication.cpp:302 #18 0xb704e9cb in QCoreApplication::notifyInternal (this=0xbf8a0678, receiver=0xa05aea0, event=0xbf8a035c) at kernel/qcoreapplication.cpp:610 #19 0xb707d361 in QCoreApplication::sendEvent (this=0x9cd2e34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 QTimerInfoList::activateTimers (this=0x9cd2e34) at kernel/qeventdispatcher_unix.cpp:572 #21 0xb7079900 in timerSourceDispatch (source=0x9cd2e00) at kernel/qeventdispatcher_glib.cpp:165 #22 0xb477d4b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb4780a13 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0xb4780b98 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0xb7079858 in QEventDispatcherGlib::processEvents (this=0x9ca98d0, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #26 0xb672dfd5 in QGuiEventDispatcherGlib::processEvents (this=0x9ca98d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #27 0xb704d01a in QEventLoop::processEvents (this=0xbf8a0580, flags=...) at kernel/qeventloop.cpp:149 #28 0xb704d462 in QEventLoop::exec (this=0xbf8a0580, flags=...) at kernel/qeventloop.cpp:201 #29 0xb704f8b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #30 0xb668e697 in QApplication::exec () at kernel/qapplication.cpp:3525 #31 0x0804a6d0 in main (argc=) at ../../kmail/main.cpp:146 Reported using DrKonqi -- 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 190910] New: l10n: message list activity aggregation assumes week starts on monday
https://bugs.kde.org/show_bug.cgi?id=190910 Summary: l10n: message list activity aggregation assumes week starts on monday Product: kmail Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: s...@platonix.com Version:(using KDE 4.2.2) OS:Linux Installed from:Debian testing/unstable Packages In the message list, I select the Aggregation Mode to be "Current Activity, Threaded". This groups the messages into categories such as "Today", "Yesterday", "Last week". However, it seems that the division to weeks assumes the week starts on Monday. For example, today, Tuesday 28/4, messages from Sunday 26/4 show up under "Last Week". Here in Israel, weeks start on Sunday, and the "Country/Region&Language"/"Time&Dates" settings are correct; the messages should be under "This week" or "Two days ago" or whatever. (of course, the problem extends further, messages from Sunday 19/4, which should be under "last week", are under "two weeks ago" etc). -- 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 134036] Stop treating every line as a separate paragraph for BIDI purposes
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=134036 --- Additional Comments From shai platonix com 2007-12-20 17:45 --- Created an attachment (id=22634) --> (http://bugs.kde.org/attachment.cgi?id=22634&action=view) Patch for better treatment of directionality I am providing here a patch to implement what I described above: Each line takes its direction from the line before it, unless it is beginning a paragraph. A line begins a paragraph if it is the first, or the previous line was empty, or the previous line is longer than 78 (indicating that it was in fact a paragraph and not a line -- outlook messages sometimes arrive like that), or the previous line is shorter than 78 and adding the first word from this line wouldn't make it longer (that is, we guess that it wasn't broken just for line wrap). I'm pretty sure this is not perfect, because the problem is not well-defined. However, I'm pretty sure it's an improvement. It should fix most of the problems we BiDi users see with lines jumping around and getting messed up in the middle of paragraphs. The only situation I can see, where the patch produces a behavior which is worse than the unpatached version, is where a message has a paragraph ending in a line of length close to 78, the next paragraph is not separated by an empty line (perhaps it is designated by indenting the first line in), and this next paragraph should switch direction. I think this is much more rare than the current problem (a line starting in a word of the other direction in the middle of a paragraph), so I think this patch is worthy. Of course, the patch is GPLed. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 134036] Stop treating every line as a separate paragraph for BIDI purposes
--- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=134036 --- Additional Comments From shai platonix com 2007-12-14 18:04 --- Diego, I will be happy to work on this a little -- I have some time for it these days. I may bug you for assistance. I haven't looked at the text editor or any other part of KMail, but I will be very surprised if at least my item 3 above cannot be handled. One idea I have about handling it is doing "line unwrap" -- a paragraph separator would be any newline that couldn't have been inserted by line wrap (that is, if adding the first word from the next line to the line would still not make the line length over 78). This will still miss some cases (e.g. broken-off end-lines in 5-times-nested quotations), but I think it will be a huge improvement over the current situation. And the cases where it would err on the other side (connect separate paragraphs) are, I think, really rare. I'll try to contact you about this next week. Have fun, Shai. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
