[krita] [Bug 412393] Scale Image dialogue pops up on the wrong screen when crop/transform was used before
https://bugs.kde.org/show_bug.cgi?id=412393 --- Comment #11 from Tyson Tan --- I tested this on Manjaro Gnome 18.1.0 LiveUSB, Krita 4.2.7beta1.appimage. It doesn't happen there. So I think this is a Manjaro KDE + Appimage specific issue. Do you have some suggestions that if I want to get to the bottom of this, where should I look at? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412393] Scale Image dialogue pops up on the wrong screen when crop/transform was used before
https://bugs.kde.org/show_bug.cgi?id=412393 --- Comment #10 from Tyson Tan --- Here are my test results: 1) krita-4.3.0-prealpha-0d8465d-x86_64.appimage doesn't fix the issue. 2) It has nothing to do with physical display order. The dialogue always pops up on the top-left corner of the upper screen. 3) I tried to create window rules in Kwin, forcing it to position inside the main window, but to no effect. 4) The issue doesn't happen to Krita 4.2.6 under 10 1903. Maybe it is a Manjaro KDE vs. appimage specific issue. I will get a Gnome LiveUSB later today to confirm that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 --- Comment #5 from Sergey --- > the SQLite databases should reside on a fast local drive. How can I specify a new database location before (!) Launching the program? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 --- Comment #4 from Sergey --- > You have no write permission to the database file. I did on the server: nas4free: Album# ls -l digikam4.db -rwxrw-r-- 1 lary admin 42672128 Sep 11 21:24 digikam4.db nas4free: Album# chmod 0666 digikam4.db nas4free: Album# chown lary:users digikam4.db And: nas4free: Album# chmod 0666 thumbnails-digikam.db nas4free: Album# chmod 0666 recognition.db nas4free: Album# chmod 0666 Thumbs.db nas4free: Album# chown lary:users thumbnails-digikam.db recognition.db Thumbs.db Digikam program behavior has changed, but it still did not work: digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV9ToV10" ] Statement [ "DROP TABLE IF EXISTS ImageHaarMatrix;" ] digikam.coredb: Core database: schema update to V 10 failed! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411432] Every time I try adding and editing text, the whole program freezes and crashes.
https://bugs.kde.org/show_bug.cgi?id=411432 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |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.
[kpat] [Bug 411691] Only happens in Opensuse 15.1 in most games the cards will only autodrop a few, and then it stops., often crashes when Yukon is selected
https://bugs.kde.org/show_bug.cgi?id=411691 --- 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 411906] Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 --- Comment #5 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.
[krename] [Bug 402678] crash opening more than one folder
https://bugs.kde.org/show_bug.cgi?id=402678 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.
[dolphin] [Bug 412396] Information Panel shows wrong amount of items
https://bugs.kde.org/show_bug.cgi?id=412396 --- Comment #5 from Christoph Feck --- I would say this is intended, or do we want users to always toggle hidden files to check before they are going to delete a folder they think is empty? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411260] "f=mkv" or "f=matroska" produces MP4 file output
https://bugs.kde.org/show_bug.cgi?id=411260 --- Comment #9 from Jonathan Gilbert --- MLT master now has a fix for this issue, so as long as it has another release before the next Kdenlive release, and Kdenlive updates to take that release, this bug should be resolved. :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #110 from Guilherme Almeida --- This problem doesn't happen here. It has never happen, by the way. Operating System: Arch Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 5.3.1-arch1-1-ARCH OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz GPU: NVIDIA GeForce MX150 Memory: 7,7 GiB NVIDIA driver: nvidia-dkms 435.21-7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #109 from Darin Miller --- This is still broken on Eoan (which has 5.12.4) when the NVidia driver is enabled. Thus, I recommend changing status to reopened. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-13-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412333] Cursor disappears after selecting color in another image.
https://bugs.kde.org/show_bug.cgi?id=412333 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #7 from vanyossi --- I can reproduce this in the following condition and steps: Window mode: tabs - With two images open: - Change focus from canvas to any other docker, (example, Change brush opacity) - Now, do not make cursor enter the canvas area and change active image by selecting another tab. - Enter canvas and there will be no cursor. This does not happen in subwindow mode. Tested on macOS Qt 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412430] Lag using the brushes
https://bugs.kde.org/show_bug.cgi?id=412430 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from vanyossi --- does this problem goes away if you use a previous version of krita like 4.2.5 or 4.1.7? Also check https://docs.krita.org/en/contributors_manual/user_support.html#quick-solutions for some ideas on what to try. Also check in preferences > display, that the Canvas acceleration is set to "ANGLE" and not OpenGL as this later one might cause problems. And please if nothing helps reply with the contents of "Help > Show information for bug reports". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412432] Krita crash when setting dx scale to negative value in particle brush preset
https://bugs.kde.org/show_bug.cgi?id=412432 vanyossi changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412432] Krita crash when setting dx scale to negative value in particle brush preset
https://bugs.kde.org/show_bug.cgi?id=412432 vanyossi changed: What|Removed |Added Component|Dockers |Brush engines OS|MS Windows |All Platform|MS Windows |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412432] Krita crash when setting dx scale to negative value in particle brush preset
https://bugs.kde.org/show_bug.cgi?id=412432 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #1 from vanyossi --- Created attachment 122929 --> https://bugs.kde.org/attachment.cgi?id=122929=edit crash backtrace Crash easily reproduced. Setting to confirmed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412432] New: Krita crash when setting dx scale to negative value in particle brush preset
https://bugs.kde.org/show_bug.cgi?id=412432 Bug ID: 412432 Summary: Krita crash when setting dx scale to negative value in particle brush preset Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: nikola.knezevic@gmail.com Target Milestone: --- Created attachment 122928 --> https://bugs.kde.org/attachment.cgi?id=122928=edit settings from step 3 STEPS TO REPRODUCE 1. open Edit brush settings docker 2. create particle brush 3. in Brush Size adjustments drag slider of dx scale to negative values OBSERVED RESULT slider accepts new value but Krita crash. SOFTWARE/OS VERSIONS Windows: 10 64 pro Krita: 4.3.0-prealpha (git a94d1a8) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412431] New: Lock screen background changes to and keeps YouTube video thumbnails watched on a computer running KDE Plasma phone is connected to.
https://bugs.kde.org/show_bug.cgi?id=412431 Bug ID: 412431 Summary: Lock screen background changes to and keeps YouTube video thumbnails watched on a computer running KDE Plasma phone is connected to. Product: kdeconnect Version: unspecified Platform: Android OS: Android 8.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: suu...@gmail.com Target Milestone: --- SUMMARY Lock screen background changes to and keeps YouTube video thumbnails watched on a computer running KDE Plasma phone is connected to. STEPS TO REPRODUCE Watch a YouTube video in Firefox with Plasma Integration extension while phone is connected to computer running KDE Plasma via KDE Connect. OBSERVED RESULT Phone's lock screen background is changed to and stuck with a YouTube thumbnail of the video being watched on Firefox with Plasma Integration extension despite no longer being watched. KDE Connect app shows that no media was playing when YouTube video is no longer being played. EXPECTED RESULT Phone should change back to the normal background used for the lock screen when done watching a YouTube video. SOFTWARE/OS VERSIONS Android: 8.0.0 Phone: LG G6 Plus Kernel: 3.18.71 KDE Connect App: 1.13.2 ADDITIONAL INFORMATION Phone is not rooted. KDE Connect app is downloaded from Google Play. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 --- Comment #43 from Jacob --- (In reply to funkybomber from comment #41) > Thanks for the submission @Andrii Arendariuk, this is a simple, elegant > solution. Kudos! > > I took the liberty to run a couple more tests with your code in terminal, > and realised how easy it is to actually use your code to create multiple > backup files, in order to preserve icon positions per resolution (if that's > what we want - and we should). > For example, I used this command when I was in 1920x1080: > cp -f ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/plasma1920x1080.bak > > Then I changed resolution to 800x600, and I rearranged some of the desktop > icons to new places so that I would feel more comfortable while working in > this resolution. > Then I used this command (while still in 800x600) to preserve the icon > positions for this state as well: > cp -f ~/.config/plasma-org.kde.plasma.desktop-appletsrc ~/plasma800x600.bak > > Then I changed resolution back to 1920x1080 and run the command: > konsole -e killall plasmashell && cp -f ~/plasma1920x1080.bak > ~/.config/plasma-org.kde.plasma.desktop-appletsrc && plasmashell & > > which sure enough restored all my icons in the appropriate places. > > Just for the heck of it, I also run the command: > konsole -e killall plasmashell && cp -f ~/plasma800x600.bak > ~/.config/plasma-org.kde.plasma.desktop-appletsrc && plasmashell & > > which just placed the icons in the "800x600" pattern while I was still in > the 1920x1080 resolution. But that was just me playing at this point. > > The only thing remaining is someone with programming experience to make the > script run automatically when there is a resolution change. > To function properly this script should get as parameters both the "old" and > "new" resolution and then call "backup" for the "old" resolution and > "restore" (if a relevant file for this resolution exists) for the "new" > resolution. > > Obviously I'm biased because I desperately want to see a resolution to this > issue, but let's discuss: > > What are the downsides to this solution exactly? I spent several hours trying to make the resolution change idea work only to eventually give up (at least for now). What I tested out was to simply detect a "resolution change" from within a .sh script. This can actually be done. However, the problem is that when a program or game changes the resolution (temporarily?), it does not seem to actually change the desktop resolution, even though it seems that way visually. I tested this with Diablo 2 in Wine. While the game is running, the reported resolution, when requested from a .sh script, will be unchanged. Hence, we can not easily detect this. However, we could probably parse the configuration file and do a simple search and replace whenever it is corrupted. I also tried simply comparing the md5sums of the configuration and backup files, but this does not work very well at all. It seems like other things also change the configuration file, and those changes will be overwritten every time we restore from a backup automatically. Hence, a search and replace is probably best. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412430] New: Lag using the brushes
https://bugs.kde.org/show_bug.cgi?id=412430 Bug ID: 412430 Summary: Lag using the brushes Product: krita Version: 4.2.6 Platform: Other OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: taty...@hotmail.com Target Milestone: --- SUMMARY Either with mouse or my huion tablet, when I updated krita suddenly there's this slow response to my movements on the canvas. My lines appear much later, if they appear eventually. It seems like krita is about to crash or something like that. I make some lines, cursor is just standing there. I move the mouse away from the krita to mozilla or any other program, and suddenly they appear. (I have two monitors) STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 331448] Extreme lag when using a Wacom tablet on Windows
https://bugs.kde.org/show_bug.cgi?id=331448 Taty changed: What|Removed |Added CC||taty...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #18 from Kai Krakow --- (In reply to Martin Steigerwald from comment #16) > I bet I can just compile baloo via kdesrc. Does it have many dependencies on > KF libraries? I do not like to break my system at this point in time and it > has been a long time I last used kdesrc. I have no idea. I'm on Gentoo and just did "git format-patch origin/master", then symlinked my baloo Git src to /etc/portage/patches/kde-frameworks/baloo. So at least in Gentoo, that's a single package. Here's the deps from Gentoo: DEPEND=" $(add_frameworks_dep kconfig) $(add_frameworks_dep kcoreaddons) $(add_frameworks_dep kcrash) $(add_frameworks_dep kdbusaddons) $(add_frameworks_dep kfilemetadata) $(add_frameworks_dep ki18n) $(add_frameworks_dep kidletime) $(add_frameworks_dep kio) $(add_frameworks_dep solid) $(add_qt_dep qtdbus) $(add_qt_dep qtdeclarative) $(add_qt_dep qtgui) $(add_qt_dep qtwidgets) >=dev-db/lmdb-0.9.17 " I could attach my binary package if you want to try (it's basically a tar.gz, you could extract just the binaries and libs). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #17 from Kai Krakow --- (In reply to Martin Steigerwald from comment #15) > Kai, thank you very much for your work on this! About an alternative to > LMDB… I am not sure at the moment. Will think about it. Currently with my patches it seems mostly fine with LMDB. The next days of usage will draw a better picture. I think baloo needs to handle LMDB just a little bit more optimized, i.e. does it use batched writes? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #16 from Martin Steigerwald --- I bet I can just compile baloo via kdesrc. Does it have many dependencies on KF libraries? I do not like to break my system at this point in time and it has been a long time I last used kdesrc. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #15 from Martin Steigerwald --- Kai, thank you very much for your work on this! About an alternative to LMDB… I am not sure at the moment. Will think about it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #14 from Kai Krakow --- Meanwhile, my patched indexer started content indexing phase. I also added back all the expensive directories I excluded previously. It's currently indexing with a mixed R/W workload of up to 200 MB/s (most time 50-100 MB/s) without much of an impact on desktop performance. Looks good so far. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392341] Zooming not possible in neovim when guicursor enabled
https://bugs.kde.org/show_bug.cgi?id=392341 sedrubal changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||k...@sedrubal.de --- Comment #2 from sedrubal --- I'm not able to reproduce it neither any more. -- 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 #1 from Stephane MANKOWSKI ---
The skrooge configuration is stored in the file ${HOME}/.config/skroogerc.
Did you change or remove this file ?
--
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 Stephane MANKOWSKI changed: What|Removed |Added Assignee|guillaume.deb...@gmail.com |steph...@mankowski.fr --- Comment #2 from Stephane MANKOWSKI --- Are you able to load your document? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 412409] Crash when scrolling photos
https://bugs.kde.org/show_bug.cgi?id=412409 --- Comment #2 from Joan --- I could get another crash after scrolling around the pictures, this is what was printed on the console (I couldn't get the crash file this time tough: -- $ ~/.local/bin/kphotoalbum kphotoalbum.ImageManager: "Unable to convert string \"\"to double (for file /media/aseques/TOSHIBA_FOTOS/$RECYCLE.BIN/S-1-5-21-3952020594-3068430305-2178502575-1001/$IKRH22R.MOV)" kphotoalbum.ImageManager: "Unable to convert string \"\"to double (for file /media/aseques/TOSHIBA_FOTOS/$RECYCLE.BIN/S-1-5-21-3952020594-3068430305-2178502575-1001/$IID61AG.MOV)" QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image Aborting aboutToFinish handling. QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 33252, resource id: 37752474, major code: 40 (TranslateCoords), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 35004, resource id: 37752697, major code: 40 (TranslateCoords), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36901, resource id: 37752948, major code: 40 (TranslateCoords), minor code: 0 QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image QImage::scaled: Image is a null image
[kmymoney] [Bug 412429] New: étiquettes placées dans une ventilation ne sont pas détectées
https://bugs.kde.org/show_bug.cgi?id=412429 Bug ID: 412429 Summary: étiquettes placées dans une ventilation ne sont pas détectées Product: kmymoney Version: 5.0.6 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bugtracker Assignee: kmymoney-de...@kde.org Reporter: sergesar...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. ventiler une dépense par exemple 2. sur une ligne ventilée choisir une étiquette (exemple : "frais"), valider et saisir 3. quand je sélectionne l'onglet étiquettes et que je choisis l'étiquette "frais", la dépense n'apparait pas OBSERVED RESULT Il manque des dépenses avec l'étiquette "frais" lorsque cette étiquette est à l'intérieur d'une ventilation EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/Manjaro: KDE Frameworks 5.61.0 Qt 5.13.0 (construit sur 5.13.0) Le système de fenêtres xcb ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412333] Cursor disappears after selecting color in another image.
https://bugs.kde.org/show_bug.cgi?id=412333 --- Comment #6 from Ahab Greybeard --- With Windows 10 (same machine), I get the same result as with Debian 10 MATE. With colour selection from the palette docker, I lose the brush outline but not the cursor, which I normally have as crosshairs. With the Ctrl picker, there is no loss. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #13 from Kai Krakow --- I've added some patches to my experimental patchset after crunching through some of the documentation and articles available. The system responsiveness has improved a lot. Can anyone confirm that these patches help? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #12 from Kai Krakow --- Created attachment 122927 --> https://bugs.kde.org/attachment.cgi?id=122927=edit Don't fsync the file-system Let's not stress the system with fsync() after each DB transaction. This database can be easily rebuild in case it crashes. This patch removes latency spikes and input lag from the desktop environment while the indexer is running. It also seems to increase general indexing throughput while lowering the performance impact. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #11 from Kai Krakow --- Created attachment 122926 --> https://bugs.kde.org/attachment.cgi?id=122926=edit Disable read-ahead of mmap access We should not read-ahead when accessing the database because it may introduce thrashing during low-mem situation because read-aheads would start dominating the cache. This also takes some pressure away from the file-system. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #10 from Kai Krakow --- Created attachment 122925 --> https://bugs.kde.org/attachment.cgi?id=122925=edit Prepare simpler coding of environment flags This simply prepares the following patches and introduces no functional change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412428] Automatic "Allow Applications to Block Compositing" seems to not be working
https://bugs.kde.org/show_bug.cgi?id=412428 Vlad Zahorodnii changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Vlad Zahorodnii --- *** This bug has been marked as a duplicate of bug 412353 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412353] Support for _NET_WM_BYPASS_COMPOSITOR broken
https://bugs.kde.org/show_bug.cgi?id=412353 Vlad Zahorodnii changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #2 from Vlad Zahorodnii --- *** Bug 412428 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Vlad Zahorodnii changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #108 from Vlad Zahorodnii --- > Qt Version: 5.12.3 You need at least 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412428] New: Automatic "Allow Applications to Block Compositing" seems to not be working
https://bugs.kde.org/show_bug.cgi?id=412428 Bug ID: 412428 Summary: Automatic "Allow Applications to Block Compositing" seems to not be working Product: kwin Version: 5.16.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jchevar...@gmail.com Target Milestone: --- I noticed after upgrading to 5.16.90 that automatic suspension of compositing doesn't appear to be working for me anymore. I was going back to some more freesync testing, and noticed it wasn't turning on in any game. This included native games (Talos, SS3, etc), Feral Ports, and Proton games. I know at least the native/Feral games used to send the flag to turn it off automatically, which I thought was actually done at the SDL level. I have the settings "Allow Applications to Block Compositing" ticked off in System Settings. I am not sure when this actually broke (or if it is supposed to still work). Steps to reproduce: 1. Open Steam 2. Launch any game in full screen 3. Notice that compositing isn't disabled (and things like Freesync are blocked) Reproducible: Always for me. Work around: 1) Press "shift" + "alt" + "f12" 2) Compositor turns off, things like Freesync immediately start working. Operating System: Arch Linux (kde-unstable enabled, testing disabled) KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 5.3.1-arch1-1-ARCH OS Type: 64-bit Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.6 GiB of RAM GPU: NVIDIA GTX 1070 Driver: 435.21 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 412427] New: USB Audio Source Disappearing
https://bugs.kde.org/show_bug.cgi?id=412427 Bug ID: 412427 Summary: USB Audio Source Disappearing Product: plasma-pa Version: 5.16.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: jchevar...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- I have noticed after upgrading to 5.16.90, that my USB audio interface (Focusrite 2i2) seems to disappear from the Devices list - normally after sleep/resume. I have to unplug its USB cable and plug it back in to get things working again. The most strange part is that I still get (very muted) sound from my speakers even though the device is not present. I hadn't seen this before in 5.16.X and before. System: Operating System: Arch Linux (kde-unstable enabled, testing disabled) KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 5.3.1-arch1-1-ARCH OS Type: 64-bit Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #10 from Joe --- Can also confirm that this happens in Firefox and other GTK places on Arch's kde-unstable packages for me, too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412426] New: Plasma session dies on laptop screen disabled.
https://bugs.kde.org/show_bug.cgi?id=412426 Bug ID: 412426 Summary: Plasma session dies on laptop screen disabled. Product: plasmashell Version: 5.16.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: koali...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I recently upgraded to the version specified in the ticket, since then, my current setup that worked in 5.15.5 no longer works. It's a laptop connected to an external screen over usb-c. STEPS TO REPRODUCE 1. Open a plasma session, both displays will start opened(no matter if lid is open or not) 2. Open and close the lid. 1. Open a plasma session. 2. System settings -> displays 3. Click the laptop screen. 4. Click enabled to disable it. OBSERVED RESULT Crash and reopening of sddm. EXPECTED RESULT Laptop screen get disabled, showing only one screen in the virtual desktop preview, and opening all windows in the only usable screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo/plasma 5.16.5 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.60 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412425] UI "breaks" / scales after opening any dialog
https://bugs.kde.org/show_bug.cgi?id=412425 --- Comment #1 from sven.pfeif...@gmail.com --- Created attachment 122923 --> https://bugs.kde.org/attachment.cgi?id=122923=edit Screenshot after opening the application, everything is peachy -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412425] UI "breaks" / scales after opening any dialog
https://bugs.kde.org/show_bug.cgi?id=412425 --- Comment #2 from sven.pfeif...@gmail.com --- Created attachment 122924 --> https://bugs.kde.org/attachment.cgi?id=122924=edit Screenshot after closing the dialog, UI remains "scaled" and practically unusable -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412425] New: UI "breaks" / scales after opening any dialog
https://bugs.kde.org/show_bug.cgi?id=412425 Bug ID: 412425 Summary: UI "breaks" / scales after opening any dialog Product: digikam Version: 6.3.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: major Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: sven.pfeif...@gmail.com Target Milestone: --- Created attachment 122922 --> https://bugs.kde.org/attachment.cgi?id=122922=edit Screenshot after opening the preferences dialog, UI in background is scaled SUMMARY After opening any dialog on MacOS, the UI seems to switch to a scaled mode, so only a small part of the application is visible on the screen (see attached screenshot, which shows the full screen width of my display). This only occurs when opening a dialog, otherwise the UI is looking normal STEPS TO REPRODUCE 1. Open Digikam 6.3.0 on MacOS Mojave (10.14.5) 2. Open any dialog (e.g. Preferences) OBSERVED RESULT In the background the UI seems to be scaled up and stays that way when closing the dialog EXPECTED RESULT The UI doesn't change it's scale / resolution SOFTWARE/OS VERSIONS macOS: Mojave (10.14.5) KDE Frameworks Version: 5.59.0 Qt Version: Qt 5.11.3 (built against 5.11.3) ADDITIONAL INFORMATION I attached 3 screenshots showing the full screen of my MacBook Pro. first one is directly after opening the application second one is with the "Preferences" dialog opened third one after closing the dialog -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412420] New whitespace caused by invisible toolbar
https://bugs.kde.org/show_bug.cgi?id=412420 Dominik Haumann changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Dominik Haumann --- Yes, it's the External Tools toolbar. A bit inconvenient, since I was hoping that empty toolbars are invisible, which is not the case. We need to find another way to show external tools in the toolbar. Maybe by merging into the main toolbar... -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412415] Vertical unaligned filter lines in pages
https://bugs.kde.org/show_bug.cgi?id=412415 Ralf Habacker changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/3584d1f97bd0971186241 ||447c9a221ce8293acab Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||4.8.5 --- Comment #6 from Ralf Habacker --- Git commit 3584d1f97bd0971186241447c9a221ce8293acab by Ralf Habacker. Committed on 28/09/2019 at 19:28. Pushed by habacker into branch '4.8'. Move filter line to top of institutions view FIXED-IN:4.8.5 M +31 -31 kmymoney/views/kinstitutionsviewdecl.ui https://commits.kde.org/kmymoney/3584d1f97bd0971186241447c9a221ce8293acab -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412415] Vertical unaligned filter lines in pages
https://bugs.kde.org/show_bug.cgi?id=412415 --- Comment #7 from Ralf Habacker --- Git commit 8804a5ed77b57caea793c95b2df19ace6bf77cd5 by Ralf Habacker. Committed on 28/09/2019 at 19:28. Pushed by habacker into branch '4.8'. Disable search line, collapse and expand button in symbol view of account page It does not support filtering and expanding/collapsing. M +7-0kmymoney/views/kaccountsview.cpp https://commits.kde.org/kmymoney/8804a5ed77b57caea793c95b2df19ace6bf77cd5 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412415] Vertical unaligned filter lines in pages
https://bugs.kde.org/show_bug.cgi?id=412415 --- Comment #4 from Ralf Habacker --- Git commit b6f6f418669b8416ce64712bac437d2903d9f4a4 by Ralf Habacker. Committed on 28/09/2019 at 19:28. Pushed by habacker into branch '4.8'. Move filter line to top of accounts view M +31 -31 kmymoney/views/kaccountsviewdecl.ui https://commits.kde.org/kmymoney/b6f6f418669b8416ce64712bac437d2903d9f4a4 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412415] Vertical unaligned filter lines in pages
https://bugs.kde.org/show_bug.cgi?id=412415 --- Comment #5 from Ralf Habacker --- Git commit 6a7bbfb776c097bee7f7c9f2f729fbc78459e69a by Ralf Habacker. Committed on 28/09/2019 at 19:28. Pushed by habacker into branch '4.8'. Move filter line to top of category view M +3-3kmymoney/views/kcategoriesviewdecl.ui https://commits.kde.org/kmymoney/6a7bbfb776c097bee7f7c9f2f729fbc78459e69a -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410994] Losing transactions after 8000+ DB to KmyFile
https://bugs.kde.org/show_bug.cgi?id=410994 Ralf Habacker changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/781c18c3356d043da2503 ||9d50b41a658de95cac2 Version Fixed In||4.8.5 --- Comment #24 from Ralf Habacker --- Git commit 781c18c3356d043da25039d50b41a658de95cac2 by Ralf Habacker. Committed on 26/09/2019 at 18:54. Pushed by habacker into branch '4.8'. Fix fetchTransactions for sql databases Base implementation by Thomas Baumgart, adapted to 4.8 branch by Ralf Habacker. Implementation verified with mymoneydatabasemgrtest. FIXED-IN:4.8.5 M +15 -0kmymoney/mymoney/storage/mymoneydbdef.h M +101 -77 kmymoney/mymoney/storage/mymoneystoragesql.cpp https://commits.kde.org/kmymoney/781c18c3356d043da25039d50b41a658de95cac2 --- Comment #23 from Ralf Habacker --- Git commit fa7a2616c7903f6f7fddd0700e1d390945b1a521 by Ralf Habacker. Committed on 26/09/2019 at 18:54. Pushed by habacker into branch '4.8'. Fix sql statement case M +15 -15 kmymoney/mymoney/storage/mymoneystoragesql.cpp https://commits.kde.org/kmymoney/fa7a2616c7903f6f7fddd0700e1d390945b1a521 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 410994] Losing transactions after 8000+ DB to KmyFile
https://bugs.kde.org/show_bug.cgi?id=410994 --- Comment #23 from Ralf Habacker --- Git commit fa7a2616c7903f6f7fddd0700e1d390945b1a521 by Ralf Habacker. Committed on 26/09/2019 at 18:54. Pushed by habacker into branch '4.8'. Fix sql statement case M +15 -15 kmymoney/mymoney/storage/mymoneystoragesql.cpp https://commits.kde.org/kmymoney/fa7a2616c7903f6f7fddd0700e1d390945b1a521 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412286] Occational short slowdown/freeze while painting
https://bugs.kde.org/show_bug.cgi?id=412286 --- Comment #8 from acc4commissi...@gmail.com --- (In reply to Dmitry Kazakov from comment #6) > 2) Do you have View->Instant Preview enabled? Does disabling it help? Oh, I've misread the question. Sorry. :/ Instant Preview is disabled. It doesn't make any difference. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397758] Assert replying for an encapsulated message
https://bugs.kde.org/show_bug.cgi?id=397758 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from gjditchfi...@acm.org --- I can't reproduce this, neither with an older KMail 5.7.3, nor with current git master which identifies itself as 5.12.40 alpha. Can you still reproduce this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412333] Cursor disappears after selecting color in another image.
https://bugs.kde.org/show_bug.cgi?id=412333 --- Comment #5 from Frans Slothouber --- Same happens under Windows 10 on a different laptop but identical hardware This is on Lenovo Thinkpad E560. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410723] Freehand annotation jagged lines with stylus
https://bugs.kde.org/show_bug.cgi?id=410723 --- Comment #14 from independent-squirrel --- Additionally, I couldn't reproduce the problem in a Ubuntu 18.04 VM with nether the apt version 1.3.3 nor the snap version 1.7.2... this is however most likely due to the way the input is passed along; xinput does not show the pen -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412333] Cursor disappears after selecting color in another image.
https://bugs.kde.org/show_bug.cgi?id=412333 --- Comment #4 from Frans Slothouber --- Also see it under the default Ubuntu desktop (Non wayland version) And when I log in as a different user under the default Ubuntu desktop but with Wayland. Also have an identical laptop with Windows 10 on it. Will see what happens there. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 412424] Delete my account
https://bugs.kde.org/show_bug.cgi?id=412424 Tom Albers changed: What|Removed |Added CC||t...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Tom Albers --- Will do. Thanks for your contributions. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 412424] New: Delete my account
https://bugs.kde.org/show_bug.cgi?id=412424 Bug ID: 412424 Summary: Delete my account Product: bugs.kde.org Version: unspecified Platform: Other OS: unspecified Status: REPORTED Severity: critical Priority: NOR Component: database Assignee: sysad...@kde.org Reporter: tob...@freiwuppertal.de CC: she...@kde.org Target Milestone: --- Please - replace the e-mail address associated with this account by "exam...@example.com" or similar, - replace the password by a random string of characters neither you nor me save, - if possible, deactivate the account so that login is no longer possible even with the correct password. - delete this bug when done Thank you very much in advance! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407083] Multiple video import jobs running at once on a HDD - hurting performance
https://bugs.kde.org/show_bug.cgi?id=407083 --- Comment #1 from b3_1...@yahoo.co.uk --- This still hasn't been changed in Kdenlive 19.08. It still imports all the video files at once, which leads to a much slower import. It's also time-consuming to import them by hand one-by-one. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 364654] Tabs aren't aligned to right in RTL layouts
https://bugs.kde.org/show_bug.cgi?id=364654 Dominik Haumann changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Version Fixed In||19.08.2 Latest Commit||https://invent.kde.org/kde/ ||kate/commit/77f8b4530c8d095 ||89651d1225f364899cc40f923 --- Comment #4 from Dominik Haumann --- Fixed with 19.08.2 release. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412423] Rendering crashes for projects which import other kdenlive projects
https://bugs.kde.org/show_bug.cgi?id=412423 --- Comment #3 from b3_1...@yahoo.co.uk --- The same exporting as WebM, after deleting .config/kdenliverc: Rendering of ... crashed [matroska,webm @ 0x7f2b5eecad80] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f2b5ef26300] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f2b5f08fe40] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f2b5f0a7880] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [webm @ 0x7f2b5c200f00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [webm @ 0x7f2b5c200f00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [ogg @ 0x7f2ac9422b40] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac94dbc40] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac94dbc40] PES packet size mismatch [mpegts @ 0x7f2ac94dbc40] PES packet size mismatch [mpegts @ 0x7f2ac94dbc40] PES packet size mismatch [mpegts @ 0x7f2ac94dbc40] PES packet size mismatch [mpegts @ 0x7f2ac94dbc40] PES packet size mismatch [mpegts @ 0x7f2ac94dbc40] PES packet size mismatch [mpegts @ 0x7f2ac94dbc40] PES packet size mismatch [mpegts @ 0x7f2ac944a5c0] PES packet size mismatch [mpegts @ 0x7f2ac952c340] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac952c340] PES packet size mismatch [mpegts @ 0x7f2ac95aa400] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac95aa400] PES packet size mismatch [mpegts @ 0x7f2ac95aa400] PES packet size mismatch [mpegts @ 0x7f2ac95aa400] PES packet size mismatch [mpegts @ 0x7f2ac95aa400] PES packet size mismatch [mpegts @ 0x7f2ac95aa400] PES packet size mismatch [mpegts @ 0x7f2ac95aa400] PES packet size mismatch [mpegts @ 0x7f2ac95aa400] PES packet size mismatch [mpegts @ 0x7f2ac95b2000] PES packet size mismatch [mpegts @ 0x7f2ac95b0980] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac95b0980] PES packet size mismatch [matroska,webm @ 0x7f2ac9e5f340] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f2ac9d44c00] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f2aca7799c0] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f2aca77ea40] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [ogg @ 0x7f2ac119cc40] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac11a7880] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac11a7880] PES packet size mismatch [mpegts @ 0x7f2ac11a7880] PES packet size mismatch [mpegts @ 0x7f2ac11a7880] PES packet size mismatch [mpegts @ 0x7f2ac11a7880] PES packet size mismatch [mpegts @ 0x7f2ac11a7880] PES packet size mismatch [mpegts @ 0x7f2ac11a7880] PES packet size mismatch [mpegts @ 0x7f2ac11a7880] PES packet size mismatch [mpegts @ 0x7f2ac121de80] PES packet size mismatch [mpegts @ 0x7f2ac121c980] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac121c980] PES packet size mismatch [mpegts @ 0x7f2ac27a77c0] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac27a77c0] PES packet size mismatch [mpegts @ 0x7f2ac27a77c0] PES packet size mismatch [mpegts @ 0x7f2ac27a77c0] PES packet size mismatch [mpegts @ 0x7f2ac27a77c0] PES packet size mismatch [mpegts @ 0x7f2ac27a77c0] PES packet size mismatch [mpegts @ 0x7f2ac27a77c0] PES packet size mismatch [mpegts @ 0x7f2ac27a77c0] PES packet size mismatch [mpegts @ 0x7f2ac27e5540] PES packet size mismatch [mpegts @ 0x7f2ac27fc940] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f2ac27fc940] PES packet size mismatch [mpegts @ 0x7f2ac95b2000] PES packet size mismatch [mpegts @ 0x7f2ac95b2000] PES packet size mismatch [mpegts @ 0x7f2ac95b2000] PES packet size mismatch [mpegts @ 0x7f2ac95b2000] PES packet size mismatch [mpegts @ 0x7f2ac95b2000] PES packet size mismatch [mpegts @ 0x7f2ac95b2000] PES packet size mismatch [h264 @ 0x7f2ac95cf640] QP 53 out of range [h264 @ 0x7f2ac95cf640] decode_slice_header error [h264 @ 0x7f2ac95cf640] no frame! [h264 @ 0x7f2ac9df3fc0] QP 54 out of range [h264 @ 0x7f2ac9df3fc0] decode_slice_header error [h264 @ 0x7f2ac9df3fc0] no frame! [h264 @ 0x7f2ac9e75540] QP 54 out of range [h264 @ 0x7f2ac9e75540] decode_slice_header error [h264 @ 0x7f2ac9e75540] no frame! [h264 @ 0x7f2acaa587c0] QP 54 out of range [h264 @ 0x7f2acaa587c0] decode_slice_header error [h264 @ 0x7f2acaa587c0] no frame! [h264 @ 0x7f2ac960fa40] QP 54 out of range [h264 @ 0x7f2ac960fa40] decode_slice_header error [h264 @ 0x7f2ac960fa40] no frame! [h264 @ 0x7f2ac961d7c0] QP 54 out of range [h264 @ 0x7f2ac961d7c0] decode_slice_header error [h264 @ 0x7f2ac961d7c0] no frame! [h264 @ 0x7f2ac9ca4d40] top
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Leo changed: What|Removed |Added CC||bloody.f...@gmail.com --- Comment #107 from Leo --- I have exactly the same problem. This happens every time I move a window from one monitor to another by dragging it to the top of the desktop so that the window becomes the maximum size. NVidia driver: 435.21 Prime Profile: NVidia Operating System: KDE neon User Edition 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-29-generic OS Type: 64-bit Processors: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz Memory: 7,9GG -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412423] Rendering crashes for projects which import other kdenlive projects
https://bugs.kde.org/show_bug.cgi?id=412423 --- Comment #2 from b3_1...@yahoo.co.uk --- The same happens with Kdenlive 19.08.1 AppImage: Rendering of crashed [mp4 @ 0x7ff3d0200f00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 0x7ff3d0200f00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mpegts @ 0x7ff3449ed9c0] PES packet size mismatch [mpegts @ 0x7ff3449ed9c0] PES packet size mismatch [mpegts @ 0x7ff3449ed9c0] PES packet size mismatch [mpegts @ 0x7ff3449ed9c0] PES packet size mismatch [mpegts @ 0x7ff3449ed9c0] PES packet size mismatch [mpegts @ 0x7ff3449ed9c0] PES packet size mismatch [mpegts @ 0x7ff3449ed9c0] PES packet size mismatch [mpegts @ 0x7ff3449ad280] PES packet size mismatch [mpegts @ 0x7ff3449f5ac0] PES packet size mismatch [mpegts @ 0x7ff34419f980] PES packet size mismatch [mpegts @ 0x7ff34419f980] PES packet size mismatch [mpegts @ 0x7ff34419f980] PES packet size mismatch [mpegts @ 0x7ff34419f980] PES packet size mismatch [mpegts @ 0x7ff34419f980] PES packet size mismatch [mpegts @ 0x7ff34419f980] PES packet size mismatch [mpegts @ 0x7ff34419f980] PES packet size mismatch [mpegts @ 0x7ff3441a6040] PES packet size mismatch [mpegts @ 0x7ff3441c4a40] PES packet size mismatch [mpegts @ 0x7ff32eee6700] PES packet size mismatch [mpegts @ 0x7ff32eee6700] PES packet size mismatch [mpegts @ 0x7ff32eee6700] PES packet size mismatch [mpegts @ 0x7ff32eee6700] PES packet size mismatch [mpegts @ 0x7ff32eee6700] PES packet size mismatch [mpegts @ 0x7ff32eee6700] PES packet size mismatch [mpegts @ 0x7ff32eee6700] PES packet size mismatch [mpegts @ 0x7ff32ef2bac0] PES packet size mismatch [mpegts @ 0x7ff32ef59c80] PES packet size mismatch [mpegts @ 0x7ff32f0ac8c0] PES packet size mismatch [mpegts @ 0x7ff32f0ac8c0] PES packet size mismatch [mpegts @ 0x7ff32f0ac8c0] PES packet size mismatch [mpegts @ 0x7ff32f0ac8c0] PES packet size mismatch [mpegts @ 0x7ff32f0ac8c0] PES packet size mismatch [mpegts @ 0x7ff32f0ac8c0] PES packet size mismatch [mpegts @ 0x7ff32f0ac8c0] PES packet size mismatch [mpegts @ 0x7ff32f0b30c0] PES packet size mismatch [mpegts @ 0x7ff32f0eed40] PES packet size mismatch [mpegts @ 0x7ff3441a6040] PES packet size mismatch [mpegts @ 0x7ff3441a6040] PES packet size mismatch [mpegts @ 0x7ff3441a6040] PES packet size mismatch [mpegts @ 0x7ff3441a6040] PES packet size mismatch [mpegts @ 0x7ff3441a6040] PES packet size mismatch [mpegts @ 0x7ff3441a6040] PES packet size mismatch [h264 @ 0x7ff3441c67c0] QP 53 out of range [h264 @ 0x7ff3441c67c0] decode_slice_header error [h264 @ 0x7ff3441c67c0] no frame! [h264 @ 0x7ff32c837640] QP 54 out of range [h264 @ 0x7ff32c837640] decode_slice_header error [h264 @ 0x7ff32c837640] no frame! [h264 @ 0x7ff347a02bc0] QP 54 out of range [h264 @ 0x7ff347a02bc0] decode_slice_header error [h264 @ 0x7ff347a02bc0] no frame! [h264 @ 0x7ff32c7f5400] QP 54 out of range [h264 @ 0x7ff32c7f5400] decode_slice_header error [h264 @ 0x7ff32c7f5400] no frame! [h264 @ 0x7ff347a33d40] QP 54 out of range [h264 @ 0x7ff347a33d40] decode_slice_header error [h264 @ 0x7ff347a33d40] no frame! [h264 @ 0x7ff347a505c0] QP 54 out of range [h264 @ 0x7ff347a505c0] decode_slice_header error [h264 @ 0x7ff347a505c0] no frame! [h264 @ 0x7ff3441fa840] top block unavailable for requested intra mode [h264 @ 0x7ff3441fa840] error while decoding MB 22 0, bytestream 221113 [h264 @ 0x7ff32c811c40] top block unavailable for requested intra mode [h264 @ 0x7ff32c811c40] error while decoding MB 97 0, bytestream 211488 [mpegts @ 0x7ff3d0f43880] PES packet size mismatch [mpegts @ 0x7ff3d0f43880] PES packet size mismatch [mpegts @ 0x7ff3d0f43880] PES packet size mismatch [mpegts @ 0x7ff3d0f43880] PES packet size mismatch [mpegts @ 0x7ff3d0f43880] PES packet size mismatch [mpegts @ 0x7ff3d0f43880] PES packet size mismatch [mpegts @ 0x7ff3d0f43880] PES packet size mismatch -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412423] Rendering crashes for projects which import other kdenlive projects
https://bugs.kde.org/show_bug.cgi?id=412423 --- Comment #1 from b3_1...@yahoo.co.uk --- Created attachment 122921 --> https://bugs.kde.org/attachment.cgi?id=122921=edit The second project (which imports the first project) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412423] New: Rendering crashes for projects which import other kdenlive projects
https://bugs.kde.org/show_bug.cgi?id=412423 Bug ID: 412423 Summary: Rendering crashes for projects which import other kdenlive projects Product: kdenlive Version: 19.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: b3_1...@yahoo.co.uk Target Milestone: --- Created attachment 122920 --> https://bugs.kde.org/attachment.cgi?id=122920=edit The first project (which will be imported in the second project) Kdenlive 19.08 crashes when trying to render projects that have Kdenlive projects imported and inserted into tracks. It renders the part before it, then it crashes when it gets to rendering the inserted project. Sometimes it simply stalls when getting here, but most of the time the rendering crashes. STEPS TO REPRODUCE 1. Create a project, import video files into it and put them into the tracks. Save the project. 2. Create another project and import the previous project into it. Add the project into the tracks and add some video before it (intro video). 3. Render the project. OBSERVED RESULT The rendering crashes when it gets to rendering the imported project. Rendering of crashed [matroska,webm @ 0x7f4df75f9c40] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f4df51f1680] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f4df4b90d00] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f4df4be63c0] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mp4 @ 0x7f4df4200f00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 0x7f4df4200f00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [ogg @ 0x7f4d96bfa540] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d94b6c400] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d94b6c400] PES packet size mismatch [mpegts @ 0x7f4d94b6c400] PES packet size mismatch [mpegts @ 0x7f4d94b6c400] PES packet size mismatch [mpegts @ 0x7f4d94b6c400] PES packet size mismatch [mpegts @ 0x7f4d94b6c400] PES packet size mismatch [mpegts @ 0x7f4d94b6c400] PES packet size mismatch [mpegts @ 0x7f4d94b6c400] PES packet size mismatch [mpegts @ 0x7f4d94bc4cc0] PES packet size mismatch [mpegts @ 0x7f4d6463e180] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d6463e180] PES packet size mismatch [mpegts @ 0x7f4d97a96dc0] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d97a96dc0] PES packet size mismatch [mpegts @ 0x7f4d97a96dc0] PES packet size mismatch [mpegts @ 0x7f4d97a96dc0] PES packet size mismatch [mpegts @ 0x7f4d97a96dc0] PES packet size mismatch [mpegts @ 0x7f4d97a96dc0] PES packet size mismatch [mpegts @ 0x7f4d97a96dc0] PES packet size mismatch [mpegts @ 0x7f4d97a96dc0] PES packet size mismatch [mpegts @ 0x7f4d97a9dd80] PES packet size mismatch [mpegts @ 0x7f4d97ad5e40] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d97ad5e40] PES packet size mismatch [matroska,webm @ 0x7f4d649e9a80] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f4d649fe300] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f4d647138c0] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [matroska,webm @ 0x7f4d6472b180] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [ogg @ 0x7f4d67118780] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d671a7440] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d671a7440] PES packet size mismatch [mpegts @ 0x7f4d671a7440] PES packet size mismatch [mpegts @ 0x7f4d671a7440] PES packet size mismatch [mpegts @ 0x7f4d671a7440] PES packet size mismatch [mpegts @ 0x7f4d671a7440] PES packet size mismatch [mpegts @ 0x7f4d671a7440] PES packet size mismatch [mpegts @ 0x7f4d671a7440] PES packet size mismatch [mpegts @ 0x7f4d671acb80] PES packet size mismatch [mpegts @ 0x7f4d67285a00] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d67285a00] PES packet size mismatch [mpegts @ 0x7f4d6723d540] Value 1,00 for parameter 'seekable' out of range [-1 - 0] [mpegts @ 0x7f4d6723d540] PES packet size mismatch [mpegts @ 0x7f4d6723d540] PES packet size mismatch [mpegts @ 0x7f4d6723d540] PES packet size mismatch [mpegts @ 0x7f4d6723d540] PES packet size mismatch [mpegts @ 0x7f4d6723d540] PES packet size mismatch [mpegts @ 0x7f4d6723d540] PES packet size mismatch [mpegts @ 0x7f4d6723d540] PES packet size mismatch [mpegts @ 0x7f4d67244580] PES packet size mismatch [mpegts @ 0x7f4d507d0b40] Value 1,00 for
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #9 from Kai Krakow --- Here's more evidence of why LMDB may be a particularly bad choice for the workload applied by baloo: It is btree organized, and writing and maintaining btrees will result in a lot of random I/O. At some point in time, when the DB has become big enough or scrambled enough due to constant updates, this will backfire badly resulting in very bad I/O patterns. https://blog.dgraph.io/post/badger-lmdb-boltdb/ Baloo should migrate to a key/value store that is much better at writing data and maintaining its internals. Read performance of the database should probably not be the primary concern but performance of long-term writing and updating: It should maintain good read and write performance. According to the article, LMDB doesn't (except you give it the full 256GB RAM and lock it into memory). Researching a little further, we can find a quite different picture: https://en.wikipedia.org/wiki/Lightning_Memory-Mapped_Database It says that LMDB has exceptional write performance and maintains good performance altogether. Maybe this would need some benchmarks but it probably holds true only when the DB fully fits into memory all the time. And looking at the design description in that article we can easily see the downsides: The database can always only increase in size, even more when writing concurrently (there's no locking, so any time during concurrent access patterns it will append to the database). It also never re-organizes its internal structure, it just reuses memory blocks allocated from a free blocks tree without taking HDD access patterns into account. And, LMBDs design pays back best only with big values. I don't think this is what baloo stores. The article further says that LMDB can (on hypothetical file systems) fail on Linux when not using fsync(). Was fsync() added to LMDB for such a hypothetical case? This would be fatal to system performance. LMDB seems to be baked into a lot of KV databases due to it's seemingly good performance. So actually, this would need a lot more insight to decide whether LMDB is suitable for baloo (maybe it is but it isn't used optimally). Someone with more real-world experience of KV databases and associated usage patterns may comment on this. Currently, limiting the mmap size helps a lot here. And as mentioned by Martin, there's clearly a bug somewhere resulting in massive write work-loads and exceptional growth of the database. Maybe it's just a really bad access pattern by coincidence that results in exceptional bad behavior of LMDB. I was very happy with baloo performance for a long time until it suddenly broke some day. I'm not even sure that's baloo's fault: Judging from the commit subjects the code hasn't undergone any substantial changes since a long time, only small fixes and tweaks. There's commit b0890aca71aa4f0fdabe65ee7b7fbd0bc844d8b8 after KF 5.27.0 which bumped maximum index size from 5 GB to 256 GB. @Martin May this be around the time (end of 2016) when it broke for you? Your "balooctl indexSize" example seems to suggest there's a big rollover of copy-on-write operations leaving unused memory blocks behind (maybe to small to be effectively reused) and thus blowing up the DB file size. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410723] Freehand annotation jagged lines with stylus
https://bugs.kde.org/show_bug.cgi?id=410723 independent-squirrel changed: What|Removed |Added CC||BM-2cVRL7BNxUQQsFvg4JiGmkmm ||nzafzgp...@bitmessage.ch --- Comment #13 from independent-squirrel --- I have experienced the same issue on my up-to-date Arch Linux installation. I'm using a Wacom pan on my laptop screen. It is also working fine in GIMP. I downloaded and compiled the following versions and found that all of them have the same issue: 1.8.1 1.3.3 release tag 17.12.3 1.0.3 release tag 16.12.3 I therefor think that if this feature ever worked properly - which I don't know - some dependency must have changed its API. I can also confirm, that drawing with the pan results in a significant increase in points for the drawn path. I compared it to using my finger on the same touchscreen. -- You are receiving this mail because: You are watching all bug changes.
[kmplayer] [Bug 412422] New: kmplayer crashes right on start
https://bugs.kde.org/show_bug.cgi?id=412422
Bug ID: 412422
Summary: kmplayer crashes right on start
Product: kmplayer
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: koos.vrie...@gmail.com
Reporter: fe...@kngnt.org
Target Milestone: ---
Application: kmplayer ("0.12.0b")
Qt Version: 5.13.1
Frameworks Version: 5.62.0
Operating System: Linux 5.3.1-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages
-- Information about the crash:
I have just installed kmplayer and mplayer on arch linux. Then, I have tried to
start kmplayer, to only get a segfault.
The crash can be reproduced every time.
-- Backtrace:
Application: KMPlayer (kmplayer), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7ae82e5e80 (LWP 23911))]
Thread 3 (Thread 0x7f7ad700 (LWP 23914)):
#0 0x7f7aec00e415 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1 0x7f7ae4ac9f5c in ?? () from /usr/lib/dri/i965_dri.so
#2 0x7f7ae4ac9b58 in ?? () from /usr/lib/dri/i965_dri.so
#3 0x7f7aec00857f in start_thread () from /usr/lib/libpthread.so.0
#4 0x7f7aeee050e3 in clone () from /usr/lib/libc.so.6
Thread 2 (Thread 0x7f7ae6c7c700 (LWP 23912)):
#0 0x7f7aeedfa667 in poll () from /usr/lib/libc.so.6
#1 0x7f7aeb496130 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x7f7aeb496201 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3 0x7f7aed4f9a1c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4 0x7f7aed4a04ec in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5 0x7f7aed2d2385 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6 0x7f7aecad9b37 in ?? () from /usr/lib/libQt5DBus.so.5
#7 0x7f7aed2d35b0 in ?? () from /usr/lib/libQt5Core.so.5
#8 0x7f7aec00857f in start_thread () from /usr/lib/libpthread.so.0
#9 0x7f7aeee050e3 in clone () from /usr/lib/libc.so.6
Thread 1 (Thread 0x7f7ae82e5e80 (LWP 23911)):
[KCrash Handler]
#6 0x7f7aecee7148 in xcb_get_setup () from /usr/lib/libxcb.so.1
#7 0x7f7aeecba6d7 in KMPlayer::ViewArea::syncVisual() () from
/usr/lib/libkmplayercommon.so
#8 0x7f7aeecbc267 in KMPlayer::ViewArea::timerEvent(QTimerEvent*) () from
/usr/lib/libkmplayercommon.so
#9 0x7f7aed4ce3e5 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#10 0x7f7aede9f08b in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#11 0x7f7aede5b4f5 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#12 0x7f7aede64e11 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#13 0x7f7aed4a19c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#14 0x7f7aed4f8d9d in QTimerInfoList::activateTimers() () from
/usr/lib/libQt5Core.so.5
#15 0x7f7aed4f9632 in ?? () from /usr/lib/libQt5Core.so.5
#16 0x7f7aeb4943ae in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#17 0x7f7aeb4961c1 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x7f7aeb496201 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#19 0x7f7aed4f9a03 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#20 0x7f7aed4a04ec in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#21 0x7f7aed4a8326 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#22 0x7f7aeef02c70 in kdemain () from /usr/lib/libkdeinit5_kmplayer.so
#23 0x7f7aeed2fee3 in __libc_start_main () from /usr/lib/libc.so.6
#24 0x55ae427b805e in _start ()
[Inferior 1 (process 23911) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 407065] Debugging silently does not work without CMAKE_BUILD_TYPE=DEBUG
https://bugs.kde.org/show_bug.cgi?id=407065 Saurav Sengupta changed: What|Removed |Added CC||saurav1@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412421] 25+ char string without spaces search fails
https://bugs.kde.org/show_bug.cgi?id=412421 i16d0o+8ay17bwmgp...@sharklasers.com changed: What|Removed |Added Summary|25+ char string without |25+ char string without |spaces string search fails |spaces search fails -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 412421] New: 25+ char string without spaces string search fails
https://bugs.kde.org/show_bug.cgi?id=412421 Bug ID: 412421 Summary: 25+ char string without spaces string search fails Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: i16d0o+8ay17bwmgp...@sharklasers.com Target Milestone: --- Sometimes files have long filenames consisting of 25+ characters without spaces. Baloo fails to find these files when searched by the file's full name. It works when baloo is disabled. STEPS TO REPRODUCE 1. Generate a file with a 25+ character full name. abcdefghijklmnopqrstuvwxyz OBSERVED RESULT 2. With baloo enabled, search for "abcdefghijklmnopqrstuvwxyz". Terminal: baloosearch abcdefghijklmnopqrstuvwxyz / Dolphin: Dolphin>Find abcdefghijklmnopqrstuvwxyz 3. File not found. 4. Search for a <25 string "abcd", "abcdefg", "abcdefghijklmnopq". Baloo finds the file. EXPECTED RESULT Baloo finds the file when searched by its full filename. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04, 19.04, KDE Neon 20190919-1119, Debian Buster KDE (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION If the filename is split with spaces: "abcdefgh ijklmnopqrs tuvwxyz" the file can be found by its full filename. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412420] New whitespace caused by invisible toolbar
https://bugs.kde.org/show_bug.cgi?id=412420 --- Comment #2 from Christoph Cullmann --- Btw., thanks for that catch! ;=) Now that you tell me that, I see that extra space here, too :P -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412420] New whitespace caused by invisible toolbar
https://bugs.kde.org/show_bug.cgi?id=412420 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Assignee|kwrite-bugs-n...@kde.org|dhaum...@kde.org --- Comment #1 from Christoph Cullmann --- Hmm, might that be the external tools toolbar? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412420] New: New whitespace caused by invisible toolbar
https://bugs.kde.org/show_bug.cgi?id=412420 Bug ID: 412420 Summary: New whitespace caused by invisible toolbar Product: kate Version: Git Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de Target Milestone: --- About a few days ago, openQA tests started failing because kate changed looks: https://openqa.opensuse.org/tests/1043504#step/kate/22 There's added whitespace between the menu bar and the tab bar. It seems to be a toolbar with only invisible items. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 408284] Set CSV import format per account
https://bugs.kde.org/show_bug.cgi?id=408284 Syfer Polski changed: What|Removed |Added CC||syfe...@gmail.com --- Comment #3 from Syfer Polski --- Would it be possible to add a manually selectable parser for the DD/MM/ format? HSBC's midata contains the date in this format and trying to import it into Skrooge results in a "Date format not supported" error. I can provide an example file if that would help. The headers are present, but don't specify the data formats, and the list of transactions is followed by an empty line and an arranged overdraft: Date,Type,Merchant/Description,Debit/Credit,Balance 28/08/2019,))),TESCO LONDON,-£2.00,+£998.75 Arranged overdraft limit,28/09/2019,+£0.00 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #8 from Kai Krakow --- Created attachment 122919 --> https://bugs.kde.org/attachment.cgi?id=122919=edit Experimental: Reduce mmap by one magnitude This patch reduces the memory map size for LMDB by one order of magnitude (16 instead of 256 GB). After applying the patch, I purged the DB and restarted baloo. It churns along nicely now, I/O is down to less than 10 MB/s instead of 50-100 MB/s constantly before. Also, running action that obviously do a bunch of memory allocations in Plasma (like opening the app drawer) now run much smoother again (instantly instead of a noticeable but subjective delay). The whole system feels much smoother again. I'm guessing that a lot of ongoing dirty-page writebacks, page faults and VMM handling has a lot of drawbacks and introduces a lot of TLB flushes because mappings into the process are constantly updated. It also seems to introduce a lot of I/O overhead. I'm not sure why that is but it seems this big mmap has indeed drawbacks. A lot of random accesses into the mmap may cause unintentional read-ahead, unpredictable IO patterns and may dominate the cache which is what I believe causes the excessive I/O behavior. This patch (together with the previous patch) makes my system run much nicer again. I can actually use krunner again without causing a lot of additional IO and lags. My system has 32 GB of RAM. Looking at all this, I wonder if LMDB is really the right tool. It is tempting to use it, but from the project documentation it seems to be intended as a read-mostly database. This is clearly not what baloo does with it, especially during re-indexing/updating or first indexing. The mmap size seems to be tightly bound to the maximum DB size which, looking at my above test results, limits the scaling of baloo a lot. It should probably not be too difficult to swap LMDB with another key/value database better fitting the usage pattern (bursts of lots of write transactions with only occasional read transactions when a user actually searches for something). LMDB (as the DBE backing the OpenLDAP project) seems to be designed for exactly the opposite usage pattern. Are there any more thoughts of it? Any idea which key/value DBE could fit better? What about multi-threading? Current code seems to run with only 1 thread in parallel only anyways despite using the thread pool classes of Qt. I'd volunteer to invest some spare time into swapping out LMDB for something different. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389440] Filter: Add to Addressbook needs to include REPLY-TO field as source
https://bugs.kde.org/show_bug.cgi?id=389440 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||gjditchfi...@acm.org --- Comment #1 from gjditchfi...@acm.org --- Would you be able to add the reply-to address to your address book by switching header styles? For example, with KMail 5.7.3, I did this: - Choose menu item Settings → Configure KMail... - In the Plugins section, in Header Style Plugins, enable all of the header styles. - Close and re-open KMail. - Choose menu item View → Headers → Long Headers. The message's Reply-to header is now visible, and I can right-click it to add it to an address book. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 Jacob changed: What|Removed |Added CC||jacobsea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) and writes a *ton* of data while indexing
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #7 from Kai Krakow --- Created attachment 122918 --> https://bugs.kde.org/attachment.cgi?id=122918=edit Reduce stack pressure This patch reduces pressure on the used stack size by looping instead of recursively calling itself when skipping files to index. This can add up a lot when skipping many files/directories in succession. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 412419] New: Add button to build environment from prefix.sh
https://bugs.kde.org/show_bug.cgi?id=412419 Bug ID: 412419 Summary: Add button to build environment from prefix.sh Product: kdevelop Version: 5.4.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: simg...@gmail.com Target Milestone: --- SUMMARY Given that many projects come with a prefix.sh file that should be sourced to configure the running environment, it would be nice to add a button in the "Configure environment variables" page to create a new environment from the prefix.sh file. Or possibly build the environment automatically after the first build and called something like "Project name (Auto)" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 406461 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406461] Can't update from V9 to V10
https://bugs.kde.org/show_bug.cgi?id=406461 Maik Qualmann changed: What|Removed |Added CC||laryo...@mail.tomsknet.ru --- Comment #8 from Maik Qualmann --- *** Bug 412417 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393336] Brush rotation using tablet pen's rotation capped at 180 degrees.
https://bugs.kde.org/show_bug.cgi?id=393336 Oscar Franco changed: What|Removed |Added Version|4.2.6 |4.2.7-beta1 --- Comment #8 from Oscar Franco --- pen rotation now works on 4.2.7.beta1, but only for rotation, if I'd want to map pen rotation to other attributes it won't work. Tested it with size and opacity. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 --- Comment #2 from Maik Qualmann --- One more note. Your database is located on the file path on a NAS drive. For performance reasons, the SQLite databases should reside on a fast local drive. Maik -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 184122] Additional formats for Decoding Table
https://bugs.kde.org/show_bug.cgi?id=184122
Simon Hüllmandel changed:
What|Removed |Added
CC||lllusion3...@gmail.com
--- Comment #4 from Simon Hüllmandel ---
It might also be nice to support integers other than {8,16,32,64}-bit.
One format I'm working with uses one byte to specify the "size" of the integer
following this byte.
This can result in e.g 3-byte (24-bit) integers like this: 03 AB CD EF would be
0xEFCDAB.
I'm not asking for support for this specific binary format, but some way to
decode these.
One way I'm thinking of would be to go by mouse/keyboard selection.
I.e. you would select AB CD EF in the file view and get the value in the
decoding table either in a new row or by restricting the existing rows to the
selection.
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 411864] Onlinebanking with aqbanking needs rework for psd2
https://bugs.kde.org/show_bug.cgi?id=411864 AndreJ changed: What|Removed |Added CC||herbert.marsch...@online.de --- Comment #2 from AndreJ --- *** Bug 412416 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412416] Most german banks demand a "Registrierkennung" at the BaFin - otherwise HBCI is not longer possible
https://bugs.kde.org/show_bug.cgi?id=412416 AndreJ changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||andre+jo...@nurfuerspam.de --- Comment #1 from AndreJ --- Fixed in version 5.0.7 (which has no binary packages for Windows and some other OS yet. *** This bug has been marked as a duplicate of bug 411864 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- I do not know what openSUSE does wrong here because the error has already been reported. I can not reproduce it here at openSUSE Thumbleweed. You have no write permission to the database file. DigiKam does not change any rights. This must be done outside. Check the write permission on the digikam4.db and the other DB files. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 412418] Enhanced Media Controls break player in vgmrips.net
https://bugs.kde.org/show_bug.cgi?id=412418 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 412418] New: Enhanced Media Controls break player in vgmrips.net
https://bugs.kde.org/show_bug.cgi?id=412418 Bug ID: 412418 Summary: Enhanced Media Controls break player in vgmrips.net Product: plasma-browser-integration Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: ta...@tasossah.com Target Milestone: --- SUMMARY Enabling "Enhanced Media Controls" in the addon settings breaks the player in vgmrips.net. This setting is turned on by default now, meaning that the moment the addon is installed, the player no longer functions. STEPS TO REPRODUCE 1. Make sure "Enhanced Media Controls" is enabled 2. Go to https://vgmrips.net/packs/pack/ys-ii-special-ibm-pc-at 3. Click Play or click on any of the tracks OBSERVED RESULT Player gets stuck "Loading" EXPECTED RESULT Player starts playing music 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 Kernel Version: 5.3.1 OS Type: 64-bit Processors: 4 × Intel® Core™2 Quad CPU Q6600 @ 2.40GHz Memory: 6,5 GiB of RAM ADDITIONAL INFORMATION There were no observable errors in the js console in the developer tools. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 412334] Now Playing view no longer shows or updates metadata or lyrics until you manually re-play the current song
https://bugs.kde.org/show_bug.cgi?id=412334 Nate Graham changed: What|Removed |Added Version Fixed In||19.12.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412417] New: digikam fails to start - update fails
https://bugs.kde.org/show_bug.cgi?id=412417 Bug ID: 412417 Summary: digikam fails to start - update fails Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Sqlite Assignee: digikam-bugs-n...@kde.org Reporter: laryo...@mail.tomsknet.ru Target Milestone: --- SUMMARY After updating the OS to OpenSUSE 15.1, digikam stopped working: it tries to update its database from version 8 to 10, but after updating to 9 update to 10 fails. STEPS TO REPRODUCE 1. Have digikam installed on OpenSUSE 41.2 2. Update OS to OpenSUSE 15.1 3. Try to run digikam OBSERVED RESULT After launching it in command prompt: > digikam digikam.general: AlbumWatch use QFileSystemWatcher digikam.general: Database Parameters: Type: "QSQLITE" DB Core Name: "/mnt/nas4free/Album/digikam4.db" DB Thumbs Name: "/mnt/nas4free/Album/thumbnails-digikam.db" DB Face Name: "/mnt/nas4free/Album/recognition.db" DB Similarity Name: "/mnt/nas4free/Album/similarity.db" Connect Options: "" Host Name:"" Host port:-1 Internal Server: false Internal Server Path: "" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "" Password: "" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 8 digikam.coredb: Core database: makeUpdates 8 to 10 digikam.coredb: Core database: success updating to version 9 digikam.coredb: Core database: success updating to version 9 digikam.dbengine: Failure executing query: "" Error messages: "Невозможно получить строку" "attempt to write a readonly database" 8 1 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV9ToV10" ] Statement [ "DROP TABLE IF EXISTS ImageHaarMatrix;" ] digikam.coredb: Core database: schema update to V 10 failed! digikam.dbengine: Failure executing query: "REPLACE INTO Settings VALUES (?,?);" Error messages: "Невозможно получить строку" "attempt to write a readonly database" 8 1 Bound values: (QVariant(QString, "DBVersion"), QVariant(QString, "9")) digikam.dbengine: Failure executing query: "REPLACE INTO Settings VALUES (?,?);" Error messages: "Невозможно получить строку" "attempt to write a readonly database" 8 1 Bound values: (QVariant(QString, "DBVersionRequired"), QVariant(QString, "5")) digikam.coredb: Core database: cannot process schema initialization KMemoryInfo: Platform identified : "LINUX" KMemoryInfo: TotalRam: 8387072000 digikam.general: Allowing a cache size of 200 MB QThreadStorage: Thread 0x7f8a64baec40 exited after QThreadStorage 12 destroyed EXPECTED RESULT digikam runs SOFTWARE/OS VERSIONS OpenSUSE 15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403842] Libinput mouse KCM lost the scroll speed setting that was present in the evdev version
https://bugs.kde.org/show_bug.cgi?id=403842 --- Comment #13 from Claudius Ellsel --- (In reply to Tim Richardson from comment #10) > This would be great. I am sure it is obvious, but such UI needs also a > different setting for touchpad scrolling (one of Peter's 'devilish details' > which means it is hard to do in libinput), this bug really has dependency on > Bug 403843 although that one has a lot fewer vote. I think you are correct, so I added Bug 403843 as a dependency for this one. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 403843] Libinput touchpad KCM needs a scroll speed setting
https://bugs.kde.org/show_bug.cgi?id=403843 Claudius Ellsel changed: What|Removed |Added Blocks||403842 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=403842 [Bug 403842] Libinput mouse KCM lost the scroll speed setting that was present in the evdev version -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403842] Libinput mouse KCM lost the scroll speed setting that was present in the evdev version
https://bugs.kde.org/show_bug.cgi?id=403842 Claudius Ellsel changed: What|Removed |Added Depends on||403843 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=403843 [Bug 403843] Libinput touchpad KCM needs a scroll speed setting -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403842] Libinput mouse KCM lost the scroll speed setting that was present in the evdev version
https://bugs.kde.org/show_bug.cgi?id=403842 --- Comment #12 from Claudius Ellsel --- (In reply to willemvanhulle from comment #9) > Thank you for all the replies. Removing the driver does not work in Fedora. > How should the snippet look like? Have a look at https://bugs.kde.org/show_bug.cgi?id=398610#c3 maybe that can help you. -- You are receiving this mail because: You are watching all bug changes.
