[kid3] [Bug 420143] Kid3 - Does not tag DSF files larger than 2GB
https://bugs.kde.org/show_bug.cgi?id=420143 Urs Fleisch changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Urs Fleisch --- I already heard of similar problems with other audio formats, but the problem is probably the same: Kid3 uses TagLib for DSF files and TagLib uses signed 32-bit integers for file offsets, therefore it is not able to handle large files. I think the problem is known for more than seven years now: https://github.com/taglib/taglib/pull/77 Unfortunately, this merge request was only made for taglib2, the upcoming (?) next binary incompatible release TagLib 2.0. I have already included a bunch of patches in the TagLib version which I am shipping with the binary Kid3 packages, but this one is from the taglib2 branch and probably much too invasive to be backported and then maintained. So I am afraid that we will have to live with this shortcomings until TagLib 2.0 is out. Probably this bug cannot be fixed in TagLib 1.x because this would break binary compatibility. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 419646] can not submit bug report
https://bugs.kde.org/show_bug.cgi?id=419646 --- Comment #5 from Harald Sitter --- Well, that I thought would be more useful :| Please also add kf5.kio.*=true to qtlogging.ini and try again. Note that the output will likely contain plaintext passwords now, you'll want to replace them before attaching it to the bugreport. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420128] Poor result of face detection (7.0.0. beta2)
https://bugs.kde.org/show_bug.cgi?id=420128 Maik Qualmann changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INTENTIONAL |--- Status|RESOLVED|REOPENED --- Comment #3 from Maik Qualmann --- We leave the bug open until a student as part of the GSoC2020 has implemented this option to download the better model. This is a good bug report with the test images. In the other sample image in the set, also all faces are detected with the YOLO model. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 419948] Changing an individual folder to "Prefer HTML" or to "Prefer Plain Text" is not remembered after restarting KMail
https://bugs.kde.org/show_bug.cgi?id=419948 Laurent Montel changed: What|Removed |Added Latest Commit|https://commits.kde.org/kma |https://commits.kde.org/kma |il/3fab426dfd0bea6fc6fb49e3 |il/0ad5a7ac48ca69b82aea50e0 |3fe939dc14d584a4|07e2a481be670ab8 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Laurent Montel --- Git commit 0ad5a7ac48ca69b82aea50e007e2a481be670ab8 by Laurent Montel. Committed on 16/04/2020 at 05:28. Pushed by mlaurent into branch 'release/20.04'. Fix Bug 419948 - Changing an individual folder to "Prefer HTML" or to "Prefer Plain Text" is not remembered after restarting KMail FIXED-IN: 5.14.0 M +4-13 src/kmmainwidget.cpp https://commits.kde.org/kmail/0ad5a7ac48ca69b82aea50e007e2a481be670ab8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420128] Poor result of face detection (7.0.0. beta2)
https://bugs.kde.org/show_bug.cgi?id=420128 Sandra Seilmann changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #2 from Sandra Seilmann --- Thanks, Mike. since accoring your explanation this an expected behaviour of the currently used model, rather than a bug, I've set the status to resolved-intentional. Cheers, Sandra -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 420146] New: konsole crashed at start after change in .config/session/konsole_*
https://bugs.kde.org/show_bug.cgi?id=420146 Bug ID: 420146 Summary: konsole crashed at start after change in .config/session/konsole_* Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: skz...@gmail.com Target Milestone: --- Application: kdeinit5 (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-177-generic x86_64 Distribution: Ubuntu 16.04.6 LTS -- Information about the crash: - What I was doing when the application crashed: kde starting and loading from saved session - Custom settings of the application: in .config/session/konsole_* I changed from [1] Active=11 Sessions=1,2,3,4,5,6,8,7,9,10,11 [Number] NumberOfSessions=11 NumberOfWindows=1 to [1] Active=11 Sessions=1,2,3,4,5,6,8,7,9,10,11 [Number] NumberOfSessions=4 NumberOfWindows=1 (my mistake: I wanted to change Active value, but should not crash) -- Backtrace: Application: Konsole (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9c01a4e780 (LWP 2249))] Thread 2 (Thread 0x7f9beb3f8700 (LWP 2250)): #0 0x7f9c001a974d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9bff885c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f9bff8878d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f9bed755889 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f9c0051d7be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9bfdeea6ba in start_thread (arg=0x7f9beb3f8700) at pthread_create.c:333 #6 0x7f9c001b541d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f9c01a4e780 (LWP 2249)): [KCrash Handler] #6 0x7f9bef55a850 in Konsole::Session::sessionId() const () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15 #7 0x7f9bef58f328 in Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15 #8 0x7f9bef595290 in Konsole::ViewManager::createView(Konsole::Session*, Konsole::ViewContainer*, int) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15 #9 0x7f9bef59564f in Konsole::ViewManager::createView(Konsole::Session*) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15 #10 0x7f9bef59798d in Konsole::ViewManager::restoreSessions(KConfigGroup const&) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.15 #11 0x7f9bf54e11f0 in KMainWindow::readPropertiesInternal (this=this@entry=0xa9fcd0, config=0xa8b4c0, number=number@entry=1) at ../../src/kmainwindow.cpp:610 #12 0x7f9bf54e1252 in KMainWindow::restore (this=0xa9fcd0, number=1, show=) at ../../src/kmainwindow.cpp:435 #13 0x7f9bef816c6c in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so #14 0x7f9bef817d8d in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so #15 0x004085ec in ?? () #16 0x00409de9 in ?? () #17 0x0040a467 in ?? () #18 0x00405194 in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[calligrachart] [Bug 420145] New: Legend is not printed properly
https://bugs.kde.org/show_bug.cgi?id=420145 Bug ID: 420145 Summary: Legend is not printed properly Product: calligrachart Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: i...@lysator.liu.se Reporter: dand...@get2net.dk Target Milestone: --- 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.
[k3b] [Bug 419487] K3B crash when open a iso file by "right click mouse menu open" any iso file.
https://bugs.kde.org/show_bug.cgi?id=419487 --- 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.
[dolphin] [Bug 419491] Dolphin preferences thinks Trash folder is my root folder
https://bugs.kde.org/show_bug.cgi?id=419491 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418932] KWin crashed when moving a window when in Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=418932 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419496] Missing plasma panel when Wayland session is started with multi-monitor mode set to "Unify outputs". Possibly related kded5 crash.
https://bugs.kde.org/show_bug.cgi?id=419496 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419376] FEATURE REQUEST: Night mode
https://bugs.kde.org/show_bug.cgi?id=419376 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418770] Drawing tablet bug (A15Pro)
https://bugs.kde.org/show_bug.cgi?id=418770 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[digikam] [Bug 414055] Port Slideshow tool to plugin architecture [patch]
https://bugs.kde.org/show_bug.cgi?id=414055 --- Comment #30 from Maik Qualmann --- I have already restored the setting "Show Progress Indicator" to save in the config file. Will work again in the next pre-release bundles. Maik -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 388857] Krunner can't actually search for files
https://bugs.kde.org/show_bug.cgi?id=388857 Masacroso changed: What|Removed |Added Component|general |filesearch Assignee|k...@privat.broulik.de |baloo-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 370726] Text selection tool highlight unintelligible
https://bugs.kde.org/show_bug.cgi?id=370726 --- Comment #3 from Xu Zhao --- The problem persists on Okular 1.9.3. Any progress on this issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420144] Visual Studio Code desktop action doesn't launch
https://bugs.kde.org/show_bug.cgi?id=420144 --- Comment #1 from codingko...@gmail.com --- Created attachment 127589 --> https://bugs.kde.org/attachment.cgi?id=127589=edit The context menu in which the desktop action appears. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420144] New: Visual Studio Code desktop action doesn't launch
https://bugs.kde.org/show_bug.cgi?id=420144 Bug ID: 420144 Summary: Visual Studio Code desktop action doesn't launch Product: plasmashell Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: codingko...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 127588 --> https://bugs.kde.org/attachment.cgi?id=127588=edit The error dialog that is shown after clicking on the desktop action. SUMMARY Visual Studio Code's desktop file has a desktop action for opening a "New Empty Window". Clicking on the desktop file to run it works, but running this desktop action doesn't. STEPS TO REPRODUCE 1. Install VS Code (I'm using the "code" Arch Linux package). 2. From one of the application menus, or the task manager widget, right click the desktop entry for VS Code and select "New Empty Window". OBSERVED RESULT An error dialog is displayed, stating "Could not find the program '@@EXEC@@'". EXPECTED RESULT A new empty window of VS Code should be opened. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, kernel 5.6.3 (available in About System) KDE Plasma Version: 5.18.4.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION The VS Code desktop entry is as follows: > [Desktop Entry] > Name=Code - OSS > Comment=Code Editing. Redefined. > GenericName=Text Editor > Exec=/usr/bin/code-oss --no-sandbox --unity-launch %F > Icon=code-oss > Type=Application > StartupNotify=false > StartupWMClass=Code > Categories=Utility;TextEditor;Development;IDE; > MimeType=text/plain; > Actions=new-empty-window; > Keywords=vscode; > > [Desktop Action new-empty-window] > Name=New Empty Window > Exec=/usr/bin/code-oss --no-sandbox --new-window %F > Icon=code-oss This bug may be able to be made more generalized, however I have not seen any other applications exhibit this behavior. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420039] kwin_wayland: Windows are often invisible and unusable, triggers session crash
https://bugs.kde.org/show_bug.cgi?id=420039 David Edmundson changed: What|Removed |Added Ever confirmed|1 |0 Status|RESOLVED|REPORTED Resolution|FIXED |--- --- Comment #27 from David Edmundson --- It will only fix the crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420039] kwin_wayland: Windows are often invisible and unusable, triggers session crash
https://bugs.kde.org/show_bug.cgi?id=420039 --- Comment #26 from Mircea Kitsune --- (In reply to David Edmundson from comment #25) Does this also fix the invisible windows? The session crash appears as more of a side effect to that... the core problem seems to be the renderer not "finding" a window when it's been minimized and deactivated. If not perhaps this should stay open until that part can be solved as well. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 353216] qtcurve-qt5 is missing the qtcurve window decoration in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=353216 --- Comment #36 from Yichao Yu --- > I give up. There are a number of people that would have helped you when I > first mentioned this to you four years ago. It's a shame. I won't comment on > this anymore. Since you are making it sound like I intentionally did nothing and asked for no help I'll make it clear even though I think I'm not really obligated to give an explaination otherwise. First, there are times (ok, twice maybe) that I was offered help privately in terms of actually contributing code but then didn't hear back. I see this both as a missing opportunity to get it ported and a sign of maybe it is not as trivial as I thought it was. Secondly, I've also looked at the help in terms of documentation and the issue, as mentioned above, is that the complexity from the qtcurve side. I can see that if one know the qtcurve side of things well, the port shouldn't be very hard. (In case it is not clear, I did not write the qt4 version of the kwin theme.) It is trivial to use the template implementation to get something working while throwing away everything qtcurve currently have. The difficulty is in large part to figure out what the code in qtcurve is doing and I assume none of the help are in that area. Note that this is very different from the widget theme, where basically everything has a 1-1 mapping, the porting is much more mechanical and fixes afterwards can be done mostly incrementally. Now those are my accessments, most if not all of the conclusions are actually scattering among the few comments I've already made above. They may or may not be accurate but that's what I find and why I determined it is harder than I want to spend much time on any time soon. If any of the assumptions/findings I had above are not accurate making this easier than what I thought, I'm certainly open to constructive suggestions. > Do you want to close this bug report and mark it as WONTFIX? No, I've left this open as an acknowledgement that this is a nice to have feature. This can be close if it doesn't make sense to have, which is not the case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420039] kwin_wayland: Windows are often invisible and unusable, triggers session crash
https://bugs.kde.org/show_bug.cgi?id=420039 David Edmundson changed: What|Removed |Added Latest Commit||https://commits.kde.org/kwi ||n/d0875aa11707dd042e14f8723 ||e1fd141452dca80 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #25 from David Edmundson --- Git commit d0875aa11707dd042e14f8723e1fd141452dca80 by David Edmundson. Committed on 15/04/2020 at 23:57. Pushed by davidedmundson into branch 'Plasma/5.18'. [wayland] avoid potential crash when checking for window inhibitions on desktop change Summary: Xwayland clients are sometimes offset from being visible to having a surface applied. We might also have internal windows which will be AbstractClients without a surface. No idle interface will be set up for non wayland clients, but on a desktop change we itterate through all AbstractClients and need to guard somewhere. Test Plan: None Reviewers: #kwin, apol Reviewed By: apol Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D28858 M +1-1idle_inhibition.cpp https://commits.kde.org/kwin/d0875aa11707dd042e14f8723e1fd141452dca80 -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 420143] Kid3 - Does not tag DSF files larger than 2GB
https://bugs.kde.org/show_bug.cgi?id=420143 Christophe changed: What|Removed |Added Summary|Does not tag DSF files |Kid3 - Does not tag DSF |larger than 2GB |files larger than 2GB -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 420143] New: Does not tag DSF files larger than 2GB
https://bugs.kde.org/show_bug.cgi?id=420143 Bug ID: 420143 Summary: Does not tag DSF files larger than 2GB Product: kid3 Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: christophe.ge...@neuf.fr Target Milestone: --- SUMMARY Does not tag DSF files larger than 2GB STEPS TO REPRODUCE 1. find a DSF file larger than 2GB 2. select in Kid3 for tagging 3. click Save, , wait till it gives hand back OBSERVED RESULT No tag EXPECTED RESULT Tagged file SOFTWARE/OS VERSIONS Windows: Kid3 3.8.2/Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Thank you for your attention -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 305072] Animated GIF is some milliseconds too slow
https://bugs.kde.org/show_bug.cgi?id=305072 --- Comment #8 from Colin Griffith --- I'm now relatively convinced that this is, in part, caused by bug 420141 (which I just filed today). However, I'm noticing that even on gifs with alpha transparency, there's STILL a small amount of slowdown - just not nearly as much. So while I think that bug helps get to the root of the problem, there's still something else going on here. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 353216] qtcurve-qt5 is missing the qtcurve window decoration in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=353216 --- Comment #35 from Roman Bysh --- I give up. There are a number of people that would have helped you when I first mentioned this to you four years ago. It's a shame. I won't comment on this anymore. Do you want to close this bug report and mark it as WONTFIX? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416830] Elisa crashes on start Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=416830 Rick changed: What|Removed |Added CC||rickjcar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 353216] qtcurve-qt5 is missing the qtcurve window decoration in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=353216 --- Comment #34 from Yichao Yu --- Err, assuming you are still talking about the kwin support (you changed how you talked about it so I assumed you were talking about something else), I've already mentioned above that I've given it my fair try and I don't think it's something that is possible to have a clear timeline for due to the complexity. It's a fairly low priority wishlist item. I'm not planning to work on it any time soon but pull requests are and has always been welcome. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414055] Port Slideshow tool to plugin architecture [patch]
https://bugs.kde.org/show_bug.cgi?id=414055 --- Comment #29 from griffiths_a...@icloud.com --- F2 to show the prefs works OK. Could you now please address the persistence of the 'Show Progress Indicator' setting? That's what I originally wanted looking at so that I don't need to change settings every time I use the slideshow, and was the pre-beta3 behaviour. Thanks.. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420056] BUY/SELL information ignored when importing OFX investment transactions
https://bugs.kde.org/show_bug.cgi?id=420056 Dawid Wróbel changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kmy ||money/8bd68cd8a2e0ebadedc04 ||ff665d6704d6395d8a0 Resolution|--- |FIXED --- Comment #3 from Dawid Wróbel --- Git commit 8bd68cd8a2e0ebadedc04ff665d6704d6395d8a0 by Dawid Wróbel. Committed on 15/04/2020 at 22:54. Pushed by wrobelda into branch 'bug-420056'. Add option to enable fixing of the buy/sell signs Some providers do not follow the OFX spec and do not assign the correct positive/negative signage to amount (TOTALs) and quantity (UNITs) values assosciated with BUY/SELL investment transactions (see OFX2.2, section 13.3.3). This change adds option to OFX import dialog and account's online settings to force the signage to follow the the spec. GUI: M +1-0kmymoney/plugins/ofx/import/dialogs/konlinebankingstatus.cpp M +19 -2kmymoney/plugins/ofx/import/dialogs/konlinebankingstatusdecl.ui M +18 -1kmymoney/plugins/ofx/import/importoption.ui M +96 -74 kmymoney/plugins/ofx/import/ofximporter.cpp https://commits.kde.org/kmymoney/8bd68cd8a2e0ebadedc04ff665d6704d6395d8a0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 419975] When importing transactions, we're matching against the other transactions also being imported
https://bugs.kde.org/show_bug.cgi?id=419975 Dawid Wróbel changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/1655f78fd9bcbb3c23f2a |money/84d204b26fd449f501d4f |5c8d8d4cf05a61823a0 |7cb360adad7def73627 --- Comment #5 from Dawid Wróbel --- Git commit 84d204b26fd449f501d4f7cb360adad7def73627 by Dawid Wróbel. Committed on 15/04/2020 at 22:49. Pushed by wrobelda into branch 'bug-420056'. Add option to enable fixing of the buy/sell signs Some providers do not follow the OFX spec and do not assign the correct positive/negative signage to amount (TOTALs) and quantity (UNITs) values assosciated with BUY/SELL investment transactions (see OFX2.2, section 13.3.3). This change adds option to OFX import dialog and account's online settings to force the signage to follow the the spec. GUI: M +1-0kmymoney/plugins/ofx/import/dialogs/konlinebankingstatus.cpp M +19 -2kmymoney/plugins/ofx/import/dialogs/konlinebankingstatusdecl.ui M +18 -1kmymoney/plugins/ofx/import/importoption.ui M +96 -74 kmymoney/plugins/ofx/import/ofximporter.cpp https://commits.kde.org/kmymoney/84d204b26fd449f501d4f7cb360adad7def73627 -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 353216] qtcurve-qt5 is missing the qtcurve window decoration in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=353216 --- Comment #33 from Roman Bysh --- Sorry. The qtcurve-qt5. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416279] Add option "Reverse charges and payments" to OFX import
https://bugs.kde.org/show_bug.cgi?id=416279 --- Comment #3 from Dawid Wróbel --- Git commit 264f15318338c119eb83476811700f7bc8680089 by Dawid Wróbel. Committed on 15/04/2020 at 22:31. Pushed by wrobelda into branch 'bug-420056'. Initialize "Invert Amount" setting for online transactions. The "Invert Amount" setting was never being initialized correctly when importing transactions online. M +3-1kmymoney/plugins/ofx/import/ofximporter.cpp https://commits.kde.org/kmymoney/264f15318338c119eb83476811700f7bc8680089 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420142] New: segmentation fault
https://bugs.kde.org/show_bug.cgi?id=420142 Bug ID: 420142 Summary: segmentation fault Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: maus...@libero.it CC: aleix...@kde.org Target Milestone: --- Created attachment 127587 --> https://bugs.kde.org/attachment.cgi?id=127587=edit It is a file with a bug report SUMMARY see attached file STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 19.4 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 419396] When trying to open a 7z encrypted archive, Krusader does not ask for a password
https://bugs.kde.org/show_bug.cgi?id=419396
Toni Asensi Esteve changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kru
||sader/b4e016807f5c334fce253
||179a38925a5667c0563
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Toni Asensi Esteve ---
Git commit b4e016807f5c334fce253179a38925a5667c0563 by Toni Asensi Esteve.
Committed on 15/04/2020 at 22:38.
Pushed by asensi into branch 'master'.
Archives: Fix a 7z execution, allow password asking, clarify the name of a
function
In Krusader, nowadays it turns out that in
`kio_krarcProtocol::checkIf7zIsEncrypted()`: 7z is executed with a " t -y "
argument, instead of being executed with two arguments, therefore the execution
fails. To avoid that, a simple change can be made.
In more detail: After applying the proposed changes, a 7z execution is left as
other places are in the Krusader source code like in
`KRarcHandler::checkIf7zIsEncrypted(bool , QString fileName)`:
proc << KrServices::fullPathName("7z") << "-y" << "t";
or `KRarcHandler::arcFileCount(const QString& archive, const QString& type,
const QString& password, KRarcObserver *observer)`:
else if (type == "7z") lister << KrServices::fullPathName("7z") << "-y" <<
"l";
After the change is applied, at least an improvement is seen: when the user
tries to enter a compressed 7z file, its password is asked.
Besides:
- A `checkOutputForPassword()` function that was used (and useful) only for
7z files was renamed as `check7zOutputForPassword()`.
Test plan: The one described in the task [Solve some bugs related to archives,
remove some duplicated code](https://phabricator.kde.org/T12876).
FIXED: [ 419396 ] When trying to open a 7z encrypted archive, Krusader does not
ask for a password
Differential Revision: https://phabricator.kde.org/D28411
M +3-4krArc/krarc.cpp
M +1-1krArc/krarc.h
https://commits.kde.org/krusader/b4e016807f5c334fce253179a38925a5667c0563
--
You are receiving this mail because:
You are watching all bug changes.
[krusader] [Bug 417107] QCoreApplication::applicationDirPath: Please instantiate the QApplication object first
https://bugs.kde.org/show_bug.cgi?id=417107 Toni Asensi Esteve changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kru ||sader/2f168d23c20d69f00d733 ||ca970a49096b1ab0782 Status|CONFIRMED |RESOLVED --- Comment #5 from Toni Asensi Esteve --- Git commit 2f168d23c20d69f00d733ca970a49096b1ab0782 by Toni Asensi Esteve. Committed on 15/04/2020 at 22:38. Pushed by asensi into branch 'master'. Archives: Solve the 'QCoreApplication::applicationDirPath: Please instantiate the QApplication object first' error Solve the «QCoreApplication::applicationDirPath: Please instantiate the QApplication object first» error, what required moving code. Besides, after the code of the `generateKrarcArchiveMimetypes()` function was moved to a constructor, that code is executed only once and the source code ends up being simplified. Make the KrServices class simpler by moving archive-related code to an archive-related class. Test plan: The one described in the task [Solve some bugs related to archives, remove some duplicated code](https://phabricator.kde.org/T12876). FIXED: [ 417107 ] QCoreApplication::applicationDirPath: Please instantiate the QApplication object first Differential Revision: https://phabricator.kde.org/D28413 M +1-1krArc/krarcbasemanager.cpp M +1-3krusader/Archive/abstractthreadedjob.cpp M +72 -0krusader/Archive/krarchandler.cpp M +14 -0krusader/Archive/krarchandler.h M +0-2krusader/Archive/packjob.cpp M +2-1krusader/Konfigurator/kgprotocols.cpp M +1-1krusader/Panel/panelfunc.cpp M +2-3krusader/Search/krsearchmod.cpp M +1-0krusader/krglobal.cpp M +3-0krusader/krglobal.h M +5-82 krusader/krservices.cpp M +0-6krusader/krservices.h M +4-0krusader/krusader.cpp M +0-3krusader/main.cpp https://commits.kde.org/krusader/2f168d23c20d69f00d733ca970a49096b1ab0782 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 420141] New: Gwenview acts slow and leaks memory when zooming/panning images without an alpha channel
https://bugs.kde.org/show_bug.cgi?id=420141 Bug ID: 420141 Summary: Gwenview acts slow and leaks memory when zooming/panning images without an alpha channel Product: gwenview Version: 19.12.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: tyna...@gmail.com Target Milestone: --- SUMMARY Gwenview is sluggish and leaks memory constantly when viewing images which lack an alpha channel. Memory increases every time any operation is performed, such as panning/zooming the view, or the next frame of a gif being rendered. STEPS TO REPRODUCE 1. Open the system monitor (I use KSysGuard) and filter process names to only show Gwenview. 2. Open an image that lacks an alpha channel. 3. Zoom in on the image so that you can pan, and observe that RAM usage increases. 4. Pan around the image, and observe that RAM usage increases. 5. Switch to an image with an alpha channel. Note that RAM usage does not decrease. 6. Zoom in on the image so that you can pan, and observe that RAM usage stays constant. 7. Pan around the image, and observe that RAM usage stays constant. OBSERVED RESULT Every time you zoom or pan the image, the operation is sluggish and at a low framerate... And Gwenview's memory consumption gets higher. The slowdown is particularly noticeable when panning. Note that this does not happen when you switch to viewing an image with an alpha channel - RAM usage stays constant (but does not go down), and panning around the image is incredibly fast and smooth. EXPECTED RESULT The same behavior that is observed when viewing images with an alpha channel - constant RAM usage, and smooth panning/zooming. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-46-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processing Unit: ASUSTeK R9 290X DirectCU II OC OpenGL Renderer: AMD Radeon R9 200 Series (HAWAII, DRM 3.33.0, 5.3.0-46-generic, LLVM 10.0.0) OpenGL Core Profile Version: 4.6 (Core Profile) Mesa 20.0.0-devel - padoka PPA ADDITIONAL INFORMATION This happens whether I have 'Animations' (in the 'Image View' settings) set to 'OpenGL', 'Software', or 'None'. Images with an alpha channel are smooth regardless of whether or not the image actually has any transparent (or semi-transparent) pixels. Given the reliance on an alpha channel, I'm going to guess that the image data is getting converted from an array of RGB bytes (each structure being 24 bits wide, and thus not 32-bit aligned) to a 32-bit aligned RGBA array, each pixel being 4 bytes instead of 3 bytes... And this operation is being done every time zooming and panning occurs. I'm guessing that one of either the converted, or the temporary non-converted, version of the pixmap is not being destructed/freed properly. It's also worth mentioning that animated .gif files that have a color reserved for transparent pixels play smoothly and do not cause increased RAM usage over time, while viewing an animated .gif file which does not reserve a color for transparency play back sluggishly and increase RAM usage with each frame that gets displayed. This bug has bothered me for YEARS now. I would have thought it would be reported by now, but I've only seen tangentially related reports (like 'leaks memory in fullscreen mode', 'when viewing lots of files', etc.) when searching for what to follow. Many bugs have reportedly been fixed years ago, but I still see their effects now with current versions, but only with some images - images without alpha channels. I have a feeling that many of the memory leak or slowdown bugs are actually just this one bug dealing with non-alpha-channel images. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420139] "Save copy as"
https://bugs.kde.org/show_bug.cgi?id=420139 --- Comment #3 from zep...@gmail.com --- BTW, the "Save copy as" directory was (very nicely IMO) maintained across logouts, reboots, etc. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420139] "Save copy as"
https://bugs.kde.org/show_bug.cgi?id=420139 --- Comment #2 from zep...@gmail.com --- No. "Save as" defaults to the directory containing the original PDF. "Save copy as" defaulted to the directory where the last "save as copy" was performed. So when Mozilla opens PDFs by passing them to okular, the "Save as" directory will always be somewhere under /tmp. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 364978] ksysguard shows negative relative start time due to getting the timezone wrong
https://bugs.kde.org/show_bug.cgi?id=364978 g507...@nwytg.net changed: What|Removed |Added CC||g507...@nwytg.net --- Comment #5 from g507...@nwytg.net --- Timezones do not explain this, because ksysguard always shows me relative start times that are days or weeks in the future. They are utterly wrong. I think the problems start after resuming the system from standby. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 353216] qtcurve-qt5 is missing the qtcurve window decoration in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=353216 --- Comment #32 from Yichao Yu --- I don't know what you meant by qtcurve-qt. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420139] "Save copy as"
https://bugs.kde.org/show_bug.cgi?id=420139 Albert Astals Cid changed: What|Removed |Added Resolution|--- |NOT A BUG CC||aa...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Albert Astals Cid --- Save as is just Save copy as, isn't it? -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 353216] qtcurve-qt5 is missing the qtcurve window decoration in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=353216 --- Comment #31 from Roman Bysh --- What is the status of qtcurve-qt? Are you going to finish it this year? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 419302] Dolphin search shows a lot of duplicates
https://bugs.kde.org/show_bug.cgi?id=419302 --- Comment #4 from Philip P. --- Steps to reproduce: 1. Enter any directory 2. ´touch baloon´ 3. `baloosearch baloon` 4. `rm baloon` 5. `baloosearch baloon` Repeat an infinite amount of times to create an infinite number of duplicates :) -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 420136] Varying font sizes on sub-pages
https://bugs.kde.org/show_bug.cgi?id=420136 --- Comment #2 from carl --- the link to the mockup is https://kde.carlschwan.eu/index-new and not https://kde.carlschwan.eu/ -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 420136] Varying font sizes on sub-pages
https://bugs.kde.org/show_bug.cgi?id=420136 carl changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||schwanc...@protonmail.com --- Comment #1 from carl --- The size is the same for https://kde.org/plasma-desktop and most of the KDE websites (e.g https://kde.org/community/whatiskde/). The font-size is defined in https://invent.kde.org/websites/aether-sass/-/blob/master/css/includes/_typography.scss The problem is in the homepage. https://kde.org contains tons of hardcoded font-size and is in the process of being updated completely. See the current mockup at https://kde.carlschwan.eu. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420114] Cannot delete assigned TAG entries from all or part of affected line items without reassignment of TAG
https://bugs.kde.org/show_bug.cgi?id=420114 schoenes-...@web.de changed: What|Removed |Added Summary|Cannot delete assigned Cue |Cannot delete assigned TAG |entries from all or part of |entries from all or part of |affected line items without |affected line items without |reassignment of Cue |reassignment of TAG -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 419465] Wallet failed to get opened by PAM, error code is -9
https://bugs.kde.org/show_bug.cgi?id=419465 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Albert Astals Cid --- (In reply to Christoph Feck from comment #3) > Interesting. Bug 416461 states that KWallet/PAM issues appeared with update > to 5.18.3 for many people, but also earlier for the original reporter. I > tend to believe that there not a Plasma update broke it, but some lower > level component changed. > > The only code change in kwallet-pam since a long time was indeed an update > in 5.18.4 to support encrypted systems, see > https://cgit.kde.org/kwallet-pam.git/commit/ > ?id=2bb4c6dc870ff59c6f62c4b12bf9be229d9ff8da > > It looks like this commit broke non-encrypted systems? @Martin Interesting I'm using that version both in encrypted and non-encrypted systems (two different laptops) and it works fine. Do have an actual password or is it a passwordless system? Are you using sddm or any other login manager? @Ongun your thing seems different, please open a different bug report. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406629] Konsole needs either less tear-off sensativity or the ability to disable tear-off tabs
https://bugs.kde.org/show_bug.cgi?id=406629 zep...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 CC||zep...@gmail.com Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #2 from zep...@gmail.com --- I'm now using 19.12.3 with Kubuntu 20.04 beta. I don't understand how this is thought to be fixed. I upgraded from 16.04 LTS, and the inadvertent tab tearing off is so bad I have moved the tab bar to the top so the mouse usually is not near it. But this is far less productive, because the top is so far from where the typing and cutting and pasting is. If there is a way to disable this, it is not obvious in the menu. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420114] Cannot delete assigned Cue entries from all or part of affected line items without reassignment of Cue
https://bugs.kde.org/show_bug.cgi?id=420114
--- Comment #2 from schoenes-...@web.de ---
Thomas:
Sorry for the confusion - it's TAG, of course, not CUE. Same word in
German ("Stichwort"), but of course two totally different items in
English. Incorrect re-translation on my side.
On Wed, 2020-04-15 at 18:13 +, Thomas Baumgart wrote:
> https://bugs.kde.org/show_bug.cgi?id=420114
>
> Thomas Baumgart changed:
>What|Removed |Added---
> ---
> -- Resolution|
> -
> -- |WAITINGFORINFO Status|REPORTE
> D|NEEDSINFO
> --- Comment #1 from Thomas Baumgart ---What do
> you refer to as 'cue or cue entry'? What is the German word for it?
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 420140] New: Expand Application Launcher menu to fit more entries on screen when there is room
https://bugs.kde.org/show_bug.cgi?id=420140 Bug ID: 420140 Summary: Expand Application Launcher menu to fit more entries on screen when there is room Product: plasmashell Version: 5.18.4 Platform: Chakra OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: subscri...@blackbrook.org CC: plasma-b...@kde.org Target Milestone: 1.0 By default, the popup menu uses maybe half of the screen height. If you have more favorites than fit in this area, you are forced to scroll the menu to find them. This is a little frustrating where there is plenty of room on the screen to display them all. It seems to me there is no advantage to not using the available space. It should expand menu upwards until either the screen edge is reached or there is no longer a scrollbar required. There used to be a workaround in the ability to resize this menu. This ability seems to have been lost, but really it should not need to be customized by the user, the optimal size is what I have described above. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418708] Settings shows double entry for flatpak flathub
https://bugs.kde.org/show_bug.cgi?id=418708 --- Comment #4 from Ian Newton --- Gnome Application Platform install issue seems to be resolved and is maybe irrelevant but the double entry for Flatpak repos and packages remains. It is not clear where the configuration for Discover is stored as there appear to be no config files? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420003] Global shortcut: show windows from all desktops has no effect
https://bugs.kde.org/show_bug.cgi?id=420003 --- Comment #2 from tony.spe...@outlook.com --- Created attachment 127585 --> https://bugs.kde.org/attachment.cgi?id=127585=edit Effects Not that I'm aware of, I didn't change something in this regard. The setting is enabled -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401154] gwenview should not change image colors if system-wide color management is enabled
https://bugs.kde.org/show_bug.cgi?id=401154 --- Comment #15 from Alex Fliker --- Maybe worth taking a look at showFoto app? It's handling color in a correct way. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420139] New: "Save copy as"
https://bugs.kde.org/show_bug.cgi?id=420139 Bug ID: 420139 Summary: "Save copy as" Product: okular Version: 1.9.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: zep...@gmail.com Target Milestone: --- SUMMARY Okular used to have a "Save copy as" option (e.g. in Kubuntu 2016.4 LTS). It is MIA now. I see some bugs referencing this (e.g #348644), but did not find an explicit bug describing its removal. UTILITY I used this all the time. Because web browser rendering of PDFs is still somewhat janky, I always set up firefox to use okular to open all PDFs. Then I want to save them. Unfortunately, the "Save as" dialog always defaults to the mozilla temp directory (where the original file is). The "Save copy as" dialog used to default to the last directory where you actually saved a copy, so when you are saving multiple PDFs to a directory, it was much more functional to do it this way. BOTTOM LINE This is a removal of a very useful feature, so it feels very much like a regression. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418708] Settings shows double entry for flatpak flathub
https://bugs.kde.org/show_bug.cgi?id=418708 --- Comment #3 from Ian Newton --- Created attachment 127584 --> https://bugs.kde.org/attachment.cgi?id=127584=edit Screenshot of double entry for flatpak flathub and all packages are duplicated -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401154] gwenview should not change image colors if system-wide color management is enabled
https://bugs.kde.org/show_bug.cgi?id=401154 --- Comment #14 from Misha Aizatulin --- Got it. So if I understand correctly, gwenview tells the system (presumably X) "I do my own colour management, please don't modify my output", but the system is ignoring that? Perhaps the thing that modifies output here is not X, but some component that oyranos relies on? In fact, looks like there's a bug report to that extent: https://github.com/oyranos-cms/oyranos/issues/60 -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 418908] Add option to hide menubar
https://bugs.kde.org/show_bug.cgi?id=418908 Martin Koller changed: What|Removed |Added CC||kol...@aon.at --- Comment #1 from Martin Koller --- why would one want to see no menubar ? Most actions are only reachable from it... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357136] Can't configure Application Launcher Menu to work well in positions other than bottom left of screen
https://bugs.kde.org/show_bug.cgi?id=357136 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 419646] can not submit bug report
https://bugs.kde.org/show_bug.cgi?id=419646 --- Comment #4 from Martin Koller --- Created attachment 127583 --> https://bugs.kde.org/attachment.cgi?id=127583=edit logs logs from a crash I forced by kill -4 of a kwrite instance -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 414440] Brightness gets maximized after screen times out.
https://bugs.kde.org/show_bug.cgi?id=414440 --- Comment #5 from Pietro F. Fontana --- Update, I still experience the issue but it became harder to reproduce. I tried the following: 1. set screen dim timeout to 1min, set screen energy saving timeout to 2min 2. set automatic screen lock to 1min 3. wait until the screen is locked and turned off alternative 3. lock the screen and wait until it turns off 4. wake up the screen and unlock it I am not able to reproduce the issue, but I still experience it everyday when I leave the computer locked for a longer period. The Plasma applet behaves in a consistent way on my system, it always displays the current brightness. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.2 Kernel Version: 5.6.3-2-MANJARO Display: wayland server: X.org 1.20.8 driver: modesetting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373299] Zoom shortcuts dont work after focus given to docker windows
https://bugs.kde.org/show_bug.cgi?id=373299 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/d454a04e713c0f |krita/commit/f49dac3a603d8d |fc4167021680f69be3698871ec |40108523be436be1b251966ac5 --- Comment #4 from Dmitry Kazakov --- Git commit f49dac3a603d8d40108523be436be1b251966ac5 by Dmitry Kazakov. Committed on 15/04/2020 at 20:48. Pushed by dkazakov into branch 'master'. Fix pan/zoom shortcuts not working after accessing any docker The reason for the bug was that KisExtendedModifiersMapper:: queryExtendedModifiers() has never been implemented for Windows. Therefore all the shortcuts including Space could potentially be lost when the user pressed it without focusing on the canvas. We also need an implementation for OSX. Related: bug 372646, bug 391088 M +53 -3libs/ui/input/kis_extended_modifiers_mapper.cpp https://invent.kde.org/kde/krita/commit/f49dac3a603d8d40108523be436be1b251966ac5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372646] Unable to pan after picking color from reference image until canvas is clicked once first
https://bugs.kde.org/show_bug.cgi?id=372646 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/d454a04e713c0f |krita/commit/f49dac3a603d8d |fc4167021680f69be3698871ec |40108523be436be1b251966ac5 --- Comment #16 from Dmitry Kazakov --- Git commit f49dac3a603d8d40108523be436be1b251966ac5 by Dmitry Kazakov. Committed on 15/04/2020 at 20:48. Pushed by dkazakov into branch 'master'. Fix pan/zoom shortcuts not working after accessing any docker The reason for the bug was that KisExtendedModifiersMapper:: queryExtendedModifiers() has never been implemented for Windows. Therefore all the shortcuts including Space could potentially be lost when the user pressed it without focusing on the canvas. We also need an implementation for OSX. Related: bug 373299, bug 391088 M +53 -3libs/ui/input/kis_extended_modifiers_mapper.cpp https://invent.kde.org/kde/krita/commit/f49dac3a603d8d40108523be436be1b251966ac5 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 419970] Amarok does not play - Does not load Phonon plugins and simply does nothing when I try to start a track
https://bugs.kde.org/show_bug.cgi?id=419970 --- Comment #10 from Myriam Schweingruber --- I changed it because you are talking mostly about the master branch. Amarok 2.9.0 not working anymore on specific distros is not much we can do about, it all depends on the distro packaging and tee availability of the KDE4 libraries, including Phonon. So if a distro decides to remove the libraries, there is of course no way Amarok 2.9.0 could work. Please stick to one version in a bug report, else this is impossible to trace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391088] Pan tool shortcut inactive a few moments after docker widget interaction.
https://bugs.kde.org/show_bug.cgi?id=391088 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/d454a04e713c0f |krita/commit/f49dac3a603d8d |fc4167021680f69be3698871ec |40108523be436be1b251966ac5 --- Comment #10 from Dmitry Kazakov --- Git commit f49dac3a603d8d40108523be436be1b251966ac5 by Dmitry Kazakov. Committed on 15/04/2020 at 20:48. Pushed by dkazakov into branch 'master'. Fix pan/zoom shortcuts not working after accessing any docker The reason for the bug was that KisExtendedModifiersMapper:: queryExtendedModifiers() has never been implemented for Windows. Therefore all the shortcuts including Space could potentially be lost when the user pressed it without focusing on the canvas. We also need an implementation for OSX. Related: bug 372646, bug 373299 M +53 -3libs/ui/input/kis_extended_modifiers_mapper.cpp https://invent.kde.org/kde/krita/commit/f49dac3a603d8d40108523be436be1b251966ac5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372646] Unable to pan after picking color from reference image until canvas is clicked once first
https://bugs.kde.org/show_bug.cgi?id=372646 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/5438445da96517 |krita/commit/d454a04e713c0f |85585ea913c37293737a5ee608 |fc4167021680f69be3698871ec Status|ASSIGNED|RESOLVED --- Comment #15 from Dmitry Kazakov --- Git commit d454a04e713c0ffc4167021680f69be3698871ec by Dmitry Kazakov. Committed on 15/04/2020 at 20:46. Pushed by dkazakov into branch 'krita/4.3'. Fix pan/zoom shortcuts not working after accessing any docker The reason for the bug was that KisExtendedModifiersMapper:: queryExtendedModifiers() has never been implemented for Windows. Therefore all the shortcuts including Space could potentially be lost when the user pressed it without focusing on the canvas. We also need an implementation for OSX. Related: bug 373299, bug 391088 M +53 -3libs/ui/input/kis_extended_modifiers_mapper.cpp https://invent.kde.org/kde/krita/commit/d454a04e713c0ffc4167021680f69be3698871ec -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373299] Zoom shortcuts dont work after focus given to docker windows
https://bugs.kde.org/show_bug.cgi?id=373299 Dmitry Kazakov changed: What|Removed |Added Resolution|DUPLICATE |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/d454a04e713c0f ||fc4167021680f69be3698871ec --- Comment #3 from Dmitry Kazakov --- Git commit d454a04e713c0ffc4167021680f69be3698871ec by Dmitry Kazakov. Committed on 15/04/2020 at 20:46. Pushed by dkazakov into branch 'krita/4.3'. Fix pan/zoom shortcuts not working after accessing any docker The reason for the bug was that KisExtendedModifiersMapper:: queryExtendedModifiers() has never been implemented for Windows. Therefore all the shortcuts including Space could potentially be lost when the user pressed it without focusing on the canvas. We also need an implementation for OSX. Related: bug 372646, bug 391088 M +53 -3libs/ui/input/kis_extended_modifiers_mapper.cpp https://invent.kde.org/kde/krita/commit/d454a04e713c0ffc4167021680f69be3698871ec -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391088] Pan tool shortcut inactive a few moments after docker widget interaction.
https://bugs.kde.org/show_bug.cgi?id=391088 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/d454a04e713c0f ||fc4167021680f69be3698871ec Resolution|DUPLICATE |FIXED --- Comment #9 from Dmitry Kazakov --- Git commit d454a04e713c0ffc4167021680f69be3698871ec by Dmitry Kazakov. Committed on 15/04/2020 at 20:46. Pushed by dkazakov into branch 'krita/4.3'. Fix pan/zoom shortcuts not working after accessing any docker The reason for the bug was that KisExtendedModifiersMapper:: queryExtendedModifiers() has never been implemented for Windows. Therefore all the shortcuts including Space could potentially be lost when the user pressed it without focusing on the canvas. We also need an implementation for OSX. Related: bug 372646, bug 373299 M +53 -3libs/ui/input/kis_extended_modifiers_mapper.cpp https://invent.kde.org/kde/krita/commit/d454a04e713c0ffc4167021680f69be3698871ec -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418898] When using Qt 5.15, Plasmashell crashes inQQmlComponentPrivate::requiredProperties() when "Edit Panel" is selected
https://bugs.kde.org/show_bug.cgi?id=418898 Patrick Silva changed: What|Removed |Added CC||b...@lindev.ch --- Comment #5 from Patrick Silva --- *** Bug 420133 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420133] Plasmashell crashes when selecting "Edit Panel" in the right-click menu
https://bugs.kde.org/show_bug.cgi?id=420133 --- Comment #3 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 418898 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420133] Plasmashell crashes when selecting "Edit Panel" in the right-click menu
https://bugs.kde.org/show_bug.cgi?id=420133 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 415404 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415404] Glitch when moving the cursor on vertical panel with autohide with touch screen edge enabled
https://bugs.kde.org/show_bug.cgi?id=415404 Patrick Silva changed: What|Removed |Added CC||b...@lindev.ch --- Comment #6 from Patrick Silva --- *** Bug 420133 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 420138] New: Connecting any bluetooth device causes Plasma freeze
https://bugs.kde.org/show_bug.cgi?id=420138 Bug ID: 420138 Summary: Connecting any bluetooth device causes Plasma freeze Product: Bluedevil Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: now...@gmail.com Reporter: r...@qkiz.pl CC: plasma-b...@kde.org Target Milestone: --- Created attachment 127582 --> https://bugs.kde.org/attachment.cgi?id=127582=edit syslog SUMMARY When I'm connecting any bluetooth device (phone, headphones) Plasma stucks and not updating. I can move windows , mouse is moving, but panel is not responding clock is not updated. Restarting X helps or removing btusb kernel module. STEPS TO REPRODUCE 1. Enable bluetooth 2. Connect any BT device 3. OBSERVED RESULT Plasma not responding, widgets are not updating. Cant switch windows on panel. EXPECTED RESULT Everything should work fine as in Gnome SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 18.10, KDE 5.18.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION Syslog in attachment -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 420137] New: Missing indentation for info-box caption
https://bugs.kde.org/show_bug.cgi?id=420137 Bug ID: 420137 Summary: Missing indentation for info-box caption Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: mue...@gmail.com Target Milestone: --- Created attachment 127581 --> https://bugs.kde.org/attachment.cgi?id=127581=edit Missing indentation on caption SUMMARY Missing indentation on the info-box caption, see attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398220] Invisible windows appear randomly on wayland
https://bugs.kde.org/show_bug.cgi?id=398220 --- Comment #14 from Kyle Tirak --- I'm on Arch. There's AUR packages. I'll give it a shot when I have a moment. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 420136] New: Varying font sizes on sub-pages
https://bugs.kde.org/show_bug.cgi?id=420136 Bug ID: 420136 Summary: Varying font sizes on sub-pages Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: mue...@gmail.com Target Milestone: --- SUMMARY https://kde.org/plasma-desktop seems to use a bigger font size (see header) than the rest of https://www.kde.org. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419604] Kdenlive freezes when creating a folder during clip playback
https://bugs.kde.org/show_bug.cgi?id=419604
--- Comment #12 from farid ---
Also this after quitting GDB:
(gdb) bt
#0 0x718cca67 in __pthread_clockjoin_ex () at /usr/lib/libpthread.so.0
#1 0x7fffde24a228 in consumer_stop (parent=) at
consumer_sdl2_audio.c:217
#2 0x76f163cc in mlt_consumer_stop (self=0x62e30400) at
mlt_consumer.c:1667
#3 0x56ca46dd in GLWidget::setProducer(std::shared_ptr
const&, bool, int)
(this=0x615fe680, producer=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 4, weak count 1) = {...},
isActive=true, position=-1)
at /home/farid/kdenlive/src/monitor/glwidget.cpp:924
#4 0x56cf7b56 in Monitor::slotOpenClip(std::shared_ptr
const&, int, int)
(this=0x6140003bbe40, controller=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {...}, in=-1,
out=-1)
at /home/farid/kdenlive/src/monitor/monitor.cpp:1445
#5 0x564b271c in
Bin::setMonitor(Monitor*)::$_39::operator()(std::shared_ptr, int,
int) const
(this=0x60370790, clip=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {...}, in=-1,
out=-1)
at /home/farid/kdenlive/src/bin/bin.cpp:1556
#6 0x564b2586 in QtPrivate::FunctorCall, QtPrivate::List, int, int>, void,
Bin::setMonitor(Monitor*)::$_39>::call(Bin::setMonitor(Monitor*)::$_39&,
void**)
(f=..., arg=0x7fff8d40) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#7 0x564b22b1 in QtPrivate::Functor::call, int, int>,
void>(Bin::setMonitor(Monitor*)::$_39&, void*, void**) (f=...,
arg=0x7fff8d40)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:256
#8 0x564b21cf in
QtPrivate::QFunctorSlotObject, int, int>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
(which=1, this_=0x60370780, r=0x61653d80, a=0x7fff8d40,
ret=0x0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:443
#9 0x71effcde in () at /usr/lib/libQt5Core.so.5
#10 0x55fc1c98 in Bin::openClip(std::shared_ptr, int, int)
(this=0x61653d80, _t1=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {...}, _t2=-1,
_t3=-1)
at kdenliveLib_autogen/NNRPYQ7WAA/moc_bin.cpp:1475
#11 0x5645b722 in Bin::openProducer(std::shared_ptr)
--Type for more, q to quit, c to continue without paging--
(this=0x61653d80, controller=std::shared_ptr (empty) =
{...})
at /home/farid/kdenlive/src/bin/bin.cpp:2459
#12 0x56441c66 in Bin::setCurrent(std::shared_ptr
const&) (this=0x61653d80, item=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {...})
at /home/farid/kdenlive/src/bin/bin.cpp:3865
#13 0x56440733 in Bin::selectProxyModel(QModelIndex const&)
(this=0x61653d80, id=...)
at /home/farid/kdenlive/src/bin/bin.cpp:1810
#14 0x564b9480 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (Bin::*)(QModelIndex
const&)>::call(void (Bin::*)(QModelIndex const&), Bin*, void**) (f=
(void (Bin::*)(Bin * const, const QModelIndex &)) 0x56440130
, o=0x61653d80,
arg=0x7fff9e20) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152
#15 0x564b90be in QtPrivate::FunctionPointer::call, void>(void
(Bin::*)(QModelIndex const&), Bin*, void**) (f=
(void (Bin::*)(Bin * const, const QModelIndex &)) 0x56440130
, o=0x61653d80,
arg=0x7fff9e20) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185
#16 0x564b8bca in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
(which=1, this_=0x603000a60780, r=0x61653d80, a=0x7fff9e20,
ret=0x0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:418
#17 0x71effcde in () at /usr/lib/libQt5Core.so.5
#18 0x55fced56 in ProjectSortProxyModel::selectModel(QModelIndex
const&) (this=0x606000dc5e00, _t1=...)
at kdenliveLib_autogen/NNRPYQ7WAA/moc_projectsortproxymodel.cpp:203
#19 0x566098e5 in
ProjectSortProxyModel::onCurrentRowChanged(QItemSelection const&,
QItemSelection const&)
(this=0x606000dc5e00, current=..., previous=...) at
/home/farid/kdenlive/src/bin/projectsortproxymodel.cpp:172
#20 0x5660e84c in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(ProjectSortProxyModel::*)(QItemSelection const&, QItemSelection
const&)>::call(void (ProjectSortProxyModel::*)(QItemSelection const&,
QItemSelection const&), ProjectSortProxyModel*, void**) (f=
[kdenlive] [Bug 419604] Kdenlive freezes when creating a folder during clip playback
https://bugs.kde.org/show_bug.cgi?id=419604
--- Comment #11 from farid ---
Does this say anything (full log attached):
Thread 1 (Thread 0x7fffec5708c0 (LWP 9444)):
#0 0x718cca67 in __pthread_clockjoin_ex () at /usr/lib/libpthread.so.0
#1 0x7fffde24a228 in consumer_stop (parent=) at
consumer_sdl2_audio.c:217
self = 0x62e30400
#2 0x76f163cc in mlt_consumer_stop (self=0x62e30400) at
mlt_consumer.c:1667
properties = 0x62e30400
priv = 0x61400069d040
#3 0x56ca46dd in GLWidget::setProducer(std::shared_ptr
const&, bool, int) (this=0x615fe680, producer=warning: RTTI symbol not
found for class 'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 4, weak count 1) = {...},
isActive=true, position=-1) at
/home/farid/kdenlive/src/monitor/glwidget.cpp:924
currentId = {static null = {}, d = 0x603000d10e30}
--Type for more, q to quit, c to continue without paging--
error = 0
consumerPosition = 189
#4 0x56cf7b56 in Monitor::slotOpenClip(std::shared_ptr
const&, int, int) (this=0x6140003bbe40, controller=warning: RTTI symbol not
found for class 'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {...}, in=-1,
out=-1) at /home/farid/kdenlive/src/monitor/monitor.cpp:1445
#5 0x564b271c in
Bin::setMonitor(Monitor*)::$_39::operator()(std::shared_ptr, int,
int) const (this=0x60370790, clip=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {...}, in=-1,
out=-1) at /home/farid/kdenlive/src/bin/bin.cpp:1556
#6 0x564b2586 in QtPrivate::FunctorCall, QtPrivate::List, int, int>, void,
Bin::setMonitor(Monitor*)::$_39>::call(Bin::setMonitor(Monitor*)::$_39&,
void**) (f=..., arg=0x7fff8d40) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#7 0x564b22b1 in QtPrivate::Functor::call, int, int>,
void>(Bin::setMonitor(Monitor*)::$_39&, void*, void**) (f=...,
arg=0x7fff8d40) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256
#8 0x564b21cf in
QtPrivate::QFunctorSlotObject, int, int>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x60370780, r=0x61653d80, a=0x7fff8d40, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#9 0x71effcde in () at /usr/lib/libQt5Core.so.5
#10 0x55fc1c98 in Bin::openClip(std::shared_ptr, int, int)
(this=0x61653d80, _t1=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {...}, _t2=-1,
_t3=-1) at kdenliveLib_autogen/NNRPYQ7WAA/moc_bin.cpp:1475
--Type for more, q to quit, c to continue without paging--
_a = {0x0, 0x7fff8ea0, 0x7fff8d20, 0x7fff8d30}
#11 0x5645b722 in Bin::openProducer(std::shared_ptr)
(this=0x61653d80, controller=std::shared_ptr (empty) = {...})
at /home/farid/kdenlive/src/bin/bin.cpp:2459
#12 0x56441c66 in Bin::setCurrent(std::shared_ptr
const&) (this=0x61653d80, item=warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {...}) at
/home/farid/kdenlive/src/bin/bin.cpp:3865
clp = std::shared_ptr (use count 1426063428, weak count
1223002439) = {get() = 0x7fff8ff0}
#13 0x56440733 in Bin::selectProxyModel(QModelIndex const&)
(this=0x61653d80, id=...) at /home/farid/kdenlive/src/bin/bin.cpp:1810
currentItem = warning: RTTI symbol not found for class
'std::_Sp_counted_ptr'
warning: RTTI symbol not found for class 'std::_Sp_counted_ptr'
std::shared_ptr (use count 7, weak count 2) = {get() =
0x617000222b00}
#14 0x564b9480 in QtPrivate::FunctorCall,
QtPrivate::List, void, void (Bin::*)(QModelIndex
const&)>::call(void (Bin::*)(QModelIndex const&), Bin*, void**) (f=(void
(Bin::*)(Bin * const, const QModelIndex &)) 0x56440130
, o=0x61653d80,
arg=0x7fff9e20) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152
#15 0x564b90be in QtPrivate::FunctionPointer::call, void>(void
(Bin::*)(QModelIndex const&), Bin*, void**) (f=(void (Bin::*)(Bin * const,
const QModelIndex &)) 0x56440130 , o=0x61653d80, arg=0x7fff9e20) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:185
#16 0x564b8bca in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x603000a60780, r=0x61653d80, a=0x7fff9e20, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:418
#17 0x71effcde in () at /usr/lib/libQt5Core.so.5
#18 0x55fced56 in ProjectSortProxyModel::selectModel(QModelIndex
const&) (this=0x606000dc5e00, _t1=...) at kde--Type
[kdenlive] [Bug 419604] Kdenlive freezes when creating a folder during clip playback
https://bugs.kde.org/show_bug.cgi?id=419604 farid changed: What|Removed |Added Attachment #127579|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419604] Kdenlive freezes when creating a folder during clip playback
https://bugs.kde.org/show_bug.cgi?id=419604 --- Comment #10 from farid --- Created attachment 127580 --> https://bugs.kde.org/attachment.cgi?id=127580=edit gdb log full -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419604] Kdenlive freezes when creating a folder during clip playback
https://bugs.kde.org/show_bug.cgi?id=419604 --- Comment #9 from farid --- Created attachment 127579 --> https://bugs.kde.org/attachment.cgi?id=127579=edit gdb log -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418460] Tray notification icons are missing
https://bugs.kde.org/show_bug.cgi?id=418460 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #7 from Nate Graham --- Ah, that! *** This bug has been marked as a duplicate of bug 418662 *** -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 420038] When I go to RENAME in Dolphin, there are no options in Portuguese (PT-BR) which is the default language, but in English some options.
https://bugs.kde.org/show_bug.cgi?id=420038 --- Comment #4 from Luiz Fernando Ranghetti --- Hi, If this comes from Qt its correct, Qt doesn't have pt_BR translations, I tried last year but it was not incorporated yet (I doubt it will ever be): https://bugreports.qt.io/browse/QTBUG-74431 Regards -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418662] Some system tray icons seem to choose the wrong color/become invisible
https://bugs.kde.org/show_bug.cgi?id=418662 Nate Graham changed: What|Removed |Added CC||med.medin.2...@gmail.com --- Comment #3 from Nate Graham --- *** Bug 418460 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401154] gwenview should not change image colors if system-wide color management is enabled
https://bugs.kde.org/show_bug.cgi?id=401154 --- Comment #13 from Christoph Feck --- Both conversions (from image to CIEXYZ, and from CIEXYZ to monitor) are merged into a single transformation inside liblcms2. Applications don't transfer CIEXYZ data to the X11 server; they only transfer (hardware) (s)RGB. The purpose of the CMS server is to ensure that applications that are not aware of the CMS are treated as sRGB input (usually, but that is changeable), and then the server can apply the monitor color space transformations according to its profile. If this was a two step transformation, then you would effectively need to go from image color space to sRGB, then from sRGB to the monitor space, and this could cause loss of color data, because both the image and the monitor could be wider than sRGB. If CMSs were a deal when X11 was invented, it would have required that applications send CIEXYZ data, instead of RGB data. But alas... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419622] Close/hide the Discover window during install
https://bugs.kde.org/show_bug.cgi?id=419622 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Nate Graham --- Oh I see, it just takes up space. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 419097] Wrong icon for Raku/perl6
https://bugs.kde.org/show_bug.cgi?id=419097 Christoph Feck changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Christoph Feck --- No, it doesn't help, because only Dolphin and Krusader are using KDE code. If both show the issue, then the bug is in a lower level KDE framework. But if you say Dolphin messes up your system, we need to wait until someone can provide the information requested in comment 1. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419622] Close/hide the Discover window during install
https://bugs.kde.org/show_bug.cgi?id=419622 --- Comment #5 from dagobert...@mailbox.org --- I'm sorry english is not my first language ... Maybe it is called the task switcher? It just takes up space, where other windows might sit. I just attached a screenshot which might help describing. -- You are receiving this mail because: You are watching all bug changes.
[knetattach] [Bug 420135] New: Network Folder Wizard does not accept protocol name in server field
https://bugs.kde.org/show_bug.cgi?id=420135 Bug ID: 420135 Summary: Network Folder Wizard does not accept protocol name in server field Product: knetattach Version: 5.18.4 Platform: unspecified OS: unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eidu...@outlook.com Target Milestone: --- When using the Network Folder Wizard to add an FTP location, a user may enter "ftp://; in front of the server address in the "Server:" field. This prompts an error message as only the numerical address should be entered. It may take the user a long time to figure out why it doesn't work. It would therefore be helpful to either: 1) Automatically remove "ftp://; from the string, or... 2) present a meaningful error message about the "Server:" field. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419622] Close/hide the Discover window during install
https://bugs.kde.org/show_bug.cgi?id=419622 --- Comment #4 from dagobert...@mailbox.org --- Created attachment 127578 --> https://bugs.kde.org/attachment.cgi?id=127578=edit Discover "blocks" the task bar since there is less free space -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366462] Desktop icons cannot be interacted with via touch
https://bugs.kde.org/show_bug.cgi?id=366462 The Feren OS Dev changed: What|Removed |Added CC||ferenos...@outlook.com --- Comment #17 from The Feren OS Dev --- I can also reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418460] Tray notification icons are missing
https://bugs.kde.org/show_bug.cgi?id=418460 --- Comment #6 from medin --- (In reply to Nate Graham from comment #3) > What exactly is the problem here? Can you clarify? In the last upgrades this problem is not visible, but earlier after upgrading some 3rd apps (like Copyq) notification indicators become missing in notification area. I will try to observe if I get the same bug in future upgrades -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419135] On the fonts settings page, the Apply button is enabled, even if there were no changes
https://bugs.kde.org/show_bug.cgi?id=419135 hexclo...@outlook.com changed: What|Removed |Added CC||hexclo...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 420134] New: usb wacom one tablet conflict with kde
https://bugs.kde.org/show_bug.cgi?id=420134 Bug ID: 420134 Summary: usb wacom one tablet conflict with kde Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: cristianb...@hotmail.com Target Milestone: --- Application: kded4 (4.14.32) KDE Platform Version: 4.14.32 Qt Version: 4.8.7 Operating System: Linux 4.9.40-wifislax64 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: connecting usb wacom one tablet. After this a message telling kde suddenly stopped o likewise appeared, and printscreen key did not launch ksnapshot The crash can be reproduced every time. -- Backtrace: Application: Servicio de KDE (kded4), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7ff3fd8bb77d in KConfigGroup::readEntry(char const*, QString const&) const () at /usr/lib64/libkdecore.so.5 #7 0x7ff3fd8c04f2 in KConfigGroup::readEntry(char const*, QStringList const&) const () at /usr/lib64/libkdecore.so.5 #8 0x7ff3fd8c05b2 in KConfigGroup::readEntry(QString const&, QStringList const&) const () at /usr/lib64/libkdecore.so.5 #9 0x7ff3df09cb78 in Wacom::ProfileManager::profileRotationList() const () at /usr/lib64/kde4/kded_wacomtablet.so #10 0x7ff3df09ce12 in Wacom::ProfileManager::profileNumber(QString const&) const () at /usr/lib64/kde4/kded_wacomtablet.so #11 0x7ff3df09d4c9 in Wacom::ProfileManager::udpdateCurrentProfileNumber(QString const&) () at /usr/lib64/kde4/kded_wacomtablet.so #12 0x7ff3df08eaf7 in Wacom::TabletHandler::setProfile(QString const&, QString const&) () at /usr/lib64/kde4/kded_wacomtablet.so #13 0x7ff3df08b818 in Wacom::TabletHandler::onTabletAdded(Wacom::TabletInformation const&) () at /usr/lib64/kde4/kded_wacomtablet.so #14 0x7ff3df080eb1 in Wacom::TabletHandler::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.2] () at /usr/lib64/kde4/kded_wacomtablet.so #15 0x7ff3fd22de30 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/qt/lib/libQtCore.so.4 #16 0x7ff3df081752 in Wacom::TabletFinder::tabletAdded(Wacom::TabletInformation) () at /usr/lib64/kde4/kded_wacomtablet.so #17 0x7ff3df088822 in Wacom::TabletFinder::scan() () at /usr/lib64/kde4/kded_wacomtablet.so #18 0x7ff3df0879de in Wacom::TabletDaemon::TabletDaemon(QObject*, QList const&) () at /usr/lib64/kde4/kded_wacomtablet.so #19 0x7ff3df088328 in QObject* KPluginFactory::createInstance(QWidget*, QObject*, QList const&) () at /usr/lib64/kde4/kded_wacomtablet.so #20 0x7ff3fda2ac52 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () at /usr/lib64/libkdecore.so.5 #21 0x7ff3e62ee53a in () at /usr/lib64/libkdeinit4_kded4.so #22 0x7ff3e62eef07 in () at /usr/lib64/libkdeinit4_kded4.so #23 0x7ff3e62ef760 in () at /usr/lib64/libkdeinit4_kded4.so #24 0x7ff3e62ef7c3 in () at /usr/lib64/libkdeinit4_kded4.so #25 0x7ff3e62f1e8a in () at /usr/lib64/libkdeinit4_kded4.so #26 0x7ff3fe280e1b in () at /usr/lib64/libkdeui.so.5 #27 0x7ff3fe280e95 in () at /usr/lib64/libkdeui.so.5 #28 0x7ff3fe2810e3 in () at /usr/lib64/libkdeui.so.5 #29 0x7ff3fd5aa135 in () at /usr/lib64/qt/lib/libQtDBus.so.4 #30 0x7ff3fd5ab60b in () at /usr/lib64/qt/lib/libQtDBus.so.4 #31 0x7ff3fd5ac2f7 in () at /usr/lib64/qt/lib/libQtDBus.so.4 #32 0x7ff3fd5ac4fb in () at /usr/lib64/qt/lib/libQtDBus.so.4 #33 0x7ff3fd233921 in QObject::event(QEvent*) () at /usr/lib64/qt/lib/libQtCore.so.4 #34 0x7ff3fc37585f in QApplication::event(QEvent*) () at /usr/lib64/qt/lib/libQtGui.so.4 #35 0x7ff3fc37048c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtGui.so.4 #36 0x7ff3fc376f5c in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtGui.so.4 #37 0x7ff3fe2798aa in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #38 0x7ff3fd21ac0d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/qt/lib/libQtCore.so.4 #39 0x7ff3fd21de6e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/qt/lib/libQtCore.so.4 #40 0x7ff3fd248f3e in () at /usr/lib64/qt/lib/libQtCore.so.4 #41 0x7ff3f7ad4797 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #42 0x7ff3f7ad49c8 in () at /usr/lib64/libglib-2.0.so.0 #43 0x7ff3f7ad4a6c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #44 0x7ff3fd2490ae in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #45 0x7ff3fc4139e6 in () at
[plasmashell] [Bug 419596] Double clicking on mp3 file freezes plasma desktop
https://bugs.kde.org/show_bug.cgi?id=419596 --- Comment #3 from medin --- Created attachment 127577 --> https://bugs.kde.org/attachment.cgi?id=127577=edit Elisa crashes desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419596] Double clicking on mp3 file freezes plasma desktop
https://bugs.kde.org/show_bug.cgi?id=419596 --- Comment #2 from medin --- (In reply to Nate Graham from comment #1) > Cannot reproduce with Elisa and an MP3 file on the desktop. The same bug happens using right mouse click, I tried changing from modesetting driver to intel but the result is the same, you can see my attached video for more info. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419604] Kdenlive freezes when creating a folder during clip playback
https://bugs.kde.org/show_bug.cgi?id=419604 --- Comment #8 from emohr --- I tested as you showed. It doesn't crash but the "switch" from one clip to the other take in some cases some time. Here a log from Visual Studio showing this "switch": The thread 0x1784 has exited with code 0 (0x0). The thread 0x1924 has exited with code 0 (0x0). MUTEX LOCK setmodel MUTEX UNLOCK setmodel MUTEX LOCK loadEffects COUNT: 0 /// GOT AUDIO TRACKS: (7) The thread 0x218c has exited with code 0 (0x0). The thread 0x212c has exited with code 0 (0x0). The thread 0x22e0 has exited with code 0 (0x0). The thread 0x1490 has exited with code 0 (0x0). The thread 0x2224 has exited with code 0 (0x0). The thread 0x1c10 has exited with code 0 (0x0). MUTEX LOCK setmodel MUTEX UNLOCK setmodel MUTEX LOCK loadEffects COUNT: 0 /// GOT AUDIO TRACKS: (7) The thread 0xc68 has exited with code 0 (0x0). The thread 0x22c0 has exited with code 0 (0x0). The thread 0x1208 has exited with code 0 (0x0). The thread 0x1944 has exited with code 0 (0x0). The thread 0x2174 has exited with code 0 (0x0). The thread 0x1918 has exited with code 0 (0x0). The thread 0x13d4 has exited with code 0 (0x0). MUTEX LOCK setmodel MUTEX UNLOCK setmodel MUTEX LOCK loadEffects COUNT: 0 /// GOT AUDIO TRACKS: (7) The thread 0x215c has exited with code 0 (0x0). The thread 0x14dc has exited with code 0 (0x0). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 401154] gwenview should not change image colors if system-wide color management is enabled
https://bugs.kde.org/show_bug.cgi?id=401154 --- Comment #12 from Misha Aizatulin --- > Gwenview should convert it to the current monitor's profile (or just sRGB, in > case none is set). I might be misunderstanding how color management works, but is applying a profile a composable operation? If so, is it then correct to say that the job of gwenview is to apply the image profile and the job of X is to apply the system profile? If that is correct then why does gwenview need to know the system profile? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402432] Konsole Add-On Installer crashes when entering a search term
https://bugs.kde.org/show_bug.cgi?id=402432 --- Comment #6 from Christoph Feck --- Probably caused by the nested event loop from KNS3::DownloadDialog::exec(). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358071] Kmail adds wrong contacts to e-mail when using contact groups
https://bugs.kde.org/show_bug.cgi?id=358071 --- Comment #3 from Christoph Feck --- We didn't find a developer or contributor yet who is able to investigate this issue. -- You are receiving this mail because: You are watching all bug changes.
