[krita] [Bug 396430] New: I can not find the color code place.
https://bugs.kde.org/show_bug.cgi?id=396430 Bug ID: 396430 Summary: I can not find the color code place. Product: krita Version: 4.0.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: iyagi...@gmail.com Target Milestone: --- No matter where I look, I can not find the color code place. Also , I have to get the color code. -- 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 #14 from Martin Flöser --- Can you compare the wm_hints property? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396429] New: Palette docker not acting right, crashes
https://bugs.kde.org/show_bug.cgi?id=396429 Bug ID: 396429 Summary: Palette docker not acting right, crashes Product: krita Version: 4.1.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kurtwla...@gmail.com Target Milestone: --- I was attempting to set up a new palette for a drawing I am coloring. I attempted to create color groups first then add colors to them. I created a group, then a second, then on the third it crashes. This also happens if I create the groups after adding a color to another. In addition, when I added colors to a group they neither appeared nor were there any indication that the color id count increased. I am aware that in the version I was using the day before the colors would not appear until there were several added. I originally encountered this bug using Krita 4.0.0, but it was not encountered earlier as I have been able to add colors and groups the day before, I did update my windows this morning so that may be a clue. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 394348] Umounting mounted disk image (e.g. .iso file) does not remove it from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=394348 Dr. Chapatin changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396428] New: Bad scrolling up and down performance when editing a file on a sshfs
https://bugs.kde.org/show_bug.cgi?id=396428 Bug ID: 396428 Summary: Bad scrolling up and down performance when editing a file on a sshfs Product: kdevelop Version: 5.1.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: as9902...@gmail.com Target Milestone: --- When editing a php or a cpp file from an sshfs folder with KDevelop 5.1.1 simple actions like Page up, Page down, arrow up/down turn into a nightmare. Just navigating through the edited file it freezes the cursor numerous times for 20-30 seconds each time. The files are about 5k in size or less. Copying the remote files to a local folder everything works properly. Another source code editing tool called Sublime Text works fine on the same remote folder. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396427] Odd/left over rendering in locked layers after using transform tool a second time on layer group
https://bugs.kde.org/show_bug.cgi?id=396427 --- Comment #1 from vanyossi --- Created attachment 113893 --> https://bugs.kde.org/attachment.cgi?id=113893=edit Odd rendering after move tool After using move tool certain moves makes the rendering on the locked layer show a ghost in the transform tool preview. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396427] New: Odd/left over rendering in locked layers after using transform tool a second time on layer group
https://bugs.kde.org/show_bug.cgi?id=396427 Bug ID: 396427 Summary: Odd/left over rendering in locked layers after using transform tool a second time on layer group Product: krita Version: git master Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: ghe...@gmail.com Target Milestone: --- Created attachment 113892 --> https://bugs.kde.org/attachment.cgi?id=113892=edit group one locked one not locked Transform tool and locked layers render improperly for groups with locked layers. The locked layer will be render in the preview as transformable but the pixels will not update (as probably is expected). The odd thing comes in the second transform: the locked layer will render as if it was transformed previouly. Steps to reproduce: Using the file provided 1. transform tool, do any transformation on the group layer (this has locked and unlocked layers). 2. apply transformation 3. Activate transform tool again on the group layer Result: The locked layer will render the preview in transform tool as if it was transformed in the previous transformation. This odd rendering will stay for the duration of the session. It also happens after using the move tool. Using the file provided move the group such as the black shape to the top such as it dissapears (it also works to move it so it touches the four corners). It's not necessary for the shape to dissapear but it makes the effect more easily achievable. -- 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 Neousr changed: What|Removed |Added CC||neo...@protonmail.com --- Comment #3 from Neousr --- I can confirm this behavior with a 1 hour long mp3 using elisa 0.2.0 on Neon 5.13.2 UE. Skipping through different sections of the seek bar will eventually fail returning the small cursor (circle) to the beginning of the bar, reporting the incorrect length and position of the player. This can be related to the bug #376106 on this same component. Since both bugs once triggered return and try to return the player to minute 0:00. -- 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 #2 from bugreporte...@gmail.com --- I have to withdraw some (but not all) of what I said in my last comment. After further testing, even the user profile we assumed was "better" is not really better. It simply worked better a couple times. But on further testing, this user proves just as problematic as the other user profile. We find that both user profiles on this machine have all the problems described in the earlier comments. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396426] New: No notification when Discover finds updates
https://bugs.kde.org/show_bug.cgi?id=396426 Bug ID: 396426 Summary: No notification when Discover finds updates Product: Discover Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Sometimes I start plasma and Discover icon in the system tray indicates no update available. Some minutes later a small blue/red icon overlaps the Discover icon in the system tray indicating that updates are available but Discover/Plasma shows no updates notification. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396425] New: krita <3.0 on raspian stretch RPI3
https://bugs.kde.org/show_bug.cgi?id=396425 Bug ID: 396425 Summary: krita <3.0 on raspian stretch RPI3 Product: krita Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: darrenjamesmar...@yahoo.com Target Milestone: --- 2.8 krita jessie repos installed on raspian stretch RPI3 b+. dependencies appear resolved. obvious issues w/ update w/o hold for outdated libs. no krita on current stretch raspian or RPIF repos. GOAL: Educational G3-6. Any iteration krita running with any OS ver even dedicated and standalone Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [Current thread is 1 (Thread 0x732959c0 (LWP 720))] Thread 5 (Thread 0x69aff320 (LWP 752)): #0 0x74156d5c in g_main_context_check () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 #1 0x74157314 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 4 (Thread 0x64c2d320 (LWP 751)): #0 0x7424694c in __pthread_cond_wait (cond=0x13b1ec8, mutex=0x13b1eb0) at pthread_cond_wait.c:186 #1 0x75af3030 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #2 0x765aa19c in ?? () from /usr/lib/arm-linux-gnueabihf/libQtGui.so.4 #3 0x75af2a88 in ?? () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #4 0x7423ffc4 in start_thread (arg=0x64c2d320) at pthread_create.c:335 Backtrace stopped: Cannot access memory at address 0x3e4 Thread 3 (Thread 0x6a629320 (LWP 740)): #0 0x7424694c in __pthread_cond_wait (cond=0xa83f28, mutex=0xa83f10) at pthread_cond_wait.c:186 #1 0x75af3030 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #2 0x75aef174 in QSemaphore::tryAcquire(int, int) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #3 0x7552fa54 in KisTileDataSwapper::run() () from /usr/lib/libkritaimage.so.13 #4 0x75af2a88 in ?? () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #5 0x7423ffc4 in start_thread (arg=0x6a629320) at pthread_create.c:335 #6 0x76dc1bc8 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:76 from /lib/arm-linux-gnueabihf/libc.so.6 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 2 (Thread 0x6ae29320 (LWP 739)): #0 0x7424694c in __pthread_cond_wait (cond=0xa83cb0, mutex=0xa83c98) at pthread_cond_wait.c:186 #1 0x75af3030 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #2 0x75aeed14 in QSemaphore::acquire(int) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #3 0x7551219c in ?? () from /usr/lib/libkritaimage.so.13 #4 0x755125ac in ?? () from /usr/lib/libkritaimage.so.13 #5 0x75af2a88 in ?? () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4 #6 0x7423ffc4 in start_thread (arg=0x6ae29320) at pthread_create.c:335 #7 0x76dc1bc8 in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:76 from /lib/arm-linux-gnueabihf/libc.so.6 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x732959c0 (LWP 720)): #0 0x76d8d030 in nanosleep () at ../sysdeps/unix/syscall-template.S:84 #1 0x76d8cf00 in __sleep (seconds=0) at ../sysdeps/posix/sleep.c:55 #2 0x747b4aa8 in ?? () from /usr/lib/libkdeui.so.5 Backtrace stopped: previous frame identical to this frame (corrupt stack?) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396145] Frequent crashing with vector pen and calligraphy tools
https://bugs.kde.org/show_bug.cgi?id=396145 --- Comment #4 from bentontram...@gmail.com --- You are awesome! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396119] Rendering errors in new floating "find" toolbar
https://bugs.kde.org/show_bug.cgi?id=396119 Kurt Hindenburg changed: What|Removed |Added Latest Commit||https://commits.kde.org/kon ||sole/e176667d6809083808d89c ||4a68a963d10fbfce33 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Kurt Hindenburg --- Git commit e176667d6809083808d89c4a68a963d10fbfce33 by Kurt Hindenburg, on behalf of Mariusz Glebocki. Committed on 12/07/2018 at 00:49. Pushed by hindenburg into branch 'master'. IncrementalSearchBox: fix rendering during terminal scroll Summary: Prevent search widget from moving when scrolling session. Test Plan: * Run `seq 1000` * Turn on search * Hold Shift+Up, Shift+Down Actual result: the search box scrolls with terminal contents Expected result: only terminal should scroll, the box should remain unchanged Reviewers: #konsole, hindenburg Reviewed By: #konsole, hindenburg Subscribers: hindenburg, ngraham, konsole-devel Tags: #konsole Differential Revision: https://phabricator.kde.org/D14038 M +1-1src/TerminalDisplay.cpp https://commits.kde.org/konsole/e176667d6809083808d89c4a68a963d10fbfce33 -- 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 #1 from bugreporte...@gmail.com --- Further updates. I tested two more different systems today, both laptops with multiple external monitors connected. With this testing, I observed several new behaviors. 1. The problem is not exactly the same on all user accounts on the same system. Under plasma5, some user accounts have severe problems with Display & Monitor (and panel and desktop configuration) settings getting lost and other user accounts are less adversely affected. 2. The display layout (I guess this is also called screen geometry) as well as some panel and desktop settings can be lost by logging out and logging back in (without any hardware changes. 3. The same settings can also be lost by undocking and re-docking without logging out for that entire process. 4. In a user account that has a problem with some displays not being enabled (by kscreen), logging out to sddm results in sddm showing all the connected displays properly. 5. Sometimes, after logging in or connecting to the dock, Plasma5 fails to show any desktop at all (just blank black screens). A normal, non-sudo user cannot recover from this except by rebooting as far as we know. It can become a very serious problem. However, one workaround we found for privileged users is to switch to a different virtual console (CTRL-ALT-F2 in Arch for example) and run sudo systemctl restart sddm. In terms of the differences in user accounts, one user account we tested never remembers all 3 connected displays. It also loses the primary display setting. After adding the missing display (which had been configured previously), it doesn't remember the correct placement (geometry/layout). It loses one panel. It loses a desktop background too. This user account has this problem every single time docking or logging in (even if never undocked after logging out). This user account on this system did not have any of these issues until the recent plasma5 updates a couple weeks ago. Another user account on the same machine has much fewer problems. We did see a few display issues, but we also had several successful undock-dock sequences where the display and related configuration was remembered. Obviously more testing is needed due to the inconsistencies observed, but we can definitely say that there are important differences per user account. Can anyone suggest any user configs or user settings that might be related to this behavior. We will test further is someone suggests some steps. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 --- Comment #5 from Dr. Chapatin --- Created attachment 113891 --> https://bugs.kde.org/attachment.cgi?id=113891=edit screenshot taken on Arch, plasma 5.13.3 unfortunately it's not fixed in plasma 5.13.3, Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368600] GTK Application Style cursors/icons themes lists should be in alphabetical order
https://bugs.kde.org/show_bug.cgi?id=368600 Dr. Chapatin changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395070] Krita Crashes suddenly without warning
https://bugs.kde.org/show_bug.cgi?id=395070 --- Comment #12 from Bryan Willis --- Sorry, one more thing I'd like to add. The transform tool works on an app image of Krita 4.0.1 that I have laying around. So it really was the upgrade to 4.1 that has broken the transform tool. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395070] Krita Crashes suddenly without warning
https://bugs.kde.org/show_bug.cgi?id=395070 --- Comment #11 from Bryan Willis --- Sorry to spam here. But now my program on any file just permanently won't transform. It always crashes. I'm going to try upgrading and see if that helps. If not, I think krita might have just broke too badly for me to use any longer. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395070] Krita Crashes suddenly without warning
https://bugs.kde.org/show_bug.cgi?id=395070 --- Comment #10 from Bryan Willis --- Okay so I've gotten that last crash to repeat itself. I opened the autosave file, saved it out as a new krita file. And the exact same crash happened again when I attempted to lasso, then transform part of my drawing. I'm beginning to notice a pattern where using the transform tools causes this, but I don't want to throw you guys off with bad information. Either way, here's another crash log: (gdb) thread apply all bt Thread 23 (Thread 0x7fff9e5ff700 (LWP 3495)): #0 0x7fffee024ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff9e5fec40, expected=0, futex_word=0x6708a650) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fffee024ed9 in __pthread_cond_wait_common (abstime=0x7fff9e5fed00, mutex=0x6708a600, cond=0x6708a628) at pthread_cond_wait.c:533 #2 0x7fffee024ed9 in __pthread_cond_timedwait (cond=0x6708a628, mutex=0x6708a600, abstime=0x7fff9e5fed00) at pthread_cond_wait.c:667 #3 0x74c73458 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74c6f52d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74c7216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffee01e6db in start_thread (arg=0x7fff9e5ff700) at pthread_create.c:463 #7 0x7435088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fff830ff700 (LWP 3494)): #0 0x74343bf9 in __GI___poll (fds=0x66e7f9b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffec999439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffec99954c in g_main_context_iteration () ---Type to continue, or q to quit--- at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fff8310736d in () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4 0x7fffec9c0e05 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fffee01e6db in start_thread (arg=0x7fff830ff700) at pthread_create.c:463 #6 0x7435088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fffa4e5b700 (LWP 3478)): #0 0x74343bf9 in __GI___poll (fds=0x7fff98004690, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffec999439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffec99954c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x74ea98ef in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74e4e9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74c6d22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffb6bc12a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x74c7216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ---Type to continue, or q to quit--- #8 0x7fffee01e6db in start_thread (arg=0x7fffa4e5b700) at pthread_create.c:463 #9 0x7435088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fffa6723700 (LWP 3477)): #0 0x74343bf9 in __GI___poll (fds=0x7fffa0003110, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffec999439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffec99954c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x74ea98ef in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74e4e9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74c6d22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffb73c36f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x74c7216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fffee01e6db in start_thread (arg=0x7fffa6723700) at pthread_create.c:463 #9 0x7435088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ---Type to continue, or q to quit--- Thread 7 (Thread 0x7fffb5f2f700 (LWP 3476)): #0 0x7fffee0249f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x606e7e80) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fffee0249f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x606e7e30, cond=0x606e7e58) at pthread_cond_wait.c:502 #2 0x7fffee0249f3 in __pthread_cond_wait (cond=0x606e7e58, mutex=0x606e7e30) at pthread_cond_wait.c:655 #3 0x74c7359b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74c6be5f in QSemaphore::tryAcquire(int, int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x71f93f43 in
[krita] [Bug 395070] Krita Crashes suddenly without warning
https://bugs.kde.org/show_bug.cgi?id=395070 --- Comment #9 from Bryan Willis --- Here's another crash. I don't know where you guys are with this. I'm sure you're busy, but I'd deeply appreciate it if someone could provide some insight into why this is happening. Thanks. (gdb) set pagination off (gdb) thread apply all bt Thread 91 (Thread 0x7fff9e5ff700 (LWP 3233)): #0 0x7fffee024ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fff9e5fec40, expected=0, futex_word=0x66408730) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fffee024ed9 in __pthread_cond_wait_common (abstime=0x7fff9e5fed00, mutex=0x664086e0, cond=0x66408708) at pthread_cond_wait.c:533 #2 0x7fffee024ed9 in __pthread_cond_timedwait (cond=0x66408708, mutex=0x664086e0, abstime=0x7fff9e5fed00) at pthread_cond_wait.c:667 #3 0x74c73458 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74c6f52d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74c7216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffee01e6db in start_thread (arg=0x7fff9e5ff700) at pthread_create.c:463 #7 0x7435088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fffa4e5b700 (LWP 2535)): #0 0x74343bf9 in __GI___poll (fds=0x7fff980031f0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffec999439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffec99954c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x74ea98ef in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74e4e9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74c6d22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffb6bc12a6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x74c7216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fffee01e6db in start_thread (arg=0x7fffa4e5b700) at pthread_create.c:463 #9 0x7435088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fffa6723700 (LWP 2534)): #0 0x74343bf9 in __GI___poll (fds=0x7fffa0003110, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fffec999439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fffec99954c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x74ea98ef in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74e4e9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x74c6d22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fffb73c36f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x74c7216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fffee01e6db in start_thread (arg=0x7fffa6723700) at pthread_create.c:463 #9 0x7435088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fffb5f2f700 (LWP 2533)): #0 0x7fffee0249f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x606e8424) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fffee0249f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x606e83d0, cond=0x606e83f8) at pthread_cond_wait.c:502 #2 0x7fffee0249f3 in __pthread_cond_wait (cond=0x606e83f8, mutex=0x606e83d0) at pthread_cond_wait.c:655 #3 0x74c7359b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x74c6be5f in QSemaphore::tryAcquire(int, int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x71f93f43 in KisTileDataSwapper::waitForWork() (this=) at ./libs/image/tiles3/swap/kis_tile_data_swapper.cpp:86 #6 0x71f9416a in KisTileDataSwapper::run() (this=0x7247fc60 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at ./libs/image/tiles3/swap/kis_tile_data_swapper.cpp:92 #7 0x74c7216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fffee01e6db in start_thread (arg=0x7fffb5f2f700) at pthread_create.c:463 #9 0x7435088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fffb6730700 (LWP 2532)): #0 0x7fffee0249f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x606e81b4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fffee0249f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x606e8160, cond=0x606e8188) at pthread_cond_wait.c:502 #2 0x7fffee0249f3 in __pthread_cond_wait (cond=0x606e8188, mutex=0x606e8160) at pthread_cond_wait.c:655 #3 0x74c7359b in QWaitCondition::wait(QMutex*, unsigned long) () at
[valgrind] [Bug 396367] unhandled syscall amd64-darwin unix:520 and unix:521
https://bugs.kde.org/show_bug.cgi?id=396367 Rhys Kidd changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Assignee|jsew...@acm.org |rhysk...@gmail.com CC||rhysk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 334075] plugin for Terminal on bottom of GUI and view terminal doesn't work
https://bugs.kde.org/show_bug.cgi?id=334075 Hadjo changed: What|Removed |Added CC||hagualsh...@gmail.com -- 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 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #8 from Tom Hughes --- That looks very similar to my version at https://github.com/tomhughes/valgrind/commit/40a30ca68769c0825e078b731cd115849b1a6744 but I think you've got something a bit extra cope with multiple ro segments? -- 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 H.J. Lu changed: What|Removed |Added Summary|Reading debug info of |Reading debug info of |binaries linked with|binaries with readonly |readonly PT_LOAD segments |PT_LOAD segments -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 395682] Reading debug info of binaries linked with readonly PT_LOAD segments
https://bugs.kde.org/show_bug.cgi?id=395682 H.J. Lu changed: What|Removed |Added Summary|Reading debug info of |Reading debug info of |binaries linked with|binaries linked with |binutils ld -z |readonly PT_LOAD segments |separate-code | --- Comment #7 from H.J. Lu --- The problem is with readonly PT_LOAD segments. Please try users/hjl/pr395682/master branch at https://github.com/hjl-tools/valgrind/tree/users/hjl/pr395682/master -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 301447] Desktop grid effect changes activities
https://bugs.kde.org/show_bug.cgi?id=301447 --- Comment #13 from Stefanos Harhalakis --- Thanks Vlad! -- 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 #13 from john Terragon --- Isn't that something that an application can set/change to give a suggestion to the wm (the hint part...)? Anyways, let me know if there's something else I can try. I sync'ed the two roots with another system, a desktop one (and more recent, a 4770k I think). I see the same behavior, it's about triple the cpu usage by kwin 5.13 wrt to 5.12. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396381] PyKrita doesn't load with PyQt 5.11
https://bugs.kde.org/show_bug.cgi?id=396381 Antonio Rojas changed: What|Removed |Added Resolution|LATER |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Antonio Rojas --- Patch at https://phabricator.kde.org/D14061 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396424] New: Says it can not save program files in krita. Will not save anything, and it crashes.
https://bugs.kde.org/show_bug.cgi?id=396424 Bug ID: 396424 Summary: Says it can not save program files in krita. Will not save anything, and it crashes. Product: krita Version: 4.1.0 alpha Platform: Other OS: other Status: UNCONFIRMED Severity: grave Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: katmcelroy...@gmail.com Target Milestone: --- Krita 4.1.0 is bugging out. I have a Windows8. Even if I make a new file and don't draw anything it still gives me this= Could not save C:/Program Files/Krita (x64)/share/krita/templates/comics/.source/help.kra Reason: It gives no reason, and I have been making a comic. Also made it a normal custom document and not on comic templates(not that I haven't tryed). I made a sketch before and I saved it but the next day when I tried to load it, it would not and closed the program and it loaded up but I cannot add anything to it cuz it will not save. I am not sure what to do. Even when my computer is Windowes8 it's a 10 and system info says this= 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.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Lukas Sabota changed: What|Removed |Added CC||lu...@lwsabota.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395816] KWin froze on pointer constraint OSD
https://bugs.kde.org/show_bug.cgi?id=395816 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Q_GLOBAL_STATIC can't lock-up. I don't think it's frozen where that backtrace ends up. Given we have a geometry resize, I'd say it's more likely we're in an infinite resizing loop. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 395885] Printer Settings should be saved under user profile, not global CUPS configuration
https://bugs.kde.org/show_bug.cgi?id=395885 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395346] Closing an application crashes Kwin
https://bugs.kde.org/show_bug.cgi?id=395346 David Edmundson changed: What|Removed |Added CC||cip...@gmail.com --- Comment #15 from David Edmundson --- *** Bug 392614 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392614] kwin_wayland crash when theme applied
https://bugs.kde.org/show_bug.cgi?id=392614 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #5 from David Edmundson --- #20 0x7f3f071d2974 in QQuickRenderControl::~QQuickRenderControl (this=0x555d6e06e530, __in_chrg=) at items/qquickrendercontrol.cpp:181 it is *** This bug has been marked as a duplicate of bug 395346 *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 396423] New: file drag image stays stuck over mouse
https://bugs.kde.org/show_bug.cgi?id=396423 Bug ID: 396423 Summary: file drag image stays stuck over mouse Product: krdc Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: tuc03...@gmail.com Target Milestone: --- Created attachment 113890 --> https://bugs.kde.org/attachment.cgi?id=113890=edit image hanging over mouse After trying to drag a file to copy to RDP client session, the folder icon became stuck over the mouse. this has persisted accross app purge, .home configuration removal, and a reboot. all sessions once started still have that icon stuck over the clients mouse. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395346] Closing an application crashes Kwin
https://bugs.kde.org/show_bug.cgi?id=395346 David Edmundson changed: What|Removed |Added Resolution|FIXED |UPSTREAM --- Comment #14 from David Edmundson --- FWIW, my workaround was reverted as it caused another error. My proper fix in Qt 5.12 still remains. I'm not sure if it's worth me redoing the workaround concept but at a different level. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395346] Closing an application crashes Kwin
https://bugs.kde.org/show_bug.cgi?id=395346 David Edmundson changed: What|Removed |Added CC||mspe...@gmail.com --- Comment #13 from David Edmundson --- *** Bug 396258 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #8 from David Edmundson --- #20 0x7f5d8176f200 in QQuickRenderControl::~QQuickRenderControl (this=0x564050e58fa0, __in_chrg=) It is *** This bug has been marked as a duplicate of bug 395346 *** -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #11 from Albert Astals Cid --- (In reply to David Edmundson from comment #10) > > That's why I am asking someone from the Plasma side to answer whether we > > want to backport this fixes or not. Pretty please? > > yes please. Thanks for confirmation :) I'm away from a computer until next week and then i have to take care of KDE Applications 18.08 branching, but it is my understanding that next Plasma 5.12 release is not until september so i should be on time for that :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396422] New: Plasma crashes when trying to change clock settings
https://bugs.kde.org/show_bug.cgi?id=396422
Bug ID: 396422
Summary: Plasma crashes when trying to change clock settings
Product: plasmashell
Version: 5.8.7
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: lars...@northernraven.de
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.8.7)
Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.138-59-default x86_64
Distribution: "openSUSE Leap 42.3"
-- Information about the crash:
- What I was doing when the application crashed:
Change appearance ("Erscheinungsbild") settings of the clock applet.
The crash does not seem to be reproducible.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efdce5ea900 (LWP 3719))]
Thread 17 (Thread 0x7efcd3df8700 (LWP 7850)):
#0 0x7efdc7a6530d in poll () at /lib64/libc.so.6
#1 0x7efdc40bd314 in () at /usr/lib64/libglib-2.0.so.0
#2 0x7efdc40bd42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3 0x7efdc837b1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4 0x7efdc8328bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5 0x7efdc8163f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x7efdc8168a29 in () at /usr/lib64/libQt5Core.so.5
#7 0x7efdc7261724 in start_thread () at /lib64/libpthread.so.0
#8 0x7efdc7a6de8d in clone () at /lib64/libc.so.6
Thread 16 (Thread 0x7efcdcdd8700 (LWP 7847)):
#0 0x7efdc72660ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7efdc816969b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2 0x7efdcc09a55b in () at /usr/lib64/libQt5Quick.so.5
#3 0x7efdcc09c2d5 in () at /usr/lib64/libQt5Quick.so.5
#4 0x7efdc8168a29 in () at /usr/lib64/libQt5Core.so.5
#5 0x7efdc7261724 in start_thread () at /lib64/libpthread.so.0
#6 0x7efdc7a6de8d in clone () at /lib64/libc.so.6
Thread 15 (Thread 0x7efcc93cd700 (LWP 7846)):
#0 0x7efdc7a6530d in poll () at /lib64/libc.so.6
#1 0x7efdc40bd314 in () at /usr/lib64/libglib-2.0.so.0
#2 0x7efdc40bd42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3 0x7efdc837b1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4 0x7efdc8328bfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5 0x7efdc8163f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x7efdcb49b3d8 in () at /usr/lib64/libQt5Qml.so.5
#7 0x7efdc8168a29 in () at /usr/lib64/libQt5Core.so.5
#8 0x7efdc7261724 in start_thread () at /lib64/libpthread.so.0
#9 0x7efdc7a6de8d in clone () at /lib64/libc.so.6
Thread 14 (Thread 0x7efccd4bd700 (LWP 6954)):
#0 0x7efdc72660ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7efdc816969b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2 0x7efdcc09a55b in () at /usr/lib64/libQt5Quick.so.5
#3 0x7efdcc09c2d5 in () at /usr/lib64/libQt5Quick.so.5
#4 0x7efdc8168a29 in () at /usr/lib64/libQt5Core.so.5
#5 0x7efdc7261724 in start_thread () at /lib64/libpthread.so.0
#6 0x7efdc7a6de8d in clone () at /lib64/libc.so.6
Thread 13 (Thread 0x7efbc700 (LWP 5944)):
#0 0x7efdc72660ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7efdc816969b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2 0x7efdcc09a55b in () at /usr/lib64/libQt5Quick.so.5
#3 0x7efdcc09c2d5 in () at /usr/lib64/libQt5Quick.so.5
#4 0x7efdc8168a29 in () at /usr/lib64/libQt5Core.so.5
#5 0x7efdc7261724 in start_thread () at /lib64/libpthread.so.0
#6 0x7efdc7a6de8d in clone () at /lib64/libc.so.6
Thread 12 (Thread 0x7efceeddf700 (LWP 5884)):
#0 0x7efdc72660ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7efdc816969b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2 0x7efdcc09a55b in () at /usr/lib64/libQt5Quick.so.5
#3 0x7efdcc09c2d5 in () at /usr/lib64/libQt5Quick.so.5
#4 0x7efdc8168a29 in () at /usr/lib64/libQt5Core.so.5
#5 0x7efdc7261724 in start_thread () at /lib64/libpthread.so.0
#6 0x7efdc7a6de8d in clone () at /lib64/libc.so.6
Thread 11 (Thread 0x7efcc8bcc700 (LWP 4353)):
#0 0x7efdc72660ff in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7efdc816969b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib64/libQt5Core.so.5
#2 0x7efdcc09a55b in () at
[plasmashell] [Bug 396359] crash in QQuickItemPrivate::addToDirtyList
https://bugs.kde.org/show_bug.cgi?id=396359 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396359] crash in QQuickItemPrivate::addToDirtyList
https://bugs.kde.org/show_bug.cgi?id=396359 --- Comment #3 from David Edmundson --- Other dupe reports are all whilst hotplugging displays. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374930] Plasma crashes when hot-plug new displays
https://bugs.kde.org/show_bug.cgi?id=374930 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from David Edmundson --- *** This bug has been marked as a duplicate of bug 396359 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396359] crash in QQuickItemPrivate::addToDirtyList
https://bugs.kde.org/show_bug.cgi?id=396359 David Edmundson changed: What|Removed |Added Summary|Plasma crashes when panel |crash in |get blocked |QQuickItemPrivate::addToDir ||tyList Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Component|general |generic-crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396359] crash in QQuickItemPrivate::addToDirtyList
https://bugs.kde.org/show_bug.cgi?id=396359 David Edmundson changed: What|Removed |Added CC||dmitry.s.lisov...@gmail.com --- Comment #2 from David Edmundson --- *** Bug 374930 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369864] Plasma crash when second monitor is plugged
https://bugs.kde.org/show_bug.cgi?id=369864 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from David Edmundson --- *** This bug has been marked as a duplicate of bug 396359 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396359] crash in QQuickItemPrivate::addToDirtyList
https://bugs.kde.org/show_bug.cgi?id=396359 David Edmundson changed: What|Removed |Added CC||baretdid...@gmail.com --- Comment #1 from David Edmundson --- *** Bug 369864 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 396351] "Remove" button changes to "Downloading" while a snap package is uninstalled
https://bugs.kde.org/show_bug.cgi?id=396351 Aleix Pol changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dis ||cover/fa66dbf50b06b75a8bf41 ||a6683212f60010c8f71 --- Comment #1 from Aleix Pol --- Git commit fa66dbf50b06b75a8bf41a6683212f60010c8f71 by Aleix Pol. Committed on 11/07/2018 at 21:28. Pushed by apol into branch 'Plasma/5.12'. Proper status when removing snaps M +1-1libdiscover/backends/SnapBackend/SnapTransaction.cpp https://commits.kde.org/discover/fa66dbf50b06b75a8bf41a6683212f60010c8f71 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 396394] Elisa doesn't run when I launch it from the Application Launcher nor will Elisa run from the terminal. Kubuntu 18.04
https://bugs.kde.org/show_bug.cgi?id=396394 Matthieu Gallien changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Matthieu Gallien --- I am investigating possible solutions. Not sure I will be able to quickly find a solution. I am reading about the flatpak support for proprietary OpenGL drivers. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 396320] Revive KCM-Trackpoint settings
https://bugs.kde.org/show_bug.cgi?id=396320 --- Comment #3 from m.w...@web.de --- @Nate: Is this documentation really complete? Has press-to-select been removed from beeing able to be configured? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396179] Krita crashing randomly
https://bugs.kde.org/show_bug.cgi?id=396179 --- Comment #8 from Mohammad --- The crashing is not caused by the transform tool. I don't know what is causing it though, and it crashes every 10-15 minutes. It's been a week or more since this has been happening and it's the most annoying thing ever. I hope I get it fixed soon. -- 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 Ralf Habacker changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Ralf Habacker --- Just recognized, that this fix does not help, if the transaction form below the ledger view is used. > In "Ledger view", date displays full CCYY format How do you setup this format ? I cannot enter this format in the KDE regional settings kcontrol module, started inside kmymoney with "settings"->"KDE regional/language settings". The date column in the ledger view uses the regional short date format. If I enter the long format e..g "WOCHENTAG, tT. MONAT " I can see that some dates e.g. "Donnerstag, 26. September 6999" in german, the last digit is still hidden. This is because int Register::minimumColumnWidth(int col) there is used KGlobal::locale()->formatDate(QDate(6999, 12, 29), KLocale::ShortDate) + " "); for calculating the date column width. This returning "Sonntag, 29. Dezember 6999" for german language, which is shorter than the longest possible string in german. "Donnerstag, 26. September 6999" In other languages the longest date string may be on a different date. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 396394] Elisa doesn't run when I launch it from the Application Launcher nor will Elisa run from the terminal. Kubuntu 18.04
https://bugs.kde.org/show_bug.cgi?id=396394 Neousr changed: What|Removed |Added CC||neo...@protonmail.com --- Comment #1 from Neousr --- I can confirm this behavior, same error message. Neon 5.13 UE >From what i can gather by trying to replicate some bugs on Elisa 0.2.0. The problem seems only present when using the proprietary nvidia driver. (396.24.02). Elisa runs with out problem using any of the open source drivers (intel,amd,nvidia). As an observation the current kdenlive flatpak outputs the same error. (there is no report at the moment on that) So my educated guess can it be a OpenGL acceleration problem between the libraries/flatpak and the nvidia driver? -- 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 --- Comment #3 from Toni Asensi Esteve --- > Do you have any ideas on HOW this can be implemented in code? Which file will > involve most of the changes etc. I haven't worked with those sections of the source code of Krusader :-( -- 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 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #3 from Toni Asensi Esteve --- > No, I tried but I can not reproduce the issue on the same files. > So what is that mean? If I can not reproduce then to report bug is > pointless? > > Please explain bug report system to let me and you to do less pointless > work. Sometimes a problem happens because of a particular problem in a particular computer, and therefore the bug is not reproducible by a developer, and so there's not much he can do about it, he sees that the system is working correctly :-( Anyway, thanks for your interest. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396421] unshading a window should (probably) raise it to the front
https://bugs.kde.org/show_bug.cgi?id=396421 Martin Flöser changed: What|Removed |Added Resolution|--- |WONTFIX Severity|normal |wishlist Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Flöser --- Shading and unshading are not actions which affect the stacking order or the active state. The idea is to temporarily hide/show the window. There is no indication that users in general want that to change. It has been like that for decades. Given that I changed the report to feature request. For the feature request I'm sorry to say that this won't be implemented. Shading is a hardly used feature and thus does not justify adding another config option given that there are easy workarounds. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396421] New: unshading a window should (probably) raise it to the front
https://bugs.kde.org/show_bug.cgi?id=396421 Bug ID: 396421 Summary: unshading a window should (probably) raise it to the front Product: kwin Version: 5.12.6 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kd...@osndok.com Target Milestone: --- Created attachment 113889 --> https://bugs.kde.org/attachment.cgi?id=113889=edit freshly-unshaded window hidden by its neighbors This probably isn't noticed in the default configuration, as the first click of double-clicking a titlebar to unshade a window will also raise that window. However, if one uses the mouse-wheel to shade/unshade windows (which has being able to densely-pack still-usable windows in-place), the window *OFTEN* is obscured by the adjacent shaded windows when unshaded. In practice, the most frequently used window will statistically be on top, but it can still be quite a nuisance. (I have attached a screenshot of this effect) I'm sure it sounds trivial, as the workaround would be to simply click the titlebar again that is under the mouse (like bug#8005), but I find that there is something odd about this mouse-wheel-to-button lateral movement that discourages any sort of haste, even with repetition. So I'm a bit stuck... on the one hand, I *can* just set the double click action to be window shading (and avoid the odd/slow finger motion), but then I would lose other productivity boosts like double clicking to make the window appear on all desktops, and a peculiar benefit of quickly shading windows en-mass by moving the mouse position & wheel at the same time. It would be nice if there was an option, default, window-rule-boolean, or plugin to simply raise windows when they are unshaded. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388440] scrolling in KMail: "page down" only works once
https://bugs.kde.org/show_bug.cgi?id=388440 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #10 from Till Schäfer --- I can reproduce this issue with - KMail 5.8.2 - qt 5.11.1 - frameworks 5.47 on gentoo. Page up does always jump to the top and does not scroll one page up. Page down does always jump to the second page (even if i already scrolled further). The previous mentioned workaround (unmap (set to none) shortcut "Scroll Message Down/Up (more)") works for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356447] ansincronized wacom cintiq pencil
https://bugs.kde.org/show_bug.cgi?id=356447 Tom changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED CC||jakotom2...@gmail.com Resolution|WORKSFORME |--- --- Comment #3 from Tom --- I have the same problem... and I am not able to solve it by calibrating my Cintiq or something like that. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 396311] About dialog Qt(?WebEngine) version
https://bugs.kde.org/show_bug.cgi?id=396311 Moonchild changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Moonchild --- Well, currently i have QtWebEngine version, different then Qt version, and that what is displayed in this dialog is quite wrong... However, i'm closing the issue. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396420] New: Popular URLs in Location Bar
https://bugs.kde.org/show_bug.cgi?id=396420 Bug ID: 396420 Summary: Popular URLs in Location Bar Product: krusader Version: 2.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: dufferzaf...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Do we really need a separate Popular URLs Panel? Browsers don't! All they have is a single location bar and that seems to work really well. Is there something inherent about file managers that prevents us from using the same design? Sorry I have more questions than answers / ideas, but I really wanted to discuss how (or if) the Krusader UI/UX can be improved. Only because I love it so much! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 393621] Sound distortion when annotation is opened/made.
https://bugs.kde.org/show_bug.cgi?id=393621 Johannes Krupp changed: What|Removed |Added CC||kde@jkrupp.ninja -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 396360] Shortcut F does not toggle between original size and fit to window any more
https://bugs.kde.org/show_bug.cgi?id=396360 --- Comment #3 from Henrik Fehlauer --- At least commits shouldn't break people's existing workflows ;) We could provide default shortcuts for every mode (Fit/Fill/100%), but switching back and forth is much quicker when you don't have to hunt for another key and can simply toggle the same shortcut. How about doing both: - "=" for 100%, Ctrl++ and Ctrl+- for Zoom In/Out (like in Firefox) - "F" for Fit (zoom to 100% if already zoomed to fit) - "Shift+F" for Fill (zoom to 100% if already zoomed to fill) And for middle-clicking, it could work like this (to be added to the docbook): - Middle-click: Toggle between Fit and 100% - Shift + middle-click: Toggle between Fill and 100% -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396419] New: Popular URLs Panel should remember it's size
https://bugs.kde.org/show_bug.cgi?id=396419 Bug ID: 396419 Summary: Popular URLs Panel should remember it's size Product: krusader Version: 2.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: dufferzaf...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- The default view for Popular URLs panel is very small. Screenshot: https://i.imgur.com/QvbL39I.png It doesn't allow me to visually differentiate the paths. I end up resizing the panel most of the times. But then, Krusader just forgets the sizing and opens it again with small size. -- 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 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes --- I don't think we have any code which does searching for dynamic libraries - we just load the interpreter (ie ld.so) and then let that do the actual dynamic linking. So this must be some environmental difference - either literally in the environment variables, or in the auxilliary vector or something. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396418] New: Add a canvas with auto-hiding area like Android
https://bugs.kde.org/show_bug.cgi?id=396418 Bug ID: 396418 Summary: Add a canvas with auto-hiding area like Android Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided In other mobile OS, you have a Canvas element with top, bottom, left and right components that can be hidden when you press on the canvas or after a delay. On desktopm they become visible when you move the mouse. Such component would be useful for camera or video chat apps like Ring-KDE. It is currently hardcoded, but could be upstreamed as a generic kirigami component -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396417] New: It is hard to recover size in the global drawer
https://bugs.kde.org/show_bug.cgi?id=396417 Bug ID: 396417 Summary: It is hard to recover size in the global drawer Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided In the global drawer, there is the name of the application in the drawer header. This is all and well, but when more space is required in the drawer, it is nicer to get rid of it dynamically instead of having a scrollable drawer. As of recently, getting to disable the header icon and app name is possible, but the space wasn't fully recovered. Also getting a QtQuick.Layout2 based element to take the full height can be made to work, but it definitely doesn't "just works" when you use `Layout.fillHeight: true`. In both case, you can dark magic around the issues using Voodoo, but the code is ugly and it should not be necessary. tl;dr: going from having the header to not having the header while using the full drawer height should work and it currently doesn't. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396416] New: The mobile swipe item handles have issues with different sized entries
https://bugs.kde.org/show_bug.cgi?id=396416 Bug ID: 396416 Summary: The mobile swipe item handles have issues with different sized entries Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided (disclaimer: This is a summary of a meeting discussion) When using a list of swipe item with inconsistent height, the handles become all over the place instead of vertically aligned. This is because taller elements have a different kind of handle than the smaller one. While equally sized elements are always preferred, it isn't always practical. For example, if a Ring-KDE account goes down, it need to be very explicit and an (/!\) emblem is added to the list and it increases the height a bit. The point being it doesn't render correctly and it should. If I should find a better way to display the account list with consistent size is parallel to this bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 396415] New: Valgrind is not looking up $ORIGIN rpath of shebang programs
https://bugs.kde.org/show_bug.cgi?id=396415
Bug ID: 396415
Summary: Valgrind is not looking up $ORIGIN rpath of shebang
programs
Product: valgrind
Version: 3.10.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: jack.zhao.f...@gmail.com
Target Milestone: ---
> uname -a
Linux zanarkand 3.10.0-693.2.2.el7.x86_64 #1 SMP Sat Sep 9 03:55:24 EDT 2017
x86_64 x86_64 x86_64 GNU/Linux
> valgrind --version
valgrind-3.10.0
-
Steps to reproduce:
1. Write a bare-minimum library with something that can be included. Mine
looked like this:
> cat foo.h
extern void doSomething(void);
> cat foo.cpp
#include
void doSomething(void) {
std::cout << "did something" << std::endl;
}
2. Write a bare-minimum program that accepts a file as an argument and does
something to the file. Make sure to include the library we just made and invoke
its function. In my case I made it just print the file contents to stdout after
invoking the doSomething function. See:
> cat main.cpp
#include
#include
#include
#include "foo.h"
int main(int argc, char* argv[]) {
doSomething();
if (argc != 2) {
std::cerr << "one parameter, should be file path" << std::endl;
}
std::string line;
std::ifstream myfile(argv[1]);
if (myfile.is_open()) {
while(getline(myfile, line)) {
std::cout << line << std::endl;
}
myfile.close();
}
}
3. Build the library as a shared object (i.e. libfoo.so)
4. Build the main program with the following rpath: $ORIGIN/../lib, see:
> readelf -d main
Dynamic section at offset 0x1de8 contains 28 entries:
TagType Name/Value
0x0001 (NEEDED) Shared library: [libfoo.so]
0x0001 (NEEDED) Shared library: [libstdc++.so.6]
0x0001 (NEEDED) Shared library: [libgcc_s.so.1]
0x0001 (NEEDED) Shared library: [libc.so.6]
0x000f (RPATH) Library rpath: [$ORIGIN/../lib]
0x000c (INIT) 0x400c90
0x000d (FINI) 0x401104
0x0019 (INIT_ARRAY) 0x601dc8
0x001b (INIT_ARRAYSZ) 16 (bytes)
0x001a (FINI_ARRAY) 0x601dd8
0x001c (FINI_ARRAYSZ) 8 (bytes)
0x6ef5 (GNU_HASH) 0x400298
0x0005 (STRTAB) 0x4005e8
0x0006 (SYMTAB) 0x4002e8
0x000a (STRSZ) 976 (bytes)
0x000b (SYMENT) 24 (bytes)
0x0015 (DEBUG) 0x0
0x0003 (PLTGOT) 0x602000
0x0002 (PLTRELSZ) 480 (bytes)
0x0014 (PLTREL) RELA
0x0017 (JMPREL) 0x400ab0
0x0007 (RELA) 0x400a68
0x0008 (RELASZ) 72 (bytes)
0x0009 (RELAENT)24 (bytes)
0x6ffe (VERNEED)0x4009f8
0x6fff (VERNEEDNUM) 3
0x6ff0 (VERSYM) 0x4009b8
0x (NULL) 0x0
5. Put the library and main program in the following directories:
test_repro/lib/libfoo.so
test_repro/bin/main
6. Create the following file at the following location with a shebang line that
points to main:
test_repro/script/subdir/myscript (the `subdir` is important here)
> cat myscript
#!/path/to/my/test_repro/bin/main
lorem ipsum
7. Make the 'myscript' file executable, and run it. It should work - main gets
invoked as the program to feed the file into, and main is able to load in
libfoo.so.
8. Run myscript through valgrind (i.e. `valgrind ./myscript`) and observe that
it fails to load libfoo.so
-
Note that:
- issue does not happen when running `valgrind /path/to/my/test_repro/bin/main
myscript` (i.e. when execution does not depend on shebang)
- issue does not happen when rpath contains an absolute path to
/path/to/my/test_repro/lib, only when rpath relies on $ORIGIN
- issue does not happen if I put `myscript` into `test_repro/script` instead
of `test_repro/script/subdir`. This suggests that $ORIGIN path is processed but
treated as path relative to `myscript` instead of path relative to the shebang
program `main`.
Anyway, thanks!
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kirigami] [Bug 396414] New: There is an usability issue in mobile swipe item
https://bugs.kde.org/show_bug.cgi?id=396414 Bug ID: 396414 Summary: There is an usability issue in mobile swipe item Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided (disclaimer: This is a summary of a meeting discussion) When using swipe item, you get a list of action represented as icons. On the desktop, you can have a tooltip and the user kind of expect them. On the mobile, you may or may not be able to hold the icon pressed, but this is hard to discover. The users seem scare to click on actions where they are not sure what the icon does. Given the worst case scenario in Ring-KDE is doing a phone call by accident, the user just ignore the actions because they are scared. Some ways to showing the action text (label) either by displaying the actions vertically, a popup or anything else would be needed to fix this perceived problem. More discussions are needed with the VDG about this. -- 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 --- Comment #2 from pointl...@maildrop.cc --- No, I tried but I can not reproduce the issue on the same files. So what is that mean? If I can not reproduce then to report bug is pointless? Please explain bug report system to let me and you to do less pointless work. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396413] New: Add a way to disable SwipeItem actions when editing
https://bugs.kde.org/show_bug.cgi?id=396413 Bug ID: 396413 Summary: Add a way to disable SwipeItem actions when editing Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided (disclaimer: This is a summary of a meeting discussion) When adding an "edit" mode to an item, there is an annoying regression since Kirigami switched from a swipe action to a mouse hover action on the desktop. If you change the swipe item component to add some TextEntry or buttons, they keep moving around when you move the mouse. Some way to tell the swipe delegate to stop doing magic while the item is locked in edit mode is required to fix this UX regression. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396404] Limit the length of appmenu / global menu
https://bugs.kde.org/show_bug.cgi?id=396404 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- >I don't know if there is a mechanism to tell the plasmoids that the panel has >reached the maximun length, Kind of Plasmoids (should) set an implicit size, the panel will resize, then resize the plasmoid. The plasmoid should based contents on the size it is, not the size it wants to be. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396412] New: Improve the new sidebar concept for desktop mode
https://bugs.kde.org/show_bug.cgi?id=396412 Bug ID: 396412 Summary: Improve the new sidebar concept for desktop mode Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided (disclaimer: This is a summary of a meeting discussion) The new sidebar component allows a compact always visible vertical bar. This is perfect to replace Ring-KDE hardcoded sidebar/dock component. One feature I wish to have is the ability to "pin" the expanded sidebar to stay open. The idea to the place the timeline and other "QDockWidget" equivalent. I no not need to have more than 1 visible at once. This would make the UX confusing and it's not necessary. The only change compared to the current state is to have a button to "pin" the expanded drawer to stay open and reserve it's space instead of being an overlay. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396411] New: Make the header more flexible
https://bugs.kde.org/show_bug.cgi?id=396411 Bug ID: 396411 Summary: Make the header more flexible Product: frameworks-kirigami Version: 5.39.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided (disclaimer: This is a summary of a meeting discussion) Ring-KDE currently cannot make use of the Kirigami header in the way our design and workflow wish to use it because of the following limitations: * Not being able to replace the label and background with a custom QML component that contains the contact photo, name and bookmark status * Having a single main action in desktop mode makes little sense and waste space, Ring-KDE has 4 main actions (call, video call, share screen and chat). Each action has an icon and a label. It is wished the action can make a single row when possible, a 2x2 grid when the width doesn't allow it, then 4 iconified icons if it still doesn't fit. Smaller than that triggers the mobile mode. In the mobile mode, Marco proposed to move the 4 actions to the bottom using a standardized Kirigami replacement for the "single round button" currently shown. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 301447] Desktop grid effect changes activities
https://bugs.kde.org/show_bug.cgi?id=301447 --- Comment #12 from Marcin Migacz --- You found it ! That is fantastic :D After living with that bug more than a year is a great information ! :D Can you tell me how i can apply this changes ? I'm on manjaro. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395566] Bad font rendering makes desktop effects kcm unusable when I set 1.2 as display scalling factor
https://bugs.kde.org/show_bug.cgi?id=395566 Nate Graham changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #5 from Nate Graham --- If it's an upstream bug, it's different from the one that I thought it was that was fixed in 5.11. Can you locate the bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395566] Bad font rendering makes desktop effects kcm unusable when I set 1.2 as display scalling factor
https://bugs.kde.org/show_bug.cgi?id=395566 Martin Flöser changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #4 from Martin Flöser --- Nevertheless an upstream bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396338] Desktop locked at 75fps when compositor is enabled
https://bugs.kde.org/show_bug.cgi?id=396338 --- Comment #5 from Rokas Kupstys --- "Show FPS" desktop effect. -- 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 #12 from Martin Flöser --- It changes WM_HINTS property. I need to check, but my feeling is that this is not allowed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396338] Desktop locked at 75fps when compositor is enabled
https://bugs.kde.org/show_bug.cgi?id=396338 --- Comment #4 from Martin Flöser --- >From where do you get the information that it is 75 fps? -- 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 Ralf Habacker changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.8.3 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/ce26e771673a1d4f2a376 ||2499556134396ab9369 --- Comment #1 from Ralf Habacker --- Git commit ce26e771673a1d4f2a3762499556134396ab9369 by Ralf Habacker. Committed on 11/07/2018 at 16:58. Pushed by habacker into branch '4.8'. Fix 'Last digit of date field is obscured by "details column" in ledger view' The setting of the minimum and maximum column header width to the same value has been removed so that the column width can be calculated from the content. FIXED-IN:4.8.3 M +0-3kmymoney/views/kgloballedgerview.cpp https://commits.kde.org/kmymoney/ce26e771673a1d4f2a3762499556134396ab9369 -- 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 Ralf Habacker changed: What|Removed |Added Summary|Last digit obsucred Date|Last digit of date field is |display |obscured by "details ||column" in ledger view -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396405] Last digit obsucred Date display
https://bugs.kde.org/show_bug.cgi?id=396405 Ralf Habacker changed: What|Removed |Added Summary|Date display|Last digit obsucred Date ||display CC||ralf.habac...@freenet.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396395] Task manager window ordering on application restart
https://bugs.kde.org/show_bug.cgi?id=396395 Eike Hein changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eike Hein --- There's no code present to remember or restore any positions. If sorting is set to e.g. alphabetic (the default) it's, well, alphabetic. If it's set to Manual, new windows are appended in the order they are opened. So it's up to the application to reopen its windows in the right order. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 396410] New: notes driving me batty
https://bugs.kde.org/show_bug.cgi?id=396410 Bug ID: 396410 Summary: notes driving me batty Product: knotes Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: don-redhat-...@isis.cs3-inc.com CC: myr...@kde.org Target Milestone: --- I'd be surprised if this is NOT a duplicate but I've searched long and hard. I'm on linux - fedora 24, There are so many different versions of kde things in my yum list installed I don't even know where to start. SOMEHOW I managed to create a very large number of sticky notes - some unintended use of keyboard or mouse or combination. 1. How can I find out how many there are? 2. How can I delete them all at once, not one at a time? 3. How can I kill/disable/remove/eliminate notes from my desktop? 4. I suspect that whatever created the notes also caused my copy/paste to stop working. How can I reset whatever it does that makes copy/paste work? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 395682] Reading debug info of binaries linked with binutils ld -z separate-code
https://bugs.kde.org/show_bug.cgi?id=395682 --- Comment #6 from Mark Wielaard --- (In reply to H.J. Lu from comment #5) > (In reply to Mark Wielaard from comment #4) > > The root cause is that ld -z separate-code introduces various new PT_LOAD > > This is very misleading. I don't know why you say that, or why you removed the rest of the sentence "... and the code in valgrind interpreting the PT_LOAD mappings is very specific about what it does and what it doesn't consider a code or data mapping to match symbols and debuginfo against." The point is simply that if people want to work around it the simplest thing to do for now is to use ld -z no-separate-code, which is what fedora is doing for now till we get valgrind fixed. I didn't say that it is the only way that valgrind might get confused by different PT_LOAD segment setups. In fact if you look at the code pointed out in comment #4 you'll see that there are lots of ways to confuse valgrind. And that the code is horribly architecture and OS specific. It just doesn't work with -z separate-code at the moment. We have to fix that (and hopefully fix other things while we do it). But for now just don't use -z separate-code or build binutils with --disable-separate-code. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 396215] 2.8.0 playlist looses information about tracks on the local filesystem
https://bugs.kde.org/show_bug.cgi?id=396215 --- Comment #3 from Thomas Hejze --- (In reply to Christoph Feck from comment #2) > KDE:Extra repository has Amarok 2.9.0 for openSUSE 42.3 in case you do not > want to update to newer openSUSE version. Please ask for help in a forum of > your distribution how to install software from the KDE:Extra repository. Adding a repository is quit easy. I will give it a try, thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 --- Comment #11 from Camille Bissuel --- OK, it works so well I through your worked in it ! I just warned Peter Hutterer you need help, but I don't know if he can spare time for that, even if I hope so ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 --- Comment #10 from Boudewijn Rempt --- *** Bug 396409 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396409] Rotation support for Wacom Art Pen under Wayland
https://bugs.kde.org/show_bug.cgi?id=396409 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt --- Let's have only one wayland bug to track; not that Krita actually uses libinput at the moment. *** This bug has been marked as a duplicate of bug 379174 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 395682] Reading debug info of binaries linked with binutils ld -z separate-code
https://bugs.kde.org/show_bug.cgi?id=395682 --- Comment #5 from H.J. Lu --- (In reply to Mark Wielaard from comment #4) > The root cause is that ld -z separate-code introduces various new PT_LOAD This is very misleading. This simple test: https://github.com/hjl-tools/simple-linux/tree/divide-by-zero doesn't use -z separate-code: [hjl@gnu-cfl-1 simple-linux]$ readelf -lW test Elf file type is EXEC (Executable file) Entry point 0x40019a There are 3 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align LOAD 0x00 0x0040 0x0040 0x000240 0x000240 R E 0x1000 LOAD 0x001000 0x00401000 0x00401000 0x00 0x00 RW 0x1000 GNU_STACK 0x00 0x 0x 0x00 0x00 RWE 0x10 Section to Segment mapping: Segment Sections... 00 .text .rodata .eh_frame 01 .data .bss 02 [hjl@gnu-cfl-1 simple-linux]$ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 --- Comment #9 from Boudewijn Rempt --- Um... We never did anything related to wayland, at all. We never received any patches from Wayland fans for krita. There has been no code written for wayland support at all. Krita directly links to X11 libraries on Linux, unconditionally, and uses xcb to get tablet events. That means that if you run Krita in a wayland sessions, it uses the X11 compatibility layer, whatever it is called. If that layer doesn't forward rotation events, then there's nothing we can do. We still need a wayland fan to step up and implement tablet support; that code might then be upstreamed to Qt, which doesn't have tablet support under Wayland either. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379174] Wacom Tablet support with Krita on Gnome/Wayland
https://bugs.kde.org/show_bug.cgi?id=379174 --- Comment #8 from Camille Bissuel --- Good news, Krita 4.1 is almost working with Wayland on Ubuntu 18.04. Stylus works, touch gestures are working, I only miss Rotation support for the Wacom Art Pen (see bug 396409). Maybe the borders of drawing strokes are a little too sharp using Wayland. Boud, can you explain us what is the status of Wyaland support in Krita ? Thanks in advance, Camille -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396409] New: Rotation support for Wacom Art Pen under Wayland
https://bugs.kde.org/show_bug.cgi?id=396409 Bug ID: 396409 Summary: Rotation support for Wacom Art Pen under Wayland Product: krita Version: 4.1.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: welc...@nylnook.art Target Milestone: --- Hi dear Krita Team, Good news, Krita 4.1 is almost working with Wayland on Ubuntu 18.04 (See bug 379174) ! Stylus works, touch gestures are working, I only miss Rotation support for the Wacom Art Pen. It seems that Krita is simply not using the corresponding lipinput event (see https://gitlab.freedesktop.org/libinput/libinput/issues/76). So this is an humble request to add it... and finally enjoy drawing and touching my cintiq at the same time ;) Thanks a lot -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396403] okular/KF5 support for 'v4 YCC-RGB' and 'v2 GBR' ICC profiles is broken
https://bugs.kde.org/show_bug.cgi?id=396403 --- Comment #12 from Ralf Habacker --- File a related bug, see https://bugzilla.opensuse.org/show_bug.cgi?id=1100900 -- 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 --- Comment #5 from yaron...@gmail.com --- I've used the "qt5ct" package to set all the configurations I mentioned earlier. Installed it from ppa, but you can also download a deb file. See here: http://www.webupd8.org/2015/11/configure-qt5-application-style-icons.html If I understand correctly it's not really necessary, but it gives some GUI which makes things easier! -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 395119] Open multiple files at once from project view
https://bugs.kde.org/show_bug.cgi?id=395119 --- Comment #2 from Karl Ove Hufthammer --- (In reply to Adrián Chaves (Gallaecio) from comment #1) > What if we simply make Ctrl+click open the clicked file without changing the > focus? It should be easier to implement, and solve the scenario you describe. Yes, I would be happy if this was implemented. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396408] Resets SVG source manual correction
https://bugs.kde.org/show_bug.cgi?id=396408 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396403] okular/KF5 support for 'v4 YCC-RGB' and 'v2 GBR' ICC profiles is broken
https://bugs.kde.org/show_bug.cgi?id=396403 Luigi Toscano changed: What|Removed |Added Resolution|INVALID |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
