[lattedock] [Bug 410707] A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/bf66aa35a75d65c04f5 |te-dock/f7d968ff6d9651b0112 |27db41dea2d92d57f18b3 |cf75e3e169c249fd4b4ea --- Comment #6 from Michail Vourlakos --- Git commit f7d968ff6d9651b0112cf75e3e169c249fd4b4ea by Michail Vourlakos. Committed on 08/08/2019 at 06:51. Pushed by mvourlakos into branch 'master'. update struts when normalThickness value changes --the issue was pretty obvious when the user was using a top view with thickness < 24px. and a bottom view always visible. In that case the top view struts on startup did not decrease below at 24px. M +5-2app/view/visibilitymanager.cpp https://commits.kde.org/latte-dock/f7d968ff6d9651b0112cf75e3e169c249fd4b4ea -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410695] KDE application launcher button no longer animated.
https://bugs.kde.org/show_bug.cgi?id=410695 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/8a9224ed3c05b2df2b3 |te-dock/2b9b95279d2457bec36 |e0d28308ba94ec109d7cb |d2c97f3371d8a56597ad8 --- Comment #4 from Michail Vourlakos --- Git commit 2b9b95279d2457bec36d2c97f3371d8a56597ad8 by Michail Vourlakos. Committed on 08/08/2019 at 06:51. Pushed by mvourlakos into branch 'master'. enable highlighting effect for plasma indicator M +1-1indicators/org.kde.latte.plasma/package/ui/main.qml https://commits.kde.org/latte-dock/2b9b95279d2457bec36d2c97f3371d8a56597ad8 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 410705] Trojita: Message that was opened in a standalone window should be marked as read
https://bugs.kde.org/show_bug.cgi?id=410705 --- Comment #2 from Ringill --- I hide the messaging pane using mouse. I resize it, making it thinner and thinner, and then after it passes some barrier of width (about 100-150 pixels), it disappears completely. I find it very useful on my small screen (1024 x 600) on old EEE PC. Qt widget style is Breeze, LXQT theme Lubuntu Arc. Thease are stock settings of Lubuntu 18.10 that I have. View->Layout is Wide. IMAP->Settings->automatically mark messages as read is "immediately". -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410695] KDE application launcher button no longer animated.
https://bugs.kde.org/show_bug.cgi?id=410695 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/8a9224ed3c05b2df2b3 ||e0d28308ba94ec109d7cb Resolution|--- |FIXED --- Comment #3 from Michail Vourlakos --- Git commit 8a9224ed3c05b2df2b3e0d28308ba94ec109d7cb by Michail Vourlakos. Committed on 08/08/2019 at 06:25. Pushed by mvourlakos into branch 'v0.9'. enable highlighting effect for plasma indicator M +1-1indicators/org.kde.latte.plasma/package/ui/main.qml https://commits.kde.org/latte-dock/8a9224ed3c05b2df2b3e0d28308ba94ec109d7cb -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410707] A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 Michail Vourlakos changed: What|Removed |Added Latest Commit||https://commits.kde.org/lat ||te-dock/bf66aa35a75d65c04f5 ||27db41dea2d92d57f18b3 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Michail Vourlakos --- Git commit bf66aa35a75d65c04f527db41dea2d92d57f18b3 by Michail Vourlakos. Committed on 08/08/2019 at 06:46. Pushed by mvourlakos into branch 'v0.9'. update struts when normalThickness value changes --the issue was pretty obvious when the user was using a top view with thickness < 24px. and a bottom view always visible. In that case the top view struts on startup did not decrease below at 24px. M +5-2app/view/visibilitymanager.cpp https://commits.kde.org/latte-dock/bf66aa35a75d65c04f527db41dea2d92d57f18b3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410689] [Regression] Ctrl+Shift+Left/Right doesn't move tabs
https://bugs.kde.org/show_bug.cgi?id=410689 --- Comment #2 from Konstantin Kharlamov --- (In reply to Kurt Hindenburg from comment #1) > This was fixed in 68ea9bf6cc118118e824a661013b4f3438a7728e around Jun 26 so > your version should have it. > > > I have Ctrl+Alt+arrow Hmm, this one works. > have you changed the shortcut? I don't remember doing so, AFAIK it's default hotkey. Either way, when I go to "Setings → Configure Shortcuts", I see "Ctrl+Shift+Left" is set to "Focus Left Terminal". This works in Konsole from my distro repository (19.04.03), but it doesn't in the one built from master when I run it from the build directory. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410642] Reviews are not show
https://bugs.kde.org/show_bug.cgi?id=410642 Tobias Deiminger changed: What|Removed |Added CC||haxti...@posteo.de --- Comment #9 from Tobias Deiminger --- (In reply to Albert Astals Cid from comment #8) > My suggestion is you attach that pdf to the bug trackers of the other pdf > viewers and say "look, it works on Adobe Reader, so it should work for you > too" and see what they say They are aware, see below. Issue happens because the FreeText annotation in the attached PDF has no AP (appearance stream). Firefox uses PDF.js, they have an issue with FreeText without AP: https://github.com/mozilla/pdf.js/issues/6810 Chrome uses PDFium, seems they have issue with FreeText in general: https://bugs.chromium.org/p/pdfium/issues/detail?id=569 Okular, Evince (and Zathura, depending on configuration) use poppler. Poppler displays correctly without AP, but can't store AP when saving the PDF. Adobe displays (copes without AP) and writes (saves AP) correctly. PDF 1.7 says AP is optional. I.e., readers must be able to display the annotation anyway. PDF 2.0 says AP is mandatory. I.e., writers must be able to generate and save AP along with the annotation. So no use in blaming some party, all could do better. Solving is just not that easy and needs an extra portion of spare (or sponsored) time. Now that PDF 2.0 has made AP mandatory, I believe duty has shifted somewhat to poppler side. I'd suggest to close this one and open an issue at poppler side? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410707] A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 Michail Vourlakos changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410703] [Wayland] Standalone plasma-nm KCM freezes after manual resizing
https://bugs.kde.org/show_bug.cgi?id=410703 --- Comment #2 from Jan Grulich --- You can ignore the comment, I tried it myself and I can reproduce it, while other kcms seem to work fine. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410703] [Wayland] Standalone plasma-nm KCM freezes after manual resizing
https://bugs.kde.org/show_bug.cgi?id=410703 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- Does any other standalone KCM freeze on wayland? You can try to open any other with kcmshell5. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 410714] New: clazy-detaching-temporary: Don't warn on detaching pointer values
https://bugs.kde.org/show_bug.cgi?id=410714 Bug ID: 410714 Summary: clazy-detaching-temporary: Don't warn on detaching pointer values Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: markus.haberlander...@gmail.com CC: smart...@kde.org Target Milestone: --- SUMMARY I am currently fixing deprecation warnings for QChart in Qt 5.12. The following link shows the suggested change (Qt examples changed with adding the deprecation message): https://codereview.qt-project.org/c/qt/qtcharts/+/227902/4/examples/charts/scatterinteractions/chartview.cpp Doing this gives me a warning: warning: Don't call QList::first() on temporary [-Wclazy-detaching-temporary] I believe calling QList::first() is no problem here, it only means that a pointer is copied, which is not a problem IMHO. STEPS TO REPRODUCE Run clazy on the Scatter Interactions Sample in Qt 5.12. OBSERVED RESULT Clazy returns clazy-detaching-temporary EXPECTED RESULT Clazy should not return an error here. SOFTWARE/OS VERSIONS Running clazy from QtC 4.9.2, Qt version is 5.12.4. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 350031] [transform-tool] transform tool and switching layer bug
https://bugs.kde.org/show_bug.cgi?id=350031 Ranjith changed: What|Removed |Added CC||ranjithasa...@hotmail.com OS|Linux |MS Windows Version|2.9 |4.2.5 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410707] A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 --- Comment #4 from Mikhail Zolotukhin --- Created attachment 122003 --> https://bugs.kde.org/attachment.cgi?id=122003&action=edit A minimal layout, on which the issue is reproduced I took everything from the panel and the dock, so they are both empty. However if I remove the dock at the bottom completely, there is no gap between the panel and a window. If I add a new standard Dock to the bottom of a screen and restart Latte - the gap is starting to appear again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409639] Kwin crash on suspend system
https://bugs.kde.org/show_bug.cgi?id=409639 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410146] Kwin crashes with too many visual effects
https://bugs.kde.org/show_bug.cgi?id=410146 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409636] Can you add layer clip locking? In ps, you can hold down the ALT key to lock the lower color area, and in medibang, you can also have tabs.
https://bugs.kde.org/show_bug.cgi?id=409636 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.
[kate] [Bug 408760] Kate segfaults when Korean files are open with uim
https://bugs.kde.org/show_bug.cgi?id=408760 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 381821] Wrong value on high ISO settings & fix Exposure value formatting
https://bugs.kde.org/show_bug.cgi?id=381821 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 410679] Can't use Fcitx or Ibus input method in KDE/Qt app
https://bugs.kde.org/show_bug.cgi?id=410679 --- Comment #3 from 20l8kxxl8...@opayq.com --- You can try to find fcitx-frontend-qt5 in Discover. If you can find it and it installs successfully, then you should be able to use fcitx in KDE/ Qt applications. However, if you can find the package but it fails to install (due to dependency problem), then you may have to build the package yourself (refer to the forum post link I posted above). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 410679] Can't use Fcitx or Ibus input method in KDE/Qt app
https://bugs.kde.org/show_bug.cgi?id=410679 --- Comment #2 from 20l8kxxl8...@opayq.com --- This KDE Community Forum post may be useful: https://forum.kde.org/viewtopic.php?f=309&t=154174#p404551 If you have other problems, feel free to ask your questions on forum.kde.org. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #30 from Kishore Gopalakrishnan --- (In reply to davidblunkett from comment #28) > Just ran into this bug - bloody hell it's annoying. It is working fine on a > parallel system (presumably the old token is still valid on that?). > > The bodge to disable kmail's "gmail" authentication by switching from > "imap.gmail.com" to and IP address and using PLAIN authentication has worked > for me but this is a poor fix. > > I can't find any way to switch to PLAIN without nobbling the address which > is really annoying but this should (at least) be an available option. Are you sure about the address thing? I have been able to use it by just switching the authentication to SSL/TLS, port 993, PLAIN (still using imap.gmail.com). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410689] [Regression] Ctrl+Shift+Left/Right doesn't move tabs
https://bugs.kde.org/show_bug.cgi?id=410689 --- Comment #1 from Kurt Hindenburg --- This was fixed in 68ea9bf6cc118118e824a661013b4f3438a7728e around Jun 26 so your version should have it. I have Ctrl+Alt+arrow - have you changed the shortcut? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410711] in-window search window display OBFUSCATES active display.
https://bugs.kde.org/show_bug.cgi?id=410711 --- Comment #2 from pgnd --- noted. given a choice, "I" would prefer the old, in-tabbar location. I do understand that there are code/design decisions that make that a *bad* choice, at least going forward. that said, 'me too' on the movable/transparent/etc wish. thx! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410711] in-window search window display OBFUSCATES active display.
https://bugs.kde.org/show_bug.cgi?id=410711 --- Comment #1 from Kurt Hindenburg --- Yes, that's the expected behavior ATM - there's a wish to have it movable and/or transparent. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #53 from Aaron Lavarnway --- Aha, I found the issue. Nvidia had vertical sync forced on, which added significant drawing/panning delay. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #52 from Aaron Lavarnway --- On the most recent nightly build (and the most recent test build you've given me), it's fixed. But I think It also applies some sort of smoothing/stabilization to the pen in general. Including brushes, even if stabilization is set off. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 410699] The Autofocus V-curve looks weird
https://bugs.kde.org/show_bug.cgi?id=410699 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 400222] Ekos eating ram.
https://bugs.kde.org/show_bug.cgi?id=400222 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |NEEDSINFO --- Comment #2 from Jasem Mutlaq --- Please check with KStars 3.3.4 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398744] Possible leak in file descriptors
https://bugs.kde.org/show_bug.cgi?id=398744 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #9 from Jasem Mutlaq --- Cannot be reproduced with 3.3.4. Please reopen if you can reproduce it reliably. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405476] Saving the Ekos settings
https://bugs.kde.org/show_bug.cgi?id=405476 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO Version Fixed In||3.3.4 --- Comment #6 from Jasem Mutlaq --- Please check 3.3.4 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405900] Scheduler : no way to pause or abort a schedule
https://bugs.kde.org/show_bug.cgi?id=405900 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #1 from Jasem Mutlaq --- Please check 3.3.4 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 410094] Kstars sometimes fails to wait for a slew to happen before slew is regarded as complete on the mount tool.
https://bugs.kde.org/show_bug.cgi?id=410094 --- Comment #12 from Jasem Mutlaq --- Ok I'm not sure... Is the driver update period 250ms? I see 4 IPS_BUSYs in 1 second. If that is the case, just try to make the period 1 second and see if that makes any difference? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 178320] Konsole split view: in both views same content
https://bugs.kde.org/show_bug.cgi?id=178320 --- Comment #49 from Shmerl --- Is this included in 19.04.3? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 410227] stars 3.3.2 crashes on startup
https://bugs.kde.org/show_bug.cgi?id=410227 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #2 from Jasem Mutlaq --- Please check 3.3.4 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 409880] Kstars 3.3.2 crashes viewing histogram
https://bugs.kde.org/show_bug.cgi?id=409880 Jasem Mutlaq changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Jasem Mutlaq --- Please check KStars 3.3.4 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 409648] KStars crashes intermitently while executing capture sequence on Ekos
https://bugs.kde.org/show_bug.cgi?id=409648 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Jasem Mutlaq --- Please check 3.3.4. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 406446] Ekos fails to recognise Astrometry index files
https://bugs.kde.org/show_bug.cgi?id=406446 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||3.3.4 --- Comment #3 from Jasem Mutlaq --- Issue found and fixed. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 410713] New: Marble crashed whilst trying to view KML track
https://bugs.kde.org/show_bug.cgi?id=410713 Bug ID: 410713 Summary: Marble crashed whilst trying to view KML track Product: marble Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: ho...@spliced.me.uk Target Milestone: --- Application: marble (2.2.20 (2.3 development version)) Qt Version: 5.9.4 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.58-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: trying to get Elevation Profile plug-in to work for loaded track The crash can be reproduced every time. -- Backtrace: Application: Marble Virtual Globe (marble), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2fdbff5940 (LWP 12490))] Thread 8 (Thread 0x7f2f54ff9700 (LWP 12868)): #0 0x7f2fd7308ba8 in read () from /lib64/libc.so.6 #1 0x7f2fce162a50 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2fce11dc38 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2fce11e0d0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f2fce11e23c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2fd7e54c1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f2fd7dfd09a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f2fd7c2c4da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f2fd7c310ce in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f2fd0c5f569 in start_thread () from /lib64/libpthread.so.0 #10 0x7f2fd731785f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f2f4f7fe700 (LWP 12532)): #0 0x7f2fd0c658ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2fd78aeb4c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib64/libstdc++.so.6 #2 0x7f2fd43f5e09 in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f2fd43f4b10 in ?? () from /usr/lib64/libQt5WebKit.so.5 #4 0x7f2fd43f8de8 in ?? () from /usr/lib64/libQt5WebKit.so.5 #5 0x7f2fd442b4aa in ?? () from /usr/lib64/libQt5WebKit.so.5 #6 0x7f2fd0c5f569 in start_thread () from /lib64/libpthread.so.0 #7 0x7f2fd731785f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f2f577fe700 (LWP 12531)): #0 0x7f2fd0c658ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2fd78aeb4c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib64/libstdc++.so.6 #2 0x7f2fd43f5e09 in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f2fd43f4b10 in ?? () from /usr/lib64/libQt5WebKit.so.5 #4 0x7f2fd43f8de8 in ?? () from /usr/lib64/libQt5WebKit.so.5 #5 0x7f2fd442b4aa in ?? () from /usr/lib64/libQt5WebKit.so.5 #6 0x7f2fd0c5f569 in start_thread () from /lib64/libpthread.so.0 #7 0x7f2fd731785f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f2f557fa700 (LWP 12530)): #0 0x7f2fd0c658ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2fd78aeb4c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib64/libstdc++.so.6 #2 0x7f2fd43f5e09 in WTF::ParkingLot::parkConditionally(void const*, std::function, std::function, std::chrono::time_point > >) () from /usr/lib64/libQt5WebKit.so.5 #3 0x7f2fd43f4b10 in ?? () from /usr/lib64/libQt5WebKit.so.5 #4 0x7f2fd43f8de8 in ?? () from /usr/lib64/libQt5WebKit.so.5 #5 0x7f2fd442b4aa in ?? () from /usr/lib64/libQt5WebKit.so.5 #6 0x7f2fd0c5f569 in start_thread () from /lib64/libpthread.so.0 #7 0x7f2fd731785f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f2fb6dee700 (LWP 12494)): #0 0x7f2fd730d0bb in poll () from /lib64/libc.so.6 #1 0x7f2fce11e129 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2fce11e23c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2fd7e54c1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f2fd7dfd09a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f2fd7c2c4da in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f2fd7c310ce in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f2fd0c5f569 in start_thread () from /lib64/libpthread.so.0 #8 0x7f2fd731785f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f2fb7fff700 (LWP 12493)): #0 0x7f2fd7308ba8 in read () from /lib64/libc.so.6 #1 0x7f2fce162a50 in ?? () from /usr/lib64/libglib-2.0.so.0 #2
[kmymoney] [Bug 410688] Password problem with database SQLCipher
https://bugs.kde.org/show_bug.cgi?id=410688 --- Comment #1 from Jack --- Can you try opening the file (on either system) with a command line tool, to see if you can get any more detailed error messages? I assume you can repeatedly open each file on the system where it was created? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 410712] New: sudo systemsettings5 crashes from cli
https://bugs.kde.org/show_bug.cgi?id=410712 Bug ID: 410712 Summary: sudo systemsettings5 crashes from cli Product: systemsettings Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: d...@northcreek.ca Target Milestone: --- Application: systemsettings5 (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-55-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: >From terminal: sudo systemsettings5 - Custom settings of the application: sudo I previously tried to change the printer from color to grayscale, it wants a root user to confirm, and I have no idea what the root password is because I use sudo. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f56c2fcb800 (LWP 6521))] Thread 4 (Thread 0x7f56a4c27700 (LWP 6534)): #0 0x7f56b88ca664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f56b8883b18 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f56b88844fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f56b88846dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f56bf36a90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f56bf30f9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f56bf12e22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f56bcc836f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f56bf13316d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f56babd56db in start_thread (arg=0x7f56a4c27700) at pthread_create.c:463 #10 0x7f56bea2e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f56943b2700 (LWP 6533)): #0 0x7f56bea21bf9 in __GI___poll (fds=0x7f568c004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f56b88845c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f56b88846dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f56bf36a90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f56bf30f9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f56bf12e22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f56bcc836f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f56bf13316d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f56babd56db in start_thread (arg=0x7f56943b2700) at pthread_create.c:463 #9 0x7f56bea2e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f56ae3ee700 (LWP 6523)): #0 0x7f56bea21bf9 in __GI___poll (fds=0x7f56a0004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f56b88845c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f56b88846dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f56bf36a90b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f56bf30f9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f56bf12e22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f56c0c74d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f56bf13316d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f56babd56db in start_thread (arg=0x7f56ae3ee700) at pthread_create.c:463 #9 0x7f56bea2e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f56c2fcb800 (LWP 6521)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #5 0x7f56be94d801 in __GI_abort () at abort.c:79 #6 0x7f56bf11dfa7 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f56bd8039f0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #8 0x7f56bd803d5a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #9 0x7f56bd805f8e in QQuickWidget::resizeEvent(QResizeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #10 0x7f56c0360be2 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f56bd806
[kate] [Bug 410446] "Append newline at the end of file on save" option does not work
https://bugs.kde.org/show_bug.cgi?id=410446 --- Comment #3 from Eugene Shalygin --- Why do you think this behaviour is not confusing for a plain-text editor? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 410696] No thumbnails generated for cb7 comic book archives
https://bugs.kde.org/show_bug.cgi?id=410696 --- Comment #3 from riddervancoca...@hotmail.com --- (In reply to Nate Graham from comment #1) > Can you attach one such file for testing purposes? Done! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 410696] No thumbnails generated for cb7 comic book archives
https://bugs.kde.org/show_bug.cgi?id=410696 --- Comment #2 from riddervancoca...@hotmail.com --- Created attachment 122002 --> https://bugs.kde.org/attachment.cgi?id=122002&action=edit A cb7 file for testing. The images and text that it contains are out of copyright. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410707] A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 --- Comment #3 from Michail Vourlakos --- Send your layout file, the one you observe the issue -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410707] A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 Michail Vourlakos changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410707] A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 --- Comment #2 from Mikhail Zolotukhin --- (In reply to Michail Vourlakos from comment #1) > Your plasma theme is faulty. Change to another plasma theme. My Workspace theme is default Breeze shipped with Plasma. I haven't made any modifications to it. I tried Arc Dark theme too, but a gap appears anyway. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 410708] New icons for KTimeTracker
https://bugs.kde.org/show_bug.cgi?id=410708 --- Comment #1 from Alexander Potashev --- > The current animation has low FPS (1 FPS), thus I need to look at the tray > icon for a whole second just to check if ... ... to check if a task timer is running. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410711] New: in-window search window display OBFUSCATES active display.
https://bugs.kde.org/show_bug.cgi?id=410711 Bug ID: 410711 Summary: in-window search window display OBFUSCATES active display. Product: konsole Version: 19.07.80 Platform: Other URL: https://i.imgur.com/006gCew.png OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: pgnet@gmail.com Target Milestone: --- Flags: Usability+ KDE's UI changed, a while ago now, to no longer display the search bar in the TABBAR, out of konsole content context, to IN-WINDOW. This OBFUSCATES active text in the window, e.g. https://i.imgur.com/006gCew.png , requiring you repeatedly WORKAROUND by either DISABLE/HIDE the search window, of scroll-past it to a 'clear' prompt. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392607] Crash sometimes when applying Tags to images
https://bugs.kde.org/show_bug.cgi?id=392607 --- Comment #19 from meku --- (In reply to caulier.gilles from comment #18) > Meku do you see my comment #16 ? > > Best > > Gilles Caulier Sorry I have not begun using 6.2.0 yet. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410710] Make Kdevelop usable for professional use
https://bugs.kde.org/show_bug.cgi?id=410710 Christoph Feck changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Christoph Feck --- Since you reported the issues separately, I fail to see the need for this ticket. Could you please clarify why it is needed? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410710] Make Kdevelop usable for professional use
https://bugs.kde.org/show_bug.cgi?id=410710 jd.fratt...@free.fr changed: What|Removed |Added CC||jd.fratt...@free.fr -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410710] New: Make Kdevelop usable for professional use
https://bugs.kde.org/show_bug.cgi?id=410710 Bug ID: 410710 Summary: Make Kdevelop usable for professional use Product: kdevelop Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: jd.fratt...@free.fr Target Milestone: --- Please make Kdevelop usable for profesional use by removing most of its inconveniences (hangs, code not recognized, bad makefile recognition...). Kdevelop is good but could become great. I have been using Kdevelop since its 0.8 version but recently had to switch to something else due to many features not working properly (see for example my other reported bugs). With Visual Studio Code, Gnome Builder and other alternatives this would become very sad if Kdevelop will slowly dying because it is one of the most promising IDEs, which provides good functionalities. So please make Kdevelop more strong and focused on it being robust for the next releases. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 410704] Shortcut to opening a message in a standalone window
https://bugs.kde.org/show_bug.cgi?id=410704 Jan Kundrát changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Jan Kundrát --- Please upgrade to a version from git, this has been implemented by https://gerrit.vesnicky.cesnet.cz/r/891 . Sorry, we haven't had a release in quite some time :(. I'm afraid that using Enter is not directly possible because of a conflict with QAbstractItemView::activated, though. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 410687] KDevelop is listed twice under updates
https://bugs.kde.org/show_bug.cgi?id=410687 --- Comment #4 from Friedrich W. H. Kossebau --- Perhaps related, the kdevelop appdata file so far also missed to feature some . This just got committed to 5.4 branch & merged to master. Though still surprising that menu desktop files are considered over the appdata file description, where the latter should point out this is one single app. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 410705] Trojita: Message that was opened in a standalone window should be marked as read
https://bugs.kde.org/show_bug.cgi?id=410705 Jan Kundrát changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Jan Kundrát --- How exactly do you "hide the message pane"? On my system and with the latest git, the actual portion of the main window which contains a single "opened" message cannot be hidden by resizing because there's a minimal size hint which Qt respects. What Qt style/theme do you use? Which view layout (menu View -> Layout) are you using? What is your Settings -> Automatically mark messages as read? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 410706] Trojita: plain text messages unreadable because of small width
https://bugs.kde.org/show_bug.cgi?id=410706 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 378684 *** -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 378684] Incorrect page width for plain text messages
https://bugs.kde.org/show_bug.cgi?id=378684 Christoph Feck changed: What|Removed |Added CC||ring...@gmail.com --- Comment #14 from Christoph Feck --- *** Bug 410706 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410466] Drag and dropping text from Kate into konsole does not paste text into Konsole
https://bugs.kde.org/show_bug.cgi?id=410466 pgnd changed: What|Removed |Added Version|19.04.3 |19.07.80 Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"
https://bugs.kde.org/show_bug.cgi?id=410355 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"
https://bugs.kde.org/show_bug.cgi?id=410355 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED Ever confirmed|1 |0 --- Comment #15 from Nate Graham --- (In reply to vialav from comment #14) > I've just tested the patch and it has fixed my issue. Thank you for your > coding. Excellent! Of note, the bug can't be closed yet because the patch hasn't actually gotten merged. Since you've tested it and verified that it works, it would be very helpful if you could post a comment on https://phabricator.kde.org/D22993 mentioning this (you can even formally accept). That would help get it merged faster. > I wondered where the stop-looking-for-nonexistent-file branch was planted as > I could not find it on anongit.kde.org, and ended up downloading the raw > diff from D22993. Yep, that was the right way to do it (for now; once we move to GitLab there will be branches you can download). > Compiled with -Wsuggest-override there where some further overall > suggestions, which are unrelated to this issue. Closing it as kindly fixed. Please feel free to submit a patch that fixes those issues! See https://community.kde.org/Infrastructure/Phabricator to learn how. You can just paste a raw diff if you don't want to set up arcanist on your machine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395390] After making the default panel vertically-oriented, Kickoff's layout is messed up until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=395390 --- Comment #27 from Nate Graham --- The patch was submitted on Phabricator: https://phabricator.kde.org/D22988 It's winding its way through the review process now :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410709] Background parser no longer working in KDevelop 5.4.0 using Generic Project Manager (Manager=KDevGenericManager)
https://bugs.kde.org/show_bug.cgi?id=410709 --- Comment #2 from Francis Herne --- To be clear, do projects using other manager plugins work as expected? --- The initial packaging of 5.4 in Neon had a problem with the Clang dependencies which prevented kdev-clang from working at all; that should hopefully have been fixed a few hours ago, so please try updating again and see if it works. If only the Generic manager is affected, something else is probably at fault. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410709] Background parser no longer working in KDevelop 5.4.0 using Generic Project Manager (Manager=KDevGenericManager)
https://bugs.kde.org/show_bug.cgi?id=410709 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||kosse...@kde.org --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for reporting the issue. A similar observation had been told before on the #kdevelop irc channel, and it was found that the KDevelop Neon packages were not build against the desired llvm/clang libraries. A fix should be on the way to Neon users in updated packages already. Please look out for package updates the next days (perhaps already now) and retry. If still not working in a week, please reopen the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 410699] The Autofocus V-curve looks weird
https://bugs.kde.org/show_bug.cgi?id=410699 --- Comment #3 from Jean-Claude --- I tested with real stars and the bug doesn't occur. It only occurs with the simulator. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410707] A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 Michail Vourlakos changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Michail Vourlakos --- Your plasma theme is faulty. Change to another plasma theme. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410693] "Add spacer" button disappeared in new Latte dock version
https://bugs.kde.org/show_bug.cgi?id=410693 --- Comment #2 from radimir.caci...@gmail.com --- Thanks, it worked. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410709] New: Background parser no longer working in KDevelop 5.4.0 using Generic Project Manager (Manager=KDevGenericManager)
https://bugs.kde.org/show_bug.cgi?id=410709 Bug ID: 410709 Summary: Background parser no longer working in KDevelop 5.4.0 using Generic Project Manager (Manager=KDevGenericManager) Product: kdevelop Version: 5.4.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: ricardo@hotmail.com Target Milestone: --- SUMMARY KDevGenericManager in 5.4.0 seems to have broken C++ tools STEPS TO REPRODUCE 1. Upgrade KDevelop from 5.3.3 to 5.4 2. Open any project using the Generic Project Manager OBSERVED RESULT - Background Parser not running - Go-to in a symbol is not working (Ctrl+mouse) - Project → Open Configuration Menu does not show tab to configure compiler flags - C++ integration seems fully disabled 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.
[kget] [Bug 410406] update module 'mirror research' url
https://bugs.kde.org/show_bug.cgi?id=410406 Wolfgang Bauer changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Wolfgang Bauer --- Thank you for reporting that. I'll have a look at removing them tomorrow (hopefully in time for the 19.08 release). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409690] Add option to auto copy screenshot to clipboard
https://bugs.kde.org/show_bug.cgi?id=409690 --- Comment #5 from Vladimir --- Created attachment 122001 --> https://bugs.kde.org/attachment.cgi?id=122001&action=edit KSnip I've switch to Ksnip, it already has the feature I need. Thank you for your time! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 410708] New: New icons for KTimeTracker
https://bugs.kde.org/show_bug.cgi?id=410708 Bug ID: 410708 Summary: New icons for KTimeTracker Product: Breeze Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: aspotas...@gmail.com CC: kain...@gmail.com Target Milestone: --- SUMMARY KTimeTracker uses custom icons from its source code repository ( https://cgit.kde.org/ktimetracker.git/ ). Most of them are raster and too small for modern screens. And none of them match Breeze style. It would be nice to release KTimeTracker 5.0 with modern icons/artwork. I will list and describe each of the icons: 1. pics/active-icon.gif. It used to be 8 raster images, I merged them into this GIF. This is used as tray icon when a task is active (i.e. time tracking is ON at the moment). When no tasks are active, a fixed frame of this GIF is used as tray icon. Drawbacks: - Raster image, should be an SVG - The colors do not match modern icon themes, should be a Breeze icon - Animated. In my opinion, constantly running animation might distract users. However I have no good ideas on how to tell the user that a task is active without using animation, may be add a red dot on top of normal icon - the one that is commonly understood as "recording"/LIVE. - The current animation has low FPS (1 FPS), thus I need to look at the tray icon for a whole second just to check if . If we choose to continue using animation, it should be made smooth, I can for example animate a clock face overlay programmatically at a higher FPS. 2. pics/watch.gif. Used in list view the the application window when a task is active. It's mostly good, but is a raster one as well, might look pixelated on high resolution screens. Low FPS of animation is not that big of a problem here because if you need an icon is list view, then the respective task is obviously active (otherwise the watch.gif icon is hidden). 3. empty-watch.xpm. Just an empty image. Placeholder for when watch.gif is not used in the list view. 4. task-incomplete.xpm, task-complete.xpm. Has two uses: - Icons for actions "Mark as Complete" / "Mark as Incomplete" - Task completion indicator in the list view. If progress of a task is at 100%, then "task-complete" is used. Otherwise, "task-incomplete" is used. The indicator is clickable: it toggles task completion (sets task progress to 100% or to 0%, depending on the previous state). Both of these are raster images and do not match the Breeze icon theme, this is not good for display in menu items and/or on toolbar. May be the task completion indicator in list view should use a different icons, they don't have to be the same with the action items. And we probably don't really need that clickable behaviour of the indicator, it's a quite obscure and hacky feature anyway, may be at least replace it with a regular checkbox. 5. icons/*-actions-subtask-new-ktimetracker. This icon does not match Breeze theme. It is used for the "Add Subtask..." action. A similar action "Add Task" (adds top-level task) uses the standard icon "document-new" which is already present in Breeze themes. 6. icons/*-apps-ktimetracker. Application icon. Looks good to me, however you might say it looks old. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410642] Reviews are not show
https://bugs.kde.org/show_bug.cgi?id=410642 --- Comment #8 from Albert Astals Cid --- (In reply to tutonis from comment #7) > Is it officially declared as gold standard? It's the implementation of the guys that wrote the spec, so kind of yes. > I do not have (right now) technical knowledge needed to debg this issue - my > contribution was to document the issue and do testing or other non technical > work. My suggestion is you attach that pdf to the bug trackers of the other pdf viewers and say "look, it works on Adobe Reader, so it should work for you too" and see what they say -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410642] Reviews are not show
https://bugs.kde.org/show_bug.cgi?id=410642 --- Comment #7 from tuto...@gmail.com --- I do not understand how adobe reader is relevant here? Is it officially declared as gold standard? More over it is the only one of many viewers which shows 100% of annotations as okular. I do not have (right now) technical knowledge needed to debg this issue - my contribution was to document the issue and do testing or other non technical work. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 409220] Discover says "Check Connectivity" instead of displaying content with AppStream 0.12.7
https://bugs.kde.org/show_bug.cgi?id=409220 --- Comment #23 from Wolfgang Bauer --- (In reply to Frank Kruger from comment #21) > The issue is solved for me with the fix discussed here: > https://github.com/ximion/appstream/issues/243. I don't think this fixes anything in regards to *this* bug. FWIW, I just noticed this error message today, with openSUSE's AppStream 0.12.7 package that includes that fix. Running "appstreamcli refresh" manually made it go away. No idea where the problem lies though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395390] After making the default panel vertically-oriented, Kickoff's layout is messed up until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=395390 --- Comment #26 from Piotr Mierzwinski --- I can confirm that patch works. I mean that issue I reported here: Bug 396583 just disappeared. I followed for instruction placed here: https://gitlab.com/snippets/1882509 BTW. There is also thread on reddit mentioning about this issue: https://www.reddit.com/r/kde/comments/cm8bef/i_forked_kickoff_and_made_favorites_display_in_a/ -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 410655] Suggests to use Q_ENUM when you can't use it
https://bugs.kde.org/show_bug.cgi?id=410655 --- Comment #1 from Albert Astals Cid --- On the other hand since Q_ENUMS(Status); there actually does nothing, i guess what it should say is "your code is terrible, remove that Q_ENUMS or move it inside a QObject" :D -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410642] Reviews are not show
https://bugs.kde.org/show_bug.cgi?id=410642 --- Comment #6 from Albert Astals Cid --- So you don't know if it's a bug. Unless you can prove we're doing it wrong i'll say we're doing it right if Adobe Reader shows the things we create. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410707] New: A gap between a panel and a maximized window appears on an application startup
https://bugs.kde.org/show_bug.cgi?id=410707 Bug ID: 410707 Summary: A gap between a panel and a maximized window appears on an application startup Product: lattedock Version: 0.9.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: zom...@protonmail.com Target Milestone: --- Created attachment 122000 --> https://bugs.kde.org/attachment.cgi?id=122000&action=edit The gap between the panel and the maximized window SUMMARY Creating a panel that is less than 24px and has disabled thickness margins results in gaps appearing on Latte startup. STEPS TO REPRODUCE 1. Create Latte Panel 2. Make its height less than 24px 3. Disable thickness margins 4. Restart Latte 5. Maximize window OBSERVED RESULT There is a gap between the panel and the maximized window, as if the panel occupies that empty space. EXPECTED RESULT There is no gap between the panel and the maximized window, the panel has the height that was set in the settings. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION The gap disappears after opening panel settings and then closing them. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 410685] Make Ctrl+W shortcut work in Ctrl+Tab list
https://bugs.kde.org/show_bug.cgi?id=410685 --- Comment #2 from Dominik Haumann --- Good idea. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 410706] New: Trojita: plain text messages unreadable because of small width
https://bugs.kde.org/show_bug.cgi?id=410706 Bug ID: 410706 Summary: Trojita: plain text messages unreadable because of small width Product: trojita Version: 0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: ring...@gmail.com Target Milestone: --- SUMMARY Plain text messages are impossible to read because they are displayed as a column of text of width 2-3 characters. It consistently happens both in message pane and standalone windows. STEPS TO REPRODUCE 1. Receive a plain text message 2. Select it in Inbox 3. Look at the message pane OBSERVED RESULT Unreadable long column of width 2-3 characters EXPECTED RESULT Text wrapping should happen on window border. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Lubuntu 18.10, LXQT 0.13.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION The display resolution is 1024 x 600, if that matters. Opening the message in a standalone window does not help. A link to particular plain text message as an example: https://groups.google.com/forum/#!original/racket-users/hWF4QU2Rnbg/BU1RfMfeEgAJ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410355] inotify_add_watch("~/.dropbox/aggregation.dbx") failed: "No such file or directory"
https://bugs.kde.org/show_bug.cgi?id=410355 vialav changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #14 from vialav --- I've just tested the patch and it has fixed my issue. Thank you for your coding. I wondered where the stop-looking-for-nonexistent-file branch was planted as I could not find it on anongit.kde.org, and ended up downloading the raw diff from D22993. Compiled with -Wsuggest-override there where some further overall suggestions, which are unrelated to this issue. Closing it as kindly fixed. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 410705] New: Trojita: Message that was opened in a standalone window should be marked as read
https://bugs.kde.org/show_bug.cgi?id=410705 Bug ID: 410705 Summary: Trojita: Message that was opened in a standalone window should be marked as read Product: trojita Version: 0.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: ring...@gmail.com Target Milestone: --- SUMMARY When the message pane is hidden, opening the message in a standalone window should result in this message being marked as read. It does not happen. STEPS TO REPRODUCE 1. Hide the message pane 2. Select an unread message in the Inbox and open it in a standalone window 3. Close the standalone window OBSERVED RESULT Message is still marked as unread in the Inbox EXPECTED RESULT Message should be marked as read SOFTWARE/OS VERSIONS Linux/KDE Plasma: Lubuntu 18.10 / LXQT 0.13.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410657] Digikam 6.2 bad sorting
https://bugs.kde.org/show_bug.cgi?id=410657 --- Comment #6 from Maik Qualmann --- The option "Update file timestamp when files are modified" can be found in the metadata settings. The text changed a bit yesterday and is now: "Update file modification timestamp when files are modified" It is quite normal, if you change a file, that then the file modification date contains the current date. The sorting would change so constantly. So you can disable this update, digiKam changes it back to the previous date after each file change. This is basically bad for backup programs they may not recognize that the file has changed (read the What's Help). Since the last version, we also monitor the modification date of sidecar to respond to external changes. Now only if the upper option is activated. I hope I've described something understandable... Maik -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 410704] New: Shortcut to opening a message in a standalone window
https://bugs.kde.org/show_bug.cgi?id=410704 Bug ID: 410704 Summary: Shortcut to opening a message in a standalone window Product: trojita Version: 0.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: ring...@gmail.com Target Milestone: --- SUMMARY It is essential to be able to open a message in a standalone window without using the mouse. The most obvious key for that would be the Enter key, but it does not work. There is also no "open message in a standalone window" option or anything like that in IMAP->Configure Shortcuts (however, surprisingly, "Close Standalonw Message Window" is there). STEPS TO REPRODUCE 1. Hide the message pane for better experience of the problem 2. Navigate through inbox with keyboard 3. Press Enter on a chosen message OBSERVED RESULT Nothing EXPECTED RESULT The message should open in a standalone window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Lubuntu 18.10 Qt Version: 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410703] New: [Wayland] Standalone plasma-nm KCM freezes after manual resizing
https://bugs.kde.org/show_bug.cgi?id=410703 Bug ID: 410703 Summary: [Wayland] Standalone plasma-nm KCM freezes after manual resizing Product: plasma-nm Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kcm Assignee: jgrul...@redhat.com Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. right click on the network icon in systray 2. select "Configure network connections..." 3. resize horizontally the plasma-nm KCM by dragging its border 4. click on any part of the KCM OBSERVED RESULT KCM freezes - window decoration says "Not responding..." EXPECTED RESULT KCM never freezes SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.3 Thread 5 (Thread 0x7fb4405c4700 (LWP 10128)): #0 0x7fb47519bd37 in __libc_sendmsg (fd=3, msg=msg@entry=0x7fb4405c3530, flags=flags@entry=16448) at ../sysdeps/unix/sysv/linux/sendmsg.c:28 #1 0x7fb4649ed41d in wl_connection_flush (connection=0x563ef86b1d60) at ../src/connection.c:315 #2 0x7fb4649ed5ef in wl_connection_flush (connection=) at ../src/connection.c:297 #3 0x7fb4649ecc38 in wl_display_flush (display=display@entry=0x563ef86ad900) at ../src/wayland-client.c:1986 #4 0x7fb4649eccd6 in wl_display_dispatch_queue (display=0x563ef86ad900, queue=0x7fb438004b50) at ../src/wayland-client.c:1765 #5 0x7fb4649ecf4b in wl_display_roundtrip_queue (display=0x563ef86ad900, queue=0x7fb438004b50) at ../src/wayland-client.c:1238 #6 0x7fb45746be21 in ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #7 0x7fb45746c11d in ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #8 0x7fb45746c1d4 in ?? () from /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0 #9 0x7fb4551e0ae6 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #10 0x7fb4551e0ed5 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #11 0x7fb4551dc28d in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #12 0x7fb470e1e848 in QSGBatchRenderer::Renderer::renderBatches (this=this@entry=0x7fb438010250) at scenegraph/coreapi/qsgbatchrenderer.cpp:2517 #13 0x7fb470e24056 in QSGBatchRenderer::Renderer::render (this=) at scenegraph/coreapi/qsgbatchrenderer.cpp:2735 #14 0x7fb470e14810 in QSGRenderer::renderScene (this=0x7fb438010250, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:244 #15 0x7fb470e14cbb in QSGRenderer::renderScene (this=, fboId=) at scenegraph/coreapi/qsgrenderer.cpp:197 #16 0x7fb470e51830 in QSGDefaultRenderContext::renderNextFrame (this=0x563ef8900aa0, renderer=0x7fb438010250, fboId=) at scenegraph/qsgdefaultrendercontext.cpp:182 #17 0x7fb470eb3a18 in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x563ef871d7c0, size=...) at items/qquickwindow.cpp:486 #18 0x7fb470e5ce92 in QSGRenderThread::syncAndRender (this=this@entry=0x563ef8f7a470) at scenegraph/qsgthreadedrenderloop.cpp:646 #19 0x7fb470e60ae8 in QSGRenderThread::run (this=0x563ef8f7a470) at scenegraph/qsgthreadedrenderloop.cpp:730 #20 0x7fb471eacc72 in QThreadPrivate::start (arg=0x563ef8f7a470) at thread/qthread_unix.cpp:361 #21 0x7fb46ea4c6db in start_thread (arg=0x7fb4405c4700) at pthread_create.c:463 #22 0x7fb47519a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fb453670700 (LWP 10126)): #0 0x7fb47518dbf9 in __GI___poll (fds=0x7fb444003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb46bfb75c9 in g_main_context_poll (priority=, n_fds=1, fds=0x7fb444003ce0, timeout=, context=0x7fb444000bf0) at ../../../../glib/gmain.c:4203 #2 g_main_context_iterate (context=context@entry=0x7fb444000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3897 #3 0x7fb46bfb76dc in g_main_context_iteration (context=0x7fb444000bf0, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3963 #4 0x7fb4720e2daf in QEventDispatcherGlib::processEvents (this=0x7fb444000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #5 0x7fb47208403a in QEventLoop::exec (this=this@entry=0x7fb45366fd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fb471eab4ca in QThread::exec (this=this@entry=0x563ef8907800) at thread/qthread.cpp:531 #7 0x7fb470915115 in QQmlThreadPrivate::run (this=0x563ef8907800) at qml/ftw/qqmlthread.cpp:148 #8 0x7fb471eacc72 in QThreadPrivate::start (arg=0x563ef8907800) at thread/qthread_unix.cpp:361 #9 0x7fb46ea4c6db in start_thread (arg=0x7fb453670700) at pthread_create.c:463 #10 0x7fb47519a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fb453e71700 (LWP 10125)
[digikam] [Bug 410657] Digikam 6.2 bad sorting
https://bugs.kde.org/show_bug.cgi?id=410657 --- Comment #5 from maderios --- I rebuilt DK, sorting works normally now, thanks, but i don't understand some things: > respect the option "Update file timestamp when files are modified" > when changes are made in sidecars. I did not find this option in settings, i didn't change anything in settings but, it works... My digikamrc [Metadata Settings] Clear Metadata If Rescan=true Custom Sidecar Extensions= EXIF Rotate=false EXIF Set Orientation=false Metadata Writing Mode=1 Rescan File If Modified=true Rotate By Internal Flag=true Rotate By Metadata Flag=false Rotate Contents Lossless=true Rotate Contents Lossy=false Save Color Label=false Save Date Time=false Save EXIF Comments=false Save FaceTags=false Save Pick Label=false Save Rating=false Save Tags=true Save Template=false Update File Timestamp=false Use Lazy Synchronization=false Use XMP Sidecar For Reading=true Write Metadata To RAW Files=false Write RAW Files=false > If external changes in sidecars are to be detected, > this option must be activated. > A change requires a re-read of the metadata or a > restart to perform the initial scan. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 410687] KDevelop is listed twice under updates
https://bugs.kde.org/show_bug.cgi?id=410687 Nate Graham changed: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |lei...@leinir.dk Product|kdevelop|Discover Version|5.4.0 |5.16.4 Component|general |discover --- Comment #3 from Nate Graham --- Ah, I see, it's actually that KDevelop ships two .desktop files: org.kde.kdevelop.desktop and org.kde.kdevelop_ps.desktop. kdevelop_ps.desktop is the one that provides the "KDevelop (Pick Session)" string. At this point I'm unsure if the issue is caused by KDevelop providing these files in an odd way, or if Discover is parsing and displaying the information incorrectly. Aleix, any ideas? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410687] KDevelop is listed twice under updates
https://bugs.kde.org/show_bug.cgi?id=410687 Friedrich W. H. Kossebau changed: What|Removed |Added CC||kosse...@kde.org --- Comment #2 from Friedrich W. H. Kossebau --- Nate, what do you mean by "two of the KDevelop packages have AppStream Data"? This leaves one puzzled what to do. There is only one kdevelop appdata file: https://cgit.kde.org/kdevelop.git/tree/org.kde.kdevelop.appdata.xml Any other appdata files (actually metainfo,xml files) are part of kdev-python & kdev-php respective. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 410642] Reviews are not show
https://bugs.kde.org/show_bug.cgi?id=410642 --- Comment #5 from tuto...@gmail.com --- I am not familiar with pdf standard but I do imagine the analogy to html should stand - user/program can craft non conformant html markup code and browsers choose to show it correctly or error out. In this situation there are multiple viewers showing different results - this does seem that annotations could be "crafted" better or that most pdf viewers are meh on standards. In that case is there any combination where annotation is shown correctly in all viewers? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 410689] [Regression] Ctrl+Shift+Left/Right doesn't move tabs
https://bugs.kde.org/show_bug.cgi?id=410689 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410687] KDevelop is listed twice under updates
https://bugs.kde.org/show_bug.cgi?id=410687 Nate Graham changed: What|Removed |Added Version|5.16.4 |5.4.0 Component|discover|general Product|Discover|kdevelop CC||n...@kde.org Assignee|lei...@leinir.dk|kdevelop-bugs-n...@kde.org --- Comment #1 from Nate Graham --- As you can see, technically they're different entries, not duplicates. What's going on here two of the KDevelop packages have AppStream Data (which is used to identify something as an app). Instead, only one should. Moving to KDevelop. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 410682] Plasma Add-On Installer deletes plasmoids/ folder entirely when uninstalling a widget if the widget's folder is not present
https://bugs.kde.org/show_bug.cgi?id=410682 Nate Graham changed: What|Removed |Added Severity|normal |critical CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 410685] Make Ctrl+W shortcut work in Ctrl+Tab list
https://bugs.kde.org/show_bug.cgi?id=410685 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- +1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 410685] Make Ctrl+W shortcut work in Ctrl+Tab list
https://bugs.kde.org/show_bug.cgi?id=410685 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 410680] baloo doesn't index words far down in HTML documents
https://bugs.kde.org/show_bug.cgi?id=410680 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 410701] kglobalaccel5 takes all CPU when plugging USB keyboard
https://bugs.kde.org/show_bug.cgi?id=410701 Malte changed: What|Removed |Added Version|unspecified |5.16.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410676] Menu icon used in window decorations doesn't follow icon theme
https://bugs.kde.org/show_bug.cgi?id=410676 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #3 from Nate Graham --- Same issue and root cause as Bug 351055. *** This bug has been marked as a duplicate of bug 351055 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351055] Icons are upscaled in "Large Icons" Task Switcher because KWin gets icons from the window rather than the window's application's desktop file
https://bugs.kde.org/show_bug.cgi?id=351055 Nate Graham changed: What|Removed |Added CC||quwenruo.bt...@gmx.com --- Comment #55 from Nate Graham --- *** Bug 410676 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz
https://bugs.kde.org/show_bug.cgi?id=395632 --- Comment #47 from Kailash --- And yes, I am ready to do whatever I can to help you, testing wise :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395632] On RX Vega 64, KDE compositor does not run at 144Hz even though monitor refresh rate is set to 144Hz
https://bugs.kde.org/show_bug.cgi?id=395632 --- Comment #46 from Kailash --- > > This issue isn't RX Vega 64 specific it seems. On my laptop with Intel graphics, Painting blocks on vertical retrace is also returning No. > > Does this mean you noticed low refresh rates on a laptop with high refresh > rate display and Intel graphics as well? I can confirm my laptop has this issue (Inspiron 7559) as well, framerate doesn't change with refresh rate changes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409378] Title bar too large, when the title contains an unicode star
https://bugs.kde.org/show_bug.cgi?id=409378 --- Comment #5 from Alexander Schier --- What does this mean for this bug? I experience the behaviour in the KWin title bar and as a user I would like to have it fixed. Did you report it to upstream or what is the correct upstream to report it to? I guess the best course of action would be, when you work with the upstream, as I already see an upstream bug closed as "Wontfix: KDE issue, ask the KDE project". -- You are receiving this mail because: You are watching all bug changes.
