[kdenlive] [Bug 375691] New: Crash on most "deshake" values for "rx" / "ry"
https://bugs.kde.org/show_bug.cgi?id=375691 Bug ID: 375691 Summary: Crash on most "deshake" values for "rx" / "ry" Product: kdenlive Version: 16.08.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: rip...@freakmail.de Target Milestone: --- (Possibly related to https://bugs.kde.org/show_bug.cgi?id=364531 ?) Application: kdenlive (16.08.2) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I used a short (hand-filmed) video clip (2048x1162) in a Full-HD project in Kdenlive. I then applied the "deshake" filter to the video and set "rx" and "ry" to 24 (other settings unchanged). When the preview is supposed to be updated (e.g. by clicking on some time in the timeline), Kdenlive crashes. If I set "rx" and "ry" to 16 or 32, Kdenlive does not crash. I also tried "8" and "20" both do crash Kdenlive. If I'm reading http://ffmpeg.org/ffmpeg-filters.html#deshake correctly (and if I am correct that Kdenlive deshake == ffmpeg deshake), valid values are 0-64. BTW: The default for rx and ry is "16" according to the website, but is set to "0" in Kdenlive - I don't know if that's on purpose or not. The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efc08af9900 (LWP 3397))] Thread 14 (Thread 0x7efb77ffe700 (LWP 3445)): #0 0x7efbff67a0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7efbd95e4bdb in worker (v=0x7efba0a61a00) at libavfilter/pthread.c:73 #2 0x7efbff675734 in start_thread () from /lib64/libpthread.so.0 #3 0x7efc00f5ad3d in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7efb8700 (LWP 3444)): #0 0x7efbff67a0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7efbd95e4bdb in worker (v=0x7efba0a61a00) at libavfilter/pthread.c:73 #2 0x7efbff675734 in start_thread () from /lib64/libpthread.so.0 #3 0x7efc00f5ad3d in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7efbac663700 (LWP 3443)): #0 0x7efbff67a0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7efbd95e4bdb in worker (v=0x7efba0a61a00) at libavfilter/pthread.c:73 #2 0x7efbff675734 in start_thread () from /lib64/libpthread.so.0 #3 0x7efc00f5ad3d in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7efba51a8700 (LWP 3442)): #0 0x7efbff67a0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7efbd95e4bdb in worker (v=0x7efba0a61a00) at libavfilter/pthread.c:73 #2 0x7efbff675734 in start_thread () from /lib64/libpthread.so.0 #3 0x7efc00f5ad3d in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7efba7ffe700 (LWP 3441)): #0 0x7efbff67a0af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7efbd95e4bdb in worker (v=0x7efba0a61a00) at libavfilter/pthread.c:73 #2 0x7efbff675734 in start_thread () from /lib64/libpthread.so.0 #3 0x7efc00f5ad3d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7efba73b9700 (LWP 3440)): [KCrash Handler] #6 ff_pixelutils_sad_u_16x16_sse2 () at libavutil/x86/pixelutils.asm:165 #7 0x7efbd96093a2 in find_block_motion (mv=, stride=1920, cy=24, cx=24, src2=0x7efb6b767360 "\265\307\320\314\315\320\324\334\337\334\326\277\276\276\304\316\323\327\333\337\343\351\342\342\340\340\342\342\343\346\354\357\363\366\371\371\370\366\365\363\362\361\363\360\352\366\355\350\353\351\345\320\311\313\333\355\361\352\345\355\355\360\366\372\372\372\372\372\372\372\373\373\370\362\357\352\322\310\331\362\367\370\367\367", '\366' , "\364\363\357\353\337\300\254\225\215\204}\213\244\322\347\347\350\355\357\341\310\267\260\256\255\253\277\323\346\357\363\363\363\363\362\363\365\373\375\377\377\377\377\377\375\375\371\363\355\353\354\357\346\326\311\266\226\202sb\\\205\255\331\355\352\346\335\330\312\274\240\217}\200\201\204\216\222\211|w\204\222\234\240\247\254\273\302\310\325\336\350\355\354\347\334\324\311\302\310\324\370"..., src1=0x7efb6b767360 "\265\307\320\314\315\320\324\334\337\334\326\277\276\276\304\316\323\327\333\337\343\351\342\342\340\340\342\342\343\346\354\357\363\366\371\371\370\366\365\363\362\361\363\360\352\366\355\350\353\351\345\320\311\313\333\355\361\352\345\355\355\360\366\372\372\372\372\372\372\372\373\373\370\362\357\352\322\310\331\362\367\370\367\367", '\366' ,
[kpat] [Bug 326932] Solver reports winnable game 1268426203 as unwinnable
https://bugs.kde.org/show_bug.cgi?id=326932 --- Comment #4 from Martin Riethmayer <rip...@freakmail.de> --- Sorry for the extremely late comment: when loading the game, Kpatience (3.6, KF 5.33, Qt 5.7.1) on KDE Neon User stable (Plasma 5.9.5) still reports the saved game as unwinnable. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369573] kdevelop consumes all available memory when editing js file [QmlJS::NodeJS::moduleDirectories]
https://bugs.kde.org/show_bug.cgi?id=369573 --- Comment #14 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 105695 --> https://bugs.kde.org/attachment.cgi?id=105695=edit Heaptrack of KDevelop with remote JS file As requested by Milian Wolff on https://bugs.kde.org/show_bug.cgi?id=367893 I've added a heaptrack. Hope this helps? This is a very small JS file, it seems the background parser seems to run wild again after clicking here and there. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369573] kdevelop consumes all available memory when editing js file [QmlJS::NodeJS::moduleDirectories]
https://bugs.kde.org/show_bug.cgi?id=369573 --- Comment #16 from Martin Riethmayer <rip...@freakmail.de> --- Here's the heaptrack with debug symbols: http://bit.ly/2qP7Otc The increase in memory usage did not start until I made the first change to the JS file (increased a timeout from 2500 to 25000). I did not press "Save", just as soon as I hit the "0" the memory increase seemed to start. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369573] kdevelop consumes all available memory when editing js file [QmlJS::NodeJS::moduleDirectories]
https://bugs.kde.org/show_bug.cgi?id=369573 Martin Riethmayer <rip...@freakmail.de> changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #12 from Martin Riethmayer <rip...@freakmail.de> --- *** Bug 367893 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background
https://bugs.kde.org/show_bug.cgi?id=367893 Martin Riethmayer <rip...@freakmail.de> changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #5 from Martin Riethmayer <rip...@freakmail.de> --- This is most likely a duplicate of https://bugs.kde.org/show_bug.cgi?id=369573 as this also happens for me on remote file systems only. I'll try to provide a heaptrack at the other report. Sorry for the delayed reply. *** This bug has been marked as a duplicate of bug 369573 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369573] kdevelop consumes all available memory when editing js file [QmlJS::NodeJS::moduleDirectories]
https://bugs.kde.org/show_bug.cgi?id=369573 --- Comment #18 from Martin Riethmayer <rip...@freakmail.de> --- Sorry, no debug symbols for kdevqmljs seem to be available on KDE Neon DEV stable. Most simple steps to reproduce: 1.) Create a file "test.js" on a remote server 2.) Enter the text "var tmp = 2500;" (without the quotes) (or any other text) 3.) Open KDevelop 4.) Via SFTP or FISH, open that file 5.) Insert a "0" (so change 2500 => 25000) (or make any other change) Expected result: Nothing really should happen Actual result: Memory usage goes through the roof until KDevelop crashes System info: KDE Neon DEV stable (updated 2017-05-29) KDevelop 5.1.1 KDE Frameworks 5.35 Qt 5.7.1 Additional info: This has happened to me also on older versions of KDevelop and other distros. I've not yet encountered this problem with other file-types (e.g. php, css...). Workaround: disable background-parser. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394819] Can't activate kickoff menu if mouse at corner of screen
https://bugs.kde.org/show_bug.cgi?id=394819 --- Comment #7 from Martin Riethmayer --- I think this is a different issue than bug 387775 though. In that bug, the problem is the screen edges and screen corners. In this case, the problem is from "shadows" that are still applied even though compositing is turned off thus actually leaving gaps and visual glitches in the panel. See esp. attachment 112943 - the red rectangle should not be visible right of the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394819] Can't activate kickoff menu if mouse at corner of screen
https://bugs.kde.org/show_bug.cgi?id=394819 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #5 from Martin Riethmayer --- I was able to reproduce this on a clean install : 1.) Disable compositing (e.g. by pressing Alt+Shift+F12) 2.) Move the panel to the left screen edge -> Notice that there's already some space at the bottom of the panel 3.) Move the panel to the top screen edge -> Notice that there's now a space between the panel itself and the area where the width could be changed 4.) Move the panel back to the bottom screen edge -> There's now a couple of pixels on the screen bottom without a panel. As soon as you turn compositing back on, it looks good again and works as expected. If you turn off compositing again, the issue reported is visible and in effect. My guess (without looking at the source): when compositing is off, there's still some "shadow" margin or padding calculated for "left panel" (probably also "right panel") and "top panel" which will persist even after moving back to the "bottom panel". -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 375691] Crash on most "deshake" values for "rx" / "ry"
https://bugs.kde.org/show_bug.cgi?id=375691 Martin Riethmayer changed: What|Removed |Added Version|16.08.2 |18.04.0 Platform|openSUSE RPMs |Neon Packages --- Comment #2 from Martin Riethmayer --- Still crashing in Kdenlive 17.11.80 on KDE Neon User: KDE Plasma 5.12.2 KDE FW: 5.48.0 Qt: 5.11.0 Kernel: 4.13.0 Also crashing in Kdenliv 18.03.70 on KDE Neon Git unstable as of today: KDE Plasma 5.13.80 KDE FW: 5.48.0 Qt: 5.11.0 Kernel: 4.13.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394819] Can't activate kickoff menu if mouse at corner of screen
https://bugs.kde.org/show_bug.cgi?id=394819 --- Comment #8 from Martin Riethmayer --- This seems to be fixed, might be thanks to https://phabricator.kde.org/R242:412a517576d5505c9f700f13b8f33257c07e220d (see also https://bugs.kde.org/show_bug.cgi?id=389215 ) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401236] New: Kipi Plugins not detected
https://bugs.kde.org/show_bug.cgi?id=401236 Bug ID: 401236 Summary: Kipi Plugins not detected Product: gwenview Version: Other (add details in bug description) Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: rip...@freakmail.de Target Milestone: --- SUMMARY On the KDE Neon Dev Stable edition, the KIPI-plugins seem not be detected by gwenview Gwenview is reported at version 18.11.80 STEPS TO REPRODUCE 1. Install Kipi plugins (apt install kipi-plugins) 2. Open Gwenview 3. Open "Plugins"-Menu OBSERVED RESULT Only option is "Install Plugins" EXPECTED RESULT Kipi Plugins should be available SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Dev Stable (available in About System) KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION When clicking on the "Install Plugins" in the Menu, Discover opens with an error message: "Couldn't open appstream://photolayoutseditor.desktop" -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401236] Kipi Plugins not detected
https://bugs.kde.org/show_bug.cgi?id=401236 Martin Riethmayer changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #2 from Martin Riethmayer --- Hi Nate, thanks for taking a look into this. I don't think the bug report itself is a dup of 391669 - only the "Additional Information" part seems to be. The actual bug report is about the installed Kipi plugins not being visible in Gwenview. Maybe I should have reported this in two different reports. I've reopened the bug, if you think this is still due to the missing Appstream metadata, feel free to ignore me and close it again! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401236] Installed Kipi Plugins not detected
https://bugs.kde.org/show_bug.cgi?id=401236 Martin Riethmayer changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Martin Riethmayer --- I can still reproduce this on Neon Dev Stable: Gwenview does not show any KIPI plugins. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Dev Stable (available in About System) KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 Gwenview: 18.12.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408300] New: Color schemes grid view doesn't scroll after mouse-wheel-induced change of displayed schemes
https://bugs.kde.org/show_bug.cgi?id=408300 Bug ID: 408300 Summary: Color schemes grid view doesn't scroll after mouse-wheel-induced change of displayed schemes Product: systemsettings Version: 5.15.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: mwoehlke.fl...@gmail.com Reporter: rip...@freakmail.de CC: jpwhit...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open the system settings, go to colors KCM 2. With the mouse wheel(!), change the displayed schemes from "All Schemes" to "Light Schemes" or "Dark Schemes" 3. Try to scroll the grid view with the mouse wheel (either after only moving the mouse to the grid view or after clicking into the grid view) OBSERVED RESULT The grid view doesn't scroll EXPECTED RESULT The grid view should scroll SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon Unstable Edition (available in About System) KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408571] New: Bouncing cursor doesn't stop after opening new location as Tab in dolphin
https://bugs.kde.org/show_bug.cgi?id=408571 Bug ID: 408571 Summary: Bouncing cursor doesn't stop after opening new location as Tab in dolphin Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: rip...@freakmail.de Target Milestone: --- Since Plasma 5.16, folders (or other locations) are opened inside a new Tab in dolphin (previously it was opened as a new Window). The bouncy cursor does not stop bouncing, however, after the Tab is open. This happens in other applications, that will open new tabs (e.g. this also happens when you for example open a text document and Kate is already open) STEPS TO REPRODUCE 1. Open a folder in dolphin 2. Open another folder in dolphin (which will create a new Tab in the first dolphin window) (Same goes for: 1.) Open document in Kate, 2.) Open another document with Kate (will create new Tab) OBSERVED RESULT Bouncing cursor will remain bouncing for a while EXPECTED RESULT Bouncing cursor should stop bouncing as soon as there is nothing more to wait for (i.e. the tab has been opened and the appropriate content has been displayed). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon Git unstable (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION You can see the behaviour in https://cdn.kde.org/promo/20190611_Plasma5.16/dolphin_cut.mp4.gif (linked from the 5.16.0 release announcement) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408571] Bouncing cursor doesn't stop after opening new Tab (e.g. dolphin when opening a second folder, kate when opening second document...)
https://bugs.kde.org/show_bug.cgi?id=408571 Martin Riethmayer changed: What|Removed |Added Summary|Bouncing cursor doesn't |Bouncing cursor doesn't |stop after opening new |stop after opening new Tab |location as Tab in dolphin |(e.g. dolphin when opening ||a second folder, kate when ||opening second document...) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 414102] New: KMail crashes when trying to open E-Mail
https://bugs.kde.org/show_bug.cgi?id=414102 Bug ID: 414102 Summary: KMail crashes when trying to open E-Mail Product: kontact Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rip...@freakmail.de Target Milestone: --- Application: kontact (5.10.3) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.25-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: I tried to open an email with PDF attachments. From a very short glance at the backtrace, it seems like the crash might be inside the parsing of KItenary? Sorry, I cannot attach the PDFs due to privacy reasons. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8ac4d03900 (LWP 17439))] Thread 29 (Thread 0x7f896f6fe700 (LWP 17517)): #0 0x7f8abb2baaf2 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8abb2bb150 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8abb2bb2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8ac21b196b in QEventDispatcherGlib::processEvents (this=0x7f896cb0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f8ac215690a in QEventLoop::exec (this=this@entry=0x7f896f6fdcb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f8ac1f74daa in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f8ac1f79ced in QThreadPrivate::start (arg=0x555c2804ffe0) at thread/qthread_unix.cpp:368 #7 0x7f8abd174569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f8ac165e9ef in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f896feff700 (LWP 17514)): #0 0x7f8abd17a8ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f8ab1e6ec45 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f8ab1e6f127 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f8ab1e6fec1 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f8ab1e6c55b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f8abd174569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f8ac165e9ef in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f897cb6f700 (LWP 17480)): #0 0x7f8ac164fc98 in read () from /lib64/libc.so.6 #1 0x7f8abb2ffca0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8abb2bacb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8abb2bb150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8abb2bb2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f8ac21b196b in QEventDispatcherGlib::processEvents (this=0x7f8978000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f8ac215690a in QEventLoop::exec (this=this@entry=0x7f897cb6ecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f8ac1f74daa in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f8ac1f79ced in QThreadPrivate::start (arg=0x555c24e3b910) at thread/qthread_unix.cpp:368 #9 0x7f8abd174569 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8ac165e9ef in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f898e8b2700 (LWP 17472)): #0 0x7f8ac164fc98 in read () from /lib64/libc.so.6 #1 0x7f8abb2ffca0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8abb2bacb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8abb2bb150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8abb2bb2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f8ac21b196b in QEventDispatcherGlib::processEvents (this=0x7f8984000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f8ac215690a in QEventLoop::exec (this=this@entry=0x7f898e8b1cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f8ac1f74daa in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f8ac1f79ced in QThreadPrivate::start (arg=0x555c24d163a0) at thread/qthread_unix.cpp:368 #9 0x7f8abd174569 in start_thread () from /lib64/libpthread.so.0 #10 0x7f8ac165e9ef in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7f898f0b3700 (LWP 17471)): #0 0x7f8abb300ff4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8abb2ba6a9 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8abb2bb0db in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8abb2bb2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8ac21b196b in QEventDispatcherGlib::processEvents (this=0x7f898b10, flags=...) at
[kontact] [Bug 414102] KMail crashes when trying to open E-Mail
https://bugs.kde.org/show_bug.cgi?id=414102 --- Comment #1 from Martin Riethmayer --- Maybe it's time to upgrade my KDE Applications: the error does not occur on KDE Neon, Plasma 5.17.2, Kontact 5.12.3, Qt 5.13.1, KDE FW 5.63.0 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 414102] KMail crashes when trying to open E-Mail
https://bugs.kde.org/show_bug.cgi?id=414102 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 414102] KMail crashes when trying to open E-Mail
https://bugs.kde.org/show_bug.cgi?id=414102 --- Comment #2 from Martin Riethmayer --- Created attachment 123997 --> https://bugs.kde.org/attachment.cgi?id=123997=edit New crash information added by DrKonqi kontact (5.12.3) using Qt 5.13.1 - What I was doing when the application crashed: Sorry, I had this not happen on Neon, but updating Leap 15.1 to the current KDE FW, Apps and Plasma release does not help. This is still crashing every time I'm trying to open a specific mail with PDF attachments -- Backtrace (Reduced): #7 0x7f1c0548ae83 in opj_destroy_codec () from /usr/lib64/libopenjp2.so.7 #8 0x7f1c05b7e5c4 in JPXStreamPrivate::init2 (this=0x55cfd0c21140, format=format@entry=OPJ_CODEC_JP2, buf=buf@entry=0x55cfd1032a00 "", length=length@entry=1999, indexed=indexed@entry=false) at /usr/src/debug/poppler-0.81.0-lp151.8.1.x86_64/poppler/JPEG2000Stream.cc:361 #9 0x7f1c05b7ea60 in JPXStream::init (this=this@entry=0x55cfd10097e0) at /usr/src/debug/poppler-0.81.0-lp151.8.1.x86_64/poppler/JPEG2000Stream.cc:235 #10 0x7f1c05b7f086 in JPXStream::getImageParams (this=0x55cfd10097e0, bitsPerComponent=0x7ffc6ccfe518, csMode=0x7ffc6ccfe51c) at /usr/src/debug/poppler-0.81.0-lp151.8.1.x86_64/poppler/JPEG2000Stream.cc:140 #11 0x7f1c05a8f09f in Gfx::doImage (this=this@entry=0x55cfd0bc5d10, ref=ref@entry=0x7ffc6ccfec70, str=0x55cfd10097e0, inlineImg=inlineImg@entry=false) at /usr/src/debug/poppler-0.81.0-lp151.8.1.x86_64/poppler/Gfx.cc:4220 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 304552] add multi-page scanning option
https://bugs.kde.org/show_bug.cgi?id=304552 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 299517] Skanlite should support scan to pdf.
https://bugs.kde.org/show_bug.cgi?id=299517 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 Martin Riethmayer changed: What|Removed |Added CC||k...@kn0x.org --- Comment #15 from Martin Riethmayer --- *** Bug 417423 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 Martin Riethmayer changed: What|Removed |Added CC||m...@iyanmv.com --- Comment #13 from Martin Riethmayer --- *** Bug 417474 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417474] Fonts configuration broken
https://bugs.kde.org/show_bug.cgi?id=417474 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Riethmayer --- *** This bug has been marked as a duplicate of bug 416358 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417450] Apply Button is not clickable in fonts config page
https://bugs.kde.org/show_bug.cgi?id=417450 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Riethmayer --- *** This bug has been marked as a duplicate of bug 416358 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 Martin Riethmayer changed: What|Removed |Added CC||talent...@hotmail.com --- Comment #14 from Martin Riethmayer --- *** Bug 417450 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417423] Can't apply fonts
https://bugs.kde.org/show_bug.cgi?id=417423 Martin Riethmayer changed: What|Removed |Added Status|REPORTED|RESOLVED CC||rip...@freakmail.de Resolution|--- |DUPLICATE --- Comment #4 from Martin Riethmayer --- *** This bug has been marked as a duplicate of bug 416358 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419172] Baloo crash on login
https://bugs.kde.org/show_bug.cgi?id=419172 Martin Riethmayer changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Martin Riethmayer --- Thanks, fixed -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 419446] New: Newer VirtualBox guest additions needed
https://bugs.kde.org/show_bug.cgi?id=419446 Bug ID: 419446 Summary: Newer VirtualBox guest additions needed Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: rip...@freakmail.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Wit the guest additions shipped with Neon, it's not possible to resize the VirtualBox guest after a default installation. The issue is that the default graphics adapter is VMSVGA, which is only supported in newer GuestAdditions (according to several forum topics e.g. [1] [2] ) STEPS TO REPRODUCE 1. Install Neon User Edition in VirtualBox with default settings (except larger HDD) 2. Try to resize the window after installation OBSERVED RESULT Impossible to resize (Note: It's possible to resize after switching the graphics adapter to VBoxSVGA, which is not recommended for Linux guests) EXPECTED RESULT Window should resize ADDITIONAL INFORMATION [1] https://forums.virtualbox.org/viewtopic.php?f=3=93668 [2] https://forums.virtualbox.org/viewtopic.php?f=3=94889 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 419446] Newer VirtualBox guest additions needed
https://bugs.kde.org/show_bug.cgi?id=419446 Martin Riethmayer changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED|RESOLVED --- Comment #1 from Martin Riethmayer --- Will most likely be fixed after Neon is updated to 20.04: https://launchpad.net/ubuntu/focal/+package/virtualbox-guest-additions-iso Thanks kbroulik for pointing this out - closing, sorry for the Spam :-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419172] New: Baloo crash on login
https://bugs.kde.org/show_bug.cgi?id=419172 Bug ID: 419172 Summary: Baloo crash on login Product: frameworks-baloo Version: 5.68.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: rip...@freakmail.de Target Milestone: --- Application: baloo_file (5.68.0) Qt Version: 5.14.1 Frameworks Version: 5.68.0 Operating System: Linux 4.12.14-lp151.28.40-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: Ballo crashes after/during login (every time). Very willing to help finding out the cause for this! I'm also on IRC in #plasma (ripper17) The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4b02156f00 (LWP 2876))] Thread 3 (Thread 0x7f4af6521700 (LWP 3357)): [KCrash Handler] #6 0x7f4affa4d160 in raise () from /lib64/libc.so.6 #7 0x7f4affa4e741 in abort () from /lib64/libc.so.6 #8 0x7f4afdbeca82 in mdb_assert_fail (env=0x5640676b7540, expr_txt=expr_txt@entry=0x7f4afdbee50f "rc == 0", func=func@entry=0x7f4afdbeee88 <__func__.6935> "mdb_page_dirty", line=line@entry=2071, file=0x7f4afdbee4f0 "mdb.c") at mdb.c:1487 #9 0x7f4afdbe1d85 in mdb_page_dirty (txn=0x5640676bd160, mp=) at mdb.c:2071 #10 0x7f4afdbe2f6a in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f4af651ff48, mc=) at mdb.c:2252 #11 0x7f4afdbe31d9 in mdb_page_touch (mc=mc@entry=0x7f4af6520480) at mdb.c:2370 #12 0x7f4afdbe4cf4 in mdb_cursor_touch (mc=mc@entry=0x7f4af6520480) at mdb.c:6308 #13 0x7f4afdbe7e8e in mdb_cursor_put (mc=0x7f4af6520480, key=0x7f4af6520860, data=0x7f4af6520870, flags=) at mdb.c:6442 #14 0x7f4afdbeab1b in mdb_put (txn=0x5640676bd160, dbi=9, key=key@entry=0x7f4af6520860, data=data@entry=0x7f4af6520870, flags=flags@entry=0) at mdb.c:8800 #15 0x7f4b0110cc28 in Baloo::DocumentTimeDB::put (this=this@entry=0x7f4af6520970, docId=, docId@entry=1358280967818577923, info=...) at /usr/src/debug/baloo5-5.68.0-lp151.230.1.x86_64/src/engine/documenttimedb.cpp:74 #16 0x7f4b011288ac in Baloo::WriteTransaction::addDocument (this=0x5640678b2300, doc=...) at /usr/src/debug/baloo5-5.68.0-lp151.230.1.x86_64/src/engine/writetransaction.cpp:81 #17 0x7f4b01120ae6 in Baloo::Transaction::addDocument (this=this@entry=0x7f4af6520af0, doc=...) at /usr/src/debug/baloo5-5.68.0-lp151.230.1.x86_64/src/engine/transaction.cpp:254 #18 0x564065cfbbba in Baloo::UnindexedFileIndexer::run (this=0x5640679691d0) at /usr/src/debug/baloo5-5.68.0-lp151.230.1.x86_64/src/file/unindexedfileindexer.cpp:73 #19 0x7f4b00555282 in QThreadPoolThread::run (this=0x56406793f300) at thread/qthreadpool.cpp:99 #20 0x7f4b00551b2c in QThreadPrivate::start (arg=0x56406793f300) at thread/qthread_unix.cpp:342 #21 0x7f4afe04b569 in start_thread () from /lib64/libpthread.so.0 #22 0x7f4affb0f9ef in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f4af7034700 (LWP 2882)): #0 0x7f4affb00c98 in read () from /lib64/libc.so.6 #1 0x7f4afc0f2c80 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4afc0adcb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4afc0ae150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f4afc0ae2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f4b007a07eb in QEventDispatcherGlib::processEvents (this=0x7f4afb10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f4b0073fd4a in QEventLoop::exec (this=this@entry=0x7f4af7033c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f4b00550657 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f4b0134d115 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f4b00551b2c in QThreadPrivate::start (arg=0x7f4b015c4da0) at thread/qthread_unix.cpp:342 #10 0x7f4afe04b569 in start_thread () from /lib64/libpthread.so.0 #11 0x7f4affb0f9ef in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f4b02156f00 (LWP 2876)): #0 0x7f4affb0519b in poll () from /lib64/libc.so.6 #1 0x7f4afc0ae1a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4afc0ae2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4b007a07cc in QEventDispatcherGlib::processEvents (this=0x5640676a3c30, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f4b0073fd4a in QEventLoop::exec (this=this@entry=0x7ffd117546b0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f4b007494c0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1400 #6 0x564065cf04cc in main (argc=, argv=) at
[Skanlite] [Bug 426829] add OCR capabilities
https://bugs.kde.org/show_bug.cgi?id=426829 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430122] Crash of kdeinit5 when saving (version 20.11.90)
https://bugs.kde.org/show_bug.cgi?id=430122 Martin Riethmayer changed: What|Removed |Added Product|kdenlive|kio-extras Component|User Interface |Thumbnails and previews Assignee|j...@kdenlive.org |plasma-b...@kde.org --- Comment #1 from Martin Riethmayer --- Reassining to kio-extras: Looking into this a bit more: This only happens, when the "Preview" is enabled in the "Save File"-dialog. It seems to be an issue with the "oldfilm" effect that I applied to one kdenlive-file and the settings of that effect: The crash occurs for any value less than 12 (e.g. "4" or "11"), but not for values larger than 12 (e.g. the default "14" or "31" etc.) for the "Y-Delta". The above is only true for a preview size of 96px or larger in Dolphin or the "Save"-dialog. For a smaller preview size (e.g. 80px), the crash still occurs. For a 1080p video, this somehow probably makes sense: 1080/12 = 90 (which is smaller than 96px preview size, but bigger than 80px preview size) 1080/11 = 98.18181 (bigger than 96px preview size). Maybe this can help someone figure out, what's going on in the thumbnailer? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 430122] New: Crash of kdeinit5 when saving (version 20.11.90)
https://bugs.kde.org/show_bug.cgi?id=430122 Bug ID: 430122 Summary: Crash of kdeinit5 when saving (version 20.11.90) Product: kdenlive Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: rip...@freakmail.de Target Milestone: --- Created attachment 133927 --> https://bugs.kde.org/attachment.cgi?id=133927=edit kdeinit5 crashlog with debug info SUMMARY STEPS TO REPRODUCE 1. Create a new project 2. Import anything (e.g. an mp3, a jpg, mp4 video) by drag and drop from dolphin 3. Press CTRL+S to save the project OBSERVED RESULT Crash of kdeinit5, saving works, kdenlive continues to work EXPECTED RESULT No crash of kdeinit5 Note: This crash even happens after removing the mp3 file again from the timeline and project. Default project is 1080p25 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.57-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics MLT Version 6.22.1 FFmpeg Qt 5.15.2 (compiled against 5.15.2) xcb window system -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430122] Crash of kdeinit5 when saving (version 20.11.90)
https://bugs.kde.org/show_bug.cgi?id=430122 --- Comment #3 from Martin Riethmayer --- Wow, thanks for the quick fix, I'll check if this works as soon as I get newer packages (sorry, can't compile myself...) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 444835] New: Custom padding via CSS file changes tab-style unexpectedly
https://bugs.kde.org/show_bug.cgi?id=444835
Bug ID: 444835
Summary: Custom padding via CSS file changes tab-style
unexpectedly
Product: konsole
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: tabbar
Assignee: konsole-de...@kde.org
Reporter: rip...@freakmail.de
Target Milestone: ---
SUMMARY
When using a user-defined stylesheet, setting a different padding "destroys"
the rest of the styling
STEPS TO REPRODUCE
1. Create a custom CSS file with the content
QTabBar::tab { padding: 8px; }
2. Apply the stylesheet in Konsole preferences -> Tab Bar
OBSERVED RESULT
The tabs do respect the new padding but also lose a bunch of other styling
information (e.g. the blue highlight...)
EXPECTED RESULT
The tabs should only change the padding, not the rest of the styling
Note: This does not apply generally to all settings in the custom CSS file. If
you put
QTabBar::tab { min-width: 200px; }
then only the minimum width of the tabs is changed, the rest of the styling
appears to be unchanged, e.g. the blue highlight line is still intact.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon / Kubuntu
KDE Plasma Version: 5.23.2 / 5.18.5
KDE Frameworks Version: 5.87.0 / 5.68.0
Qt Version: 5.15.3 / 5.12.8
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 449855] Proxy makes Night Color fail to apply on Plasma start
https://bugs.kde.org/show_bug.cgi?id=449855 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #1 from Martin Riethmayer --- I can reproduce this on KDE neon, 5.24.0, KDE FW 5.90, QT 5.15.3, Wayland. I've used an empty URL auto-config (so that obviously fails) as proxy. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449789] Impossible to change the user avatar
https://bugs.kde.org/show_bug.cgi?id=449789 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #2 from Martin Riethmayer --- Can't reproduce KDE neon, fresh install, all up-to-date: Plasma: 5.24 Frameworks: 5.90.0 QT: 5.15.3 Graphics Platform: X11 / Wayland (both tested) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449860] New: Systemsettings: clearing search term shows incorrect left column
https://bugs.kde.org/show_bug.cgi?id=449860 Bug ID: 449860 Summary: Systemsettings: clearing search term shows incorrect left column Product: systemsettings Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rip...@freakmail.de Target Milestone: --- SUMMARY *** Clearing the search brings the left column back to the contents of the last KCM *** STEPS TO REPRODUCE 1. Open Systemsettings, search for anything (e.g. "display") 2. Click on any search result (e.g. display configuration) 3. Click "Back" 4. Search term is still filled in, click on the "X" to delete the search term OBSERVED RESULT Left column switches back to the content of the previously visited KCM (in the above example: the display configuration with Gamma, Compositor, Night color...) EXPECTED RESULT Left column shows all available KCMs. Note: If I click "back" again, the left column now does show all KCMs and the search term has been cleared. So clearing the term works, it's just updating the left column to the wrong view or something? SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon User Edition, fully up-to-date KDE Plasma Version: Plasma 5.24 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Graphics Platform: Wayland and X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469472] KWin stops redrawing content of some windows
https://bugs.kde.org/show_bug.cgi?id=469472 --- Comment #4 from Martin Riethmayer --- It *might* have to do something with one of the following two things (I'm starting so see some kind of pattern): - KDEConnect notifications. I feel like if there's a phone call incoming and the system has been running for a while (e.g. a couple of KDEConnect notifications have come in), the above situation happens. Reasoning (for believing this might cause the issue): A playing video stops quickly, but is resumed only after a couple of minutes after the call has ended. It seems like something is preventing the notification of the ended call to un-pause the video? The notification of the incoming call is also very late and sometimes drawn in a slow manner (e.g. first the notification box with transparent content, then a couple of seconds later the content is drawn). - More in general: If ton's of notifications are in the notification history. E.g. I get a ton of e-mail (using Thunderbird), Slack messages, KTeaTimer-notifications, Signal (the messenger), ... so my notifications history fills up quickly. Reasoning (for believing this might cause the issue): if (at that point) I'm still able to clear the notification history, that seems to improve things most of the time (again: hard to be sure and reproduce). Also, if I think about it, I try to clear my notification history more often, now, which seems to help to prevent the issue. Could there be something like a notification-history-overflow that brings down performance / impacts KWin (or other components)? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476629] Unstable ISO does not boot
https://bugs.kde.org/show_bug.cgi?id=476629 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #5 from Martin Riethmayer --- Trying to boot unstable ISO in VirtualBox 6.1.38_Ubuntu r153438: I get the Neon log with spinning cogwheel, then the error messages "drm:vmw_host_printf [vmwgfx]] ERROR Failed to send host log message." and "[FAILED] Failed to start Migrate UID 1000 from semi-wrong groups to correct ones.." After that, I'm stuck on a black screen, can't even switch to another VT. I can get Neon to boot up if I enable 3d Acceleration in the VM settings of VirtualBox (I've also set Graphics memory to 48MB, not sure if this is related. *Only* increasing Graphics memory to 48MB is not enough to make it boot). I thought it might have to do with Plasma switching to wayland by default? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476790] New: Install option in Welcome Center misses an icon and won't launch install process
https://bugs.kde.org/show_bug.cgi?id=476790 Bug ID: 476790 Summary: Install option in Welcome Center misses an icon and won't launch install process Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: rip...@freakmail.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** neon-unstable-20231109-1616 The option to install Neon from the "Welcome center" is missing the icon clicking on it leads to "Internal error: could not prompt the user for which application to start" *** STEPS TO REPRODUCE 1. Boot up neon-unstable-20231109-1616 ISO (e.g. in VirtualBox) 2. Click on the install icon on first page of Welcome Center OBSERVED RESULT Icon is missing, Install process does not start EXPECTED RESULT Icon is present, Install process should start SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition (2023-11-09) (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Had to set VirtualBox to enable 3D-Accelaration, otherwise neon won't boot up (see #476629) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476791] New: Installation window is transparent
https://bugs.kde.org/show_bug.cgi?id=476791 Bug ID: 476791 Summary: Installation window is transparent Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: rip...@freakmail.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** neon-unstable-20231109-1616 The installation window is transparent *** STEPS TO REPRODUCE 1. Boot up live image 2. Search for "Install system" script in Application Launcher and start it OBSERVED RESULT Shadow of the window and window controls are drawn, but no content (window is transparent) EXPECTED RESULT Window should show content SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition (2023-11-09) (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Had to set VirtualBox to enable 3D-Accelaration, otherwise neon won't boot up (see #476629) Other windows (e.g. Dolphin, Systemsettings, InfoCenter) show up fine -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 467640] New: Filesystem view disappears at every start of KDevelop
https://bugs.kde.org/show_bug.cgi?id=467640 Bug ID: 467640 Summary: Filesystem view disappears at every start of KDevelop Classification: Applications Product: kdevelop Version: 5.11.230380 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rip...@freakmail.de Target Milestone: --- SUMMARY The filesystem view disappears every restart of KDevelop STEPS TO REPRODUCE 1. Enable file system view on the left toolbar 2. Close and Re-Open KDevelop (with last session) OBSERVED RESULT File system view is gone and has to be re-enabled. KDevelop only start with the "Documents" view. EXPECTED RESULT File system view should remain visible SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230318 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.4-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4770R CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Pro Graphics 5200 Manufacturer: GIGABYTE Product Name: M4HM87P-00 System Version: 1.x ADDITIONAL INFORMATION .config/kdeveloprc is acting "weird": When I manually add the filesystem view, it get's updated: [MainWindow_code] (1) Tool Views Order=org.kdevelop.DocumentsView,org.kdevelop.FileManagerView When I close an re-open KDevelop, this line is still active, but the Filesystem view is not shown. If I close KDevelop now, it will be changed to [MainWindow_code] (1) Tool Views Order=org.kdevelop.DocumentsView The sections [User Interface][Main Window 0][Area code] [User Interface][Main Window 0][Area debug] [User Interface][Main Window 0][Area review] all contain "org.kdevelop.FileManagerView:1" and retain that line and value throughout all restarts. Removing kdeveloprc and starting fresh does not solve the issue. Note: This is kind of the opposite of https://bugs.kde.org/show_bug.cgi?id=385916 which never went anywhere. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467962] New: Enable dragging of breadcrum folders to left panel
https://bugs.kde.org/show_bug.cgi?id=467962 Bug ID: 467962 Summary: Enable dragging of breadcrum folders to left panel Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: rip...@freakmail.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I would appreciate the ability to drag a folder from the breadcrumb navigation to the folder panel. Currently, especially when I'm currently inside the "target folder", I'll have to navigate one folder up and then drag the folder from there. It would be nice and a minor time saver to be able to drag the folder from the breadcrumb, too STEPS TO REPRODUCE 1. Navigate to a folder 2. Try to drag the breadcrumb entry of that folder to the panel OBSERVED RESULT Breadcrumb can't be dragged EXPECTED RESULT Bradcrumb can be dragged Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-69-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800U with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: RENOIR -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467962] Enable dragging of breadcrum folders to left panel
https://bugs.kde.org/show_bug.cgi?id=467962 --- Comment #2 from Martin Riethmayer --- Created attachment 157811 --> https://bugs.kde.org/attachment.cgi?id=157811=edit Drag Bradcrumb I'd like to click and hold on the folder marked with "1" in the screenshot (so the right-most, currently displayed folder) and then drag it over like the arrow "2" in the screenshot. The folder (in my example "pkg") would then show up on the places panel. The main view should remain the same, e.g. still display the "mod" subfolder. To achieve this currently, I would have to navigate one folder up (so to "go" in my screenshot) and then drag the folder "pkg" from there. If this is difficult to implement, feel free to close the wish, it's just a small annoyance and can be circumvented by spending 2 extra clicks. I had hoped that this might be just something like a flag added to the breadcrumb and thought this could be useful. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408571] Bouncing cursor doesn't stop after opening new Tab (e.g. dolphin when opening a second folder, kate when opening second document...)
https://bugs.kde.org/show_bug.cgi?id=408571 Martin Riethmayer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Martin Riethmayer --- Doplhin does not retain a bouncing cursor when openening a new folder from krunner or from Desktop-Shortcut or from within dolhin itself. Marking as resolved, fixed -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468899] [Spectacle 23.04] Video Recording - Add configuration options and shortcuts to Spectacle settings page.
https://bugs.kde.org/show_bug.cgi?id=468899 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #1 from Martin Riethmayer --- Rectangular region video recording is also reported in https://bugs.kde.org/show_bug.cgi?id=469779 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469472] New: KWin stops redrawing content of some windows
https://bugs.kde.org/show_bug.cgi?id=469472 Bug ID: 469472 Summary: KWin stops redrawing content of some windows Classification: Plasma Product: kwin Version: 5.24.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rip...@freakmail.de Target Milestone: --- Created attachment 158762 --> https://bugs.kde.org/attachment.cgi?id=158762=edit Output of kwin_x11 --replace SUMMARY Seemingly randomly, (some) windows are not being drawn any more. Currently, no Thunderbird windows (main, compose-window) are re-drawn, Systemsettings start with a black content (title bar is drawn), krunner doesn't show up. If I bring Thunderbird to the front (by clicking on the entry in the task manager), the screen does not update correctly, but shows old content (from a Konsole window that should now be "beneath" Thunderbird in the graphical stack). I can still interact with the session, e.g. I'm typing this message, if I bring Konsole to the front of Thunderbird I can run commands etc. I can close some windows (e.g. systemsettings), but not Thunderbird (times out, display is grayed and there should be the dialog from KWin to force quit, but that dialog is not drawn). STEPS TO REPRODUCE 1. Sorry, I don't know how to reproduce this OBSERVED RESULT Some re-drawing seems to break. EXPECTED RESULT KWin should continue to redraw the content of all applications Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-71-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: RENOIR ADDITIONAL INFORMATION I've added some output from kwin_x11 --replace from a Konsole window. I'll happily add more info if wanted but since I can't reproduce the issue, it might take a while. I'm also not very familiar with getting more detailed info, if possible, please be a little detailed in what I have to do to get the requested info. I'll attach the log from plasmashell --replace, too, if that's of any help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469472] KWin stops redrawing content of some windows
https://bugs.kde.org/show_bug.cgi?id=469472 --- Comment #1 from Martin Riethmayer --- Created attachment 158763 --> https://bugs.kde.org/attachment.cgi?id=158763=edit Output of plasmashell --replace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469472] KWin stops redrawing content of some windows
https://bugs.kde.org/show_bug.cgi?id=469472 --- Comment #3 from Martin Riethmayer --- Created attachment 158765 --> https://bugs.kde.org/attachment.cgi?id=158765=edit Output of kscreen-doctor -o -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469472] KWin stops redrawing content of some windows
https://bugs.kde.org/show_bug.cgi?id=469472 --- Comment #2 from Martin Riethmayer --- Created attachment 158764 --> https://bugs.kde.org/attachment.cgi?id=158764=edit Output of qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 479395] New: Crash on trying to re-open draft from local folder
https://bugs.kde.org/show_bug.cgi?id=479395 Bug ID: 479395 Summary: Crash on trying to re-open draft from local folder Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rip...@freakmail.de Target Milestone: --- Application: kontact (5.24.3 (23.08.3)) Qt Version: 5.15.11 Frameworks Version: 5.112.0 Operating System: Linux 6.6.2-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: When trying to re-open a draft from a local folder after sending failed, KMail / Kontact crashed. The draft was still available and would open at the next start, so no data was lost. This happened multiple times until I finally managed to have the correct SMTP configured (which is really, really, really not intuitive if you have multiple accounts configured...). I could not reproduce this by simply making a draft and re-opening it. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 doActivate (sender=0x56271f1aa780, signal_index=4, argv=0x7ffc5a33ffc0) at kernel/qobject.h:132 #5 0x7ff48eb1e0af in QMetaObject::activate (sender=sender@entry=0x56271f1aa780, m=, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc5a33ffc0) at kernel/qobject.cpp:3985 #6 0x7ff3f47c0e4c in KMCommand::completed (_t1=0x56271f1aa780, this=0x56271f1aa780) at /usr/src/debug/kmail-23.08.3/build/src/kmailprivate_autogen/EWIEGA46WW/moc_kmcommands.cpp:201 #7 KMCommand::slotPostTransfer (this=0x56271f1aa780, result=KMCommand::OK) at /usr/src/debug/kmail-23.08.3/src/kmcommands.cpp:263 #8 0x7ff48eb25442 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5a3400f0, r=0x56271f1aa780, this=0x562720700f50) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #9 doActivate (sender=0x56271f1aa780, signal_index=3, argv=0x7ffc5a3400f0) at kernel/qobject.cpp:3925 #10 0x7ff48eb1e0af in QMetaObject::activate (sender=sender@entry=0x56271f1aa780, m=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc5a3400f0) at kernel/qobject.cpp:3985 #11 0x7ff3f47c1a9a in KMCommand::messagesTransfered (_t1=KMCommand::OK, this=0x56271f1aa780) at /usr/src/debug/kmail-23.08.3/build/src/kmailprivate_autogen/EWIEGA46WW/moc_kmcommands.cpp:194 #12 KMCommand::slotJobFinished (this=0x56271f1aa780) at /usr/src/debug/kmail-23.08.3/src/kmcommands.cpp:368 #13 0x7ff48eb25442 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5a340220, r=0x56271f1aa780, this=0x56271c077a10) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x56271ea666a0, signal_index=6, argv=0x7ffc5a340220) at kernel/qobject.cpp:3925 #15 0x7ff48fdad115 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #16 0x7ff48fdb141b in ?? () from /lib64/libKF5CoreAddons.so.5 #17 0x7ff48eb18f50 in QObject::event (this=0x56271ea666a0, e=0x56271e738970) at kernel/qobject.cpp:1347 #18 0x7ff48f7a519e in QApplicationPrivate::notify_helper (this=, receiver=0x56271ea666a0, e=0x56271e738970) at kernel/qapplication.cpp:3640 #19 0x7ff48eaed198 in QCoreApplication::notifyInternal2 (receiver=0x56271ea666a0, event=0x56271e738970) at kernel/qcoreapplication.cpp:1064 #20 0x7ff48eaed35e in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #21 0x7ff48eaf0791 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x56271bbb5ae0) at kernel/qcoreapplication.cpp:1821 #22 0x7ff48eaf0cd8 in QCoreApplication::sendPostedEvents (receiver=, event_type=) at kernel/qcoreapplication.cpp:1680 #23 0x7ff48eb468c3 in postEventSourceDispatch (s=0x56271bbf9cf0) at kernel/qeventdispatcher_glib.cpp:277 #24 0x7ff485513f30 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7ff485515b58 in ?? () from /lib64/libglib-2.0.so.0 #26 0x7ff48551620c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x7ff48eb460d6 in QEventDispatcherGlib::processEvents (this=0x56271bba2e70, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7ff48eaebc2b in QEventLoop::exec (this=this@entry=0x7ffc5a340610, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7ff48eaf40c0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x56271a9a7fd3 in main (argc=, argv=) at /usr/src/debug/kontact-23.08.3/src/main.cpp:216 [Inferior 1 (process 29314) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471292] Crash in ShellContainmentModel::load() when attempting to delete a panel from "Manage Desktops And Panels" window
https://bugs.kde.org/show_bug.cgi?id=471292 --- Comment #18 from Martin Riethmayer --- Cool, I can confirm there's no more crash for me after latest updates, thanks. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476629] Unstable ISO does not boot
https://bugs.kde.org/show_bug.cgi?id=476629 --- Comment #9 from Martin Riethmayer --- Can't confirm, "neon-unstable-20231126-1118.iso" still will not boot if 3D acceleration is disabled in VirtualBox. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477760] New: Manage Desktop and Panels remains accesible when it shouldn't be
https://bugs.kde.org/show_bug.cgi?id=477760 Bug ID: 477760 Summary: Manage Desktop and Panels remains accesible when it shouldn't be Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: "Manage Desktop and Panels" window Assignee: plasma-b...@kde.org Reporter: rip...@freakmail.de Target Milestone: 1.0 SUMMARY *** "Manage Desktop and Panels" should not be shown if only one screen and one panel is active, but it remains visible after deleting a second panel. STEPS TO REPRODUCE 1. Add a panel (so that there's at least two) 2. Enter "Manage Desktop and Panels" 3. Remove one panel OBSERVED RESULT "MDaP" is still available, even though there's only one screen and one panel available right now. EXPECTED RESULT "MDaP" should not be accessible in Edit Mode. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon unstable with all updates from 2023-11-30, 09:21 UTC (available in About System) KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION The problem is resolved after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471292] Crash in ShellContainmentModel::load() when attempting to delete a panel
https://bugs.kde.org/show_bug.cgi?id=471292
--- Comment #10 from Martin Riethmayer ---
Created attachment 163178
--> https://bugs.kde.org/attachment.cgi?id=163178=edit
GDB output of the crash
I can 100% reproduce this in KDE neon unstable (all up-to-date).
Additional Info (not present in my original report): This persists across
reboot, so the panel really is not removed.
Just to re-iterate (see #476991 for automatic crash report):
Application: plasmashell (5.81.0)
Qt Version: 6.6.0
Frameworks Version: 5.245.0
Operating System: Linux 6.2.0-36-generic x86_64
Windowing System: Wayland
Distribution: KDE neon Unstable Edition
DrKonqi: 5.81.0 [CoredumpBackend]
-- Information about the crash:
Steps to reproduce
1.) Add new (default) Panel
2.) Activate Edit mode ("Alt+D, E") via right-click menu of the desktop
3.) Activate Editing of Desktop and Panels (translated from German, sorry)
4.) Remove any panel
Actual Result:
Plasma crashes, the panel is not removed. Note: The Edit mode (Alt+D, E) will
not show the option for editing desktops and panels right now, you'd have to
add another panel to enter it again.
Expected Result:
Panel is removed.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 471292] Crash in ShellContainmentModel::load() when attempting to delete a panel
https://bugs.kde.org/show_bug.cgi?id=471292 --- Comment #14 from Martin Riethmayer --- @Nate: I've looked at your Bug 477117, and your steps seem to be a little different: You're entering the panel edit mode and delete the panel from there, while in this bug report, I'm entering the desktop edit mode and then "Manage Desktops And Panels..." so that probably explains the different Backtrace? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471292] Crash in ShellContainmentModel::load() when attempting to delete a panel
https://bugs.kde.org/show_bug.cgi?id=471292 --- Comment #13 from Martin Riethmayer --- Yes, the desktop and panel edit mode was invoked before the crash. Sorry, new to GDB. Should I upload a new one, wher I start GDB only just before really removing the panel? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476991] New: Crash on removing panel
https://bugs.kde.org/show_bug.cgi?id=476991
Bug ID: 476991
Summary: Crash on removing panel
Classification: Plasma
Product: plasmashell
Version: master
Platform: Neon
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: rip...@freakmail.de
Target Milestone: 1.0
Application: plasmashell (5.81.0)
Qt Version: 6.6.0
Frameworks Version: 5.245.0
Operating System: Linux 6.2.0-36-generic x86_64
Windowing System: Wayland
Distribution: KDE neon Unstable Edition
DrKonqi: 5.81.0 [CoredumpBackend]
-- Information about the crash:
Steps to reproduce
1.) Add new (default) Panel
2.) Activate Edit mode ("Alt+D, E") via right-click menu of the desktop
3.) Activate Editing of Desktop and Panels (translated from German, sorry)
4.) Remove any panel
Actual Result:
Plasma crashes, the panel is not removed. Note: The Edit mode (Alt+D, E) will
not show the option for editing desktops and panels right now, you'd have to
add another panel to enter it again
Expected Result:
Panel is removed.
The crash can be reproduced every time.
-- Backtrace (Reduced):
#5 0x7f063c7cbc15 in QObject::disconnect(QObject const*, char const*,
QObject const*, char const*) (sender=0x21, signal=signal@entry=0x0,
receiver=receiver@entry=0x55f3a0009b00, method=method@entry=0x0) at
./src/corelib/kernel/qobject.cpp:3197
#6 0x55f39a153294 in ShellContainmentModel::load() (this=0x55f3a0009b00)
at ./shell/shellcontainmentconfig.cpp:332
#7 0x55f39a0d4940 in ShellContainmentModel::qt_metacall(QMetaObject::Call,
int, void**) (this=0x55f3a0009b00, _c=QMetaObject::InvokeMetaMethod, _id=1,
_a=0x7ffe98dfa6c8) at
./obj-x86_64-linux-gnu/shell/plasmashell_autogen/EWIEGA46WW/moc_shellcontainmentconfig.cpp:324
#8 0x7f063e049613 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int,
void**) const (this=0x7ffe98dfa980, type=QMetaObject::InvokeMetaMethod,
index=, argv=) at
./src/qml/qml/qqmlobjectorgadget.cpp:14
#9 0x7f063e140713 in QV4::CallMethod (callType=,
callArgs=, engine=, argTypes=,
argCount=, returnType=..., index=,
object=) at
/usr/include/x86_64-linux-gnu/qt6/QtCore/qvarlengtharray.h:84
The reporter indicates this bug may be a duplicate of or related to bug 476034.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 476991] Crash on removing panel
https://bugs.kde.org/show_bug.cgi?id=476991 --- Comment #1 from Martin Riethmayer --- Created attachment 163150 --> https://bugs.kde.org/attachment.cgi?id=163150=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476791] Qt apps running as root are transparent (and so Installation window is transparent)
https://bugs.kde.org/show_bug.cgi?id=476791 --- Comment #6 from Martin Riethmayer --- It still does not work with the newest unstable image (2023-11-19) and after running sudo apt update && sudo pkcon update Tested in VirtualBox 6.1 and 7.0 on Ubuntu 22.04 as host. This might be a problem only within VirtualBox (or even with certain graphics settings), I've not yet tested it on real hardware -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476790] Install option in Welcome Center misses an icon and won't launch install process
https://bugs.kde.org/show_bug.cgi?id=476790 Martin Riethmayer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Martin Riethmayer --- The Welcome Center no longer has a page to install, so it's also not missing the image any longer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481937] After plasma6 update, VM is unusable with 3D acceleration turned off
https://bugs.kde.org/show_bug.cgi?id=481937 Martin Riethmayer changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #5 from Martin Riethmayer --- I've investigated a bit further. To do so, I enabled 3d acceleration and installed Neon, then disabled 3d acceleration again. If you do *not* enable auto-login, you'll get as far as the SDDM login screen. You can now switch TTYs (e.g. by hitting (Right-)CTRL+F3). I've updated the guest-additions manually from the command line to match the version of the VBox on the host (in my case: 7.0.14 is running on host, the GuestAdditions now are also installed at version 7.0.14 inside the Guest - check with "(Right-)CTRL+N" and selecting "runtime"). This does not make any difference, but at least I'm fairly certain now, that the mismatch of the GuestAdditions shipped by Neon (6.0.0) and the actual VBox Host version are not to blame. >From journalctl, I can see the failed attempts to log in to a Wayland session (X session works), but I have no clue if any of the messages actually mean anything. When logging in, quite a few things seem to get done, e.g. Finished KSpash "ready" Stage. or Reached target Startup of XDG autostart applications. A few warnings or suspicious messages that I noticed are: - VMware: No 3D enables (0, success). - libEGL warning: egl: failed to create dri2 screen (happens quite often) - qt.qpa.wayland: Creating a fake screen in order for Qt not to crash (happens quite often) I don't know how to debug further ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 Martin Riethmayer <rip...@freakmail.de> changed: What|Removed |Added Platform|openSUSE RPMs |Neon Packages Version|5.6.2 |5.6.95 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #7 from Martin Riethmayer <rip...@freakmail.de> --- This is also happening in KDE Neon ( neon-devedition-gitstable-20160619-1048-amd64.iso ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #6 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 99544 --> https://bugs.kde.org/attachment.cgi?id=99544=edit Log of kded5 debug output, config files of kscreen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #5 from Martin Riethmayer <rip...@freakmail.de> --- This is still happening with the latest versions of kscreen in OpenSUSE Factory from GIT: kscreen5: 5.6.90git~20160613T210802~b0e02c9-12.1 libkscreen2-plugin: 5.6.90git~20160614T154913~2792f55-16.1 Steps to reproduce: 1.) Start a VirtualBox VM with up-to-date OpenSUSE factory and two monitors for the VM 2.) Place the monitors side-by-side in KCM 3.) Go to a konsole and run "xrandr --output VGA-2 --off", then "xrandr --output VGA-2 --auto" Expected result: The monitors should be configured side-by-side again Actual result: The monitors are in "clone" mode Reproducible: Always I'll attach the kscreen log. I've set kscreen.*=true in qtdebugging.ini and restarted kded5. I'll also attach the config files after each step, e.g. the initial state is "xyz.0", after applying the side-by-side config once in KCM "xyz.1", second apply is "xyz.2", xrandr off is "xyz.3" and xrandr auto is "xyz.4" At the time of restarting kded5, my monitors where in "clone" mode (config file ".0"), so I went to the KCM and positioned them side-to-side. After hitting "Apply" once, the config is saved twice (e.g. the log was written up to and including line 16) (config file ".1") The KCM still believes that there are changes to apply, so after hitting "Apply" for the second time, the log gets written up to and including line 24. (config file ".2") After running "xrandr --output VGA-2 --off", log is written including line 32 (config file ".3") After running "xrandr --output VGA-2 --auto", log is written until the last line. (config file ".4") I noted that the filename of the kscreen config is always the same - I don't know if this is the way it's supposed to be? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358283] VD: Make user-added plasmoid icons the same size of the system tray icons
https://bugs.kde.org/show_bug.cgi?id=358283 Martin Riethmayer <rip...@freakmail.de> changed: What|Removed |Added CC||rip...@freakmail.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 354115] One of the screens stays blank after energy saving mode
https://bugs.kde.org/show_bug.cgi?id=354115 Martin Riethmayer <rip...@freakmail.de> changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #14 from Martin Riethmayer <rip...@freakmail.de> --- Sorry for commenting on a "Resolved" issue, this is mainly to provide a solution that worked for me: xset dpms force off did turn all monitors blank, moving the mouse then woke them all up. "xset dpms force on" did not work. Should this be reported upstream? Where? Additional info: I sometimes have the same problem, but I'm on Kubuntu 14.04 LTS, KDE Platform Version 4.13.3 Version === KWin version: 4.11.11 KDE SC version (runtime): 4.13.3 KDE SC version (compile): 4.13.2 Qt Version: 4.8.6 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 331963] KDE Telepathy rename contact - no way to change contact name and avatar
https://bugs.kde.org/show_bug.cgi?id=331963 Martin Riethmayer <rip...@freakmail.de> changed: What|Removed |Added CC||rip...@freakmail.de --- Comment #8 from Martin Riethmayer <rip...@freakmail.de> --- Would it be possible to have a temporary solution with some kind of "merge" strategy? It's been more than 2 years now for (quote) "One of the most requested features in KDE Telepathy" and this is still not possible. I trust that the overall design and pairing with the PIM-stack is a really good idea in the long term, however it's blocking the development of important features, it seems. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #1 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 98391 --> https://bugs.kde.org/attachment.cgi?id=98391=edit diff output of complete home directory after powering off/on one of the monitors I copied my complete home directory before powering off one of the monitors. Powered off one monitor, powered it back on and made a diff of the backup-home-directory and my new "live" home directory. Only .xsession-errors changed, which you can see in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #2 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 98392 --> https://bugs.kde.org/attachment.cgi?id=98392=edit xrandr -q output before AND after powering off/on There's no change in the output of xrandr -q before and after powering one monitor off, then on again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] New: Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 Bug ID: 361750 Summary: Multi-Screen configuration lost Product: plasmashell Version: 5.6.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: rip...@freakmail.de CC: plasma-b...@kde.org After powering off and on one monitor, the configuration is completely broken Reproducible: Always Steps to Reproduce: 1. Set-up a Multi-Monitor environment: 2 screens (1xHDMI / 1xDVI->HDMI, monitors next to each other) 2. Turn off the left monitor 3. Turn the left monitor back on again Actual Results: The off/on Monitor does not regain it's setup Expected Results: The Multi-Monitor setup should not change in any way. If it is possible (which I don't know) I'd prefer that there'd be no change at all just because a monitor powers off - only change something if a monitor physically gets disconnected, though I'm afraid that this is probably impossible to distinguish. At least there should not be any change if monitors are powered of by Powerdevil or other system-energy-saving tools (I believe that this happened to me before, but I'm not 100% sure). This is most likely related to https://bugs.kde.org/show_bug.cgi?id=356225 but I'm not on a Laptop and I'm not physically unplugging a monitor (i.e. pulling a cable) but simply powering off/on. xrandr -q is identical after powering off/on one of the monitors (so xrandr actually get's it right) - could it be some timing issue / race condition? Additionally, after going to systemsettings and deactivating / re-activating the "broken" monitor, I sometimes do not get my panels back on the original spot. I'm attaching some files in the next comment(s) (it's not possible to make attachments in the original report, is it?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #3 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 98393 --> https://bugs.kde.org/attachment.cgi?id=98393=edit Output of hwinfo (just in case, I don't think this actually is a hardware issue) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #4 from Martin Riethmayer <rip...@freakmail.de> --- One more thing (sorry, this just happened and I wasn't aware of this before): My system is a two-user-system. If I turn off one monitor while being logged in as user1, the configuration of user2 (not logged in at that moment) is changed and not restored to the correct settings. Reproducible: I think it's always, but it's a bit harder to test Steps to reproduce: 1.) Set up two (or more) users 2.) Log in as user1 3.) Turn off one monitor, than on again 4.) Log off as user1, log on as user2 Expected results: The configuration of user2 should not have changed in any way Actual result: The multi-monitor setup of user2 is broken -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365467] New: Positioning changes in display configuration need to be applied twice
https://bugs.kde.org/show_bug.cgi?id=365467 Bug ID: 365467 Summary: Positioning changes in display configuration need to be applied twice Product: KScreen Version: 5.7.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: rip...@freakmail.de The KScreen KCM somehow does and at the same time doesn't recognize changing the position in a multiscreen setup. If I change the Display Configuration and hit "Apply" the changes are indeed applied, but the "Apply"-Button remains active, leaving the KCM prompts for "Unsaved changes" and the "*" in the titlebar remains. Note: This is not true for all parameter, e.g. changing the resolution of one monitor on a multiscreen setup, the "Apply"-Button works as expected. Reproducible: Always Steps to Reproduce: 1. Open the "Display and Configuration" KCM 2. Change the positioning of a multiscreen setup (e.g. from "left-of" to "right-of") 3. Hit "Apply" Actual Results: The changes are applied but the "Apply"-Button stays active, KCM thinks there's changed information. A second hit on "Apply" works. Expected Results: The "Apply"-Button should be disabled and the KCM shouldn't think there are any more changes to be applied I don't know if there are other properties except changing the positioning of a multiscreen-setup where this bug appears as well. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #11 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 100164 --> https://bugs.kde.org/attachment.cgi?id=100164=edit Screenshot KDE Neon 2016-07-19 "Cloned" desktop (except mouse cursor) and resize-handle misplaced -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #12 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 100165 --> https://bugs.kde.org/attachment.cgi?id=100165=edit output of kscreen bug (2016.07-09) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #14 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 100166 --> https://bugs.kde.org/attachment.cgi?id=100166=edit Outpu of kscreen-console bug and kscreen config files before, during and after -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #10 from Martin Riethmayer <rip...@freakmail.de> --- It's getting a bit weird now - latest KDE neon dev stable with apt-get update and apt-get upgrade: The initial bug (kind of) persists: after xrandr --off and xrandr --auto of VGA-2 (in the VirtualBox VM) my screen configuration is broken. I had set an empty panel on screen two, now both panels are shown on both screens, the konsole-window is shown on both screens (and in sync when typing) BUT the mouse courser is in only one screen and can be moved as if they are side-by-side. Again: everything (including the KCM kscreen config) appears to have the two screens in "Clone" mode - except the mouse courser which I can move from left to right screen and is only shown in one screen. I also noticed that the resize-handle of the mouse is appearing a couple of pixels to the right and to the bottom of where they should actually appear (I'll attach a screenshot). If I update the config in the KCM the panels appear in the correct screen. Note: xrandr can only turn off VGA-2 in this snapshot, trying to turn off VGA-1 has an effect in the KCM only (where the resolution of VGA-1 is increased and the display is labelled to be disabled (i.e. the "Enabled" checkbox is off)) but the screen actually stays active. I'll also attach the output of "kscreen-console bug" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 Martin Riethmayer <rip...@freakmail.de> changed: What|Removed |Added Version|5.6.95 |5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 --- Comment #8 from Martin Riethmayer <rip...@freakmail.de> --- Still happening in neon-useredition-20160705-0929-amd64 and also openSUSE Tumbleweed (5.7.0) It has improved slightly as long as I don't turn of the primary monitor. However, when I turn off primary, everything is still misconfigured when turning it back on again: - panels gone or on the wrong screen - second user's configuration (not logged in at that time) scrambled: sometimes with a black background, no panels, I can see the mouse but can't right click, sometimes only the panels are misconfigured, sometimes - in the VM, monitors are still set to clone instead of side-by-side after off/on Unfortunately, http://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/ did not solve this -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367893] KDevelop crashes - probably while parsing JS-file in background
https://bugs.kde.org/show_bug.cgi?id=367893 --- Comment #2 from Martin Riethmayer <rip...@freakmail.de> --- Created attachment 101107 --> https://bugs.kde.org/attachment.cgi?id=101107=edit Loading this file with background parser enabled crashes KDevelop for me Sorry for the late reply, I was now able to reproduce the issue, I've attached the file that is causing the freeze / crash. As soon as I open that file, KDevelopkdev increases its memory usage from ca 100MB to 14.6 GB (which is probably the maximum available at that time) if the background parser is active. If I deactivate the background parser, everything is working as expected. This is on KDevelop 5.0.0, KDE FW 5.25.0, Qt 5.6.1, KDE-Plasma 5.74, Kernel 4.7.2-1-default, 64-bit xcb windowing system, Intel Core i7-4770R CPU@3.2 GHz, 16 GB RAM. Two more observations: If I open the file with disabled background parser, then enable the parser and immediately quit KDevelop (CTRL+Q), the application window disappears, but the process is still active and will grab all RAM until it crashes. You can actually watch the RAM usage go up in the system monitor. After KDevelop crashes, there's usually (but not every time) still some kind of zombie-process in the system monitor. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 367893] New: KDevelop crashes - probably while parsing JS-file in background
https://bugs.kde.org/show_bug.cgi?id=367893 Bug ID: 367893 Summary: KDevelop crashes - probably while parsing JS-file in background Product: kdevelop Version: 5.0.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rip...@freakmail.de Application: kdevelop (5.0.0) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.7.1-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160822) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I was editing some PHP and XSL files without problems. When I opened a (simple) JS file and switched to another tab, the entire computer began to "stutter" (e.g. mp3 playback with Amarok with gaps). A few seconds later, KDevelop crashed. I've turned of the background parser and have again opende a couple of php and XSL files and a JS file, this time, no crash occured . I did not do excessive testing if this is a coincidence This is on a freshly installed Opensuse Tumbleweed, KDevelop 5.0.0, KF 5.24, Qt 5.6.1, xcb windowing system -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f90640d2900 (LWP 27228))] Thread 16 (Thread 0x7f8ff28b4700 (LWP 27683)): #0 0x7f9060dafa7d in read () from /lib64/libc.so.6 #1 0x7f9059dafd00 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f9059d6cb26 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f9059d6cff4 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f9059d6d16c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f90616dfaeb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f906168776a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f90614ad3b3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f905efb66df in ?? () from /usr/lib64/libKDevPlatformLanguage.so.10 #9 0x7f90614b22d8 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7f905a9f8474 in start_thread () from /lib64/libpthread.so.0 #11 0x7f9060dbc3ed in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f8ff3fff700 (LWP 27349)): #0 0x7f905a9fe09f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f90614b318b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f9055e9aec0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f9055e9f068 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f9055e9cf09 in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f90614b22d8 in ?? () from /usr/lib64/libQt5Core.so.5 #15 0x7f905a9f8474 in start_thread () from /lib64/libpthread.so.0 #16 0x7f9060dbc3ed in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f9010b94700 (LWP 27348)): #0 0x7f905a9fe09f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f90614b318b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x7f9055e9aec0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f9055e9f068 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f9055e9f0c2 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f9055e9a03d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
[KScreen] [Bug 361750] Multi-Screen configuration lost
https://bugs.kde.org/show_bug.cgi?id=361750 Martin Riethmayer <rip...@freakmail.de> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #15 from Martin Riethmayer <rip...@freakmail.de> --- This is no longer happening in Plasma 5.8.0, Qt 5.7.0. Marking as resolved fixed - thanks for your work on MultiScreen-Issues! -- You are receiving this mail because: You are watching all bug changes.
