[Akonadi] [Bug 341884] dozens of duplicate mails in ~/.local/share/akonadi/file_db_data
https://bugs.kde.org/show_bug.cgi?id=341884 --- Comment #10 from Bernhard Jungk f...@projectstarfire.de --- Thanks for the advice, indeed it seems to be better now. I'll keep an eye on that folder for a while. -- 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 347854] akonadi_imap_resource has copied every new e-mail 36 times into the inbox folder of three other accounts
https://bugs.kde.org/show_bug.cgi?id=347854 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de --- Comment #4 from Bernhard Jungk f...@projectstarfire.de --- I have a very similar bug for a few days now. No and then akonadi/kmail2 seems to duplicate messages, but the duplicates are greyed out dummies. The only possibility to remove them is to go to the webmail interface and delete the duplicates there. -- 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
[Akonadi] [Bug 347854] akonadi_imap_resource has copied every new e-mail 36 times into the inbox folder of three other accounts
https://bugs.kde.org/show_bug.cgi?id=347854 --- Comment #5 from Bernhard Jungk f...@projectstarfire.de --- Maybe the bug is related to this one: https://bugs.kde.org/show_bug.cgi?id=348103? -- 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
[Akonadi] [Bug 348103] Thousands of empty messages with duplicate headers created in accounts
https://bugs.kde.org/show_bug.cgi?id=348103 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de --- Comment #3 from Bernhard Jungk f...@projectstarfire.de --- Created attachment 92841 -- https://bugs.kde.org/attachment.cgi?id=92841action=edit mail duplication This is what I am getting for almost every mail I receive. The phantom mails also cannot be removed by KMail. -- 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 341884] dozens of duplicate mails in ~/.local/share/akonadi/file_db_data
https://bugs.kde.org/show_bug.cgi?id=341884 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de --- Comment #6 from Bernhard Jungk f...@projectstarfire.de --- This problem is becoming unbearable for me. :-( ~/.local/share/akonadi/file_db_data$ fdupes -m . 84860 duplicate files (in 3857 sets), occupying 13738.0 megabytes -- 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
[kontact] [Bug 315666] Kontact crashed while running in the background
https://bugs.kde.org/show_bug.cgi?id=315666 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de -- 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 319958] New: KMail2 looses messages/empty received message
https://bugs.kde.org/show_bug.cgi?id=319958 Bug ID: 319958 Summary: KMail2 looses messages/empty received message Classification: Unclassified Product: kmail2 Version: 4.10.2 Platform: Ubuntu Packages URL: http://fire.coldbloodedice.de/upload/kmail2_lost_messa ge.png OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: f...@projectstarfire.de Sometimes a message is just plain empty and lost! (See screenshot, there I tried to open the selected mail.) In the screenshot I tried to open the message, however the corresponding message dialog shows up a completely empty mail. If I close kmail2, the message vanished and has left for heaven ... I think this is connected to a change in my internet connection while kmail2/akonadi tries to download mails. I witnessed this behavior now twice and everytime I had a) either lost the wireless connection or b) I changed the connection settings to use some VPN. Therefore this may be as well be not connected to kmail2 but to akonadi. I'm not sure. Reproducible: Always Steps to Reproduce: 1. Wait until kmail2/akonadi tries to fetch new mails 2. While fetching mails, disconnect your computer from the internet Actual Results: The message is displayed in the message list, however, the message itself is empty. Expected Results: I want to read my Mails! - I'm using POP3 to fetch mails - I'm using the Use pipelining for faster mail download option. - I did not check Leave fetched messages on the server, therefore at least two messages are no lost forever for me :-( -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 313287] New: Akregator Kontact plugin doesn't show feed entries anymore
https://bugs.kde.org/show_bug.cgi?id=313287 Bug ID: 313287 Summary: Akregator Kontact plugin doesn't show feed entries anymore Classification: Unclassified Product: akregator Version: 4.9.97 RC2 Hardware: Other URL: http://fire.coldbloodedice.de/upload/akregator.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kontact plugin Assignee: kdepim-bugs@kde.org Reporter: f...@projectstarfire.de The akregator plugin for kontact doesn't show any entries anymore. However, starting akregator without kontact works fine. Reproducible: Always Steps to Reproduce: 1. Klick on any feed Actual Results: Any empty window. Expected Results: The window on the right should show all (read and new) entries. Using akregator standalone works: http://fire.coldbloodedice.de/upload/akregator1.png -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[akregator] [Bug 313287] Akregator Kontact plugin doesn't show feed entries anymore
https://bugs.kde.org/show_bug.cgi?id=313287 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Bernhard Jungk f...@projectstarfire.de --- Uhm ... I'm so stupid, sorry for your time ;-) -- 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 255388] Kmail filters dont work in incoming mail
https://bugs.kde.org/show_bug.cgi?id=255388 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de --- Comment #74 from Bernhard Jungk f...@projectstarfire.de --- I think I have the same, a similar problem. I have set up several filters to move messages to separate folders. Sometimes an incoming mail is filtered, sometimes not. Applying the filter manually usually helps. This could be annoying. Furthermore I don't understand why filtered/moved messages show first up in the inbox folder after all. This was working much better with the old kmail. -- 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 260824] Crash of Kontact/Kadressbook when opening vCard
https://bugs.kde.org/show_bug.cgi?id=260824 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #2 from Bernhard Jungk f...@projectstarfire.de --- I finally had the time to try to reproduce the bug. Happily I'm unable to do so. The bug seems to be fixed in 4.8. -- 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 281402] Akonadi agent crash whe sending email
https://bugs.kde.org/show_bug.cgi?id=281402 --- Comment #11 from Bernhard Jungk fire projectstarfire de 2012-02-17 18:37:13 --- Created an attachment (id=68882) -- (http://bugs.kde.org/attachment.cgi?id=68882) New crash information added by DrKonqi akonadi_maildispatcher_agent (4.8) on KDE Platform 4.8.00 (4.8.0 using Qt 4.7.4 - What I was doing when the application crashed: Sending a mail, while a proxy server was configured (via autoconfiguration). -- Backtrace (Reduced): #7 operator[] (akey=..., this=0x80) at /usr/include/qt4/QtCore/qhash.h:738 #8 KIO::ProtoQueue::removeJob (this=0x0, job=optimized out) at ../../kio/kio/scheduler.cpp:483 #9 0x7fe918455e57 in KIO::SchedulerPrivate::assignJobToSlave (this=optimized out, slave=0x2235220, job=0x2243e80) at ../../kio/kio/scheduler.cpp:1274 #10 0x7fe91ad5e18c in MailTransport::SmtpJob::startSmtpJob (this=0x21d6bb0) at ../../mailtransport/smtpjob.cpp:244 #11 0x7fe91ad5f0e7 in MailTransport::SmtpJob::doStart (this=0x21d6bb0) at ../../mailtransport/smtpjob.cpp:133 -- 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 281402] Akonadi agent crash whe sending email
https://bugs.kde.org/show_bug.cgi?id=281402 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de --- Comment #7 from Bernhard Jungk fire projectstarfire de 2012-01-18 11:03:39 --- I experienced this bug (almost the same backtrace) with the recent version from KDE SC 4.8 RC2. Has the fix been applied to the 4.8 branch? -- 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 289831] Kontact crash after closing kontact with crashed korganizer
https://bugs.kde.org/show_bug.cgi?id=289831 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de -- 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 289831] Kontact crash after closing kontact with crashed korganizer
https://bugs.kde.org/show_bug.cgi?id=289831 --- Comment #2 from Bernhard Jungk fire projectstarfire de 2011-12-28 04:23:30 --- Created an attachment (id=67175) -- (http://bugs.kde.org/attachment.cgi?id=67175) New crash information added by DrKonqi kontact (4.8 rc1) on KDE Platform 4.7.95 (4.8 RC1 (4.7.95) using Qt 4.7.4 - What I was doing when the application crashed: I tried to move a message from one folder back to the inbox to try a new filter. What actually happend was not what I expected: 1. I moved the message via drag and drop to the inbox 2. The message disappeared in the originating folder 3. Switching to the inbox showed no sign of the message 4. Switching back to the originating folder showed the message sitting there 5. Quitting Kontact/KMail2 now crashes Kontact/KMail2 Notice that Kontact/KMail2 does not crash if moving a message succeeded, which sometimes does work. It seems to work for some folders and not for others. -- Backtrace (Reduced): #6 0x7f778ad7f3a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f778ad82b0b in __GI_abort () at abort.c:92 [...] #9 0x7f778adc1a96 in malloc_printerr (action=3, str=0x7f778aea8108 munmap_chunk(): invalid pointer, ptr=optimized out) at malloc.c:6283 #10 0x7f7787be496d in qDeleteAllQListNode*::const_iterator (end=optimized out, begin=optimized out) at /usr/include/qt4/QtCore/qalgorithms.h:322 #11 qDeleteAllQListNode* (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330 -- 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 289831] Kontact crash after closing kontact with crashed korganizer
https://bugs.kde.org/show_bug.cgi?id=289831 --- Comment #3 from Bernhard Jungk fire projectstarfire de 2011-12-28 04:27:40 --- 1. I moved the message via drag and drop to the inbox 2. The message disappeared in the originating folder 3. Switching to the inbox showed no sign of the message 4. Switching back to the originating folder showed the message sitting there 5. Quitting Kontact/KMail2 now crashes Kontact/KMail2 Actually I got this description wrong. (4) is does not show any message in the originating folder! -- 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 263401] New: Kontact crash on exit after switching sidebar options
https://bugs.kde.org/show_bug.cgi?id=263401 Summary: Kontact crash on exit after switching sidebar options Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: f...@projectstarfire.de Application: kontact (4.4.9) KDE Platform Version: 4.5.95 (4.6 RC2) Qt Version: 4.7.1 Operating System: Linux 2.6.37-12-server x86_64 Distribution: Ubuntu natty (development branch) -- Information about the crash: - What I was doing when the application crashed: Change sidebar options from Icons Text to Icons Only or from Icons Only to Icons Text, then close kontact - kontact crashes. This may be related to Bug 250138? The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f13062667a0 (LWP 4332))] Thread 2 (Thread 0x7f12ddd71700 (LWP 4340)): #0 0xff60017b in ?? () #1 0x7f12ddd70ac0 in ?? () #2 0x7fff973ff7b2 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7f13062667a0 (LWP 4332)): [KCrash Handler] #6 QSortFilterProxyModelPrivate::proxy_to_source (this=0x16d39e0, proxy_index=value optimized out) at itemviews/qsortfilterproxymodel.cpp:369 #7 0x7f13048ea63d in QSortFilterProxyModel::mapToSource (this=value optimized out, proxyIndex=value optimized out) at itemviews/qsortfilterproxymodel.cpp:2500 #8 0x7f13048eb7c5 in QSortFilterProxyModelPrivate::store_persistent_indexes (this=value optimized out) at itemviews/qsortfilterproxymodel.cpp:995 #9 0x7f13048eddda in QSortFilterProxyModelPrivate::clear_mapping (this=0x16d39e0) at itemviews/qsortfilterproxymodel.cpp:299 #10 0x7f13048e8442 in QAbstractProxyModel::qt_metacall (this=0x160f9c0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=value optimized out) at .moc/release-shared/moc_qabstractproxymodel.cpp:72 #11 0x7f13048f0ed5 in QSortFilterProxyModel::qt_metacall (this=0x160f9c0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff973b9040) at .moc/release-shared/moc_qsortfilterproxymodel.cpp:118 #12 0x7f13039abbb8 in QMetaObject::activate (sender=0x16d3680, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff973b9040) at kernel/qobject.cpp:3280 #13 0x7f13039ac0cf in QObject::destroyed (this=value optimized out, _t1=0x16d3680) at .moc/release-shared/moc_qobject.cpp:149 #14 0x7f13039ad7b7 in QObject::~QObject (this=0x16d3680, __in_chrg=value optimized out) at kernel/qobject.cpp:842 #15 0x7f1305e8fa66 in ~QStringListModel (this=0x16d3680, __in_chrg=value optimized out) at /usr/include/qt4/QtGui/qstringlistmodel.h:57 #16 ~Model (this=0x16d3680, __in_chrg=value optimized out) at ../../../kontact/src/iconsidepane.cpp:82 #17 Kontact::Model::~Model (this=0x16d3680, __in_chrg=value optimized out) at ../../../kontact/src/iconsidepane.cpp:82 #18 0x7f13039a91e4 in QObjectPrivate::deleteChildren (this=0x1575580) at kernel/qobject.cpp:1957 #19 0x7f13043a01f2 in QWidget::~QWidget (this=0x1575500, __in_chrg=value optimized out) at kernel/qwidget.cpp:1600 #20 0x7f1305e8f00d in ~Navigator (this=value optimized out, __in_chrg=value optimized out) at ../../../kontact/src/iconsidepane.h:43 #21 Kontact::Navigator::~Navigator (this=value optimized out, __in_chrg=value optimized out) at ../../../kontact/src/iconsidepane.h:43 #22 0x7f13039a91e4 in QObjectPrivate::deleteChildren (this=0x1574ad0) at kernel/qobject.cpp:1957 #23 0x7f13043a01f2 in QWidget::~QWidget (this=0x1574a70, __in_chrg=value optimized out) at kernel/qwidget.cpp:1600 #24 0x7f1305e8d4bd in ~IconSidePane (this=0x1574a70, __in_chrg=value optimized out) at ../../../kontact/src/iconsidepane.cpp:523 #25 Kontact::IconSidePane::~IconSidePane (this=0x1574a70, __in_chrg=value optimized out) at ../../../kontact/src/iconsidepane.cpp:525 #26 0x7f1305e86836 in Kontact::MainWindow::~MainWindow (this=0x1576450, __in_chrg=value optimized out, __vtt_parm=value optimized out) at ../../../kontact/src/mainwindow.cpp:254 #27 0x7f1305e869c9 in Kontact::MainWindow::~MainWindow (this=0x1576450, __in_chrg=value optimized out, __vtt_parm=value optimized out) at ../../../kontact/src/mainwindow.cpp:260 #28 0x7f13039aaa78 in QObject::event (this=0x1576450, e=value optimized out) at kernel/qobject.cpp:1202 #29 0x7f13043a498d in QWidget::event (this=0x1576450, event=0x2885480) at kernel/qwidget.cpp:8659 #30 0x7f130476decb in QMainWindow::event (this=0x1576450, event=0x2885480) at widgets/qmainwindow.cpp:1478 #31 0x7f130516ca6e in KXmlGuiWindow::event (this=0x1576450, ev=0x2885480) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:126 #32 0x7f1304354024 in QApplicationPrivate::notify_helper (this=0x156fa30,
[Bug 250138] Kontact crashed when switching sidebar options (small to large icons, or, show icons only) (Qt 4.7) [QModelIndex, QSortFilterProxyModel::parent, QPersistentModelIndex::parent]
https://bugs.kde.org/show_bug.cgi?id=250138 --- Comment #47 from Bernhard Jungk fire projectstarfire de 2011-01-05 23:50:43 --- It still crashes here with 4.4.9 but not 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 261100] New: Crash changing icon size of side bar in kontact
https://bugs.kde.org/show_bug.cgi?id=261100 Summary: Crash changing icon size of side bar in kontact Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: f...@projectstarfire.de Application: kontact (4.4.9) KDE Platform Version: 4.5.85 (4.6 Beta2) Qt Version: 4.7.1 Operating System: Linux 2.6.37-11-server x86_64 Distribution: Ubuntu natty (development branch) -- Information about the crash: - What I was doing when the application crashed: Changing the size of the icons of the side bar. The backtrace is very different to the one I marked as a possible duplicate. Maybe this is a different bug? The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f255dbf57a0 (LWP 2401))] Thread 2 (Thread 0x7f253540f700 (LWP 2455)): #0 0xff60017b in ?? () #1 0x7f253540eac0 in ?? () #2 0x7fffb77ff7b2 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7f255dbf57a0 (LWP 2401)): [KCrash Handler] #6 QSortFilterProxyModelPrivate::proxy_to_source (this=0x1929590, proxy_index=value optimized out) at itemviews/qsortfilterproxymodel.cpp:369 #7 0x7f255c26b7bd in QSortFilterProxyModel::mapToSource (this=value optimized out, proxyIndex=value optimized out) at itemviews/qsortfilterproxymodel.cpp:2499 #8 0x7f255c26a271 in QSortFilterProxyModel::data (this=value optimized out, index=..., role=13) at itemviews/qsortfilterproxymodel.cpp:1712 #9 0x7f255c28cc9a in data (this=0x17d3c30, option=..., index=...) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:398 #10 QStyledItemDelegate::sizeHint (this=0x17d3c30, option=..., index=...) at itemviews/qstyleditemdelegate.cpp:440 #11 0x7f255d81d931 in Kontact::Delegate::sizeHint (this=0x17d3c30, option=..., index=value optimized out) at ../../../kontact/src/iconsidepane.cpp:225 #12 0x7f255c203b11 in QListViewPrivate::itemSize (this=0x17a0240, option=..., index=...) at itemviews/qlistview.cpp:1788 #13 0x7f255c20405b in itemSize (this=0x19228a0, index=...) at ../../include/QtGui/private/../../../src/gui/itemviews/qlistview_p.h:473 #14 QListModeViewBase::indexToListViewItem (this=0x19228a0, index=...) at itemviews/qlistview.cpp:2215 #15 0x7f255c207a93 in QListViewPrivate::indexToListViewItem (this=0x17a0240, index=...) at itemviews/qlistview.cpp:1733 #16 0x7f255c208151 in rectForIndex (this=value optimized out, index=...) at ../../include/QtGui/private/../../../src/gui/itemviews/qlistview_p.h:345 #17 QListView::rectForIndex (this=value optimized out, index=...) at itemviews/qlistview.cpp:1226 #18 0x7f255c2082ce in QListView::visualRect (this=value optimized out, index=value optimized out) at itemviews/qlistview.cpp:561 #19 0x7f255c1e4396 in QAbstractItemView::update (this=value optimized out, index=value optimized out) at itemviews/qabstractitemview.cpp:3135 #20 0x7f255c1e446e in QAbstractItemViewPrivate::setHoverIndex (this=0x17a0240, index=...) at itemviews/qabstractitemview.cpp:150 #21 0x7f255c1e5fd6 in QAbstractItemView::viewportEvent (this=0x17d4410, event=0x7fffb7762620) at itemviews/qabstractitemview.cpp:1572 #22 0x7f255b315107 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=value optimized out, receiver=0x1922390, event=0x7fffb7762620) at kernel/qcoreapplication.cpp:847 #23 0x7f255bcd2b11 in QApplicationPrivate::notify_helper (this=0x17cfdd0, receiver=0x1922390, e=0x7fffb7762620) at kernel/qapplication.cpp:4441 #24 0x7f255bcd34bc in QApplicationPrivate::dispatchEnterLeave (enter=0x1922390, leave=value optimized out) at kernel/qapplication.cpp:2773 #25 0x7f255bcd3b2b in QApplicationPrivate::sendMouseEvent (receiver=0x1922390, event=0x7fffb7762890, alienWidget=0x1922390, nativeWidget=0x19207a0, buttonDown=0x7f255c7c6398, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3085 #26 0x7f255bd520c0 in QETWidget::translateMouseEvent (this=0x19207a0, event=value optimized out) at kernel/qapplication_x11.cpp:4438 #27 0x7f255bd50871 in QApplication::x11ProcessEvent (this=0x7fffb7763550, event=0x7fffb77631e0) at kernel/qapplication_x11.cpp:3564 #28 0x7f255bd78d62 in x11EventSourceDispatch (s=0x17d7250, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #29 0x7f2554377c4d in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #30 0x7f2554378438 in ?? () from /lib/libglib-2.0.so.0 #31 0x7f25543786c9 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #32 0x7f255b33fecf in QEventDispatcherGlib::processEvents (this=0x179cc30, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:415 #33 0x7f255bd789fe in
[Bug 260824] New: Crash of Kontact/Kadressbook when opening vCard
https://bugs.kde.org/show_bug.cgi?id=260824 Summary: Crash of Kontact/Kadressbook when opening vCard Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: f...@projectstarfire.de Application: kontact (4.4.8) KDE Platform Version: 4.5.85 (4.6 Beta2) Qt Version: 4.7.1 Operating System: Linux 2.6.37-10-server x86_64 Distribution: Ubuntu natty (development branch) -- Information about the crash: - What I was doing when the application crashed: Opening a vCard file. The crash always happens. The backtrace seems to be different to the other bug report, maybe this is related? The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0x7fd3aa54f780 (LWP 6807))] Thread 4 (Thread 0x7fd382997700 (LWP 6829)): #0 0x7fd3a0cd275e in g_main_context_check () from /lib/libglib-2.0.so.0 #1 0x7fd3a0cd3052 in ?? () from /lib/libglib-2.0.so.0 #2 0x7fd3a0cd3559 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7fd3a7c98f26 in QEventDispatcherGlib::processEvents (this=0x200d030, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:417 #4 0x7fd3a7c6d362 in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fd3a7c6d59c in QEventLoop::exec (this=0x7fd382996da0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7fd3a7b84274 in QThread::exec (this=value optimized out) at thread/qthread.cpp:490 #7 0x7fd3a7c4f82f in QInotifyFileSystemWatcherEngine::run (this=0x21824e0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fd3a7b86a2e in QThreadPrivate::start (arg=0x21824e0) at thread/qthread_unix.cpp:285 #9 0x7fd3a119b971 in start_thread (arg=value optimized out) at pthread_create.c:304 #10 0x7fd3a757192d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 3 (Thread 0x7fd385a6f700 (LWP 6831)): #0 0x7fd3a7565203 in __poll (fds=value optimized out, nfds=value optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fd3a0cd3030 in ?? () from /lib/libglib-2.0.so.0 #2 0x7fd3a0cd3559 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7fd3a7c98f26 in QEventDispatcherGlib::processEvents (this=0x1ebdc60, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:417 #4 0x7fd3a7c6d362 in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fd3a7c6d59c in QEventLoop::exec (this=0x7fd385a6eda0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7fd3a7b84274 in QThread::exec (this=value optimized out) at thread/qthread.cpp:490 #7 0x7fd3a7c4f82f in QInotifyFileSystemWatcherEngine::run (this=0x1d6d970) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fd3a7b86a2e in QThreadPrivate::start (arg=0x1d6d970) at thread/qthread_unix.cpp:285 #9 0x7fd3a119b971 in start_thread (arg=value optimized out) at pthread_create.c:304 #10 0x7fd3a757192d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7fd38674f700 (LWP 6832)): #0 0x7fd3a0cd300d in ?? () from /lib/libglib-2.0.so.0 #1 0x7fd3a0cd3559 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #2 0x7fd3a7c98f26 in QEventDispatcherGlib::processEvents (this=0x2048110, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:417 #3 0x7fd3a7c6d362 in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #4 0x7fd3a7c6d59c in QEventLoop::exec (this=0x7fd38674edb0, flags=...) at kernel/qeventloop.cpp:201 #5 0x7fd3a7b84274 in QThread::exec (this=value optimized out) at thread/qthread.cpp:490 #6 0x7fd39c4c213c in Herqq::Upnp::HControlPointThread::run() () from /usr/lib/libHUpnp.so.0 #7 0x7fd3a7b86a2e in QThreadPrivate::start (arg=0x1fddb00) at thread/qthread_unix.cpp:285 #8 0x7fd3a119b971 in start_thread (arg=value optimized out) at pthread_create.c:304 #9 0x7fd3a757192d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 1 (Thread 0x7fd3aa54f780 (LWP 6807)): [KCrash Handler] #6 0x7fd3a74beba5 in raise (sig=value optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7fd3a74c26b0 in abort () at abort.c:92 #8 0x7fd3a78c97ed in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #9 0x7fd3a78c7a36 in ?? () from /usr/lib/libstdc++.so.6 #10 0x7fd3a78c7a63 in std::terminate() () from /usr/lib/libstdc++.so.6 #11 0x7fd3a78c7bb6 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #12 0x7fd3a7c6d692 in QEventLoop::exec (this=0x7fffed750070, flags=...) at
[Bug 259777] Akonadi crashes when loading vCard File
https://bugs.kde.org/show_bug.cgi?id=259777 --- Comment #3 from Bernhard Jungk fire projectstarfire de 2010-12-20 21:39:08 --- Created an attachment (id=55110) -- (http://bugs.kde.org/attachment.cgi?id=55110) New crash information added by DrKonqi akonadi_vcard_resource (0.1) on KDE Platform 4.5.85 (4.6 Beta2) using Qt 4.7.1 - What I was doing when the application crashed: I was attaching a vCard file as a new addressbook. -- Backtrace (Reduced): #12 0x7f03c769f692 in QEventLoop::exec (this=0x7fff8c1456b0, flags=...) at kernel/qeventloop.cpp:214 #13 0x7f03c76a39bb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #14 0x7f03c7b1fc92 in Akonadi::ResourceBase::init (r=0xba52d0) at ../../akonadi/resourcebase.cpp:283 #15 0x0040eec6 in initVCardResource (argc=value optimized out, argv=value optimized out) at /usr/include/akonadi/resourcebase.h:188 #16 main (argc=value optimized out, argv=value optimized out) at ../../../resources/vcard/vcardresource.cpp:189 -- 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 259777] Akonadi crashes when loading vCard File
https://bugs.kde.org/show_bug.cgi?id=259777 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de -- 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 236569] New: Kontact crash on exit
https://bugs.kde.org/show_bug.cgi?id=236569 Summary: Kontact crash on exit Product: kontact Version: 4.4.3 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: f...@projectstarfire.de Application: kontact (4.4.3) KDE Platform Version: 4.4.3 (KDE 4.4.3) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic x86_64 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Kontact crashes sporadically on exit. I was not able to record the exact steps to reproduce the crash, but I will investigate the problem further. I hope that the backtrace will shed some light on the crash for the developers. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f79b89b1780 (LWP 3255))] Thread 2 (Thread 0x7f7997db1710 (LWP 3487)): #0 0x7f79b5a8cf53 in *__GI___poll (fds=value optimized out, nfds=value optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f79ae5c04a9 in g_main_context_poll (context=0x19c1470, block=value optimized out, dispatch=value optimized out, self=value optimized out) at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2904 #2 g_main_context_iterate (context=0x19c1470, block=value optimized out, dispatch=value optimized out, self=value optimized out) at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2586 #3 0x7f79ae5c08fc in IA__g_main_context_iteration (context=0x19c1470, may_block=1) at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2654 #4 0x7f79b6e77566 in QEventDispatcherGlib::processEvents (this=0x2b478e0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:414 #5 0x7f79b6e4c992 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #6 0x7f79b6e4cd6c in QEventLoop::exec (this=0x7f7997db0d90, flags=) at kernel/qeventloop.cpp:201 #7 0x7f79b6d56d59 in QThread::exec (this=value optimized out) at thread/qthread.cpp:487 #8 0x7f79b6e2d178 in QInotifyFileSystemWatcherEngine::run (this=0x17c6ab0) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7f79b6d59775 in QThreadPrivate::start (arg=0x17c6ab0) at thread/qthread_unix.cpp:248 #10 0x7f79b0b369ca in start_thread (arg=value optimized out) at pthread_create.c:300 #11 0x7f79b5a9969d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 1 (Thread 0x7f79b89b1780 (LWP 3255)): [KCrash Handler] #5 QAction::isChecked (this=0x2e0065) at kernel/qaction.cpp:1075 #6 0x7f7993142adc in ActionManager::writeSettings (this=0x2f121a0) at ../../korganizer/actionmanager.cpp:738 #7 0x7f79933e47a7 in ~KOrganizerPart (this=0x4042ca0, __in_chrg=value optimized out, __vtt_parm=value optimized out) at ../../korganizer/korganizer_part.cpp:103 #8 0x7f79b6e5ca5c in QObjectPrivate::deleteChildren (this=0x15993a0) at kernel/qobject.cpp:1986 #9 0x7f79b62642d5 in ~QWidget (this=0x1599210, __in_chrg=value optimized out) at kernel/qwidget.cpp:1469 #10 0x7f79b7910d55 in ~KMainWindow (this=0x1599210, __in_chrg=value optimized out) at ../../kdeui/widgets/kmainwindow.cpp:476 #11 0x7f79b85ce154 in ~MainWindow (this=0x1599210, __in_chrg=value optimized out, __vtt_parm=value optimized out) at ../../../kontact/src/mainwindow.cpp:260 #12 0x7f79b6e5dd6d in QObject::event (this=0x1599210, e=0x30e1ff0) at kernel/qobject.cpp:1231 #13 0x7f79b625cbdf in QWidget::event (this=0x1599210, event=0x30e1ff0) at kernel/qwidget.cpp:8455 #14 0x7f79b661fcab in QMainWindow::event (this=0x1599210, event=0x30e1ff0) at widgets/qmainwindow.cpp:1433 #15 0x7f79b794d783 in KXmlGuiWindow::event (this=0x2e0065, ev=0x0) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:131 #16 0x7f79b620722c in QApplicationPrivate::notify_helper (this=0x144f440, receiver=0x1599210, e=0x30e1ff0) at kernel/qapplication.cpp:4300 #17 0x7f79b620d6fb in QApplication::notify (this=0x7fff1a2764a0, receiver=0x1599210, e=0x30e1ff0) at kernel/qapplication.cpp:4183 #18 0x7f79b7836536 in KApplication::notify (this=0x7fff1a2764a0, receiver=0x1599210, event=0x30e1ff0) at ../../kdeui/kernel/kapplication.cpp:302 #19 0x7f79b6e4e06c in QCoreApplication::notifyInternal (this=0x7fff1a2764a0, receiver=0x1599210, event=0x30e1ff0) at kernel/qcoreapplication.cpp:704 #20 0x7f79b6e507e7 in QCoreApplication::sendEvent (receiver=0x0, event_type=value optimized out, data=0x1414620) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value optimized out, data=0x1414620) at kernel/qcoreapplication.cpp:1345 #22 0x7f79b6e779d3 in QCoreApplication::sendPostedEvents (s=value optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #23 postEventSourceDispatch (s=value
[Bug 188271] Cannot logon to newsgroup
https://bugs.kde.org/show_bug.cgi?id=188271 --- Comment #19 from Bernhard Jungk fire projectstarfire de 2009-07-27 17:22:04 --- Well, my configuration is somewhat like this: Internal Network News Server Firewall Internet The News Server can only be accessed from inside the Internal Network, not from the Internet. My point is, that this is not an Internal Error of knode and thus the error message should be somewhat more meaningful, otherwise this will trigger more duplicate bug reports. -- 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 188271] Cannot logon to newsgroup
https://bugs.kde.org/show_bug.cgi?id=188271 Bernhard Jungk f...@projectstarfire.de changed: What|Removed |Added CC||f...@projectstarfire.de --- Comment #17 from Bernhard Jungk fire projectstarfire de 2009-07-25 00:28:59 --- I just hit this bug with the following message: Internal Error Please send a full bug report at http://bugs.kde.org Unexpected server response to CONNECT command: 502 You have no permission to talk. Goodbye. I can't use the server from where I am now (the server can only be access from inside the local network and not from the internet), but still, this message is wrong, because it is not an error in knode. -- 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
