[Bug 143187] session management problems (kontact often thinks it is already running)
https://bugs.kde.org/show_bug.cgi?id=143187 --- Comment #24 from Jose 2010-01-19 14:43:29 --- That's right. Now I have Kopete running and set to online by default, so it starts first and opens kwallet. Then, Kontact does not crash. The same happens with NetworkManager using kwallet to store its passwords. But if nothing opens kwallet and kontact tries to open it, it fails with the aforementioned error. -- 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 143187] session management problems (kontact often thinks it is already running)
https://bugs.kde.org/show_bug.cgi?id=143187 Jose changed: What|Removed |Added CC||getace...@yahoo.es --- Comment #16 from Jose 2009-02-26 09:53:19 --- I'm getting this bug on Kubuntu Intrepid with KDE 4.2.0. I have an IMAP account. Everytime KDE starts, it warns be about kontact being running. If I click on continue, then two instances of Kontact open, if I close one of them, both of them crash. If I click on exit, nothing happens but I have to start kontact manually and then everything is ok. It didn't happen with KDE 4.1 -- 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 187023] Kontact starts twice on KDE start
https://bugs.kde.org/show_bug.cgi?id=187023 Jose changed: What|Removed |Added CC||getace...@yahoo.es --- Comment #1 from Jose 2009-04-03 14:29:41 --- It still happens in KDE 4.2.2 -- 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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]
https://bugs.kde.org/show_bug.cgi?id=169048 Jose changed: What|Removed |Added CC||getace...@yahoo.es -- 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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]
https://bugs.kde.org/show_bug.cgi?id=169048 --- Comment #27 from Jose 2010-06-22 10:06:50 --- Created an attachment (id=48213) --> (http://bugs.kde.org/attachment.cgi?id=48213) New crash information added by DrKonqi I just defined a filter on an imap acount. Kontact crashed when an e-mail arrived. It doesn't crash always. -- 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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]
https://bugs.kde.org/show_bug.cgi?id=169048 --- Comment #28 from Jose 2010-06-22 10:13:13 --- Created an attachment (id=48214) --> (http://bugs.kde.org/attachment.cgi?id=48214) New crash information added by DrKonqi Well, it always happens. The case is that I had a KDE 4.4.4 installation but it was upgraded from KDE 4.0.X to 4.4.4. I had some filters defined in kontact and it never crashed because of them. Then, I renamed the .kde directory because the configuration was messed for some applications and I started with a new .kde folder. I have configured everything but as it was expected, my old filters were forgotten. Now I've defined them again and it has started to crash, which it didn't do before. -- 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 236782] Akonadi ical plugin crashes when I open my session
https://bugs.kde.org/show_bug.cgi?id=236782 Jose changed: What|Removed |Added CC||getace...@yahoo.es -- 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 236782] Akonadi ical plugin crashes when I open my session
https://bugs.kde.org/show_bug.cgi?id=236782 --- Comment #4 from Jose 2010-06-23 08:36:10 --- Created an attachment (id=48251) --> (http://bugs.kde.org/attachment.cgi?id=48251) New crash information added by DrKonqi It started crashing once I added a Google Calendar resource to KOrganizer -- 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 236782] Akonadi ical plugin crashes when I open my session
https://bugs.kde.org/show_bug.cgi?id=236782 --- Comment #5 from Jose 2010-06-23 08:37:53 --- I deleted the Akonadi resource from KOrganizer and it stopped crashing. -- 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 166021] New: "m" key for moving messages works very slowly
--- 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=166021 Summary: "m" key for moving messages works very slowly Product: kmail Version: 1.9.52 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: jcouto wanadoo es Version: 1.9.52 (using 4.00.84 (KDE 4.0.84 (KDE 4.1 >= 20080625), Debian packages) Compiler: cc OS:Linux (i686) release 2.6.25-2-686 When you press the "m" key for moving a message to a folder, the dialog box for choosing the folder takes much time to appear. This renders the "m" key unusable. You are building a great piece of software inside of the amazing KDE4 framework. Congratulations! ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 166022] New: "m" key for moving messages works very slowly
--- 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=166022 Summary: "m" key for moving messages works very slowly Product: kmail Version: 1.9.52 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: jcouto wanadoo es Version: 1.9.52 (using 4.00.84 (KDE 4.0.84 (KDE 4.1 >= 20080625), Debian packages) Compiler: cc OS:Linux (i686) release 2.6.25-2-686 When you press the "m" key for moving a message to a folder, the dialog box for choosing the folder takes much time to appear. This renders the "m" key unusable. You are building a great piece of software inside of the amazing KDE4 framework. Congratulations! ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 169921] New: "Exchange compatible invitation naming" option doesn't stay checked
http://bugs.kde.org/show_bug.cgi?id=169921 Summary: "Exchange compatible invitation naming" option doesn't stay checked Product: kmail Version: 1.10.0 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version: 1.10.0 (using 4.1.00 (KDE 4.1.0), Debian packages) Compiler: cc OS:Linux (i686) release 2.6.26-1-686 Go to Settings > Configure KMail > Misc > Groupware > Groupware Compatability & Legacy Options. Check "Exchange compatible invitation naming" and the other compatability options. Accept the dialog and open it again. The compatible invitation naming is not checked. Regards. -- Configure bugmail: http://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
[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar
https://bugs.kde.org/show_bug.cgi?id=334569 Jose Roberto changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||colombo...@gmail.com --- Comment #17 from Jose Roberto --- I would link to ask to reopen this bug because I am having this issue right now. I can provide more information if required. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Stable (kernel 5.10.27) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are on the CC list for the bug.
[kmail] [Bug 131642] Mark selected message as read after X seconds should be disabled while selecting messages
https://bugs.kde.org/show_bug.cgi?id=131642 Jose Couto changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WAITINGFORINFO |--- --- Comment #5 from Jose Couto --- Hello. The request is still valid for Kmail2. Regards. -- 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 320950] New: Importing mails from Thunderbird doesn't work completely
https://bugs.kde.org/show_bug.cgi?id=320950
Bug ID: 320950
Summary: Importing mails from Thunderbird doesn't work
completely
Classification: Unclassified
Product: Akonadi
Version: 4.10
Platform: Debian unstable
URL: http://forum.kde.org/viewtopic.php?f=215&t=111005
OS: Linux
Status: UNCONFIRMED
Severity: grave
Priority: NOR
Component: Migration
Assignee: kdepim-bugs@kde.org
Reporter: coque.co...@gmail.com
When I run kmailcvt to import my email from icedove (Debian's Thunderbird), it
finishes without errors, but some folders doesn't get imported.
Several hours after kmailcvt has finished, the emails' files in the maildir
resource continue to grow, whithout having any clue about when the process is
complete.
Reproducible: Always
Steps to Reproduce:
1.Erase the KMail/Akonadi/Nepomuk configuration and data with the following
commands:
cd ~
akonadictl stop
find .kde .local .config -name '*kmail*' -exec rm -rf \{\} \;
find .kde .local .config -name '*akonadi*' -exec rm -rf \{\} \;
find .kde .local .config -name '*nepomuk*' -exec rm -rf \{\} \;
rm -rf ~/.local/share/local-mail/
2. Launch kmailcvt and import the Thunderbird emails (10GB more or less). It
lasts around 1h, and it ends without errors.
3. Monitor the maildir repository for new mails. In my case, it is located at
~/.local/share/akonadi_maildir_resource_0. I do a "find . > /tmp/maildir-`date
+%Y%m%d%H%M`.txt" there from time to time with these results:
-rw-r--r-- 1 jcouto jcouto 556444 Jun 8 17:49 maildir-201306081749.txt
-rw-r--r-- 1 jcouto jcouto 556574 Jun 8 17:50 maildir-201306081750.txt
-rw-r--r-- 1 jcouto jcouto 557742 Jun 8 17:52 maildir-201306081752.txt
-rw-r--r-- 1 jcouto jcouto 560207 Jun 8 18:00 maildir-201306081800.txt
-rw-r--r-- 1 jcouto jcouto 561375 Jun 8 18:03 maildir-201306081803.txt
-rw-r--r-- 1 jcouto jcouto 565531 Jun 8 18:12 maildir-201306081812.txt
-rw-r--r-- 1 jcouto jcouto 8436095 Jun 8 19:44 maildir-201306081944.txt
-rw-r--r-- 1 jcouto jcouto 8436095 Jun 8 20:06 maildir-201306082006.txt
-rw-r--r-- 1 jcouto jcouto 8436095 Jun 8 20:50 maildir-201306082049.txt
-rw-r--r-- 1 jcouto jcouto 8436095 Jun 8 21:51 maildir-201306082151.txt
-rw-r--r-- 1 jcouto jcouto 8436095 Jun 9 00:10 maildir-201306090010.txt
-rw-r--r-- 1 jcouto jcouto 8436095 Jun 9 10:43 maildir-201306091043.txt
Note that kmailcvt has finished around Jun 8 18:00, while the repository
continues growing for several hours.
Actual Results:
On Jun 9, I miss some folders in the imported email. Besides, Kmail2 is
extremely slow when I select any local folder.
Expected Results:
There should be a way to know when the import process is finished. I'm not sure
where my emails is between kmailcvt has ended and they appear in the file
system. What would have happened if I had turned off my computer just when
kmailcvt had completed?
--
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
[kaddressbook] [Bug 321343] New: Vcard Directory Akonadi resource: Enable changes-by-other-programs monitoring
https://bugs.kde.org/show_bug.cgi?id=321343 Bug ID: 321343 Summary: Vcard Directory Akonadi resource: Enable changes-by-other-programs monitoring Classification: Unclassified Product: kaddressbook Version: 4.9 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jf...@coasin.com.mx CC: to...@kde.org Using a VCard Directory resource for kaddressbook was in the 3.X era the easiest way to share an addressbook among users. Now that Akonadi handles the resource, it looks as if a handled-by-akonadi Database is created and the actual VCard files are used as some sort of back-up. When a second user changes a contact, the Vcard file is changed but the first user doesn't notice this change and therefore doesn't update its Akonadi resource. There was some discussion about it in: http://comments.gmane.org/gmane.comp.kde.users.pim/21477 Kevin Kramer, in what could sum it all, said: "In theory this could be handled very similar to how the maildir handler manages its directories, i.e. monitor for changes by other programs. Limited man power has so far not allowed to apply those enchancements to the vcard directory handler yet." **This could be a bug if thinking of it working "right" in version 3.5. There's another bug (right clicking an akonadi vcard directory resource and clicking refresh doesn't re-read VCard files), but I'm away from my computer. Will report that one later when I can confirm if a qdbus manual command actually re-reads the VCard files and see if it's a bug in the UI or if it's a dbus bug. Reproducible: Always Steps to Reproduce: 1. Add a VCard Directory resource for user A 2. Add a VCard Directory resource for user B pointing to the same directory 3. User B changes a contact detail in the aforementioned resource Actual Results: 4. User A doesn't get the changes User B made Expected Results: 4. Akonadi detects that there was a change in the files and updates the information in its local database -- 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 327769] New: Problemas de contrapropuesta
https://bugs.kde.org/show_bug.cgi?id=327769 Bug ID: 327769 Summary: Problemas de contrapropuesta Classification: Unclassified Product: kmail2 Version: 4.11.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: joselui...@hotmail.com Application: kmail (4.11.2) KDE Platform Version: 4.11.2 Qt Version: 4.8.5 Operating System: Linux 3.11.4-201.fc19.x86_64 x86_64 Distribution: "Fedora release 19 (Schrödinger’s Cat)" -- Information about the crash: - What I was doing when the application crashed: Recibí una invitación de calendario al correo, cuando doy click en contrapropuesta nada pasa por unos minutos hasta que vuelvo a dar click y la aplicación se cierra. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f92b44dc8c0 (LWP 2969))] Thread 4 (Thread 0x7f92a3c9b700 (LWP 2975)): #0 0x00346780b575 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x003b21ecd34d in WTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQtWebKit.so.4 #2 0x003b21ecd389 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQtWebKit.so.4 #3 0x003467807c53 in start_thread () from /lib64/libpthread.so.0 #4 0x003466cf5e1d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f9262556700 (LWP 2976)): #0 0x00346780b575 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x003b21c0dadd in JSC::BlockAllocator::blockFreeingThreadMain() () from /lib64/libQtWebKit.so.4 #2 0x003b21efcba6 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQtWebKit.so.4 #3 0x003467807c53 in start_thread () from /lib64/libpthread.so.0 #4 0x003466cf5e1d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f9261090700 (LWP 2978)): #0 0x003469c86f9a in g_mutex_get_impl () from /lib64/libglib-2.0.so.0 #1 0x003469c87279 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #2 0x003469c47280 in g_main_context_acquire () from /lib64/libglib-2.0.so.0 #3 0x003469c47fb5 in g_main_context_iterate.isra.22 () from /lib64/libglib-2.0.so.0 #4 0x003469c481fc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x003b117a7166 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #6 0x003b11778ecf in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #7 0x003b117791c5 in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #8 0x003b1167866f in QThread::exec() () from /lib64/libQtCore.so.4 #9 0x003b1167ad0f in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #10 0x003467807c53 in start_thread () from /lib64/libpthread.so.0 #11 0x003466cf5e1d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f92b44dc8c0 (LWP 2969)): [KCrash Handler] #5 0x003b252566d2 in Akonadi::ITIPHandler::processiTIPMessage(QString const&, QString const&, QString const&) () from /lib64/libakonadi-calendar.so.4 #6 0x003b25258ada in Akonadi::ITIPHandler::Private::onLoadFinished(bool, QString const&) () from /lib64/libakonadi-calendar.so.4 #7 0x003b1178df78 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4 #8 0x003b25261614 in Akonadi::FetchJobCalendar::loadFinished(bool, QString const&) () from /lib64/libakonadi-calendar.so.4 #9 0x003b1179232e in QObject::event(QEvent*) () from /lib64/libQtCore.so.4 #10 0x003b133c84dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4 #11 0x003b133ceaa0 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4 #12 0x003b14a3fe9a in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5 #13 0x003b1177a26d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4 #14 0x003b1177d1df in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQtCore.so.4 #15 0x003b117a7883 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQtCore.so.4 #16 0x003469c47e06 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x003469c48158 in g_main_context_iterate.isra.22 () from /lib64/libglib-2.0.so.0 #18 0x003469c481fc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x003b117a7145 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #20 0x003b13464fc6 in QGuiEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtGui.so.4 #21 0x003b11778ecf in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #22 0x003b117791c5 in QEventLoop::exec(QFlags)
[Akonadi] [Bug 331095] New: Error al archivar carpetas de correo
https://bugs.kde.org/show_bug.cgi?id=331095 Bug ID: 331095 Summary: Error al archivar carpetas de correo Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Archive Mail Agent Assignee: kdepim-bugs@kde.org Reporter: joselui...@hotmail.com Application: akonadi_archivemail_agent (4.11) KDE Platform Version: 4.11.5 Qt Version: 4.8.5 Operating System: Linux 3.12.9-201.fc19.x86_64 x86_64 Distribution: "Fedora release 19 (Schrödinger’s Cat)" -- Information about the crash: - What I was doing when the application crashed: Había configurado el archivo automático de carpetas de correo. Después de crear una carpeta de "Archivo". Di inicio forzado al archivado y al poco tiempo me dió el error. -- Backtrace: Application: (akonadi_archivemail_agent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fb14b6068c0 (LWP 2190))] Thread 2 (Thread 0x7fb13da6d700 (LWP 2996)): #0 0x003ebbaeb7fd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x003ebf2480e4 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fb138002bb0, timeout=-1, context=0x7fb1380009a0) at gmain.c:3995 #2 g_main_context_iterate (context=context@entry=0x7fb1380009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3696 #3 0x003ebf2481ec in g_main_context_iteration (context=0x7fb1380009a0, may_block=1) at gmain.c:3762 #4 0x0033853a6d56 in QEventDispatcherGlib::processEvents (this=0x7fb1380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #5 0x003385378b2f in QEventLoop::processEvents (this=this@entry=0x7fb13da6cce0, flags=...) at kernel/qeventloop.cpp:149 #6 0x003385378e25 in QEventLoop::exec (this=this@entry=0x7fb13da6cce0, flags=...) at kernel/qeventloop.cpp:204 #7 0x003385278a1f in QThread::exec (this=this@entry=0x1d3b2c0) at thread/qthread.cpp:536 #8 0x00338535a3e3 in QInotifyFileSystemWatcherEngine::run (this=0x1d3b2c0) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x00338527b0bf in QThreadPrivate::start (arg=0x1d3b2c0) at thread/qthread_unix.cpp:338 #10 0x003ebc607c53 in start_thread (arg=0x7fb13da6d700) at pthread_create.c:308 #11 0x003ebbaf5dbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7fb14b6068c0 (LWP 2190)): [KCrash Handler] #6 ref (this=0x620061004c6160) at ../../src/corelib/arch/qatomic_x86_64.h:121 #7 QUrl::QUrl (this=0x7fff4d265b50, other=...) at io/qurl.cpp:4266 #8 0x003cc9d25bf9 in KUrl::KUrl (this=0x7fff4d265b50, _u=...) at /usr/src/debug/kdelibs-4.11.5/kdecore/io/kurl.cpp:490 #9 0x00413f6a in url (this=0x1f76a30) at /usr/src/debug/kdepim-4.11.5/archivemailagent/archivemailinfo.cpp:215 #10 ArchiveMailInfo::dirArchive (this=this@entry=0x1f76a30) at /usr/src/debug/kdepim-4.11.5/archivemailagent/archivemailinfo.cpp:88 #11 0x00414662 in ArchiveMailInfo::listOfArchive (this=0x1f76a30, folderName=...) at /usr/src/debug/kdepim-4.11.5/archivemailagent/archivemailinfo.cpp:116 #12 0x0040ea23 in ArchiveMailManager::backupDone (this=0x1674720, info=0x1f76a30) at /usr/src/debug/kdepim-4.11.5/archivemailagent/archivemailmanager.cpp:124 #13 0x004167be in ArchiveJob::slotBackupDone (this=0x163a9e0, info=...) at /usr/src/debug/kdepim-4.11.5/archivemailagent/archivejob.cpp:105 #14 0x00338538db98 in QMetaObject::activate (sender=sender@entry=0x2057fd0, m=m@entry=0x3cdab59880 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff4d265ed0) at kernel/qobject.cpp:3547 #15 0x003cda863f92 in MailCommon::BackupJob::backupDone (this=this@entry=0x2057fd0, _t1=...) at /usr/src/debug/kdepim-4.11.5/x86_64-redhat-linux-gnu/mailcommon/backupjob.moc:115 #16 0x003cda864891 in MailCommon::BackupJob::finish (this=0x2057fd0) at /usr/src/debug/kdepim-4.11.5/mailcommon/job/backupjob.cpp:222 #17 0x003cda8661b5 in MailCommon::BackupJob::archiveNextFolder (this=this@entry=0x2057fd0) at /usr/src/debug/kdepim-4.11.5/mailcommon/job/backupjob.cpp:349 #18 0x003cda866a0c in MailCommon::BackupJob::archiveNextMessage (this=0x2057fd0) at /usr/src/debug/kdepim-4.11.5/mailcommon/job/backupjob.cpp:234 #19 0x003385391f3e in QObject::event (this=0x2057fd0, e=) at kernel/qobject.cpp:1194 #20 0x0037a0fc84dc in QApplicationPrivate::notify_helper (this=this@entry=0x14f1270, receiver=receiver@entry=0x2057fd0, e=e@entry=0x21343f0) at kernel/qapplication.cpp:4562 #21 0x0037a0fceaa0 in QApplication::notify (this=this@entry=0x7fff4d266970, receiver=receiver@entry=0x2057fd0, e=e@entry=0x21343f0) at kernel/qapplication.cpp:4348 #22 0x003cca83fd5a in KApplication::notify (this=0x7fff4d266970,
[Bug 232965] often a quote is appended to attachment filename
https://bugs.kde.org/show_bug.cgi?id=232965 Jose Couto changed: What|Removed |Added CC||coque.co...@gmail.com --- Comment #3 from Jose Couto 2011-12-20 17:14:25 --- I'm suffering the same problem with debian unstable's version of kmail (1.13.7 with KDE 4.7.4). These are the headers for the file: Content-Type: application/vnd.openxmlformats-officedocument.presentationml.presentation; name="SAT20112024_VF_IPV6_PROOF_OF_CONCEPT_v0.4.pptx" Content-Description: SAT20112024_VF_IPV6_PROOF_OF_CONCEPT_v0.4.pptx Content-Disposition: attachment; filename="SAT20112024_VF_IPV6_PROOF_OF_CONCEPT_v0.4.pptx"; size=1449021; creation-date="Wed, 30 Nov 2011 12:14:04 GMT"; modification-date="Wed, 07 Dec 2011 16:10:52 GMT" Content-Transfer-Encoding: base64 -- 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 131642] Mark selected message as read after X seconds should be disabled while selecting messages
https://bugs.kde.org/show_bug.cgi?id=131642 --- Comment #4 from Jose Couto --- I'm using Debian Unstable, which hasn't upgraded Kmail to Kmail2 yet. I'll upgrade the request as soon as I test the new Kmail, but I'd be glad to see anyone with access to Kmail2 do it now. Regards. -- 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 139551] index files from 774 to 700 for security improvement
http://bugs.kde.org/show_bug.cgi?id=139551 --- Comment #4 from Jose Da Silva 2008-09-23 11:03:05 --- Yes, I see .kde/share/kmail has rwx-- folder rights in Kmail 1.9.9 under KDE3.5.9 In 3.3 it was worse, but in 3.5 various files are still created as rw-rw-r-- If Linux provides you tools to improve security, why not make use of them? :-) Let's say for example that today you have several shared plugins such as flash animation for Firefox, Konqueror, or Opera could it be conceivable that in future that it may be possible to share email data between clients...say Kmail if you do it by GUI, and some other mail client such as "mail" if you do/read/parse/other by script. Let's suppose that you keep your mail in a common location such as ~/.Mail and put a link from ~/.kde/shared/apps/kmail/mail to ~/.Mail but ~/.Mail is rwxr-xr-x The above is a "what-if?" scenario, and allowing the file system to hold an additional level of security by making your files rw--- is just an additional precaution for unlikely "what-if?"s Just a thought Jose -- Configure bugmail: http://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 208245] New: Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 Summary: Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it Product: kmail Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: digi...@joescat.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.31-desktop-2mnb i686 Distribution: "Mandriva Linux 2010.0" What I was doing when the application crashed: Currently testing Mandriva 2010.0 RC1 with KDE 4.3.1 and Kmail 1.12.1 and was able to repeatedly crash Kmail when I created a new folder, then copied an email from my inbox (in maildir format) into my new folder (I called inba which was in mbox format), then attempted to look at the new email in the inba folder, at which point Kmail crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0x0001 in ?? () #7 0xb757044a in ?? () from /usr/lib/libkmailprivate.so.4 #8 0xb75669dd in ?? () from /usr/lib/libkmailprivate.so.4 #9 0xb7566b33 in ?? () from /usr/lib/libkmailprivate.so.4 #10 0xb756a49d in ?? () from /usr/lib/libkmailprivate.so.4 #11 0xb71cac44 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb71cb965 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb7206365 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #14 0xb71d0576 in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #15 0xb71c48fb in QObject::event () from /usr/lib/libQtCore.so.4 #16 0xb67d96cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #17 0xb67e110e in QApplication::notify () from /usr/lib/libQtGui.so.4 #18 0xb7e81a78 in KApplication::notify () from /usr/lib/libkdeui.so.5 #19 0xb71b475e in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #20 0xb71e2c31 in ?? () from /usr/lib/libQtCore.so.4 #21 0xb71e047e in ?? () from /usr/lib/libQtCore.so.4 #22 0xb4667bf2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb466b4c8 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0xb466b5ee in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0xb71e03c8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #26 0xb687b51a in ?? () from /usr/lib/libQtGui.so.4 #27 0xb71b2d7d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #28 0xb71b31c9 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #29 0xb71b5660 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #30 0xb67d9544 in QApplication::exec () from /usr/lib/libQtGui.so.4 #31 0x0804a529 in _start () 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 208245] Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 --- Comment #1 from Jose Da Silva 2009-09-23 08:38:19 --- Created an attachment (id=37120) --> (http://bugs.kde.org/attachment.cgi?id=37120) this is kde bugreport from crash #2 To be sure, I attempted to reproduce the crash. The 1st crash seen is actually the 3rd crash, this attachment is crash #2. -- 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 208245] Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 --- Comment #2 from Jose Da Silva 2009-09-23 08:41:55 --- Created an attachment (id=37121) --> (http://bugs.kde.org/attachment.cgi?id=37121) crash #1 This was the 1st crash produced. To produce the crash, you need to have some emails within your inbox folder. Then create a new folder. My inbox is in maildir format, the new inbox is in mbox format, I named the new inbox with a nonsense name like inba. I then copied an email from my inbox into my inba folder. then I clicked on the email in my inba folder, which then made Kmail crash. This is using Kmail in Mandriva 2010.0 RC1 -- 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 208245] Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 --- Comment #4 from Jose Da Silva 2009-09-24 07:32:01 --- This report happened when I pointed towards the "Local Folder" and right clicked to create a new inba folder (as mbox), copied a simple email from inbox (maildir format) by dragging the email to the inba folder and clicking copy. When I clicked on the copied email within the inba folder, kmail crashed. Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0x0a387380 in ?? () #7 0xb747544a in KMReaderWin::parseMsg (this=0x9ded060, aMsg=0xa2cf100) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1681 #8 0xb746b9dd in KMReaderWin::displayMessage (this=0x9ded060) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1605 #9 0xb746bb33 in KMReaderWin::updateReaderWin (this=0x9ded060) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1545 #10 0xb746f49d in KMReaderWin::qt_metacall (this=0x9ded060, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf948fac) at /usr/src/debug/kdepim-4.3.1/build/kmail/kmreaderwin.moc:168 #11 0xb70cfc44 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb70d0965 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb710b365 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #14 0xb70d5576 in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #15 0xb70c98fb in QObject::event () from /usr/lib/libQtCore.so.4 #16 0xb66de6cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #17 0xb66e610e in QApplication::notify () from /usr/lib/libQtGui.so.4 #18 0xb7d86a78 in KApplication::notify () from /usr/lib/libkdeui.so.5 #19 0xb70b975e in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #20 0xb70e7c31 in ?? () from /usr/lib/libQtCore.so.4 #21 0xb70e547e in ?? () from /usr/lib/libQtCore.so.4 #22 0xb456ab92 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb456e468 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0xb456e58e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0xb70e53c8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #26 0xb678051a in ?? () from /usr/lib/libQtGui.so.4 #27 0xb70b7d7d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #28 0xb70b81c9 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #29 0xb70ba660 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #30 0xb66de544 in QApplication::exec () from /usr/lib/libQtGui.so.4 #31 0x0804a529 in main (argc=3, argv=0xbf9498b4) at /usr/src/debug/kdepim-4.3.1/kmail/main.cpp:146 You may note I copy and pasted the report this time because last time I copy and pasted to kwrite (then saved), but now kwrite crashes when I attempt to save the pasted data, so it may be that kwrite is also affected by the same bug maybe? -- 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 208245] Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 --- Comment #5 from Jose Da Silva 2009-09-24 07:42:17 --- This trace produced while inbox was highlighted, and then I pointed to "File->New->Folder" and created a new folder called inbb (mbox format) which was then attached as a subfolder of inbox (maildir format). I then dragged an email from inbox and copied it into inbb. Then I pointed at inbb, highlighted the new and only email present in inbb and clicked the new email which then crashed kmail. These crashes don't appear to happen if these new inboxes already exist with something already in them. If an email already exists before I drag something in, then I am okay. I also notice that the preview panel is empty when I first click on these new inboxes after I have dragged an email into them. Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0xb73aa447 in KMReaderWin::parseMsg (this=0x85961d0, aMsg=0x8cbdea8) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1681 #7 0xb73a09dd in KMReaderWin::displayMessage (this=0x85961d0) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1605 #8 0xb73a0b33 in KMReaderWin::updateReaderWin (this=0x85961d0) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1545 #9 0xb73a449d in KMReaderWin::qt_metacall (this=0x85961d0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf83df2c) at /usr/src/debug/kdepim-4.3.1/build/kmail/kmreaderwin.moc:168 #10 0xb7004c44 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7005965 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb7040365 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #13 0xb700a576 in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #14 0xb6ffe8fb in QObject::event () from /usr/lib/libQtCore.so.4 #15 0xb66136cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #16 0xb661b10e in QApplication::notify () from /usr/lib/libQtGui.so.4 #17 0xb7cbba78 in KApplication::notify () from /usr/lib/libkdeui.so.5 #18 0xb6fee75e in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #19 0xb701cc31 in ?? () from /usr/lib/libQtCore.so.4 #20 0xb701a47e in ?? () from /usr/lib/libQtCore.so.4 #21 0xb449fb92 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0xb44a3468 in ?? () from /usr/lib/libglib-2.0.so.0 #23 0xb44a358e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #24 0xb701a3c8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #25 0xb66b551a in ?? () from /usr/lib/libQtGui.so.4 #26 0xb6fecd7d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #27 0xb6fed1c9 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #28 0xb6fef660 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #29 0xb6613544 in QApplication::exec () from /usr/lib/libQtGui.so.4 #30 0x0804a529 in main (argc=3, argv=0xbf83e834) at /usr/src/debug/kdepim-4.3.1/kmail/main.cpp:146 -- 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 208245] Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 --- Comment #6 from Jose Da Silva 2009-09-24 07:57:06 --- pointed to local folder and created a new folder. Looked in the new folder called inbc (mbox format, empty, preview panel empty) Copied an email from inbox (maildir format) into the new inbcc box, then looked at the inbcc box. Preview panel empty, clicked on the new (and only) email present, and then kmail crashed. This bug seems repeatable. I've added the Kwrite crash as bug 208351. Maybe the crash information within it may help resolve this crash as well as Kwrite's crash too. Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0x098e9f8c in ?? () #7 0xb754a44a in KMReaderWin::parseMsg (this=0x94ef348, aMsg=0x935f338) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1681 #8 0xb75409dd in KMReaderWin::displayMessage (this=0x94ef348) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1605 #9 0xb7540b33 in KMReaderWin::updateReaderWin (this=0x94ef348) at /usr/src/debug/kdepim-4.3.1/kmail/kmreaderwin.cpp:1545 #10 0xb754449d in KMReaderWin::qt_metacall (this=0x94ef348, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfbe7e3c) at /usr/src/debug/kdepim-4.3.1/build/kmail/kmreaderwin.moc:168 #11 0xb71a4c44 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb71a5965 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb71e0365 in QTimer::timeout () from /usr/lib/libQtCore.so.4 #14 0xb71aa576 in QTimer::timerEvent () from /usr/lib/libQtCore.so.4 #15 0xb719e8fb in QObject::event () from /usr/lib/libQtCore.so.4 #16 0xb67b36cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #17 0xb67bb10e in QApplication::notify () from /usr/lib/libQtGui.so.4 #18 0xb7e5ba78 in KApplication::notify () from /usr/lib/libkdeui.so.5 #19 0xb718e75e in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #20 0xb71bcc31 in ?? () from /usr/lib/libQtCore.so.4 #21 0xb71ba47e in ?? () from /usr/lib/libQtCore.so.4 #22 0xb463fb92 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb4643468 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0xb464358e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0xb71ba3c8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #26 0xb685551a in ?? () from /usr/lib/libQtGui.so.4 #27 0xb718cd7d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #28 0xb718d1c9 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #29 0xb718f660 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #30 0xb67b3544 in QApplication::exec () from /usr/lib/libQtGui.so.4 #31 0x0804a529 in main (argc=3, argv=0xbfbe8744) at /usr/src/debug/kdepim-4.3.1/kmail/main.cpp:146 -- 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 208245] Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 --- Comment #7 from Jose Da Silva 2009-10-12 23:33:59 --- More information plus crash details filed with the mandriva bugzilla. https://qa.mandriva.com/show_bug.cgi?id=53942 It appears this crash is caused by the preview window - more details starting with comment 5 up to 9 https://qa.mandriva.com/show_bug.cgi?id=53942#c5 -- 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 208245] Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 --- Comment #8 from Jose Da Silva 2009-10-12 23:38:25 --- Created an attachment (id=37547) --> (http://bugs.kde.org/attachment.cgi?id=37547) crash report with preview window shown below message list This crash report is already attached in https://qa.mandriva.com/show_bug.cgi?id=53942#c5 There are further snapshots taken in 6...9 at above page. -- 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 180741] crash in kmail (typeinfo name for, KMReaderWin::parseMsg)
https://bugs.kde.org/show_bug.cgi?id=180741 Jose Da Silva changed: What|Removed |Added CC||digi...@joescat.com --- Comment #41 from Jose Da Silva 2009-10-14 02:24:10 --- There appears to be several bugs mentioned in here and I was recommended to become a duplicate of this bug. however, I see what appears to be various bugs lumped in here which makes this bug 180741 only more confusing to figure-out. My bug 208245 has been narrowed-down to be related with the preview window. If it is enabled, then there is a seg fault, if it is turned-off then kmail operates okay and continues to operate okay. This question is probably most related with these bug reports: bug 206180, bug 207197, bug 208296, bug 209008, bug 209704 Question: Are you using the preview window when you reported your bug? Did your kmail crash if you had the preview window enabled. Did your kmail continue to work okay if the preview window was off. If you reported your bug AND you can reproduce the bug with the preview window enabled but cannot reproduce the crash with the preview window turned-off, then you probably have the same bug as bug 208245. Sorry to bother anybody with this strange question if your bug does not appear related to the preview window. Thanks. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 208245] Kmail 1.12.1 on KDE 4.3.1 crashes when new inbox created and file copied to it, then opened in it
https://bugs.kde.org/show_bug.cgi?id=208245 --- Comment #10 from Jose Da Silva 2009-10-14 02:25:45 --- Thanks for pointing-out that bug, but you have several bugs in bug 180741 that may actually be separate problems. Some seem to sound like race-problems where one application looks for info before the other application flushes-out data. This bug creates a segfault and appears only to happen if you enable the preview window, otherwise the problem does not appear to happen. I looked at bug 180741 and I think some of these bugs are related to the preview window: bug 206180, bug 207197, bug 208296, (maybe if there was only 1 message in the trash then also) bug 208314, bug 209008, bug 209704. I'll ask as https://bugs.kde.org/show_bug.cgi?id=180741#c41 hopefully it separates some of those bugs apart. -- 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 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 jose bernardo silva changed: What|Removed |Added CC||josebernar...@yahoo.com -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 180741] crash in kmail (typeinfo name for, KMReaderWin::parseMsg)
https://bugs.kde.org/show_bug.cgi?id=180741 --- Comment #43 from Jose Da Silva 2009-10-17 22:23:06 --- Just want to let you know that with my bug 208245, you can create a crash if you enable preview window in the options, but if you do not enable the preview window, you do not get a crash. I'm guessing this problem is all related to the preview window and whether it is selected or not selected. -- 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 211900] New: kmail attachments not sync with directory contents
https://bugs.kde.org/show_bug.cgi?id=211900 Summary: kmail attachments not sync with directory contents Product: kmail Version: unspecified Platform: Mandriva RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: digi...@joescat.com Version:(using KDE 4.3.2) OS:Linux Installed from:Mandriva RPMs I was asked to report this bug upstream into KDE. It is currently registered in mandriva's bugzilla as bug # 54855 ( http://qa.mandriva.com/show_bug.cgi?id=54855 ) - Description of problem: Kmail has trouble Forwarding some attachments, so as a temporary solution, I have saved attachments into a temporary directory, and then open a new email and attach the attachments from the temporary directory. What I noticed is that kmail does not update it's knowledge of what is in the directory. Version-Release number of selected component (if applicable): kmail in mandriva 2010_rc1 (KDE 4.3.2) How reproducible: Open up an email and save attachments to a temporary directory, then close email, then create a new email and open to attach the attachments - you may have 1 file shown in directory even though there are many files in directory. Once or twice I managed to get kmail to update it's knowledge by using konqueror (pointing to same directory) to show "hidden files" (this creates a .directory file) but this wasn't consistent, so something else is not working right. Steps to Reproduce: 1. Open an email with multiple attachments (that fail to be Forwarded if you tried to Forward email). 2. Click on attachment, select "Save attachment" 3. When it asks to save, Create a new temporary directory, then save the attachment in the new temporary directory. 4. Save other attachments from same email in this new temporary directory. You may notice that Kmail only shows 1 attachment in this new temporary directory even if you have 2 or more (therefore there is a bug on the save too). 5. close email. 6. Create a new email. 7. Select attach (to attach a file) 8. Change to the temporary directory holding your previously saved attachments. 9. You may see only 1 attachment in this directory even if there are more present (there is a bug here with the save/open dialogue box). -- 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 211900] kmail attachments not sync with directory contents
https://bugs.kde.org/show_bug.cgi?id=211900 --- Comment #1 from Jose Da Silva 2009-10-26 08:06:32 --- Created an attachment (id=37840) --> (http://bugs.kde.org/attachment.cgi?id=37840) picture.png (while opening to attach) Took a snapshot of a temporary directory currently holding several files. there are also 4 additional files in this temporary folder 001.jpg, 002.jpg, 003.jpg and 004.jpg. Even though the files do not show in the open/save dialogue box (therefore you cannot use the mouse to attach the file), I was able to highlight them by typing a 0 in the Name box and therefore attaching them in that manner. This is definitely a broken feature that needs fixing. -- 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 180741] crash in kmail (typeinfo name for, KMReaderWin::parseMsg)
https://bugs.kde.org/show_bug.cgi?id=180741 --- Comment #52 from Jose Da Silva 2009-11-11 22:37:11 --- Hi Dario, Read comment#41 and comment#43. Does it crash if you have the preview window open? Does it crash if you have the preview window closed? For myself, I was able to narrow my problem down to the preview pane causing the problem. If it crashes for you regardless of preview pane, you maybe might have a different bug. I'm guessing there are probably 3 different bugs lumped-into this particular bug based on activity that caused crashes. does anyone know what was the clues that suggested all these bugs are related? -- 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
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 Jose Da Silva changed: What|Removed |Added CC||digi...@joescat.com --- Comment #20 from Jose Da Silva --- Created attachment 134223 --> https://bugs.kde.org/attachment.cgi?id=134223&action=edit Blacked-out rectangles in Kmail and systemsettings5 Recent problem seen (happened between 9/27 to 12/13 in Mageia8beta1 with latest updates). This problem does not appear to be Wayland related since it also shows up in XFCE and LDXE too. Reported as bug https://bugs.mageia.org/show_bug.cgi?id=27884 Problem appears same also on systemsettings5 - attachment added. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 430673] New: Kmail no se conecta con los servicios de YaHoo
https://bugs.kde.org/show_bug.cgi?id=430673 Bug ID: 430673 Summary: Kmail no se conecta con los servicios de YaHoo Product: kmail2 Version: 5.15.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jac...@yahoo.es Target Milestone: --- SUMMARY Kmail no se conecta con los servicios se YaHoo mail STEPS TO REPRODUCE 1. Use las configuraciones automaticas 2. Use las configuraciones manuales 3. OBSERVED RESULT Siempre igual no se conecta con el servidor, indica que no puede autenticaser y que el servidior a cerrado la conexion SLL/TTL EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuSe Tumbleweed (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Las cuentas de Gmail y de Outlook funcionan bien -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 --- Comment #24 from Jose Da Silva --- Problem appears resolved - unable to reproduce it now (32bit) Kmail 5.16.0 (20.12.0) KDE Framework 5.76.0 QT 5.15.2 (was 5.15.1 earlier) xcb windowing system Appears to be Working now on KDE-plasma, XFCE, LXDE - Mageia8beta1-cauldron -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 377223] Kaddressbook crash when deleting tag "" (version 5.4.2)
https://bugs.kde.org/show_bug.cgi?id=377223 --- Comment #3 from Jose Da Silva --- Hi Justin, The problem is still there. I have created a test.vcf you can import and test for yourself. Trying to understand this problem further, it apparently is based on CATEGORIES which is something that worked a long time ago. Looking at my Mageia1 which is pretty old as it is, I apparently imported CATEGORIES from an older install, maybe when I had contacts on a kde3 version. Seems kde4 and kde5 lost the art on how to work with CATEGORIES. Starting with a new user, and empty addressbook. Start kaddressbook 1 start kaddressbook 2 menu->File->New->addressbook 3 choose "Personal Contacts" (to create a new addressbook) [OK] 4 /home/[user]/.local/share/contacts/ then [OK] (apparently default save here) At this point there is a new/empty Personal addressbook. 5 menu->File->Import->ImportVcard 6 choose test.vcf, and put it in "Personal Contacts" [OK] You will need to exit kaddressbook and then re-run kaddressbook to see the three new contact additions in the name column. You will not see "Categories", but they exist. 7. Search for Friend, and you see two contacts. 8. Search for Business and you see one contact. 9. Search for Work, and you see two contacts. Here is some confusion between old Kaddressbook and new Kaddressbook On the old 4.4.11 (Mageia1) also shows "", therefore this bug is older than kde4, and maybe going further back to kde3. kde4 has a separate temp file from the vcard file - maybe this is how it managed to hold CATEGORIES which are not in the current vcards. 2021jan03old4411.jpg shows a picture of "CATEGORIES" which has the confusing term of "Tags" in the recent Kaddressbook (I think this might be maybe seen as "Groups" on an Android phone if I imported this vcf file into a phone) and might be seen also on other addressbooks - but I'm only guessing now. If looking at the latest "Tags" and clicking on button [...] you will see tags that are blank. Version 5.16.0 (20.07.90) 10. If you look at the red "x" on "Select Tags" pop-up window and choose to delete an entry, kaddress will crash. You'll notice all the Tags show up as "". Hopefully this will help you verify and debug the problem. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 377223] Kaddressbook crash when deleting tag "" (version 5.4.2)
https://bugs.kde.org/show_bug.cgi?id=377223 --- Comment #4 from Jose Da Silva --- Created attachment 134497 --> https://bugs.kde.org/attachment.cgi?id=134497&action=edit three virtual contacts for a new personal address book 3 contacts named, Don'T Ask, Guess Who, and New BFF in file test.vcf This file contains CATEGORIES (something that I probably imported from kde3 and seems to be lost now (can't seem to add them, import, export these), but they are useful, to group people into various groups. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 377223] Kaddressbook crash when deleting tag "" (version 5.4.2)
https://bugs.kde.org/show_bug.cgi?id=377223 --- Comment #5 from Jose Da Silva --- Created attachment 134498 --> https://bugs.kde.org/attachment.cgi?id=134498&action=edit kde4 (mageia1) example of "Categories" - which now appear to be called TAGS -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 377223] Kaddressbook crash when deleting tag "" (version 5.4.2)
https://bugs.kde.org/show_bug.cgi?id=377223 --- Comment #6 from Jose Da Silva --- Created attachment 134499 --> https://bugs.kde.org/attachment.cgi?id=134499&action=edit kde5 (mageia8beta) with blank TAGS, that crash if you try to delete any -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 377223] Kaddressbook crash when deleting tag "" (version 5.4.2)
https://bugs.kde.org/show_bug.cgi?id=377223 Jose Da Silva changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Jose Da Silva --- KaddressBook version 5.16.0 (20.07.90) Mageia8beta with latest updates. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 415222] Kaddressbook no tags in exported vcard
https://bugs.kde.org/show_bug.cgi?id=415222 Jose Da Silva changed: What|Removed |Added CC||digi...@joescat.com --- Comment #3 from Jose Da Silva --- Looking forward to hopefully see CATEGORIES exported in VCARD or some other manner, otherwise it would be difficult to backup anything useful. I've added a small vcard sample in bug#377223 if that helps anything here for testing. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Jose María Galdós changed: What|Removed |Added CC||txemafi...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 426547] New: mga8beta1 - kmail2 - org.kde.pim.webengineviewer: WebEngine render process crashed (32bit)
https://bugs.kde.org/show_bug.cgi?id=426547
Bug ID: 426547
Summary: mga8beta1 - kmail2 - org.kde.pim.webengineviewer:
WebEngine render process crashed (32bit)
Product: kmail2
Version: 5.15.0
Platform: Mageia RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: UI
Assignee: kdepim-bugs@kde.org
Reporter: digi...@joescat.com
Target Milestone: ---
SUMMARY
Requested to bring bug upstream to KDE. Details here:
https://bugs.mageia.org/show_bug.cgi?id=27273
Maintainer indicates this bug was fixed for 64bit, however, this but continues
to have problems at 32bit.
Main reason for starting bug report was due to crash message:
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf
failure in syscall 0403
STEPS TO REPRODUCE
1. Lacking a working wizard import, I cloned a folder from an earlier kmail,
for example: .local/share/local-mail/inbox-2019/{cur/ new/ tmp/}, which shows
up in kmail2 as inbox-2019
2. Open a terminal so you can read any stdout or stderr messages.
3. type kmail in terminal to start kmail.
4. select added folder inbox-2019, to view email in this new folder.
(note default inbox and send boxes are still empty. kmail user account(s) has
not been added yet).
5. moving the mouse over the email list appears functionable, but moving the
mouse over the email viewing panel brings out repeated crash message:
org.kde.pim.webengineviewer: WebEngine render process crashed
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf
failure in syscall 0403
6. This might be related, or not, but at this point, kmail2 steals focus from
other programs, so for example, while typing the error report in FireFox, kmail
kept jumping into focus, and also taking whatever was typed as belonging to
kmail.
7. Ran kmail2 as default akonadi/mysql, but also running as akonadi/sqlite had
no change.
OBSERVED RESULT
Moving mouse over email view panel started UI bad behaviour. This can be seen
if you open a terminal, and start kmail from a terminal - repeated crash report
and other bad behaviour. Have to exit kmail to be able to use other programs.
EXPECTED RESULT
To be able to read additional folders like inbox-2019, inbox-2018, inbox-2017
... without crash reports.
To be able to run other programs like kwrite or firefox without having kmail
stealing focus.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
mageia8 beta1
KDE Plasma Version: 5.15.0
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Maintainer recommended one other of the reported error messages can probably
deserve a new bug report. See here (comment3):
https://bugs.mageia.org/show_bug.cgi?id=27273
If you think it should be reported as another bug, we can start another bug
report.
--
You are receiving this mail because:
You are the assignee for the bug.
[kaddressbook] [Bug 377223] New: Kaddressbook crash when deleting tag "" (version 5.4.2)
https://bugs.kde.org/show_bug.cgi?id=377223 Bug ID: 377223 Summary: Kaddressbook crash when deleting tag "" (version 5.4.2) Product: kaddressbook Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: digi...@joescat.com CC: to...@kde.org Target Milestone: --- Application: kaddressbook (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.9.12-200.fc25.i686 i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Recently updated several Addresses, and then I was going to use tags to group contacts according to various activities. I was puzzled why the first three tags are "", and therefore decided to delete them and create new tags, like soccer, skiing, computing. I selected trashcan to delete tag 1, and the pop-up question 'Do you really want to remove the tag ""?' appeared. Kaddressbook crashed when clicking 'delete' to remove tag1. Problem is repeatable for any of the 3 "" tags. -- Backtrace: Application: KAddressBook (kaddressbook), signal: Aborted Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xaaa13840 (LWP 11848))] Thread 25 (Thread 0x9c1fdb40 (LWP 12350)): #0 0xb776bcd9 in __kernel_vsyscall () #1 0xb4beee9c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb12682fc in base::ConditionVariable::Wait() () from /lib/libQt5WebEngineCore.so.5 #3 0xb12745f6 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib/libQt5WebEngineCore.so.5 #4 0xb1274a60 in base::SequencedWorkerPool::Worker::Run() () from /lib/libQt5WebEngineCore.so.5 #5 0xb1274c5d in base::SimpleThread::ThreadMain() () from /lib/libQt5WebEngineCore.so.5 #6 0xb12710ee in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/libQt5WebEngineCore.so.5 #7 0xb4be94ee in start_thread () from /lib/libpthread.so.0 #8 0xb516002e in clone () from /lib/libc.so.6 Thread 24 (Thread 0x9b9fcb40 (LWP 12349)): #0 0xb776bcd9 in __kernel_vsyscall () #1 0xb4beee9c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb12682fc in base::ConditionVariable::Wait() () from /lib/libQt5WebEngineCore.so.5 #3 0xb12745f6 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib/libQt5WebEngineCore.so.5 #4 0xb1274a60 in base::SequencedWorkerPool::Worker::Run() () from /lib/libQt5WebEngineCore.so.5 #5 0xb1274c5d in base::SimpleThread::ThreadMain() () from /lib/libQt5WebEngineCore.so.5 #6 0xb12710ee in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/libQt5WebEngineCore.so.5 #7 0xb4be94ee in start_thread () from /lib/libpthread.so.0 #8 0xb516002e in clone () from /lib/libc.so.6 Thread 23 (Thread 0x849eeb40 (LWP 12027)): #0 0xb776bcd9 in __kernel_vsyscall () #1 0xb4beee9c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb12682fc in base::ConditionVariable::Wait() () from /lib/libQt5WebEngineCore.so.5 #3 0xb12745f6 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () from /lib/libQt5WebEngineCore.so.5 #4 0xb1274a60 in base::SequencedWorkerPool::Worker::Run() () from /lib/libQt5WebEngineCore.so.5 #5 0xb1274c5d in base::SimpleThread::ThreadMain() () from /lib/libQt5WebEngineCore.so.5 #6 0xb12710ee in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/libQt5WebEngineCore.so.5 #7 0xb4be94ee in start_thread () from /lib/libpthread.so.0 #8 0xb516002e in clone () from /lib/libc.so.6 Thread 22 (Thread 0x851efb40 (LWP 12026)): #0 0xb776bcd9 in __kernel_vsyscall () #1 0xb516dd32 in __lll_lock_wait_private () from /lib/libc.so.6 #2 0xb516f701 in __fprintf_chk () from /lib/libc.so.6 #3 0xabc4ae94 in _warn_helper () from /lib/libevent-2.0.so.5 #4 0xabc4afb7 in event_warn () from /lib/libevent-2.0.so.5 #5 0xabc4ff4c in epoll_dispatch () from /lib/libevent-2.0.so.5 #6 0xabc3740f in event_base_loop () from /lib/libevent-2.0.so.5 #7 0xb121cc0b in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /lib/libQt5WebEngineCore.so.5 #8 0xb124492a in base::MessageLoop::RunHandler() () from /lib/libQt5WebEngineCore.so.5 #9 0xb125b76f in base::RunLoop::Run() () from /lib/libQt5WebEngineCore.so.5 #10 0xb1244302 in base::MessageLoop::Run() () from /lib/libQt5WebEngineCore.so.5 #11 0xb127529b in base::Thread::ThreadMain() () from /lib/libQt5WebEngineCore.so.5 #12 0xb12710ee in base::(anonymous namespace)::ThreadFunc(void*) () from /lib/libQt5WebEngineCore.so.5 #13 0xb4be94ee in start_thread () from /lib/libpthread.so.0 #14 0xb516002e in clone () from /lib/libc.so.6 Thread 21 (Thread 0x859f0b40 (LWP 12025)): #0 0xb776bcd9 in
[kmail2] [Bug 312460] Kmail can not show correct number of unread mails
https://bugs.kde.org/show_bug.cgi?id=312460 Jose Orlando Pereira changed: What|Removed |Added CC||j...@di.uminho.pt --- Comment #43 from Jose Orlando Pereira --- (In reply to comment #41) > Created attachment 81027 [details] > Correct fix. > > Correct fix is point 2. This causes an additional problem for me, at least with the MySQL backend and with akonadi-1.10.2: Unread count in the folder list does not reflect actual number of unread messages, but instead shows the total number of messages in the folder. BTW, there is also a similar query (i.e. itemWithFlagCount on SEEN) in ./server/src/handlerhelper.cpp that the patch does not change. Should 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 234905] New: saving vcards importing vcards
https://bugs.kde.org/show_bug.cgi?id=234905 Summary: saving vcards importing vcards Product: kaddressbook Version: unspecified Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: hinc...@dem.inpe.br CC: to...@kde.org Version: 4.4.2 (using 4.4.2 (KDE 4.4.2) "release 241", KDE:KDE4:Factory:Desktop / openSUSE_11.2) Compiler: gcc OS:Linux (x86_64) release 2.6.31.12-0.2-desktop upgraded from kde 3.3.5 to 4.4.2 all contacts from addressbook were lost. As I tried to import the cards from from /.kde4/share/... /kabc I get a window asking for a the "address book the imported contact will be saved to". But don't give me any options nor allows to type in. -- 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 234905] saving vcards importing vcards
https://bugs.kde.org/show_bug.cgi?id=234905 --- Comment #1 from Jose N Hinckel 2010-04-20 19:05:45 --- Same behavior when trying to add/save a new contact. -- 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 180741] crash in kmail (typeinfo name for, KMReaderWin::parseMsg)
https://bugs.kde.org/show_bug.cgi?id=180741 Jose Da Silva changed: What|Removed |Added CC|digi...@joescat.com | -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 264861] Google calendar and contacts don't work
https://bugs.kde.org/show_bug.cgi?id=264861 Jose Luis Bolos changed: What|Removed |Added CC||joseluisbo...@gmail.com --- Comment #10 from Jose Luis Bolos 2011-02-25 17:45:24 --- I've been trying to get this working since months ago, with several versions of several distros, and always give up due to this bug. Never got it to work. Right now I'm un Kubuntu 10.10 with the same versions than #6: ii akonadi-kde-resource-googledata 1.2.0-0ubuntu1 ii akonadi-server 1.4.90-0ubuntu1~maverick1~ppa1 ii kontact 4:4.4.9-0ubuntu1~maverick2~ppa1 ii korganizer 4:4.4.9-0ubuntu1~maverick2~ppa1 ii libgcal0 0.9.6-0ubuntu1 -- 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 264861] Google calendar and contacts don't work
https://bugs.kde.org/show_bug.cgi?id=264861 --- Comment #11 from Jose Luis Bolos 2011-02-27 03:38:30 --- Created an attachment (id=57544) --> (http://bugs.kde.org/attachment.cgi?id=57544) C program using the libgcal library that works OK I've tested this code (from the libgcal page) and, when executed, shows me a list of all my contacts in about 6 seconds. kaddressbook, e.g., hangs forever trying to load the contacts. So I'm pretty confident the problem is in akonadi-googledata or in akonadi itself. -- 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 264861] Google calendar and contacts don't work
https://bugs.kde.org/show_bug.cgi?id=264861 Jose Luis Bolos changed: What|Removed |Added Attachment #57544|C program using the libgcal |C sample using the libgcal description|library that works OK |library that shows the ||contacts OK -- 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 276620] Mark EMail Actions spikes Virtuoso CPU usage
https://bugs.kde.org/show_bug.cgi?id=276620 Jose M. Prieto changed: What|Removed |Added CC||jmpri...@gmx.net -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 264861] Google calendar and contacts don't work
https://bugs.kde.org/show_bug.cgi?id=264861 --- Comment #45 from Jose Luis Bolos 2011-08-30 22:20:25 --- I've also find this libkgoogle: http://progdan.cz/2011/08/akonadi-google-resource-complete-rewrite/ although the author itself says it's still a long way from being completely finished. -- 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 174403] New: Kontact crash with SIGSEGV at startup
http://bugs.kde.org/show_bug.cgi?id=174403 Summary: Kontact crash with SIGSEGV at startup Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version: 4.1.2 (using KDE 4.1.2) OS:Linux Installed from:Ubuntu Packages After upgrade to Kubuntu 8.10 kontact crashes at start: Aplicación: Kontact (kontact), señal SIGSEGV (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb4e0b6c0 (LWP 5436)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no de
[kmail2] [Bug 331824] New: When replying a mail, the signature (image) replaces all previous images
https://bugs.kde.org/show_bug.cgi?id=331824 Bug ID: 331824 Summary: When replying a mail, the signature (image) replaces all previous images Classification: Unclassified Product: kmail2 Version: 4.11.5 Platform: Fedora RPMs URL: https://app.box.com/s/kzz433dvxlcajng5dxiq OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: josei.deleoncor...@openmailbox.org Sorry for my bad english In my job I have to simulate the outlook style so I configure de reply template as shown in the "Steps to Reproduce" In the config dialog I check automatically insert signature, insert signature above quoted text, prepend separator to signature and reply or forward using HTML if present. I do this to reply above the previous messages. I configure my signature as a HTML image and when I reply a mail, my signature replaces all the images in the previous messages. To fix it I cut the image in half and configure my signature with two images, one above the other. With this all previos images are preserved Reproducible: Always Steps to Reproduce: 1.Configure the composer as follows: check "automatically insert signature", "insert signature above quoted text", "prepend separator to signature" and "reply or forward using HTML if present" 2.Configure the signature as a image 3.Configure the reply template as follows: %FORCEDHTML %CURSOR ---De: %OFROMADDR Enviado el: %ODATE %OTIME Para: %OTOADDR CC: %OADDRESSEESADDR Asunto: %OFULLSUBJECT %TEXT 4. Reply an HTML mail with images Actual Results: You will see your signature replacing all the previos images, images sent by other people like their signature. Expected Results: Not replace the images with the signature image. In the URL field I share a file where you can see what is happening, these HTML files were saved with the composer, Message, save as File menu option. Thanks a lot :) -- 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 331824] When replying a mail, the signature (image) replaces all previous images
https://bugs.kde.org/show_bug.cgi?id=331824 Jose de Leon Cordon changed: What|Removed |Added CC||josei.deleoncordon@openmail ||box.org -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 223236] kmail cannot connect to LDAP over SSL
https://bugs.kde.org/show_bug.cgi?id=223236 --- Comment #7 from Jose Arthur Benetasso Villanova 2011-05-09 00:36:27 --- I've fixed my problem. I did a: echo "TLS_REQCERT never" > ~/.ldaprc and now it's working. -- 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 286307] Kmail crash
https://bugs.kde.org/show_bug.cgi?id=286307 Jose Arthur Benetasso Villanova changed: What|Removed |Added CC|jose.art...@gmail.com | -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 287486] New: Kontact crashes while opening an email
https://bugs.kde.org/show_bug.cgi?id=287486 Summary: Kontact crashes while opening an email Product: kontact Version: unspecified Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: jose.art...@gmail.com Application: kontact (4.7.3) KDE Platform Version: 4.7.3 (4.7.3) Qt Version: 4.8.0 Operating System: Linux 3.1.1-2.fc16.x86_64 x86_64 Distribution: "Fedora release 16 (Verne)" -- Information about the crash: - What I was doing when the application crashed: Opening a specific email. All other emails works. My machine is up-to-date. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f69389b7840 (LWP 2704))] Thread 4 (Thread 0x7f692d519700 (LWP 2705)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x00349d1973cc in WTF::TCMalloc_PageHeap::scavengerThread (this=0x349db90f80) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x00349d1974f9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x003479807d90 in start_thread (arg=0x7f692d519700) at pthread_create.c:309 #4 0x003478ceed8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f692cc18700 (LWP 2706)): #0 0x003479809dd5 in __pthread_mutex_lock (mutex=0x7f69240009a8) at pthread_mutex_lock.c:65 #1 0x00347c044f4f in g_main_context_poll (n_fds=1, fds=0x7f69240013e0, priority=, timeout=7587, context=0x7f69240009a0) at gmain.c:3381 #2 g_main_context_iterate (context=0x7f69240009a0, block=, dispatch=1, self=) at gmain.c:3068 #3 0x00347c04544c in g_main_context_iteration (context=0x7f69240009a0, may_block=1) at gmain.c:3136 #4 0x0034835a6896 in QEventDispatcherGlib::processEvents (this=0x7f69240008c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003483576c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x003483576ed7 in QEventLoop::exec (this=0x7f692cc17d40, flags=...) at kernel/qeventloop.cpp:204 #7 0x003483478ad7 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x00348347bb1b in QThreadPrivate::start (arg=0x23d1d10) at thread/qthread_unix.cpp:298 #9 0x003479807d90 in start_thread (arg=0x7f692cc18700) at pthread_create.c:309 #10 0x003478ceed8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f68e0154700 (LWP 2760)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x00348347c02b in wait (time=18446744073709551615, this=0x7f68d80074c0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=, mutex=0x7f68d8005c90, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x003483477e44 in QSemaphore::acquire (this=0x7f68e0152cc0, n=1) at thread/qsemaphore.cpp:144 #4 0x00348358bcb5 in QMetaObject::activate (sender=0x4acf100, m=, local_signal_index=, argv=0x7f68e0152d30) at kernel/qobject.cpp:3524 #5 0x0034852f59c4 in QHttpThreadDelegate::authenticationRequired (this=, _t1=, _t2=0x7f68d8002748) at .moc/release-shared/moc_qhttpthreaddelegate_p.cpp:178 #6 0x0034852f5f08 in QHttpThreadDelegate::qt_static_metacall (_o=0x4acf100, _c=, _id=, _a=) at .moc/release-shared/moc_qhttpthreaddelegate_p.cpp:104 #7 0x00348358b7d1 in QMetaObject::activate (sender=0x7f68d8005940, m=, local_signal_index=, argv=0x7f68e0152f60) at kernel/qobject.cpp:3546 #8 0x0034852f46f7 in QHttpNetworkReply::authenticationRequired (this=, _t1=, _t2=0x7f68d8002748) at .moc/release-shared/moc_qhttpnetworkreply_p.cpp:192 #9 0x0034852558d7 in QHttpNetworkConnectionPrivate::handleAuthenticateChallenge (this=0x7f68d8002600, socket=0x7f68d8002390, reply=0x7f68d8005940, isProxy=false, resend=@0x7f68e01531ef) at access/qhttpnetworkconnection.cpp:378 #10 0x00348525bb44 in QHttpNetworkConnectionChannel::handleStatus (this=0x7f68d80026e8) at access/qhttpnetworkconnectionchannel.cpp:824 #11 0x00348525c2ba in QHttpNetworkConnectionChannel::allDone (this=0x7f68d80026e8) at access/qhttpnetworkconnectionchannel.cpp:700 #12 0x00348525cdcb in QHttpNetworkConnectionChannel::_q_receiveReply (this=0x7f68d80026e8) at access/qhttpnetworkconnectionchannel.cpp:505 #13 0x00348525d8b2 in QHttpNetworkConnectionChannel::_q_readyRead (this=0x7f68d80026e8) at access/qhttpnetworkconnectionchannel.cpp:968 #14 0x00348358b7d1 in QMetaObject::activate (sender=0x7f68d8002390, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3546 #15 0x0034852cc8bf in Q
[Bug 223236] kmail cannot connect to LDAP over SSL
https://bugs.kde.org/show_bug.cgi?id=223236 Jose Arthur Benetasso Villanova changed: What|Removed |Added CC||jose.art...@gmail.com --- Comment #6 from Jose Arthur Benetasso Villanova 2011-01-16 03:31:57 --- Hi. I filled this one some time ago: https://bugzilla.redhat.com/show_bug.cgi?id=663210 Its the same 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
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 jose bernardo silva changed: What|Removed |Added CC|josebernar...@yahoo.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
[kaddressbook] [Bug 223236] kmail cannot connect to LDAP over SSL
https://bugs.kde.org/show_bug.cgi?id=223236 --- Comment #11 from Jose Arthur Benetasso Villanova --- I dont use kmail anymore, but I remember that I could solve this problem with a dot file. I think that it was .ldaprc with "TLS_REQCERT never" inside it. -- You are receiving this mail because: You are the assignee for the bug.
