[plasmashell] [Bug 426886] config/panel is lost after wake-up with 2 monitors
https://bugs.kde.org/show_bug.cgi?id=426886 Matthew Dawson changed: What|Removed |Added Target Milestone|--- |1.0 Product|frameworks-kconfig |plasmashell Assignee|matt...@mjdsystems.ca |k...@davidedmundson.co.uk Version|unspecified |5.18.5 CC||plasma-b...@kde.org Component|general |general --- Comment #2 from Matthew Dawson --- Re-assigning to plasmashell, as Plasma is the one responding to the change in monitor configuration. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 428536] org.kde.pim.maildispatcher: Item does not have the required attribute Address.
https://bugs.kde.org/show_bug.cgi?id=428536 Matthew Dawson changed: What|Removed |Added CC||matt...@mjdsystems.ca -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 291834] KGet crash when several dialog boxes are being dealt with.
https://bugs.kde.org/show_bug.cgi?id=291834 Matthew Dawson changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Matthew Dawson --- (In reply to Justin Zobel from comment #1) > Thanks for the report Matthew, are you able to please test and confirm if > this issue is still occurring or if this bug report can be marked as > resolved. I've set the bug status to "needsinfo" pending your response, > please change back to "reported" or "resolved" when you respond, thanks. Hi Justin, I haven't used KGet for several years at this point, so I don't remember exactly what happened in this crash. For now I'll just mark this as resolved. If I stumble across the bug again at some point I'll update this bug appropriately. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 433610] KDE PIM memory/CPU leak
https://bugs.kde.org/show_bug.cgi?id=433610 Matthew Dawson changed: What|Removed |Added CC||matt...@mjdsystems.ca --- Comment #3 from Matthew Dawson --- This issue is likely caused by an downstream issue in Gentoo's qtwebengine package (see here: https://bugs.gentoo.org/773919 ). Can you try taking the steps outlined in this comment: https://bugs.gentoo.org/773919#c21 and see if that resolves your problem? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 409886] K3b burning tools not burn any CD / DVD. It shown blank after burn
https://bugs.kde.org/show_bug.cgi?id=409886 Matthew Dawson changed: What|Removed |Added Assignee|matt...@mjdsystems.ca |k...@kde.org Component|general |Burning/Hardware Product|frameworks-kconfig |k3b CC||mich...@jabster.pl, ||tr...@kde.org --- Comment #1 from Matthew Dawson --- Re-assigning to the K3b product so this issue can be investigated. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 387820] KConfigGui misbehave at runtime when link time optimizations are enabled
https://bugs.kde.org/show_bug.cgi?id=387820 --- Comment #1 from Matthew Dawson --- Sorry if I misunderstand your proposed solution, but it sounds like KConfigCore will then need to make calls into KConfigGui, would require it to be linked together and defeat the purpose of having them separate. I'm not sure how we can make the necessary call across libraries without having the two of them be linked together. Maybe some trickery with the dynamic linker? But that seems error prone, and unlikely to work with LTO. I definitely would like to see this fixed in KConfig though, and making the library more robust against compilers changing is good as well. But I would like to keep KConfigCore from linking against QtGui. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 387820] KConfigGui misbehave at runtime when link time optimizations are enabled
https://bugs.kde.org/show_bug.cgi?id=387820 --- Comment #3 from Matthew Dawson --- (In reply to Emmanuel Lepage Vallée from comment #2) > kconfigskeleton.cpp is part of KConfigGui, so if the private .h is part of > KConfigGui too, then there's no issue. Nothing from KConfigCore is involved. Sorry, you are correct about that. The name of the class confused me, as I wasn't able to double check that when I replied. As such, I'm generally ok with this plan. My only concern is ensuring that the write happens in a way ensuring that the variables are correctly initialized (through correct acquire/release semantics), but that can be handled in review! If you (or someone else) can write a patch to fix this issue, I'd be happy to review it. Thanks for taking a look into this and LTO! -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 375392] KConfig 5.30 do not compile with Macports under MacOS
https://bugs.kde.org/show_bug.cgi?id=375392 Matthew Dawson changed: What|Removed |Added Product|frameworks-kconfig |extra-cmake-modules Component|general |general Assignee|matt...@mjdsystems.ca |alex.me...@kde.org CC||ecm-bugs-n...@kde.org, ||matt...@mjdsystems.ca --- Comment #6 from Matthew Dawson --- Re-assigning to ECM as it appears to be caused by a change there. I suspect https://phabricator.kde.org/D4363 may have caused it, but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 402673] New: Akonadi server incompatible with latest Mysql defaults (NO_ZERO_DATE enabled by default) when using database created using older akonadi versions
https://bugs.kde.org/show_bug.cgi?id=402673 Bug ID: 402673 Summary: Akonadi server incompatible with latest Mysql defaults (NO_ZERO_DATE enabled by default) when using database created using older akonadi versions Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: matt...@mjdsystems.ca Target Milestone: --- After updating my system to the latest packages on Gentoo, akonadi (upgrading from 18.08.2 to 18.12.0) no longer starts. Enabling verbose output gives the following text: org.kde.pim.akonadiserver: Updating indexes org.kde.pim.akonadiserver: "CREATE INDEX PimItemTable_mimeTypeIndex ON PimItemTable (mimeTypeId)" org.kde.pim.akonadiserver: Updating index failed: Sql error: Invalid default value for 'atime' QMYSQL: Unable to execute query Query: CREATE INDEX PimItemTable_mimeTypeIndex ON PimItemTable (mimeTypeId) It appears mysql 5.7 by defaults enables NO_ZERO_DATE. When attempting to update the database, mysql refuses to touch the affected table as the table definition is invalid. I assume I didn't have issues on the older Akonadi versions as I only got upgraded to 5.7 in Novemeber, and there were no interesting updates at that time to the PimItemTable. As the default wasn't used during insert, Akonadi was able to operate normally. It seems to the best option is to add a migration to change all TIMESTAMP columns to have an appropriate default, or disable NO_ZERO_DATE in the mysql configuration explicitly. I'd be happy to create/contribute a patch for either option (I have a backup of my database to test against!). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385468] "Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped."
https://bugs.kde.org/show_bug.cgi?id=385468 --- Comment #4 from Matthew Dawson --- The original reason this was added was that KDE4 update scripts would get run by KF5, creating a configuration file. Then the KDE4 migration would not run, resulting in users losing their settings. This was put in at the time to stop that from occurring. Ideally, kconf_update would not create an empty configuration file for a migration just to note the migration had been run. However, there are some side effects to that change which make it more complicated to implement, and thus has not yet happened. Without fixing kconf_update, I don't want to back out the change as it still has a good reason. I also like that all the update files now have an enforced version header, which will make it easy to update the format in the future. And most configuration file update scripts should now have the header if required, so there will likely be more pain to revert it at this time. However, you do raise the good point that this requirement is not well communicated. That should definitely be fixed. Is there any particular place you would have expected this information to be present? Also, if the configuration update script is for KDE4 configuration files, you can skip putting a Version=5 header at the top. Instead, you can have the fully updated file migrated to the new configuration file location and start with a fresh update script for KF5. Or continue adding to the file. Whatever works best for okular. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 385468] "Missing \"Version=5\", file '/usr/share/kconf_update/okular.upd' will be skipped."
https://bugs.kde.org/show_bug.cgi?id=385468 --- Comment #6 from Matthew Dawson --- (In reply to Albert Astals Cid from comment #5) > (In reply to Matthew Dawson from comment #4) > > Also, if the configuration update script is for KDE4 configuration files, > > you can skip putting a Version=5 header at the top. Instead, you can have > > the fully updated file migrated to the new configuration file location and > > start with a fresh update script for KF5. Or continue adding to the file. > > Whatever works best for okular. > > For my application there's no such thing as "KDE4" configuration files, they > are just configuration files, and ideally one should be able to go from an > old version (based on kdelibs4, irrelevant) where the okular.upd had not > been run to the new version (based on KF5, irrelevant) and get okular.upd > run and then the config be migrated to the new location. > > As I understand you're saying that this is impossible and thus i basically > should just remove the .upd file? The situation may have changed since this was brought up. At the time, you'd use the Kdelibs4Migration class ( https://api.kde.org/frameworks/kcoreaddons/html/classKdelibs4Migration.html ) to move the file to the new KF5 location (using the XDG directory instead of the .kde directory). The upd file wasn't used for that purpose. If using the upd file is now the recommended way to do the migration, then you can ignore my suggestion. I'm not sure though the upd file is flexible to handle custom kde prefixes that Kdelibs4Migration does. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 365054] KRDC allways closed after typing the wrong server password
https://bugs.kde.org/show_bug.cgi?id=365054 Matthew Dawson changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/krdc ||/a6dca605fae01440cb510d65fd ||1896ba77646722 --- Comment #5 from Matthew Dawson --- Git commit a6dca605fae01440cb510d65fd1896ba77646722 by Matthew Dawson. Committed on 01/08/2016 at 17:24. Pushed by mdawson into branch 'Applications/16.08'. Avoid crash when handling RDP error and xfreerdp quits. If xfreerdp sent a failure message then quit, the RDP plugin would first show a message box with a relevant message. During that time, the inner event loop would handle the xfreerdp process quitting, which would signal krdc to cleanup the RDP plugin's resources. When the message box event loop completed, the RdpView would have been destroyed, causing a crash. Now the RdpView signals that the view is quitting as soon as the message box is shown, and avoids trying to quit twice if another part signals a quit. Once the message box is dismissed, the process continues as normal. This adds the necessary mechanisms to handle this, as well as moving the message box display code to connectionError, to avoid some duplication. REVIEW: 128569 M +24 -20 rdp/rdpview.cpp M +10 -1rdp/rdpview.h http://commits.kde.org/krdc/a6dca605fae01440cb510d65fd1896ba77646722 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 370007] Quickbooks Support Phone Number
https://bugs.kde.org/show_bug.cgi?id=370007 Matthew Dawson changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Matthew Dawson --- Spam -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner
https://bugs.kde.org/show_bug.cgi?id=364342 Matthew Dawson changed: What|Removed |Added CC||matt...@mjdsystems.ca -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 367658] newer "fonts"-directory is not found by general configurations
https://bugs.kde.org/show_bug.cgi?id=367658 Matthew Dawson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM Product|frameworks-kconfig |unknown Assignee|matt...@mjdsystems.ca |unassigned-b...@kde.org Component|general |general --- Comment #1 from Matthew Dawson --- I believe this is an issue from Qt, as Qt reports the location location as ~/.fonts, and not $XDG_DATA_HOME/fonts. Can you please report the bug to them, and add a comment here with the url of the Qt bug? If they report back a change is required in KDE, please reopen this bug. Note that KConfig isn't the right place for this, as KConfig only helps an application manage its configuration files, and doesn't actually supply fonts. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368139] Krunner crash because QtWebEngine::initialize failed
https://bugs.kde.org/show_bug.cgi?id=368139 Matthew Dawson changed: What|Removed |Added Resolution|--- |DUPLICATE CC||matt...@mjdsystems.ca Status|UNCONFIRMED |RESOLVED --- Comment #2 from Matthew Dawson --- *** This bug has been marked as a duplicate of bug 364342 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner
https://bugs.kde.org/show_bug.cgi?id=364342 Matthew Dawson changed: What|Removed |Added CC||bernhard+...@scheirle.de --- Comment #13 from Matthew Dawson --- *** Bug 368139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 360146] New: Konsole crash while searching history
https://bugs.kde.org/show_bug.cgi?id=360146 Bug ID: 360146 Summary: Konsole crash while searching history Product: konsole Version: 15.12.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: matt...@mjdsystems.ca Application: konsole (15.12.2) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.3.3-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: While searching through my history for "..", konsole crashed. Just before I had tried searching for ".." and it had landed me in a different part of my history I didn't care about, so I scrolled back and tried again. That time konsole crashed. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f93f860a880 (LWP 9630))] Thread 2 (Thread 0x7f93e7572700 (LWP 9633)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f93efa1152b in cnd_wait (mtx=0xcf6c80, cond=0xcf6ca8) at /usr/src/debug/media-libs/mesa-11.1.2/mesa-11.1.2/include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0xcf6c80) at /usr/src/debug/media-libs/mesa-11.1.2/mesa-11.1.2/src/gallium/auxiliary/os/os_thread.h:259 #3 radeon_drm_cs_emit_ioctl (param=param@entry=0xcf6930) at /usr/src/debug/media-libs/mesa-11.1.2/mesa-11.1.2/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:653 #4 0x7f93efa110f8 in impl_thrd_routine (p=) at /usr/src/debug/media-libs/mesa-11.1.2/mesa-11.1.2/include/c11/threads_posix.h:87 #5 0x7f94040a5552 in start_thread (arg=0x7f93e7572700) at pthread_create.c:333 #6 0x7f940bda796d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f93f860a880 (LWP 9630)): [KCrash Handler] #6 0x7f940b9e3b5c in Konsole::HistoryFile::get (loc=-2628, size=2628, buffer=, this=0xfa1f50) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/History.cpp:163 #7 Konsole::HistoryScrollFile::getCells (this=0xfa1f10, lineno=, colno=, count=, res=) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/History.cpp:262 #8 0x7f940ba15465 in Konsole::Screen::copyLineToStream (this=this@entry=0xbe3b30, line=line@entry=-6399987, start=, count=219, count@entry=-1, decoder=decoder@entry=0x7ffe90b74920, appendNewLine=appendNewLine@entry=true, preserveLineBreaks=true, trimTrailingSpaces=false) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/Screen.cpp:1239 #9 0x7f940ba15608 in Konsole::Screen::writeToStream (this=0xbe3b30, decoder=0x7ffe90b74920, startIndex=, endIndex=, preserveLineBreaks=true, trimTrailingSpaces=false) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/Screen.cpp:1184 #10 0x7f940ba31f2a in Konsole::SearchHistoryTask::executeOnScreenWindow (this=this@entry=0x11c1930, session=..., window=...) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/SessionController.cpp:1882 #11 0x7f940ba323f1 in Konsole::SearchHistoryTask::execute (this=0x11c1930) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/SessionController.cpp:1802 #12 0x7f940ba2fa0f in Konsole::SessionController::beginSearch (this=0x1084580, text=..., direction=1) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/SessionController.cpp:1274 #13 0x7f940875436b in QtPrivate::QSlotObjectBase::call (a=0x7ffe90b74bb0, r=0x1084580, this=) at ../../src/corelib/kernel/qobject_impl.h:124 #14 QMetaObject::activate (sender=sender@entry=0xdceb90, signalOffset=, local_signal_index=local_signal_index@entry=32766, argv=argv@entry=0xb218b0) at kernel/qobject.cpp:3698 #15 0x7f9408754e12 in QMetaObject::activate (sender=sender@entry=0xdceb90, m=m@entry=0x7f940bcb0e40 , local_signal_index=32766, local_signal_index@entry=0, argv=0xb218b0, argv@entry=0x7ffe90b74bb0) at kernel/qobject.cpp:3578 #16 0x7f940ba6d515 in Konsole::IncrementalSearchBar::searchChanged (this=this@entry=0xdceb90, _t1=...) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2_build/src/moc_IncrementalSearchBar.cpp:251 #17 0x7f940b9e8718 in Konsole::IncrementalSearchBar::notifySearchChanged (this=0xdceb90) at /usr/src/debug/kde-apps/konsole-15.12.2/konsole-15.12.2/src/IncrementalSearchBar.cpp:150 #18 0x7f940875436b in QtPrivate::QSlotObjectBase::call (a=0x7ffe90b74cc0, r=0xdceb90, this=) at ../../src/corelib/kernel/qobject_impl.h:124 #19 QMetaObject::activate (sender=sender@entry=0x1021630, signalOffset=, local_signal_index=local_signal_index@entry=32766, argv=argv@entry=0xb218b0) at kernel/qobject.cpp:3698 #20 0x7f9408754e12 in QMetaObject::activate (sender=sender@entry=0x1021630, m=m@e
[konsole] [Bug 360146] Konsole crash while searching history
https://bugs.kde.org/show_bug.cgi?id=360146 --- Comment #1 from Matthew Dawson --- Oh, I forgot to mention it crashed at: buffer[i] = _fileMap[loc + i]; with i == 0 Since loc was < 0, I assumed the crash had a clear cause. The assert to catch it a few files up was missed as I'm compiled with QT_NO_DEBUG set. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 352260] Baloo crashes when finding a new file
https://bugs.kde.org/show_bug.cgi?id=352260 --- Comment #4 from Matthew Dawson --- So, LMDB is failing with error MDB_BAD_TXN, with a message of "Transaction must abort, has a child, or is invalid". Having got an debug version of Baloo installed, it turns out this gets printed earlier: ASSERT failure in PositionDB::put: "MDB_MAP_FULL: Environment mapsize limit reached", file /var/tmp/portage/kde-frameworks/baloo-5.19.0/work/baloo-5.19.0/src/engine/positiondb.cpp, line 80 KCrash: Attempting to start /usr/bin/baloo_file from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'baloo_file' crashing... Aborted For me, I have 6.5T worth of data in over 2 million files, so I'm not surprised I broke a limit. Would a system to recover from this error and resize the database be ok? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 363826] New: Crash in KSharedDataCache in KPat
https://bugs.kde.org/show_bug.cgi?id=363826 Bug ID: 363826 Summary: Crash in KSharedDataCache in KPat Product: kpat Version: 3.6 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: matt...@mjdsystems.ca CC: kde-games-b...@kde.org Application: kpat (3.6) (Compiled from sources) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.6.0-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: I was loading a game of patience, when KPat randomly crashed. Every so often it will do this when loading a game (the type of game doesn't seem to matter). I looked at the result of the comparision in gdb and the memory appared to be present and I could read the data, so I don't know why it crashed. It did crash reading from a register, but I don't know how to recover the value in gdb after KCrash's signal handler has run. Any hints regarding that would be appreciated to help track it down. May be related to bug #361426, which also crashed around where I did, except it actually tried locking the lock. The crash can be reproduced sometimes. -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 18562:movl(%rsp), %edi [Current thread is 1 (Thread 0x7f2609331880 (LWP 28538))] Thread 6 (Thread 0x7f25f2df0700 (LWP 28543)): #0 0x7f260534342d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f25fdd4ebba in poll (__timeout=-1, __nfds=1, __fds=0x7f25f2defbf0) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x24da680, cond=cond@entry=0x24da6c0, vector=vector@entry=0x0, count=count@entry=0x0) at /usr/src/debug/x11-libs/libxcb-1.11.1/libxcb-1.11.1/src/xcb_conn.c:459 #3 0x7f25fdd51091 in xcb_wait_for_event (c=0x24da680) at /usr/src/debug/x11-libs/libxcb-1.11.1/libxcb-1.11.1/src/xcb_in.c:693 #4 0x7f25f451c289 in QXcbEventReader::run (this=0x24da080) at qxcbconnection.cpp:1313 #5 0x7f2605daca4d in QThreadPrivate::start (arg=0x24da080) at thread/qthread_unix.cpp:340 #6 0x7f2600b51652 in start_thread (arg=0x7f25f2df0700) at pthread_create.c:334 #7 0x7f260534cc8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f25f1672700 (LWP 28545)): #0 0x7f260534342d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f26003d62fd in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f25e4003020, timeout=, context=0x7f25e4000990) at /usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f25e4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3835 #3 0x7f26003d6433 in g_main_context_iteration (context=0x7f25e4000990, may_block=may_block@entry=1) at /usr/src/debug/dev-libs/glib-2.46.2-r3/glib-2.46.2/glib/gmain.c:3901 #4 0x7f2605ff1dab in QEventDispatcherGlib::processEvents (this=0x7f25e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f2605f9631b in QEventLoop::exec (this=this@entry=0x7f25f1671cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f2605da7885 in QThread::exec (this=this@entry=0x7f2602712e40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #7 0x7f2602692bf6 in QDBusConnectionManager::run (this=0x7f2602712e40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:181 #8 0x7f2605daca4d in QThreadPrivate::start (arg=0x7f2602712e40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #9 0x7f2600b51652 in start_thread (arg=0x7f25f1672700) at pthread_create.c:334 #10 0x7f260534cc8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f25d6e1a700 (LWP 28562)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f25eb99546b in cnd_wait (mtx=0x27627b0, cond=0x27627d8) at /usr/src/debug/media-libs/mesa-11.2.2/mesa-11.2.2/include/c11/threads_posix.h:159 #2 pipe_semaphore_wait (sema=0x27627b0) at /usr/src/debug/media-libs/mesa-11.2.2/mesa-11.2.2/src/gallium/auxiliary/os/os_thread.h:259 #3 radeon_drm_cs_emit_ioctl (param=param@entry=0x2762380) at /usr/src/debug/media-libs/mesa-11.2.2/mesa-11.2.2/src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:688 #4 0x7f25eb995018 in impl_thrd_routine (p=) at /usr/src/debug/media-libs/mesa-11.2.2/mesa-11.2.2/include/c11/threads_posix.h:87 #5 0x7f2
[Baloo] [Bug 352260] Baloo crashes when finding a new file
https://bugs.kde.org/show_bug.cgi?id=352260 Matthew Dawson changed: What|Removed |Added CC||matt...@mjdsystems.ca Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #2 from Matthew Dawson --- Hi Vishesh, I've got this happening reliably for me. Relevant Valgrind output (too large for a comment, I'll attach the full thing): ==30783== ==30783== Conditional jump or move depends on uninitialised value(s) ==30783==at 0x4C2E945: _intel_fast_memcpy (vg_replace_strmem.c:929) ==30783==by 0x5A28EF1: memcpy (string3.h:53) ==30783==by 0x5A28EF1: Baloo::PostingCodec::decode(QByteArray const&) (postingcodec.cpp:42) ==30783==by 0x5A0F35F: Baloo::PostingDB::get(QByteArray const&) (postingdb.cpp:100) ==30783==by 0x5A24FC2: Baloo::WriteTransaction::commit() (writetransaction.cpp:286) ==30783==by 0x5A1AC72: Baloo::Transaction::commit() (transaction.cpp:262) ==30783==by 0x422869: Baloo::MetadataMover::moveFileMetadata(QString const&, QString const&) (metadatamover.cpp:58) ==30783==by 0x619C36A: call (qobject_impl.h:124) ==30783==by 0x619C36A: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3698) ==30783==by 0x426DB5: moved (moc_kinotify.cpp:330) ==30783==by 0x426DB5: KInotify::slotEvent(int) (kinotify.cpp:421) ==30783==by 0x619C36A: call (qobject_impl.h:124) ==30783==by 0x619C36A: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3698) ==30783==by 0x6221A1B: QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (moc_qsocketnotifier.cpp:134) ==30783==by 0x61A9192: QSocketNotifier::event(QEvent*) (qsocketnotifier.cpp:260) ==30783==by 0x616B3DB: notify (qcoreapplication.cpp:1038) ==30783==by 0x616B3DB: QCoreApplication::notifyInternal(QObject*, QEvent*) (qcoreapplication.cpp:965) ==30783== ==30783== Invalid read of size 16 ==30783==at 0x4C2E900: _intel_fast_memcpy (vg_replace_strmem.c:929) ==30783==by 0x5A28EF1: memcpy (string3.h:53) ==30783==by 0x5A28EF1: Baloo::PostingCodec::decode(QByteArray const&) (postingcodec.cpp:42) ==30783==by 0x5A0F35F: Baloo::PostingDB::get(QByteArray const&) (postingdb.cpp:100) ==30783==by 0x5A24FC2: Baloo::WriteTransaction::commit() (writetransaction.cpp:286) ==30783==by 0x5A1AC72: Baloo::Transaction::commit() (transaction.cpp:262) ==30783==by 0x422869: Baloo::MetadataMover::moveFileMetadata(QString const&, QString const&) (metadatamover.cpp:58) ==30783==by 0x619C36A: call (qobject_impl.h:124) ==30783==by 0x619C36A: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3698) ==30783==by 0x426DB5: moved (moc_kinotify.cpp:330) ==30783==by 0x426DB5: KInotify::slotEvent(int) (kinotify.cpp:421) ==30783==by 0x619C36A: call (qobject_impl.h:124) ==30783==by 0x619C36A: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3698) ==30783==by 0x6221A1B: QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (moc_qsocketnotifier.cpp:134) ==30783==by 0x61A9192: QSocketNotifier::event(QEvent*) (qsocketnotifier.cpp:260) ==30783==by 0x616B3DB: notify (qcoreapplication.cpp:1038) ==30783==by 0x616B3DB: QCoreApplication::notifyInternal(QObject*, QEvent*) (qcoreapplication.cpp:965) ==30783== Address 0x4065000 is not stack'd, malloc'd or (recently) free'd ==30783== KCrash: Attempting to start /usr/bin/baloo_file from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash: Application 'baloo_file' crashing... ==30783== ==30783== HEAP SUMMARY: ==30783== in use at exit: 145,962,439 bytes in 691,847 blocks ==30783== total heap usage: 61,909,015 allocs, 61,217,168 frees, 12,624,450,230 bytes allocated ==30783== ==30783== LEAK SUMMARY: ==30783==definitely lost: 0 bytes in 0 blocks ==30783==indirectly lost: 0 bytes in 0 blocks ==30783== possibly lost: 3,337,148 bytes in 86 blocks ==30783==still reachable: 142,625,291 bytes in 691,761 blocks ==30783== suppressed: 0 bytes in 0 blocks ==30783== Rerun with --leak-check=full to see details of leaked memory ==30783== ==30783== For counts of detected and suppressed errors, rerun with: -v ==30783== Use --track-origins=yes to see where uninitialised values come from ==30783== ERROR SUMMARY: 681434 errors from 42 contexts (suppressed: 0 from 0) Killed But I think the root cause is something around LMDB. I got it to happen in gdb and poked around some. The address given back by mdb_get is invalid to start with. I tried to get GDB to break if rc != 0 (my desktop has Qt compiled without debugging, so the asserts disappear), but it didn't before it crashed again. Could mdb be returning invalid po
[Baloo] [Bug 352260] Baloo crashes when finding a new file
https://bugs.kde.org/show_bug.cgi?id=352260 --- Comment #3 from Matthew Dawson --- Created attachment 97549 --> https://bugs.kde.org/attachment.cgi?id=97549&action=edit Valgrind output -- You are receiving this mail because: You are watching all bug changes.
