[dolphin] [Bug 405449] Dolphin crashes when transfering files from a disk to another with different FS
https://bugs.kde.org/show_bug.cgi?id=405449 David Hallas changed: What|Removed |Added CC||da...@davidhallas.dk --- Comment #1 from David Hallas --- This looks like the same bug as #368287 - Could you try and reproduce the issue with Frameworks 5.56.0? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #15 from Rob --- It definitely should not be able to run on 10.11 because QT now refuses to support that version of the OS. But I did set the deployment targets to 10.12 and I did test it out on a 10.12 system awhile back. I thought it was all working. I can try to run a few tests on it tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #14 from Andre Kovacs --- Yes, I just updated from El Capitan to High Sierra to be able to run KStars 3.1.1. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #13 from Rob --- Illegal Instruction 4?? Interesting. That is the error I have seen before when I try to run software that was built to run for a newer version of Mac OS X on an older OS X. But you said you are running High Sierra. . . Let me look into this one. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 405422] ksudoku live-git (commit 09814312d) small-game generation fails with "Unable to generate a puzzle of the chosen variant"
https://bugs.kde.org/show_bug.cgi?id=405422 --- Comment #1 from Ian Wadham --- I used to be maintainer/developer for KSudoku, but am out of touch with it now. However I will try to help narrow this problem down. The message you are getting seems to be from the "welcome" screen (where you choose a puzzle type). It was added to the code in April 2017, see https://phabricator.kde.org/D5671. Do you stay on the welcome screen after you see the message? Please confirm. Please can you give me a precise list of the names of the puzzle types for which you get the message. For example, which "6x6" are you using, the one with rectangular blocks or the Mathdoku - Settable Size with size set to 6x6? Or maybe both? You say that games smaller than 9x9 seem to fail, but what about variant (non-Classic) games of size 9x9, such as Killer Sudoku, Aztec, Jigsaw or even Samurai? Your comments about compiler and Qt changes may also be a clue. There is some very old code in KSudoku (2007-08 vintage) that I have never dared touch. Perhaps some of that has been rendered invalid or works differently now. I regret that I cannot actually build and test the latest KSudoku code, because I now work on an Apple Macbook and am unable to build KF5 and Qt5. BTW, it does not surprise me that the clock wraps around, but I think you might find Samurai (five 9x9 grids) more fun than a 25x25... :-) -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 386744] Arabic–Indic numerals not recognized as valid numbers
https://bugs.kde.org/show_bug.cgi?id=386744 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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.
[kcalc] [Bug 357860] Launcher is on white background when all other launchers are on black
https://bugs.kde.org/show_bug.cgi?id=357860 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.
[dragonplayer] [Bug 381673] problems with changing to full-screen mode and returning back to normal mode.
https://bugs.kde.org/show_bug.cgi?id=381673 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 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.
[amarok] [Bug 404695] Icy Cast metadata received from stream doesn't updates the author correctly
https://bugs.kde.org/show_bug.cgi?id=404695 --- 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.
[Spectacle] [Bug 404983] Spectacle cannot take screenshots in QPainter
https://bugs.kde.org/show_bug.cgi?id=404983 e...@linuxmail.org changed: What|Removed |Added CC||m...@baloneygeek.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400538] vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55
https://bugs.kde.org/show_bug.cgi?id=400538 --- Comment #4 from Alex Henrie --- Wine has been using IRETQ since May 2009: https://source.winehq.org/git/wine.git/commitdiff/880d00fb43de924a3543b0ad53b5aaf0ad63d0cb The first reference I could find to IRETQ in Wine causing a problem with Valgrind was in January 2013: https://sourceforge.net/p/valgrind/mailman/message/30422124/ -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #12 from Andre Kovacs --- Here's the console output of the failed execution via the command line (original version of astrometry.net solver): "/Applications/Astronomia/kstars.app/Contents/MacOS/astrometry/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -L 32.5717 -H 53.9383 -u aw -3 17.3038 -4 -55.1392 -5 30 --config /Applications/Astronomia/kstars.app/Contents/MacOS/astrometry/bin/astrometry.cfg -W ./solution.wcs ./test.fits Reading input file 1 of 1: "./test.fits"... Illegal instruction: 4" -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #11 from Andre Kovacs --- Here's the console output of the successful execution via the command line (older version of astrometry.net solver): "/Applications/Astronomia/kstars.app/Contents/MacOS/astrometry/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -L 32.5717 -H 53.9383 -u aw -3 17.3038 -4 -55.1392 -5 30 --config /Applications/Astronomia/kstars.app/Contents/MacOS/astrometry/bin/astrometry.cfg -W ./solution.wcs ./test.fits Reading input file 1 of 1: "./test.fits"... Extracting sources... Downsampling by 2... simplexy: found 1474 sources. /Applications/Astronomia/kstars.app/Contents/MacOS/python/bin/site-packages/pyfits/__init__.py:22: PyFITSDeprecationWarning: PyFITS is deprecated, please use astropy.io.fits PyFITSDeprecationWarning) # noqa Reading sort column "FLUX" Sorting sort column mmapping input file Copying table header. Writing row 0 Done /Applications/Astronomia/kstars.app/Contents/MacOS/python/bin/site-packages/pyfits/__init__.py:22: PyFITSDeprecationWarning: PyFITS is deprecated, please use astropy.io.fits PyFITSDeprecationWarning) # noqa Solving... Reading file "./test.axy"... Only searching for solutions within 30 degrees of RA,Dec (17.3038,-55.1392) Field 1 did not solve (index index-4210.fits, field objects 1-10). Field 1 did not solve (index index-4209.fits, field objects 1-10). Field 1 did not solve (index index-4208.fits, field objects 1-10). Field 1 did not solve (index index-4207-11.fits, field objects 1-10). Field 1 did not solve (index index-4207-08.fits, field objects 1-10). Field 1 did not solve (index index-4207-04.fits, field objects 1-10). Field 1 did not solve (index index-4206-11.fits, field objects 1-10). log-odds ratio 295.194 (1.58973e+128), 53 match, 0 conflict, 44 distractors, 77 index. RA,Dec = (17.1018,-55.2418), pixel scale 0.590997 arcsec/pix. Hit/miss: Hit/miss: -++-++-+++-++-++--+++-++-+-+--++---+-+--+-+-+(best)--- Field 1: solved with index index-4206-08.fits. Field 1 solved: writing to file ./test.solved to indicate this. Field: ./test.fits Field center: (RA,Dec) = (17.103504, -55.241262) deg. Field center: (RA H:M:S, Dec D:M:S) = (01:08:24.841, -55:14:28.542). Field size: 51.334 x 34.2598 arcminutes Field rotation angle: up is 89.8983 degrees E of N Field parity: neg Creating new FITS file "./test.new"... -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #10 from Andre Kovacs --- I managed to use your commands to successfully call the plate solver via the command line, and using the Options displayed on Ekos. Here're my commands: export PATH=/Applications/Astronomia/kstars.app/Contents/MacOS/netpbm/bin:/Applications/Astronomia/kstars.app/Contents/MacOS/python/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin export PYTHONPATH=/Applications/Astronomia/kstars.app/Contents/MacOS/python/bin/site-packages /Applications/Astronomia/kstars.app/Contents/MacOS/astrometry/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -L 32.5717 -H 53.9383 -u aw -3 17.3038 -4 -55.1392 -5 30 --config /Applications/Astronomia/kstars.app/Contents/MacOS/astrometry/bin/astrometry.cfg -W ./solution.wcs ./test.fits -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405293] CSV importer does not handle transfers
https://bugs.kde.org/show_bug.cgi?id=405293 --- Comment #5 from Jim Davis --- Attached are three csv files labelled BankA, BankB, and BankA_all_accts. These are a sample of 1 month of historical transactions, with redacted (replaced) account numbers and in some cases a note in the format (jd note: xxx). Bank "B" is my primary checking & savings, Bank "A" is a secondary checking but has better organizational and external account linking abilities. In both cases, csv output can be combined (all internal and external linked accounts) or separated by account. Currently only Bank "A" is linked to Bank "B" but both have an option to link to other (external) bank transactions. Bank "A" allows for both a custom description as well as 2 levels of categories with splits, plus tags. Bank "B" allows for a custom "nickname (description) and has only 1 category with splits and call them "tags" in the csv. Bank "A" web software: MX http://www.mx.com/company/ also ref: https://webcache.googleusercontent.com/search?q=cache:uZjwPbc_rVoJ:https://www.crunchbase.com/organization/moneydesktop+=4=en=clnk=us Bank "B" web software: Fiserv https://www.fiserv.com/customer-channel-management/internet-banking.aspx -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405293] CSV importer does not handle transfers
https://bugs.kde.org/show_bug.cgi?id=405293 --- Comment #4 from Jim Davis --- Created attachment 118795 --> https://bugs.kde.org/attachment.cgi?id=118795=edit Sample Bank CSV Export #3 of 3 Sample Bank CSV Export #3 of 3 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405293] CSV importer does not handle transfers
https://bugs.kde.org/show_bug.cgi?id=405293 --- Comment #3 from Jim Davis --- Created attachment 118794 --> https://bugs.kde.org/attachment.cgi?id=118794=edit Sample Bank CSV Export #2 of 3 Sample Bank CSV Export #2 of 3 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405293] CSV importer does not handle transfers
https://bugs.kde.org/show_bug.cgi?id=405293 --- Comment #2 from Jim Davis --- Created attachment 118793 --> https://bugs.kde.org/attachment.cgi?id=118793=edit Sample Bank CSV Export #1 Attached are three csv files labelled BankA, BankB, and BankA_all_accts. These are a sample of 1 month of historical transactions, with redacted (replaced) account numbers and in some cases a note in the format (jd note: xxx). Bank "B" is my primary checking & savings, Bank "A" is a secondary checking but has better organizational and external account linking abilities. In both cases, csv output can be combined (all internal and external linked accounts) or separated by account. Currently only Bank "A" is linked to Bank "B" but both have an option to link to other (external) bank transactions. Bank "A" allows for both a custom description as well as 2 levels of categories with splits, plus tags. Bank "B" allows for a custom "nickname (description) and has only 1 category with splits and call them "tags" in the csv. Bank "A" web software: MX http://www.mx.com/company/ also ref: https://webcache.googleusercontent.com/search?q=cache:uZjwPbc_rVoJ:https://www.crunchbase.com/organization/moneydesktop+=4=en=clnk=us Bank "B" web software: Fiserv https://www.fiserv.com/customer-channel-management/internet-banking.aspx -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390642] Cursor gets stuck with the wrong icon after moving between canvas and gui
https://bugs.kde.org/show_bug.cgi?id=390642 --- Comment #47 from vanyossi --- It is solved for me on latest master and Qt 5.12.1 with xcb patches/changes from Dmitry. Cursor no longer gets stuck when going between GUI and Canvas. OpenGL Accel is enabled. Coould you check this is the case by checking the dmg below? (link to google drive) https://drive.google.com/file/d/1bdCJ7vZK8B-18bFdpDKa8R9fzdBd3-mE/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #9 from Andre Kovacs --- Here's the verbose output of the success execution (older version of astrometry.net solver): "2019-03-14T00:37:10 Solution coordinates: RA (01h 09m 14s) DEC (-55° 08' 05") Telescope Coordinates: RA (01h 09m 12s) DEC (-55° 08' 21") 2019-03-14T00:37:10 WCS information updated. Images captured from this point forward shall have valid WCS. 2019-03-14T00:37:10 Solver completed in 8 seconds. 2019-03-14T00:37:01 Starting solver... 2019-03-14T00:37:01 Index files index-4202 to index-4204 are missing. Astrometry.net would not be able to adequately solve plates until you install the missing index files. Download the index files from http://www.astrometry.net 2019-03-14T00:37:01 Image received. 2019-03-14T00:36:47 Capturing image... 2019-03-14T00:35:55 World Coordinate System (WCS) is enabled. CCD rotation must be set either manually in the CCD driver or by solving an image before proceeding to capture any further images, otherwise the WCS information may be invalid. 2019-03-14T00:35:54 Detected Astrometry.net version 0.73 2019-03-14T00:35:54 Idle." -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #8 from Andre Kovacs --- How do I enable the log level required to be able to see the commands that Ekos used to call the astrometry.net process? I couldn't get any information on that by enabling the Verbosity as Verbose, under KStars -> Preferences -> Advanced -> Logging Output. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 313841] No keyboard shortcut for "Find" action
https://bugs.kde.org/show_bug.cgi?id=313841 Kurt Hindenburg changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kon ||sole/6ba044c145a68b0356fde5 ||cf210d9db812eba310 Resolution|--- |FIXED --- Comment #8 from Kurt Hindenburg --- Git commit 6ba044c145a68b0356fde5cf210d9db812eba310 by Kurt Hindenburg, on behalf of Nicolas Fella. Committed on 14/03/2019 at 03:25. Pushed by hindenburg into branch 'master'. Define shortcuts for Find actions also for konsolepart Summary: The find action in Yakuake (and other konsolepart users) is missing a shortcut. This is because the shortcut is only defined for Konsole and not for the part. Test Plan: Press Ctrl + Shift + F in Yakuake, search bar opens Reviewers: #konsole, hindenburg, hein Reviewed By: #konsole, hindenburg Subscribers: konsole-devel Tags: #konsole Differential Revision: https://phabricator.kde.org/D19451 M +10 -13 src/SessionController.cpp https://commits.kde.org/konsole/6ba044c145a68b0356fde5cf210d9db812eba310 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #7 from Andre Kovacs --- Here's the verbose output of the failed execution (original version of astrometry.net solver): "2019-03-14T00:17:24 Solver failed. Try again. 2019-03-14T00:17:24 Error starting solver: Process crashed 2019-03-14T00:17:24 Starting solver... 2019-03-14T00:17:24 Index files index-4202 to index-4204 are missing. Astrometry.net would not be able to adequately solve plates until you install the missing index files. Download the index files from http://www.astrometry.net 2019-03-14T00:17:24 Image received. 2019-03-14T00:17:10 Capturing image... 2019-03-14T00:17:09 Changing filter to Green... 2019-03-14T00:15:56 World Coordinate System (WCS) is enabled. CCD rotation must be set either manually in the CCD driver or by solving an image before proceeding to capture any further images, otherwise the WCS information may be invalid. 2019-03-14T00:15:56 Detected Astrometry.net version 0.76 2019-03-14T00:15:56 Idle." Unfortunately, there's not much in it besides the strange error that the optional index files are missing. -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 405419] Tajikistan Map Update
https://bugs.kde.org/show_bug.cgi?id=405419 --- Comment #2 from Victor Ibragimov --- 1)The information referenced to a Wikipedia page at https://en.wikipedia.org/wiki/Regions_of_Tajikistan is outdated and also needs to be updated. "Qurghonteppa" city was remaned to "Bokhtar" city. 2) English version of region name "Вилояти Мухтори Кӯҳистони Бадахшон" was initially incorrectly translated from its original Tajik into English since "Gorno-Badakhshan" is a transliteration from its Russian version "Горно-Бадахшан.." It will be highly appreciated to update English version to "Kuhistoni Badakhshon Autonomous Region" to make it correct. 3)Yes, in addition to a 4 Regions Map that would be great to have a Districts Map, so students can explore more of Tajikistan and learn to know all those beautiful geographical names and their locations. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405158] Konsole Crashes When Logging Out All Tabs in a Window Using "Copy Input To" Feature
https://bugs.kde.org/show_bug.cgi?id=405158 Kurt Hindenburg changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kon ||sole/cb49c985a31692806be5f8 ||f717d79b1425cfcbc9 Status|ASSIGNED|RESOLVED --- Comment #2 from Kurt Hindenburg --- Git commit cb49c985a31692806be5f8f717d79b1425cfcbc9 by Kurt Hindenburg, on behalf of David Hallas. Committed on 14/03/2019 at 03:01. Pushed by hindenburg into branch 'master'. Fixes crash when using the Copy Input To All Tabs feature Summary: Fixes crash when using the Copy Input To All Tabs feature. The crash is caused because the sessions are removed from the SessionManager before the MainWindow is updated. When the MainWindow receives the activeViewChanged signal it assumes that the SessionManager::sessionProfile returns a valid Profile pointer, but in this case it has already been freed and is therefore nullptr. The fix is to simply check if the new active Session has a valid Profile, if not simply ignore it. Test Plan: 1. Open Konsole window 2. Open multiple tabs within that Konsole window 3. (apparently an important piece) Scroll through the tabs and go back to the first one opened, on the far left of the tab bar 4. Select Edit menu -> Copy Input To -> All Tabs in Current Window 5. Type a ctrl-D to issue logout command to all tabs in window Reviewers: #konsole, hindenburg Reviewed By: #konsole, hindenburg Subscribers: hindenburg, konsole-devel Tags: #konsole Differential Revision: https://phabricator.kde.org/D19642 M +3-0src/MainWindow.cpp https://commits.kde.org/konsole/cb49c985a31692806be5f8f717d79b1425cfcbc9 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 405460] error while loading shared libraries: libdouble-conversion.so.3.0.0
https://bugs.kde.org/show_bug.cgi?id=405460 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Severity|critical|normal Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Please report upgrade issues to the bug tracker of your distribution. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404321] Zooming icon dont change after zoom gesture on OSX
https://bugs.kde.org/show_bug.cgi?id=404321 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from vanyossi --- I can confirm this bug on latest master 5c0ca4e. it only occurs when zooming with the touch pad. It seems to be an event signal is mixed up as rotating and zooming repeatedly with the touchpad will make the cursor get back to normal eventually. WORKAROUND: use keboard gesture to zoom in/out [Alt + spacebar + cursor drag] -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #6 from Rob --- Created attachment 118792 --> https://bugs.kde.org/attachment.cgi?id=118792=edit successful terminal run what should happen in the terminal if everything works correctly. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #5 from Rob --- Created attachment 118791 --> https://bugs.kde.org/attachment.cgi?id=118791=edit command location where to get the command for the terminal -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #4 from Rob --- Created attachment 118790 --> https://bugs.kde.org/attachment.cgi?id=118790=edit terminal window The terminal window during the command -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #3 from Rob --- To find out what is wrong, you will need to run a test on your astrometry setup. 1. Plate solve something, it can be a simulator image, it doesn't matter what. 2. Then did you see in the log where it printed the commands that it tried? Try running those from a terminal window. >From your Log these are the commands you should run. (You could copy and paste them to the terminal): export PATH=/Applications/kstars.app/Contents/MacOS/netpbm/bin:/Applications/kstars.app/Contents/MacOS/python/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin export PYTHONPATH=/Applications/kstars.app/Contents/MacOS/python/bin/site-packages /Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -3 351.405 -4 61.698 -5 30 --config /Applications/kstars.app/Contents/MacOS/astrometry/bin/astrometry.cfg -W /private/var/folders/l3/yznjwk917w9_f9qglkhkndprgn/T/solution.wcs /private/var/folders/l3/yznjwk917w9_f9qglkhkndprgn/T/fitstVCXWV.fits Just one note: the last part of the command where it says "/private/var/folders/l3/yznjwk917w9_f9qglkhkndprgn/T/fitstVCXWV.fits". That is a temporary file, so that is what you would need to change. (also probably the wcs file right before that) -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405437] Local astrometry server crashes after upgrading from KStars 2.9.8 to KStars 3.1.0, and 3.1.1 afterwards
https://bugs.kde.org/show_bug.cgi?id=405437 --- Comment #2 from Rob --- Can you run this from the command line on the latest version from the DMG to see what fails? This won't give us enough information to diagnose the issue on your system. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 405462] New: wrong display of annotation
https://bugs.kde.org/show_bug.cgi?id=405462 Bug ID: 405462 Summary: wrong display of annotation Product: okular Version: 1.3.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: gassa...@kde.org Target Milestone: --- Created attachment 118789 --> https://bugs.kde.org/attachment.cgi?id=118789=edit difference between display of okular and adobe SUMMARY Open a pdf file from a business partner okular displays "DRAFT" (over "Sign here") acoread displays "Sign here" I can provide the file on demand STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Ubuntu 18.04 KDE Frameworks 5.44.0 Qt 5.9.5 (built against 5.9.5) The xcb windowing system okular: version 1.3.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 253657] missing some amd64 to let wine/amd64 run on valgrind/amd64
https://bugs.kde.org/show_bug.cgi?id=253657 --- Comment #23 from Daniel Lehman --- > 0030:err:seh:NtRaiseException Unhandled exception code c01d flags 0 addr > 0x7bc95b63 that's probably the iretq instruction from set_cpu_context > What VALGRIND_OPTS are you using? -v --trace-children=yes --error-limit=no --log-file=output.txt --leak-check=full --leak-resolution=high --show-leak-kinds=all > did I miss a step? no, sorry, i forgot that i had to create a symlink to find the pdb: ln -s $HOME $WINEPREFIX/drive_Y because the baked-in path is Y:/stuff/leakage -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 405461] New: Save dialog crashes when making 3 nested folders
https://bugs.kde.org/show_bug.cgi?id=405461 Bug ID: 405461 Summary: Save dialog crashes when making 3 nested folders Product: kate Version: 18.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: quantumpha...@gmail.com Target Milestone: --- Application: kate (18.12.3) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.18.0-15-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: I was saving a new file to a buildroot rootfs overlay and needed to make a `rootfs_overlay/etc/init.d` directory. Furthur testing leads to it crashing when making new folder after new folder. - Steps to reproduce: 1. Open a new file in Kate 2. Save as 3. Navigate to `/tmp/` 4. New folder test1 5. New folder test2 6. New folder test3 7. Segfault The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe616d0f840 (LWP 21241))] Thread 33 (Thread 0x7fe5677fe700 (LWP 8911)): #0 0x7fe6115d5bf9 in __GI___poll (fds=0x560c4e13e560, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe60b06a539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe60b06a8d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe57cd2a026 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fe60b092105 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe60cfee6db in start_thread (arg=0x7fe5677fe700) at pthread_create.c:463 #6 0x7fe6115e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7fe567fff700 (LWP 8910)): #0 0x7fe6115d10b4 in __GI___libc_read (fd=46, buf=0x7fe567ffeca0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fe60b0aecd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe60b06a027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe60b06a4e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe60b06a64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe60b06a691 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fe60b092105 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fe60cfee6db in start_thread (arg=0x7fe567fff700) at pthread_create.c:463 #8 0x7fe6115e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fe57d7fa700 (LWP 30196)): #0 0x7fe60cff49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560c4cbd0ea4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe60cff49f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x560c4cbd0e50, cond=0x560c4cbd0e78) at pthread_cond_wait.c:502 #2 0x7fe60cff49f3 in __pthread_cond_wait (cond=0x560c4cbd0e78, mutex=0x560c4cbd0e50) at pthread_cond_wait.c:655 #3 0x7fe611ce9b4b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe611ce9e59 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe5ed7e6935 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fe5ed7ea7e8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fe5ed7e5bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fe5ed7ea842 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fe5ed7e5bfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fe5ed7e86ab in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fe611ce2bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fe60cfee6db in start_thread (arg=0x7fe57d7fa700) at pthread_create.c:463 #13 0x7fe6115e288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fe57dffb700 (LWP 30195)): #0 0x7fe60cff49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x560c4cbd0ea4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe60cff49f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x560c4cbd0e50, cond=0x560c4cbd0e78) at pthread_cond_wait.c:502 #2 0x7fe60cff49f3 in __pthread_cond_wait (cond=0x560c4cbd0e78, mutex=0x560c4cbd0e50) at pthread_cond_wait.c:655 #3 0x7fe611ce9b4b in
[kde] [Bug 405460] New: error while loading shared libraries: libdouble-conversion.so.3.0.0
https://bugs.kde.org/show_bug.cgi?id=405460 Bug ID: 405460 Summary: error while loading shared libraries: libdouble-conversion.so.3.0.0 Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mariana...@icloud.com Target Milestone: --- SUMMARY The upgrade from Plasma 5.15.2 to 5.15.3 made starting KDE impossible because of a wrong call to libdouble-conversion.so.3.0.0 which does not exist. Instead the existing symlink to the latest updated library is called /usr/lib/libdouble-conversion.so.3 without any zeros. Changing the name of the symlink to /usr/lib/libdouble-conversion.so.3.0.0 and adjusting the symlink /usr/lib/libdouble-conversion.so would remedy this temporarily. KDE should make the right call to the original symlink though. STEPS TO REPRODUCE 1. Update KDE Plasma desktop from 5.15.2 to 5.15.3 2. Reboot 3. Start X OBSERVED RESULT X will error out stating "Could not start kdeinit5. Check your installation." and return to the console. EXPECTED RESULT X should start normally without errors. SOFTWARE/OS VERSIONS Linux: 5.0.0-arch1-1-ARCH KDE Plasma Version: 5.15.3-1 KDE Frameworks Version: 5.56.1-1 Qt Version: 5.12.1-2 UPDATED PACKAGES: [2019-03-13 17:52] [ALPM] upgraded double-conversion (3.1.1-1 -> 3.1.4-1) [2019-03-13 17:52] [ALPM] upgraded bluedevil (1:5.15.2-1 -> 1:5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kdecoration (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded breeze (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded breeze-gtk (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded protobuf (3.6.1.3-1 -> 3.7.0-1) [2019-03-13 17:52] [ALPM] upgraded clementine (1.3.1-20 -> 1.3.1-21) [2019-03-13 17:52] [ALPM] upgraded kirigami2 (5.56.0-2 -> 5.56.1-1) [2019-03-13 17:52] [ALPM] upgraded discover (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded drkonqi (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded gtk-update-icon-cache (3.24.5-1 -> 3.24.7-1) [2019-03-13 17:52] [ALPM] upgraded gtk3 (3.24.5-1 -> 3.24.7-1) [2019-03-13 17:52] [ALPM] upgraded kactivitymanagerd (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kde-cli-tools (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded libksysguard (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-framework (5.56.0-3 -> 5.56.1-1) [2019-03-13 17:52] [ALPM] upgraded milou (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kwin (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-integration (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-workspace (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kdeplasma-addons (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kgamma5 (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded khotkeys (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kinfocenter (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kmenuedit (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded knetattach (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded libkscreen (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kscreen (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded ksshaskpass (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded ksysguard (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kwallet-pam (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kwayland-integration (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded kwrited (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded oxygen (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-browser-integration (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded polkit-kde-agent (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded systemsettings (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-desktop (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-nm (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-pa (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-sdk (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-vault (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded plasma-workspace-wallpapers (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded powerdevil (5.15.2-2 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded python-psutil (5.5.0-1 -> 5.6.0-1) [2019-03-13 17:52] [ALPM] upgraded sddm-kcm (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded user-manager (5.15.2-1 -> 5.15.3-1) [2019-03-13 17:52] [ALPM] upgraded xdg-desktop-portal-kde (5.15.2-1 -> 5.15.3-1) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action
https://bugs.kde.org/show_bug.cgi?id=405450 --- Comment #4 from Christoph Feck --- Truth is, Kwin developers are already swamped with bug reports (either valid, or invalid, because they are vendor driver specific). Adding more options to KWin will only increase maintainance burden. Unless you want to step up and implement and maintain the added code for new features, there is little point in piling up more feature requests in bugzilla. That might come as a surprise, but considering the experiences made in the last years, there is no other option. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399863] segfault when repeatedly sorting
https://bugs.kde.org/show_bug.cgi?id=399863 --- Comment #4 from Walter Lapchynski --- Oh and I'm not super familiar with ASan but if I grok the docs correctly, a simple -fsanitize=address to cmake should make things work and I didn't really notice anything different. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399863] segfault when repeatedly sorting
https://bugs.kde.org/show_bug.cgi?id=399863 --- Comment #3 from Walter Lapchynski --- After some further testing that involved increasing the memory allocation on the VMs I was using, I found that there seems to be some relationship between the amount of messages required to trigger it and the amount of memory. It's probably based more on size of messages (or mailbox/folder) rather than individual numbers of messages from what I can tell. Anyways, similar backtrace with b94f4307. Thread 1 "trojita" received signal SIGSEGV, Segmentation fault. 0x73eeda82 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 (gdb) backs[Ktrace full #0 0x73eeda82 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x73eee056 in QSortFilterProxyModel::flags(QModelIndex const&) const () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x74b3fc71 in QTreeView::isExpanded(QModelIndex const&) const () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #3 0x74b4ace5 in QTreeView::verticalScrollbarValueChanged(int) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #4 0x74ad9d5f in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x73f3f5c6 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x749778ae in QAbstractSlider::valueChanged(int) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x74977f14 in QAbstractSlider::setValue(int) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x73f3f703 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x74887f62 in QAction::toggled(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7488a3b0 in QAction::setChecked(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7488b79a in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7488bc81 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x73f3f5c6 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x74889a2e in QActionPrivate::sendDataChanged() () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7488a397 in QAction::setChecked(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x73f3f703 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x5578451c in Imap::Mailbox::PrettyMsgListModel::sortingPreferenceChanged(int, Qt::SortOrder) (this=this@entry=0x55c80630, _t1=, _t1@entry=2, _t2=, _t2@entry=Qt::AscendingOrder) at /home/lubuntu/trojita/_build/Imap_autogen/I7YDGANZM2/moc_PrettyMsgListModel.cpp:131 _a = {0x0, 0x7fffca2c, 0x7fffca28} #18 0x55735ff3 in Imap::Mailbox::PrettyMsgListModel::sort(int, Qt::SortOrder) (this=0x55c80630, column=2, order=Qt::AscendingOrder) at /home/lubuntu/trojita/src/Imap/Model/PrettyMsgListModel.cpp:244 threadingModel = criterium = Imap::Mailbox::ThreadingMsgListModel::SORT_FROM willSort = true #19 0x73f3f5c6 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x74ae536f in QHeaderView::sortIndicatorChanged(int, Qt::SortOrder) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x74aee975 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x74aeebfa in QHeaderView::mouseReleaseEvent(QMouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x748cc748 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7496ff4e in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x74ae149b in QAbstractItemView::viewportEvent(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x74af038b in QHeaderView::viewportEvent(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x73f1618b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7488e481 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x74895d08 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x73f16479 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x74895019 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x748e7264 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x748e9dee in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7488e491 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x74895ac0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36
[plasma-pa] [Bug 405459] New: Adding possibility to control volume and music via bluetooth headphones
https://bugs.kde.org/show_bug.cgi?id=405459 Bug ID: 405459 Summary: Adding possibility to control volume and music via bluetooth headphones Product: plasma-pa Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: sh...@paranoici.org CC: plasma-b...@kde.org Target Milestone: --- Hi, my bluetooth headphones when are connected with android smartphone allow to control phone remotely. Like change volume of sound, pause and resume, also start next song. It'd be superb to have something like this in plasma. :) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405458] New: MIPS mkFormVEC arguments swapped?
https://bugs.kde.org/show_bug.cgi?id=405458 Bug ID: 405458 Summary: MIPS mkFormVEC arguments swapped? Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: m...@klomp.org CC: mips3...@gmail.com Target Milestone: --- The following function in VEX/priv/host_mips_defs.c static UChar *mkFormVEC(UChar *p, UInt op, UInt ws, UInt wt, UInt wd) { UInt theInstr; vassert(op < 0x20); vassert(wt < 0x20); vassert(ws < 0x20); vassert(wd < 0x20); theInstr = OPC_MSA | (op << 21) | (wt << 16) | (ws << 11) | (wd << 6) | 0x1E; return emit32(p, theInstr); } And the use in: case Msa_VEC: { UInt v_wt = qregEnc(i->Min.MsaVec.wt); UInt v_ws = qregEnc(i->Min.MsaVec.ws); UInt v_wd = qregEnc(i->Min.MsaVec.wd); p = mkFormVEC(p, i->Min.MsaVec.op, v_wt, v_ws, v_wd); goto done; } Looks like they swap the arguments wt and ws. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405381] Mouse pointer gets fixed to a move symbol just after drag and drop media from the clip monitor to timeline
https://bugs.kde.org/show_bug.cgi?id=405381 --- Comment #3 from ksy20...@chollian.net --- (In reply to emohr from comment #1) > To test: > - open a new project. > - Hit CTR+SHIFT+, (comma) and tick under Misc “Check if first added clip > matches project profile”. > - Insert your video again. > - Now the project gets adjusted to the video you have. > > If you have still the crash: > - View -> make sure “clip properties” is hit. > > Please post a screenshot here of the properties of the clip which causes he > crash. Thanks for the reply, but this is not about a crash. Any video clip (even generated within Kdenlive) can always have this symptom. Please refer to the attached screenshot(a video actually). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405381] Mouse pointer gets fixed to a move symbol just after drag and drop media from the clip monitor to timeline
https://bugs.kde.org/show_bug.cgi?id=405381 --- Comment #2 from ksy20...@chollian.net --- Created attachment 118788 --> https://bugs.kde.org/attachment.cgi?id=118788=edit Reproduce demo movie clip I added a movie clip for demo. Please notice the mouse pointer in the movie especially just after the dragged clip dropped on the timeline. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 405276] Unable to switch television channels by shortcuts
https://bugs.kde.org/show_bug.cgi?id=405276 --- Comment #2 from higuita --- Updating with a little more info Starting kaffeine with -d do not show anything useful While playing a channel, doing qdbus org.mpris.kaffeine /Player Prev qdbus org.kde.kaffeine /Player Prev Doesn't do anything, nor pressing page-up (or Next/page down) but doing qdbus org.mpris.kaffeine /Player Stop qdbus org.mpris.kaffeine /MainApplication quit do work fine (org.kde.kaffeine also work) i'm using libvlc backend and i tried to followed the code until VlcMediaWidget::jumpToNextChapter(), but yep, i'm totally lost! :D -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405457] New: export doesn't happen
https://bugs.kde.org/show_bug.cgi?id=405457 Bug ID: 405457 Summary: export doesn't happen Product: kdenlive Version: 18.12.1 Platform: Other OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: gionata.pri...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Just export the project. 2. 3. OBSERVED RESULT The export starts and ends instantly, without producing any file and without saying any error message. It doesn't depend on the parameters, I tried in every format, in every directory. Restarting kdenlive doesn't work, not even restarting the pc. I already tried changing the name to the "kdenliverc" file in "appdata/local" directory and opening kdenlive again, like you told me sometime ago for another bug. Initially it seemed to work but soon after the first export it does it again. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372555] Input Device - Mouse - Reverse scroll direction Not Working
https://bugs.kde.org/show_bug.cgi?id=372555 Veps changed: What|Removed |Added CC||v...@gmx.de --- Comment #14 from Veps --- Plasma: 5.8.6 Framework: 5.28.0 Qt: 5.7.1 Bug still present. Checkbox in System Settings->Hardware->Input Devices->Mouse has no effect: checked or unchecked, no difference. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404617] KWin Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=404617 --- Comment #8 from Arjun Menon --- I can't reproduce this bug anymore. After I update all my packages, KWin stopped crashing, and Plasma started crashing instead: https://bugs.kde.org/show_bug.cgi?id=405406 But as two people pointed out, the source of these troubles is the proprietary Nvidia driver. I uninstalled the Nvidia driver; and now everything (ie. Nouveau) works perfectly! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 --- Comment #12 from Maik Qualmann --- This is just a quick fix. I do not close the bug yet, because I want to improve the function even more. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405406] Plasma Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=405406 --- Comment #2 from Arjun Menon --- You are right. This bug was fixed after I uninstalled the proprietary Nvidia driver! Hurray! Nouveau is doing its job well! I'm so happy. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 --- Comment #11 from Maik Qualmann --- Git commit c2d993ef70086ee518be04f7175835774493b0d5 by Maik Qualmann. Committed on 13/03/2019 at 22:28. Pushed by mqualmann into branch 'master'. quick fix for the album path problem M +1-1core/libs/database/collection/collectionmanager_album.cpp https://commits.kde.org/digikam/c2d993ef70086ee518be04f7175835774493b0d5 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405456] New: Search for custom header fails with inconclusive error message
https://bugs.kde.org/show_bug.cgi?id=405456 Bug ID: 405456 Summary: Search for custom header fails with inconclusive error message Product: kmail2 Version: 5.7.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: quaz...@posteo.de Target Milestone: --- Created attachment 118787 --> https://bugs.kde.org/attachment.cgi?id=118787=edit Screenshot of the error message # SUMMARY Trying to search (with "s") for a custom header field fails with an error message. # STEPS TO REPRODUCE 1. Open search dialog (see screenshot). 2. In the "Choose or type..." field, enter your desired header, e.g. "X-MyHeaderField". 3. In the value field, enter your desired value. 4. Press "Search" button # OBSERVED RESULT An error message appears: "Search failed some errors were found: You forgot to add conditions." # EXPECTED RESULT Search for messages with the expected condition. # SOFTWARE/OS VERSIONS Distro: Ubuntu 18.04.2 LTS Qt: 5.9.5 KDE: 5.44.0 # ADDITIONAL INFORMATION This would be a workaround for me until bug #283020 is implemented. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 405455] New: Replace smileys with emojis
https://bugs.kde.org/show_bug.cgi?id=405455 Bug ID: 405455 Summary: Replace smileys with emojis Product: kmail2 Version: 5.7.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: debianign...@gmx.de Target Milestone: --- Created attachment 118786 --> https://bugs.kde.org/attachment.cgi?id=118786=edit My try to match UTF-8 emojis to KMail smileys SUMMARY In the composer window there is a "Add Smiley" button which only works when the message is being composed as rich-text format. Since UTF-8 is continually expanded with emojis and is supported by every self-respecting platform, my suggestion is to replace those smileys with UTF-8 emojis which would make them available for plaintext mails, too. STEPS TO REPRODUCE 1. Compose a new e-mail 2. Disable rich-text format 3. Click the "Add smiley" button OBSERVED RESULT The button is greyed out and therefore doesn't work. EXPECTED RESULT The button unfolds a menu with a set of emoticons which are inserted as UTF-8 emojis when clicked. The recipient's client can display them without further interpretation (unlike classic smileys). SOFTWARE/OS VERSIONS Linux/KDE Plasma: 4.20.6/5.14.5 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION In the attachment you'll find some UTF-8 equivalents to the smileys in the Smiley menu, the ones I couldn't find are marked with X. The "tofus" are the one which are too new in UTF-8 and can't be displayed even using the Noto Sans font. Last but not least I added some suggestions which I think are used quite often and therefore would fit well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405454] Desktop names don't appear in the pager applet, only "..."
https://bugs.kde.org/show_bug.cgi?id=405454 David Faure changed: What|Removed |Added Summary|Pager too small for desktop |Desktop names don't appear |names to appear |in the pager applet, only ||"..." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405454] New: Pager too small for desktop names to appear
https://bugs.kde.org/show_bug.cgi?id=405454 Bug ID: 405454 Summary: Pager too small for desktop names to appear Product: plasmashell Version: 5.15.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: fa...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 118785 --> https://bugs.kde.org/attachment.cgi?id=118785=edit screenshot of pager applet SUMMARY The pager option to show desktop names doesn't actually show desktop names, on most setups, for lack of space (applet too small, font too big --> only "..." appears). STEPS TO REPRODUCE 1. Configure multiple virtual desktops 2. Add pager applet to panel 3. Configure pager 4. Click on "Display: Desktop Name" OBSERVED RESULT See screenshot attached. The names don't appear, only "..." Obviously the applet needs to be bigger for the names to appear. EXPECTED RESULT I can make the names appear if I make my panel HUGE (in terms of height). It would be much better if the names used a smaller font when there isn't enough room. And the applet could take more space horizontally. There doesn't seem to be a way to change the width of the applet, other than by increasing the height. How does that work? Constant aspect ratio or something? According to my wife who has good memory, this used to work better some versions ago, the text was visible on panels with a reasonable height. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.0 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action
https://bugs.kde.org/show_bug.cgi?id=405450 --- Comment #3 from pmarget...@gmail.com --- ...cont. Furthermore, you allow Double click: minimize action (which can't be undone in the same way), Minimize is also in the list for Left, Middle and Right buttons, and you can even have it activate on Window Actions->Inner Window,Titlebar & Frame in combination with a modifier key. So why is wheel action an exception all of a sudden? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action
https://bugs.kde.org/show_bug.cgi?id=405450 --- Comment #2 from pmarget...@gmail.com --- (In reply to Martin Flöser from comment #1) >It makes zero sense to also include minimize in it. If a window isn't maxized, it would make sense that mouse wheel down minimizes it. What's your argument for why exactly it makes zero sense? >Even more minimize in that list would be unacceptable as it's an action > which cannot be reversed in the same way. Is this a KDE design principle written somewhere? There are other ways to restore a minimized window: alt-tabbing, task manager... -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 405278] [feature request] EPG from xmltv
https://bugs.kde.org/show_bug.cgi?id=405278 --- Comment #15 from higuita --- > I'm aware - although here, EPG data is reliable for most channels and there's > no xmltv grabber for Brazilian channels - AFAIKT. Well, here the normal DVB-T do have good EPG, but i have fiber cable, that give all the channels using a operator tv box, also with EPG (and other features, like recording, rent movies, etc). That box (actually the router in my setup) also injecting in the home coax network about 60 analog channels and 60 DVB-T channels (mostly duplicated) for any other TV in the house without using the operator box. Are this "internal distribution" channels that lack the EPG. Using a tv card i can use tvtime to see the analog signal and a dvb-t card for the digital feed. the xmltv grabber for my operator, was i that studied their tv guid website and created a shell script to generate it. Later another guy used my findings and build a proper xmltv grabber > You don't need to go to the channel's config window. Just open the EPG guide > from the TV menu. All channels with EPG are there. yep, i found that, but that show the ones that DO have EPG... finding the ones without still forces one to list all channels and manually remove the ones that are missing. This feature can be in the EPG guide too, by default show only EGP channels (the current way) and pressing some bottom or checkbox, show all channels, even ones without EPG >> Sadly i do not know how to program, so i can't really helping develop this :) > That's a good opportunity to learn :-) I actually want to learn, but something more simple like python or go... c++, i have problems even trying to read it, probably because everything that uses c++ is already way too big for me to understand :D -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 Maik Qualmann changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #10 from Maik Qualmann --- Thank you for the log file. I can reproduce the problem not only under Windows but also under Linux. The cause is that both collections start with the same name. The bad function is CollectionManager::album(QString). I will fix it tomorrow. @Gilles, this Windows computer also takes almost 35 seconds to load the plugins. It's up to the size of the plugins, maybe we should provide a 64 bit version without a debug code. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 367480] baloo_file crashes in Baloo::PostingCodec::decode
https://bugs.kde.org/show_bug.cgi?id=367480 Nate Graham changed: What|Removed |Added Summary|Crash inside|baloo_file crashes in |Baloo::PostingCodec::decode |Baloo::PostingCodec::decode -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 405215] Nothing happens when "Change permissions..." button is clicked in K3b settings
https://bugs.kde.org/show_bug.cgi?id=405215 --- Comment #2 from Antonio Rojas --- And how are packagers supposed to know that a feature is broken and should not be enabled, if it is nowhere mentioned? With this option disabled, one gets a useless settings pane where one can check and uncheck stuff with no visible way to apply changes - so either way, it looks broken. This should either be fixed, or the permissions settings tab completely removed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 403720] Baloo crashes at KDE session start.
https://bugs.kde.org/show_bug.cgi?id=403720 --- Comment #3 from Valerii Malov --- Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov. Committed on 13/03/2019 at 21:50. Pushed by valeriymalov into branch 'master'. Baloo engine: treat every non-success code as a failure Summary: Treating only MDB_NOTFOUND as an error leads to use of uninitliazed pointers and handle IDs in other cases (e.g. when get fails with MDB_BAD_TXN) and wreaks havoc in the application. Related: bug 361186, bug 390823, bug 372880, bug 395888, bug 367480 Reviewers: #baloo, bruns, poboiko Reviewed By: #baloo, bruns Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D18664 M +12 -9src/engine/database.cpp M +26 -17 src/engine/documentdatadb.cpp M +30 -22 src/engine/documentdb.cpp M +30 -22 src/engine/documentiddb.cpp M +25 -16 src/engine/documenttimedb.cpp M +0-1src/engine/documenturldb.cpp M +4-3src/engine/documenturldb.h M +4-5src/engine/fsutils.cpp M +28 -15 src/engine/idfilenamedb.cpp M +22 -13 src/engine/idtreedb.cpp M +37 -29 src/engine/mtimedb.cpp M +0-2src/engine/phraseanditerator.cpp M +24 -19 src/engine/positiondb.cpp M +31 -27 src/engine/postingdb.cpp M +47 -13 src/engine/transaction.cpp M +4-4src/engine/transaction.h M +3-2src/file/extractorprocess.cpp M +5-5src/file/fileindexscheduler.cpp M +5-4src/file/indexcleaner.cpp M +0-1src/file/main.cpp M +1-1src/file/metadatamover.cpp https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 367480] Crash inside Baloo::PostingCodec::decode
https://bugs.kde.org/show_bug.cgi?id=367480 --- Comment #136 from Valerii Malov --- Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov. Committed on 13/03/2019 at 21:50. Pushed by valeriymalov into branch 'master'. Baloo engine: treat every non-success code as a failure Summary: Treating only MDB_NOTFOUND as an error leads to use of uninitliazed pointers and handle IDs in other cases (e.g. when get fails with MDB_BAD_TXN) and wreaks havoc in the application. Related: bug 361186, bug 390823, bug 372880, bug 395888, bug 403720 Reviewers: #baloo, bruns, poboiko Reviewed By: #baloo, bruns Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D18664 M +12 -9src/engine/database.cpp M +26 -17 src/engine/documentdatadb.cpp M +30 -22 src/engine/documentdb.cpp M +30 -22 src/engine/documentiddb.cpp M +25 -16 src/engine/documenttimedb.cpp M +0-1src/engine/documenturldb.cpp M +4-3src/engine/documenturldb.h M +4-5src/engine/fsutils.cpp M +28 -15 src/engine/idfilenamedb.cpp M +22 -13 src/engine/idtreedb.cpp M +37 -29 src/engine/mtimedb.cpp M +0-2src/engine/phraseanditerator.cpp M +24 -19 src/engine/positiondb.cpp M +31 -27 src/engine/postingdb.cpp M +47 -13 src/engine/transaction.cpp M +4-4src/engine/transaction.h M +3-2src/file/extractorprocess.cpp M +5-5src/file/fileindexscheduler.cpp M +5-4src/file/indexcleaner.cpp M +0-1src/file/main.cpp M +1-1src/file/metadatamover.cpp https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 372880] baloo_file crashes in Baloo::IdFilenameDB::get()
https://bugs.kde.org/show_bug.cgi?id=372880 --- Comment #9 from Valerii Malov --- Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov. Committed on 13/03/2019 at 21:50. Pushed by valeriymalov into branch 'master'. Baloo engine: treat every non-success code as a failure Summary: Treating only MDB_NOTFOUND as an error leads to use of uninitliazed pointers and handle IDs in other cases (e.g. when get fails with MDB_BAD_TXN) and wreaks havoc in the application. Related: bug 361186, bug 390823, bug 395888, bug 367480, bug 403720 Reviewers: #baloo, bruns, poboiko Reviewed By: #baloo, bruns Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D18664 M +12 -9src/engine/database.cpp M +26 -17 src/engine/documentdatadb.cpp M +30 -22 src/engine/documentdb.cpp M +30 -22 src/engine/documentiddb.cpp M +25 -16 src/engine/documenttimedb.cpp M +0-1src/engine/documenturldb.cpp M +4-3src/engine/documenturldb.h M +4-5src/engine/fsutils.cpp M +28 -15 src/engine/idfilenamedb.cpp M +22 -13 src/engine/idtreedb.cpp M +37 -29 src/engine/mtimedb.cpp M +0-2src/engine/phraseanditerator.cpp M +24 -19 src/engine/positiondb.cpp M +31 -27 src/engine/postingdb.cpp M +47 -13 src/engine/transaction.cpp M +4-4src/engine/transaction.h M +3-2src/file/extractorprocess.cpp M +5-5src/file/fileindexscheduler.cpp M +5-4src/file/indexcleaner.cpp M +0-1src/file/main.cpp M +1-1src/file/metadatamover.cpp https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 395888] baloo_file crashes in Baloo::DocTermsCodec::decode()
https://bugs.kde.org/show_bug.cgi?id=395888 --- Comment #4 from Valerii Malov --- Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov. Committed on 13/03/2019 at 21:50. Pushed by valeriymalov into branch 'master'. Baloo engine: treat every non-success code as a failure Summary: Treating only MDB_NOTFOUND as an error leads to use of uninitliazed pointers and handle IDs in other cases (e.g. when get fails with MDB_BAD_TXN) and wreaks havoc in the application. Related: bug 361186, bug 390823, bug 372880, bug 367480, bug 403720 Reviewers: #baloo, bruns, poboiko Reviewed By: #baloo, bruns Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D18664 M +12 -9src/engine/database.cpp M +26 -17 src/engine/documentdatadb.cpp M +30 -22 src/engine/documentdb.cpp M +30 -22 src/engine/documentiddb.cpp M +25 -16 src/engine/documenttimedb.cpp M +0-1src/engine/documenturldb.cpp M +4-3src/engine/documenturldb.h M +4-5src/engine/fsutils.cpp M +28 -15 src/engine/idfilenamedb.cpp M +22 -13 src/engine/idtreedb.cpp M +37 -29 src/engine/mtimedb.cpp M +0-2src/engine/phraseanditerator.cpp M +24 -19 src/engine/positiondb.cpp M +31 -27 src/engine/postingdb.cpp M +47 -13 src/engine/transaction.cpp M +4-4src/engine/transaction.h M +3-2src/file/extractorprocess.cpp M +5-5src/file/fileindexscheduler.cpp M +5-4src/file/indexcleaner.cpp M +0-1src/file/main.cpp M +1-1src/file/metadatamover.cpp https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390823] baloo_file crashes in Baloo::IdTreeDB::get()
https://bugs.kde.org/show_bug.cgi?id=390823 --- Comment #1 from Valerii Malov --- Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov. Committed on 13/03/2019 at 21:50. Pushed by valeriymalov into branch 'master'. Baloo engine: treat every non-success code as a failure Summary: Treating only MDB_NOTFOUND as an error leads to use of uninitliazed pointers and handle IDs in other cases (e.g. when get fails with MDB_BAD_TXN) and wreaks havoc in the application. Related: bug 361186, bug 372880, bug 395888, bug 367480, bug 403720 Reviewers: #baloo, bruns, poboiko Reviewed By: #baloo, bruns Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D18664 M +12 -9src/engine/database.cpp M +26 -17 src/engine/documentdatadb.cpp M +30 -22 src/engine/documentdb.cpp M +30 -22 src/engine/documentiddb.cpp M +25 -16 src/engine/documenttimedb.cpp M +0-1src/engine/documenturldb.cpp M +4-3src/engine/documenturldb.h M +4-5src/engine/fsutils.cpp M +28 -15 src/engine/idfilenamedb.cpp M +22 -13 src/engine/idtreedb.cpp M +37 -29 src/engine/mtimedb.cpp M +0-2src/engine/phraseanditerator.cpp M +24 -19 src/engine/positiondb.cpp M +31 -27 src/engine/postingdb.cpp M +47 -13 src/engine/transaction.cpp M +4-4src/engine/transaction.h M +3-2src/file/extractorprocess.cpp M +5-5src/file/fileindexscheduler.cpp M +5-4src/file/indexcleaner.cpp M +0-1src/file/main.cpp M +1-1src/file/metadatamover.cpp https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 361186] baloo_file crashes in Baloo::PositionDB::get()
https://bugs.kde.org/show_bug.cgi?id=361186 --- Comment #6 from Valerii Malov --- Git commit eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d by Valerii Malov. Committed on 13/03/2019 at 21:50. Pushed by valeriymalov into branch 'master'. Baloo engine: treat every non-success code as a failure Summary: Treating only MDB_NOTFOUND as an error leads to use of uninitliazed pointers and handle IDs in other cases (e.g. when get fails with MDB_BAD_TXN) and wreaks havoc in the application. Related: bug 390823, bug 372880, bug 395888, bug 367480, bug 403720 Reviewers: #baloo, bruns, poboiko Reviewed By: #baloo, bruns Subscribers: cullmann, ngraham, bruns, kde-frameworks-devel, #baloo Tags: #frameworks, #baloo Differential Revision: https://phabricator.kde.org/D18664 M +12 -9src/engine/database.cpp M +26 -17 src/engine/documentdatadb.cpp M +30 -22 src/engine/documentdb.cpp M +30 -22 src/engine/documentiddb.cpp M +25 -16 src/engine/documenttimedb.cpp M +0-1src/engine/documenturldb.cpp M +4-3src/engine/documenturldb.h M +4-5src/engine/fsutils.cpp M +28 -15 src/engine/idfilenamedb.cpp M +22 -13 src/engine/idtreedb.cpp M +37 -29 src/engine/mtimedb.cpp M +0-2src/engine/phraseanditerator.cpp M +24 -19 src/engine/positiondb.cpp M +31 -27 src/engine/postingdb.cpp M +47 -13 src/engine/transaction.cpp M +4-4src/engine/transaction.h M +3-2src/file/extractorprocess.cpp M +5-5src/file/fileindexscheduler.cpp M +5-4src/file/indexcleaner.cpp M +0-1src/file/main.cpp M +1-1src/file/metadatamover.cpp https://commits.kde.org/baloo/eb68430ae5f4fc4c4a2e5b1798683ff6a639ad3d -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 405452] [refactoring_timeline] Latest git version crashes when adding anything to the timeline
https://bugs.kde.org/show_bug.cgi?id=405452 JORGETECH changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 405419] Tajikistan Map Update
https://bugs.kde.org/show_bug.cgi?id=405419 --- Comment #1 from Albert Astals Cid --- https://en.wikipedia.org/wiki/Regions_of_Tajikistan seems to agree with what we have maybe what you want is in addition to the regions map to have a districts map? -- You are receiving this mail because: You are watching all bug changes.
[step] [Bug 405453] New: Massive memory usage in STEP
https://bugs.kde.org/show_bug.cgi?id=405453 Bug ID: 405453 Summary: Massive memory usage in STEP Product: step Version: 0.1.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: ks.vladi...@gmail.com Reporter: franci_n...@hotmail.it Target Milestone: --- SUMMARY When I modify the settings for the collision solver, the risk of a colossal memory usage is serious. More than 5 GB will be used if tolerance is set to 0.01. That is not a problem when you have more than 5 GB of free space, but unfortunately this is not my case. I think it would be a good idea if a message of warning appeared before starting the simulation. STEPS TO REPRODUCE 1. Create a circle of infinite mass 2. Create a particle that will collide with the circle. 3. Before starting the simulation, set the tollerances of the solver1 and the collision solver to very low value. 4. Start simulation. OBSERVED RESULT 5 GB of internal memory is used (in my case this means a full memory occupation), and my computer become very slow even after the crash of step. The only way to go back to normality is reboot and free memory by command line. EXPECTED RESULT Before starting the simulation, a warning message should appear, like "You are going to waste 5 GB of your memory, are you sure? If not, change tolerance parameters." SOFTWARE/OS VERSIONS Linux 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 405420] North Macedonia+Eswatini Update
https://bugs.kde.org/show_bug.cgi?id=405420 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/kge ||ography/51b49cea779f114c0bf ||662826e19d104eda21cc9 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Albert Astals Cid --- Git commit 51b49cea779f114c0bf662826e19d104eda21cc9 by Albert Astals Cid. Committed on 13/03/2019 at 21:29. Pushed by aacid into branch 'master'. Swaziland renamed themselves to Eswatini M +1-1data/africa.kgm M +1-1data/world.kgm https://commits.kde.org/kgeography/51b49cea779f114c0bf662826e19d104eda21cc9 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 214110] "Preload an instance" option for Dolphin
https://bugs.kde.org/show_bug.cgi?id=214110 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 405420] North Macedonia+Eswatini Update
https://bugs.kde.org/show_bug.cgi?id=405420 --- Comment #1 from Albert Astals Cid --- North Macedonia was fixed on Feb 18 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 138956] KDE 5: low level API to control scrolling
https://bugs.kde.org/show_bug.cgi?id=138956 --- Comment #7 from Thomas Friedrichsmeier --- Frankly, I'm not sure, I understand that PR. However, to clarify, my (somewhat esoteric) usecase: 1) User selects something near the top of the document, implicitly changing cursor position. 2) I need to set the cursor back to the very end of the document (not editing anything, though). I would like to have a way to accomplish step 2 *without* apparent scrolling, i.e. the view should remain scrolled where ever it was scrolled to by the user. It should not jump to make last line visible. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 405452] New: [refactoring_timeline] Latest git version crashes when adding anything to the timeline
https://bugs.kde.org/show_bug.cgi?id=405452 Bug ID: 405452 Summary: [refactoring_timeline] Latest git version crashes when adding anything to the timeline Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jorgesan...@gmail.com Target Milestone: --- Application: kdenlive (19.03.70) Qt Version: 5.11.1 Frameworks Version: 5.54.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: As the title says if you add anything to the timeline the application crashes The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc32af8a940 (LWP 17977))] Thread 37 (Thread 0x7fc26a7fd700 (LWP 18039)): #0 0x7fc335f826d9 in __GI___poll (fds=0x563e89751290, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc330b35e46 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc330b35f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc33664c15b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc3365f916b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc3364480b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc337538396 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fc336451c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc334c5c164 in start_thread (arg=) at pthread_create.c:486 #9 0x7fc335f8edef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 36 (Thread 0x7fc2c2ffd700 (LWP 18038)): #0 0x7fc335f53707 in getpid () at ../sysdeps/unix/syscall-template.S:60 #1 0x7fc3305afd3f in pa_detect_fork () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #2 0x7fc334ca7cdb in pa_stream_writable_size () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7fc30ce38d25 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #4 0x7fc30cd98836 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #5 0x7fc30cddf5ec in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #6 0x7fc30ce54f89 in () at /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0 #7 0x7fc334c5c164 in start_thread (arg=) at pthread_create.c:486 #8 0x7fc335f8edef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 35 (Thread 0x7fc2aaffd700 (LWP 18037)): #0 0x7fc334c622eb in futex_wait_cancelable (private=, expected=0, futex_word=0x563e8b6f625c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc334c622eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x563e8b6f6208, cond=0x563e8b6f6230) at pthread_cond_wait.c:502 #2 0x7fc334c622eb in __pthread_cond_wait (cond=0x563e8b6f6230, mutex=0x563e8b6f6208) at pthread_cond_wait.c:655 #3 0x7fc3381aaa93 in () at /usr/lib/x86_64-linux-gnu/libmlt.so.6 #4 0x563e7fa67b07 in RenderThread::run() (this=0x7fc2b709d5f0) at /home/jorgetech/Temp/kdenlive/src/monitor/glwidget.cpp:1559 #5 0x7fc336451c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc334c5c164 in start_thread (arg=) at pthread_create.c:486 #7 0x7fc335f8edef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 34 (Thread 0x7fc2c27fc700 (LWP 18036)): #0 0x7fc334c622eb in futex_wait_cancelable (private=, expected=0, futex_word=0x563e8c44ec18) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc334c622eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x563e8c44ec20, cond=0x563e8c44ebf0) at pthread_cond_wait.c:502 #2 0x7fc334c622eb in __pthread_cond_wait (cond=0x563e8c44ebf0, mutex=0x563e8c44ec20) at pthread_cond_wait.c:655 #3 0x7fc318490512 in () at /usr/lib/x86_64-linux-gnu/mlt/libmltsdl2.so #4 0x7fc334c5c164 in start_thread (arg=) at pthread_create.c:486 #5 0x7fc335f8edef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7fc2ed9a8700 (LWP 18035)): #0 0x7fc3305ddb4b in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #1 0x7fc3305dea6d in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #2 0x7fc3305dee19 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #3 0x7fc3305df66a in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #4 0x7fc334c9f568 in pa_mainloop_dispatch () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fc334c9f83c in pa_mainloop_iterate () at
[dolphin] [Bug 171743] Shortcut for moving between parts in Split View
https://bugs.kde.org/show_bug.cgi?id=171743 Hamidreza Jafari changed: What|Removed |Added CC|hamidrjaf...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 399863] segfault when repeatedly sorting
https://bugs.kde.org/show_bug.cgi?id=399863 --- Comment #2 from Walter Lapchynski --- One piece of information I failed to include: it seems to require at least 10 messages. -- You are receiving this mail because: You are watching all bug changes.
[buildsystem] [Bug 369554] sleeper design bug in the installation layout due to assumptions about filesystem case sensitivity
https://bugs.kde.org/show_bug.cgi?id=369554 --- Comment #10 from RJVB --- >Ah you're still confused by non-namespaced frameworks vs namespaced frameworks. Confused, no, I simply wasn't aware that one could want to try to apply namespacing to headers too - and fail to see the point. It's a bit of a miracle I never ran into problems with the KIO headers! >Would mean the include works even if you didn't ask to use Attica via >find_package, that's what we want to prevent here. Idem, don't see really the point nor why it would require an extra level of indirection for the forwarding headers (assuming you apply the same principle to the non-forwarding headers). I do see the drawback: those huge commandlines I mentioned earlier. Try finding something specific in there when you need to (and I can still remember when my builds failed because commandlines simply got too long). >Can we accept this and move on? I guess this is where I get to say "whatever" ... :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405070] Remove "Configure Task Manager" from window/app specific area of the context menu
https://bugs.kde.org/show_bug.cgi?id=405070 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/1daf42d9d734f96 ||9c31016825d8a7a93a6f95fbb Version Fixed In||5.16 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- Git commit 1daf42d9d734f969c31016825d8a7a93a6f95fbb by Nate Graham. Committed on 13/03/2019 at 20:54. Pushed by ngraham into branch 'master'. [Task Manager] Reorganize and improve presentation of context menu Summary: This patch improves the UX of the Task Manager's context menu by offering more logical separation and grouping of elements, improving strings, and adding or changing icons, as appropriate. The result hopefully feels more harmonious, less confusing, and less intimidating. Related: bug 405040, bug 405071, bug 405065 FIXED-IN: 5.16 Test Plan: "Window Actions" sub-menu: {F6688726} With places: {F6688732} With just actions: {F6688733} With many actions: {F6688743} With virtual desktops and activities: {F6688748} Reviewers: #plasma, #vdg, ndavis, hein Reviewed By: #plasma, #vdg, ndavis, hein Subscribers: abetts, broulik, ndavis, trickyricky26, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D19606 M +189 -170 applets/taskmanager/package/contents/ui/ContextMenu.qml M +1-0applets/taskmanager/plugin/backend.cpp https://commits.kde.org/plasma-desktop/1daf42d9d734f969c31016825d8a7a93a6f95fbb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405040] "Alternatives..." menu-item give wrong impression that I can install an alternative of the clicked task
https://bugs.kde.org/show_bug.cgi?id=405040 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.16 Latest Commit||https://commits.kde.org/pla ||sma-desktop/1daf42d9d734f96 ||9c31016825d8a7a93a6f95fbb Status|CONFIRMED |RESOLVED --- Comment #1 from Nate Graham --- Git commit 1daf42d9d734f969c31016825d8a7a93a6f95fbb by Nate Graham. Committed on 13/03/2019 at 20:54. Pushed by ngraham into branch 'master'. [Task Manager] Reorganize and improve presentation of context menu Summary: This patch improves the UX of the Task Manager's context menu by offering more logical separation and grouping of elements, improving strings, and adding or changing icons, as appropriate. The result hopefully feels more harmonious, less confusing, and less intimidating. Related: bug 405071, bug 405070, bug 405065 FIXED-IN: 5.16 Test Plan: "Window Actions" sub-menu: {F6688726} With places: {F6688732} With just actions: {F6688733} With many actions: {F6688743} With virtual desktops and activities: {F6688748} Reviewers: #plasma, #vdg, ndavis, hein Reviewed By: #plasma, #vdg, ndavis, hein Subscribers: abetts, broulik, ndavis, trickyricky26, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D19606 M +189 -170 applets/taskmanager/package/contents/ui/ContextMenu.qml M +1-0applets/taskmanager/plugin/backend.cpp https://commits.kde.org/plasma-desktop/1daf42d9d734f969c31016825d8a7a93a6f95fbb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405071] Improve context menu UX
https://bugs.kde.org/show_bug.cgi?id=405071 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/1daf42d9d734f96 ||9c31016825d8a7a93a6f95fbb Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.16 --- Comment #2 from Nate Graham --- Git commit 1daf42d9d734f969c31016825d8a7a93a6f95fbb by Nate Graham. Committed on 13/03/2019 at 20:54. Pushed by ngraham into branch 'master'. [Task Manager] Reorganize and improve presentation of context menu Summary: This patch improves the UX of the Task Manager's context menu by offering more logical separation and grouping of elements, improving strings, and adding or changing icons, as appropriate. The result hopefully feels more harmonious, less confusing, and less intimidating. Related: bug 405040, bug 405070, bug 405065 FIXED-IN: 5.16 Test Plan: "Window Actions" sub-menu: {F6688726} With places: {F6688732} With just actions: {F6688733} With many actions: {F6688743} With virtual desktops and activities: {F6688748} Reviewers: #plasma, #vdg, ndavis, hein Reviewed By: #plasma, #vdg, ndavis, hein Subscribers: abetts, broulik, ndavis, trickyricky26, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D19606 M +189 -170 applets/taskmanager/package/contents/ui/ContextMenu.qml M +1-0applets/taskmanager/plugin/backend.cpp https://commits.kde.org/plasma-desktop/1daf42d9d734f969c31016825d8a7a93a6f95fbb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405065] Improve Recent Documents in app-specific panel context menu
https://bugs.kde.org/show_bug.cgi?id=405065 Nate Graham changed: What|Removed |Added Version Fixed In||5.16 Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/1daf42d9d734f96 ||9c31016825d8a7a93a6f95fbb Resolution|--- |FIXED --- Comment #2 from Nate Graham --- Git commit 1daf42d9d734f969c31016825d8a7a93a6f95fbb by Nate Graham. Committed on 13/03/2019 at 20:54. Pushed by ngraham into branch 'master'. [Task Manager] Reorganize and improve presentation of context menu Summary: This patch improves the UX of the Task Manager's context menu by offering more logical separation and grouping of elements, improving strings, and adding or changing icons, as appropriate. The result hopefully feels more harmonious, less confusing, and less intimidating. Related: bug 405040, bug 405071, bug 405070 FIXED-IN: 5.16 Test Plan: "Window Actions" sub-menu: {F6688726} With places: {F6688732} With just actions: {F6688733} With many actions: {F6688743} With virtual desktops and activities: {F6688748} Reviewers: #plasma, #vdg, ndavis, hein Reviewed By: #plasma, #vdg, ndavis, hein Subscribers: abetts, broulik, ndavis, trickyricky26, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D19606 M +189 -170 applets/taskmanager/package/contents/ui/ContextMenu.qml M +1-0applets/taskmanager/plugin/backend.cpp https://commits.kde.org/plasma-desktop/1daf42d9d734f969c31016825d8a7a93a6f95fbb -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 405386] RKWard Version 0.7.0z+0.7.1+devel1 can't preview Markdown
https://bugs.kde.org/show_bug.cgi?id=405386 --- Comment #10 from Thomas Friedrichsmeier --- I'll have to admit, I don't quite get it. What I suspect is at play, is that somehow your system is configured to open XHTML files as text. You may want to check the File Associations section in your System Settings, particularly the "Embedding" tab. *However*, I tried reproducing your issue, here, by fiddling with these settings, and failed. You can probably "fix" the problem, by removing the string "KPartsIntegration | " from rkward/windows/rkhtmlwindow.cpp, as this will limit our HTML window to always showing rendered HTML, instead of an appropriate KPart (in this case a ktexteditor part). I'm not quite sure what side-effects this might be causing, though. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400538] vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55
https://bugs.kde.org/show_bug.cgi?id=400538 --- Comment #3 from Doug Johnson --- See the wine source here for usage of IRETQ: https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/signal_x86_64.c -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 400538] vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55
https://bugs.kde.org/show_bug.cgi?id=400538 Doug Johnson changed: What|Removed |Added CC||dou...@gmail.com --- Comment #2 from Doug Johnson --- IRETQ appears to be used by wine to start executing a CPU context. In normal operation this context is generated by the CPU when it is interrupted and pushed onto the stack, which is picked up by IRETQ when the interrupt is done being handled. Wine appears to generate this context on the stack itself so it's not using one generated by the CPU for IRETQ. Simply executing IRETQ without a valid CPU context on the stack will surely cause a segfault as the stack doesn't contain a valid instruction pointer and other CPU state. The segfault may even be caused by a stack underflow in this case, I am not sure. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 138956] KDE 5: low level API to control scrolling
https://bugs.kde.org/show_bug.cgi?id=138956 Lothar changed: What|Removed |Added CC||loh@googlemail.com --- Comment #6 from Lothar --- >From the initial posting, I guess this is related to BUG: 399014 BUG: 306745 or better, it may fixed by the Patch https://phabricator.kde.org/D17857 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 trb changed: What|Removed |Added CC||tere...@gmail.com --- Comment #7 from trb --- W pełni podzielam opinie Krzysztofa i Grzecho. Na początku wydawało mi się to tylko zabawnym udziwnieniem, ale na dłuższą metę jest męczące i mylące. Rozumiem dobre intencje autora, ale takie tłumaczenie wiele nie naprawia pod względem językowym, a jest zupełnie niepraktyczne. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 405451] New: Kdenlive Widow ver. 18.12.1 will not render jpg pictures. They are displayed OK in editing mode but once rendered, it only shows white screen. It is working correctly for
https://bugs.kde.org/show_bug.cgi?id=405451 Bug ID: 405451 Summary: Kdenlive Widow ver. 18.12.1 will not render jpg pictures. They are displayed OK in editing mode but once rendered, it only shows white screen. It is working correctly for video files. Product: kdenlive Version: 18.12.1 Platform: Other OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: kevinma...@netscape.net Target Milestone: --- SUMMARY Kdenlive Widow ver. 18.12.1 will not render jpg pictures. They are displayed OK in editing mode but once rendered, it only shows white screen. It is working correctly for video files. STEPS TO REPRODUCE 1. I tried creating the same project on two different windows 10 machines 2. 3. OBSERVED RESULT the same EXPECTED RESULT none SOFTWARE/OS VERSIONS Windows:1- 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.
[kwin] [Bug 405421] FEATURE REQUEST: Quick Tiling as a window rule
https://bugs.kde.org/show_bug.cgi?id=405421 Martin Flöser changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- There is a general geometry rule. For everything more specific there are KWin scripts. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 403317] KMAIL2; "Share Text" plugin segfaults
https://bugs.kde.org/show_bug.cgi?id=403317 Wolfgang Bauer changed: What|Removed |Added CC||robert.sku...@gmail.com --- Comment #7 from Wolfgang Bauer --- *** Bug 403566 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403566] KMail crashes imediatelly when new mail button is cliecked
https://bugs.kde.org/show_bug.cgi?id=403566 Wolfgang Bauer changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Wolfgang Bauer --- As there has not been any response so far, let's assume this is a duplicate... *** This bug has been marked as a duplicate of bug 403317 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405450] Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action
https://bugs.kde.org/show_bug.cgi?id=405450 Martin Flöser changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- Maximize/Restore are the options to go from maximize to restore and from restore back to maximize. It makes zero sense to also include minimize in it. Even more minimize in that list would be unacceptable as it's an action which cannot be reversed in the same way. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332065] Metadata not shown for non-indexed files
https://bugs.kde.org/show_bug.cgi?id=332065 Wolfgang Bauer changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #41 from Wolfgang Bauer --- (In reply to Илья Индиго from comment #38) > In openSUSE Tumbleweed with KDE4 It still doesn't work. :-( "KDE4" is unmaintained/unsupported since years, and baloo 4.x as well. So please don't reopen old bugs about that, thanks. And new bug reports about baloo 5.x should go to the component "frameworks-baloo", btw. > When I use baloo5-file and baloo5-widgets, disabling the indexing causes the > tooltips to stop. Sure, baloo5 is incompatible with "KDE4", even though it provides a "baloo_file_extractor" binary as well. Btw, I just tried here with the latest legacy 4.x software, and tooltips do show the image dimensions with baloo disabled. Maybe you just messed up your installation, e.g. by overwriting baloo4's baloo_file_extractor with baloo5's one. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404858] "Add Network Folder" tooltip icon does not show on Breeze, shows correctly on Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=404858 David Hallas changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |da...@davidhallas.dk Status|CONFIRMED |ASSIGNED --- Comment #10 from David Hallas --- I have a fix in review here: https://phabricator.kde.org/D19738 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 396990] [Regression from Frameworks 5.47 -> 5.48] Dolphin icons are incorrectly aligned if display scaling is used
https://bugs.kde.org/show_bug.cgi?id=396990 --- Comment #20 from Christoph Feck --- Regarding Dolphin, it uses custom pixmaps to colorize the icons for the selection effect. Using scaling factors affects such code. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 368130] Vi-mode search box disappears if used again while the search box is still open
https://bugs.kde.org/show_bug.cgi?id=368130 Lothar changed: What|Removed |Added CC||loh@googlemail.com --- Comment #1 from Lothar --- Here is some patch offer, but cant' say if it's sufficient or make things event worse https://phabricator.kde.org/D19408 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405406] Plasma Crashes After Waking Up From Sleep
https://bugs.kde.org/show_bug.cgi?id=405406 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Crash is in libnvidia-glcore.so.418.43 Please report this issue directly to NVIDIA develoeprs via https://devtalk.nvidia.com/default/topic/522835/linux/if-you-have-a-problem-please-read-this-first/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 404843] s390x: backtrace sometimes ends prematurely
https://bugs.kde.org/show_bug.cgi?id=404843 --- Comment #3 from Andreas Arnez --- To summarize some of the discussion on IRC about this topic today (please correct if I misunderstood anything): * Valgrind's unwinder needs to be extra fast. For instance, Memcheck takes a stack trace for each block allocated, and then again when it's freed. * In order to be fast, the unwinder limits the number of registers to unwind. Currently no platform unwinds more than 5 registers. * Initial register values are copied into an UnwindStartRegs in VG_(get_UnwindStartRegs) from the registers of the specified simulated threads. * In order to use FPRs for unwinding, they have to be added to the UnwindStartRegs and D3UnwindRegs structures, and summary rule fields for the s390 variant of DiCfSI must be added as well. Preferably we only add a few FPRs, to limit the performance impact. I'll probably look into that soon. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405378] Missing libz.dll on launch
https://bugs.kde.org/show_bug.cgi?id=405378 --- Comment #5 from caulier.gil...@gmail.com --- Git commit 48fd5e4bc85dd4b61af762f0200db6b0cc74900c by Gilles Caulier. Committed on 13/03/2019 at 19:13. Pushed by cgilles into branch 'master'. DrMinGw only provide 2 dlls usable without extra Microsoft debug tools. M +0-5project/bundles/mxe/04-build-installer.sh https://commits.kde.org/digikam/48fd5e4bc85dd4b61af762f0200db6b0cc74900c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405450] New: Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action
https://bugs.kde.org/show_bug.cgi?id=405450 Bug ID: 405450 Summary: Extend Maximize/Restore action into a tri-state Maximize/Restore/Minimize action Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: pmarget...@gmail.com Target Milestone: --- PROPOSAL: Please change the System settings -> Window management -> Window Behavior -> Titlebar Actions -> Maximize/Restore action into a Maximize/Restore/Minimize action ALTERNATIVE: Currently it's not possible to implement something like this via KWin scripting since there is no signal for "when you scroll over the titlebar". There isn't even a generic "mouse operation" or "wheel operation" signal on titlebar. If we had a signal to connect to, we could easily switch between the 3 states using something like: client.titlebarWheel.connect(function(delta){ // prevent default action somehow. if (delta > 0) { // scroll up if (!client.maximized && !client.minimized) { client.maximized = true } } else if (delta < 0) { // scroll down if (client.maximized && !client.minimized) { client.maximized = false } else if (!client.minimized) { client.minimized = true } } }) RELATED: the client.maximized does not exist currently as KWin has a complicated MaximizeMode enum that can be MaximizeVertical, MaximizeHorizontal, MaximizeFull (what a normal user considers "maximized"), and MaximizeRestore (not maximized). Since it was a complicated enum property, it seems nobody ever implemented a simple bool maximized property SEE: https://bugs.kde.org/show_bug.cgi?id=387097 NOTE: This bug from 2003 with the same wish was solved in 2005, but seems we've dropped that code... SEE: https://bugs.kde.org/show_bug.cgi?id=66519 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 404919] Akgregator crash on startup
https://bugs.kde.org/show_bug.cgi?id=404919 gin...@pm.me changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #4 from gin...@pm.me --- It is possible that the kernel or driver was updated. I run Akgregator today and it didn't crashed on start. Thanks for the help. -- You are receiving this mail because: You are watching all bug changes.