[krita] [Bug 407205] You can no longer drag and drop using tab mode
https://bugs.kde.org/show_bug.cgi?id=407205 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- I confirm this in master. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354364] Crash of DNG converter
https://bugs.kde.org/show_bug.cgi?id=354364 Maik Qualmann changed: What|Removed |Added CC||g...@gkrathbun.net --- Comment #39 from Maik Qualmann --- *** Bug 407203 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 407203] Crash on trying to convert a .NEF file
https://bugs.kde.org/show_bug.cgi?id=407203 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- You are using very old software. Here a icon is missing in the icon set, read the description of the double bug report. If there are no newer packages for your distribution, you can also try the AppImage from www.digikam.org. Maik *** This bug has been marked as a duplicate of bug 354364 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407197] Target album does not exist
https://bugs.kde.org/show_bug.cgi?id=407197 Maik Qualmann changed: What|Removed |Added Summary|standartzielalum|Target album does not exist -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407197] standartzielalum
https://bugs.kde.org/show_bug.cgi?id=407197 Maik Qualmann changed: What|Removed |Added Component|Albums-MainView |Import-Albums -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407011] kdenlive 18.12.3 MP4/VOB rendering looses lip sync after adding 2nd audio track
https://bugs.kde.org/show_bug.cgi?id=407011 --- Comment #1 from Peter Bieringer --- Just note if I delete the in kdenlive streched WAV and imported one stretched with ffmpeg, all works fine again -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407197] standartzielalum
https://bugs.kde.org/show_bug.cgi?id=407197 Maik Qualmann changed: What|Removed |Added Resolution|--- |WORKSFORME Version Fixed In||6.2.0 CC||metzping...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Maik Qualmann --- You have enabled the option to download the images to a target album. Your default album for download was deleted or moved. Go to Camera Settings and select a new destination album. This is not a program error. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407205] You can no longer drag and drop using tab mode
https://bugs.kde.org/show_bug.cgi?id=407205 --- Comment #1 from reptilli...@live.com --- layer docker* Correction. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407205] New: You can no longer drag and drop using tab mode
https://bugs.kde.org/show_bug.cgi?id=407205 Bug ID: 407205 Summary: You can no longer drag and drop using tab mode Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: reptilli...@live.com Target Milestone: --- SUMMARY Basically what title said. You could do it in subwindow mode fine and dandy.I would like to see it work on tab mode. STEPS TO REPRODUCE Tab Mode 1. Open two images. 2. Click and hold the button over the layer. 3. Move it over the title of the document. 4. See the nope cursor To verify it works on Subwindow mode After Step #3, you simply move it into the layer document after the subwindow switched OBSERVED RESULT No indication it works EXPECTED RESULT Behaves like the sub-window counterpart SOFTWARE/OS VERSIONS Windows: 10 x64 Qt Version: 5.12 Software : Krita 4.2 Pre-Alpha git dd3746f ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405369] Cursor preferences no longer respected
https://bugs.kde.org/show_bug.cgi?id=405369 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.
[kdenlive] [Bug 373813] Crash when inserting new track above the first one
https://bugs.kde.org/show_bug.cgi?id=373813 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[konqueror] [Bug 405816] virtualbox freebsd host=linux arch
https://bugs.kde.org/show_bug.cgi?id=405816 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392932] Window position fault with 4.1.0 pre-alpha (2d068df) appimage Window Layouts tool
https://bugs.kde.org/show_bug.cgi?id=392932 Bug Janitor Service changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405949] software is broken
https://bugs.kde.org/show_bug.cgi?id=405949 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #13 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405549] "Waiting for image to complete operation"
https://bugs.kde.org/show_bug.cgi?id=405549 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[plasmashell] [Bug 405982] Crash when using grouped window list
https://bugs.kde.org/show_bug.cgi?id=405982 --- 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.
[kdenlive] [Bug 374171] Kdenlive crashed when closing and saving a project
https://bugs.kde.org/show_bug.cgi?id=374171 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.
[frameworks-baloo] [Bug 405317] Cannot find file just created in home directory
https://bugs.kde.org/show_bug.cgi?id=405317 --- Comment #24 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.
[kdenlive] [Bug 407204] New: Dissolve effect fades black.
https://bugs.kde.org/show_bug.cgi?id=407204 Bug ID: 407204 Summary: Dissolve effect fades black. Product: kdenlive Version: 17.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: zibby...@gmail.com Target Milestone: --- Anywhere there is a dissolve transition the video fades to/from black. It is only visible in the final rendered video. I tried various rendering methods and they all seem to have the same issue. Using Xubuntu 18.04 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406784] Alt-tab makes KWin crash when the window is destroyed during switch
https://bugs.kde.org/show_bug.cgi?id=406784 Nate Graham changed: What|Removed |Added Version Fixed In||5.16.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 QIN Yuhao changed: What|Removed |Added CC||qinq_...@buaa.edu.cn -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 407203] New: Crash on trying to convert a .NEF file
https://bugs.kde.org/show_bug.cgi?id=407203 Bug ID: 407203 Summary: Crash on trying to convert a .NEF file Product: kipiplugins Version: 4.12.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: imaging-bugs-n...@kde.org Reporter: g...@gkrathbun.net Target Milestone: --- Application: dngconverter (4.12.0) KDE Platform Version: 4.14.16 Qt Version: 4.8.7 Operating System: Linux 4.4.0-146-generic x86_64 Distribution: Ubuntu 16.04.6 LTS -- Information about the crash: - What I was doing when the application crashed: I clicked on the filename of the NEF (Nikon D810's RAW format) file in Dolphin, and it opened DNG converter. I didn't change any settings, just clicked the Convert button, and the app immediately crashed. - Custom settings of the application: None. All settings left at default. The crash can be reproduced every time. -- Backtrace: Application: DNG Image Converter (dngconverter), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f12b3344980 (LWP 10402))] Thread 6 (Thread 0x7f128700 (LWP 10410)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f12b16b13a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f12b2690c9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f12b2693993 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f12b26924ef in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #5 0x7f12b16b0e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f12b05036ba in start_thread (arg=0x7f128700) at pthread_create.c:333 #7 0x7f12af99841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f129d95c700 (LWP 10407)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f12b16b13a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f12b2690c9c in ?? () from /usr/lib/libthreadweaver.so.4 #3 0x7f12b2693993 in ?? () from /usr/lib/libthreadweaver.so.4 #4 0x7f12b26939ac in ?? () from /usr/lib/libthreadweaver.so.4 #5 0x7f12b26924ef in ThreadWeaver::Thread::run() () from /usr/lib/libthreadweaver.so.4 #6 0x7f12b16b0e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f12b05036ba in start_thread (arg=0x7f129d95c700) at pthread_create.c:333 #8 0x7f12af99841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f129e1af700 (LWP 10406)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f12b16b13a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f12b2b38a14 in KDcrawIface::RActionThreadBase::run() () from /usr/lib/libkdcraw.so.23 #3 0x7f12b16b0e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f12b05036ba in start_thread (arg=0x7f129e1af700) at pthread_create.c:333 #5 0x7f12af99841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f129e9b0700 (LWP 10404)): #0 0x7f12af98c74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f12aba8238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f12aba8249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f12b17f12ce in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f12b17bf18f in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f12b17bf4f5 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f12b16ae549 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f12b179f223 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f12b16b0e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f12b05036ba in start_thread (arg=0x7f129e9b0700) at pthread_create.c:333 #10 0x7f12af99841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f129f1b1700 (LWP 10403)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f12b16b13a6 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f12b28d776e in KIPIPlugins::KPRawThumbThread::run() () from /usr/lib/digikam/libkipiplugins.so.4.12.0 #3 0x7f12b16b0e3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f12b05036ba in start_thread (arg=0x7f129f1b1700)
[konsole] [Bug 406828] Color of title of not currently selected tab not changed when new output appears
https://bugs.kde.org/show_bug.cgi?id=406828
--- Comment #3 from Arfrever Frehtes Taifersar Arahesis
---
This problem was introduced in commit 6e8153a78e3c63e514a6ecb62f6c9b4b504e7eb7:
https://cgit.kde.org/konsole.git/commit/?id=6e8153a78e3c63e514a6ecb62f6c9b4b504e7eb7
commit 6e8153a78e3c63e514a6ecb62f6c9b4b504e7eb7
(refs/git-r3/kde-apps/konsole/5/__main__)
Author: Tomaz Canabrava
AuthorDate: 2019-03-26 21:33:09 -0400
Commit: Kurt Hindenburg
CommitDate: 2019-03-26 21:50:18 -0400
Multiple Splits per Tab
Summary:
This is what I envision for the Konsole Tab / Splits
management. One tab contain a QSPlitter that can contain
multiple TerminalDisplays / Splits.
You can test this behavior by hitting ctrl + shift + 9
and ctrl + shift + 0 to activate the splits, and ctrl +
shift + t to activate a new tab.
Old:
{F6484123}
New:
{F6484124}
What works:
- Tab Creation
- Split Creation (Even Recursive splitting)
- Terminal Close will close the Split on last split
- Last last split to close will close the tab
- Last tab to close will close konsole
- Detaching
- Tab Renaming
- Closing splits after detach
- Closing windows after detach
- Detach / Reattach works!
This patch series has the commits of Thomas Surrel, Maciej Niedbdalski and
Myself.
Reviewers: #konsole, hindenburg
Reviewed By: #konsole, hindenburg
Subscribers: luc4, hallas, anthonyfieroni, gennad, ngraham, thsurrel,
maciejn, mglb, hindenburg, konsole-devel
Tags: #konsole
Differential Revision: https://phabricator.kde.org/D17643
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 406752] Menu for "New Tab" button shown in incorrect location for non-first triggering
https://bugs.kde.org/show_bug.cgi?id=406752 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added CC||da...@davidhallas.dk --- Comment #6 from Arfrever Frehtes Taifersar Arahesis --- This problem was introduced in commit 03a78c2a9f4248653e928c341bb4610c4aeea33b: https://cgit.kde.org/konsole.git/commit/?id=03a78c2a9f4248653e928c341bb4610c4aeea33b commit 03a78c2a9f4248653e928c341bb4610c4aeea33b (HEAD) Author: David Hallas AuthorDate: 2019-03-28 08:55:18 -0400 Commit: Kurt Hindenburg CommitDate: 2019-03-28 09:14:13 -0400 Fixes minor memory leaks Summary: Fixes a few minor memory leaks found with address sanitizer. The newTabButton and closeTabButton was not passed a parent and is not deleted in the destructor of TabbedViewContainer which will cause them to be leaked when closing a tab. Instead pass the TabbedViewContainer as the parent. The same goes for the profileMenu, it was not passed a parent pointer at contruction and the setMenu function doesn't take ownership of it, so therefore it was also leaked. Test Plan: Compile konsole with address sanitizer. Open and close konsole. Reviewers: #konsole, hindenburg Reviewed By: #konsole, hindenburg Subscribers: hindenburg, konsole-devel Tags: #konsole Differential Revision: https://phabricator.kde.org/D19634 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406828] Color of title of not currently selected tab not changed when new output appears
https://bugs.kde.org/show_bug.cgi?id=406828 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=406752| -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406828] Color of title of not currently selected tab not changed when new output appears
https://bugs.kde.org/show_bug.cgi?id=406828 --- Comment #2 from Arfrever Frehtes Taifersar Arahesis --- (In reply to Arfrever Frehtes Taifersar Arahesis from comment #4) > This problem was introduced in commit > 4cddc420e319686956446da2724a27a672817ff1 I have been deceived by https://cgit.kde.org/konsole.git/log/?h=master showing commits from all branches (not only "master" branch) (while e.g. https://cgit.kde.org/konsole.git/log/?h=Applications/19.04 shows commits from only "Applications/19.04" branch). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406752] Menu for "New Tab" button shown in incorrect location for non-first triggering
https://bugs.kde.org/show_bug.cgi?id=406752 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added CC|tcanabr...@kde.org | --- Comment #5 from Arfrever Frehtes Taifersar Arahesis --- (In reply to Arfrever Frehtes Taifersar Arahesis from comment #4) > This problem was introduced in commit > 4cddc420e319686956446da2724a27a672817ff1 I have been deceived by https://cgit.kde.org/konsole.git/log/?h=master showing commits from all branches (not only "master" branch) (while e.g. https://cgit.kde.org/konsole.git/log/?h=Applications/19.04 shows commits from only "Applications/19.04" branch). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406752] Menu for "New Tab" button shown in incorrect location for non-first triggering
https://bugs.kde.org/show_bug.cgi?id=406752 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=406828| -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406828] Color of title of not currently selected tab not changed when new output appears
https://bugs.kde.org/show_bug.cgi?id=406828 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=406752 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406752] Menu for "New Tab" button shown in incorrect location for non-first triggering
https://bugs.kde.org/show_bug.cgi?id=406752 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=406828 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406752] Menu for "New Tab" button shown in incorrect location for non-first triggering
https://bugs.kde.org/show_bug.cgi?id=406752 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added CC||tcanabr...@kde.org --- Comment #4 from Arfrever Frehtes Taifersar Arahesis --- This problem was introduced in commit 4cddc420e319686956446da2724a27a672817ff1: https://cgit.kde.org/konsole.git/commit/?id=4cddc420e319686956446da2724a27a672817ff1 commit 4cddc420e319686956446da2724a27a672817ff1 Author: Tomaz Canabrava AuthorDate: 2019-03-28 09:27:15 -0400 Commit: Kurt Hindenburg CommitDate: 2019-03-28 09:50:38 -0400 Simplify TerminalDisplay code Reviewers: #konsole, hindenburg Reviewed By: #konsole, hindenburg Subscribers: hindenburg, konsole-devel Tags: #konsole Differential Revision: https://phabricator.kde.org/D20088 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406828] Color of title of not currently selected tab not changed when new output appears
https://bugs.kde.org/show_bug.cgi?id=406828 Arfrever Frehtes Taifersar Arahesis changed: What|Removed |Added CC||tcanabr...@kde.org --- Comment #1 from Arfrever Frehtes Taifersar Arahesis --- This problem was introduced in commit 4cddc420e319686956446da2724a27a672817ff1: https://cgit.kde.org/konsole.git/commit/?id=4cddc420e319686956446da2724a27a672817ff1 commit 4cddc420e319686956446da2724a27a672817ff1 Author: Tomaz Canabrava AuthorDate: 2019-03-28 09:27:15 -0400 Commit: Kurt Hindenburg CommitDate: 2019-03-28 09:50:38 -0400 Simplify TerminalDisplay code Reviewers: #konsole, hindenburg Reviewed By: #konsole, hindenburg Subscribers: hindenburg, konsole-devel Tags: #konsole Differential Revision: https://phabricator.kde.org/D20088 -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 407194] Honor system font scaling setting
https://bugs.kde.org/show_bug.cgi?id=407194 --- Comment #3 from Aleix Pol --- Can you make sure you have org.kde.PlatformTheme.QGnomePlatform installed? It could make sense to have this issue tracked in there https://github.com/flathub/org.kde.PlatformTheme.QGnomePlatform -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396675] Could not save - Failed to save the annotations for layer ...
https://bugs.kde.org/show_bug.cgi?id=396675 ocumo changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Version|4.1.0 |unspecified --- Comment #8 from ocumo --- Sadly, this project behaves like a one man's show, despite of what other enthusiastic contexts say, where even big names like Intel or Google are mentioned. The truth is, when the leader is down (for understandable and worrying reasons), there is a huge impact. Not a criticism, it's hard reality, as has been rather rudely expressed several times in comments in bug reports. Some hard facts that don't play nicely about krita's "team" response to this serious issue: 1. Despite overwhelming demonstrations that this problem will (and I bet that it does) affect others in a valid use case, there has been no noticeable interest in this bug. 2. Not only there is lack of user's interest or, more likely, lack of knowledge and stomack for entering the ugly world of bugs reports. The problem extends more importantly to krita's team. "Doesn't affect me? Then too bad." Fact, there are not enough people to even look at what has cost me dozens of hours of troubleshooting and reporting, late at night, making huge efforts to painfully demonstrate a real problem in real case scenario. It is announced in some places that there is a team, but there is only one person looking at this bug report. With indeed only one person looking at this, it is impossible to manage the workload, and one could hardly blame such overwhelmed person, only wish him to take care of his health seriously. This is absolutely insane. 3. I have lost the count of the times I have been told that this is not a krita's code problem. Frankly, it's beyond irritating that such statement would be thrown in a bug report. Who is interested in fingerpointing? How old are we, 6? Who's problem it is that your product doesn't work in a VALID use case? Not a fantasy, not an edge case. A normal case. If krita doesn't recognize the strokes of my toothbrush on my monitor, I won't blame you or open a ticket on Oral-B's customer support or on the supermarket where I bought it for 2.35 Euros. I can't say this clearer or frequently enough: I do not care "who" forgot a semicolon or who wrote an idiotic API or 3rd party program or which criminal manufactures a disastrous piece of hardware. As long as that thing is required and supported by your product, then you own that problem. Your product doesn't work in a __valid_use_case__. If I wouldn't have proven a *valid use case*, I wouldn't be wasting my time here, late at night and with bad health. Why is it so hard to say: "yes, it is _our_ problem, because it affects _our_ product and _our_ users." ? I will never get it. Have you ever had a problem with your new car? would you accept they do nothing because they blame China, which produces such bad aluminium that your engine cracked? What about your stinky smoking "non-polluting" Volkswagen? Whether the root cause is bad Ubuntu, bad KDE, bad Qt, Wacom, Nvidia, bad Goverment, the NSA or climate changes: the only and absolute workable truth is that krita is _the_thing_ that doesn't work in a well documented, normal _valid_use_case_scenario_, demonstrated to exhaustion, literally. I don't see any interest to admit it and _document_ it for the existing and potential users. It seems it isn't interesting except to myself. No matter how moronic Linux, Ubuntu, Debian or Qt might be and how clean and elegant krita's code might be, it is krita's team lack of taking ownership of well demonstrated, well described valid failure modes and not providing vital information in the right places, what deeply frustrates any good intentions and all hard efforts I have made to help. No, it has nothing to do with work load, not after nearly a year of so much discussion and information offered from my side in the same topic. 4. No matter how overwhelming the work load of a one man's show might be, this 8 months late "response" is inequivocably poor and frustrating because you have known the issue and stated that you know the solution since very long time already (https://bugs.kde.org/show_bug.cgi?id=392251#c24) and yet no follow up action was taken to at least inform the users, other than "we need to think" in an obscure comment deep down in a long thread of some bug report more than half a year ago. Please no blame on overwhelming work load and loneliness. That has been demonstrated countless times, not in the kindest manners, which I reckon why, having been myself victim of burnout. So please, don't. I have been in worse situations than that, truly alone and without any resources at all, no Google, no Intel, no money. Only pressure. One myocardial infarct later, I should know. Believe me
[Qt/KDE Flatpak Runtime] [Bug 407194] Honor system font scaling setting
https://bugs.kde.org/show_bug.cgi?id=407194 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- What does tweak tool actually set? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403508] animated brush tips have wrong selection mode
https://bugs.kde.org/show_bug.cgi?id=403508 vanyossi changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/81407392c72f8b ||1b8d9ac9fb703486e506a7fbd4 --- Comment #4 from vanyossi --- Git commit 81407392c72f8b1b8d9ac9fb703486e506a7fbd4 by Ivan Yossi. Committed on 03/05/2019 at 23:14. Pushed by ivany into branch 'master'. Fix missing event on animation stamp creation M +1-0plugins/paintops/libpaintop/kis_custom_brush_widget.cpp https://invent.kde.org/kde/krita/commit/81407392c72f8b1b8d9ac9fb703486e506a7fbd4 -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 407194] Honor system font scaling setting
https://bugs.kde.org/show_bug.cgi?id=407194 --- Comment #1 from Aleix Pol --- This will need some investigation because for me it works fine on Plasma+Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 179948] No user feedback if the download of an icon theme fails
https://bugs.kde.org/show_bug.cgi?id=179948 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 336952] Install button remains permanently disabled if download error occurs
https://bugs.kde.org/show_bug.cgi?id=336952 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407107] Dropbox plugin doesn't auto update state of files
https://bugs.kde.org/show_bug.cgi?id=407107 Txutxifel changed: What|Removed |Added CC||jesa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 396515] Record Show Not Working
https://bugs.kde.org/show_bug.cgi?id=396515 --- Comment #13 from Kenneth --- Thanks, however, Kaffeine version 2.0.14. on Ubuntu does exhibit the issue... I'll post a question on Launchpad anyway. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407202] New: glitches after I click "Add flathub" button
https://bugs.kde.org/show_bug.cgi?id=407202 Bug ID: 407202 Summary: glitches after I click "Add flathub" button Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: bugsefor...@gmx.com CC: aleix...@kde.org Target Milestone: --- Created attachment 119833 --> https://bugs.kde.org/attachment.cgi?id=119833=edit screenshot SUMMARY The attached screenshot shows the black glitches that appeared after click on "Add flathub" button in "Sources" page. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 407201] New: gwenview crashed when I clicked on "Share" button in toolbar after modify toolbar settings
https://bugs.kde.org/show_bug.cgi?id=407201 Bug ID: 407201 Summary: gwenview crashed when I clicked on "Share" button in toolbar after modify toolbar settings Product: gwenview Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY I exported a screenshot from spectacle to gwenview, I added "Crop" button to gwenview toolbar, I changed "Text position" (right click on toolbar) to "Icons only, I clicked the button in toolbar to share a image using various services and gwenview crashed. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 Thread 3 (Thread 0x7fb45afa9700 (LWP 26463)): #0 0x7fb4831519f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55f0170795a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55f017079558, cond=0x55f017079580) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55f017079580, mutex=0x55f017079558) at pthread_cond_wait.c:655 #3 0x7fb45b6e4dcb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7fb45b6e4af7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7fb48314b6db in start_thread (arg=0x7fb45afa9700) at pthread_create.c:463 #6 0x7fb488ff588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fb46bfff700 (LWP 26461)): #0 0x7fb488fe8bf9 in __GI___poll (fds=0x7fb464011b40, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb4816455c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb4816456dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb48992b15b in QEventDispatcherGlib::processEvents (this=0x7fb464000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fb4898cc64a in QEventLoop::exec (this=this@entry=0x7fb46bffecb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fb4896f441a in QThread::exec ( this=this@entry=0x7fb4881efd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #6 0x7fb487f78015 in QDBusConnectionManager::run ( this=0x7fb4881efd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7fb4896f5bc2 in QThreadPrivate::start ( arg=0x7fb4881efd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7fb48314b6db in start_thread (arg=0x7fb46bfff700) at pthread_create.c:463 #9 0x7fb488ff588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fb48e18b8c0 (LWP 26458)): #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7fb4844f208d in KCrash::defaultCrashHandler(int) () from /usr/lib/x86_64-linux-gnu/libKF5Crash.so.5 #2 #3 QListData::begin (this=0x55f0177d4e60) at ../../include/QtCore/../../src/corelib/tools/qlist.h:116 #4 QList::contains_impl (t=: , this=0x55f0177d4e60) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1023 #5 QList::contains (t=: , this=0x55f0177d4e60) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1006 #6 QWidget::insertAction (this=0x55f017219cf0, before=before@entry=0x0, action=0x55f01725ad30) at kernel/qwidget.cpp:3273 #7 0x7fb48b0e9d6a in QWidget::addAction (this=, action=) at kernel/qwidget.cpp:3238 #8 0x55f014d7f7ba in Gwenview::KIPIInterface::loadPlugins (this=this@entry=0x55f01725ae20) at ./app/kipiinterface.cpp:285 #9 0x55f014d804d4 in Gwenview::KIPIInterface::loadPlugins (this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:239 #10 Gwenview::KIPIInterface::pluginActions (this=0x55f01725ae20, category=category@entry=KIPI::ExportPlugin) at ./app/kipiinterface.cpp:371 #11 0x55f014d7b390 in Gwenview::KIPIExportAction::init (this=0x55f017173390) at ./app/kipiexportaction.cpp:92 #12 0x7fb4898fdf3f in QtPrivate::QSlotObjectBase::call (a=0x7ffdd13abb30, r=0x55f017173390, this=0x55f017173d70) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #13 QMetaObject::activate (sender=sender@entry=0x55f017173610, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3759 #14 0x7fb4898fe4f7 in QMetaObject::activate (sender=sender@entry=0x55f017173610, m=m@entry=0x7fb48b791b80 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3631 #15 0x7fb48b2219a0 in QMenu::aboutToShow (this=this@entry=0x55f017173610) at
[cantor] [Bug 407200] New: cantor python backends are hardcoded to the system
https://bugs.kde.org/show_bug.cgi?id=407200 Bug ID: 407200 Summary: cantor python backends are hardcoded to the system Product: cantor Version: 19.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: python3-backend Assignee: nlmin...@gmail.com Reporter: jsar...@gmail.com CC: alexander.se...@web.de, fil...@kde.org Target Milestone: --- I'd like to use python3 (and its packages, etc) in cantor within my conda environment, but that doesn't seem to be possible. It is somehow hardcoded to use system's python version: /usr/lib/python3 -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #99 from Jan Przybylak --- I found this implementation that mostly works: https://gitlab.com/Vogtinator/kio-fuse -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407199] cannot start Wayland session on neon dev unstable. coredumpctl indicates kwin_wayland crash.
https://bugs.kde.org/show_bug.cgi?id=407199 Patrick Silva changed: What|Removed |Added Summary|cannot start Wayand session |cannot start Wayland |on neon dev unstable. |session on neon dev |coredumpctl indicates |unstable. coredumpctl |kwin_wayland crash. |indicates kwin_wayland ||crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407199] New: cannot start Wayand session on neon dev unstable. coredumpctl indicates kwin_wayland crash.
https://bugs.kde.org/show_bug.cgi?id=407199 Bug ID: 407199 Summary: cannot start Wayand session on neon dev unstable. coredumpctl indicates kwin_wayland crash. Product: kwin Version: git master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY I only see a black screen without cursor when I try to start Wayland session on neon dev unstable. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 Thread 7 (Thread 0x7fae59e84700 (LWP 1105)): #0 0x7fae85ec9bf9 in __GI___poll (fds=0x7fae50003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fae7d0005c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fae7d0006dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fae86a3413f in QEventDispatcherGlib::processEvents (this=0x7fae5b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4 0x7fae869d564a in QEventLoop::exec (this=this@entry=0x7fae59e83d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fae867fd41a in QThread::exec (this=this@entry=0x5564886269e0) at thread/qthread.cpp:531 #6 0x7fae813b52e5 in QQmlThreadPrivate::run (this=0x5564886269e0) at qml/ftw/qqmlthread.cpp:148 #7 0x7fae867febc2 in QThreadPrivate::start (arg=0x5564886269e0) at thread/qthread_unix.cpp:361 #8 0x7fae87e656db in start_thread (arg=0x7fae59e84700) at pthread_create.c:463 #9 0x7fae85ed688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fae5aad7700 (LWP 1093)): #0 0x7fae87e6bed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fae5aad6b80, expected=0, futex_word=0x556488298aa0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fae5aad6c40, mutex=0x556488298a50, cond=0x556488298a78) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=cond@entry=0x556488298a78, mutex=mutex@entry=0x556488298a50, abstime=abstime@entry=0x7fae5aad6c40) at pthread_cond_wait.c:667 #3 0x7fae86805ac6 in QWaitConditionPrivate::wait_relative (this=0x556488298a50, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x556488298a50) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=, mutex=0x556488295050, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7fae86805e25 in QWaitCondition::wait (this=this@entry=0x5564885ac300, mutex=mutex@entry=0x556488295050, time=) at thread/qwaitcondition_unix.cpp:209 #7 0x7fae868035dd in QThreadPoolThread::run (this=0x5564885ac2f0) at thread/qthreadpool.cpp:144 #8 0x7fae867febc2 in QThreadPrivate::start (arg=0x5564885ac2f0) at thread/qthread_unix.cpp:361 #9 0x7fae87e656db in start_thread (arg=0x7fae5aad7700) at pthread_create.c:463 #10 0x7fae85ed688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fae6e674700 (LWP 1088)): #0 0x7fae85ec9bf9 in __GI___poll (fds=0x7fae680177d0, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fae7d0005c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fae7d0006dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fae86a3413f in QEventDispatcherGlib::processEvents (this=0x7fae68000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4 0x7fae869d564a in QEventLoop::exec (this=this@entry=0x7fae6e673cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fae867fd41a in QThread::exec ( this=this@entry=0x7fae87e5cd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #6 0x7fae87be5015 in QDBusConnectionManager::run ( this=0x7fae87e5cd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7fae867febc2 in QThreadPrivate::start ( arg=0x7fae87e5cd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7fae87e656db in start_thread (arg=0x7fae6e674700) at pthread_create.c:463 #9 0x7fae85ed688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fae6d815700 (LWP 1089)): #0 0x7fae85ec9bf9 in __GI___poll (fds=0x7fae60003ce0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fae7d0005c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fae7d0006dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fae86a3413f in
[kaffeine] [Bug 397594] Kaffeine plays video in a separate window under Wayland
https://bugs.kde.org/show_bug.cgi?id=397594 --- Comment #11 from Patrick Silva --- Unfortunately I do not know. I could test Kaffeine on neon dev unstable installed on my laptop, but currently I can't start Wayland session on such system. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407198] New: Cannot add to favourites in gnome
https://bugs.kde.org/show_bug.cgi?id=407198 Bug ID: 407198 Summary: Cannot add to favourites in gnome Product: dolphin Version: 18.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: jakub.buc...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Cannot add to favourites in gnome. SOLUTION Modify org.kde.dolphin.desktop file and add StartupWMClass=dolphin STEPS TO REPRODUCE 1. Install dolphin in fedora 29 (probably Ubuntu as well) via dnf 2. Open overview (system key) 3. Type dolphin 4. Right click on dolphin icon - (in other apps there is an option 'add to favourites') OBSERVED RESULT There is no way of adding it to favourites EXPECTED RESULT Show an option 'add to favourites', as i other apps SOFTWARE/OS VERSIONS Fedora 29 ADDITIONAL INFORMATION Related bugs: https://bugs.kde.org/show_bug.cgi?id=390732 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407197] standartzielalum
https://bugs.kde.org/show_bug.cgi?id=407197 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Please comment in English only, else we cannot help you... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407166] Kwin produces gray image without color
https://bugs.kde.org/show_bug.cgi?id=407166 --- Comment #4 from lbrod...@gmail.com --- Thank you. That did it. On Fri, May 3, 2019 at 7:25 AM Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=407166 > > Christoph Feck changed: > >What|Removed |Added > > > Resolution|--- |NOT A BUG > Status|REPORTED|RESOLVED > > --- Comment #3 from Christoph Feck --- > > Currently Active Effects: > > - > > kwin4_effect_grayscale > > Disable the grayscale effect. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 397594] Kaffeine plays video in a separate window under Wayland
https://bugs.kde.org/show_bug.cgi?id=397594 --- Comment #10 from Mauro Carvalho Chehab --- (In reply to Patrick Silva from comment #9) > well, this bug persists on Arch Linux running kaffeine 2.0.17 + Wayland 1.17 > + vlc 3.0.6 + Qt 5.13 beta3. Thanks for checking it. Weird that it is not happening here on Fedora... Could this be due to some different packaging configuration? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 407195] implementation/realisation association depends on class name
https://bugs.kde.org/show_bug.cgi?id=407195 --- Comment #2 from Michael --- PS: this is my first time using umbrello and I am amazed how awesome it is! Cheers -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407197] New: standartzielalum
https://bugs.kde.org/show_bug.cgi?id=407197 Bug ID: 407197 Summary: standartzielalum Product: digikam Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-MainView Assignee: digikam-bugs-n...@kde.org Reporter: r.petr...@web.de Target Milestone: --- Created attachment 119831 --> https://bugs.kde.org/attachment.cgi?id=119831=edit ich kann kein standartzielalbum anlegen. fehler : standartzielalbum -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405892] Font preview looks badly rendered in tooltip when I hover over a font file
https://bugs.kde.org/show_bug.cgi?id=405892 --- Comment #5 from Patrick Silva --- This bug only occurs when I use breeze look and feel theme. Font preview looks good with breeze dark. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 407195] implementation/realisation association depends on class name
https://bugs.kde.org/show_bug.cgi?id=407195 Michael changed: What|Removed |Added Version|2.24.3 (KDE Applications|2.26.0 (KDE Applications |17.12.3)|18.08.0) --- Comment #1 from Michael --- initially found in 2.24.3 reproduced also with 2.26.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407196] New: plasmashell wakes up a lot (eating CPU and battery) on stock configuration
https://bugs.kde.org/show_bug.cgi?id=407196
Bug ID: 407196
Summary: plasmashell wakes up a lot (eating CPU and battery) on
stock configuration
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Application Launcher (Kickoff)
Assignee: k...@davidedmundson.co.uk
Reporter: d...@dosowisko.net
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
Seems like Application Launcher widget is somewhat responsible for elevated CPU
(and battery) usage on plasmashell.
STEPS TO REPRODUCE
1. Run a vanilla clean Plasma session.
2. Wait a but until everything finishes launching and becomes idle.
3. Attach strace to a running plasmashell process ("sudo strace -f -p `pidof
plasmashell`")
OBSERVED RESULT
Lots of repeated polls with timeout values less than 20ms, easily eating
significant amounts of CPU (around 5% here).
EXPECTED RESULT
Some occasional polls, plasmashell achieving <1% CPU usage when idle.
--
Afterwards (additional info gathered when investigating):
STEPS TO REPRODUCE
1. Remove Application Launcher widget from the default panel.
2. Add it back.
OBSERVED RESULT
plasmashell becomes way more CPU friendly.
--
STEPS TO REPRODUCE
1. Restart plasmashell.
OBSERVED RESULT
plasmashell becomes CPU hungry again.
EXPECTED RESULT
plasmashell should still be CPU friendly.
--
STEPS TO REPRODUCE
1. Remove Application Launcher.
2. (optionally) Add Application Menu.
3. Restart plasmashell.
OBSERVED RESULT
Plasma is still CPU friendly
SOFTWARE/OS VERSIONS
Tested with latest (2019-05-03) Neon Developer Edition ISO.
ADDITIONAL INFORMATION
All the steps above suggest that something is wrong with Application Launcher
widget, but only when it's loaded together with Plasma and/or panel (adding it
with a default panel causes the same result as restarting whole Plasma).
--
You are receiving this mail because:
You are watching all bug changes.
[kaffeine] [Bug 397594] Kaffeine plays video in a separate window under Wayland
https://bugs.kde.org/show_bug.cgi?id=397594 --- Comment #9 from Patrick Silva --- well, this bug persists on Arch Linux running kaffeine 2.0.17 + Wayland 1.17 + vlc 3.0.6 + Qt 5.13 beta3. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 407195] New: implementation/realisation association depends on class name
https://bugs.kde.org/show_bug.cgi?id=407195 Bug ID: 407195 Summary: implementation/realisation association depends on class name Product: umbrello Version: 2.24.3 (KDE Applications 17.12.3) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: meisterl...@gmx.eu Target Milestone: --- Created attachment 119830 --> https://bugs.kde.org/attachment.cgi?id=119830=edit sample project with the described class and interface names, that can be used to reproduce the issue SUMMARY the implementation / realization association can only be set on classes that are listed after the interface in the tree view (sorted by name) STEPS TO REPRODUCE 1. extract attached java code 2. import *.java files from subfolders of src/main/java 3. drag interface QuakVerhalten from tree view to class diagram view 4. drag classes Quaken, Quietschen, StummesQuaken from the tree view to the class diagram view 5. check association arrows. only the classes that come after the interface have the implementation arrow. the class Quaken does not have the realization arrow. When drawing the association manually and double-clicking to edit the association, the Realization association is not available in the combo box. OBSERVED RESULT not all implementations of the interface QuakVerhalten are displayed with the correct realization association. The classes with a class name that is before the interface name can not have the realization association. Only after renaming the classes, the realization association can be used. EXPECTED RESULT All classes that implement an interface should show as realization of the interface regardless of their name. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I also tried to reproduce this issue by manually creating an interface test and implementing classes atest and ztest, but I could not set the realization association at all. If this is a usage error, I am extremely sorry. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 396515] Record Show Not Working
https://bugs.kde.org/show_bug.cgi?id=396515 --- Comment #12 from Mauro Carvalho Chehab --- (In reply to Mauro Carvalho Chehab from comment #11) > (In reply to Kenneth from comment #10) > > Are there any plans to update the [Debian] Ubuntu servers? > > No clue. You should ask Debian/Ubuntu developers about that, probably by > opening a BZ there, asking them to either upgrade to version 2.0.17 or to > backport patches. > > Btw, there is at least one important fix on version 2.0.17 with affects > channel detection (together with a lot of other fixed bugs). > > So, I strongly suggest using version 2.0.17. In the specific case of this BZ, Debian sid/buster now comes with Kaffeine 2.0.15: https://packages.debian.org/search?keywords=kaffeine So, you should likely be able to update to at least 2.0.15. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 369232] cmake fails on missing rcc, it's a runtime dep though
https://bugs.kde.org/show_bug.cgi?id=369232 --- Comment #4 from Jarosław Staniek --- In addition, breeze-icons.rcc will be used for app-wide autotests, when the main GUI is invoked. For now we have one autotest like this. I rather consider running autotests and ensuring they pass as a prerequisite of packaging, or a post-build step. Therefore, configure-time check for presence of breeze-icons.rcc is not a bad thing. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 380936] to compress a kexi db provides a crash
https://bugs.kde.org/show_bug.cgi?id=380936 --- Comment #6 from Jarosław Staniek --- @Albrecht, do you see any issue in Compact Database feature in your KEXI version on Arch linux? Please specify your version. If there's no problem with Arch we could make this report refer to the Flatpak version (KEXI 3.2). -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 380936] to compress a kexi db provides a crash
https://bugs.kde.org/show_bug.cgi?id=380936 Jarosław Staniek changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #5 from Jarosław Staniek --- Upstream offers Flatpak instead of AppImage https://community.kde.org/Kexi/Snapshots#Linux However "Unknown error" appears in this case too. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 405069] Missing Breeze icons file for KEXI
https://bugs.kde.org/show_bug.cgi?id=405069 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 405069] Missing Breeze icons file for KEXI
https://bugs.kde.org/show_bug.cgi?id=405069 Jarosław Staniek changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version|unspecified |3.2.0 Beta Target Milestone|--- |3.2 Assignee|kexi-b...@kde.org |stan...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 405171] MySQL and PostgreSQL plugins not found for KEXI flatpak
https://bugs.kde.org/show_bug.cgi?id=405171 Jarosław Staniek changed: What|Removed |Added Summary|Database plugins not found |MySQL and PostgreSQL |for KEXI flatpak|plugins not found for KEXI ||flatpak -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 396515] Record Show Not Working
https://bugs.kde.org/show_bug.cgi?id=396515 --- Comment #11 from Mauro Carvalho Chehab --- (In reply to Kenneth from comment #10) > Are there any plans to update the [Debian] Ubuntu servers? No clue. You should ask Debian/Ubuntu developers about that, probably by opening a BZ there, asking them to either upgrade to version 2.0.17 or to backport patches. Btw, there is at least one important fix on version 2.0.17 with affects channel detection (together with a lot of other fixed bugs). So, I strongly suggest using version 2.0.17. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407191] Video playback stops and mouse cursor is laggy while partition manager creates and formats partitions
https://bugs.kde.org/show_bug.cgi?id=407191 --- Comment #1 from Andrius Štikonas --- Did you notice anything else unusual? E.g. CPU usage went up to 100% or maybe system started swapping. I never observed anything like that and nobody else reported this. As it stands, I'm not even sure where to start with this bug. You might want to try running some of the same commands that partition manager runs to see if any of them cause slowdowns (if you start partitionmanager from terminal with "KPMCORE_DEBUG=1 partitionmanager" it will print list of commands that it is running), although, a few commands require input which is not printed. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 386146] Kaffeine program information encrypted on UK (Freeview)
https://bugs.kde.org/show_bug.cgi?id=386146 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Mauro Carvalho Chehab --- As it is now possible to import EPG data on Kaffeine via XMLTV files, I'm closing this bug. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 386146] Kaffeine program information encrypted on UK (Freeview)
https://bugs.kde.org/show_bug.cgi?id=386146 --- Comment #2 from Mauro Carvalho Chehab --- (In reply to Mauro Carvalho Chehab from comment #1) > (In reply to Michael from comment #0) > > Kaffeine does not display the OSD and Program Guide properly. The > > information given is unreadable garbage; almost as if it were encrypted. > > Apart from this, the television works well. I am using a Hauppauge Dual > > Tuner USB device, and my system language is UK English. Thank you for any > > advice. > > That is a known issue. The problem is that UK (Freeview) encrypts the data > at the Event Information Table - EIT, using huffman-based tables. While it > is not hard to decrypt, there are some patents an licenses that apply to the > huffman decoding tables. > > Adding it to Kaffeine or libdvbv5 could be problematic, from legal > standpoint. Kaffeine 2.0.17 adds a feature that allows you to use EPG in UK: it comes with support for XMLTV files. With that, you could either import the XMLTV using existing xmltv grabber scripts or write your own, eventually getting the data from EPG via an external application, with would decrypt and produce a XMLTV file, allowing it to be done outside Kaffeine, and preventing any licensing issues at Kaffeine's code. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 401383] Elisa crash after deleting Music forlder from library.
https://bugs.kde.org/show_bug.cgi?id=401383 --- Comment #2 from Matthieu Gallien --- Are you still able to reproduce this bug ? It looks to me like a bug in the qml engine (precisely in the threaded rendering code). -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 390934] Kaffeine 2.0.14 doesn't find leadtek DTV1800h and DTV1000-T PCI tuner cards
https://bugs.kde.org/show_bug.cgi?id=390934 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #12 from Mauro Carvalho Chehab --- As on the previous close, this is not a bug. Yet, if you want that this deserves a better explanation or a different interface, feel free to send us patches. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 396515] Record Show Not Working
https://bugs.kde.org/show_bug.cgi?id=396515 --- Comment #10 from Kenneth --- Are there any plans to update the [Debian] Ubuntu servers? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 400335] Elisa doesn't provide Global menu
https://bugs.kde.org/show_bug.cgi?id=400335 Matthieu Gallien changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Matthieu Gallien --- Are you able to do a test ? I have created https://phabricator.kde.org/D21006 to implement that. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 394158] Exit dialogue when records are scheduled does not remember it's state.
https://bugs.kde.org/show_bug.cgi?id=394158 --- Comment #2 from Mauro Carvalho Chehab --- Created attachment 119829 --> https://bugs.kde.org/attachment.cgi?id=119829=edit Exit while recording dialog I suspect that it is the window manager you're using that it is somehow trying to implement such feature without support inside the app. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 394158] Exit dialogue when records are scheduled does not remember it's state.
https://bugs.kde.org/show_bug.cgi?id=394158 --- Comment #1 from Mauro Carvalho Chehab --- (In reply to romeoK from comment #0) > When you close Kaffeine and there are scheduled records, Kaffeine asks if > you really want to quit. If you select 'yes' and 'don't show this message > again', the next time you close Kaffeine, the same message is shown again > nevertheless. I'm not sure why it is showing 'don't show this message again' in the first place. Here, it just asks for yes/no. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 407194] New: Honor system font scaling setting
https://bugs.kde.org/show_bug.cgi?id=407194 Bug ID: 407194 Summary: Honor system font scaling setting Product: Qt/KDE Flatpak Runtime Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: accessibility Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: ila...@zoho.com Target Milestone: --- SUMMARY KDE flatpak apps do not seem to honor system font scaling setting. I run Gnome 3 as the host DE and have increased the font size from Gnome's tweak tool. When I run Qt/KDE apps installed via Flatpak (have tested VLC and KeePassXC from Flathub as well as Okular from kdeapps), the apps stubbornly display the default font size instead of the one I have choosed. The problem does not seem to extend to GTK flatpak apps. Also, Qt apps installed from system repository work fine. This problem has been evident for quite a while (1) but there doesn't seem to be a formal bug report yet. Font scaling is important for not only those with high DPI displays, but also those with visual impairment. There are strong ethical obligations towards and in some locales even legal obligations to keep accessibility in mind. Please take this seriously. 1) https://www.reddit.com/r/kde/comments/910awy/how_to_make_kde_flatpak_apps_respect_font_settings/ STEPS TO REPRODUCE 1. Run Gnome DE and set the font scaling to e. g. 1.4 from the tweak-tool 2. Install some Qt/KDE flatpak app 3. Run the app and inspect the font size OBSERVED RESULT The default size font is displayed EXPECTED RESULT The font size should be bigger as set from the tweak-tool SOFTWARE/OS VERSIONS CentOS 7, Fedora 30 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 397028] Exit Problems in main window after TV program change
https://bugs.kde.org/show_bug.cgi?id=397028 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Mauro Carvalho Chehab --- This bug should have beeen fixed upstream.Please test with Kaffeine 2.0.17. If it still occurs, feel free to re-open. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 391116] kaffeine doesn't find some transponders on Astr 19.2E
https://bugs.kde.org/show_bug.cgi?id=391116 --- Comment #13 from Mauro Carvalho Chehab --- Could you please test with Kaffeine 2.0.17? I found a bug there with could be affecting channel scanning: https://cgit.kde.org/kaffeine.git/commit/?id=7960208dad913d331ffdd6a129bfdc935337a4e5 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 398075] Kaffeine doesn't find some transponders on Astra 19.2E - Part 2 of bug 391116
https://bugs.kde.org/show_bug.cgi?id=398075 Mauro Carvalho Chehab changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Mauro Carvalho Chehab --- I'm closing this BZ, as this is still #391116. So, let's place them altogether again. *** This bug has been marked as a duplicate of bug 391116 *** -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 391116] kaffeine doesn't find some transponders on Astr 19.2E
https://bugs.kde.org/show_bug.cgi?id=391116 --- Comment #12 from Mauro Carvalho Chehab --- *** Bug 398075 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407193] New: Cursor stops working after setting render threads higher than one
https://bugs.kde.org/show_bug.cgi?id=407193 Bug ID: 407193 Summary: Cursor stops working after setting render threads higher than one Product: kdenlive Version: 19.04.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: matteo.magnoni.m...@gmail.com Target Milestone: --- After setting the render threads to six(I have an i5-8400), the cursor stopped working. After hours of trail and error I stumbled on a forum where a guy discovered that the problem lied with the render threads. After setting them back to one the cursor started working again(the problem and the fix got reproduced on a laptop with the latest version of Manjaro) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Mint 19.1 Cinnamon(kernel version: 5.0) -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 398075] Kaffeine doesn't find some transponders on Astra 19.2E - Part 2 of bug 391116
https://bugs.kde.org/show_bug.cgi?id=398075 --- Comment #1 from Mauro Carvalho Chehab --- Could you please test with Kaffeine 2.0.17? I found a bug there with could be affecting channel scanning: https://cgit.kde.org/kaffeine.git/commit/?id=7960208dad913d331ffdd6a129bfdc935337a4e5 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 399383] Does not display TV picture after OS resume from suspend mode
https://bugs.kde.org/show_bug.cgi?id=399383 Mauro Carvalho Chehab changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Mauro Carvalho Chehab --- That's likely a driver's bug. So, I'm closing the issue. If you want, feel free to add here the dmesg, and I'll try to address it very likely via a Kernel patch. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 400668] Have to rescan channels every time I start Kaffeine
https://bugs.kde.org/show_bug.cgi?id=400668 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Mauro Carvalho Chehab --- There was some issues at the Kaffeine exit code that would be preventing the storage of the channel list. This was already solved on Kaffeine 2.0.17. Please upgrade to it and re-test. As this was already fixed (at least I can't reproduce it here anymore), I'm closing this bug. If it is still happening on Kaffeine's 2.0.17, feel free to re-open it. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 398952] Channels icon mess in kaffeine 2.0.x
https://bugs.kde.org/show_bug.cgi?id=398952 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Mauro Carvalho Chehab --- As this is working for me, I suspect that this is an issue at either the icon set setup at Plasma, or the broadcaster is not providing information about encrypted channels via the usual descriptor. As, on either case, there's not much we can do at Kaffeine's side, I'm closing this. If you belive it is a mistake, feel free to re-open, providing additional information. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 398808] Kaffeine 2.0.15 backend (libVLC) doesn't work fine with vdpau on some GPUs like Radeon HD 5450
https://bugs.kde.org/show_bug.cgi?id=398808 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #6 from Mauro Carvalho Chehab --- As this bug is actually a problem at libVLC (with should probably be fixed there some day - if not already), I'm closing this. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 397578] no device created by kaffeine but the hauppauge driver should be the correct [/lib/firmware/dvb-demod-si2168-b40-01.fw] on hauppauge usb-stick WinTV-SoloHD.
https://bugs.kde.org/show_bug.cgi?id=397578 Mauro Carvalho Chehab changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Mauro Carvalho Chehab --- Sorry, hit enter too soon... (In reply to Mauro Carvalho Chehab from comment #2) > That looks like an install issue, that it is requiring all users of /dev/dvb > to belong to the "group" video, easily solved with a command like: > ># groupadd video username > (where username is your user at the Linux machine) > > or with # chmod 666 /dev/dvb/* (that would likely require running it after every reboot) In any case, this is not related to Kaffeine itself, so I'm closing it. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407192] Filesystems created by Partition manager are owned by root
https://bugs.kde.org/show_bug.cgi?id=407192 --- Comment #1 from Andrius Štikonas --- Hmm, I'm not sure if it's partition manager's responsibility to do that. It might be whoever is mounting (Solid?). I discussed it briefly with Fedora packager some time ago (after fedora bug was open https://bugzilla.redhat.com/show_bug.cgi?id=1538641) It was actually Fedora packager who thought that this is not partition manager's responsibility. Well, let's keep this bug open, to track this issue even though I was aware of it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407157] Lens Auto-Correction for fixed-lens cameras
https://bugs.kde.org/show_bug.cgi?id=407157 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||6.2.0 CC||metzping...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- apply patch from Mátyás Forstner to correct the lens detection for fixed lenses Fixed-lens cameras usually do not write lens information tag. If there is exactly one lens available in the database for a given camera model, treat it as exact match. https://invent.kde.org/kde/digikam/commit/f214f8402788cc33ca2443a935233a27e4c3ee24 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 397578] no device created by kaffeine but the hauppauge driver should be the correct [/lib/firmware/dvb-demod-si2168-b40-01.fw] on hauppauge usb-stick WinTV-SoloHD.
https://bugs.kde.org/show_bug.cgi?id=397578 --- Comment #2 from Mauro Carvalho Chehab --- That looks like an install issue, that it is requiring all users of /dev/dvb to belong to the "group" video, easily solved with a command like: # groupadd video username or with (where username is your user at the Linux machine) -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 401216] Freeze after switching TV channels
https://bugs.kde.org/show_bug.cgi?id=401216 --- Comment #3 from Mauro Carvalho Chehab --- I found a longstanding bug at Kaffeine, with got fixed at version 2.0.17: https://cgit.kde.org/kaffeine.git/commit/?id=7960208dad913d331ffdd6a129bfdc935337a4e5 Basically, it is a race condition that happens during scan time, but may also happen while doing channel switch. Could you please test if Kaffeine 2.0.17 solves the issue you're facing? -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 377535] Slider progress is not turn on
https://bugs.kde.org/show_bug.cgi?id=377535 Mauro Carvalho Chehab changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 396515] Record Show Not Working
https://bugs.kde.org/show_bug.cgi?id=396515 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 396515] Record Show Not Working
https://bugs.kde.org/show_bug.cgi?id=396515 --- Comment #9 from Mauro Carvalho Chehab --- The bug should already be fixed on a Kaffeine version later than 2.0.14. So, I'm closing this bug. Please test with Kaffeine 2.0.17. If it still occurs, please re-open it, providing additional information about how to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 402383] tv channels no video, only audio
https://bugs.kde.org/show_bug.cgi?id=402383 Mauro Carvalho Chehab changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Mauro Carvalho Chehab --- I suspect that this bug was already fixed. So, I'm closing it. If it still occurs on Kaffeine 2.0.17, please re-open providing extra information. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 397594] Kaffeine plays video in a separate window under Wayland
https://bugs.kde.org/show_bug.cgi?id=397594 --- Comment #8 from Mauro Carvalho Chehab --- I just re-checked it here on Fedora 30, with comes with: vlc-core-3.0.7-0.1.fc30.x86_64 libwayland-server-1.17.0-1.fc30.x86_64 qt5-qtwayland-5.12.1-1.fc30.x86_64 qt5-qtbase-devel-5.12.1-2.fc30.x86_64 Was unable to reproduce this bug anymore. So, I guess this was already fixed. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 403308] Unable to use multiple TV tuners.
https://bugs.kde.org/show_bug.cgi?id=403308 --- Comment #5 from Mauro Carvalho Chehab --- (In reply to lordbludwin from comment #4) > Thanks for the response. Hopefully this is the screen you meant. Yes. Sorry for taking so long to return here... I've been busy with Kernel stuff those days. Instead of "Old device" and "New device", try to use the same name for both tuners. That should allow Kaffeine to think as both as belonging to the same group of tuners. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 404746] Add Eutelsat 7A Satellite
https://bugs.kde.org/show_bug.cgi?id=404746 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Mauro Carvalho Chehab --- The channel information comes from the https://git.linuxtv.org/dtv-scan-tables.git/ tree. I did an update there sometime ago, adding Eutelsat 7A, and other Satellites, imported with information from LyngSat data. The new scanfile.dvb should be available for download via the Kaffeine's GUI option. It should be already at Kaffeine version 2.0.17 as well. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407192] New: Filesystems created by Partition manager are owned by root
https://bugs.kde.org/show_bug.cgi?id=407192 Bug ID: 407192 Summary: Filesystems created by Partition manager are owned by root Product: partitionmanager Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: matejm98m...@gmail.com Target Milestone: --- SUMMARY New partitions with these filesystems are owned by root after creation and so cannot be written to without chown-ing first: XFS, Btrfs, Ext4 EXPECTED RESULT New partitions are owned by user so they can be used (written to) normally. SOFTWARE/OS VERSIONS Partition manager 4.0.0 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57 Qt Version: 5.13.0beta1 -- You are receiving this mail because: You are watching all bug changes.
