[krita] [Bug 430872] Fails to build on RISC-V due to failing to link with atomics
https://bugs.kde.org/show_bug.cgi?id=430872 --- Comment #1 from John Scott --- This issue seems to be fixed by this merge request, which removes the internal CheckAtomic.cmake and instead uses the more robust one from extra-cmake-modules: https://invent.kde.org/graphics/krita/-/merge_requests/498 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 408176] Alternative initialisation? Sagemath (= 8.6-6) on python 2 (unicode issue?) crashes on: exec sage-ipython -i --simple-prompt
https://bugs.kde.org/show_bug.cgi?id=408176
John Scott changed:
What|Removed |Added
CC||jsc...@posteo.net
--- Comment #19 from John Scott ---
It's tangentially related to the issue at hand, so I'm posting this here, but
Cantor gives trouble with the current (9.2) version of SageMath in Debian
Unstable. This is partly due to what I believe is a Sage bug, SAGE_ROOT being
an empty string, but I think there's still room to simplify cantor-execsage
immensely and this is what we're tentatively going to be shipping for Debian
Bullseye.
Please see the commit here:
https://salsa.debian.org/qt-kde-team/kde/cantor/-/commit/7b7f610
and perhaps the Debian bug here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972346#19
I basically turn cantor-execsage into the one-liner
{ echo "sage-ipython -i --simple-prompt"; cat; } | $1 --sh
which pipes the command into a Sage shell. Instead of mangling SAGE_ROOT,
opening the Sage shell with 'sage --sh' seems more elegant, but may not be a
supported command-line argument with older versions of Sage.
Please let me know if you plan to adopt this upstream. It looks like it will be
shipping in Debian Bullseye, but this trick of opening a Sage shell should work
with non-Debian-packaged Sage as well.
--
You are receiving this mail because:
You are watching all bug changes.
[marble] [Bug 401252] Marble segfaults when closing
https://bugs.kde.org/show_bug.cgi?id=401252 John Scott changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from John Scott --- This issue is from too long ago; I won't be able to reproduce it, so closing instead. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430872] New: Fails to build on RISC-V due to failing to link with atomics
https://bugs.kde.org/show_bug.cgi?id=430872 Bug ID: 430872 Summary: Fails to build on RISC-V due to failing to link with atomics Product: krita Version: 4.4.1 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: jsc...@posteo.net Target Milestone: --- Hi, Krita [fails to build on RISC-V with Debian unstable](https://buildd.debian.org/status/package.php?p=krita=sid), and although I don't have a patch, I'm pretty sure I've found the cause. (I'm more of a GLib/GTK person myself.) It fails like /usr/bin/ld: CMakeFiles/kritaimage.dir/tiles3/kis_tile_data_store.cc.o: in function `Leapfrog, DefaultValueTraits > >::TableMigration::run()': ./obj-riscv64-linux-gnu/libs/image/./libs/image/3rdparty/lock_free_map/leapfrog.h:475: undefined reference to `__atomic_exchange_1' ``` The CMake module that tries to check atomic support seems to be doing this: if (LLVM_COMPILER_IS_GCC_COMPATIBLE) # First check if atomics work without the library. check_working_cxx_atomics(HAVE_CXX_ATOMICS_WITHOUT_LIB) # If not, check if the library exists, and atomics work with it. if(NOT HAVE_CXX_ATOMICS_WITHOUT_LIB) check_library_exists(atomic __atomic_fetch_add_4 "" HAVE_LIBATOMIC) On RISC-V, atomics of four and eight bytes do not require library support (such as with `-pthread`), but for one and two bytes it does. Hence if this check is missing out on checking the need to link for one-byte atomics, that would explain the failure. For a more eloquent explanation, here's a similar issue in zstd that was fixed: https://github.com/facebook/zstd/pull/1103 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 401252] Marble segfaults when closing
https://bugs.kde.org/show_bug.cgi?id=401252 --- Comment #2 from John Scott --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 (In reply to Justin Zobel from comment #1) > Thank you for the crash report. > > As it has been a while since this was reported, can you please test and > confirm if this issue is still occurring or if this bug report can be marked > as resolved. Oof, I filed this bug when Debian Buster was in the middle of the testing cycle, so it's going to be slightly tricky for me to reproduce. I also don't use GNOME Boxes anymore, having been persuaded by this community to migrate to KDE and Plasma :) I'll give a try using virt-manager. -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQT287WtmxUhmhucNnhyvHFIwKstpwUCX9tgGAAKCRByvHFIwKst p9+jAQDi+87sYs36dj5Z5+PPzXSqrv7IL2lSwQcY/JsL9V6CIwEAxeDamvwvOgMh tA7pv15gZZoXeZxbYZi1OI1lgatiqQU= =UUWo -END PGP SIGNATURE- -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 402780] Akonadi doesn't work with Exchange again
https://bugs.kde.org/show_bug.cgi?id=402780 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 422410] EWS resource uses 100% CPU when its target server becomes inaccessible
https://bugs.kde.org/show_bug.cgi?id=422410 John Scott changed: What|Removed |Added Ever confirmed|0 |1 CC||jsc...@posteo.net Status|REPORTED|CONFIRMED --- Comment #1 from John Scott --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I can reproduce this every time on Debian Bullseye if, for example, I disconnect my computer from the Internet but don't tell KMail to 'Go Offline.' Two processes seem to eat the CPU, and I don't know what their relation is: akonadi_ews_res and http_so. Here's a crummy backtrace from when I stopped the former: #0 0x7f894330f4bf in __GI___poll (fds=0x5614f8a31510, nfds=8, timeout=40) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f893e859dce in g_main_context_poll (priority=, n_fds=8, fds=0x5614f8a31510, timeout=, context=0x7f8930005000) at ../../../glib/gmain.c:4395 #2 g_main_context_iterate (context=context@entry=0x7f8930005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4087 #3 0x7f893e859eef in g_main_context_iteration (context=0x7f8930005000, may_block=may_block@entry=1) at ../../../glib/gmain.c:4157 #4 0x7f89438bf31b in QEventDispatcherGlib::processEvents(QFlags) (this=0x5614f84d4be0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f89438684db in QEventLoop::exec(QFlags) (this=this@entry=0x7ffc114e3b90, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #6 0x7f8943870782 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #7 0x7f894c80faae in Akonadi::ResourceBase::init(Akonadi::ResourceBase&) () at /lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5 #8 0x5614f6c2d1c3 in () #9 0x7f8943242cca in __libc_start_main (main=0x5614f6bdaa10, argc=3, argv=0x7ffc114e3e78, init=, fini=, rtld_fini=, stack_end=0x7ffc114e3e68) at ../csu/libc-start.c:308 #10 0x5614f6bdf33a in () and from the latter: #0 0x7f3da04c25b6 in __ppoll (fds=fds@entry=0x7ffec64504e8, nfds=nfds@entry=1, timeout=, timeout@entry=0x7ffec6450480, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7f3da08872a0 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x7ffec6450480, nfds=1, fds=0x7ffec64504e8) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x7ffec6450480, nfds=1, fds=0x7ffec64504e8) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll (fds=fds@entry=0x7ffec64504e8, nfds=nfds@entry=1, timeout_ts=0x7ffec64504f0) at kernel/qcore_unix.cpp:164 #5 0x7f3d9c5d27a2 in qt_poll_msecs (nfds=1, timeout=, fds=0x7ffec64504e8) at ../../include/QtCore/5.14.2/QtCore/private/../../../../../src/corelib/kernel/qcore_unix_p.h:381 #6 QNativeSocketEnginePrivate::nativeSelect (this=this@entry=0x56127de01fc0, timeout=, checkRead=checkRead@entry=true, checkWrite=checkWrite@entry=false, selectForRead=selectForRead@entry=0x7ffec64505c6, selectForWrite=0x7ffec64505c7) at socket/qnativesocketengine_unix.cpp:1435 #7 0x7f3d9c5d0271 in QNativeSocketEngine::waitForReadOrWrite (this=0x56127de02b00, readyToRead=0x7ffec64505c6, readyToWrite=, checkRead=, checkWrite=, msecs=, timedOut=0x0) at socket/qnativesocketengine.cpp:1120 #8 0x7f3d9c5c37b6 in QAbstractSocket::waitForReadyRead (this=0x56127de038c0, msecs=6) at ../../include/QtCore/5.14.2/QtCore/private/../../../../../src/corelib/tools/qringbuffer_p.h:218 #9 0x7f3d9c7b90e8 in KIO::ConnectionBackend::waitForIncomingTask (this=0x56127de05d90, ms=6) at ./src/core/connectionbackend.cpp:168 #10 0x7f3d9c7b9dc5 in KIO::Connection::waitForIncomingTask (this=, ms=ms@entry=6) at ./src/core/connection.cpp:204 #11 0x7f3d9c814cdd in KIO::SlaveBase::dispatchLoop (this=0x7ffec6450730) at ./src/core/slavebase.cpp:328 #12 0x7f3d9b01fda2 in kdemain () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so #13 0x56127d771c5d in ?? () #14 0x56127d772d4a in ?? () #15 0x56127d77373a in ?? () #16 0x56127d76e63f in ?? () #17 0x7f3da03f5cca in __libc_start_main (main=0x56127d76dc70, argc=5, argv=0x7ffec6451128, init=, fini=, rtld_fini=, stack_end=0x7ffec6451118) at ../csu/libc-start.c:308 #18 0x56127d76f2aa in ?? () I'll work on getting some better ones, but I'd appreciate tips like what breakpoints to set. I don't remember which way it was but when debugging, if I stopped one of the programs, a new process would spawn. That makes it tricky to pin where the fault lies: akonadi_ews_res or http_so. -BEGIN PGP SIGNATURE- iQ9FBAEWCA7tFiEE9vO1rZsVIZobnDZ4crxxSMCrLacFAl98rg3ODiYAmQINBFzE 2VsBEADAj1mv5RNr31Hy597sG0eAiTJkfOigNmVhV/53DGVJ6qll7FVHxTCT9Sfz UAZ0J9CQ9cRpOfhiD6RyF
[korganizer] [Bug 427393] Incidence editor crashes deleting template
https://bugs.kde.org/show_bug.cgi?id=427393 John Scott changed: What|Removed |Added Component|general |incidence editors Platform|Debian stable |Debian testing Version|unspecified |5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 427393] New: Incidence editor crashes deleting template
https://bugs.kde.org/show_bug.cgi?id=427393 Bug ID: 427393 Summary: Incidence editor crashes deleting template Product: korganizer Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jsc...@posteo.net Target Milestone: --- Application: korganizer (5.14.1 (20.04.0)) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.8.0-2-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I was making an event from the 'New Event...' dialog with a title and times put in. I made a new template from this and gave it a nameWhen I open the incidence editor, on the command-line I see org.kde.pim.incidenceeditor: free slot calculation: invalid range. range( 0 ) / mSlotResolutionSeconds( 900 ) = 0 Now whenever I try to delete this template, it crashes. Just to try to see if I could make a workaround, I created a second template with a new name and was *apparently* able to delete the first (after restarting, it's still there). Still when I try to delete this apparent last one it crashes again. If I try various combinations of applying, deleting, and/or creating I can get messages like these qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2084, resource id: 46353165, major code: 40 (TranslateCoords), minor code: 0 or QSocketNotifier: Invalid socket 12 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... QSocketNotifier: Invalid socket 34 and type 'Read', disabling... QSocketNotifier: Invalid socket 31 and type 'Read', disabling... QSocketNotifier: Invalid socket 32 and type 'Read', disabling... QSocketNotifier: Invalid socket 38 and type 'Read', disabling... QSocketNotifier: Invalid socket 16 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... What follows is a backtrace that seems more relevant than the Dr. Konqi one to the incidence editor: #0 IncidenceEditorNG::TemplateManagementDialog::slotRemoveTemplate (this=0x7fffe80090e0) at ./src/templatemanagementdialog.cpp:186 #1 0x769188c6 in QtPrivate::QSlotObjectBase::call (a=0x7fffc310, r=0x7fffe80090e0, this=0x568ae0c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #2 doActivate (sender=0x568a9b20, signal_index=9, argv=argv@entry=0x7fffc310) at kernel/qobject.cpp:3870 #3 0x76912830 in QMetaObject::activate (sender=sender@entry=0x568a9b20, m=m@entry=0x778792a0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffc310) at kernel/qobject.cpp:3930 #4 0x7746c762 in QAbstractButton::clicked (this=this@entry=0x568a9b20, _t1=) at .moc/moc_qabstractbutton.cpp:313 #5 0x7746d0ca in QAbstractButtonPrivate::emitClicked (this=this@entry=0x568a9b60) at widgets/qabstractbutton.cpp:415 #6 0x7746e91f in QAbstractButtonPrivate::click (this=this@entry=0x568a9b60) at widgets/qabstractbutton.cpp:408 #7 0x7746eaf1 in QAbstractButton::mouseReleaseEvent (this=0x568a9b20, e=0x7fffc8d0) at widgets/qabstractbutton.cpp:1012 #8 0x773c052e in QWidget::event (this=0x568a9b20, event=0x7fffc8d0) at kernel/qwidget.cpp:9033 #9 0x7738003f in QApplicationPrivate::notify_helper (this=, receiver=0x568a9b20, e=0x7fffc8d0) at kernel/qapplication.cpp:3685 #10 0x77385781 in QApplication::notify(QObject*, QEvent*) () at kernel/qapplication.cpp:3129 #11 0x768e3b62 in QCoreApplication::notifyInternal2 (receiver=0x568a9b20, event=0x7fffc8d0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #12 0x77384696 in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x568a9b20, event=event@entry=0x7fffc8d0, alienWidget=alienWidget@entry=0x568a9b20, nativeWidget=0x7fffe80090e0, buttonDown=, lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2615 #13 0x773d895e in QWidgetWindow::handleMouseEvent (this=0x568ae840, event=0x7fffcb90) at /usr/include/c++/10/bits/atomic_base.h:420 #14 0x773db7ae in QWidgetWindow::event (this=0x568ae840, event=0x7fffcb90) at kernel/qwidgetwindow.cpp:295 #15 0x7738003f in
[kmail2] [Bug 338184] RFE: enable specifying custom headers
https://bugs.kde.org/show_bug.cgi?id=338184 --- Comment #2 from John Scott --- For anyone looking for a quick fix, this can be done on the command-line: kmail -s foo --header In-Reply-To:bar -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 92591] Support for RFC 3676 ( format=flowed/fixed, delsp=yes/no )
https://bugs.kde.org/show_bug.cgi?id=92591 --- Comment #17 from John Scott --- In 2020, there's no reason to not be using soft line wrapping, as opposed to composing mails with non-semantic hard line breaks. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 --- Comment #16 from John Scott --- Created attachment 129456 --> https://bugs.kde.org/attachment.cgi?id=129456=edit New crash information added by DrKonqi akregator (5.14.1 (20.04.0)) using Qt 5.12.5 I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1. The crash *does* happen for me when manually right-clicking and opening in a new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I was able to reproduce with JavaScript disabled, and also opening in a Background Tab. What seems to do it for me is clicking a link beneath the title on an /r/netsec post, which you can get the RSS feed like https://www.reddit.com/r/netsec/.rss -- Backtrace (Reduced): #4 0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent() const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7b6ad178b5 in QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7b6ad1fb8e in QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*, std::unique_ptr >, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7b6c740187 in content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int, int, content::mojom::CreateNewWindowParams const&, content::SessionStorageNamespace*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7b6c44d150 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 --- Comment #17 from John Scott --- Created attachment 129457 --> https://bugs.kde.org/attachment.cgi?id=129457=edit New crash information added by DrKonqi akregator (5.14.1 (20.04.0)) using Qt 5.12.5 I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1. The crash *does* happen for me when manually right-clicking and opening in a new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I was able to reproduce with JavaScript disabled, and also opening in a Background Tab. What seems to do it for me is clicking a link beneath the title on an /r/netsec post, which you can get the RSS feed like https://www.reddit.com/r/netsec/.rss -- Backtrace (Reduced): #4 0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent() const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7b6ad178b5 in QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7b6ad1fb8e in QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*, std::unique_ptr >, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7b6c740187 in content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int, int, content::mojom::CreateNewWindowParams const&, content::SessionStorageNamespace*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7b6c44d150 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 --- Comment #16 from John Scott --- Created attachment 129456 --> https://bugs.kde.org/attachment.cgi?id=129456=edit New crash information added by DrKonqi akregator (5.14.1 (20.04.0)) using Qt 5.12.5 I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1. The crash *does* happen for me when manually right-clicking and opening in a new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I was able to reproduce with JavaScript disabled, and also opening in a Background Tab. What seems to do it for me is clicking a link beneath the title on an /r/netsec post, which you can get the RSS feed like https://www.reddit.com/r/netsec/.rss -- Backtrace (Reduced): #4 0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent() const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7b6ad178b5 in QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7b6ad1fb8e in QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*, std::unique_ptr >, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7b6c740187 in content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int, int, content::mojom::CreateNewWindowParams const&, content::SessionStorageNamespace*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7b6c44d150 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 John Scott changed: What|Removed |Added CC|jsc...@posteo.net | -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 416856] building with openbabel 3.0 not supported
https://bugs.kde.org/show_bug.cgi?id=416856 --- Comment #8 from John Scott --- (In reply to Antonio Rojas from comment #7) > 3.1 is release, I've submitted my patch for review > > https://phabricator.kde.org/D29482 Awesome! OpenBabel 3.1.1 is making its way into Debian Unstable shortly, so when the dust settles it'll be easy to add your patch and get this enabled -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 419836] Events with empty UID are present in akonadi console but not showing up in the calendar
https://bugs.kde.org/show_bug.cgi?id=419836 John Scott changed: What|Removed |Added CC||philippe.roub...@free.fr --- Comment #6 from John Scott --- *** Bug 378391 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 378391] ics merging fails
https://bugs.kde.org/show_bug.cgi?id=378391 John Scott changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from John Scott --- *** This bug has been marked as a duplicate of bug 419836 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388036] Include support for autocrypt
https://bugs.kde.org/show_bug.cgi?id=388036 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] ItemRetrievalManager crash
https://bugs.kde.org/show_bug.cgi?id=408897 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 416856] building with openbabel 3.0 not supported
https://bugs.kde.org/show_bug.cgi?id=416856 --- Comment #6 from John Scott --- (In reply to John Scott from comment #5) > Upstream has given no indication of planning to make a release soon, so I've > filed a bug to bring the CMake issues to their attention. Upstream is now certain that they will release 3.0.1 soon, which will switch to being able to use FindOpenBabel3 and fix many other issues. -- 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 John Scott changed: What|Removed |Added See Also||http://bugs.debian.org/9490 ||42 CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 416856] building with openbabel 3.0 not supported
https://bugs.kde.org/show_bug.cgi?id=416856 John Scott changed: What|Removed |Added See Also||https://github.com/openbabe ||l/openbabel/issues/2148 --- Comment #5 from John Scott --- Upstream has given no indication of planning to make a release soon, so I've filed a bug to bring the CMake issues to their attention. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 92591] Support for RFC 3676 ( format=flowed/fixed, delsp=yes/no )
https://bugs.kde.org/show_bug.cgi?id=92591 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 416856] building with openbabel 3.0 not supported
https://bugs.kde.org/show_bug.cgi?id=416856 John Scott changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||jsc...@posteo.net Ever confirmed|0 |1 --- Comment #2 from John Scott --- This blocks introduction of the molecular editor into Debian, but I hope it'll be possible to enable building it soon: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951674 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 363277] a Telepathy Connection Manager named 'sipe' is missing or it cannot handle protocol 'sipe'
https://bugs.kde.org/show_bug.cgi?id=363277 John Scott changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||jsc...@posteo.net --- Comment #3 from John Scott --- In Debian also. If one tries to make another type of account first, then clicks Office 365/Lync, it acts weird and reopens the dialog for the previous account type. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet
https://bugs.kde.org/show_bug.cgi?id=393002 John Scott changed: What|Removed |Added CC||jsc...@posteo.net --- Comment #17 from John Scott --- Affects Akonadi 19.08.3 on Debian unstable. I worked around by making the appropriate entry with KWalletManager, though this would surely not be useful for anyone using OAuth2. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 402874] Kamoso crashes on launch somewhere in NVIDIA driver
https://bugs.kde.org/show_bug.cgi?id=402874 John Scott changed: What|Removed |Added CC||jsc...@posteo.net --- Comment #3 from John Scott --- I get a similar crash with Intel GPU. See my report downstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916076 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 415100] please support uploading large backtraces
https://bugs.kde.org/show_bug.cgi?id=415100 John Scott changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from John Scott --- *** This bug has been marked as a duplicate of bug 248807 *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 248807] Report with a long backtrace can't be sent (bugzilla 65k limit per comment)
https://bugs.kde.org/show_bug.cgi?id=248807 John Scott changed: What|Removed |Added CC||jsc...@posteo.net --- Comment #18 from John Scott --- *** Bug 415100 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 383923] Start generating backtrace and searching for possible duplicates right after 'Report Bug' button was pressed in crash window
https://bugs.kde.org/show_bug.cgi?id=383923 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 317139] Upload Backtraces only as Attachment to Bug Report instead of posting it in the Comment
https://bugs.kde.org/show_bug.cgi?id=317139 John Scott changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=415100 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 415100] New: please support uploading large backtraces
https://bugs.kde.org/show_bug.cgi?id=415100 Bug ID: 415100 Summary: please support uploading large backtraces Product: drkonqi Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jsc...@posteo.net Target Milestone: --- Flags: corner_case+ I see at #317139 that the choice to include backtraces inline instead of as attachments is intentional. I recently tried to submit a bug report, but my backtrace was so large that Bugzilla could not handle it inline: Error sending the crash report: /Received unexpected error code 114 from bugzilla. Error message was: Comments cannot be longer than 65535 characters../ Please consider using an attachment in this case and see my downstream report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946618 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 John Scott changed: What|Removed |Added Summary|[Wayland] Message viewer|[Wayland] Message viewer |displays only a black |displays only a black |rectangle when restoring|rectangle |from systray| -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414057] [Wayland] Message viewer shows a black screen or is transparent under Wayland
https://bugs.kde.org/show_bug.cgi?id=414057 John Scott changed: What|Removed |Added Status|REPORTED|RESOLVED CC||jsc...@posteo.net Resolution|--- |DUPLICATE --- Comment #2 from John Scott --- *** This bug has been marked as a duplicate of bug 397825 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle when restoring from systray
https://bugs.kde.org/show_bug.cgi?id=397825 --- Comment #7 from John Scott --- *** Bug 414057 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 378391] ics merging fails
https://bugs.kde.org/show_bug.cgi?id=378391 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 411777] import of vcs fails, still says success
https://bugs.kde.org/show_bug.cgi?id=411777 --- Comment #2 from John Scott --- (In reply to Martin Koller from comment #0) > Created attachment 122574 [details] > test vcs > > SUMMARY > A webpage produced the attached vcs file. > When importing it, korganizer shows a blue bar saying "1 incidence was > successfully imported" but in konsole I see the log output: > > Incidence has empty UID. id= 336260 ; summary= "Test" Please fix it. > Ignoring this incidence. > org.kde.pim.kcalcore: The incidence didn't have any UID! Report a bug to > the application that generated this file. > > OBSERVED RESULT > The incidence is not shown in korganizer > > EXPECTED RESULT > Show imported incidence. > When an import finds a missing UID, it should simply generate one and import > the file, instead of just ignoring this file. A user can not control what > content a web server produces and there is zero chance that a user can > convince any company to fix the producer. > Please be more forgiving on broken input. > > SOFTWARE/OS VERSIONS > KDE Frameworks 5.61.0 > Qt 5.13.0 (built against 5.13.0) > The xcb windowing system > openSuse Leap 15.0 The mention of an issue with empty UID looks similar to https://bugs.kde.org/show_bug.cgi?id=378391#c2 , could you take a look? -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 408890] Livepreview runs BibTeX instead of Biber
https://bugs.kde.org/show_bug.cgi?id=408890
John Scott changed:
What|Removed |Added
Flags||corner_case+
Ever confirmed|0 |1
CC||jsc...@posteo.net
Status|REPORTED|CONFIRMED
--- Comment #2 from John Scott ---
@abyss Except for the fact that running Biber from the menu doesn't work for me
(maybe it was a fluke), I am able to reproduce your issue on 2.9.93.
You're right. It does seem like giving the full path to Biber makes the
difference. First I made a healthy LaTeX document like this with all of my
settings normal and it was able to build fine:
\documentclass{article}``
\usepackage[backend=biber, style=alphabetic]{biblatex}
\addbibresource{Reference.bib}
\begin{document}
\begin{abstract}
\end{abstract}
Test \cite{whomstever}
\section{One}
\end{document}
After that, I go to the settings and change Biber to its full path,
/usr/bin/biber in my case. I go down the Build menu to Reset Auto-Detected Back
End, and typing a little more, the live preview still works fine.
If I take out the \cite{} and save, then it breaks as you described. Resetting
the auto-detected backend doesn't make a difference. Changing the setting to
Biber explicitly makes it work. Switching it to Auto-Detect after that keeps
using Biber. But if you try to write \cite{} again, it will switch to BibTeX.
Kile always does the right thing if Biber isn't given as a full path.
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 408296] KDEInit could not launch /usr/bin/kile
https://bugs.kde.org/show_bug.cgi?id=408296 John Scott changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||jsc...@posteo.net Ever confirmed|0 |1 --- Comment #2 from John Scott --- Also with 2.9.93 on Debian Buster -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 411777] import of vcs fails, still says success
https://bugs.kde.org/show_bug.cgi?id=411777 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 410590] Dragon crashes when closing playing video
https://bugs.kde.org/show_bug.cgi?id=410590 --- Comment #1 from John Scott --- Created attachment 121932 --> https://bugs.kde.org/attachment.cgi?id=121932=edit WebM backtrace the backtrace included with my report was from playing an MP4 video -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 410590] New: Dragon crashes when closing playing video
https://bugs.kde.org/show_bug.cgi?id=410590 Bug ID: 410590 Summary: Dragon crashes when closing playing video Product: dragonplayer Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sit...@kde.org Reporter: jsc...@posteo.net CC: myr...@kde.org Target Milestone: --- Application: dragon (17.08.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: This happens to me nearly every time playing MP4 and WebM videos with Dragon and closing the window. However, it doesn't occur if I pause the video first. The file size doesn't seem to make a difference, even a 9 MB video can cause the crash also. The crash can be reproduced every time. -- Backtrace: Application: Dragon Player (dragon), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb5a62126c0 (LWP 9202))] Thread 4 (Thread 0x7fb57ea29700 (LWP 9207)): #0 0x7fb5aa45900c in futex_wait_cancelable (private=0, expected=0, futex_word=0x557a4e2de628) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb5aa45900c in __pthread_cond_wait_common (abstime=0x0, mutex=0x557a4e2de5d8, cond=0x557a4e2de600) at pthread_cond_wait.c:502 #2 0x7fb5aa45900c in __pthread_cond_wait (cond=0x557a4e2de600, mutex=0x557a4e2de5d8) at pthread_cond_wait.c:655 #3 0x7fb57eff1e03 in cnd_wait (mtx=0x557a4e2de5d8, cond=0x557a4e2de600) at ../src/../include/c11/threads_posix.h:155 #4 0x7fb57eff1e03 in util_queue_thread_func (input=input@entry=0x557a4e39f740) at ../src/util/u_queue.c:270 #5 0x7fb57eff1b57 in impl_thrd_routine (p=) at ../src/../include/c11/threads_posix.h:87 #6 0x7fb5aa452fa3 in start_thread (arg=) at pthread_create.c:486 #7 0x7fb5aadb44cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fb59f929700 (LWP 9204)): #0 0x7fb5a97a2e84 in g_mutex_unlock (mutex=0x7fb598000bf0) at ../../../glib/gthread-posix.c:1355 #1 0x7fb5a9758fed in g_main_context_iterate (context=context@entry=0x7fb598000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3868 #2 0x7fb5a975925c in g_main_context_iteration (context=0x7fb598000bf0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3981 #3 0x7fb5ab43e87b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fb598000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb5ab3ec27b in QEventLoop::exec(QFlags) (this=this@entry=0x7fb59f928d30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7fb5ab23bec6 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7fb5ab694545 in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fb5ab245aa7 in QThreadPrivate::start(void*) (arg=0x7fb5ab714d60) at thread/qthread_unix.cpp:367 #8 0x7fb5aa452fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7fb5aadb44cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fb5a5454700 (LWP 9203)): #0 0x7fb5aada9819 in __GI___poll (fds=0x7fb5a5453c78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb5aa413cf7 in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fb5aa41591a in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fb5a5dc6d79 in QXcbEventReader::run() (this=0x557a4e0dec00) at qxcbconnection.h:409 #4 0x7fb5ab245aa7 in QThreadPrivate::start(void*) (arg=0x557a4e0dec00) at thread/qthread_unix.cpp:367 #5 0x7fb5aa452fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7fb5aadb44cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fb5a62126c0 (LWP 9202)): [KCrash Handler] #6 0x7fb5aacf27bb in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fb5aacdd535 in __GI_abort () at abort.c:79 #8 0x7fb5a9168e58 in flush (f=) at pulsecore/fdsem.c:170 #9 0x7fb5a9168e58 in flush (f=0x557a4e4ef6e0) at pulsecore/fdsem.c:139 #10 0x7fb5a916982f in pa_fdsem_after_poll (f=0x557a4e4ef6e0) at pulsecore/fdsem.c:314 #11 0x7fb5a91813ed in semread_cb (m=, e=, fd=, events=, userdata=0x557a4e94cd80) at pulsecore/srbchannel.c:209 #12 0x7fb5aa1aa3d6 in dispatch_func (source=0x557a4e2f88c0, callback=, userdata=) at pulse/glib-mainloop.c:203 #13 0x7fb5a9758f2e in g_main_dispatch (context=0x7fb5a0004ff0) at ../../../glib/gmain.c:3182 #14 0x7fb5a9758f2e in g_main_context_dispatch (context=context@entry=0x7fb5a0004ff0) at ../../../glib/gmain.c:3847 #15 0x7fb5a97591c8 in g_main_context_iterate
[frameworks-ki18n] [Bug 386053] i18ncp() incorrectly appends I18N_EXCESS_ARGUMENTS_SUPPLIED when singular and plural format strings use different variables
https://bugs.kde.org/show_bug.cgi?id=386053 John Scott changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=370940 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370940] DPI field shows: 300 DPI (I18N_EXCESS_ARGUMENTS_SUPPLIED)
https://bugs.kde.org/show_bug.cgi?id=370940 John Scott changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=386053 --- Comment #2 from John Scott --- I think #386053 might be related -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403359] Kontact crashes when closing email window
https://bugs.kde.org/show_bug.cgi?id=403359 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 405881] Kopete crash when trying to manage xoauth2 tokens
https://bugs.kde.org/show_bug.cgi?id=405881 --- Comment #3 from John Scott --- (In reply to John Scott from comment #2) > I've got this backtrace on Debian Buster with Kopete 1.13. Forgot my backtrace. Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 Kopete::PasswordedAccount::password (this=0x0) at ./libkopete/kopetepasswordedaccount.cpp:46 #7 0x7fe7cb3fbd0c in DlgJabberXOAuth2::DlgJabberXOAuth2 (this=0x5609650b3500, account=, parent=) at ./protocols/jabber/ui/dlgjabberxoauth2.cpp:34 #8 0x7fe7cb3e52ae in JabberEditAccountWidget::slotManageXOAuth2Clicked (this=0x5609652c92c0) at ./protocols/jabber/ui/jabbereditaccountwidget.cpp:441 #9 0x7fe7d9c5ac90 in QMetaObject::activate (sender=sender@entry=0x56096525c360, m=m@entry=0x7fe7d9a0cf80 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd5ca4f760) at kernel/qobject.cpp:3567 #10 0x7fe7d9760b82 in QAbstractButton::clicked (this=this@entry=0x56096525c360, _t1=) at .moc/release-shared/moc_qabstractbutton.cpp:219 #11 0x7fe7d94bea35 in QAbstractButtonPrivate::emitClicked (this=0x5609651e1fa0) at widgets/qabstractbutton.cpp:548 #12 0x7fe7d94bfde4 in QAbstractButtonPrivate::click (this=0x5609651e1fa0) at widgets/qabstractbutton.cpp:541 #13 0x7fe7d94bfed4 in QAbstractButton::mouseReleaseEvent (this=0x56096525c360, e=0x7ffd5ca4fc80) at widgets/qabstractbutton.cpp:1123 #14 0x7fe7d9179a28 in QWidget::event (this=0x56096525c360, event=0x7ffd5ca4fc80) at kernel/qwidget.cpp:8590 #15 0x7fe7d9127a2c in QApplicationPrivate::notify_helper (this=this@entry=0x560965037f60, receiver=receiver@entry=0x56096525c360, e=e@entry=0x7ffd5ca4fc80) at kernel/qapplication.cpp:4570 #16 0x7fe7d912e3fc in QApplication::notify (this=this@entry=0x7ffd5ca50470, receiver=receiver@entry=0x56096525c360, e=e@entry=0x7ffd5ca4fc80) at kernel/qapplication.cpp:4113 #17 0x7fe7da2eebba in KApplication::notify (this=0x7ffd5ca50470, receiver=0x56096525c360, event=0x7ffd5ca4fc80) at ./kdeui/kernel/kapplication.cpp:311 #18 0x7fe7d9c46afb in QCoreApplication::notifyInternal (this=0x7ffd5ca50470, receiver=receiver@entry=0x56096525c360, event=event@entry=0x7ffd5ca4fc80) at kernel/qcoreapplication.cpp:955 #19 0x7fe7d912db3b in QCoreApplication::sendEvent (event=, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #20 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x56096525c360, event=event@entry=0x7ffd5ca4fc80, alienWidget=alienWidget@entry=0x56096525c360, nativeWidget=nativeWidget@entry=0x560965411d60, buttonDown=buttonDown@entry=0x7fe7d9a1e348 , lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3178 #21 0x7fe7d91a0d84 in QETWidget::translateMouseEvent (this=0x560965411d60, event=) at kernel/qapplication_x11.cpp:4556 #22 0x7fe7d919f9d0 in QApplication::x11ProcessEvent (this=0x7ffd5ca50470, event=event@entry=0x7ffd5ca4ffc0) at kernel/qapplication_x11.cpp:3674 #23 0x7fe7d91c706c in x11EventSourceDispatch (s=0x560965039260, callback=0x0, user_data=0x0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:118 #24 0x7fe7d720af2e in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fe7d720b1c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7fe7d720b25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fe7d9c738e1 in QEventDispatcherGlib::processEvents (this=0x560964ffb8e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #28 0x7fe7d91c71f7 in QGuiEventDispatcherGlib::processEvents (this=, flags=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2436 #29 0x7fe7d9c4538f in QEventLoop::processEvents (this=this@entry=0x7ffd5ca503a0, flags=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2436 #30 0x7fe7d9c4565e in QEventLoop::exec (this=this@entry=0x7ffd5ca503a0, flags=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2452 #31 0x7fe7d9c4ab2a in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qglobal.h:2437 #32 0x560963875f47 in main (argc=3, argv=0x7ffd5ca505d8) at ./kopete/main.cpp:105 [Inferior 1 (process 3261) detached] -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 405881] Kopete crash when trying to manage xoauth2 tokens
https://bugs.kde.org/show_bug.cgi?id=405881 John Scott changed: What|Removed |Added CC||jsc...@posteo.net Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from John Scott --- This happens to me with XMPP too, without having to enter any details. Click to add account -> Jabber -> Connection and then manage the tokens. I've got this backtrace on Debian Buster with Kopete 1.13. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408631] New: Crash when sending Konversation to tray
https://bugs.kde.org/show_bug.cgi?id=408631 Bug ID: 408631 Summary: Crash when sending Konversation to tray Product: plasmashell Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jsc...@posteo.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-5-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: I'm having some trouble reproducing this again, but I hope that my backtrace might shed some light on this. I was using Konversation a few hours ago, having been playing with the On-Screen Display settings. I might've kept the configuration dialog open, but anyway closing the main window made Plasma crash somehow. I'll keep playing with it and update if I can reproduce it. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc5b6473840 (LWP 753))] Thread 13 (Thread 0x7fc5759dc700 (LWP 9053)): #0 0x7fc5bb476819 in __GI___poll (fds=0x7fc558001b30, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc5b91e6101 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7fc5b91d7920 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fc5b91d7f6e in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fc5b91d8020 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fc5b91e6049 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fc5b748f4f8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #7 0x7fc5ba6abfa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fc5bb4814cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7fc5768a9700 (LWP 5137)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5571e5db0a04) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5571e5db09b0, cond=0x5571e5db09d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5571e5db09d8, mutex=0x5571e5db09b0) at pthread_cond_wait.c:655 #3 0x7fc5bb79025b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5571e5db09b0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x5571e5879410, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7fc595006d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fc59500aae8 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fc595005e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fc59500ab42 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fc595005e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fc595008bb9 in ThreadWeaver::Thread::run() () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fc5bb78faa7 in QThreadPrivate::start (arg=0x7fc570003ce0) at thread/qthread_unix.cpp:367 #12 0x7fc5ba6abfa3 in start_thread (arg=) at pthread_create.c:486 #13 0x7fc5bb4814cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fc5770aa700 (LWP 5136)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5571e5db0a04) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5571e5db09b0, cond=0x5571e5db09d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5571e5db09d8, mutex=0x5571e5db09b0) at pthread_cond_wait.c:655 #3 0x7fc5bb79025b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x5571e5db09b0) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=, mutex=0x5571e5879410, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7fc595006d30 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fc59500aae8 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fc595005e3d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fc59500ab42 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fc595005e3d in
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report
https://bugs.kde.org/show_bug.cgi?id=381644 John Scott changed: What|Removed |Added CC||jsc...@posteo.net --- Comment #21 from John Scott --- Dr. Konqi crashed trying to get a new backtrace for Plasma, and I think my crash might be related. Application: drkonqi (drkonqi), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff3e4952840 (LWP 1312))]h Thread 4 (Thread 0x7ff3d963a700 (LWP 1348)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x56438d1bb908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56438d1bb8b8, cond=0x56438d1bb8e0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56438d1bb8e0, mutex=0x56438d1bb8b8) at pthread_cond_wait.c:655 #3 0x7ff3d9c1ce63 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7ff3d9c1cbb7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7ff3e8bd7fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff3e93944cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff3e1b60700 (LWP 1316)): #0 __GI___libc_read (nbytes=16, buf=0x7ff3e1b5fb10, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7ff3e1b5fb10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7ff3e8029aa0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff3e7fe3c0f in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff3e7fe40e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff3e7fe425c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7ff3e989b87b in QEventDispatcherGlib::processEvents (this=0x7ff3d4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7ff3e984927b in QEventLoop::exec (this=this@entry=0x7ff3e1b5fd30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7ff3e9698ec6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7ff3ea6d5545 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7ff3e96a2aa7 in QThreadPrivate::start (arg=0x7ff3ea755d60) at thread/qthread_unix.cpp:367 #11 0x7ff3e8bd7fa3 in start_thread (arg=) at pthread_create.c:486 #12 0x7ff3e93944cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff3e3b8e700 (LWP 1313)): #0 0x7ff3e9389819 in __GI___poll (fds=0x7ff3e3b8dc78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff3e7f70cf7 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff3e7f7291a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff3e44f6d79 in QXcbEventReader::run (this=0x56438ce0b300) at qxcbconnection.h:409 #4 0x7ff3e96a2aa7 in QThreadPrivate::start (arg=0x56438ce0b300) at thread/qthread_unix.cpp:367 #5 0x7ff3e8bd7fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff3e93944cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff3e4952840 (LWP 1312)): [KCrash Handler] #6 0x56438cd0a6e9 in BacktraceLine::type (this=0x56438dcfc308) at ./src/parser/backtraceline.h:59 #7 GdbHighlighter::highlightBlock (this=this@entry=0x7ff3dc00b290, text=...) at ./src/gdbhighlighter.cpp:80 #8 0x7ff3e9d49f39 in QSyntaxHighlighterPrivate::reformatBlock (this=this@entry=0x7ff3dc00a2d0, block=...) at text/qsyntaxhighlighter.cpp:201 #9 0x7ff3e9d4a0f8 in QSyntaxHighlighterPrivate::reformatBlocks (this=0x7ff3dc00a2d0, from=, charsRemoved=, charsAdded=14) at text/qsyntaxhighlighter.cpp:182 #10 0x7ff3e9873906 in QMetaObject::activate (sender=0x56438d007be0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3771 #11 0x7ff3e9f7640a in QTextDocument::contentsChange (this=this@entry=0x56438d007be0, _t1=, _t2=, _t3=) at .moc/moc_qtextdocument.cpp:383 #12 0x7ff3e9d084f1 in QTextDocumentPrivate::finishEdit (this=0x56438d022b00) at text/qtextdocument_p.cpp:1217 #13 0x7ff3e9d08751 in QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1201 #14 QTextDocumentPrivate::endEditBlock (this=) at text/qtextdocument_p.cpp:1184 #15 0x7ff3ea3a03f5 in QWidgetTextControlPrivate::append (this=0x56438d0084e0, text=..., format=format@entry=Qt::AutoText) at widgets/qwidgettextcontrol.cpp:3136 #16 0x7ff3ea3a049e in QWidgetTextControl::append (this=, text=...) at widgets/qwidgettextcontrol.cpp:3142 #17 0x7ff3ea37cd89 in QTextEdit::append (this=, text=...) at widgets/qtextedit.cpp:2626 #18 0x56438ccf9160 in BacktraceWidget::backtraceNewLine (this=, line=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:436 #19 0x7ff3e9873a43 in
[plasmashell] [Bug 374273] Plasma crash when dragging person widget to the desktop
https://bugs.kde.org/show_bug.cgi?id=374273 John Scott changed: What|Removed |Added CC||jsc...@posteo.net --- Comment #3 from John Scott --- This might be fixed by https://phabricator.kde.org/D14232 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 407666] New: Dial phone number with tel:// and sms:// via xdg
https://bugs.kde.org/show_bug.cgi?id=407666 Bug ID: 407666 Summary: Dial phone number with tel:// and sms:// via xdg Product: kaddressbook Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jsc...@posteo.net CC: to...@kde.org Target Milestone: --- Support for dialing phone numbers from contacts is handled in the Configure dialog, choosing a program such as Ekiga or Skype. With KDE Connect's tel:// URL handler, most programs on my system can tell my phone to dial a number this way without extra configuration, including Firefox and Okular. KAddressBook is an exception, because it seems to require its own configuration for setting how to dial a number instead of using the mechanism these other programs utilize. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 338184] RFE: enable specifying custom headers
https://bugs.kde.org/show_bug.cgi?id=338184 John Scott changed: What|Removed |Added Summary|RFE: allow me specify the |RFE: enable specifying |in-reply-to/references |custom headers |headers explicitly | CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kgraphviewer] [Bug 394116] Copyright declarations are inconsistent and unclear
https://bugs.kde.org/show_bug.cgi?id=394116 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 354512] Please omit the "Comment" field from key generation dialog box.
https://bugs.kde.org/show_bug.cgi?id=354512 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 130529] support for rss on https protokol missing
https://bugs.kde.org/show_bug.cgi?id=130529 John Scott changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from John Scott --- This bug is old, and Akregator has supported HTTPS for a long time now. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 John Scott changed: What|Removed |Added CC||hast0...@gmail.com --- Comment #40 from John Scott --- *** Bug 357281 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 273391] Akregator should not ask to restore session if there is nothing to restore
https://bugs.kde.org/show_bug.cgi?id=273391 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 357281] the date of a specific feed are completely wrong
https://bugs.kde.org/show_bug.cgi?id=357281 John Scott changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from John Scott --- *** This bug has been marked as a duplicate of bug 256034 *** -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 402176] Cantor crashes when trying to execute cell with SageMath backend
https://bugs.kde.org/show_bug.cgi?id=402176 John Scott changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=404752 Platform|Debian stable |Debian testing CC||jsc...@posteo.net --- Comment #2 from John Scott --- Per #404752 which I reported, your crash was probably caused by an issue in Debian. Can you check whether this occurs after upgrading to sagemath 8.6-6? -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 404752] Cantor crashes with Sage backend
https://bugs.kde.org/show_bug.cgi?id=404752 John Scott changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=402176 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 404752] Cantor crashes with Sage backend
https://bugs.kde.org/show_bug.cgi?id=404752 John Scott changed: What|Removed |Added Resolution|NOT A BUG |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 John Scott changed: What|Removed |Added CC||anand.chi...@gmail.com --- Comment #39 from John Scott --- *** Bug 262271 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.
https://bugs.kde.org/show_bug.cgi?id=262271 John Scott changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #19 from John Scott --- *** This bug has been marked as a duplicate of bug 256034 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.
https://bugs.kde.org/show_bug.cgi?id=262271 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370940] DPI field shows: 300 DPI (I18N_EXCESS_ARGUMENTS_SUPPLIED)
https://bugs.kde.org/show_bug.cgi?id=370940 John Scott changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406167] New: Show all messages in mbox
https://bugs.kde.org/show_bug.cgi?id=406167 Bug ID: 406167 Summary: Show all messages in mbox Product: kmail2 Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: jsc...@posteo.net Target Milestone: --- I find it handy to download mbox files with multiple messages, mostly for the sake of working with Debian's BTS. Opening an mbox for a bug shows "The file contains multiple messages. Only the first message is shown." It would be nice to see the other messages inside. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 314087] Use marble to show addresses and coordinates
https://bugs.kde.org/show_bug.cgi?id=314087 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 406047] New: '\' character at end of displayed address
https://bugs.kde.org/show_bug.cgi?id=406047 Bug ID: 406047 Summary: '\' character at end of displayed address Product: kaddressbook Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jsc...@posteo.net CC: to...@kde.org Target Milestone: --- Created attachment 119158 --> https://bugs.kde.org/attachment.cgi?id=119158=edit screenshot showing contact's address I use my CalDAV/CardDAV account with Posteo across several devices. Addresses display fine with Google's Contacts for Android (the app with which most contacts and addresses were created) and also with Contacts on macOS. KAddressBook often shows a "\" at the end of the first address line, but the other clients display the addresses fine, so I'm assuming this is a bug in KAddressBook. Right-clicking and choosing to copy the address also includes the backslash, but it's not visible in the editor. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14 KDE Frameworks Version: 5.54 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 370940] DPI field shows: 300 DPI (I18N_EXCESS_ARGUMENTS_SUPPLIED)
https://bugs.kde.org/show_bug.cgi?id=370940 John Scott changed: What|Removed |Added Platform|Other |Debian stable CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403159] Blank page on print and print preview
https://bugs.kde.org/show_bug.cgi?id=403159 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404492] Kmail show empty printpreview and crashes after closing it, and producing empty print
https://bugs.kde.org/show_bug.cgi?id=404492 --- Comment #3 from John Scott --- (In reply to Wolfgang Bauer from comment #2) > (In reply to John Scott from comment #1) > And the crash looks like another duplicate of bug#398577... I believe that might've been DrKonqi's initial suggestion too, but that bug pertains to Kontact, which I wasn't using when I had the crash. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404492] Kmail show empty printpreview and crashes after closing it, and producing empty print
https://bugs.kde.org/show_bug.cgi?id=404492 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404492] Kmail show empty printpreview and crashes after closing it, and producing empty print
https://bugs.kde.org/show_bug.cgi?id=404492 --- Comment #1 from John Scott --- Created attachment 118920 --> https://bugs.kde.org/attachment.cgi?id=118920=edit New crash information added by DrKonqi kmail (5.9.3) using Qt 5.11.3 I've found this bug with 18.08.3 on Debian Buster. -- Backtrace (Reduced): #7 0x7fe9a2704d95 in content::RenderProcessHostImpl::ShutdownRequest() () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fe9a1f022a5 in content::mojom::RendererHostStubDispatch::Accept(content::mojom::RendererHost*, mojo::Message*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fe9a3b81959 in IPC::(anonymous namespace)::ChannelAssociatedGroupController::AcceptOnProxyThread(mojo::Message) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7fe9a3b8143e in void base::internal::Invoker, base::internal::PassedWrapper >, void ()>::RunImpl, base::internal::PassedWrapper > const&, 0ul, 1ul>(void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::* const&)(mojo::Message), std::tuple, base::internal::PassedWrapper > const&, std::integer_sequence) [clone .isra.234] () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7fe9a32bb688 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403065] Akregator crashes when adding link
https://bugs.kde.org/show_bug.cgi?id=403065 --- Comment #1 from John Scott --- Created attachment 118848 --> https://bugs.kde.org/attachment.cgi?id=118848=edit New crash information added by DrKonqi akregator (5.9.3) using Qt 5.11.3 I experienced this on Debian, previewing feeds in Firefox which invoked Akregator. It takes 15 seconds or so for it to crash. I hope my backtrace can be helpful. It could be a coincidence, but I did notice after subscribing to the feed that it showed in 'Imported Folder,' but the feed doesn't have a name and the icon is an 'x' in a bubble. -- Backtrace (Reduced): #6 0x7f78efd05dbf in Akregator::Feed::slotAddToFetchQueue (this=0x5626423d3910, queue=0x562641cc8f70, intervalFetchOnly=) at ./src/feed/feed.cpp:535 #7 0x7f78efd1aff1 in Akregator::Folder::slotAddToFetchQueue (this=, queue=0x562641cc8f70, intervalFetchOnly=true) at ./src/folder.cpp:389 #8 0x7f78ee7da703 in QtPrivate::QSlotObjectBase::call (a=0x7ffdb25a93e0, r=0x562641b1db00, this=0x562641ca83e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 [...] #10 0x7f78ee7e62d7 in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:200 #11 0x7f78ee7dae0b in QObject::event (this=0x562641c14c10, e=) at kernel/qobject.cpp:1232 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403065] Akregator crashes when adding link
https://bugs.kde.org/show_bug.cgi?id=403065 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404881] Kontact crashes when closing Akregator from tray icon
https://bugs.kde.org/show_bug.cgi?id=404881 John Scott changed: What|Removed |Added Component|general |akregator -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 206527] Be able to split the main editorwindow
https://bugs.kde.org/show_bug.cgi?id=206527 John Scott changed: What|Removed |Added Status|REPORTED|RESOLVED CC||jsc...@posteo.net Resolution|--- |DUPLICATE --- Comment #3 from John Scott --- *** This bug has been marked as a duplicate of bug 143918 *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 143918] [wish] being able to split editing window
https://bugs.kde.org/show_bug.cgi?id=143918 John Scott changed: What|Removed |Added CC||didier.heris...@gmail.com --- Comment #9 from John Scott --- *** Bug 206527 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 405245] Enable showing document preview in separate window
https://bugs.kde.org/show_bug.cgi?id=405245 John Scott changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 405245] New: Enable showing document preview in separate window
https://bugs.kde.org/show_bug.cgi?id=405245 Bug ID: 405245 Summary: Enable showing document preview in separate window Product: kile Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: jsc...@posteo.net Target Milestone: --- On my laptop, I have limited screen real estate for both editing and previewing my document. Keeping document preview in a separate window would make Kile more nice to use on multiple displays. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404881] Kontact crashes when closing Akregator from tray icon
https://bugs.kde.org/show_bug.cgi?id=404881 John Scott changed: What|Removed |Added OS|NetBSD |Linux -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404881] Kontact crashes when closing Akregator from tray icon
https://bugs.kde.org/show_bug.cgi?id=404881 John Scott changed: What|Removed |Added OS|Linux |NetBSD Platform|Debian stable |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 404881] New: Kontact crashes when closing Akregator from tray icon
https://bugs.kde.org/show_bug.cgi?id=404881 Bug ID: 404881 Summary: Kontact crashes when closing Akregator from tray icon Product: kontact Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jsc...@posteo.net Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-2-amd64 x86_64 Distribution: Debian GNU/Linux buster/sid -- Information about the crash: On my system, I open Kontact and navigate to Feeds. When I secondary click on the icon and choose Quit, Kontact crashes. I can reproduce on X11 and Wayland. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa36988df00 (LWP 1928))] Thread 29 (Thread 0x7fa285a7f700 (LWP 12706)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7fa285a7e400, expected=0, futex_word=0x7fa285a7e5e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fa285a7e4a0, mutex=0x7fa285a7e598, cond=0x7fa285a7e5c0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fa285a7e5c0, mutex=0x7fa285a7e598, abstime=0x7fa285a7e4a0) at pthread_cond_wait.c:667 #3 0x7fa377800a37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fa37780330a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fa3778033f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fa377807981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fa377808c7f in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fa377811c81 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fa37dc6bfa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fa37ee2680f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fa280238700 (LWP 12705)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7fa280237400, expected=0, futex_word=0x7fa2802375e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fa2802374a0, mutex=0x7fa280237598, cond=0x7fa2802375c0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fa2802375c0, mutex=0x7fa280237598, abstime=0x7fa2802374a0) at pthread_cond_wait.c:667 #3 0x7fa377800a37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fa37780330a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fa3778033f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fa377807981 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fa377808e61 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fa377811c81 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fa37dc6bfa3 in start_thread (arg=) at pthread_create.c:486 #10 0x7fa37ee2680f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fa27a6a8700 (LWP 12703)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7fa27a6a7400, expected=0, futex_word=0x7fa27a6a75e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fa27a6a74a0, mutex=0x7fa27a6a7598, cond=0x7fa27a6a75c0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fa27a6a75c0, mutex=0x7fa27a6a7598, abstime=0x7fa27a6a74a0) at pthread_cond_wait.c:667 #3 0x7fa377800a37 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fa37780330a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fa3778033f2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fa377807981 in
[cantor] [Bug 404752] Cantor crashes with Sage backend
https://bugs.kde.org/show_bug.cgi?id=404752 John Scott changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from John Scott --- (In reply to Alexander Semke from comment #1) > The code in SageSession::updateSageVersion() needs to be made more stable... > > What does 'sage -v' returns on your computer? No, it doesn't. On my system, it returns /usr/bin/sage: line 16: /src/bin/sage-version.sh: No such file or directory which is clearly a bug in Debian's SageMath package. I'll file it downstream, thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 404752] Cantor crashes with Sage backend
https://bugs.kde.org/show_bug.cgi?id=404752 John Scott changed: What|Removed |Added Platform|Debian stable |Debian testing Version|unspecified |18.12 Component|general |sage-backend -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 404752] New: Cantor crashes with Sage backend
https://bugs.kde.org/show_bug.cgi?id=404752
Bug ID: 404752
Summary: Cantor crashes with Sage backend
Product: cantor
Version: unspecified
Platform: Debian stable
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: fil...@kde.org
Reporter: jsc...@posteo.net
CC: alexander.se...@web.de, alexanderrie...@gmail.com
Target Milestone: ---
Application: cantor (18.12.0)
Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-2-amd64 x86_64
Distribution: Debian GNU/Linux buster/sid
-- Information about the crash:
My backtrace was obtained when I'd been using Wayland, but the crash happens on
X11 also. The crash occurs when trying to execute any command at all, including
when using the menus.
Here's the command-line output when it crashes.
Using Wayland-EGL
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/backends"
Creating MaximaBackend
Creating NullBackend
Creating SageBackend
dir: "/usr/bin/cantor/backends"
Backend "Sage" offers extensions: ("HistoryExtension", "ScriptExtension",
"CASExtension", "CalculusExtension", "LinearAlgebraExtension", "PlotExtension",
"PackagingExtension")
Spawning a new Sage session
new worksheetaccess interface
loading assistants...
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/assistants"
plugin "AdvancedPlot" is not supported by "Sage"
plugin "Create Matrix" is supported by "Sage" , requires extensions
("LinearAlgebraExtension")
plugin "Differentiate" is supported by "Sage" , requires extensions
("CalculusExtension")
plugin "Eigenvalues" is supported by "Sage" , requires extensions
("LinearAlgebraExtension", "HistoryExtension")
plugin "Eigenvectors" is supported by "Sage" , requires extensions
("LinearAlgebraExtension", "HistoryExtension")
plugin "Import Package" is supported by "Sage" , requires extensions
("PackagingExtension")
plugin "Integrate" is supported by "Sage" , requires extensions
("CalculusExtension")
plugin "Invert Matrix" is supported by "Sage" , requires extensions
("LinearAlgebraExtension", "HistoryExtension")
plugin "Plot2d" is supported by "Sage" , requires extensions
("PlotExtension")
plugin "Plot3d" is supported by "Sage" , requires extensions
("PlotExtension")
plugin "QalculatePlot" is not supported by "Sage"
plugin "RunScript" is supported by "Sage" , requires extensions
("ScriptExtension")
plugin "Solve" is supported by "Sage" , requires extensions
("CASExtension")
dir: "/usr/bin/cantor/assistants"
loading panel plugins for session of type "Sage"
Requesting capabilities of SageSession
dir: "/usr/lib/x86_64-linux-gnu/qt5/plugins/cantor/panels"
plugin "Help" is supported, requires extensions ("")
plugin "Variable Manager" is not supported
dir: "/usr/bin/cantor/panels"
Requesting capabilities of SageSession
Entry Appended
adding panel for "Help"
Using the 'xdg-shell-v6' shell integration
ShortcutOverride 16777220 QFlags(ShiftModifier)
login
found version: ()
The crash can be reproduced every time.
-- Backtrace:
Application: Cantor (cantor), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7fa1a2b800 (LWP 13000))]
Thread 3 (Thread 0x7f7f974e8700 (LWP 13002)):
#0 futex_wait_cancelable (private=0, expected=0, futex_word=0x558ea1a453d8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x558ea1a45388,
cond=0x558ea1a453b0) at pthread_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x558ea1a453b0, mutex=0x558ea1a45388) at
pthread_cond_wait.c:655
#3 0x7f7f97743a32 in cnd_wait (mtx=0x558ea1a45388, cond=0x558ea1a453b0) at
../src/../include/c11/threads_posix.h:155
#4 util_queue_thread_func (input=input@entry=0x558ea1ad3bb0) at
../src/util/u_queue.c:270
#5 0x7f7f977435f7 in impl_thrd_routine (p=) at
../src/../include/c11/threads_posix.h:87
#6 0x7f7fa5436fa3 in start_thread (arg=) at
pthread_create.c:486
#7 0x7f7fa60ca80f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 2 (Thread 0x7f7f9e7e2700 (LWP 13001)):
#0 __GI___libc_read (nbytes=16, buf=0x7f7f9e7e1b50, fd=5) at
../sysdeps/unix/sysv/linux/read.c:26
#1 __GI___libc_read (fd=5, buf=buf@entry=0x7f7f9e7e1b50,
nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2 0x7f7fa48f6aa0 in read (__nbytes=16, __buf=0x7f7f9e7e1b50,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#3 g_wakeup_acknowledge (wakeup=0x7f7f98001510) at ../../../glib/gwakeup.c:210
#4 0x7f7fa48b0c0f in g_main_context_check
(context=context@entry=0x7f7f98001cb0, max_priority=2147483647,
fds=fds@entry=0x7f7f98005440, n_fds=n_fds@entry=1) at
../../../glib/gmain.c:3698
#5 0x7f7fa48b10e0 in g_main_context_iterate
[kontact] [Bug 398577] closing a message subwindow crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=398577 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 404164] Crashes when saving document upon closing
https://bugs.kde.org/show_bug.cgi?id=404164 John Scott changed: What|Removed |Added Platform|Debian stable |Debian testing -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 404164] New: Crashes when saving document upon closing
https://bugs.kde.org/show_bug.cgi?id=404164 Bug ID: 404164 Summary: Crashes when saving document upon closing Product: kile Version: 2.9.92 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: jsc...@posteo.net Target Milestone: --- Application: kile (2.9.92) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-2-amd64 x86_64 Distribution: Debian GNU/Linux buster/sid -- Information about the crash: Closing Kile without saving a document first and proceeding to save as suggested makes Kile crash, but doesn't have any practical consequences and is an annoyance at worst. I reported it downstream [1] where someone chimed in with details on the probable upstream issue. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919030 The crash can be reproduced every time. -- Backtrace: Application: Kile (kile), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=0, expected=0, futex_word=0x55b22ef72190) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 [Current thread is 1 (Thread 0x7fd057feb880 (LWP 3911))] Thread 5 (Thread 0x7fcffbfff700 (LWP 5830)): #0 0x7fd06294a289 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fd05d023f1a in g_cond_wait_until (cond=cond@entry=0x55b22ed02a68, mutex=mutex@entry=0x55b22ed02a60, end_time=end_time@entry=12062223028) at ../../../glib/gthread-posix.c:1449 #2 0x7fd05cfac051 in g_async_queue_pop_intern_unlocked (queue=queue@entry=0x55b22ed02a60, wait=wait@entry=1, end_time=end_time@entry=12062223028) at ../../../glib/gasyncqueue.c:422 #3 0x7fd05cfac611 in g_async_queue_timeout_pop (queue=0x55b22ed02a60, timeout=timeout@entry=1500) at ../../../glib/gasyncqueue.c:545 #4 0x7fd05d002d61 in g_thread_pool_wait_for_new_pool () at ../../../glib/gthreadpool.c:167 #5 0x7fd05d002d61 in g_thread_pool_thread_proxy (data=) at ../../../glib/gthreadpool.c:364 #6 0x7fd05d002325 in g_thread_proxy (data=0x7fd008005190) at ../../../glib/gthread.c:784 #7 0x7fd05fac0fa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7fd06294f80f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fd04d2e6700 (LWP 3916)): #0 0x7fd05fac6fbc in futex_wait_cancelable (private=0, expected=0, futex_word=0x55b22efde638) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd05fac6fbc in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b22efde5e8, cond=0x55b22efde610) at pthread_cond_wait.c:502 #2 0x7fd05fac6fbc in __pthread_cond_wait (cond=0x55b22efde610, mutex=0x55b22efde5e8) at pthread_cond_wait.c:655 #3 0x7fd04d8caa32 in cnd_wait (mtx=0x55b22efde5e8, cond=0x55b22efde610) at ../src/../include/c11/threads_posix.h:155 #4 0x7fd04d8caa32 in util_queue_thread_func (input=input@entry=0x55b22f31fab0) at ../src/util/u_queue.c:270 #5 0x7fd04d8ca5f7 in impl_thrd_routine (p=) at ../src/../include/c11/threads_posix.h:87 #6 0x7fd05fac0fa3 in start_thread (arg=) at pthread_create.c:486 #7 0x7fd06294f80f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fd04700 (LWP 3914)): [KCrash Handler] #6 0x7fd05fda6cfd in _mm_loadu_si128(long long __vector(2) const*) (__P=) at /usr/lib/gcc/x86_64-linux-gnu/8/include/emmintrin.h:1397 #7 0x7fd05fda6cfd in ucstrncmp (l=, b=0x55b230a21878, a=0xab645fd2c8c0) at tools/qstring.cpp:685 #8 0x7fd05fda6cfd in ucstrcmp(QChar const*, size_t, QChar const*, size_t) (a=a@entry=0xab645fd2c8c0, alen=13, b=0x55b230a21878, blen=11) at tools/qstring.cpp:899 #9 0x7fd05fdacb0a in qt_compare_strings (cs=Qt::CaseSensitive, rhs=..., lhs=...) at ../../include/QtCore/../../src/corelib/tools/qstringview.h:275 #10 0x7fd05fdacb0a in operator<(QString const&, QString const&) (s1=..., s2=...) at tools/qstring.cpp:3214 #11 0x7fd062c75b70 in qMapLessThanKey(QString const&, QString const&) (key2=..., key1=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:69 #12 0x7fd062c75b70 in QMapNode::lowerBound(QString const&) (akey=..., this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:155 #13 0x7fd062c75b70 in QMapData::findNode(QString const&) const (this=, akey=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:287 #14 0x7fd062c72805 in QMap::constFind(QString const&) const (this=0x55b22fceef70, akey=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmap.h:867 #15 0x7fd062c72805 in KileParser::LaTeXParser::parse() (this=0x55b230c874f0) at ./src/parser/latexparser.cpp:186 #16 0x7fd062c79362 in KileParser::ParserThread::run() (this=0x55b22eeff2c0) at ./src/parser/parserthread.cpp:193 #17 0x7fd05fd39cd7 in QThreadPrivate::start(void*)
[kwin] [Bug 387313] Buffer age is broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=387313 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle when restoring from systray
https://bugs.kde.org/show_bug.cgi?id=397825 John Scott changed: What|Removed |Added CC||jsc...@posteo.net --- Comment #6 from John Scott --- I can reproduce on Debian Buster too. Maybe this is related to #402241 as the latter is Wayland-specific and causes more widespread trouble drawing the UI. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 402241] KMail Wayland UI drawing flakiness
https://bugs.kde.org/show_bug.cgi?id=402241 John Scott changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 402241] KMail Wayland UI drawing flakiness
https://bugs.kde.org/show_bug.cgi?id=402241 John Scott changed: What|Removed |Added CC||jsc...@posteo.net --- Comment #1 from John Scott --- I'm experiencing this on Intel graphics too, on Debian Testing. KMail becomes difficult to use when opening multiple KMail windows; they fight with each other if I don't minimize one. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 402539] look for offline Maxima documentation
https://bugs.kde.org/show_bug.cgi?id=402539 --- Comment #2 from John Scott --- (In reply to Nikita Sirgienko from comment #1) That'd be great. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 402539] New: look for offline Maxima documentation
https://bugs.kde.org/show_bug.cgi?id=402539 Bug ID: 402539 Summary: look for offline Maxima documentation Product: cantor Version: 18.08 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: maxima-backend Assignee: alexander.se...@web.de Reporter: jsc...@posteo.net CC: alexanderrie...@gmail.com Target Milestone: --- The "Show Maxima help" button links directly to the docs on their website, though on my system I have installed the docs as packaged by Debian from maxima-doc, and they can be read at /usr/share/doc/maxima-doc/html/maxima.html It would be convenient if there were a way for package maintainers to specify where to look for documentation offline so that it can be opened instead if available. -- You are receiving this mail because: You are watching all bug changes.
