[frameworks-plasma] [Bug 426129] New: Context menu appears on a different screen when drag a file to a folder.
https://bugs.kde.org/show_bug.cgi?id=426129 Bug ID: 426129 Summary: Context menu appears on a different screen when drag a file to a folder. Product: frameworks-plasma Version: 5.73.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tooltips Assignee: notm...@gmail.com Reporter: mail.alex.voro...@gmail.com CC: k...@davidedmundson.co.uk, plasma-b...@kde.org Target Milestone: --- Created attachment 131376 --> https://bugs.kde.org/attachment.cgi?id=131376=edit BugVideo SUMMARY The context menu appears on a different screen when drag file to folder. STEPS TO REPRODUCE 1. Use 2 screens 2. Create folder 3. Try to drag file to new folder on right screen OBSERVED RESULT Context menu appears on a different (left) screen EXPECTED RESULT Context menu should appear near the cursor (on right screen) SOFTWARE/OS VERSIONS System:Kernel: 5.8.3-2-MANJARO x86_64 bits: 64 compiler: N/A Desktop: KDE Plasma 5.19.4 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412 Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 driver: modesetting alternate: fbdev,intel,vesa resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.1.6 compat-v: 3.0 direct render: Yes ADDITIONAL INFORMATION If I try to move a file to a folder on a left screen, the context menu appears in the correct place on left screen. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 426128] Pictures are not scaled
https://bugs.kde.org/show_bug.cgi?id=426128 JJussi changed: What|Removed |Added CC||em.bugs.kde@jjussi.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 426128] New: Pictures are not scaled
https://bugs.kde.org/show_bug.cgi?id=426128 Bug ID: 426128 Summary: Pictures are not scaled Product: akregator Version: 5.15.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: em.bugs.kde@jjussi.com Target Milestone: --- Created attachment 131375 --> https://bugs.kde.org/attachment.cgi?id=131375=edit Screen capture of the scaling problem SUMMARY STEPS TO REPRODUCE 1. Add feed https://azurecomcdn.azureedge.net/en-us/blog/feed/ 2. Select Title "Azure Cost Management + Billing updates – August 2020" 3. Scale your akregator to FullHD wide 1920px 4. Notice that text is rendered successful, but pictures are wider than internal browser (look attached screen capture) OBSERVED RESULT Pictures are wider than window EXPECTED RESULT Pictures should be scaled, like when you open same page to external browser (Chromium) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426116] Compact database (unique block instead of loose files)
https://bugs.kde.org/show_bug.cgi?id=426116 caulier.gil...@gmail.com changed: What|Removed |Added Component|Albums-Engine |Database -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426116] Compact database (unique block instead of loose files)
https://bugs.kde.org/show_bug.cgi?id=426116 --- Comment #2 from Jo --- I'm talking about the database files created to monitor folder and file changes on hd (digikam.db, recognition.db, similarity.db, thumbnails.db, etc. ), so it'll be the collection of albums -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414589] Crashed while painting
https://bugs.kde.org/show_bug.cgi?id=414589 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 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 426124] Cannot Animate Because Krita Crashes
https://bugs.kde.org/show_bug.cgi?id=426124 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- 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.
[ark] [Bug 425938] Drag & Drop file from Ark to mpv
https://bugs.kde.org/show_bug.cgi?id=425938 Nicolas Frattaroli changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #2 from Nicolas Frattaroli --- That dbus API is bad. It requires the application to implement Ark-specific handling for drag-and-drop events by making the application tell Ark to extract the file instead of having Ark just extract the file to a temporary location and pass that temporary location to the application through the normal drag and drop mechanism with no involvement of a secondary dbus API to initiate this process. Is there literally any reason as to why it was misengineered this way? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 380078] Mouse remote control does not work using Wayland
https://bugs.kde.org/show_bug.cgi?id=380078 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #9 from Thiago Sueto --- Is this still reproducible? I cannot reproduce this on current master. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426047] Crash in multiple System Settings KCMs
https://bugs.kde.org/show_bug.cgi?id=426047 --- Comment #2 from Thiago Sueto --- Just tested this: it's Wayland-only, impossible to reproduce on Xorg. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410156] KDE Connect Does The Virtual Mouse Scrolldown Inverted Under Wayland
https://bugs.kde.org/show_bug.cgi?id=410156 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #3 from Thiago Sueto --- I can confirm this issue on current master branch. Operating System: openSUSE Tumbleweed 20200823 KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426124] Cannot Animate Because Krita Crashes
https://bugs.kde.org/show_bug.cgi?id=426124 --- Comment #2 from charlesvantus...@hotmail.com --- (In reply to Tymond from comment #1) > Can you please check out Krita Plus version from > https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/ ? Does it > also crash? I have checked out your 4.4 alpha version and it does not crash doing the same operation that was crashing the 4.3 version of Krita. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 421885] Crash on login: full wayland and xwayland
https://bugs.kde.org/show_bug.cgi?id=421885 --- Comment #2 from Thiago Sueto --- This is no longer reproducible on current master for me. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425402] Application Dashboard doesn't cover Plasma panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=425402 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #1 from Thiago Sueto --- Can't reproduce on current master branch. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 383067] wayland: application dashboard appears on wrong screen
https://bugs.kde.org/show_bug.cgi?id=383067 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #4 from Thiago Sueto --- I can confirm this bug on current Plasma from master branch. Operating System: openSUSE Tumbleweed 20200823 KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421237] Changing Activities effect broken on Wayland ( from kwin master )
https://bugs.kde.org/show_bug.cgi?id=421237 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #7 from Thiago Sueto --- I can't reproduce this on current master branch. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426127] New: Mouse button stays depressed
https://bugs.kde.org/show_bug.cgi?id=426127 Bug ID: 426127 Summary: Mouse button stays depressed Product: okular Version: 1.3.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ragha...@cs.wisc.edu Target Milestone: --- SUMMARY Every now and then okular enters a strange mode where, if I simply move the mouse it scrolls the page up or down instead of moving the cursor. STEPS TO REPRODUCE 1. Open a pdf document 2. Hold left button down and drag the mouse over the page of content. Okular enters this mode. It is not not clear how to exit this mode. OBSERVED RESULT When this happens, even closing okular and restarting it does not help. If I have multiple instances of okular running together, all of them get affected by this issue at the same time together. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426108] No audio after update to 20.04 - pipewire 0.3.8-1 - snd_hda_intel
https://bugs.kde.org/show_bug.cgi?id=426108 Martín Perazzo changed: What|Removed |Added CC||paulfeak...@gmail.com --- Comment #1 from Martín Perazzo --- *** Bug 425892 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425892] KDE Neon 5.19.4 Updated Caused Most Audio Devices to Disappear
https://bugs.kde.org/show_bug.cgi?id=425892 Martín Perazzo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #14 from Martín Perazzo --- *** This bug has been marked as a duplicate of bug 426108 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426108] No audio after update to 20.04 - pipewire 0.3.8-1 - snd_hda_intel
https://bugs.kde.org/show_bug.cgi?id=426108 Martín Perazzo changed: What|Removed |Added CC||rechapit...@yahoo.com.ar -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425266] baloo_file_extractor crashing repeatedly when indexing starts
https://bugs.kde.org/show_bug.cgi?id=425266 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #1 from Thiago Sueto --- Hello, could you enable the debug repositories for Ubuntu? You can do so by following this: https://wiki.ubuntu.com/Debug%20Symbol%20Packages After that, please install kubuntu-debug-installer and reproduce this bug again, using Dr. Konqi to fetch the required debug symbols. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425977] Button to assign keyboard shortcut shows a tooltip with unnecessary empty area
https://bugs.kde.org/show_bug.cgi?id=425977 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #2 from Thiago Sueto --- Can confirm, this occurs for any widget. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426047] Crash in multiple System Settings KCMs
https://bugs.kde.org/show_bug.cgi?id=426047 --- Comment #1 from Thiago Sueto --- Additional information: Opening each of the faulty KCMs individually works, but clicking on any other KCM leads to the same crash. Likewise, closing System Settings also leads to the same crash. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 425942] Elisa crash on open
https://bugs.kde.org/show_bug.cgi?id=425942 --- Comment #1 from Thiago Sueto --- No longer reproducible after updating today. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423259] Faulty icons display
https://bugs.kde.org/show_bug.cgi?id=423259 Dawid Wróbel changed: What|Removed |Added Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/-/commit/3e6114 ||a0847c122db1bcbb94e3a6de3f6 ||ab272b2 Version Fixed In||5.1.1 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Dawid Wróbel --- This was fixed in https://invent.kde.org/office/kmymoney/-/commit/3e6114a0847c122db1bcbb94e3a6de3f6ab272b2 -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 415883] ISBNdb returns no results with multiple ISBN numbers, work with single number lookup
https://bugs.kde.org/show_bug.cgi?id=415883 Robby Stephenson changed: What|Removed |Added Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/tellico/commit/8628c977c |ce/tellico/commit/37fcff21e |bfdb6f6660528fac7ef50b19c9e |ae2e8e3d10bb4884a97ac0b9140 |3603|3be2 --- Comment #3 from Robby Stephenson --- Git commit 37fcff21eae2e8e3d10bb4884a97ac0b91403be2 by Robby Stephenson. Committed on 03/09/2020 at 01:31. Pushed by rstephenson into branch 'master'. Update ISBNdb data source to search for multiple ISBN values Per the API documentation, this functionality is only available for Premium and Pro plans. However, with my current Premium plan, I still fail to receive results. FIXED-IN: 3.3.3 M +4-0ChangeLog M +45 -13 src/fetch/isbndbfetcher.cpp M +1-3src/fetch/isbndbfetcher.h M +44 -14 src/tests/isbndbfetchertest.cpp https://invent.kde.org/office/tellico/commit/37fcff21eae2e8e3d10bb4884a97ac0b91403be2 -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 415883] ISBNdb returns no results with multiple ISBN numbers, work with single number lookup
https://bugs.kde.org/show_bug.cgi?id=415883 Robby Stephenson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||3.3.3 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/offi ||ce/tellico/commit/8628c977c ||bfdb6f6660528fac7ef50b19c9e ||3603 --- Comment #2 from Robby Stephenson --- Git commit 8628c977cbfdb6f6660528fac7ef50b19c9e3603 by Robby Stephenson. Committed on 03/09/2020 at 01:31. Pushed by rstephenson into branch '3.3'. Update ISBNdb data source to search for multiple ISBN values Per the API documentation, this functionality is only available for Premium and Pro plans. However, with my current Premium plan, I still fail to receive results. FIXED-IN: 3.3.3 M +4-0ChangeLog M +45 -13 src/fetch/isbndbfetcher.cpp M +1-3src/fetch/isbndbfetcher.h M +44 -14 src/tests/isbndbfetchertest.cpp https://invent.kde.org/office/tellico/commit/8628c977cbfdb6f6660528fac7ef50b19c9e3603 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426111] Dolphin not showing free space
https://bugs.kde.org/show_bug.cgi?id=426111 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 424050 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424050] Sometimes free space available disappears from the status bar after I mount a partition of an internal hard disk
https://bugs.kde.org/show_bug.cgi?id=424050 Patrick Silva changed: What|Removed |Added CC||tapiwazimunh...@gmail.com --- Comment #3 from Patrick Silva --- *** Bug 426111 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426126] plasmashell crashed from mouseover taskbar
https://bugs.kde.org/show_bug.cgi?id=426126 Alex -lx- Kuhnen changed: What|Removed |Added CC||l...@lx21.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426126] New: plasmashell crashed from mouseover taskbar
https://bugs.kde.org/show_bug.cgi?id=426126 Bug ID: 426126 Summary: plasmashell crashed from mouseover taskbar Product: plasmashell Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: l...@lx21.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-10-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: --I moved the mouse over the taskbar, which is normally hided in my settings, and after showing the taskbar, the system freezes for about 30-40 seconds. --Normally (by moving the mouse to the taskbar) I wanted to switch from dolphin to konsole when the crash happens. --There were no big operations running in dolphin or konsole but a backup script (cp -ru ... ...) was running as cronjob in the background. --By the way: the memory used by plasmashell is increasing from 90MB (after login) up to 300-400MB in 20-30 minutes. And there isn't really a difference between working with the system or not working with it... The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f44c8fe4840 (LWP 17386))] Thread 8 (Thread 0x7f449f7fe700 (LWP 17559)): #0 0x7f44cdfe7819 in __GI___poll (fds=0x7f4498004e10, nfds=1, timeout=5629) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f44cc0dc136 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f44cc0dc25c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f44ce4f9743 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f44ce4a715b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f44ce2f6e76 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f44ce300a67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f44cd21cfa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7f44cdff24cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f44aafe6700 (LWP 17553)): #0 0x7ffe0ed8eb34 in clock_gettime () #1 0x7f44cdf6 in __GI___clock_gettime (clock_id=1, tp=0x7f44aafe5a60) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f44ce4f9061 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f44ce4f7899 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f44ce4f7e95 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f44ce4f94be in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f44cc0db669 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f44cc0dc06b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f44cc0dc25c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f44ce4f9743 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f44ce4a715b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f44ce2f6e76 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f44cfeac476 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f44ce300a67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f44cd21cfa3 in start_thread (arg=) at pthread_create.c:486 #15 0x7f44cdff24cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f44b3020700 (LWP 17544)): #0 0x7f44cd22300c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55f8548579d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f44cd22300c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f854857988, cond=0x55f8548579b0) at pthread_cond_wait.c:502 #2 0x7f44cd22300c in __pthread_cond_wait (cond=0x55f8548579b0, mutex=0x55f854857988) at pthread_cond_wait.c:655 #3 0x7f44b736e51b in () at /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7f44b736e397 in () at /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7f44cd21cfa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7f44cdff24cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f44b3821700 (LWP 17543)): #0 0x7f44cd22300c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55f854857878) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f44cd22300c in
[kdelibs] [Bug 247270] Option to display menubar only when holding down (or another meta-key)
https://bugs.kde.org/show_bug.cgi?id=247270 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #8 from Roy --- Over a decade later, is there another standard way to give focus to the menu bar? I haven't found one, which is a bit of a disappointment after leaving Windows. One thing to be wary of would be the Sticky Keys accessibility feature. If Lock Keys is off, pressing Alt twice would work, but with it on (the default) it would have to be a hold or something else. Best to consult with someone who relies on that feature. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426119] Latte-Dock 0.9.86 on kubuntu 20.04 qml loading error
https://bugs.kde.org/show_bug.cgi?id=426119
--- Comment #3 from SlothDS ---
(In reply to Michail Vourlakos from comment #1)
> 1. Are you sure that kde frameworks is 5.68? That codepath is executed only
> with 5.69 and above
> 2. Try to install kirigami2 library
1. yes, system info screenshot attached.
2. kirigami2 installed
$ dpkg -l | awk '/kirigami/{print $2 "_" $3}'
kirigami2-dev_5.68.0-0ubuntu2
libkf5kirigami2-5_5.68.0-0ubuntu2
libkf5kirigami2-doc_5.68.0-0ubuntu2
qml-module-org-kde-kirigami2_5.68.0-0ubuntu2
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 426119] Latte-Dock 0.9.86 on kubuntu 20.04 qml loading error
https://bugs.kde.org/show_bug.cgi?id=426119 --- Comment #2 from SlothDS --- Created attachment 131374 --> https://bugs.kde.org/attachment.cgi?id=131374=edit system info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425590] no OSD indication when switching keyboard layout with Application Policy
https://bugs.kde.org/show_bug.cgi?id=425590 Andrey changed: What|Removed |Added URL||https://invent.kde.org/plas ||ma/kwin/-/merge_requests/21 ||0 Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426120] wrong OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426120 Andrey changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 URL||https://invent.kde.org/plas ||ma/kwin/-/merge_requests/21 ||0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426122] redundant OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426122 Andrey changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED URL||https://invent.kde.org/plas ||ma/kwin/-/merge_requests/21 ||0 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 411681] Yakuake always shown on second monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=411681 --- Comment #4 from Claudius Ellsel --- So you don't use scaling to make contents bigger/smaller on the screens? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 425384] Yakuake jumps between displays since 20.08.0
https://bugs.kde.org/show_bug.cgi?id=425384 --- Comment #6 from Claudius Ellsel --- Alright, thanks for confirming! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 275433] [multi-head] multiple window size issues
https://bugs.kde.org/show_bug.cgi?id=275433 Claudius Ellsel changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #17 from Claudius Ellsel --- (In reply to Nicolas from comment #15) > As the patch seems to be working better also for other people, I can clean > up the patch and prepare a proper merge request for the change That would be great! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 394858] Show on all desktops not working
https://bugs.kde.org/show_bug.cgi?id=394858 Claudius Ellsel changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 394858] Show on all desktops not working
https://bugs.kde.org/show_bug.cgi?id=394858 --- Comment #7 from Claudius Ellsel --- Maybe we have actually to different causes here, one Wayland related and one also happening on X11 under certain conditions. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 394858] Show on all desktops not working
https://bugs.kde.org/show_bug.cgi?id=394858 Claudius Ellsel changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Claudius Ellsel --- Alright, thanks for the additional details! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425288] D a frame to a Background layer with color as default pixel creates artifacts
https://bugs.kde.org/show_bug.cgi?id=425288 Eoin O'Neill changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/8a5e90a9b |hics/krita/commit/414ccc726 |708da17abeff0c38a92ab873e9a |cb5dbc89d7d88a43016fa86b0f5 |61fc|f5a9 --- Comment #5 from Eoin O'Neill --- Git commit 414ccc726cb5dbc89d7d88a43016fa86b0f5f5a9 by Eoin O'Neill. Committed on 02/09/2020 at 22:28. Pushed by eoinoneill into branch 'krita/4.3'. Frame Drag and Drop Default Pixel Correction When uploading a frame to dstData (KisPaintDeviceData), we should make sure that the defaultPixel between the two are equivalient and rectify the issue if they do not match. (cherry picked from commit 8a5e90a9b708da17abeff0c38a92ab873e9a61fc) M +12 -0libs/image/kis_paint_device.cc https://invent.kde.org/graphics/krita/commit/414ccc726cb5dbc89d7d88a43016fa86b0f5f5a9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425286] It is possible to D frames onto a locked layer
https://bugs.kde.org/show_bug.cgi?id=425286 Eoin O'Neill changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/8ab41ecb1 |hics/krita/commit/0de750e3a |638394f8b730d93265b5fa592aa |d19747f0c3583ed8976e84ff891 |9142|96de --- Comment #3 from Eoin O'Neill --- Git commit 0de750e3ad19747f0c3583ed8976e84ff89196de by Eoin O'Neill. Committed on 02/09/2020 at 22:22. Pushed by eoinoneill into branch 'krita/4.3'. Frame Drag and Drop No Longer Accepted on Uneditable Layers Locked layers and invisible layers cannot accept new keyframe content when drag and dropping data, which is in line with the rest of the timeline design. (cherry picked from commit 8ab41ecb1638394f8b730d93265b5fa592aa9142) M +2-0plugins/dockers/animation/timeline_frames_model.cpp https://invent.kde.org/graphics/krita/commit/0de750e3ad19747f0c3583ed8976e84ff89196de -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 425410] Names of tag categories suddenly have superfluous ampersands added to them
https://bugs.kde.org/show_bug.cgi?id=425410 --- Comment #10 from Johannes Zarl-Zierl --- I have opened a bug with Qt: https://bugreports.qt.io/browse/QTBUG-86407 -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 426088] Compile error (kdesrc-build)
https://bugs.kde.org/show_bug.cgi?id=426088 Justin changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Justin --- Solus -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418699] Keyboard Switching policy Application always shows keyboard change OSD notification on Wayland
https://bugs.kde.org/show_bug.cgi?id=418699 --- Comment #7 from Andrey --- (In reply to elman from comment #6) > Hi Andrey. I tried again on Plasma 5.19.5 and you are right. Now it behaves > differently. OSD shows only when I start typing. Which is somehow even more > confusing to me. Hi Elman, thanks for testing. Actually, the behavior you described earlier is still there - just switch with Alt+Tab without typing between apps with different layout and you'll get the OSD. Still, I'm not sure if the both OSDs are bugs or features. There are bunch of fixes pending on that matter, so it looks OK for me here even with that OSDs. I'll ask you to retest (e.g on KDE Neon Dev) when that fixes land so you could decide for yourself. > When I use Thunderbird, sometimes I write in English and > sometimes in different language. So I do not remember which layout I used > last and there is no way of knowing until I start typing. It's not quite the case any more - see bug 425343. You can know the current layout at any time just by hovering the Keyboard Layout applet. > Not to mention > that OSD might appear over the text I'm typing and it is distracting. Didn't notice that problem, but I don't use Plasma as my daily driver (yet?). > The other bug I mentioned is that system tray layout indicator doesn't show > current layout. See https://bugs.kde.org/show_bug.cgi?id=390079 Yeah, that's what should be done for sure. Thanks for reporting. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 425841] SIGPIPE, then a crash when the first event loop starts at least 60 seconds after KDevelop launch
https://bugs.kde.org/show_bug.cgi?id=425841 Francis Herne changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.7.0 Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/43db1a ||72dbbe91e231ab7349f202df6a5 ||fb4337c Status|REPORTED|RESOLVED --- Comment #1 from Francis Herne --- Git commit 43db1a72dbbe91e231ab7349f202df6a5fb4337c by Francis Herne, on behalf of Igor Kushnir. Committed on 02/09/2020 at 22:03. Pushed by flherne into branch 'master'. Don't crash during a slow (>= 60 seconds) startup A quick benchmark shows that the added QCoreApplication::processEvents() call takes the same time - 6 milliseconds - in Debug and Release builds. 6 milliseconds is not a noticeable startup slowdown, especially considering that the event loop does useful work: processes events, which would have to be handled eventually anyway. FIXED-IN: 5.7.0 M +6-0app/main.cpp https://invent.kde.org/kdevelop/kdevelop/commit/43db1a72dbbe91e231ab7349f202df6a5fb4337c -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426114] System Settings crashed when attempting select Display and Monitor.
https://bugs.kde.org/show_bug.cgi?id=426114 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |NOT A BUG --- Comment #2 from David Edmundson --- >#8 0x7f4b688d77c4 in QQuickWidgetPrivate::handleContextCreationFailure >(this=this@entry=0x562bb4f2ffa0, format=...) at >/usr/include/qt5/QtCore/qarraydata.h:208 It's a recurring bug of nvidia updating libGL without the kernel being restarted with the matching kernel. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 425931] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=425931 --- Comment #3 from john4deidre2...@xtra.co.nz --- Created attachment 131373 --> https://bugs.kde.org/attachment.cgi?id=131373=edit New crash information added by DrKonqi kontact (5.15.0 (20.08.0)) using Qt 5.15.0 - What I was doing when the application crashed: This happens intermittently each time kontact is started -- Backtrace (Reduced): #4 0x7f91c96e6347 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append (this=0x55b52906e0a0, t=@0x7ffc396395c0: 0x55b529215380) at ../../include/QtCore/../../src/corelib/tools/qlist.h:622 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426119] Latte-Dock 0.9.86 on kubuntu 20.04 qml loading error
https://bugs.kde.org/show_bug.cgi?id=426119 --- Comment #1 from Michail Vourlakos --- 1. Are you sure that kde frameworks is 5.68? That codepath is executed only with 5.69 and above 2. Try to install kirigami2 library -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426114] System Settings crashed when attempting select Display and Monitor.
https://bugs.kde.org/show_bug.cgi?id=426114 --- Comment #1 from guyto...@yahoo.com --- Seems to be resolved after updating system. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426086] Tiff file reading extremely slow
https://bugs.kde.org/show_bug.cgi?id=426086 --- Comment #3 from k...@binkmail.com --- More observation. Viewing one of these files in the digiKam slideshow takes about 2 minutes to load and digiKam memory usage slowly increases by about 600MB during that 2 minutes then falls back to about the original usage when the image is displayed. Sure looks like digiKam is reading all of this 500MB tag (for some reason backwards and slowly) into memory then discarding it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426125] New: The 'Link to application' option 'Run in terminal' can overwrite an application configuration file
https://bugs.kde.org/show_bug.cgi?id=426125 Bug ID: 426125 Summary: The 'Link to application' option 'Run in terminal' can overwrite an application configuration file Product: plasmashell Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: atesc...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I turn on the 'Run in terminal' option in a 'Link to application' on the desktop, some process hijacks the options for the application and overwrites the applications configuration file. This, in turn, destroys the application's ability to operate. STEPS TO REPRODUCE 1. Create a 'Link to application' 2. Setup the application command to include a "--config" option for the application 3. In "Advanced Options" select "Run in terminal" and "Do not close when command exits" 4. Select OK and OK to create the desktop link 5. Run the new desktop link OBSERVED RESULT The file pointed to by the "--config" option for the application is corrupted / overwritten losing all setting to effectively operate the application. EXPECTED RESULT The config file for the application is not altered / corrupted / overwritten by other processes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION By making the applications file Read Only, the system reports the culprit when the application is started in a dialog: konsole - Dialog (i) Configuration file "/home/<..redacted..>/Bin/agraph-7.0.2/lib/agraph.cfg" not writable. Please contact your system administrator. When starting konsole with a --config option and a file it reports: "Unknown option 'config'." Help on konsole also does not report the option. So, what is the major malfunction? Indeed, some process within or about konsole is taking the options for their own. The application still receives the options and proceeds. However, at some point, the config file is overwritten by the other process and corrupting the application. When the file is Read/Write, the overwritten file contents show the following: [Desktop Entry] DefaultProfile= [Favorite Profiles] Favorites= [MainWindow] State=/wD9AoHCBAQICPwA ToolBarsMovable=Disabled I've placed the application command in quotes to try to mitigate to no avail. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426124] Cannot Animate Because Krita Crashes
https://bugs.kde.org/show_bug.cgi?id=426124 Tymond changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from Tymond --- Can you please check out Krita Plus version from https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/ ? Does it also crash? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426124] Cannot Animate Because Krita Crashes
https://bugs.kde.org/show_bug.cgi?id=426124 charlesvantus...@hotmail.com changed: What|Removed |Added CC||charlesvantus...@hotmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426124] New: Cannot Animate Because Krita Crashes
https://bugs.kde.org/show_bug.cgi?id=426124 Bug ID: 426124 Summary: Cannot Animate Because Krita Crashes Product: krita Version: 4.3.0-beta1 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: charlesvantus...@hotmail.com Target Milestone: --- Created attachment 131372 --> https://bugs.kde.org/attachment.cgi?id=131372=edit Video recording of Krita crash when clicking on second animation frame SUMMARY STEPS TO REPRODUCE 1. Open Krita 2. Create New File for animation 3. Have Docker/Timeline/Onionskins toolbars 4. Click on any other animation frame causes Krita to crash. OBSERVED RESULT: Krita crashes. Impossible to animate due to crashing. 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.
[digikam] [Bug 426086] Tiff file reading extremely slow
https://bugs.kde.org/show_bug.cgi?id=426086 --- Comment #2 from k...@binkmail.com --- Bit hard for me to tell what is going on especially when it is easy to have these files in the system disk cache which hides the problem and difficult to know it is in the cache. Seems to be related to additional layers saved in photoshop and possibly in particular smart object layers. I took a 20 M pixel 16 bit tiff file which was about 100MB. Loaded in photoshop, duplicated the background layer, turned that layer into a smart object and applied a simple filter then saved the file as tiff. The file size increased by about 600MB and it chokes digiKam but nothing else. I guess digiKam is slowly reading the large extra elements it doesn't need to. The problem files are huge. This is a tiffdump of one: Magic: 0x4949 Version: 0x2a Directory 0: offset 8 (0x8) next 0 (0) SubFileType (254) LONG (4) 1<0> ImageWidth (256) SHORT (3) 1<3109> ImageLength (257) SHORT (3) 1<4663> BitsPerSample (258) SHORT (3) 3<16 16 16> Compression (259) SHORT (3) 1<8> Photometric (262) SHORT (3) 1<2> Make (271) ASCII (2) 10 Model (272) ASCII (2) 6 StripOffsets (273) LONG (4) 84<26978 985968 1957330 2933846 3906524 4887716 5874280 6864180 7862052 8865962 9875066 10882740 11884212 12894074 13906004 14919378 15934402 16947186 17960762 18976602 19997708 21021120 22044318 23069588 ...> Orientation (274) SHORT (3) 1<1> SamplesPerPixel (277) SHORT (3) 1<3> RowsPerStrip (278) SHORT (3) 1<56> StripByteCounts (279) LONG (4) 84<958990 971362 976516 972677 981192 986563 989900 997871 1003909 1009104 1007673 1001471 1009861 1011929 1013374 1015023 1012783 1013576 1015839 1021106 1023411 1023197 1025270 1028923 ...> XResolution (282) RATIONAL (5) 1<72> YResolution (283) RATIONAL (5) 1<72> PlanarConfig (284) SHORT (3) 1<1> ResolutionUnit (296) SHORT (3) 1<2> Software (305) ASCII (2) 31 DateTime (306) ASCII (2) 20<2020:07:11 04:08:26\0> 700 (0x2bc) BYTE (1) 17251<0x3c 0x3f 0x78 0x70 0x61 0x63 0x6b 0x65 0x74 0x20 0x62 0x65 0x67 0x69 0x6e 0x3d 0x22 0xef 0xbb 0xbf 0x22 0x20 0x69 0x64 ...> 33723 (0x83bb) UNDEFINED (7) 31<0x1c 0x2 00 00 0x2 00 00 0x1c 0x2 0x37 00 0x8 0x32 0x30 0x32 0x30 0x30 0x32 0x30 0x39 0x1c 0x2 0x3c 00 ...> 34377 (0x8649) BYTE (1) 8058<0x38 0x42 0x49 0x4d 0x4 0x25 00 00 00 00 00 0x10 0xcc 0xf3 0xa8 0x58 0xb9 0xcd 0x3f 0xd2 0x8e 0xcd 0xc9 0x50 ...> 34665 (0x8769) LONG (4) 1<84116084> ICC Profile (34675) UNDEFINED (7) 560<00 00 0x2 0x30 0x41 0x44 0x42 0x45 0x2 0x10 00 00 0x6d 0x6e 0x74 0x72 0x52 0x47 0x42 0x20 0x58 0x59 0x5a 0x20 ...> 37724 (0x935c) UNDEFINED (7) 502520192<0x41 0x64 0x6f 0x62 0x65 0x20 0x50 0x68 0x6f 0x74 0x6f 0x73 0x68 0x6f 0x70 0x20 0x44 0x6f 0x63 0x75 0x6d 0x65 0x6e 0x74 ...> is the 37724 at the end a 500MB tag that tiffdump doesn't know? If so I guess that is what digikam has to be reading at 4MB/s to take so long. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 425461] Option to start applications on double click
https://bugs.kde.org/show_bug.cgi?id=425461 --- Comment #2 from manuelcha...@gmail.com --- (In reply to Michail Vourlakos from comment #1) > I dont know any other taskmanager offering this, even windows do not offer > such option that they use double-click almost everywhere. It's true Window itself doesn't offer that option, but I used to enable that option through "7+ Taskbar Tweaker" which can customize the taskbar's behavior. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 Andrey changed: What|Removed |Added Flags||Usability+, VisualDesign+ -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 425410] Names of tag categories suddenly have superfluous ampersands added to them
https://bugs.kde.org/show_bug.cgi?id=425410 --- Comment #9 from Johannes Zarl-Zierl --- Thanks for checking! So the takeaway so far is that the title of QDockWidget (i.e. the dockable parts used in the annotation dialog) is displaying the accelerators incorrectly in the following styles: cde motif Windows Fusion Btw. this also affects other applications as well. I tested with "QT_STYLE_OVERRIDE=Fusion tellico" and see the same kind of display problem (tellico uses the QDockWidget as well). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425343] [Wayland] Keyboard Layout applet doesn't follow actual layout switching
https://bugs.kde.org/show_bug.cgi?id=425343 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=390079 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425343 CC||butir...@gmail.com Assignee|unassigned-b...@kde.org |butir...@gmail.com Status|CONFIRMED |ASSIGNED --- Comment #9 from Andrey --- Hi, please note Keyboard Layout applet follows actual layout now: bug 425343. I agree it's a pity it doesn't show the layout permanently though. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 425232] PPC ISA 3.1 support is missing, part 2
https://bugs.kde.org/show_bug.cgi?id=425232 --- Comment #10 from Carl Love --- Correction the third set of patches is in https://bugs.kde.org/show_bug.cgi?id=426123 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426108] No audio after update to 20.04 - pipewire 0.3.8-1 - snd_hda_intel
https://bugs.kde.org/show_bug.cgi?id=426108 Daniel changed: What|Removed |Added CC||daniel.skap...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 426123] PPC ISA 3.1 support is missing, part 3
https://bugs.kde.org/show_bug.cgi?id=426123 --- Comment #2 from Carl Love --- The previous set of patches is in https://bugs.kde.org/show_bug.cgi?id=425232 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 425232] PPC ISA 3.1 support is missing, part 2
https://bugs.kde.org/show_bug.cgi?id=425232 --- Comment #9 from Carl Love --- The third set of patches is inhttps://bugs.kde.org/show_bug.cgi?id=425232 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 426123] PPC ISA 3.1 support is missing, part 3
https://bugs.kde.org/show_bug.cgi?id=426123 --- Comment #1 from Carl Love --- Created attachment 131371 --> https://bugs.kde.org/attachment.cgi?id=131371=edit Add 3.1 instruction test suite support -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 426123] New: PPC ISA 3.1 support is missing, part 3
https://bugs.kde.org/show_bug.cgi?id=426123 Bug ID: 426123 Summary: PPC ISA 3.1 support is missing, part 3 Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: c...@us.ibm.com Target Milestone: --- Created attachment 131370 --> https://bugs.kde.org/attachment.cgi?id=131370=edit add isa 3.1 support for instructiions to guest_ppc_toIR.c This patch contains the third set of patches for the PPC64 ISA 3.1 valgrind support. The set only consists of one Valgrind and one testsuite patch as the are relatively large. The Valgrind patch adds support for the SIMD permute class instructions. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418699] Keyboard Switching policy Application always shows keyboard change OSD notification on Wayland
https://bugs.kde.org/show_bug.cgi?id=418699 Andrey changed: What|Removed |Added Flags||Usability+, VisualDesign+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426122] redundant OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426122 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=418699 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418699] Keyboard Switching policy Application always shows keyboard change OSD notification on Wayland
https://bugs.kde.org/show_bug.cgi?id=418699 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=426122 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425590] no OSD indication when switching keyboard layout with Application Policy
https://bugs.kde.org/show_bug.cgi?id=425590 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=426122 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426120] wrong OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426120 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=426122 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 425930] "Edit Dock" menu crashes when trying to toggle on "Advanced Options" on second monitor dock
https://bugs.kde.org/show_bug.cgi?id=425930 --- Comment #6 from Matt McDonald --- (In reply to Michail Vourlakos from comment #4) > This is not reproducable in my multi-screen system. Please try again with > latest commits. Sorry I've had some hardware issues that necessitated both a reinstall and temporary use of a single monitor, I should hopefully have my second monitor setup back up and running today. Will report back. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426122] redundant OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426122 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425590, ||https://bugs.kde.org/show_b ||ug.cgi?id=426120 Flags||Wayland+, X11- Assignee|kwin-bugs-n...@kde.org |butir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426122] New: redundant OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426122 Bug ID: 426122 Summary: redundant OSD indication when switching keyboard layout with Policy other than Global Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: butir...@gmail.com Target Milestone: --- SUMMARY Described the case with Application switching Policy. STEPS TO REPRODUCE 1. Set Application Policy for keyboard layout switching in Keyboard Settings. Make sure there are at least 2 layouts. 2. Switch layout in one app, note OSD notification pop up on the switching. 3. Focus another app with mouse. 4. Start switching to the first app, now using Alt+Tab key combination. While pressing Alt+Tab, hold down Alt for a while, then Tab. OBSERVED RESULT On Alt, OSD notification popup immediately even before the app switch. EXPECTED RESULT We are not interested in OSD for the previous app on app switching. SOFTWARE/OS VERSIONS Operating System: Ubuntu 20.04 KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426112] Virtual Keyboard problems with lock screen
https://bugs.kde.org/show_bug.cgi?id=426112 --- Comment #3 from medin --- (In reply to David Edmundson from comment #2) > Can you share your screen resolution please so I can reproduce. I have a laptop with screen 15.6" and resolution 1366x768. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426121] New: Nightlight turns off when launching Nvidia X Settings
https://bugs.kde.org/show_bug.cgi?id=426121 Bug ID: 426121 Summary: Nightlight turns off when launching Nvidia X Settings Product: systemsettings Version: 5.19.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: transtr...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY Nightlight turns off when launching Nvidia X Settings. The option is still toggled on, but night color doesn't work anymore. To fix it, you need to disable the night color(animation from the chosen color to normal does happen/occur) and re-enable it. Every opening of the NVIDIA X Server Settings causes the Night Color to stop working until re-enabled. STEPS TO REPRODUCE 1. Turn on Night Color 2. Open application NVIDIA X Server Settings OBSERVED RESULT - Night Color turns off EXPECTED RESULT - None SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux x86_64(last update 02.09.2020) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.19 Qt Version: - QMake version 3.1 - Using Qt version 5.15.0 in /usr/lib ADDITIONAL INFORMATION NVIDIA Driver Version: 450.66 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425286] It is possible to D frames onto a locked layer
https://bugs.kde.org/show_bug.cgi?id=425286 Eoin O'Neill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/8ab41ecb1 ||638394f8b730d93265b5fa592aa ||9142 Resolution|--- |FIXED --- Comment #2 from Eoin O'Neill --- Git commit 8ab41ecb1638394f8b730d93265b5fa592aa9142 by Eoin O'Neill. Committed on 02/09/2020 at 20:44. Pushed by eoinoneill into branch 'master'. Frame Drag and Drop No Longer Accepted on Uneditable Layers Locked layers and invisible layers cannot accept new keyframe content when drag and dropping data, which is in line with the rest of the timeline design. M +2-0plugins/dockers/animation/timeline_frames_model.cpp https://invent.kde.org/graphics/krita/commit/8ab41ecb1638394f8b730d93265b5fa592aa9142 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Matt McDonald changed: What|Removed |Added CC||gardotd...@gmail.com --- Comment #26 from Matt McDonald --- I also have this bug on Manjaro Linux 20.0.3 (Plasma 5.19.4). Weirdly my old install that I just wiped the other day, that had been around for months, had working shortcuts (they must have been grandfathered, as others have said). But now all new shortcuts fail unless I use the "Custom Shortcuts" menu instead of the "Global Shortcuts" as intended. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426113] When closing emacs with C-z from fullscreen kwin crashes
https://bugs.kde.org/show_bug.cgi?id=426113 --- Comment #1 from Vlad Zahorodnii --- I can't reproduce this bug with kwin 5.18 built from source code. Have you installed any kwin scripts? also since it's a crash, a backtrace would be really helpful with diagnosing the root cause of the crash. You can retrieve the backtrace by clicking a sad face icon in the system tray after kwin has crashed. Make sure that you have installed all relevant debug packages for kwin before attempting to retrieve the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425288] D a frame to a Background layer with color as default pixel creates artifacts
https://bugs.kde.org/show_bug.cgi?id=425288 Eoin O'Neill changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/8a5e90a9b ||708da17abeff0c38a92ab873e9a ||61fc Status|ASSIGNED|RESOLVED --- Comment #4 from Eoin O'Neill --- Git commit 8a5e90a9b708da17abeff0c38a92ab873e9a61fc by Eoin O'Neill. Committed on 02/09/2020 at 20:20. Pushed by eoinoneill into branch 'master'. Frame Drag and Drop Default Pixel Correction When uploading a frame to dstData (KisPaintDeviceData), we should make sure that the defaultPixel between the two are equivalient and rectify the issue if they do not match. M +12 -0libs/image/kis_paint_device.cc https://invent.kde.org/graphics/krita/commit/8a5e90a9b708da17abeff0c38a92ab873e9a61fc -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426082] Calendar schedules all appointments full day
https://bugs.kde.org/show_bug.cgi?id=426082 --- Comment #4 from Dave Bachmann --- Same issue with upper case. Typically it's en_CA.UTF-8, but I could live with US. From: bugzilla_nore...@kde.org Sent: Wednesday, September 2, 2020 10:55 To: davebachm...@hotmail.com Subject: [kontact] [Bug 426082] Calendar schedules all appointments full day https://bugs.kde.org/show_bug.cgi?id=426082 gjditchfi...@acm.org changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from gjditchfi...@acm.org --- Dang. For the record, what locale do you normally run in? I see a typo in my previous comment: I meant to type "LANG=en_US.UTF-8 korganizer" (uppercase "US"). -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425590] no OSD indication when switching keyboard layout with Application Policy
https://bugs.kde.org/show_bug.cgi?id=425590 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=426120 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426120] wrong OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426120 Andrey changed: What|Removed |Added Flags||Wayland+, X11- See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425590 Assignee|kwin-bugs-n...@kde.org |butir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426120] New: wrong OSD indication when switching keyboard layout with Policy other than Global
https://bugs.kde.org/show_bug.cgi?id=426120 Bug ID: 426120 Summary: wrong OSD indication when switching keyboard layout with Policy other than Global Product: kwin Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: butir...@gmail.com Target Milestone: --- SUMMARY Described the case with Application switching Policy. STEPS TO REPRODUCE 1. Set Application Policy for keyboard layout switching in Keyboard Settings. Make sure there are at least 2 layouts. 2. Switch layout in one app, note OSD notification pop up on the switching. 3. Focus another app with mouse. 4. Start switching to the first app from there, now using Alt+Tab key combination. While pressing Alt+Tab, hold Alt for a little until Task Switcher appears, then shortly release Alt. OBSERVED RESULT After the app switches, OSD notification indicates wrong layout (of the previous app). EXPECTED RESULT OSD should correspond to the actual app just switched. SOFTWARE/OS VERSIONS Operating System: Ubuntu 20.04 KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426112] Virtual Keyboard problems with lock screen
https://bugs.kde.org/show_bug.cgi?id=426112 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Can you share your screen resolution please so I can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426119] New: Latte-Dock 0.9.86 on kubuntu 20.04 qml loading error
https://bugs.kde.org/show_bug.cgi?id=426119 Bug ID: 426119 Summary: Latte-Dock 0.9.86 on kubuntu 20.04 qml loading error Product: lattedock Version: git (master) Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: sl...@devils.su Target Milestone: --- SUMMARY Latest latte-dock loaded with loading QML file error on Kubuntu 20.04 LTS. STEPS TO REPRODUCE 1. get latte-dock latest git version 2. build 3. run with latte-dock --cc OBSERVED RESULT Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.latte.containment/contents/ui/main.qml:1350:13: Type Background.MultiLayered unavailable file:///usr/share/plasma/plasmoids/org.kde.latte.containment/contents/ui/background/MultiLayered.qml:295:5: Type Colorizer.CustomBackground unavailable file:///usr/share/plasma/plasmoids/org.kde.latte.containment/contents/ui/colorizer/CustomBackground.qml:116:26: Type KirigamiShadowedRectangle unavailable EXPECTED RESULT Latte-Dock has no QML errors SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 LTS (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Latte-Dock Version: 0.9.86 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426118] Tag named -Unknown- cannot be deleted
https://bugs.kde.org/show_bug.cgi?id=426118 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426118] Tag named -Unknown- cannot be deleted
https://bugs.kde.org/show_bug.cgi?id=426118 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- This is intentional, the face engine needs this tag to assign unknown faces. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425892] KDE Neon 5.19.4 Updated Caused Most Audio Devices to Disappear
https://bugs.kde.org/show_bug.cgi?id=425892 --- Comment #13 from Daniel --- (In reply to Paul Feakins from comment #12) > What you're seeing in that bug is actually subtly different from what I'm > seeing. You mention the volume icon is greyed-out, but for me the icon is > there, I can click it, and some outputs are shown - digital ones - but the > analogue one I would usually use was not there. As above, pavucontrol > allowed me to select it and get it back. I think it may be because we have different hardware, for my case I suppose that all my audio hardware is controlled by Intel HDA Sound in the intel chipset, that's why I have only dummy output. My guess is that hda_intel outputs are the one affected. Do yo have several audio outputs/hardware managed by different chips? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 372464] Simple editing/annotation features (drawing Arrows / Text / Highlighting) after doing screenshot
https://bugs.kde.org/show_bug.cgi?id=372464 --- Comment #14 from Nate Graham --- Yes this feature uses that exact same annotation widget from KSnip. :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426118] Tag named -Unknown- cannot be deleted
https://bugs.kde.org/show_bug.cgi?id=426118 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Metadata-Editor |Tags-Engine -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426118] New: Tag named -Unknown- cannot be deleted
https://bugs.kde.org/show_bug.cgi?id=426118 Bug ID: 426118 Summary: Tag named -Unknown- cannot be deleted Product: digikam Version: 7.0.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: minor Priority: NOR Component: Metadata-Editor Assignee: digikam-bugs-n...@kde.org Reporter: jo.y.v...@gmail.com Target Milestone: --- SUMMARY Inside Captions-Tag: there is a face tag with a sub-tag called "unknown". It is possible to rename the tag "unknown", but impossible to delete that tag, because Digikam re-creates this tag over and over again, after deletion SOFTWARE/OS VERSIONS macOS: 10.14.6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426115] Make drag-n-drop more evident
https://bugs.kde.org/show_bug.cgi?id=426115 caulier.gil...@gmail.com changed: What|Removed |Added OS|All |macOS CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426116] Compact database (unique block instead of loose files)
https://bugs.kde.org/show_bug.cgi?id=426116 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- What do you mean by conpact "database" Do you talk about the core database files used by digiKAm to store all metadata for the DAM ? Do you talk about the collection of album ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365263] Dragging a image to an Album cannot see which album easily
https://bugs.kde.org/show_bug.cgi?id=365263 Maik Qualmann changed: What|Removed |Added CC||jo.y.v...@gmail.com --- Comment #5 from Maik Qualmann --- *** Bug 426115 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426116] Compact database (unique block instead of loose files)
https://bugs.kde.org/show_bug.cgi?id=426116 caulier.gil...@gmail.com changed: What|Removed |Added OS|All |macOS -- You are receiving this mail because: You are watching all bug changes.
