[kmail2] [Bug 485279] New: Drag-and-drop from the mail reader doesn't work for mails that consist of only the attachment
https://bugs.kde.org/show_bug.cgi?id=485279 Bug ID: 485279 Summary: Drag-and-drop from the mail reader doesn't work for mails that consist of only the attachment Classification: Applications Product: kmail2 Version: 5.24.5 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: m...@dblsaiko.net Target Milestone: --- SUMMARY Dragging a file out of the mail reader only creates a broken desktop entry for mails that have headers Content-Disposition: attachment. Mails containing DMARC reports from Google are formatted this way, for example. STEPS TO REPRODUCE 1. Open mail which consists only of the attachment 2. Drag attachment onto desktop OBSERVED RESULT It creates a file named "attachment:?place=body". When you try to open it, an error dialog saying "Could not read file attachment:?place=body." pops up. EXPECTED RESULT Drag-and-drop works like for attachments in a multipart email. SOFTWARE/OS VERSIONS Operating System: NixOS 24.05 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.6.22 (64-bit) Graphics Platform: Wayland Processors: 24 × 13th Gen Intel® Core™ i7-13700F Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 6800 XT ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 484574] New: Service Akonadi is not starting
https://bugs.kde.org/show_bug.cgi?id=484574 Bug ID: 484574 Summary: Service Akonadi is not starting Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: akonadiconsole Assignee: kdepim-bugs@kde.org Reporter: marco.fredu...@freduccibagarotti.eu CC: c...@carlschwan.eu Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Open KMail or KAddressBook 2. Service Akonadi is not working. This service is not start 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux distro: "KDE neon 6.0" Release:22.04 Codename: jammy Versione di KDE Plasma: 6.0.0 Versione di KDE Frameworks: 6.0.0 Versione di QT: 6.6.2 Piattaforma grafica:Wayland Hardware Processore grafico :Mesa Intel UHD Graphics 630 Nome del prodotto: HP Zbook 15 G5 Serial number: 5CD9206N5Z Operating system: Linux PC name: MARCO-HP.freduccibagarotti.eu.local Kernel version: 6.5.0-26-generic 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 ADDITIONAL INFORMATION I can to execute kmail application from terminal: qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "stateChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMState qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "connectivityChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMConnectivityState qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "deviceTypeChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMDeviceType qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "meteredChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMMetered Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadiserver: Starting up the Akonadi Server... org.kde.pim.akonadiserver: Did not find MySQL server default configuration (mysql-global.conf) org.kde.pim.akonadiserver: Shutting down AkonadiServer... org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally... qt.svg: :238:6: Could not resolve property: #linearGradient7814 qt.svg: :238:6: Could not resolve property: #linearGradient7814 qt.svg: :238:6: Could not resolve property: #linearGradient6730 org.kde.pim.akonadicore: Job error: "" for collection: QList() org.kde.pim.akonadicore: Job error: "" for collection: QList() org.kde.pim.messagelist: Failed to load tags "" org.kde.pim.kmail: "" org.kde.pim.mailcommon: failed to retrieve tags "" qt.svg: :238:6: Could not resolve property: #linearGradient7814 qt.svg: :238:6: Could not resolve property: #linearGradient7814 qt.svg: :238:6: Could not resolve property: #linearGradient6730 ^CShutting down... sudo akonadictl start QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' org.kde.pim.akonadictl: Starting Akonadi Server... org.kde.pim.akonadicontrol: Service org.freedesktop.Akonadi.Control.lock already registered, terminating now. Error: akonadi_control was started but didn't register at D-Bus session bus. Make sure your system is set up correctly! -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 430537] Cannot add EWS server
https://bugs.kde.org/show_bug.cgi?id=430537 --- Comment #2 from Marco Schmidlin --- Happens to me on Kubuntu 23.04. Is there any more details that needs to be provided? Seeing that there are major changes on the way for KF6, will those address the several issues for Office365 support? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 430537] Cannot add EWS server
https://bugs.kde.org/show_bug.cgi?id=430537 Marco Schmidlin changed: What|Removed |Added CC||ner...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402780] Akonadi doesn't work with Exchange again
https://bugs.kde.org/show_bug.cgi?id=402780 Marco Schmidlin changed: What|Removed |Added CC||ner...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 468185] New: KAdressbook crashes when opened
https://bugs.kde.org/show_bug.cgi?id=468185 Bug ID: 468185 Summary: KAdressbook crashes when opened Classification: Applications Product: kaddressbook Version: 5.19.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ma...@trunzerweb.de CC: to...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Opening KAddressbook from KMail menu 2. KAddessbook crashes 3. It also crashes immediately after displaying the window when calling from command line of a shell OBSERVED RESULT Crash EXPECTED RESULT No Crash ;-) Application: kaddressbook (5.19.3 (21.12.3)) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.14.21-150400.24.46-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.4" DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Opening KAddressbook from KMail menu I think I scrolled a little bit through the contacts, but it crashes also just after opning. I assume it has to do with the contacts and otentially with contact groups that are stored. The crash can be reproduced every time. -- Backtrace: Application: KAddressBook (kaddressbook), signal: Aborted [KCrash Handler] #4 0x7fb1f1842c6b in raise () from /lib64/libc.so.6 #5 0x7fb1f1844305 in abort () from /lib64/libc.so.6 #6 0x7fb1f1cb5675 in ?? () from /usr/lib64/libstdc++.so.6 #7 0x7fb1f1cc0d0c in ?? () from /usr/lib64/libstdc++.so.6 #8 0x7fb1f1cc0d77 in std::terminate() () from /usr/lib64/libstdc++.so.6 #9 0x7fb1f1cc0fd8 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #10 0x7fb1ef212946 in Akonadi::Item::throwPayloadException(int, int) const () from /usr/lib64/libKF5AkonadiCore.so.5 #11 0x7fb1f4f33cb3 in Akonadi::Item::payloadImpl (this=0x7fb19c05d6b8) at /usr/include/KF5/AkonadiCore/akonadi/item.h:793 #12 0x7fb1f4f3ca52 in Akonadi::Item::payload (this=this@entry=0x7fb19c05d6b8) at /usr/include/KF5/AkonadiCore/akonadi/item.h:768 #13 0x7fb1f4f382d3 in ContactInfoProxyModel::ContactCacheData::setData (this=0x55c35ce0b6c8, item=...) at /usr/src/debug/kaddressbook-21.12.3-bp154.1.22.x86_64/src/contactinfoproxymodel.cpp:365 #14 0x7fb1f4f3a0a2 in ContactInfoProxyModel::slotFetchJobFinished (this=0x55c35cd35630, job=) at /usr/src/debug/kaddressbook-21.12.3-bp154.1.22.x86_64/src/contactinfoproxymodel.cpp:292 #15 0x7fb1f234c1c7 in QtPrivate::QSlotObjectBase::call (a=0x7ffcc2165790, r=0x55c35cd35630, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x55c35cf97dc0, signal_index=6, argv=0x7ffcc2165790) at kernel/qobject.cpp:3886 #17 0x7fb1f2345782 in QMetaObject::activate (sender=sender@entry=0x55c35cf97dc0, m=m@entry=0x7fb1f42736e0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffcc2165790) at kernel/qobject.cpp:3946 #18 0x7fb1f4020f7c in KJob::result (this=this@entry=0x55c35cf97dc0, _t1=, _t1@entry=0x55c35cf97dc0, _t2=...) at /usr/src/debug/kcoreaddons-5.90.0-150400.3.2.3.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #19 0x7fb1f4022481 in KJob::finishJob (this=0x55c35cf97dc0, emitResult=) at /usr/src/debug/kcoreaddons-5.90.0-150400.3.2.3.x86_64/src/lib/jobs/kjob.cpp:98 #20 0x7fb1f2342d9b in QObject::event (this=0x55c35cf97dc0, e=0x55c35cf99310) at kernel/qobject.cpp:1314 #21 0x7fb1f32c73bc in QApplicationPrivate::notify_helper (this=this@entry=0x55c35c752860, receiver=receiver@entry=0x55c35cf97dc0, e=e@entry=0x55c35cf99310) at kernel/qapplication.cpp:3632 #22 0x7fb1f32ce1a0 in QApplication::notify (this=0x7ffcc2165e20, receiver=0x55c35cf97dc0, e=0x55c35cf99310) at kernel/qapplication.cpp:3156 #23 0x7fb1f230ec23 in QCoreApplication::notifyInternal2 (receiver=0x55c35cf97dc0, event=0x55c35cf99310) at kernel/qcoreapplication.cpp:1064 #24 0x7fb1f230edfe in QCoreApplication::sendEvent (receiver=receiver@entry=0x55c35cf97dc0, event=event@entry=0x55c35cf99310) at kernel/qcoreapplication.cpp:1462 #25 0x7fb1f2311641 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55c35c7304b0) at kernel/qcoreapplication.cpp:1821 #26 0x7fb1f2311bc8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680 #27 0x7fb1f2371983 in postEventSourceDispatch (s=0x55c35c8a1530) at kernel/qeventdispatcher_glib.cpp:277 #28 0x7fb1ea07582b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #29 0x7fb1ea075bd0 in
[kmail2] [Bug 457346] KMail crashes when typing in "Find Action"
https://bugs.kde.org/show_bug.cgi?id=457346 --- Comment #2 from Marco --- Created attachment 157362 --> https://bugs.kde.org/attachment.cgi?id=157362=edit New crash information added by DrKonqi kmail (5.22.3 (22.12.3)) using Qt 5.15.8 After clicking on Help and Find Action, I tried to insert text as soon as I entered the first character Kmail crashed -- Backtrace (Reduced): #4 0x7f8b99ba8d03 in QAction::text() const () from /lib64/libQt5Widgets.so.5 #5 0x7f8b96db5949 in KCommandBarModel::Item::displayName() const () from /lib64/libKF5ConfigWidgets.so.5 #6 0x7f8b96db6610 in KCommandBarModel::data(QModelIndex const&, int) const () from /lib64/libKF5ConfigWidgets.so.5 #7 0x7f8b96daa574 in CommandBarFilterModel::filterAcceptsRow(int, QModelIndex const&) const () from /lib64/libKF5ConfigWidgets.so.5 #8 0x7f8b98e7935f in QSortFilterProxyModelPrivate::create_mapping(QModelIndex const&) const () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 457346] KMail crashes when typing in "Find Action"
https://bugs.kde.org/show_bug.cgi?id=457346 Marco changed: What|Removed |Added CC||marco.tall...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 446579] Kontact crashes when I go to "Contacts"
https://bugs.kde.org/show_bug.cgi?id=446579 --- Comment #3 from Marco --- Created attachment 155116 --> https://bugs.kde.org/attachment.cgi?id=155116=edit New crash information added by DrKonqi kaddressbook (5.19.3 (21.12.3)) using Qt 5.15.2 - What I was doing when the application crashed: starting contact (either from kmail menu entry or as kaddressbook from command line - see separate comment) -- Backtrace (Reduced): #10 0x7fd5d13ba946 in Akonadi::Item::throwPayloadException(int, int) const () from /usr/lib64/libKF5AkonadiCore.so.5 #11 0x7fd5d7273cb3 in Akonadi::Item::payloadImpl (this=0x7fd57805d468) at /usr/include/KF5/AkonadiCore/akonadi/item.h:793 #12 0x7fd5d727ca52 in Akonadi::Item::payload (this=this@entry=0x7fd57805d468) at /usr/include/KF5/AkonadiCore/akonadi/item.h:768 #13 0x7fd5d72782d3 in ContactInfoProxyModel::ContactCacheData::setData (this=0x5647339ea868, item=...) at /usr/src/debug/kaddressbook-21.12.3-bp154.1.22.x86_64/src/contactinfoproxymodel.cpp:365 #14 0x7fd5d727a0a2 in ContactInfoProxyModel::slotFetchJobFinished (this=0x5647339ffa50, job=) at /usr/src/debug/kaddressbook-21.12.3-bp154.1.22.x86_64/src/contactinfoproxymodel.cpp:292 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 446579] Kontact crashes when I go to "Contacts"
https://bugs.kde.org/show_bug.cgi?id=446579 Marco changed: What|Removed |Added CC||ma...@trunzerweb.de --- Comment #2 from Marco --- Additional info to this new crash information: When starting kaddressbook from command line: --- marco@localhost:~> kaddressbook terminate called after throwing an instance of 'Akonadi::PayloadException' what(): Akonadi::PayloadException: Wrong payload type (requested: sp(0); present: sp(2)) KCrash: Application 'kaddressbook' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi [1]+ Angehalten kaddressbook --- -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 462362] New: Memory leak in akonadi_ical_resource with remote calendars
https://bugs.kde.org/show_bug.cgi?id=462362 Bug ID: 462362 Summary: Memory leak in akonadi_ical_resource with remote calendars Classification: Frameworks and Libraries Product: Akonadi Version: 5.21.3 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ICal file resource Assignee: kdepim-bugs@kde.org Reporter: m...@dblsaiko.net Target Milestone: --- Created attachment 154116 --> https://bugs.kde.org/attachment.cgi?id=154116=edit Debugger log for akonadi_ical_resource SUMMARY One of the iCal URLs I have connected to Akonadi refreshes every about 3 seconds and seems to leak memory in the agent process (about 300kB) every time it does, eventually causing the system to lock up if not restarted (no idea why instead of the process getting OOM killed, as I do not have any swap). This does not happen for the other iCal URL resource, it refreshes without leaking memory. I attached the log from Akonadi Console for the agent (removed the URL for the calendar). Additionally, every time it refreshes, this gets printed to stdout: > kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "%1, > %2" msgid_plural: "" msgctxt: "Two statuses, for example \"Online, Running > (66%)\" or \"Offline, Broken\"" > kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "%1, > %2" msgid_plural: "" msgctxt: "Two statuses, for example \"Online, Running > (66%)\" or \"Offline, Broken\"" > kf.i18n: KLocalizedString: Using an empty domain, fix the code. msgid: "%1, > %2" msgid_plural: "" msgctxt: "Two statuses, for example \"Online, Running > (66%)\" or \"Offline, Broken\"" > The hash has changed. STEPS TO REPRODUCE 1. Honestly, I have no idea, since it only occurs with one calendar I'm subscribed to. OBSERVED RESULT On every refresh (visible from Akonadi Console) the memory usage of akonadi_ical_resource process increases. EXPECTED RESULT akonadi_ical_resource memory usage should not grow indefinitely. SOFTWARE/OS VERSIONS Operating System: NixOS 22.11 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 5.15.79 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 23.4 GiB of RAM Graphics Processor: AMD Radeon RX Vega ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 450554] Deleting an event from a Google calendar does not delete it on the Google server
https://bugs.kde.org/show_bug.cgi?id=450554 Marco changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 450554] New: Deleting an event from a Google calendar does not delete it on the Google server
https://bugs.kde.org/show_bug.cgi?id=450554 Bug ID: 450554 Summary: Deleting an event from a Google calendar does not delete it on the Google server Product: kdepim Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: phoenix_8...@hotmail.com Target Milestone: --- SUMMARY As from the title. STEPS TO REPRODUCE 1. Configure a google groupware calendar with kdepim 2. Access the calendar with any app supporting kdepim (e.g., KOrganizer, Kalendar) 3. Select an event and delete it OBSERVED RESULT The event gets deleted on the local machine but persists online. If I force the calendar app to fetch again the online calendar, the event is back locally. EXPECTED RESULT The event should also be removed from the online Google calendar SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 35 (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91 Qt Version: ADDITIONAL INFORMATION Adding events works fine. They also appear on the online Google server when added via Kalendar/KOrganizer. I am using kdepim-runtime 21.12.2 with the latest Google calendar patch: https://bugs.kde.org/show_bug.cgi?id=449024 Without this patch, events would not even show up in Kalendar/KOrganizer. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 449341] New: ading a new entry in the calender
https://bugs.kde.org/show_bug.cgi?id=449341 Bug ID: 449341 Summary: ading a new entry in the calender Product: korganizer Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: huiky2...@yahoo.com Target Milestone: --- Application: korganizer (5.18.3 (21.08.3)) Qt Version: 5.15.2 Frameworks Version: 5.89.0 Operating System: Linux 5.15.16-200.fc35.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 35 (KDE Plasma) DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: wen ading a new calendar entry and keeps doing it on and off sometimes only The crash can be reproduced sometimes. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Content of s_kcrashErrorMessage: std::unique_ptr = {get() = } [KCrash Handler] #6 0x7fd78d3e193e in QSortFilterProxyModelPrivate::proxy_to_source (this=0x5604dfb4bac0, proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:572 #7 0x7fd78d3e37a9 in QSortFilterProxyModel::mapToSource (proxyIndex=..., this=0x5604df3d8b00) at itemmodels/qsortfilterproxymodel.cpp:3171 #8 QSortFilterProxyModelPrivate::store_persistent_indexes (this=) at itemmodels/qsortfilterproxymodel.cpp:1248 #9 0x7fd78d3e594b in QSortFilterProxyModelPrivate::_q_sourceLayoutAboutToBeChanged (this=0x5604dfb4bac0, sourceParents=..., hint=) at itemmodels/qsortfilterproxymodel.cpp:1639 #10 0x7fd78d43c430 in doActivate (sender=0x5604e00dcb70, signal_index=9, argv=0x7ffe382da040) at kernel/qobject.cpp:3898 #11 0x7fd78d437367 in QMetaObject::activate (sender=sender@entry=0x5604e00dcb70, m=m@entry=0x7fd78d6df940 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7ffe382da040) at kernel/qobject.cpp:3946 #12 0x7fd78d3b9a7a in QAbstractItemModel::layoutAboutToBeChanged (this=this@entry=0x5604e00dcb70, _t1=..., _t2=, _t2@entry=QAbstractItemModel::NoLayoutChangeHint) at .moc/moc_qabstractitemmodel.cpp:578 #13 0x7fd78cbc0a84 in IncidenceEditorNG::AttendeeTableModel::setAttendees (attendees=..., this=0x5604e00dcb70) at /usr/src/debug/kf5-incidenceeditor-21.08.3-1.fc35.x86_64/src/attendeetablemodel.cpp:212 #14 IncidenceEditorNG::IncidenceAttendee::load (this=0x5604e00dc410, incidence=...) at /usr/src/debug/kf5-incidenceeditor-21.08.3-1.fc35.x86_64/src/incidenceattendee.cpp:186 #15 0x7fd78cbb28d8 in IncidenceEditorNG::CombinedIncidenceEditor::load (this=this@entry=0x5604dfaa4cd0, incidence=...) at /usr/src/debug/kf5-incidenceeditor-21.08.3-1.fc35.x86_64/src/combinedincidenceeditor.cpp:83 #16 0x7fd78cc0cd10 in IncidenceEditorNG::IncidenceDialogPrivate::handleItemSaveFinish (saveAction=IncidenceEditorNG::EditorItemManager::Create, this=0x5604dfa8e500) at /usr/src/debug/kf5-incidenceeditor-21.08.3-1.fc35.x86_64/src/incidencedialog.cpp:478 #17 IncidenceEditorNG::IncidenceDialog::qt_static_metacall (_o=, _c=, _id=, _a=) at /usr/src/debug/kf5-incidenceeditor-21.08.3-1.fc35.x86_64/redhat-linux-build/src/KF5IncidenceEditor_autogen/include/moc_incidencedialog.cpp:156 #18 0x7fd78d43c430 in doActivate (sender=0x5604df9ccaf0, signal_index=3, argv=0x7ffe382da390) at kernel/qobject.cpp:3898 #19 0x7fd78d437367 in QMetaObject::activate (sender=sender@entry=0x5604df9ccaf0, m=m@entry=0x7fd78cc43220 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe382da390) at kernel/qobject.cpp:3946 #20 0x7fd78cbb1e33 in IncidenceEditorNG::EditorItemManager::itemSaveFinished (_t1=IncidenceEditorNG::EditorItemManager::Create, this=0x5604df9ccaf0) at /usr/src/debug/kf5-incidenceeditor-21.08.3-1.fc35.x86_64/redhat-linux-build/src/KF5IncidenceEditor_autogen/include/moc_editoritemmanager.cpp:267 #21 IncidenceEditorNG::ItemEditorPrivate::itemFetchResult (job=, this=0x5604dfa8e8f0) at /usr/src/debug/kf5-incidenceeditor-21.08.3-1.fc35.x86_64/src/editoritemmanager.cpp:123 #22 IncidenceEditorNG::EditorItemManager::qt_static_metacall (_o=, _c=, _id=, _a=) at /usr/src/debug/kf5-incidenceeditor-21.08.3-1.fc35.x86_64/redhat-linux-build/src/KF5IncidenceEditor_autogen/include/moc_editoritemmanager.cpp:131 #23 0x7fd78d43c430 in doActivate (sender=0x5604df314d10, signal_index=6, argv=0x7ffe382da4e0) at kernel/qobject.cpp:3898 #24 0x7fd78d437367 in QMetaObject::activate (sender=sender@entry=0x5604df314d10, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffe382da4e0) at kernel/qobject.cpp:3946 #25 0x7fd78e585450 in KJob::result (this=this@entry=0x5604df314d10, _t1=, _t1@entry=0x5604df314d10, _t2=...) at /usr/src/debug/kf5-kcoreaddons-5.89.0-1.fc35.x86_64/redhat-linux-build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #26 0x7fd78e589abb in KJob::finishJob (this=0x5604df314d10,
[korganizer] [Bug 444686] New: Wayland (?): Agenda view slows down when moving the mouse
https://bugs.kde.org/show_bug.cgi?id=444686 Bug ID: 444686 Summary: Wayland (?): Agenda view slows down when moving the mouse Product: korganizer Version: GIT (master) Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-bugs@kde.org Reporter: m...@dblsaiko.net Target Milestone: --- SUMMARY On my 150% scaled display, moving the mouse over KOrganizer's agenda view makes it take noticeably long to update, most visible by the red line on the timeline that shows where the mouse is moving like the mouse was moved but delayed. It seems to process every mouse move event even if new ones have already come in which makes it take a long time to become responsive again if you moved the mouse around a lot. The issue occurs similarly but way less severely when moving KOrganizer over to my 100% scaled display. There, just moving the mouse around makes it behave normally but dragging to select cells still has the same problem. (I'm assuming it's just not taking as long to redraw the window there so it's less noticeable.) I put "Wayland (?)" in the title because I'm not exactly sure if this is Wayland-specific, I noticed it first when I switched to Wayland though and haven't tried X11 since. STEPS TO REPRODUCE 1. (optional) Set display scale to 150% 2. Open agenda view 3. Move/drag mouse around on the table OBSERVED RESULT The UI slows down, taking longer to regain responsiveness the more you moved the mouse around. EXPECTED RESULT The UI stays responsive. SOFTWARE/OS VERSIONS Operating System: Gentoo 2.8 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-gentoo-dist (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 23.4 GiB of RAM Graphics Processor: Radeon RX Vega ADDITIONAL INFORMATION KOrganizer commit 7ab02ec -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 444684] New: Adding a VCALENDAR by URL makes it not sync unless you manually restart the ical resource agent
https://bugs.kde.org/show_bug.cgi?id=444684 Bug ID: 444684 Summary: Adding a VCALENDAR by URL makes it not sync unless you manually restart the ical resource agent Product: korganizer Version: GIT (master) Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: import/export Assignee: kdepim-bugs@kde.org Reporter: m...@dblsaiko.net Target Milestone: --- SUMMARY I was trying to add a Moodle calendar to KOrganizer, which gives you a calendar URL in VCALENDAR format. After adding it as an "iCal Calendar File" via the URL, it creates an empty calendar called "akonadi_ical_resource_n" (where n is a number). Neither syncing the calendar nor restarting KOrganizer nor restarting Akonadi populates it. I tried messing around with it in Akonadi Console and found that restarting the ical agent for the calendar makes it sort of work: it creates another calendar with the actual name I gave it in the add dialog which has all the entries in it, but the old "akonadi_ical_resource_n" one stays and trying to remove it to clean it up because it's useless takes the actual calendar with it, probably because they are owned by the same agent. (I ended up clearing out all the content types in the Internals tab, yes, the one that says "Do not even think about changing anything in here!" ;), to make it at least not show up anymore.) STEPS TO REPRODUCE 1. Add a VCALENDAR URL via the iCal type, optionally give it a name 2. The added calendar doesn't have the name you input and it doesn't sync either 3. Restart the agent in Akonadi Console to have the actual calendar show up but the empty one stay OBSERVED RESULT The added calendar ignores the name you gave it and never gets populated. EXPECTED RESULT The added calendar populates with the data behind the URL. SOFTWARE/OS VERSIONS Operating System: Gentoo 2.8 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-gentoo-dist (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 23.4 GiB of RAM Graphics Processor: Radeon RX Vega ADDITIONAL INFORMATION KOrganizer commit 7ab02ec Akonadi commit 21dc82c -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 428762] Akonadi is asking for gmail authentication every 10ish minutes?
https://bugs.kde.org/show_bug.cgi?id=428762 --- Comment #21 from Marco Albanese --- Could it be related with bug 429406 ? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 428762] Akonadi is asking for gmail authentication every 10ish minutes?
https://bugs.kde.org/show_bug.cgi?id=428762 Marco Albanese changed: What|Removed |Added CC||deli...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 425053] New: Akonadi_indexing_agent crash on boot
https://bugs.kde.org/show_bug.cgi?id=425053 Bug ID: 425053 Summary: Akonadi_indexing_agent crash on boot Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: deli...@gmail.com Target Milestone: --- Application: akonadi_indexing_agent (5.14.3 (20.04.3)) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.7.12-arch1-1 x86_64 Windowing system: X11 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was just starting the kde session and the icon af the crash was in the sys tray The crash can be reproduced every time. -- Backtrace: Application: akonadi_indexing_agent (akonadi_indexing_agent), signal: Aborted [KCrash Handler] #4 0x7f72d6ff3355 in raise () at /usr/lib/libc.so.6 #5 0x7f72d6fdc853 in abort () at /usr/lib/libc.so.6 #6 0x7f72d723086a in __gnu_cxx::__verbose_terminate_handler() () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #7 0x7f72d723cd8a in __cxxabiv1::__terminate(void (*)()) (handler=) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #8 0x7f72d723cdf7 in std::terminate() () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #9 0x7f72d723d09e in __cxxabiv1::__cxa_throw(void*, std::type_info*, void (*)(void*)) (obj=obj@entry=0x55c12227e6c0, tinfo=0x7f72d8cb6770 , tinfo@entry=0x7f72d8c40850 , dest=dest@entry=0x7f72d8adc430 ) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95 #10 0x7f72d8a70f80 in GlassTable::set_overwritten() const (this=this@entry=0x55c12240e020) at /usr/include/c++/10.1.0/ext/new_allocator.h:89 #11 0x7f72d8a712be in GlassTable::block_to_cursor(Glass::Cursor*, int, unsigned int) const (this=0x55c12240e020, C_=0x55c12240e0e8, j=, n=12414) at backends/glass/glass_table.cc:335 #12 0x7f72d8b34c75 in GlassTable::find(Glass::Cursor*) const (this=this@entry=0x55c12240e020, C_=C_@entry=0x55c12240e0e8) at ./common/wordaccess.h:57 #13 0x7f72d8b35321 in GlassTable::get_exact_entry(std::__cxx11::basic_string, std::allocator > const&, std::__cxx11::basic_string, std::allocator >&) const (this=this@entry=0x55c12240e020, key="C32", tag="") at backends/glass/glass_table.cc:1482 #14 0x7f72d8b256e8 in GlassPostListTable::get_freqs(std::__cxx11::basic_string, std::allocator > const&, unsigned int*, unsigned int*, unsigned int*) const (this=0x55c12240e020, term=..., termfreq_ptr=0x7ffd27212f08, collfreq_ptr=0x7ffd27212f0c, wdfub_ptr=0x0) at backends/glass/glass_postlist.cc:159 #15 0x7f72d8bc17d1 in Xapian::Weight::Internal::accumulate_stats(Xapian::Database::Internal const&, Xapian::RSet const&) (this=0x55c122407450, subdb=..., rset=...) at weight/weightinternal.cc:91 #16 0x7f72d8b804d8 in LocalSubMatch::prepare_match(bool, Xapian::Weight::Internal&) (this=, nowait=, total_stats=...) at matcher/localsubmatch.cc:172 #17 0x7f72d8b88851 in prepare_sub_matches (stats=..., leaves=std::vector of length 1, capacity 1 = {...}) at matcher/multimatch.cc:237 #18 MultiMatch::MultiMatch(Xapian::Database const&, Xapian::Query const&, unsigned int, Xapian::RSet const*, unsigned int, unsigned int, int, double, Xapian::Enquire::docid_order, unsigned int, Xapian::Enquire::Internal::sort_setting, bool, double, Xapian::Weight::Internal&, Xapian::Weight const*, std::vector, std::allocator > > const&, bool, bool) (this=0x7ffd27213180, db_=..., query_=..., qlen=, omrset=0x0, collapse_max_=, collapse_key_=4294967295, percent_cutoff_=0, weight_cutoff_=, order_=Xapian::Enquire::ASCENDING, sort_key_=4294967295, sort_by_=Xapian::Enquire::Internal::REL, sort_value_forward_=true, time_limit_=, stats=..., weight_=0x55c122412150, matchspies_=std::vector of length 0, capacity 0, have_sorter=false, have_mdecider=false) at matcher/multimatch.cc:353 #19 0x7f72d8a97d66 in Xapian::Enquire::Internal::get_mset(unsigned int, unsigned int, unsigned int, Xapian::RSet const*, Xapian::MatchDecider const*) const (this=0x7f72c0008790, first=0, maxitems=44788, check_at_least=, rset=0x0, mdecider=0x0) at ./include/xapian/intrusive_ptr.h:352 #20 0x7f72d8a98016 in Xapian::Enquire::get_mset(unsigned int, unsigned int, unsigned int, Xapian::RSet const*, Xapian::MatchDecider const*) const (this=this@entry=0x7ffd27213350, first=first@entry=0, maxitems=maxitems@entry=4294967295, check_at_least=check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at ./include/xapian/intrusive_ptr.h:165 #21 0x7f72d8c965fd in Akonadi::Search::PIM::IndexedItemsPrivate::findIndexedInDatabase(QSet&, long long, QString const&) (this=, indexed=..., collectionId=, dbPath=...) at /usr/src/debug/akonadi-search-20.04.3/lib/indexeditems.cpp:163 #22 0x7f72d8c969d1 in
[kmail2] [Bug 423912] New: Change email background to white when using dark mode
https://bugs.kde.org/show_bug.cgi?id=423912 Bug ID: 423912 Summary: Change email background to white when using dark mode Product: kmail2 Version: 5.14.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: deli...@gmail.com Target Milestone: --- Created attachment 129922 --> https://bugs.kde.org/attachment.cgi?id=129922=edit Example of a background-less html email on a dark theme It would be really helpful to have a switch per email to temporary change the background to white when using a dark theme, since some email are designed ( wrongly ) assuming the background is white and they are difficult to read in this way. STEPS TO REPRODUCE 1. Set a "dark" theme 2. Open an HTML email with trasparent (or no ) background which assume a white default background OBSERVED RESULT The background of the email is the one from the dark theme, but the email is not designed for it EXPECTED RESULT There is an option to temporary set the email background to white ( IIRC I've seen something similar in the gmail android app ). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422469] Akonadiserver Crashes
https://bugs.kde.org/show_bug.cgi?id=422469 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Product|plasmashell |Akonadi Version|5.18.5 |unspecified Component|generic-crash |general Assignee|plasma-b...@kde.org |kdepim-bugs@kde.org Target Milestone|1.0 |--- -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 416885] Encoding gets lost
https://bugs.kde.org/show_bug.cgi?id=416885 Marco changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #2 from Marco --- Thanks. That was it. Issue can be closed from my point of view. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 416887] New: In multipart plain text/HTML messages the possibility to switch to HTML is not displayed
https://bugs.kde.org/show_bug.cgi?id=416887 Bug ID: 416887 Summary: In multipart plain text/HTML messages the possibility to switch to HTML is not displayed Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ma...@trunzerweb.de Target Milestone: --- Created attachment 125504 --> https://bugs.kde.org/attachment.cgi?id=125504=edit The plain code of an example message SUMMARY In former versions (that from OpenSuSE Leap 15.0 or 42.0 for example) when I received an email with both plain text and HTML the text was displayed, but at the bottom there was a possibility to select the HTML. Now I do not have the possibility to select HTML. As often the plain text does not really contain the content, I cannot read the email anymore then. OBSERVED RESULT Only text content is displayed with no possibility to select HTML part. EXPECTED RESULT Possibility to select the HTML part 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 416885] New: Encoding gets lost
https://bugs.kde.org/show_bug.cgi?id=416885 Bug ID: 416885 Summary: Encoding gets lost Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ma...@trunzerweb.de Target Milestone: --- SUMMARY After every tool start the message encoding (for the window displaying the selected message) in menu Ansicht/Kodierung festlegen... (Germanversion; I would expect something like View/Encoding) is set to "Baltisch" ("Baltic"). i always have to set it to "Automatisch" ("Automatic") manually. At the next restart (after rebooting) the setting is lost again. I could not find another setting to det the enclding besides the mentioned menu entry. STEPS TO REPRODUCE 1. Start kmail OBSERVED RESULT Encoding is set to Baltic EXPECTED RESULT Encoding is set like it was during closing, i. e. "Automatic" in my case. 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.
[kontact] [Bug 399196] Kontact crash when trying to import calendar (search)
https://bugs.kde.org/show_bug.cgi?id=399196 Marco Richetta changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 399196] Kontact crash when trying to import calendar (search)
https://bugs.kde.org/show_bug.cgi?id=399196 Marco Richetta changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Marco Richetta --- I described the issues I have trying to provide the backtrace. If that's not enough please let me know so I can keep trying on debugging. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 399196] Kontact crash when trying to import calendar (search)
https://bugs.kde.org/show_bug.cgi?id=399196 --- Comment #3 from Marco Richetta --- Hi! After posting the bug I changed to the language of Kontact from Spanish to English to make sure I correctly explained the steps. After that change I can't open Kontact anymore because it crashes everytime. Anyway, I tried to generate the backtrace or at least provide some useful debugging info. GDB === > gdb kontact > gdb run [Depuración de hilo usando libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Nuevo Thread 0x7fffc89f0700 (LWP 10767)] "Here are 22 more memory addresses" KSycoca unavailable. Kontact will be unable to find plugins. Thread 1 "kontact" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. KONTACT === Trying to open kontact normally pops up a notification of the crash. On the crash handler, I go to Developer Information and generate the backtrace. It has some records like this #1 0x7f585b966747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 It provides me a list of packages that can help on provide better information but I don't understand what I have to install. This is the list: /usr/bin/kontact /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 /usr/lib/x86_64-linux-gnu/libkontactprivate.so.5 I installed kdelibs5-dbg like it says on the Guideline, then searched for dbg packages for kontact or Qt5 but I'm not sure what to install. I hope this may be helpful. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 399196] New: Kontact crash when trying to import calendar (search)
https://bugs.kde.org/show_bug.cgi?id=399196 Bug ID: 399196 Summary: Kontact crash when trying to import calendar (search) Product: kontact Version: 5.7.3 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: calendar Assignee: kdepim-bugs@kde.org Reporter: marcoriche...@gmail.com Target Milestone: --- Created attachment 115301 --> https://bugs.kde.org/attachment.cgi?id=115301=edit Before typing for search. SUMMARY When trying to import a new calendar, Kontact crashes just after you type a letter on the search box. STEPS TO REPRODUCE 1. Kontact 2. Calendar 3. File - Import - Obtain new (I have it in Spanish so I don't know the real translation on English) 4. Type on the search box. OBSERVED RESULT Attached on the image EXPECTED RESULT Calendars that match your search SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION If you open KOrganizer directly, the functionality is correct. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 397944] System Tray - KOrganizer and Daemon are hard to disable
https://bugs.kde.org/show_bug.cgi?id=397944 Marco Martin changed: What|Removed |Added Target Milestone|1.0 |--- CC||notm...@gmail.com Assignee|plasma-b...@kde.org |kdepim-bugs@kde.org Product|plasmashell |korganizer Version|5.13.4 |unspecified Component|System Tray |general -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 377485] regression: system tray icon no longer shows number of unread articles
https://bugs.kde.org/show_bug.cgi?id=377485 Marco Mattiolo <marco.matti...@hotmail.it> changed: What|Removed |Added CC||marco.matti...@hotmail.it -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 389919] Kleopatra crashes on sign / encrypt with redirected %appdata%
https://bugs.kde.org/show_bug.cgi?id=389919 --- Comment #2 from Marco <marco.gerv...@kklh.ch> --- Maybe the following is helpful: FAULTING_IP: kleopatra+5216 00405216 8b10mov edx,dword ptr [eax] EXCEPTION_RECORD: -- (.exr 0x) ExceptionAddress: 00405216 (kleopatra+0x5216) ExceptionCode: c005 (Access violation) ExceptionFlags: NumberParameters: 2 Parameter[0]: Parameter[1]: Attempt to read from address CONTEXT: -- (.cxr 0x0;r) eax= ebx=0360 ecx= edx=6aa77760 esi=02e5 edi=0028c420 eip=77d7d10c esp=0028c3bc ebp=0028c3f8 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=0202 ntdll!NtGetContextThread+0xc: 77d7d10c c20800 ret 8 DEFAULT_BUCKET_ID: NULL_POINTER_READ PROCESS_NAME: kleopatra.exe ERROR_CODE: (NTSTATUS) 0xc005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden. EXCEPTION_CODE: (NTSTATUS) 0xc005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden. EXCEPTION_PARAMETER1: EXCEPTION_PARAMETER2: READ_ADDRESS: FOLLOWUP_IP: kleopatra+5216 00405216 8b10mov edx,dword ptr [eax] NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 APP: kleopatra.exe ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre FAULTING_THREAD: 663c PRIMARY_PROBLEM_CLASS: NULL_POINTER_READ BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_READ LAST_CONTROL_TRANSFER: from 0053b002 to 00405216 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 0028d058 0053b002 006ec806 003d08fc kleopatra+0x5216 0028d1b8 004f57b3 0028d2c8 kleopatra+0x13b002 0028d248 0061c4e2 0002 004d kleopatra+0xf57b3 0028d2c8 0060bcab 0028d2ec fffe 776bb106 kleopatra+0x21c4e2 0028d358 0060d80f 0028d37c kleopatra+0x20bcab 0028d3d8 66b2d78e 0001 02d6af70 0365e448 kleopatra+0x20d80f 0028d4f8 025482bf 0028d770 0028d770 Qt5Core!ZN15QSocketNotifier5eventEP6QEvent+0x21e 0028d508 6d0d3014 001c 0028d61c 0009 Qt5Widgets!ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8f libgcc_s_sjlj_1!Unwind_SjLj_Unregister+0x34 STACK_COMMAND: ~0s; .ecxr ; kb SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: kleopatra+5216 FOLLOWUP_NAME: MachineOwner MODULE_NAME: kleopatra IMAGE_NAME: kleopatra.exe DEBUG_FLR_IMAGE_TIMESTAMP: 409 FAILURE_BUCKET_ID: NULL_POINTER_READ_c005_kleopatra.exe!Unknown BUCKET_ID: APPLICATION_FAULT_NULL_POINTER_READ_kleopatra+5216 ANALYSIS_SOURCE: UM FAILURE_ID_HASH_STRING: um:null_pointer_read_c005_kleopatra.exe!unknown FAILURE_ID_HASH: {12cee584-1682-698c-b1f8-5a9efd0fae34} Followup: MachineOwner -- You are receiving this mail because: You are on the CC list for the bug.
[kleopatra] [Bug 389919] Kleopatra crashes on sign / encrypt with redirected %appdata%
https://bugs.kde.org/show_bug.cgi?id=389919 Marco <marco.gerv...@kklh.ch> changed: What|Removed |Added CC||marco.gerv...@kklh.ch --- Comment #1 from Marco <marco.gerv...@kklh.ch> --- We use GnuPG4Win with kleopatra 3.0.3 and it seems that we have the same problem. keo-log says: Got unexpected locking error 161 couldn't lock local file 0x5f20788 -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account
https://bugs.kde.org/show_bug.cgi?id=364802 --- Comment #11 from Marco Gamberoni <gamber...@libero.it> --- Some details from akonadiconsole when the bug is here, after a resuming (cannot say suspend in ram has something to do with the bug, but could.) After copying the info below, "Abort activity" does not stop task 24652, "Toggle Online/Offline" does. No idea of how to go from this info to the relevant source code. Hints? == akonadikonsole, resource task list for akonadi_imap_resource_3 has: __ ResourceScheduler: Online current task: 24652 SyncCollectionAttributes collection 52 queue 0 is empty queue 1 1 tasks: 24667 ChangeReplay queue 2 is empty queue 3 is empty queue 4 3 tasks: 24651 SyncCollection collection 55 24654 SyncCollection collection 48 24656 SyncCollection collection 52 IMAP tasks: RetrieveCollectionMetadataTask akonadiconsole debugger tab for the akonadi_imap_resource_3 akonadi_imap_resource_3 (0x564323260440) 423831 { Response: "FetchCollections" Error Code: "0" Error Msg: "" ID: "48" Name: "outbox" Parent ID: "42" Remote ID: "/outbox" Remote Revision: "" Resource: "akonadi_imap_resource_3" Mimetypes: "(message/rfc822, inode/directory)" Statistics: { Count: "204" Unseen: "0" Size: "100488225" } Search Query: "" Search Collections: "QVector()" Cache Policy: { Inherit: "true" Interval: "5" Cache Timeout: "-1" Sync on Demand: "true" Local Parts: "(ENVELOPE, HEAD, RFC822)" } Ancestors: { { ID: "42" Remote ID: "imap://gamber...@libero.it@imapmail.libero.it/" Name: "gamber...@libero.it" Attributes: "QMap()" } { ID: "0" Remote ID: "" Name: "" Attributes: "QMap()" } } Attributes: "QMap((ENTITYDISPLAY, ("" "mail-folder-sent" "mail-folder-sent" ()))(MESSAGEFOLDER, outbound)(collectionannotations, /shared )(collectionflags, \Answered \Flagged \Deleted \Seen \Draft $SENT $ATTACHMENT $FORWARDED $QUEUED \*)(collectionquota, 330485760 1073741824)(expirationcollectionattribute, akonadi_imap_resource_3 (0x564323260440) 423831 { Response: "FetchCollections" Error Code: "0" Error Msg: "" ID: "-1" Name: "" Parent ID: "-1" Remote ID: "" Remote Revision: "" Resource: "" Mimetypes: "()" Statistics: { Count: "-1" Unseen: "-1" Size: "-1" } Search Query: "" Search Collections: "QVector()" Cache Policy: { Inherit: "true" Interval: "-1" Cache Timeout: "-1" Sync on Demand: "false" Local Parts: "()" } Ancestors: { } Attributes: "QMap()" Display: "Undefined" Sync: "Undefined" Index: "Undefined" Enabled: "true" Virtual: "false" Referenced: "false" } akonadi_imap_resource_3 (0x564323260440) 423832 { Command: "FetchCollections" Collections: "UID 55" Depth: "0" Resource: "akonadi_imap_resource_3" Mimetypes: "()" Ancestors Depth: "2" Ancestors Attributes: "QSet()" Enabled: "false" Sync: "true" Display: "false" Index: "false" Status: "true" } akonadi_imap_resource_3 (0x564323260440) 423832 { Response: "FetchCollections" Error Code: "0" Error Msg: "" ID: "55" Name: "trash" Parent ID: "42" Remote ID: "/trash" Remote Revision: "" Resource: "akonadi_imap_resource_3" Mimetypes: "(message/rfc822, inode/directory)" Statistics: { Count: "538" Unseen: "428" Size: "34264841" } Search Query: "" Search Collections: "QVector()" Cache Policy: { Inherit: "true" Interval: "5" Cache Timeout: "-1" Sync on Demand: "true" Local Parts: "(ENVELOPE, HEAD, RFC822)" } Ancestors: { { ID: "42" Remote ID: "imap://gamber...@libero.it@imapmail.libero.it/" Name: "gamber...@libero.it" Attributes: "QMap()" } { ID: "0" Remote ID: "" Name: "" Attributes: "QMap()" } } Attributes: "QMap((ENTITYDISPLAY, ("" "user-trash" "" ()))(SpecialCollectionAttribute, trash)(collectionannotations, /shared )(collectionflags, \Answered \Flagged \Deleted \Seen \Draft $social $
[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account
https://bugs.kde.org/show_bug.cgi?id=364802 Marco Gamberoni <gamber...@libero.it> changed: What|Removed |Added CC||gamber...@libero.it --- Comment #10 from Marco Gamberoni <gamber...@libero.it> --- Me too. Since many months, about once a day, have to work around this bug with "akonadictl restart". Unrelated to gmail. For me it happens on imapmail.libero.it:993 (SSL) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kmail2] [Bug 254133] KMail terminates on startup with the error: Could not fetch root collection of resource akonadi_maildir_resource_1.
https://bugs.kde.org/show_bug.cgi?id=254133 marco.cas...@qvaliz.ptchanged: What|Removed |Added CC||marco.cas...@qvaliz.pt -- You are receiving this mail because: You are the assignee for the bug.
[kmail] [Bug 53321] kmail may ignore repeated cc headers
https://bugs.kde.org/show_bug.cgi?id=53321 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||kilija...@hotmail.com --- Comment #2 from Marco Martin <notm...@gmail.com> --- *** Bug 378748 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376220] Crash in Akonadi::Monitor::mimeTypesMonitored
https://bugs.kde.org/show_bug.cgi?id=376220 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||devuran...@gmx.net --- Comment #7 from Marco Martin <notm...@gmail.com> --- *** Bug 378474 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 376220] Crash in Akonadi::Monitor::mimeTypesMonitored
https://bugs.kde.org/show_bug.cgi?id=376220 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||bryan.j.don...@gmail.com --- Comment #6 from Marco Martin <notm...@gmail.com> --- *** Bug 378001 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 372914] Digital clock setting crash
https://bugs.kde.org/show_bug.cgi?id=372914 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||bugrprt21...@online.de --- Comment #3 from Marco Martin <notm...@gmail.com> --- *** Bug 377844 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371826] Kmail new mail systray icon invisible unless hovered
https://bugs.kde.org/show_bug.cgi?id=371826 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||notm...@gmail.com --- Comment #3 from Marco Martin <notm...@gmail.com> --- does the same machine also has wrong colors for other kstatusnotifier based icons? one example is konversation. if konversatio has a white icon while kmail a black one, then is the icon svg to be broken in https://cgit.kde.org/kmail.git/tree/src/kmsystemtray.cpp#n71 i see that an icon called "kmail" is looked for. the systray takes it from the plasma theme, and that is a correct svg, and colors correctly, at least in master what version of plasma-framework is used? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 345005] Filters do not work on the body of the message if the message is in base64
https://bugs.kde.org/show_bug.cgi?id=345005 Marco Gamberoni <gamber...@libero.it> changed: What|Removed |Added CC||gamber...@libero.it --- Comment #4 from Marco Gamberoni <gamber...@libero.it> --- Created attachment 101206 --> https://bugs.kde.org/attachment.cgi?id=101206=edit email with the Base64 encoded text: "The file 4207_66496070.zip has been infected with the virus JS/Nemucod.SMK9!tr, and has been removed." Attaching an example email where a filter intendet to move to Spam if body contains "Nemucod" fails. This is the filter definition copied from .config/akonadi_mailfilter_agentrc): [Filter #0] Applicability=2 AutomaticName=true ConfigureShortcut=true ConfigureToolbar=false Enabled=true StopProcessingHere=true ToolbarName=<>: Nemucod accounts-set=akonadi_imap_resource_0 action-args-0=224 action-name-0=transfer actions=1 apply-on=check-mail,manual-filtering contentsA=Nemucod fieldA= funcA=contains identifier=CBlqQTvFEp7ZHSUb name=<>: Nemucod operator=and rules=1 This is from the filter log viewer: [11:41:08] Esecuzione regole di filtro: (verifica tutti i criteri seguenti) "" "Nemucod" [11:41:08] 0 = "" "Nemucod" -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 368161] Plasma (plasmashell), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=368161 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||jodr...@live.com --- Comment #1 from Marco Martin <notm...@gmail.com> --- *** Bug 369332 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 327613] Kmail2 inserting my own email address in reply all
https://bugs.kde.org/show_bug.cgi?id=327613 Marco Ceriani <shikamar...@gmail.com> changed: What|Removed |Added CC||shikamar...@gmail.com --- Comment #2 from Marco Ceriani <shikamar...@gmail.com> --- I'm using Kmail 4.14.10 and it seems fixed. I even forgot about it. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 358565] Crash when reverting to "Defaults" in "Icon Theme" settings
https://bugs.kde.org/show_bug.cgi?id=358565 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||elvisblanco1...@aol.com --- Comment #1 from Marco Martin <notm...@gmail.com> --- *** Bug 358771 has been marked as a duplicate of this bug. *** -- 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 358771] Plasma crashed when changed the icon theme
https://bugs.kde.org/show_bug.cgi?id=358771 Marco Martin <notm...@gmail.com> changed: What|Removed |Added Resolution|--- |DUPLICATE CC||notm...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin <notm...@gmail.com> --- *** This bug has been marked as a duplicate of bug 358565 *** -- 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 358565] Crash when reverting to "Defaults" in "Icon Theme" settings
https://bugs.kde.org/show_bug.cgi?id=358565 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||bugs.kde.org@t9productions. ||com --- Comment #2 from Marco Martin <notm...@gmail.com> --- *** Bug 360575 has been marked as a duplicate of this bug. *** -- 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 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 --- Comment #27 from marco <e-an...@gmx.de> --- kmail 5.1.2 -- 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 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 marco <e-an...@gmx.de> changed: What|Removed |Added CC||e-an...@gmx.de --- Comment #26 from marco <e-an...@gmx.de> --- i have this problem too. i have the felling that importing old mail killed something. even recreating accounts doesnt solve it. in my case imap is somehow completely broken now because of these greyed out ghost mails. -- 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 354518] Akonadi crash in Kontact
https://bugs.kde.org/show_bug.cgi?id=354518 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||xingqibache...@qq.com --- Comment #3 from Marco Martin <notm...@gmail.com> --- *** Bug 359486 has been marked as a duplicate of this bug. *** -- 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 329779] crash without kontakt open (while background email check on POP3 runs on the default account and a mailinglist filter is used)
https://bugs.kde.org/show_bug.cgi?id=329779 Marco Martin <notm...@gmail.com> changed: What|Removed |Added CC||k...@kiekerjan.isdronken.nl --- Comment #1 from Marco Martin <notm...@gmail.com> --- *** Bug 356090 has been marked as a duplicate of this bug. *** -- 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
[Akonadi] [Bug 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
https://bugs.kde.org/show_bug.cgi?id=335090 --- Comment #46 from Marco Solieri sou...@xt3.it --- (In reply to Larx from comment #45) Akonadi 1 has never got usable over years (for me, but I seem not to be the only one). If I read the post linked above, I see again good ideas for Akonadi Next - but Akonadi 1 also was a good idea in theory, I suppose... Given the obvious lack of manpower, I don't know if it wouldn't be better to develop reliable, no-nonsense and solid PIM apps for KDE instead of again putting all ressources into a lofty framework with many theoretic advantages, but lots of shortcomings for the practical use. Maybe not usable is a bit overstating (and ungenerous), but from my experience I cannot say better than painful. Larx's opinion therefore seems like a reasonable (or: sensible) line of reasoning to me. In spite of this, it could still be totally incorrect, if the aim of framework rewriting is precisely at targeting some fundamental and unresolved source of problems affecting the first 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
[Akonadi] [Bug 338571] Performance Regression: Folder synchronisation in 4.14 very slow compared to kMail from KDE 4.13.x
https://bugs.kde.org/show_bug.cgi?id=338571 Marco Clemencic marco.clemen...@gmail.com changed: What|Removed |Added CC||marco.clemen...@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
[kdepimlibs] [Bug 340425] Unable to compile kdepimlibs. #include nested too deeply in ber.cpp due to ldap.h and lber.h
https://bugs.kde.org/show_bug.cgi?id=340425 --- Comment #1 from giuseppe marco randazzo gmranda...@gmail.com --- Ok.. /System/Library/Frameworks/LDAP.framework/Headers/ contain these two headers ldap.h and lber.h that contains: cat ldap.h #include lber.h cat lber.h #include ldap.h FindLdap search and find these headers inside the framework directory ant these are included indefinitely A work around to the problem is specifying the LDAP_INCLUDE_DIR when cmake is runed cmake .. -DLDAP_INCLUDE_DIR=/usr/include/ I think there is something strange on the LDAP framework. -- 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
[kdepimlibs] [Bug 340425] New: Unable to compile kdepimlibs. #include nested too deeply in ber.cpp due to ldap.h and lber.h
https://bugs.kde.org/show_bug.cgi?id=340425 Bug ID: 340425 Summary: Unable to compile kdepimlibs. #include nested too deeply in ber.cpp due to ldap.h and lber.h Product: kdepimlibs Version: unspecified Platform: Homebrew (Mac OS X) OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: kldap Assignee: kdepim-bugs@kde.org Reporter: gmranda...@gmail.com Hello, I've upgraded to yosemite and i was trying to recompile kdepimlibs. However i get this error: [ 58%] Building CXX object kldap/CMakeFiles/kldap.dir/ber.o In file included from /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:38: In file included from /System/Library/Frameworks/LDAP.framework/Headers/lber.h:1: In file included from /System/Library/Frameworks/LDAP.framework/Headers/lber.h:1: .. In file included from /System/Library/Frameworks/LDAP.framework/Headers/lber.h:1: In file included from /System/Library/Frameworks/LDAP.framework/Headers/lber.h:1: /System/Library/Frameworks/LDAP.framework/Headers/lber.h:1:10: error: #include nested too deeply #include lber.h ^ In file included from /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:39: In file included from /System/Library/Frameworks/LDAP.framework/Headers/ldap.h:1: In file included from /System/Library/Frameworks/LDAP.framework/Headers/ldap.h:1: In file included from /System/Library/Frameworks/LDAP.framework/Headers/ldap.h:1: /System/Library/Frameworks/LDAP.framework/Headers/ldap.h:1:10: error: #include nested too deeply #include ldap.h ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:64:5: error: unknown type name 'BerElement' BerElement *mBer; ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:72:13: error: use of undeclared identifier 'ber_alloc_t' d-mBer = ber_alloc_t( LBER_USE_DER ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:79:17: error: variable has incomplete type 'struct berval' struct berval bv; ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:79:10: note: forward declaration of 'berval' struct berval bv; ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:97:15: error: use of undeclared identifier 'ber_init' d-mBer = ber_init( bv ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:98:5: error: use of undeclared identifier 'ber_bvfree' ber_bvfree( bv ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:110:15: error: use of undeclared identifier 'ber_init' d-mBer = ber_init( bv ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:111:5: error: use of undeclared identifier 'ber_bvfree' ber_bvfree( bv ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:121:25: error: member access into incomplete type 'struct berval' ret = QByteArray( bv-bv_val, bv-bv_len ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:119:10: note: forward declaration of 'berval' struct berval *bv; ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:122:5: error: use of undeclared identifier 'ber_bvfree' ber_bvfree( bv ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:143:11: error: unknown type name 'ber_int_t' ber_int_t v = va_arg( args, int ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:164:25: error: variable has incomplete type 'struct berval' struct berval bv; ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:164:18: note: forward declaration of 'berval' struct berval bv; ^ In file included from /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:27: /usr/local/Cellar/qt/4.8.6/include/QtCore/qvarlengtharray.h:177:51: error: invalid application of 'sizeof' to an incomplete type 'berval' char array[sizeof(qint64) * (((Prealloc * sizeof(T)) / sizeof(qint64)) + 1)]; ^ /usr/local/Cellar/qt/4.8.6/include/QtCore/qvarlengtharray.h:175:5: note: in instantiation of member class 'QVarLengthArrayberval, 256::anonymous union at /usr/local/Cellar/qt/4.8.6/include/QtCore/qvarlengtharray.h:175:5' requested here union { ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:201:42: note: in instantiation of template class 'QVarLengthArrayberval, 256' requested here QVarLengthArraystruct berval bvs( V-count( ) ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:200:34: note: forward declaration of 'berval' QVarLengthArraystruct berval * bv ( V-count()+1 ); ^ /tmp/kdepimlibs-eZuLb1/kdepimlibs-4.14.0/kldap/ber.cpp:262:13: error: use of undeclared identifier 'ber_memfree' ber_memfree( c );
[akregator] [Bug 336417] Akregator crashes when being closed
https://bugs.kde.org/show_bug.cgi?id=336417 Marco Mattiolo marco.matti...@hotmail.it changed: What|Removed |Added CC||marco.matti...@hotmail.it --- Comment #4 from Marco Mattiolo marco.matti...@hotmail.it --- Same here with Akregator 4:4.14.0-1 on Debian testing. Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 0x7fc78d1149ad in isSignalConnected (signal_index=7, this=0x20) at kernel/qobject_p.h:237 #7 QMetaObject::activate (sender=0x20725a0, m=m@entry=0x7fc78f14f900 Akregator::Frame::staticMetaObject, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff71594770) at kernel/qobject.cpp:3472 #8 0x7fc78ef362a2 in Akregator::Frame::signalCompleted (this=optimized out, _t1=0x20725a0) at moc_frame.cpp:200 #9 0x7fc78ef2ba8b in Akregator::Frame::slotSetState (this=optimized out, state=state@entry=Akregator::Frame::Completed) at ../../../akregator/src/frame.cpp:94 #10 0x7fc7743f0407 in Akregator::MainWidget::slotFetchingStopped (this=0x2064060) at ../../../akregator/src/mainwidget.cpp:808 #11 0x7fc78d114c5c in QMetaObject::activate (sender=sender@entry=0x1efef00, m=m@entry=0x7fc78f14f940 Akregator::FetchQueue::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #12 0x7fc78ef35d23 in Akregator::FetchQueue::signalStopped (this=this@entry=0x1efef00) at moc_fetchqueue.cpp:126 #13 0x7fc78ef2b6b9 in Akregator::FetchQueue::slotAbort (this=this@entry=0x1efef00) at ../../../akregator/src/fetchqueue.cpp:68 #14 0x7fc78ef2b73a in Akregator::FetchQueue::~FetchQueue (this=0x1efef00, __in_chrg=optimized out) at ../../../akregator/src/fetchqueue.cpp:50 #15 0x7fc78ef2b7a9 in Akregator::FetchQueue::~FetchQueue (this=0x1efef00, __in_chrg=optimized out) at ../../../akregator/src/fetchqueue.cpp:53 #16 0x7fc78ef2a5d9 in Akregator::Kernel::~Kernel (this=0x7fc78f151718 Akregator::Kernel::self()::self, __in_chrg=optimized out) at ../../../akregator/src/kernel.cpp:66 #17 0x7fc78c469b39 in __run_exit_handlers (status=0, listp=0x7fc78c7d45a8 __exit_funcs, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #18 0x7fc78c469b85 in __GI_exit (status=optimized out) at exit.c:104 #19 0x7fc78c453b4c in __libc_start_main (main=0x407230 main(int, char**), argc=5, argv=0x7fff71594ab8, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fff71594aa8) at libc-start.c:321 #20 0x004079ed in _start () -- 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 338565] Dav resource should inform user if goes offline
https://bugs.kde.org/show_bug.cgi?id=338565 Marco Solieri sou...@xt3.it changed: What|Removed |Added CC||sou...@xt3.it -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
https://bugs.kde.org/show_bug.cgi?id=335090 Marco Solieri sou...@xt3.it changed: What|Removed |Added CC||sou...@xt3.it -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338570] Akonadi Dav Resource: Missing Conflict Resolution
https://bugs.kde.org/show_bug.cgi?id=338570 Marco Solieri sou...@xt3.it changed: What|Removed |Added CC||sou...@xt3.it -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338570] Akonadi Dav Resource: Missing Conflict Resolution
https://bugs.kde.org/show_bug.cgi?id=338570 Marco Solieri sou...@xt3.it changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Marco Solieri sou...@xt3.it --- *** This bug has been confirmed by popular vote. *** -- 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 338309] New: Akregator 4.14 RC crashes when closing
https://bugs.kde.org/show_bug.cgi?id=338309 Bug ID: 338309 Summary: Akregator 4.14 RC crashes when closing Product: akregator Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: giannini.ma...@gmail.com Created attachment 88270 -- https://bugs.kde.org/attachment.cgi?id=88270action=edit akregatorkcrash Application: akregator (4.14 rc) KDE Platform Version: 4.13.97 Qt Version: 4.8.6 Operating System: Linux 3.13.0-34-generic i686 Distribution: Ubuntu 14.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Distro: Kubuntu 14.04 LTS Akregator crashes when closing. The crash occurred 4 times since I upgraded to KDE 4.14 RC -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0xb33b6980 (LWP 2027))] Thread 2 (Thread 0xa9875b40 (LWP 2031)): #0 0xb48e118a in __GI___pthread_mutex_lock (mutex=0xa8f00558) at ../nptl/pthread_mutex_lock.c:125 #1 0xb5ed6c74 in pthread_mutex_lock (mutex=0xa8f00558) at forward.c:192 #2 0xb484d100 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb48079bd in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb48082df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb4808528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0xb6d6d95f in QEventDispatcherGlib::processEvents (this=0xa8f00468, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #7 0xb6d3c823 in QEventLoop::processEvents (this=this@entry=0xa9875258, flags=...) at kernel/qeventloop.cpp:149 #8 0xb6d3cb49 in QEventLoop::exec (this=this@entry=0xa9875258, flags=...) at kernel/qeventloop.cpp:204 #9 0xb6c2923d in QThread::exec (this=this@entry=0xa0b7680) at thread/qthread.cpp:537 #10 0xb6d1cc44 in QInotifyFileSystemWatcherEngine::run (this=0xa0b7680) at io/qfilesystemwatcher_inotify.cpp:265 #11 0xb6c2bb6f in QThreadPrivate::start (arg=0xa0b7680) at thread/qthread_unix.cpp:349 #12 0xb48def70 in start_thread (arg=0xa9875b40) at pthread_create.c:312 #13 0xb5ec988e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 1 (Thread 0xb33b6980 (LWP 2027)): [KCrash Handler] #7 data (this=0x5d) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135 #8 qGetPtrHelperQScopedPointerQObjectData (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2467 #9 d_func (this=0x59) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:115 #10 QMetaObject::activate (sender=sender@entry=0x9e56748, m=m@entry=0xb75ddc1c Akregator::Frame::staticMetaObject, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0xbffd59f8) at kernel/qobject.cpp:3489 #11 0xb75c4325 in Akregator::Frame::signalCompleted (this=this@entry=0x9e56748, _t1=_t1@entry=0x9e56748) at moc_frame.cpp:200 #12 0xb75b9cfc in Akregator::Frame::slotSetState (this=0x9e56748, state=state@entry=Akregator::Frame::Completed) at ../../../akregator/src/frame.cpp:94 #13 0xb075b8b8 in Akregator::MainWidget::slotFetchingStopped (this=0x9db7020) at ../../../akregator/src/mainwidget.cpp:808 #14 0xb077c178 in Akregator::MainWidget::qt_static_metacall (_o=0x9e484d0, _id=164091624, _a=0xbffd5af8, _c=optimized out) at moc_mainwidget.cpp:190 #15 0xb6d530f7 in QMetaObject::activate (sender=sender@entry=0x9c8c3a0, m=m@entry=0xb75ddc4c Akregator::FetchQueue::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3539 #16 0xb75c3d85 in Akregator::FetchQueue::signalStopped (this=this@entry=0x9c8c3a0) at moc_fetchqueue.cpp:126 #17 0xb75b961a in Akregator::FetchQueue::slotAbort (this=this@entry=0x9c8c3a0) at ../../../akregator/src/fetchqueue.cpp:68 #18 0xb75b9699 in Akregator::FetchQueue::~FetchQueue (this=0x9c8c3a0, __in_chrg=optimized out) at ../../../akregator/src/fetchqueue.cpp:50 #19 0xb75b971c in Akregator::FetchQueue::~FetchQueue (this=0x9c8c3a0, __in_chrg=optimized out) at ../../../akregator/src/fetchqueue.cpp:53 #20 0xb75b8457 in Akregator::Kernel::~Kernel (this=0xb75de65c Akregator::Kernel::self()::self, __in_chrg=optimized out) at ../../../akregator/src/kernel.cpp:66 #21 0xb5e104e1 in __run_exit_handlers (status=status@entry=0, listp=0xb5f893c4 __exit_funcs, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #22 0xb5e1053d in __GI_exit (status=0) at exit.c:104 #23 0xb5df6a8b in __libc_start_main (main=0x804dd00 main(int, char**), argc=5, argv=0xbffd5cf4, init=0x8050830 __libc_csu_init, fini=0x80508a0 __libc_csu_fini, rtld_fini=0xb772a180 _dl_fini, stack_end=0xbffd5cec) at libc-start.c:321 #24 0x0804e426 in _start () Segnala a https://bugs.kde.org/ -- You are receiving this mail because: You are the assignee for the
[akregator] [Bug 338309] Akregator 4.14 RC crashes when closing
https://bugs.kde.org/show_bug.cgi?id=338309 Marco giannini.ma...@gmail.com changed: What|Removed |Added CC||giannini.ma...@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
[Akonadi] [Bug 333449] Creating/editing/deleting a todo list item results in an Invalid item payload and Bad request
https://bugs.kde.org/show_bug.cgi?id=333449 --- Comment #7 from Marco Antonucci marco.antonucc...@gmail.com --- Created attachment 86565 -- https://bugs.kde.org/attachment.cgi?id=86565action=edit LibKGAPi.log -- 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 333449] Creating/editing/deleting a todo list item results in an Invalid item payload and Bad request
https://bugs.kde.org/show_bug.cgi?id=333449 Marco Antonucci marco.antonucc...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Marco Antonucci marco.antonucc...@gmail.com --- *** This bug has been confirmed by popular vote. *** -- 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
[kmail2] [Bug 323900] Page-margins in KDE-printer-settings
https://bugs.kde.org/show_bug.cgi?id=323900 Marco Morath marco_mor...@hotmail.com changed: What|Removed |Added CC||marco_mor...@hotmail.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
[kmail2] [Bug 323900] New: Page-margins in KDE-printer-settings
https://bugs.kde.org/show_bug.cgi?id=323900 Bug ID: 323900 Summary: Page-margins in KDE-printer-settings Classification: Unclassified Product: kmail2 Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: marco_mor...@hotmail.com It would be good if I could configure the default print settings a bit more specific. I often print to e-mails or save them as a PDF. However, I always have to adapt in KMail the printer margin settings, so that the contents do not get printed in the margin. The ideal thing would be the following: Easily set the printer margins in the general printer settings from KDE. Every program can handle it (eg KMail), if it gets the settings from KDE. Of course it would be perfect, if KDE or KMail get the the settings mirrored for duplex printing (the left margin would be the inner margin and the right margin the outer margin). KDE or KMail should configure that automatically, if the printer is set to duplex-printing. By default it's better to set the marings for printing e-mails and other things to work with to 10 mm at the top, the bottom an the right/outer margin. The left/inner margin should be 20 mm by default, because the pages get perforated. Reproducible: Always Steps to Reproduce: N/A Actual Results: N/A Expected Results: pre-define printer-settings for real printers and PDF-printers/pdf-export. -- 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 317790] kmail triggers lots of disconnected/no auth attempts log entries in Dovecot
https://bugs.kde.org/show_bug.cgi?id=317790 Marco Springer k...@glitchbox.nl changed: What|Removed |Added CC||k...@glitchbox.nl --- Comment #3 from Marco Springer k...@glitchbox.nl --- Apr 09 12:06:30 server dovecot[13887]: imap-login: Disconnected (no auth attempts in 0 secs): user=, rip={ext_ip}, lip={int_ip}, TLS, session=fEEXterZAgDZd+iC This is repeated multiple times per second, indefinitely. This is, until I stop akonadi through akonadictl stop. After a few seconds, akonadi is completely stopped and the messages stop at the server side. When I issue a akonadictl start, everything starts up perfectly normal and all is working normal again. When a connection issue arises, only for a minute or so, the dovecot server gets spammed at again coming from kmail/akonadi, requiring me to stop/start akonadi again. Sounds like some piece of connection checking code that ends up in an endless loop? -- 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
[kmail2] [Bug 283033] New mail notification sound does not always trigger on new mail arrival.
https://bugs.kde.org/show_bug.cgi?id=283033 Marco Solieri sou...@xt3.it changed: What|Removed |Added CC||sou...@xt3.it --- Comment #6 from Marco Solieri sou...@xt3.it --- I confirm the bug with KDE 4.8.4 and Kmail 1.13.7 on Debian amd64. I have one IMAP account in connected mode, with filtering on Sieve only. No new mail is notified, except for the currently selected directory. None of the notifications I set up is executed: no beep, no sound, no message, no command execution. I think it's an important feature for an email client and I hope this bug will be considered as so. I would be happy to provide any other additional useful information to help the fix. -- 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 290158] no notificatoin on arrival of mail
https://bugs.kde.org/show_bug.cgi?id=290158 Marco Solieri sou...@xt3.it changed: What|Removed |Added CC||sou...@xt3.it --- Comment #2 from Marco Solieri sou...@xt3.it --- Please, consider merging to #283033. -- 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 304111] Kleopatra fails to build
https://bugs.kde.org/show_bug.cgi?id=304111 Marco Martin notm...@gmail.com changed: What|Removed |Added CC||notm...@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 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Marco Vittorini Orgeas ma...@mavitt.org changed: What|Removed |Added Version|4.7 |4.8 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294485] Crash when adding a traditional KDE calendar
https://bugs.kde.org/show_bug.cgi?id=294485 Marco Vader ma...@mmvinder.nl changed: What|Removed |Added CC||ma...@mmvinder.nl -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294485] Crash when adding a traditional KDE calendar
https://bugs.kde.org/show_bug.cgi?id=294485 --- Comment #1 from Marco Vader ma...@mmvinder.nl --- Created attachment 69602 -- https://bugs.kde.org/attachment.cgi?id=69602action=edit New crash information added by DrKonqi akonadi_kcal_resource (4.7) on KDE Platform 4.7.4 (4.7.4) using Qt 4.8.0 - What I was doing when the application crashed: It crashes every after a sleep/wakup cycle. The problem started when a traditional calendar was added. -- Backtrace (Reduced): #6 begin (this=0xd9) at /usr/include/QtCore/qlist.h:101 #7 contains (this=0xd9, t=synthetic pointer) at /usr/include/QtCore/qlist.h:874 #8 removeRef (t=0x1883c60, this=0xd9) at /usr/src/debug/kdepimlibs-4.7.4/kcal/listbase.h:118 #9 KCal::Incidence::removeRelation (this=0x15a4fb0, incidence=0x1883c60) at /usr/src/debug/kdepimlibs-4.7.4/kcal/incidence.cpp:535 #10 0x003e02a5335b in KCal::Incidence::~Incidence (this=0x1883c60, __in_chrg=optimized out) at /usr/src/debug/kdepimlibs-4.7.4/kcal/incidence.cpp:207 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293649] The openXchange resource interprets the birthday wrong
https://bugs.kde.org/show_bug.cgi?id=293649 Marco Nelles ma...@maniatek.com changed: What|Removed |Added CC||ma...@maniatek.com --- Comment #1 from Marco Nelles marco maniatek com 2012-03-01 09:24:10 --- I can reproduce the bug and will have a closer look on it. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 293649] The openXchange resource interprets the birthday wrong
https://bugs.kde.org/show_bug.cgi?id=293649 --- Comment #2 from Marco Nelles marco maniatek com 2012-03-01 11:56:50 --- Okay, Problem: QDateTime is unable to handle dates/times earlier than 1970-01-01 00:00:00. I've fixed this with a workaround in this Akonadi resource. COMMIT: cf86c0a8f0e6a6363c6fcd86e84225f83317dab0 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259633] Cannot create new folders under 'KMail Folders'
https://bugs.kde.org/show_bug.cgi?id=259633 --- Comment #35 from Marco Vittorini Orgeas marco mavitt org 2012-01-26 12:13:01 --- (In reply to comment #34) Wait.. Please see #32. This is half fixed... I do not think that creating a new folder and NOT showing it is OK... It did not work like this before, and it does not work like this for delete folder. KMail Version 4.7.4: I right click on Local Folders - Add Folder, insert a name and then click OK, the tree of folders is refreshed to show the created folder. No need to reboot: this issue can be closed as solved or maybe wait for someone else to confirm before doing so. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259633] Cannot create new folders under 'KMail Folders'
https://bugs.kde.org/show_bug.cgi?id=259633 Marco Vittorini Orgeas ma...@mavitt.org changed: What|Removed |Added CC||ma...@mavitt.org -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259633] Cannot create new folders under 'KMail Folders'
https://bugs.kde.org/show_bug.cgi?id=259633 Marco Vittorini Orgeas ma...@mavitt.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 --- Comment #28 from Marco Vittorini Orgeas marco mavitt org 2012-01-25 21:51:20 --- *** This bug has been confirmed by popular vote. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259633] Cannot create new folders under 'KMail Folders'
https://bugs.kde.org/show_bug.cgi?id=259633 --- Comment #29 from Marco Vittorini Orgeas marco mavitt org 2012-01-25 21:56:07 --- As of version 4.7.4 isn't possible to create top level Imap folders..I'm shocked to find this bug still open, shouldn't severity be bumped and the bug be assigned ?? otherwise why not?!? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259633] Cannot create new folders under 'KMail Folders'
https://bugs.kde.org/show_bug.cgi?id=259633 --- Comment #31 from Marco Vittorini Orgeas marco mavitt org 2012-01-25 22:14:43 --- (In reply to comment #30) It would probably help if this would have been reported/discussed in a respective bug report. As far as I can determine from the latest comments this seems to work for local folders and apply to IMAP. Can anyone confirm that this still does not work for KMail Folders? As of 4.7.4, it's perfectly possible to add local folders, while it's *impossible* to add IMAP ones. In this bug there's a good amount of info: change the title and go straight ahead to the issue ?! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292418] New: Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Summary: Kmail can't create IMAP top level folders Product: kmail2 Version: 4.7 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: ma...@mavitt.org Version: 4.7 (using KDE 4.7.4) OS:Linux Simple as in subject: Kmail can't create IMAP top level folders. Try to right click on the imap account name/folder and there will be no Add folder entry. Select an imap account name/folder and then click main menu Folder: Add folder is greyed out. Reproducible: Always Steps to Reproduce: right click on the imap account name/folder and there will be no Add folder entry. Select an imap account name/folder and then click main menu Folder: Add folder is greyed out. Expected Results: To find a way to create top level IMAP folders! I've select Major severity: even if there's no data loss, this issue severely prevents normal work with imap accounts! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Marco Vittorini Orgeas ma...@mavitt.org changed: What|Removed |Added CC||ma...@mavitt.org -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259633] Cannot create new folders under 'KMail Folders'
https://bugs.kde.org/show_bug.cgi?id=259633 --- Comment #33 from Marco Vittorini Orgeas marco mavitt org 2012-01-25 22:40:54 --- OK: https://bugs.kde.org/show_bug.cgi?id=292418, please close this one and go straight voting and confirming the new one! -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 285676] akonadi blocks kmail because of searching for bogus emails
https://bugs.kde.org/show_bug.cgi?id=285676 --- Comment #19 from Marco Clemencic marco clemencic gmail com 2011-11-29 15:34:43 --- the suggestion of comment #17 works, but it is a workaround and not a fix. BTW, that's what I did to be able to work. To answer to comment #18: 1. my understanding of the difference is that in one case the top level directory can contain mails while the other not: 'kmail folders' (broken one) is a directory containing MailDirs, while 'local folders' (working one) is a MailDir... so it can contain nested MailDirs. 2. after the migration you get the broken one. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 285676] akonadi blocks kmail because of searching for bogus emails
https://bugs.kde.org/show_bug.cgi?id=285676 --- Comment #9 from Marco Clemencic marco clemencic gmail com 2011-11-12 10:48:40 --- Ok, I managed to reproduce the problem. From a fresh account, start Kontact (KMail2 should be enough). Prepare a directory with this kind of substructure: testing └── fldr1 ├── cur ├── new └── tmp From the KMail settings create a KMail Maildir account making it pointing to the directory testing. Create a new mail and save it as draft. Copy the file in the new subdirectory of the drafts directory (somewhere in ~/.local/share/.local-mail.directory/) to the directory testing/fldr1/new. From the KMail interface select the folder fldr1 and synchronize it (F5 or right-click and synchronize). Nothing seems to happen, but go to the KMail settings, then accounts, and you will see that the testing account got stuck in the synchronization and is unusable. The Maildir type of account (not KMail Maildir) doesn't seem to have the problem. If you try the same procedure using a Maildir account, it behaves correctly. Cheers Marco -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 285676] akonadi blocks kmail because of searching for bogus emails
https://bugs.kde.org/show_bug.cgi?id=285676 Marco Clemencic marco.clemen...@gmail.com changed: What|Removed |Added CC||marco.clemen...@gmail.com --- Comment #7 from Marco Clemencic marco clemencic gmail com 2011-11-11 11:45:29 --- Same for me. KMail is unusable: my the outbox folder is stuck because of that, so I have to use another mail client to be able to send emails. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 285676] akonadi blocks kmail because of searching for bogus emails
https://bugs.kde.org/show_bug.cgi?id=285676 --- Comment #8 from Marco Clemencic marco clemencic gmail com 2011-11-11 18:31:21 --- I managed to recover my outbox folder. What probably happened is that the Akonadi database and the maildir directory got desynchronized after a crash of the system (I have troubles with the suspend). In this situation the akonadi_mixedmaildir_resource seems to get stuck trying to synchronize. To recover the outbox I had to remove the files that were in the 'new' directory and remove the pim items from the database by hand. If I manage to reproduce the problem in a simple case I'll post it here. Cheers Marco -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 283080] New: Akonadi message Local Folders: Unsupported Type. Email from POP account disappear!
https://bugs.kde.org/show_bug.cgi?id=283080 Summary: Akonadi message Local Folders: Unsupported Type. Email from POP account disappear! Product: kmail2 Version: 4.7 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: scilir...@tiscali.it Version: 4.7 (using KDE 4.7.1) OS:Linux When downloading e-mail from all of my pop accounts I get many times the error Local Folder: Unsupported Type from Akonadi. Each time the error is displayed, a message is actually deleted from the server and not donwloaded (or not saved in the inbox folder). I checked the maildir hoping it was only a visualization problem: it's not, the messages are lost. This appear to happen randomly on some messages. Every day, something like 30% of the messages are lost this way. Very very bad thing!!! (I didn't realize immediately what was happening, it has brought me in big troubles with a few people!) Hope it's possible to fix this - and maybe to recover the lost data??? Thanks! Reproducible: Always Steps to Reproduce: Happens every time I check my e-mails with pop accounts. But only some 30% of the messages are affected. Actual Results: Something like 10 out of 15 messages are correctly downloaded. I get five times the error Local Folders: Unsupported Type trom Akonadi and 5 messages are deleted from the server, but not saved on the computer. Expected Results: All e-mail messages correctly downloades. No error messages. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 283080] Akonadi message Local Folders: Unsupported Type. Email from POP account disappear!
https://bugs.kde.org/show_bug.cgi?id=283080 Marco Scilironi scilir...@tiscali.it changed: What|Removed |Added CC||scilir...@tiscali.it -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282889] New: Kontact (KMail) crash with proxy
https://bugs.kde.org/show_bug.cgi?id=282889 Summary: Kontact (KMail) crash with proxy Product: kontact Version: 4.4.10 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: marco.clemen...@gmail.com Application: kontact (4.4.10) KDE Platform Version: 4.7.1 (4.7.1) Qt Version: 4.7.2 Operating System: Linux 2.6.38-11-generic x86_64 Distribution: Ubuntu 11.04 -- Information about the crash: - What I was doing when the application crashed: I clicked the button to check for new mails. - Custom settings of the application: I have enabled a proxy server in the system configuration using a .pac file. I might be that the proxy server is not well configured, but it works for http and https. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fed4841c7a0 (LWP 2698))] Thread 3 (Thread 0x7fed2773b700 (LWP 2917)): #0 0x7fed45877f03 in __poll (fds=value optimized out, nfds=value optimized out, timeout=value optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fed3f2ed104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fed3f2ed9f2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fed28852c44 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fed3f3143e4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fed3f7b8d8c in start_thread (arg=0x7fed2773b700) at pthread_create.c:304 #6 0x7fed4588504d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x in ?? () Thread 2 (Thread 0x7fed27f3c700 (LWP 3005)): #0 0x7fed45877f03 in __poll (fds=value optimized out, nfds=value optimized out, timeout=value optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fed3f2ed104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fed3f2ed639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fed45fbf446 in QEventDispatcherGlib::processEvents (this=0x4edeec0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fed45f93882 in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fed45f93abc in QEventLoop::exec (this=0x7fed27f3bdb0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7fed45eaa924 in QThread::exec (this=value optimized out) at thread/qthread.cpp:492 #7 0x7fed45f75c2f in QInotifyFileSystemWatcherEngine::run (this=0x52e25e0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fed45ead175 in QThreadPrivate::start (arg=0x52e25e0) at thread/qthread_unix.cpp:320 #9 0x7fed3f7b8d8c in start_thread (arg=0x7fed27f3c700) at pthread_create.c:304 #10 0x7fed4588504d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fed4841c7a0 (LWP 2698)): [KCrash Handler] #6 detach (this=0x0, job=0x5691b10) at /usr/include/qt4/QtCore/qhash.h:299 #7 operator[] (this=0x0, job=0x5691b10) at /usr/include/qt4/QtCore/qhash.h:738 #8 KIO::ProtoQueue::removeJob (this=0x0, job=0x5691b10) at ../../kio/kio/scheduler.cpp:483 #9 0x7fed37a7 in KIO::SchedulerPrivate::assignJobToSlave (this=value optimized out, slave=0x4d20810, job=0x5691b10) at ../../kio/kio/scheduler.cpp:1273 #10 0x7fed38b2 in KIO::Scheduler::assignJobToSlave (slave=0x4d20810, job=0x5691b10) at ../../kio/kio/scheduler.cpp:841 #11 0x7fed2b690877 in KMail::PopAccount::connectJob (this=value optimized out) at ../../kmail/popaccount.cpp:279 #12 0x7fed2b692f43 in KMail::PopAccount::startJob (this=0x3b2bf00) at ../../kmail/popaccount.cpp:414 #13 0x7fed2b699a19 in KMail::PopAccount::processNewMail (this=0x3b2bf00, _interactive=true) at ../../kmail/popaccount.cpp:196 #14 0x7fed2b5de9c4 in KMail::AccountManager::processNextCheck (this=0x3267ba0, _newMail=value optimized out) at ../../kmail/accountmanager.cpp:231 #15 0x7fed2b5df30a in KMail::AccountManager::singleCheckMail (this=0x3267ba0, account=0x3b2bf00, interactive=value optimized out) at ../../kmail/accountmanager.cpp:157 #16 0x7fed2b5e06a2 in KMail::AccountManager::checkMail (this=0x3267ba0, _interactive=true) at ../../kmail/accountmanager.cpp:353 #17 0x7fed2b77b1d2 in KMMainWidget::qt_metacall (this=0x3b53300, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7fff8e6f4560) at ./kmmainwidget.moc:363 #18 0x7fed45fa95f8 in QMetaObject::activate (sender=0x3cc9f70, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff8e6f4560) at kernel/qobject.cpp:3287 #19 0x7fed4694a122 in QAction::triggered (this=value optimized out, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #20 0x7fed4694a30f in QAction::activate (this=0x3cc9f70, event=value
[Bug 273794] New: Error while opening an E-Mail
https://bugs.kde.org/show_bug.cgi?id=273794 Summary: Error while opening an E-Mail Product: kontact Version: 4.4.10 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: marco_mor...@hotmail.com Application: kontact (4.4.10) KDE Platform Version: 4.6.00 (4.6.0) release 6 Qt Version: 4.7.1 Operating System: Linux 2.6.37.6-0.5-desktop x86_64 Distribution: openSUSE 11.4 (x86_64) -- Information about the crash: I'd like to open an E-Mail. Before I was informed, that Kontact was running two times. I closed one of them (the second one) and opened an E-Mail. Then Kontact crashed. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x7fb21b857cc4 in KMFolder::getMsg (this=value optimized out, idx=1571) at /usr/src/debug/kdepim-4.4.10/kmail/kmfolder.cpp:379 #7 0x7fb21bb30d84 in KMail::MessageListView::Widget::viewMessageSelected (this=0x12eff40, msg=0x1f6a020) at /usr/src/debug/kdepim-4.4.10/kmail/messagelistview/widget.cpp:163 #8 0x7fb21b03aaa6 in MessageList::Core::View::slotSelectionChanged (this=0x17b2d60) at /usr/src/debug/kdepim-4.4.10/messagelist/core/view.cpp:1905 #9 0x7fb21b03d4f6 in MessageList::Core::View::qt_metacall (this=0x17b2d60, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff949c0010) at /usr/src/debug/kdepim-4.4.10/build/messagelist/view.moc:93 #10 0x7fb236bbddef in QMetaObject::activate (sender=0x12dc6f0, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff949c0010) at kernel/qobject.cpp:3272 #11 0x7fb2364d01a7 in QItemSelectionModel::selectionChanged (this=value optimized out, _t1=value optimized out, _t2=value optimized out) at .moc/release-shared/moc_qitemselectionmodel.cpp:152 #12 0x7fb2364d6d67 in QItemSelectionModel::emitSelectionChanged (this=0x12dc6f0, newSelection=..., oldSelection=...) at itemviews/qitemselectionmodel.cpp:1525 #13 0x7fb2364d6ff7 in QItemSelectionModel::select (this=0x12dc6f0, selection=value optimized out, command=value optimized out) at itemviews/qitemselectionmodel.cpp:1088 #14 0x7fb2364c62e4 in QTreeViewPrivate::select (this=0x18006e0, topIndex=value optimized out, bottomIndex=value optimized out, command=...) at itemviews/qtreeview.cpp:3651 #15 0x7fb2364c6f40 in QTreeView::setSelection (this=value optimized out, rect=value optimized out, command=...) at itemviews/qtreeview.cpp:2280 #16 0x7fb23647d331 in QAbstractItemView::mousePressEvent (this=0x17b2d60, event=value optimized out) at itemviews/qabstractitemview.cpp:1665 #17 0x7fb21b03b17f in MessageList::Core::View::mousePressEvent (this=0x17b2d60, e=0x7fff949c17f0) at /usr/src/debug/kdepim-4.4.10/messagelist/core/view.cpp:2086 #18 0x7fb235fc6829 in QWidget::event (this=0x17b2d60, event=0x7fff949c17f0) at kernel/qwidget.cpp:8196 #19 0x7fb23636a906 in QFrame::event (this=0x17b2d60, e=0x7fff949c17f0) at widgets/qframe.cpp:557 #20 0x7fb23647ac23 in QAbstractItemView::viewportEvent (this=0x17b2d60, event=0x7fff949c17f0) at itemviews/qabstractitemview.cpp:1619 #21 0x7fb2364bfa85 in QTreeView::viewportEvent (this=0x17b2d60, event=0x7fff949c17f0) at itemviews/qtreeview.cpp:1256 #22 0x7fb236ba8d87 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=value optimized out, receiver=0x17a64e0, event=0x7fff949c17f0) at kernel/qcoreapplication.cpp:847 #23 0x7fb235f74ce1 in QApplicationPrivate::notify_helper (this=0x641d60, receiver=0x17a64e0, e=0x7fff949c17f0) at kernel/qapplication.cpp:4441 #24 0x7fb235f7daac in QApplication::notify (this=value optimized out, receiver=0x17a64e0, e=0x7fff949c17f0) at kernel/qapplication.cpp:4006 #25 0x7fb2375099e6 in KApplication::notify (this=0x7fff949c2520, receiver=0x17a64e0, event=0x7fff949c17f0) at /usr/src/debug/kdelibs-4.6.0/kdeui/kernel/kapplication.cpp:311 #26 0x7fb236ba8bfc in QCoreApplication::notifyInternal (this=0x7fff949c2520, receiver=0x17a64e0, event=0x7fff949c17f0) at kernel/qcoreapplication.cpp:732 #27 0x7fb235f75d25 in sendEvent (receiver=0x17a64e0, event=0x7fff949c17f0, alienWidget=0x17a64e0, nativeWidget=0xfad680, buttonDown=0x7fb236a44178, lastMouseReceiver=..., spontaneous=true) at ../../src/corelib/kernel/qcoreapplication.h:215 #28 QApplicationPrivate::sendMouseEvent (receiver=0x17a64e0, event=0x7fff949c17f0, alienWidget=0x17a64e0, nativeWidget=0xfad680, buttonDown=0x7fb236a44178, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3105 #29 0x7fb235ff3e08 in QETWidget::translateMouseEvent (this=0xfad680, event=value optimized out) at kernel/qapplication_x11.cpp:4438 #30 0x7fb235ff24c9 in QApplication::x11ProcessEvent (this=0x7fff949c2520, event=0x7fff949c2150) at kernel/qapplication_x11.cpp:3564 #31
[Bug 257097] Categories (nepomuk) dont'run
https://bugs.kde.org/show_bug.cgi?id=257097 Marco Roeder m...@marco-roeder.net changed: What|Removed |Added CC||m...@marco-roeder.net --- Comment #4 from Marco Roeder mail marco-roeder net 2011-03-11 01:19:39 --- I can confirm the issue. It has been there since quite a while. I'm attaching screenshots of what goes wrong. Screenshot 1: New User Test created. No categories (in German: Kategorien) so far. Screenshot 2: Opened the edit categories window. We see that there are some categories, but there are no names attached to them. Screenshot 3: Created a new category Test Screenshot 4: The edit category window is closed. KAddressbook shows a nepomuk resource identifier in the categories box Screenshot 5: Opened again the edit categories window. We see a number of things: the number of entries increased by one, but again all names are empty. Also, all entries are ticked now. Expected behaviour would be that we have a Test entry that is ticked. Screenshot 6: Closed the categories window and opened it again. Now the number of categories increased again significantly. KAddressbook 4.4.9, KDE 4.6.1. from KDE Backports repository, running on Kubuntu 10.10 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 261593] Frequent plasma-desktop crashes [KCalCore::IncidenceBase::isReadOnly, CalendarSupport::Calendar::Private::dataChanged]
https://bugs.kde.org/show_bug.cgi?id=261593 Marco Martin notm...@gmail.com changed: What|Removed |Added CC||dave.griffith...@gmail.com --- Comment #10 from Marco Martin notmart gmail com 2011-01-19 17:01:49 --- *** Bug 263651 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 259851] New: Crash when reloading Calendar using GroupDAV and eGroupware
https://bugs.kde.org/show_bug.cgi?id=259851 Summary: Crash when reloading Calendar using GroupDAV and eGroupware Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: marco.wuel...@medivation.ch Application: kontact (4.4.8) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.2 Operating System: Linux 2.6.32-26-generic x86_64 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: We are using eGroupware V1.6.03 and GroupDAV as Backend for Kontact. The Calender crashes sometimes when reloading the data from eGroupware. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f3ef353a780 (LWP 13662))] Thread 2 (Thread 0x7f3ed0ea2700 (LWP 13664)): #0 0x7f3ef0608f93 in *__GI___poll (fds=value optimized out, nfds=value optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f3ee91394a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x7f3ee91398fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7f3ef19f4566 in QEventDispatcherUNIXPrivate (this=0x2fc5dd0) at kernel/qeventdispatcher_unix.cpp:155 #4 0x7f3ed0ea1d90 in ?? () #5 0x02fc4e20 in ?? () #6 0x02fc68c0 in ?? () #7 0x7f3ed0ea1db0 in ?? () #8 0x7f3ef19c9d6c in QMutexLocker::unlock (path=value optimized out) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:108 #9 ~QMutexLocker (path=value optimized out) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:104 #10 QCoreApplication::addLibraryPath (path=value optimized out) at kernel/qcoreapplication.cpp:2342 #11 0x in ?? () Thread 1 (Thread 0x7f3ef353a780 (LWP 13662)): [KCrash Handler] #5 0x in ?? () #6 0x7f3ed3b8e98b in KOrg::IncidenceMonthItem::realStartDate (this=0x33eb1d0) at ../../korganizer/views/monthview/monthitem.cpp:343 #7 0x7f3ed3b8c35c in KOrg::MonthView::reloadIncidences (this=0x306e550) at ../../korganizer/views/monthview/monthview.cpp:330 #8 0x7f3ed3b8d4df in KOrg::MonthView::setStartDate (this=0x306e550, start=value optimized out) at ../../korganizer/views/monthview/monthview.cpp:296 #9 0x7f3ed3b8d53e in KOrg::MonthView::showDates (this=0x306e550, start=..., end=value optimized out) at ../../korganizer/views/monthview/monthview.cpp:283 #10 0x7f3ed3bd2d86 in KOViewManager::updateView (this=0x2f64db0, start=..., end=...) at ../../korganizer/koviewmanager.cpp:237 #11 0x7f3ed3bc13da in CalendarView::updateView (this=0x2f64b40, start=..., end=..., updateTodos=value optimized out) at ../../korganizer/calendarview.cpp:810 #12 0x7f3ed3bc29e0 in CalendarView::updateView (this=0x2f64b40) at ../../korganizer/calendarview.cpp:821 #13 0x7f3ed3bd1618 in CalendarView::qt_metacall (this=0x2f64b40, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff1634dec0) at ./calendarview.moc:589 #14 0x7f3ef19dde3f in QDebug::maybeSpace (dbg=) at ../../include/QtCore/../../src/corelib/io/qdebug.h:93 #15 QDebug::operator (dbg=) at ../../include/QtCore/../../src/corelib/io/qdebug.h:111 #16 operator (dbg=) at kernel/qobject.cpp:3685 #17 0x7f3ef08ade40 in ?? () from /lib/libc.so.6 #18 0x02490560 in ?? () #19 0x7f3ef08ade40 in ?? () from /lib/libc.so.6 #20 0x in ?? () This bug may be a duplicate of or related to bug 214895. Possible duplicates by query: bug 256504, bug 244901, bug 244836, bug 242335, bug 238907. Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 251671] New: Multiple home phone numbers are not parsed
https://bugs.kde.org/show_bug.cgi?id=251671 Summary: Multiple home phone numbers are not parsed Product: kaddressbook Version: unspecified Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: brbr...@gmail.com CC: to...@kde.org Version: unspecified (using KDE 4.4.5) OS:Linux It looks like kaddressbook lost the ability to parse vcards with multiple home phone numbers in the transition to 4.4.5. Only the first phone number is shown or editable. Reproducible: Didn't try Steps to Reproduce: Add this VCard to the address book BEGIN:VCARD ADR;TYPE=home:;;Viale Foo\, 10;Firenze;;50131;Italia BDAY:1962-02-09T00:00:00 CLASS:PUBLIC EMAIL:f...@gmail.com FN:John Doe N:Doe;John;;; NAME:John Doe REV:2009-11-22T17:35:29 TEL;TYPE=CELL:221254545 TEL;TYPE=HOME:055567567 TEL;TYPE=HOME:0556456456 UID:8ocYXspjEi VERSION:3.0 END:VCARD Actual Results: Only the first home phone is shown, either in the contact row, contact details or edit window! Expected Results: All home phone numbers should be shown. This happened updating to 4.4.5 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 246430] when importing a vCard, zeros in the dates are required
https://bugs.kde.org/show_bug.cgi?id=246430 Marco Costantini marco.costantin...@yahoo.it changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #4 from Marco Costantini marco costantini71 yahoo it 2010-08-02 11:15:45 --- Remember Postel's Prescription: Be generous in what you accept, rigorous in what you emit. (See http://www.faqs.org/docs/artu/ch11s06.html ) So I think that Kaddressbook should accept (of course only when importing vCards generated elsewhere) also dates in which the leading zeros are missing. The fix can is very simple: if the month or the day are one digit only, then add a leading zero. The broken vCards come from this Facebook application: http://www.facebook.com/apps/application.php?id=75422854687ref=ts http://apps.facebook.com/getvcard/ which is probably proprietary, but certainly not a highly proprietary one. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 246430] New: when importing a vCard, zeros in the dates are required
https://bugs.kde.org/show_bug.cgi?id=246430 Summary: when importing a vCard, zeros in the dates are required Product: kaddressbook Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: marco.costantin...@yahoo.it CC: to...@kde.org Version: unspecified (using KDE 4.4.2) OS:Linux Suppose that I import a vCard in Kaddressbook. I the vCard contains a line such as BDAY:1900-5-19 (note the one-digit month), then the date is not imported in the Kaddressbok contact. On the other hand, if the line is BDAY:1900-05-19 (note the month with a leading zero), the the date is correctly imported. This happens with both version 4.2.2 and 3.5 of Kaddressbook. Even if the vcard standard requires the two digit numbers, I think it would be better to support also the one-digit ones. I set the severity to major, because actualy there is a data loss: when importing the vCards, the date gets lost. Reproducible: Always Steps to Reproduce: Just try to import a vCard file, once with a line BDAY:1900-05-19 then import the same file, but with that line modified into BDAY:1900-5-19 without the zero Actual Results: In the first case the date is imported, and in the second is not Expected Results: the date should be imported in both cases OS: Linux (x86_64) release 2.6.32-21-generic Compiler: cc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 148498] Disabling interval mail checking of an account causes loop of checks
https://bugs.kde.org/show_bug.cgi?id=148498 Marco Brancalion marcobrancal...@gmail.com changed: What|Removed |Added CC||marcobrancal...@gmail.com --- Comment #11 from Marco Brancalion marcobrancalion gmail com 2009-12-23 12:02:59 --- KMail Version 1.12.2 With KDE 4.3.2 (KDE 4.3.2) I confirm the infinite loop bug after changing retrieve interval time to switched off. I stopped the loop by re-setting some interval time 0, and then again putting it off, and clicking apply. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 217031] New: KMail crashes during start
https://bugs.kde.org/show_bug.cgi?id=217031 Summary: KMail crashes during start Product: kmail Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: ironm...@gmail.com Application that crashed: kmail Version of the application: 1.12.2 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-15-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: no errors on console -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0x010d25ae in KMail::SearchJob::searchCompleteFolder (this=0xa2b8c18) at ../../kmail/searchjob.cpp:87 #7 0x01032124 in KMail::FolderJob::start (this=0x0) at ../../kmail/folderjob.cpp:106 #8 0x00ed40a8 in KMFolderImap::search (this=0xa0bd510, pattern=0x9e32fd8) at ../../kmail/kmfolderimap.cpp:2412 #9 0x0102d185 in KMSearch::slotProcessNextBatch (this=0xa2c1048) at ../../kmail/kmfoldersearch.cpp:272 #10 0x010319d3 in KMSearch::qt_metacall (this=0xa2c1048, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfd1013c) at ./kmfoldersearch.moc:79 #11 0x009a6263 in QMetaObject::activate (sender=0xa2bda40, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #12 0x009a6ec2 in QMetaObject::activate (sender=0xa2bda40, m=0xa81904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #13 0x009e0667 in QTimer::timeout (this=0xa2bda40) at .moc/release-shared/moc_qtimer.cpp:128 #14 0x009ab9ae in QTimer::timerEvent (this=0xa2bda40, e=0xbfd105d0) at kernel/qtimer.cpp:261 #15 0x009a03bf in QObject::event (this=0xa2bda40, e=0xbfd105d0) at kernel/qobject.cpp:1075 #16 0x03d38f54 in QApplicationPrivate::notify_helper (this=0x9e31ea0, receiver=0xa2bda40, e=0xbfd105d0) at kernel/qapplication.cpp:4056 #17 0x03d4067c in QApplication::notify (this=0xbfd12ef0, receiver=0xa2bda40, e=0xbfd105d0) at kernel/qapplication.cpp:3603 #18 0x00578bfa in KApplication::notify (this=0xbfd12ef0, receiver=0xa2bda40, event=0xbfd105d0) at ../../kdeui/kernel/kapplication.cpp:302 #19 0x009906cb in QCoreApplication::notifyInternal (this=0xbfd12ef0, receiver=0xa2bda40, event=0xbfd105d0) at kernel/qcoreapplication.cpp:610 #20 0x009bd7ce in QCoreApplication::sendEvent (this=0x9e32254) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #21 QTimerInfoList::activateTimers (this=0x9e32254) at kernel/qeventdispatcher_unix.cpp:572 #22 0x009bb0e0 in timerSourceDispatch (source=0x9e32220) at kernel/qeventdispatcher_glib.cpp:165 #23 0x08206e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #24 0x0820a720 in ?? () from /lib/libglib-2.0.so.0 #25 0x0820a853 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #26 0x009bb02c in QEventDispatcherGlib::processEvents (this=0x9d1a180, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #27 0x03dd9be5 in QGuiEventDispatcherGlib::processEvents (this=0x9d1a180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #28 0x0098ec79 in QEventLoop::processEvents (this=0xbfd10960, flags=) at kernel/qeventloop.cpp:149 #29 0x0098f0ca in QEventLoop::exec (this=0xbfd10960, flags=...) at kernel/qeventloop.cpp:201 #30 0x00610d60 in KWallet::Wallet::openWallet (name=..., w=77594647, ot=KWallet::Wallet::Synchronous) at ../../kdeui/util/kwallet.cpp:252 #31 0x020b8967 in MailTransport::TransportManager::wallet (this=0x9eb20a0) at ../../mailtransport/transportmanager.cpp:420 #32 0x020ad465 in MailTransport::Transport::readPassword (this=0x9f68718) at ../../mailtransport/transport.cpp:245 #33 0x020ad741 in MailTransport::Transport::qt_metacall (this=0x9f68718, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfd10b9c) at ./transport.moc:66 #34 0x009a6263 in QMetaObject::activate (sender=0x9f5c6a0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #35 0x009a6ec2 in QMetaObject::activate (sender=0x9f5c6a0, m=0xa80908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #36 0x009ab387 in QSingleShotTimer::timeout (this=0x9f5c6a0) at .moc/release-shared/qtimer.moc:76 #37 0x009ab49c in QSingleShotTimer::timerEvent (this=0x9f5c6a0) at kernel/qtimer.cpp:298 #38 0x009a03bf in QObject::event (this=0x9f5c6a0, e=0xbfd11030) at kernel/qobject.cpp:1075 #39 0x03d38f54 in QApplicationPrivate::notify_helper (this=0x9e31ea0, receiver=0x9f5c6a0, e=0xbfd11030) at kernel/qapplication.cpp:4056 #40 0x03d4067c in QApplication::notify (this=0xbfd12ef0, receiver=0x9f5c6a0, e=0xbfd11030) at kernel/qapplication.cpp:3603 #41 0x00578bfa in KApplication::notify (this=0xbfd12ef0, receiver=0x9f5c6a0, event=0xbfd11030) at ../../kdeui/kernel/kapplication.cpp:302 #42 0x009906cb in QCoreApplication::notifyInternal (this=0xbfd12ef0, receiver=0x9f5c6a0, event=0xbfd11030) at kernel/qcoreapplication.cpp:610 #43 0x009bd7ce in QCoreApplication::sendEvent
[Bug 208719] New: different structure to manage phones/email/IM items
https://bugs.kde.org/show_bug.cgi?id=208719 Summary: different structure to manage phones/email/IM items Product: kaddressbook Version: unspecified Platform: Debian testing OS/Version: Linux Status: NEW Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: mme...@mail.com CC: to...@kde.org, t...@iki.fi +++ This bug was initially created as a clone of Bug #110350 +++ Version: KDE 4.x Installed from:Debian testing/unstable Packages OS:Linux I propose a different structure for KAddressbook data, that, on my opinion, is much more flexible and effective in office usage. The current structure seems be taken from early PIM assistants, with a very limited capacity, and a rigid structure of data (vCard). In fact, you have a predefined number of fields where enter phone numbers/emails and whatever, with only a limited set of description for the fields (i.e. home, work, work fax, mobile...). A program in Delphi that I've build time ago and that I find very effective has a different aproach. a) you have unlimited number of items (telephones, e-mails, etc.) associated to a contact (master-detail tables) b) you have a free description of the item (i.e. wife's phone, Rome office L2 (I use L2 as mnemonic to indicete second phone line), private e-mail, etc. c) you have a list of types of item, that currently in my program is: phone, mobile, fax only, phone and fax, e-mail d) an additional info field, so it can contain the IM protocol, if the item is of type IM, or the type of switch if the numeber is associated with a phone+fax (manual/automatic) e) you can order them at will (so you put on top the more used), thanks to an order field Very draft screenshot (just to give you an idea) http://www.ammdomus.it/download/KDE/kontact_addresses_03.png Advantages: 1) you can manage every situations, with a unlimited numbers of items per contact, as for people with more than one office, or with a lot of people that can be contacted but have to belong to the same contact (so you have A.C.M.E. inc. as contact, and numbers/faxes/e-mails of the director, a pair of managers, the responsable of marketing, one secretary, an employee that is a friend of you, etc.) 2) you have separation between the number/e-mail, the description, and the type of technology (phone/fax/e-mail/messanger...). This greately helps when automatically dialing, or for other automatic management of these information 3) when you want to contact someone, you can filter the important info in a snap, i..e if you have to make a call, show only the rows of type phone or phone and fax, if you have to send a mail, just the type e-mail, etc., or have them showed in different color/icons 4) these data can be the base of data for a pecific telphony CRM/CTI program, with call queues, call annotations, etc. (I'm thinking about an integration with Asterisk or Yate PBX, for instance) Disadvantages: when you have to synch with a portable PIM (like iPaq), you don't have a 1:1 correspondence with the fields, since it uses the vCard desigh. To overcome this, there can be used multiples aproaches (the first that comes me to my mind is add one more field with PIM sync vcard kind that contains the old classifications, so the transfer can work with those items that have tha field that matches). In any case, the current situation is already of partial match. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 206221] New: kontact (kmail) crashes after an imap connection is lost
https://bugs.kde.org/show_bug.cgi?id=206221 Summary: kontact (kmail) crashes after an imap connection is lost Product: kontact Version: unspecified Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: marco.clemen...@gmail.com Application that crashed: kontact Version of the application: 4.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.28-15-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: After the connection is lost (for any reason) a notification message is display and, when I close it, kontact crashes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 KIO::Slave::deref (this=0x30c5a20) at /build/buildd/kde4libs-4.3.1/kio/kio/slave.cpp:242 #6 0x7fac578cdf6f in KIO::Slave::gotInput (this=0x30c5a20) at /build/buildd/kde4libs-4.3.1/kio/kio/slave.cpp:335 #7 0x7fac578d01c8 in KIO::Slave::qt_metacall (this=0x30c5a20, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff62e79010) at /build/buildd/kde4libs-4.3.1/obj-x86_64-linux-gnu/kio/slave.moc:76 #8 0x7fac553cbea2 in QMetaObject::activate (sender=0x30d4a30, from_signal_index=value optimized out, to_signal_index=4, argv=0x5e6fb70) at kernel/qobject.cpp:3113 #9 0x7fac577eadb1 in KIO::ConnectionPrivate::dequeue (this=0x30e9310) at /build/buildd/kde4libs-4.3.1/kio/kio/connection.cpp:82 #10 0x7fac577eb20a in KIO::Connection::qt_metacall (this=0x30d4a30, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x322ca40) at /build/buildd/kde4libs-4.3.1/obj-x86_64-linux-gnu/kio/connection.moc:73 #11 0x7fac553c65d8 in QObject::event (this=0x30d4a30, e=0x31fd5b0) at kernel/qobject.cpp: #12 0x7fac55f36f4d in QApplicationPrivate::notify_helper (this=0x155c020, receiver=0x30d4a30, e=0x31fd5b0) at kernel/qapplication.cpp:4056 #13 0x7fac55f3f18a in QApplication::notify (this=0x7fff62e7b830, receiver=0x30d4a30, e=0x31fd5b0) at kernel/qapplication.cpp:4021 #14 0x7fac5733bdeb in KApplication::notify (this=0x7fff62e7b830, receiver=0x30d4a30, event=0x31fd5b0) at /build/buildd/kde4libs-4.3.1/kdeui/kernel/kapplication.cpp:302 #15 0x7fac553b66ac in QCoreApplication::notifyInternal (this=0x7fff62e7b830, receiver=0x30d4a30, event=0x31fd5b0) at kernel/qcoreapplication.cpp:610 #16 0x7fac553b731a in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x152f850) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #17 0x7fac553dfe03 in postEventSourceDispatch (s=value optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #18 0x7fac4eb0720a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7fac4eb0a8e0 in ?? () from /usr/lib/libglib-2.0.so.0 #20 0x7fac4eb0aa7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7fac553dfa8f in QEventDispatcherGlib::processEvents (this=0x152f0a0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327 #22 0x7fac55fcfbdf in QGuiEventDispatcherGlib::processEvents (this=0x20, flags=value optimized out) at kernel/qguieventdispatcher_glib.cpp:202 #23 0x7fac553b4f42 in QEventLoop::processEvents (this=value optimized out, flags={i = 1659345296}) at kernel/qeventloop.cpp:149 #24 0x7fac553b5314 in QEventLoop::exec (this=0x7fff62e799d0, flags={i = 1659345392}) at kernel/qeventloop.cpp:201 #25 0x7fac563cde3e in QDialog::exec (this=0x5911c40) at dialogs/qdialog.cpp:498 #26 0x7fac572c1862 in KMessageBox::createKMessageBox (dialog=0x5911c40, icon=value optimized out, te...@0x7fff62e7a340, strli...@0x7fff62e7a120, a...@0x7fff62e7a020, checkboxReturn=0x7fff62e7a09f, options={i = 1659346784}, detai...@0x7fff62e7a010, notifyType=QMessageBox::Information) at /build/buildd/kde4libs-4.3.1/kdeui/dialogs/kmessagebox.cpp:331 #27 0x7fac572c29f7 in KMessageBox::createKMessageBox (dialog=0x5911c40, icon=QMessageBox::Information, te...@0x7fff62e7a340, strli...@0x7fff62e7a120, a...@0x7fff62e7a020, checkboxReturn=0x7fff62e7a09f, options={i = 1659347056}, detai...@0x7fff62e7a010) at /build/buildd/kde4libs-4.3.1/kdeui/dialogs/kmessagebox.cpp:151 #28 0x7fac572c4fa7 in KMessageBox::informationListWId (parent_id=0, te...@0x7fff62e7a340, strli...@0x7fff62e7a120, capti...@0x7fff62e7a300, dontshowagainna...@0x7fff62e7a2d0, options= {i = 1659347168}) at /build/buildd/kde4libs-4.3.1/kdeui/dialogs/kmessagebox.cpp:1008 #29 0x7fac572c5103 in KMessageBox::informationList (parent=0x0, te...@0x7fff62e7a340, strli...@0x7fff62e7a120, capti...@0x7fff62e7a300, dontshowagainna...@0x7fff62e7a2d0, options=value optimized out) at /build/buildd/kde4libs-4.3.1/kdeui/dialogs/kmessagebox.cpp:977 #30 0x7fac572c5151 in