[kwin] [Bug 343184] KWin misdetects trimple-buffering (at least on login)
https://bugs.kde.org/show_bug.cgi?id=343184 Matthias Dahl changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387025] New: KMail crashes when launched
https://bugs.kde.org/show_bug.cgi?id=387025 Bug ID: 387025 Summary: KMail crashes when launched Product: kmail2 Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@carewolf.com Target Milestone: --- Application: kmail (5.6.80) Qt Version: 5.9.1 Frameworks Version: 5.41.0 Operating System: Linux 4.13.0-16-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: After the latest update of neon stable kmail now crashes everytime I try launching it. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f160793b980 (LWP 16829))] Thread 5 (Thread 0x7f15f6ffd700 (LWP 16834)): #0 0x7f162dc0070d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f162252138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f162252149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f162e52894b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f162e4d17ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f162e2facd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f162e2ff989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f16240476ba in start_thread (arg=0x7f15f6ffd700) at pthread_create.c:333 #8 0x7f162dc0c3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f15f77fe700 (LWP 16833)): #0 0x7f1622565a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1622521381 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f162252149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f162e52894b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f162e4d17ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f162e2facd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f162e2ff989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f16240476ba in start_thread (arg=0x7f15f77fe700) at pthread_create.c:333 #8 0x7f162dc0c3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f15f7fff700 (LWP 16832)): #0 0x7f162dc0070d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f162252138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f162252149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f162e52894b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f162e4d17ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f162e2facd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f162e2ff989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f16240476ba in start_thread (arg=0x7f15f7fff700) at pthread_create.c:333 #8 0x7f162dc0c3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f15fd8a8700 (LWP 16831)): #0 0x7f1622565a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f16225209a0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f16225212bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f162252149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f162e52894b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f162e4d17ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f162e2facd4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f163050cb75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f162e2ff989 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f16240476ba in start_thread (arg=0x7f15fd8a8700) at pthread_create.c:333 #10 0x7f162dc0c3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f160793b980 (LWP 16829)): [KCrash Handler] #6 0x7f16255158ca in QExplicitlySharedDataPointer::operator= (o=..., this=0x2825928) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qshareddata.h:188 #7 KConfigGroup::operator= (this=this@entry=0x2825920, rhs=...) at /workspace/build/src/core/kconfiggroup.cpp:512 #8 0x7f1628129081 in Akonadi
[systemsettings] [Bug 382317] Main navigation has disappeared
https://bugs.kde.org/show_bug.cgi?id=382317 --- Comment #9 from Allan Sandfeld --- Hasn't happened in several months now. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 382317] Main navigation has disappeared
https://bugs.kde.org/show_bug.cgi?id=382317 Allan Sandfeld changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #8 from Allan Sandfeld --- Hasn't happened in several months now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 386191] Loading of providers from file https://download.kde.org/ocs/providers.xml failed
https://bugs.kde.org/show_bug.cgi?id=386191 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #5 from Alexander Mentyu --- 'Install' button does nothing for me too when i'm trying to install themes, icons, etc. from GHNS dialog. And also there is no 'Loading of providers from file https://download.kde.org/ocs/providers.xml failed' message in GHNS window - only 'Installation failed' popup after some time. Distribution: KDE neon Developer Edition - Stable Branches Plasma: 5.11.3 Frameworks: 5.41.0 Qt: 5.9.1 Kernel 4.10.0-38-generic Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387026] New: idea: "don't change focus" hotkey
https://bugs.kde.org/show_bug.cgi?id=387026 Bug ID: 387026 Summary: idea: "don't change focus" hotkey Product: kwin Version: unspecified Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- This will probably sound a bit far-fetched, but the more I think about it the more I think it'd be useful for users who like me prefer to do as much as possible with the keyboard: Many applications, among which web browsers, have a feature (sometimes optional) in which the running instance "activates" itself when it receives a document or page reference to open. Even if that's the desired behaviour in most cases, there are also circumstances where you don't want this to happen. Example: I'm scanning my email and/or RSS feeds in Kontakt, say for housing or job ad alerts. I'll be coming across a number of links I'll want to investigate, but I don't want to handle each link serially, going back and forth between apps. Currently, that means I click on a link, then have to move the mouse cursor outside my zone of (mental) focus in order to give the (input) focus back to Kontakt because my browser stole it when coming to the front. (Despite have focus-follows-mouse and the mouse cursor over the Kontakt window.) Let me repeat that often this is wanted behaviour: let a window activate and get focus without having to touch the mouse. I don't see many ways how you can alter this behaviour on a case-by-case basis, but a hotkey feature in the window manager should be a solution. Define a modifier or function key (or any key that usually does nothing useful) to be pressed when or immediately after you click a link or do something that'll cause the designated document handler to activate. When this hotkey is pressed, KWin will not allow focus to change. You might even make this a 2-level feature: optionally KWin could also "freeze" the window stacking order. (Useful on small screens, or if you set your browser to take up the entire screen so the focus window becomes hidden anyway.) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387025] KMail crashes when launched
https://bugs.kde.org/show_bug.cgi?id=387025 --- Comment #1 from Allan Sandfeld --- Valgrind seems to be blocked by drkonqi from seeing the details of the crash, there are few errors before though, but they look unrelated: ==21778== Thread 6 QThread: ==21778== Invalid read of size 2 ==21778==at 0x6D197F9: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x12A35DC0: g_main_context_check (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x12A3632F: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x12A3649B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x6D1992E: QEventDispatcherGlib::processEvents(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6CC27C9: QEventLoop::exec(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6AEBCD3: QThread::exec() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6AF0988: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x10F7E6B9: start_thread (pthread_create.c:333) ==21778==by 0x740C3DC: clone (clone.S:109) ==21778== Address 0x2d94b3f6 is 6 bytes inside a block of size 16 free'd ==21778==at 0x4C2F24B: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==21778==by 0x6CFD105: QSocketNotifier::setEnabled(bool) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6D197F8: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x12A35DC0: g_main_context_check (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x12A3632F: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x12A3649B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x6D1992E: QEventDispatcherGlib::processEvents(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6CC27C9: QEventLoop::exec(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6AEBCD3: QThread::exec() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6AF0988: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x10F7E6B9: start_thread (pthread_create.c:333) ==21778==by 0x740C3DC: clone (clone.S:109) ==21778== Block was alloc'd at ==21778==at 0x4C2E0EF: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==21778==by 0x6D1A471: QEventDispatcherGlib::registerSocketNotifier(QSocketNotifier*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6CFCF87: QSocketNotifier::QSocketNotifier(long long, QSocketNotifier::Type, QObject*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x10074878: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.1) ==21778==by 0x10061E44: QAbstractSocket::setSocketDescriptor(long long, QAbstractSocket::SocketState, QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.1) ==21778==by 0x100781DE: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.1) ==21778==by 0x10078639: QLocalSocket::connectToServer(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Network.so.5.9.1) ==21778==by 0xCE847E9: Akonadi::Connection::doReconnect() (in /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5.6.80) ==21778==by 0xCFAF1A4: Akonadi::Connection::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (in /usr/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5.6.80) ==21778==by 0x6CF1C58: QObject::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x5FF03FB: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.9.1) ==21778==by 0x5FF7E06: QApplication::notify(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.9.1) ==21778== ==21778== Invalid read of size 2 ==21778==at 0x6D19784: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x12A35DC0: g_main_context_check (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x12A3632F: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x12A3649B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==21778==by 0x6D1992E: QEventDispatcherGlib::processEvents(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6CC27C9: QEventLoop::exec(QFlags) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6AEBCD3: QThread::exec() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x6AF0988: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.1) ==21778==by 0x10F7E6B9: start_thread (pthread_create.c:333) ==21778==by 0x740C3DC: clone (clone.S:109) ==21778== Address 0x2d94b3f4 is 4 bytes inside a block of size 16 free'd ==21778==at 0x4C2F24B: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==217
[kde] [Bug 369238] KDevelop5 hang on exit in itemrepository.h (deleteItem())
https://bugs.kde.org/show_bug.cgi?id=369238 Kevin Funk changed: What|Removed |Added CC||argo...@gmail.com --- Comment #3 from Kevin Funk --- *** Bug 387021 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387021] instance hangs after session selection
https://bugs.kde.org/show_bug.cgi?id=387021 Kevin Funk changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kevin Funk --- Yep. Known issue. Difficult to debug/solve. *** This bug has been marked as a duplicate of bug 369238 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 386191] Loading of providers from file https://download.kde.org/ocs/providers.xml failed
https://bugs.kde.org/show_bug.cgi?id=386191 --- Comment #6 from Alexander Mentyu --- My previous comment it's not correct - themes, icons.. are installing but without any notifications or changes of installed addons' buttons in GHNS window. The 'Installation failed' popups are appearing for Dropbox services addons. -- You are receiving this mail because: You are watching all bug changes.
[Purpose] [Bug 387027] New: unversioned genericly named libs
https://bugs.kde.org/show_bug.cgi?id=387027 Bug ID: 387027 Summary: unversioned genericly named libs Product: Purpose Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: sit...@kde.org Target Milestone: --- Currently master installs - libReviewboardHelpers.so - libPhabricatorHelpers.so These helper libs have a too generic name. They should be something like libKF5PurposeReviewboardHelpers. They are also unversioned which is the far larger problem. These libraries are installed into public directories, meaning any application can find them. When KF6 happens this will be a world of trouble as they must be versioned then to keep kf5 and 6 co-installable, at which point an old client can load the new library (the aformentioned name change also helps guard against this). To achieve a similar behavior set a version on the target and install the libraries with `LIBRARY NAMELINK_SKIP`. This will version them but keep them from installing a libfoo.so development symlink to keep them from being easily linked to. This should get fixed before integration into frameworks I think. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 387028] New: upstream change in shared-mime-info breaks KMimeTypeTest autotest
https://bugs.kde.org/show_bug.cgi?id=387028 Bug ID: 387028 Summary: upstream change in shared-mime-info breaks KMimeTypeTest autotest Product: frameworks-kdelibs4support Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: rikmi...@kubuntu.org Target Milestone: --- This upstream change breaks/fails the KMimeTypeTest autotest https://cgit.freedesktop.org/xdg/shared-mime-info/commit/?id=5770d10a79591add24106204c748e5c94b2a0544 "Rename application/x-trig to application/trig" and the test fails with https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/armhf/k/kdelibs4support/20171117_084358_5c7b7@/log.gz FAIL! : KMimeTypeTest::testThreads() Compared values are not the same Actual (lookedupMime->name()): "application/trig" Expected (name): "application/x-trig" Loc: [/tmp/autopkgtest.amJeDY/build.pBk/kdelibs4support-5.38.0/autotests/kmimetypetest.cpp(518)] -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386857] next window shortcut picks a random tab
https://bugs.kde.org/show_bug.cgi?id=386857 --- Comment #5 from Kevin Funk --- I mean that I can't reproduce your issue by activating "Previous window" and "next window". The order in which the active window moves seems fine over here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387019] Plasma shell crash - plasmoids
https://bugs.kde.org/show_bug.cgi?id=387019 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Cannot reproduce this crash in: Distribution: KDE neon Developer Edition - Stable Branches Plasma: 5.11.3 Frameworks: 5.41.0 Qt: 5.9.1 Kernel 4.10.0-38-generic Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 379719] KDEPlasmaPlatformTheme causes a crash if an MDI Window with a menubar is created with the global menu enabled
https://bugs.kde.org/show_bug.cgi?id=379719 Darren Edale changed: What|Removed |Added Attachment #108875|0 |1 is obsolete|| --- Comment #14 from Darren Edale --- Created attachment 108912 --> https://bugs.kde.org/attachment.cgi?id=108912&action=edit Sample backtrace with (almost) all debug symbols This is a backtrace from running the same code as for the old backtrace it obsoletes, with additional debug symbols available. I hope this helps. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387006] Failing tests in master
https://bugs.kde.org/show_bug.cgi?id=387006 --- Comment #1 from Christophe Giboudeaux --- no change with 5.10 beta 4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387019] Plasma shell crash - plasmoids
https://bugs.kde.org/show_bug.cgi?id=387019 --- Comment #2 from Alexander Mentyu --- Also tried in Netrunner Rolling without reproducibility: Plasma: 5.10.3 Frameworks: 5.36.0 Qt: 5.9.1 Kernel 4.10.0-38-generic Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kimagemapeditor] [Bug 386696] desktop-mime-but-no-exec-code lintian error when packaging.
https://bugs.kde.org/show_bug.cgi?id=386696 Luigi Toscano changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kim ||agemapeditor/6e914b7c1f5116 ||1fa6e4cb692146b7f9057c24ba --- Comment #1 from Luigi Toscano --- Git commit 6e914b7c1f51161fa6e4cb692146b7f9057c24ba by Luigi Toscano. Committed on 17/11/2017 at 10:46. Pushed by ltoscano into branch 'Applications/17.12'. .desktop: kimagemapeditor can take a list of files Remote URLs do not work (at least http), which could be a bug or not (see the old bug 144151 for ftp). For now fix the desktop file, because it specifies a MimeType entry and that means the need for a keyword (%f, %F, %u or %U) in the Exec line (lintian says desktop-mime-but-no-exec-code), or the MimeType entry to be dropped. M +1-1org.kde.kimagemapeditor.desktop https://commits.kde.org/kimagemapeditor/6e914b7c1f51161fa6e4cb692146b7f9057c24ba -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 387012] Failing tests in master
https://bugs.kde.org/show_bug.cgi?id=387012 --- Comment #2 from Christophe Giboudeaux --- FTR, I've just tested with 5.10 beta4, Only 2 tests fail now. 2 - kwindowsystem-kmanagerselectiontest (Failed) 5 - kwindowsystem-kkeyserver_x11_unittest (Failed) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7
https://bugs.kde.org/show_bug.cgi?id=386945 Julian Seward changed: What|Removed |Added Attachment #108906|0 |1 is obsolete|| --- Comment #6 from Julian Seward --- Created attachment 108913 --> https://bugs.kde.org/attachment.cgi?id=108913&action=edit Next attempt at a fix * fixes crashing (from my buggy implementation of cntlzd) * removes all (I think) invalid read warnings (I reimplemented ldbrx) Still invalidly reports conditional branches on uninit data. Something is not right somewhere. Really, how Valgrind handles integer conditional branches on POWER isn't good (too complex, hard to analyse) and should be reimplemented. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 --- Comment #62 from Alex Ioannou --- The issue went away for me! It's back now though after this happened: Downgrade: plasma-integration:amd64 (4:5.11.0-0neon+16.04+xenial+build58, 5.11.3-0neon+16.04+xenial+build64) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 382619] Additional routes in the IPv4 tab of the connection editors are not saved for wired connections.
https://bugs.kde.org/show_bug.cgi?id=382619 Jan-Matthias Braun changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #8 from Jan-Matthias Braun --- Hej! I have been able to wait long enough -- I cannot observe it anymore in 5.11.3. So, thanks a lot for whatever you did, even if it had nothing to do with this problem. :-) Cheers, Jan -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7
https://bugs.kde.org/show_bug.cgi?id=386945 --- Comment #7 from Markus Trippelsdorf --- Thanks. The gcc crash is gone, but I still get lots of invalid read warnings. However the amount of errors is much lower now: >From (valgrind trunk): ERROR SUMMARY: 89817 errors from 298 contexts To (your patch and --expensive-definedness-checks=yes): ERROR SUMMARY: 6495 errors from 85 contexts BTW valgrind trunk (without any patch) doesn't like --expensive-definedness-checks=yes: ==64698== Memcheck, a memory error detector ==64698== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==64698== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright info ==64698== Command: /home/trippels/gcc_test/usr/local/bin/../libexec/gcc/powerpc64le-unknown-linux-gnu/8.0.0/cc1plus -fpreprocessed bench.ii -quiet -dumpbase bench.cpp -auxbase ben ch -O2 -version -o bench.s ==64698== vex: priv/host_ppc_isel.c:1531 (iselWordExpr_R_wrk): Assertion `0' failed. vex storage: T total 666718712 bytes allocated vex storage: P total 192 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==64698==at 0x58084148: show_sched_status_wrk (m_libcassert.c:355) ==64698==by 0x5808430F: report_and_quit (m_libcassert.c:426) ==64698==by 0x5808458B: panic (m_libcassert.c:502) ==64698==by 0x5808458B: vgPlain_core_panic_at (m_libcassert.c:507) ==64698==by 0x580845DB: vgPlain_core_panic (m_libcassert.c:512) ==64698==by 0x580B1987: failure_exit (m_translate.c:751) ==64698==by 0x581CBA7B: vex_assert_fail (main_util.c:247) ==64698==by 0x5825AC83: iselWordExpr_R_wrk (host_ppc_isel.c:1531) ==64698==by 0x5825AC83: iselWordExpr_R (host_ppc_isel.c:1404) ==64698==by 0x5825E48F: iselWordExpr_RH_wrk (host_ppc_isel.c:2756) ==64698==by 0x5825E48F: iselWordExpr_RH (host_ppc_isel.c:2704) ==64698==by 0x58259B6B: iselWordExpr_R_wrk (host_ppc_isel.c:1477) ==64698==by 0x58259B6B: iselWordExpr_R (host_ppc_isel.c:1404) ==64698==by 0x58259E6B: iselWordExpr_R_wrk (host_ppc_isel.c:1505) ==64698==by 0x58259E6B: iselWordExpr_R (host_ppc_isel.c:1404) ==64698==by 0x5825E48F: iselWordExpr_RH_wrk (host_ppc_isel.c:2756) ==64698==by 0x5825E48F: iselWordExpr_RH (host_ppc_isel.c:2704) ==64698==by 0x58259AFB: iselWordExpr_R_wrk (host_ppc_isel.c:1481) ==64698==by 0x58259AFB: iselWordExpr_R (host_ppc_isel.c:1404) ==64698==by 0x58258363: iselCondCode_wrk (host_ppc_isel.c:2965) ==64698==by 0x5826AAF7: iselCondCode (host_ppc_isel.c:2915) ==64698==by 0x5826AAF7: iselStmt (host_ppc_isel.c:6385) ==64698==by 0x5826AAF7: iselSB_PPC (host_ppc_isel.c:6983) ==64698==by 0x581C859F: libvex_BackEnd (main_main.c:1049) ==64698==by 0x581C859F: LibVEX_Translate (main_main.c:1186) ==64698==by 0x580B5323: vgPlain_translate (m_translate.c:1805) ==64698==by 0x58110E9F: handle_chain_me (scheduler.c:1084) ==64698==by 0x58113FFF: vgPlain_scheduler (scheduler.c:1428) ==64698==by 0x5812F697: thread_wrapper (syswrap-linux.c:103) ==64698==by 0x5812F697: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 64698) ==64698==at 0x10B22120: equal (hash-traits.h:221) ==64698==by 0x10B22120: equal_keys (hash-map-traits.h:57) ==64698==by 0x10B22120: equal (hash-map.h:44) ==64698==by 0x10B22120: hash_table, opt_pass*> >::hash_entry, xcallocator >::find_with_hash(char const* const&, unsigned int) (hash-table.h:846) ==64698==by 0x10B18C33: get (hash-map.h:161) ==64698==by 0x10B18C33: gcc::pass_manager::register_pass_name(opt_pass*, char const*) (passes.c:864) ==64698==by 0x10B19433: gcc::pass_manager::register_one_dump_file(opt_pass*) (passes.c:834) ==64698==by 0x10B19567: gcc::pass_manager::register_dump_files(opt_pass*) (passes.c:846) ==64698==by 0x10B195A7: gcc::pass_manager::register_dump_files(opt_pass*) (passes.c:849) ==64698==by 0x10B195A7: gcc::pass_manager::register_dump_files(opt_pass*) (passes.c:849) ==64698==by 0x10B1F7EF: gcc::pass_manager::pass_manager(gcc::context*) (passes.c:1615) ==64698==by 0x101C220B: general_init (toplev.c:1168) ==64698==by 0x101C220B: toplev::main(int, char**) (toplev.c:2148) ==64698==by 0x101C51A7: main (main.c:39) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 386042] Only one attempt to enter correct webdav password. It will not be asked a second time
https://bugs.kde.org/show_bug.cgi?id=386042 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Elvis Angelaccio --- Confirmed. There is a workaround though, run 'kquitapp5 kiod5'. This will kill the kpasswdserver module which is responsible for the authentication. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386997] Systemsettings crashed by searching
https://bugs.kde.org/show_bug.cgi?id=386997 --- Comment #1 from isa-...@gmx.de --- Probably a related to or a duplicate of Bug 386683 - Crash when searching in system settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386683] Crash when searching in system settings
https://bugs.kde.org/show_bug.cgi?id=386683 isa-...@gmx.de changed: What|Removed |Added CC||isa-...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387000] GPS Longitude Decimalisation Appears Incorrect In Map
https://bugs.kde.org/show_bug.cgi?id=387000 --- Comment #2 from Maik Qualmann --- It comes with the seconds part of the longitude to an incorrect conversion into a rational number by Exiv2. The rational values are completely wrong. Since we need the number as a floating-point number and the toFloat() function returns correct value, this problem can be circumvented in Exiv2. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 387029] New: Test failure in master
https://bugs.kde.org/show_bug.cgi?id=387029
Bug ID: 387029
Summary: Test failure in master
Product: frameworks-kio
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: christo...@krop.fr
CC: kdelibs-b...@kde.org
Target Milestone: ---
Tested with master & Qt 5.10 beta 4 :
12/54 Testing: kiocore-kprotocolinfotest
QDEBUG : KProtocolInfoTest::testCapabilities() 13:27:15 -
kprotocolinfotest(31544) - kf5.kio.core: KProtocolInfoFactory::findProtocol:
Refilling KProtocolInfoFactory cache in the hope to find "imap"
QDEBUG : KProtocolInfoTest::testCapabilities() 13:27:15 -
kprotocolinfotest(31544) - KProtocolInfoTest::testCapabilities: kio_imap
capabilities: ()
PASS : KProtocolInfoTest::testCapabilities()
FAIL! : KProtocolInfoTest::testProtocolForArchiveMimetype() Compared values
are not the same
Actual (zip) : "krarc"
Expected (QStringLiteral("zip")): "zip"
Loc: [/kde/src/5/frameworks/kio/autotests/kprotocolinfotest.cpp(142)]
---
29/54 Testing: kiowidgets-kdirlistertest
QDEBUG : KDirListerTest::testRenameItem() 13:27:39 - kdirlistertest(31917) -
kf5.kio.core.dirlister: KCoreDirListerCache::slotFileRenamed:
QUrl("file:///tmp/kdirlistertest-yyrrYi/toplevelfile_2") ->
QUrl("file:///tmp/kdirlistertest-yyrrYi/toplevelfile_2.renamed.html")
QDEBUG : KDirListerTest::testRenameItem() 13:27:39 - kdirlistertest(31917) -
kf5.kio.core.dirlister: KCoreDirListerCache::emitRefreshItem: old:
"toplevelfile_2" QUrl("file:///tmp/kdirlistertest-yyrrYi/toplevelfile_2") new:
"toplevelfile_2.renamed.html"
QUrl("file:///tmp/kdirlistertest-yyrrYi/toplevelfile_2.renamed.html")
FAIL! : KDirListerTest::testRenameItem() Compared values are not the same
Actual (entry.second.mimetype()): "application/x-extension-html"
Expected (QString("text/html")) : "text/html"
Loc: [/kde/src/5/frameworks/kio/autotests/kdirlistertest.cpp(507)]
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 384549] Only first click on System monitor open Ksysguard
https://bugs.kde.org/show_bug.cgi?id=384549 --- Comment #6 from jeremy9...@gmail.com --- > Do you have a low maintenance distro with up to date packages to recommend, > something like Fedora ? I'm back on Kubuntu (17.10). A really good distro ! I think I will stay for a while with the next Kubuntu LTS (18.04). It would be awesome if the Kubuntu LTS could always benefit a really stable KDE/Plasma release ! By the way I confirm the bug is fixed on 5.11 ! Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385679] Discover crashes in QObjectPrivate::addConnection() while searching
https://bugs.kde.org/show_bug.cgi?id=385679 --- Comment #5 from Aleix Pol --- Note to self. Here's the backtrace with symbols from one of the duplicates: Thread 1 (Thread 0x7fb17e0c55c0 (LWP 8483)): [KCrash Handler] #6 0x00010001 in ?? () #7 0x7fb17a10ace2 in QObjectPrivate::connectImpl (sender=sender@entry=0x55f64e5f9f20, signal_index=9, receiver=receiver@entry=0x55f64e6c7ab0, slot=slot@entry=0x7ffc1cd93f20, slotObj=slotObj@entry=0x7fb16400ab60, type=, types=, senderMetaObject=) at kernel/qobject.cpp:4847 #8 0x7fb17a10aeb2 in QObject::connectImpl (sender=sender@entry=0x55f64e5f9f20, signal=signal@entry=0x7ffc1cd93f10, receiver=0x55f64e6c7ab0, slot=slot@entry=0x7ffc1cd93f20, slotObj=0x7fb16400ab60, type=Qt::AutoConnection, types=0x0, senderMetaObject=0x7fb11d6f6c20 ) at kernel/qobject.cpp:4784 #9 0x7fb11d4e6336 in QObject::connect const&), void (ResultsStream::*)(QVector const&)> (type=Qt::AutoConnection, slot=(void (ResultsStream::*)(ResultsStream * const, const QVector &)) 0x7fb17d038670 const&)>, receiver=, signal=(void (KNSBackend::*)(KNSBackend * const, const QVector &)) 0x7fb11d4f1120 const&)>, sender=0x55f64e5f9f20) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:259 #10 KNSBackendoperator() (__closure=0x55f64eaf6ca0) at ./libdiscover/backends/KNSBackend/KNSBackend.cpp:357 #11 QtPrivate::FunctorCall, QtPrivate::List<>, void, KNSBackend::searchStream(const QString&):: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:130 #12 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:240 #13 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55f64eaf6c90, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:168 #14 0x7fb17a107452 in QObject::event (this=0x55f64e6c7ab0, e=) at kernel/qobject.cpp:1246 #15 0x7fb17b6d646c in QApplicationPrivate::notify_helper (this=this@entry=0x55f64bd9d290, receiver=receiver@entry=0x55f64e6c7ab0, e=e@entry=0x55f64e603320) at kernel/qapplication.cpp:3717 #16 0x7fb17b6ddd34 in QApplication::notify (this=0x7ffc1cd94550, receiver=0x55f64e6c7ab0, e=0x55f64e603320) at kernel/qapplication.cpp:3476 #17 0x7fb17a0d7de8 in QCoreApplication::notifyInternal2 (receiver=0x55f64e6c7ab0, event=event@entry=0x55f64e603320) at kernel/qcoreapplication.cpp:1018 #18 0x7fb17a0da55d in QCoreApplication::sendEvent (event=0x55f64e603320, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #19 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55f64bda2df0) at kernel/qcoreapplication.cpp:1678 #20 0x7fb17a0daae8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1532 #21 0x7fb17a130e53 in postEventSourceDispatch (s=0x55f64bdff0f0) at kernel/qeventdispatcher_glib.cpp:276 #22 0x7fb1741a5fb7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fb1741a61f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fb1741a627c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fb17a13047f in QEventDispatcherGlib::processEvents (this=0x55f64be05dc0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x7fb17a0d5e3a in QEventLoop::exec (this=this@entry=0x7ffc1cd94490, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #27 0x7fb17a0deda4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1291 #28 0x55f64aab4fa8 in main (argc=, argv=) at ./discover/main.cpp:151 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 387030] New: Overview page mode orders pages from right to left.
https://bugs.kde.org/show_bug.cgi?id=387030 Bug ID: 387030 Summary: Overview page mode orders pages from right to left. Product: okular Version: 1.2.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: am...@fisica.ist.utl.pt Target Milestone: --- In the Fedora 27 version of okular the multiple page view mode of pdfs shows pages in reverse order (lowest page number on the right). -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 384894] User avatar is changed even when the password dialog is canceled
https://bugs.kde.org/show_bug.cgi?id=384894 Dr. Chapatin changed: What|Removed |Added Summary|Asks for password when |User avatar is changed even |changing picture|when the password dialog is ||canceled --- Comment #4 from Dr. Chapatin --- I can confirm on neon dev unstable. When I apply the new avatar, user-manager asks for my password. If I cancel the password dialog, user-manager shows the password dialog again two times and apply the new avatar even if I cancel all the three password dialogs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 387031] New: Test failures in master
https://bugs.kde.org/show_bug.cgi?id=387031 Bug ID: 387031 Summary: Test failures in master Product: frameworks-ktexteditor Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: christo...@krop.fr Target Milestone: --- Tested with master & Qt 5.10 beta 4. The following tests fail : 62 - katesyntaxtest (Failed) 63 - vimode_modes (Failed) 64 - vimode_view (Failed) Output is attached for these 3 tests -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 387030] Overview page mode orders pages from right to left.
https://bugs.kde.org/show_bug.cgi?id=387030 Albert Astals Cid changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Can you attach a screenshot? Are you sure you didn't enable RTL mode on the settings? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 387031] Test failures in master
https://bugs.kde.org/show_bug.cgi?id=387031 --- Comment #1 from Christophe Giboudeaux --- Created attachment 108914 --> https://bugs.kde.org/attachment.cgi?id=108914&action=edit trimmed autotests output -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377045] On Windows, KDevelop fails to recognize the c++ standard library
https://bugs.kde.org/show_bug.cgi?id=377045 geetam chawla changed: What|Removed |Added CC||geetam.cha...@gmail.com --- Comment #5 from geetam chawla --- @Kevin Funk I forgot to include BUG keyword in the commit message, can you close this, now that it is fixed? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377045] On Windows, KDevelop fails to recognize the c++ standard library
https://bugs.kde.org/show_bug.cgi?id=377045 Kevin Funk changed: What|Removed |Added Version Fixed In||5.2.1 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Kevin Funk --- Fixed by https://phabricator.kde.org/D8805 -- correct? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377045] On Windows, KDevelop fails to recognize the c++ standard library
https://bugs.kde.org/show_bug.cgi?id=377045 --- Comment #7 from geetam chawla --- (In reply to Kevin Funk from comment #6) > Fixed by https://phabricator.kde.org/D8805 -- correct? and this: https://phabricator.kde.org/D8831 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387032] New: Desktop freeze and reload
https://bugs.kde.org/show_bug.cgi?id=387032 Bug ID: 387032 Summary: Desktop freeze and reload Product: plasmashell Version: 5.10.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: elwe...@vmcmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.2 Frameworks Version: 5.38.0 Operating System: Linux 4.13.12-200.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: - What I was doing when the application crashed: Nothing special. I was perhaps scrolling through a web page or Akregator - Unusual behavior I noticed: Desktop flickers, freezes and reloads. - Custom settings of the application: I have 3 monitors 2 have slideshows of many pictures. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa9c55ba4c0 (LWP 2713))] Thread 32 (Thread 0x7fa8bdffb700 (LWP 9620)): #0 0x7fa9d043790b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa9d1d143db in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7fa8e72ec0d5 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #3 0x7fa8e72f0048 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #4 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #5 0x7fa8e72f00a2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #6 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #7 0x7fa8e72f00a2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #8 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #9 0x7fa8e72f00a2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #10 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #11 0x7fa8e72f00a2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #12 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #13 0x7fa8e72f00a2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #14 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #15 0x7fa8e72f00a2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #16 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #17 0x7fa8e72f00a2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #18 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #19 0x7fa8e72f00a2 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #20 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #21 0x7fa8e72edf8b in ThreadWeaver::Thread::run() () from /lib64/libKF5ThreadWeaver.so.5 #22 0x7fa9d1d13c72 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #23 0x7fa9d043136d in start_thread () from /lib64/libpthread.so.0 #24 0x7fa9d10f4e1f in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7fa8be7fc700 (LWP 9619)): #0 0x7fa9d043790b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa9d1d143db in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7fa8e72ec0d5 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5 #3 0x7fa8e72f0048 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () from /lib64/libKF5ThreadWeaver.so.5 #4 0x7fa8e72eb29d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread
[krita] [Bug 387033] New: Krita crash when applying certain g'mic layer filters
https://bugs.kde.org/show_bug.cgi?id=387033 Bug ID: 387033 Summary: Krita crash when applying certain g'mic layer filters Product: krita Version: 3.3.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: astrow...@gmail.com Target Milestone: --- Created attachment 108915 --> https://bugs.kde.org/attachment.cgi?id=108915&action=edit backtrace for error Hi, I'm getting consistent crashes when applying g'mic filters to layers as 'blend [standard]'. It happens with most of the filter modes I've tried (grain extract, value, darken etc) Input/output options tried are 'active and below' or 'all'. other options are set at default. I'm using Windows 10 pro x64 Krita 3.3.2 (also crashed on 3.3.1) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7
https://bugs.kde.org/show_bug.cgi?id=386945 --- Comment #8 from Julian Seward --- (In reply to Markus Trippelsdorf from comment #7) > Thanks. > The gcc crash is gone, but I still get lots of invalid read warnings. > > However the amount of errors is much lower now: > > From (valgrind trunk): > ERROR SUMMARY: 89817 errors from 298 contexts > To (your patch and --expensive-definedness-checks=yes): > ERROR SUMMARY: 6495 errors from 85 contexts I re-checked my fixes. I cannot figure out why V still reports undefined value errors now. Can you point me at the bit of the gcc source that generates this code? Maybe that has some further explanation of how this should work. > I still get lots of invalid read warnings. I get those too (see below). These are misaligned (non-8-byte-aligned) ldbrx instructions (I checked) as part of this inlined strcmp. Is the strcmp-inlining expected to produce misaligned loads, or not? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387033] Krita crash when applying certain g'mic layer filters
https://bugs.kde.org/show_bug.cgi?id=387033 Alvin Wong changed: What|Removed |Added CC||alvinhoc...@gmail.com --- Comment #1 from Alvin Wong --- What pixel format is your image in? What layers do you have in your file? (A sceenshot or even the file itself would help) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387034] New: Kickoff shows wrong user avatar after I change the avatar of the actual account and select another user account from the list
https://bugs.kde.org/show_bug.cgi?id=387034 Bug ID: 387034 Summary: Kickoff shows wrong user avatar after I change the avatar of the actual account and select another user account from the list Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 neon dev unstable here... 1. open system settings, "account details", "users manager" 2. create two user accounts 3. change your avatar to a picture different of the second user account avatar 4. select the second account in accounts list 5. open kickoff apps menu Result: kickoff shows the avatar of the second account instead your avatar -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 387035] New: Baloo Crash
https://bugs.kde.org/show_bug.cgi?id=387035 Bug ID: 387035 Summary: Baloo Crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: householdwo...@gmail.com Target Milestone: --- Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.10.0-38-generic x86_64 Distribution: Ubuntu 16.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Organizing files by clicking, holding and sliding them from one directory to another using dolphin in split screen mode. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f13dd227900 (LWP 1754))] Thread 2 (Thread 0x7f12919ba700 (LWP 2247)): #0 0x7f13d84d1a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f13d848c929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13d848d2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13d848d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f13dbf3f7eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f13dbee6b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00420cd8 in Baloo::FileContentIndexer::run() () #7 0x7f13dbd052d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f13dbd087be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f13da9526ba in start_thread (arg=0x7f12919ba700) at pthread_create.c:333 #10 0x7f13db3023dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f13dd227900 (LWP 1754)): [KCrash Handler] #6 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:35 #7 0x7f13dc3dc275 in Baloo::IdTreeDB::get(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #8 0x7f13dc3d901d in Baloo::DocumentUrlDB::getChildren(unsigned long long) const () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #9 0x7f13dc3f2697 in Baloo::WriteTransaction::removeRecursively(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #10 0x7f13dc3f26c7 in Baloo::WriteTransaction::removeRecursively(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #11 0x00429685 in Baloo::MetadataMover::removeMetadata(Baloo::Transaction*, QString const&) () #12 0x004296cd in Baloo::MetadataMover::removeFileMetadata(QString const&) () #13 0x7f13dbf17baf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00432f05 in Baloo::PendingFileQueue::removeFileIndex(QString const&) () #15 0x00427856 in Baloo::PendingFileQueue::processCache() () #16 0x7f13dbf17baf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f13dbf245c8 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f13dbf18bb3 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f13dbee936c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f13dbf3e5ed in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f13dbf3eb29 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f13d848d197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f13d848d3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f13d848d49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f13dbf3f7cf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f13dbee6b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f13dbeeebec in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x0041698c in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7
https://bugs.kde.org/show_bug.cgi?id=386945 --- Comment #9 from Julian Seward --- Misaligned loads as referred to in comment 8: ==63134== Invalid read of size 8 ==63134==at 0xB163FE4: process_symtab (lto-plugin.c:905) ==63134==by 0xB16D897: simple_object_elf_find_sections (simple-object-elf.c:570) ==63134==by 0xB16BAF7: simple_object_find_sections (simple-object.c:194) ==63134==by 0xB1645A7: claim_file_handler (lto-plugin.c:1009) ==63134==by 0x1003A1BF: ??? (in /usr/bin/ld) ==63134==by 0x10035F9F: ??? (in /usr/bin/ld) ==63134== Address 0x4797413 is 243 bytes inside a block of size 249 alloc'd ==63134==at 0x4083F40: malloc (vg_replace_malloc.c:299) ==63134==by 0x41EC7FB: xmalloc (in /usr/lib64/libbfd-2.25.1-32.base.el7_4.1.so) ==63134==by 0xB16D7CF: simple_object_elf_find_sections (simple-object-elf.c:535) ==63134==by 0xB16BAF7: simple_object_find_sections (simple-object.c:194) ==63134==by 0xB1645A7: claim_file_handler (lto-plugin.c:1009) ==63134==by 0x1003A1BF: ??? (in /usr/bin/ld) ==63134==by 0x10035F9F: ??? (in /usr/bin/ld) ==63134== ==63134== Invalid read of size 8 ==63134==at 0xB1639F4: process_offload_section (lto-plugin.c:952) ==63134==by 0xB16D897: simple_object_elf_find_sections (simple-object-elf.c:570) ==63134==by 0xB16BAF7: simple_object_find_sections (simple-object.c:194) ==63134==by 0xB164757: claim_file_handler (lto-plugin.c:1022) ==63134==by 0x1003A1BF: ??? (in /usr/bin/ld) ==63134==by 0x10035F9F: ??? (in /usr/bin/ld) ==63134== Address 0x4797c53 is 243 bytes inside a block of size 249 alloc'd ==63134==at 0x4083F40: malloc (vg_replace_malloc.c:299) ==63134==by 0x41EC7FB: xmalloc (in /usr/lib64/libbfd-2.25.1-32.base.el7_4.1.so) ==63134==by 0xB16D7CF: simple_object_elf_find_sections (simple-object-elf.c:535) ==63134==by 0xB16BAF7: simple_object_find_sections (simple-object.c:194) ==63134==by 0xB164757: claim_file_handler (lto-plugin.c:1022) ==63134==by 0x1003A1BF: ??? (in /usr/bin/ld) ==63134==by 0x10035F9F: ??? (in /usr/bin/ld) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387034] Kickoff shows wrong user avatar after I change the avatar of the actual account and select another user account from the list
https://bugs.kde.org/show_bug.cgi?id=387034 --- Comment #1 from Dr. Chapatin --- fixing step 2: create a new user account, so you have two accounts on your system now -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387036] New: scrollview-within-a-scrollview paradigm is user-hostile
https://bugs.kde.org/show_bug.cgi?id=387036 Bug ID: 387036 Summary: scrollview-within-a-scrollview paradigm is user-hostile Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: pointedst...@zoho.com Target Milestone: --- Created attachment 108916 --> https://bugs.kde.org/attachment.cgi?id=108916&action=edit Screenshot When using Discover to perform software updates, each package can be clicked to display the package's changelog (if available). However the changelog is embedded within a scrollview, which leads to a situation where there are scrollviews within a larger scrollview. This causes two usability issues: - The scrollview is short and wide, making it hard to actually read the content - Your cursor can easily find itself above a package changelog scrollview and get its focus stolen when you are reying to scroll the list of packages I recommend taking the package changelogs out of their scrollviews and just display the full content in a non-scrolling view as tall as necessary if the user clicks on it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 346741] bring back "auto-lock screen on login" option from KDM/Plasma 4
https://bugs.kde.org/show_bug.cgi?id=346741 --- Comment #9 from Claus Appel --- (In reply to Holger from comment #7) > (In reply to Claus Appel from comment #6) > > Could you please elaborate on why this is not secure? It is not clear to me. > > Sure. An unencrypted HDD can either be physically extracted and read / > modified in another PC, that is running it's own operating system. To that > other computer everything on your HDD is just data, no restrictions apply. All right, that makes sense. But does this have anything to do with "autologin-and-lock-screen"? Is it MORE secure to demand password BEFORE logging in the user than it is to demand password AFTER logging in the user? If not, then this - while good advice - does not have anything to do with this bug report, IMO. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387036] Scrollview-within-a-scrollview paradigm is sub-optimal
https://bugs.kde.org/show_bug.cgi?id=387036 Nate Graham changed: What|Removed |Added Summary|scrollview-within-a-scrollv |Scrollview-within-a-scrollv |iew paradigm is |iew paradigm is sub-optimal |user-hostile| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7
https://bugs.kde.org/show_bug.cgi?id=386945 --- Comment #10 from Markus Trippelsdorf --- For some reason I cannot CC Aaron Sawdey, who wrote the PPC strcmp patch: https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=244598 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387026] idea: "don't change focus" hotkey
https://bugs.kde.org/show_bug.cgi?id=387026 Martin Flöser changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- Please have a look at window rules for focus stealing prevention. There is not much more we can do. We don't know that you clicked a link. All we see is that there is a valid request from another application to gain focus. With focus stealing prevention you can disallow such requests. But a dynamic feature is not possible. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386683] Crash when searching in system settings
https://bugs.kde.org/show_bug.cgi?id=386683 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Is this reproducible? If we can get it in valgrind that'd be great -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387033] Krita crash when applying certain g'mic layer filters
https://bugs.kde.org/show_bug.cgi?id=387033 --- Comment #2 from Asa --- Created attachment 108917 --> https://bugs.kde.org/attachment.cgi?id=108917&action=edit krita before opening q'mic and applying filter -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387036] Scrollview-within-a-scrollview paradigm is sub-optimal
https://bugs.kde.org/show_bug.cgi?id=387036 --- Comment #1 from Nate Graham --- Proof-of-concept patch available at https://phabricator.kde.org/D8869 The patch may not be quite the right way to implement this change, but hopefully it illustrates the general idea. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387033] Krita crash when applying certain g'mic layer filters
https://bugs.kde.org/show_bug.cgi?id=387033 --- Comment #3 from Asa --- Hi, I've tried various images in different pixel formats RGB 8/16/32 bit, CMYK 8/16/32. My workflow for the layers is to create a new image/open an existing image, then duplicate the layer once or twice, then start q'mic to apply the filter. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387033] Krita crash when applying certain g'mic layer filters
https://bugs.kde.org/show_bug.cgi?id=387033 --- Comment #4 from Asa --- This is the windows error event generated by the crash, not sure if it's useful - Faulting application name: krita.exe, version: 0.0.0.0, time stamp: 0x01940641 Faulting module name: kritaqmic.dll, version: 0.0.0.0, time stamp: 0x Exception code: 0xc005 Fault offset: 0x00013bd8 Faulting process id: 0x2aa0 Faulting application start time: 0x01d35fb548e9e345 Faulting application path: C:\Program Files\Krita (x64)\bin\krita.exe Faulting module path: C:\Program Files\Krita (x64)\lib\kritaplugins\kritaqmic.dll Report Id: 1710503b-e530-497f-8154-bce5725e98f8 Faulting package full name: Faulting package-relative application ID: -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 382262] Media frame plasmoid causes plasmashell memory leak
https://bugs.kde.org/show_bug.cgi?id=382262 makism changed: What|Removed |Added CC||mak...@gmail.com --- Comment #4 from makism --- I finally managed to track the memory leak in plasmashell into this widget. still there in both Fedora 26 and 27 beta. some details: KDE Plasma 5.10.5 KDE Framewoks 5.39.0 Qt 5.9.2 Kernel: 4.13.12-300 GLX: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) OpenGL version: 3.0 Mesa 17.2.4 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387037] New: Discover crashes on finishing update install
https://bugs.kde.org/show_bug.cgi?id=387037 Bug ID: 387037 Summary: Discover crashes on finishing update install Product: Discover Version: 5.8.8 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: j...@heywoodkunz.com Target Milestone: --- Application: plasma-discover (5.8.8) Qt Version: 5.6.1 Frameworks Version: 5.36.0 Operating System: Linux 4.4.0-98-generic x86_64 Distribution: Ubuntu 16.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Installing the recommended update using Discover. This happens everytime I update, regardless whether or not I have recently rebooted. In this particular case, my box has been up for 3 days without restart. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3ecd1228c0 (LWP 25661))] Thread 11 (Thread 0x7f3e88a64700 (LWP 25677)): #0 0x7f3ec99a670d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3ec6b7138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3ec6b7149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3eca5d737b in QEventDispatcherGlib::processEvents (this=0x7f3e7c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f3eca57fffa in QEventLoop::exec (this=this@entry=0x7f3e88a63d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f3eca3a89e4 in QThread::exec (this=) at thread/qthread.cpp:500 #6 0x7f3eca3ad808 in QThreadPrivate::start (arg=0x2a1d350) at thread/qthread_unix.cpp:341 #7 0x7f3ec72de6ba in start_thread (arg=0x7f3e88a64700) at pthread_create.c:333 #8 0x7f3ec99b23dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f3e8ac0d700 (LWP 25675)): #0 0x7f3eca3a5d69 in std::__atomic_base::compare_exchange_strong (__m2=, __m1=std::memory_order_release, __p2=0x0, __p1=@0x7f3e8ac0caa8: 0x1, this=0x26ade78) at /usr/include/c++/5/bits/atomic_base.h:752 #1 std::atomic::compare_exchange_strong (__m=std::memory_order_release, __p2=0x0, __p1=@0x7f3e8ac0caa8: 0x1, this=0x26ade78) at /usr/include/c++/5/atomic:475 #2 QAtomicOps::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=0x1, _q_value=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_cxx11.h:167 #3 QBasicAtomicPointer::testAndSetRelease (currentValue=, newValue=0x0, expectedValue=, this=0x26ade78) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:278 #4 QBasicMutex::fastTryUnlock (current=, this=0x26ade78) at thread/qmutex.h:85 #5 QMutex::unlock (this=this@entry=0x26ade78) at thread/qmutex.cpp:271 #6 0x7f3eca5d6a11 in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:138 #7 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:132 #8 QThreadData::canWaitLocked (this=0x26ade50) at ../../include/QtCore/5.6.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:246 #9 postEventSourcePrepare (s=0x7f3e800012d0, timeout=0x7f3e8ac0cb34) at kernel/qeventdispatcher_glib.cpp:253 #10 0x7f3ec6b7091d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f3ec6b712bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f3ec6b7149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f3eca5d737b in QEventDispatcherGlib::processEvents (this=0x7f3e88c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #14 0x7f3eca57fffa in QEventLoop::exec (this=this@entry=0x7f3e8ac0cd00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #15 0x7f3eca3a89e4 in QThread::exec (this=) at thread/qthread.cpp:500 #16 0x7f3eca3ad808 in QThreadPrivate::start (arg=0x2680560) at thread/qthread_unix.cpp:341 #17 0x7f3ec72de6ba in start_thread (arg=0x7f3e8ac0d700) at pthread_create.c:333 #18 0x7f3ec99b23dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f3e9165a700 (LWP 25673)): #0 0x7f3ec99a670d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3ec6b7138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3ec6b71712 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3e92ddf9d6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f3ec6b97bb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3ec72de6ba in start_thread (arg=0x7f3e9165a700) at pthread_create.c:333 #6 0x7f3ec99b23dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread
[kwin] [Bug 387026] idea: "don't change focus" hotkey
https://bugs.kde.org/show_bug.cgi?id=387026 --- Comment #2 from RJVB --- I already looked at those, they're set to what's most commonly useful. Similarly I have focus-follows-mouse set to the best compromise setting. I've also already asked around for other things that could improve the experience in the scenario I described ([1]) Maybe my description was too long to be readable. You can implement various levels of focus stealing prevention in KWin, right? Why then couldn't you implement a version where keeping a certain key pressed switches prevention to the strictest form? Technically speaking of course? I realise of course that you cannot know the context of a focus or raise request, but the user does and can do something to moderate the effect of the request he just triggered. 1) a WM command-cum-hotkey "give focus to the window currently under the mouse" would also do the trick for me. Hitting that key to restore focus is not very different from keeping a key pressed to prevent focus from changing. I could of course click the mouse button but that would always raise the window, which is not always what I want. -- You are receiving this mail because: You are watching all bug changes.
[kwebkitpart] [Bug 387038] New: middle click to open link in a background tab
https://bugs.kde.org/show_bug.cgi?id=387038 Bug ID: 387038 Summary: middle click to open link in a background tab Product: kwebkitpart Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: webkit-de...@kde.org Reporter: jsar...@gmail.com Target Milestone: --- I recently moved from QtWebEngine to QtWebKit and so far so good! IMO, much better, lighter and with enhanced functionality (on a side note I would encourage to release a new version so final users can enjoy it!). One thing that I'm missing from QtWebEngine is to open links in the background with middle click, so the flow is not broken. I don't recall configuring anything in QtWebEngine, so I guess this is the default behavior. I couldn't find the way to set this as default behavior in QtWebKit. Is it possible? Any clue? Thank you for the good work! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387033] Krita crash when applying certain g'mic layer filters
https://bugs.kde.org/show_bug.cgi?id=387033 Alvin Wong changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Alvin Wong --- OK, Looks like I can reproduce the crash, seem to happen when Input Mode uses more than one layer. Perhaps due to output having less layers than input. Also crashes on 4.0 pre-alpha 2 (pretty much expected): krita.exe caused an Access Violation at location 7FFC2E9E3DE8 in module kritaqmic.dll Reading from location . AddrPC Params 7FFC2E9E3DE8 3E9A05B0 26BEA090 26BEA0BC kritaqmic.dll!visitNodeWithPaintDevice [C:/dev/4/64/i/include/QtCore/qdebug.h @ 146] 7FFC33A6A8D3 3EB1ED40 26BEA090 26BEA0BC libkritaimage.dll! ?? [C:/dev/4/64/krita/libs/image/commands_new/kis_processing_command.cpp @ 35] 7FFC33AE1EFF 26BEA090 0003 libkritaimage.dll!doStrokeCallback [C:/dev/4/64/krita/libs/image/kis_stroke_strategy_undo_command_based.cpp @ 73] 7FFC33C9C442 2679F8D0 7FFC350B93E0 2679F8D0 libkritaimage.dll!run [C:/dev/4/64/krita/libs/image/kis_base_node.h @ 320] 7FFC34D7CF61 3EB1ED30 26817E00 Qt5Core.dll!QThreadPoolPrivate::clear 7FFC34D80AA6 Qt5Core.dll!QThreadStorageData::finish 7FFC74691FE4 KERNEL32.DLL!BaseThreadInitThunk 7FFC76F5EF91 ntdll.dll!RtlUserThreadStart Crash location is probably https://github.com/KDE/krita/blob/d6bfc136a743b2c30e72d8f76edccb3e2b027bc2/plugins/extensions/qmic/kis_import_qmic_processing_visitor.cpp#L73 The obvious mistake is not doing sanity bound checking on `m_images`, but more probably needs to be done to handle the action properly (perhaps involving layer deletion). I don't know enough to comment. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 387039] file dialog hang whenever dragging a file/directory
https://bugs.kde.org/show_bug.cgi?id=387039 Marc Cousin changed: What|Removed |Added CC||cousinm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 387039] New: file dialog hang whenever dragging a file/directory
https://bugs.kde.org/show_bug.cgi?id=387039 Bug ID: 387039 Summary: file dialog hang whenever dragging a file/directory Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: cousinm...@gmail.com Target Milestone: --- How to reproduce: With a kde app (kate, okular for instance), go to the file dialog and try to drag a file or directory, the app will hang with a wrong direction sign until you press escape. I used to do this to add shortcuts to the left part of the file dialog. I don't know when it started, but I have this on both my computers, very different hardware, one of them installed a long time ago. kde is 17.08.3-1 right now. Please tell me what information I can provide (I didn't see anything in the stdout of those apps). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383711] All Albums Disappear
https://bugs.kde.org/show_bug.cgi?id=383711 vxd changed: What|Removed |Added CC||vu.do1...@gmail.com --- Comment #5 from vxd --- I too have experience this issue many times. My albums are on an external HDD and are marked as an external HDD. If the HDD is not connected after using Digikam the albums from the external HDD will be removed when I close and open Digikam. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387040] New: Git commit c829ec79 broke investment price chart
https://bugs.kde.org/show_bug.cgi?id=387040 Bug ID: 387040 Summary: Git commit c829ec79 broke investment price chart Product: kmymoney Version: 4.8.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: djhoul...@gmail.com Target Milestone: --- Created attachment 108918 --> https://bugs.kde.org/attachment.cgi?id=108918&action=edit Examply KMyMoney file The latest commit to the 4.8 branch has broken one of my investment reports. I have shares which are priced in USD and my base currency in KMyMoney is GBP. I produce two investment price charts for the shares showing the last year's price history. One shows the price history in USD, the other in GBP. This is achieved by ticking or unticking "Convert values to base currency" in the report configuration. After commit c829ec79 the GBP price history is not converting the price. The chart shows price history in USD. Attached is a KMyMoney file which can be used to show the problem, a screen print of the USD chart and prints of the GBP chart before and after the commit. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387040] Git commit c829ec79 broke investment price chart
https://bugs.kde.org/show_bug.cgi?id=387040 --- Comment #1 from David Houlden --- Created attachment 108919 --> https://bugs.kde.org/attachment.cgi?id=108919&action=edit USD chart -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387040] Git commit c829ec79 broke investment price chart
https://bugs.kde.org/show_bug.cgi?id=387040 --- Comment #2 from David Houlden --- Created attachment 108920 --> https://bugs.kde.org/attachment.cgi?id=108920&action=edit GBP chart before commit -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387040] Git commit c829ec79 broke investment price chart
https://bugs.kde.org/show_bug.cgi?id=387040 --- Comment #3 from David Houlden --- Created attachment 108921 --> https://bugs.kde.org/attachment.cgi?id=108921&action=edit GBP chart after commit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387033] Krita crash when applying certain g'mic layer filters
https://bugs.kde.org/show_bug.cgi?id=387033 Alvin Wong changed: What|Removed |Added CC||nicholaslapoin...@gmail.com --- Comment #6 from Alvin Wong --- Hi Nicholas, since I saw that you've fixed a few things regarding gmic-qt in the past, perhaps you will know better than me? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387036] Scrollview-within-a-scrollview paradigm is sub-optimal
https://bugs.kde.org/show_bug.cgi?id=387036
Nate Graham changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Latest Commit||https://commits.kde.org/dis
||cover/732a0ffb2ab0cac9778ea
||490098ddad02ece824d
--- Comment #2 from Nate Graham ---
Git commit 732a0ffb2ab0cac9778ea490098ddad02ece824d by Nathaniel Graham.
Committed on 17/11/2017 at 16:14.
Pushed by ngraham into branch 'master'.
Don't use a scrollview to display package changelogs
Summary:
Don't put the package changelogs in a scrollview, because it introduces some
usability issues (see the bug for details).
Also change the "Open" button to day "More Information..." since it wasn't
clear what you were opening.
Test Plan:
Tested in KDE Neon. Package changelogs are now fully visible without being in a
tiny scrollview:
{F5495553}
Reviewers: #discover_software_store, apol
Reviewed By: #discover_software_store, apol
Subscribers: abetts, broulik, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D8869
M +5-8discover/qml/UpdatesPage.qml
https://commits.kde.org/discover/732a0ffb2ab0cac9778ea490098ddad02ece824d
--
You are receiving this mail because:
You are watching all bug changes.
[Purpose] [Bug 387027] unversioned genericly named libs
https://bugs.kde.org/show_bug.cgi?id=387027 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pur ||pose/4b08657658fd8cd6a89911 ||ca2e3e9f79f2215e9c --- Comment #1 from Aleix Pol --- Git commit 4b08657658fd8cd6a89911ca2e3e9f79f2215e9c by Aleix Pol. Committed on 17/11/2017 at 16:19. Pushed by apol into branch 'master'. Version internal libraries from the plugins M +2-1src/plugins/phabricator/CMakeLists.txt M +2-1src/plugins/reviewboard/CMakeLists.txt https://commits.kde.org/purpose/4b08657658fd8cd6a89911ca2e3e9f79f2215e9c -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 387041] New: "Reason" and "Change Log" are frequently identical
https://bugs.kde.org/show_bug.cgi?id=387041 Bug ID: 387041 Summary: "Reason" and "Change Log" are frequently identical Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PackageKit Assignee: aleix...@kde.org Reporter: pointedst...@zoho.com Target Milestone: --- Created attachment 108922 --> https://bugs.kde.org/attachment.cgi?id=108922&action=edit "Reason:" and "Change Log" are nearly identical [Discover from git master on KDE Neon] See attached screenshot. In KDE Neon, with Ubuntu packaging, the Reason and Change Log fields both get populated, but are identical save for a few formatting differences. We probably don't need both in this case, but I'm not sure how we would go about detecting this in a sane and accurate manner. -- You are receiving this mail because: You are watching all bug changes.
[Purpose] [Bug 386952] "pure virtual function called" from Phabricator plugin
https://bugs.kde.org/show_bug.cgi?id=386952 --- Comment #2 from Aleix Pol --- Well, wait, this means we are doing a wrong cast, no? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387032] Desktop freeze and reload
https://bugs.kde.org/show_bug.cgi?id=387032 David Edmundson changed: What|Removed |Added Component|general |generic-crash Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386527] kdevelop crashes on startup -- "Failed to create OpenGL context"
https://bugs.kde.org/show_bug.cgi?id=386527 --- Comment #3 from Joachim Reichel --- Wasn't the plan to keep this bug open to implement a proper error message and/or prevent the crash if possible? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386527] kdevelop crashes on startup -- "Failed to create OpenGL context"
https://bugs.kde.org/show_bug.cgi?id=386527 Kevin Funk changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #4 from Kevin Funk --- Well, right. Reopened. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387042] New: root actions don't work
https://bugs.kde.org/show_bug.cgi?id=387042 Bug ID: 387042 Summary: root actions don't work Product: dolphin Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pawelci...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- One of the Root Actions, available when right clicking on a file or folder, is to open the folder as root. However, nothing happens after typing the password. Dolphin version 17.08.3 (not available in the version menu above). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387042] some root actions don't work
https://bugs.kde.org/show_bug.cgi?id=387042 Pawel changed: What|Removed |Added Summary|root actions don't work |some root actions don't ||work -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387043] New: Bold font rendering does not use Bold font variant
https://bugs.kde.org/show_bug.cgi?id=387043 Bug ID: 387043 Summary: Bold font rendering does not use Bold font variant Product: konsole Version: 17.08.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: k...@ashka.me Target Milestone: --- Created attachment 108923 --> https://bugs.kde.org/attachment.cgi?id=108923&action=edit Fontconfig It looks like the font renderer does not use the bold variant of the font when rendering bold, or if it does, it ignores fontconfig settings. I have seen some possible duplicates but I believe they do not apply to my issue. Attached are 2 screenshots created with this bash line: echo "`tput sgr0`this is `tput bold`bold`tput sgr0`". One is using the regular variant of the font, the other is using the bold variant of the font to show what rendering should look like on my system. Attached is also a slimmed version of my fontconfig. The font that I am using has a license that does not allow me to attach it to this ticket. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387043] Bold font rendering does not use Bold font variant
https://bugs.kde.org/show_bug.cgi?id=387043 --- Comment #1 from k...@ashka.me --- Created attachment 108924 --> https://bugs.kde.org/attachment.cgi?id=108924&action=edit Regular font style selected -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387043] Bold font rendering does not use Bold font variant
https://bugs.kde.org/show_bug.cgi?id=387043 --- Comment #2 from k...@ashka.me --- Created attachment 108925 --> https://bugs.kde.org/attachment.cgi?id=108925&action=edit Bold font style selected -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387043] Bold font rendering does not use Bold font variant
https://bugs.kde.org/show_bug.cgi?id=387043 k...@ashka.me changed: What|Removed |Added Attachment #108923|application/xml |text/plain mime type|| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387000] GPS Longitude Decimalisation Appears Incorrect In Map
https://bugs.kde.org/show_bug.cgi?id=387000 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/bac54a7834064573946a3c ||380be77b0e3f076e53 Status|UNCONFIRMED |RESOLVED Version Fixed In||5.8.0 Resolution|--- |FIXED --- Comment #3 from Maik Qualmann --- Git commit bac54a7834064573946a3c380be77b0e3f076e53 by Maik Qualmann. Committed on 17/11/2017 at 17:49. Pushed by mqualmann into branch 'master'. fix possible wrong return value from Exiv2 toRational() function FIXED-IN: 5.8.0 M +2-1NEWS M +32 -57 libs/dmetadata/metaengine_gps.cpp https://commits.kde.org/digikam/bac54a7834064573946a3c380be77b0e3f076e53 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384497] Rating reviews doesn't work
https://bugs.kde.org/show_bug.cgi?id=384497 Nate Graham changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Nate Graham --- Not able to reproduce this anymore. Let's call it fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 Venca B Spam changed: What|Removed |Added Version|5.1.80 |5.2.0 --- Comment #2 from Venca B Spam --- I tested KDevelop 5.2.0 from Neon packages today and it still do not work properly. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de --- Comment #3 from Sven Brauch --- Hm, actually I don't think we have a concept of adding system includes from projects at all, so this is not super simple to fix. I see how it's a minor problem in some specific situations, though. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387044] New: Don't complete class methods if "echo" is in added before
https://bugs.kde.org/show_bug.cgi?id=387044 Bug ID: 387044 Summary: Don't complete class methods if "echo" is in added before Product: kdevelop Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Code completion Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Created attachment 108926 --> https://bugs.kde.org/attachment.cgi?id=108926&action=edit Example In a PHP project opened with KDevelop, there are two files: 1. classes.php - which contains below code: 2. test_bench.php - which contains: If in the second file, I added the next row: $test-> the autocomplete is displayed with all public methods and variable from KDevelop_Test class. But if "echo" is added before $test->, the autocomplete after $test-> is not displayed and in my opinion this is an issue. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385519] Colors are displayed inverted when using ANGLE
https://bugs.kde.org/show_bug.cgi?id=385519 --- Comment #9 from nestorantonio@gmail.com --- Hello Alvin, how are you? Were you able to obtain new information on the other report? To tell you little bit more about my situation the main reason I been low on HD memory is because before using Parallels I tried in fact to do a dual boot with Windows using Bootcamp, an assistant that comes with the Mac that makes the process easier. However during the installation, when it was making the new partition, an error came up resulting on a dead space on my hard drive that I can't use anymore. That's why I haven't dared much to install a new OS natively on the Mac since then, and went for Parallels instead. Otherwise I would do it gladly, as a Krita user I'm very thankful with the work that the whole dev team has been doing on the software. Right now I'm using OpenGL without problems, but still if there is something I can help you with let me know. On Wed, Oct 25, 2017 at 7:18 PM, Nestor Antonio Zambrano < nestorantonio@gmail.com> wrote: > You're right, though at this moment it would be difficult for me to do a > dual boot because I'm running out of HD memory. After I tested Krita on the > Windows machine I realized that it also uses an Intel integrated graphic > card, so I made the test. We would have to wait if the other report > coincides with the specs of the mac then. > > On Oct 25, 2017 11:47 AM, "Alvin Wong" wrote: > >> https://bugs.kde.org/show_bug.cgi?id=385519 >> >> --- Comment #7 from Alvin Wong --- >> Will you be able to dual boot Windows on your mac (not using Parallels) >> to test >> it? Otherwise I think the chance of it being specifically related to >> Intel Iris >> is pretty low. >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387044] Don't complete class members if "echo" is in added before
https://bugs.kde.org/show_bug.cgi?id=387044 Silviu changed: What|Removed |Added Summary|Don't complete class|Don't complete class |methods if "echo" is in |members if "echo" is in |added before|added before -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #4 from Venca B Spam --- I did not dig into details (yet) however I was thinking that as long as KDevelop is using Clang as backend for C++ language support (code completion & friends), it does not play a role. I mean, if the Clang call for particular project/file is using proper flags/parameters, then KDevelop should receive proper expansion/evaluation of the completion query. Or am I completely wrong? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387044] Don't complete class members if "echo" is in added before
https://bugs.kde.org/show_bug.cgi?id=387044 Kevin Funk changed: What|Removed |Added CC||ppr...@liwjatan.at Component|Code completion |Language Support: PHP -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #5 from Sven Brauch --- It's not that simple, we can retrieve information from the build system but we assemble the compiler command line ourselves. We also add your hand-configured includes etc. and that code, from a quick look, simply doesn't have a way to add system includes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #6 from Venca B Spam --- Ok, I got it. I have observation that in some cases when the include is already written e.g. ```code #include ``` The included file can be "clicked-through" (Ctrl+LMB on the included file) which will open the file. Is this evaluated by different process/principle? This observation gives me still some home.. :-) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384162] Crash just after switching session [KDevelop::ProjectChangesModel::repositoryBranchChanged]
https://bugs.kde.org/show_bug.cgi?id=384162 --- Comment #4 from Kevin Funk --- Hm. I can't reproduce this issue here. :| For those who can reproduce every time, could you please check if this patch fixes the issue for you? https://phabricator.kde.org/D8852 David maybe? Thanks a lot in advance -- and sorry for taking your time. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387000] GPS Longitude Decimalisation Appears Incorrect In Map
https://bugs.kde.org/show_bug.cgi?id=387000 --- Comment #4 from hardy.pub...@gmail.com --- Many thanks Maik! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #7 from Sven Brauch --- I think the thing is that clang simply doesn't suggest local includes (specified with -I) when typing #include < even though the resulting code would still be compiling. Since we specify all your includes with -I (I think) the analyzer doesn't complain, but doesn't suggest the completions either. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383711] All Albums Disappear
https://bugs.kde.org/show_bug.cgi?id=383711 --- Comment #6 from hardy.pub...@gmail.com --- (In reply to vxd from comment #5) > I too have experience this issue many times. My albums are on an external > HDD and are marked as an external HDD. > > If the HDD is not connected after using Digikam the albums from the external > HDD will be removed when I close and open Digikam. So are you removing the HDD with digiKam open? If so, then I'm not surprised that digiKam removes the albums. I think it constantly scans for file changes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] IDefinesAndIncludesManager does not differentiate system and local includes (-isystem vs -I) retrieved from the build system, causing issues with C++ code completion
https://bugs.kde.org/show_bug.cgi?id=386421 Sven Brauch changed: What|Removed |Added Summary|KDevelop C++ code |IDefinesAndIncludesManager |completion does not respect |does not differentiate |user defined system-wide|system and local includes |include directories in |(-isystem vs -I) retrieved |CMake projects. |from the build system, ||causing issues with C++ ||code completion -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387044] Don't complete class members if "echo" is added before
https://bugs.kde.org/show_bug.cgi?id=387044 Silviu changed: What|Removed |Added Summary|Don't complete class|Don't complete class |members if "echo" is in |members if "echo" is added |added before|before -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386527] kdevelop crashes on startup -- "Failed to create OpenGL context"
https://bugs.kde.org/show_bug.cgi?id=386527 Sven Brauch changed: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||velop/49b5df418539b97137c2a ||9c63fa3ce139908e420 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Sven Brauch --- Git commit 49b5df418539b97137c2a9c63fa3ce139908e420 by Sven Brauch. Committed on 17/11/2017 at 19:00. Pushed by brauch into branch '5.2'. Use Software scene graph backend for welcome page Differential Revision: https://phabricator.kde.org/D8872 M +2-0app/CMakeLists.txt M +9-0app/main.cpp https://commits.kde.org/kdevelop/49b5df418539b97137c2a9c63fa3ce139908e420 -- You are receiving this mail because: You are watching all bug changes.
