[kontact] [Bug 415634] kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #59 from Andras --- (In reply to Kishore Gopalakrishnan from comment #58) Oh my I just didn't noticed this cuz so obvious I'd love to use Google's supervision for login lol. Anyways thanks it works for me. Probably I've to use this option for now hm. Also correction, I meant it's not possible to turn on less secure app when there is 2 step verification is used and in this case Google gives the option for app password what should work for less secure apps too, well it doesn't work either. I used my accounts in Kontact with app pw for years and now I had to reconfigure Akonandi for whatever misbehaving after some upgrade and this message just started appearing for all of my setup. Anyways, I hope it'll be solved somehow soon. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #57 from Andras --- What plain authentication you guys are talking about? It's only for outgoing setup, incoming has to be configured in a way it's asked by Google anyway and basically that's where this problem is happening at least for me. I have a bunch, around 10 account setup in the right way in Kontact, I have 2 step auth.. so there is no option to set less secure app in Google account but in that case it won't be necessary in theory. It doesn't work for me either, same message appears for all of my account so I just wait. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kdelibs] [Bug 210416] opens all http://... links with kwrite
https://bugs.kde.org/show_bug.cgi?id=210416 --- Comment #8 from Andras Georgy Bekes --- As the ticket mentions, this happened when I upgraded from KDE 3 to 4. Even if the bug still exists, I doubt it is worth spending any time with it. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 396694] New: Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 Bug ID: 396694 Summary: Kontact crashes right after start Product: kontact Version: 5.8.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: andrasszerencs...@gmail.com Target Milestone: --- Application: kontact (5.8.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: On KDE Neon, Plasma desktop was upgraded from 5.12 to 5.13 and I restarted the system. Simple tried to start Kontact application and it's every time crashes. The crash can be reproduced every time. -- 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 0x7f310b224940 (LWP 6854))] Thread 2 (Thread 0x7f30dcc4b700 (LWP 6857)): #0 0x7f3107c0474d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f310196738c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f30d8003020, timeout=, context=0x7f30d8000990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f30d8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f310196749c in g_main_context_iteration (context=0x7f30d8000990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f31087320bb in QEventDispatcherGlib::processEvents (this=0x7f30d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f31086d95ba in QEventLoop::exec (this=this@entry=0x7f30dcc4ac40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f310850e5e4 in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7f3106e77f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f3108519727 in QThreadPrivate::start (arg=0x7f31070f0d60) at thread/qthread_unix.cpp:367 #9 0x7f310395e6ba in start_thread (arg=0x7f30dcc4b700) at pthread_create.c:333 #10 0x7f3107c1041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f310b224940 (LWP 6854)): [KCrash Handler] #6 0x7f310acb2c20 in KontactInterface::PimUniqueApplication::staticMetaObject () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #7 0x7f310aaadd3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x0040437b in main (argc=1, argv=0x7ffe00e3f848) at /workspace/build/src/main.cpp:216 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 --- Comment #17 from Andras --- (In reply to michele mazza from comment #16) > This can be worked around by installing and using different header themes. > View -> Headers -> Download New Themes > I'm using Obsidian headers. > They are not applied to new mails you write though. Thank you for your help however against reluctance I have to note it is NOT the solution. This issue should have been solved long ago. Also, only Obsidian suits for this work around. KDE application won't work in KDE environment out of the box for such a long time? It's nothing else but shame! Resilient CSS please. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 --- Comment #14 from Andras --- Same here, It's really messed up with dark themes like breeze-dark. Dark text on dark background and white on white, etc. I also had theme issue with Thunderbird and Firefox but it's easy to fix with their own dark themes and "apply colors to non-qt app" unchecked or with css configuration. I think KMail should work out of the box with all KDE Plasma settings as a QT application. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 317803] Kmail2 renders colors based on the user system colors rather than the default colors browsers use.
https://bugs.kde.org/show_bug.cgi?id=317803 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362608] Default colours unusable on dark theme
https://bugs.kde.org/show_bug.cgi?id=362608 --- Comment #15 from Andras --- Same here, some html texts are bright on bright background in Kmail. Debian Stretch, Plasma desktop, Kmail Version 5.2.3, KDE Frameworks 5.28.0, Qt 5.7.1 (built against 5.7.1). I'm glad I found this thread. After a lot attempt to fix it, it's just very frustrating to realize that nothing will be solve this problem but redevelop Kmail. I mean that's absolutely true that the themes, color schemes or any other visual settings by desktop environments has nothing to do with this problem. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 362608] Default colours unusable on dark theme
https://bugs.kde.org/show_bug.cgi?id=362608 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com --- Comment #14 from Andras --- Created attachment 107517 --> https://bugs.kde.org/attachment.cgi?id=107517&action=edit Kmail html messages texts bright on bright background. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 210416] opens all http://... links with kwrite
https://bugs.kde.org/show_bug.cgi?id=210416 --- Comment #4 from Andras Georgy Bekes 2010-03-08 14:02:23 --- > Does the same happen for you with links you click in > konqueror? I've solved the problem by removing the extra kwrite entries from all the file associations. I can't remember if it happened in konqueror as well, but again: the root cause was the infection of file associations by kwrite. So the problem is basically solved, the question is how my file associations get into that bogus state. -- 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 77862] kio_imap processes hang when connection status changes
https://bugs.kde.org/show_bug.cgi?id=77862 --- Comment #56 from Andras Georgy Bekes 2010-03-01 12:05:20 --- > It is a shame that is has become a routine for me to close and start kmail > again every time my laptop comes out from 'suspend to ram' My suspend script closes kmail before suspending and starts it thereafter. Georgy -- 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 212885] crash when deleting (move to trash) in IMAP folder
https://bugs.kde.org/show_bug.cgi?id=212885 --- Comment #1 from Andras Georgy Bekes 2009-11-03 11:06:39 --- New info, after having restarted KMail: The mail that I was deleting has been copied to the trash folder, while it has not been deleted from its original folder. The next mail in the folder was shown by KMail without any problem. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 212885] New: crash when deleting (move to trash) in IMAP folder
https://bugs.kde.org/show_bug.cgi?id=212885 Summary: crash when deleting (move to trash) in IMAP folder Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bek...@sch.bme.hu Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.30-1-686-bigmem i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: I do not know whether the crash was caused by deleting the mail (moving to trash folder on the same IMAP account) or showing the next one in the folder. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb123a741 in KMFolderImap::take (this=0x91ff238, idx=-1) at ../../kmail/kmfolderimap.cpp:596 #7 0xb117e0e4 in FolderStorage::takeMessages (this=0x91ff238, msgList=...) at ../../kmail/folderstorage.cpp:474 #8 0xb114b4ce in KMFolder::takeMessages (this=0x91fb750, msgList=...) at ../../kmail/kmfolder.cpp:432 #9 0xb123861d in KMFolderImap::addMsgQuiet (this=0x931bbf0, msgList=...) at ../../kmail/kmfolderimap.cpp:381 #10 0xb123e782 in KMFolderImap::qt_metacall (this=0x931bbf0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbf99f4cc) at ./kmfolderimap.moc:156 #11 0xb7709303 in QMetaObject::activate (sender=0xa78b760, from_signal_index=7, to_signal_index=7, argv=0xbf99f4cc) at kernel/qobject.cpp:3112 #12 0xb7709f42 in QMetaObject::activate (sender=0xa78b760, m=0xb17514d0, local_signal_index=3, argv=0xbf99f4cc) at kernel/qobject.cpp:3186 #13 0xb13825a3 in KMail::FolderJob::messageCopied (this=0xa78b760, _t1=...) at ./folderjob.moc:120 #14 0xb1391f84 in KMail::ImapJob::slotCopyMessageResult (this=0xa78b760, job=0xb9346f0) at ../../kmail/imapjob.cpp:655 #15 0xb1393404 in KMail::ImapJob::qt_metacall (this=0xa78b760, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf99f65c) at ./imapjob.moc:88 #16 0xb7709303 in QMetaObject::activate (sender=0xb9346f0, from_signal_index=7, to_signal_index=7, argv=0xbf99f65c) at kernel/qobject.cpp:3112 #17 0xb7709f42 in QMetaObject::activate (sender=0xb9346f0, m=0xb7a1dc28, local_signal_index=3, argv=0xbf99f65c) at kernel/qobject.cpp:3186 #18 0xb78c04d3 in KJob::result (this=0xb9346f0, _t1=0xb9346f0) at ./kjob.moc:188 #19 0xb78c0979 in KJob::emitResult (this=0xb9346f0) at ../../kdecore/jobs/kjob.cpp:304 #20 0xb6119bd5 in KIO::SimpleJob::slotFinished (this=0xb9346f0) at ../../kio/kio/job.cpp:477 #21 0xb6116863 in KIO::SimpleJob::qt_metacall (this=0xb9346f0, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbf99f7b8) at ./jobclasses.moc:159 #22 0xb7709303 in QMetaObject::activate (sender=0x9c03088, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112 #23 0xb7709f42 in QMetaObject::activate (sender=0x9c03088, m=0xb62c1ba4, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186 #24 0xb61df7d7 in KIO::SlaveInterface::finished (this=0x9c03088) at ./slaveinterface.moc:165 #25 0xb61e3587 in KIO::SlaveInterface::dispatch (this=0x9c03088, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #26 0xb61dfcb7 in KIO::SlaveInterface::dispatch (this=0x9c03088) at ../../kio/kio/slaveinterface.cpp:91 #27 0xb61d1c9d in KIO::Slave::gotInput (this=0x9c03088) at ../../kio/kio/slave.cpp:322 #28 0xb61d4183 in KIO::Slave::qt_metacall (this=0x9c03088, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf99fa88) at ./slave.moc:76 #29 0xb7709303 in QMetaObject::activate (sender=0x9bff8e8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #30 0xb7709f42 in QMetaObject::activate (sender=0x9bff8e8, m=0xb62be4e0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #31 0xb60ddd57 in KIO::Connection::readyRead (this=0x9bff8e8) at ./connection.moc:86 #32 0xb60df663 in KIO::ConnectionPrivate::dequeue (this=0x9c00928) at ../../kio/kio/connection.cpp:82 #33 0xb60dfa46 in KIO::Connection::qt_metacall (this=0x9bff8e8, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xcc89cf0) at ./connection.moc:73 #34 0xb7702b0b in QMetaCallEvent::placeMetaCall (this=0xbe30ca0, object=0x9bff8e8) at kernel/qobject.cpp:477 #35 0xb77045e0 in QObject::event (this=0x9bff8e8, e=0xbe30ca0) at kernel/qobject.cpp:1110 #36 0xb6d33a94 in QApplicationPrivate::notify_helper (this=0x8e43458, receiver=0x9bff8e8, e=0xbe30ca0) at kernel/qapplication.cpp:4065 #37 0xb6d3bbee in QApplication::notify (this=0xbf9a034c, receiver=0x9bff8e8, e=0xbe30ca0) at kernel/qapplication.cpp:3605 #38 0xb7bf60fd in KApplication::notify (this=0xbf9a034c, receiver=0x9bff8e8, event=0xbe30ca0) at ../../kdeui/kernel/kapplication.cpp:302 #39 0xb76f41eb in QCoreApplication::notifyInternal (this=0xbf9a034c, receiver=0x9bff8e8, event=0xbe30ca0) at kernel/qcoreapplication.cpp:610 #40 0xb76f4e2e in QCoreAp
[Bug 212062] New: address search in LDAP source crashes
https://bugs.kde.org/show_bug.cgi?id=212062 Summary: address search in LDAP source crashes Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bek...@sch.bme.hu Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.30-1-686-bigmem i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: Crash when composing mail. Mail body empty, subject empty, to, etc empty. When typing in the To: field, KMail crashes when the result of the search arrives and should be displayed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 QListWidgetItem::text (this=0xc06a370, adrs=...) at /usr/include/qt4/QtGui/qlistwidget.h:90 #7 KPIM::AddresseeLineEdit::slotLDAPSearchData (this=0xc06a370, adrs=...) at ../../libkdepim/addresseelineedit.cpp:820 #8 0xb7f2438a in KPIM::AddresseeLineEdit::qt_metacall (this=0xc06a370, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfe6348c) at ./addresseelineedit.moc:95 #9 0xb14ae38a in KMLineEdit::qt_metacall (this=0xc06a370, _c=QMetaObject::InvokeMetaMethod, _id=84, _a=0xbfe6348c) at ./kmlineeditspell.moc:68 #10 0xb1522f3a in RecipientLineEdit::qt_metacall (this=0xc06a370, _c=QMetaObject::InvokeMetaMethod, _id=84, _a=0xbfe6348c) at ./recipientseditor.moc:123 #11 0xb77f6b33 in QMetaObject::activate (sender=0xa78eb88, from_signal_index=5, to_signal_index=5, argv=0xbfe6348c) at kernel/qobject.cpp:3112 #12 0xb77f7782 in QMetaObject::activate (sender=0xa78eb88, m=0xb7fa8248, local_signal_index=1, argv=0xbfe6348c) at kernel/qobject.cpp:3186 #13 0xb7f27613 in KPIM::LdapSearch::searchData (this=0xa78eb88, _t1=...) at ./ldapclient.moc:205 #14 0xb7f2b3af in KPIM::LdapSearch::slotDataTimer (this=0xa78eb88) at ../../libkdepim/ldapclient.cpp:465 #15 0xb7f2b43d in KPIM::LdapSearch::finish (this=0xa78eb88) at ../../libkdepim/ldapclient.cpp:472 #16 0xb7f2b480 in KPIM::LdapSearch::slotLDAPDone (this=0xaf344f8) at ../../libkdepim/ldapclient.cpp:454 #17 0xb7f2e3c3 in KPIM::LdapSearch::qt_metacall (this=0xa78eb88, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfe635a8) at ./ldapclient.moc:184 #18 0xb77f6b33 in QMetaObject::activate (sender=0xa892948, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #19 0xb77f7782 in QMetaObject::activate (sender=0xa892948, m=0xb7fa8238, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #20 0xb7f27747 in KPIM::LdapClient::done (this=0xa892948) at ./ldapclient.moc:103 #21 0xb7f27eff in KPIM::LdapClient::slotDone (this=0xa892948) at ../../libkdepim/ldapclient.cpp:119 #22 0xb7f2b96b in KPIM::LdapClient::qt_metacall (this=0xa892948, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfe6372c) at ./ldapclient.moc:92 #23 0xb77f6b33 in QMetaObject::activate (sender=0xbd046c8, from_signal_index=7, to_signal_index=7, argv=0xbfe6372c) at kernel/qobject.cpp:3112 #24 0xb77f7782 in QMetaObject::activate (sender=0xbd046c8, m=0xb7b09b48, local_signal_index=3, argv=0xbfe6372c) at kernel/qobject.cpp:3186 #25 0xb79ad3d3 in KJob::result (this=0xbd046c8, _t1=0xbd046c8) at ./kjob.moc:188 #26 0xb79ad879 in KJob::emitResult (this=0xbd046c8) at ../../kdecore/jobs/kjob.cpp:304 #27 0xb62087b5 in KIO::SimpleJob::slotFinished (this=0xbd046c8) at ../../kio/kio/job.cpp:477 #28 0xb6209113 in KIO::TransferJob::slotFinished (this=0xbd046c8) at ../../kio/kio/job.cpp:948 #29 0xb62056a3 in KIO::TransferJob::qt_metacall (this=0xbd046c8, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfe63968) at ./jobclasses.moc:343 #30 0xb77f6b33 in QMetaObject::activate (sender=0xb672bb8, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112 #31 0xb77f7782 in QMetaObject::activate (sender=0xb672bb8, m=0xb63afb84, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186 #32 0xb62ce437 in KIO::SlaveInterface::finished (this=0xb672bb8) at ./slaveinterface.moc:165 #33 0xb62d21e7 in KIO::SlaveInterface::dispatch (this=0xb672bb8, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175 #34 0xb62ce917 in KIO::SlaveInterface::dispatch (this=0xb672bb8) at ../../kio/kio/slaveinterface.cpp:91 #35 0xb62c08fd in KIO::Slave::gotInput (this=0xb672bb8) at ../../kio/kio/slave.cpp:322 #36 0xb62c2de3 in KIO::Slave::qt_metacall (this=0xb672bb8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe63c38) at ./slave.moc:76 #37 0xb77f6b33 in QMetaObject::activate (sender=0xba626e0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #38 0xb77f7782 in QMetaObject::activate (sender=0xba626e0, m=0xb63ac4c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #39 0xb61cc937 in KIO::Connection::readyRead (this=0xba626e0) at ./connection.moc:86 #
[Bug 210416] opens all http://... links with kwrite
https://bugs.kde.org/show_bug.cgi?id=210416 --- Comment #2 from Andras Georgy Bekes 2009-10-13 13:14:46 --- Type associations for "General": text/html: Kwrite first, then konqueror, etc. Kwrite shows up two more times in the list! text/htmlh: Kwrite is the first, second and third in the list! application/xhtml+xml: Kwrite is not the first, but shows up 3 times in the list... application/pdf: Kwrite is the first (and no more Kwrites...) application/x-php: Kwrite, Kwrite, Kwrite... application/atom+xml: Kwrite first, then others, Kwrite two more times.. image/x-eps: Kwrite is not the first, but shows up 3 times in the list... The settings for "Embedded" seem normal. These are just examples... Kwrite has infested my associations 3 times... Where are these settings stored? Is it under the .kde directory? -- 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 161844] folder mis-sorted, messages not shown
https://bugs.kde.org/show_bug.cgi?id=161844 Andras Georgy Bekes changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #11 from Andras Georgy Bekes 2009-10-13 10:41:08 --- It seems the bug does not exist on KDE 4.3 (KMail 1.12.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 210416] New: opens all http://... links with kwrite
https://bugs.kde.org/show_bug.cgi?id=210416 Summary: opens all http://... links with kwrite Product: kmail Version: unspecified Platform: Debian testing OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: bek...@sch.bme.hu Version:(using KDE 4.3.1) Installed from:Debian testing/unstable Packages Whenever I click on a http://... link in KMail, the link is always opened in kwrite. I think it should be opened in konqueror or in some "default browser". The problem is present since I upgraded from KDE 3. Before the upgrade I deleted my .kde directory and did not (yet) change file associations at all. -- 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 197848] New: E-Mail link with many addresses
https://bugs.kde.org/show_bug.cgi?id=197848
Summary: E-Mail link with many addresses
Product: kmail
Version: 1.11.90
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: bib...@vignet.hu
Version: 1.11.90 (using 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)), Kubuntu
packages)
Compiler: cc
OS:Linux (x86_64) release 2.6.28-13-generic
Status: I got a mail, that was send to 30 (or more) other address as well
("To:").
All off the addresses are shown (that's ok), but on the end of the lines, the
last addresses aren't formatted as a link. So if I click on the last address in
the line, nothing happens (should pop up a window with new mail).
Exceptions: last 2 lines (in my case)
It's only happen, when an address is the last word in that line, some examples:
-Fail:
"...@bar.com"
-Correct:
"... Foo Bar \n
"
I guess, that the problem is the mail icon on right-up corner, but i'm mot
sure.
--
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 161844] folder mis-sorted, messages not shown
https://bugs.kde.org/show_bug.cgi?id=161844 --- Comment #9 from Andras Georgy Bekes 2009-04-06 11:42:18 --- I am still using KMail 1.9.9. and the problem still exists (I'm quitting KMail and deleting ~/.kde/share/apps/kmail/imap/.$WHEIRD_NUMBER.directory/.$FOLDERNAME.index.* several times a day). I will switch to KMail 1.9.10 or KDE 4.2 whenever they enter Debian testing. -- 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 161844] folder mis-sorted, messages not shown
http://bugs.kde.org/show_bug.cgi?id=161844 --- Comment #7 from Andras Georgy Bekes 2009-01-26 10:46:23 --- I still have this problem with KMail 1.9.9, both with an m$ exchange IMAP server and a Sun IMAP server (a "Sun Java System Messaging Server" I think). -- 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 52426] profiles should bind to certain outgoing addresses
http://bugs.kde.org/show_bug.cgi?id=52426 Andras Georgy Bekes bekesa sch bme hu changed: What|Removed |Added CC||bek...@sch.bme.hu --- Comment #11 from Andras Georgy Bekes 2009-01-12 11:05:52 --- Instead of adding a comment, you should vote on the bug. -- 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 161844] folder mis-sorted, messages not shown
http://bugs.kde.org/show_bug.cgi?id=161844 --- Comment #6 from Andras Georgy Bekes 2008-08-28 14:10:15 --- Since I sent the backtrace, every time kmail crashes again I check whether it's the same as what I sent. I checked like 4 or 5 such backtraces and it is always exactly the same (file names and line numbers match). The crash always happens after the folder gets mis-sorted and I switch to another folder and back. If I quit kmail after the folder gets screwed up and delete ~/.kde/share/apps/kmail/imap/.$WHEIRD_NUMBER.directory/.$FOLDERNAME.index.* files, everything works again. -- 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 161844] folder mis-sorted, messages not shown
--- 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=161844 --- Additional Comments From bekesa sch bme hu 2008-08-13 10:42 --- I'm using debian and have installed kdepim-dbg and kdelibs-dbg (there is no kmail-dbg package). The kcrash file is attached. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 161844] folder mis-sorted, messages not shown
--- 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=161844 --- Additional Comments From bekesa sch bme hu 2008-08-13 10:41 --- Created an attachment (id=26819) --> (http://bugs.kde.org/attachment.cgi?id=26819&action=view) KMail crashed. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 161844] folder mis-sorted, messages not shown
--- 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=161844 --- Additional Comments From bekesa sch bme hu 2008-06-04 15:56 --- For I don't know why but this bug shows up more frequently, now I meet with it several times a day. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 161844] New: folder mis-sorted, messages not shown
--- 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=161844 Summary: folder mis-sorted, messages not shown Product: kmail Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: bekesa sch bme hu Version:(using KDE 3.5.9) Installed from:Debian testing/unstable Packages While reading mails in an IMAP folder (reading, deleting, reading next, etc, periodic reloads), the sorting of messages suddenly gets screwed up. The unread messages get to the top of the list (while they should be in the bottom of the list, my folders are sorted according to "Order of Arrival"). After this event, the unread messages can't be read, if I select them, their message body remains blank. Switching to other folder and switching back doesn't help, neither restarting kmail. When switching from the screwed up folder to another and back, kmail crashes with some probability, but not always. The only workaround I've found is deleting ~/.kde/share/apps/kmail/imap/.$WHEIRD_NUMBER.directory/.$FOLDERNAME.index.* files. I can't reproduce the bug intentionally, but it happens like once or twice a week, so it's getting annoying. The problem appeared about a month ago I think. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 160969] hangs while eagerly eating memory before crashing
--- 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=160969 bekesa sch bme hu changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Additional Comments From bekesa sch bme hu 2008-04-19 19:52 --- The problem is most probably caused by a misbehaviour of KAddressBook. I've filed a bug report for it (Bug 161033). ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 160969] hangs while eagerly eating memory before crashing
--- 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=160969 --- Additional Comments From bekesa sch bme hu 2008-04-19 17:05 --- Just to make the above clear: currently my KMail starts with opening a mail folder that happens to be empty, so it does not try to show me a mail at s I also have a new way to reproduce the faulty behaviour: Instead of clicking on a non-empty folder, I start writing a new mail. In the "Composer" window, everything works, except for the "To:" field. Whenever I start typing in that field, memory eating starts. Maybe the fault is addressbook-related? I've tried, Kaddressbook starts eating memory immediately when I start it... ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 160969] New: hangs while eagerly eating memory before crashing
--- 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=160969 Summary: hangs while eagerly eating memory before crashing Product: kmail Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs kde org ReportedBy: bekesa sch bme hu Version:(using KDE 3.5.9) Installed from:Debian testing/unstable Packages KMail starts up normally. Does connect to IMAP server normally and indexes mails normally. After clicking on a mail, its memory consumption constantly increases without doing anything observable. CPU usage is low (5-30%), probably because of thrashing. After it eats 2000M VIRT memory, dies (not unexpectedly) with the following message: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc *** KMail got signal 6 (Crashing) KCrash: Application 'kmail' crashing... It is 100% reproducible, and does the same when reading local mail(dir) or IMAP. I suppose that the problem is within some library, because I can reproduce similar behaviour with kopete, however, kopete does this right after starting it, even before creating its window or opening kwallet. The two problems started at the same time, probably after upgrading to the bogus library version. How can I check which debian packages were updated in the last 2-3 days? I remember there was an upgrade of several kde-related packages that probably contained upgrades of all the common kopete-kmail libraries :-( But maybe not. I haven't (yet) found other KDE apps that behave the same. Kopete bug report is Bug 160940. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
