[kwin] [Bug 487155] KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot
https://bugs.kde.org/show_bug.cgi?id=487155 --- Comment #5 from Andreas Nordal --- That version info I think was filled in by DrKonqui (I don't remember writing it). It happened again. Here is what happened to poor /dev/null when when it was Firefox I resized, so that KDE6 crashed and can't be restarted: > ls -l /dev/null -rw--- 1 root root 9 mai 29 00:47 /dev/null > sudo xxd devnull : 6469 7361 626c 6564 0a disabled. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487155] KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot
https://bugs.kde.org/show_bug.cgi?id=487155 --- Comment #2 from Andreas Nordal --- Created attachment 169577 --> https://bugs.kde.org/attachment.cgi?id=169577=edit New crash information added by DrKonqi kate (24.02.2) using Qt 5.15.13 Third time in a row. I think I'm discovering a more consistent way to trigger it. I accidentally made the window quarter-screen-sized before I hit the point where it becomes half-sized. -- Backtrace (Reduced): #6 drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (stroker=, y=32770, x=1540) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:159 #7 drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (y=32770, x=1540, stroker=0x7ffdf4f91ba0) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:152 #8 drawLine(QCosmeticStroker*, qreal, qreal, qreal, qreal, int) (stroker=0x7ffdf4f91ba0, rx1=, ry1=, rx2=, ry2=, caps=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:809 #9 0x7fe6810cb67a in QCosmeticStroker::drawLine(QPointF const&, QPointF const&) (this=0x7ffdf4f91ba0, p1=..., p2=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:356 #10 0x7fe6810f089c in QRasterPaintEngine::drawLines(QLine const*, int) (this=, lines=, lineCount=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qpaintengine_raster.cpp:3198 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487155] KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot
https://bugs.kde.org/show_bug.cgi?id=487155 --- Comment #1 from Andreas Nordal --- Created attachment 169576 --> https://bugs.kde.org/attachment.cgi?id=169576=edit New crash information added by DrKonqi kate (24.02.2) using Qt 5.15.13 Exactly the same happened again. I dragged Kate to the right half side of the screen. It's usually not that often. -- Backtrace (Reduced): #6 drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (stroker=, y=32770, x=1540) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:159 #7 drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (y=32770, x=1540, stroker=0x7ffc49e1bc60) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:152 #8 drawLine(QCosmeticStroker*, qreal, qreal, qreal, qreal, int) (stroker=0x7ffc49e1bc60, rx1=, ry1=, rx2=, ry2=, caps=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:809 #9 0x7fa901ccb67a in QCosmeticStroker::drawLine(QPointF const&, QPointF const&) (this=0x7ffc49e1bc60, p1=..., p2=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:356 #10 0x7fa901cf089c in QRasterPaintEngine::drawLines(QLine const*, int) (this=, lines=, lineCount=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qpaintengine_raster.cpp:3198 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487155] KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot
https://bugs.kde.org/show_bug.cgi?id=487155 Andreas Nordal changed: What|Removed |Added CC||andreas_norda...@hotmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 487155] New: KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot
https://bugs.kde.org/show_bug.cgi?id=487155 Bug ID: 487155 Summary: KDE6: Dragging windows into screen edges often crashes the program and sometimes the whole desktop so I have to reboot Classification: Applications Product: kate Version: 24.02.2 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kate (24.02.2) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.8-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I like that you can maximize or half-size a window by dragging it over the top or side edges. This was no problem in KDE5, but in KDE6, it sometimes crashes the window. Kate is no special. It happens to Konsole and Firefox too. When it's firefox, the whole desktop crashes and /dev/null becomes replaced with a regular file (usually of zero bytes, but sometimes containing a linefeed terminated message), and KDE hangs forever when I try to restart it, so I have to reboot. The crash can be reproduced sometimes. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7f48e5ac7a8e in BYTE_MUL (a=4294967040, x=Python Exception : Cannot access memory at address 0x7f4250821808 #5 sourceOver (color=4293783021, d=Python Exception : Cannot access memory at address 0x7f4250821808 #6 drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (stroker=, y=32770, x=1540) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:159 #7 drawPixelARGB32Opaque(QCosmeticStroker*, int, int, int) (y=32770, x=1540, stroker=0x7ffc8fe21c50) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:152 #8 drawLine(QCosmeticStroker*, qreal, qreal, qreal, qreal, int) (stroker=0x7ffc8fe21c50, rx1=, ry1=, rx2=, ry2=, caps=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:809 #9 0x7f48e5acb67a in QCosmeticStroker::drawLine(QPointF const&, QPointF const&) (this=0x7ffc8fe21c50, p1=..., p2=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qcosmeticstroker.cpp:356 #10 0x7f48e5af089c in QRasterPaintEngine::drawLines(QLine const*, int) (this=, lines=, lineCount=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/gui/painting/qpaintengine_raster.cpp:3198 #11 0x7f48e457ea16 in QPainter::drawLine(int, int, int, int) (y2=, x2=, y1=0, x1=, this=0x7ffc8fe232b0, this=, x1=, y1=, x2=, y2=) at /usr/include/qt6/QtGui/qpainter.h:455 #12 KateRenderer::paintTextLine(QPainter&, KateLineLayout*, int, int, QRectF const&, KTextEditor::Cursor const*, QFlags) (this=0x55e7e6b67720, paint=..., range=0x55e7eac99d60, xStart=0, xEnd=65012, textClipRect=, cursor=0x7ffc8fe232b8, flags=...) at /usr/src/debug/ktexteditor-6.2.0/src/render/katerenderer.cpp:969 #13 0x7f48e45f0b9a in KateViewInternal::paintEvent(QPaintEvent*) (this=0x55e7e77fc290, e=0x7ffc8fe23500) at /usr/src/debug/ktexteditor-6.2.0/src/render/katetextlayout.cpp:119 #14 0x7f48e640e38d in QWidget::event(QEvent*) (this=0x55e7e77fc290, event=0x7ffc8fe23500) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:9183 #15 0x7f48e63c2f1e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55e7e77fc290, e=0x7ffc8fe23500) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qapplication.cpp:3287 #16 0x7f48e518f060 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55e7e77fc290, event=0x7ffc8fe23500) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1134 #17 0x7f48e518f6a9 in QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (receiver=, event=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qcoreapplication.cpp:1589 #18 0x7f48e63fe955 in QWidgetPrivate::sendPaintEvent(QRegion const&) (this=this@entry=0x55e7e76c3e50, toBePainted=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:5647 #19 0x7f48e6400599 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) (this=this@entry=0x55e7e76c3e50, pdev=pdev@entry=0x55e7e74db900, rgn=..., offset=..., flags=flags@entry=..., sharedPainter=sharedPainter@entry=0x0, repaintManager=) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/widgets/kernel/qwidget.cpp:5597 #20 0x7f48e6402849 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) (this=0x55e7e7601310, pdev=0x55e7e74db900, siblings=...,
[ghostwriter] [Bug 478992] New: Ghostwriter replaces nonbreaking space on save
https://bugs.kde.org/show_bug.cgi?id=478992 Bug ID: 478992 Summary: Ghostwriter replaces nonbreaking space on save Classification: Applications Product: ghostwriter Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: andreas_norda...@hotmail.com Target Milestone: --- SUMMARY Opening and saving a markdown file replaces nonbreaking spaces with spaces. This happens on save: The GUI is able to show and preserve nonbreaking spaces through opening, editing and saving (by configuring to "show unbreakable space"), but what actually gets saved is replaced. STEPS TO REPRODUCE 1. printf '\xC2\xA0' > nbsp.md 2. ghostwriter nbsp.md 3. In Ghostwriter, press Ctrl+SQ OBSERVED RESULT xxd nbsp.md : 20 EXPECTED RESULT xxd nbsp.md : c2a0 SOFTWARE/OS VERSIONS Using pandoc version 3.1.9 KDE Frameworks 5.112.0 Qt 5.15.11 openSUSE Tumbleweed 20231214 ADDITIONAL INFORMATION Kate preserves nonbreaking space. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453854] Please follow BinaryUnitDialect, appropriately
https://bugs.kde.org/show_bug.cgi?id=453854 --- Comment #9 from Andreas Nordal --- Is it a good idea to use the same configuration for everything? There may be opposite conventions to follow: For network speed, I would even suggest that if the configuration isn't SI, the configuration is wrong. But opposite for memory and partition sizes. Not that I would argue for more options. Rather that getting the default right in each case without not making the user choose between two wrongs is more important. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 474155] New: plasma-systemmonitor should show bandwidth in SI bits/s, not binary-prefixed bytes/s
https://bugs.kde.org/show_bug.cgi?id=474155 Bug ID: 474155 Summary: plasma-systemmonitor should show bandwidth in SI bits/s, not binary-prefixed bytes/s Classification: Applications Product: plasma-systemmonitor Version: 5.27.7 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: andreas_norda...@hotmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- I would like plasma-systemmonitor's bandwidth view (specifically its Y-axis) to show 1000s of b/s, not 1024s of B/s. E.g. my internet bandwidth is 10 Mb/s, not 1.3 MiB/s. I don't think it needs to be configurable: Isn't SI-b/s simply the common unit of bandwidth? To the point of being confusing when it's anything else? Case in point: Every ISP gives numbers in megabits/s. Try asking any non-technical person what that is in mebibytes/s. STEPS TO REPRODUCE 1. Run plasma-systemmonitor → Logg → Network 2. Take a bandwidth test. OBSERVED RESULT Wrong unit on the Y-axis. EXPECTED RESULT Right unit on the Y-axis. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230902 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] On X11, all windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 --- Comment #30 from Andreas Nordal --- I wrote the duplicate bug #468177, and I haven't had this problem in a while. Testing again, it works! kwin 5.27.7-1.2 OpensuseTumbleweed 20230823 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468177] New: Window left outside remaining screen area after disconnecting monitor
https://bugs.kde.org/show_bug.cgi?id=468177 Bug ID: 468177 Summary: Window left outside remaining screen area after disconnecting monitor Classification: Plasma Product: kwin Version: 5.27.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- SUMMARY I have a laptop with a FHD screen and a separate 4K monitor. I have set the laptop screen to turn off when connected to the monitor, so in my case, the screen area halves in width and height when disconnecting the monitor. So far so good. I like to work with Konsole on the left half of the screen and Kate on the right. When I disconnect, only Konsole remains visible, and the minimize animation reveals that Kate is exactly outside the remaining screen area. In this state, Kate is unreachable: I can't move it into the remaining screen area, because I can't grab it, because the mouse pointer won't go there. Thankfully, I can F11-fullscreen it and save my work. But there is no way I can get the window inside the remaining screen area again other than restarting it. STEPS TO REPRODUCE 1. Have 2 screens of different width connected in the mode where the small screen shows the upper left pixels of the big one or is off. 2. Drag a window into the right desktop edge, so it snaps into exactly the right half of the screen. 3. Disconnect the big screen. OBSERVED RESULT The window that I snapped to the right side of the screen is left outside the remaining screen area. EXPECTED RESULT The window that I snapped to the right side of the screen is somewhere on the right side of the screen. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230331 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: HP Product Name: HP EliteBook 840 G6 ADDITIONAL INFORMATION Reproducibility: 10/10 The phenomenon happens only in width, not height: If I put Konsole in the lower left quadrant before disconnecting, I still see Konsole in the lower left quadrant. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 89299] prevent paste of newline characters
https://bugs.kde.org/show_bug.cgi?id=89299 --- Comment #70 from Andreas Nordal --- > Do you know if there’s a way to ask the program if it supports bracketed > paste? The program tells the terminal: printf "\e[?2004h" # Enable bracketed paste printf "\e[?2004l" # Disable bracketed paste It's initially off (because the terminal can't assume the program supports it). Konsole apparently understands this (whereas weston-terminal does not). I can verify this by running those commands in bash (which doesn't enable it after every command, at least by default). Apropos terminal support: > Bracketed-paste isn't a Konsole feature, it's a BASH feature It's necessarily a protocol between the two: Something has to bracket the paste, and it's the terminal (that implements pasting) that has a chance to distinguish it from the enter key. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 89299] prevent paste of newline characters
https://bugs.kde.org/show_bug.cgi?id=89299 --- Comment #68 from Andreas Nordal --- > I've noticed and found the new bracketed paste feature quite annoying. What's annoying about that? I would for sure not prefer a popup. That's making a problem out of a non-problem. In fish, when you paste the wrong thing, irrespective of linecount, just press Ctrl+C to not execute. Alternatively, hold down Ctrl+U to erase every line of it. I don't know of a multiline erase, though. Isn't the ideal solution rather that multiline strings just aren't any special, surprising, dangerous or annoying? That's status quo. If the program running in the terminal doesn't support bracketed paste, though, that would be when a popup is warranted. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438744] New: Feature request: Let indentation be indentation when outcommenting lines
https://bugs.kde.org/show_bug.cgi?id=438744
Bug ID: 438744
Summary: Feature request: Let indentation be indentation when
outcommenting lines
Product: kate
Version: 21.04.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: part
Assignee: kwrite-bugs-n...@kde.org
Reporter: andreas_norda...@hotmail.com
Target Milestone: ---
STEPS TO REPRODUCE
1. In Kwrite/Kate/KDevelop, mark the body of this C++ function and press
Ctrl+D:
void f() {
{
;
}
}
EXPECTED RESULT
Preferrably this:
void f() {
// {
// ;
// }
}
Or this (not my favourite, but also fine):
void f() {
// {
// ;
// }
}
OBSERVED RESULT
void f() {
// {
// ;
// }
}
The "// " comment prefix is inserted before, instead of after, the indentation.
I think it would be better to do the opposite – not change the indentation
level of the outcommented code.
This is to make it easy to visually follow the indentation level of an
uncommented block with the surrounding code.
As it is, it is even a bit hard to see which exact indentation level the code
is at when outcommented like this.
Third, it is what automatic code formatters do.
ADDITIONAL INFORMATION
The same applies to probably most languages supported by katepart, with the
notable exception of python, which already does the right thing! Well, the "not
my favourite, but also fine" alternative.
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 433632] Network speed reported incorrectly in system tray icon when first open
https://bugs.kde.org/show_bug.cgi?id=433632 --- Comment #9 from Andreas Nordal --- I found this one, with a similar screenshot to mine: https://bugs.kde.org/show_bug.cgi?id=420365 I'm not sure if there is a difference between these reports, of if I should have submitted there instead. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 433632] Network speed reported incorrectly in system tray icon when first open
https://bugs.kde.org/show_bug.cgi?id=433632 --- Comment #8 from Andreas Nordal --- distro: Opensuse Tumbleweed plasma-nm5 5.21.4-1.1 plasma-framework 5.81.0-1.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 433632] Network speed reported incorrectly in system tray icon when first open
https://bugs.kde.org/show_bug.cgi?id=433632 Andreas Nordal changed: What|Removed |Added CC||andreas_norda...@hotmail.co ||m --- Comment #6 from Andreas Nordal --- Created attachment 137802 --> https://bugs.kde.org/attachment.cgi?id=137802=edit graphed network speed with annotations In the speed graph, it looks like a phallic main spike with two side lobes. If you leave it open, the graph continues with a more realistic speed, but due to scaling, the actual speed is not a pixel above the x-axis until this towering monument has gone out of view. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 435910] New: KDevelop crashed on close [ProblemInlineNoteProvider]
https://bugs.kde.org/show_bug.cgi?id=435910 Bug ID: 435910 Summary: KDevelop crashed on close [ProblemInlineNoteProvider] Product: kdevelop Version: 5.6.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kdevelop (5.6.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.6-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I closed KDevelop (from the task manager (right-click → "Close")). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f7d227dd2e8 in ProblemInlineNoteProvider::~ProblemInlineNoteProvider (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/probleminlinenoteprovider.cpp:85 #5 0x7f7d227e3ab5 in ProblemInlineNoteProvider::~ProblemInlineNoteProvider (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/probleminlinenoteprovider.cpp:83 #6 qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320 #7 qDeleteAll > (c=..., c=...) at /usr/include/qt5/QtCore/qalgorithms.h:328 #8 ProblemReporterPlugin::~ProblemReporterPlugin (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/problemreporterplugin.cpp:111 #9 0x7f7d227e3bf9 in ProblemReporterPlugin::~ProblemReporterPlugin (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/problemreporterplugin.cpp:112 #10 0x7f7d68258d35 in KDevelop::PluginController::unloadPlugin(KDevelop::IPlugin*, KDevelop::PluginController::PluginDeletion) () from /usr/lib64/libKDevPlatformShell.so.56 #11 0x7f7d68258e12 in KDevelop::PluginController::cleanup() () from /usr/lib64/libKDevPlatformShell.so.56 #12 0x7f7d68266781 in KDevelop::Core::cleanup() () from /usr/lib64/libKDevPlatformShell.so.56 #13 0x7f7d68266b84 in KDevelop::Core::shutdown() () from /usr/lib64/libKDevPlatformShell.so.56 #14 0x7f7d6824685f in KDevelop::MainWindow::~MainWindow() () from /usr/lib64/libKDevPlatformShell.so.56 #15 0x7f7d682468c9 in KDevelop::MainWindow::~MainWindow() () from /usr/lib64/libKDevPlatformShell.so.56 #16 0x7f7d6693b10f in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #17 0x7f7d64abb969 in KXmlGuiWindow::event(QEvent*) () from /usr/lib64/libKF5XmlGui.so.5 #18 0x7f7d6768d4ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f7d6690f32a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x7f7d66911d61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #21 0x7f7d66967233 in ?? () from /usr/lib64/libQt5Core.so.5 #22 0x7f7d62f8af57 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x7f7d62f8b2d8 in ?? () from /usr/lib64/libglib-2.0.so.0 #24 0x7f7d62f8b38f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x7f7d669668bf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #26 0x7f7d6690dceb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #27 0x7f7d66915f60 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #28 0x55d28c50a6e6 in main (argc=, argv=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/app/main.cpp:850 [Inferior 1 (process 13193) detached] Possible duplicates by query: bug 435427, bug 434725, bug 434602, bug 434236, bug 434205. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407841] Kdevelop crashes with a segmentation fault when parsing my project
https://bugs.kde.org/show_bug.cgi?id=407841 --- Comment #2 from Andreas Nordal --- I have the same symptom with Kdevelop 5.6.0 – sigsegv when parsing the project. I ran kdevelop in gdb to get the backtrace. I did this 3 times to see if it segfaults at the same place every time, and it seems so: clang::InjectedClassNameType::getDecl in tools/clang/lib/AST/Type.cpp:3387 This happens in an extremely deep recursion inside libclang-10: The two functions TransformTypos::RecursiveTransformLoop and TransformTypos::CheckForRecursiveTypos are running in tandem 23214 or 20548 times (not the same every time) before calling the series of functions that lead to the segfault. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407841] Kdevelop crashes with a segmentation fault when parsing my project
https://bugs.kde.org/show_bug.cgi?id=407841 Andreas Nordal changed: What|Removed |Added CC||andreas_norda...@hotmail.co ||m --- Comment #1 from Andreas Nordal --- Created attachment 131672 --> https://bugs.kde.org/attachment.cgi?id=131672=edit Kdevelop backtrace -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 425178] New: Docker is spewing UdevQt: unhandled device action "move"
https://bugs.kde.org/show_bug.cgi?id=425178 Bug ID: 425178 Summary: Docker is spewing UdevQt: unhandled device action "move" Product: frameworks-solid Version: 5.72.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: lu...@kde.org Reporter: andreas_norda...@hotmail.com CC: kdelibs-b...@kde.org Target Milestone: --- While running `docker build`, this error message appears multiple times: UdevQt: unhandled device action "move" STEPS TO REPRODUCE 1. Put this in a Dockerfile in its own directory: FROM alpine:3.8 RUN echo hello RUN echo world 2. Run `docker build .` from within the directory OBSERVED RESULT Sending build context to Docker daemon 2.048kB Step 1/3 : FROM alpine:3.8 ---> c8bccc0af957 Step 2/3 : RUN echo hello ---> Running in b2857dfcbb26 hello UdevQt: unhandled device action "move" Removing intermediate container b2857dfcbb26 ---> 75635d880095 Step 3/3 : RUN echo world ---> Running in 8718e2e15b17 world UdevQt: unhandled device action "move" Removing intermediate container 8718e2e15b17 ---> 84fa6aaab150 Successfully built 84fa6aaab150 EXPECTED RESULT The «UdevQt: unhandled device action "move"» lines should obviously not be there. ADDITIONAL INFORMATION The message comes from /usr/lib64/libKF5Solid.so.5.72.0. The only other occurrence of the error message on my system is in /usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so, but by editing both binaries, I could determine that it was from Solid. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 425163] New: Kate is spewing kf5.kio.kdirmodel: protocol mismatch: "" vs "file"
https://bugs.kde.org/show_bug.cgi?id=425163 Bug ID: 425163 Summary: Kate is spewing kf5.kio.kdirmodel: protocol mismatch: "" vs "file" Product: frameworks-kio Version: 5.72.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Annoying error message in the terminal. STEPS TO REPRODUCE touch file.txt && kate file.txt OBSERVED RESULT kf5.kio.kdirmodel: protocol mismatch: "" vs "file" EXPECTED RESULT SOFTWARE/OS VERSIONS kate 20.04.3 openSUSE Tumbleweed 20200807 KDE Plasma Version: 5.19 KDE Frameworks Version: 5.72.0 Qt Version: 5.15 ADDITIONAL INFORMATION Kwrite does not suffer from this. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 89299] prevent paste of newline characters
https://bugs.kde.org/show_bug.cgi?id=89299 --- Comment #58 from Andreas Nordal --- Nobody mentioning bracketed paste? https://web.archive.org/web/20190806043517/https://cirw.in/blog/bracketed-paste That's the final solution to all world problems, and Konsole supports it. Just use a shell that also supports it, like fish. Then, you can paste multiline strings in complete safety and bliss, and they won't execute until you physically hit enter. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 421120] New: Kdevelop crashed while typing if statement in C++
https://bugs.kde.org/show_bug.cgi?id=421120 Bug ID: 421120 Summary: Kdevelop crashed while typing if statement in C++ Product: kdevelop Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kdevelop (5.5.0) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.6-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was writing an if statement, and when I had written the opening curly brace and a line feed, Kdevelop crashed. Reproducibility: Low. I have only had this a couple of times in about a month, and I'm using Kdevelop every day. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6713d9fcc0 (LWP 13448))] Thread 23 (Thread 0x7f66dcf47700 (LWP 15499)): #0 0x7f672309a4fc in read () from /lib64/libc.so.6 #1 0x7f67163a00f1 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #2 0x7f67172e0a0e in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #3 0x7f67172e14b0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f67172e1570 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f67172ef439 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f67163cdd78 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f6720755efa in start_thread () from /lib64/libpthread.so.0 #8 0x7f67230a93bf in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f66b27fc700 (LWP 13720)): #0 0x7f672075c795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f67234231db in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x7f6723423299 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #3 0x7f671fcdd6b0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f671fcdda1a in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #24 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #25 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #26 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #27 0x7f671fcd5cce in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #28 0x7f671fcdda71 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #29 0x7f671fcd5cce in
[plasmashell] [Bug 408247] New: [Dual monitor, powersave] taskbar showing windows from the wrong screen
https://bugs.kde.org/show_bug.cgi?id=408247 Bug ID: 408247 Summary: [Dual monitor, powersave] taskbar showing windows from the wrong screen Product: plasmashell Version: 5.15.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: andreas_norda...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I come back to the computer after the screens have turned off, some times both task managers only show the windows of the left screen, or only the windows of the right screen, despite being configured to show the windows from their respective screens. Reproducibility: 1/10 (guesstimate). STEPS TO REPRODUCE 1. Have 2 screens permanently connected. 2. Have 2 panels, one on each screen. 3. Configure each panel's task manager to only show windows from their own screens. 4. Turn both screens off, or enable screen power saving and wait for them to do it themselves. 5. Turn both screens on, or in the screen power saving case, wiggle the mouse or whatever for them to come on. OBSERVED RESULT Some times, both task managers only show windows from the left screen, and some times both only show windows from the right screen, and some times they show the windows from their own screens. In this botched state, the phenomenon does not go away if I disable and re-enable the setting to only show windows from the same screen – looks like the affected task manager "thinks" it's on the other screen! What works to resolve the botched state, is to turn both monitors off and on as simultaneously as possible. It often takes a couple of tries. EXPECTED RESULT Each task manager should show the windows from their own screen, as configured. SOFTWARE/OS VERSIONS OpenSuse Tumbleweed KDE Frameworks 5.57.0 Qt 5.12.2 plasma5desktop-5.15.4-1.1 ADDITIONAL INFORMATION 1. This bug is at least as old as this computer (december 2015). 2. My screens are identical (Dell), both connected via Displayport to the same Intel IGP. 3. An even rarer phenomenon that also happens in the same scenario is that one screen doesn't turn on. In this case, I can wake the unwilling screen up by going into the Linux console (Ctrl+Alt+F1) and start Weston (`weston-launch`). Then, if I quickly go back to X (Alt+F7), the screens will flicker briefly, but remain on. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401559] New: FFplay crashes KWin reliably
https://bugs.kde.org/show_bug.cgi?id=401559 Bug ID: 401559 Summary: FFplay crashes KWin reliably Product: kwin Version: 5.14.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kwin_x11 (5.14.3) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Play any video with ffplay. Works every time. I'm using OpenSuse Tumbleweed. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9adf1d9d00 (LWP 2845))] Thread 6 (Thread 0x7f9ac4ed7700 (LWP 2967)): #0 0x7f9ae55644dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9ae604d01a in () at /usr/lib64/libQt5Script.so.5 #2 0x7f9ae604d03b in () at /usr/lib64/libQt5Script.so.5 #3 0x7f9ae555e554 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9ae7bdeccf in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9ac7306700 (LWP 2949)): #0 0x7f9ae55644dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9ac774df5b in () at /usr/lib64/dri/i965_dri.so #2 0x7f9ac774dc87 in () at /usr/lib64/dri/i965_dri.so #3 0x7f9ae555e554 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9ae7bdeccf in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9ad5de5700 (LWP 2938)): #0 0x7f9ae7bd43c6 in ppoll () at /lib64/libc.so.6 #1 0x7f9ae6739ac1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9ae673af39 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f9ae66eaadb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9ae6539de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f9ae4d77485 in () at /usr/lib64/libQt5Qml.so.5 #6 0x7f9ae65439b7 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f9ae555e554 in start_thread () at /lib64/libpthread.so.0 #8 0x7f9ae7bdeccf in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f9ad7cd0700 (LWP 2891)): #0 0x7f9ae7bd43c6 in ppoll () at /lib64/libc.so.6 #1 0x7f9ae6739ac1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f9ae673af39 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #3 0x7f9ae66eaadb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9ae6539de6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #5 0x7f9ae4848545 in () at /usr/lib64/libQt5DBus.so.5 #6 0x7f9ae65439b7 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f9ae555e554 in start_thread () at /lib64/libpthread.so.0 #8 0x7f9ae7bdeccf in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f9adcffa700 (LWP 2886)): #0 0x7f9ae7bd42c9 in poll () at /lib64/libc.so.6 #1 0x7f9ae80eecc7 in () at /usr/lib64/libxcb.so.1 #2 0x7f9ae80f08ea in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f9add4f8519 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f9ae65439b7 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f9ae555e554 in start_thread () at /lib64/libpthread.so.0 #6 0x7f9ae7bdeccf in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f9adf1d9d00 (LWP 2845)): [KCrash Handler] #6 0x7f9ae7b1c08b in raise () at /lib64/libc.so.6 #7 0x7f9ae7b054e9 in abort () at /lib64/libc.so.6 #8 0x7f9ae7b053c1 in _nl_load_domain.cold.0 () at /lib64/libc.so.6 #9 0x7f9ae7b146f2 in () at /lib64/libc.so.6 #10 0x7f9ae545343f in () at /usr/lib64/libepoxy.so.0 #11 0x7f9ae5428f8a in () at /usr/lib64/libepoxy.so.0 #12 0x7f9ae54d50ac in KWin::GLRenderTarget::~GLRenderTarget() () at /usr/lib64/libkwinglutils.so.11 #13 0x7f9ae61cb4ad in () at /usr/lib64/libkwin4_effect_builtins.so.1 #14 0x7f9ae61cda37 in () at /usr/lib64/libkwin4_effect_builtins.so.1 #15 0x7f9ae61cdc19 in () at /usr/lib64/libkwin4_effect_builtins.so.1 #16 0x7f9ae776957a in KWin::EffectsHandlerImpl::unloadAllEffects() () at /usr/lib64/libkwin.so.5 #17 0x7f9ae7769607 in KWin::EffectsHandlerImpl::~EffectsHandlerImpl() () at /usr/lib64/libkwin.so.5 #18 0x7f9ad74ab008 in () at /usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so #19 0x7f9ad74ab0d9 in () at /usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so #20 0x7f9ae774aa8f in () at /usr/lib64/libkwin.so.5 #21 0x7f9ae774b01c in KWin::Compositor::suspend(KWin::Compositor::SuspendReason) () at
[kdevelop] [Bug 398903] New: KDevelop: Another crash when opening project
https://bugs.kde.org/show_bug.cgi?id=398903 Bug ID: 398903 Summary: KDevelop: Another crash when opening project Product: kdevelop Version: 5.2.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kdevelop (5.2.4) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: KDevelop crashed after reopening project after previous crash. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f69a85e89c0 (LWP 14858))] Thread 21 (Thread 0x7f693700 (LWP 15048)): #0 0x7f69b400e8c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f69b77a30fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f69b779af62 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f69b77a2a67 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f69b4008554 in start_thread () at /lib64/libpthread.so.0 #5 0x7f69b7282ccf in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f6960ff9700 (LWP 15020)): #0 0x7f69b400e4dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f69b77a321b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f69b30cd800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f69b30d1538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f69b30cc90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f69b30d1592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f69b30cc90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f69b30cf689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f69b77a2a67 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f69b4008554 in start_thread () at /lib64/libpthread.so.0 #10 0x7f69b7282ccf in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f6961ffb700 (LWP 15018)): #0 0x7f69b400e4dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f69b77a321b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f69b30cd800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f69b30d1538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f69b30cc90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f69b30d1592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f69b30cc90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f69b30cf689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f69b77a2a67 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f69b4008554 in start_thread () at /lib64/libpthread.so.0 #10 0x7f69b7282ccf in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f69627fc700 (LWP 15017)): #0 0x7f69b400e4dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f69b77a321b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f69b30cd800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f69b30d1538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f69b30cc90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f69b30d1592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f69b30cc90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f69b30cf689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f69b77a2a67 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f69b4008554 in start_thread () at /lib64/libpthread.so.0 #10 0x7f69b7282ccf in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f6962ffd700 (LWP 15016)): #0 0x7f69b400e4dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f69b77a321b in QWaitCondition::wait(QMutex*, unsigned long) () at
[kdevelop] [Bug 398902] New: KDevelop crashes intermittently.
https://bugs.kde.org/show_bug.cgi?id=398902 Bug ID: 398902 Summary: KDevelop crashes intermittently. Product: kdevelop Version: 5.2.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kdevelop (5.2.4) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Switching tabs back and forth. Code indexing was happening in the background. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe49b0089c0 (LWP 28292))] Thread 21 (Thread 0x7fe43a31b700 (LWP 28456)): #0 0x7fe4a9c93d34 in read () at /lib64/libc.so.6 #1 0x7fe4a5b9f6f0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe4a5b5acdf in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe4a5b5b1b0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe4a5b5b32c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe4aa3bd0bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe4aa36a09b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fe4aa1b8e96 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fe4a8ad808c in () at /usr/lib64/libKDevPlatformLanguage.so.52 #9 0x7fe4aa1c2a67 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fe4a6a28554 in start_thread () at /lib64/libpthread.so.0 #11 0x7fe4a9ca2ccf in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7fe43bfff700 (LWP 28455)): [KCrash Handler] #6 0x00e1 in () #7 0x7fe46810a3e0 in clang::ASTUnit::~ASTUnit() () at /usr/lib64/../lib64/libclangFrontend.so.6 #8 0x7fe46811a412 in () at /usr/lib64/../lib64/libclangFrontend.so.6 #9 0x7fe4311f38d1 in llvm::CrashRecoveryContext::~CrashRecoveryContext() () at /usr/lib64/../lib64/libLLVM.so.6 #10 0x7fe46854bc7e in clang_parseTranslationUnit2FullArgv () at /usr/lib64/libclang.so.6 #11 0x7fe46854b8e9 in clang_parseTranslationUnit2 () at /usr/lib64/libclang.so.6 #12 0x7fe46864e30e in ParseSessionData::ParseSessionData(QVector const&, ClangIndex*, ClangParsingEnvironment const&, QFlags) () at /usr/lib64/libKDevClangPrivate.so.30 #13 0x7fe46a16d353 in () at /usr/lib64/qt5/plugins/kdevplatform/30/kdevclangsupport.so #14 0x7fe46a16f413 in () at /usr/lib64/qt5/plugins/kdevplatform/30/kdevclangsupport.so #15 0x7fe4a5af07ea in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7fe4a5af0d58 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7fe4a5aefc60 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7fe4a5aef73b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7fe4aa1c2a67 in () at /usr/lib64/libQt5Core.so.5 #20 0x7fe4a6a28554 in start_thread () at /lib64/libpthread.so.0 #21 0x7fe4a9ca2ccf in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fe458ff9700 (LWP 28454)): #0 0x7fe4a6a2e8c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe4aa1c30fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe4abcfa2cb in KDevelop::ForegroundLock::relock() () at /usr/lib64/libKDevPlatformUtil.so.52 #3 0x7fe4a89a532f in KDevelop::ParseJob::translateDUChainToRevision(KDevelop::TopDUContext*) () at /usr/lib64/libKDevPlatformLanguage.so.52 #4 0x7fe4697171ef in () at /usr/lib64/qt5/plugins/kdevplatform/30/kdevqmljslanguagesupport.so #5 0x7fe4a5af07ea in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fe4a5af0d58 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fe4a5aefc60 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fe4a5aef73b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7fe4aa1c2a67 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fe4a6a28554 in start_thread () at /lib64/libpthread.so.0 #11 0x7fe4a9ca2ccf in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fe4597fa700 (LWP 28453)): #0 0x7fe4a6a2e4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
[kdevelop] [Bug 398897] New: KDevelop crashed after opening project
https://bugs.kde.org/show_bug.cgi?id=398897 Bug ID: 398897 Summary: KDevelop crashed after opening project Product: kdevelop Version: 5.2.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kdevelop (5.2.4) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: KDevelop was not following the include directories I had set up for the project, so I right-clicked one of the includes that were not found and followed the dialog to open the project. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7e298289c0 (LWP 3468))] Thread 21 (Thread 0x7f7db495f700 (LWP 28214)): #0 0x7f7e3524e8c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7e389e30fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7e389daf62 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f7e389e2a67 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f7e35248554 in start_thread () at /lib64/libpthread.so.0 #5 0x7f7e384c2ccf in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f7dda7fc700 (LWP 3630)): #0 0x7f7e3524e4dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7e389e321b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7e3430d800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f7e34311538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f7e3430f689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f7e389e2a67 in () at /usr/lib64/libQt5Core.so.5 #11 0x7f7e35248554 in start_thread () at /lib64/libpthread.so.0 #12 0x7f7e384c2ccf in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f7ddaffd700 (LWP 3629)): #0 0x7f7e3524e4dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7e389e321b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f7e3430d800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f7e34311538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f7e3430c90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f7e34311592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #20
