[plasma-pa] [Bug 396835] Feature Request: Add a "silence mode" to plasma-pa
https://bugs.kde.org/show_bug.cgi?id=396835 MrPepe changed: What|Removed |Added CC||felipepe...@web.de --- Comment #2 from MrPepe --- +1 for this request This is a huge point for me regarding the "Usability and Productivity" epic. I usually don't remember what the cached setting is from before plugging my earphones into my laptop. If I mute the sound while the earphones are plugged in I expect it to be muted afterwards as well. I have already had some embarrassing situations in the library. -- You are receiving this mail because: You are watching all bug changes.
kde-bugs-dist@kde.org
https://bugs.kde.org/show_bug.cgi?id=402376 --- Comment #5 from Eike Hein --- > But dragging Task Manager buttons makes less sense because in the UI they > represent open *instances* of windows or apps, not the *concept* of the app > itself. And that's what dragging them is used for by users, too (e.g. to move a window to a different virtual desktop on the pager). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402574] Disappearing icons
https://bugs.kde.org/show_bug.cgi?id=402574 Eike Hein changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Eike Hein --- Could you record a video? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 402565] WindowThumbnail becomes black randomly
https://bugs.kde.org/show_bug.cgi?id=402565 Eike Hein changed: What|Removed |Added Version|unspecified |5.53.0 CC||h...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 402565] WindowThumbnail becomes black randomly
https://bugs.kde.org/show_bug.cgi?id=402565 Eike Hein changed: What|Removed |Added Assignee|h...@kde.org|notm...@gmail.com Target Milestone|1.0 |--- Version|5.14.4 |unspecified Component|Task Manager|components Summary|Thumbnail becomes black |WindowThumbnail becomes |randomly|black randomly Product|plasmashell |frameworks-plasma -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402770] Selection tool (disappear content)
https://bugs.kde.org/show_bug.cgi?id=402770 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org Status|REPORTED|NEEDSINFO --- Comment #1 from Boudewijn Rempt --- Sorry, I cannot reproduce that. Please provide a screen recording that shows exactly what you're doing or a test file that makes it easy to reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402779] New: Okular, when printing 2 pages per sheet, prints the wrong pages.
https://bugs.kde.org/show_bug.cgi?id=402779 Bug ID: 402779 Summary: Okular, when printing 2 pages per sheet, prints the wrong pages. Product: okular Version: 1.3.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: aeg...@internode.on.net Target Milestone: --- SUMMARY If I try and print two pages from a PDF (a Canon camera manual in this instance), two per A4 sheet, I get four pages, the wrong ones, two per sheet. The result is the same for larger numbers of pages. Specifying Print to File causes the pages per sheet option to be greyed out. Also ignores the page number selection and copies the whole file over, but bigger, with each page placed as what looks like A5 in the middle of an A4 page. STEPS TO REPRODUCE 1. Open a PDF file with okular. 2. Open the print dialog. 3. Open Printer Properties 4. Set Pages per Sheet to 2. OK. 5. Open Options. 6. Select specific pages. (I did not try the Pages From as I needed specific single pages from the file) 7. Print. OBSERVED RESULT Four pages are printed, two per sheet. The second of each pair is a page twice the specified page number, the first is the page before. For instance, if I specify pages 65 and 73, I get pages 129, 130, 145, 146. EXPECTED RESULT One sheet containing two pages. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Open SUSE Leap 15 KDE Plasma Version: plasmashell 5.12.6 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION Leap 15 upgraded from 42.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384820] Allow matching library paths across different operating systems? [patch]
https://bugs.kde.org/show_bug.cgi?id=384820 Maik Qualmann changed: What|Removed |Added Summary|Allow matching library |Allow matching library |paths across different |paths across different |operating systems? |operating systems? [patch] -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 402447] Some Security Settings are not applied
https://bugs.kde.org/show_bug.cgi?id=402447 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||mon...@kde.org Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- 5.8.3 is very old. I fixed it in last version 5.9.3 or 5.10.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 402463] Inline JPG images do not show up properly in KMail
https://bugs.kde.org/show_bug.cgi?id=402463 Laurent Montel changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I confirm this bug. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 402077] SaveFile does not set the current_name
https://bugs.kde.org/show_bug.cgi?id=402077 --- Comment #15 from qdzcu...@sharklasers.com --- (In reply to Jan Grulich from comment #9) > From the logs it looks everything is correct and I can't think of any reason > why it doesn't work for you. Maybe try to put some debug there to see if > selectFile() is really called in SaveFile() method. I recompiled xdg-desktop-portal-kde from the latest git (commit 57b2179) and it now works. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 402778] unable to copy from windows and paste in linux
https://bugs.kde.org/show_bug.cgi?id=402778 MISAL changed: What|Removed |Added CC||misal.va...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 402778] New: unable to copy from windows and paste in linux
https://bugs.kde.org/show_bug.cgi?id=402778 Bug ID: 402778 Summary: unable to copy from windows and paste in linux Product: klipper Version: 0.9.7 Platform: MS Windows OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: misal.va...@gmail.com Target Milestone: --- SUMMARY unable to copy from windows and paste in linux STEPS TO REPRODUCE 1. copy text from windows 2. paste in linux Also tried by clearing klipper history, it doesn't work OBSERVED RESULT its still pasting last copied text in LINUX EXPECTED RESULT pasted text should be from windows SOFTWARE/OS VERSIONS Windows: 10 MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 402777] New: konqueror crash when restart system
https://bugs.kde.org/show_bug.cgi?id=402777 Bug ID: 402777 Summary: konqueror crash when restart system Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: ayvonnica...@yahoo.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I restarted my computer. This hapens every time I start my computer. I do not have Konqueror set to run automatically. I do not notice any other issues -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1bb951a840 (LWP 1555))] Thread 19 (Thread 0x7f1b267fc700 (LWP 1750)): #0 0x7f1bae4cb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55c9c8dcdaf8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1bae4cb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55c9c8dcdaa8, cond=0x55c9c8dcdad0) at pthread_cond_wait.c:502 #2 0x7f1bae4cb9f3 in __pthread_cond_wait (cond=0x55c9c8dcdad0, mutex=0x55c9c8dcdaa8) at pthread_cond_wait.c:655 #3 0x7f1b8931dc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f1b8931e177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f1b8931ef11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f1b8931b5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f1bae4c56db in start_thread (arg=0x7f1b267fc700) at pthread_create.c:463 #8 0x7f1bb8d7c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f1b26ffd700 (LWP 1745)): #0 0x7f1bb8d6b167 in __GI___libc_write (fd=2, buf=0x7f1b26ff9e00, nbytes=39) at ../sysdeps/unix/sysv/linux/write.c:26 #1 0x7f1bb8ce61bd in _IO_new_file_write (f=0x7f1bb9047680 <_IO_2_1_stderr_>, data=0x7f1b26ff9e00, n=39) at fileops.c:1203 #2 0x7f1bb8ce6b2f in new_do_write (to_do=, data=0x7f1b26ff9e00 "[warn] epoll_wait: Bad file descriptor\n", fp=0x7f1bb9047680 <_IO_2_1_stderr_>) at fileops.c:457 #3 0x7f1bb8ce6b2f in _IO_new_file_xsputn (f=0x7f1bb9047680 <_IO_2_1_stderr_>, data=, n=39) at fileops.c:1277 #4 0x7f1bb8cb9707 in buffered_vfprintf (s=s@entry=0x7f1bb9047680 <_IO_2_1_stderr_>, format=format@entry=0x7f1b871fc6a8 "[%s] %s\n", args=args@entry=0x7f1b26ffc3c0) at vfprintf.c:2350 #5 0x7f1bb8cb6726 in _IO_vfprintf_internal (s=s@entry=0x7f1bb9047680 <_IO_2_1_stderr_>, format=0x7f1b871fc6a8 "[%s] %s\n", ap=ap@entry=0x7f1b26ffc3c0) at vfprintf.c:1301 #6 0x7f1bb8d8d4c6 in ___fprintf_chk (fp=0x7f1bb9047680 <_IO_2_1_stderr_>, flag=1, format=) at fprintf_chk.c:35 #7 0x7f1b871e49ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #8 0x7f1b871e4b44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #9 0x7f1b871e646c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #10 0x7f1b871dc114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #11 0x7f1b892eeb0d in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7f1b892eada8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7f1b8930777b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7f1b8931f4d6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7f1b8931b5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #16 0x7f1bae4c56db in start_thread (arg=0x7f1b26ffd700) at pthread_create.c:463 #17 0x7f1bb8d7c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f1b277fe700 (LWP 1744)): #0 0x7f1bae4cb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f1b277fda78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f1bae4cb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f1b277fda28, cond=0x7f1b277fda50) at pthread_cond_wait.c:502 #2 0x7f1bae4cb9f3 in __pthread_cond_wait (cond=0x7f1b277fda50, mutex=0x7f1b277fda28) at pthread_cond_wait.c:655 #3 0x7f1b89313999 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f1b893139c7 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f1b892ee4db in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f1b892eada8 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f1b8930777b in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f1b8931f4d6 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f1b8
[kdenlive] [Bug 398478] User Interface crashes when clip job stabilizing and adding .mlt automatically
https://bugs.kde.org/show_bug.cgi?id=398478 --- Comment #9 from Evert Vorster --- emohr, please read comment #3. I use Vidstab2, from the clip jobs in the context menu from the project bin. TLDR #1; The UI should not crash from normal user input. TLDR #2; That job generates invalid .mlt file Kind regards, Evert -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 357134] Ark is unable to open RAR archives after update to 15.12
https://bugs.kde.org/show_bug.cgi?id=357134 Paulo Ricardo Da Silva changed: What|Removed |Added CC||paulo8...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 384171] ZWO ASI120MC-S camera crashes on MacOS
https://bugs.kde.org/show_bug.cgi?id=384171 --- Comment #12 from Jean-Claude --- I verified again : The imager ZWO ASI1600MC-C camera and the guider ZWO ASI120MC-S camera work well in TheSkyX (no crash). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 362946] keyboard kcm build too fat
https://bugs.kde.org/show_bug.cgi?id=362946 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402689] KWin crashes with OpenGL compositing enabled when using dedicated GPU (radeon) in hybrid graphics notebook
https://bugs.kde.org/show_bug.cgi?id=402689 --- Comment #9 from Martin Flöser --- (In reply to Christoph Feck from comment #8) > Funny. It crashes both in Thread 1 and Thread 12. It is possible that one > crash is the cause for the other. Yes, it's the OpenGL freeze prevention. The code points make sense. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 --- Comment #1 from Martin Flöser --- Please use xev to compare the key events of the real and fake super key. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402292] A Krita crash if I want to select color space (AnimePalett,TealMagentaGold,ColorNegative,RedBleuYellow,Smokey)
https://bugs.kde.org/show_bug.cgi?id=402292 --- 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 402236] Hi i had problem of red and blue colour inverted. What should I do? Thank you
https://bugs.kde.org/show_bug.cgi?id=402236 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401633] [HUION] Pen shortcut doesn't work
https://bugs.kde.org/show_bug.cgi?id=401633 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 392133] Huge memory consumption while doing nothing
https://bugs.kde.org/show_bug.cgi?id=392133 --- Comment #23 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.
[latte-dock] [Bug 402776] New: The setting dialog disappears when switching between modes several times
https://bugs.kde.org/show_bug.cgi?id=402776 Bug ID: 402776 Summary: The setting dialog disappears when switching between modes several times Product: latte-dock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tr...@yandex.com Target Milestone: --- Created attachment 117235 --> https://bugs.kde.org/attachment.cgi?id=117235&action=edit video The setting dialog disappears when switching between modes several times. Please see the video. Anyways, the new ui of the setting dialog looks very nice! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391781] Add support for SIXEL in Konsole
https://bugs.kde.org/show_bug.cgi?id=391781 --- Comment #1 from Kurt Hindenburg --- Well at some point I wonder if we're trying to do too much in a terminal... the images look good in xterm though. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402096] Removing memory card causes device to disappear from the system.
https://bugs.kde.org/show_bug.cgi?id=402096 Nate Graham changed: What|Removed |Added Component|Device Notifier |general Ever confirmed|0 |1 Product|plasmashell |frameworks-solid Target Milestone|1.0 |--- Status|REPORTED|CONFIRMED Version|master |5.53.0 Assignee|plasma-b...@kde.org |lu...@kde.org CC||kdelibs-b...@kde.org, ||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 402775] New: Can not play videos for douyu.com
https://bugs.kde.org/show_bug.cgi?id=402775 Bug ID: 402775 Summary: Can not play videos for douyu.com Product: Falkon Version: unspecified Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: hufeng1...@gmail.com Target Milestone: --- 1. enter any video page: like https://www.douyu.com/topic/Kespa?rid=288016 2. falkon can not play video. 3. chrome browser and firefox browser working correct. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 402774] New: Contacts show up multiple times
https://bugs.kde.org/show_bug.cgi?id=402774 Bug ID: 402774 Summary: Contacts show up multiple times Product: kontact Version: 5.7.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: kdepim-b...@kde.org Reporter: thec...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Sync Google contacts 2. View contacts in Kontact 3. All groups are selected after first sync OBSERVED RESULT My contacts show up multiple times because they exist in multiple groups. Deselecting groups starts to thin out the duplication. Finally, when only the top-level account is selected, I only see one entry per contact. EXPECTED RESULT Because the groups are "subfolders" of the main google.com account, I don't expect having them selected to show the entries duplicated. The entries in the contact list should always be de-duped. 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.
[amarok] [Bug 402773] Current Track is missing, not showing anything.
https://bugs.kde.org/show_bug.cgi?id=402773 hong changed: What|Removed |Added CC||hong7...@gmail.com --- Comment #1 from hong --- Created attachment 117234 --> https://bugs.kde.org/attachment.cgi?id=117234&action=edit this pic shows the empty Current Track -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 402773] New: Current Track is missing, not showing anything.
https://bugs.kde.org/show_bug.cgi?id=402773 Bug ID: 402773 Summary: Current Track is missing, not showing anything. Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Context View/Current Track Assignee: amarok-bugs-d...@kde.org Reporter: hong7...@gmail.com Target Milestone: kf5 SUMMARY i just installed Amarok on Kubuntu 18.04. there is local NAS drive that contains music files. When i play tracks, Current Track in the middle context pane is not showing anything. Most of the area is white except for a thin vertical bar which i'm assuming is the window. even after i stop playing, Recently Played is not showing at all. STEPS TO REPRODUCE 1. install on Kubuntu 2. play from local location, 3. OBSERVED RESULT it looks to me like the window is sized wrong or something because it just looks strange. i tried removing all other applets but the behavior is the same. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 402746] Audio replay glitches, and application doesn't fully close
https://bugs.kde.org/show_bug.cgi?id=402746 --- Comment #3 from seise...@icloud.com --- And thank you for putting the work around for the themes. I was freaking out for a second there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 301622] Mouse pointer gets huge if a second large screen is connected
https://bugs.kde.org/show_bug.cgi?id=301622 Ariel Garcia changed: What|Removed |Added CC||aog20...@gmail.com --- Comment #39 from Ariel Garcia --- I also confirm this issue, running Debian testing/buster with KDE Plasma: 5.14.3 Qt version: 5.11.2 KDE Frameworks: 5.51.0 on a laptop with an internal display 2560x1440 plus an 3440x1440 external monitor, Intel integrated graphics, and default theme breeze. As mentioned in some former comments, the workaround of setting the mouse size to 24 only works temporarily. Only forcing the fonts DPI "solves" the problem in my case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402689] KWin crashes with OpenGL compositing enabled when using dedicated GPU (radeon) in hybrid graphics notebook
https://bugs.kde.org/show_bug.cgi?id=402689 --- Comment #8 from Christoph Feck --- Funny. It crashes both in Thread 1 and Thread 12. It is possible that one crash is the cause for the other. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402689] KWin crashes with OpenGL compositing enabled when using dedicated GPU (radeon) in hybrid graphics notebook
https://bugs.kde.org/show_bug.cgi?id=402689 --- Comment #7 from jmlokosiew...@gmail.com --- Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f38d8b45fc0 (LWP 1119))] Thread 13 (Thread 0x7f381bfff700 (LWP 1709)): #0 0x7f38df769afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f38c483a004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f38c4839d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f38df763a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f38e206db23 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f3838b12700 (LWP 1708)): [KCrash Handler] #4 0x7f38e1fa9d7f in raise () at /usr/lib/libc.so.6 #5 0x7f38e1f94672 in abort () at /usr/lib/libc.so.6 #6 0x7f38e09717fc in () at /usr/lib/libQt5Core.so.5 #7 0x7f38d61d2dc3 in KWin::X11StandalonePlatformoperator() (__closure=) at /usr/include/qt/QtCore/qlogging.h:91 #8 0x7f38d61d2dc3 in QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::X11StandalonePlatform::createOpenGLSafePoint(KWin::Platform::OpenGLSafePoint):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #9 0x7f38d61d2dc3 in QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #10 0x7f38d61d2dc3 in QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:439 #11 0x7f38e0b923e0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #12 0x7f38e0b9e418 in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #13 0x7f38e0b92b1b in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7f38e152fe34 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7f38e1537671 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7f38e0b678f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7f38e0bbc955 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #18 0x7f38e0bbaa9e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f38e0b6658c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7f38e09aa5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #21 0x7f38e09ab9cc in () at /usr/lib/libQt5Core.so.5 #22 0x7f38df763a9d in start_thread () at /usr/lib/libpthread.so.0 #23 0x7f38e206db23 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f3839349700 (LWP 1705)): #0 0x7f38df769afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f38c483a004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f38c4839d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f38df763a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f38e206db23 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f3839b4a700 (LWP 1704)): #0 0x7f38df769afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f38c483a004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f38c4839d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f38df763a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f38e206db23 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f383a34b700 (LWP 1703)): #0 0x7f38df769afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f38c483a004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f38c4839d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f38df763a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f38e206db23 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f383ab4c700 (LWP 1702)): #0 0x7f38df769afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f38c483a004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f38c4839d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f38df763a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f38e206db23 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f383b34d700 (LWP 1701)): #0 0x7f38df769afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f38c483a004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f38c4839d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f38df763a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f38e206db23 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f383bb4e700 (LWP 1700)): #0 0x7f38df769afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f38c483a004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f38c4839d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f38df763a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f
[dolphin] [Bug 356062] Dolphin Filter by Baloo Tag
https://bugs.kde.org/show_bug.cgi?id=356062 Nate Graham changed: What|Removed |Added CC||f4tm...@web.de --- Comment #5 from Nate Graham --- *** Bug 401684 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401684] can't search for keywords
https://bugs.kde.org/show_bug.cgi?id=401684 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- (In reply to Michael Kaiser from comment #2) > So how can I search for keywords at all? See https://bugs.kde.org/show_bug.cgi?id=356062#c1 It's a little obtuse, but we'll fix it. :) *** This bug has been marked as a duplicate of bug 356062 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402765] Zoom effect ignores mouse tracking option (Wayland)
https://bugs.kde.org/show_bug.cgi?id=402765 --- Comment #3 from Alexander Schlarb --- Thanks for the response! Here it is: == Version === KWin version: 5.14.4 Qt Version: 5.11.2 Qt compile version: 5.11.2 XCB compile version: 1.13 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12003000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.oxygen Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 5, 4, 3, 9 decorationButtonsRight: 6, 1 borderSize: 2 gridUnit: 20 font: eufm10,17,-1,5,50,0,0,0,0,0,LyX smallSpacing: 5 largeSpacing: 20 Platform == Name: DRM Active: true Atomic Mode Setting: true Options === focusPolicy: 1 nextFocusPrefersMouse: true clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 200 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 5 focusPolicyIsReasonable: true borderSnapZone: 100 windowSnapZone: 100 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 2 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 2 glSmoothScale: 2 xrenderSmoothScale: true maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: true cursorPushBackDistance: 1x1 timeThreshold: 50 reActivateThreshold: 500 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: LP156WF6-SPK eDP-1-unbekannt Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 60.02 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon R7 Graphics (CARRIZO, DRM 3.26.0, 4.18.0-3-amd64, LLVM 7.0.1) OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.6 OpenGL platform interface: EGL OpenGL shading language version string: 4.40 Driver: R600G GPU class: Unknown OpenGL version: 4.4 GLSL version: 4.40 Mesa version: 18.2.6 Linux kernel version: 4.18 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom snaphelper mousemark mouseclick kwin4_effect_translucency kwin4_effect_morphingpopups kwin4_effect_login kwin4_effect_logout dimscreen kwin4_effect_maximize kwin4_effect_dialogparent kwin4_effect_fade kwin4_effect_windowaperture kwin4_effect_frozenapp slidingpopups screenshot minimizeanimation desktopgrid cubeslide cube coverswitch colorpicker highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - mousemark blur contrast Effect Settings: zoom: zoomFactor: 1.0999 mousePointer: 1 mouseTracking: 0 enableFocusTracking: true followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 snaphelper: mousemark: width: 3 color: #ff mouseclick: color1: #ff color2: #00ff00 color3: #ff lineWidth: 1 ringLife: 200 ringSize: 10 ringCount: 1 showText: false font: DejaVu Serif,16,-1,5,50,0,0,0,0,0,Book enabled: false kwin4_effect_translucency: kwin4_effect_morphingpopups: kwin4_effect_login: kwin4_effect_logout: dimscreen: kwin4_effect_maximize: kwin4_effect_dialogparent: kwin4_effect_fade: kwin4_effect_windowa
[kmymoney] [Bug 402772] New: Switching Workspace Makes Ledger Jump to End
https://bugs.kde.org/show_bug.cgi?id=402772 Bug ID: 402772 Summary: Switching Workspace Makes Ledger Jump to End Product: kmymoney Version: 5.0.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: joel.mad...@hotmail.com Target Milestone: --- SUMMARY If you navigate to somewhere in the middle of your transactions in a ledger and then switch workspaces back and forth, KMyMoney jumps to the end of the ledger and highlights the last item. Additionally (I believe same root cause): Moving between workspaces removes filter from ledger (and similarly jumps to end of ledger) STEPS TO REPRODUCE 1. Open ledger with quite a few items 2. Navigate to middle of ledger and highlight an item 3. Switch workspace to the right (to workspace #2) 4. Switch back to workspace on left (to workspace #1) OBSERVED RESULT KMyMoney jumps to the end of the ledger and highlights the last item EXPECTED RESULT No change in view/selected item in KMyMoney when jumping between workspaces ALTERNATIVE REPRO STEPS 1. Open a ledger with quite a few items 2. Filter for a particular item 3. Switch workspaces as described above OBSERVED Filter goes away, KMyMoney jumps to end of ledger and highlights last item EXPECTED No change in filter status or view/selected item just because of change in workspace. SOFTWARE/OS VERSIONS 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.
[frameworks-kio] [Bug 400423] No warning when creating conflicting directory
https://bugs.kde.org/show_bug.cgi?id=400423
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In||5.54
Latest Commit||https://commits.kde.org/kio
||/ef57863a73c0e58b94f9f9f0aa
||1f4e918d98e79a
Status|CONFIRMED |RESOLVED
--- Comment #5 from Nate Graham ---
Git commit ef57863a73c0e58b94f9f9f0aa1f4e918d98e79a by Nate Graham.
Committed on 01/01/2019 at 23:26.
Pushed by ngraham into branch 'master'.
Display error instead of silently failing when asked to create folder that
already exists
Summary:
FIXED-IN: 5.54
Test Plan:
1. `mkdir ~/test`
2. In Dolphin, try to create `~/test`: folder not created
3. In Dolphin, try to create `~/test/foo`: folder created
4. In Dolphin, try to create `~/testo`: folder created
{F6481099}
Reviewers: #dolphin, elvisangelaccio, dfaure
Reviewed By: #dolphin, elvisangelaccio, dfaure
Subscribers: anthonyfieroni, dfaure, emateli, elvisangelaccio, Codezela,
kde-frameworks-devel
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D17617
M +15 -10 src/filewidgets/knewfilemenu.cpp
https://commits.kde.org/kio/ef57863a73c0e58b94f9f9f0aa1f4e918d98e79a
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 402771] New: Better integration with Plasma (Web shortcuts)
https://bugs.kde.org/show_bug.cgi?id=402771 Bug ID: 402771 Summary: Better integration with Plasma (Web shortcuts) Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: schwanc...@protonmail.com Target Milestone: --- SUMMARY Falkon don't use the web shortcuts defined by Plasma like for example Konqueror or Krunner. This is a pretty niche feature, so not urgent. But could be cool to add. STEPS TO REPRODUCE 1. type "gg:hello" in the url bar OBSERVED RESULT Open duckduckgo (default search engine) with the search 'gg:hello' EXPECTED RESULT Open google with the search 'hello' SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.14 KDE Frameworks Version: 5.53 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402770] New: Selection tool (disappear content)
https://bugs.kde.org/show_bug.cgi?id=402770 Bug ID: 402770 Summary: Selection tool (disappear content) Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: va...@post.com Target Milestone: --- SUMMARY Selection tool (disappear content when try move selection on same layer). It's happen when layer was lock\unlock (transparent). STEPS TO REPRODUCE 1. make new (transparent) layer. 2. draw and lock them (transparent) to coloring. 3. after unlock it. 4. select area (on this layer). 5. try move (inside selection draw disappear). OBSERVED RESULT To solve it, copy "bug" layer. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402617] Crash when cancelling "Find in files" during collection stage
https://bugs.kde.org/show_bug.cgi?id=402617 Christoph Roick changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||chris...@gmx.de --- Comment #7 from Christoph Roick --- I could reproduce this by searching in the home folder with the current master of KDevelop. The check seems to be a proper fix. Would you provide a patch in phabricator which also includes a similar check in GrepOutputView::rowsRemoved()? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402734] File > Export As... > Auto-open created file
https://bugs.kde.org/show_bug.cgi?id=402734 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- That sounds like a clippy-looks-like-you're-writting-a-letter idea to me. Yes you want to do that, but i know no other application that automatically opens the file on export so doing that is totally unexpected by the users. -1 from my side give how annoying it'd be for people that don't want it -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402767] latte content color not calculated when kde desktop background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=402767 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Michail Vourlakos --- unfortunately plasma does not provide a way to know which background is used when the slideshow setting is used. currently Latte git version provides the following for that feature: 1. it is multi-screen aware 2. it supports single file backgrounds 3. is supports single color backgrounds [2] and [3] are the only that can be supported with the current plasma infrastructure. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402769] New: Present Windows - All desktops sometimes makes KWin crash
https://bugs.kde.org/show_bug.cgi?id=402769 Bug ID: 402769 Summary: Present Windows - All desktops sometimes makes KWin crash Product: kwin Version: 5.14.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: paulo76.alga...@hotmail.com Target Milestone: --- Application: kwin_x11 (5.14.4) Qt Version: 5.11.2 Frameworks Version: 5.53.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: KDE Neon BK -- Information about the crash: - What I was doing when the application crashed: Was trying to use Present Windows - All desktops - Custom settings of the application: I have Present Windows - All desktops set to the top corner of the screen and sometimes, while moving the mouse cursor there and while some heavier processing is being done by the cpu, KWin crashes. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcb9fa9d840 (LWP 1574))] Thread 9 (Thread 0x7fcb7e158700 (LWP 6627)): #0 0x7ffd67562979 in ?? () #1 0x7ffd67562c30 in clock_gettime () #2 0x7fcb9f40eea6 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fcb7e157b90) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fcb9c9f6951 in qt_clock_gettime (ts=0x7fcb7e157b90, clock=) at kernel/qelapsedtimer_unix.cpp:111 #4 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #5 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #6 0x7fcb9c9f5189 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fcb70036570) at kernel/qtimerinfo_unix.cpp:91 #7 0x7fcb9c9f5765 in QTimerInfoList::timerWait (this=this@entry=0x7fcb70036570, tm=...) at kernel/qtimerinfo_unix.cpp:388 #8 0x7fcb9c9f4764 in QEventDispatcherUNIX::processEvents (this=0x7fcb7003b0a0, flags=...) at kernel/qeventdispatcher_unix.cpp:485 #9 0x7fcb9c99b30a in QEventLoop::exec (this=this@entry=0x7fcb7e157d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #10 0x7fcb9c7c6bba in QThread::exec (this=) at thread/qthread.cpp:525 #11 0x7fcb96eb64f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fcb9c7d1adb in QThreadPrivate::start (arg=0x7fcb800906e0) at thread/qthread_unix.cpp:367 #13 0x7fcb9842a6db in start_thread (arg=0x7fcb7e158700) at pthread_create.c:463 #14 0x7fcb9f3ff88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fcb63561700 (LWP 2213)): #0 0x7fcb9f3f2cf6 in __GI_ppoll (fds=fds@entry=0x7fcb58001a38, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fcb9c9f2d51 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fcb58001a38) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7fcb58001a38, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7fcb9c9f445e in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7fcb9c99b30a in QEventLoop::exec (this=this@entry=0x7fcb63560d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7fcb9c7c6bba in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7fcb96eb64f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fcb9c7d1adb in QThreadPrivate::start (arg=0x559d1cdf6a70) at thread/qthread_unix.cpp:367 #9 0x7fcb9842a6db in start_thread (arg=0x7fcb63561700) at pthread_create.c:463 #10 0x7fcb9f3ff88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fcb6700 (LWP 2146)): #0 QEventDispatcherUNIX::processEvents (this=0x7fcb68045520, flags=...) at kernel/qeventdispatcher_unix.cpp:485 #1 0x7fcb9c99b30a in QEventLoop::exec (this=this@entry=0x7fcb6fffed40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #2 0x7fcb9c7c6bba in QThread::exec (this=) at thread/qthread.cpp:525 #3 0x7fcb96eb64f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x7fcb9c7d1adb in QThreadPrivate::start (arg=0x559d1cb2eb10) at thread/qthread_unix.cpp:367 #5 0x7fcb9842a6db in start_thread (arg=0x7fcb6700) at pthread_create.c:463 #6 0x7fcb9f3ff88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fcb62d60700 (LWP 1719)): #0 0x7fcb984309f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fcb9b9d6fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fcb9b9d6f68, cond=0x7fcb9b9d6f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x
[Discover] [Bug 385754] [Flatpak] The number of updates available shown by Discover and its tray icon don't match
https://bugs.kde.org/show_bug.cgi?id=385754 conta...@disroot.org changed: What|Removed |Added CC||conta...@disroot.org Version|5.13.5 |5.14.4 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402344] Update notifier shows 1 update available, although CLI and Discover GUI show system up-to-date
https://bugs.kde.org/show_bug.cgi?id=402344 conta...@disroot.org changed: What|Removed |Added CC||conta...@disroot.org --- Comment #4 from conta...@disroot.org --- For me Discover wouldn't show the flatpaks updates pending, even though the tray icon would report them. 'flatpak update' command fixed it -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 386456] tests fail – kirigamiplugin doesn't register components
https://bugs.kde.org/show_bug.cgi?id=386456 h.goe...@crazy-compilers.com changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from h.goe...@crazy-compilers.com --- This error no longer occurs in 5.49.0. (But now: No tests were found!!!) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402766] kwin crash for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=402766 --- Comment #2 from Mathias Homann --- will do when it happens again - or is there a way to get a better stacktrace out of an old crash? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 402768] New: Missing record monitor.
https://bugs.kde.org/show_bug.cgi?id=402768 Bug ID: 402768 Summary: Missing record monitor. Product: kdenlive Version: 18.08.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: hrabov...@volny.cz Target Milestone: --- Created attachment 117233 --> https://bugs.kde.org/attachment.cgi?id=117233&action=edit Screenshot According to manual, there should be button "Record monitor" or somethink like that, but there is only Project monitor and Clip monitor. How to grab video from external device in kdenlive? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402689] KWin crashes with OpenGL compositing enabled when using dedicated GPU (radeon) in hybrid graphics notebook
https://bugs.kde.org/show_bug.cgi?id=402689 --- Comment #6 from Vlad Zagorodniy --- Could you please repackage libepoxy as well? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402766] kwin crash for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=402766 Vlad Zagorodniy changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Vlad Zagorodniy --- The backtrace lacks debug symbols. Could you please install kwin debug packages and submit a new backtrace? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 402723] Thumbnails for Speeddial do not load
https://bugs.kde.org/show_bug.cgi?id=402723 Alexander Browne changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402765] Zoom effect ignores mouse tracking option (Wayland)
https://bugs.kde.org/show_bug.cgi?id=402765 Vlad Zagorodniy changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Vlad Zagorodniy --- Works fine for me on both X11 and Wayland. Could you please post output of qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 397271] Unattended access settings lost on reboot
https://bugs.kde.org/show_bug.cgi?id=397271 Alexey Min changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 397271] Unattended access settings lost on reboot
https://bugs.kde.org/show_bug.cgi?id=397271 --- Comment #4 from Alexey Min --- > Where is the password saved? All general settings are stored in ~/.config/krfbrc, but passwords are stored inside KWallet. Launch kwalletmanager (in kubuntu/neon package should be called kwalletmanager) and see - https://i.imgur.com/t7CFnQl.png The problem is probably with this: after reboot you need to enter kwallet password to unlock your wallet (you should see this window - https://i.imgur.com/MF714Vp.png ), if you cancel that window without entering that password kwallet cannot not be opened and unattended password is generated randomly at krfb startup (and not saved anywhere). You should see "Could not open KWallet, Falling back to config file" in krfb output if started from console. You can either configure kwallet auto-unlock on user login. Or there is a workaround to not use KWallet for storing passwords. There is a hidden (from UI) option, called "noWallet". You can manually edit ~/.config/krfbrc (when krfb program is shut down of course) and add a line in section [Security]: noWallet=true like that: [Security] allowUnattendedAccess=true noWallet=true After that you start krfb, configure unattended password once using GUI, and then it will be stored into this config file forever. It should persist on reboots. We could add an option in krfb, in security settings, a checkbox "Store passwords in KWallet" to make this option visible in UI... -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 397271] Unattended access settings lost on reboot
https://bugs.kde.org/show_bug.cgi?id=397271 Alexey Min changed: What|Removed |Added Assignee|grundleb...@googlemail.com |alexey@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 402746] Audio replay glitches, and application doesn't fully close
https://bugs.kde.org/show_bug.cgi?id=402746 --- Comment #2 from seise...@icloud.com --- I mean static like a popping sound. It only happens in kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402767] New: latte content color not calculated when kde desktop background is set to slideshow
https://bugs.kde.org/show_bug.cgi?id=402767 Bug ID: 402767 Summary: latte content color not calculated when kde desktop background is set to slideshow Product: latte-dock Version: 0.8.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: lukasz.g...@gmail.com Target Milestone: --- SUMMARY docks contents are not colored if the dekstop background is changed through slideshow setting. STEPS TO REPRODUCE 1. configure latte 8.3.1 to use monochrome content colors based on desktop background 2. use slideshow setting as your plasma background mode 3. add some images varying in luminosity OBSERVED RESULT as we cycle through slideshow, the content color is not changed. ie, we end up with white text/tray icons on a white-ish desktop background EXPECTED RESULT background color detection should be triggered also when the slide change occurs -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 402723] Thumbnails for Speeddial do not load
https://bugs.kde.org/show_bug.cgi?id=402723 --- Comment #2 from shina...@gmail.com --- Awesome!!! It worked!!! Thank you so much!!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402766] New: kwin crash for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=402766 Bug ID: 402766 Summary: kwin crash for no apparent reason Product: kwin Version: 5.14.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mathias.hom...@opensuse.org Target Milestone: --- Application: kwin_x11 (5.14.4) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.12.14-lp150.12.28-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: i was switching between applications - Unusual behavior I noticed: nothing unusual, but i had an openGL game running in a window. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f107c0ce940 (LWP 3595))] Thread 7 (Thread 0x7f104b398700 (LWP 14681)): #0 0x7f10749eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1078da970b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55e2167a4c50) at thread/qwaitcondition_unix.cpp:146 #2 0x7f1078da970b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55e218a23f90, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f1078da9a19 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x55e218a23f98, mutex=0x55e218a23f90, time=) at thread/qwaitcondition_unix.cpp:208 #4 0x7f1073b8c3d8 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f1073b8c80a in () at /usr/lib64/libQt5Quick.so.5 #6 0x7f1078da2782 in QThreadPrivate::start(void*) (arg=0x55e218a23f10) at thread/qthread_unix.cpp:361 #7 0x7f10749e5559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f107ba6081f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f105991d700 (LWP 14680)): #0 0x7ffd9874db27 in clock_gettime () #1 0x7f107ba6e106 in clock_gettime () at /lib64/libc.so.6 #2 0x7f1078fd7591 in qt_clock_gettime (ts=0x7f105991caa0, clock=) at kernel/qelapsedtimer_unix.cpp:111 #3 0x7f1078fd7591 in do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 0x7f1078fd7591 in qt_gettime() () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f1078fd5dc9 in QTimerInfoList::updateCurrentTime() (this=this@entry=0x7f104c0373c0) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f1078fd63a5 in QTimerInfoList::timerWait(timespec&) (this=this@entry=0x7f104c0373c0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f1078fd53a4 in QEventDispatcherUNIX::processEvents(QFlags) (this=0x7f104c036a40, flags=...) at kernel/qeventdispatcher_unix.cpp:485 #8 0x7f1078f7922a in QEventLoop::exec(QFlags) (this=this@entry=0x7f105991cc50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #9 0x7f1078da0fda in QThread::exec() (this=) at thread/qthread.cpp:531 #10 0x7f10734086b5 in () at /usr/lib64/libQt5Qml.so.5 #11 0x7f1078da2782 in QThreadPrivate::start(void*) (arg=0x7f105c06c350) at thread/qthread_unix.cpp:361 #12 0x7f10749e5559 in start_thread () at /lib64/libpthread.so.0 #13 0x7f107ba6081f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f1043766700 (LWP 5384)): #0 0x7f10749eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1078da970b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55e2166708e0) at thread/qwaitcondition_unix.cpp:146 #2 0x7f1078da970b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55e216668a20, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f1078da9a19 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x55e216668a28, mutex=0x55e216668a20, time=) at thread/qwaitcondition_unix.cpp:208 #4 0x7f1073b8c3d8 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f1073b8c80a in () at /usr/lib64/libQt5Quick.so.5 #6 0x7f1078da2782 in QThreadPrivate::start(void*) (arg=0x55e2166689a0) at thread/qthread_unix.cpp:361 #7 0x7f10749e5559 in start_thread () at /lib64/libpthread.so.0 #8 0x7f107ba6081f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f1042f65700 (LWP 3753)): #0 0x7f10749eb89d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1077ca87a4 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f1077ca87e9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f10749e5559 in start_thread () at /lib64/libpthread.so.0 #4 0x7f107ba6081f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f105889f700 (LWP 3667)): #0 0x7f107ba56176 in ppoll () at /lib64/libc.so.6 #1 0x7f1078fd3991 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 0x7f1078fd3991 in qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f105d18) at kernel/qcore_unix.cpp:132 #3 0x7f1078
[krfb] [Bug 401994] Cannot launch krfb's interface
https://bugs.kde.org/show_bug.cgi?id=401994 Alexey Min changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE CC||alexey@gmail.com --- Comment #7 from Alexey Min --- *** This bug has been marked as a duplicate of bug 397271 *** -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 397271] Unattended access settings lost on reboot
https://bugs.kde.org/show_bug.cgi?id=397271 --- Comment #3 from Alexey Min --- *** Bug 401994 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401772] Screen cannot be rotated
https://bugs.kde.org/show_bug.cgi?id=401772 deadite66 changed: What|Removed |Added CC||lee295...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not turned on
https://bugs.kde.org/show_bug.cgi?id=368063 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not turned on
https://bugs.kde.org/show_bug.cgi?id=368063 Claudius Ellsel changed: What|Removed |Added CC||cliv...@protonmail.com --- Comment #8 from Claudius Ellsel --- *** Bug 388156 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 388156] NumLock settings are not being applied
https://bugs.kde.org/show_bug.cgi?id=388156 Claudius Ellsel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||claudius.ell...@live.de --- Comment #5 from Claudius Ellsel --- *** This bug has been marked as a duplicate of bug 368063 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402765] Zoom effect ignores mouse tracking option (Wayland)
https://bugs.kde.org/show_bug.cgi?id=402765 --- Comment #1 from Alexander Schlarb --- Forgot to mention: I added “Wayland” in the title since I only tried this on Wayland so far. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402765] New: Zoom effect ignores mouse tracking option (Wayland)
https://bugs.kde.org/show_bug.cgi?id=402765 Bug ID: 402765 Summary: Zoom effect ignores mouse tracking option (Wayland) Product: kwin Version: 5.14.4 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: alexander-kde@ninetailed.ninja Target Milestone: --- SUMMARY When changing the settings of the “Zoom” effect there is an option called “mouse tracking” whose default value defaults to “Proportional”. This works as expected, however when changing this to “Disabled” I'd expect a zoomed-in desktop to stick whatever location it had when zooming in and NOT move when the mouse cursor is moved (correct me if I'm misinterpreting something here!). At least for me on Wayland this is not the case however. STEPS TO REPRODUCE 1. Open the settings of the “Zoom” effect plugin (under system-settings → workspace-behaviour) 2. Change “mouse tracking” to “disabled” 3. Click “OK” to save and close the dialog 4. Zoom in using the keybinding (Super+`=` by default) OBSERVED RESULT When moving the mouse cursor the part of the desktop currently visible will move along with the mouse cursor – sometimes it will zoom into the upper-left edge of the screen instead, jumping to the current mouse position only after nudging the mouse. EXPECTED RESULT The desktop should zoom into the desktop at the current mouse position but should not respond to changes in the cursor position afterwards. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable with KDE Neon user repo (there is no About System anywhere) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.2 GPU: AMD Radeon R9 M270 (amdgpu driver) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 399981] Discover: Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #37 from Andras --- (In reply to lega99 from comment #36) > I do not have libkf5newstuff I have libkf5newstuff-dev and it's not > installed. It's already fixed, you don't have to assume anything and additional packages won't be necessary to install. Report back after KDE Frameworks 5.54 arrives on your system and your plasma-discovery still won't work regarding to this bug. Its release expected around January 12th, 2019 (now I'm assuming :) that 2018 is a typo on frameworks schedules page): https://community.kde.org/Schedules/Frameworks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 382269] Inner Glow Improvements
https://bugs.kde.org/show_bug.cgi?id=382269 --- Comment #3 from Paul Geraskin --- Hi. I found that this filter mode is called "signed distance field". Just google it. https://www.google.ru/search?q=signed+distance+field&newwindow=1&client=ms-android-xiaomi&prmd=ivsn&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjZ4t70_IHdAhXKB5oKHcyFAW8Q_AUIESgB&biw=360&bih=564 There is such a filter for Unity https://www.google.ru/search?q=signed+distance+field&newwindow=1&client=ms-android-xiaomi&prmd=ivsn&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjZ4t70_IHdAhXKB5oKHcyFAW8Q_AUIESgB&biw=360&bih=564#imgrc=9W_AKcDyzGw42M https://catlikecoding.com/sdf-toolkit/docs/texture-generator/ I hope this information will be useful. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 392946] Hi-DPI cards too small to use.
https://bugs.kde.org/show_bug.cgi?id=392946 Oberon changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||obe...@arvanadesign.com Ever confirmed|0 |1 --- Comment #12 from Oberon --- I have this same issue on Linux Mint 19.1 with a 4k screen. For some reason the "Oxygen Air" deck appears at normal size, all others are tiny. I tried installing all of the optional decks and none of them work either. A clean reinstall of kpat made no difference. I tried creating a new user as requested in Comment #6 and running kpat as that user; also no difference. Maximizing and unmaximizing also did not work for me. Using the Oxygen Air deck in the meantime until resolved. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 397271] Unattended access settings lost on reboot
https://bugs.kde.org/show_bug.cgi?id=397271 Alexey Min changed: What|Removed |Added CC||alexey@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 373474] git master - crashed while clicking on a position in Timeline. [backtrace log included]
https://bugs.kde.org/show_bug.cgi?id=373474 emohr changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from emohr --- I don't see something crash specific in the log. If you like you can test with the current Kdenlive_Nightly_Appimage: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ We closed this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402760] Source browse mode activated when saving the document with shortcut
https://bugs.kde.org/show_bug.cgi?id=402760 RJVB changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||rjvber...@gmail.com Severity|normal |major Ever confirmed|0 |1 --- Comment #2 from RJVB --- I can confirm both observations (KF5 5.52.0 and Qt 5.9.7). The symptom with typing numbers is new AFAICT, I only noticed it for the first time today. This reminds me of a long-standing issue on Mac, where sometimes all input becomes "suspended" and I have to switch key focus to and from a different application. I don't think that's related to saving, but I do know I've already noticed it after switching to the patchreview view. I think this is a major issue because it happens so frequently (and because of the keyboard input aspect if it's indeed related). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396631] Templates listed twice
https://bugs.kde.org/show_bug.cgi?id=396631 emohr changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||fritzib...@gmx.net --- Comment #2 from emohr --- This problem is solved with the current Refactoring version. If you like you can test with the current Kdenlive_Nightly_Appimage: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ We closed this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 Dalton Durst changed: What|Removed |Added CC||d...@ltondur.st -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402764] New: Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 Bug ID: 402764 Summary: Caps Lock as additional Super does not trigger Alt+F1 shortcut Product: kwin Version: 5.12.7 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: d...@ltondur.st Target Milestone: --- SUMMARY When "Make Caps Lock an additional Super" is enabled in Keyboard > Advanced > Caps Lock behavior, pressing Caps Lock once (to create a Super keypress) does not trigger the ALT+F1 shortcut to (by default) open the application launcher. STEPS TO REPRODUCE 1. Enable "Make Caps Lock an additional Super" in Keyboard > Advanced > Caps Lock behavior and apply the changes 2. Verify that tapping the real Super key on the keyboard raises the Application Launcher. 3. Tap the Caps Lock key to send a Super keypress OBSERVED RESULT The Application Launcher does not appear. However, shortcuts which use Super as a modifier key (such as Meta+T) work correctly. EXPECTED RESULT The Application Launcher appears SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 I can work around this issue by setting the application launcher to a different multi-key shortcut, such as Meta+Space. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402689] KWin crashes with OpenGL compositing enabled when using dedicated GPU (radeon) in hybrid graphics notebook
https://bugs.kde.org/show_bug.cgi?id=402689 --- Comment #5 from jmlokosiew...@gmail.com --- $ kwin_x11 -v kwin 5.14.80 Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fad9e2e7fc0 (LWP 1108))] Thread 15 (Thread 0x7facdbfff700 (LWP 1602)): #0 0x7fada4f09ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fada6151a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fada6151b97 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fada614fbb4 in () at /usr/lib/libQt5Core.so.5 #4 0x7fada614b9cc in () at /usr/lib/libQt5Core.so.5 #5 0x7fada4f03a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fada780db23 in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7facf8ff9700 (LWP 1601)): #0 0x7fada4f09ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fada6151a59 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fada6151b97 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fada614fbb4 in () at /usr/lib/libQt5Core.so.5 #4 0x7fada614b9cc in () at /usr/lib/libQt5Core.so.5 #5 0x7fada4f03a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fada780db23 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7facf97fa700 (LWP 1600)): #0 0x7fada4f09afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fad05fa8004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fad05fa7d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fada4f03a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fada780db23 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7facf9ffb700 (LWP 1599)): [KCrash Handler] #4 0x7fada7749d7f in raise () at /usr/lib/libc.so.6 #5 0x7fada7734672 in abort () at /usr/lib/libc.so.6 #6 0x7fada61117fc in () at /usr/lib/libQt5Core.so.5 #7 0x7fad9c175dc3 in KWin::X11StandalonePlatformoperator() (__closure=) at /usr/include/qt/QtCore/qlogging.h:91 #8 0x7fad9c175dc3 in QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::X11StandalonePlatform::createOpenGLSafePoint(KWin::Platform::OpenGLSafePoint):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #9 0x7fad9c175dc3 in QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #10 0x7fad9c175dc3 in QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:439 #11 0x7fada63323e0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #12 0x7fada633e418 in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #13 0x7fada6332b1b in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7fada6ccfe34 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7fada6cd7671 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x7fada63078f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7fada635c955 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #18 0x7fada635aa9e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7fada630658c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7fada614a5c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #21 0x7fada614b9cc in () at /usr/lib/libQt5Core.so.5 #22 0x7fada4f03a9d in start_thread () at /usr/lib/libpthread.so.0 #23 0x7fada780db23 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7facfa7fc700 (LWP 1597)): #0 0x7fada4f09afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fad05fa8004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fad05fa7d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fada4f03a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fada780db23 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7facfaffd700 (LWP 1596)): #0 0x7fada4f09afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fad05fa8004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fad05fa7d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fada4f03a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fada780db23 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7facfb7fe700 (LWP 1595)): #0 0x7fada4f09afc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fad05fa8004 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fad05fa7d28 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fada4f03a
[Discover] [Bug 402763] New: Discover crashes every time I'm trying to search for updates
https://bugs.kde.org/show_bug.cgi?id=402763 Bug ID: 402763 Summary: Discover crashes every time I'm trying to search for updates Product: Discover Version: 5.14.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: c.alf...@outlook.it Target Milestone: --- Application: plasma-discover (5.14.4) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.19.12-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was just trying to search for updates from the app, but Discover freezes and crashes. The crash can be reproduced every time. -- Backtrace: Application: Scopri (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f93b8f42f80 (LWP 9047))] Thread 48 (Thread 0x7f9317fff700 (LWP 9230)): #0 0x7f93b74e0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f93b5c75540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93b5c7562e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9364b38f5f in () at /usr/lib/libostree-1.so.1 #4 0x7f93b5c5067b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f93b675fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f93b74ebb23 in clone () at /usr/lib/libc.so.6 Thread 47 (Thread 0x7f9336b5b700 (LWP 9229)): #0 0x7f93b74e0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f93b5c75540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93b5c7562e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9364b38f5f in () at /usr/lib/libostree-1.so.1 #4 0x7f93b5c5067b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f93b675fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f93b74ebb23 in clone () at /usr/lib/libc.so.6 Thread 46 (Thread 0x7f93254ce700 (LWP 9228)): #0 0x7f93b74e0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f93b5c75540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93b5c7562e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9364b38f5f in () at /usr/lib/libostree-1.so.1 #4 0x7f93b5c5067b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f93b675fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f93b74ebb23 in clone () at /usr/lib/libc.so.6 Thread 45 (Thread 0x7f93167fc700 (LWP 9227)): #0 0x7f93b74e0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f93b5c75540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93b5c7562e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9364b38f5f in () at /usr/lib/libostree-1.so.1 #4 0x7f93b5c5067b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f93b675fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f93b74ebb23 in clone () at /usr/lib/libc.so.6 Thread 44 (Thread 0x7f9327fff700 (LWP 9226)): #0 0x7f93b74e0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f93b5c75540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93b5c7562e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9364b38f5f in () at /usr/lib/libostree-1.so.1 #4 0x7f93b5c5067b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f93b675fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f93b74ebb23 in clone () at /usr/lib/libc.so.6 Thread 43 (Thread 0x7f9325ccf700 (LWP 9225)): #0 0x7f93b74e0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f93b5c75540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93b5c7562e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9364b38f5f in () at /usr/lib/libostree-1.so.1 #4 0x7f93b5c5067b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f93b675fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f93b74ebb23 in clone () at /usr/lib/libc.so.6 Thread 42 (Thread 0x7f93177fe700 (LWP 9224)): #0 0x7f93b74e0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f93b5c75540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93b5c7562e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9364b38f5f in () at /usr/lib/libostree-1.so.1 #4 0x7f93b5c5067b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f93b675fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f93b74ebb23 in clone () at /usr/lib/libc.so.6 Thread 41 (Thread 0x7f9316ffd700 (LWP 9208)): #0 0x7f93b74e0c21 in poll () at /usr/lib/libc.so.6 #1 0x7f93b5c75540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f93b5c7562e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f9364b38f5f in () at /usr/lib/libostree-1.so.1 #4 0x7f93b5c5067b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f93b675fa9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7
[kdenlive] [Bug 397250] All slowmotion effects in project lost upon saving
https://bugs.kde.org/show_bug.cgi?id=397250 emohr changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from emohr --- The speed effect is completely new written in the refactoring version. If you like you can test with the current Kdenlive_Nightly_Appimage: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397253] Opening error when double click project file
https://bugs.kde.org/show_bug.cgi?id=397253 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from emohr --- Please try with the current Kdenlive AppImage version 18.12.0e https://files.kde.org/kdenlive/release/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396386] wrong framework in the project
https://bugs.kde.org/show_bug.cgi?id=396386 emohr changed: What|Removed |Added Platform|Other |MS Windows Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||fritzib...@gmx.net --- Comment #1 from emohr --- It could be that this is an issue with 18.04 and MLT. Please try with the current Kdenlive version 18.12.0: https://files.kde.org/kdenlive/release/ Do you work with the Windows version? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396274] Cannot fold or zoom/unzoom audio tracks
https://bugs.kde.org/show_bug.cgi?id=396274 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||fritzib...@gmx.net --- Comment #1 from emohr --- Please try with the current Kdenlive_Nightly_Appimage https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387609] Icons, text and buttons are very small on 4k HiDPI monitors + non-KDE desktop environments
https://bugs.kde.org/show_bug.cgi?id=387609 emohr changed: What|Removed |Added Keywords||junior-jobs Status|REPORTED|CONFIRMED CC||fritzib...@gmx.net Ever confirmed|0 |1 Flags||Brainstorm+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402762] New: Task manager lib does not detect properly the "sxiv" appName
https://bugs.kde.org/show_bug.cgi?id=402762 Bug ID: 402762 Summary: Task manager lib does not detect properly the "sxiv" appName Product: plasmashell Version: 5.14.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: mvourla...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY as reported at: https://github.com/psifidotos/applet-window-title/issues/28 sxiv is an image viewer, its desktop file is called sxiv.desktop but in order for the plasma libtaskmanager to detect its appName properly it needs in the desktop file: StartupWMClass=sxiv I am reporting this because I thought that for desktop files that StartupWMClass is not present the desktop filename is used instead. STEPS TO REPRODUCE 1. execute: sxiv "icon-file" 2. notice the appName in the taskmanager e.g. at previews, it is empty EXPECTED RESULT appName should be sxiv -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394287] Open project with Flathub version does not maintain the aspect ratio
https://bugs.kde.org/show_bug.cgi?id=394287 emohr changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from emohr --- We closed this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 396110] "clip problems" window keeps popping up on opening a project despite all clips are in place
https://bugs.kde.org/show_bug.cgi?id=396110 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from emohr --- As version 18.04 has some MLT issues please try with the current Kdenlive AppImage version 18.12.0e https://files.kde.org/kdenlive/release/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395905] cannot add effect on to the track
https://bugs.kde.org/show_bug.cgi?id=395905 emohr changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||fritzib...@gmx.net --- Comment #1 from emohr --- Please try with the current Kdenlive AppImage version 18.12.0e https://files.kde.org/kdenlive/release/ Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395803] Rotoscopy undo not working
https://bugs.kde.org/show_bug.cgi?id=395803 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Flags||timeline_corruption+ Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from emohr --- This should be fixed in the Refactoring version. If you like you can test with the current Kdenlive_Nightly_Appimage: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387236] Library "sequences" not correctly rendered.
https://bugs.kde.org/show_bug.cgi?id=387236 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO Flags||timeline_corruption+ CC||fritzib...@gmx.net --- Comment #2 from emohr --- It seems you import an MLT library. If yes this function is broken somewhere around version 16.12. It is re-implemented in the Refactoring version. If you like you can test with the current Kdenlive_Nightly_Appimage: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378576] Kdenlive crashes opening project archive
https://bugs.kde.org/show_bug.cgi?id=378576 emohr changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from emohr --- Could you try in the meantime? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392147] Add dialog to make ELF files executable
https://bugs.kde.org/show_bug.cgi?id=392147 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com Summary|Properly handle ELF files |Add dialog to make ELF ||files executable Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400924] disable clip still doesn't work
https://bugs.kde.org/show_bug.cgi?id=400924 emohr changed: What|Removed |Added CC||fritzib...@gmx.net Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from emohr --- It works on version 18.12 and Refactoring (AppImage and Windows). It seems you have some “left over” from a previous Kdenlive installation. Rename/delete kdenliverc see here: https://community.kde.org/Kdenlive/Configuration Please try with the current Kdenlive AppImage version 18.12.0e https://files.kde.org/kdenlive/release/ Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 402651] [Feature request] Add description/tooltip for items in second level of sidebarview/treeview
https://bugs.kde.org/show_bug.cgi?id=402651
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.15.0
Latest Commit||https://commits.kde.org/sys
||temsettings/2766f9b9277667c
||c7e38f694310f695ec8f36f92
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #3 from Nate Graham ---
Git commit 2766f9b9277667cc7e38f694310f695ec8f36f92 by Nate Graham.
Committed on 01/01/2019 at 18:04.
Pushed by ngraham into branch 'master'.
Show tooltips for subcategories
Summary:
Tooltips are already shown for both categories as well as top-level items
at the category level (e.g. Printers). This patch makes the tooltips
show up for subcategory items as well.
FIXED-IN: 5.15.0
Test Plan: {F6515354, size=full}
Reviewers: #vdg, #plasma, mart, davidedmundson
Reviewed By: #plasma, davidedmundson
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D17864
M +14 -0sidebar/SidebarMode.cpp
M +2-0sidebar/SidebarMode.h
M +8-0sidebar/package/contents/ui/SubCategoryPage.qml
https://commits.kde.org/systemsettings/2766f9b9277667cc7e38f694310f695ec8f36f92
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 400925] when you go "duplicate clip", the original will be selected -- and it could be otherwise
https://bugs.kde.org/show_bug.cgi?id=400925 emohr changed: What|Removed |Added Flags||low_hanging+ Version|18.08.3 |Appimage - Refactoring Severity|normal |wishlist CC||fritzib...@gmx.net Keywords||junior-jobs --- Comment #1 from emohr --- Thank you for reporting. I confirm this behavior. I change this to wishlist if you don't mind. And change to refactoring. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402759] Latte crash when display scaling factor set to 1.4
https://bugs.kde.org/show_bug.cgi?id=402759 Michail Vourlakos changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #9 from Michail Vourlakos --- (In reply to Fabian from comment #8) > The systray also lives in a latte dock and is gone after the crash. > > But I guess I found the problem. I am still using "Active Window Control" > for displaying the window title in a dock at the top. When setting "Fit > text" to "Always fit" it is crashing, when changing that to "Just elide" or > "Fit on hover" it is not crashing anymore -.- > Fantastic analysis! :) BTW I was also using AWC for my needs but because it is not maintained and it was creating to much instability in my system, I developed these: https://www.opendesktop.org/p/1274975/ https://www.opendesktop.org/p/1274218/ https://www.opendesktop.org/p/1272871/ > So I guess you can close this issue. But anyway, thanks for your fast > responses and (of course) for this great piece of software :-) ! > > And a happy and wonderful new year! thank you ... :) -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402759] Latte crash when display scaling factor set to 1.4
https://bugs.kde.org/show_bug.cgi?id=402759 --- Comment #8 from Fabian --- The systray also lives in a latte dock and is gone after the crash. But I guess I found the problem. I am still using "Active Window Control" for displaying the window title in a dock at the top. When setting "Fit text" to "Always fit" it is crashing, when changing that to "Just elide" or "Fit on hover" it is not crashing anymore -.- So I guess you can close this issue. But anyway, thanks for your fast responses and (of course) for this great piece of software :-) ! And a happy and wonderful new year! -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402759] Latte crash when display scaling factor set to 1.4
https://bugs.kde.org/show_bug.cgi?id=402759 --- Comment #7 from Michail Vourlakos --- If you have a systray then if when you reload Latte you will see an icon for kcrash in the systray. BTW if it doesn't crash with Default layout then it is probably an applet you are using. You could try to add applets in the Default layout until you find the one creating the crash... -- You are receiving this mail because: You are watching all bug changes.
