[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 jochen changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #18 from jochen --- Comment 15 worked. Apologies not closing earlier. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcalendarcore] [Bug 389336] current mDirtyFields handling in IncidenceBase implementation causes issues with event revision counts (iCal SEQUENCE property)
https://bugs.kde.org/show_bug.cgi?id=389336 --- Comment #2 from Jochen Trumpf --- I no longer use kdepim as there were too many unfixed bugs persisting for years despite detailed bug reports. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 454898] New: Crash on start after modifing google account settings
https://bugs.kde.org/show_bug.cgi?id=454898 Bug ID: 454898 Summary: Crash on start after modifing google account settings Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jochen.faehnl...@ff-ipsheim.de Target Milestone: --- Application: kontact (5.19.3 (21.12.3)) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-33-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I changed google email account settings of its trash. It was setted to "local folder/trash" and i changed it to "Google account/[Google Mail]/trash". After restart of kontact it crashes with error message: "Could not create collection trash, resourceId 31". My Google imap resource has identifier: akonadi_imap_resource_11 ResourceId 31 has name "akonadi_maildir_resource_1" and is the local folder. If i rollback my changes of the trash settings with akonadiconsole, kontact starts without error. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f125987f599 in QScopedPointer >::operator-> (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #5 qGetPtrHelper > > (ptr=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1143 #6 QAction::d_func (this=0x0) at ../../include/QtWidgets/../../src/widgets/kernel/qaction.h:63 #7 QAction::setText (this=0x0, text=...) at kernel/qaction.cpp:714 #8 0x7f118bef3b3a in KMMainWidget::updateFolderMenu() () from /lib/x86_64-linux-gnu/libkmailprivate.so.5 #9 0x7f118befea85 in KMMainWidget::setupActions() () from /lib/x86_64-linux-gnu/libkmailprivate.so.5 #10 0x7f118bf04cf9 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) () from /lib/x86_64-linux-gnu/libkmailprivate.so.5 #11 0x7f11a0253edc in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kmailpart.so #12 0x7f11a0254396 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kmailpart.so #13 0x7f1259ecc912 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #14 0x7f125a058a83 in KontactInterface::Core::createPart(char const*) () from /lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #15 0x7f11a02bddda in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kontact5/kontact_kmailplugin.so #16 0x7f125a05bf2c in KontactInterface::Plugin::part() () from /lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #17 0x7f125a08b87b in Kontact::MainWindow::selectPlugin (this=0x5642d1cb4240, plugin=0x5642ced1b160) at ./src/mainwindow.cpp:554 #18 0x7f125a08c954 in Kontact::MainWindow::loadSettings (this=this@entry=0x5642d1cb4240) at ./src/mainwindow.cpp:683 #19 0x7f125a090978 in Kontact::MainWindow::initObject (this=0x5642d1cb4240) at ./src/mainwindow.cpp:149 #20 0x7f125a0913eb in Kontact::MainWindow::MainWindow (this=, this=) at ./src/mainwindow.cpp:86 #21 0x5642cd06b635 in KontactApp::activate (this=0x7ffce08eebe0, args=..., workingDir=...) at ./src/main.cpp:118 #22 0x7f125a0581be in KontactInterface::PimUniqueApplication::newInstance(QByteArray const&, QStringList const&, QString const&) () from /lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #23 0x7f125a05b137 in ?? () from /lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #24 0x7f125a05b233 in KontactInterface::PimUniqueApplication::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #25 0x7f1259dfd59b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #26 0x7f1259e00fec in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #27 0x7f1259e0187d in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7f1259e03dac in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #29 0x7f1258d7240e in QObject::event (this=0x7ffce08eebe0, e=0x7f11e4042df0) at kernel/qobject.cpp:1314 #30 0x7f1259883713 in QApplicationPrivate::notify_helper (this=, receiver=0x7ffce08eebe0, e=0x7f11e4042df0) at kernel/qapplication.cpp:3637 #31 0x7f1258d44e2a in QCoreApplication::notifyInternal2 (receiver=0x7ffce08eebe0, event=0x7f11e4042df0) at kernel/qcoreapplication.cpp:1064 #32 0x7f1258d47f17 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5642ce832620) at kernel/qcoreapplication.cpp:1821 #33 0x7f1258d9ea57 in postEventSourceDispatch (s=0x5642ce85b5f0) at kernel/qeventdispatcher_glib.cpp:277 #34 0x7f124f142d1b in g_main_context_dispatch () from
[plasmashell] [Bug 442938] New: Plasma crashes while dragging plasmoid
https://bugs.kde.org/show_bug.cgi?id=442938 Bug ID: 442938 Summary: Plasma crashes while dragging plasmoid Product: plasmashell Version: 5.21.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jochen.faehnl...@ff-ipsheim.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-34-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: I dragged a plasmoid from one monitor to the next. Thereby the content of the plasmoid disappears and plasma crashes. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fd8e1d99138 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fd8e1d9e095 in QSGBatchRenderer::Renderer::renderBatches() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fd8e1d9e7a2 in QSGBatchRenderer::Renderer::render() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fd8e1d86c84 in QSGRenderer::renderScene(QSGBindable const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fd8e1d87153 in QSGRenderer::renderScene(unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fd8e1de78d7 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fd8e1e53139 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fd8e1df5aed in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fd8e1df6457 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7fd8e012b341 in QThreadPrivate::start (arg=0x5594e87dbad0) at thread/qthread_unix.cpp:329 #14 0x7fd8df1ce450 in start_thread (arg=0x7fd853fff640) at pthread_create.c:473 #15 0x7fd8dfd6ed53 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (LWP 4618 "plasmash:gdrv0"): #1 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5594e88fcfb0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7fd8df1d4540 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5594e88fcf60, cond=0x5594e88fcf88) at pthread_cond_wait.c:504 #3 __pthread_cond_wait (cond=0x5594e88fcf88, mutex=0x5594e88fcf60) at pthread_cond_wait.c:628 #4 0x7fd8d91ba29b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd8d91b3e2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #6 0x7fd8df1ce450 in start_thread (arg=0x7fd871078640) at pthread_create.c:473 #7 0x7fd8dfd6ed53 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (LWP 4615 "plasmash:gdrv0"): #1 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5594e8831630, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7fd8df1d4540 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5594e88315e0, cond=0x5594e8831608) at pthread_cond_wait.c:504 #3 __pthread_cond_wait (cond=0x5594e8831608, mutex=0x5594e88315e0) at pthread_cond_wait.c:628 #4 0x7fd8d91ba29b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fd8d91b3e2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #6 0x7fd8df1ce450 in start_thread (arg=0x7fd871879640) at pthread_create.c:473 #7 0x7fd8dfd6ed53 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (LWP 4612 "QNetworkAccessM"): #1 __GI___libc_read (fd=24, buf=0x7fd8728a7a90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fd8de6e4d1c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd8de737c6d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fd8de6e2023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fd8e037021b in QEventDispatcherGlib::processEvents (this=0x7fd86b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fd8e031511b in QEventLoop::exec (this=this@entry=0x7fd8728a7c40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #7 0x7fd8e012a182 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7fd8e012b341 in QThreadPrivate::start
[plasmashell] [Bug 442489] context menu misaligned
https://bugs.kde.org/show_bug.cgi?id=442489 Jochen Fähnlein changed: What|Removed |Added CC||jochen.faehnlein@ff-ipsheim ||.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442489] context menu misaligned
https://bugs.kde.org/show_bug.cgi?id=442489 Jochen Fähnlein changed: What|Removed |Added Attachment #141573|Screenshot with kontact and |Screenshot with dolphin and description|its context menu|its context menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442489] New: context menu misaligned
https://bugs.kde.org/show_bug.cgi?id=442489 Bug ID: 442489 Summary: context menu misaligned Product: plasmashell Version: 5.21.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: jochen.faehnl...@ff-ipsheim.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 141573 --> https://bugs.kde.org/attachment.cgi?id=141573=edit Screenshot with kontact and its context menu With use of wayland nearly all context menus of KDE applications are misaligned to the cursor position. STEPS TO REPRODUCE 1. Open e.g. kontact 2. click with right mouse button to open the context menu The opened context menu is far away from the current cursor position. A screenshot is attached. SOFTWARE/OS VERSIONS Operating System: Ubuntu 21.04 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: Radeon RX 570 Series Displays: 2 - 0: Transformation: normal - 1: Transformation: 90 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 440657] Restart system after yay -Syu with ASUS 32" Monitor attached (as I mostly have)
https://bugs.kde.org/show_bug.cgi?id=440657 --- Comment #2 from Jochen --- (In reply to Michail Vourlakos from comment #1) > This is no detailed backtrace What does that mean? Tried to fill any information needed on the bug tracking app in Garuda. What do you miss and how to we get ahaed now? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 440657] New: Restart system after yay -Syu with ASUS 32" Monitor attached (as I mostly have)
https://bugs.kde.org/show_bug.cgi?id=440657 Bug ID: 440657 Summary: Restart system after yay -Syu with ASUS 32" Monitor attached (as I mostly have) Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jburkh...@ik.me Target Milestone: --- Application: latte-dock (0.10.75) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.7-arch1-1-surface x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: Garuda Linux -- Information about the crash: - What I was doing when the application crashed: - I was just restarting after the update. - Before the update I was in "hibernate mode" but my Surface Book 2 awoke just fine - Unusual behavior I noticed: - The Latte doc came slower as I commonly notice - Only two icons in the top bar appeared - But th others, like wireless connection appeared soow afterwards The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f30869a4840 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7f30869d5b1c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7f30869bc3fa in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7f30869c1b76 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7f30869c2585 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #9 0x7f30869a9602 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7f3086a18123 in QSGOpenGLLayer::grab() () at /usr/lib/libQt5Quick.so.5 #11 0x7f3086a1875e in QSGOpenGLLayer::updateTexture() () at /usr/lib/libQt5Quick.so.5 #12 0x7f3086b87b67 in QQuickOpenGLShaderEffectMaterial::updateTextures() const () at /usr/lib/libQt5Quick.so.5 #13 0x7f30869a9dad in QSGRenderer::preprocess() () at /usr/lib/libQt5Quick.so.5 #14 0x7f30869a95c9 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #15 0x7f30869a9af4 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #16 0x7f3086a0fdd3 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #17 0x7f3086a7fd81 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #18 0x7f3086a1ea67 in () at /usr/lib/libQt5Quick.so.5 #19 0x7f3086a1f447 in () at /usr/lib/libQt5Quick.so.5 #20 0x7f308491efef in () at /usr/lib/libQt5Core.so.5 #21 0x7f3083bd0259 in start_thread () at /usr/lib/libpthread.so.0 #22 0x7f30844275e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f3024fa7640 (LWP 5187) "latte-do:gdrv0"): #1 0x7f3083bd6270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7f306d8ad53c in () at /usr/lib/dri/iris_dri.so #3 0x7f306d8a7598 in () at /usr/lib/dri/iris_dri.so #4 0x7f3083bd0259 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f30844275e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f3025c0e640 (LWP 4274) "KCupsConnection"): #1 0x7f3082de5b29 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3082d8f871 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3084b6304f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3084b08d1c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f308491de12 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f3025cf029b in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f308491efef in () at /usr/lib/libQt5Core.so.5 #8 0x7f3083bd0259 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f30844275e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f302670e640 (LWP 4272) "latte-dock"): #1 0x7f3080313524 in () at /usr/lib/libusbmuxd-2.0.so.6 #2 0x7f30803148a9 in () at /usr/lib/libusbmuxd-2.0.so.6 #3 0x7f3083bd0259 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f30844275e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f3046d34640 (LWP 4235) "QQmlThread"): #1 0x7f308441cb43 in poll () at /usr/lib/libc.so.6 #2 0x7f3082de5b29 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f3082d8f871 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f3084b6304f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3084b08d1c in QEventLoop::exec(QFlags) () at
[Akonadi] [Bug 440387] New: All open applications of all desktops chrashes ...
https://bugs.kde.org/show_bug.cgi?id=440387 Bug ID: 440387 Summary: All open applications of all desktops chrashes ... Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: bu...@protonmail.com Target Milestone: --- Application: akonadiserver (5.17.3 (21.04.3)) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.10.53-1-lts x86_64 Windowing System: Wayland Drkonqi Version: 5.22.4 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: when open over a asigned edge-bottom all applications from all workspaces if clicking on one of it. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x564fbed8d544 in ?? () #5 0x7f54f5b244ff in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #6 0x7f54f5af7378 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7f54f5afa4a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #8 0x7f54f5b509a4 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f54f3d8b10c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #10 0x7f54f3ddeb99 in ?? () from /usr/lib/libglib-2.0.so.0 #11 0x7f54f3d88871 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #12 0x7f54f5b4ffd6 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #13 0x7f54f5af5d1c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #14 0x7f54f5afe284 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #15 0x564fbed8a44f in ?? () #16 0x7f54f5468b25 in __libc_start_main () from /usr/lib/libc.so.6 #17 0x564fbed8cfee in ?? () [Inferior 1 (process 1230) detached] Possible duplicates by query: bug 440377, bug 440356, bug 440343, bug 440175, bug 440159. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.
https://bugs.kde.org/show_bug.cgi?id=430157 Jochen Fähnlein changed: What|Removed |Added CC||jochen.faehnlein@ff-ipsheim ||.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 428123] New: baloo_file crashes on every login
https://bugs.kde.org/show_bug.cgi?id=428123 Bug ID: 428123 Summary: baloo_file crashes on every login Product: frameworks-baloo Version: 5.68.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: jochen.faehnl...@ff-ipsheim.de Target Milestone: --- Application: baloo_file_extractor (5.68.0) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-52-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Restart the system. On every login to plasma baloo crashes. The crash can be reproduced every time. -- Backtrace: Application: Datei-Extraktion für Baloo (baloo_file_extractor), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb39698c800 (LWP 1923))] Thread 3 (Thread 0x7fb394fb0700 (LWP 1941)): #0 __GI___libc_read (nbytes=16, buf=0x7fb394fafb60, fd=8) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=8, buf=0x7fb394fafb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fb3988ef89f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb3988a6cfe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb3988a7152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb3988a72e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb399f2a583 in QEventDispatcherGlib::processEvents (this=0x7fb388000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7fb399ed14db in QEventLoop::exec (this=this@entry=0x7fb394fafd70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7fb399d09785 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7fb39af34efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fb399d0a9d2 in QThreadPrivate::start (arg=0x7fb39afb7d80) at thread/qthread_unix.cpp:361 #11 0x7fb399406609 in start_thread (arg=) at pthread_create.c:477 #12 0x7fb39293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fb395827700 (LWP 1931)): #0 0x7fb39998caff in __GI___poll (fds=0x7fb395826ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb398834c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fb39883690a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fb396280298 in QXcbEventQueue::run (this=0x5623c0d9e3d0) at qxcbeventqueue.cpp:228 #4 0x7fb399d0a9d2 in QThreadPrivate::start (arg=0x5623c0d9e3d0) at thread/qthread_unix.cpp:361 #5 0x7fb399406609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fb39293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fb39698c800 (LWP 1923)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fb39989c859 in __GI_abort () at abort.c:79 #8 0x7fb3995c7a83 in mdb_assert_fail (env=0x5623c0df57f0, expr_txt=expr_txt@entry=0x7fb3995ca02f "rc == 0", func=func@entry=0x7fb3995ca978 <__func__.7221> "mdb_page_dirty", line=line@entry=2127, file=0x7fb3995ca010 "mdb.c") at mdb.c:1542 #9 0x7fb3995bc6d5 in mdb_page_dirty (mp=, txn=0x5623c0df6c50) at mdb.c:2114 #10 mdb_page_dirty (txn=0x5623c0df6c50, mp=) at mdb.c:2114 #11 0x7fb3995bd966 in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7ffcd36af5a8, mc=) at mdb.c:2308 #12 0x7fb3995bdba3 in mdb_page_touch (mc=mc@entry=0x7ffcd36afae0) at mdb.c:2495 #13 0x7fb3995bf7ec in mdb_cursor_touch (mc=mc@entry=0x7ffcd36afae0) at mdb.c:6523 #14 0x7fb3995c28f9 in mdb_cursor_put (mc=mc@entry=0x7ffcd36afae0, key=key@entry=0x7ffcd36afec0, data=data@entry=0x7ffcd36afed0, flags=flags@entry=0) at mdb.c:6657 #15 0x7fb3995c576b in mdb_put (txn=0x5623c0df6c50, dbi=2, key=key@entry=0x7ffcd36afec0, data=data@entry=0x7ffcd36afed0, flags=flags@entry=0) at mdb.c:9022 #16 0x7fb39b001d92 in Baloo::PostingDB::put (this=this@entry=0x7ffcd36affb0, term=..., list=...) at ./src/engine/postingdb.cpp:80 #17 0x7fb39b019ca8 in Baloo::WriteTransaction::commit (this=0x5623c0df5770) at ./src/engine/writetransaction.cpp:326 #18 0x7fb39b009c63 in Baloo::Transaction::commit (this=0x5623c0deecd0) at ./src/engine/transaction.cpp:306 #19 0x5623c0cec62c in Baloo::App::processNextFile (this=0x7ffcd36b0750) at ./src/file/extractor/app.cpp:119 #20 0x7fb399f0b5b6 in QtPrivate::QSlotObjectBase::call (a=0x7ffcd36b0140, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #21 QSingleShotTimer::timerEvent (this=0x5623c0ef39f0) at
[kmail2] [Bug 417978] kmail shows only empty messages
https://bugs.kde.org/show_bug.cgi?id=417978 Jochen Fähnlein changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 417978] kmail shows only empty messages
https://bugs.kde.org/show_bug.cgi?id=417978 --- Comment #1 from Jochen Fähnlein --- *** Bug 418852 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 417978] kmail shows only empty messages
https://bugs.kde.org/show_bug.cgi?id=417978 Jochen Fähnlein changed: What|Removed |Added CC||jochen.faehnlein@ff-ipsheim ||.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 418852] No email content shown
https://bugs.kde.org/show_bug.cgi?id=418852 Jochen Fähnlein changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jochen Fähnlein --- *** This bug has been marked as a duplicate of bug 417978 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 418852] No email content shown
https://bugs.kde.org/show_bug.cgi?id=418852 Jochen Fähnlein changed: What|Removed |Added CC||jochen.faehnlein@ff-ipsheim ||.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 418852] New: No email content shown
https://bugs.kde.org/show_bug.cgi?id=418852 Bug ID: 418852 Summary: No email content shown Product: kmail2 Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: jochen.faehnl...@ff-ipsheim.de Target Milestone: --- Created attachment 126786 --> https://bugs.kde.org/attachment.cgi?id=126786=edit Screenshot of the behaviour The content of all emails is currently not displayed. Neither plain text emails nor HTML emails. The view remains empty in the preview area and also when the email is opened. As workaround I am currently using the message structure. This shows the content correctly, as can be seen from the appendix. From there I can open the attachments or the text part e.g. with Kate. STEPS TO REPRODUCE 1. open kmail 2. select an email OBSERVED RESULT All email content is empty EXPECTED RESULT The content plain text / HTML is shown in the preview area. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.10 (available in About System) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 418287] New: Column "Status" in SEPA transaction list
https://bugs.kde.org/show_bug.cgi?id=418287 Bug ID: 418287 Summary: Column "Status" in SEPA transaction list Product: kmymoney Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: joc...@r-ci.de Target Milestone: --- Regarding SEPA transactions: What about adding a column like "status" to the output list? Sometimes I add SEPA transfers to the list to be executed later. It would be easier to find them if they are marked in the list of outgoing transactions (Account, Action, destination, value). A date when the transaction is to be executed would also be helpful. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 417978] kmail shows only empty messages
https://bugs.kde.org/show_bug.cgi?id=417978 Jochen Fähnlein changed: What|Removed |Added Version|unspecified |5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 417978] New: kmail shows only empty messages
https://bugs.kde.org/show_bug.cgi?id=417978 Bug ID: 417978 Summary: kmail shows only empty messages Product: kmail2 Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: jochen.faehnl...@ff-ipsheim.de Target Milestone: --- Created attachment 126244 --> https://bugs.kde.org/attachment.cgi?id=126244=edit Email viewer with structure view and empty content view SUMMARY kmail shows no content of the emails. Neither in HTML nor in text mode. Neither in preview nor in opened mode. Akonadi gets the content correctly and the message structure view in kmail shows the content correctly. STEPS TO REPRODUCE 1. select any email. The preview content is empty. OBSERVED RESULT EXPECTED RESULT Shows the message content. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415517] AppImage - KIO slaves not included
https://bugs.kde.org/show_bug.cgi?id=415517 --- Comment #7 from jochen --- Confirming that I do not have kio or kioslaves installed locally. My high level config: Arch Linux; LXQT; just the following KDE components are installed locally: kguiaddons 5.65.0-2 (kf5) kidletime 5.65.0-2 (kf5) kwayland 5.65.0-2 (kf5) kwindowsystem 5.65.0-2 (kf5) oxygen-icons 1:5.65.0-2 (kf5) solid 5.65.0-2 (kf5) libkscreen 5.17.5-1 (plasma) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415517] AppImage - Price update not working
https://bugs.kde.org/show_bug.cgi?id=415517 --- Comment #4 from jochen --- Still no luck when testing this ticket: # downloaded today's stable appimage build: KMyMoney-5.0.7-286c3ae-x86_64.AppImage # started KMyMoney-5.0.7-286c3ae-x86_64.AppImage Same error message on console than before. Only this path has changed, but I presume that's appimage specific: kf5.kio.core: couldn't create slave: "Can not find 'kioslave' executable at '/tmp/.mount_KMyMonfqzl0M/usr/bin, /tmp/.mount_KMyMonfqzl0M/usr/libexec, /home/appimage/appimage-workspace/deps/usr/lib/x86_64-linux-gnu/libexec/kf5'" -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415517] AppImage - Price update not working
https://bugs.kde.org/show_bug.cgi?id=415517 --- Comment #3 from jochen --- Apologies. I confused the ticket. Pls ignore my earlier comment (#2). Re-testing... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415517] AppImage - Price update not working
https://bugs.kde.org/show_bug.cgi?id=415517 jochen changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from jochen --- No luck, sorry. I did: # download today's stable appimage build: KMyMoney-5.0.7-286c3ae-x86_64.AppImage # deleted .config/kmymoney # deleted .aqbanking # started KMyMoney-5.0.7-286c3ae-x86_64.AppImage # loaded my kmy file (using for years) # configured aqbanking ## hbci ## pin/tan account ## skipping "special settings" ### cert downloaded: accepted ### tan mode: 902 phototan version 6 ### message: successfully setup # closing aqbanking setup # account > map account > kbanking # account > update account ## no import; immediate getting message as originally described; no prompt for pin or start date Still strange... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 --- Comment #14 from jochen --- Forgot to mention: I was starting with a new .aqbanking profile, did not migrate. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 --- Comment #13 from jochen --- Not sure whether this helps: I build gwenhywfar, aqbanking and kmymoney in (archlinux) docker image. All three fresh from git/master. Getting now same behaviour (#41518 & this ticket) than using appimage. Reverted back to previous docker build (kmymoney 5.0.3). At least shortcuts working again. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519
jochen changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #6 from jochen ---
Yes, it is a strange issue. I do not mind if the ticket gets closed without
solution. Might be a one off issue, dedicated to my installation. Although
there is nothing I can think of what could be that special.
Using AQHBCI_LOGLEVEL=debug ./KMyMoney-5.0.7-3227834-x86_64.AppImage does not
change anything. Console stay empty when trying to update - whether for single
account or all. Of course, other log messages are logged to console.
Given how fast the window with the message ("no transactions imported"; as
attached) appears, I am not prompted for HBCI/bank login and nothing logged to
console, it almost appears to me like that's a dead menu/button. But given it
is working for you, this cannot be true.
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 411272] Not saving changes to Shortcuts
https://bugs.kde.org/show_bug.cgi?id=411272 --- Comment #9 from jochen --- This KDE behaviour gives users of an AppImage version, which are not using KDE but something else a hard time... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415518] AppImage - Shortcuts not preserved
https://bugs.kde.org/show_bug.cgi?id=415518 jochen changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from jochen --- *** This bug has been marked as a duplicate of bug 411272 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 411272] Not saving changes to Shortcuts
https://bugs.kde.org/show_bug.cgi?id=411272 jochen changed: What|Removed |Added CC||schimpf.joc...@yahoo.com --- Comment #8 from jochen --- *** Bug 415518 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 jochen changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from jochen --- Again, thank you for looking into this and very swift reply - in particular on days like this: merry x-mas. I tried now: - Checked "edit account/online settings/download" tab: Already set to "ask user" - Unmapped/remapped accounts: no change - Deleted .aqbanking and setup aqbanking again (in KMyMoney) -- User got created -- Accounts got downloaded -- TX still not loading/unchanged - Started from scratch, i.e. created new kmy-file - Added just one account (as prompted during setup process) - Mapped account - Unchanged, still same behvior, i.e. TX not pulled from bank What puzzles me most: There is no logging at all on console when trying to download transactions. Initially my setup was created on <5.0.3 - 5.0.3 was working fine until 2FA kicked in. That version is on running as docker image, which I was hoping to get rid of by using appimage. Worse comes to worst I will build a new docker image with 5.0.7 version. I just thought I raise a bug since it might affect others as well. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 jochen changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from jochen --- Thank you for swift reply. Using KMyMoney-5.0.7-3227834-x86_64.AppImage does still not work for me. Pls note that I do not have a local aqbanking installation - just in case this matters. Upgrading/downloading accounts did work, downloading transaction/statements does not. Weird. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415519] New: AppImage - aqbanking Update (All) Accounts not working
https://bugs.kde.org/show_bug.cgi?id=415519 Bug ID: 415519 Summary: AppImage - aqbanking Update (All) Accounts not working Product: kmymoney Version: 5.0.7 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: schimpf.joc...@yahoo.com Target Milestone: --- Created attachment 124684 --> https://bugs.kde.org/attachment.cgi?id=124684=edit Import Message SUMMARY Importing transactions/account statements not working, not for single account, not for all accounts. STEPS TO REPRODUCE 1. Menu: Account > Update all accounts... 2. 3. OBSERVED RESULT Immediately a window pops up reporting no transactions imported (attached). No prompt for HBCI/bank login, etc. No output on console either! EXPECTED RESULT Prompted for HBCI/bank login, tx imported SOFTWARE/OS VERSIONS Linux/KDE Plasma: non-Plasma / Linux (x86_64) release 5.4.2-arch1-1 (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: qt5 ADDITIONAL INFORMATION KMyMoney version (appimage): 5.0.7-05ff395 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415518] New: AppImage - Shortcuts not preserved
https://bugs.kde.org/show_bug.cgi?id=415518 Bug ID: 415518 Summary: AppImage - Shortcuts not preserved Product: kmymoney Version: 5.0.7 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: schimpf.joc...@yahoo.com Target Milestone: --- SUMMARY Changing shortcuts is not persisted, must be re-applied on each app start. STEPS TO REPRODUCE 1. Menu: Settings > Configure Shortcuts... 2. Make change, e.g. I removed duplicate entry: KMyMoney > Copy > Alternate > Ctrl+Ins (which also exists for 'New'; so getting an error when using this shortcut) 3. Save & restart KMM OBSERVED RESULT Default shortcuts are available again, customization is gone EXPECTED RESULT Custom shortcuts persisted SOFTWARE/OS VERSIONS Linux/KDE Plasma: non-Plasma / Linux (x86_64) release 5.4.2-arch1-1 (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: qt5 ADDITIONAL INFORMATION KMyMoney version (appimage): 5.0.7-05ff395 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 415517] New: AppImage - Price update not working
https://bugs.kde.org/show_bug.cgi?id=415517 Bug ID: 415517 Summary: AppImage - Price update not working Product: kmymoney Version: 5.0.7 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: schimpf.joc...@yahoo.com Target Milestone: --- SUMMARY Price/rate update not working STEPS TO REPRODUCE 1. Menu: Tools > Update Stock and Currency Prices... 2. From/To: current date/both same date 3. Click button: Update All OBSERVED RESULT Error: created tmpfile kf5.kdbusaddons: Can not find 'kdeinit5' executable at "/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/jochen/bin/:/home/jochen/tmp/dockerhomedev/bin/node-current/bin:/home/jochen/tmp/dockerhomedev/bin/VSCode-linux-x64" "/tmp/.mount_KMyMonkiTige/usr/bin, /tmp/.mount_KMyMonkiTige/usr/bin" kf5.kio.core: couldn't create slave: "Can not find 'kioslave' executable at '/tmp/.mount_KMyMonkiTige/usr/bin, /tmp/.mount_KMyMonkiTige/usr/libexec, /home/appimage/appimage-workspace/deps/usr/lib/x86_64-linux-gnu/libexec/kf5'" kmymoney_webpricequote: quotedata "" EXPECTED RESULT Prices updated SOFTWARE/OS VERSIONS Linux/KDE Plasma: non-Plasma / Linux (x86_64) release 5.4.2-arch1-1 (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: qt5 ADDITIONAL INFORMATION kMyMoney version (appimage): 5.0.7-05ff395 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 409145] New: Kile crashes when opening a file on first application launch
https://bugs.kde.org/show_bug.cgi?id=409145 Bug ID: 409145 Summary: Kile crashes when opening a file on first application launch Product: kile Version: 2.9.92 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: j_oc...@hotmail.de Target Milestone: --- Application: kile (2.9.92) Qt Version: 5.12.4 Frameworks Version: 5.59.0 Operating System: Linux 5.1.14-zen1-1-zen x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Kile crashes when opening a file on first application launch - What I was doing when the application crashed: I started Kile for the first time on this machine. within the first session I opened a preexisting .tex file that opens and compiles without issues on a different machine also using Kile. After a restart of Kile I had to run the wizard again. After that I again restarted Kile and opened the file with no problems. So, there might be a bug that only affects the first launch (which I guess may be critical for a user's opinion) but I can't say that for sure as I haven't tested any further. If requested I can delete the .config files and try to reproduce the issue. -- Backtrace: Application: Kile (kile), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8fd28ded40 (LWP 1601))] Thread 5 (Thread 0x7f8fc982b700 (LWP 1611)): #0 0x7f8fd91343c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8fd940ccf0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f8fd940cde2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f8fdc45e708 in () at /usr/lib/libkdeinit5_kile.so #4 0x7f8fd9406bf0 in () at /usr/lib/libQt5Core.so.5 #5 0x7f8fd912e57f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f8fdc130f13 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8fca02c700 (LWP 1610)): #0 0x7f8fdc12bc6d in syscall () at /usr/lib/libc.so.6 #1 0x7f8fd9408fb2 in QSemaphore::acquire(int) () at /usr/lib/libQt5Core.so.5 #2 0x7f8fd95f778f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #3 0x7f8fdc4f0815 in () at /usr/lib/libkdeinit5_kile.so #4 0x7f8fdc45e984 in () at /usr/lib/libkdeinit5_kile.so #5 0x7f8fd9406bf0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f8fd912e57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f8fdc130f13 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f8fcb01f700 (LWP 1609)): #0 0x7f8fdc121fbc in read () at /usr/lib/libc.so.6 #1 0x7f8fd6ce2961 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f8fd6d32f70 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f8fd6d34766 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f8fd6d348ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f8fd962327c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f8fd95ca3ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f8fd94059c5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f8fda512b37 in () at /usr/lib/libQt5DBus.so.5 #9 0x7f8fd9406bf0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f8fd912e57f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f8fdc130f13 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8fd18eb700 (LWP 1608)): #0 0x7f8fdc126497 in poll () at /usr/lib/libc.so.6 #1 0x7f8fd77dc630 in () at /usr/lib/libxcb.so.1 #2 0x7f8fd77de2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f8fd2440079 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f8fd9406bf0 in () at /usr/lib/libQt5Core.so.5 #5 0x7f8fd912e57f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f8fdc130f13 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f8fd28ded40 (LWP 1601)): [KCrash Handler] #6 0x7f8fd9fc5565 in QAction::setEnabled(bool) () at /usr/lib/libQt5Widgets.so.5 #7 0x7f8fdc3aefef in () at /usr/lib/libkdeinit5_kile.so #8 0x7f8fdc3afd59 in () at /usr/lib/libkdeinit5_kile.so #9 0x7f8fdc3b000d in () at /usr/lib/libkdeinit5_kile.so #10 0x7f8fd95f7460 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #11 0x7f8fdc4f2433 in () at /usr/lib/libkdeinit5_kile.so #12 0x7f8fdc43169d in () at /usr/lib/libkdeinit5_kile.so #13 0x7f8fdc435c9a in () at /usr/lib/libkdeinit5_kile.so #14 0x7f8fdc3d24e0 in () at /usr/lib/libkdeinit5_kile.so #15 0x7f8fdc3d64f2 in () at /usr/lib/libkdeinit5_kile.so #16 0x7f8fdc3dbdba in () at /usr/lib/libkdeinit5_kile.so #17 0x7f8fd95f7460 in
[frameworks-baloo] [Bug 405480] New: baloo crashes with signal aborted after login
https://bugs.kde.org/show_bug.cgi?id=405480 Bug ID: 405480 Summary: baloo crashes with signal aborted after login Product: frameworks-baloo Version: 5.56.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: j_oc...@hotmail.de Target Milestone: --- Application: baloo_file_extractor (5.56.0) Qt Version: 5.12.1 Frameworks Version: 5.56.0 Operating System: Linux 4.19.28-1-lts x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: logged in to a session after boot within the previous session baloo also crashed without visible cause - Custom settings of the application: I do not consider this to be relevant but if it is, I don't want to waste anybodys time by not mentioning that I replaced kwin with i3. -- Backtrace: Application: Datei-Extraktion für Baloo (baloo_file_extractor), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6b034a800 (LWP 1127))] Thread 3 (Thread 0x7fa6a071b700 (LWP 1166)): #0 0x7fa6b3c82c21 in poll () at /usr/lib/libc.so.6 #1 0x7fa6b2bf2690 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fa6b2bf277e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fa6b41b7d04 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa6b4160b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fa6b3fa4569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fa6b5141ba6 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fa6b3fa596c in () at /usr/lib/libQt5Core.so.5 #8 0x7fa6b36e6a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fa6b3c8db23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fa6af2db700 (LWP 1139)): #0 0x7fa6b3c82c21 in poll () at /usr/lib/libc.so.6 #1 0x7fa6b2b65630 in () at /usr/lib/libxcb.so.1 #2 0x7fa6b2b672db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fa6afeae949 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fa6b3fa596c in () at /usr/lib/libQt5Core.so.5 #5 0x7fa6b36e6a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa6b3c8db23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fa6b034a800 (LWP 1127)): [KCrash Handler] #6 0x7fa6b3bc9d7f in raise () at /usr/lib/libc.so.6 #7 0x7fa6b3bb4672 in abort () at /usr/lib/libc.so.6 #8 0x7fa6b38a4602 in () at /usr/lib/liblmdb.so #9 0x7fa6b3899465 in () at /usr/lib/liblmdb.so #10 0x7fa6b389a6e6 in () at /usr/lib/liblmdb.so #11 0x7fa6b389a91b in () at /usr/lib/liblmdb.so #12 0x7fa6b389c54c in () at /usr/lib/liblmdb.so #13 0x7fa6b389f64b in mdb_cursor_put () at /usr/lib/liblmdb.so #14 0x7fa6b38a244b in mdb_put () at /usr/lib/liblmdb.so #15 0x7fa6b51f9a30 in Baloo::PositionDB::put(QByteArray const&, QVector const&) () at /usr/lib/libKF5BalooEngine.so.5 #16 0x7fa6b520d690 in Baloo::WriteTransaction::commit() () at /usr/lib/libKF5BalooEngine.so.5 #17 0x7fa6b5203563 in Baloo::Transaction::commit() () at /usr/lib/libKF5BalooEngine.so.5 #18 0x5649c1311f4d in () #19 0x7fa6b4198b57 in () at /usr/lib/libQt5Core.so.5 #20 0x7fa6b418d10b in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7fa6b4b29e24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #22 0x7fa6b4b316e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #23 0x7fa6b4161e99 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7fa6b41b7095 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #25 0x7fa6b41b795a in () at /usr/lib/libQt5Core.so.5 #26 0x7fa6b2bf07bf in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #27 0x7fa6b2bf2739 in () at /usr/lib/libglib-2.0.so.0 #28 0x7fa6b2bf277e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #29 0x7fa6b41b7ce9 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #30 0x7fa6b4160b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #31 0x7fa6b4168e36 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #32 0x5649c130f27f in () #33 0x7fa6b3bb6223 in __libc_start_main () at /usr/lib/libc.so.6 #34 0x5649c130f32e in () [Inferior 1 (process 1127) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 404929] Astrometry doesn't work at all in version 3.1
https://bugs.kde.org/show_bug.cgi?id=404929 --- Comment #22 from Jochen --- (In reply to Rob from comment #21) > mv /Applications/kstars.app/Contents/MacOS/python/bin/python > /Applications/kstars.app/Contents/MacOS/python/bin/python2.7 I've tried it and it worked. Thanks a lot. If I get it right, with renaming python this way it could be found anymore in this path, right? Can you explain what exactly the problem is here? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 404929] Astrometry doesn't work at all in version 3.1
https://bugs.kde.org/show_bug.cgi?id=404929 Jochen changed: What|Removed |Added CC||j...@planet-r.de --- Comment #2 from Jochen --- I've had the same issues as described and got it to work doing two things. 1. I've changed the solver setting in the Astrometry.net panel by unchecking "solver" (which disabled *Internal solver*) and entered the path "/Applications/KStars.app/Contents/MacOS/astrometry/bin/solve-field". The setting *Internal solver* seems not to link to it internally. 2. I've installed netpbm manually using homebrew. It seems that netbpm supplied by Kstars itself isn't working or even not used at all. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 402282] New: Kontact crashes on terminating
https://bugs.kde.org/show_bug.cgi?id=402282 Bug ID: 402282 Summary: Kontact crashes on terminating Product: kontact Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jochen.faehnl...@ff-ipsheim.de Target Milestone: --- Application: kontact (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-42-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: clicked on menu / file / terminate after that the exception occured The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7719d81600 (LWP 4995))] Thread 30 (Thread 0x7f755fba1700 (LWP 29341)): #0 0x7f77124b8ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f755fba07e0, expected=0, futex_word=0x7f76b8005504) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f77124b8ed9 in __pthread_cond_wait_common (abstime=0x7f755fba0880, mutex=0x7f76b80054b0, cond=0x7f76b80054d8) at pthread_cond_wait.c:533 #2 0x7f77124b8ed9 in __pthread_cond_timedwait (cond=0x7f76b80054d8, mutex=0x7f76b80054b0, abstime=0x7f755fba0880) at pthread_cond_wait.c:667 #3 0x7f77074da652 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f77074b0799 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f77074b0cfb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f77074a95eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f77124b26db in start_thread (arg=0x7f755fba1700) at pthread_create.c:463 #8 0x7f771673388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f757aafd700 (LWP 29245)): #0 0x7f77124b8ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f757aafc7e0, expected=0, futex_word=0x7f76b8005504) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f77124b8ed9 in __pthread_cond_wait_common (abstime=0x7f757aafc880, mutex=0x7f76b80054b0, cond=0x7f76b80054d8) at pthread_cond_wait.c:533 #2 0x7f77124b8ed9 in __pthread_cond_timedwait (cond=0x7f76b80054d8, mutex=0x7f76b80054b0, abstime=0x7f757aafc880) at pthread_cond_wait.c:667 #3 0x7f77074da652 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f77074b0799 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f77074b0cfb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f77074a95eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f77124b26db in start_thread (arg=0x7f757aafd700) at pthread_create.c:463 #8 0x7f771673388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f7598ab1700 (LWP 21980)): #0 0x7f7716726bf9 in __GI___poll (fds=0x7f76b404b140, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7710432539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f771043264c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f771728790b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f771722c9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f771704b22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f771705016d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f77124b26db in start_thread (arg=0x7f7598ab1700) at pthread_create.c:463 #8 0x7f771673388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f75a33fc700 (LWP 24230)): #0 0x7f7710478049 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f7710431aa3 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f771043246b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f771043264c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f771728790b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f771722c9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f771704b22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f771705016d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f77124b26db in start_thread (arg=0x7f75a33fc700) at pthread_create.c:463 #9 0x7f771673388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f75b33b0700 (LWP 20599)): #0
[kcalcore] [Bug 392952] New: Regression: port to QTimeZone leads to blowing up iCal file size
https://bugs.kde.org/show_bug.cgi?id=392952 Bug ID: 392952 Summary: Regression: port to QTimeZone leads to blowing up iCal file size Product: kcalcore Version: git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jochen.tru...@anu.edu.au Target Milestone: --- Created attachment 111933 --> https://bugs.kde.org/attachment.cgi?id=111933=edit fix for repeated VTIMEZONE entries in iCal resource Commit https://cgit.kde.org/kcalcore.git/commit/?h=Applications/17.12=d90afd544828cc3391720c7aaf9135fa577f303a introduced an unintended side effect that is blowing up iCal file sizes by storing a VTIMEZONE entry per event instead of a consolidated list. The issue is ultimately caused by the replacement of the QMap based ICalTimeZones class with a QVector based type for tzUsedList. The ICalTimeZones::add method did check whether a to be added timezone is already in the map, whereas the replacement QVector::push_back method does not. The bug occurs in lines 2419-2421 (Application/17.12 branch) of icalformat_p.cpp and is easily fixed with the attached patch. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384122] KOrganizer - No invitation sent when selecting multiple attendees + no email address autocompletion
https://bugs.kde.org/show_bug.cgi?id=384122 --- Comment #9 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- This commit https://cgit.kde.org/akonadi-calendar.git/commit/src/mailclient_p.cpp?h=Applications/17.12=5765ecd1595232d2bd9724c2f95e9faa600d9da1 seems to have fixed the issue for me. For some reason it did not make it into my installed version (akonadi-calendar-17.08.3 on gentoo), but it appears this commit is included since 17.12.0. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 386988] Schedule > Publish Item Information - Error: Unable to publish the item '...'
https://bugs.kde.org/show_bug.cgi?id=386988 Jochen Trumpf <jochen.tru...@anu.edu.au> changed: What|Removed |Added CC||jochen.tru...@anu.edu.au --- Comment #8 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- I suspect the underlying reason for the error is the same as in bug #384122. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384122] KOrganizer - No invitation sent when selecting multiple attendees + no email address autocompletion
https://bugs.kde.org/show_bug.cgi?id=384122 Jochen Trumpf <jochen.tru...@anu.edu.au> changed: What|Removed |Added CC||jochen.tru...@anu.edu.au --- Comment #8 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- I have the same issue in version 5.6.3. I rarely use this functionality so I am unsure how long the bug has been there. Starting from a console gives (edited for privacy): Input: "Jochen Trumpf <x@y>, a@b" Error: "The email address you have entered is not valid because it contains an unexpected comma." This is with mixed address types but the same happens with a single type. -- You are receiving this mail because: You are watching all bug changes.
[kcalcore] [Bug 389336] New: current mDirtyFields handling in IncidenceBase implementation causes issues with event revision counts (iCal SEQUENCE property)
https://bugs.kde.org/show_bug.cgi?id=389336 Bug ID: 389336 Summary: current mDirtyFields handling in IncidenceBase implementation causes issues with event revision counts (iCal SEQUENCE property) Product: kcalcore Version: git Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jochen.tru...@anu.edu.au Target Milestone: --- To reproduce the issue: 1) Accept an event invitation from kmail that you are not the organizer of (not sure if this is really necessary but it is the case that I fully tracked down). 2) Edit the event in korganizer and be careful to ONLY add an alarm. 3) Get the event organizer to send you an event update, for example, with a changed location. 4) Observe how the location change is shown in "reverse logic". 5) Try to accept the changed invitation and get the "This is not an update" error. What happens under the hood: Step 2) above should not lead to an increment of the event revision (iCal SEQUENCE property). At least that is the intent of the allowedModificationsWithoutRevisionUpdate logic in akonadi-calendar/incidencechanger.cpp lines 1022ff. Two things are going wrong, though, and if you watch the actual akonadi payload (e.g. in akonadiconsole), you will see that the revision gets incremented TWICE! So by the time the organizer sends an update, the local copy is seemingly newer, leading to the incorrect display in kmail as well as the error in Steps 4) resp. 5) above. One of the revision count increments is caused by lines 657ff in incidenceeditor/incidencedialog.cpp. This seems to be an unconditional increment in this context and I have no idea why it would be there. It appears to preclude any form of "smart" handling of changes within akonadi. The other revision count increment is due to a failure of the allowedModificationsWithoutRevisionUpdate logic mentioned above. In that function, the dirtyFields() call on the incidence returns many more fields than just IncidenceBase::FieldLastModified and IncidenceBase::FieldAlarms. On my machine it lists a total of 10 fields, including FieldRevision due to the previous increment in incidencedialog.cpp. The issue seems to be that some of the modifier methods in IncidenceBase and its children set the respective dirty flag even if the value of the property has not changed. For example, setOrganizer in IncidenceBase does not check the previous value and setSecrecy in Incidence or setTransparency in Event fail similarly. On the other hand, some of the set methods do this correctly, for example setUid in IncidenceBase. On my machine, I have observed incorrect behavior for Description, Recurrence, Attachment, Secrecy, Transparency, Attendees, and Organizer (and possibly for Alarms and Revision as well, but that might be confounded with the other issues described here). Additionally, toggling the alarm on the event (e.g. via the context menu in korganizer) seems to set IncidenceBase::FieldUnknown in dirtyFields() where it should probably be FieldAlarms. With FieldUnknown, toggling the alarm causes similar issues as described here. While you are fixing this, the logic in allowedModificationsWithoutRevisionUpdate should probably be expanded to also allow modifications of Categories (not 100% sure about this but I would think that categories are a local property given that they map to akonadi tags). Many people are colour-coding their agendas using (local) categories and in the current implementation that breaks invitation updates. I am more than happy to try suggested fixes if needed. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 352214] Event is not displayed in the UI if the invitation list contains the creator's email address with PARTSTAT=NEEDS-ACTION (or maybe anything else than PARTSTAT=ACCEPTED?)
https://bugs.kde.org/show_bug.cgi?id=352214 Jochen Trumpf <jochen.tru...@anu.edu.au> changed: What|Removed |Added CC||jochen.tru...@anu.edu.au -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 388509] Kontact Failed to load /usr/bin/libGLESv2.so and crash in wayland
https://bugs.kde.org/show_bug.cgi?id=388509 --- Comment #7 from Jochen <joc...@intevation.de> --- Of course _not_ wayland, since wayland still does not support the nvidia drivers officially. I used i3. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 388509] Kontact Failed to load /usr/bin/libGLESv2.so and crash in wayland
https://bugs.kde.org/show_bug.cgi?id=388509 --- Comment #5 from Jochen <joc...@intevation.de> --- I discussed the issue before posting here in the archlinux IRC-Channel, because I had the correct version installed. What helped resolving the bug was a full reboot of the system. If this still doesn't help, I'd suggest to head over to the ArchLinux user forum. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 388509] Kontact Failed to load /usr/bin/libGLESv2.so and crash in wayland
https://bugs.kde.org/show_bug.cgi?id=388509 Jochen <joc...@intevation.de> changed: What|Removed |Added CC||joc...@intevation.de --- Comment #3 from Jochen <joc...@intevation.de> --- The Bug is fixed now over at Archlinux: https://bugs.archlinux.org/task/56993 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 386071] New: Crash of Akonadi
https://bugs.kde.org/show_bug.cgi?id=386071 Bug ID: 386071 Summary: Crash of Akonadi Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jochen.faehnl...@ff-ipsheim.de Target Milestone: --- Application: akonadi_baloo_indexer (4.14) KDE Platform Version: 4.14.30 Qt Version: 4.8.7 Operating System: Linux 4.10.0-37-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: After each start or restart of akonadia via "akonadictl restart" I get that exception. The crash can be reproduced every time. -- Backtrace: Application: (akonadi_baloo_indexer), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7fb1456de77f in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 #7 0x7fb1456e037a in __GI_abort () at abort.c:89 #8 0x7fb1492c1f15 in qt_message_output(QtMsgType, char const*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fb147df4cc7 in () at /usr/lib/libakonadi-kde.so.4 #10 0x7fb147df418a in () at /usr/lib/libakonadi-kde.so.4 #11 0x7fb1493f6d11 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7fb14693503c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7fb14693bf76 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #14 0x7fb147699f5a in KApplication::notify(QObject*, QEvent*) () at /usr/lib/libkdeui.so.5 #15 0x7fb1493dc8ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #16 0x7fb1493e0366 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x7fb14940d09e in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x7fb144da1377 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fb144da15e0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fb144da168c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fb14940d20e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x7fb1469e2666 in () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x7fb1493db12f in QEventLoop::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #24 0x7fb1493db495 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x7fb1493e1459 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #26 0x7fb147df143d in Akonadi::AgentBase::init(Akonadi::AgentBase*) () at /usr/lib/libakonadi-kde.so.4 #27 0x55f432c1f1f3 in () #28 0x7fb1456c93f1 in __libc_start_main (main=0x55f432c183a0, argc=3, argv=0x7ffdce4e9d08, init=, fini=, rtld_fini=, stack_end=0x7ffdce4e9cf8) at ../csu/libc-start.c:291 #29 0x55f432c1845a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 378436] Instance create job emits result too early
https://bugs.kde.org/show_bug.cgi?id=378436 Jochen <joc...@intevation.de> changed: What|Removed |Added CC||joc...@intevation.de --- Comment #1 from Jochen <joc...@intevation.de> --- The problem still persists in accountwizard 4:17.08.2+p16.04+git20171013.0400-0 from the current KDE Neon devedition gitstable. I haven't tested if the patch still fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #16 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- Oh, and I forgot to say, obviously one needs to fix existing iCal resources by hand or discard them and start from scratch. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #15 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- The above two patches against 17.08.1 fix this issue for me. My calendar setup is rather basic with everything in a single timezone and I have not tested if the patches would work with multiple timezones. But at least they give a pointer to where to start. The approach taken in the patches is to make this change seamless for the user. Everything looks and behaves the same from their perspective but what gets written to the iCal resource changes. The current korganizer GUI is limited compared to the full KCalCore API for recurrence. I have tried to map the existing limitations in the GUI best possible to the KCalCore API (except for the currently naive handling of timezones). This would break if the korganizer GUI would ever allow sub-daily recurrence. But for now we can write DATE entries for all day recurrences and DATE-TIME entries otherwise. I am unsure how to properly merge the exception dates from the GUI into the exDateTimes in the case of different timezones. There is probably an API for that in KCalCore but I did not check. The patches are not doing anything fancy so properly porting to Qt5 should be straightforward. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #14 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- Created attachment 108009 --> https://bugs.kde.org/attachment.cgi?id=108009=edit patch for korganizer -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 --- Comment #13 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- Created attachment 108008 --> https://bugs.kde.org/attachment.cgi?id=108008=edit patch for incidenceeditor -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 169336] Events excluded or deleted in a recurring event block still show in other clients subscribed to a calendar (see RFC 2445 re. EXDATE)
https://bugs.kde.org/show_bug.cgi?id=169336 Jochen Trumpf <jochen.tru...@anu.edu.au> changed: What|Removed |Added CC||jochen.tru...@anu.edu.au --- Comment #12 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- I can confirm this issue is still present in version 17.08.1. Even if you were to take a literal interpretation of the RFC, the following is surely a bug: As pointed out in Comment #7 by David Jarvie, a DATE based exemption of a DATE-TIME recurrence would need to be interpreted as exempting all occurrences that intersect that (floating) DATE. However, if you select only one specific occurrence in the korganizer GUI, it writes a DATE based exemption to the ical file which in that case would also exempt the other intersecting occurrences that were not selected. The only way this can be made consistent is to write a TZID plus DATE-TIME based exemption if the user selects and deletes a specific occurrence of a recurring event with a TZID and DATE-TIME based DTSTART, which is exactly what Windows, Apple, Thunderbird, etc. all do ... -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379848] When there is a lot of WiFi connections, the VPN connection is not shown in the list
https://bugs.kde.org/show_bug.cgi?id=379848 --- Comment #14 from Jochen Buchholz <bookw...@security.de> --- I use gentoo linux and the version 5.9.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379848] When there is a lot of WiFi connections, the VPN connection is not shown in the list
https://bugs.kde.org/show_bug.cgi?id=379848 Jochen Buchholz <bookw...@security.de> changed: What|Removed |Added CC||bookw...@security.de --- Comment #13 from Jochen Buchholz <bookw...@security.de> --- I have the same problem, my openvpn connections are not shown. I must always start nmtui-connect, in this tool I can start the openvpn connection without problems. A special detail is, this problem occurs only when I connected via wifi. When I plug in my cable, the vpn connections are shown and I can connect. I have > 20 Wifi Accesspoints in my neighbourhood. It is very useless to display all these wifi accesspoints priorized, when I'm already connected with wifi. It would be useful to show other possible connections, like vpn connections on top and after these connections the wifi accesspoints. 80% of my shown wifi connections are under 5% signalstrengt, so the wifi accesspoints coud be shown at the end of the list, ordered by sinal strength. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382431] New: Plasma crashed after closing multiple instances of Okular
https://bugs.kde.org/show_bug.cgi?id=382431 Bug ID: 382431 Summary: Plasma crashed after closing multiple instances of Okular Product: plasmashell Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: j_oc...@hotmail.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.6) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.74-18.20-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I was simply closing several windows - Unusual behavior I noticed: nothing I noticed - Custom settings of the application: altered color-scheme, nothing more. Design is breeze-dark. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc5feba7900 (LWP 2212))] Thread 18 (Thread 0x7fc5008ac700 (LWP 29237)): #0 0x7fc5f78ca0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc5f87b765b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc53eeb142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc53eeb4dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc53eeaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc53eeb4e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc53eeaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fc53eeb2a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fc5f87b69e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc5f78c5744 in start_thread () at /lib64/libpthread.so.0 #10 0x7fc5f80c4aad in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fc5010ad700 (LWP 29236)): #0 0x7fc5f78ca0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc5f87b765b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc53eeb142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc53eeb4dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc53eeaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc53eeb4e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc53eeaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fc53eeb2a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fc5f87b69e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc5f78c5744 in start_thread () at /lib64/libpthread.so.0 #10 0x7fc5f80c4aad in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fc5018ae700 (LWP 29235)): #0 0x7fc5f78ca0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc5f87b765b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc53eeb142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc53eeb4dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc53eeaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fc53eeb4e32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fc53eeaf45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fc53eeb2a46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fc5f87b69e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc5f78c5744 in start_thread () at /lib64/libpthread.so.0 #10 0x7fc5f80c4aad in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fc5020af700 (LWP 29234)): #0 0x7fc5f78ca0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc5f87b765b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fc53eeb142f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fc53eeb4dea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fc53eeaf45b in
[kontact] [Bug 379500] Mails with calender information are displayed in plain source instead of calender information
https://bugs.kde.org/show_bug.cgi?id=379500 Jochen <joc...@intevation.de> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Jochen <joc...@intevation.de> --- (In reply to Laurent Montel from comment #2) > Did you installed kdepim-addons ? I didn't and that fixed the problem for me! Thank you! Will ask at arch if the can adjust the kdepim-addons from optional dependencies to dependencies for convenience. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 379500] New: Mails with calender information are displayed in plain source instead of calender information
https://bugs.kde.org/show_bug.cgi?id=379500 Bug ID: 379500 Summary: Mails with calender information are displayed in plain source instead of calender information Product: kontact Version: GIT (master) Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: joc...@intevation.de Target Milestone: --- Created attachment 105336 --> https://bugs.kde.org/attachment.cgi?id=105336=edit Top Message is an ICS File with some HTML Messagen, bottom two are Vcalender Message and Source Mails with information about VCALENDER Events or *.ics Events are not displayed as calendar events. When using an old instance, like e3.5, all events in mails are displayed correctly. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 379500] Mails with calender information are displayed in plain source instead of calender information
https://bugs.kde.org/show_bug.cgi?id=379500 Jochen <joc...@intevation.de> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 373988] KOrganiser time zone locked to UTC and not possible to change.
https://bugs.kde.org/show_bug.cgi?id=373988 Jochen <joc...@intevation.de> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Platform|Ubuntu Packages |Archlinux Packages Version|5.1.3 |GIT (master) --- Comment #9 from Jochen <joc...@intevation.de> --- kcmshell5 workaround doensn't work for me, since there is no "formats" module installed. The problem persists. Also: I cant change the week beginning to Monday, instead of Sunday. Can only speak for Archlinux and version 17.04.0-1 (Should be git-master) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376241] software centre is empty
https://bugs.kde.org/show_bug.cgi?id=376241 --- Comment #18 from Jochen <kdebugs.170...@login.jochenschuh.de> --- https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1577918 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376241] software centre is empty
https://bugs.kde.org/show_bug.cgi?id=376241 --- Comment #16 from Jochen <kdebugs.170...@login.jochenschuh.de> --- As described in Bug 376659 I'm new to Linux. So what does "resolved downstream" mean? Is there a fix waiting for delivery? Is someone working on this? I can not find any "~/.local/share/gnome-software". And I don't know how to "contact my distro". -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376659] Discover does not show any software
https://bugs.kde.org/show_bug.cgi?id=376659 --- Comment #1 from Jochen <kdebugs.170...@login.jochenschuh.de> --- Additional information: In between I installed sudo apt-get install software-center -> Software-center is working as expected, it shows available and installed software, and I can install software with it. -> Discover still does not show any software. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376659] New: Discover does not show any software
https://bugs.kde.org/show_bug.cgi?id=376659 Bug ID: 376659 Summary: Discover does not show any software Product: Discover Version: 5.6.2 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kdebugs.170...@login.jochenschuh.de Target Milestone: --- I‘m completely new to Linux, if you need any additional information please explain how I can get it :) Problem: Discover does not show any software, it is completely empty. What I did: I installed Kubuntu using an usb stick with kubuntu-16.04.1-desktop-amd64.iso parallel to Windows 7 (partitions „/“, „/home“ and „/swap“ manually created), system language „German“. After installation discover _did show_ software in its categories (I could browse them). Search function however _did not work_, it just showed no results no matter what I entered. System said there where around 230 updates available which I installed. After installation of these updates discovery is empty. No software is shown in categories any more, and search function still does not work. Discover only promotes some software in the rotating top area (VLC for example) – those descriptions float out of their boxes. If I click on one of these promoted software a detail window with description and install button appears. Since I‘m new to Linux I tried 16.04 Ubuntu (with unity) and then Ubuntu MATE on the same machine. Both had a fully working software center. So I believe this is a bug in discover. Maybe related to https://bugs.kde.org/show_bug.cgi?id=372729 https://bugs.kde.org/show_bug.cgi?id=367526 https://bugs.kde.org/show_bug.cgi?id=363392 https://bugs.kde.org/show_bug.cgi?id=376241 https://answers.launchpad.net/ubuntu/+source/plasma-discover/+question/294053 https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1573994 -- You are receiving this mail because: You are watching all bug changes.
[ksshaskpass] [Bug 376228] git fails with "Unable to extract keyFile from phrase"
https://bugs.kde.org/show_bug.cgi?id=376228 Jochen Trumpf <jochen.tru...@anu.edu.au> changed: What|Removed |Added CC||jochen.tru...@anu.edu.au --- Comment #3 from Jochen Trumpf <jochen.tru...@anu.edu.au> --- The proposed patch fixes the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 373988] KOrganiser time zone locked to UTC and not possible to change.
https://bugs.kde.org/show_bug.cgi?id=373988 Jochen <joc...@intevation.de> changed: What|Removed |Added CC||joc...@intevation.de --- Comment #7 from Jochen <joc...@intevation.de> --- I can't remove the UTC timezone from my calender. I can add others, I can remove the added ones, but not the UTC timezone. Every event in all my calenders now alert me an hour early. I use latest Arch with korganizer 16.12.1-1. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373321] New: Feature Request: check for duplicates during import
https://bugs.kde.org/show_bug.cgi?id=373321 Bug ID: 373321 Summary: Feature Request: check for duplicates during import Product: digikam Version: 5.3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Keywords: usability Severity: normal Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: jochen.weya...@gmx.de Target Milestone: --- Hello, after testing some different picture managing programs I found that Digikam is a really superb application. However, I think it would be nice if duplicates could be found in the importing process. It should be avoided to add duplicates to the collection rather than searching for duplicates in already imported material. Especially if pictures are shared with friends or copied to an importing directory manually, the applictaion doesn't recognise the pictures as already known. Maybe the already existing duplicates function can be integrated into the import function with an option to not import duplicates. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Jochen Trumpf <jochen.tru...@anu.edu.au> changed: What|Removed |Added CC||jochen.tru...@anu.edu.au -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 363309] certificates signed through marginal trusted certificates are incorrectly displayed
https://bugs.kde.org/show_bug.cgi?id=363309 Jochen <joc...@intevation.de> changed: What|Removed |Added CC||joc...@intevation.de -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 363309] New: certificates signed through marginal trusted certificates are incorrectly displayed
https://bugs.kde.org/show_bug.cgi?id=363309 Bug ID: 363309 Summary: certificates signed through marginal trusted certificates are incorrectly displayed Product: kleopatra Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: joc...@intevation.de CC: kdepim-b...@kde.org, m...@kde.org The Display of trust in a certificate is insufficient in Kleoptra. It seems that it doesn't matter wich trust state (except for "not trusted") a certificate has or gains, it always will be shown in the tab "trusted certificate". Reproducible: Always Steps to Reproduce: 1. Create 3 Keypairs (Frank, Lisa & Bart) 2. Export Barts Public Key 3. Delete Barts Keypair 4. Import Barts Public Key 5. Sign Barts Key with Lisas ID 6. Export Lisas Public Key 7. Delete Lisas Keypair 8. Import Lisas Public Key 9. Sign Lisas Key with Franks ID 10. Set Lisas Trustlevel to "marginal" Actual Results: Now all certificates are shown in the Tab "Trusted Certificates". Expected Results: Only Franks and Lisas should be shown in the Tab "Trusted Certificates". Franks, because its an Identity you created by yourself and Lisas because its signed with Franks key. But Barts identity should not show up here, because the trustlevel in this certificate is set through Lisas signing, which is just trusted on level "marginal". -- You are receiving this mail because: You are watching all bug changes.
