[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983
--- Comment #10 from frmdstryr ---
(In reply to frmdstryr from comment #9)
> (In reply to frmdstryr from comment #8)
> > (In reply to Igor Kushnir from comment #7)
> > > I cannot reproduce the infinite loop when I add a bogus dependency to the
> > > simple meson project created from a KDevelop template
> > > (Standard=>Terminal=>Meson C++):
> > > ```
> > > + bb=dependency('missingd', version:'>=5.0')
> > > executable('kdev-meson-cpp-test-project',
> > > 'main.cpp',
> > > include_directories : incdir
> > > + , dependencies : bb
> > > ```
> > >
> > > The configuration job fails once and is not restarted:
> > > ```
> > > Run-time dependency missingd found: NO (tried pkgconfig and cmake)
> > >
> > > meson.build:15:3: ERROR: Dependency "missingd" not found, tried pkgconfig
> > > and cmake
> > >
> > > A full log can be found at
> > > /path/to/kdev-meson-cpp-test-project/build/meson-logs/meson-log.txt
> > > *** Failure: Exit code 1 ***
> > > ```
> > >
> > > Is some additional configuration of the project or KDevelop needed?
> >
> > Does the build/meson-info/meson-info.json file exist? It occurred for a
> > project (https://github.com/horizon-eda/horizon) that was already imported
> > and built but then I updated a library version that meson could not find.
>
> I also cannot reproduce with the template project, let me see what else it
> required for this to happen.
Ok, it was more complicated to reproduce:
1. Create the project using the meson template
2. Build the project
3. Add a line in meson.build to introduce an error like a non-existent library
or missing version
4. Run prune
5. Run build or configure again and the loop should start
There may be an better/easier way to fix it since it seems like a race
condition because there is a watch on create and dirty it so the job appears to
be running twice in parallel.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983
--- Comment #9 from frmdstryr ---
(In reply to frmdstryr from comment #8)
> (In reply to Igor Kushnir from comment #7)
> > I cannot reproduce the infinite loop when I add a bogus dependency to the
> > simple meson project created from a KDevelop template
> > (Standard=>Terminal=>Meson C++):
> > ```
> > + bb=dependency('missingd', version:'>=5.0')
> > executable('kdev-meson-cpp-test-project',
> > 'main.cpp',
> > include_directories : incdir
> > + , dependencies : bb
> > ```
> >
> > The configuration job fails once and is not restarted:
> > ```
> > Run-time dependency missingd found: NO (tried pkgconfig and cmake)
> >
> > meson.build:15:3: ERROR: Dependency "missingd" not found, tried pkgconfig
> > and cmake
> >
> > A full log can be found at
> > /path/to/kdev-meson-cpp-test-project/build/meson-logs/meson-log.txt
> > *** Failure: Exit code 1 ***
> > ```
> >
> > Is some additional configuration of the project or KDevelop needed?
>
> Does the build/meson-info/meson-info.json file exist? It occurred for a
> project (https://github.com/horizon-eda/horizon) that was already imported
> and built but then I updated a library version that meson could not find.
I also cannot reproduce with the template project, let me see what else it
required for this to happen.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983
--- Comment #8 from frmdstryr ---
(In reply to Igor Kushnir from comment #7)
> I cannot reproduce the infinite loop when I add a bogus dependency to the
> simple meson project created from a KDevelop template
> (Standard=>Terminal=>Meson C++):
> ```
> + bb=dependency('missingd', version:'>=5.0')
> executable('kdev-meson-cpp-test-project',
> 'main.cpp',
> include_directories : incdir
> + , dependencies : bb
> ```
>
> The configuration job fails once and is not restarted:
> ```
> Run-time dependency missingd found: NO (tried pkgconfig and cmake)
>
> meson.build:15:3: ERROR: Dependency "missingd" not found, tried pkgconfig
> and cmake
>
> A full log can be found at
> /path/to/kdev-meson-cpp-test-project/build/meson-logs/meson-log.txt
> *** Failure: Exit code 1 ***
> ```
>
> Is some additional configuration of the project or KDevelop needed?
Does the build/meson-info/meson-info.json file exist? It occurred for a
project (https://github.com/horizon-eda/horizon) that was already imported and
built but then I updated a library version that meson could not find.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 409278] Konsole sometimes stops showing input characters
https://bugs.kde.org/show_bug.cgi?id=409278 --- Comment #4 from frmdstryr --- Have not seen this lately, this can be closed. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 --- Comment #4 from frmdstryr --- (In reply to Igor Kushnir from comment #3) > (In reply to frmdstryr from comment #2) > > I pushed a branch that stops the loop to github > > https://github.com/KDE/kdevelop/compare/master...frmdstryr:kdevelop:meson-info-only-reparse-if-contents-changed > > . I had problems pushing to invent. > What problem? Did you fork the KDevelop repository? Tried pushing to an SSH > URL, e.g. g...@invent.kde.org:frmdstryr/kdevelop.git ? If the bug is present > only in the branch work/apol/kf6, target it in your merge request. I figured it out and pushed to https://invent.kde.org/frmdstryr/kdevelop/-/tree/meson-info-only-reparse-if-contents-changed?ref_type=heads . This issue is unrelated to KF6 from what I can tell. The file watcher triggers when the meson file stats change even if no contents changed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 --- Comment #2 from frmdstryr --- (In reply to Igor Kushnir from comment #1) > A fix merge request at > https://invent.kde.org/kdevelop/kdevelop/-/merge_requests is welcome. Note > that few KDevelop developers use Meson, so the KDevMesonManager plugin is > not actively maintained. But users occasionally contribute small fixes to > Meson support. I pushed a branch that stops the loop to github https://github.com/KDE/kdevelop/compare/master...frmdstryr:kdevelop:meson-info-only-reparse-if-contents-changed . I had problems pushing to invent. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] New: Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 Bug ID: 482983 Summary: Meson project with missing dependency re configures in infinite loop Classification: Applications Product: kdevelop Version: 5.12.230802 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Build tools: Meson Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- SUMMARY If a required dependency is missing in a project using the meson build system KDevelop keeps trying to reconfigure the project in an infinite loop. STEPS TO REPRODUCE 1. Clone a project that uses meson (eg horizon-eda) 2. Add a missing dependency or uninstall a required dependency 3. Configure the project in KDevelop or in a terminal OBSERVED RESULT KDevelop keeps trying to reconfigure in an infinite loop. EXPECTED RESULT It should run configure once, fail, then stop. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.0.0 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION It seems like there is something triggering a reconfigure on a file change since running meson in a separate terminal in the build folder causes KDevelop to start reconfiguring. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418065] Crash during autocomplete under Wayland.
https://bugs.kde.org/show_bug.cgi?id=418065 --- Comment #7 from frmdstryr --- (In reply to Justin Zobel from comment #6) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! I have not seen this lately. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409178] [wayland] Crash when opening a file
https://bugs.kde.org/show_bug.cgi?id=409178 --- Comment #4 from frmdstryr --- Have not seen this lately. It can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405704] [wayland] Crash opening quick open to select a file
https://bugs.kde.org/show_bug.cgi?id=405704 --- Comment #2 from frmdstryr --- (In reply to Justin Zobel from comment #1) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Have not seen this in a long time so this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405368] [wayland] Crash when clicking job status during parsing
https://bugs.kde.org/show_bug.cgi?id=405368 --- Comment #2 from frmdstryr --- (In reply to Justin Zobel from comment #1) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status when you reply to > "CONFIRMED" when replying. Thank you! I can't reproduce anymore on 5.9.220801, not sure if something was changed but it appears to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433818] Konsole max height gets "stuck" and cannot be resized to larger than 14 rows high
https://bugs.kde.org/show_bug.cgi?id=433818 --- Comment #3 from frmdstryr --- Correct. After closing all text editor tabs it begins working again. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433818] Konsole max height gets "stuck" and cannot be resized to larger than 14 rows high
https://bugs.kde.org/show_bug.cgi?id=433818 --- Comment #1 from frmdstryr --- It seems like the minimum size of the editors just keeps growing. This is not specific to the Konsole, any dock item from the bottom is doing this. If the window is maximized and I open the Problems or Find/Replace in Files it will increase the whole window size. If I switch to the console, then back it grows again. I did this a few times and now it won't even show the bottom bar on the screen anymore when maximized. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433818] New: Konsole max height gets "stuck" and cannot be resized to larger than 14 rows high
https://bugs.kde.org/show_bug.cgi?id=433818 Bug ID: 433818 Summary: Konsole max height gets "stuck" and cannot be resized to larger than 14 rows high Product: kdevelop Version: 5.6.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- SUMMARY The Konsole pane at the bottom sometimes becomes "stuck" and cannot be resized to larger than 10-14 rows high. The max height depends on which screen it's on (on a 1080 screen its 10 rows). After it get's stuck, the only way I've found to get the Konsole to resize larger is to either restart the application or close all open editors. This issue only started occurring a few weeks ago. I use horizontal split panes, not sure if that matters. STEPS TO REPRODUCE I'm unsure how to reproduce. But it has happened multiple times in different projects. Will update if I can find out how to reproduce it. OBSERVED RESULT The Konsole pane stops expanding after about 10% of the screen. It can be resized to smaller but not larger. EXPECTED RESULT The Konsole pane should expand to any height. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-66-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 31.1 GiB of RAM Graphics Processor: GeForce MX130/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426878] New: Opening a python project
https://bugs.kde.org/show_bug.cgi?id=426878 Bug ID: 426878 Summary: Opening a python project Product: kdevelop Version: 5.6.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.6.0) Qt Version: 5.15.0 Frameworks Version: 5.74.0 Operating System: Linux 5.4.0-48-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: Upon opening a project it crashes. The option to clear the cache no longer appears? The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f851300ed07 in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f84f67fa7e0, node=0x6) at ./parser/generated.h:164 #5 0x7f8513010103 in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84da6d52b0) at ./parser/generated.h:243 #6 0x7f851300f23a in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84d43bcac8) at ./parser/generated.h:323 #7 0x7f851301115b in Python::PythonAstTransformer::visitNodeList<_expr, Python::ExpressionAst>(asdl_seq*) (node=0x7f84d43bca60, this=0x7f84f67fa7e0) at ./parser/generated.h:38 #8 Python::PythonAstTransformer::visitNode(_slice*) (this=this@entry=0x7f84f67fa7e0, node=) at ./parser/generated.h:513 #9 0x7f851300f673 in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84d43bcb08) at ./parser/generated.h:354 #10 0x7f85130108ac in Python::PythonAstTransformer::visitNodeList<_expr, Python::ExpressionAst>(asdl_seq*) (this=0x7f84f67fa7e0, node=0x7f84d43bca18) at ./parser/generated.h:38 #11 0x7f851300edae in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84d43bcc40) at ./parser/generated.h:389 #12 0x7f85130108ac in Python::PythonAstTransformer::visitNodeList<_expr, Python::ExpressionAst>(asdl_seq*) (this=0x7f84f67fa7e0, node=0x7f84d43bc9f8) at ./parser/generated.h:38 #13 0x7f851300f345 in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84d43bcc70) at ./parser/generated.h:277 #14 0x7f85130108ac in Python::PythonAstTransformer::visitNodeList<_expr, Python::ExpressionAst>(asdl_seq*) (this=0x7f84f67fa7e0, node=0x7f84d43bc978) at ./parser/generated.h:38 #15 0x7f851300f345 in Python::PythonAstTransformer::visitNode(_expr*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84d43bcce0) at ./parser/generated.h:277 #16 0x7f8513013243 in Python::PythonAstTransformer::visitNode(_stmt*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84d43bcd10) at ./parser/generated.h:729 #17 0x7f8513014d8c in Python::PythonAstTransformer::visitNodeList<_stmt, Python::Ast>(asdl_seq*) (this=0x7f84f67fa7e0, node=0x7f84d43c2150) at ./parser/generated.h:38 #18 0x7f8513013ad4 in Python::PythonAstTransformer::visitNode(_stmt*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84d43bd8e8) at ./parser/generated.h:580 #19 0x7f8513014d8c in Python::PythonAstTransformer::visitNodeList<_stmt, Python::Ast>(asdl_seq*) (this=0x7f84f67fa7e0, node=0x7f84d43c0a80) at ./parser/generated.h:38 #20 0x7f85130136ac in Python::PythonAstTransformer::visitNode(_stmt*) (this=this@entry=0x7f84f67fa7e0, node=0x7f84d43d3540) at ./parser/generated.h:617 #21 0x7f851300b053 in Python::PythonAstTransformer::visitNodeList<_stmt, Python::Ast>(asdl_seq*) (node=0x7f84d4339370, this=0x7f84f67fa7e0) at ./parser/generated.h:38 #22 Python::PythonAstTransformer::run(_mod*, QString) (moduleName=..., syntaxtree=, this=0x7f84f67fa7e0) at ./parser/generated.h:16 #23 Python::AstBuilder::parse(QUrl const&, QString&) (this=this@entry=0x7f84f67fa898, filename=..., contents=...) at ./parser/astbuilder.cpp:275 #24 0x7f8513005b54 in Python::ParseSession::parse() (this=0x7f84d406df20) at ./parser/parsesession.cpp:76 #25 0x7f8511e85a3c in Python::ParseJob::run(QSharedPointer, ThreadWeaver::Thread*) (this=) at ./pythonparsejob.cpp:155 #26 0x7f856b31bd8f in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) (this=, self=..., thread=0x55614dacc950) at /usr/include/c++/9/bits/atomic_base.h:318 #27 0x7f856b31c38d in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) (this=, job=..., thread=) at /usr/include/c++/9/bits/atomic_base.h:318 #28 0x7f856b31b0a7 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) (this=, self=..., th=0x55614dacc950) at ./src/job.cpp:65 #29 0x7f856b31ac81 in ThreadWeaver::Thread::run() (this=0x55614dacc950) at
[kdevelop] [Bug 418065] Crash during autocomplete under Wayland.
https://bugs.kde.org/show_bug.cgi?id=418065 --- Comment #5 from frmdstryr --- Please disregard the part about disabling "Enable auto completion", it still seems to occur either way, just less frequently. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418065] Crash during autocomplete under Wayland.
https://bugs.kde.org/show_bug.cgi?id=418065 --- Comment #2 from frmdstryr --- This crash occurs so frequently it makes KDevelop unusable for python code. I noticed two things: 1. It only seems to happen on python source code 2. After crashing and restarting it (the autocomplete) usually works one time 3. When it crashes it is showing two popup autocompletions at the same time Disabling "Enable auto completion" under the Settings -> Editing -> Auto Completion prevents this from crashing. But somehow autocomplete still works... could this be some issue with the python plugin? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 418065] Crash during autocomplete under Wayland.
https://bugs.kde.org/show_bug.cgi?id=418065 frmdstryr changed: What|Removed |Added CC||frmdst...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #14 from frmdstryr --- Created attachment 125826 --> https://bugs.kde.org/attachment.cgi?id=125826=edit qtdiag output Attached the qtdiag output. At my office I normally have two monitors attached, A regular 1920x1080 monitor and 4k monitor. So there's three screens FHD, 4k laptop at 2x scale, and 4k monitor (which I run at 2560 x 1440). Strangely this only happens when the monitors are _not_ plugged in, maybe it's something leftover from that configuration that does not reset with a restart? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #11 from frmdstryr --- When I change the scaling to 1.0 and the menu's show up at the correct location as well and I can't get it to crash. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #10 from frmdstryr --- Created attachment 125717 --> https://bugs.kde.org/attachment.cgi?id=125717=edit New crash information added by DrKonqi kdevelop (5.5.0) using Qt 5.13.2 - What I was doing when the application crashed: Sorry I had kdevelop-dbgsym but not the kdevplatform55-libs-dbgsym. This is with 2x scaling, will try again without scaling. -- Backtrace (Reduced): #6 0x7f047e5f0780 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7f048051ac42 in (anonymous namespace)::ActiveToolTipManager::doVisibility() (this=0x7f0480736d70 <(anonymous namespace)::manager()::m>) at ./kdevplatform/util/activetooltip.cpp:109 #8 0x7f047db39362 in QObject::event(QEvent*) (this=0x7f0480736d70 <(anonymous namespace)::manager()::m>, e=) at kernel/qobject.cpp:1260 #9 0x7f047f2eceac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x557209099e80, receiver=receiver@entry=0x7f0480736d70 <(anonymous namespace)::manager()::m>, e=e@entry=0x55720b0ccc50) at kernel/qapplication.cpp:3703 #10 0x7f047f2f44b0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffd87cf1aa0, receiver=0x7f0480736d70 <(anonymous namespace)::manager()::m>, e=0x55720b0ccc50) at kernel/qapplication.cpp:3449 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #8 from frmdstryr --- This does not occur on another project that doesn't have code hinting popups so it does seem to be related to the popup info/hints. Also the messed up menu's also occur on the "terminal" app so it's not specific to KDevelop. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #7 from frmdstryr --- Created attachment 125675 --> https://bugs.kde.org/attachment.cgi?id=125675=edit New crash information added by DrKonqi kdevelop (5.5.0) using Qt 5.13.2 - What I was doing when the application crashed: Re-opened project. It seems to occur when it tries to popup info on one of the code items. -- Backtrace (Reduced): #6 0x7fc39221d780 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7fc394147c42 in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55 #8 0x7fc391766362 in QObject::event(QEvent*) (this=0x7fc394363d70, e=) at kernel/qobject.cpp:1260 #9 0x7fc392f19eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x56245f00be80, receiver=receiver@entry=0x7fc394363d70, e=e@entry=0x56247c4bae10) at kernel/qapplication.cpp:3703 #10 0x7fc392f214b0 in QApplication::notify(QObject*, QEvent*) (this=0x7fff54bb2d20, receiver=0x7fc394363d70, e=0x56247c4bae10) at kernel/qapplication.cpp:3449 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #6 from frmdstryr --- The context menu's popup at the wrong location as well in KDevelop but work fine in Kate / KWrite (see attached picture). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #5 from frmdstryr --- It's a laptop with a 4k screen running at 2x scale. There were no displays connected. I'll try again with debug symbols. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #4 from frmdstryr --- Created attachment 125674 --> https://bugs.kde.org/attachment.cgi?id=125674=edit Menu's popup at wrong location -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #2 from frmdstryr --- Created attachment 125668 --> https://bugs.kde.org/attachment.cgi?id=125668=edit New crash information added by DrKonqi kdevelop (5.5.0) using Qt 5.13.2 - What I was doing when the application crashed: I restarted and tried to use my project again. Have to stick with KWrite for now... -- Backtrace (Reduced): #6 0x7f8b39616780 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7f8b3b540c42 in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55 #8 0x7f8b38b5f362 in QObject::event(QEvent*) (this=0x7f8b3b75cd70, e=) at kernel/qobject.cpp:1260 #9 0x7f8b3a312eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55ba56b52e80, receiver=receiver@entry=0x7f8b3b75cd70, e=e@entry=0x55ba584ba130) at kernel/qapplication.cpp:3703 #10 0x7f8b3a31a4b0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffec94ba180, receiver=0x7f8b3b75cd70, e=0x55ba584ba130) at kernel/qapplication.cpp:3449 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 --- Comment #1 from frmdstryr --- Created attachment 125666 --> https://bugs.kde.org/attachment.cgi?id=125666=edit New crash information added by DrKonqi kdevelop (5.5.0) using Qt 5.13.2 - What I was doing when the application crashed: As soon as I scroll in a file it crashes. It was working fine before updating today. -- Backtrace (Reduced): #6 0x7feeec408780 in QScreen::geometry() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7f332c42 in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformUtil.so.55 #8 0x7feeeb951362 in QObject::event(QEvent*) (this=0x7f54ed70, e=) at kernel/qobject.cpp:1260 #9 0x7feeed104eac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55cc9c959e80, receiver=receiver@entry=0x7f54ed70, e=e@entry=0x55cc9e6b54e0) at kernel/qapplication.cpp:3703 #10 0x7feeed10c4b0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffd4f4d4480, receiver=0x7f54ed70, e=0x55cc9e6b54e0) at kernel/qapplication.cpp:3449 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 frmdstryr changed: What|Removed |Added CC||frmdst...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] Crash In QScreen::geometry
https://bugs.kde.org/show_bug.cgi?id=417151 frmdstryr changed: What|Removed |Added Summary|Crash when restoring|Crash In QScreen::geometry |unsaved file| -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417151] New: Crash when restoring unsaved file
https://bugs.kde.org/show_bug.cgi?id=417151 Bug ID: 417151 Summary: Crash when restoring unsaved file Product: kdevelop Version: 5.5.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.5.0) Qt Version: 5.13.2 Frameworks Version: 5.66.0 Operating System: Linux 5.3.0-28-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Opened a project after a crash occured. KDevelop prompted that the file was unsaved and asked to restore it, when it is restored the file resotred loads (properly) but then KDevelop immediately crashes. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7eff215cfbc0 (LWP 26551))] Thread 20 (Thread 0x7efe667fc700 (LWP 26708)): #0 0x7eff16a6c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557a946a0574) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7eff16a6c9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x557a946a0520, cond=0x557a946a0548) at pthread_cond_wait.c:502 #2 0x7eff16a6c9f3 in __pthread_cond_wait (cond=0x557a946a0548, mutex=0x557a946a0520) at pthread_cond_wait.c:655 #3 0x7eff1e273aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557a946a0520) at thread/qwaitcondition_unix.cpp:146 #4 0x7eff1e273aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x557a946f13f0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7eff1e273df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x557a946bb918, mutex=0x557a946f13f0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7eff14667845 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7eff1466b6f8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7eff14666b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7eff146695bb in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7eff1e26cb52 in QThreadPrivate::start(void*) (arg=0x7efe580025e0) at thread/qthread_unix.cpp:360 #11 0x7eff16a666db in start_thread (arg=0x7efe667fc700) at pthread_create.c:463 #12 0x7eff1db1288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7efe66ffd700 (LWP 26707)): #0 0x7eff16a6c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557a946a0574) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7eff16a6c9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x557a946a0520, cond=0x557a946a0548) at pthread_cond_wait.c:502 #2 0x7eff16a6c9f3 in __pthread_cond_wait (cond=0x557a946a0548, mutex=0x557a946a0520) at pthread_cond_wait.c:655 #3 0x7eff1e273aeb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557a946a0520) at thread/qwaitcondition_unix.cpp:146 #4 0x7eff1e273aeb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x557a946f13f0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7eff1e273df9 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x557a946bb918, mutex=0x557a946f13f0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7eff14667845 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7eff1466b6f8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7eff14666b0d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7eff146695bb in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7eff1e26cb52 in QThreadPrivate::start(void*) (arg=0x7efe540025e0) at thread/qthread_unix.cpp:360 #11 0x7eff16a666db in start_thread (arg=0x7efe66ffd700) at pthread_create.c:463 #12 0x7eff1db1288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7efe677fe700 (LWP 26706)): #0 0x7eff16a6c9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x557a946a0574) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7eff16a6c9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x557a946a0520, cond=0x557a946a0548) at pthread_cond_wait.c:502 #2 0x7eff16a6c9f3 in __pthread_cond_wait
[kdevelop] [Bug 411108] New: KDevelop crashes due to background parsing of python project
https://bugs.kde.org/show_bug.cgi?id=411108 Bug ID: 411108 Summary: KDevelop crashes due to background parsing of python project Product: kdevelop Version: 5.4.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.4.0) Qt Version: 5.12.3 Frameworks Version: 5.61.0 Operating System: Linux 5.0.0-23-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I was using firefox and it crashed in the background. This seems to occur very frequently. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7faa99bf6bc0 (LWP 17830))] Thread 36 (Thread 0x7fa9803b2700 (LWP 18012)): #0 0x7faa8cd4f649 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7faa8cd08470 in g_main_context_acquire () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7faa8cd09485 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7faa8cd096dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7faa96adfdcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7faa96a8103a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7faa968a84ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7faa94fb1e3f in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.54 #8 0x7faa968a9c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7faa8eea66db in start_thread (arg=0x7fa9803b2700) at pthread_create.c:463 #10 0x7faa961a988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 35 (Thread 0x7fa98700 (LWP 18011)): #0 0x7ffc1d7b37c0 in clock_gettime () #1 0x7faa961b8ea6 in __GI___clock_gettime (clock_id=1, tp=0x7fa98fffe680) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7faa96adf6b1 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7faa96addee9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7faa96ade4c5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7faa96adfb0e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7faa8cd08b28 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7faa8cd094fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7faa8cd096dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7faa96adfdcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7faa96a8103a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7faa968a84ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7faa94fb1e3f in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.54 #13 0x7faa968a9c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7faa8eea66db in start_thread (arg=0x7fa98700) at pthread_create.c:463 #15 0x7faa961a988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 34 (Thread 0x7fa9b0ff9700 (LWP 18010)): #0 0x7faa961a3839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7faa968a9f75 in QBasicMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7faa3aee1d3a in Python::AstBuilder::parse(QUrl const&, QString&) () at /usr/lib/x86_64-linux-gnu/libkdevpythonparser.so #3 0x7faa3aedce01 in Python::ParseSession::parse() () at /usr/lib/x86_64-linux-gnu/libkdevpythonparser.so #4 0x7faa31cddea8 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/32/kdevpythonlanguagesupport.so #5 0x7faa8caaa9ba in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7faa8caaaf98 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7faa8caa9c00 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7faa8caa975d in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7faa968a9c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7faa8eea66db in start_thread (arg=0x7fa9b0ff9700) at pthread_create.c:463 #11
[frameworks-ktexteditor] [Bug 405401] [wayland] KDevelop crashes when showing/hiding scrollbar text preview
https://bugs.kde.org/show_bug.cgi?id=405401 --- Comment #10 from frmdstryr --- I re-enabled the preview and have not had any of these for two weeks now so I think this can be closed. If it occurs again, I'll create a new issue. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 409278] Konsole sometimes stops showing input characters
https://bugs.kde.org/show_bug.cgi?id=409278 --- Comment #2 from frmdstryr --- No it is local. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409340] By switching opened files and opening context menu, the context menu grows with no limit.
https://bugs.kde.org/show_bug.cgi?id=409340 frmdstryr changed: What|Removed |Added CC||frmdst...@protonmail.com --- Comment #1 from frmdstryr --- *** Bug 409421 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409421] [wayland] Menu items are repeated in debugger context menu in Debug view
https://bugs.kde.org/show_bug.cgi?id=409421 frmdstryr changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from frmdstryr --- *** This bug has been marked as a duplicate of bug 409340 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409421] [wayland] Menu items are repeated in debugger context menu in Debug view
https://bugs.kde.org/show_bug.cgi?id=409421 --- Comment #1 from frmdstryr --- Created attachment 121288 --> https://bugs.kde.org/attachment.cgi?id=121288=edit Menu items repeated 4 times -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409421] New: [wayland] Menu items are repeated in debugger context menu in Debug view
https://bugs.kde.org/show_bug.cgi?id=409421 Bug ID: 409421 Summary: [wayland] Menu items are repeated in debugger context menu in Debug view Product: kdevelop Version: 5.3.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com CC: niko.s...@gmail.com Target Milestone: --- Created attachment 121287 --> https://bugs.kde.org/attachment.cgi?id=121287=edit Screenshot of context menu with duplicated items SUMMARY Menu items get repeated in the editor context menu when debugging. See attached image. STEPS TO REPRODUCE 1. Debug an application with gdb 2. Open a file in the editor and right click 3. Open another file and right click on the editor again, the items duplicate again OBSERVED RESULT Several menu items are repeated, eg Debug, Git, Review Patch, Analyze, External scripts. I've seen this repeated up to 4 times before. EXPECTED RESULT Context menu items should appear once. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.16 (available in About System) KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 409278] New: Konsole sometimes stops showing input characters
https://bugs.kde.org/show_bug.cgi?id=409278 Bug ID: 409278 Summary: Konsole sometimes stops showing input characters Product: konsole Version: 19.04.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- SUMMARY I've noticed that on several occasions Konsole stops displaying the input characters. STEPS TO REPRODUCE I have not yet determined how to reproduce this, but it has occurred several times over that past 3 months or so. It seems to only happen when I have a long running process that has been going for several hours, eg if I leave and come back the next day while it's running. It's a server that auto restarts on a file change (watchmedo is used to restart a python process on file change). A virtual env is also activated, I'm not sure if that matters. OBSERVED RESULT The output still is displayed and the input still works (can still run commands) it's just nothing that is typed is shown. The cursor simply sits at the start and doesn't move when typing or when I paste text with the mouse. Mouse scrolling works fine. It happens per tab, so opening a new tab works fine. Also I can choose "Copy input to" and that will show what is being typed in another tab. Also Ctrl+C does not work while a process is running, eg running "sleep 10" and pressing ctrl+c does not abort, but if use send signal and choose SIGINT from the menu and that will interrupt the process. However if no process is running the "^C" IS displayed when pressed, it seems to be the only input that is printed (or that may be output by the shell). EXPECTED RESULT Input characters should be displayed as normal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.16 KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Apologies for the lack of info in this report. If there's anything I can do to get more debug info on this please let me know, I will try to figure out how to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409178] [wayland] Crash when opening a file
https://bugs.kde.org/show_bug.cgi?id=409178 frmdstryr changed: What|Removed |Added Summary|Crash when opening a file |[wayland] Crash when ||opening a file -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409188] [Wayland] Crash when opening file with kwrite
https://bugs.kde.org/show_bug.cgi?id=409188 frmdstryr changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from frmdstryr --- Looks like a dup *** This bug has been marked as a duplicate of bug 408910 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408910] Konsole crashes on wayland
https://bugs.kde.org/show_bug.cgi?id=408910 frmdstryr changed: What|Removed |Added CC||frmdst...@protonmail.com --- Comment #2 from frmdstryr --- *** Bug 409188 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409188] New: [Wayland] Crash when opening file with kwrite
https://bugs.kde.org/show_bug.cgi?id=409188 Bug ID: 409188 Summary: [Wayland] Crash when opening file with kwrite Product: dolphin Version: 19.04.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: frmdst...@protonmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (19.04.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-52-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Right clicked on a file and chose "open with kwrite". The file opened but dolphin crashed.. Looks to be related to wayland. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f13d18cd240 (LWP 10900))] Thread 4 (Thread 0x7f13a7fde700 (LWP 10904)): #0 0x7f13d1179bf9 in __GI___poll (fds=0x7f13a0004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f13c33d84c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13c33d85dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13cb07ddcb in QEventDispatcherGlib::processEvents (this=0x7f13ab20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f13cb01f03a in QEventLoop::exec (this=this@entry=0x7f13a7fddda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f13cae464ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f13cae47c72 in QThreadPrivate::start (arg=0x55e31a9362b0) at thread/qthread_unix.cpp:361 #7 0x7f13c57c06db in start_thread (arg=0x7f13a7fde700) at pthread_create.c:463 #8 0x7f13d118688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f13b10e2700 (LWP 10903)): #0 0x7f13c57c69f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e31a5e0d18) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e31a5e0cc8, cond=0x55e31a5e0cf0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e31a5e0cf0, mutex=0x55e31a5e0cc8) at pthread_cond_wait.c:655 #3 0x7f13b2267dcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f13b2267af7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f13c57c06db in start_thread (arg=0x7f13b10e2700) at pthread_create.c:463 #6 0x7f13d118688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f13b9d0f700 (LWP 10902)): #0 0x7f13cb07dbe2 in socketNotifierSourceCheck (source=) at kernel/qeventdispatcher_glib.cpp:95 #1 0x7f13c33d7ee1 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f13c33d8470 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f13c33d85dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f13cb07ddcb in QEventDispatcherGlib::processEvents (this=0x7f13b4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f13cb01f03a in QEventLoop::exec (this=this@entry=0x7f13b9d0ed70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f13cae464ca in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7f13cb4ec015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f13cae47c72 in QThreadPrivate::start (arg=0x7f13cb763d80) at thread/qthread_unix.cpp:361 #9 0x7f13c57c06db in start_thread (arg=0x7f13b9d0f700) at pthread_create.c:463 #10 0x7f13d118688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f13d18cd240 (LWP 10900)): [KCrash Handler] #6 0x7f13bbd57cf9 in wl_proxy_marshal () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #7 0x7f13bc1dd29a in wl_surface_damage (height=, width=, y=, x=, wl_surface=) at ../../include/QtWaylandClient/5.12.3/QtWaylandClient/private/../../../../../src/client/wayland-wayland-client-protocol.h:2753 #8 QtWayland::wl_surface::damage (this=, x=, y=, width=, height=) at qwayland-wayland.cpp:1124 #9 0x7f13bc1c0474 in QtWaylandClient::QWaylandWindow::damage (this=, rect=...) at qwaylandwindow.cpp:565 #10 0x7f13bc1caa69 in QtWaylandClient::QWaylandAbstractDecoration::contentImage (this=0x55e31b527df0) at qwaylandabstractdecoration.cpp:134 #11 0x7f13bc1b7a1b in QtWaylandClient::QWaylandShmBackingStore::updateDecorations (this=this@entry=0x55e31aa78860) at qwaylandshmbackingstore.cpp:323 #12 0x7f13bc1b7fe0 in QtWaylandClient::QWaylandShmBackingStore::flush (this=this@entry=0x55e31aa78860, window=window@entry=0x55e31a6cbab0, region=..., offset=...) at
[kdevelop] [Bug 409178] Crash when opening a file
https://bugs.kde.org/show_bug.cgi?id=409178 --- Comment #2 from frmdstryr --- Opening the same file using quick open works without issues. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409178] Crash when opening a file
https://bugs.kde.org/show_bug.cgi?id=409178 frmdstryr changed: What|Removed |Added CC||frmdst...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409178] Crash when opening a file
https://bugs.kde.org/show_bug.cgi?id=409178 --- Comment #1 from frmdstryr --- Created attachment 121135 --> https://bugs.kde.org/attachment.cgi?id=121135=edit New crash information added by DrKonqi kdevelop (5.3.2) using Qt 5.12.3 - What I was doing when the application crashed: Attempted to open the file again and it repeated the. -- Backtrace (Reduced): #6 0x7f3ac74cdae0 in KDevelop::Bucket::deleteItem >(unsigned short, unsigned int, KDevelop::ItemRepository&) (repository=..., hash=0, index=, this=) at ./kdevplatform/serialization/itemrepository.h:526 #7 0x7f3ac74cdae0 in KDevelop::ItemRepository::deleteItem(unsigned int) (index=, this=0x7f3ac7f7ffc8 ) at ./kdevplatform/serialization/itemrepository.h:1380 #8 0x7f3ac74cdae0 in Utils::Set::unrefNode(unsigned int) (this=this@entry=0x7f3a4df86b00, current=) at ./kdevplatform/language/util/setrepository.cpp:1087 [...] #10 0x7f3ac73f5f6c in Utils::StorableSet::insertIndex(unsigned int) (index=, this=) at ./kdevplatform/language/util/setrepository.h:195 #11 0x7f3ac73f5f6c in Utils::StorableSet::insert(KDevelop::IndexedTopDUContext const&) (t=..., this=) at ./kdevplatform/language/util/setrepository.h:171 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409178] New: Crash when opening a file
https://bugs.kde.org/show_bug.cgi?id=409178 Bug ID: 409178 Summary: Crash when opening a file Product: kdevelop Version: 5.3.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-52-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: KDevelop crashed when I tried to open a file from the project explorer. It repeated the crash when I tried again. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd047daebc0 (LWP 4687))] Thread 22 (Thread 0x7fcfa27fc700 (LWP 4842)): #0 0x7fd03d0929f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x559b2ae58d10) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd03d0929f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x559b2ae58cc0, cond=0x559b2ae58ce8) at pthread_cond_wait.c:502 #2 0x7fd03d0929f3 in __pthread_cond_wait (cond=0x559b2ae58ce8, mutex=0x559b2ae58cc0) at pthread_cond_wait.c:655 #3 0x7fd044a92dbb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x559b2ae58cc0) at thread/qwaitcondition_unix.cpp:146 #4 0x7fd044a92dbb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x559b2ae358f0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fd044a930c9 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x559b2ae35858, mutex=0x559b2ae358f0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7fd03ac8e925 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fd03ac927d8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fd03ac8dbed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fd03ac92832 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fd03ac8dbed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fd03ac9069b in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fd044a8bc72 in QThreadPrivate::start(void*) (arg=0x7fcf980025e0) at thread/qthread_unix.cpp:361 #13 0x7fd03d08c6db in start_thread (arg=0x7fcfa27fc700) at pthread_create.c:463 #14 0x7fd04438b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7fcfa2ffd700 (LWP 4841)): #0 0x7fd03d0929f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x559b2ae58d10) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fd03d0929f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x559b2ae58cc0, cond=0x559b2ae58ce8) at pthread_cond_wait.c:502 #2 0x7fd03d0929f3 in __pthread_cond_wait (cond=0x559b2ae58ce8, mutex=0x559b2ae58cc0) at pthread_cond_wait.c:655 #3 0x7fd044a92dbb in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x559b2ae58cc0) at thread/qwaitcondition_unix.cpp:146 #4 0x7fd044a92dbb in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x559b2ae358f0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fd044a930c9 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x559b2ae35858, mutex=0x559b2ae358f0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7fd03ac8e925 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fd03ac927d8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fd03ac8dbed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fd03ac92832 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fd03ac8dbed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fd03ac92832 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fd03ac8dbed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7fd03ac9069b in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7fd044a8bc72 in QThreadPrivate::start(void*) (arg=0x7fcf940021e0) at
[drkonqi] [Bug 408993] drkonqi crash in backtraceline.h 59
https://bugs.kde.org/show_bug.cgi?id=408993 frmdstryr changed: What|Removed |Added Summary|drkonqi crash in|drkonqi crash in |backgraceline.h 59 |backtraceline.h 59 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 408993] New: drkonqi crash in backgraceline.h 59
https://bugs.kde.org/show_bug.cgi?id=408993 Bug ID: 408993 Summary: drkonqi crash in backgraceline.h 59 Product: drkonqi Version: 5.16.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: backtraceparsing Assignee: unassigned-b...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Created attachment 121056 --> https://bugs.kde.org/attachment.cgi?id=121056=edit Crash trace SUMMARY DrKonqi crashed while attempting to submit another crash report. STEPS TO REPRODUCE N/A OBSERVED RESULT I noticed before it occurred the window width started "jumping" by about 50 pixels or so. Also, I've seen the stack trace from thread 3 in various crashes so could this be an issue with i965_dri. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel: 4.15.0-52-generic Wayland: Yes ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 408422] New: Find/replace in files makes KDevelop laggy/unresponsive if match is found in very long line
https://bugs.kde.org/show_bug.cgi?id=408422 Bug ID: 408422 Summary: Find/replace in files makes KDevelop laggy/unresponsive if match is found in very long line Product: kdevelop Version: 5.3.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Output Views Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- SUMMARY When doing a find/replace in files in a project which contains minified javascript files KDevelop becomes laggy when a search returns a match in the file. This seems to be because these minified files are a single line that may be upwards of several hundered kb. STEPS TO REPRODUCE 1. Download one or more large minified js file and include in a project eg https://code.jquery.com/jquery-3.4.1.min.js 2. Include *.js filter and search for a string within the file eq "jQuery" 3. Open the find/replace tool view and scroll until the result is in view OBSERVED RESULT When the result shows up in he find/replace tool view KDevelop becomes very laggy especially the mouse goes over the result. EXPECTED RESULT KDevelop should limit the amount of text it displays in the result list and tooltip to avoid any lag. Perhaps make the size adjustable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405704] New: [wayland] Crash opening quick open to select a file
https://bugs.kde.org/show_bug.cgi?id=405704 Bug ID: 405704 Summary: [wayland] Crash opening quick open to select a file Product: kdevelop Version: 5.3.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I used the shortcut keys to try to open a file using the quick open dialog. First time I've seen this happen. Doesn't seem to occur often. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9c790c2bc0 (LWP 22939))] Thread 23 (Thread 0x7f9bd4ff9700 (LWP 23096)): #0 0x7f9c6e3db9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56527e0495f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f9c6e3db9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x56527e0495a0, cond=0x56527e0495c8) at pthread_cond_wait.c:502 #2 0x7f9c6e3db9f3 in __pthread_cond_wait (cond=0x56527e0495c8, mutex=0x56527e0495a0) at pthread_cond_wait.c:655 #3 0x7f9c75db3b4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x56527e0495a0) at thread/qwaitcondition_unix.cpp:146 #4 0x7f9c75db3b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x56527e06b290, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f9c75db3e59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x56527e06b1f8, mutex=0x56527e06b290, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f9c6bfd7935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f9c6bfdb7e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f9c6bfd6bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f9c6bfd96ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f9c75dacbc2 in QThreadPrivate::start(void*) (arg=0x7f9bb40025e0) at thread/qthread_unix.cpp:361 #11 0x7f9c6e3d56db in start_thread (arg=0x7f9bd4ff9700) at pthread_create.c:463 #12 0x7f9c756ac88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f9bd57fa700 (LWP 23095)): #0 0x7f9c6e3db9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56527e0495f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f9c6e3db9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x56527e0495a0, cond=0x56527e0495c8) at pthread_cond_wait.c:502 #2 0x7f9c6e3db9f3 in __pthread_cond_wait (cond=0x56527e0495c8, mutex=0x56527e0495a0) at pthread_cond_wait.c:655 #3 0x7f9c75db3b4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x56527e0495a0) at thread/qwaitcondition_unix.cpp:146 #4 0x7f9c75db3b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x56527e06b290, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f9c75db3e59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x56527e06b1f8, mutex=0x56527e06b290, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f9c6bfd7935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f9c6bfdb7e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f9c6bfd6bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f9c6bfdb842 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f9c6bfd6bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f9c6bfd96ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7f9c75dacbc2 in QThreadPrivate::start(void*) (arg=0x7f9bc00025e0) at thread/qthread_unix.cpp:361 #13 0x7f9c6e3d56db in start_thread (arg=0x7f9bd57fa700) at pthread_create.c:463 #14 0x7f9c756ac88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f9bd5ffb700 (LWP 23094)): #0 0x7f9c6e3db9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56527e0495f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f9c6e3db9f3 in __pthread_cond_wait_common
[frameworks-ktextwidgets] [Bug 405401] [wayland] KDevelop crashes when showing/hiding scrollbar text preview
https://bugs.kde.org/show_bug.cgi?id=405401 --- Comment #7 from frmdstryr --- Also it seems to only occur (on my system) when highlighting is enabled. I guess it takes longer to render or something. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktextwidgets] [Bug 405401] [wayland] KDevelop crashes when showing/hiding scrollbar text preview
https://bugs.kde.org/show_bug.cgi?id=405401 --- Comment #6 from frmdstryr --- Created attachment 118757 --> https://bugs.kde.org/attachment.cgi?id=118757=edit New crash information added by DrKonqi kwrite (18.12.3) using Qt 5.12.0 - What I was doing when the application crashed: Thanks. I can reproduce it with KWrite. >From looking at the code it looks like there should be a null check in https://github.com/mgerstner/ktexteditor/blob/5a90cee2f73ab80a41220b3dbc67cbe4f0db8d49/src/view/kateviewhelpers.cpp#L466 before delete m_textPreview; This occurs when moving my mouse to another window (one screen to another) in which both the scrollbar leaveEvent and the window deactivated eventFilter will trigger in https://github.com/mgerstner/ktexteditor/blob/5a90cee2f73ab80a41220b3dbc67cbe4f0db8d49/src/view/kateviewhelpers.cpp#L357-L372 -- Backtrace (Reduced): #7 0x7fdfa35556a4 in QWindowPrivate::setVisible (this=0x55c3f9b63720, visible=visible@entry=false) at kernel/qwindow.cpp:402 #8 0x7fdfa3dd1d6d in QWidgetWindow::setNativeWindowVisibility (this=this@entry=0x55c3fa498830, visible=visible@entry=false) at kernel/qwidgetwindow.cpp:205 #9 0x7fdfa3dac54f in QWidgetPrivate::hide_sys (this=this@entry=0x55c3fa42d640) at kernel/qwidget.cpp:8227 #10 0x7fdfa3db3900 in QWidgetPrivate::hide_helper (this=this@entry=0x55c3fa42d640) at kernel/qwidget.cpp:8155 #11 0x7fdfa3db85a0 in QWidget::setVisible (this=0x55c3fa3131e0, visible=) at kernel/qwidget.cpp:8357 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405401] [wayland] KDevelop crashes due to QWidget setVisible false followed by setVisible true
https://bugs.kde.org/show_bug.cgi?id=405401 --- Comment #4 from frmdstryr --- Created attachment 118756 --> https://bugs.kde.org/attachment.cgi?id=118756=edit New crash information added by DrKonqi kdevelop (5.3.2) using Qt 5.12.0 - What I was doing when the application crashed: @Sven Brauch, disabling the setting appears to work. Thank you very much! @Friedrich W. H. Kossebau, added the dbgsym -- Backtrace (Reduced): #6 0x in () #7 0x7f298d9506a4 in QWindowPrivate::setVisible(bool) (this=0x556100ef6d10, visible=visible@entry=false) at kernel/qwindow.cpp:402 #8 0x7f298e6bbd6d in QWidgetWindow::setNativeWindowVisibility(bool) (this=this@entry=0x556111543290, visible=visible@entry=false) at kernel/qwidgetwindow.cpp:205 #9 0x7f298e69654f in QWidgetPrivate::hide_sys() (this=this@entry=0x556eab70) at kernel/qwidget.cpp:8227 #10 0x7f298e69d900 in QWidgetPrivate::hide_helper() (this=this@entry=0x556eab70) at kernel/qwidget.cpp:8155 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405401] [wayland] KDevelop crashes due to QWidget setVisible false followed by setVisible true
https://bugs.kde.org/show_bug.cgi?id=405401 frmdstryr changed: What|Removed |Added CC||frmdst...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405401] [wayland] KDevelop crashes due to QWidget setVisible false followed by setVisible true
https://bugs.kde.org/show_bug.cgi?id=405401 --- Comment #2 from frmdstryr --- Thank you, will try this and update later today. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 405401] New: [wayland] KDevelop crashes due to QWidget setVisible false followed by setVisible true
https://bugs.kde.org/show_bug.cgi?id=405401 Bug ID: 405401 Summary: [wayland] KDevelop crashes due to QWidget setVisible false followed by setVisible true Product: kdevelop Version: 5.3.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: On a wayland plasma session KDevelop frequently crashes when moving my mouse from one screen to another. It occurs more often when using a split view of editors. A ticket was opened on this issue before in which said this was supposed to be fixed in Qt 5.12 but that apparently is not true as it still happens on the latest version of plasma. This happens VERY frequenly and is extremely annoying. Thankfully KDevelop is great at saving work and nothing is ever lost when this happens (except time). Any help would be appreciated... The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5beb576bc0 (LWP 32177))] Thread 16 (Thread 0x7f5b61ffb700 (LWP 32315)): #0 0x7f5be088f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55a60cea01e4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f5be088f9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55a60cea0190, cond=0x55a60cea01b8) at pthread_cond_wait.c:502 #2 0x7f5be088f9f3 in __pthread_cond_wait (cond=0x55a60cea01b8, mutex=0x55a60cea0190) at pthread_cond_wait.c:655 #3 0x7f5be8267b4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55a60cea0190) at thread/qwaitcondition_unix.cpp:146 #4 0x7f5be8267b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55a60cf3e240, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f5be8267e59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x55a60cf3e1a8, mutex=0x55a60cf3e240, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f5bde48b935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f5bde48f7e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f5bde48abfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f5bde48d6ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f5be8260bc2 in QThreadPrivate::start(void*) (arg=0x7f5b4c0025e0) at thread/qthread_unix.cpp:361 #11 0x7f5be08896db in start_thread (arg=0x7f5b61ffb700) at pthread_create.c:463 #12 0x7f5be7b6088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f5b627fc700 (LWP 32314)): #0 0x7f5be7b5a839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f5be8260ec5 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=) at thread/qfutex_p.h:92 #2 0x7f5be8260ec5 in QtLinuxFutex::futexWait >(QBasicAtomicPointer&, QBasicAtomicPointer::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 0x7f5be8260ec5 in lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:142 #4 0x7f5be8260ec5 in QBasicMutex::lockInternal() (this=0x7f5beb039d68 <(anonymous namespace)::tryLockMutex>) at thread/qmutex_linux.cpp:159 #5 0x7f5be82610ab in QMutex::lock() (this=this@entry=0x7f5beb039d68 <(anonymous namespace)::tryLockMutex>) at thread/qmutex.cpp:227 #6 0x7f5beae06a41 in QMutexLocker::QMutexLocker(QBasicMutex*) (m=0x7f5beb039d68 <(anonymous namespace)::tryLockMutex>, this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:206 #7 0x7f5beae06a41 in KDevelop::ForegroundLock::relock() (this=0x7f5b627fae1f) at ./kdevplatform/util/foregroundlock.cpp:104 #8 0x7f5be6834ec7 in KDevelop::ParseJob::translateDUChainToRevision(KDevelop::TopDUContext*) (this=0x7f5b582d6970, context=0x55a610a61b20) at ./kdevplatform/language/backgroundparser/parsejob.cpp:428 #9 0x7f5b810dbd7b in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kdevplatform/31/kdevpythonlanguagesupport.so #10 0x7f5bde48e9ca in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7f5bde48efa8 in
[kdevelop] [Bug 405371] New: [wayland] Crash when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=405371 Bug ID: 405371 Summary: [wayland] Crash when resuming from suspend Product: kdevelop Version: 5.3.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: It crashed immediately when my laptop resumed from suspend. I have a second monitor plugged in if that matters. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f97f1b8abc0 (LWP 15724))] Thread 15 (Thread 0x7f978214c700 (LWP 15919)): #0 0x7f97e4cfe43b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f97e4d009d3 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f97e4d0146b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f97e4d0164c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f97eeaaa15b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f9774013930, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f97eea4b64a in QEventLoop::exec(QFlags) (this=this@entry=0x7f978214b910, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f97ee87341a in QThread::exec() (this=this@entry=0x5571b024ad50) at thread/qthread.cpp:531 #7 0x7f97ecf7af0f in KDevelop::CompletionWorkerThread::run() (this=0x5571b024ad50) at ./kdevplatform/language/codecompletion/codecompletionmodel.cpp:79 #8 0x7f97ee874bc2 in QThreadPrivate::start(void*) (arg=0x5571b024ad50) at thread/qthread_unix.cpp:361 #9 0x7f97e6e9d6db in start_thread (arg=0x7f978214c700) at pthread_create.c:463 #10 0x7f97ee17488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f9778a65700 (LWP 15908)): #0 0x7f97e6ea39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5571869d06c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f97e6ea39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5571869d0670, cond=0x5571869d0698) at pthread_cond_wait.c:502 #2 0x7f97e6ea39f3 in __pthread_cond_wait (cond=0x5571869d0698, mutex=0x5571869d0670) at pthread_cond_wait.c:655 #3 0x7f97ee87bb4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5571869d0670) at thread/qwaitcondition_unix.cpp:146 #4 0x7f97ee87bb4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5571869e1f30, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f97ee87be59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5571869e1e98, mutex=0x5571869e1f30, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f97e4a9f935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f97e4aa37e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f97e4a9ebfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f97e4aa16ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f97ee874bc2 in QThreadPrivate::start(void*) (arg=0x5571b1070de0) at thread/qthread_unix.cpp:361 #11 0x7f97e6e9d6db in start_thread (arg=0x7f9778a65700) at pthread_create.c:463 #12 0x7f97ee17488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f9779266700 (LWP 15907)): #0 0x7f97e6ea39f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5571869d06c4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f97e6ea39f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5571869d0670, cond=0x5571869d0698) at pthread_cond_wait.c:502 #2 0x7f97e6ea39f3 in __pthread_cond_wait (cond=0x5571869d0698, mutex=0x5571869d0670) at pthread_cond_wait.c:655 #3 0x7f97ee87bb4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5571869d0670) at thread/qwaitcondition_unix.cpp:146 #4 0x7f97ee87bb4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5571869e1f30, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f97ee87be59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5571869e1e98, mutex=0x5571869e1f30, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f97e4a9f935 in
[kdevelop] [Bug 405368] New: [wayland] Crash when clicking job status during parsing
https://bugs.kde.org/show_bug.cgi?id=405368 Bug ID: 405368 Summary: [wayland] Crash when clicking job status during parsing Product: kdevelop Version: 5.3.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: Just opened KDevelop, clicked the parse job status (bottom right) when it was at about 6% and it crashed (very large project). -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 [Current thread is 1 (Thread 0x7f7d074a5bc0 (LWP 14094))] Thread 17 (Thread 0x7f7c7df28700 (LWP 14458)): #0 0x7f7d03a82bf9 in __GI___poll (fds=0x7f7c70115820, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f7cfa61c539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7cfa61c64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7d043c515b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f7c700418d0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f7d0436664a in QEventLoop::exec(QFlags) (this=this@entry=0x7f7c7df27910, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f7d0418e41a in QThread::exec() (this=this@entry=0x5640f8043da0) at thread/qthread.cpp:531 #6 0x7f7d02895f0f in KDevelop::CompletionWorkerThread::run() (this=0x5640f8043da0) at ./kdevplatform/language/codecompletion/codecompletionmodel.cpp:79 #7 0x7f7d0418fbc2 in QThreadPrivate::start(void*) (arg=0x5640f8043da0) at thread/qthread_unix.cpp:361 #8 0x7f7cfc7b86db in start_thread (arg=0x7f7c7df28700) at pthread_create.c:463 #9 0x7f7d03a8f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f7c5bfff700 (LWP 14287)): #0 0x7f7cfc7be9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5640c7bdc5d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f7cfc7be9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5640c7bdc580, cond=0x5640c7bdc5a8) at pthread_cond_wait.c:502 #2 0x7f7cfc7be9f3 in __pthread_cond_wait (cond=0x5640c7bdc5a8, mutex=0x5640c7bdc580) at pthread_cond_wait.c:655 #3 0x7f7d04196b4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5640c7bdc580) at thread/qwaitcondition_unix.cpp:146 #4 0x7f7d04196b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5640c7c798e0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f7d04196e59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5640c7c79848, mutex=0x5640c7c798e0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f7cfa3ba935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f7cfa3be7e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f7cfa3b9bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f7cfa3bc6ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f7d0418fbc2 in QThreadPrivate::start(void*) (arg=0x7f7c600025e0) at thread/qthread_unix.cpp:361 #11 0x7f7cfc7b86db in start_thread (arg=0x7f7c5bfff700) at pthread_create.c:463 #12 0x7f7d03a8f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f7c74a8d700 (LWP 14286)): #0 0x7f7cfc7be9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5640c7bdc5d4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f7cfc7be9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5640c7bdc580, cond=0x5640c7bdc5a8) at pthread_cond_wait.c:502 #2 0x7f7cfc7be9f3 in __pthread_cond_wait (cond=0x5640c7bdc5a8, mutex=0x5640c7bdc580) at pthread_cond_wait.c:655 #3 0x7f7d04196b4b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5640c7bdc580) at thread/qwaitcondition_unix.cpp:146 #4 0x7f7d04196b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5640c7c798e0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f7d04196e59 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5640c7c79848, mutex=0x5640c7c798e0, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f7cfa3ba935 in
[kdevelop] [Bug 402617] Crash when cancelling "Find in files" during collection stage
https://bugs.kde.org/show_bug.cgi?id=402617
--- Comment #6 from frmdstryr ---
Yep that worked.
void GrepOutputView::updateScrollArea()
{
if(!model()) {
return;
}
for (int col = 0; col < model()->columnCount(); ++col)
resultsTreeView->resizeColumnToContents(col);
}
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 377673] Brightness gets brighter when low battery
https://bugs.kde.org/show_bug.cgi?id=377673 frmdstryr <frmdst...@gmail.com> changed: What|Removed |Added Platform|Other |Neon Packages --- Comment #1 from frmdstryr <frmdst...@gmail.com> --- rm@xps:~$ uname -a Linux xps 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux jrm@xps:~$ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: neon Description:KDE neon User Edition 5.9 Release:16.04 Codename: xenial jrm@xps:~$ -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 377673] New: Brightness gets brighter when low battery
https://bugs.kde.org/show_bug.cgi?id=377673 Bug ID: 377673 Summary: Brightness gets brighter when low battery Product: Powerdevil Version: 5.9.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: frmdst...@gmail.com Target Milestone: --- Thus bug in https://bugs.kde.org/show_bug.cgi?id=198463 must have come back. If my brightness is down all the way (working at night) and the laptop goes into low power mode, the brightness goes up to the low power setting. It should use the minimum of the two settings (current and low power setting). Thanks!! -- You are receiving this mail because: You are watching all bug changes.
[solid] [Bug 198463] powerdevil should not increase brightness when switching to a more conservative power profile if brightness is already lower than default for that profile
https://bugs.kde.org/show_bug.cgi?id=198463 frmdstryr <frmdst...@gmail.com> changed: What|Removed |Added CC||frmdst...@gmail.com --- Comment #15 from frmdstryr <frmdst...@gmail.com> --- I'm seeing this issue on 5.9.3 -- You are receiving this mail because: You are watching all bug changes.
