[plasmashell] [Bug 380503] New: Plasma can't start and always crashes at startup
https://bugs.kde.org/show_bug.cgi?id=380503 Bug ID: 380503 Summary: Plasma can't start and always crashes at startup Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pin...@hotmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.8.0-36-generic i686 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Just startup Kubuntu - Unusual behavior I noticed: No desktop appeared - Custom settings of the application: None: default install of Kubuntu 16.04.2 (fresh install) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb1ac1800 (LWP 1252))] Thread 8 (Thread 0xa1313b40 (LWP 1515)): #0 0xb76f4ce5 in __kernel_vsyscall () #1 0xb76f4979 in __vdso_clock_gettime () #2 0xb4d38142 in __GI___clock_gettime (clock_id=1, tp=0xa1312f04) at ../sysdeps/unix/clock_gettime.c:115 #3 0xb509c338 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #4 0xb522b232 in QTimerInfoList::updateCurrentTime() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb522b754 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb522cd19 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb43bf5db in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb43c0024 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb43c0254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0xb522d964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb51d27a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb51d2bfa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #13 0xb4ff8f1d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #14 0xa1841980 in KCupsConnection::run() () from /usr/lib/i386-linux-gnu/libkcupslib.so #15 0xb4ffe43b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #16 0xb4bd3295 in start_thread (arg=0xa1313b40) at pthread_create.c:333 #17 0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 7 (Thread 0xa9285b40 (LWP 1344)): #0 0xb43bcf00 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb43bf9f0 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb43c00b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb43c0254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb522d964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb51d27a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb51d2bfa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb4ff8f1d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb6c4a7a9 in ?? () from /usr/lib/i386-linux-gnu/libQt5Quick.so.5 #9 0xb4ffe43b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb4bd3295 in start_thread (arg=0xa9285b40) at pthread_create.c:333 #11 0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 6 (Thread 0xaa950b40 (LWP 1333)): #0 0xb76f4ce5 in __kernel_vsyscall () #1 0xb4bd8a6c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb4d3764d in __pthread_cond_wait (cond=0xb76648d0, mutex=0xb76648b8) at forward.c:149 #3 0xb752ca2c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5 #4 0xb752ca6c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5 #5 0xb4bd3295 in start_thread (arg=0xaa950b40) at pthread_create.c:333 #6 0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 5 (Thread 0xaba78b40 (LWP 1302)): #0 0xb4406488 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb43bfa65 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb43c00b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb43c0254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb522d964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb51d27a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb51d2bfa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Co
[plasmashell] [Bug 396614] New: Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 Bug ID: 396614 Summary: Plasmashell + Wayland - frequent hangs/crashes when opening start menu Product: plasmashell Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: kurko2...@gmail.com Target Milestone: 1.0 Flags: Wayland+ Created attachment 113990 --> https://bugs.kde.org/attachment.cgi?id=113990&action=edit Crash report from KDE crash reporter When opening or using the applications menu/start menu when using Wayland, Plasmashell often hangs or crashes. This can happen in several different ways but I'm not sure if these are related: 1) Plasmashell crashes and restarts, and the KDE bug reporter is started. A crash report is attached. 2) Plasmashell freezes and stops working (CPU usage goes to 100% of 1 core) but keyboard and mouse still work and can be used to switch between tasks or to access text console. 3) Plasmashell freezes and keyboard and mouse are frozen too. Only kernel SysRq keys can be used to reboot the computer or sometimes to recover from the situation without rebooting. I think this problem, and especially nr. 3), happens more often if you move the mouse over the menu immediately after clicking the menu icon, i.e. before the menu opening effect has finished. Or, move the mouse *very* fast over the opened menu. This does not seem to happen when X11 is used. System information: Arch Linux, x86-64, kernel version (uname -a): 4.17.5-1-ARCH Plasma package versions: 5.13.3-1 GPU: Nvidia GTX 980 Ti Driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 391703] New: Some SVG elements are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=391703 Bug ID: 391703 Summary: Some SVG elements are not displayed correctly Product: karbon Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: kurko2...@gmail.com Target Milestone: --- Created attachment 111316 --> https://bugs.kde.org/attachment.cgi?id=111316&action=edit example files Some elements of SVG files are not displayed correctly. Examples are attached. example1.svg: The X-axis title text is not displayed in the correct location. If the texts are converted to paths (e.g. by using Inkscape), this problem does not occur. example2.svg: Legend text colors are wrong. Firefox can display both images without problems. Karbon version is 2.9.11 on Debian Stretch. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 391704] New: Minor problems with EPS images
https://bugs.kde.org/show_bug.cgi?id=391704 Bug ID: 391704 Summary: Minor problems with EPS images Product: karbon Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: kurko2...@gmail.com Target Milestone: --- Created attachment 111317 --> https://bugs.kde.org/attachment.cgi?id=111317&action=edit examples Some EPS images are not displayed exactly as they should be. Examples are attached. Both examples: Curves extend outside the plot area. example_noText.eps: Same image as example.eps, but texts have been converted to paths. Same problem occurs. Additionally, the text elements appear to be filled with solid color. Evince and Okular should display the files correctly. Karbon version is 2.9.11 on Debian Stretch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed
https://bugs.kde.org/show_bug.cgi?id=345563 Johan changed: What|Removed |Added CC|pin...@hotmail.com | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481288] Gdrive invalid protocol after create a Google account to access Google Drive
https://bugs.kde.org/show_bug.cgi?id=481288 Johan changed: What|Removed |Added CC||johangil...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481288] Gdrive invalid protocol after create a Google account to access Google Drive
https://bugs.kde.org/show_bug.cgi?id=481288
--- Comment #6 from Johan ---
I have a similar error when I try to open gdrive via dolphin.
org.kde.kgapi: Bad request, Google replied ' "{\n \"error\": {\n\"code\":
400,\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"errors\": [\n {\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"domain\": \"global\",\n\"reason\": \"invalidParameter\",\n
\"location\": \"fields\",\n\"locationType\": \"parameter\"\n
}\n]\n }\n}\n" '
org.kde.kgapi: Bad request, Google replied ' "{\n \"error\": {\n\"code\":
400,\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"errors\": [\n {\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"domain\": \"global\",\n\"reason\": \"invalidParameter\",\n
\"location\": \"fields\",\n\"locationType\": \"parameter\"\n
}\n]\n }\n}\n" '
kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the
"kio_gdrive" KIO worker.
--
You are receiving this mail because:
You are watching all bug changes.
[elisa] [Bug 428697] New: Elisa crashes every time when scrolling down Album list
https://bugs.kde.org/show_bug.cgi?id=428697 Bug ID: 428697 Summary: Elisa crashes every time when scrolling down Album list Product: elisa Version: 20.08.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: johanwillemd...@gmail.com Target Milestone: --- Application: elisa (20.08.2) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.9.1-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Every time I scroll down the Album list Elisa chrashes (on Xorg). The crash can be reproduced every time. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [New LWP 6908] [New LWP 6909] [New LWP 6911] [New LWP 6912] [New LWP 6913] [New LWP 6914] [New LWP 6915] [New LWP 6925] [New LWP 6926] [New LWP 6927] [New LWP 6928] [New LWP 6929] [New LWP 6933] [New LWP 6934] [New LWP 6935] [New LWP 6936] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fea5ce3de7f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fea59cd4e80 (LWP 6906))] Thread 17 (Thread 0x7fe9f27fc640 (LWP 6936)): #0 0x7fea5ce43799 in syscall () from /lib64/libc.so.6 #1 0x7fea5b09e1ef in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7fea341cbdd3 in gst_base_sink_wait_preroll () from /usr/lib64/libgstbase-1.0.so.0 #3 0x7fea341cc33d in gst_base_sink_do_preroll () from /usr/lib64/libgstbase-1.0.so.0 #4 0x7fea341ef91c in ?? () from /usr/lib64/libgstbase-1.0.so.0 #5 0x7fea341f1145 in ?? () from /usr/lib64/libgstbase-1.0.so.0 #6 0x7fea341c1450 in ?? () from /usr/lib64/libgstbase-1.0.so.0 #7 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #8 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #9 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #10 0x7fea34591c9b in gst_proxy_pad_chain_default () from /usr/lib64/libgstreamer-1.0.so.0 #11 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #12 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #13 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #14 0x7fea34591c9b in gst_proxy_pad_chain_default () from /usr/lib64/libgstreamer-1.0.so.0 #15 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #16 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #17 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #18 0x7fea341cf6ad in ?? () from /usr/lib64/libgstbase-1.0.so.0 #19 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #20 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #21 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #22 0x7fea341cf6ad in ?? () from /usr/lib64/libgstbase-1.0.so.0 #23 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #24 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #25 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #26 0x7fea34591c9b in gst_proxy_pad_chain_default () from /usr/lib64/libgstreamer-1.0.so.0 #27 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #28 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #29 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #30 0x7fea10687e9b in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #31 0x7fea345cf5ef in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #32 0x7fea5b0769e4 in ?? () from /usr/lib64/libglib-2.0.so.0 #33 0x7fea5b0760ee in ?? () from /usr/lib64/libglib-2.0.so.0 #34 0x7fea5ba19eb1 in start_thread () from /lib64/libpthread.so.0 #35 0x7fea5ce48ccf in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7fe9f2ffd640 (LWP 6935)): #0 0x7fea5ce43799 in syscall () from /lib64/libc.so.6 #1 0x7fea5b09e1ef in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7fea10686f5b in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #3 0x7fea345a5b2a in gst_pad_query () from /usr/lib64/libgstreamer-1.0.so.0 #4 0x7fea345a88ab in gst_pad_peer_query () from /usr/lib64/libgstreamer-1.0.so.0 #5 0x7fea345a90d6 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #6 0x7fea345a48ae in gst_pad_forward () from /usr/lib64/libgstreamer-1.0.so.0 #7 0x7fea345a4f96 in gst_pad_query_default () from /usr/lib64/libgstreamer-1.0.so.0 #8 0x7fea345a5b2a in gst_pad_query () from /usr/lib64/libgstreamer-1.0.so.0 #9 0x7fea345a88ab in gst_pad_peer_query () from /usr/lib64/libgstreamer-1.0.so.0 #10 0x7
[elisa] [Bug 428585] Elisa is crashing when scrolling Album view
https://bugs.kde.org/show_bug.cgi?id=428585 --- Comment #4 from Johan --- Elisa is crashing when scrolling Album view happens only when Elisa is updating Music collection. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402230] Messed up special character (──)
https://bugs.kde.org/show_bug.cgi?id=402230 Johan changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Johan --- Checking that option seems to fix it, thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #1 from johan --- Created attachment 117410 --> https://bugs.kde.org/attachment.cgi?id=117410&action=edit Plasmashell crash report from the KDE crash reporter -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #2 from johan --- Plasmashell version 5.14.4 crashed today when I had the applications menu open and was about to open the shutdown menu. It restarted automatically and the crash reporter appeared. A log is attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 johan changed: What|Removed |Added Attachment #117410|Plasmashell crash report|Crash report, plasmashell description|from the KDE crash reporter |5.14.4, using the system ||menu (shutdown submenu) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #3 from johan --- Created attachment 117416 --> https://bugs.kde.org/attachment.cgi?id=117416&action=edit Crash report, plasmashell 5.14.5, using the system menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #4 from johan --- Another crash report attached. Plasmashell version 5.14.5. Plasmashell crashed when I used the system menu/applications menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403133] New: Plenty of flickering and graphical glitches during and after startup if compositing is enabled
https://bugs.kde.org/show_bug.cgi?id=403133 Bug ID: 403133 Summary: Plenty of flickering and graphical glitches during and after startup if compositing is enabled Product: plasmashell Version: 5.14.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kurko2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Flags: X11+ When KDE desktop is being started, there's a lot of flicker and other glitches. After the startup is completed, the desktop may look normal or not. But if you move mouse over the task bar, use the applications menu, or start an application, the flickering continues. The startup splash screen often appears when this problem occurs. A workaround is to disable compositing. When compositing is off, this problem does not occur. Also, this problem does not occur with Wayland. Here's a video showing this problem: https://mega.nz/#!4pQw1AgR!Ujblms_CSSIrczLKpRapoLBiZGrM8xwXJ3JZm7-1EG8 Compositing options: Enable compositor on startup: yes Animation speed: medium Scale method: Accurate Rendering backend: OpenGL 2.0 Tearing prevention: Full screen repaints Keep window thumbnails: Only for shown windows Allow applications to block compositing: yes System information: Arch Linux, x86-64, kernel version: 4.20.0-arch1-1-ARCH Plasmashell version: 5.14.5 (also occurred with 5.14.4) GPU: Nvidia GTX 980 Ti GPU driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #6 from johan --- I changed the render loop setting to basic and it seems to be more stable indeed. I haven't experienced any crashes yet, but Plasma may sometimes freeze when trying to shut down the computer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403653] New: Random, complete desktop crashes when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=403653 Bug ID: 403653 Summary: Random, complete desktop crashes when Wayland is used Product: plasmashell Version: 5.14.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: kurko2...@gmail.com Target Milestone: 1.0 Flags: Wayland+ Created attachment 117676 --> https://bugs.kde.org/attachment.cgi?id=117676&action=edit dmesg and coredump information (I'm not sure if Plasmashell is the correct category for this - please change it if needed.) When KDE desktop is used with Wayland, the desktop sometimes crashes completely and returns to the SDDM login screen. Most processes of the user are also terminated when this happens. This occurs randomly and not very often. The desktop may work for hours before it crashes. The crash may occur at any moment. I haven't noticed any specific actions that lead to crash. Please note that render loop is set to Basic in "kcmshell5 qtquicksettings" as suggested in the comments of bug #396614 Some dmesg and core dump information is attached. This time only drkonqi appeared in the core dumps. Sometimes other processes appear as well. System information: Arch Linux, x86-64, kernel version (uname -r): 4.20.3-arch1-1-ARCH Plasma package versions: 5.14.5-2 GPU: Nvidia GTX 980 Ti Driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 403654] New: Konversation crashed on shutdown
https://bugs.kde.org/show_bug.cgi?id=403654 Bug ID: 403654 Summary: Konversation crashed on shutdown Product: konversation Version: 1.7.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: kurko2...@gmail.com Target Milestone: --- Created attachment 117677 --> https://bugs.kde.org/attachment.cgi?id=117677&action=edit report from drkonqi When Konversation is closed, it may crash. A report from drkonqi is attached. This crash occurred after clicking "yes" in the prompt that appeared when attempting to closing Konversation. This occurred when Wayland was used, but I don't know if Wayland is related to the crash. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 403654] Konversation crashed on shutdown
https://bugs.kde.org/show_bug.cgi?id=403654 --- Comment #1 from johan --- Created attachment 117686 --> https://bugs.kde.org/attachment.cgi?id=117686&action=edit Core dump information -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403653] Random, complete desktop crashes when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=403653 --- Comment #1 from johan --- Created attachment 117687 --> https://bugs.kde.org/attachment.cgi?id=117687&action=edit Core dump information Another crash. Again only drkonqi appeared in core dumps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453438] New: Crashed when login
https://bugs.kde.org/show_bug.cgi?id=453438
Bug ID: 453438
Summary: Crashed when login
Product: kwin
Version: 5.24.5
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: johanbe...@gmail.com
Target Milestone: ---
Application: kwin_x11 (5.24.5)
Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.13.0-40-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Restarted after install updates.
- Unusual behavior I noticed:
None unusual behavior were noticed.
The crash can be reproduced every time.
-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
[New LWP 2682]
[New LWP 2687]
[New LWP 2689]
[New LWP 2703]
[New LWP 2709]
[New LWP 2713]
[New LWP 2726]
[New LWP 2727]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f27f7acd9cf in __GI___poll (fds=0x7ffe8f988ff8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="constructor",file="/usr/share/kwin/scripts/bismuth/contents/code/index.mjs",fullname="/usr/share/kwin/scripts/bismuth/contents/code/index.mjs",line="2024",language="js"},".
-
(beware that frames may have been optimized out)
[Current thread is 1 (Thread 0x7f27f313c9c0 (LWP 2669))]
Thread 9 (Thread 0x7f27b700 (LWP 2727)):
#0 0x7f27f7acdac6 in __ppoll (fds=0x7f27b4000d98, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44
#1 0x7f27f8bb8559 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#2 0x7f27f8bb9c03 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#3 0x7f27f8b6087b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x7f27f897a442 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x7f27f897b623 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7f27f875f609 in start_thread (arg=) at
pthread_create.c:477
#7 0x7f27f7ada163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 8 (Thread 0x7f27d48a9700 (LWP 2726)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55ec569d4230) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ec569d41e0,
cond=0x55ec569d4208) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55ec569d4208, mutex=0x55ec569d41e0) at
pthread_cond_wait.c:638
#3 0x7f27ea63a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x7f27ea63a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5 0x7f27f875f609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f27f7ada163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 7 (Thread 0x7f27d50aa700 (LWP 2713)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55ec568a4d58) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ec568a4d08,
cond=0x55ec568a4d30) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55ec568a4d30, mutex=0x55ec568a4d08) at
pthread_cond_wait.c:638
#3 0x7f27ea63a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x7f27ea63a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5 0x7f27f875f609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f27f7ada163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 6 (Thread 0x7f27d59ec700 (LWP 2709)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x7f27f00b8550) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f27f00b8500,
cond=0x7f27f00b8528) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x7f27f00b8528, mutex=0x7f27f00b8500) at
pthread_cond_wait.c:638
#3 0x7f27ea63a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x7f27ea63a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5 0x7f27f875f609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f27f7ada163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 5 (Thread 0x7f27d6dee700 (LWP 2703)):
#0 0x7f27f8bb9a59 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x7f27f8b6087b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#2 0x7f27f897a442 in QThread::exec() () from
/li
[konqueror] [Bug 67859] [test case] Overflowed Text and Anchors don't seem to work
https://bugs.kde.org/show_bug.cgi?id=67859 Johan changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|CONFIRMED |RESOLVED --- Comment #11 from Johan --- (In reply to Justin Zobel from comment #10) > Thank you for the bug report. > > As this report hasn't seen any changes in 10 years or more, we ask if you > can please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. Hi Justin, Thank you for reminding me that I opened this bug maaany years ago. I thought it would have been automatically closed a long time ago (as it is the case on many other bug trackers) but now it is... ;-) Best regards, Johan -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 391703] Some SVG elements are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=391703 johan changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from johan --- I confirm that this bug still exists in Karbon 3.2.1 on Debian 11 Bullseye. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 391704] Minor problems with EPS images
https://bugs.kde.org/show_bug.cgi?id=391704 johan changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from johan --- I confirm that this bug still exists in Karbon 3.2.1 on Debian 11 Bullseye. Additionally, the image seems to be improperly placed on the canvas/page. I don't remember if this problem occurred when this bug was reported. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] New: Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 Bug ID: 404571 Summary: Complete desktop crash when Wayland is used Product: kwin Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kurko2...@gmail.com Target Milestone: --- Flags: Wayland+, nouveau+ Created attachment 118203 --> https://bugs.kde.org/attachment.cgi?id=118203&action=edit dmesg and core dump information Sometimes when using KDE desktop with Wayland, the desktop crashes completely. This occurs randomly. The system typically returns to the SDDM login screen. Bug #403653 is related. Crash information of KWin was requested. A file is attached, containing some information from dmesg and coredumpctl. For some reason the core dump is truncated. I'll try to provide a complete one later. No other core dumps were created when this crash occurred. System information: Arch Linux, x86-64, kernel version: 4.20.8-arch1-1-ARCH KWin package version: 5.15.0-1 GPU: Nvidia GTX 980 Ti Driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze Please note that render loop is set to Basic in "kcmshell5 qtquicksettings" as suggested in the comments of bug #396614 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 johan changed: What|Removed |Added Attachment #118203|0 |1 is obsolete|| --- Comment #3 from johan --- Created attachment 118231 --> https://bugs.kde.org/attachment.cgi?id=118231&action=edit dmesg and non-truncated core dump information New core dump information and some messages from dmesg attached -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403133] Plenty of flickering and graphical glitches during and after startup if compositing is enabled
https://bugs.kde.org/show_bug.cgi?id=403133 --- Comment #2 from johan --- After some updates, this does not occur anymore. I don't know if it was due to a KDE or Nouveau bug but it's gone anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #5 from johan --- Created attachment 118381 --> https://bugs.kde.org/attachment.cgi?id=118381&action=edit crash dump information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #6 from johan --- Created attachment 118382 --> https://bugs.kde.org/attachment.cgi?id=118382&action=edit crash dump information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #7 from johan --- Created attachment 118383 --> https://bugs.kde.org/attachment.cgi?id=118383&action=edit crash dump information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #8 from johan --- Created attachment 118384 --> https://bugs.kde.org/attachment.cgi?id=118384&action=edit crash dump information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #9 from johan --- So are these crash reports completely useless without debugging symbols? I can try to install symbols next but it seems to be a bit complicated. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358231] desktop locks up when moving files
https://bugs.kde.org/show_bug.cgi?id=358231 johan changed: What|Removed |Added CC||kurko2...@gmail.com --- Comment #19 from johan --- I can confirm this on Arch Linux. Moving as few as 10 small files using Dolphin can cause the desktop to freeze for 10 seconds or so. plasma-desktop package is 5.13.5-1 and dolphin is 18.08.1-2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380384] Plasma-Wayland completely freezing on Nouveau driver
https://bugs.kde.org/show_bug.cgi?id=380384 johan changed: What|Removed |Added CC||kurko2...@gmail.com --- Comment #11 from johan --- Could bug #396614 be related? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] New: Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 Bug ID: 396614 Summary: Plasmashell + Wayland - frequent hangs/crashes when opening start menu Product: plasmashell Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: kurko2...@gmail.com Target Milestone: 1.0 Flags: Wayland+ Created attachment 113990 --> https://bugs.kde.org/attachment.cgi?id=113990&action=edit Crash report from KDE crash reporter When opening or using the applications menu/start menu when using Wayland, Plasmashell often hangs or crashes. This can happen in several different ways but I'm not sure if these are related: 1) Plasmashell crashes and restarts, and the KDE bug reporter is started. A crash report is attached. 2) Plasmashell freezes and stops working (CPU usage goes to 100% of 1 core) but keyboard and mouse still work and can be used to switch between tasks or to access text console. 3) Plasmashell freezes and keyboard and mouse are frozen too. Only kernel SysRq keys can be used to reboot the computer or sometimes to recover from the situation without rebooting. I think this problem, and especially nr. 3), happens more often if you move the mouse over the menu immediately after clicking the menu icon, i.e. before the menu opening effect has finished. Or, move the mouse *very* fast over the opened menu. This does not seem to happen when X11 is used. System information: Arch Linux, x86-64, kernel version (uname -a): 4.17.5-1-ARCH Plasma package versions: 5.13.3-1 GPU: Nvidia GTX 980 Ti Driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 391703] New: Some SVG elements are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=391703 Bug ID: 391703 Summary: Some SVG elements are not displayed correctly Product: karbon Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: kurko2...@gmail.com Target Milestone: --- Created attachment 111316 --> https://bugs.kde.org/attachment.cgi?id=111316&action=edit example files Some elements of SVG files are not displayed correctly. Examples are attached. example1.svg: The X-axis title text is not displayed in the correct location. If the texts are converted to paths (e.g. by using Inkscape), this problem does not occur. example2.svg: Legend text colors are wrong. Firefox can display both images without problems. Karbon version is 2.9.11 on Debian Stretch. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 391704] New: Minor problems with EPS images
https://bugs.kde.org/show_bug.cgi?id=391704 Bug ID: 391704 Summary: Minor problems with EPS images Product: karbon Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: kurko2...@gmail.com Target Milestone: --- Created attachment 111317 --> https://bugs.kde.org/attachment.cgi?id=111317&action=edit examples Some EPS images are not displayed exactly as they should be. Examples are attached. Both examples: Curves extend outside the plot area. example_noText.eps: Same image as example.eps, but texts have been converted to paths. Same problem occurs. Additionally, the text elements appear to be filled with solid color. Evince and Okular should display the files correctly. Karbon version is 2.9.11 on Debian Stretch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed
https://bugs.kde.org/show_bug.cgi?id=345563 Johan changed: What|Removed |Added CC|pin...@hotmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380503] New: Plasma can't start and always crashes at startup
https://bugs.kde.org/show_bug.cgi?id=380503 Bug ID: 380503 Summary: Plasma can't start and always crashes at startup Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pin...@hotmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.8.0-36-generic i686 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Just startup Kubuntu - Unusual behavior I noticed: No desktop appeared - Custom settings of the application: None: default install of Kubuntu 16.04.2 (fresh install) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb1ac1800 (LWP 1252))] Thread 8 (Thread 0xa1313b40 (LWP 1515)): #0 0xb76f4ce5 in __kernel_vsyscall () #1 0xb76f4979 in __vdso_clock_gettime () #2 0xb4d38142 in __GI___clock_gettime (clock_id=1, tp=0xa1312f04) at ../sysdeps/unix/clock_gettime.c:115 #3 0xb509c338 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #4 0xb522b232 in QTimerInfoList::updateCurrentTime() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb522b754 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb522cd19 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb43bf5db in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb43c0024 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb43c0254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0xb522d964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb51d27a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb51d2bfa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #13 0xb4ff8f1d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #14 0xa1841980 in KCupsConnection::run() () from /usr/lib/i386-linux-gnu/libkcupslib.so #15 0xb4ffe43b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #16 0xb4bd3295 in start_thread (arg=0xa1313b40) at pthread_create.c:333 #17 0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 7 (Thread 0xa9285b40 (LWP 1344)): #0 0xb43bcf00 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb43bf9f0 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb43c00b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb43c0254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb522d964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb51d27a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb51d2bfa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb4ff8f1d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb6c4a7a9 in ?? () from /usr/lib/i386-linux-gnu/libQt5Quick.so.5 #9 0xb4ffe43b in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb4bd3295 in start_thread (arg=0xa9285b40) at pthread_create.c:333 #11 0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 6 (Thread 0xaa950b40 (LWP 1333)): #0 0xb76f4ce5 in __kernel_vsyscall () #1 0xb4bd8a6c in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187 #2 0xb4d3764d in __pthread_cond_wait (cond=0xb76648d0, mutex=0xb76648b8) at forward.c:149 #3 0xb752ca2c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5 #4 0xb752ca6c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5 #5 0xb4bd3295 in start_thread (arg=0xaa950b40) at pthread_create.c:333 #6 0xb4d2aeee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 5 (Thread 0xaba78b40 (LWP 1302)): #0 0xb4406488 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb43bfa65 in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb43c00b1 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb43c0254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb522d964 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb51d27a3 in QEventLoop::processEvents(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb51d2bfa in QEventLoop::exec(QFlags) () from /usr/lib/i386-linux-gnu/sse2/libQt5Co
[marble] [Bug 373104] New: Map data broken in Alingsås
https://bugs.kde.org/show_bug.cgi?id=373104 Bug ID: 373104 Summary: Map data broken in Alingsås Product: marble Version: Marble Maps 1.0 (Android) Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: e8jo...@gmail.com Target Milestone: --- In the city of Alingsås, Sweden, the river going through the city is rendered wrong. For instance, the roads Tennisgatan, Sidenvägen, Mjörngatan are not partially flooded. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388759] Constant screen repaints after display configuration is changed
https://bugs.kde.org/show_bug.cgi?id=388759 Johan Hartzenberg changed: What|Removed |Added CC||jo...@webmaster.co.za --- Comment #2 from Johan Hartzenberg --- I can confirm this issue. HP ProBook 6560b Intel i915 KDE Neon 5.11 Linux komputer 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389218] Patch: Massive repaints in plasmashell due to missing patch in Qt 5.9.3
https://bugs.kde.org/show_bug.cgi?id=389218 Johan Hartzenberg changed: What|Removed |Added CC||jo...@webmaster.co.za -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 Johan Hartzenberg changed: What|Removed |Added CC||jo...@webmaster.co.za --- Comment #58 from Johan Hartzenberg --- I am also affected by high CPU and Memory related issues in plasmashell/kwin_x11. I got the feeling though that the high CPU was the system trying to find pages to swap, etc e.g dealing with the memory "leak" in plasmashell. My Linux debugging skills does not allow me to verify this suspicion. After reading this thread as well as other discussions (Kubuntuforums) I have now removed all but the most essential plasmoids. I will monitor but this is rather irksome. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478248] plasmashell ERROR:ssl_client_socket_impl.cc(975) handshake failed; returned -1, SSL error code 1, net_error -100 in system log
https://bugs.kde.org/show_bug.cgi?id=478248 Johan Sandgren changed: What|Removed |Added CC||johan...@axis.com --- Comment #2 from Johan Sandgren --- (In reply to qtm4ig from comment #1) > please close this bug. > I understood what the problem is Can you please share more details what you understood/found qtm4ig? I see this also but have no clue how to resolve it, if no bug still. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484470] Dolphin KIO gdrive unable to open google drive folder. "Loading folder" displayed indefinitely.
https://bugs.kde.org/show_bug.cgi?id=484470 Rony Johan changed: What|Removed |Added Version|23.08.3 |23.08.5 CC||ronyjohan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] New: Periodic flicker on secondary monitor with fullscreen window on primary monitor
https://bugs.kde.org/show_bug.cgi?id=481750 Bug ID: 481750 Summary: Periodic flicker on secondary monitor with fullscreen window on primary monitor Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jo...@skold.cc Target Milestone: --- SUMMARY Using wayland with two monitors: - Dell AW3423DW, 3440x1440 @ 175 Hz, DisplayPort - cocopar 133LR, 1920x1080 @ 60 Hz, HDMI My GPU is an AMD RX 6900 XT, and I'm using the RADV vulkan drivers (v. 24.0.1). The AMDVLK drivers are not installed. Whenever I have a window in fullscreen on the Dell monitor, the cocopar will flicker from time to time. As in it goes black for a second or two before coming back on. Sometimes I can go several minutes without seeing the flicker, other times it happens again within seconds. It seems to happen very frequently when toggling fullscreen on or off, so that's a fast way to repro. If I force atomic modesetting off (`KWIN_DRM_NO_AMS=1`) it's a 100% repro rate whenever toggling fullscreen on or off. STEPS TO REPRODUCE 1. Have two monitors connected and configured to extend the desktop. 2. Toggle fullscreen on or off in some application on one monitor. OBSERVED RESULT The second monitor turns off and on again. EXPECTED RESULT The second monitor does not turn off. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.6-zen1-1-zen / 6.0 RC2 KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION - The Dell monitor never flickers, it's always the cocopar. - Toggling fullscreen on or off on the cocopar also causes it to flicker. - The same setup worked in an older version of plasma (unsure of what version, but whatever was in arch's repos a few months ago), with `KWIN_DRM_NO_AMS=1`. Unsure about without. - The same setup also works in sway, with or without atomic modesetting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 Johan Sköld changed: What|Removed |Added Summary|Periodic flicker on |Periodic flicker on |secondary monitor with |secondary monitor with |fullscreen window on|fullscreen window on any |primary monitor |monitor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #1 from Johan Sköld --- To clarify: It flickers regardless of if a window is fullscreened on my first or second monitor. I wrote most of the original summary before verifying that, and forgot to update parts of it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #2 from Johan Sköld --- Sorry, one more thing to add that I just noticed. If I open Spectacle and press "Rectangular Region", the monitor flickers off/on every single time I move the mouse cursor. Regardless of which monitor I move it on. And I thought to check `journalctl`. Looking at the last 50 thousand lines, just about every single line says: feb 24 00:13:58 pc kwin_wayland[2937]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glUniformMatrix(matrix size mismatch) The even remotely relevant lines that don't say that are: feb 24 00:09:34 pc kwin_wayland[2937]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x592bbe8e7690) [...] feb 24 00:10:16 pc systemd[2870]: Starting Spectacle screenshot capture utility... [...] feb 24 00:10:16 pc spectacle[6436]: QApplication: invalid style override 'adwaita-dark' passed, ignoring it. Available styles: Breeze, Oxygen, Windows, Fusion [...] feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: VAAPI: Failed to initialize display feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: DRM device not found feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: VAAPI: Failed to initialize display feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: DRM device not found feb 24 00:10:16 pc systemd[2870]: Started Spectacle screenshot capture utility. [...] feb 24 00:10:16 pc plasmashell[3214]: QQuickItem: Cannot set FocusScope once item has children and is in a window. [...] feb 24 00:11:18 pc plasmashell[3214]: error creating screencast "Could not find window id 0" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #4 from Johan Sköld --- Created attachment 166080 --> https://bugs.kde.org/attachment.cgi?id=166080&action=edit Image shifting on monitor before it turns off. Thanks for the link. I applied that patch to version 5.93.0 of kwin and built it, and while it did get rid of the journalctl spam, my monitor still flickers when I enter or exit fullscreen with some window, and occasionally while just having a window fullscreened. So the original problem is still there. If it helps, just before the monitor turns off the image shifts a bit. When entering fullscreen it shifts down, while when leaving fullscreen it shifts up. Attaching a slow-mo clip of what it looks like when entering fullscreen on my other monitor (just out of view). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #6 from Johan Sköld --- It does not, the same thing still happens. Even more weirdly, it happens when I fullscreen a transparent window as well, so I don't think direct scanout would be active either way? Although I just realized what's causing it. I remembered my second monitor technically supports VRR, but tends to flicker when it's enabled (only in Linux though, likely a driver bug). Both my monitors had VRR set to "Automatic". If I disable it on the second monitor the flicker stops. Is it possible that KWin enabled VRR on the second monitor too when fullscreening something on my main monitor? Otherwise this may also be some driver bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434785] New: Proposal: Operation to move subtitle to playhead
https://bugs.kde.org/show_bug.cgi?id=434785 Bug ID: 434785 Summary: Proposal: Operation to move subtitle to playhead Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jvrom...@squirrel.nl Target Milestone: --- This is an enhancement request for an operation that speeds up adding subtitles. Tentative operation name: "move subtitle to playhead", hereafter referred to as MSTP. Semantics: - When the playhead is BEFORE a subtitle, move the start of this subtitle to the playhead position. - When the playhead is IN a subtitle, move the start of the subtitle to the playhead position. - Otherwise it is ignored. Rationale: In most cases the text of the subtitles is available in some text document. You can create a subtitle and copy/paste all text lines into in. Make this subtitle long. - Now start playing until the playhead is at the point where the next subtitle should start. - Activate MSTP and the subtitles moves to the playhead. - Continue to play until the playhead reaches the end of the subtitle. - Use the scissors tool to split off the first line of the subtitles. - Start playing until the playhead is at the point where the next subtitle should start, SMTP, etc... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424025] New: Cannot render to mp4
https://bugs.kde.org/show_bug.cgi?id=424025 Bug ID: 424025 Summary: Cannot render to mp4 Product: kdenlive Version: 20.04.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: e8jo...@gmail.com Target Milestone: --- SUMMARY When trying to render to mp4, the UI claims that libx264 isn't available. When generating a mlt-script and hacking it, I can still render using libx264. STEPS TO REPRODUCE 1. Create video project 2. Select render 3. Attempt to render to mp4 OBSERVED RESULT "Unsupported video codec: libx264" EXPECTED RESULT No warnings or errors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian testing, dist-upgraded today (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION As mentioned, I can hack the mlt file and run it as a script, it just works. It would be nice to either have this fixed, or to being able to override this warning and just run melt even though kdenlive thinks there will be issues. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424025] Cannot render to mp4
https://bugs.kde.org/show_bug.cgi?id=424025 Johan Thelin changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from Johan Thelin --- It works after doing a dist-upgrade today (with the distro release). I suspect it has to do with the ffmpeg update made this week. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420678] Meta key not working in Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=420678 --- Comment #2 from Johan Zietsman --- Hi Nate Yes, "Alt+F1" is shown here. On Mon, Apr 27, 2020 at 11:45 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=420678 > > Nate Graham changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > Please go to [Right-click on Application Launcher] > Configure Application > Launcher > Keyboard Shortcuts. > > Do you see "Alt+F1" listed as the shortcut there? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420678] New: Meta key not working in Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=420678 Bug ID: 420678 Summary: Meta key not working in Kubuntu 20.04 Product: plasmashell Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: johan.ziets...@ex-mente.co.za CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I installed Kubuntu 20.04 on my Dell Vostro 5481 laptop today. The Meta key is not working. STEPS TO REPRODUCE 1. Sign into Kubuntu. 2. Press the Meta key. 3. Nothing happens. OBSERVED RESULT Nothing happens when I press the Meta key. EXPECTED RESULT I expect the Application Launcher menu to pop up when I press the Meta key. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458460] New: Allow for moving mouse diagonally to select instance of app
https://bugs.kde.org/show_bug.cgi?id=458460 Bug ID: 458460 Summary: Allow for moving mouse diagonally to select instance of app Product: plasmashell Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: johan.borglin.sjo...@gmail.com Target Milestone: 1.0 Created attachment 151678 --> https://bugs.kde.org/attachment.cgi?id=151678&action=edit Reproducton steps SUMMARY Task manager currently swaps shown preview window too quickly. When going to select a preview instance of an app the mouse pointer will naturally touch other running app icons as part of travelling the shortest distance to the app preview. This causes the previous app preview to be lost. Best way of understanding this is watching the attached video, I think. STEPS TO REPRODUCE 1. Have a Task manager widget ready 2. Launch two of one app, one of another 2. Hover over the app with two instances, causing preview windows for the app to show 3. Attempt to take shortest route with mouse to 2nd instance to the right (that is: move diagonally) 4. This will cause the mouse to touch the app to the right of the current app in the task manager bar OBSERVED RESULT The preview windows of the 2 app will disappear, and the preview window of the other app will appear EXPECTED RESULT Some delay in showing the other app, allowing the user to select the 2nd instance of the originally previewed app. Currently, the user must first go up and then to the right, to avoid touching any other app. This is super annoying! Requiring the mouse to stand still on the app before switching preview would be great. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 --- Comment #41 from Johan Sjölén --- Thank you Nate, for directing my bug to this one. I saw that there has been a suggested fix based on "triangle mouse filtering". Such a solution seems to previously have been implemented for something else, but the other way around. So at least the technique as named seems legitimate. https://phabricator.kde.org/D13192 Unfortunately Bharadwaj seems to have abandoned their fix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454349] Searching for something automatically selects the second item instead of the first
https://bugs.kde.org/show_bug.cgi?id=454349 Johan Sköld changed: What|Removed |Added CC||jo...@skold.cc --- Comment #8 from Johan Sköld --- I can reproduce this consistently as well in kickoff, but I also seem to have figured out what happens (but not why). 1. Open kickoff and search for something 2. Highlight one of the options with the mouse 3. Press escape to close kickoff 4. Move the cursor away 5. Open kickoff and search for something again (it doesn't have to be the same term) When I do that, it selects the same entry that I hovered with the mouse in step 2. So if I hovered the third entry, it will select the third entry. It sometimes even reproduces without searching for anything once you re-open kickoff, if you had the cursor in a position where it would highlight something in the default view. If I search for something and hover the 6th entry on the left side of the view, once I re-open kickoff it selects "Games" without me doing anything. KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #35 from Johan Sköld --- It happened again this morning, so I looked at `journalctl` in a tty before unlocking it. Nothing appears to show up when I click "Unlock", but there are a few lines that appear to be potentially relevant earlier in the log. Filtered to skip device connect spam from switching back/forth between ttys: > Jul 18 11:57:58 pc kwin_wayland[2002]: QMetaProperty::read: Unable to handle > unregistered datatype 'KWin::SessionState' for property > 'KWin::EffectsHandlerImpl::sessionState' > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: > QML Connections: Detected function "onConfigurationChanged" in Connections > element. This is probably intended to be a signal handler but no signal of > the target matches the name. > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: > QML Connections: Detected function "onRepaintNeeded" in Connections element. > This is probably intended to be a signal handler but no signal of the target > matches the name. > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:67: > TypeError: Cannot read property 'wallpaper' of null > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:71: > TypeError: Cannot read property 'wallpaper' of null > Jul 18 11:57:59 pc plasmashell[2195]: qt.qpa.wayland: Wayland does not > support QWindow::requestActivate() > Jul 18 11:57:59 pc plasmashell[2195]: qt.qpa.wayland: Wayland does not > support QWindow::requestActivate() > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: qt.qpa.wayland: Wayland does > not support QWindow::requestActivate() > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: qt.qpa.wayland: Wayland does > not support QWindow::requestActivate() > Jul 18 11:58:05 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool > Jul 18 11:58:05 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool There's also a bit of bismuth spam since I installed that yesterday to give it a try, but I did not have that installed yet when I ran into this yesterday so it seems unrelated and I thus filtered it out above. Operating System: EndeavourOS KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 486804] New: KDE Neon systemupdate fails for several days
https://bugs.kde.org/show_bug.cgi?id=486804 Bug ID: 486804 Summary: KDE Neon systemupdate fails for several days Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: wauters.jo...@telenet.be CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- Created attachment 169339 --> https://bugs.kde.org/attachment.cgi?id=169339&action=edit screenshot of the actual bug. KDE Neon system update seems to fail for a few days now. Tried serveeral times, even afer a clean reboot of the system. See attachment -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427545] Dual DisplayPort monitors (tiled, MST, e.g. 5k) are not supported by KWin
https://bugs.kde.org/show_bug.cgi?id=427545 Johan Toft changed: What|Removed |Added CC||johan.t...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393781] wallpaper cannot span multiple screens
https://bugs.kde.org/show_bug.cgi?id=393781 Johan Toft changed: What|Removed |Added CC||johan.t...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 491405] New: Using the controle box of a tranaction the screen of my laptop blinks black.
https://bugs.kde.org/show_bug.cgi?id=491405 Bug ID: 491405 Summary: Using the controle box of a tranaction the screen of my laptop blinks black. Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: buildsystem Assignee: kmymoney-de...@kde.org Reporter: wolthu...@proton.me Target Milestone: --- If I had modified a transaction, then at least I use the Status box to put on Controlled. If I hid this box my screen of my laptop starts blink black. It starts after the update version 5.1.3 and the new version of Linux MInt 22.0 Wilma. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434785] Proposal: Operation to move subtitle to playhead
https://bugs.kde.org/show_bug.cgi?id=434785 --- Comment #3 from Johan Vromans --- Thanks for the suggestion. It surely helps, but the frequent (and necessary) switching between the subtitle edit window and the track (to make it active) is still less than optimal. Nevertheless I can live with it. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 Johan Manuel changed: What|Removed |Added CC||johan.man...@live.fr --- Comment #41 from Johan Manuel --- *** Bug 338501 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 338501] Monitor doesn't go to sleep when the screen is locked
https://bugs.kde.org/show_bug.cgi?id=338501 Johan Manuel changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE --- Comment #4 from Johan Manuel --- Unfortunately I don't have the right setup to try and reproduce this now, but I think this is in fact a duplicate of https://bugs.kde.org/show_bug.cgi?id=348529 as a comment above indicated, so I will close it as such. *** This bug has been marked as a duplicate of bug 348529 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 --- Comment #45 from Johan Sjölén --- (In reply to Bharadwaj Raju from comment #43) > (In reply to Johan Sjölén from comment #41) > > Unfortunately Bharadwaj seems to have abandoned their fix. > > I suppose if you're looking at > https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/832, it might > appear "abandoned" since there is only one code review comment on the whole > thread. Most of the discussion is in the corresponding Plasma Frameworks MR > here: > https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/442. > Please follow that for progress. Hi Bharadwaj! I saw that your more generalized PR was merged, awesome job :-). Do you happen to know whether this ticket should be considered fixed? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400103] Feature Request remember last used directory in places (Save as dialog)
https://bugs.kde.org/show_bug.cgi?id=400103 Johan Mittermeier changed: What|Removed |Added CC||johan.mitterme...@gmx.de --- Comment #7 from Johan Mittermeier --- Oh yes, could we have that please? Just created an account to add a comment here. I was looking for a replacement for acroread and okular seems to be the only alternative that has almost all the features acroread had. But saving always starts in a tmp directory of my browser and I need many clicks to get to the directory I want to save downloads. If I click more pdfs that go in the same directory I have to do all these clicks over and over again :( Please add this feature! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388759] Constant screen repaints after display configuration is changed
https://bugs.kde.org/show_bug.cgi?id=388759 Johan Hartzenberg changed: What|Removed |Added CC||jo...@webmaster.co.za --- Comment #2 from Johan Hartzenberg --- I can confirm this issue. HP ProBook 6560b Intel i915 KDE Neon 5.11 Linux komputer 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:40:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389218] Patch: Massive repaints in plasmashell due to missing patch in Qt 5.9.3
https://bugs.kde.org/show_bug.cgi?id=389218 Johan Hartzenberg changed: What|Removed |Added CC||jo...@webmaster.co.za -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 Johan Hartzenberg changed: What|Removed |Added CC||jo...@webmaster.co.za --- Comment #58 from Johan Hartzenberg --- I am also affected by high CPU and Memory related issues in plasmashell/kwin_x11. I got the feeling though that the high CPU was the system trying to find pages to swap, etc e.g dealing with the memory "leak" in plasmashell. My Linux debugging skills does not allow me to verify this suspicion. After reading this thread as well as other discussions (Kubuntuforums) I have now removed all but the most essential plasmoids. I will monitor but this is rather irksome. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 373104] New: Map data broken in Alingsås
https://bugs.kde.org/show_bug.cgi?id=373104 Bug ID: 373104 Summary: Map data broken in Alingsås Product: marble Version: Marble Maps 1.0 (Android) Platform: Android OS: Android 5.x Status: UNCONFIRMED Severity: normal Priority: NOR Component: android Assignee: marble-b...@kde.org Reporter: e8jo...@gmail.com Target Milestone: --- In the city of Alingsås, Sweden, the river going through the city is rendered wrong. For instance, the roads Tennisgatan, Sidenvägen, Mjörngatan are not partially flooded. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 491810] New: Crash when fething calendar
https://bugs.kde.org/show_bug.cgi?id=491810 Bug ID: 491810 Summary: Crash when fething calendar Classification: Frameworks and Libraries Product: Akonadi Version: 5.24.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: EWS Resource Assignee: kdepim-b...@kde.org Reporter: johan.erla...@gmail.com CC: c...@carlschwan.eu, kri...@op.pl Target Milestone: --- SUMMARY I have suffered from kmail not sending mail to crashes in ews. What I can see is that ews starts fetching calendar items, 0 of 14 (0% done). It doesn't change until it crashes or I force restart of akonadi. STEPS TO REPRODUCE 1. Configure kmail 2. Subscriptions 3. Check Calendar 4. Press ok and wait for problem to start. I takes some time for the problem to begin. I realise that this might not fail for all since it could be something in my outlook calendar that not all have. OBSERVED RESULT The resource waits for download of Calendar items. After a while it stops fetching mail, sending is impossible and then it crashes. EXPECTED RESULT Calendar items is fetched. Rest of kmail is working like fetching mail and sending. SOFTWARE/OS VERSIONS Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-40-generic (64-bit) Graphics Platform: offscreen Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics ADDITIONAL INFORMATION Backtrace (I hope this can give a hint of why it crashes) #0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at ./nptl/pthread_sigmask.c:43 #1 0x75a63d2454fd in __GI___sigprocmask (how=, set=, oset=) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x75a63df800d4 in KCrash::setCrashHandler (handler=handler@entry=0x0) at ./src/kcrash.cpp:419 #3 0x75a63df826b7 in KCrash::defaultCrashHandler (sig=11) at ./src/kcrash.cpp:630 #4 #5 std::__atomic_base::operator++ (this=0x18) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:118 #6 QAtomicOps::ref (_q_value=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:283 #7 QBasicAtomicInteger::ref (this=0x18) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:118 #8 QSharedPointer::ref (this=0x7ffc8de67310) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:509 #9 QSharedPointer::QSharedPointer (other=..., this=0x7ffc8de67310) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:371 #10 EwsFetchCalendarDetailJob::exceptionItemsFetched (this=, job=) at /usr/src/kdepim-runtime-4:23.08.5-0ubuntu3/resources/ews/calendar/ewsfetchcalendardetailjob.cpp:179 #11 0x75a63dd12e16 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8de674a0, r=0x5c4cd251aa60, this=0x5c4cd231dc10) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x5c4cd2a56ff0, signal_index=6, argv=0x7ffc8de674a0) at kernel/qobject.cpp:3925 #13 0x75a63dd0b697 in QMetaObject::activate (sender=sender@entry=0x5c4cd2a56ff0, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc8de674a0) at kernel/qobject.cpp:3985 #14 0x75a647782266 in KJob::result (this=this@entry=0x5c4cd2a56ff0, _t1=, _t1@entry=0x5c4cd2a56ff0, _t2=...) at /usr/src/kcoreaddons-5.115.0-0ubuntu5/obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #15 0x75a6477880eb in KJob::finishJob (this=0x5c4cd2a56ff0, emitResult=) at /usr/src/kcoreaddons-5.115.0-0ubuntu5/src/lib/jobs/kjob.cpp:98 #16 0x75a63dd12e16 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8de675d0, r=0x5c4cd2a56ff0, this=0x5c4cd2551df0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate (sender=0x5c4cd271f3e0, signal_index=6, argv=0x7ffc8de675d0) at kernel/qobject.cpp:3925 #18 0x75a63dd0b697 in QMetaObject::activate (sender=sender@entry=0x5c4cd271f3e0, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc8de675d0) at kernel/qobject.cpp:3985 #19 0x75a647782266 in KJob::result (this=this@entry=0x5c4cd271f3e0, _t1=, _t1@entry=0x5c4cd271f3e0, _t2=...) at /usr/src/kcoreaddons-5.115.0-0ubuntu5/obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #20 0x75a6477880eb in KJob::finishJob (this=0x5c4cd271f3e0, emitResult=) at /usr/src/kcoreaddons-5.115.0-0ubuntu5/src/lib/jobs/kjob.cpp:98 #21 0x75a63dd12e16 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8de676a0, r=0x5c4cd271f3e0, this=0x5c4cd26a4660) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #22 doActivate (sender=0x5c4cd24df650, signal_index=7, argv=0x7ffc8de676a0) at kernel/qobject.cpp:3925 #23 0x75a63dd0b697 in QMetaObject::activate (sender=sender@entry=0x5c4cd24df650, m=m@entry=0x75a647a22ba0 , local_signal_index=local_signal_index@en
[Akonadi] [Bug 491810] Crash when fething calendar
https://bugs.kde.org/show_bug.cgi?id=491810 Johan Erlands changed: What|Removed |Added CC||johan.erla...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 491810] Crash when fething calendar
https://bugs.kde.org/show_bug.cgi?id=491810 --- Comment #1 from Johan Erlands --- I don't think subscriptions is involved in this issue. I have deselected calendar from subscriptions and still it fetches (tries to) calendar items. It always get stuck at 0% of calendar items and it crashes when I press `Check mail`. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 491810] Crash when fething calendar
https://bugs.kde.org/show_bug.cgi?id=491810 --- Comment #4 from Johan Erlands --- Thank you, that was quick. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 382473] Breeze style breaks mouse input on Wayland compositors
https://bugs.kde.org/show_bug.cgi?id=382473
Johan Klokkhammer Helsing changed:
What|Removed |Added
CC||johan.hels...@qt.io
--- Comment #8 from Johan Klokkhammer Helsing ---
Hugo, you should be able to just delete the
XdgShellV5 {
...
}
part, since the clients can run fine on just wl_shell.
If it's still broken, there's a minimal qml compositor for the tech preview
(5.7) API here: http://blog.qt.io/blog/2016/06/13/new-compositor-api-qtwayland/
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 382473] Breeze style breaks mouse input on Wayland compositors
https://bugs.kde.org/show_bug.cgi?id=382473 --- Comment #18 from Johan Klokkhammer Helsing --- This (qtwayland) patch should fix it: https://codereview.qt-project.org/#/c/200604/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372484] New: HTML captions only show in right side panel as rendered, not editable source
https://bugs.kde.org/show_bug.cgi?id=372484
Bug ID: 372484
Summary: HTML captions only show in right side panel as
rendered, not editable source
Product: digikam
Version: 5.3.0
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Metadata-Editor
Assignee: digikam-de...@kde.org
Reporter: creideiki+kdeb...@ferretporn.se
Target Milestone: ---
I recently started writing image captions in HTML, for posting to a Piwigo
gallery. This has made editing captions in digiKam a pain.
When initially writing a caption, I can write HTML source code as I expect.
However, if I switch to another photo and then switch back, the "Captions" box
in the right sidebar ("Description" tab) now shows the caption as rendered HTML
instead, making it impossible to edit.
The caption editor should not try to interpret HTML, but instead always show
the editable source code.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 372484] HTML captions only show in right side panel as rendered, not editable source
https://bugs.kde.org/show_bug.cgi?id=372484 --- Comment #1 from Karl-Johan Karlsson --- Created attachment 102235 --> https://bugs.kde.org/attachment.cgi?id=102235&action=edit Caption editor when initially entering caption -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372484] HTML captions only show in right side panel as rendered, not editable source
https://bugs.kde.org/show_bug.cgi?id=372484 --- Comment #2 from Karl-Johan Karlsson --- Created attachment 102236 --> https://bugs.kde.org/attachment.cgi?id=102236&action=edit Caption editor after switching to another photo and back -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392376] Wayland socket buffer gets filled up and application terminates when GUI thread was blocked
https://bugs.kde.org/show_bug.cgi?id=392376 Johan Klokkhammer Helsing changed: What|Removed |Added CC||johan.hels...@qt.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392376] Wayland socket buffer gets filled up and application terminates when GUI thread was blocked
https://bugs.kde.org/show_bug.cgi?id=392376 --- Comment #2 from Johan Klokkhammer Helsing --- Maybe you can send more ping events and stop sending pointer events when a client doesn't answer? I think this is what Weston does. It would probably solve the problem in almost all cases. (I was not able to reproduce a crash on Weston) It's not currently (without significant hacks) possible to read wayland events without also dispatching them, so there's not much we can really do except tell application code to stop blocking the GUI thread. >From what I can tell, you're also going to have the same problem with blocking GTK clients as they handle events the same way we do. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392520] New: Long URLs are not clickable in plaintext message viewer
https://bugs.kde.org/show_bug.cgi?id=392520 Bug ID: 392520 Summary: Long URLs are not clickable in plaintext message viewer Product: kmail2 Version: 5.7.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: creideiki+kdeb...@ferretporn.se Target Milestone: --- Created attachment 111733 --> https://bugs.kde.org/attachment.cgi?id=111733&action=edit Screenshot demonstrating the bug The plaintext message viewer makes URLs it recognises clickable. However, this only works for short URLs, up to 255 characters. At 256 characters and above, URLs are no longer clickable. This is a problem, since such long URLs are fairly common. For example, when Kickstarter and Patreon send project updates through e-mail, the links include long random tokens, almost always pushing them over the 255-character limit. Attached is a screenshot demonstrating this effect, with a text/plain e-mail with two URLs, one of 255 characters and one of 256. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389426] Cannot cancel IMAP connection to server with wrong certificate
https://bugs.kde.org/show_bug.cgi?id=389426 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392792] New: Plasmashell startup takes several minutes of 100% CPU in Mesa
https://bugs.kde.org/show_bug.cgi?id=392792 Bug ID: 392792 Summary: Plasmashell startup takes several minutes of 100% CPU in Mesa Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: creideiki+kdeb...@ferretporn.se CC: plasma-b...@kde.org Target Milestone: 1.0 After upgrading plasma-desktop from 5.10.5 to 5.12.4, starting plasmashell at login takes about 5 minutes of 100% CPU. During this time, the desktop is black and no panel is visible. Everything else in my KDE desktop works, so I can e.g. press Alt-F2 to get a launcher which can start Konsole and Firefox, or press keyboard shortcuts to change virtual desktops in KWin with animations and normal performance. While the plasmashell process is using 100% CPU, "perf top" says almost all of that goes to Mesa: PerfTop:4992 irqs/sec kernel: 7.4% exact: 0.0% [4000Hz cycles], (all, 2 CPUs) - 54.42% i915_dri.so [.] _mesa_unpack_rgba_row 9.61% i915_dri.so [.] fetch_vector4 5.25% i915_dri.so [.] _mesa_execute_program 2.90% i915_dri.so [.] linear_texel_locations 2.70% i915_dri.so [.] store_vector4 1.84% i915_dri.so [.] sample_2d_linear.isra.30 1.78% [kernel][k] ___bpf_prog_run 1.75% i915_dri.so [.] fetch_texel_lod 1.63% i915_dri.so [.] lerp_rgba_2d 1.62% [kernel][k] read_hpet 0.86% i915_dri.so [.] fetch_texel_2d_B8G8R8A8_UNORM 0.50% i915_dri.so [.] sample_linear_2d GDB backtraces of the plasmashell process end somewhere deep within Mesa (with the other threads waiting for poll()): Thread 1 (Thread 0x7ffa810cd7c0 (LWP 10927)): #0 _mesa_unorm_to_float (src_bits=, x=) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/main/format_utils.h:57 #1 unpack_float_b8g8r8a8_unorm (dst=0x7ffd84accc40, void_src=0x7ff9c9d0dd4c) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/main/format_unpack.c:154 #2 _mesa_unpack_rgba_row (format=MESA_FORMAT_B8G8R8A8_UNORM, n=, src=, dst=) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/main/format_unpack.c:5364 #3 0x7ffa56f9600a in sample_2d_linear (samp=samp@entry=0x55b8d1f4a430, img=img@entry=0x55b8d1ebceb0, texcoord=texcoord@entry=0x7ffd84accdf0, rgba=rgba@entry=0x7ffd84accd10, ctx=) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/swrast/s_texfilter.c:1191 #4 0x7ffa56f961d1 in sample_linear_2d (ctx=, samp=0x55b8d1f4a430, tObj=, n=, texcoords=, lambda=, rgba=0x7ffd84accd10) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/swrast/s_texfilter.c:1399 #5 0x7ffa56f84ce0 in fetch_texel_lod (ctx=, texcoord=, ---Type to continue, or q to quit--- lambda=, unit=, color=0x7ffd84acce00) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/swrast/s_fragprog.c:92 #6 0x7ffa56fc9ffc in fetch_texel (color=0x7ffd84acce00, lodBias=0, texcoord=0x7ffd84accdf0, inst=0x55b8d3d327e0, machine=0x55b8d34a51f0, ctx=0x55b8d22f10b0) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/program/prog_execute.c:310 #7 _mesa_execute_program (ctx=ctx@entry=0x55b8d22f10b0, program=program@entry=0x55b8d3d2ef90, machine=machine@entry=0x55b8d34a51f0) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/program/prog_execute.c:1159 #8 0x7ffa56f84f9f in run_program (start=0, end=, span=0x7ffd84acdcd0, ctx=) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/swrast/s_fragprog.c:215 #9 _swrast_exec_fragment_program (ctx=, span=0x7ffd84acdcd0) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/swrast/s_fragprog.c:272 #10 0x7ffa56f8b503 in _swrast_write_rgba_span (ctx=ctx@entry=0x55b8d22f10b0, span=span@entry=0x7ffd84acdcd0) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/swrast/s_span.c:1264 #11 0x7ffa56f9e718 in general_triangle (ctx=0x55b8d22f10b0, v0=, v1=, v2=0x55b8d386b858) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/swrast/s_tritemp.h:824 #12 0x7ffa56f65867 in _tnl_render_tri_strip_elts (ctx=0x55b8d22f10b0, start=0, count=6, flags=) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/tnl/t_vb_rendertmp.h:234 #13 0x7ffa56f66238 in run_render (ctx=0x55b8d22f10b0, stage=) at /var/tmp/portage/media-libs/mesa-18.0.0/work/mesa-18.0.0/src/mesa/tnl/t_vb_render.c:323 #14 0x7ffa56f5c68a in _tnl_run_pipeline (ct
[plasmashell] [Bug 392792] Plasmashell startup takes several minutes of 100% CPU in Mesa
https://bugs.kde.org/show_bug.cgi?id=392792 --- Comment #1 from Karl-Johan Karlsson --- It turns out this happens not only at startup, but while running as well. A few times per hour, the panel stops responding to input, plasmashell takes a whole CPU core and "perf top" shows the same Mesa functions running. After a minute or two, things quiet down and the panel starts responding again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392792] Plasmashell startup takes several minutes of 100% CPU in Mesa
https://bugs.kde.org/show_bug.cgi?id=392792 Karl-Johan Karlsson changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385998] New: Scam detection reads GnuPG output, giving false positives
https://bugs.kde.org/show_bug.cgi?id=385998 Bug ID: 385998 Summary: Scam detection reads GnuPG output, giving false positives Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: creideiki+kdeb...@ferretporn.se Target Milestone: --- This is for version 5.6.2, which is not an available alternative. GnuPG key BF8806F188590D8F includes a user ID containing an HTTPS URL. When looking at a mail signed by that key, KMail complains that it is a scam, citing: This email contains a link (mailto:https://censored,address@censored,address@censored,https://censored) which contains multiple http://. This is often the case in scam emails. Scam detection should only operate on the text of the e-mail itself, not locally generated GnuPG output. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 393423] Make "use the terminal color scheme for the scrollbar" an option
https://bugs.kde.org/show_bug.cgi?id=393423 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466290] When the dock icon indicates there are updates available, it shouldn't take 5 minutes to find out what they are.
https://bugs.kde.org/show_bug.cgi?id=466290 Johan Aires Rastén changed: What|Removed |Added CC||jo...@oljud.se --- Comment #2 from Johan Aires Rastén --- It doesn't take 5 minutes for me, but I've also found it a slight annoyance that I need to wait for it to fetch updates after the system has told me that updates are available. I've _just_ updated my packages in case that matters, but here are my timings: Clicking the "updates are available" icon in the systray: 7 seconds to fetch updates. packagekit-backend: Less than one second, almost immediate on the second attempt. fwupd-backend: Immediate. kns-backend: 7 seconds, the terminal is spammed with "log_attica_plugin: We got an OpenDesktop account, but it seems to be lacking the id token. This means an old SignOn OAuth2 plugin was used for logging in. The plugin may have been upgraded in the meantime, but an account created using the old plugin cannot be used, and you must log out and back in again." while it is updating. flatpak-backend: Immediate. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466290] KNS backend is slow and delays Discover from being able to show content after launch
https://bugs.kde.org/show_bug.cgi?id=466290 --- Comment #4 from Johan Aires Rastén --- Is it possible to disable the kns-backend? As far as I can tell, it provides "application addons" and "plasma addons", not sure if I have installed anything from there, but I don't think so. It doesn't seem possible to check installed software per source, would be nice if I could click "Installed" and then "Application Addons" in the sidebar to filter, but when I do this it goes to browse available apps instead. Maybe there's something I could put in .config/discoverrc but I haven't found any documentation for available options -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466290] KNS backend is slow and delays Discover from being able to show content after launch
https://bugs.kde.org/show_bug.cgi?id=466290 --- Comment #6 from Johan Aires Rastén --- Is there any way to list all apps installed from a specific backend? Manually browsing through installed apps in Discover I see that Arc Dark theme and some related packs are distributed by "KDE Store". This would be the KNS backend, right? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 417848] Make applet activate Night Color when it's currently inactive
https://bugs.kde.org/show_bug.cgi?id=417848 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427007] New: Add manual mode to night color
https://bugs.kde.org/show_bug.cgi?id=427007 Bug ID: 427007 Summary: Add manual mode to night color Product: systemsettings Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: creideiki+kdeb...@ferretporn.se CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY I want to manually control when night color is activated. The closest I have been able to get is: 1. In System settings -> Display and monitor -> Night color, set activation time to "Always on". 2. In the panel, add a Night color control plasmoid. 3. Click the plasmoid when I want to turn night color on or off. This has worked so far, except for activating night color on every login, which is not a huge problem because it only happens after rebooting for kernel upgrades. However, tonight night color is inhibited by some unknown thing and forging magic cookies to "qdbus org.kde.KWin /ColorCorrect org.kde.kwin.ColorCorrect.uninhibit" doesn't enable it. I could continue fighting the inhibition system, or try adding a new DBus interface to show the inhibitor list, but instead of adding workarounds to workarounds I have a feature request: add a manual mode, which ignores the inhibitor system entirely and just features an on/off switch in the panel. Remembering the last status and re-applying that at login (instead of always activating it) would be a bonus. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427073] New: Some of Krita pop up window stuck in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=427073 Bug ID: 427073 Summary: Some of Krita pop up window stuck in the middle of the screen Product: krita Version: 4.3.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: johan...@gmail.com Target Milestone: --- Created attachment 131984 --> https://bugs.kde.org/attachment.cgi?id=131984&action=edit The screen shot. I hope the text and the picture are self explanatory SUMMARY STEPS TO REPRODUCE 1. Create a Filter Layer in Krita 4.3.0 for Ubuntu 18.05.5 2. The properties window freezes in the middle of the screen. 3. Not only that, the canvas underneath become darken a bit so its so hard to see the changes. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427073] Some of Krita pop up window stuck in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=427073 --- Comment #2 from Johan Tri Handoyo --- Filter Mask and Filter Layer are both in the same problem. I'm using the appimage. -- You are receiving this mail because: You are watching all bug changes.
