[plasmashell] [Bug 478831] New: Plasmashell runs out of filedescriptors when emacs visits lotts of files
https://bugs.kde.org/show_bug.cgi?id=478831 Bug ID: 478831 Summary: Plasmashell runs out of filedescriptors when emacs visits lotts of files Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: goe...@uddeborg.se Target Milestone: 1.0 Created attachment 164340 --> https://bugs.kde.org/attachment.cgi?id=164340=edit Strace from plasmashell started shortly before the problem SUMMARY When I run an elisp program in my emacs, it very often results in the desktop panel disappearing and the background goes black. It lasts for a couple of seconds and then the panel and background reappears. The emacs program finishes successfully and does not seem to be affected. In the journal there are those messages from plasmashell. dec 21 09:25:42 mimmi plasmashell[425833]: error marshalling arguments for get_icon: dup failed: För många öppna filer dec 21 09:25:42 mimmi plasmashell[425833]: Error marshalling request: För många öppna filer dec 21 09:25:42 mimmi plasmashell[425833]: The Wayland connection experienced a fatal error: För många öppna filer dec 21 09:25:42 mimmi systemd[416625]: plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE "För många öppna filer" is Swedish for "Too many open files" STEPS TO REPRODUCE Running my emacs program as described above, but it somehow is dependent on my environment. I've not been able to create an independent reproducer. OBSERVED RESULT Plasmashell exits with a failure. Systemd then starts a new instance, so the desktop recovers. EXPECTED RESULT I don't understand why this affects plasmashell at all. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.11 Fedora 39 ADDITIONAL INFORMATION This has happened for a while, it did not appear in any specific version. The emacs program does a "grep" over files in my home directory and then emacs visits the file positions listed by the "grep" command. The command typically finds entries in up to 50 files, and the total number of hits could be in the range of hundreds. The risk of triggering the problem seems to increase with more matches, but it is hard to say exactly. As mentioned, I have tried to reproduce with a set of test files in a simple environment, but been unable to trigger it. I started debugging by attatching an "strace" to plasmashell before running my emacs function, and have a trace from where the problem is triggered. I note that plasmashell is opening /sys/devices/system/cpu/online and creates pipes over and over again, until it runs out of file descriptors. I attach the trace hoping it might be of some help. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 430157] KDE .desktop parser complains about files that have Type= "Application" but no Exec line, although this situation is normal.
https://bugs.kde.org/show_bug.cgi?id=430157 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437406] Cannot drag-and-drop between Wayland and Xwayland apps
https://bugs.kde.org/show_bug.cgi?id=437406 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436246] Mouse selection clipboard (PRIMARY) works on Wayland, but klipper wont capture it
https://bugs.kde.org/show_bug.cgi?id=436246 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 143227] Konsole doesn't seem to support xterm's style titeInhibit option
https://bugs.kde.org/show_bug.cgi?id=143227 --- Comment #4 from Göran Uddeborg --- To clarify, I can't find any "Sessions" tab in the settings. Using "linux" as "TERM" still works, but with it's drawbacks. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 143227] Konsole doesn't seem to support xterm's style titeInhibit option
https://bugs.kde.org/show_bug.cgi?id=143227 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se --- Comment #3 from Göran Uddeborg --- I'm still missing this feature in Konsole 20.04.1. Unfortunately, the workaround from comment 1 does not seem to be available any more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433576] Compose Key does not work since Plasma 5.21 on Wayland
https://bugs.kde.org/show_bug.cgi?id=433576 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417939] Context menu disappears when tooltip disappears
https://bugs.kde.org/show_bug.cgi?id=417939 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404335] Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session
https://bugs.kde.org/show_bug.cgi?id=404335 --- Comment #30 from Göran Uddeborg --- Yes, starting my (plasma) session from GDM everything seems to work properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404335] Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session
https://bugs.kde.org/show_bug.cgi?id=404335 --- Comment #28 from Göran Uddeborg --- Created attachment 134407 --> https://bugs.kde.org/attachment.cgi?id=134407=edit Beginning of wayland-errors The symptoms of this issue are the following, right? - The desktop background is black. - There is no context menu on the background. - The panel doesn't start. - Applications started via autostart files DO get started. If so; I see this issue too, but with Intel graphics. (More exactly, a Lenovo T460.) This is on Fedora 33. It didn't appear when I initially upgraded to 33, but when I recently upgraded everything it started. I tried the suggestion from comment #24, but it didn't make any difference. I also added a ps command, and redirected standard out to standard error so it would get caught in the wayland-errors file, and attach the beginning of that file here. (I don't know where standard out shows up, if anywhere, otherwise.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404335] Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session
https://bugs.kde.org/show_bug.cgi?id=404335 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411729] Greek accents and dead keys do not work in Debian Stable
https://bugs.kde.org/show_bug.cgi?id=411729 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 423119] dcopserver doesn't launch with XDG_RUNTIME_DIR set
https://bugs.kde.org/show_bug.cgi?id=423119 --- Comment #2 from Göran Uddeborg --- Sorry! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 423119] New: dcopserver doesn't launch with XDG_RUNTIME_DIR set
https://bugs.kde.org/show_bug.cgi?id=423119 Bug ID: 423119 Summary: dcopserver doesn't launch with XDG_RUNTIME_DIR set Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: goe...@uddeborg.se Target Milestone: --- SUMMARY After upgrading my Fedora system, ksensors stopped working. Some investigation done in a Fedora bug (https://bugzilla.redhat.com/show_bug.cgi?id=1768193) figured out the underlying reason is that dcopserver doesn't start as long as XDG_RUNTIME_DIR, which it is by default. Since this appears to me to be an upstreams bug, I'm reporting it here. STEPS TO REPRODUCE 1. ksensors OBSERVED RESULT ICE Connection rejected! DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed ICE Connection rejected! DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed DCOPServer self-test failed. kdeinit: DCOPServer could not be started, aborting. EXPECTED RESULT A ksensors icon in the status field of the panel. SOFTWARE/OS VERSIONS I'm not sure where to find "About System", but this is on a Fedora 32 system with these RPMs: ksensors-0.7.3-45.fc32.x86_64 kdelibs3-3.5.10-103.fc32.x86_64 ADDITIONAL INFORMATION Running env -u XDG_RUNTIME_DIR ksensors seems to work as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 400041] [wayland] Crashes when opening ttf file with kfontview
https://bugs.kde.org/show_bug.cgi?id=400041 --- Comment #3 from Göran Uddeborg --- FWIW, the problem is not restricted to ttf fonts. With version 5.18.5 on Fedora 32 kfontview crashes also with otf, pcb, and pcf fonts. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421723] Kfontview crashes immediately on start under Wayland
https://bugs.kde.org/show_bug.cgi?id=421723 Göran Uddeborg changed: What|Removed |Added Summary|Kfontview crashes |Kfontview crashes |immediately on start|immediately on start under ||Wayland --- Comment #1 from Göran Uddeborg --- I did some additional experimentation, and found the error does not occur if I go back to the X11 Plasma desktop. I normally use the Wayland Plasma desktop, where it happens every time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421723] New: Kfontview crashes immediately on start
https://bugs.kde.org/show_bug.cgi?id=421723 Bug ID: 421723 Summary: Kfontview crashes immediately on start Product: systemsettings Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: kcm_fontinst Assignee: plasma-b...@kde.org Reporter: goe...@uddeborg.se Target Milestone: --- Application: kfontview (5.18.5) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.6.11-300.fc32.x86_64 x86_64 Windowing system: Wayland Distribution: Fedora 32 (Workstation Edition) -- Information about the crash: When I start kfontview from the command line it crashes immediately. It crashes, regardless which font file I give as argument. The crash can be reproduced every time. -- Backtrace: Application: Teckensnittsvisning (kfontview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f49191dc580 (LWP 14441))] Thread 6 (Thread 0x7f48fd295700 (LWP 14446)): #0 0x7f491c1f8e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f49088471db in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f4908846cab in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f491c1f2432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f491cc8c9d3 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f48fda96700 (LWP 14445)): #0 0x7f491c1f8e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f49088471db in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f4908846cab in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f491c1f2432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f491cc8c9d3 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f48fe297700 (LWP 1)): #0 0x7f491c1f8e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f49088471db in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f4908846cab in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f491c1f2432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f491cc8c9d3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f48fea98700 (LWP 14443)): #0 0x7f491c1f8e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f49088471db in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f4908846cab in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f491c1f2432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f491cc8c9d3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f490af48700 (LWP 14442)): #0 0x7f491cc81b6f in poll () from /lib64/libc.so.6 #1 0x7f491b7b8aee in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7f491b7b8c23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f491d1dac23 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f491d18e21b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f491d002577 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f491c22b4da in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f491d003846 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f491c1f2432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f491cc8c9d3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f49191dc580 (LWP 14441)): [KCrash Handler] #6 0x7f490b0be761 in XRenderFindDisplay () from /lib64/libXrender.so.1 #7 0x7f490b0beaf5 in XRenderQueryExtension () from /lib64/libXrender.so.1 #8 0x7f4909cb1ec5 in _XftDisplayInfoGet.part.0 () from /lib64/libXft.so.2 #9 0x7f4909cb6a9e in XftFontInfoFill () from /lib64/libXft.so.2 #10 0x7f4909cb7360 in XftFontOpenPattern () from /lib64/libXft.so.2 #11 0x7f4909ce10e8 in KFI::CFcEngine::queryFont() () from /lib64/libkfontinstui.so.5 #12 0x7f4909ce18b8 in KFI::CFcEngine::getSizes() () from /lib64/libkfontinstui.so.5 #13 0x7f4909ce2f46 in KFI::CFcEngine::draw(QString const&, unsigned int, int, QColor const&, QColor const&, int, int, bool, QList const&, QList*) () from /lib64/libkfontinstui.so.5 #14 0x7f4909d1c963 in KFI::CFontPreview::showFont() () from /usr/lib64/qt5/plugins/kfontviewpart.so #15 0x7f4909d22468 in KFI::CFontViewPart::timeout() () from /usr/lib64/qt5/plugins/kfontviewpart.so #16 0x7f491d1c1506 in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f491d1b630f in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f491da96e76 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f491d18f8a0 in
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 397347] UdevQt: unhandled device action "bind"
https://bugs.kde.org/show_bug.cgi?id=397347 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 340245] pam-kwallet fails to send hash to kwalletd
https://bugs.kde.org/show_bug.cgi?id=340245 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 358752] strigita_torrent_analyzer causes deepgrep to crash
https://bugs.kde.org/show_bug.cgi?id=358752 Göran Uddeborg changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Göran Uddeborg --- I no longer run strigi, since Fedora stopped providing it. The tool isn't important enough to me to keep an own build. For me personally, the bug is no longer relevant; I don't know if it has been fixed in later versions. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 374657] Non-ascii home directory causes kajongg to crash during startup (again)
https://bugs.kde.org/show_bug.cgi?id=374657 --- Comment #2 from Göran Uddeborg <goe...@uddeborg.se> --- So you're migrating to Python 3. Nice. Python 3 certainly reduces the encoding issues with Python 2 significantly! Inspired by your comment, I made a try to simply run my kajongg version with Python 3, to see if the Fedora fix could be as simple as modifying the shebang line and adjusting the RPM dependencies. It wasn't quite that easy, unfortunately. The Python 3 version of Twisted, at least the Fedora packaging, doesn't provide any twisted.spread module which is apparently used. But maybe 16.08.3 just wasn't ready for Python 3. I guess it isn't worth it to debug this too much with t he old version of kajongg. Thanks for a quick fix! -- You are receiving this mail because: You are watching all bug changes.
[kajongg] [Bug 374657] New: Non-ascii home directory causes kajongg to crash during startup (again)
https://bugs.kde.org/show_bug.cgi?id=374657
Bug ID: 374657
Summary: Non-ascii home directory causes kajongg to crash
during startup (again)
Product: kajongg
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: wolfg...@rohdewald.de
Reporter: goe...@uddeborg.se
CC: kde-games-b...@kde.org
Target Milestone: ---
It seems bug 322606 has returned.
When I try to start kajongg, it ends immediately with a Python traceback,
complaining about a UnicodeEncodeError. If I change the HOME environment
variable to some pure ASCII path, it works. To reproduce see below. The first
invocation of kajongg comes up with a window, while the second one fails as can
be seen.
This is on a Fedora 25 system with kajongg-16.08.3-1.fc25.noarch.
[göran@mimmi ~]$ mkdir /tmp/göran /tmp/goeran
[göran@mimmi ~]$ HOME=/tmp/goeran kajongg
[göran@mimmi ~]$ HOME=/tmp/göran kajongg
Traceback (most recent call last):
File "/usr/bin/kajongg", line 172, in
parseOptions()
File "/usr/bin/kajongg", line 147, in parseOptions
if not initDb():
File "/usr/share/kde4/apps/kajongg/query.py", line 283, in initDb
PrepareDB(DBHandle.dbPath()) # create or upgrade
File "/usr/share/kde4/apps/kajongg/query.py", line 161, in dbPath
return Options.dbPath if Options.dbPath else appdataDir() + name
File "/usr/share/kde4/apps/kajongg/kde.py", line 94, in appdataDir
unicode(KGlobal.dirs().locateLocal("appdata", ""))) + '/'
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 6: ordinal
not in range(128)
--
You are receiving this mail because:
You are watching all bug changes.
[kde] [Bug 358752] New: strigita_torrent_analyzer causes deepgrep to crash
https://bugs.kde.org/show_bug.cgi?id=358752 Bug ID: 358752 Summary: strigita_torrent_analyzer causes deepgrep to crash Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: goe...@uddeborg.se After installing kdenetwork-strigi-analyzers, the command "deepgrep" crashes immediately on invocation. Reproducible: Always Steps to Reproduce: 1. Install strigi and kdenetwork-strigi-analyzers 2. deepgrep xyz . Actual Results: Segmentation violation crash (with core dump if enabled). Expected Results: No crash. I couldn't find the appropriate version in the version field above, but these are the RPMs I have installed: kdenetwork-strigi-analyzers-15.04.2-4.fc23.x86_64 strigi-0.7.8-11.fc23.x86_64 I initially filed a Fedora bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1302879) but got the advice to do this upstreams report. See below for the backtrace of the crash. I tried to understand what is wrong, but ended up in a "how could this possibly have worked" situation instead. In StreamAnalyzerPrivate::analyze (in the strigi code) a loop is executed as long as "input" is 0 or one other case. So here clearly input==0 is expected. Then connectInputStream(input) is called on the iterated object, in this case a TorrentThroughAnalyzer. In TorrentThroughAnalyzer.connectInputStream() a ByteStream object is created from the (possibly 0) "input". ByteStream initializes its "m_input" member directly from the argument. Then the prefix ++ operator is called on that new stream. ByteStream::operator++() calls refillBuffer if the "m_buffer" element is zero, which it will be since it was just initialized to zero on stream creation. And in ByteStream::refillBuffer() the member function read() of "m_input" is called. As "m_input" is still zero, I can't see how this ever could have worked. C++ can do many strange things under the hood, and I've been fooled before. But surely, a call of a virtual member function requires a valid object pointer, doesn't it? #0 0x7f507af7521a in ByteStream::refillBuffer (this=0x7ffe980a4470) at ../../torrent/bytestream.cpp:63 #1 0x7f507af7533d in ByteStream::operator++ (this=this@entry=0x7ffe980a4470) at ../../torrent/bytestream.cpp:54 #2 0x7f507af784e7 in TorrentThroughAnalyzer::connectInputStream (this=0x5587521e03e0, input=0x0) at ../../torrent/torrent_analyzer.cpp:74 #3 0x7f507ce28732 in Strigi::StreamAnalyzerPrivate::analyze (this=0x558752225af0, idx=..., input=input@entry=0x0) at /usr/src/debug/strigi-0.7.8/libstreamanalyzer/lib/streamanalyzer.cpp:392 #4 0x7f507ce290d8 in Strigi::StreamAnalyzer::analyze (this=, idx=..., input=input@entry=0x0) at /usr/src/debug/strigi-0.7.8/libstreamanalyzer/lib/streamanalyzer.cpp:359 #5 0x7f507ce03228 in Strigi::AnalysisResult::index (this=this@entry=0x7ffe980a4600, file=file@entry=0x0) at /usr/src/debug/strigi-0.7.8/libstreamanalyzer/lib/analysisresult.cpp:235 #6 0x7f507ce0929a in Strigi::DirAnalyzer::Private::analyzeFile (this=this@entry=0x5587521ddef0, path=..., mtime=1449744713, realfile=) at /usr/src/debug/strigi-0.7.8/libstreamanalyzer/lib/diranalyzer.cpp:111 #7 0x7f507ce09f37 in Strigi::DirAnalyzer::Private::analyzeDir (this=0x5587521ddef0, dir=..., nthreads=8, c=, lastToSkip=...) at /usr/src/debug/strigi-0.7.8/libstreamanalyzer/lib/diranalyzer.cpp:254 #8 0x5587502f0a69 in main (argc=, argv=) at /usr/src/debug/strigi-0.7.8/strigiutils/bin/deepfind/deepgrep.cpp:82 -- You are receiving this mail because: You are watching all bug changes.
