[Akonadi] [Bug 403058] Crash of akonadiserver upon startup
https://bugs.kde.org/show_bug.cgi?id=403058 --- Comment #1 from Erik Quaeghebeur --- I did an update of Qt from 5.11.1 to 5.11.3 yesterday, and it seems this may have something to do with it. Namely, I observed the following on the konsole where I tried to start akonadi after it crashed: org.kde.pim.akonadicontrol: ProcessControl: Application "akonadiserver" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application 'akonadiserver' crashed! 1 restarts left. Cannot mix incompatible Qt library (version 0x50b01) with this library (version 0x50b03) KCrash: Application 'akonadiserver' crashing... KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 403058] New: Crash of akonadiserver upon startup
https://bugs.kde.org/show_bug.cgi?id=403058 Bug ID: 403058 Summary: Crash of akonadiserver upon startup Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: k...@equaeghe.nospammail.net Target Milestone: --- Application: akonadiserver (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.52.0 Operating System: Linux 4.14.83-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: The computer was starting up, so I assume that akonadiserver crashed while it was starting. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcc54cadd40 (LWP 10950))] Thread 2 (Thread 0x7fcc48641700 (LWP 10959)): #0 0x7fcc52970d63 in poll () from /lib64/libc.so.6 #1 0x7fcc4f4e70b9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcc4f4e71cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcc534edf5b in QEventDispatcherGlib::processEvents (this=0x7fcc4b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fcc53499ffa in QEventLoop::exec (this=this@entry=0x7fcc48640cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fcc532fdf5a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fcc53b62de5 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fcc533079af in QThreadPrivate::start (arg=0x7fcc53ddad60) at thread/qthread_unix.cpp:367 #8 0x7fcc517ee96a in start_thread () from /lib64/libpthread.so.0 #9 0x7fcc5297c92f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fcc54cadd40 (LWP 10950)): [KCrash Handler] #6 0x7fcc528ae83b in raise () from /lib64/libc.so.6 #7 0x7fcc528b0081 in abort () from /lib64/libc.so.6 #8 0x556c14b57bce in akMessageHandler (type=, context=..., msg=...) at /var/tmp/portage/kde-apps/akonadi-18.08.3/work/akonadi-18.08.3/src/shared/akdebug.cpp:177 #9 0x556c14b59fac in (anonymous namespace)::RemoteLogger::dbusLogger (type=QtFatalMsg, ctx=..., msg=...) at /var/tmp/portage/kde-apps/akonadi-18.08.3/work/akonadi-18.08.3/src/shared/akremotelog.cpp:183 #10 0x7fcc532f4107 in qt_message_print (msgType=msgType@entry=QtFatalMsg, context=..., message=...) at global/qlogging.cpp:1791 #11 0x7fcc532f41e8 in qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x7fcc53615aa0 "Cannot mix incompatible Qt library (version 0x%x) with this library (version 0x%x)", ap=ap@entry=0x7ffeb75e29a0) at global/qlogging.cpp:365 #12 0x7fcc532e16f8 in QMessageLogger::fatal (this=this@entry=0x7ffeb75e2a80, msg=msg@entry=0x7fcc53615aa0 "Cannot mix incompatible Qt library (version 0x%x) with this library (version 0x%x)") at global/qlogging.cpp:877 #13 0x7fcc534c232e in QObjectPrivate::QObjectPrivate (this=, version=) at kernel/qobject.cpp:217 #14 0x7fcc47c37c9e in QSqlDriverPrivate::QSqlDriverPrivate (this=0x556c167694a0) at /usr/include/qt5/QtSql/5.11.1/QtSql/private/qsqldriver_p.h:71 #15 QSQLiteDriverPrivate::QSQLiteDriverPrivate (this=0x556c167694a0) at /var/tmp/portage/kde-apps/akonadi-18.08.3/work/akonadi-18.08.3/src/qsqlite/src/qsql_sqlite.cpp:149 #16 QSQLiteDriver::QSQLiteDriver (this=0x556c1676ade0, parent=0x0) at /var/tmp/portage/kde-apps/akonadi-18.08.3/work/akonadi-18.08.3/src/qsqlite/src/qsql_sqlite.cpp:590 #17 0x7fcc47c3cf5e in QSQLiteDriverPlugin::create (this=, name=...) at /var/tmp/portage/kde-apps/akonadi-18.08.3/work/akonadi-18.08.3/src/qsqlite/src/smain.cpp:68 #18 0x7fcc53df6890 in ?? () from /usr/lib64/libQt5Sql.so.5 #19 0x7fcc53df6cd1 in QSqlDatabase::addDatabase(QString const&, QString const&) () from /usr/lib64/libQt5Sql.so.5 #20 0x556c149a750e in Akonadi::Server::AkonadiServer::createDatabase (this=this@entry=0x556c16761ca0) at /var/tmp/portage/kde-apps/akonadi-18.08.3/work/akonadi-18.08.3/src/server/akonadi.cpp:349 #21 0x556c149a9016 in Akonadi::Server::AkonadiServer::init (this=0x556c16761ca0) at /var/tmp/portage/kde-apps/akonadi-18.08.3/work/akonadi-18.08.3/src/server/akonadi.cpp:92 #22 0x7fcc534d0dd4 in QtPrivate::QSlotObjectBase::call (a=0x7ffeb75e2ee0, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 #23 QSingleShotTimer::timerEvent (this=0x556c1675f960) at kernel/qtimer.cpp:318 #24 0x7fcc534c53db in QObject::event (this=0x556c1675f960, e=) at kernel/qobject.cpp:1273 #25 0x7fcc5349b11a in doNotify (receiver=, event=) at kernel/qcoreapplication.cpp:1137 #26 0x7fcc5349b207 in QCoreApplication::notifyInternal2
[krita] [Bug 402625] Dialog box keeps popping up, saying that krita doesn't recognize file type
https://bugs.kde.org/show_bug.cgi?id=402625 --- Comment #6 from Tristan Y. --- (In reply to Boudewijn Rempt from comment #5) > Tristan: Um, doesn't this happen then? > > Ahab: long comments are fine in bugzilla. It does happen but I'm just saying stuff I thought you already knew so that why I said never mind, sorry for any confusion over that -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401912] Crash on adding GPS coordinates to multiple images (6.0.0beta3 Windows x64)
https://bugs.kde.org/show_bug.cgi?id=401912 --- Comment #5 from Andrius --- (In reply to caulier.gilles from comment #3) > Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just > released ? > > https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ I just added geolocation to about 500 images and the application did not crash... The only thing I have noticed is that digiKam regenerated thumbnails after I added GPS coordinates to the images. I am not sure why. -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 336020] Python script arguments do not update when input is updated
https://bugs.kde.org/show_bug.cgi?id=336020 Adit Jain changed: What|Removed |Added CC||aditjain1...@gmail.com --- Comment #4 from Adit Jain --- Hey I am new to the KDE community, I would like to get started (or get my feet wet as you say :)) Can I start working on this? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401912] Crash on adding GPS coordinates to multiple images (6.0.0beta3 Windows x64)
https://bugs.kde.org/show_bug.cgi?id=401912 --- Comment #4 from Andrius --- (In reply to caulier.gilles from comment #2) > Maik, > > Under Windows, we use now DrMinGW to get the crash backtrace automatically > in a dialog in this kind of situation (as under Linux in fact). > > There is no specific reason to run digiKam in GDB as well. The DrMinGW crash > handler must do the job instead. It's more simple for end users to report a > dysfunction. > > Andrius, do you see the crash handler dialog appear when application crash ? > If yes, all the relevant backtrace must be there. Just copy and paste the > contents in this file. > > Look like Krita application use also DrMinGW. The team provide a nice > documentation to get all debug information for developers : > > https://docs.krita.org/en/reference_manual/dr_minw_debugger.html > > Gilles Caulier Gilles, no the application crashes quietly and there is no DrMinGW window pops up. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 403057] New: Cannot build packages with Craft: cmake failed with exit code 9
https://bugs.kde.org/show_bug.cgi?id=403057 Bug ID: 403057 Summary: Cannot build packages with Craft: cmake failed with exit code 9 Product: Craft Version: unspecified Platform: Other OS: OS X Status: REPORTED Severity: normal Priority: NOR Component: Blueprints Assignee: vonr...@kde.org Reporter: audv...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- SUMMARY Getting no output from CMake. It seems CMake that is packaged through Craft is broken as even invoking it as `cmake --help` shows no output. STEPS TO REPRODUCE 1. Install Craft 2. Source craft environment 3. craft systemsettings OBSERVED RESULT 2019-01-09 22:52:51,851 DEBUG Command "/Users/tatsh/.local/share/dev-utils/bin/cmake" -G "Ninja" -DBUILD_TESTING=ON -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_INSTALL_PREFIX="/Users/tatsh/.local/share" -DCMAKE_PREFIX_PATH="/Users/tatsh/.local/share" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DKDE_INSTALL_BUNDLEDIR="/Users/tatsh/.local/share/Applications/KDE" -DAPPLE_SUPPRESS_X11_WARNING=ON -DKDE_INSTALL_USE_QT_SYS_PATHS=ON "/Users/tatsh/.local/share/build/kde/plasma/systemsettings/work/systemsettings-5.14.4" failed with exit code 9 2019-01-09 22:52:51,852 WARNING Action: compile for kde/plasma/systemsettings:5.14.4 FAILED 2019-01-09 22:52:51,852 INFO *** Craft all failed: kde/plasma/systemsettings after 1 second *** 2019-01-09 22:52:51,856 DEBUG Craft was unable to locate: snoretoast, in None 2019-01-09 22:52:51,856 ERROR fatal error: package kde/plasma/systemsettings all failed EXPECTED RESULT The package should build. SOFTWARE/OS VERSIONS Windows: MacOS: macOS 10.14.2 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 403056] Migration Testing
https://bugs.kde.org/show_bug.cgi?id=403056 Ben Cooksley changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/dum ||my/40695b5b27ba2cc7cf3b656b ||ca60cceb468e0b1d Resolution|--- |FIXED --- Comment #1 from Ben Cooksley --- Git commit 40695b5b27ba2cc7cf3b656bca60cceb468e0b1d by Ben Cooksley. Committed on 10/01/2019 at 03:14. Pushed by bcooksley into branch 'master'. Try 2, helps when hooks are enabled on the Dummy repository. D +0-7CHANGELOG https://commits.kde.org/dummy/40695b5b27ba2cc7cf3b656bca60cceb468e0b1d -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 403056] New: Migration Testing
https://bugs.kde.org/show_bug.cgi?id=403056 Bug ID: 403056 Summary: Migration Testing Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: bcooks...@kde.org CC: she...@kde.org Target Milestone: --- Testing the migration - all systems operational? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 120399] Kompare doesnt show arabic characters correctly
https://bugs.kde.org/show_bug.cgi?id=120399 michael changed: What|Removed |Added Assignee|joachim.e...@gmx.de |reeves...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 72625] keybindings settings dialogue
https://bugs.kde.org/show_bug.cgi?id=72625 Ralf Habacker changed: What|Removed |Added Version Fixed In||3.94.0 Status|CONFIRMED |RESOLVED CC||ralf.habac...@freenet.de Resolution|--- |FIXED Latest Commit||https://cgit.kde.org/umbrel ||lo.git/commit/?id=d72b1086d ||b5f4d96a083df9a08e83a226058 ||708d Latest Commit|https://cgit.kde.org/umbrel | |lo.git/commit/?id=d72b1086d | |b5f4d96a083df9a08e83a226058 | |708d| --- Comment #2 from Ralf Habacker --- The port to KDE Version 4 introduces a key binding dialog that implements this feature request. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403055] The entire UI is a bug. It is poorly functioning in several ways.
https://bugs.kde.org/show_bug.cgi?id=403055 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- It works fine for several users, so you are probably using a distribution that does not care for KDE software (many don't). In this case, you can use AppImages or different distributions. Please also read https://www.kde.org/code-of-conduct/ before reporting other issues. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403045] KDev-Python crashes when parsing RHS of annotated assignment with lambda [Python::UseBuilder::contextAtOrCurrent]
https://bugs.kde.org/show_bug.cgi?id=403045 Matěj Laitl changed: What|Removed |Added Summary|KDev-Python crashes when|KDev-Python crashes when |parsing Python 3.6 |parsing RHS of annotated |@dataclass definition with |assignment with lambda |field() |[Python::UseBuilder::contex |[Python::UseBuilder::contex |tAtOrCurrent] |tAtOrCurrent] | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 204768] Dolphin-Konqueror plugin to solve encoding problems marked as WONTFIX
https://bugs.kde.org/show_bug.cgi?id=204768 --- Comment #19 from Christoph Feck --- Is this still needed? I added code to https://bugreports.qt.io/browse/QTBUG-59402 that could be integrated into Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403055] New: The entire UI is a bug. It is poorly functioning in several ways.
https://bugs.kde.org/show_bug.cgi?id=403055 Bug ID: 403055 Summary: The entire UI is a bug. It is poorly functioning in several ways. Product: kdenlive Version: 18.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: randallcod...@protonmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start up the program 2. Click on any drop down window, or try drag a file, or do anything really 3. Be frustrated as buttons appear to "stick", you can't "let go" on objects, you reopen a menu you didn't click on 4. Question the motives behind making this software (pure sadism?) OBSERVED RESULT Buttons appear to "stick", you can't "let go" of objects at times, a menu drop down reopens without clicking on it. EXPECTED RESULT A normal and functioning UI. PHILOSOPHICAL NOTE This is why communism doesn't work. Free products are often poorly made compared to commercial software SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403027] type inference bloats when functools.partial is present, but functools is not imported
https://bugs.kde.org/show_bug.cgi?id=403027 Francis Herne changed: What|Removed |Added Status|REPORTED|CONFIRMED Component|Code completion |Language support Ever confirmed|0 |1 Severity|minor |crash CC||m...@flherne.uk --- Comment #1 from Francis Herne --- Er...right. Yes. WHAT? HOW? Thanks for the report, I can reproduce this with 5.3-git and the provided example. Occasionally (but not always) the type was rounded to `unsure(Instance, ) bar...`, which is slightly more reasonable and prevented it from growing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403038] KWin crashes (occasionally) when running script to minimize current open window
https://bugs.kde.org/show_bug.cgi?id=403038 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/ba7aecfe53d765e0f94626ed0 ||0010a40284b99c0 Resolution|--- |FIXED --- Comment #4 from David Edmundson --- Git commit ba7aecfe53d765e0f94626ed00010a40284b99c0 by David Edmundson. Committed on 09/01/2019 at 23:37. Pushed by davidedmundson into branch 'master'. [scripting] Avoid threading issues when loading from a file Summary: KWin::Script::loadScriptFromFile ran in it's own thread and accessed member variables of KWin::Script without any guards. Potentially script could be destroyed whilst the file is loading. Rather than adding mutexes everywhere, this patch scopes the QFile object to be local to the threaded function making it independent. Test Plan: Ran a script from a file Reviewers: #kwin, graesslin Reviewed By: #kwin, graesslin Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D18126 M +8-8scripting/scripting.cpp M +3-6scripting/scripting.h https://commits.kde.org/kwin/ba7aecfe53d765e0f94626ed00010a40284b99c0 -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403045] KDev-Python crashes when parsing Python 3.6 @dataclass definition with field() [Python::UseBuilder::contextAtOrCurrent]
https://bugs.kde.org/show_bug.cgi?id=403045 --- Comment #2 from Francis Herne --- Even tinier example: `foo: Any = lambda x: 10` Cause is that contextAtOrCurrent() fails on the RHS of annotated assignments. The same crash occurs with a comprehension in place of the lambda. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] New: GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 Bug ID: 403054 Summary: GeoIP.dat.gz Product: ktorrent Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: glenn...@glennmcc.org Target Milestone: --- Created attachment 117375 --> https://bugs.kde.org/attachment.cgi?id=117375=edit screen capture of ktorrent message SUMMARY File or folder not found STEPS TO REPRODUCE 1. start ktorrent OBSERVED RESULT The file or folder http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz does not exist EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 402932] Framerate displayed in UI is bad compared to framerate possible when shooting a video
https://bugs.kde.org/show_bug.cgi?id=402932 --- Comment #2 from Nate Graham --- Found a way to semi-reproduce: 1. Open Kamoso -> displayed video framerate is < 1 FPS 2. Open effects gallery drawer: framerate of video behind drawer becomes normal 3. Close drawer: some of the time, the framerte of the video reverts again 4. Open and close drawer repeatedly: framerate of video becomes normal for a while, including after closing and re-opening the app The trick for me is that the framerate of the main video is always normal while the Effects Gallery drawer is open. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402044] Global menu duplicates LibreOffice menus
https://bugs.kde.org/show_bug.cgi?id=402044 Christoph Feck changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #3 from Christoph Feck --- Let's re-open it for further inspection. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403045] KDev-Python crashes when parsing Python 3.6 @dataclass definition with field() [Python::UseBuilder::contextAtOrCurrent]
https://bugs.kde.org/show_bug.cgi?id=403045 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Version|5.2.4 |5.3.1 Target Milestone|--- |5.3.2 Assignee|m...@svenbrauch.de |m...@flherne.uk Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Francis Herne --- Confirmed; still reproducible with 5.3-git. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 402932] Framerate displayed in UI is bad compared to framerate possible when shooting a video
https://bugs.kde.org/show_bug.cgi?id=402932 --- Comment #1 from Nate Graham --- Having used Kamoso a lot lately, I note that this is only sometimes reproducible: sometimes the framerate is abysmal, and sometimes it's fine. Generally the first time I launch Kamoso after not using it for a day or so, the framerate is bad, but then at some point while I'm repeatedly launching it while testing patches, I suddenly notice that the framerate is normal. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 403049] 17.12.3 does not open *.xcf files. The previous version did.
https://bugs.kde.org/show_bug.cgi?id=403049 --- Comment #2 from Christoph Feck --- This might be a duplicate of bug 360821. GIMP has changed the .xcf image format for GIMP 2.9 and later, so if you also upgraded GIMP, you could check if it is possible to write in the old (GIMP 2.8) format. If not, exporting to any other lossless format (.png or .tiff) should also work. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 403001] Scheduled transactions show wrong date in forecast and ignore action for non-processing day
https://bugs.kde.org/show_bug.cgi?id=403001 Ian Neal changed: What|Removed |Added Keywords||regression --- Comment #1 from Ian Neal --- This did work correctly under 4.8.x so is a regression. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 Mathias Johansson changed: What|Removed |Added CC||luni...@gmail.com --- Comment #124 from Mathias Johansson --- Hi, I think i may encounter the same issue. I wrote about my issues in #401253 This is what happens when i run Beta 3 and run scan faces on my collection. nCVFaceDetector::cascadeResult: detectMultiScale: image size ( 800 , 450 ) searchIncrement 1.1 grouping 3 flags 1 min size ( 26 , 26 ) Digikam::IccManager::IccManager: Cannot open workspace color profile "" Digikam::DImg::load: "/home/mathias/photos/Osorterat/Mathias/osorterade bilder/Messenger/received_10208789201436022.jpeg" : JPEG file identified Digikam::FacePipeline::Private::checkFinished: Check for finish: 51 packages, 0 infos to filter, hasFinished() false Digikam::FacePipeline::Private::checkFinished: Check for finish: 51 packages, 0 infos to filter, hasFinished() false Digikam::FacePipeline::Private::checkFinished: Check for finish: 51 packages, 0 infos to filter, hasFinished() false Digikam::DImg::load: "/home/mathias/photos/Osorterat/Mathias/osorterade bilder/Messenger/received_10208790012496298.jpeg" : JPEG file identified /tmp/.mount_digika4WzBy9/AppRun: line 115: 1381 Segmentation fault (core dumped) digikam $@ Cam I help you in anyway? I have just started to test out Digikam to see if I like the workflow. However my Face detect still crashes in BETA 3 as it did in BETA 2. I have tested it with both a local database, Centralized MySQL environment. Tested it on 2 different Windows 10 and also installed a xUbuntu 18.04 and all of them crashes in BETA 3. I then tested in 5.9 and it seems stable (not had that much time to test). If you guys need help with debugging just give me a shout. I have both windows / Linux machine running. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 402805] Right and middle mouse don't work sometimes
https://bugs.kde.org/show_bug.cgi?id=402805 --- Comment #2 from k...@trummer.xyz --- I think it started happening after the upgrade to Qt 5.12 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 402929] .xml file assoc: Kate moves to #2 in priority list against my will
https://bugs.kde.org/show_bug.cgi?id=402929 --- Comment #7 from Alexander Potashev --- Then I checked the filetypes KCM again and the list for application/xml is still as follows: Google Chrome Kate Firefox Konqueror ... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 402929] .xml file assoc: Kate moves to #2 in priority list against my will
https://bugs.kde.org/show_bug.cgi?id=402929 --- Comment #6 from Alexander Potashev --- Thanks! [aspotashev@glue ~]$ qtpaths --locate-file GenericConfigLocation mimeapps.list /home/aspotashev/.config/mimeapps.list [aspotashev@glue ~]$ cat /home/aspotashev/.config/mimeapps.list [Added Associations] application/pdf=org.kde.okular.desktop; application/rtf=libreoffice-writer.desktop; application/xml=google-chrome.desktop;firefox.desktop;kfmclient_html.desktop;org.kde.kate.desktop;wine-extension-xml.desktop;org.kde.kwrite.desktop;libreoffice-writer.desktop;okularApplication_txt.desktop;org.kde.calligrawords_ascii.desktop;wine-extension-txt.desktop; model/x.stl-binary=org.kde.okteta.desktop; text/plain=org.kde.kate.desktop; [Added KDE Service Associations] application/xhtml+xml=khtml.desktop;webenginepart.desktop; application/xml=khtml.desktop;webenginepart.desktop; text/html=khtml.desktop;webenginepart.desktop; [Default Applications] application/pdf=org.kde.okular.desktop; application/rtf=libreoffice-writer.desktop; application/xml=google-chrome.desktop; model/x.stl-binary=org.kde.okteta.desktop; text/html=firefox.desktop text/plain=org.kde.kate.desktop; x-scheme-handler/http=google-chrome.desktop; x-scheme-handler/https=google-chrome.desktop; x-scheme-handler/jetbrains=jetbrains-toolbox.desktop x-scheme-handler/slack=slack.desktop x-scheme-handler/tg=telegramdesktop.desktop [aspotashev@glue ~]$ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360262] Plasmashell and krunner stop responding after copying text to clipboard
https://bugs.kde.org/show_bug.cgi?id=360262 --- Comment #5 from Alexander Meshcheryakov --- I found that "Configure Clipboard -> Actions -> Enable MIME-based actions" has to be enabled to observe this bug. What a relief, I can just disable this feature and don't observe this hangup anymore. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402192] Can't run flatpaks from within Discover (packaged using flatpak)
https://bugs.kde.org/show_bug.cgi?id=402192
--- Comment #6 from Andrey ---
Am I understand right I can just move away desktopFile in my installation to
try, without modifying the code?:
const QString desktopFile = installPath() +
QStringLiteral("/export/share/applications/") + appstreamId();
const QString runservice = QStringLiteral(CMAKE_INSTALL_FULL_LIBEXECDIR_KF5
"/discover/runservice");
if (QFile::exists(desktopFile) && QFile::exists(runservice)) {
QProcess::startDetached(runservice, {desktopFile});
return;
}
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 402738] symlinks to mounted NTFS volumes are hidden in Dolphin
https://bugs.kde.org/show_bug.cgi?id=402738 --- Comment #2 from kdeb...@caseyconnor.org --- Huh, I see the discussion at https://phabricator.kde.org/D13782 And it does look like that code is in place as you describe: https://cgit.kde.org/kio.git/tree/src/ioslaves/file/file_unix.cpp?h=v5.50.0#n567 I don't know if the umask matters, but as reported above, I use umask=007 in /etc/fstab -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403053] SAFE ASSERT (krita): "!sanityCheckPointer.isValid()" in KisDocument.cpp line 501
https://bugs.kde.org/show_bug.cgi?id=403053 --- Comment #1 from fabian.castronu...@gmail.com --- EDIT: I forgot: it seems the file was saved OK. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403053] New: SAFE ASSERT (krita): "!sanityCheckPointer.isValid()" in KisDocument.cpp line 501
https://bugs.kde.org/show_bug.cgi?id=403053 Bug ID: 403053 Summary: SAFE ASSERT (krita): "!sanityCheckPointer.isValid()" in KisDocument.cpp line 501 Product: krita Version: 4.1.5 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: fabian.castronu...@gmail.com Target Milestone: --- Created attachment 117374 --> https://bugs.kde.org/attachment.cgi?id=117374=edit error message screenshot SUMMARY When closing a document and clicking in "Yes" when asked to save it, this error appeared. STEPS TO REPRODUCE 1. I couldn't reproduce it, and it only happened once. 2. - 3. - OBSERVED RESULT - EXPECTED RESULT - SOFTWARE/OS VERSIONS Linux/Cinnamon ADDITIONAL INFORMATION Krita Version: 4.1.5 Qt Version (compiled): 5.10.0 Version (loaded): 5.10.0 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.15.0-43-generic Pretty Productname: Linux Mint 18.3 Product Type: linuxmint Product Version: 18.3 OpenGL Info **OpenGL not initialized** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 254099] SCAN : refresh collection with a script in commandline
https://bugs.kde.org/show_bug.cgi?id=254099 stefan.mueller...@gmail.com changed: What|Removed |Added CC||stefan.mueller...@gmail.com --- Comment #5 from stefan.mueller...@gmail.com --- any chance that it could be realized after the DK 6 release? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 403052] New: Crashes out of Google login after 'Next' is pressed from email going into password entry
https://bugs.kde.org/show_bug.cgi?id=403052 Bug ID: 403052 Summary: Crashes out of Google login after 'Next' is pressed from email going into password entry Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: xtian170...@googlemail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Go to Google account login page 2. type email address 3. click next OBSERVED RESULT program terminates EXPECTED RESULT password entry form SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Ubuntu Studio 18.10 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Just installed, first thing attempted although took a few reboots to see it performing at expected computer speed - numerous times loading Google home page appeared hanging with a progress bar around 37%. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403050] Export to remote storage does not work
https://bugs.kde.org/show_bug.cgi?id=403050 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 397856 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 397856] Export to remote storage: transfer not done
https://bugs.kde.org/show_bug.cgi?id=397856 --- Comment #6 from Maik Qualmann --- *** Bug 403050 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403051] New: In Neon 18.04, kaffeine no longer recognises existence of tuner card
https://bugs.kde.org/show_bug.cgi?id=403051 Bug ID: 403051 Summary: In Neon 18.04, kaffeine no longer recognises existence of tuner card Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: rb_y...@yahoo.co.uk CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Originally reported as Kaffeine bug - Bug ID 400815 Having recently installed Neon 18.04, kaffeine no longer recognises the existence of the tuner card - in fact the Start pane in kaffeine lacks the 'Digital TV' box and the 'Television' menu entry. Response to Bug ID 400815 is that this is a packaging bug - this version of Kaffeine has been compiled without Digital TV support. STEPS TO REPRODUCE 1. Install Neon 18.04 2. Install kaffeine from the Neon repos. 3. Start up kaffeine OBSERVED RESULT No 'Digital TV' box on Start panel and no 'Television' on menu bar. EXPECTED RESULT 'Digital TV' box on Start panel and 'Television' option on menu bar. SOFTWARE VERSIONS Kaffeine: 2.0.15 KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 (built against 5.11.1) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402638] High CPU usage when searching
https://bugs.kde.org/show_bug.cgi?id=402638 Peter Eszlari changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Version|5.14.4 |unspecified Resolution|FIXED |--- --- Comment #2 from Peter Eszlari --- This also happens with the master branch. But I found something: If I minimize Discover's windows, the searching stops and the CPU usage is down. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403050] New: Export to remote storage does not work
https://bugs.kde.org/show_bug.cgi?id=403050 Bug ID: 403050 Summary: Export to remote storage does not work Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Export-FileTransfer Assignee: digikam-bugs-n...@kde.org Reporter: philippe.quag...@laposte.net Target Milestone: --- SUMMARY In beta 3, the export image to remote storage does not work, i get the following error: «some images have not been transfered and are still in the queue. Try again». But in fact, whatever I try I always get this message and no images are transfered. STEPS TO REPRODUCE 1. select image 2. choose export to remote storage 3. export OBSERVED RESULT error message, nothing transfered EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: ubuntu appimage (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403047] Inhibit powersaving for fullscreen applications
https://bugs.kde.org/show_bug.cgi?id=403047 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- That's not true. It's inhibiting for any app that chooses to inhibits. You also don't need an additional plasmoid, you can disable power management from the main battery applet. I don't think an option based on guessing heuristics helps. For the users that enable it they'll get false positives and we still have a bug for the users that don't enable it. >for playing games with controllers. Then lets fix that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392607] Crash sometimes when applying Tags to images
https://bugs.kde.org/show_bug.cgi?id=392607 --- Comment #9 from Maik Qualmann --- It crashes relatively deep in the QSortFilterProxyModel. There have been Qt bugreports lately. I can not reproduce the problem. we'll see if they can reproduce the problem with Qt-5.12. https://bugreports.qt.io/browse/QTBUG-44962 https://bugreports.qt.io/browse/QTBUG-67948 Maik -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 403049] 17.12.3 does not open *.xcf files. The previous version did.
https://bugs.kde.org/show_bug.cgi?id=403049 Martin Koller changed: What|Removed |Added Resolution|--- |NOT A BUG CC||kol...@aon.at Status|REPORTED|RESOLVED --- Comment #1 from Martin Koller --- kolourpaint does not implement the ability to read any file format. This is done by using KDE's imageformat plugins. On my system xcf is handled by /usr/lib64/qt5/plugins/imageformats/kimg_xcf.so which is here part of the kimageformats rpm package. Check your installation - something is missing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #22 from lurulf --- It really seems that you have a hidden entry between your "from" and "to" destination. Right-click on an empty area of the places panel, and I bet you get an option "Show hidden places" or "Show all entries". When you get the "move, copy, link" options, you have dropped an entry above another. You have to place it between two entries so the blue border line appears. Hope this help. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 403049] New: 17.12.3 does not open *.xcf files. The previous version did.
https://bugs.kde.org/show_bug.cgi?id=403049 Bug ID: 403049 Summary: 17.12.3 does not open *.xcf files. The previous version did. Product: kolourpaint Version: 18.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: dovegl...@yahoo.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Click File > Open. 2. Navigate to an *.xcf file. 3. Try to open it. OBSERVED RESULT It does not open and there's an error message that kolourpaint cannot not open *.xcf files. EXPECTED RESULT kolourpaint should open *.xcf files ( made in Gimp ) so I can save it as *.png, as it did in the previous version. SOFTWARE/OS VERSIONS Linux Mint 19.1 Cinnamon with kde-runtime ADDITIONAL INFORMATION I have to boot Mint 18.3 ( other partition ) to use the previous version for *.xcf processing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403048] New: Freeze in Strokes/Layers jobs [GDB backtrace]
https://bugs.kde.org/show_bug.cgi?id=403048
Bug ID: 403048
Summary: Freeze in Strokes/Layers jobs [GDB backtrace]
Product: krita
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Layer Stack
Assignee: krita-bugs-n...@kde.org
Reporter: griffinval...@gmail.com
Target Milestone: ---
SUMMARY
Krita freezes from time to time, not sure what is causing it(it seems to be
related with hiding and showing layers), but I do get a backtrace in GDB when
sending ctrl+c.
Image is a 300dpi a4 with 8bit and two layers.
-
Thread 1 "krita" received signal SIGINT, Interrupt.
0x70f362fc in KisUpdaterContext::getContextSnapshotEx
(this=0x6811f480) at
/home/wolthera/krita/src/libs/image/kis_updater_context.cpp:68
68 Q_FOREACH (const KisUpdateJobItem *item, m_jobs) {
(gdb) thread apply all backtrace
Thread 9 (Thread 0x7fff9aaa3700 (LWP 4425)):
#0 0x7314bbf9 in __GI___poll (fds=0x7fff8c003ce0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fffeaf18539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fffeaf1864c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x73c9e04b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x73c4230a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x73a6dbba in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x73a78adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x7fffec8146db in start_thread (arg=0x7fff9aaa3700) at
pthread_create.c:463
#8 0x7315888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 8 (Thread 0x7fff9b2a4700 (LWP 4412)):
#0 0x7314bbf9 in __GI___poll (fds=0x7fff94005440, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fffeaf18539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fffeaf1864c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x73c9e02f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x73c4230a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x73a6dbba in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7fffd889d826 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7 0x73a78adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x7fffec8146db in start_thread (arg=0x7fff9b2a4700) at
pthread_create.c:463
#9 0x7315888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 7 (Thread 0x7fffb1caf700 (LWP 4403)):
#0 0x7314bbf9 in __GI___poll (fds=0x7fff9c004ee0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7fffeaf18539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fffeaf1864c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x73c9e02f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x73c4230a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x73a6dbba in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7fffd84224f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7 0x73a78adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x7fffec8146db in start_thread (arg=0x7fffb1caf700) at
pthread_create.c:463
#9 0x7315888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 6 (Thread 0x7fffb14ae700 (LWP 4374)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x73a6c870 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2 0x73a6c6e2 in QSemaphore::tryAcquire(int, int) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3 0x70dd6e4c in KisTileDataSwapper::waitForWork (this=0x715464e0
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>)
at
/home/wolthera/krita/src/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86
#4 0x70dd6e68 in KisTileDataSwapper::run (this=0x715464e0
<(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder+64>)
at
/home/wolthera/krita/src/libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92
#5 0x73a78adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7fffec8146db in start_thread (arg=0x7fffb14ae700) at
pthread_create.c:463
#7 0x7315888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 4 (Thread 0x7fffb4412700 (LWP
[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState()
https://bugs.kde.org/show_bug.cgi?id=402328 --- Comment #8 from Serge Moreau --- I am not used with these kinds of procedure. I installed Plasma-discover-debug. Tell me what I must do. Sorry SM -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 403047] New: Inhibit powersaving for fullscreen applications
https://bugs.kde.org/show_bug.cgi?id=403047 Bug ID: 403047 Summary: Inhibit powersaving for fullscreen applications Product: Powerdevil Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: darkwingbuc...@gmail.com Target Milestone: --- Right now, power saving only inhibits for media players. I have to use the Caffeine Plus plasmoid to correctly inhibit power saving in situations for playing games with controllers. Power management should also have an option to inhibit when any full screen application is running -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402883] Useless search in installed apps
https://bugs.kde.org/show_bug.cgi?id=402883 --- Comment #7 from Nate Graham --- Oh, of course. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403046] New: Clicking "Update This Installer" Doesn't Do Anything
https://bugs.kde.org/show_bug.cgi?id=403046 Bug ID: 403046 Summary: Clicking "Update This Installer" Doesn't Do Anything Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: cdbing...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Running the live image and then clicking install; the installer starts and gives some text under 'Language' saying, "You may wish to update this installer". However, clicking "update this installer" does nothing. STEPS TO REPRODUCE 1. Run live image. 2. Click 'install neon user'. 3. Click "update this installer". OBSERVED RESULT Nothing happens. EXPECTED RESULT The installer is updated and returns updated or returns no update necessary. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.14 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402826] Code recognition does not work all the time
https://bugs.kde.org/show_bug.cgi?id=402826 --- Comment #1 from jd.fratt...@free.fr --- When using kdevelop for a long (ie several hours or even more) without interrupting (no kdevelop restart, no reboot), such a thing could happen: file a.cpp is well recognized at the beginning of the session. Edit other files (a.cpp can be kept in a tab or be closed). Later on, come back to edit a.cpp, some functions, namespaces or classes are not recognized anymore. Or the full file is completely full of white words. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState()
https://bugs.kde.org/show_bug.cgi?id=402328 --- Comment #7 from Aleix Pol --- Hey, I'm sorry but that's not showing the debug symbols for the fwupd backend which is what we're after. Which package did you install? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402523] Discover crashing everytime
https://bugs.kde.org/show_bug.cgi?id=402523 Max changed: What|Removed |Added CC||therainson...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402883] Useless search in installed apps
https://bugs.kde.org/show_bug.cgi?id=402883 --- Comment #6 from Aleix Pol --- We can (and it applies cleanly), although 5.14.6 won't happen so it's not going to make a difference. :/ -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 403039] The Interest pull down field missing when trying to enter income transaction in Investment ledger
https://bugs.kde.org/show_bug.cgi?id=403039 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/a606f027f9dade40b2706 ||36dc46cfc0d33340ed2 Version Fixed In||5.0.3 --- Comment #1 from Thomas Baumgart --- Git commit a606f027f9dade40b270636dc46cfc0d33340ed2 by Thomas Baumgart. Committed on 09/01/2019 at 19:17. Pushed by tbaumgart into branch '5.0'. Fix investment transaction editor The investment transaction editor did not handle all fields according to the selected transaction type. This change fixes these issues. FIXED-IN: 5.0.3 M +9-9kmymoney/dialogs/investactivities.cpp M +0-63 kmymoney/dialogs/investtransactioneditor.cpp M +0-2kmymoney/dialogs/investtransactioneditor.h https://commits.kde.org/kmymoney/a606f027f9dade40b270636dc46cfc0d33340ed2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 347685] Transaction contains erroneous *** UNASSIGNED *** in Tags view if no payee is given
https://bugs.kde.org/show_bug.cgi?id=347685 Thomas Baumgart changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.0.3 Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kmy ||money/97e3186babf1d4426f5fb ||d2cd9c9a6da459ea37d --- Comment #9 from Thomas Baumgart --- Git commit 97e3186babf1d4426f5fbd2cd9c9a6da459ea37d by Thomas Baumgart. Committed on 03/01/2019 at 16:34. Pushed by tbaumgart into branch '5.0'. Fix transaction register display in tags view In case a transaction had a tag assigned, an amount differing from zero, a category assigned but no payee, the register in the tags view showed wrong results. This fixes the behavior so that the memo is shown instead of the erroneous text "*** UNASSIGNED ***" FIXED-IN: 5.0.3 M +8-5kmymoney/widgets/stdtransaction.cpp https://commits.kde.org/kmymoney/97e3186babf1d4426f5fbd2cd9c9a6da459ea37d -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 246028] wish for being able to save "sessions" (with multiple tabs)
https://bugs.kde.org/show_bug.cgi?id=246028 Mel changed: What|Removed |Added CC||samme...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 306257] Add a feature so that we can save and restore a dolphin session
https://bugs.kde.org/show_bug.cgi?id=306257 Mel changed: What|Removed |Added CC||samme...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384392] konsole (always), kwrite (sometimes) doesn't restore "Application menu" in title bar after restore session
https://bugs.kde.org/show_bug.cgi?id=384392 Mel changed: What|Removed |Added CC||samme...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402563] Plasma freezes when I right click on some entry in the apps launcher
https://bugs.kde.org/show_bug.cgi?id=402563 mail.mac...@gmail.com changed: What|Removed |Added CC||mail.mac...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 403042] Qt5 from KDE 5.12 runtime requires Linux kernel >= 3.17
https://bugs.kde.org/show_bug.cgi?id=403042 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||aleix...@kde.org --- Comment #1 from Aleix Pol --- Should be fixed as of https://phabricator.kde.org/R257:a029f2957e947f6e32fe8a595edb0ac553654e90 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371211] No metadata editing offered anymore
https://bugs.kde.org/show_bug.cgi?id=371211 --- Comment #4 from Knut Hildebrandt --- (In reply to caulier.gilles from comment #3) > Note : it's now possible since version 5.0.0 to use this tool from Showfoto > image editor, if you don't want to use digiKam as well.. I already have noticed and use it there. But that is only a workaround, since my standard image viewer is gwenview. From gwenview there I used to make minor changes to metadata until it vanished from kipiplugins. Digikam I only use to mange my picture archive, which are stored on a separate external disk. Anyhow, thanks for the hint. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401967] Tasks progress starts with 0% in batch removal/installation
https://bugs.kde.org/show_bug.cgi?id=401967 Aleix Pol changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Aleix Pol --- We are showing the percentage of remaining transactions, I'd say it's okay. It also wouldn't make sense to start at 80% after having done some operations. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401177] Discover doesn't show Wallpapers, only "still looking" throbber
https://bugs.kde.org/show_bug.cgi?id=401177 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Aleix Pol --- This should be fixed please test on 5.15 and reopen if it's not the case. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401827] none/tests/ppc64/test_isa_2_06_part3 failure on ppc64le (xvrsqrtesp)
https://bugs.kde.org/show_bug.cgi?id=401827 Will Schmidt changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Will Schmidt --- At first blush, behaviour here is similar to what is being seen in 401828 (valgrind, errors with isa_2_06_part1 test). Net is that the testcase fails under valgrind when a newer gcc is used to build it.Test runs OK outside of valgrind. Test runs OK under valgrind if the test is built with -O0. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401334] No application back-ends found, please report to your distribution error when launching Discover
https://bugs.kde.org/show_bug.cgi?id=401334 --- Comment #18 from Aleix Pol --- Can you still see this? This is very weird... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401845] Package not found error after second and subsequent cancellations of installation/removal of same app
https://bugs.kde.org/show_bug.cgi?id=401845 --- Comment #5 from Aleix Pol --- Also see c980ddf6. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 355594] Create new folder with existent name does nothing
https://bugs.kde.org/show_bug.cgi?id=355594 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|FIXED |DUPLICATE --- Comment #6 from Nate Graham --- *** This bug has been marked as a duplicate of bug 400423 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 400423] No warning when creating conflicting directory
https://bugs.kde.org/show_bug.cgi?id=400423 Nate Graham changed: What|Removed |Added CC||codestr...@posteo.org --- Comment #6 from Nate Graham --- *** Bug 355594 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401845] Package not found error after second and subsequent cancellations of installation/removal of same app
https://bugs.kde.org/show_bug.cgi?id=401845 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||6469e828293af01b6dfa3bf30b2 ||88761756f6554 Version Fixed In||5.15 Status|REPORTED|RESOLVED --- Comment #4 from Aleix Pol --- This should have been fixed by 6469e828293af01b6dfa3bf30b288761756f6554 which will be in 5.15. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 403045] KDev-Python crashes when parsing Python 3.6 @dataclass definition with field() [Python::UseBuilder::contextAtOrCurrent]
https://bugs.kde.org/show_bug.cgi?id=403045 Kevin Funk changed: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |m...@svenbrauch.de Component|general |general CC||m...@svenbrauch.de Product|kdevelop|kdev-python -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403045] KDev-Python crashes when parsing Python 3.6 @dataclass definition with field() [Python::UseBuilder::contextAtOrCurrent]
https://bugs.kde.org/show_bug.cgi?id=403045 Kevin Funk changed: What|Removed |Added Summary|KDev-Python crashes when|KDev-Python crashes when |parsing Python 3.6 |parsing Python 3.6 |@dataclass definition with |@dataclass definition with |field() |field() ||[Python::UseBuilder::contex ||tAtOrCurrent] -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399571] [KNS] Update button can take a long time to get enabled when any backends are slow to update
https://bugs.kde.org/show_bug.cgi?id=399571 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Aleix Pol --- This issue was fixed with: https://phabricator.kde.org/D17593 https://phabricator.kde.org/D17594 If it resurfaces we can decide to start timeout-ing backends. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402553] Icon in sources dropdown looks a checkbox
https://bugs.kde.org/show_bug.cgi?id=402553 --- Comment #1 from Aleix Pol --- Created attachment 117372 --> https://bugs.kde.org/attachment.cgi?id=117372=edit On my neon system Doesn't look like this in here. It should be showing the "package-available" icon. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 355594] Create new folder with existent name does nothing
https://bugs.kde.org/show_bug.cgi?id=355594 Shubham changed: What|Removed |Added Resolution|--- |FIXED CC||aryan100jan...@gmail.com Status|REPORTED|RESOLVED --- Comment #5 from Shubham --- https://phabricator.kde.org/D17617 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402192] Can't run flatpaks from within Discover (packaged using flatpak)
https://bugs.kde.org/show_bug.cgi?id=402192 --- Comment #5 from Aleix Pol --- You can try commenting the runservice bit in FlatpakResource::invokeApplication and see if it works. Beyond it's discover asking flatpak to run. If that solves it we can see to changing the code the right way. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402491] Unclear behavior when internet connection is interrupted during an update
https://bugs.kde.org/show_bug.cgi?id=402491 Aleix Pol changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Aleix Pol --- Can you check what happens when you do this with pkcon separately? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402638] High CPU usage when searching
https://bugs.kde.org/show_bug.cgi?id=402638 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||2029e2b98d8a4e6a124c0240e8b ||2cca79a0c05b7 Status|REPORTED|RESOLVED Version Fixed In||5.15.0 --- Comment #1 from Aleix Pol --- This should be solved as of 2029e2b98d8a4e6a124c0240e8b2cca79a0c05b7 which will appear in 5.15. It would be useful if you can test master FWIW, as this is a rather big change. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 --- Comment #2 from Will Schmidt --- Created attachment 117371 --> https://bugs.kde.org/attachment.cgi?id=117371=edit simpler standalone testcase simpler standalone testcase -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401828] none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and fcfidus)
https://bugs.kde.org/show_bug.cgi?id=401828 Will Schmidt changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Will Schmidt --- Started to investigate this one. Still more investigation to do, but I wanted to do a snapshot braindump at this point. It looks like the behavior is affected by the optimization level used to build the testcase itself. Using a significantly stripped down test that exercises the fcfids instruction similar to how the valgrind test does, I see # $> gcc -v gcc version 9.0.0 20181130 (experimental) (GCC) > gcc test_fcfids.c -O0 -o test_fcfids 11:37:31 0 p8 ppc64le willschm@pike:~/valgrind_builds/valgrind/none/tests/ppc64> valgrind ./test_fcfids ==104410== Memcheck, a memory error detector <...> 0.00 0 0 testcase => (raw sp)0 ) 1000.00 1 4.65201e+18 testcase 408f4000 => (raw sp) 5e811e80 ) But with -O or -O1 (or higher), the 5e811e80 value disappears. 11:39:04 0 p8 ppc64le willschm@pike:~/valgrind_builds/valgrind/none/tests/ppc64> gcc test_fcfids.c -O1 -o test_fcfids 11:39:12 0 p8 ppc64le willschm@pike:~/valgrind_builds/valgrind/none/tests/ppc64> valgrind ./test_fcfids ==104524== Memcheck, a memory error detector <...> 0.00 0 0 testcase => (raw sp)0 ) 1000.00 1 4.65201e+18 testcase 408f4000 => (raw sp)0 ) # but is still present when run outside of valgrind. 11:39:14 0 p8 ppc64le willschm@pike:~/valgrind_builds/valgrind/none/tests/ppc64> ./test_fcfids 0.00 0 0 testcase => (raw sp)0 ) 1000.00 1 4.65201e+18 testcase 408f4000 => (raw sp) 5e811e80 ) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 367480] Crash inside Baloo::PostingCodec::decode
https://bugs.kde.org/show_bug.cgi?id=367480 --- Comment #127 from Tim Mason --- Created attachment 117370 --> https://bugs.kde.org/attachment.cgi?id=117370=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403045] New: KDev-Python crashes when parsing Python 3.6 @dataclass definition with field()
https://bugs.kde.org/show_bug.cgi?id=403045 Bug ID: 403045 Summary: KDev-Python crashes when parsing Python 3.6 @dataclass definition with field() Product: kdevelop Version: 5.2.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ma...@laitl.cz Target Milestone: --- Application: kdevelop (5.2.4) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.14.78-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: KDevelop started to crash as soon as I typed following code (the last line): @dataclass class RecordData: imagery_files: int = 0 record_files: int = 0 per_type_sqkm: dict = field(default_factory=lambda: defaultdict(float)) The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7f8eea4880 (LWP 11395))] Thread 19 (Thread 0x7f7f15ffb700 (LWP 11526)): #0 0x7f7f8b5a1ab8 in __GI___nanosleep (requested_time=requested_time@entry=0x7f7f15ff9c10, remaining=remaining@entry=0x7f7f15ff9c10) at ../sysdeps/unix/sysv/linux/nanosleep.c:28 #1 0x7f7f8befd55d in qt_nanosleep (amount=...) at kernel/qelapsedtimer_unix.cpp:195 #2 0x7f7f8bd14d60 in QThread::usleep (usecs=usecs@entry=500) at thread/qthread_unix.cpp:542 #3 0x7f7f8972cba8 in KDevelop::DUChainLock::lockForWrite (this=0x7f7f89ec8c60 , timeout=0) at /var/tmp/portage/dev-util/kdevelop-5.2.4/work/kdevelop-5.2.4/kdevplatform/language/duchain/duchainlock.cpp:152 #4 0x7f7f8972cdbc in KDevelop::DUChainWriteLocker::lock (this=0x7f7f15ff9d80) at /var/tmp/portage/dev-util/kdevelop-5.2.4/work/kdevelop-5.2.4/kdevplatform/language/duchain/duchainlock.cpp:246 #5 0x7f7f2b95ac57 in Python::DeclarationBuilder::createModuleImportDeclaration (this=this@entry=0x7f7f15ffa780, moduleName=..., declarationName=..., declarationIdentifier=declarationIdentifier@entry=0x7f7f0002f3e0, problemEncountered=..., rangeNode=rangeNode@entry=0x0) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:683 #6 0x7f7f2b95bf5f in Python::DeclarationBuilder::visitImportFrom (this=0x7f7f15ffa780, node=0x7f7f9e90) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:451 #7 0x7f7f2b956938 in Python::DeclarationBuilder::visitNode (this=0x7f7f15ffa780, node=0x7f7f9e90) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:1844 #8 0x7f7f48fc6b7c in Python::AstVisitor::visitNodeList (l=..., this=0x7f7f15ffa968) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/parser/astvisitor.h:50 #9 Python::AstDefaultVisitor::visitCode (this=this@entry=0x7f7f15ffa968, node=node@entry=0x7f7f0002a400) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/parser/astdefaultvisitor.cpp:91 #10 0x7f7f2b952280 in Python::ContextBuilder::visitCode (this=this@entry=0x7f7f15ffa780, node=node@entry=0x7f7f0002a400) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/contextbuilder.cpp:318 #11 0x7f7f2b95749a in Python::DeclarationBuilder::visitCode (this=0x7f7f15ffa780, node=0x7f7f0002a400) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:345 #12 0x7f7f2b956938 in Python::DeclarationBuilder::visitNode (this=0x7f7f15ffa780, node=0x7f7f0002a400) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/declarationbuilder.cpp:1844 #13 0x7f7f2b967835 in KDevelop::AbstractContextBuilder::supportBuild (context=0x7f7f00065520, node=0x7f7f0002a400, this=0x7f7f15ffa780) at /usr/include/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:131 #14 KDevelop::AbstractTypeBuilder::supportBuild (this=0x7f7f15ffa780, node=0x7f7f0002a400, context=) at /usr/include/kdevplatform/language/duchain/builders/abstracttypebuilder.h:84 #15 0x7f7f2b94dfdb in KDevelop::AbstractContextBuilder::build (updateContext=..., node=0x7f7f0002a400, url=..., this=0x7f7f15ffa780) at /usr/include/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:111 #16 Python::ContextBuilder::build (this=this@entry=0x7f7f15ffa780, url=..., node=node@entry=0x7f7f0002a400, updateContext=...) at /var/tmp/portage/dev-util/kdevelop-python-5.2.4/work/kdev-python-5.2.4/duchain/contextbuilder.cpp:75 #17 0x7f7f2b95708b in Python::DeclarationBuilder::build (this=this@entry=0x7f7f15ffa780, url=..., node=0x7f7f0002a400, updateContext=...) at
[Discover] [Bug 403044] New: Discover crash at system startup
https://bugs.kde.org/show_bug.cgi?id=403044 Bug ID: 403044 Summary: Discover crash at system startup Product: Discover Version: 5.14.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: robert.sku...@gmail.com Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.2 Frameworks Version: 5.53.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: Discover crashed at system startup (after login of course). System without connection to the internet. The crash does not seem to be reproducible. -- Backtrace: Application: Odkrywca (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3502c36200 (LWP 3078))] Thread 10 (Thread 0x7f34b2f8f700 (LWP 3769)): #0 0x7f34feade934 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f34feadd189 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f34feadf7a5 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f34f870df51 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f34f870e4e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f34f870e64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f34feadf04b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f34fea8330a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f34fe8aebba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f34fe8b9adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f34fa8aa6db in start_thread (arg=0x7f34b2f8f700) at pthread_create.c:463 #11 0x7f34fe1b188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f34c19de700 (LWP 3479)): #0 0x7f34fe1a00b4 in __GI___libc_read (fd=31, buf=0x7f34c19ddb90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f34f8752cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f34f870e027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f34f870e4e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f34f870e64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f34feadf04b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f34fea8330a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f34fe8aebba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f34fe8b9adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f34fa8aa6db in start_thread (arg=0x7f34c19de700) at pthread_create.c:463 #10 0x7f34fe1b188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f34c37fe700 (LWP 3212)): #0 0x7f34fe1a00b4 in __GI___libc_read (fd=18, buf=0x7f34c37fdcd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f34f8752cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f34f870e027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f34f870e4e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f34f870e8d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f34cd7cd026 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f34f8736105 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f34fa8aa6db in start_thread (arg=0x7f34c37fe700) at pthread_create.c:463 #8 0x7f34fe1b188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f34c3fff700 (LWP 3211)): #0 0x7f34fe1a00b4 in __GI___libc_read (fd=16, buf=0x7f34c3ffece0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f34f8752cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f34f870e027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f34f870e4e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f34f870e64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f34f870e691 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f34f8736105 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f34fa8aa6db in start_thread (arg=0x7f34c3fff700) at pthread_create.c:463 #8 0x7f34fe1b188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f34c9972700 (LWP
[kwin] [Bug 403038] KWin crashes (occasionally) when running script to minimize current open window
https://bugs.kde.org/show_bug.cgi?id=403038 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402787] Baloo crashed
https://bugs.kde.org/show_bug.cgi?id=402787 Reinhard Auner changed: What|Removed |Added CC||reinhardau...@gmx.at -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 402787] Baloo crashed
https://bugs.kde.org/show_bug.cgi?id=402787 --- Comment #1 from Reinhard Auner --- Created attachment 117369 --> https://bugs.kde.org/attachment.cgi?id=117369=edit New crash information added by DrKonqi baloo_file (5.45.0) using Qt 5.9.4 - What I was doing when the application crashed: I had open Google Chrome and Amarok, nothing else. -- Backtrace (Reduced): #7 0x7fcce704da93 in memcpy (__len=2067, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7fccdcaf1997, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42 #9 0x7fcce703ef64 in Baloo::PostingDB::get (this=this@entry=0x7fccdcaf1a80, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100 #10 0x7fcce704b180 in Baloo::WriteTransaction::commit (this=0x7f8cd0031b80) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259 #11 0x7fcce70444c2 in Baloo::Transaction::commit (this=this@entry=0x7fccdcaf1b90) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #21 from roger herz-fischler --- Created attachment 117368 --> https://bugs.kde.org/attachment.cgi?id=117368=edit an attempt to move a directory up -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #20 from roger herz-fischler --- Created attachment 117367 --> https://bugs.kde.org/attachment.cgi?id=117367=edit christoph feck comment I was unable to locate -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #19 from roger herz-fischler --- Created attachment 117366 --> https://bugs.kde.org/attachment.cgi?id=117366=edit dolphin handbook: configuration -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #18 from roger herz-fischler --- Created attachment 117365 --> https://bugs.kde.org/attachment.cgi?id=117365=edit configuration search 03 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #17 from roger herz-fischler --- Created attachment 117364 --> https://bugs.kde.org/attachment.cgi?id=117364=edit configuration search 02 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #16 from roger herz-fischler --- Created attachment 117363 --> https://bugs.kde.org/attachment.cgi?id=117363=edit configuration file search 01 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #15 from roger herz-fischler --- Created attachment 117362 --> https://bugs.kde.org/attachment.cgi?id=117362=edit parker reed comment re work around I had already tried to find the configuration file, but as the snapshots show I can not find it -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #14 from roger herz-fischler --- Created attachment 117361 --> https://bugs.kde.org/attachment.cgi?id=117361=edit configuration file for Dolphin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399430] Dolphin: Places: Regression: Move items up/down not working properly
https://bugs.kde.org/show_bug.cgi?id=399430 --- Comment #13 from roger herz-fischler --- Created attachment 117360 --> https://bugs.kde.org/attachment.cgi?id=117360=edit configuration file for Dolphin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399580] Kwin Aborts after disabling Laptop monitor
https://bugs.kde.org/show_bug.cgi?id=399580 --- Comment #9 from Michael D --- I have the same issue on plasma 5.14.4, so doesn't seem to be the same as bug 399564 if that was fixed in 5.14.1. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 403043] New: Dolphin configuration menu button labels are not entirely visible
https://bugs.kde.org/show_bug.cgi?id=403043 Bug ID: 403043 Summary: Dolphin configuration menu button labels are not entirely visible Product: dolphin Version: 18.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: alt.su-7oon2...@yopmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 117359 --> https://bugs.kde.org/attachment.cgi?id=117359=edit button labels not fully visible SUMMARY Some Dolphin configuration menu button labels are not entirely visible STEPS TO REPRODUCE 1. Open Dolphin 2. Click the free space indicator progress bar (bottom right, next to the numeric free space indicator) 3. Click Configure (bottom of the context menu) OBSERVED RESULT Some button labels are not fully visible. See the attached image Other info: I'm using 120 as the font DPI, and I haven't touched other scaling settings -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 401962] Kontact crash on certain emails
https://bugs.kde.org/show_bug.cgi?id=401962 Volker Krause changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Volker Krause --- Thanks for the detailed report! I can confirm the problem with 18.08 (Kontact 5.9), the problem is a nullptr dereference of the "ref" argument in the following stack trace line: #6 KItinerary::ExtractorOutputDevice::drawImage (this=0x56214836c610, state=0x562141dd7490, ref=0x0, str=0x56214852a6c0, width=134, height=23, colorMap=0x7ffe93a2f3c0, interpolate=false, maskColors=0x0, inlineImg=true) at ./src/pdfdocument.cpp:175 This has been fixed in 18.12 and master already, I can't reproduce the issue there anymore. Until you get a chance to upgrade to Kontact 5.10 a possible workaround is to remove plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so while Kontact is not running (exact location differs depending on the distro, usually somewhere below /usr/lib*), unless you absolutely rely on KDE Itinerary integration. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402841] Animation curve opacity doesn't display correctly during playback and sometimes during timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=402841 joup...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/aed191675e826f37d1173af4 ||9d22b212094c434a Status|REPORTED|RESOLVED --- Comment #7 from joup...@gmail.com --- Git commit aed191675e826f37d1173af49d22b212094c434a by Jouni Pentikäinen. Committed on 09/01/2019 at 16:12. Pushed by jounip into branch 'master'. Always update UI time when changing displayed frame Before this change, playback for cached vs. uncached frames behaved slightly differently, causing some frames to never be displayed when scrubbing. This also fixes missing UI updates for layer opacity slider when the property is animated. Related: bug 401630 M +3-3libs/ui/canvas/kis_animation_player.cpp https://commits.kde.org/krita/aed191675e826f37d1173af49d22b212094c434a -- You are receiving this mail because: You are watching all bug changes.
