[Bug 311619] Attachment checker checks quoted text
https://bugs.kde.org/show_bug.cgi?id=311619 --- Comment #2 from Laurent Montel mon...@kde.org --- As discussed on irc we can't fix this bug. It's reply when setting reply using HTML if present activated. it's generate a quoted text without quote = so regexp can't exclude it from check. will fix when we will able to use real html composer (see composereditor-ng for 4.11) -- 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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #242 from Silver Salonen silver.salo...@gmail.com --- I agree - although KMail does an acceptable job for me, sometimes the changed e-mail contents is still very important and I end up using some other e-mail clients (even Roundcube webmail) for this purpose. One more thing that frequently happens is that HTML-tables lose borders in KMail compositor. -- 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 311619] Attachment checker checks quoted text
https://bugs.kde.org/show_bug.cgi?id=311619 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- 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 311621] New: No way to set all groups expanded by default
https://bugs.kde.org/show_bug.cgi?id=311621 Bug ID: 311621 Severity: normal Version: 4.9.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: No way to set all groups expanded by default Classification: Unclassified OS: Linux Reporter: juss...@ubuntu.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: message list Product: kmail2 When I enter the mail client, I would like all the groups in the list to be expanded by default. Please add an option to do this. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #243 from Laurent Montel mon...@kde.org --- One more thing that frequently happens is that HTML-tables lose borders in KMail compositor. ? it doesn't import table border format 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
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #244 from Bernd Oliver Sünderhauf pancho...@riseup.net --- As Allen said, this is already covered by a number of more specific bug reports. Plus Laurent currently works on a new composereditor-ng, so we should probably wait how this turns out and then file specific bug reports against it. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 311490] IMAP folders marked with red color
https://bugs.kde.org/show_bug.cgi?id=311490 nucleo nuc...@fedoraproject.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID -- 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 31951] line length in Kmail does not scale with window size
https://bugs.kde.org/show_bug.cgi?id=31951 ele...@gmail.com changed: What|Removed |Added CC||ele...@gmail.com --- Comment #34 from ele...@gmail.com --- Kmail 4.8.5, kubuntu 12.04.1 LTS: Another vote to push this issue to solved. Dynamic wrap is the path to take. So obvious... -- 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 311587] KMail2 crash if trying to opening a Free/Busy-Time-EMail
https://bugs.kde.org/show_bug.cgi?id=311587 Sergio Martins iamser...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||iamser...@gmail.com Assignee|kdepim-bugs@kde.org |iamser...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 311633] New: Kmail does not filter by non-ASCII patterns in message body
https://bugs.kde.org/show_bug.cgi?id=311633 Bug ID: 311633 Severity: minor Version: 4.9 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail does not filter by non-ASCII patterns in message body Classification: Unclassified OS: Linux Reporter: kr...@bigmir.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: Mail Filter Agent Product: Akonadi Mail filtering works for message body only if message contains ASCII symbols. Such messages have Content-Transfer-Encoding: 7Bit. If I have a message with non-ASCII symbols then message have Content-Transfer-Encoding: base64 and is not filtered. Such message is not filtered even it contains ASCII pattern. Reproducible: Always Steps to Reproduce: 1. Create a filter [Filter #0] Applicability=0 AutomaticName=false ConfigureShortcut=true ConfigureToolbar=false Enabled=true Icon=system-run StopProcessingHere=true ToolbarName=Test action-args-0=47 action-name-0=copy actions=1 apply-on=check-mail,manual-filtering contentsA=Test fieldA=body funcA=contains identifier=BXQFswGQDI6gV6Jm name=Test operator=and rules=1 2. Send a message which contains one word Test 3.Send another message with non-ASCII characters, e.g. Test - Тест Actual Results: For step 2 pattern was found and message was copied to specified folder. For step 3 pattern was not found. Expected Results: Pattern is found for both messages (step 2 and 3) and both messages are copied. -- 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 311633] Kmail2 does not filter by non-ASCII patterns in message body
https://bugs.kde.org/show_bug.cgi?id=311633 Kryol kr...@bigmir.net changed: What|Removed |Added Summary|Kmail does not filter by|Kmail2 does not filter by |non-ASCII patterns in |non-ASCII patterns in |message body|message body -- 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 311633] Kmail2 does not filter by non-ASCII patterns in message body
https://bugs.kde.org/show_bug.cgi?id=311633 Kryol kr...@bigmir.net changed: What|Removed |Added CC||kr...@bigmir.net -- 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 311634] New: kontact/kmail hangs then crashes upon openinng/checking for new mail
https://bugs.kde.org/show_bug.cgi?id=311634 Bug ID: 311634 Severity: crash Version: 4.9.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact/kmail hangs then crashes upon openinng/checking for new mail Classification: Unclassified OS: Linux Reporter: bosy...@hotmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.4) KDE Platform Version: 4.9.4 Qt Version: 4.8.2 Operating System: Linux 3.5.0-20-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Just started Kontact, wanted to check mail - but the mail content never showed up. Instead I stared at an empty window for a while, until it crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f4e405737c0 (LWP 14394))] Thread 3 (Thread 0x7f4e38b88700 (LWP 14395)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f4e51bd0dec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f4e52599de0) at wtf/FastMalloc.cpp:2495 #2 0x7f4e51bd0f19 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at wtf/FastMalloc.cpp:1618 #3 0x7f4e4d080e9a in start_thread (arg=0x7f4e38b88700) at pthread_create.c:308 #4 0x7f4e52905cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 2 (Thread 0x7f4e38287700 (LWP 14396)): #0 0x7f4e528fa303 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f4e4cbb3036 in g_main_context_poll (n_fds=1, fds=0x7f4e300029c0, timeout=6365, context=0x7f4e39a0, priority=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3440 #2 g_main_context_iterate (dispatch=1, block=optimized out, context=0x7f4e39a0, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3141 #3 g_main_context_iterate (context=0x7f4e39a0, block=optimized out, dispatch=1, self=optimized out) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3083 #4 0x7f4e4cbb3164 in g_main_context_iteration (context=0x7f4e39a0, may_block=1) at /build/buildd/glib2.0-2.32.3/./glib/gmain.c:3207 #5 0x7f4e5307c906 in QEventDispatcherGlib::processEvents (this=0x7f4e38c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f4e5304be42 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f4e5304c097 in QEventLoop::exec (this=0x7f4e38286dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f4e52f4b057 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7f4e52f4e07b in QThreadPrivate::start (arg=0x24d0240) at thread/qthread_unix.cpp:307 #10 0x7f4e4d080e9a in start_thread (arg=0x7f4e38287700) at pthread_create.c:308 #11 0x7f4e52905cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 1 (Thread 0x7f4e405737c0 (LWP 14394)): [KCrash Handler] #6 0x7f4def93a40f in MailCommon::FolderTreeWidget::selectedCollections (this=0x2e09670) at ../../mailcommon/foldertreewidget.cpp:244 #7 0x7f4defcfe598 in KMMainWidget::updateFolderMenu (this=0x2e09b50) at ../../kmail/kmmainwidget.cpp:4167 #8 0x7f4defd139da in KMMainWidget::qt_static_metacall (_o=0x2e09b50, _c=optimized out, _id=optimized out, _a=0x7fff78d919f0) at ./kmmainwidget.moc:462 #9 0x7f4e53061761 in QMetaObject::activate (sender=0x33b6950, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #10 0x7f4e5306af2f in QSingleShotTimer::timerEvent (this=0x33b6950) at kernel/qtimer.cpp:317 #11 0x7f4e53066659 in QObject::event (this=0x33b6950, e=optimized out) at kernel/qobject.cpp:1157 #12 0x7f4e53a487b4 in notify_helper (e=0x7fff78d92110, receiver=0x33b6950, this=0x23a4a00) at kernel/qapplication.cpp:4556 #13 QApplicationPrivate::notify_helper (this=0x23a4a00, receiver=0x33b6950, e=0x7fff78d92110) at kernel/qapplication.cpp:4528 #14 0x7f4e53a4d583 in QApplication::notify (this=0x7fff78d93e80, receiver=0x33b6950, e=0x7fff78d92110) at kernel/qapplication.cpp:4417 #15 0x7f4e54783786 in KApplication::notify (this=0x7fff78d93e80, receiver=0x33b6950, event=0x7fff78d92110) at ../../kdeui/kernel/kapplication.cpp:311 #16 0x7f4e5304d30c in QCoreApplication::notifyInternal (this=0x7fff78d93e80, receiver=0x33b6950, event=0x7fff78d92110) at kernel/qcoreapplication.cpp:915 #17 0x7f4e5307e6d2 in sendEvent (event=0x7fff78d92110, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #18 QTimerInfoList::activateTimers
[Bug 311646] New: Kmail crash on opening email
https://bugs.kde.org/show_bug.cgi?id=311646 Bug ID: 311646 Severity: crash Version: 4.9.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crash on opening email Classification: Unclassified OS: Linux Reporter: crgla...@gmail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.4) KDE Platform Version: 4.9.4 release 4 Qt Version: 4.8.4 Operating System: Linux 3.1.10-1.16-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: Kmail has been running for 5 hours without issue. Received new mail. Highlighted new email and received this crash. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fb70254f760 (LWP 4142))] Thread 3 (Thread 0x7fb6e9dd9700 (LWP 4143)): #0 0x7fb6fa281e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb6fed0af52 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7fb6fed0af89 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7fb6fa27df05 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb6ffa4f10d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb6e94d8700 (LWP 4144)): #0 0x7fb6ffa45ff3 in poll () from /lib64/libc.so.6 #1 0x7fb6f9d6eae8 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb6f9d6efa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb7001bfa36 in QEventDispatcherGlib::processEvents (this=0x7fb6e40008c0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fb70018f252 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fb70018f4a7 in QEventLoop::exec (this=0x7fb6e94d7e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fb70008d777 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7fb7000907dc in QThreadPrivate::start (arg=0x6404c0) at thread/qthread_unix.cpp:338 #8 0x7fb6fa27df05 in start_thread () from /lib64/libpthread.so.0 #9 0x7fb6ffa4f10d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb70254f760 (LWP 4142)): [KCrash Handler] #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x4cf2b70, hm=optimized out, sc=optimized out, rp=optimized out, pu=optimized out, db=optimized out, contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:842 #7 0x7fb6fb24c379 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x4cf2b70, _c=optimized out, _id=optimized out, _a=optimized out) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:97 #8 0x7fb7001a9946 in QObject::event (this=0x4cf2b70, e=optimized out) at kernel/qobject.cpp:1203 #9 0x7fb700bb11e4 in notify_helper (e=0x7fb6800071d0, receiver=0x4cf2b70, this=0x63d850) at kernel/qapplication.cpp:4562 #10 QApplicationPrivate::notify_helper (this=0x63d850, receiver=0x4cf2b70, e=0x7fb6800071d0) at kernel/qapplication.cpp:4534 #11 0x7fb700bb5fb3 in QApplication::notify (this=0x7fffc522eb60, receiver=0x4cf2b70, e=0x7fb6800071d0) at kernel/qapplication.cpp:4423 #12 0x7fb7018f7506 in KApplication::notify (this=0x7fffc522eb60, receiver=0x4cf2b70, event=0x7fb6800071d0) at /usr/src/debug/kdelibs-4.9.4/kdeui/kernel/kapplication.cpp:311 #13 0x7fb70019071c in QCoreApplication::notifyInternal (this=0x7fffc522eb60, receiver=0x4cf2b70, event=0x7fb6800071d0) at kernel/qcoreapplication.cpp:946 #14 0x7fb700193fca in sendEvent (event=0x7fb6800071d0, receiver=0x4cf2b70) at kernel/qcoreapplication.h:231 #15 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x60d850) at kernel/qcoreapplication.cpp:1570 #16 0x7fb7001bf5a3 in sendPostedEvents () at kernel/qcoreapplication.h:236 #17 postEventSourceDispatch (s=0x643230) at kernel/qeventdispatcher_glib.cpp:279 #18 0x7fb6f9d6e5dd in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #19 0x7fb6f9d6edd8 in ?? () from /usr/lib64/libglib-2.0.so.0 #20 0x7fb6f9d6efa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #21 0x7fb7001bf9cf in QEventDispatcherGlib::processEvents (this=0x60d110, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #22 0x7fb700c54abe in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #23 0x7fb70018f252 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #24 0x7fb70018f4a7 in QEventLoop::exec (this=0x7fffc522eaf0, flags=...) at kernel/qeventloop.cpp:204 #25 0x7fb7001942c5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #26 0x004038c9 in main (argc=1, argv=0x7fffc522f188) at /usr/src/debug/kdepim-4.9.4/kontact/src/main.cpp:219 Possible duplicates by query: bug 311259, bug 311056, bug 306649, bug 306400, bug 306298. Reported
[Bug 302707] KMail Fatal Error: Accessed global static 'SchedulerPrivate *schedulerPrivate()'
https://bugs.kde.org/show_bug.cgi?id=302707 Martin littlec...@gmx.net changed: What|Removed |Added CC||littlec...@gmx.net -- 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 302707] KMail Fatal Error: Accessed global static 'SchedulerPrivate *schedulerPrivate()'
https://bugs.kde.org/show_bug.cgi?id=302707 --- Comment #3 from Martin littlec...@gmx.net --- Created attachment 75815 -- https://bugs.kde.org/attachment.cgi?id=75815action=edit New crash information added by DrKonqi kontact (4.9.4) on KDE Platform 4.9.4 using Qt 4.8.3 - What I was doing when the application crashed: I had two active activities, Kontact running on one of them, I was using the other. When I clicked on the Kontact icon in the icon-only task manager Kontact crashed. I tried three times to reproduce the crash by running Kontact on a different activity from where I activated it but, alas, with no luck ;) -- Backtrace (Reduced): #6 0x7f3cbe5b7425 in __GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f3cbe5bab8b in __GI_abort () at abort.c:91 [...] #11 0x7f3c5b70ba47 in operator- (this=optimized out) at ../../mailcommon/mailkernel.cpp:53 #12 MailCommon::Kernel::self () at ../../mailcommon/mailkernel.cpp:69 #13 0x7f3c5b6fe169 in MailCommon::FolderCollection::writeConfig (this=this@entry=0x2d57350) at ../../mailcommon/foldercollection.cpp:208 -- 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 311114] Distribution lists get converted to empty contact entries
https://bugs.kde.org/show_bug.cgi?id=34 Grégory Oestreicher g...@kamago.net changed: What|Removed |Added Component|DAV Resource|kcalcore Version|1.8.1 |4.9 Product|Akonadi |kdepimlibs --- Comment #3 from Grégory Oestreicher g...@kamago.net --- Thanks for the procedure. It appears that the problem comes from KCalCore, which does not have support for the X-ADDRESSBOOKSERVER-MEMBER property. Event worse, this property is not correctly read from the VCard, losing some membership in the process. Re-assigning to the right product. Cheers, Grégory -- 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 311657] New: kmail 2, sometimes doesn't read correctly the email or don't find message structure.
https://bugs.kde.org/show_bug.cgi?id=311657 Bug ID: 311657 Severity: normal Version: 4.9.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail 2, sometimes doesn't read correctly the email or don't find message structure. Classification: Unclassified OS: Linux Reporter: ser...@serjux.com Hardware: Fedora RPMs Status: UNCONFIRMED Component: commands and actions Product: kmail2 As I wrote in kdepim mailing list: I see this problem in 2012-02-06 23:30, that fail to read or find structure, so this is not new, just seems that is a race condition (just happens occasionally ) here is some examples: http://www.serjux.com/Aurea%20e%20Richie%20Campbell%20em%20exclusivo%20no%20seu%20music%20box!.mbox http://www.serjux.com/%5BSPAM%5D.mbox http://www.serjux.com/Brevemente_Nova%20Vers%C3%A3o%20do%20SAPO%20Mail.mbox This one I notice at the time that don't have content boundary in the end, but is legal . Reproducible: Couldn't Reproduce -- 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 311657] kmail 2, sometimes doesn't read correctly the email or don't find message structure.
https://bugs.kde.org/show_bug.cgi?id=311657 --- Comment #1 from Sérgio Basto ser...@serjux.com --- Created attachment 75818 -- https://bugs.kde.org/attachment.cgi?id=75818action=edit other example happens at 4 of dez 2012 -- 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 311666] New: Kontact starts minimized despite lunching it wih --iconify switch
https://bugs.kde.org/show_bug.cgi?id=311666 Bug ID: 311666 Severity: normal Version: 4.9.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact starts minimized despite lunching it wih --iconify switch Classification: Unclassified OS: Linux Reporter: m...@archlinux.us Hardware: Archlinux Packages Status: UNCONFIRMED Component: general Product: kontact Hi all, for some of us that makes extensive use of most Kontact components it would be great if the flag --iconify actually works because launching $ kontact --iconify launchs kontact indeed but to both System Tray _AND_ minimized to the Task Manager. Reproducible: Always Steps to Reproduce: 1. Launch kontact with --iconify flag expecting to have Kontact launched and docked in the systray. 2. 3. Actual Results: With the --iconify option it is indeed launched and docked at the systray... and alongside minimized as any open application in the Task Manager. Expected Results: To launch Kontact *just* iconified, that is launched and hide in the System Tray bar. -- 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 311667] New: If KMail is launched at startup time it will stay Offline.
https://bugs.kde.org/show_bug.cgi?id=311667 Bug ID: 311667 Severity: normal Version: 4.9.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: If KMail is launched at startup time it will stay Offline. Classification: Unclassified OS: Linux Reporter: m...@archlinux.us Hardware: Archlinux Packages Status: UNCONFIRMED Component: general Product: kmail2 If KMail is launched at startup time then it will be stay Offline until you restart it, the Work Online menu option wont't do anything. I suspect there could be a race condition here because while NetworkManager is launched far earlier at boot time (thanks to systemd) the KDE environment may not be able to setup a working internet connection fast enough before Kontact/Kmail is invoked. I use a bash script as a work around that sleeps for ten seconds and then launch Kontact. Reproducible: Always Steps to Reproduce: 1. System Settings - Startup and Shutdown - Add Program - kontact --iconify 2. 3. Actual Results: Log out and in again: it should work - meaning KMail will be Online. Reboot: -- it shoudln't work now. Kmail will be launched Offline and the only way to change it back online is to restart the app (or the whole Kontact PIM Suite). Expected Results: When Kmail/Kontact is started it is already online. -- 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 311666] Kontact starts minimized despite lunching it wih --iconify switch
https://bugs.kde.org/show_bug.cgi?id=311666 Jekyll Wu adap...@gmail.com changed: What|Removed |Added CC||adap...@gmail.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
