[korganizer] [Bug 466212] New: Crossing korganizer window border while prolonging an event causes crash
https://bugs.kde.org/show_bug.cgi?id=466212 Bug ID: 466212 Summary: Crossing korganizer window border while prolonging an event causes crash Classification: Applications Product: korganizer Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@patrick-nagel.net Target Milestone: --- Application: korganizer (5.21.3 (22.08.3)) Qt Version: 5.15.6 Frameworks Version: 5.102.0 Operating System: Linux 5.19.0-31-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: I had added school holidays from Apr-3 to Apr-14 (multi-day event). When I wanted to extend it to also cover the last weekend (Apr-15+16), I grabbed the end of the event and moved the mouse to the right. I didn't stop it early enough and somehow exited the korganizer window. In that instant korganizer crashed. I could reproduce it easily. Also, when I prolong the event and stop moving the mouse at the correct time, everything works as designed. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 0x7f433977745d in ?? () from /lib/x86_64-linux-gnu/libKF5EventViews.so.5abi1 #5 0x7f433aebc178 in QGraphicsScene::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f433ab6bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f4339ebae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f433aed7c42 in QGraphicsViewPrivate::mouseMoveEventHandler(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f433abaeb48 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f433ac5b552 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f4339ebaba3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f433ab6bf22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f433ab745b2 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f4339ebae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f433ab726b2 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f433abc80dc in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f433abcb4a0 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f433ab6bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f4339ebae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f433a3426fd in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #21 0x7f433a31663c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7f433293578e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #23 0x7f43377e4569 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f43378393c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f43377e1d20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f4339f14aea in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f4339eb97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f4339ec1c2a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x5573c01f9149 in ?? () #30 0x7f4339423510 in __libc_start_call_main (main=main@entry=0x5573c01f8b90, argc=argc@entry=1, argv=argv@entry=0x7ffdecbe90b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7f43394235c9 in __libc_start_main_impl (main=0x5573c01f8b90, argc=1, argv=0x7ffdecbe90b8, init=, fini=, rtld_fini=, stack_end=0x7ffdecbe90a8) at ../csu/libc-start.c:381 #32 0x5573c01f95a5 in ?? () [Inferior 1 (process 45680) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 383009] Searching body of message returns all messages with attachment
https://bugs.kde.org/show_bug.cgi?id=383009 Patrick changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||m...@patricksmits.net --- Comment #4 from Patrick --- Reproducible in Kmail 5.22.2 (22.12.2) on Arch Linux. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 421276] kmail crashed when I tried to use "Send via email" feature of Dolphin
https://bugs.kde.org/show_bug.cgi?id=421276 Patrick Silva changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Patrick Silva --- Cannot reproduce on neon unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.6 Graphics Platform: Wayland -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 460308] Attempt to attach a recent file fails with "Retrieving data from recentlyused is not supported"
https://bugs.kde.org/show_bug.cgi?id=460308 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- possibly duplicate of bug 459485 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 389230] Account assistant shows Wayland generic icon
https://bugs.kde.org/show_bug.cgi?id=389230 Patrick Silva changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Patrick Silva --- Cannot reproduce with kmail 22.03.40 running natively on Wayland on neon unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 428057] Under Wayland left click tray icon menu displayed on random part of screen
https://bugs.kde.org/show_bug.cgi?id=428057 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- On neon unstable, no menu opens when I left-click on tray icon. Right-click menu opens in the correct position. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 444116] New: The identity bound to an account always reverts to standard identity after restart of kmail
https://bugs.kde.org/show_bug.cgi?id=444116
Bug ID: 444116
Summary: The identity bound to an account always reverts to
standard identity after restart of kmail
Product: kmail2
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: config dialog
Assignee: kdepim-bugs@kde.org
Reporter: p...@in-transit.cc
Target Milestone: ---
SUMMARY
KMail sends mail from newly set up accounts with the standard identity instead
of the newly created identity.
STEPS TO REPRODUCE
1. Set up new account with new identity
2. Click the folder of the new account
3. Click "New"
OBSERVED RESULT
The identity chosen by KMail in the drop down menu is the standard identity.
EXPECTED RESULT
The identity should be the new identity.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon Testing 20211019-1822
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.88
Qt Version: 5.15.3
ADDITIONAL INFORMATION
KMail is my standard mail program and I use it with various accounts. During
the last six months this became a problem. Setting up a new account and linking
it to a new identity semms to work fine until I try to send a mail - KMail
automatically chooses the standard identity to send the mail.
In the settings dialogue (>Settings >Configure KMail >Receiving >[new Id]
>Modify >Advanced) under Identity settings "Use default identity" is not marked
and the dropdown menu shows correctly [new Id] as the chosen Id.
But in the "Folder properties" of the new account under the "General" tab the
dropdown menu shows the standard identity as selected ("Use default identity"
is not marked). After choosing [New Id] as the "Sender identity" subsequent
mails will be sent with the correct identity. After a restart of KMail the
standard identity will again be used instead of the [new Id].
The bug seems to have been introduced with the version of KMail that came with
Kubuntu 21.04 (hirsute hippo) and it's present in 21.10 as well. I checked the
current KDE Neon testing as well (KMail Version 5.18.3 (21.08.3)) and it is
still there.
--
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 #23 from Patrick Silva --- I can't reproduce this bug on neon unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- 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 #14 from Patrick Silva --- (In reply to tromzy from comment #13) > Well if I do a "xprop", the cursor does not change over the Kmail window, so > I guess it means it's Wayland native ? yes. Weirdly kmail is still buggy on my Wayland session. :( -- 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 #12 from Patrick Silva --- it's still happening here. Are you sure that kmail is running natively on Wayland on your system? Operating System: Arch Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 426957] New: Maildir path ending with a slash causes issues
https://bugs.kde.org/show_bug.cgi?id=426957 Bug ID: 426957 Summary: Maildir path ending with a slash causes issues Product: Akonadi Version: 5.15.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: m...@patricksmits.net Target Milestone: --- SUMMARY A maildir account with a path ending with a slash causes the auto sync to fail. Manual syncing does work correctly. STEPS TO REPRODUCE 1. Create a maildir account using an existing maildir (e.g. a postfix maildir) and make sure the path ends with a slash. 2. Send a mail to the existing maildir. OBSERVED RESULT Akonadi console browser doesn't show any changes to the mailbox. EXPECTED RESULT Akonadi console browser should show a new mail. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.8.10-arch1-1 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION When enabled, the the Akonadi console debugger will show an invalid path under "collections". It also shows that the maildir resource returns an error (code 1, 0 collections found). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 425632] mbox, kmail does not display any mail
https://bugs.kde.org/show_bug.cgi?id=425632 Patrick changed: What|Removed |Added Ever confirmed|0 |1 CC||m...@patricksmits.net Status|REPORTED|CONFIRMED --- Comment #1 from Patrick --- I can confirm this issue on Kmail 5.15.1 and KDE Frameworks 5.74.0. Kmail doesn't show the e-mails of a mbox mailbox in /var/spool/mail. -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 424405] Clicking on the notes widget in the task bar does not always open the note
https://bugs.kde.org/show_bug.cgi?id=424405 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 410612 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 391735] Recurrence end after X occurrences does not count excluded dates
https://bugs.kde.org/show_bug.cgi?id=391735 Patrick changed: What|Removed |Added CC||m...@patricksmits.net --- Comment #1 from Patrick --- I just ran into a similar problem with daily occurrences (version 5.14.2). This looks like a bug to me. An exception isn't an occurrence and shouldn't be included in the count. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409517] [Wayland] KMail freezes
https://bugs.kde.org/show_bug.cgi?id=409517 --- Comment #4 from Patrick Silva --- kmail is still freezing on Wayland. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 421276] New: kmail crashed when I tried to use "Send via email" feature of Dolphin
https://bugs.kde.org/show_bug.cgi?id=421276 Bug ID: 421276 Summary: kmail crashed when I tried to use "Send via email" feature of Dolphin Product: kmail2 Version: Git (master) Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY I right-clicked on a video file in Dolphin, hovered over "Share", chose "Send via email..." then kmail crashed. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Thread 20 (Thread 0x7f6c5568f700 (LWP 18081)): #0 0x7f6c9c9f3c96 in __libc_send (fd=fd@entry=4, buf=buf@entry=0x7f6c5568da60, len=len@entry=32, flags=flags@entry=0) at ../sysdeps/unix/sysv/linux/send.c:28 #1 0x7f6c93256451 in (anonymous namespace)::ProcessNetlinkRequest >::operator() (bufsize=8192, this=, func=..., buf=0x7f6c48010e18 "", hdr=0x7f6c5568da60, sock=4) at kernel/qnetworkinterface_linux.cpp:163 #2 0x7f6c93256451 in (anonymous namespace)::processNetlinkRequest > (l=..., bufsize=8192, buf=0x7f6c48010e18 "", hdr=0x7f6c5568da60, sock=4) at kernel/qnetworkinterface_linux.cpp:218 #3 0x7f6c93256451 in getInterfaces (buf=0x7f6c48010e18 "", sock=4) at kernel/qnetworkinterface_linux.cpp:274 #4 0x7f6c93256451 in QNetworkInterfaceManager::scan() (this=) at kernel/qnetworkinterface_linux.cpp:446 #5 0x7f6c93247d05 in QNetworkInterfaceManager::allInterfaces() (this=) at kernel/qnetworkinterface.cpp:118 #6 0x7f6c93248554 in QNetworkInterface::allInterfaces() () at kernel/qnetworkinterface.cpp:876 #7 0x7f6c54a49986 in QGenericEngine::doRequestUpdate() (this=0x55ab28204850) at qgenericengine.cpp:286 #8 0x7f6c9d2ff1f6 in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const (this=this@entry=0x7f6c5568e030, object=object@entry=0x55ab28204850, connectionType=Qt::DirectConnection, connectionType@entry=Qt::AutoConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:2294 #9 0x7f6c9d3010e8 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) (obj=0x55ab28204850, member=member@entry=0x7f6c932d4005 "requestUpdate", type=type@entry=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1515 #10 0x7f6c9323481b in QMetaObject::invokeMethod(QObject*, char const*, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=0x7f6c932d4005 "requestUpdate", obj=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:461 #11 0x7f6c9323481b in QNetworkConfigurationManagerPrivate::pollEngines() (this=0x55ab282190a0) at bearer/qnetworkconfigmanager_p.cpp:493 #12 0x7f6c932c8665 in QNetworkConfigurationManagerPrivate::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at .moc/moc_qnetworkconfigmanager_p.cpp:132 #13 0x7f6c9d3284b9 in doActivate(QObject*, int, void**) (sender=0x7f6c4800e4b0, signal_index=3, argv=0x7f6c5568e5e0) at kernel/qobject.cpp:3882 #14 0x7f6c9d322f92 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7f6c4800e4b0, m=m@entry=0x7f6c9d7bbce0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f6c5568e5e0) at kernel/qobject.cpp:3930 #15 0x7f6c9d32c297 in QTimer::timeout(QTimer::QPrivateSignal) (this=this@entry=0x7f6c4800e4b0, _t1=...) at .moc/moc_qtimer.cpp:205 #16 0x7f6c9d32c5f8 in QTimer::timerEvent(QTimerEvent*) (this=0x7f6c4800e4b0, e=) at kernel/qtimer.cpp:257 #17 0x7f6c9d3204e3 in QObject::event(QEvent*) (this=0x7f6c4800e4b0, e=0x7f6c5568e750) at kernel/qobject.cpp:1361 #18 0x7f6c9d2ed491 in doNotify (event=0x7f6c5568e750, receiver=0x7f6c4800e4b0) at kernel/qcoreapplication.cpp:1165 #19 0x7f6c9d2ed491 in QCoreApplication::notify(QObject*, QEvent*) (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1151 #20 0x7f6c9d2ed491 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7f6c4800e4b0,
[kmail2] [Bug 421275] New: Context menu of systray icon is misplaced
https://bugs.kde.org/show_bug.cgi?id=421275 Bug ID: 421275 Summary: Context menu of systray icon is misplaced Product: kmail2 Version: Git (master) Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 128331 --> https://bugs.kde.org/attachment.cgi?id=128331=edit screenshot STEPS TO REPRODUCE 1. open kmail 2. right-click on its systray icon 3. dismiss the context menu of systray icon 4. right-click on the systray icon of kmail again OBSERVED RESULT misplaced context menu, see the attached screenshot please. EXPECTED RESULT context menu should always open in correct position SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 417240] Report bug dialog selects wrong (default) version when opening bugzilla
https://bugs.kde.org/show_bug.cgi?id=417240 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- I think that it's not a kmail issue. The same happened on my system a few days ago when I tried to report a bug of elisa music player using its "Launch Bug Report Wizard" option. Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 413071] [Wayland] Kmail crashes when resized or maximized
https://bugs.kde.org/show_bug.cgi?id=413071 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 417207] Notes widget doesn't launch when no window is active
https://bugs.kde.org/show_bug.cgi?id=417207 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 410612 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 366356] Reply action picks the wrong To address when replying between two identities of the same KMail instance
https://bugs.kde.org/show_bug.cgi?id=366356 --- Comment #2 from Patrick Wigmore --- I have also found this bug in KMail 5.1.3. If I send myself emails from any one of my identities to any one of my other identities, and then try to reply to those emails, the default is to reply to the address that *received* the email that's being replied to, rather than the address that *sent* it. Deleting the identity that sent the email restores proper reply behaviour. Re-creating the identity restores improper reply behaviour. If the email contains a Reply-To header, then replies go to the Reply-To header and this bug is not triggered. This bug seems to have been reported previously in #301449 "Replying to a mail sent by another identity in the same kmail copy leads to replying to the current identity itself". That bug was not confirmed in a supported version of KMail, so it was RESOLVED UNMAINTAINED. I found it difficult to find this bug report, because the title is not very descriptive, so I am taking the liberty of changing the title to make it a bit more searchable. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 366356] Reply action picks the wrong To address when replying between two identities of the same KMail instance
https://bugs.kde.org/show_bug.cgi?id=366356 Patrick Wigmore changed: What|Removed |Added Summary|Reply action picks the |Reply action picks the |wrong To address|wrong To address when ||replying between two ||identities of the same ||KMail instance CC||pwbugrepo...@gmx.com --- Comment #1 from Patrick Wigmore --- I have also found this bug in KMail 5.1.3. If I send myself emails from any one of my identities to any one of my other identities, and then try to reply to those emails, the default is to reply to the address that *received* the email that's being replied to, rather than the address that *sent* it. Deleting the identity that sent the email restores proper reply behaviour. Re-creating the identity restores improper reply behaviour. If the email contains a Reply-To header, then replies go to the Reply-To header and this bug is not triggered. This bug seems to have been reported previously in #301449 "Replying to a mail sent by another identity in the same kmail copy leads to replying to the current identity itself". That bug was not confirmed in a supported version of KMail, so it was RESOLVED UNMAINTAINED. I found it difficult to find this bug report, because the title is not very descriptive, so I am taking the liberty of changing the title to make it a bit more searchable. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 413280] New: Akonadi server failed to start when I opened Kmail
https://bugs.kde.org/show_bug.cgi?id=413280 Bug ID: 413280 Summary: Akonadi server failed to start when I opened Kmail Product: Akonadi Version: GIT (master) Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 123379 --> https://bugs.kde.org/attachment.cgi?id=123379=edit akonaki self test log SUMMARY I installed Kmail on Neon unstable edition, I opened it and got a window saying "an error occured during the startup of the Akonadi server" with a button to save a report. I'm attaching such report. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 389230] Account assistant shows Wayland generic icon
https://bugs.kde.org/show_bug.cgi?id=389230 Patrick Silva changed: What|Removed |Added Version|5.11.0 |5.12.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409517] [Wayland] KMail freezes
https://bugs.kde.org/show_bug.cgi?id=409517 Patrick Silva changed: What|Removed |Added CC||tak...@disroot.org --- Comment #2 from Patrick Silva --- *** Bug 409796 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409796] KMail Won't Start (Not Responding) Under Wayland Session
https://bugs.kde.org/show_bug.cgi?id=409796 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 409517 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409517] [Wayland] KMail freezes
https://bugs.kde.org/show_bug.cgi?id=409517 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 407143] New: settings window is too small
https://bugs.kde.org/show_bug.cgi?id=407143 Bug ID: 407143 Summary: settings window is too small Product: kmail2 Version: Git (master) Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 119789 --> https://bugs.kde.org/attachment.cgi?id=119789=edit screenshot SUMMARY When I open the settings window for the first time, it looks like what we can see in the attached screenshot. STEPS TO REPRODUCE 1. open kmail 2. open "Settings" menu > "Configure kmail..." 3. EXPECTED RESULT default window size is better adjusted SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 389230] Account assistant shows Wayland generic icon
https://bugs.kde.org/show_bug.cgi?id=389230 Patrick Silva changed: What|Removed |Added Version|5.9.1 |5.11.0 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 Patrick changed: What|Removed |Added CC||patr...@noxs.nl --- Comment #42 from Patrick --- Created attachment 119395 --> https://bugs.kde.org/attachment.cgi?id=119395=edit Invalid date test feed This is what happens (Akregator 5.10.3): In Akregator::Feed::appendArticles fetched items are processed. All items are stored in the feed's archive. Only new items which have a publication date newer than the expiration date, will be appended to the feed's article list. The next time the feed is fetched, all items which were processed earlier but were not added to the article list and haven't changed since then, will be processes as new items. That's when the problems start on these two lines: Article mya(*it, this); mya.offsetPubDate(nudge); The (private) constructor of Article creates an object with an invalid publication date (the default QDateTime constructor) because the item was already stored in the feed's archive and it hasn't changed. On the next line the publication date is updated, but based on the invalid publication date. This causes the invalid date to be written to the feed's archive. It's easy to reproduce with the attached feed: 1. Add the feed to Akregator. 2. Fetch the feed. The article first appears as a blank line, but after restarting Akregator the invalid is shown. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 406405] New: Adding new feed suspends saving feeds until quit
https://bugs.kde.org/show_bug.cgi?id=406405 Bug ID: 406405 Summary: Adding new feed suspends saving feeds until quit Product: akregator Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: metakit plugin Assignee: kdepim-bugs@kde.org Reporter: patr...@noxs.nl Target Milestone: --- SUMMARY Adding a new feed causes all feeds only to be saved until Akgregator is quit. Normally feeds are saved immediately. This is caused by Akregator::Backend::StorageMK4Impl::markDirty() in storagemk4impl.cpp. When a new feed is created, the private member 'modified' is set to true, but this causes markDirty to skip the commit. STEPS TO REPRODUCE 1. Add new feed. 2. Check ~/local/share/akregator/Archive OBSERVED RESULT New feed is 0 bytes in size. Additional fetched feeds are not saved. EXPECTED RESULT New feed should be larger than 0 bytes. Additional fetched feeds should be saved immediately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 ADDITIONAL INFORMATION Possibly related to bug 199232. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 406324] New: Messages detected as scam are deleted when moved to trash
https://bugs.kde.org/show_bug.cgi?id=406324 Bug ID: 406324 Summary: Messages detected as scam are deleted when moved to trash Product: kmail2 Version: 5.10.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: patr...@noxs.nl Target Milestone: --- SUMMARY The option 'Move to Trash' in the scam detection menu doesn't move messages to trash, but deletes them permanently. The following error is logged: kmail[3963]: QObject::connect(KPIM::ProgressItem, KMTrashMsgCommand): invalid null parameter. Other move to trash actions (pressing the 'Del' key) work just fine. STEPS TO REPRODUCE 1. Select a scam message in the Inbox. 2. In the Scam detection dropdown menu, select the action 'Move to Trash'. OBSERVED RESULT The message had disappeared from the Inbox, but is not moved to the Trash. EXPECTED RESULT The message should have been moved to the Trash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405005] In KMAIL ( I do not see any KMAIL2 ) There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP
https://bugs.kde.org/show_bug.cgi?id=405005 Patrick Carabin changed: What|Removed |Added CC||patrick.cara...@gmail.com --- Comment #2 from Patrick Carabin --- STEPS TO REPRODUCE 1. Kmail unable to connect to GMAIL server 2. By mistake, click seems to remove the menus 3. Idiotic message appears 1 ms ( 0,001 sec) telling it removes the menus, and (may be) telling how to get the menus back[impossible to read, it disappears] 4. dpkg-reconfigure kmail SHOULD correct the problem, but DOES NOT 5. PURGE kmail and pim, and reinstall : does NOT solve the problem OBSERVED RESULT the menus DO NOT reappear: KMAIL unusable EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405005] In KMAIL ( I do not see any KMAIL2 ) There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP
https://bugs.kde.org/show_bug.cgi?id=405005 --- Comment #1 from Patrick Carabin --- N: Impossible de trouver le paquet kmail2 version : ii kmail 4:17.12.3-0ubuntu1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405005] In KMAIL ( I do not see any KMAIL2 ) There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP
https://bugs.kde.org/show_bug.cgi?id=405005 Patrick Carabin changed: What|Removed |Added Summary|There is a STUPID OPTION to |In KMAIL ( I do not see any |suppress the menu, and NO |KMAIL2 ) There is a STUPID |WAY BACK: dpkg-reconfigure |OPTION to suppress the |does NOT repair, Uninstall |menu, and NO WAY BACK: |+ Reinstall does NOT HELP |dpkg-reconfigure does NOT ||repair, Uninstall + ||Reinstall does NOT HELP -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 405005] New: There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP
https://bugs.kde.org/show_bug.cgi?id=405005 Bug ID: 405005 Summary: There is a STUPID OPTION to suppress the menu, and NO WAY BACK: dpkg-reconfigure does NOT repair, Uninstall + Reinstall does NOT HELP Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: patrick.cara...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 402241] KMail Wayland UI drawing flakiness
https://bugs.kde.org/show_bug.cgi?id=402241 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 387313 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400368] Cannot launch Kmail via apps launcher. It launches via terminal.
https://bugs.kde.org/show_bug.cgi?id=400368 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Patrick Silva --- cannot reproduce anymore. kmail 5.9.2 Operating System: Arch Linux KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400368] Cannot launch Kmail via apps launcher. It launches via terminal.
https://bugs.kde.org/show_bug.cgi?id=400368 Patrick Silva changed: What|Removed |Added Version|5.9.1 |5.9.2 -- You are receiving this mail because: You are the assignee for the bug.
[i18n] [Bug 401296] Erro no texto de criação das chaves
https://bugs.kde.org/show_bug.cgi?id=401296 Patrick Silva changed: What|Removed |Added Component|general |pt-BR Product|kleopatra |i18n Assignee|aheine...@intevation.de |kde-i18n-pt...@kde.org Version|3.0.1 |unspecified CC||bugsefor...@gmx.com -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 400588] Provide appropriate names for Kmail addons in Discover app store
https://bugs.kde.org/show_bug.cgi?id=400588 --- Comment #8 from Patrick Silva --- Awesome. Thank you Laurent. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400588] Provide appropriate names for Kmail addons in Discover app store
https://bugs.kde.org/show_bug.cgi?id=400588 Patrick Silva changed: What|Removed |Added Version|unspecified |5.9.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400588] New: Provide appropriate names for Kmail addons in Discover app store
https://bugs.kde.org/show_bug.cgi?id=400588 Bug ID: 400588 Summary: Provide appropriate names for Kmail addons in Discover app store Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY Already reported as bug 400203. Nate's comment: "This isn't a discover issue, though. The data comes from KDE programs that install the .knsrc definition files that provide this data. They need to add a "Name" key and provide a pretty name. See this commit for an example: https://cgit.kde.org/sddm-kcm.git/commit/?id=b3928bb58819c4306a23918762be7cd5aa663979 " STEPS TO REPRODUCE 1. open discover 2. click "Applications addons" in the side bar 3. OBSERVED RESULT Names of the categories related to Kmail (Accountwizard, ksieve_script, Messageviewer_header_themes) are not user-friendly. See the screenshot. https://bugsfiles.kde.org/attachment.cgi?id=115852 EXPECTED RESULT user-friendly names like... Account Wizard Ksieve Scripts Kmail Header Themes SOFTWARE VERSIONS Arch Linux KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51 Qt Version: 5.12 beta3 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 400482] existing blog feed is not editable/erasable
https://bugs.kde.org/show_bug.cgi?id=400482 --- Comment #1 from Patrick Silva --- *** Bug 400483 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 400483] existing blog feed is not editable/erasable
https://bugs.kde.org/show_bug.cgi?id=400483 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 400482 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400368] New: Cannot launch Kmail via apps launcher. It launches via terminal.
https://bugs.kde.org/show_bug.cgi?id=400368 Bug ID: 400368 Summary: Cannot launch Kmail via apps launcher. It launches via terminal. Product: kmail2 Version: 5.9.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- STEPS TO REPRODUCE 1. search for "kmail" in the apps launcher and try to open it 2. 3. OBSERVED RESULT nothing happens EXPECTED RESULT kmail opens SOFTWARE VERSIONS Operating System: Arch Linux kmail 5.9.2 KDE Plasma Version: 5.14.2 Qt Version: 5.12.0 beta3 KDE Frameworks Version: 5.51.0 ADDITIONAL INFORMATION kmail opens when I run "kmail" in terminal. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 399092] New: date and time menu wouldn't function
https://bugs.kde.org/show_bug.cgi?id=399092 Bug ID: 399092 Summary: date and time menu wouldn't function Product: korganizer Version: unspecified Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: timezones Assignee: kdepim-bugs@kde.org Reporter: patrickbism...@orange.fr Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION date and time menu wouldn't function -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 399091] New: Korganizer: all the events are not scheduled properly (my time-2)
https://bugs.kde.org/show_bug.cgi?id=399091 Bug ID: 399091 Summary: Korganizer: all the events are not scheduled properly (my time-2) Product: korganizer Version: unspecified Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: timezones Assignee: kdepim-bugs@kde.org Reporter: patrickbism...@orange.fr Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Paris, France is UTC+2. Now, all the events are scheduled at UTC Besides, the menu item "Configure date and Time" doesn't function, it says:"Could not start control module for date and time format." -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 305849] KOrganizer monthly view cannot scroll week by week
https://bugs.kde.org/show_bug.cgi?id=305849 Patrick Zimmermann <patr...@zakweb.de> changed: What|Removed |Added CC||patr...@zakweb.de --- Comment #7 from Patrick Zimmermann <patr...@zakweb.de> --- The bug is still present in Kontact 5.7.3 and has now been present for more than five years now! Is Kontact still actively developed? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 305849] KOrganizer monthly view cannot scroll week by week
https://bugs.kde.org/show_bug.cgi?id=305849 Patrick Zimmermann <patr...@zakweb.de> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #6 from Patrick Zimmermann <patr...@zakweb.de> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 363585] Wrong message "Some parts of this message will not be signed"
https://bugs.kde.org/show_bug.cgi?id=363585 Patrick Holthaus <patrick.holth...@uni-bielefeld.de> changed: What|Removed |Added CC||patrick.holthaus@uni-bielef ||eld.de --- Comment #1 from Patrick Holthaus <patrick.holth...@uni-bielefeld.de> --- Same thing here. Just two remarks: * It does not happen, if I select signing plus encryption. * I'm not quite sure yet but I think it produces bad signatures if I select "Send as it is". -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 199232] Database not saved until quitting
https://bugs.kde.org/show_bug.cgi?id=199232 --- Comment #9 from Patrick <patr...@noxs.nl> --- It seems Akregator (5.7.1) stops saving the feed data after a new feed is added. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 386614] Deleted event does not disappear immediatly when using google synced calendar
https://bugs.kde.org/show_bug.cgi?id=386614 Patrick Eigensatz <patrick.eigens...@gmail.com> changed: What|Removed |Added Summary|Deleted event does not |Deleted event does not |disappear immediatly when |disappear immediatly when |using synced calendar |using google synced ||calendar -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 386614] New: Deleted event does not disappear immediatly when using synced calendar
https://bugs.kde.org/show_bug.cgi?id=386614 Bug ID: 386614 Summary: Deleted event does not disappear immediatly when using synced calendar Product: korganizer Version: 5.6.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-bugs@kde.org Reporter: patrick.eigens...@gmail.com Target Milestone: --- I use KOrganizer to sync events with my Google Calendar. It now happened a few times that I deleted an entry in the agendaview and it was still there afterwards. (It only loses the Google 'g' in the upper left corner.) I have no problems when deleting a local-only event. Since the event is still showing up I can also move/stretch it, but not delete (Del key) it. Also, the context menu won't show up when right clicking on it. When showing the preceeding week and then coming back again the event is gone. Note: Menu -> View -> Refresh does *not* delete the event, I really need to change the currently displayed week and come back. It seems as if this only happens to newly created events. When I create an event, switch the week and come back and then try to delete it, this does not happen. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 382587] Article viewer jumps to scroll position of previously viewed article
https://bugs.kde.org/show_bug.cgi?id=382587 --- Comment #6 from Patrick <patr...@noxs.nl> --- To clarify my case, I'll add some steps to reproduce the problem: 1. Select an article in the article list. Make sure the article is long enough for the vertical scrollbar to appear in the article viewer. 2. In the article viewer, scroll down to the bottom of the article. 3. Select another article in the article list. Again, make sure the article is long enough for the vertical scrollbar to appear in the article viewer. Notice the scroll position after step 3. It's not at the top where you would expect it to be. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 382587] Article viewer jumps to scroll position of previously viewed article
https://bugs.kde.org/show_bug.cgi?id=382587
--- Comment #4 from Patrick <patr...@noxs.nl> ---
(In reply to Laurent Montel from comment #3)
> (In reply to Patrick from comment #2)
> > I did some debugging and found that the scroll position is remembered by the
> > chromium backend used by Qt. The scroll position restore used by
> > akregator/messagelib isn't working because javascript is disabled.
>
> it's wrong as it's execute in specific environment.
> js is enabled as private => it's execute for sure.
>
Javascript is enabled for external URLs, loaded in a new tab. But javascript is
disabled for article content stored inside the feed, shown next to the article
list (in widescreen view) or below the article list (in normal view). See the
constructor of ArticleViewerWebEnginePage.
> >
> > As
> > enabling javascript might have side effects, a possible solution is loading
> > a blank page before a new article is loaded in the viewer. You could do this
> > in ArticleHtmlWebEngineWriter::begin() by replacing:
> > mWebView->load(QUrl());
> > with
> > mWebView->load(QUrl(QStringLiteral("about:blank")));
>
>
The idea was to clear the page and reset the scroll position to the top, but it
doesn't work well with the rest of the code.
--
You are receiving this mail because:
You are the assignee for the bug.
[akregator] [Bug 382587] Article viewer jumps to scroll position of previously viewed article
https://bugs.kde.org/show_bug.cgi?id=382587
--- Comment #2 from Patrick <patr...@noxs.nl> ---
I did some debugging and found that the scroll position is remembered by the
chromium backend used by Qt. The scroll position restore used by
akregator/messagelib isn't working because javascript is disabled. As enabling
javascript might have side effects, a possible solution is loading a blank page
before a new article is loaded in the viewer. You could do this in
ArticleHtmlWebEngineWriter::begin() by replacing:
mWebView->load(QUrl());
with
mWebView->load(QUrl(QStringLiteral("about:blank")));
--
You are receiving this mail because:
You are the assignee for the bug.
[akregator] [Bug 199232] Database not saved until quitting
https://bugs.kde.org/show_bug.cgi?id=199232 --- Comment #8 from Patrick <patr...@noxs.nl> --- Regarding my previous comment, I lost a lot of articles after an uptime of about 10 days and a crash of Akregator during startup (after a reboot). I've been monitoring the archived feeds since then, but they seem to be saved correctly after each fetch. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 199232] Database not saved until quitting
https://bugs.kde.org/show_bug.cgi?id=199232 Patrick <patr...@noxs.nl> changed: What|Removed |Added CC||patr...@noxs.nl --- Comment #7 from Patrick <patr...@noxs.nl> --- This issue is still present in Akregator 5.5.3. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 382587] New: Article viewer jumps to scroll position of previously viewed article
https://bugs.kde.org/show_bug.cgi?id=382587 Bug ID: 382587 Summary: Article viewer jumps to scroll position of previously viewed article Product: akregator Version: 5.5.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: patr...@noxs.nl Target Milestone: --- The article viewer seems to remember its scroll position and apply it to the next selected article. After reading a longer article in the article viewer and selecting a new article, you first have to scroll up to the top position to read the article from the beginning. Akregator version 5.5.3. -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 377129] Akregator crashes immediatelly after being launched
https://bugs.kde.org/show_bug.cgi?id=377129 Patrick Wieland <p...@wieland-plm.de> changed: What|Removed |Added CC||p...@wieland-plm.de --- Comment #1 from Patrick Wieland <p...@wieland-plm.de> --- I think it is a packaging problem / missing dependency. I was able to fix it with "apt-get install libqt5webengine5". -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 329988] Pipe Trough filter breaks 'To:' field for messages sent to undisclosed recepients
https://bugs.kde.org/show_bug.cgi?id=329988 --- Comment #2 from Patrick <patr...@noxs.nl> --- I can't reproduce this bug because I don't receive messages addressed to unresolved recipients anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 328025] Moving read mail ends up in 'new' directory instead of 'cur' directory
https://bugs.kde.org/show_bug.cgi?id=328025 Patrick <patr...@noxs.nl> changed: What|Removed |Added Version|4.11|16.08 --- Comment #2 from Patrick <patr...@noxs.nl> --- This bug is still reproducible in akonadi 16.08. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 286025] KMail2 does not properly quote long lines in a base64 message when replying
https://bugs.kde.org/show_bug.cgi?id=286025 Patrick <patr...@noxs.nl> changed: What|Removed |Added CC||patr...@noxs.nl --- Comment #5 from Patrick <patr...@noxs.nl> --- Not reproducible in 5.3.0 (KF 5.26.0). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 369203] New: CollectionFetchJob::exec() hangs forever
https://bugs.kde.org/show_bug.cgi?id=369203
Bug ID: 369203
Summary: CollectionFetchJob::exec() hangs forever
Product: Akonadi
Version: unspecified
Platform: Debian testing
URL: https://bugs.freedesktop.org/show_bug.cgi?id=97609
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: libakonadi
Assignee: kdepim-bugs@kde.org
Reporter: patrick.o...@intel.com
SyncEvolution uses the blocking API to execute jobs. That used to work fine
with older Akonadi, but on Debian Stretch (= 4.14.10-5) it just hangs. Below is
a stand-alone test program demonstrating the problem.
On Debian Jessie, the output is:
$ ./akonadi-lsDatabase "akonadi" opened using driver "QMYSQL"
akonadi_ical_resource_0
On Debian Stretch:
$ ./akonadi-ls
^C
Shutting down "0x277afc0" ...
Here it got aborted after two hours.
Akonadi seems okay on Debian Stretch:
$ akonadictl status
Akonadi Control: running
Akonadi Server: running
akonadiprivate_log: search paths: ("lib/x86_64-linux-gnu",
"lib/x86_64-linux-gnu/qt5/plugins/", "lib/x86_64-linux-gnu/kf5/",
"lib/x86_64-linux-gnu/kf5/plugins/", "/usr/lib/qt5/plugins/",
"/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
Akonadi Server Search Support: available (Remote Search)
Available Agent Types: akonadi_akonotes_resource, akonadi_birthdays_resource,
akonadi_contacts_resource, akonadi_davgroupware_resource,
akonadi_googlecalendar_resource, akonadi_googlecontacts_resource,
akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource,
akonadi_invitations_agent, akonadi_kalarm_dir_resource,
akonadi_kalarm_resource, akonadi_knut_resource, akonadi_kolab_resource,
akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mbox_resource,
akonadi_migration_agent, akonadi_mixedmaildir_resource,
akonadi_newmailnotifier_agent, akonadi_notes_resource,
akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_vcard_resource,
akonadi_vcarddir_resource
akonadiconsole shows that there are collections.
Reproducible: Always
Steps to Reproduce:
1. cat >akonadi-ls.cpp <
#include
#include
#include
#include
#include
#include
#include
using namespace Akonadi;
/**
* We take over ownership of jobs by storing them in smart pointers
* (RAII). This is how SyncEvolution does things and more predictable
* than assuming that a future exec() call will auto-delete them as
* part of its event processing.
*
* To avoid double frees, we need to disable auto-deletion.
* This method does that. Use like this:
* std::auto_ptr statisticsJob(DisableAutoDelete(new
CollectionStatisticsJob(m_collection)));
*/
template J *DisableAutoDelete(J *job) { job->setAutoDelete(false);
return job; }
int main(int argc, char **argv)
{
KAboutData aboutData(// The program name used internally.
"syncevolution",
// The message catalog name
// If null, program name is used instead.
0,
// A displayable program name string.
ki18n("SyncEvolution"),
// The program version string.
"1.0",
// Short description of what the app does.
ki18n("Lets Akonadi synchronize with a SyncML Peer"),
// The license this code is released under
KAboutData::License_GPL,
// Copyright Statement
ki18n("(c) 2010-12"),
// Optional text shown in the About box.
// Can contain any information desired.
ki18n(""),
// The program homepage string.
"http://www.syncevolution.org/;,
// The bug report email address
"syncevolut...@syncevolution.org");
KCmdLineArgs::init(argc, argv, );
KApplication app(false);
// std::unique_ptr fetchJob(DisableAutoDelete(new
CollectionFetchJob(Collection::root(),
// CollectionFetchJob::Recursive)));
CollectionFetchJob *fetchJob = new CollectionFetchJob(Collection::root(),
CollectionFetchJob::Recursive);
fetchJob->fetchScope().setContentMimeTypes(QString("text/calendar").split(","));
if (!fetchJob->exec()) {
std::cerr << "Cannot fetch collections." << std::endl;
return 1;
}
Collection::List collections = fetchJob->collections();
foreach (const Collection , collections) {
std::cout << collection.name().toUtf8().constData() << std::endl;
}
return 0;
}
EOF
2. g++ -I/usr/include/KDE -I/usr/include/qt4 -I/usr/include/qt4/QtCore -g
akonadi-ls.cpp -o akonadi-ls -lakonadi-kde -lkdecore -lkdeui -lQtCore
3. ./akonadi-ls
Actual Results:
It hangs. gdb stacktrace:
(gdb) where
[kmail2] [Bug 360000] New: KMail grabs default PCM device on notification
https://bugs.kde.org/show_bug.cgi?id=36 Bug ID: 36 Summary: KMail grabs default PCM device on notification Product: kmail2 Version: 5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: patrick.auer...@gmail.com The soundcard of my PC stopped working after a while, so I started monitoring the usage of PCM devices in my system. What I found is that KMail grabs the default PCM device of the system when a notification dialog pops up (in my case it was the sieve script upload confirmation dialog). If the device is already in use (by pulseaudio), audio keeps working as it should. It seems that some notifications bypass pulseaudio and use ALSA directly, but do not release the device afterwards. Closing the application releases the device again, but its really annoying. Reproducible: Always Steps to Reproduce: 1. Open the sieve script editor 2. Klick OK to close the editor 3. Default PCM device gets used by KMail Actual Results: No audio over default soundcard Expected Results: Sound keeps working Arch Linux package version: 15.12.2-1 Kernel: 4.4.1-2-ARCH x86_64 output of fuser -av USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: valethF...m 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
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 Patrick Hanft patr...@phlogfile.de changed: What|Removed |Added CC||patr...@phlogfile.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 305504] Mail list unread colors are wrong with a dark theme
https://bugs.kde.org/show_bug.cgi?id=305504 Patrick Zimmermann patr...@zakweb.de changed: What|Removed |Added CC||patr...@zakweb.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
[Akonadi] [Bug 339576] Can't create new top level IMAP folder
https://bugs.kde.org/show_bug.cgi?id=339576 Patrick Auernig patrick.auer...@gmail.com changed: What|Removed |Added CC||patrick.auer...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. 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
[kmail] [Bug 202917] Retrieving IMAP folders updates takes several minutes
https://bugs.kde.org/show_bug.cgi?id=202917 --- Comment #3 from Patrick O'Callaghan pocallag...@gmail.com --- No thanks. I jumped ship to Evolution (still under KDE) years ago. -- 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 345672] New: Kontact crash while deleting IMAP folder
https://bugs.kde.org/show_bug.cgi?id=345672 Bug ID: 345672 Summary: Kontact crash while deleting IMAP folder Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: patrick.oltm...@posteo.net Application: kontact (4.14.6) KDE Platform Version: 4.14.6 Qt Version: 4.8.6 Operating System: Linux 3.19.2-201.fc21.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Trying to delete a folder (containing mails) on an IMAP server. The folder was actually deleted, as confirmed via the account's webmail interface. The crash does not seem to be reproducible. -- Backtrace: Application: Kontact (kontact), 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 0x7f81edbc1900 (LWP 2145))] Thread 3 (Thread 0x7f81a0eaf700 (LWP 2146)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x003543372093 in JSC::BlockAllocator::blockFreeingThreadMain (this=0x1d99488) at /usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128 #2 0x003543677636 in WTF::wtfThreadEntryPoint (param=0x1d8c060) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196 #3 0x003317e0752a in start_thread (arg=0x7f81a0eaf700) at pthread_create.c:310 #4 0x00331730022d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f8193fff700 (LWP 2175)): #0 0x7fff47d3ec0e in clock_gettime () #1 0x00331730e4ad in __GI___clock_gettime (clock_id=optimized out, tp=optimized out) at ../sysdeps/unix/clock_gettime.c:115 #2 0x0033222d3585 in do_gettime (frac=synthetic pointer, sec=synthetic pointer) at tools/qelapsedtimer_unix.cpp:127 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:144 #4 0x0033223b62d5 in updateCurrentTime (this=0x7f818c002ee0) at kernel/qeventdispatcher_unix.cpp:354 #5 QTimerInfoList::timerWait (this=0x7f818c002ee0, tm=...) at kernel/qeventdispatcher_unix.cpp:460 #6 0x0033223b4b7c in timerSourcePrepareHelper (src=optimized out, timeout=0x7f8193ffeb04) at kernel/qeventdispatcher_glib.cpp:143 #7 0x0033223b4c45 in timerSourcePrepare (source=optimized out, timeout=timeout@entry=0x7f8193ffeb04) at kernel/qeventdispatcher_glib.cpp:176 #8 0x00331a2490fd in g_main_context_prepare (context=context@entry=0x7f818c0009a0, priority=priority@entry=0x7f8193ffeb90) at gmain.c:3399 #9 0x00331a249a5b in g_main_context_iterate (context=context@entry=0x7f818c0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3761 #10 0x00331a249c4c in g_main_context_iteration (context=0x7f818c0009a0, may_block=1) at gmain.c:3842 #11 0x0033223b54be in QEventDispatcherGlib::processEvents (this=0x7f818c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #12 0x003322384cc1 in QEventLoop::processEvents (this=this@entry=0x7f8193ffecd0, flags=...) at kernel/qeventloop.cpp:149 #13 0x003322385025 in QEventLoop::exec (this=this@entry=0x7f8193ffecd0, flags=...) at kernel/qeventloop.cpp:204 #14 0x003322279b49 in QThread::exec (this=optimized out) at thread/qthread.cpp:538 #15 0x00332227c3af in QThreadPrivate::start (arg=0x1e61020) at thread/qthread_unix.cpp:349 #16 0x003317e0752a in start_thread (arg=0x7f8193fff700) at pthread_create.c:310 #17 0x00331730022d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f81edbc1900 (LWP 2145)): [KCrash Handler] #6 0x00353f137399 in Akonadi::FavoriteCollectionsModel::removeCollection (this=0x0, collection=...) at /usr/src/debug/kdepimlibs-4.14.6/akonadi/favoritecollectionsmodel.cpp:294 #7 0x003550adf4ac in KMMainWidget::slotCollectionRemoved (this=optimized out, col=...) at /usr/src/debug/kdepim-4.14.6/kmail/kmmainwidget.cpp:4501 #8 0x003550bdf51e in KMMainWidget::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at /usr/src/debug/kdepim-4.14.6/x86_64-redhat-linux-gnu/kmail/moc_kmmainwidget.cpp:488 #9 0x00332239acdc in QMetaObject::activate (sender=0x21e1550, m=m@entry=0x353f4d8200 Akonadi::Monitor::staticMetaObject, local_signal_index=local_signal_index@entry=16, argv=argv@entry=0x7fff47c65580) at kernel/qobject.cpp:3567 #10 0x00353f16dcf5 in Akonadi::Monitor::collectionRemoved (this=optimized out, _t1=...) at /usr/src/debug/kdepimlibs-4.14.6/x86_64-redhat-linux-gnu/akonadi/moc_monitor.cpp:343 #11 0x00353f178dee in Akonadi::MonitorPrivate::emitCollectionNotification (this=this@entry=0x2302730, msg=..., col=..., par=...,
[Akonadi] [Bug 329988] New: Pipe Trough filter breaks 'To:' field for messages sent to undisclosed recepients
https://bugs.kde.org/show_bug.cgi?id=329988 Bug ID: 329988 Summary: Pipe Trough filter breaks 'To:' field for messages sent to undisclosed recepients Classification: Unclassified Product: Akonadi Version: 4.12 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Mail Filter Agent Assignee: kdepim-bugs@kde.org Reporter: patr...@noxs.nl Messages sent by Arch Linux AUR notification system have a 'To:' field which contains 'undisclosed-recipients: ;'. After filtering this message for spam or viruses, the field is stripped to 'To' without a colon. This causes Kmail to misinterpret the next line in the header, in this case the subject. Reproducible: Always Steps to Reproduce: To reproduce the bug, you have to be subscribed to an Arch Linux AUR notification feed. 1. Disable automatic filtering and add one of the pipe trough filters to the Apply Filter menu (e.g. clamav). 2. When a message from the Arch Linux AUR notification system arrives, apply a pipe through filter. Actual Results: Part of the header: Received: by alderaan.archlinux.org (Postfix, from userid 992) id 4541624047; Tue, 14 Jan 2014 19:13:53 + (UTC) To Subject: AUR Comment for chromium-pepper-flash-stable Reply-To: nob...@archlinux.org From: aur-not...@archlinux.org Expected Results: Part of the header: Received: by alderaan.archlinux.org (Postfix, from userid 992) id 4541624047; Tue, 14 Jan 2014 19:13:53 + (UTC) To: undisclosed-recipients: ; Subject: AUR Comment for chromium-pepper-flash-stable Reply-to: nob...@archlinux.org From: aur-not...@archlinux.org I haven't been able to reproduce the bug by sending a mail to undisclosed recipients by myself. -- 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 327836] Akonadi Facebook resource crashes when attempting to enter login information for authentication
https://bugs.kde.org/show_bug.cgi?id=327836 Patrick little_big_man_...@yahoo.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Patrick little_big_man_...@yahoo.com --- After upgrading KDE to 4.12.0, I tried again and it still did not work. I checked this bug and did not realize it had been updated since I last commented on it. Upon Mr. Wu's advice, I recompiled the ICU package dev-libs/icu on Funtoo. After recompiling, I tried the Facebook and Google resources. They now seem to work without any trouble. I do not know what the problem was. Perhaps the last time I compiled ICU, I may have used some GCC optimizations that caused trouble. In any case, I did not use any optimizations other than -O2 -march=core2 this time around and it worked fine. So this bug can be closed. -- 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 327836] Akonadi Facebook resource crashes when attempting to enter login information for authentication
https://bugs.kde.org/show_bug.cgi?id=327836 --- Comment #1 from Patrick little_big_man_...@yahoo.com --- I upgraded to KDE 4.11.4, and the issue is still present. I also wanted to note that the exact same problem also occurs with the Google Contacts and Google Calendars and Tasks resources, so the issue apparently lies with some common component. -- 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 327988] Server removes header and body data of maildir records in parttable
https://bugs.kde.org/show_bug.cgi?id=327988 --- Comment #2 from Patrick patr...@noxs.nl --- No errors, but I do get the following message when the problem occurs: found 1 item parts to expire in collection sent-mail -- 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 316840] imap resource starts crazy connect / disconnect cycle to mail server
https://bugs.kde.org/show_bug.cgi?id=316840 Patrick Schaaf k...@bof.de changed: What|Removed |Added CC||k...@bof.de -- 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 328025] New: Moving read mail ends up in 'new' directory instead of 'cur' directory
https://bugs.kde.org/show_bug.cgi?id=328025 Bug ID: 328025 Summary: Moving read mail ends up in 'new' directory instead of 'cur' directory Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-bugs@kde.org Reporter: patr...@noxs.nl Once a mail is read (in Kmail), it is moved from the folder's 'new' directory to the 'cur' directory. But when you move this mail to another folder (or delete it to trash), it is moved to the folder's 'new' directory. Reproducible: Always Steps to Reproduce: 1. Select a mail in Kmail and mark it read. 2. In Kmail, move the mail to another folder. 3. Look up the mail in the maildir resource directory. Actual Results: The mail in the maildir resource is located in the target folder's 'new' directory. Expected Results: The mail in the maildir resource should be located in the target folder's 'cur' directory. -- 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 327988] New: Server removes header and body data of maildir records in parttable
https://bugs.kde.org/show_bug.cgi?id=327988 Bug ID: 327988 Summary: Server removes header and body data of maildir records in parttable Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: patr...@noxs.nl I'm heaving trouble with Akonadi Nepomuk Feeder which doesn't index existing mails, and the reason seems to be that the data in the data field of all mail records in parttable with name PLD:HEAD and name PLD:RFC822 is erased. When a new mail arrives (either sent or received), it is stored correctly in the database, but after a few minutes, the data field changes. I activated logging of the mysql server, and it shows queries like these: 3 PrepareUPDATE PartTable SET pimItemId = ?, name = ?, data = ?, datasize = ?, version = ?, external = ? WHERE ( id = ? ) 3 Reset stmt 3 ExecuteUPDATE PartTable SET pimItemId = 17353, name = 'PLD:HEAD', data = NULL, datasize = 0, version = 1, external = 0 WHERE ( id = 34943 ) 3 Reset stmt 3 ExecuteUPDATE PartTable SET pimItemId = 17353, name = 'PLD:RFC822', data = NULL, datasize = 0, version = 1, external = 0 WHERE ( id = 34945 ) 3 Reset stmt I already created a new database, but that didn't change anything. Other resources seem to be fine, only the maildir resource is affected. The Akonadi Debugger, the Job Tracker, and the Notification Monitor don't show any output when the update queries are executed. Reproducible: Always Steps to Reproduce: 1. Open Akonadi Console. 2. Select parttable in the DB browser (or use the DB console with a meaningful query). 3. Send an email. 4. Find the email in the parttable. 5. Wait a few minutes and monitor the parttable for changes (by refreshing the table). Actual Results: The data field of the records with name PLD:HEAD or PLD:RFC822 is cleared and the datasize is set to 0. Expected Results: The data field should not have changed. -- 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 324925] Already-existing MAILDIRs not getting indexed with KDE 4.11
https://bugs.kde.org/show_bug.cgi?id=324925 Patrick patr...@noxs.nl changed: What|Removed |Added CC||patr...@noxs.nl --- Comment #3 from Patrick patr...@noxs.nl --- I'm seeing the same issue here on KDE 4.11.3, Arch Linux x86_64. -- 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 327836] New: Akonadi Facebook resource crashes when attempting to enter login information for authentication
https://bugs.kde.org/show_bug.cgi?id=327836 Bug ID: 327836 Summary: Akonadi Facebook resource crashes when attempting to enter login information for authentication Classification: Unclassified Product: Akonadi Version: 4.11 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Facebook Resource Assignee: mklape...@kde.org Reporter: little_big_man_...@yahoo.com CC: kdepim-bugs@kde.org Application: akonadi_facebook_resource (4.11) KDE Platform Version: 4.11.3 (Compiled from sources) Qt Version: 4.8.5 Operating System: Linux 3.11.1-gentoo-ck1 x86_64 Distribution: (none) -- Information about the crash: - What I was doing when the application crashed: I added the Facebook resource to akonadi. Then I clicked the button to authenticate. The window for providing my Facebook login information appeared. The program immediately crashes when typing the first keystroke to input my login information. - Custom settings of the application: I'm running Funtoo Linux. Because the program repeatedly crashed, I recompiled kdepim-runtime and libkfbapi with gcc's -Og to help provide a better backtrace. The crash can be reproduced every time. -- Backtrace: Application: Facebook of type Facebook (akonadi_facebook_resource), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f8f0896d800 (LWP 4646))] Thread 3 (Thread 0x7f8eefc5d700 (LWP 4654)): #0 0x7f8f04b4890c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8eff4e1ac2 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f8eff4e1af9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f8f04b44d63 in start_thread () from /lib64/libpthread.so.0 #4 0x7f8f05053a3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8eef35c700 (LWP 4655)): #0 0x7f8f0504a15d in poll () from /lib64/libc.so.6 #1 0x7f8f0324a794 in g_main_context_iterate.isra.22 () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8f0324a89c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8f07956cc5 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f8f07928dcf in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7f8f079290c5 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7f8f07828b3f in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7f8f0782b17f in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f8f04b44d63 in start_thread () from /lib64/libpthread.so.0 #9 0x7f8f05053a3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8f0896d800 (LWP 4646)): [KCrash Handler] #5 0x7f8efa58bfa8 in icu::RuleBasedBreakIterator::handleNext(icu::RBBIStateTable const*) () from /usr/lib64/libicuuc.so.52 #6 0x7f8efa58de5f in icu::RuleBasedBreakIterator::next() () from /usr/lib64/libicuuc.so.52 #7 0x7f8efa58e01d in icu::RuleBasedBreakIterator::previous() () from /usr/lib64/libicuuc.so.52 #8 0x7f8eff190682 in WebCore::RenderText::previousOffset(int) const () from /usr/lib64/qt4/libQtWebKit.so.4 #9 0x7f8efee1146d in WebCore::Position::inRenderedText() const () from /usr/lib64/qt4/libQtWebKit.so.4 #10 0x7f8efee98be0 in WebCore::VisiblePosition::canonicalPosition(WebCore::Position const) () from /usr/lib64/qt4/libQtWebKit.so.4 #11 0x7f8efee99274 in WebCore::VisiblePosition::init(WebCore::Position const, WebCore::EAffinity) () from /usr/lib64/qt4/libQtWebKit.so.4 #12 0x7f8efee99230 in WebCore::VisiblePosition::VisiblePosition(WebCore::Position const, WebCore::EAffinity) () from /usr/lib64/qt4/libQtWebKit.so.4 #13 0x7f8efee9c0be in WebCore::VisibleSelection::setBaseAndExtentToDeepEquivalents() () from /usr/lib64/qt4/libQtWebKit.so.4 #14 0x7f8efeea0270 in WebCore::VisibleSelection::validate(WebCore::TextGranularity) () from /usr/lib64/qt4/libQtWebKit.so.4 #15 0x7f8efeea04eb in WebCore::VisibleSelection::VisibleSelection(WebCore::Position const, WebCore::EAffinity) () from /usr/lib64/qt4/libQtWebKit.so.4 #16 0x7f8eff41642f in WebCore::InsertTextCommand::input(WTF::String const, bool, WebCore::InsertTextCommand::RebalanceType) () from /usr/lib64/qt4/libQtWebKit.so.4 #17 0x7f8efee964e3 in WebCore::TypingCommand::insertTextRunWithoutNewlines(WTF::String const, bool) () from /usr/lib64/qt4/libQtWebKit.so.4 #18 0x7f8efee969bf in WebCore::TypingCommand::insertText(WTF::String const, bool) () from /usr/lib64/qt4/libQtWebKit.so.4 #19 0x7f8efee3d14a in
[kmail2] [Bug 325664] IMAP add folder creates .FOOBAR but stored in akonadi database as /FOOBAR
https://bugs.kde.org/show_bug.cgi?id=325664 --- Comment #2 from Patrick Noffke patrick.nof...@gmail.com --- The fourth column is a .. I didn't explicitly configure this in dovecot. In my /etc/dovecot/conf.d/10-mail.conf file, there is an inbox namespace, with the separator field commented out. In fact, everything is commented out in that section except inbox = yes. So I'm guessing the default is . unless it is explicitly set otherwise. I will probably upgrade to fedora 19 relatively soon. That would be the earliest I could try 4.11 (assuming they are at 4.11 in that version). -- 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 275483] kmail2 fails to download any messages
https://bugs.kde.org/show_bug.cgi?id=275483 --- Comment #9 from Patrick patr...@noxs.nl --- It seems to be fixed in 4.11.2, so it probably was a duplicate of bug 254198 (at least in my case). -- 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 325664] New: IMAP add folder creates .FOOBAR but stored in akonadi database as /FOOBAR
https://bugs.kde.org/show_bug.cgi?id=325664 Bug ID: 325664 Summary: IMAP add folder creates .FOOBAR but stored in akonadi database as /FOOBAR Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: Fedora RPMs URL: http://forum.kde.org/viewtopic.php?f=215t=109833 OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: patrick.nof...@gmail.com Please see referenced URL. I add the folder in kmail, and it doesn't show up in the subscribe list under Manage Local Subscriptions. When I modify the database using akonadiconsole, it shows up. I can see the folder is created as .FOOBAR in the dovecot maildir folder. Restarting kmail does not work. Reproducible: Always Steps to Reproduce: 1. Right click on top level of email account in left pane (where folders are shown). 2. Click Add Folder, enter folder name, hit OK. 3. Folder does not show up. 4. Right click on account, click Manage Folder Subscriptions, and folder still does not show up. 5. Modify database as shown in referenced URL. 6. Folder shows up (I didn't need to restart kmail). Actual Results: See above. Expected Results: See above. $ rpm -q kdepim kdepim-4.10.5-1.fc18.x86_64 -- 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 323168] GPG signature validation fails due to KMail modifying headers within received mails
https://bugs.kde.org/show_bug.cgi?id=323168 Patrick Zimmermann patr...@zakweb.de changed: What|Removed |Added CC||patr...@zakweb.de --- Comment #1 from Patrick Zimmermann patr...@zakweb.de --- Verified here. Received message shows as invalid signature in kmail. When saving the message locally, extracting message text and signature and removing the quotes and newline at the end of the email text gpg --verify sig text works. -- 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 323168] GPG signature validation fails due to KMail modifying headers within received mails
https://bugs.kde.org/show_bug.cgi?id=323168 --- Comment #2 from Patrick Zimmermann patr...@zakweb.de --- Forgot to say: version 4.11.00 -- 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 279278] Kmail creates an invalid S/MIME signature if the S/MIME password dialog is cancelled
https://bugs.kde.org/show_bug.cgi?id=279278 Patrick Zimmermann patr...@zakweb.de changed: What|Removed |Added CC||patr...@zakweb.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
[nepomuk] [Bug 294320] kmail complains about the semantic destkop not running, when it is
https://bugs.kde.org/show_bug.cgi?id=294320 Patrick Zimmermann patr...@zakweb.de changed: What|Removed |Added CC||patr...@zakweb.de --- Comment #19 from Patrick Zimmermann patr...@zakweb.de --- Seems to have resolved itself on my installation. I think I have not deleted any database whatsoever. Just 2-3 reboots later (perhaps an upgrade to 4.11 in between) and everything working again. -- 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 275483] kmail2 fails to download any messages
https://bugs.kde.org/show_bug.cgi?id=275483 --- Comment #8 from Patrick patr...@noxs.nl --- I found the following lines in .xsession-errors: [2364:2386:0807/120437:ERROR:object_proxy.cc(532)] Failed to call method: org.kde.KWallet.open: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [2364:2386:0807/120437:ERROR:native_backend_kwallet_x.cc(838)] Error contacting kwalletd (open) This bug might be related to bug 254198. -- 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 281227] KMail2 4.7's Find messages ... reproducibly fails to search: Unknown error. (Unable to create persistent search)
https://bugs.kde.org/show_bug.cgi?id=281227 Patrick patr...@noxs.nl changed: What|Removed |Added CC||patr...@noxs.nl --- Comment #54 from Patrick patr...@noxs.nl --- I've found what's causing the problem, but it's not KMail. In the Akonadi source, the file server/src/handler/searchpersistent.cpp (in method SearchPersistent::parseStream()) contains the following line: col.setRemoteId( queryString ); // ### remove, legacy compat This sets the remote id of the virtual collection in which the search result will be stored to the query which KMail sends to Akonadi. This collection is only created if it doesn't already exist. But the query used as remote id is too long ( 255 chars). -- 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 320517] [kde-windows] akonaditray lacks icon in the start menu
https://bugs.kde.org/show_bug.cgi?id=320517 Patrick Spendrin ps...@gmx.de changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||ps...@gmx.de Ever confirmed|0 |1 --- Comment #2 from Patrick Spendrin ps...@gmx.de --- It actually should be KDE4_INSTALL_DIR (which is an ugly hack, I know) -- 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
[kdepim] [Bug 320427] [kde-windows] importwizard lacks icon in the start menu (no kde4_add_app_icon command in the build system)
https://bugs.kde.org/show_bug.cgi?id=320427 --- Comment #2 from Patrick Spendrin ps...@gmx.de --- Git commit 833c317ddb9b079c507145f7e6cda546465e8a27 by Patrick Spendrin. Committed on 31/05/2013 at 11:07. Pushed by sengels into branch 'kde-4.10'. fix app icons for import-wizard, kjots and ktnef Related: bug 320426, bug 320454 M +2-1portage/kde/kdepim/kdepim-20080202.py A +43 -0portage/kde/kdepim/kdepim-app-icons.diff http://commits.kde.org/emerge/833c317ddb9b079c507145f7e6cda546465e8a27 -- 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
[ktnef] [Bug 320454] [kde-windows] ktnef lacks icon in the start menu (no kde4_add_app_icon command in the build system)
https://bugs.kde.org/show_bug.cgi?id=320454 --- Comment #2 from Patrick Spendrin ps...@gmx.de --- Git commit 833c317ddb9b079c507145f7e6cda546465e8a27 by Patrick Spendrin. Committed on 31/05/2013 at 11:07. Pushed by sengels into branch 'kde-4.10'. fix app icons for import-wizard, kjots and ktnef Related: bug 320427, bug 320426 M +2-1portage/kde/kdepim/kdepim-20080202.py A +43 -0portage/kde/kdepim/kdepim-app-icons.diff http://commits.kde.org/emerge/833c317ddb9b079c507145f7e6cda546465e8a27 -- 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 320517] [kde-windows] akonaditray lacks icon in the start menu
https://bugs.kde.org/show_bug.cgi?id=320517 --- Comment #6 from Patrick Spendrin ps...@gmx.de --- Git commit 70c6caa01118c7ba9cc49ce997e38297d484f8fd by Patrick Spendrin. Committed on 31/05/2013 at 16:56. Pushed by sengels into branch 'kde-4.10'. fix app icon the easy way M +2-0portage/kde/kdepim-runtime/kdepim-runtime-20101222.py A +12 -0portage/kde/kdepim-runtime/kdepim-runtime-4.10.2-20130531.diff http://commits.kde.org/emerge/70c6caa01118c7ba9cc49ce997e38297d484f8fd -- 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 275483] kmail2 fails to download any messages
https://bugs.kde.org/show_bug.cgi?id=275483 Patrick patr...@noxs.nl changed: What|Removed |Added CC||patr...@noxs.nl --- Comment #4 from Patrick patr...@noxs.nl --- This bug is still present in 4.10 on my system (Arch Linux x86_64). I've recreated the Akonadi database, I've recreated all my accounts and I've recreated the wallet for the passwords, but this didn't work. I've done some experiments which may help to solve this bug. On my system, Chromium and Kmail are normally launched when I log in. They both use Kwallet. This situation always triggers the bug. However, if I shutdown Chromium or Kmail before I log out and start them manually after the next login, then everything works fine. In the first situation, when the bug is triggered, restarting Chromium, Akonadi, and/or Kmail doesn't help. What does help is aborting the mail fetch activities in Akonadi Console and killing the kwallet daemon. In previous versions (before 4.10), I could work around the problem by disabling the mail check at startup. In 4.10, Kmail asks for a password immediately when it is launched, so this workaround no longer works. -- 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 275483] kmail2 fails to download any messages
https://bugs.kde.org/show_bug.cgi?id=275483 --- Comment #6 from Patrick patr...@noxs.nl --- The password is indeed the one for the wallet. Without a password, everything works fine. I also noticed that when this bug is triggered, Kmail asks for the password at launch and for every account when it starts trying to fetch the mail. In situations where the bug isn't triggered, Kmail asks for the password only once (at launch). -- 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 255388] Kmail filters dont work in incoming mail
https://bugs.kde.org/show_bug.cgi?id=255388 Patrick patr...@noxs.nl changed: What|Removed |Added CC||patr...@noxs.nl --- Comment #70 from Patrick patr...@noxs.nl --- This bug appears to be valid in kmail2 4.9.4. I've got multiple mail accounts (POP3), all with their own inbox folder. I've setup a filter which moves certain messages from one of the accounts' inbox into a subfolder of the inbox folder. This filter should trigger on incoming messages, but it fails to do so. It only works manually on 'apply filter'. -- 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 309891] New: Filter buttons and context menu option are not shown
https://bugs.kde.org/show_bug.cgi?id=309891 Bug ID: 309891 Severity: normal Version: 4.9.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Filter buttons and context menu option are not shown Classification: Unclassified OS: Linux Reporter: patr...@noxs.nl Hardware: Archlinux Packages Status: UNCONFIRMED Component: UI Product: kmail2 The filter buttons (like spam and ham) in the toolbar and their equivalent context menu options are are not shown after login. Only after restarting kmail, the buttons and context menu options are shown. Reproducible: Always Steps to Reproduce: 1. Boot and login (kmail starts automatically). 2. Check the kmail toolbar and context menu. 3. Restart kmail. 4. Check the kmail toolbar and context menu again. Actual Results: At step 2, the toolbar shows no filter buttons en the context menu shows no filter actions. At step 4, the buttons and actions are shown as expected, Expected Results: At step2, the toolbar should show the filter buttons and the context menu should show the filter actions according the configuration. This appears to be a problem with akonadi being started by kmail. When akonadi is already running, kmail behaves as expected. Stopping akonadi and then starting kmail, always reproduces the problem. -- 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 304586] Crash when i click on Message brut to look at in in HTML
https://bugs.kde.org/show_bug.cgi?id=304586 Patrick Carabin patrick.cara...@gmail.com changed: What|Removed |Added CC||patrick.cara...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 304586] Crash when i click on Message brut to look at in in HTML
https://bugs.kde.org/show_bug.cgi?id=304586 --- Comment #1 from Patrick Carabin patrick.cara...@gmail.com --- Created attachment 72970 -- https://bugs.kde.org/attachment.cgi?id=72970action=edit New crash information added by DrKonqi kmail (4.8.4) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1 - What I was doing when the application crashed: after the bug 304586, i restarted kmail, and when i tried this ( other ) message, a got a dump. I assume they are linked? -- Backtrace (Reduced): #8 QSharedDataPointer (o=..., this=0xbfdae948) at ../../include/QtCore/../../src/corelib/tools/qshareddata.h:93 #9 QNetworkCacheMetaData::QNetworkCacheMetaData (this=0xbfdae948, other=...) at access/qabstractnetworkcache.cpp:137 #10 0xb5aa6a4f in QNetworkAccessHttpBackend::fetchCacheMetaData (this=0xb16b8c0, oldMetaData=...) at access/qnetworkaccesshttpbackend.cpp:1016 #11 0xb5aa827e in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0xb16b8c0, hm=..., sc=-1236254775, rp=..., pu=255, db=..., contentLength=-5353546593896078287) at access/qnetworkaccesshttpbackend.cpp:828 [...] -- 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 304586] Crash when i click on Message brut to look at in in HTML
https://bugs.kde.org/show_bug.cgi?id=304586 --- Comment #1 from Patrick Carabin patrick.cara...@gmail.com --- Created attachment 72970 -- https://bugs.kde.org/attachment.cgi?id=72970action=edit New crash information added by DrKonqi kmail (4.8.4) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1 - What I was doing when the application crashed: after the bug 304586, i restarted kmail, and when i tried this ( other ) message, a got a dump. I assume they are linked? -- Backtrace (Reduced): #8 QSharedDataPointer (o=..., this=0xbfdae948) at ../../include/QtCore/../../src/corelib/tools/qshareddata.h:93 #9 QNetworkCacheMetaData::QNetworkCacheMetaData (this=0xbfdae948, other=...) at access/qabstractnetworkcache.cpp:137 #10 0xb5aa6a4f in QNetworkAccessHttpBackend::fetchCacheMetaData (this=0xb16b8c0, oldMetaData=...) at access/qnetworkaccesshttpbackend.cpp:1016 #11 0xb5aa827e in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0xb16b8c0, hm=..., sc=-1236254775, rp=..., pu=255, db=..., contentLength=-5353546593896078287) at access/qnetworkaccesshttpbackend.cpp:828 [...] --- Comment #2 from Patrick Carabin patrick.cara...@gmail.com --- Created attachment 72971 -- https://bugs.kde.org/attachment.cgi?id=72971action=edit New crash information added by DrKonqi kmail (4.8.4) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1 - What I was doing when the application crashed: after the bug 304586, i restarted kmail, and when i tried this ( other ) message, a got a dump. I assume they are linked? -- Backtrace (Reduced): #8 QSharedDataPointer (o=..., this=0xbfdae948) at ../../include/QtCore/../../src/corelib/tools/qshareddata.h:93 #9 QNetworkCacheMetaData::QNetworkCacheMetaData (this=0xbfdae948, other=...) at access/qabstractnetworkcache.cpp:137 #10 0xb5aa6a4f in QNetworkAccessHttpBackend::fetchCacheMetaData (this=0xb16b8c0, oldMetaData=...) at access/qnetworkaccesshttpbackend.cpp:1016 #11 0xb5aa827e in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0xb16b8c0, hm=..., sc=-1236254775, rp=..., pu=255, db=..., contentLength=-5353546593896078287) at access/qnetworkaccesshttpbackend.cpp:828 [...] -- 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
