[krita] [Bug 409892] Zooming with ctrl+space+drag is not smooth
https://bugs.kde.org/show_bug.cgi?id=409892 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411776] Gaussian Blur Filter Layer Doesn't Wrap Around Canvas like Gaussian Blur Filter Operation
https://bugs.kde.org/show_bug.cgi?id=411776 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 411620] No sound on AirPlay speakers
https://bugs.kde.org/show_bug.cgi?id=411620 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412143] color pick and brush stop working
https://bugs.kde.org/show_bug.cgi?id=412143 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412148] Overlapping character strings and widgets (application titles, global menu) cause lattedock to shrink
https://bugs.kde.org/show_bug.cgi?id=412148 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409931] Acer Switch Alpha 12 Stylus lift-off problem
https://bugs.kde.org/show_bug.cgi?id=409931 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411632] Kwin crashing on switching virtual desktop.
https://bugs.kde.org/show_bug.cgi?id=411632 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408153] Noticable Delay when making selection,before you can clear the contents of the selection
https://bugs.kde.org/show_bug.cgi?id=408153 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392265] Problems with icon on Create Template From Image
https://bugs.kde.org/show_bug.cgi?id=392265 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409318] Multibrush tool needs reselecting after ctrl+z
https://bugs.kde.org/show_bug.cgi?id=409318 --- Comment #13 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410553] İntuos 4 pen doesnt work outside canvas
https://bugs.kde.org/show_bug.cgi?id=410553 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 411957] Dolphin crashes on moving files to shared host folder
https://bugs.kde.org/show_bug.cgi?id=411957 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412655] Tabbox uses wrong visualization when switching between Main and Alternative while holding a common Alt
https://bugs.kde.org/show_bug.cgi?id=412655 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412655] Tabbox uses wrong visualization when switching between Main and Alternative while holding a common Alt
https://bugs.kde.org/show_bug.cgi?id=412655 --- Comment #1 from andydecle...@gmail.com --- Created attachment 123045 --> https://bugs.kde.org/attachment.cgi?id=123045=edit KCM2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412655] New: Tabbox uses wrong visualization when switching between Main and Alternative while holding a common Alt
https://bugs.kde.org/show_bug.cgi?id=412655 Bug ID: 412655 Summary: Tabbox uses wrong visualization when switching between Main and Alternative while holding a common Alt Product: kwin Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: andydecle...@gmail.com Target Milestone: --- Created attachment 123044 --> https://bugs.kde.org/attachment.cgi?id=123044=edit KCM1 SUMMARY I have both Main and Alternative Task Switchers triggered by Alt+, traversing windows differently, and using a different visualization. If I start with one, keep holding Alt, and use the rest of the trigger for the other, then it correctly changes which windows/apps it traverses, but continues to use whichever visualization was initially triggered. STEPS TO REPRODUCE 1. Configure Main Task Switcher to use Large Icons, Alt+Tab for All windows, and Only one window per application 2. Configure Alternative Task Switcher to use Grid, Alt+` for Current application, and deselect Only one window per application 3. Hold Alt, tap Tab, tap `. Alternatively: Hold Alt, tap `, tap Tab. OBSERVED RESULT When the switcher is switched, the visualization is not. EXPECTED RESULT When the switcher is switched, it ought to use its configured visualization. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Attaching screenshots of tabbox KCM settings -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 412360] All items entered are gone
https://bugs.kde.org/show_bug.cgi?id=412360
--- Comment #5 from Dave ---
I have just set up a Computer for my wife and it is Running a PEPPERMINT vers
10 as an OS. I had installed Skrooge on this computer using the Software
Manager and it has loaded Skrooge 2.11.0.It seems to have a few bugs when
running..issues with the Dashboard hi lighting text when the cursor is moved
across the desktop.I had copied the files from my computer running Linux Mint
(Skrooge 2.15.0) onto a memory stick and then tried to open the copied files
onto my wifes computer and l was getting a red hi lighted error message
[err-5] pop up and have not been able to open the file.Dave
On Wednesday, October 2, 2019, 03:13:42 a.m. EDT, Stephane MANKOWSKI
wrote:
https://bugs.kde.org/show_bug.cgi?id=412360
--- Comment #4 from Stephane MANKOWSKI ---
Hi,
${HOME}/.config/skroogerc means for you /home/dave/.config/skroogerc
Your screen capture is the directory where the source code of Skrooge is
stored.
If you build (make) and install (sudo make install) skrooge. This directory is
no more necessary because Skrooge is now installed on your system.
So, now, you just have to launch skrooge and use file/open to open your
document. Skrooge documents can be saved where you want (HD, USB drive, ...).
Regards
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 412638] Inconsistent mechanism to draw annotations
https://bugs.kde.org/show_bug.cgi?id=412638 --- Comment #1 from David Hurka --- How do you imagine "click and hold" for polyline? I think polyline should be "click and click and click and right-click to finisch". (Btw whats polyline? I can find only polygon...) The other annotations (straight line, shape) should allow both "click and click" and "click and drag". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412654] New: Krita is transparent
https://bugs.kde.org/show_bug.cgi?id=412654 Bug ID: 412654 Summary: Krita is transparent Product: krita Version: 4.2.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: eb26mm...@gmail.com Target Milestone: --- Created attachment 123042 --> https://bugs.kde.org/attachment.cgi?id=123042=edit Krita is transparent When I open up krita, it is transparent. If I create a new canvas and draw on it, it shows the desktop background underneath. I tried opening and closing krita several times and it is still transparent. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 195583] FILEIO : read header metadata from JPEG2000 files with Exiv2
https://bugs.kde.org/show_bug.cgi?id=195583 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||6.4.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #17 from caulier.gil...@gmail.com --- Exiv2 support JPEG2000 metadata since a while. I close this file now. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412653] New: Sort Installed apps by name default
https://bugs.kde.org/show_bug.cgi?id=412653 Bug ID: 412653 Summary: Sort Installed apps by name default Product: Discover Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: watisthis...@outlook.com CC: aleix...@kde.org Target Milestone: --- Discover's Installed apps view is sorted by app rating by default (and apparently from lowest to highest?). Sorting by rating is good for recommending the best new apps for a user in the other views; but when it comes to the Installed apps list, I think it would be more helpful to have Installed apps sorted _by name_. (Or if there is some reason for sort-by-rating I can't think of it now. Probably users aren't uninstalling their software just because it has got one star from other people?) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 --- Comment #10 from Michail Vourlakos --- The INSTALLATION.md file is distro/community driven, I don't maintain it, it is maintained only from kde community. Feel free to send any commit for it -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412650] Can't uninstall and reinstall digikam properly on macOS - preferences remain, no first run dialog
https://bugs.kde.org/show_bug.cgi?id=412650 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Setup-FirstRun CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- If you want to reset settings and show first run under MacOS, remove the file from your home directory: ~/Library/Preferences/digikamrc Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 --- Comment #9 from WojtasJD --- Created attachment 123041 --> https://bugs.kde.org/attachment.cgi?id=123041=edit Manjaro KDE neon 18.1.0 - Building "latte-dock" ver. 0.9.85 Manjaro KDE 18.1.0 - here autostart also works fine ;) [Plasma: 5.16.4; Frameworks: 5.61.0; Qt: 5.13.0] Build without problem, only some warnings about deprecated-declarations - file with build output attached. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412623] Layer Hiding is not saved.
https://bugs.kde.org/show_bug.cgi?id=412623 --- Comment #3 from acc4commissi...@gmail.com --- It's just a regression(a huge one) from a user's point of view; -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412623] Layer Hiding is not saved.
https://bugs.kde.org/show_bug.cgi?id=412623 --- Comment #2 from acc4commissi...@gmail.com --- (In reply to Ahab Greybeard from comment #1) > There are some actions that affect the on screen projection but don't mark > the image as being changed. These have been noted in other bug reports but I > can't find them. I remember that Tyson Tan was very keen to have layer > visibility changes saved without the need to make other changes. > > It must be one of the many things that are still being discussed and decided. What is the reason why layer visibility changes should not be saved? I'm confused that it even needs a discussion; -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412652] New: Trying to install a GTK3 theme from a file
https://bugs.kde.org/show_bug.cgi?id=412652 Bug ID: 412652 Summary: Trying to install a GTK3 theme from a file Product: systemsettings Version: 5.12.8 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: arog1...@yahoo.com Target Milestone: --- Application: systemsettings5 (5.12.8) (Compiled from sources) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Trying to install a GTK3 theme - Custom settings of the application: Trying to load the theme from a file the .theme file provided by Juno theme author eliverlara GTK3 Juno Ocean style. https://store.kde.org/p/1280977/ The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f521eb97800 (LWP 7256))] Thread 17 (Thread 0x7f51b60e4700 (LWP 7284)): #0 0x7f52166f59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5635a3037548) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52166f59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5635a30374f8, cond=0x5635a3037520) at pthread_cond_wait.c:502 #2 0x7f52166f59f3 in __pthread_cond_wait (cond=0x5635a3037520, mutex=0x5635a30374f8) at pthread_cond_wait.c:655 #3 0x7f51fae009cb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f51fae005c7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f52166ef6db in start_thread (arg=0x7f51b60e4700) at pthread_create.c:463 #6 0x7f521a5a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f51b77fe700 (LWP 7283)): #0 0x7f52166f59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5635a2cb8648) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52166f59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5635a2cb85f8, cond=0x5635a2cb8620) at pthread_cond_wait.c:502 #2 0x7f52166f59f3 in __pthread_cond_wait (cond=0x5635a2cb8620, mutex=0x5635a2cb85f8) at pthread_cond_wait.c:655 #3 0x7f51fae009cb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f51fae005c7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f52166ef6db in start_thread (arg=0x7f51b77fe700) at pthread_create.c:463 #6 0x7f521a5a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f51b7fff700 (LWP 7275)): #0 0x7f52166f59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5635a2be1c3c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f52166f59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5635a2be1be8, cond=0x5635a2be1c10) at pthread_cond_wait.c:502 #2 0x7f52166f59f3 in __pthread_cond_wait (cond=0x5635a2be1c10, mutex=0x5635a2be1be8) at pthread_cond_wait.c:655 #3 0x7f51fae009cb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f51fae005c7 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f52166ef6db in start_thread (arg=0x7f51b7fff700) at pthread_create.c:463 #6 0x7f521a5a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f51be177700 (LWP 7274)): #0 0x7f521a594bf9 in __GI___poll (fds=0x7f51b8003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f521436c5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f521436c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f521aeeb99b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f521ae909fa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f521acaf23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f52187d06f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f521acb417d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f52166ef6db in start_thread (arg=0x7f51be177700) at pthread_create.c:463 #9 0x7f521a5a188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f51ce127700 (LWP 7272)): #0 0x7f521a5b0e9f in __GI___clock_gettime (clock_id=1, tp=0x7f51ce126af0) at ../sysdeps/unix/clock_gettime.c:115 #1 0x7f521aeeb2b1 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f521aee9ae9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f521aeea0c5 in QTimerInfoList::timerWait(timespec&) () at
[krita] [Bug 412651] File overwrite warning can be skipped
https://bugs.kde.org/show_bug.cgi?id=412651 Tymond changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||tamtamy.tym...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412651] New: File overwrite warning can be skipped
https://bugs.kde.org/show_bug.cgi?id=412651 Bug ID: 412651 Summary: File overwrite warning can be skipped Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY The warning popup when trying to save a document through Save As... or Export... over an identically named file (+ format) in the folder is skipped if the File name input does not explicitly have the file ending written. This seems to only happen if the native file dialog option under Configure Krita > General > Miscellaneous is disabled. STEPS TO REPRODUCE 1. Make sure the native file dialogs option is disabled 2. Open an image file in Krita and save it into a folder 3. Overwrite it through Save As..., leave the file name unchanged but remove the file ending 4. Change the file format from the Type drop-down and try overwriting that file too OBSERVED RESULT The overwrite warning dialog is skipped. EXPECTED RESULT The overwrite warning should appear just like when the file ending is written out. SOFTWARE/OS VERSIONS Tested in master build (git 9b45d78), AppImage (git 511ecc7) and 4.2.7 from repo, all showing the same behavior. KDE Plasma 5.16.5 + Dolphin ADDITIONAL INFORMATION I'm using Plasma and Dolphin, in case that influences the behavior of the native file dialog. Original context is this reddit topic: https://www.reddit.com/r/krita/comments/dcztyv/krita_does_not_inform_me_there_is_another_file/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 --- Comment #8 from WojtasJD --- Created attachment 123040 --> https://bugs.kde.org/attachment.cgi?id=123040=edit KDE neon 5.16.5 - Building "latte-dock" ver. 0.9.85 Of course I can check ;) TL;DR - autostart is working, now file org.kde.latte-dock.desktop is copied to ~/.config/autostart/ Thank you! (Latte is reporting itself ver. 0.9.85). "KDE neon 5.16.5" (two installations with Latte Dock build/configure problems): According to build instruction from https://github.com/KDE/latte-dock/blob/master/INSTALLATION.md I've installed dependencies: sudo apt install cmake extra-cmake-modules qtdeclarative5-dev libqt5x11extras5-dev libkf5iconthemes-dev libkf5plasma-dev libkf5windowsystem-dev libkf5declarative-dev libkf5xmlgui-dev libkf5activities-dev build-essential libxcb-util-dev libkf5wayland-dev git gettext libkf5archive-dev libkf5notifications-dev libxcb-util0-dev libsm-dev libkf5crash-dev libkf5newstuff-dev and: wojtasjd@KDE:~$ git clone https://anongit.kde.org/latte-dock.git Cloning into 'latte-dock'... remote: Counting objects: 33586, done. remote: Compressing objects: 100% (12146/12146), done. remote: Total 33586 (delta 24994), reused 29019 (delta 21205) Receiving objects: 100% (33586/33586), 6.36 MiB | 4.30 MiB/s, done. Resolving deltas: 100% (24994/24994), done. wojtasjd@KDE:~$ cd latte-dock/ wojtasjd@KDE:~/latte-dock$ sh install.sh install.sh: 12: [: unexpected operator install.sh: 12: [: unexpected operator install.sh: 16: [: -a: unexpected operator install.sh: 22: [: -a: unexpected operator install.sh: 25: [: -a: unexpected operator install.sh: 29: [: unexpected operator install.sh: 32: [: unexpected operator -- The C compiler identification is GNU 7.4.0 -- The CXX compiler identification is GNU 7.4.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Could NOT find KF5SysGuard (missing: KF5SysGuard_DIR) -- Could NOT find KF5SysGuard: found neither KF5SysGuardConfig.cmake nor kf5sysguard-config.cmake CMake Error at /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find KF5 (missing: SysGuard) Call Stack (most recent call first): /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /usr/share/ECM/find-modules/FindKF5.cmake:110 (find_package_handle_standard_args) CMakeLists.txt:22 (find_package) -- Configuring incomplete, errors occurred! See also "/home/wojtasjd/latte-dock/build/CMakeFiles/CMakeOutput.log". wojtasjd@KDE:~/latte-dock$ wojtasjd@KDE:~/latte-dock$ sh install.sh install.sh: 12: [: unexpected operator install.sh: 12: [: unexpected operator install.sh: 16: [: -a: unexpected operator mkdir: nie można utworzyć katalogu „build”: Plik istnieje wojtasjd@KDE:~/latte-dock$ wojtasjd@KDE:~/latte-dock$ which sh /bin/sh wojtasjd@KDE:~/latte-dock$ file /bin/sh /bin/sh: symbolic link to dash wojtasjd@KDE:~/latte-dock$ file /bin/dash /bin/dash: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 3.2.0, BuildID[sha1]=a783260e3a5fe0afdae77417eea7fbf8d645219e, stripped wojtasjd@KDE:~/latte-dock$ ./install.sh -- Could NOT find KF5SysGuard (missing: KF5SysGuard_DIR) -- Could NOT find KF5SysGuard: found neither KF5SysGuardConfig.cmake nor kf5sysguard-config.cmake CMake Error at /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find KF5 (missing: SysGuard) Call Stack (most recent call first): /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /usr/share/ECM/find-modules/FindKF5.cmake:110 (find_package_handle_standard_args) CMakeLists.txt:22 (find_package) -- Configuring incomplete, errors occurred! See also "/home/wojtasjd/latte-dock/build/CMakeFiles/CMakeOutput.log". wojtasjd@KDE:~/latte-dock$ So I propose updating build instruction to also add this dependencies: libkf5sysguard-dev , pkg-config Executing "sh install.sh" throw some errors but simply "./install.sh" works fine. Beside "pkg-config" there was some other "Could NOT find" messages - I've attached file with build output. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 408904] ksplashqml crashes display
https://bugs.kde.org/show_bug.cgi?id=408904 --- Comment #6 from rol...@logikalsolutions.com --- Upgrading this machine from nvidia-340 to nvidia-driver-390 seems to have resolved the problem. People trapped at the 340 driver due to newer drivers not supporting older hardware will see this problem. It appears there is an assumption made about what a driver can/does provide and 340 doesn't provide it. I'm guessing this might have to be kicked up to the QT community. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412650] New: Can't uninstall and reinstall digikam properly on macOS - preferences remain, no first run dialog
https://bugs.kde.org/show_bug.cgi?id=412650 Bug ID: 412650 Summary: Can't uninstall and reinstall digikam properly on macOS - preferences remain, no first run dialog Product: digikam Version: 6.3.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: digikam...@iinet.net.au Target Milestone: --- SUMMARY I am using digikam on a Mac with a mysql database on MariaDB on a Synology NAS. I am trying to fully install and reinstall digikam on my MacBook to allow me to change the router IP and some other settings. I tried to fully uninstall digikam by deleting all of the following: \opt\digikam\... \Username\Library\Application Support\digikam\ \Applications\digikam\ I emptied the trash and rebooted. The fresh installation does not show the first run dialog to set up digikam - rather it continues to look for the database in the previous location. It eventually generates an error message that it cannot connect to the database. If you leave it there it hangs. If you click ok, it generates the error message 'Failed to open the database. If you then click ok it shows the splash screen and hangs at 'Checking iCC repository...' I tried to upgrade digikam from 5.9 to 6.3. At the same time I have changed router which has a default different IP range. I will try and alter my router back to the IP range of the other router but I would still like to be able to fully uninstall digikam if possible. After a bad experience with Apple Photos and paying $$ for Adobe Lightroom I love digikam. Thanks for all the hard work everyone. Best Regards M -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412649] New: Discover crash
https://bugs.kde.org/show_bug.cgi?id=412649 Bug ID: 412649 Summary: Discover crash Product: Discover Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: jodr...@live.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.17.80) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.1-1-puya x86_64 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: Invoked krunner to install gparted, as soon i hit "Get Gparted" from the dropdown menu i get the crash window. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f29a63ced80 (LWP 9086))] Thread 4 (Thread 0x7f299e087700 (LWP 9089)): [KCrash Handler] #6 0x7f29a5282a13 in QQmlPropertyCacheCreator::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlCompileError*) const (this=this@entry=0x7f299e085f20, obj=obj@entry=0x7f2994302a68, context=..., error=error@entry=0x7f299e085bb0) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/include/QtQml/5.13.1/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:170 #7 0x7f29a528615a in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&) (this=this@entry=0x7f299e085f20, objectIndex=, context=...) at /usr/include/qt5/QtCore/qarraydata.h:257 #8 0x7f29a5286481 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&) (this=this@entry=0x7f299e085f20, objectIndex=, context=...) at /usr/include/c++/9/bits/atomic_base.h:326 #9 0x7f29a5286481 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&) (this=this@entry=0x7f299e085f20, objectIndex=, context=...) at /usr/include/c++/9/bits/atomic_base.h:326 #10 0x7f29a5286481 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&) (this=this@entry=0x7f299e085f20, objectIndex=, context=...) at /usr/include/c++/9/bits/atomic_base.h:326 #11 0x7f29a5286481 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&) (this=this@entry=0x7f299e085f20, objectIndex=objectIndex@entry=0, context=...) at /usr/include/c++/9/bits/atomic_base.h:326 #12 0x7f29a528121c in QQmlPropertyCacheCreator::buildMetaObjects() (this=0x7f299e085f20) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/include/QtQml/5.13.1/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:143 #13 0x7f29a528121c in QQmlTypeCompiler::compile() (this=this@entry=0x7f299e0860b0) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/src/qml/compiler/qqmltypecompiler.cpp:86 #14 0x7f29a540a46b in QQmlTypeData::compile(QQmlRefPointer const&, QV4::CompiledData::ResolvedTypeReferenceMap*, std::function const&) (this=this@entry=0x7f299415da10, typeNameCache=..., resolvedTypeCache=resolvedTypeCache@entry=0x7f299e086188, dependencyHasher=...) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/src/qml/qml/qqmltypeloader.cpp:2663 #15 0x7f29a5411c61 in QQmlTypeData::done() (this=0x7f299415da10) at /usr/include/c++/9/bits/std_function.h:87 #16 0x7f29a5409a3d in QQmlDataBlob::tryDone() (this=0x7f299415da10) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/src/qml/qml/qqmltypeloader.cpp:675 #17 0x7f29a5409a3d in QQmlDataBlob::tryDone() (this=0x7f299415da10) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/src/qml/qml/qqmltypeloader.cpp:666 #18 0x7f29a540b5cf in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) (this=this@entry=0x557ed3cc9a50, blob=blob@entry=0x7f299415da10, d=...) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/src/qml/qml/qqmltypeloader.cpp:1312 #19 0x7f29a540be99 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) (this=this@entry=0x557ed3cc9a50, blob=0x7f299415da10, fileName=...) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/src/qml/qml/qqmltypeloader.cpp:1292 #20 0x7f29a540bfc9 in QQmlTypeLoader::loadThread(QQmlDataBlob*) (this=this@entry=0x557ed3cc9a50, blob=, blob@entry=0x7f299415da10) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/src/qml/qml/qqmltypeloader.cpp:1162 #21 0x7f29a541990c in PlainLoader::loadThread(QQmlTypeLoader*, QQmlDataBlob*) const (this=0x7f299e0863b7, blob=0x7f299415da10, loader=0x557ed3cc9a50) at /usr/src/debug/libqt5-qtdeclarative-5.13.1-ku.2.4.x86_64/src/qml/qml/qqmltypeloader.cpp:1007 #22
[trojita] [Bug 412648] New: offline storage should show the path and allow the user to change it.
https://bugs.kde.org/show_bug.cgi?id=412648 Bug ID: 412648 Summary: offline storage should show the path and allow the user to change it. Product: trojita Version: 0.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: bjloc...@lockie.ca Target Milestone: --- SUMMARY Offline storage should show the path and allow the user to change it. STEPS TO REPRODUCE 1. Click the menu "IMAP/Setting" and select the "Offline" tab. OBSERVED RESULT It doesn't show the storage location and doesn't allow the user to change it. EXPECTED RESULT Show the storage location and allow the user to change it. I want this because I need to be able to store my email offline on a large mechanical hard drive yet have the application on an SSD. I do this in Thunderbird by editing the config (it also should be doable from the GUI): $ cat ~/.thunderbird/profiles.ini [Profile0] IsRelative=0 Path=/bigHD/Mozilla/Thunderbird SOFTWARE/OS VERSIONS LXQt About Version 0.14.1 LXQt Version 0.14.1 Qt 5.12.2 Build type Release System Configuration /etc/xdg Share Directory /usr/share/lxqt Translations /usr/share/Lubuntu/lxqt/translations /usr/local/share/lxqt/translations /usr/share/lxqt/translations /var/lib/snapd/desktop/lxqt/translations -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389022] Switching between stylus eraser tip and regular tip messes up brush settings of both presets
https://bugs.kde.org/show_bug.cgi?id=389022 Tymond changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412479] "trim leading spaces" eats empty lines
https://bugs.kde.org/show_bug.cgi?id=412479 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon |konsole/commit/67a29e4134ff |sole/67a29e4134ff80cb64291b |80cb64291b84ebeea27a1b247fd |84ebeea27a1b247fd5 |5 | --- Comment #8 from Kurt Hindenburg --- Git commit 67a29e4134ff80cb64291b84ebeea27a1b247fd5 by Kurt Hindenburg, on behalf of Mariusz Glebocki. Committed on 05/10/2019 at 21:09. Pushed by scmsync into branch 'Applications/19.08'. Keep empty lines when "trim leading spaces" is enabled (cherry picked from commit ce2029ed75b624a9f9abb5e27428bcb51ad1e5b5) M +1-1src/Screen.cpp https://commits.kde.org/konsole/67a29e4134ff80cb64291b84ebeea27a1b247fd5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412479] "trim leading spaces" eats empty lines
https://bugs.kde.org/show_bug.cgi?id=412479 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://commits.kde.org/kon |https://invent.kde.org/kde/ |sole/ce2029ed75b624a9f9abb5 |konsole/commit/67a29e4134ff |e27428bcb51ad1e5b5 |80cb64291b84ebeea27a1b247fd ||5 --- Comment #7 from Kurt Hindenburg --- Git commit 67a29e4134ff80cb64291b84ebeea27a1b247fd5 by Kurt Hindenburg, on behalf of Mariusz Glebocki. Committed on 05/10/2019 at 21:09. Pushed by hindenburg into branch 'Applications/19.08'. Keep empty lines when "trim leading spaces" is enabled (cherry picked from commit ce2029ed75b624a9f9abb5e27428bcb51ad1e5b5) M +1-1src/Screen.cpp https://invent.kde.org/kde/konsole/commit/67a29e4134ff80cb64291b84ebeea27a1b247fd5 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 412647] New: main window resets after settings saved
https://bugs.kde.org/show_bug.cgi?id=412647 Bug ID: 412647 Summary: main window resets after settings saved Product: trojita Version: 0.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: bjloc...@lockie.ca Target Milestone: --- STEPS TO REPRODUCE 1. The trojita window opens in the lower left. 2. Move the main window. 3. Open the "IMAP/Settings" menu. 4. Click "Save" OBSERVED RESULT The trojita window is moved back to the lower left. EXPECTED RESULT The trojita window should not move. SOFTWARE/OS VERSIONS LXQt Desktop Toolbox - Technical Info LXQt About Version: 0.14.1 LXQt Version: 0.14.1 Qt: 5.12.2 Build type: Release System Configuration: /etc/xdg Share Directory:/usr/share/lxqt Translations: /usr/share/Lubuntu/lxqt/translations /usr/local/share/lxqt/translations /usr/share/lxqt/translations /var/lib/snapd/desktop/lxqt/translations -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 381547] [New Syntax] Add Syntax Support for Renpy .rpy files
https://bugs.kde.org/show_bug.cgi?id=381547 Jonathan Poelen changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/syn ||tax-highlighting/4e278a1c3e ||47b40847c66b762ac09f613a228 ||b62 Resolution|--- |FIXED --- Comment #2 from Jonathan Poelen --- Git commit 4e278a1c3e47b40847c66b762ac09f613a228b62 by Jonathan Poelen. Committed on 05/10/2019 at 20:56. Pushed by jpoelen into branch 'master'. Add syntax highlighting for RenPy (.rpy) Summary: BUG: 381547 Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, dhaumann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D24326 A +60 -0autotests/folding/highlight.rpy.fold A +67 -0autotests/html/highlight.rpy.html A +60 -0autotests/input/highlight.rpy A +60 -0autotests/reference/highlight.rpy.ref A +667 -0data/syntax/renpy.xml https://commits.kde.org/syntax-highlighting/4e278a1c3e47b40847c66b762ac09f613a228b62 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412479] "trim leading spaces" eats empty lines
https://bugs.kde.org/show_bug.cgi?id=412479 Mariusz Glebocki changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon |konsole/commit/ce2029ed75b6 |sole/ce2029ed75b624a9f9abb5 |24a9f9abb5e27428bcb51ad1e5b |e27428bcb51ad1e5b5 |5 | --- Comment #6 from Mariusz Glebocki --- Git commit ce2029ed75b624a9f9abb5e27428bcb51ad1e5b5 by Mariusz Glebocki. Committed on 05/10/2019 at 17:13. Pushed by scmsync into branch 'master'. Keep empty lines when "trim leading spaces" is enabled M +1-1src/Screen.cpp https://commits.kde.org/konsole/ce2029ed75b624a9f9abb5e27428bcb51ad1e5b5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412479] "trim leading spaces" eats empty lines
https://bugs.kde.org/show_bug.cgi?id=412479 Mariusz Glebocki changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||konsole/commit/ce2029ed75b6 ||24a9f9abb5e27428bcb51ad1e5b ||5 Status|CONFIRMED |RESOLVED --- Comment #5 from Mariusz Glebocki --- Git commit ce2029ed75b624a9f9abb5e27428bcb51ad1e5b5 by Mariusz Glebocki. Committed on 05/10/2019 at 17:13. Pushed by mglebocki into branch 'master'. Keep empty lines when "trim leading spaces" is enabled M +1-1src/Screen.cpp https://invent.kde.org/kde/konsole/commit/ce2029ed75b624a9f9abb5e27428bcb51ad1e5b5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412646] New: StartUp OpenSuse Leap 15.1
https://bugs.kde.org/show_bug.cgi?id=412646 Bug ID: 412646 Summary: StartUp OpenSuse Leap 15.1 Product: plasmashell Version: 5.12.8 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: alex6...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.8) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 4.12.14-lp151.28.16-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: StartUp OpenSuse Leap 15.1 Error: Eseguibile: plasmashell PID: 2138 Segnale: Segmentation fault (11) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff7715ab140 (LWP 2138))] Thread 9 (Thread 0x7ff69d039700 (LWP 2480)): #0 0x7ff76a70819b in poll () at /lib64/libc.so.6 #1 0x7ff764d1c1a9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff764d1c2bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff76b05777b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff76aff7c4a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff76ae1310a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff69f95b807 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7ff76ae148b2 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff769fbf569 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff76a7129ef in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7ff6b3c86700 (LWP 2453)): #0 0x7ff76a70819b in poll () at /lib64/libc.so.6 #1 0x7ff764d1c1a9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff764d1c2bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff76b05777b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff76aff7c4a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff76ae1310a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff76eeff3b6 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7ff76ae148b2 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff769fbf569 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff76a7129ef in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7ff6bfdf5700 (LWP 2428)): #0 0x7ff769fc58ad in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff744b0e92b in () at /usr/lib64/dri/i965_dri.so #2 0x7ff744b0e637 in () at /usr/lib64/dri/i965_dri.so #3 0x7ff769fbf569 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff76a7129ef in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7ff747be0700 (LWP 2406)): #0 0x7ff769fc58ad in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff770e8d784 in () at /usr/lib64/libQt5Script.so.5 #2 0x7ff770e8d7c9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7ff769fbf569 in start_thread () at /lib64/libpthread.so.0 #4 0x7ff76a7129ef in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7ff751b65700 (LWP 2396)): #0 0x7ff76a70819b in poll () at /lib64/libc.so.6 #1 0x7ff764d1c1a9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff764d1c2bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff76b05777b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff76aff7c4a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff76ae1310a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff76ea20995 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7ff76ae148b2 in () at /usr/lib64/libQt5Core.so.5 #8 0x7ff769fbf569 in start_thread () at /lib64/libpthread.so.0 #9 0x7ff76a7129ef in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7ff7533ea700 (LWP 2242)): #0 0x7ff76a703c98 in read () at /lib64/libc.so.6 #1 0x7ff764d60ca0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff764d1bcb8 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff764d1c150 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff764d1c2bc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff76b05777b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff76aff7c4a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7ff76ae1310a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7ff76ea20995 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7ff76ae148b2 in () at /usr/lib64/libQt5Core.so.5 #10 0x7ff769fbf569 in start_thread () at /lib64/libpthread.so.0 #11
[digikam] [Bug 412539] Digikam crash when starting
https://bugs.kde.org/show_bug.cgi?id=412539 --- Comment #5 from garym...@surewest.net --- (In reply to Maik Qualmann from comment #4) > @garymele > It would be nice if you could compile the digiKam git/master version on > FreeBSD and test if the problem is solved. > > Maik Thanks for the update. I don't know how to do this outside of poudriere, so will wait for the update to be added to the FreeBSD ports. Gary -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412565] Mount options
https://bugs.kde.org/show_bug.cgi?id=412565 --- Comment #4 from Recesvintvs --- I'm also afraid I don't know much about BTRFS or any other file system format. I'm just an average user and my technical knowledge is rather basic. The only way I know to verify how a partition has been mounted is simply using the command "mount", and a "mount | grep sdb1" returns: /dev/sdb1 on /run/media/myuser/mountpoint type btrfs (rw,noatime,compress=zstd:3,noacl,space_cache,commit=60,subvolid=5,subvol=/) I don't know if that's the correct way, but in case it is, I think that something is failing because even if mount says that zstd compression is being used, the numbers say the opposite. I can't believe that I get only a testimonial 1% of compression if zstd compression were really working. I'll test by mounting the external disk manually creating a folder and copying some files, and then remounting with Dolphin, repeating the process and looking if it makes any difference. In case it would, I'll report back. In case it would not, I suppose the problem must come from something else and this bug should be closed. Thank you. And if some other people read this and have any suggestion, I'm open to try them to solve the problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic from working
https://bugs.kde.org/show_bug.cgi?id=378523 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=412645 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412645] kcm_fonts shouldn't set the font styleName property in most cases
https://bugs.kde.org/show_bug.cgi?id=412645 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=378523 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412645] kcm_fonts shouldn't set the font styleName property in most cases
https://bugs.kde.org/show_bug.cgi?id=412645 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412645] kcm_fonts shouldn't set the font styleName property in most cases
https://bugs.kde.org/show_bug.cgi?id=412645 Ahmad Samir changed: What|Removed |Added CC||filipfila@gmail.com, ||k...@davidedmundson.co.uk, ||k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic from working
https://bugs.kde.org/show_bug.cgi?id=378523 --- Comment #74 from Ahmad Samir --- Konsole issue was fixed by: https://phabricator.kde.org/R319:41693fe9ee263f8f2281852a740ee52d55f003ef KTextEditor/Kate was fixed by: https://phabricator.kde.org/R39:4d91fa7e918d983e6569798dfe20c7c9faf4bb9e The fonts KCM has been pored to QML and doesn't use KFontRequester, IIUC. I'll Keep this one open for KFontRequester. For the QML fonts KCM, see bug 412645. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412645] New: kcm_fonts shouldn't set the font styleName property in most cases
https://bugs.kde.org/show_bug.cgi?id=412645 Bug ID: 412645 Summary: kcm_fonts shouldn't set the font styleName property in most cases Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: a.samir...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- Due to an upstream issue[1], when setting a font using the fonts_kcm module the QFont styleName property gets set (evident by examining kdeglobals after setting a font, e.g. you will get ',Regular' appended to that font settings entry). The upstream rationale is that this is necessary so that fonts that have weird style names would work, and that if the styleName property is set (with QFont::setStyleName()) it overrides all other font properties. This is problematic for some KDE apps, e.g. Dolphin which uses QFont::setBold() to make a certain part of its UI use the Bold variant of whatever font it's using. The recommended way to "fix" this issue is to use setStyleName() with an empty string before saving/loading the font (with QFont::to/fromString()), see the upstream bug report. Some KDE apps already use that method since they have their own embedded font selection dialogues: Konsole: https://phabricator.kde.org/R319:41693fe9ee263f8f2281852a740ee52d55f003ef KTextEditor: https://phabricator.kde.org/R39:4d91fa7e918d983e6569798dfe20c7c9faf4bb9e See also bug 378523 and https://phabricator.kde.org/D9070 [1] https://bugreports.qt.io/browse/QTBUG-63792 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412644] "Focus Follows Mouse" Option for konsole split-view
https://bugs.kde.org/show_bug.cgi?id=412644 Lukas Sabota changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Lukas Sabota --- just found this dupe; sorry about that! *** This bug has been marked as a duplicate of bug 412523 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412523] Focus follows mouse support in Konsole split view
https://bugs.kde.org/show_bug.cgi?id=412523 Lukas Sabota changed: What|Removed |Added CC||lu...@lwsabota.com --- Comment #1 from Lukas Sabota --- *** Bug 412644 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412644] New: "Focus Follows Mouse" Option for konsole split-view
https://bugs.kde.org/show_bug.cgi?id=412644 Bug ID: 412644 Summary: "Focus Follows Mouse" Option for konsole split-view Product: konsole Version: 19.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: lu...@lwsabota.com Target Milestone: --- SUMMARY Konsole currently uses a click-to-focus model for split panes. It would be fantastic to have a mouse-to-focus option that would fit in with workflows of users using mouse-to-focus in KWin. STEPS TO REPRODUCE 1. Open a Konsole window 2. Split the window with default hotkey Ctrl-( 3. Focus on each pane OBSERVED RESULT You have to click to focus on each pane. Which is fine, but... EXPECTED RESULT It would be fantastic to have an option for mouse-to-focus. ADDITIONAL INFORMATION Thank you for all the hard work on Konsole and KWin. Really enjoying the new split features! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412578] Manual geotagging is difficult and time-consuming
https://bugs.kde.org/show_bug.cgi?id=412578 --- Comment #6 from Maik Qualmann --- If you want to move around the fringes, the Google API will scroll the map, hence the demolition. I have to see if I can prevent it. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412643] New: Intermittent crash when clicking on Clementine icon in taskbar
https://bugs.kde.org/show_bug.cgi?id=412643 Bug ID: 412643 Summary: Intermittent crash when clicking on Clementine icon in taskbar Product: plasmashell Version: 5.16.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: puffpi...@firemail.cc CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Clementine has an icon in the taskbar that allows pause, previous song, next song. Selecting this icon sometimes causes as crash. KDE recovers. Selecting the icon opens a small media player control window, the crash occurs as the media player control window begins to open. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f16638c8500 (LWP 2567))] Thread 10 (Thread 0x7f1641412700 (LWP 2696)): #0 0x7f1667de460c in read () at /lib64/libc.so.6 #1 0x7f166431870f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1664364cbe in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1664366372 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f166436649f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1665a0d99b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f16659b60db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f16657ee021 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f1641c29ca8 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #9 0x7f16657ef1a2 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f1664eaef2a in start_thread () at /lib64/libpthread.so.0 #11 0x7f1667df34af in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f16488a8700 (LWP 2674)): #0 0x7f1667de460c in read () at /lib64/libc.so.6 #1 0x7f166431870f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1664364cbe in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1664366372 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f166436649f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1665a0d99b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f16659b60db in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f16657ee021 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f16674ec0c6 in () at /usr/lib64/libQt5Quick.so.5 #9 0x7f16657ef1a2 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f1664eaef2a in start_thread () at /lib64/libpthread.so.0 #11 0x7f1667df34af in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f164b230700 (LWP 2673)): #0 0x7f1664eb56a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f16597bfb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f16597bfa37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f1664eaef2a in start_thread () at /lib64/libpthread.so.0 #4 0x7f1667df34af in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f164ba31700 (LWP 2665)): #0 0x7f1664eb56a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f16597bfb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f16597bfa37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f1664eaef2a in start_thread () at /lib64/libpthread.so.0 #4 0x7f1667df34af in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f164c232700 (LWP 2664)): #0 0x7f1664eb56a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f16597bfb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f16597bfa37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f1664eaef2a in start_thread () at /lib64/libpthread.so.0 #4 0x7f1667df34af in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1658865700 (LWP 2663)): #0 0x7f1664eb56a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f16597bfb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f16597bfa37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f1664eaef2a in start_thread () at /lib64/libpthread.so.0 #4 0x7f1667df34af in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f16591a7700 (LWP 2662)): #0 0x7f1664eb56a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f16597bfb8b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f16597bfa37 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f1664eaef2a in start_thread () at /lib64/libpthread.so.0 #4 0x7f1667df34af in
[kwin] [Bug 412642] New: kwin closed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=412642 Bug ID: 412642 Summary: kwin closed unexpectedly Product: kwin Version: 5.16.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: 16fr4...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.4) Qt Version: 5.12.2 Frameworks Version: 5.61.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: Ubuntu 19.04 -- Information about the crash: - What I was doing when the application crashed: I was moving between my four virtual desktops too many times to exchange applications, until kwin reported a serious bug and the entire desktop get restarted. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f31a2450880 (LWP 1443))] Thread 8 (Thread 0x7f31993ac700 (LWP 26421)): #0 0x7f31a7e9d3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55b42c326ae0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f31a7e9d3bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b42c326a90, cond=0x55b42c326ab8) at pthread_cond_wait.c:502 #2 0x7f31a7e9d3bb in __pthread_cond_wait (cond=0x55b42c326ab8, mutex=0x55b42c326a90) at pthread_cond_wait.c:655 #3 0x7f31a8cfc733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f31a8cfc819 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f31a79da5d9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f31a79da83a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f31a8cf6612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31a7e97182 in start_thread (arg=) at pthread_create.c:486 #9 0x7f31aa39cb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f319adee700 (LWP 22121)): #0 0x7f31a7e9d3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55b42c0ec814) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f31a7e9d3bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55b42c0ec7c0, cond=0x55b42c0ec7e8) at pthread_cond_wait.c:502 #2 0x7f31a7e9d3bb in __pthread_cond_wait (cond=0x55b42c0ec7e8, mutex=0x55b42c0ec7c0) at pthread_cond_wait.c:655 #3 0x7f31a8cfc733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f31a8cfc819 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f31a79da5d9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f31a79da83a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f31a8cf6612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31a7e97182 in start_thread (arg=) at pthread_create.c:486 #9 0x7f31aa39cb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f31899ba700 (LWP 16235)): #0 0x7f31aa390826 in __GI_ppoll (fds=0x7f3178003058, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f31a8efb041 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f31a8efc4b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f31a8eaa5bb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f31a8cf52c6 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f31a7653ef5 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f31a8cf6612 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f31a7e97182 in start_thread (arg=) at pthread_create.c:486 #8 0x7f31aa39cb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f31891b9700 (LWP 1624)): #0 0x7f31a7e9d3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f31a888cfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f31a7e9d3bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f31a888cf68, cond=0x7f31a888cf90) at pthread_cond_wait.c:502 #2 0x7f31a7e9d3bb in __pthread_cond_wait (cond=0x7f31a888cf90, mutex=0x7f31a888cf68) at pthread_cond_wait.c:655 #3 0x7f31a8796eca in () at /lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f31a8796ee9 in () at /lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f31a7e97182 in start_thread (arg=) at pthread_create.c:486 #6 0x7f31aa39cb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f318b56c700 (LWP 1602)): #0 0x7f31a7e9d3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55b42b857628) at
[partitionmanager] [Bug 412575] enlarging mounted btrfs partition with "Align" option checked leads to full loss of the partition.
https://bugs.kde.org/show_bug.cgi?id=412575 --- Comment #6 from bobafetthotm...@gmail.com --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412641] New: When multiple copies of an app are installed from different sources (e.g. deb,flatpak,snap), only one is shown in menu
https://bugs.kde.org/show_bug.cgi?id=412641 Bug ID: 412641 Summary: When multiple copies of an app are installed from different sources (e.g. deb,flatpak,snap), only one is shown in menu Product: plasmashell Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: watisthis...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 OBSERVED RESULT When I install multiple versions (deb, flatpak or snap) of one same app, only one of them appears in the KDE Application launcher menu. For example, if I install Blender 2.79 from Ubuntu repos and then Blender 2.80 from snap, Application launcher menu will have only link to the deb version in Applications->Graphics. The native Blender's .desktop file is called blender.desktop in /usr/share/applications and snap has blender_blender.desktop in /var/lib/snapd/desktop/applications. Similarly Discord flatpak doesn't appear in Launcher if I have snap version installed. The flatpak has com.discordapp.Discord.desktop file in /var/lib/flatpak/exports/share/applications/ and snap has discord_discord.desktop in /var/lib/snapd/desktop/applications/. If I install first Krita snap and then Krita flatpak, the Krita flatpak will replace the Krita snap Launcher menu entry. Same with GIMP, SuperTuxKart and so on... - I used Discover to install my apps. - .desktop files seem to be in right places and in $XDG_DATA_DIRS. - _Search from Application Launcher or Krunner still finds both app versions_. - If I uninstall one app, the other's icon comes back. - My $XDG_DATA_DIRS is /usr/share//usr/share/xsessions/plasma:/home/ntt/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop EXPECTED RESULT All versions of an app from different sources have their own entries in Application launcher menu. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412479] "trim leading spaces" eats empty lines
https://bugs.kde.org/show_bug.cgi?id=412479 --- Comment #4 from Kurt Hindenburg --- thanks - there should be tests for these so they don't get overlooked - not even sure that's possible ATM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412623] Layer Hiding is not saved.
https://bugs.kde.org/show_bug.cgi?id=412623 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #1 from Ahab Greybeard --- There are some actions that affect the on screen projection but don't mark the image as being changed. These have been noted in other bug reports but I can't find them. I remember that Tyson Tan was very keen to have layer visibility changes saved without the need to make other changes. It must be one of the many things that are still being discussed and decided. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412599] "Render Animation" uses MPEG-4 size limits while in Image Sequence mode
https://bugs.kde.org/show_bug.cgi?id=412599 --- Comment #3 from Ahab Greybeard --- Evidence: https://docs.krita.org/en/reference_manual/render_animation.html?highlight=ffmpeg#setting-up-krita-for-exporting-animations zerano.com (linked to in the manual) is the Windows and macOS builds. You'll need the link I gave you. I suggest you try this to see if it solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412479] "trim leading spaces" eats empty lines
https://bugs.kde.org/show_bug.cgi?id=412479 --- Comment #3 from Mariusz Glebocki --- QChar::isSpace includes new lines at least since Qt4. Fix: https://invent.kde.org/kde/konsole/merge_requests/37 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412640] New: Widget's don't hold after restart
https://bugs.kde.org/show_bug.cgi?id=412640 Bug ID: 412640 Summary: Widget's don't hold after restart Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: chrisac...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Place Widgets 2. Restart System OBSERVED RESULT Widgets become oversized and move EXPECTED RESULT Widgets to remain the same size at the same position SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 5.4.0-rc1-gdcb8cfbd8fe9 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 1600X Six-Core Processor Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION I am using a Dual Monitor Setup with my Primary at 1440P and my secondary at 1080P. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405819] malformed font in notification panel
https://bugs.kde.org/show_bug.cgi?id=405819 Nayr438 changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412639] New: Plasma crashes on login
https://bugs.kde.org/show_bug.cgi?id=412639 Bug ID: 412639 Summary: Plasma crashes on login Product: plasmashell Version: 5.16.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: kde.for...@develdog.com Target Milestone: 1.0 Created attachment 123039 --> https://bugs.kde.org/attachment.cgi?id=123039=edit Crash report SUMMARY Following a system update, now Plasma crashes right after login. The desktop wallpaper shows up then a crash report window pops up. Once the report is filed up and the crash report window closed, there's only a black screen + the mouse cursor visible. You cannot quit, unless you restart the sddm service. Everything's fine if you pick a different desktop manager (in my case XFCE) STEPS TO REPRODUCE 1. Select user on login manager 2. Type password 3. Type enter to login OBSERVED RESULT Black (as in color) screen + visible mouse cursor. The desktop is not loaded, you can move the mouse around but that's it. Same behavior when selecting Plasma with Wayland at the bottom of the Plasma login manager. I also moved the ~/.kde folder (to let Plasma create a new one) and repeated the steps aforementioned with the same results (i.e crash and black screen). EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon User Edition 5.16 (Plasma version 5.16.5) ADDITIONAL INFORMATION Application: Plasma (plasmashell), signal: Segmentation fault (See full crash report in attachment) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412479] "trim leading spaces" eats empty lines
https://bugs.kde.org/show_bug.cgi?id=412479
--- Comment #2 from Kurt Hindenburg ---
I wonder if something in Qt changed since this went in.
This appears to work - we don't want newlines \xa to be counted as spaces.
-if (!QChar(characterBuffer[spacesCount].character).isSpace()) {
+const QChar currentChar = characterBuffer[spacesCount].character;
+if (currentChar == QChar(QLatin1Char('\xa')) ||
!currentChar.isSpace()) {
--
You are receiving this mail because:
You are watching all bug changes.
[ktorrent] [Bug 411172] KTorrent 5.1 reports incorrect agent string to trackers
https://bugs.kde.org/show_bug.cgi?id=411172 dpanter <1lq21dg6y...@opayq.net> changed: What|Removed |Added Summary|KTorrent 5.1.1-1+b1 |KTorrent 5.1 reports |incorrect agent string |incorrect agent string to ||trackers -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 408904] ksplashqml crashes display
https://bugs.kde.org/show_bug.cgi?id=408904 rol...@logikalsolutions.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from rol...@logikalsolutions.com --- This bug is impacting KDE Neon 64-bit as well, at least with respect to today's applied updates. This might have something to do with having nvidia-340 installed. Will test on another KDE Neon machine which has nvidia-340 but not current on updates. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 408904] ksplashqml crashes display
https://bugs.kde.org/show_bug.cgi?id=408904 rol...@logikalsolutions.com changed: What|Removed |Added CC||rol...@logikalsolutions.com --- Comment #4 from rol...@logikalsolutions.com --- Created attachment 123038 --> https://bugs.kde.org/attachment.cgi?id=123038=edit crash reported in KDE Neon This is the crash window shown in KDE Neon -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412599] "Render Animation" uses MPEG-4 size limits while in Image Sequence mode
https://bugs.kde.org/show_bug.cgi?id=412599 --- Comment #2 from caetano --- I'll have to contradict that. I just tested it on a fresh Debian 10 install and the error is still there. I have the ffmpeg that comes pre-installed in Debian (stable 7:4.1.4-1~deb10u1 amd64), however I assume the appimage contains its own dependencies, as that's what they're all about. Furthermore there's no indication on the Krita download page that we should download ffmpeg, whereas there is such an indication for G'MIC (https://krita.org/en/download/krita-desktop/), nor do I see any mention of ffmpeg in the installation documentation: https://docs.krita.org/en/user_manual/getting_started/installation.html?highlight=installation so it seems very unlikely to me that we're supposed to do this additional step. I could be wrong but I'll need some evidence. Did you make sure to select MPEG-4 prior to selecting Image Sequence? Maybe your specific image dimensions somehow bypassed this bug. I got the error on a 21960x3720 as well as on a 11000x200 image. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412637] application panel resets upon restarting KDE
https://bugs.kde.org/show_bug.cgi?id=412637 --- Comment #1 from James Th --- Created attachment 123037 --> https://bugs.kde.org/attachment.cgi?id=123037=edit journalctl-widget-reset-issue.txt i have tried the following, and the issue still occurs: 1) ctlr+Alt+F1, then ctrl+alt+f7 issue still remains. 2) created a new test user, and issue remians (journalctl -b attached for that user) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363878] option to make icons bigger
https://bugs.kde.org/show_bug.cgi?id=363878 Jack Lilhammers changed: What|Removed |Added CC||jack.lilhamm...@gmail.com --- Comment #8 from Jack Lilhammers --- While I don't think that this is technically a bug, it sure is a missing feature! I really prefer the icons only task manager over the other alternatives, but the icons are small and crammed together with no way to configure the appearence. Icons scaling and spacing have to be hardcoded somewhere in source. Sometime ago I skimmed through the code and didn't find 'em, but I can do it again. I'd appreciate if someone could point me in the right direction -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412638] New: Inconsistent mechanism to draw annotations
https://bugs.kde.org/show_bug.cgi?id=412638 Bug ID: 412638 Summary: Inconsistent mechanism to draw annotations Product: okular Version: 1.8.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: simg...@gmail.com Target Milestone: --- SUMMARY To start drawing a straight line or polyline annotation the user have to: - click a point - release the left mouse button - drag the pointer To start drawing a geometrical annotation (rectangle, ellipse) the user have to: - click a point - hold down the left mouse button - drag the pointer I think that the behaviour should be changed to "click and hold" for straight line and poly line. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel Version: 4.19.69-1-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412638] Inconsistent mechanism to draw annotations
https://bugs.kde.org/show_bug.cgi?id=412638 Simone Gaiarin changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406698] Transform Tool has SDR preview on HDR image
https://bugs.kde.org/show_bug.cgi?id=406698 --- Comment #7 from Tymond --- (In reply to Sree from comment #6) > Glad to see color picker problem mentioned here. But I'm confused. > If I draw a very bright white and use color picker(color selector) tool to > pick it, it picks a very dim white. Is this what you are mentioning here? No. Color picker is something different from color selector: color picker is the pipette tool, color selector is the color wheel. It picks the right color, it just draws it wrong in the on-canvas little popup boxes. And it will nearly always be much brighter than the picked color, especially light colors like light grey or white. This bug report is also only related to HDR displays. Your issue is most probably related to misconfiguration of color management, to get help please go to the official Krita forum: https://forum.kde.org/viewforum.php?f=136 or on reddit: https://reddit.com/r/krita . Most probable fix: Configure Krita -> Advanced Color Selector -> make sure "Color selector uses a different color space than image" is *unchecked*. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412637] New: application panel resets upon restarting KDE
https://bugs.kde.org/show_bug.cgi?id=412637 Bug ID: 412637 Summary: application panel resets upon restarting KDE Product: kde Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ja...@thornber.io Target Milestone: --- SUMMARY I currently have the application bar at the top of my screen, and I have various widgets e.g. system panel, time, search etc which I manually located to the top right of my screen. My application launcher is located at the top left of my screen. However, When I reboot my laptop, all widgets end up on the left side of the screen, so I need to manually move them back. STEPS TO REPRODUCE 1. move your application bar to the top of the screen, and move widgets manually to the right side of the screen. 2. restart your laptop/PC OBSERVED RESULT system tray, search, calendar etc move to the left of my screen next to my application launcher. EXPECTED RESULT Remain on the top right of my screen upon reboot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE TW (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 149902] Clicking "Input Actions" from settings:/Accessibility/ bring up "Open with..."
https://bugs.kde.org/show_bug.cgi?id=149902 Filipus Klutiero changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Filipus Klutiero --- I'm afraid this issue still exists in the form described in comment #2, as of KDE Frameworks 5.56.0. settings:/application-appearance-and-behavior/shortcuts-and-gestures/khotkeys is now settings:/workspace/shortcuts/khotkeys I suggest lowering the ticket's importance though. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406764] Add tag support to layers
https://bugs.kde.org/show_bug.cgi?id=406764 --- Comment #6 from Larpon --- Well, maybe the IDs are good enough - but I'm looking for way to identify layers between file loads. Are the layer IDs unique across reloads? -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 412636] New: gtk-font-name with localized name saved in literal bytes.
https://bugs.kde.org/show_bug.cgi?id=412636 Bug ID: 412636 Summary: gtk-font-name with localized name saved in literal bytes. Product: kde-gtk-config Version: 5.12.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: manutort...@chakra-project.org Reporter: iclement...@outlook.com CC: aleix...@kde.org Target Milestone: --- Created attachment 123036 --> https://bugs.kde.org/attachment.cgi?id=123036=edit The saved gtk3 config file SUMMARY Kde-gtk-config does not handle fonts with localized name or localized style. It saves the config it ~/.config/gtk-3.0/settings.ini. Though the file is a utf-8 encoded text file, it seems like the writer just treat the font name & style as bytes, and literally saves the representation of bytes as strings. For example, I used a font whose style in in Chinese, "常规"(Regular) is saved in the file as "\xe5\xb8\xb8\xe8\xa7\x84". Following python3 terminology, b"\xe5\xb8\xb8\xe8\xa7\x84" is a bytes when "常规" is encoded with UTF-8, but the config writer somehow directly casts the byte representation "\xe5\xb8\xb8\xe8\xa7\x84" as string in the config file. Which cause GTK3 programs not to recognize the font settings. By the way, on openSUSE 42.3 with KDE 5.8.7, it correctly saves the font style as "常规" in the config file. for example, Typora which uses GTK theme settings. (Typora:8195): Gtk-WARNING **: Error setting gtk-font-name in /home/username/.config/gtk-3.0/settings.ini: Key file contains key “gtk-font-name” which has a value that cannot be interpreted. STEPS TO REPRODUCE 1. OS being OpenSUSE 15.1 or other distro using KDE 5.12.8. 2. Set the GTK font with kde-gtk-config to a font with localized font name or font style. 3. Check the gtk3 config file in ~/.config/gtk-3.0/settings.ini. OBSERVED RESULT The localized font name or style is saved in literal representation of bytes. EXPECTED RESULT The font name and style are identical to what you see in the kde-gtk-config setting page. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.12.8 (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/a69f3013d83dd95e87b |te-dock/e04c57f4031dadb67bb |6864e543fd5222823e0f9 |087446818df66baac32f3 --- Comment #7 from Michail Vourlakos --- is it possible to check that this commit fixes the issue? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/e04c57f4031dadb67bb |te-dock/a69f3013d83dd95e87b |087446818df66baac32f3 |6864e543fd5222823e0f9 --- Comment #6 from Michail Vourlakos --- Git commit a69f3013d83dd95e87b6864e543fd5222823e0f9 by Michail Vourlakos. Committed on 05/10/2019 at 14:43. Pushed by mvourlakos into branch 'master'. search for Latte desktop file in more generic way --there are distros that do not return /usr/share/applications as their first global path for desktop files. It is better to not just search for the "applications" path but rather the desktop file also to make sure that we use the first one found. FIXED-IN:0.9.4 M +1-1app/settings/universalsettings.cpp https://commits.kde.org/latte-dock/a69f3013d83dd95e87b6864e543fd5222823e0f9 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split
https://bugs.kde.org/show_bug.cgi?id=412429 --- Comment #11 from sergesar...@gmail.com --- Thank's Ralf for help. I have modified the file test case. In my case, I don't see the splited transactions with tag in tag view. Is't the same for you. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lat ||te-dock/e04c57f4031dadb67bb ||087446818df66baac32f3 Version Fixed In||0.9.4 Status|REPORTED|RESOLVED --- Comment #5 from Michail Vourlakos --- Git commit e04c57f4031dadb67bb087446818df66baac32f3 by Michail Vourlakos. Committed on 05/10/2019 at 14:39. Pushed by mvourlakos into branch 'v0.9'. search for Latte desktop file in more generic way --there are distros that do not return /usr/share/applications as their first global path for desktop files. It is better to not just search for the "applications" path but rather the desktop file also to make sure that we use the first one found. FIXED-IN:0.9.4 M +1-1app/settings/universalsettings.cpp https://commits.kde.org/latte-dock/e04c57f4031dadb67bb087446818df66baac32f3 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 --- Comment #4 from Michail Vourlakos --- (In reply to WojtasJD from comment #3) > Thanks for reply. > > It's weird - I've installed another fresh KDE neon 5.16.5 + Latte 0.9.3 and > here autostart option is working fine. > I've installed also Kubuntu 19.04 (Plasma: 5.15.4, Frameworks: 5.56.0, Qt: > 5.12.2) + Latte 0.8.8 and here autostart option is also working fine! > > But in other three installations [fresh KDE neon 5.16.5 + Latte 0.9.3 > (virtual machine) ; another KDE neon 5.16.5 + Latte 0.9.3 (bare metal) ; > Manjaro 18.1.0 + Latte 0.9.1 (virtual machine): > - org.kde.latte-dock.desktop file doesn't appear in ~/.config/autostart/ if > I click autostart option (+ Apply) > - there is a file /usr/share/applications/org.kde.latte-dock.desktop (both > "KDE neon" and "Manjaro KDE") > - I did small experiment with steps as follows: > 1. I've manually copied file > /usr/share/applications/org.kde.latte-dock.desktop -> ~/.config/autostart/ > > 2. After launching Latte, in settings autostart option is marked > 3. Rebooted system, Latte Dock is auto-starting > 4. In settings I've unchecked autostart option (+ Apply) and then > ~/.config/autostart/org.kde.latte-dock.desktop file was deleted (as expected) > 5. Marked autostart option (+ Apply) and then in folder > ~/.config/autostart/ file was NOT created > > Additional steps on this machines doesn't help: > - latte-dock uninstall > - delete file: ~/.config/lattedockrc > - delete folder: ~/.config/latte > - delete folder: ~/.cache/lattedock > - latte-dock new install can you test a commit when I uploaded it ? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split
https://bugs.kde.org/show_bug.cgi?id=412429 --- Comment #10 from sergesar...@gmail.com --- Created attachment 123035 --> https://bugs.kde.org/attachment.cgi?id=123035=edit Test case modified -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 --- Comment #3 from WojtasJD --- Thanks for reply. It's weird - I've installed another fresh KDE neon 5.16.5 + Latte 0.9.3 and here autostart option is working fine. I've installed also Kubuntu 19.04 (Plasma: 5.15.4, Frameworks: 5.56.0, Qt: 5.12.2) + Latte 0.8.8 and here autostart option is also working fine! But in other three installations [fresh KDE neon 5.16.5 + Latte 0.9.3 (virtual machine) ; another KDE neon 5.16.5 + Latte 0.9.3 (bare metal) ; Manjaro 18.1.0 + Latte 0.9.1 (virtual machine): - org.kde.latte-dock.desktop file doesn't appear in ~/.config/autostart/ if I click autostart option (+ Apply) - there is a file /usr/share/applications/org.kde.latte-dock.desktop (both "KDE neon" and "Manjaro KDE") - I did small experiment with steps as follows: 1. I've manually copied file /usr/share/applications/org.kde.latte-dock.desktop -> ~/.config/autostart/ 2. After launching Latte, in settings autostart option is marked 3. Rebooted system, Latte Dock is auto-starting 4. In settings I've unchecked autostart option (+ Apply) and then ~/.config/autostart/org.kde.latte-dock.desktop file was deleted (as expected) 5. Marked autostart option (+ Apply) and then in folder ~/.config/autostart/ file was NOT created Additional steps on this machines doesn't help: - latte-dock uninstall - delete file: ~/.config/lattedockrc - delete folder: ~/.config/latte - delete folder: ~/.cache/lattedock - latte-dock new install -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412553] Steam is placed in "Games > Toys" category
https://bugs.kde.org/show_bug.cgi?id=412553 Luigi Toscano changed: What|Removed |Added Resolution|FIXED |DOWNSTREAM --- Comment #9 from Luigi Toscano --- Changing to DOWNSTREAM, as the original issue still originates from a downstream patch (the commit above should have had a CCBUG, not a BUG header). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406403] Tags within Split transaction not reporting correctly
https://bugs.kde.org/show_bug.cgi?id=406403 Ralf Habacker changed: What|Removed |Added Status|REPORTED|CONFIRMED Depends on||412429 Ever confirmed|0 |1 CC||ralf.habac...@freenet.de --- Comment #2 from Ralf Habacker --- The reason for this bug is the same as with bug 412429 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=412429 [Bug 412429] No display of transactions in the tags view when tags are specified in a split -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split
https://bugs.kde.org/show_bug.cgi?id=412429 Ralf Habacker changed: What|Removed |Added Blocks||406403 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=406403 [Bug 406403] Tags within Split transaction not reporting correctly -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377309] When using double-click mode, systemsettings inappropriately uses the same behavior in icon view
https://bugs.kde.org/show_bug.cgi?id=377309 --- Comment #20 from David Edmundson --- I will still be against it on account of if you've set your settings to make a grid view activate on double click, then having a grid view activate on double click is not a bug. Also if you were to patch it...don't do that. Just change the relvant handler from activated to clicked. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404527] When excluding a tag from a report the information reported is incorrect
https://bugs.kde.org/show_bug.cgi?id=404527 Ralf Habacker changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split
https://bugs.kde.org/show_bug.cgi?id=412429 Ralf Habacker changed: What|Removed |Added Blocks||404527 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=404527 [Bug 404527] When excluding a tag from a report the information reported is incorrect -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404527] When excluding a tag from a report the information reported is incorrect
https://bugs.kde.org/show_bug.cgi?id=404527 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de Depends on||412429 --- Comment #1 from Ralf Habacker --- The reason for this bug is similar to bug 412429: MyMoneyTransactionFilter::match() does exclude tags from categories Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=412429 [Bug 412429] No display of transactions in the tags view when tags are specified in a split -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 341569] Ledger: inconsistent order of detail lines
https://bugs.kde.org/show_bug.cgi?id=341569 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED CC||ralf.habac...@freenet.de Status|REPORTED|RESOLVED Version Fixed In||4.8.0 --- Comment #1 from Ralf Habacker --- Since 4.8 there is no memo field for ordering, so I assume this bug is fixed. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 --- Comment #37 from Carlos --- Created attachment 123034 --> https://bugs.kde.org/attachment.cgi?id=123034=edit New crash information added by DrKonqi plasmashell (5.16.5) using Qt 5.12.3 - What I was doing when the application crashed: Usually after printing Plasma would crash but restarting from terminal using killall plasmashell followed by kstart plasmashell would work, now it just keeps on crashing, so it becomes unusable. - Unusual behavior I noticed: Whenever printing succeeded, plasma would crash but resume. If printing failed and job stayed in printing queue, plasma would crash and never resume. Manual restart of plasma would be necessary. This is no longer working. -- Backtrace (Reduced): #6 0x7f6ae18e9c80 in JobModel::updateJob(int, KCupsJob const&) () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f6ae18ebe68 in JobModel::insertJob(int, KCupsJob const&) () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #8 0x7f6ae18ec46b in JobModel::getJobFinished(KCupsRequest*) () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #9 0x7f6b32e203e2 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6b3474d65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]
https://bugs.kde.org/show_bug.cgi?id=326289 Carlos changed: What|Removed |Added CC||cromua...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398982] Opening Balances in forecast are wrong
https://bugs.kde.org/show_bug.cgi?id=398982 Stefan Vater changed: What|Removed |Added Attachment #122984|0 |1 is obsolete|| --- Comment #7 from Stefan Vater --- Created attachment 123033 --> https://bugs.kde.org/attachment.cgi?id=123033=edit a new version of the patch No, I did not know about "make test" and how to use it. So now I changed my patch in that it only changes sign of liabilities for the forecast. This does not break the testcase. I have the impression that there is something funny going on with the liabilities in the forecast, but at least my patch seems to work. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 145295] Support PDF as image format
https://bugs.kde.org/show_bug.cgi?id=145295 caulier.gil...@gmail.com changed: What|Removed |Added Component|Setup-Views |FilesIO-Engine -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 393408] Support for extra image formats as HEIC, FLIF, JPEG-XR, WEBP [patch]
https://bugs.kde.org/show_bug.cgi?id=393408 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Support for extra image |Support for extra image |formats as HEIC, FITS, |formats as HEIC, FLIF, |JPEG-XR [patch] |JPEG-XR, WEBP [patch] -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412635] color select tool shortcut on brush tool does not respect 'sample current layer' setting in tool options
https://bugs.kde.org/show_bug.cgi?id=412635 wolthera changed: What|Removed |Added Status|REPORTED|RESOLVED CC||griffinval...@gmail.com Resolution|--- |NOT A BUG --- Comment #1 from wolthera --- No, this is because that(sample from layer/sample from full image) can be set as a seperate shortcut in settings->configure Krita->canvas input settings under 'alternate invocation'. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412634] New: Kwin crashes when I minimize the window and immediately move to another virtual desktop
https://bugs.kde.org/show_bug.cgi?id=412634 Bug ID: 412634 Summary: Kwin crashes when I minimize the window and immediately move to another virtual desktop Product: kwin Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: od...@tutanota.com Target Milestone: --- Application: kwin_x11 (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 4.19.76-1-lts x86_64 Distribution: "Arch Linux" -- Information about the crash: I have "Magic Lamp" and "Slide" Desktop Effects enalbed. When I minimize the window, the animation begins, I immediately move to another virtual desktop, and Kwin crashes. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa7a917b880 (LWP 953))] Thread 15 (Thread 0x7fa7a28cf700 (LWP 14557)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa7afdb6660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa7afdb6752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa7aea46dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa7aea4705e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa7afdb05b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fa785725700 (LWP 14556)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa792eba62c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa792eba228 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fa784d24700 (LWP 1190)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa7af837edc in () at /usr/lib/libQt5Script.so.5 #2 0x7fa7af837ef9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fa785f26700 (LWP 1045)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa792eba62c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa792eba228 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fa786927700 (LWP 1043)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa792eba62c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa792eba228 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fa787128700 (LWP 1042)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa792eba62c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa792eba228 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fa787929700 (LWP 1041)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa792eba62c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa792eba228 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fa790b3a700 (LWP 1040)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa792eba62c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa792eba228 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fa79133b700 (LWP 1039)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa792eba62c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fa792eba228 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fa7aef2157f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa7b14a40e3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fa791b3c700 (LWP 1038)): #0 0x7fa7aef27415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1
