[plasmashell] [Bug 395995] Notifications Messed up?
https://bugs.kde.org/show_bug.cgi?id=395995 --- Comment #11 from wolfyrion --- I think I have found the culprit. I have totally removed XFCE and now notifications are working fine. I dont know why XFCE is causing this issue, is a bit weird. XFCE has a file xfce4-notifyd maybe that is the culprit. I have rebooted my pc 2-3 times and notifications are fine , no problems at all. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396463] New: Dolphin crash when change between tabs
https://bugs.kde.org/show_bug.cgi?id=396463 Bug ID: 396463 Summary: Dolphin crash when change between tabs Product: dolphin Version: 18.04.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: angelbravosa...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.04.2) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.15.0-13-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: Just I clicked on the near tab (there was only a few) and Dophin Crash. I wasn't doing anything else. Very uncommon. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef4ebf3900 (LWP 5026))] Thread 10 (Thread 0x7fef1e47f700 (LWP 5037)): #0 0x7fef4e53574d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fef4175b38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fef4175b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fef486e6beb in QEventDispatcherGlib::processEvents (this=0x7fef180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fef4868e1ca in QEventLoop::exec (this=this@entry=0x7fef1e47ecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fef484c35e4 in QThread::exec (this=) at thread/qthread.cpp:522 #6 0x7fef484ce727 in QThreadPrivate::start (arg=0xf93670) at thread/qthread_unix.cpp:367 #7 0x7fef4380a6ba in start_thread (arg=0x7fef1e47f700) at pthread_create.c:333 #8 0x7fef4e54141d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7fef225b9700 (LWP 5036)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef2ea2958b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fef2ea29298 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fef4380a6ba in start_thread (arg=0x7fef225b9700) at pthread_create.c:333 #4 0x7fef4e54141d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7fef22dba700 (LWP 5035)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef2ea2958b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fef2ea29298 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fef4380a6ba in start_thread (arg=0x7fef22dba700) at pthread_create.c:333 #4 0x7fef4e54141d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7fef235bb700 (LWP 5034)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef2ea2958b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fef2ea29298 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fef4380a6ba in start_thread (arg=0x7fef235bb700) at pthread_create.c:333 #4 0x7fef4e54141d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fef23dbc700 (LWP 5033)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef2ea2958b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fef2ea29298 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fef4380a6ba in start_thread (arg=0x7fef23dbc700) at pthread_create.c:333 #4 0x7fef4e54141d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fef245bd700 (LWP 5032)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef2ea2958b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fef2ea29298 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fef4380a6ba in start_thread (arg=0x7fef245bd700) at pthread_create.c:333 #4 0x7fef4e54141d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fef2ccca700 (LWP 5031)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef2ea2958b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fef2ea29298 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fef4380a6ba in start_thread (arg=0x7fef2ccca700) at pthread_create.c:333 #4 0x7fef4e54141d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fef2dc33700 (LWP 5030)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/
[Touchpad-KCM] [Bug 395348] [Libinput backend] enable/disable touchpad setting is gray out and unavailable since plasma 5.13
https://bugs.kde.org/show_bug.cgi?id=395348 mthw0 changed: What|Removed |Added CC||jari...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395722] touchpad settings are wrong after resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=395722 mthw0 changed: What|Removed |Added CC||jari...@hotmail.com Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from mthw0 --- I didnt notice reverse scrolling being disabled, but I experience touchpad sensitivity being changed to very low. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 Nikita Melnichenko changed: What|Removed |Added Component|general |krviewer -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396436] Increase number of Popular URLs
https://bugs.kde.org/show_bug.cgi?id=396436 Nikita Melnichenko changed: What|Removed |Added Severity|minor |wishlist CC||nikita+...@melnichenko.name --- Comment #1 from Nikita Melnichenko --- For this and other Popular URL ideas: we currently don't have manpower to make improvements in this area. Feel free to step up. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395757] Connecting to network took time and system flickred multiple times
https://bugs.kde.org/show_bug.cgi?id=395757 u2fsdgv...@gmail.com changed: What|Removed |Added CC||u2fsdgv...@gmail.com --- Comment #3 from u2fsdgv...@gmail.com --- *** Bug 396459 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396459] Desktop crash
https://bugs.kde.org/show_bug.cgi?id=396459 u2fsdgv...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from u2fsdgv...@gmail.com --- (In reply to Alexander Mentyu from comment #1) > Possibly duplicate of https://bugs.kde.org/show_bug.cgi?id=395757 Maybe yes, but the crash signal is different. thank you! *** This bug has been marked as a duplicate of bug 395757 *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396419] Popular URLs Panel should remember it's size
https://bugs.kde.org/show_bug.cgi?id=396419 Nikita Melnichenko changed: What|Removed |Added Severity|minor |wishlist CC||nikita+...@melnichenko.name -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396325] Allow separate launching of locate tool
https://bugs.kde.org/show_bug.cgi?id=396325 Nikita Melnichenko changed: What|Removed |Added CC||nikita+...@melnichenko.name --- Comment #4 from Nikita Melnichenko --- I think instead of "krusader --locate" it's better to refactor the GUI code, so that it could be built as a separate tool as well as bundled into Krusader. (In reply to dufferzafar from comment #2) > ... I'm a dev myself ... > > I'd actually like to take a stab at it myself. I'll try to build Krusader > from source and then work on this. Feel free to try it out and submit a patch to https://phabricator.kde.org where we can review and iterate. For dev questions please use krusader-devel mailing list. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395993] Discover crashed after searching for a package.
https://bugs.kde.org/show_bug.cgi?id=395993 --- Comment #3 from n9p7v --- (In reply to Aleix Pol from comment #1) > Could you please try to reproduce with debug symbols? > https://wiki.ubuntu.com/DebuggingProgramCrash#Non-built- > in_debug_symbol_packages_.28.2A-dbgsym.29 I can't reproduce the crash, it happens randomly. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 395993] Discover crashed after searching for a package.
https://bugs.kde.org/show_bug.cgi?id=395993 --- Comment #2 from n9p7v --- Created attachment 113914 --> https://bugs.kde.org/attachment.cgi?id=113914&action=edit Discover crash information -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 301034] Rename input field doesn't respect text[NORMAL] when GTK theme is used
https://bugs.kde.org/show_bug.cgi?id=301034 Nikita Melnichenko changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #6 from Nikita Melnichenko --- Thanks for the reference. I'll try to check it when I have time. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 Nikita Melnichenko changed: What|Removed |Added Keywords||triaged --- Comment #4 from Nikita Melnichenko --- Reports like this are important. Please don't feel like you're wasting your or my time. In case other people encounter it, we'll know it's a problem related to some libs or actions and eventually we may narrow down the possibilities and even fix it. At this point, I agree with Toni, there is not much we can do but we'll keep an eye on it. I wonder why KCrash handler (aka DrKonqi) didn't catch this crash... P.S. Reproducibility is very desired but not always required. I fixed a few crashes in my life that I couldn't reproduce. This is one of them: bug #389413. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396459] Desktop crash
https://bugs.kde.org/show_bug.cgi?id=396459 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #1 from Alexander Mentyu --- Possibly duplicate of https://bugs.kde.org/show_bug.cgi?id=395757 -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 377341] Raise help window to foreground on F1 key
https://bugs.kde.org/show_bug.cgi?id=377341 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #2 from Alexander Mentyu --- Can reproduce Plasma: 5.13.3 Apps: 18.04.2 Frameworks: 5.47.0 Qt: 5.11.1 Kernel: 4.18.0-1-MANJARO OS: Netrunner Rolling Video: Intel 4400 Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1 Mesa 3D: 18.1.3 Screen: 1600x900 Xorg: 1.20 Wayland: 1.15.0-1 Wayland Protocols: 1.14-1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389445] Menu "Color Theme" does not work in MS Windows.
https://bugs.kde.org/show_bug.cgi?id=389445 --- Comment #3 from danthemanthathasa...@gmail.com --- I would also like to add that there might be a reason color themes have been disabled on Windows. Native UI elements don't conform to the theme, producing an uneven experience, however a fix is applicable using SetMenuInfo() and HBRUSH in the Win32 API. If one of the KDE developers could please implement these fixes (as I do not have a grasp on the KDE codebase), the entire Windows community would be very grateful. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389445] Menu "Color Theme" does not work in MS Windows.
https://bugs.kde.org/show_bug.cgi?id=389445 danthemanthathasa...@gmail.com changed: What|Removed |Added CC||danthemanthathasafan@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389445] Menu "Color Theme" does not work in MS Windows.
https://bugs.kde.org/show_bug.cgi?id=389445 --- Comment #2 from danthemanthathasa...@gmail.com --- I have found the issue. After digging through code, there is no fault with how the color themes are found. There is supposed to be a folder called "color-schemes" at "C:/Program Files/KDevelop/bin/data/color-schemes" filled with .colors files. These .colors files have been excluded from the Windows installation, so the menu shows up empty. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396462] New: kscreen-doctor: Unable to parse argumentsoutput.DP-0.8.enable
https://bugs.kde.org/show_bug.cgi?id=396462 Bug ID: 396462 Summary: kscreen-doctor: Unable to parse argumentsoutput.DP-0.8.enable Product: KScreen Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: bugreporte...@gmail.com Target Milestone: --- kscreen-doctor -o reports: Output: 446 DP-0.8 enabled connected DisplayPort etc. However, when I attempt to use DP-0.8 as a parameter to kscreen-doctor, it results in an error: Unable to parse argumentsoutput.DP-0.8.enable escaping the dot with a backslash or quoting the name does not resolve the error. I'm not sure if this is a bug. My guess is that screen names that include dots are possibly not expected and are not handled properly. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396461] Dragging and drop a file existing in the Trash folder to same Trash folder crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=396461 toni_rocha changed: What|Removed |Added Platform|Other |Kubuntu Packages --- Comment #1 from toni_rocha --- Another information: operating system is Kubuntu 18.04 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396461] New: Dragging and drop a file existing in the Trash folder to same Trash folder crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=396461 Bug ID: 396461 Summary: Dragging and drop a file existing in the Trash folder to same Trash folder crashes Plasma Product: dolphin Version: 17.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: antonioni.ro...@gmail.com Target Milestone: --- In Dolphin, drag a file in the Trash folder area, and drop in the Trash folder area. The Plasma crashes, sometimes hiding panels and showing only windows until thelogout from the system. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396460] New: Split view should close on the folder that is currently focused not the one that was opened from
https://bugs.kde.org/show_bug.cgi?id=396460 Bug ID: 396460 Summary: Split view should close on the folder that is currently focused not the one that was opened from Product: dolphin Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: split view Assignee: dolphin-bugs-n...@kde.org Reporter: tef...@gmail.com Target Milestone: --- When I open split view and I explore other folders in the panel that was opened, split view should close on the panel that I have currently selected. Right now it always closes to the panel that it was originally opened from, regardless of focus or selection. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396459] New: Desktop crash
https://bugs.kde.org/show_bug.cgi?id=396459 Bug ID: 396459 Summary: Desktop crash Product: plasmashell Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: u2fsdgv...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.13.3) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: If i use the nouveau driver and Plasma(wayland), Plasma-Desktop will crash when i click on the Wi-Fi icon. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb498c69f00 (LWP 689))] Thread 13 (Thread 0x7fb39dc3b700 (LWP 1252)): #0 0x7fb491630ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb49248d2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fb49647942d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fb49647969c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb49248cb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fb49162b075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fb491d7c53f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fb3be4f7700 (LWP 1001)): #0 0x7fb491630ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb49248d2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fb49647942d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fb49647969c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb49248cb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fb49162b075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fb491d7c53f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fb3b55f8700 (LWP 979)): #0 0x7fb491630ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb49248d2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fb49647942d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fb49647969c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb49248cb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fb49162b075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fb491d7c53f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fb3b75ef700 (LWP 974)): #0 0x7fb491630ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb49248d2fc in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fb49647942d in () at /usr/lib/libQt5Quick.so.5 #3 0x7fb49647969c in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb49248cb45 in () at /usr/lib/libQt5Core.so.5 #5 0x7fb49162b075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fb491d7c53f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fb3bdcf6700 (LWP 957)): [KCrash Handler] #6 0x7fb491cba86b in raise () at /usr/lib/libc.so.6 #7 0x7fb491ca540e in abort () at /usr/lib/libc.so.6 #8 0x7fb491ca52e0 in _nl_load_domain.cold.0 () at /usr/lib/libc.so.6 #9 0x7fb491cb3112 in () at /usr/lib/libc.so.6 #10 0x7fb3edf1b600 in () at /usr/lib/libdrm_nouveau.so.2 #11 0x7fb3edf1b563 in nouveau_pushbuf_data () at /usr/lib/libdrm_nouveau.so.2 #12 0x7fb3edf1ce68 in nouveau_pushbuf_space () at /usr/lib/libdrm_nouveau.so.2 #13 0x7fb3f2b4a7ed in () at /usr/lib/dri/nouveau_dri.so #14 0x7fb3f2b5119b in () at /usr/lib/dri/nouveau_dri.so #15 0x7fb3f2b51357 in () at /usr/lib/dri/nouveau_dri.so #16 0x7fb3f2b5290b in () at /usr/lib/dri/nouveau_dri.so #17 0x7fb3f2e01788 in () at /usr/lib/dri/nouveau_dri.so #18 0x7fb3f2e994b9 in () at /usr/lib/dri/nouveau_dri.so #19 0x7fb3f2e99e9f in () at /usr/lib/dri/nouveau_dri.so #20 0x7fb49643b8cb in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #21 0x7fb49643ca66 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #22 0x7fb496442103 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #23 0x7fb4964324ee in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #24 0x7fb4964329bc in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #25 0x7fb49646d030 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #26 0x7fb4964d0db5 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #27 0x7
[i18n] [Bug 396458] Problema no texto das tooltips do ksysguard
https://bugs.kde.org/show_bug.cgi?id=396458 --- Comment #2 from Dr. Chapatin --- Created attachment 113913 --> https://bugs.kde.org/attachment.cgi?id=113913&action=edit ksysguard em englês -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 396458] Problema no texto das tooltips do ksysguard
https://bugs.kde.org/show_bug.cgi?id=396458 --- Comment #1 from Dr. Chapatin --- Created attachment 113912 --> https://bugs.kde.org/attachment.cgi?id=113912&action=edit ksysguard em pt-br -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 396458] New: Problema no texto das tooltips do ksysguard
https://bugs.kde.org/show_bug.cgi?id=396458 Bug ID: 396458 Summary: Problema no texto das tooltips do ksysguard Product: i18n Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: pt-BR Assignee: kde-i18n-pt...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Estou postando capturas do ksysguard em pt-br e em inglês para ficar mais claro o problema. Plasma 5.13.3 no Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396071] plasma5 screen management going wrong
https://bugs.kde.org/show_bug.cgi?id=396071 --- Comment #3 from bugreporte...@gmail.com --- Is it possible to disable kscreen (without uninstalling) so that all screen management can be done by xrandr? As a test, I removed packages libkscreen and kscreen and used xrandr with very good results. The problem is that I also had to remove powerdevil. I don't think I want to manage power settings on a laptop without powerdevil, therefore, I cannot leave libkscreen and kscreen uninstalled. But I would like to know if there is a way to tell kscreen to stop managing screens so that I can do it myself with xrandr. I do not want to compile any packages, apply any patches, etc. Alternatively, can I control kscreen manually the way I would use xrandr? I see that a binary called kscreen-doctor exists, but I don't see a manual entry for it and I don't see any mention of it on the Arch Linux wiki (or anywhere else). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387759] Konsole Lacks the "Ambiguous-width characters" Option
https://bugs.kde.org/show_bug.cgi?id=387759 qdzcu...@sharklasers.com changed: What|Removed |Added Version|17.12.0 |18.04.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374410] No option for using localized era year string in Digital Clock
https://bugs.kde.org/show_bug.cgi?id=374410 qdzcu...@sharklasers.com changed: What|Removed |Added Version|5.8.5 |5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396415] Valgrind is not looking up $ORIGIN rpath of shebang programs
https://bugs.kde.org/show_bug.cgi?id=396415 --- Comment #3 from Jack Zhao --- Created attachment 113911 --> https://bugs.kde.org/attachment.cgi?id=113911&action=edit repro case -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396415] Valgrind is not looking up $ORIGIN rpath of shebang programs
https://bugs.kde.org/show_bug.cgi?id=396415 --- Comment #2 from Jack Zhao --- Hi, thanks for the response. For what it's worth, I was able to reproduce this with a barebones centos7 container. Please see log here: https://pastebin.com/raw/VbvL0khy Steps I took: 1. run a container of the centos:7 official image available from docker.io sudo docker run -i -t centos:7 /bin/bash 2. once in container, install gcc, gcc-c++, and valgrind yum install -y gcc gcc-c++ valgrind 3. download the attached repro case from some available server (or use any method to get the repro case into the container) curl http:///test_repro.tar.gz 4. unpack the repro case tar xvzf test_repro.tar.gz 5. cd into the test_repro folder cd test_repro 6. run repro.sh ./repro.sh The test_repro.tar.gz will be attached right after. So if it's an environment-induced problem, it seems to happen in default/typical environments. Any guidance on what kind of environment settings might be causing it? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 382085] "Share" tab in folder properties window shows text partially readable in the user list and in the drop down to set permissions
https://bugs.kde.org/show_bug.cgi?id=382085 Dr. Chapatin changed: What|Removed |Added Summary|Share-Tab - Userlist too|"Share" tab in folder |small |properties window shows ||text partially readable in ||the user list and in the ||drop down to set ||permissions -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393888] kickoff unusable/broken when I change the position of plasma panel on screen from bottom/top to left/right or vice-versa
https://bugs.kde.org/show_bug.cgi?id=393888 Chris Holland changed: What|Removed |Added CC||zrenf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380250] plasmashell often freeze in various IO action.
https://bugs.kde.org/show_bug.cgi?id=380250 --- Comment #7 from TOM Harrison --- sorry I mean apt upgrade. when install or update package. last time I notice seems cups update -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380250] plasmashell often freeze in various IO action.
https://bugs.kde.org/show_bug.cgi?id=380250 --- Comment #6 from TOM Harrison --- I also think so. Now the apt update will also freeze plasmashell itself. I did not know why. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep
https://bugs.kde.org/show_bug.cgi?id=395583 --- Comment #4 from Piotr Mierzwinski --- Hmmm. I tested this issue today and seems that all is fine. I made the same test like previously. Only my monitor turned off itself. I turned it on and after moving mouse cursor I got proper field to enter password. I don't know if this is Arch issue only because that users other distributions (not based on Arch) didn't reported. Please note that only you and me reported this. Where are others? Also conditions of test changed, because I have up-to-date distribution. I suppose since time first test one have changed many software and of course I have newer Plasma (5.13.3), so kscreenlocker is newer. Additionally Qt is newer (5.11.1). I don't know where the problem was. To be sure that issue went away I will make next test later. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396457] New: Font rendered incorrectly (corruption) when display scaling is not an integer.
https://bugs.kde.org/show_bug.cgi?id=396457 Bug ID: 396457 Summary: Font rendered incorrectly (corruption) when display scaling is not an integer. Product: konsole Version: 17.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: d...@dpc.pw Target Milestone: --- When using global Display scaling factor that is not an integer (1x or 2x), the konsole will commonly draw the current line a bit off (too high), leaving a thin line of white space underneath. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368707] Seekbar stops working after skipping to different parts of media
https://bugs.kde.org/show_bug.cgi?id=368707 KDE Neon user changed: What|Removed |Added Version|5.12.1 |5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396456] New: When changing orientation screen, touches are wrongly interpret by position of touch.
https://bugs.kde.org/show_bug.cgi?id=396456 Bug ID: 396456 Summary: When changing orientation screen, touches are wrongly interpret by position of touch. Product: KScreen Version: 5.13.2 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: migac...@gmail.com Target Milestone: --- Hi guys, after going to: system settings -> displays -> orientation -> and changing it to: clockwise, anticlockwise or upside down Display is rotating and that is great. Touches are interpreted like screen is in original position. It look like code rules responsible for interpretation of touches are still the same as it was before changing orientation. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396290] [PATCH] Possible tool - allocfail
https://bugs.kde.org/show_bug.cgi?id=396290 --- Comment #1 from roger.li...@cedalo.com --- Created attachment 113910 --> https://bugs.kde.org/attachment.cgi?id=113910&action=edit Patch using sha3 for hashing instead of adler32 checksums. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384617] Meta information not shown in Dolphin inside home directory (video reproduce inside)
https://bugs.kde.org/show_bug.cgi?id=384617 --- Comment #19 from Dr. Chapatin --- On my system, if baloo-widget is installed and baloo is disabled metainfo is available in dolphin info panel. However the colunms available in details view mode that should show additional info like image size, track, artist, album, etc are empty. Arch Linux plasma 5.13.3 frameworks 5.47 dolphin 18.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz
https://bugs.kde.org/show_bug.cgi?id=395632 --- Comment #21 from Benjamin Xiao --- (In reply to Christian Martinez from comment #20) > Forcing KWin to 144 fps only goes to 100 fps. Btw the Kwin "Show FPS" effect is capped at 100fps. It won't go higher than that even if Kwin is running at 144. If you don't force Kwin to run at 144, Kwin should show 60fps if you're experiencing this bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396435] emoji rendering broken
https://bugs.kde.org/show_bug.cgi?id=396435 Mariusz Glebocki changed: What|Removed |Added Assignee|konsole-de...@kde.org |m...@arccos-1.net --- Comment #2 from Mariusz Glebocki --- (In reply to Kurt Hindenburg from comment #1) > Thanks, the emojis I tested with shows only left half of emoji. > > Mariusz, can you work on this before 18.08 is release later this month? Sure -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396434] Uncontrolled log messages oversize log file up to run out of disk space
https://bugs.kde.org/show_bug.cgi?id=396434 Rafael changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #3 from Rafael --- Latest. OpenSUSE 15. In fact, I can't communicate with OpenSUSE forum cause, despite I'm registered, several months ago each time I enter in their forum, any web browers show me "too many redirections" and doesn't not show the forum after being loged. It's happening to more people too. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396455] New: Adjust time like in BQM - or ability to use BQM workflows directly while importing
https://bugs.kde.org/show_bug.cgi?id=396455 Bug ID: 396455 Summary: Adjust time like in BQM - or ability to use BQM workflows directly while importing Product: digikam Version: 5.9.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Import-PostProcessing Assignee: digikam-bugs-n...@kde.org Reporter: johannes.lists+bugs.kde@tannenhof-imshausen.de Target Milestone: --- The edit date/time function while importing isn't really useful because you can only choose an absolute date. I would like to be able to adjust timestamps the way it is possible in BQM. Or the possibility to directly choose a workflow from the BQM which is directly executed while importing the images. My problem: After importing images, the file last modified timestamp is off by two hours (daylight saving time) and one our during normal winter time compared to the created-timestamp. At the moment I correct this afterwards by selecting the newly imported images, use BQM with a saved workflow where i adjust the time as following: Using the digikam timestamp, the file last modified timestamp is changed. Unfortunately there is no way in digikam to search for images where the digikam timestamp and the file last modified timestamp differs (to find old images to correct.) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 395682] Reading debug info of binaries with readonly PT_LOAD segments
https://bugs.kde.org/show_bug.cgi?id=395682 --- Comment #12 from Mark Wielaard --- (In reply to H.J. Lu from comment #10) > (In reply to Mark Wielaard from comment #9) > > This patch fixes the issue with the reported binary in this bug and with the > > i386 glibc ld.so created on fedora (when build with ld -z separate-code). > > It doesn't fix: > > https://github.com/hjl-tools/simple-linux/tree/divide-by-zero yes, you are right, but isn't that a totally different case? Your example seems to have everything in a single rx segment and then a zero size rw segment. Is that something that is specific to they way you created that testcase without actually linking against any library, or does that happen normally in some configurations? I think it is best to create a new bug for this case and post the specific patch that solves this issue in that bug. Even though your patches might be totally correct and help fix this issue I found it hard to reason about them because some just seemed to disable various asserts without updating the comments that explained why we needed those asserts (if the comments are wrong, please update them together with the code changes). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396454] New: Frames display atop each other when rendering animation as .gif
https://bugs.kde.org/show_bug.cgi?id=396454 Bug ID: 396454 Summary: Frames display atop each other when rendering animation as .gif Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: gamerminst...@gmail.com Target Milestone: --- Created attachment 113909 --> https://bugs.kde.org/attachment.cgi?id=113909&action=edit a .kra file-replicates the issue I am having, .gifs of expected and actual results from rendering animation Overview: I made a small animation of a few frames in Krita. When I go to file>Render Animation and save it as a .gif file, the resulting .gif plays each frame on top of the previous, so by the 3rd or 4th frame its a mess of images layered on top of each other Steps to Reproduce: make a small animation or try the .kra file attached, render as a .gif Actual Results: see Actual Results.gif Expected Results: see Expected Results.gif (I was able to make the .gif as intended using a tool outside of Krita) Build Date & Platform: Krita Version: 4.1.0 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17134 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info **OpenGL not initialized** -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 396453] New: Viewing files in Ark doesn't allow resizing columns/fields in view mode
https://bugs.kde.org/show_bug.cgi?id=396453 Bug ID: 396453 Summary: Viewing files in Ark doesn't allow resizing columns/fields in view mode Product: ark Version: 18.04.1 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: david.cortes.riv...@gmail.com CC: rthoms...@gmail.com Target Milestone: --- Created attachment 113908 --> https://bugs.kde.org/attachment.cgi?id=113908&action=edit trying_to_resize If I open some compresses file with Ark and see their contents, it's not possible to resize the delimiters within fields where the contents of the file are shown (Name, Size, Owner, Group, Date). Steps to reproduce: * Create some compressed file in a format supported by Ark having a folder with some file inside it. * Open said file with Ark. * Try to resize the Name field/column (by shrinking the Size field) by hovering the mouse in the border between them. Expected behavior: * Should allow resizing the fields when hovering the mouse over the border between the fields. Actual behavior: * Doesn't allow resizing when hovering the mouse in the border. Reproducible: always. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396452] New: none/test/arm/vfp.c doesn't build with binutils 2.31 gas
https://bugs.kde.org/show_bug.cgi?id=396452 Bug ID: 396452 Summary: none/test/arm/vfp.c doesn't build with binutils 2.31 gas Product: valgrind Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: m...@klomp.org Target Milestone: --- This is most likely because of this commit: https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=58ed5c38f52511e73c9748b86c319320177fb0ca;hp=190852c8ac75cb62a737c58edfadfb0e1fcef78a Allow integer immediate for VFP vmov instructions. This patch fixes the case where you want to use an integer value the floating point immediate to a VFP vmov instruction such as vmovmi.f32 s27, #11. If the immediate is not a float we convert it and copy it's representation into the imm field and then carry on validating as if we originally entered a floating point immediate. The is considered a QoL improvement for hand assembly writers and allows more code portability between assembler. Introduced after discussion in this thread: https://sourceware.org/ml/binutils/2018-05/threads.html#00114 gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../include -I../../../coregrind -I../../../include -I../../../VEX/pub -I../../../VEX/pub -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1 -DVGPV_arm_linux_vanilla=1 -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector-g -O0 -mcpu=cortex-a8 -mfpu=neon -mthumb -c -o vfp-vfp.o `test -f 'vfp.c' || echo './'`vfp.c /tmp/ccon3RaI.s: Assembler messages: /tmp/ccon3RaI.s:42769: Error: immediate out of range -- `vmov s9,#0xbe28' /tmp/ccon3RaI.s:42800: Error: immediate out of range -- `vmov s21,#0xbe28' /tmp/ccon3RaI.s:42831: Error: immediate out of range -- `vmov s4,#0xbe28' /tmp/ccon3RaI.s:42863: Error: immediate out of range -- `vmov s19,#0xbe28' /tmp/ccon3RaI.s:42894: Error: immediate out of range -- `vmov s29,#0xbe28' /tmp/ccon3RaI.s:42926: Error: immediate out of range -- `vmov s8,#0xbe28' /tmp/ccon3RaI.s:42958: Error: immediate out of range -- `vmov s16,#0xbe28' /tmp/ccon3RaI.s:42990: Error: immediate out of range -- `vmov s0,#0xbe28' /tmp/ccon3RaI.s:43022: Error: immediate out of range -- `vmov s3,#0xbe28' /tmp/ccon3RaI.s:43053: Error: immediate out of range -- `vmov s9,#0xbe28' /tmp/ccon3RaI.s:43083: Error: immediate out of range -- `vmov s11,#0xbe28' /tmp/ccon3RaI.s:43115: Error: immediate out of range -- `vmov s30,#0xbe28' /tmp/ccon3RaI.s:44568: Error: immediate out of range -- `vmov s21,#0xbff8' /tmp/ccon3RaI.s:44569: Error: immediate out of range -- `vmov s2,#0x3fa8' /tmp/ccon3RaI.s:44596: Error: immediate out of range -- `vmov s23,#0xbff8' /tmp/ccon3RaI.s:44597: Error: immediate out of range -- `vmov s21,#0x3fa8' /tmp/ccon3RaI.s:44623: Error: immediate out of range -- `vmov s3,#0xbff8' /tmp/ccon3RaI.s:44624: Error: immediate out of range -- `vmov s3,#0x3fa8' /tmp/ccon3RaI.s:44649: Error: immediate out of range -- `vmov s19,#0xbff8' /tmp/ccon3RaI.s:44650: Error: immediate out of range -- `vmov s5,#0x3fa8' /tmp/ccon3RaI.s:44677: Error: immediate out of range -- `vmov s3,#0xbff8' /tmp/ccon3RaI.s:44678: Error: immediate out of range -- `vmov s12,#0x3fa8' /tmp/ccon3RaI.s:44705: Error: immediate out of range -- `vmov s7,#0xbff8' /tmp/ccon3RaI.s:44706: Error: immediate out of range -- `vmov s10,#0x3fa8' /tmp/ccon3RaI.s:44732: Error: immediate out of range -- `vmov s30,#0xbff8' /tmp/ccon3RaI.s:44733: Error: immediate out of range -- `vmov s13,#0x3fa8' /tmp/ccon3RaI.s:44758: Error: immediate out of range -- `vmov s17,#0xbff8' /tmp/ccon3RaI.s:44759: Error: immediate out of range -- `vmov s17,#0x3fa8' /tmp/ccon3RaI.s:44786: Error: immediate out of range -- `vmov s11,#0xbff8' /tmp/ccon3RaI.s:44787: Error: immediate out of range -- `vmov s21,#0x3fa8' /tmp/ccon3RaI.s:44814: Error: immediate out of range -- `vmov s8,#0xbff8' /tmp/ccon3RaI.s:44815: Error: immediate out of range -- `vmov s30,#0x3fa8' /tmp/ccon3RaI.s:44841: Error: immediate out of range -- `vmov s12,#0xbff8' /tmp/ccon3RaI.s:44842: Error: immediate out of range -- `vmov s9,#0x3fa8' /tmp/ccon3RaI.s:44867: Error: immediate out of range -- `vmov s6,#0xbff8' /tmp/ccon3RaI.s:44868: Error: immediate out of range -- `vmov s11,#0x3fa8' /tmp/ccon3RaI.s:44895: Error: immediate out of range -- `vmov s17,#0xbff8' /tmp/ccon3RaI.s:44896: Error: immediate out of range -- `vmov s12,#0x3fa8' /tmp/ccon3RaI.s:44923: Error: immediate out of range -- `vmov s12,#0xbff8' /tmp/ccon3RaI.s:44924: Error: immediate out of range -- `vmov s12,#0x3fa8' /tmp/ccon3RaI.s:44950: Error: immediate out of range -- `vmov s11,#0xbff8' /tmp/ccon3RaI.s:44951: Error: immediate out of
[valgrind] [Bug 393926] helpful to have report timestamp in wall-clock time
https://bugs.kde.org/show_bug.cgi?id=393926 Bill Torpey changed: What|Removed |Added Summary|helpful to have reort |helpful to have report |timestamp in wall-clock |timestamp in wall-clock |time|time -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388386] Time adjustment tool is misleading and potentially leads to data loss
https://bugs.kde.org/show_bug.cgi?id=388386 Johannes changed: What|Removed |Added CC||johannes.lists+bugs.kde.org ||@tannenhof-imshausen.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 321734] Use KWin KScreen effect
https://bugs.kde.org/show_bug.cgi?id=321734 Frederik Gladhorn changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #1 from Frederik Gladhorn --- This is lacking content. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 321734] Use KWin KScreen effect
https://bugs.kde.org/show_bug.cgi?id=321734 Frederik Gladhorn changed: What|Removed |Added Resolution|--- |WONTFIX CC||gladh...@kde.org Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 318855] Test that XRandR1.1 works in a XRandR1.1 only environment
https://bugs.kde.org/show_bug.cgi?id=318855 Frederik Gladhorn changed: What|Removed |Added CC||gladh...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Frederik Gladhorn --- xrandr 1.5 is out, I don't think there's a point in dealing with 1.1. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 318856] Unittest for XRandR 1.1
https://bugs.kde.org/show_bug.cgi?id=318856 Frederik Gladhorn changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||gladh...@kde.org Resolution|--- |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 318856] Unittest for XRandR 1.1
https://bugs.kde.org/show_bug.cgi?id=318856 Frederik Gladhorn changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 314781] We should support XRandR 1.1
https://bugs.kde.org/show_bug.cgi?id=314781 Bug 314781 depends on bug 318856, which changed state. Bug 318856 Summary: Unittest for XRandR 1.1 https://bugs.kde.org/show_bug.cgi?id=318856 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 314781] We should support XRandR 1.1
https://bugs.kde.org/show_bug.cgi?id=314781 Bug 314781 depends on bug 318855, which changed state. Bug 318855 Summary: Test that XRandR1.1 works in a XRandR1.1 only environment https://bugs.kde.org/show_bug.cgi?id=318855 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 318855] Test that XRandR1.1 works in a XRandR1.1 only environment
https://bugs.kde.org/show_bug.cgi?id=318855 Frederik Gladhorn changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 396451] New: Unable to access the Postbank homepage via krunner.
https://bugs.kde.org/show_bug.cgi?id=396451 Bug ID: 396451 Summary: Unable to access the Postbank homepage via krunner. Product: krunner Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: webshortcuts Assignee: ro...@kde.org Reporter: chris0033...@yahoo.de Target Milestone: --- Created attachment 113907 --> https://bugs.kde.org/attachment.cgi?id=113907&action=edit Postbank homepage error Hi, Currently I'm unable to access the Postbank-Homepage at https://www.postbank.de after pressing Alt+Space and typing in the above address. However I'm able to access the homepage after calling Firefox and typing in the above address in the browser's address bar. I don't get this behaviour if I try to access a website like https://www.kernel.org. Does anyone know what's going on? Is this a problem with KDE or is it a misconfigured Postbank-Website? And why does the website work with Firefox but not KDE? Firefox shows the "green lock"-symbol and everything appears to be normal. Is it safe to access Postbank's website? Please have a look at the attached screenshot. It shows the error messages. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 343104] Display and Monitor settings crash
https://bugs.kde.org/show_bug.cgi?id=343104 Frederik Gladhorn changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365865] Display resolution setting in Display Configuration not obeyed in Wayland Plasma session
https://bugs.kde.org/show_bug.cgi?id=365865 Frederik Gladhorn changed: What|Removed |Added CC||gladh...@kde.org --- Comment #11 from Frederik Gladhorn --- I think a wayland backend has recently been added, is this still a problem? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 374708] Confusing design of Resolution slider (need redisign)
https://bugs.kde.org/show_bug.cgi?id=374708 Frederik Gladhorn changed: What|Removed |Added Status|ASSIGNED|RESOLVED CC||gladh...@kde.org Resolution|--- |MOVED --- Comment #9 from Frederik Gladhorn --- I agree that the UI needs improvement. I'd propose commenting on https://phabricator.kde.org/T3464 . -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 324625] kscreen crashes kde daemon
https://bugs.kde.org/show_bug.cgi?id=324625 Frederik Gladhorn changed: What|Removed |Added CC||gladh...@kde.org Status|VERIFIED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 342601] Opening "Display and Monitor" crashes System Settings window
https://bugs.kde.org/show_bug.cgi?id=342601 Frederik Gladhorn changed: What|Removed |Added CC||gladh...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |WAITINGFORINFO --- Comment #4 from Frederik Gladhorn --- This is rather old. The first backtrace is incomplet, duplicate of https://bugs.kde.org/show_bug.cgi?id=343104 and the second crash is in the screen saver module, not kscreen. I assume these have been fixed in the meantime. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 396450] KCollapsibleGroupBox: wrong position in parent layout if there is a QLabel with word-wrap
https://bugs.kde.org/show_bug.cgi?id=396450 --- Comment #2 from Elvis Angelaccio --- Created attachment 113906 --> https://bugs.kde.org/attachment.cgi?id=113906&action=edit Actual layout -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 396450] KCollapsibleGroupBox: wrong position in parent layout if there is a QLabel with word-wrap
https://bugs.kde.org/show_bug.cgi?id=396450 --- Comment #1 from Elvis Angelaccio --- Created attachment 113905 --> https://bugs.kde.org/attachment.cgi?id=113905&action=edit Expected layout -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 343104] Display and Monitor settings crash
https://bugs.kde.org/show_bug.cgi?id=343104 Frederik Gladhorn changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WAITINGFORINFO --- Comment #2 from Frederik Gladhorn --- I guess this is so old that it can be closed. If you add a more complete backtrace, please re-open, I'd be happy to have a look. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 396450] New: KCollapsibleGroupBox: wrong position in parent layout if there is a QLabel with word-wrap
https://bugs.kde.org/show_bug.cgi?id=396450 Bug ID: 396450 Summary: KCollapsibleGroupBox: wrong position in parent layout if there is a QLabel with word-wrap Product: frameworks-kwidgetsaddons Version: 5.47.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: elvis.angelac...@kde.org CC: k...@davidedmundson.co.uk, kdelibs-b...@kde.org Target Milestone: --- Created attachment 113904 --> https://bugs.kde.org/attachment.cgi?id=113904&action=edit Self-contained test case for the issue If a KCollapsibleGroupBox contains a QLabel with word-wrapping enabled, it will be wrongly positioned in its parent layout. This issue seems to be called by the setFocusPolicy() call in overrideFocusPolicyOf(). Not sure whether the bug is in KCollapsibleGroupBox or in Qt. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396434] Uncontrolled log messages oversize log file up to run out of disk space
https://bugs.kde.org/show_bug.cgi?id=396434 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- What kind of openSUSE version do you use? I've been using openSUSE for 20 years now and have never seen log/messages written by desktop programs. In addition, openSUSE has been using Systemd-journal for quite some time, so a log/messages does not exist at all. Maik -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 343104] Display and Monitor settings crash
https://bugs.kde.org/show_bug.cgi?id=343104 Frederik Gladhorn changed: What|Removed |Added CC||gladh...@kde.org --- Comment #1 from Frederik Gladhorn --- Is this reproducible? Sadly the backtrace seems to lack symbols for kscreen, any chance that you could install debug packages and try to get a more complete backtrace? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 392735] Crash on viewing or trying to add data into any account
https://bugs.kde.org/show_bug.cgi?id=392735 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #21 from Wolfgang Bauer --- It seems that https://cgit.kde.org/kmymoney.git/commit/kmymoney/widgets/qwidgetcontainer.cpp?id=2f823a4603f1d9c823f3498e74f3fa05960e2383 (i.e. the patch from comment#11 ) does indeed fix the originally reported crash. See also https://bugzilla.opensuse.org/show_bug.cgi?id=1100025 . -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396449] New: Dolphin crash on close
https://bugs.kde.org/show_bug.cgi?id=396449 Bug ID: 396449 Summary: Dolphin crash on close Product: dolphin Version: 18.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: carlo.7...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.04.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.4-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Open Dolphin, right click on a file or folder to show the menu, then without any further clicks move the mouse to the close button of the dolphin window and click the button to close Dolphin, the application crashes.(OpenSuse Tumbleweed Plasma 5.13.2 Frameworks 5.47.0) The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f389b671c80 (LWP 25889))] Thread 4 (Thread 0x7f387a2af700 (LWP 25892)): #0 0x7f38903364dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f387af3779b in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f387af374c7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f3890330554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f389af09ccf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f3881d58700 (LWP 25891)): #0 0x7f389aefad34 in read () from /lib64/libc.so.6 #1 0x7f388dc947a0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f388dc4fd9f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f388dc50270 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f388dc503ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f38950bfb3b in QEventDispatcherGlib::processEvents (this=0x7f3874000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f389506fb3b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f3894ece326 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f3895510f45 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f3894ed78ec in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #10 0x7f3890330554 in start_thread () from /lib64/libpthread.so.0 #11 0x7f389af09ccf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f38842ef700 (LWP 25890)): #0 0x7f389aeff2c9 in poll () from /lib64/libc.so.6 #1 0x7f388d588377 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f388d589f8a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f38872ca089 in QXcbEventReader::run (this=0x558443d321c0) at qxcbconnection.h:409 #4 0x7f3894ed78ec in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #5 0x7f3890330554 in start_thread () from /lib64/libpthread.so.0 #6 0x7f389af09ccf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f389b671c80 (LWP 25889)): [KCrash Handler] #6 0x7f389635c9a0 in QGraphicsScenePrivate::storeMouseButtonsForMouseGrabber (this=this@entry=0x558444296800, event=event@entry=0x7ffdb3cc1450) at ../../include/QtCore/../../src/corelib/tools/qlist.h:540 #7 0x7f389636363b in QGraphicsScenePrivate::mousePressEventHandler (this=this@entry=0x558444296800, mouseEvent=mouseEvent@entry=0x7ffdb3cc1450) at graphicsview/qgraphicsscene.cpp:1463 #8 0x7f3896363769 in QGraphicsScene::mousePressEvent (this=, mouseEvent=0x7ffdb3cc1450) at graphicsview/qgraphicsscene.cpp:4046 #9 0x7f389636ad10 in QGraphicsScene::event (this=0x5584442c0f40, event=0x7ffdb3cc1450) at graphicsview/qgraphicsscene.cpp:3410 #10 0x7f389607dc11 in QApplicationPrivate::notify_helper (this=this@entry=0x558443d52980, receiver=receiver@entry=0x5584442c0f40, e=e@entry=0x7ffdb3cc1450) at kernel/qapplication.cpp:3728 #11 0x7f3896084df0 in QApplication::notify(QObject*, QEvent*) () at kernel/qapplication.cpp:3487 #12 0x7f3895070d29 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at ../../include/QtCore/../../src/corelib/kernel/qobject.h:142 #13 0x7f389638450b in QGraphicsView::mousePressEvent (this=0x558444247f90, event=0x7ffdb3cc1950) at /usr/include/c++/8/bits/atomic_base.h:390 #14 0x7f38960b9e69 in QWidget::event (this=this@entry=0x558444247f90, event=event@entry=0x7ffdb3cc1950) at kernel/qwidget.cpp:8897 #15 0x7f3896159c4e in QFrame::event (this=0x558444247f90, e=0x7ffdb3cc1950) at widgets/qframe.cpp:550 #16 0x7f389638567b in QGraphicsView::viewportEvent(QEvent*) () at graphicsview/qgraphicsview.cpp:2969 #17 0x7f3895070a53 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*
[digikam] [Bug 396434] Uncontrolled log messages oversize log file up to run out of disk space
https://bugs.kde.org/show_bug.cgi?id=396434 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- yes digiKam is very verbose if debug trace are enabled. But digiKam do not write something in Linux log file. All is done in the console only. So this is typically a OpenSuse customization which re-route the debug trace to a log file. This can be done easily with a Qt customization in settings. This do not be done for desktop application. Never. This must be possible to customize one by one by end user if necessary. Desktop application are not service in fact. So the problem must be reported to OpenSuse as well and fixed quickly. Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384727] [PATCH]valgrind does not support debug info for read only segments (generated by LLD)
https://bugs.kde.org/show_bug.cgi?id=384727 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Assignee|jsew...@acm.org |iv...@ivosh.net Status|UNCONFIRMED |ASSIGNED CC||iv...@ivosh.net --- Comment #3 from Ivo Raisr --- Please could you try one of the patches from bug https://bugs.kde.org/show_bug.cgi?id=395682 These two bugs seem to be very similar. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 395583] Cannot login after lock screen which went to sleep
https://bugs.kde.org/show_bug.cgi?id=395583 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com --- Comment #3 from Ben Daines --- Same issue here. Also Arch-based (Manjaro). It has nothing to do with your DVI adapter, as I'm seeing the same thing on a laptop with only an internal display. Seems to unlock properly every time when opening the lid, but if the machine goes to sleep and is woken back up with the keyboard or power button plasma will fail to unlock. If the screen is locked, but the machine has not gone to sleep, there doesn't seem to be any issues unlocking. Being that both of us are running Arch, this may be an Arch issue. However, I did not see anyone complaining about it on their forums, and there doesn't seem to be a bug report. Hopefully someone running a distro other than Arch can confirm this. Piotr, has this resolved itself with any subsequent updates? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 390923] Kate persistent sidebars changing size to minimum if additional sidebar is activated
https://bugs.kde.org/show_bug.cgi?id=390923 --- Comment #2 from Dominik Kummer --- Hi Michael, I am also experiencing it on single screen. For me its also true that the sidebar is working. I'll have to compare the source code of side- and bottombar. Maybe I can commit a bugfix soon. cheers dom -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 179261] Wish: Add support for RAID in KDE Partition Manager
https://bugs.kde.org/show_bug.cgi?id=179261 Andrius Štikonas changed: What|Removed |Added Assignee|v...@fidra.de |caiojcarva...@gmail.com CC||andr...@stikonas.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391376] Network monitor widget freeze.
https://bugs.kde.org/show_bug.cgi?id=391376 --- Comment #1 from kde38 --- I have been using 5.13 (now 5.13.3) under Arch and I have not seen this behaviour anymore. If it is still present in 5.12.* I do not know. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396345] high cpu activity after upgrade from 5.12 to 5.13
https://bugs.kde.org/show_bug.cgi?id=396345 --- Comment #23 from john Terragon --- Created attachment 113903 --> https://bugs.kde.org/attachment.cgi?id=113903&action=edit props after -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396345] high cpu activity after upgrade from 5.12 to 5.13
https://bugs.kde.org/show_bug.cgi?id=396345 --- Comment #22 from john Terragon --- Created attachment 113902 --> https://bugs.kde.org/attachment.cgi?id=113902&action=edit props before -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396444] Dolphin does not make global settings
https://bugs.kde.org/show_bug.cgi?id=396444 --- Comment #2 from GratisLPG --- > Is there a specific use case where this problem couldn't simply be resolved > by > using "Remember properties for each folder" instead? That'd be great to > know. > Thanks! >From previous environment, I'm taught that all folders must have the same size of icons for me. I noticed an interesting ailment while testing. I have the option "Remember the view properties for each folder", but when I enter, for example, in the paintings catalog, enlarge icons, close the dolphin, I still have enlarged icons everywhere, not only in the images folder. I still have a question, what is the default slider in the settings -> view mode? When I move it, nothing changes, even after restarting the program. I forgot to add that I have switched on the double panel view. -- You are receiving this mail because: You are watching all bug changes.
[kteatime] [Bug 396448] New: KTeaTime context menu broken after adding custom tea
https://bugs.kde.org/show_bug.cgi?id=396448 Bug ID: 396448 Summary: KTeaTime context menu broken after adding custom tea Product: kteatime Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@hilefoks.org Reporter: fb-...@posteo.de Target Milestone: --- Created attachment 113901 --> https://bugs.kde.org/attachment.cgi?id=113901&action=edit Broken menu Steps to reproduce: 1. Open KTeaTime 2. Right click on taskbar icon -> configure 3. Add a new tea 4. After clicking ok, the context menu is broken -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396405] Last digit of date field is obscured by "details column" in ledger view
https://bugs.kde.org/show_bug.cgi?id=396405 --- Comment #6 from Thomas Baumgart --- > From what I can see now, a correct implementation of> > Register::minimumColumnWidth() should get the longest date string for the > current language by iterating all dates for a whole given year once at > application start and use that for the date column minimal width. I would only iterate over the weekdays and the months. That leaves 19 iterations instead of 365/366. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 396444] Dolphin does not make global settings
https://bugs.kde.org/show_bug.cgi?id=396444 Julian Schraner changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||juliquad...@gmail.com --- Comment #1 from Julian Schraner --- Hello and thanks for your detailed bug report. The problem with this change would be that it would cause another bug: If a user wanted to use the slider to make all icons permanently bigger, this would not work because after a restart all changes would be gone. It is interesting to know that Nemo does apply this behavior, but I am not sure if it'd be a good change for Dolphin. Is there a specific use case where this problem couldn't simply be resolved by using "Remember properties for each folder" instead? That'd be great to know. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] No ability to switch from JEDEC to SI units in Plasma 5.x (KDE Frameworks Version : 5.22.0 / Qt 5.6.0)
https://bugs.kde.org/show_bug.cgi?id=364321 Rooty changed: What|Removed |Added CC||zy...@gmx.us -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396437] Crash when unplug HDMI cable while session is locked
https://bugs.kde.org/show_bug.cgi?id=396437 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381806] Window Decorations KCM pop up even there is no change
https://bugs.kde.org/show_bug.cgi?id=381806 Dr. Chapatin changed: What|Removed |Added Version|5.13.0 |5.13.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396077] Unnecessary Apply Changes Dialog
https://bugs.kde.org/show_bug.cgi?id=396077 Dr. Chapatin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Dr. Chapatin --- *** This bug has been marked as a duplicate of bug 381806 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381806] Window Decorations KCM pop up even there is no change
https://bugs.kde.org/show_bug.cgi?id=381806 Dr. Chapatin changed: What|Removed |Added CC||murat.cil...@gmail.com --- Comment #10 from Dr. Chapatin --- *** Bug 396077 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 --- Comment #135 from Ian Page Hands --- Coming here from (it was duped by someone) https://bugs.kde.org/show_bug.cgi?id=394583 For me at least, the task bar freezing is gone when I disable the compositor. I've been running with the compositor disabled for weeks now and I don't experience the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394583] "Panel" UI freezes, still functional but display is no longer updating
https://bugs.kde.org/show_bug.cgi?id=394583 --- Comment #4 from Ian Page Hands --- For what its worth... I have been running with the compositor disabled for a while now, and the issue is gone while in this mode. I suspect the issue still exists, but I just keep the compositor disabled. -- 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 David Edmundson changed: What|Removed |Added CC||bo...@discosucks.it --- Comment #15 from David Edmundson --- *** Bug 375781 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383660] plasmashell freezes when copying files
https://bugs.kde.org/show_bug.cgi?id=383660 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 358231 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386781] Plasma freezes until ready notification for file copy
https://bugs.kde.org/show_bug.cgi?id=386781 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 358231 *** -- 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 David Edmundson changed: What|Removed |Added CC||voidar...@gmail.com --- Comment #16 from David Edmundson --- *** Bug 386781 has been marked as a duplicate of this bug. *** -- 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 David Edmundson changed: What|Removed |Added CC||stratiladimitrie@rocketmail ||.com --- Comment #17 from David Edmundson --- *** Bug 383660 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375781] Plasma freezes while performing slow file operations
https://bugs.kde.org/show_bug.cgi?id=375781 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 358231 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 David Edmundson changed: What|Removed |Added CC||ipha...@gmail.com --- Comment #134 from David Edmundson --- *** Bug 394583 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
