[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 Martin Flöser changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.14.5 Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/0f489c3521eb5f19459b42109 ||11548237e0655b6 --- Comment #9 from Martin Flöser --- Git commit 0f489c3521eb5f19459b4210911548237e0655b6 by Martin Flöser. Committed on 05/01/2019 at 07:57. Pushed by graesslin into branch 'Plasma/5.14'. [platforms/x11/standalone] Pass kxkbconfig to Xkb prior to reconfigure Summary: This ensures that KWin gets the same keyboard layout config as is configured in the session and not a default config. FIXED-IN: 5.14.5 Test Plan: Xephyr to verify the config is applied, otherwise completely untested. I don't have an X session. Reviewers: #kwin Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D17967 M +1-0plugins/platforms/x11/standalone/x11_platform.cpp https://commits.kde.org/kwin/0f489c3521eb5f19459b4210911548237e0655b6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402871] Import: Show message when no new files are available and the "New files" filter is active
https://bugs.kde.org/show_bug.cgi?id=402871 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Severity|normal |wishlist --- Comment #1 from Maik Qualmann --- DigiKam is not Dolphin, but Dolphin does not show also a message, that there is nothing to see. DigiKam shows the hint "0 files" like Dolphin bottom left. If data is still being read this is visible on the animated digiKam logo. Maik -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402781] Redo the cache used to process indirect branch targets
https://bugs.kde.org/show_bug.cgi?id=402781
Julian Seward changed:
What|Removed |Added
Attachment #117251|0 |1
is obsolete||
--- Comment #2 from Julian Seward ---
Created attachment 117291
--> https://bugs.kde.org/attachment.cgi?id=117291=edit
Revised WIP patch
A more suitable baseline patch to use as a starting point to implement the
non {x86,amd64}-linux versions of VG_(disp_cp_xindir).
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 399613] user-trash should not look like a folder at large sizes
https://bugs.kde.org/show_bug.cgi?id=399613 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.
[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 --- Comment #8 from Martin Flöser --- No, there's no nothing to do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402852] User actions popup is not seen as a popup
https://bugs.kde.org/show_bug.cgi?id=402852 --- Comment #4 from Martin Flöser --- Our ShellClient can access the QWindow to evaluate whether it's a popup. We don't need to go over the Wayland protocol. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput
https://bugs.kde.org/show_bug.cgi?id=383379 Giusy Digital changed: What|Removed |Added CC||kurmi...@libero.it -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 402882] New: Pointing Devices KCM
https://bugs.kde.org/show_bug.cgi?id=402882 Bug ID: 402882 Summary: Pointing Devices KCM Product: Touchpad-KCM Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm Assignee: rajeeshknamb...@gmail.com Reporter: mezin.alexan...@gmail.com Target Milestone: --- A few years ago during GSoC I wrote a new KCM for touchpads/mouses/whatever libinput handles: https://github.com/amezin/pointing-devices-kcm http://amezin.github.io/kde/gsoc/2015/08/12/gsoc-update.html It's still not integrated into Plasma. But people are using it (see comments in https://aur.archlinux.org/packages/kcm-pointing-devices-git/) and even reporting that it works better than old touchpad kcm. Could somebody try to integrate it? It seems that KWin on Wayland has a bit different D-Bus interface than I expected, but otherwise it should just work. I'm not using Plasma anymore so can't even test it -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402065] Fails to properly quit on close
https://bugs.kde.org/show_bug.cgi?id=402065 --- Comment #4 from Nate Graham --- I haven't seen this recently on git master after all your welcome fixes to the fwupd backend BTW. I do still experience it with 5.14.4. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402881] New: Flatpak backend reports 100% progress from start to finish while installing, ruining update progress bars in the UI
https://bugs.kde.org/show_bug.cgi?id=402881 Bug ID: 402881 Summary: Flatpak backend reports 100% progress from start to finish while installing, ruining update progress bars in the UI Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: aleix...@kde.org Reporter: n...@kde.org CC: jgrul...@redhat.com Target Milestone: --- Discover from git master in Neon dev unstable. Installing any Flatpak app from Flathub (I tried several) results in the installation progress bars starting at 100% and not moving. Launching Discover from the CLI reveals the following output while installing: progress 100 progress 100 progress 100 progress 100 progress 100 progress 100 progress 100 progress 100 progress 100 progress 100 It starts at 100 and stays there for the duration of the installation. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 392989] Spacebar should always play/pause irrespective of focus
https://bugs.kde.org/show_bug.cgi?id=392989 Ashwin Dhakaita changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 392989] Spacebar should always play/pause irrespective of focus
https://bugs.kde.org/show_bug.cgi?id=392989 Ashwin Dhakaita changed: What|Removed |Added CC||ashwingpdhaka...@gmail.com Assignee|matthieu_gall...@yahoo.fr |ashwingpdhaka...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402640] Two search entries after install
https://bugs.kde.org/show_bug.cgi?id=402640 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Nate Graham --- Thanks Peter. Aleix, do you know if is this a bug in Flathub or Appstream? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 392835] Kdenlive AppImage does crash with XCB related error on start
https://bugs.kde.org/show_bug.cgi?id=392835 --- Comment #5 from Dirk --- (In reply to Vincent PINON from comment #4) > Do I understand wrong that last reply is that AppImage now works on your > system? > Can we close this bug? I can confirm the startup on my system with latest stable AppImage (18.12.0e as of posting this text). Here’s the startup log. $ ./kdenlive-18.12.0e-x86_64.appimage Empty filename passed to function Loading effects from "/tmp/.mount_kdenlin8QvKm/usr/share/kdenlive/effects" Loading effects from "/home/dirk/.local/share/kdenlive/effects" [startup with formats and stuff] ... QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.61' kf5.kservice.sycoca: Parse error in "/home/dirk/.config//menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" applications name: "kdenlive" applications name: "kdenlive" kf5.kservice.sycoca: Parse error in "/home/dirk/.config//menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found applications name: "kdenlive" applications name: "kdenlive" kf5.kservice.sycoca: Parse error in "/home/dirk/.config//menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator" not found -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398239] Filter “Delogo” is not configurable (-1 for all parameters) and has no effect
https://bugs.kde.org/show_bug.cgi?id=398239 --- Comment #5 from Dirk --- (In reply to emohr from comment #4) > Still not working on Refactoring version. Can confirm not working in latest stable AppImage (18.12.0e) and installed version 18.12.0. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396697] Does not open with multi monitor on left screen when panel located right screen
https://bugs.kde.org/show_bug.cgi?id=396697 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-modemmanager-qt] [Bug 349478] Qualcomm 4G modem not recognised - Works under Gnome
https://bugs.kde.org/show_bug.cgi?id=349478 --- Comment #27 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.
[kwayland-integration] [Bug 386926] notifications appearing all over the screen in Plasma with Wayland
https://bugs.kde.org/show_bug.cgi?id=386926 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401294] Latte-dock can not always reset the zoomed launcher
https://bugs.kde.org/show_bug.cgi?id=401294 --- Comment #12 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 402418] Krita 4.1.5 crash wen wacom intuos pen enter in drawing area
https://bugs.kde.org/show_bug.cgi?id=402418 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 392283] Kstars: git://anongit.kde.org/kstars.git
https://bugs.kde.org/show_bug.cgi?id=392283 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 401761] KBibTex changes LaTeX accents
https://bugs.kde.org/show_bug.cgi?id=401761 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 332191] Kget crash after server authenticate cancel
https://bugs.kde.org/show_bug.cgi?id=332191 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #17 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 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 --- Comment #8 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.
[kstars] [Bug 401935] Cooling of ASI stops 1.5C before target temp (ZWO ASI1600MM Pro)
https://bugs.kde.org/show_bug.cgi?id=401935 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402841] Animation curve opacity doesn't display correctly during playback and sometimes during timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=402841 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 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.
[plasmashell] [Bug 402880] New: Filenames on desktop fragmented when using nvidia graphics card.
https://bugs.kde.org/show_bug.cgi?id=402880 Bug ID: 402880 Summary: Filenames on desktop fragmented when using nvidia graphics card. Product: plasmashell Version: 5.14.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: felipepe...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 117290 --> https://bugs.kde.org/attachment.cgi?id=117290=edit Fragmented filenames SUMMARY Filenames on desktop fragmented when using nvidia graphics card. STEPS TO REPRODUCE 1. Start laptop using the dedicated nvidia graphics card. 2. Close the lid to suspend. 3. Open the lid and log back in. OBSERVED RESULT Names of files on the desktop are not readable anymore. EXPECTED RESULT Readable filenames. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.4 Qt Version: 5.11.2 KDE Frameworks Version: 5.53.0 Kernel Version: 4.15.0-43-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 15.6 GiB of RAM Graphics: GeForce 940MX Graphics drivers: Nvidia proprietary 410.48 ADDITIONAL INFORMATION Works fine using the Intel integrated GPU. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401768] [feature] - show app number overlay earlier
https://bugs.kde.org/show_bug.cgi?id=401768 tr...@yandex.com changed: What|Removed |Added CC||tr...@yandex.com --- Comment #3 from tr...@yandex.com --- Is there any way to display shortcut badges while holding the Meta button? Because when users are holding it, that means they arr not remembering what the needed key is, Latte should display badges in that case to guide them. Press Meta+` is a bit inconvenient. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 390744] Parenthesis 2 error
https://bugs.kde.org/show_bug.cgi?id=390744 Robby Stephenson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 399838] Tellico s'est planté
https://bugs.kde.org/show_bug.cgi?id=399838 Robby Stephenson changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 398501] data type of decimal number is missing
https://bugs.kde.org/show_bug.cgi?id=398501 --- Comment #3 from Robby Stephenson --- (In reply to JaGo from comment #2) > I'm using simple text field frequently (e.g. for item denomination - some > denominations are too high) and also for item price. I had an idea of > sorting based on item price and a report with item prices. Simple text > isn't suitable for this purpose. Having a report should work fin with simple text, and using the XSL to manipulate the value into a number. You have to do that with the XML tree anyway. Sorting is a bit trickier. I'd have to think about that - a decimal value wouldn't work with currency symbols, for example. > Is here any option to export only chosen attributes? For a report? Yes, it's a parameter in the XSL. If you use the report XSLT stylesheets stand-alone, for example, you can pass a list of the fields that should be used in the report. See https://forum.kde.org/viewtopic.php?f=200=137533 for an example. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402879] New: [Question] "Behave like a normal dock window" option in next release.
https://bugs.kde.org/show_bug.cgi?id=402879 Bug ID: 402879 Summary: [Question] "Behave like a normal dock window" option in next release. Product: latte-dock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: minhkhoitr...@gmail.com Target Milestone: --- Just wanting to ask if the next release will still have the option to disable "Behave like a normal dock window" (or override-redirect 1) so that latte won't be controlled by the window manager? I have been using this for a long time, and decided to try master but couldn't find the option. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 401894] IMBD Rating not parsed from IMBD website
https://bugs.kde.org/show_bug.cgi?id=401894 Robby Stephenson changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/tel ||lico/509d339f81d05a00e73d03 ||7102db20c56c8db42a Status|REOPENED|RESOLVED Version Fixed In||3.1.5 --- Comment #4 from Robby Stephenson --- Git commit 509d339f81d05a00e73d037102db20c56c8db42a by Robby Stephenson. Committed on 05/01/2019 at 02:01. Pushed by rstephenson into branch '3.1'. Fallback to user's locale for setting IMDB rating The IMDB fetcher assumed the decimal point would always be '.' which is obviously incorrect in many locales. While the IMDB website apparently always uses the period, fall back to using the default locale to convert to a float. FIXED-IN: 3.1.5 M +4-0ChangeLog M +3-0src/fetch/imdbfetcher.cpp M +7-0src/tests/imdbfetchertest.cpp M +1-1src/tests/tellicotest.config https://commits.kde.org/tellico/509d339f81d05a00e73d037102db20c56c8db42a -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 402878] New: Display GPU loads and vRAM in Ksysguard
https://bugs.kde.org/show_bug.cgi?id=402878 Bug ID: 402878 Summary: Display GPU loads and vRAM in Ksysguard Product: ksysguard Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ksthiele+kde...@gmail.com Target Milestone: --- SUMMARY Enhance KsysGuard with GPU stats about vRAM, GPU usage and even temperature maybe in a new Tab called "GPU" or enhance "System load" I think it would be nice to have everything in one place, also AMDGPU doesn't currently have such a control center or something. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402696] eq_SyscallStatus the 'impossible' happened with: unhandled amd64-darwin syscall: mach:50 (tzset)
https://bugs.kde.org/show_bug.cgi?id=402696 Rhys Kidd changed: What|Removed |Added Assignee|josef.weidendor...@gmx.de |rhysk...@gmail.com CC||rhysk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402841] Animation curve opacity doesn't display correctly during playback and sometimes during timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=402841 Tristan Y. changed: What|Removed |Added Attachment #117273|0 |1 is obsolete|| --- Comment #3 from Tristan Y. --- Created attachment 117289 --> https://bugs.kde.org/attachment.cgi?id=117289=edit imgur link to gif -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402841] Animation curve opacity doesn't display correctly during playback and sometimes during timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=402841 --- Comment #2 from Tristan Y. --- (In reply to mvowada from comment #1) > Hi Tristan, > I'm sorry but the attached image is really small (200px) and it's difficult > to see the problem. Please, could you upload another example (4MB limit) or > provide details on what happens and what you would expect? Thanks :) I would've uploaded with a better resolution but the file would go over the limit. I can try to use a better gif and just chop it up into separate pieces -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 402877] New: Majority of activities are missing.
https://bugs.kde.org/show_bug.cgi?id=402877 Bug ID: 402877 Summary: Majority of activities are missing. Product: gcompris Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: nobicy...@vivaldi.net Target Milestone: --- Created attachment 117288 --> https://bugs.kde.org/attachment.cgi?id=117288=edit A category showing only 1 activity SUMMARY In gcompris version 0.95 on Manjaro Linux, the majority of activities are missing. (see screenshot) SOFTWARE/OS VERSIONS Manjaro Linux Qt5 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 401874] KRunner crashes when trying to start Steam
https://bugs.kde.org/show_bug.cgi?id=401874 --- Comment #3 from Dennis Schridde --- *** Bug 402870 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 402870] KRunner crashed when I tried to start Steam
https://bugs.kde.org/show_bug.cgi?id=402870 Dennis Schridde changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Dennis Schridde --- Thread 32 (Thread 0x7fb79affd700 (LWP 9124)): [KCrash Handler] #6 Marble::GeoDataLookAt::range (this=0x0) at /tmp/portage/kde-apps/marble-18.12.0/work/marble-18.12.0/src/lib/marble/geodata/data/GeoDataLookAt.cpp:122 #7 0x7fb7dd9d4c6d in Marble::PlasmaRunner::collectMatches (this=0x558daec83520, matches=..., query=..., folder=) at /usr/include/qt5/QtCore/qlist.h:385 #8 0x7fb7dd9d56b1 in Marble::PlasmaRunner::match (this=0x558daec83520, context=...) at /tmp/portage/kde-apps/marble-18.12.0/work/marble-18.12.0/src/plasmarunner/plasmarunner.cpp:88 #9 0x7fb808203e28 in Plasma::AbstractRunner::performMatch (this=0x558daec83520, localContext=...) at /usr/include/qt5/QtCore/qarraydata.h:234 #10 0x7fb8081dd706 in ThreadWeaver::Executor::run (this=, job=..., thread=) at /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include/g++-v8/bits/atomic_base.h:295 #11 0x7fb8081dc5d0 in ThreadWeaver::Job::execute (this=, self=..., th=0x7fb7b0006180) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/job.cpp:83 #12 0x7fb8081dc087 in ThreadWeaver::Thread::run (this=0x7fb7b0006180) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:312 #13 0x7fb845edd6be in QThreadPrivate::start (arg=0x7fb7b0006180) at thread/qthread_unix.cpp:367 #14 0x7fb844ddb4f3 in start_thread () from /lib64/libpthread.so.0 #15 0x7fb845b3efbf in clone () from /lib64/libc.so.6 *** This bug has been marked as a duplicate of bug 401874 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402876] New: Random crashes of Discovery
https://bugs.kde.org/show_bug.cgi?id=402876 Bug ID: 402876 Summary: Random crashes of Discovery Product: Discover Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: m.trapano...@tutamail.com Target Milestone: --- Application: plasma-discover (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-13-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: Just opened the application, it started loading the repositories and their results and it suddenly crashes The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f79ab9efc80 (LWP 11975))] Thread 23 (Thread 0x7f79337fe700 (LWP 12070)): #0 0x7f79aee12522 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f79aedcbe3b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f79aedcbf6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f79b158f15b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f79b153c16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f79b138b0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79b1394c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79b011e164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f79b1076def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f7933fff700 (LWP 12069)): #0 0x7f79b106a6d9 in __GI___poll (fds=0x7f792c002900, nfds=1, timeout=57327) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f79aedcbe46 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f79aedcbf6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f79b158f15b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f79b153c16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f79b138b0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79b1394c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79b011e164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f79b1076def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f794c82b700 (LWP 12064)): #0 0x7f79b1065f64 in __GI___libc_read (fd=42, buf=0x7f794c82ab80, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f79aee11180 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f79aedcb91f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f79aedcbdf0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f79aedcbf6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f79b158f15b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79b153c16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79b138b0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f79b1394c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f79b011e164 in start_thread (arg=) at pthread_create.c:486 #10 0x7f79b1076def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f794dcb8700 (LWP 12026)): #0 0x7f79b01242eb in futex_wait_cancelable (private=, expected=0, futex_word=0x559ad7542608) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f79b01242eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x559ad75425b8, cond=0x559ad75425e0) at pthread_cond_wait.c:502 #2 0x7f79b01242eb in __pthread_cond_wait (cond=0x559ad75425e0, mutex=0x559ad75425b8) at pthread_cond_wait.c:655 #3 0x7f79a06ac023 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f79a06abd77 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f79b011e164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f79b1076def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f794e4b9700 (LWP 12025)): #0 0x7ffd6c734a0b in clock_gettime () #1 0x7f79b10859f6 in __GI___clock_gettime (clock_id=1, tp=0x7f794e4b8ae0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f79b158ea81 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f79b158d2b9 in QTimerInfoList::updateCurrentTime() () at
[krusader] [Bug 402875] New: Krusader copy/move dialogs no longer a separate window
https://bugs.kde.org/show_bug.cgi?id=402875 Bug ID: 402875 Summary: Krusader copy/move dialogs no longer a separate window Product: krusader Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: raquacont...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY I am not sure when exactly this started, but probably around my upgrade to 2.7.0 version of Krusader. Before, when copying/moving big files, I could start the operation and it was separate window that I could see in my taskbar. I could also minimize Krusader, but this window was not minimized with it. This has now changed and the dialog seems to be "attached" to Krusader main window. So when I minimize Krusader, there is no way for me to tell, if my long running job is finished or not. That seriously hurts my productivity and I would like to have previous behavior restored (at least as an setting option). I have tried to revert to Krusader 2.6.0, but it also behaves this way, so I suspect that it was done somehow generally in KDE ? STEPS TO REPRODUCE 1. Start copying huge file in Krusader 2. Minimize Krusader 3. Copy progress dialog is minimized as well, there is no way to tell if copying is finished or not OBSERVED RESULT See point 3 above. EXPECTED RESULT Copy dialog stays not minimized. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux current, Cinnamon 4 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 402874] New: Kamoso crashed when starting
https://bugs.kde.org/show_bug.cgi?id=402874 Bug ID: 402874 Summary: Kamoso crashed when starting Product: kamoso Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: je...@jantonio.org Target Milestone: --- Application: kamoso (3.2.3) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.20.0-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I started Kamoso for the first time, but keeps crashing. (I did not have the Pictures directory). The crash can be reproduced every time. -- Backtrace: Application: Kamoso (kamoso), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f334b621cc0 (LWP 2132))] Thread 24 (Thread 0x7f32eaffd700 (LWP 2155)): [KCrash Handler] #6 0x404ebef1 in () #7 0x7f32ece55a33 in () #8 0x7f32e02c1a70 in () #9 0x7f32eaffc060 in () #10 0x0001 in () #11 0x7f333ad73366 in () at /usr/lib/libnvidia-glcore.so.415.25 #12 0x7f333ad7df4a in () at /usr/lib/libnvidia-glcore.so.415.25 #13 0x7f333aeead93 in () at /usr/lib/libnvidia-glcore.so.415.25 #14 0x7f333aeb64f7 in () at /usr/lib/libnvidia-glcore.so.415.25 #15 0x7f333aebfc03 in () at /usr/lib/libnvidia-glcore.so.415.25 #16 0x7f333aec3718 in () at /usr/lib/libnvidia-glcore.so.415.25 #17 0x7f333aedaa87 in () at /usr/lib/libnvidia-glcore.so.415.25 #18 0x7f33276b80ce in VideoMaterial::bindTexture(int, unsigned char const*) () at /usr/lib/gstreamer-1.0/libgstqt5videosink.so #19 0x7f33276b81ca in VideoMaterial::bind() () at /usr/lib/gstreamer-1.0/libgstqt5videosink.so #20 0x7f33276b8869 in VideoMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/gstreamer-1.0/libgstqt5videosink.so #21 0x7f335260dcd4 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #22 0x7f335260ee06 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #23 0x7f3352614653 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #24 0x7f3352604a3e in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #25 0x7f3352604f0c in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #26 0x7f33526421a0 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #27 0x7f33526a6085 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib/libQt5Quick.so.5 #28 0x7f335264d940 in () at /usr/lib/libQt5Quick.so.5 #29 0x7f33526516f8 in () at /usr/lib/libQt5Quick.so.5 #30 0x7f335070a9cc in () at /usr/lib/libQt5Core.so.5 #31 0x7f334fa4da9d in start_thread () at /usr/lib/libpthread.so.0 #32 0x7f33503d8b23 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f32eb7fe700 (LWP 2154)): #0 0x7f33503d34ed in syscall () at /usr/lib/libc.so.6 #1 0x7f335216b471 in g_cond_wait () at /usr/lib/libglib-2.0.so.0 #2 0x7f33523216bf in () at /usr/lib/libgstreamer-1.0.so.0 #3 0x7f335218f4a6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f335219867b in () at /usr/lib/libglib-2.0.so.0 #5 0x7f334fa4da9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f33503d8b23 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f32ebfff700 (LWP 2153)): #0 0x7f33503d34ed in syscall () at /usr/lib/libc.so.6 #1 0x7f335216b471 in g_cond_wait () at /usr/lib/libglib-2.0.so.0 #2 0x7f3324b09579 in () at /usr/lib/libgstapp-1.0.so.0 #3 0x7f334022f811 in () at /usr/lib/libgstbase-1.0.so.0 #4 0x7f3340232870 in () at /usr/lib/libgstbase-1.0.so.0 #5 0x7f33523214bb in () at /usr/lib/libgstreamer-1.0.so.0 #6 0x7f335218f4a6 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f335219867b in () at /usr/lib/libglib-2.0.so.0 #8 0x7f334fa4da9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f33503d8b23 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f330cff9700 (LWP 2152)): #0 0x7f33503d34ed in syscall () at /usr/lib/libc.so.6 #1 0x7f335216b471 in g_cond_wait () at /usr/lib/libglib-2.0.so.0 #2 0x7f3326da9460 in () at /usr/lib/gstreamer-1.0/libgstcoreelements.so #3 0x7f33523214bb in () at /usr/lib/libgstreamer-1.0.so.0 #4 0x7f335218f4a6 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f335219867b in () at /usr/lib/libglib-2.0.so.0 #6 0x7f334fa4da9d in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f33503d8b23 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7f330d7fa700 (LWP 2151)): #0 0x7f33503d34ed in syscall () at
[kscreenlocker] [Bug 402873] New: Can't login after suspend
https://bugs.kde.org/show_bug.cgi?id=402873 Bug ID: 402873 Summary: Can't login after suspend Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ksthiele+kde...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY I have two monitors and when the system suspends after not using it for a longer time. When waking it up, only (and always even after switching hdmi cables) the right monitor gets the kscreenlock. STEPS TO REPRODUCE 1. Wait for system to go into power save mode 2. Move mouse to wake up system 3. Kscreenlocker appears and I can't enter a password OBSERVED RESULT I can't login, only when I unplug the monitor and kscreenlocker switches to the first monitor. The keyboard IS recognized I can enter press Caps Lock and it warns me about it. EXPECTED RESULT That I can enter a password and enter desktop again SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.14 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 64bit ADDITIONAL INFORMATION I have an AMD graphics card with latest stable Mesa (now at 18.2.2 on Xorg) from a PPA I also have two monitors: On the left one old "DELL UHD2410" (set as Primary Display) and on the right a newer "LG Ultrawide", as mentioned it always starts on the right monitor (the LG one). I kinda suspect that the Dell needs a bit longer to "start" and KDE ignores it and gives the LG the kscreenlocker. I also observed that I can enter characters while kscreenlocker appears after waking the system up (very short timeframe) but then it locks up most of the time I have Chromium up, maybe it also messes with kscreenlocker? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401768] [feature] - show app number overlay earlier
https://bugs.kde.org/show_bug.cgi?id=401768 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 402840] The application bar immediately hides then appears again on hover
https://bugs.kde.org/show_bug.cgi?id=402840 Michail Vourlakos changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Michail Vourlakos --- plasma X11 issue, can be solved with: https://github.com/psifidotos/Latte-Dock/wiki/F.A.Q.#q-my-left-dock-behaves-strangely-from-plasma-510-and-beyond-can-i-fix-this *** This bug has been marked as a duplicate of bug 392464 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392464] [Auto-Hide] panels behaviour is broken with touch gestures enabled under X11
https://bugs.kde.org/show_bug.cgi?id=392464 Michail Vourlakos changed: What|Removed |Added CC||felixbra...@quicknet.nl --- Comment #7 from Michail Vourlakos --- *** Bug 402840 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #8 from Jens --- KDE Neon (based on Ubuntu 18.04) with all updates applied. 64bit. I have about 180GB of images and videos, ~33000 files. If you want we can debug this together, using Teamviewer or something. -- You are receiving this mail because: You are watching all bug changes.
[kdm] [Bug 353452] Login not accepted after returning from suspend
https://bugs.kde.org/show_bug.cgi?id=353452 ksthiele changed: What|Removed |Added CC||ksthiele+kde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #7 from caulier.gil...@gmail.com --- Well i use also, dual screen, and i cannot reproduce the memory consomption in all case. 2 gb is enormous and i use system indicators if a whole memory leak appears while debugging. Which host system do you use to run the AppImage ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 402504] kstars [ERROR] Object below elevation limit
https://bugs.kde.org/show_bug.cgi?id=402504 --- Comment #10 from Mirco Massone --- Created attachment 117287 --> https://bugs.kde.org/attachment.cgi?id=117287=edit error log from ekos interface Please, can you help me? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 388302] Non-recurring all-day to-dos show up on wrong due date in agenda view
https://bugs.kde.org/show_bug.cgi?id=388302 Boian Berberov changed: What|Removed |Added Platform|openSUSE RPMs |unspecified Version|5.7.3 |5.9.2 --- Comment #7 from Boian Berberov --- My Korganizer reports 5.10.0. The highest "Version" I can set here is 5.9.2, so I am updating it to that. Also changing "Platform" to "unspecified" since there isn't a "multiple" option. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395001] Guides innaccurate on longer projects
https://bugs.kde.org/show_bug.cgi?id=395001 --- Comment #2 from Peter --- No shift when you simply save and then open the project, you have to close kdenlive in between: Steps to reproduce: Start a new 60fps project Add a colour clip to the project bin Add the clip to Video 1 track Set the duration of the clip to 4 hours Go to project timestamp 3:23:26.19 Create a guide at 3:23:26.19 Save the project Close kdenlive Open the project. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395001] Guides innaccurate on longer projects
https://bugs.kde.org/show_bug.cgi?id=395001 Peter changed: What|Removed |Added Version|18.04.1 |Appimage - Refactoring Platform|Gentoo Packages |Appimage -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395001] Guides innaccurate on longer projects
https://bugs.kde.org/show_bug.cgi?id=395001 Peter changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 374882] Double clicks needed instead of single ones
https://bugs.kde.org/show_bug.cgi?id=374882 --- Comment #2 from Johannes Zarl-Zierl --- For future reference, the new behavior is caused by Plasma now enforcing a unified look and feel via use of QStyle. I guess one *could* argue that browsing categories should work the same as browsing files. The Birthdays Page in the Settings dialog, however, is definitely behaving incorrectly. See also: https://api.kde.org/frameworks/frameworkintegration/html/classKStyle.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 --- Comment #7 from Dalton Durst --- I can confirm that it works as expected in a Wayland session. It looks like that patch was accepted -- is there anything else that I should do until it lands? I don't have a build environment for KWin... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #6 from Jens --- I should add I am using Digikam on a dual screen setup, one 1920x1080 FullHD monitor and one 2560x1440 QHD-Monitor to the left (secondary screen). Just in case this makes a difference ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402852] User actions popup is not seen as a popup
https://bugs.kde.org/show_bug.cgi?id=402852 --- Comment #3 from David Edmundson --- That's not the issue. Qmenu is already a popup in the qwindow. But our qpa doesnt send this to the shell client. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402872] New: Hide geolocation tags below images in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=402872 Bug ID: 402872 Summary: Hide geolocation tags below images in thumbnail view Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- In thumbnail view, geolocation tags (if tag display is enabled) tend to spam the tag views, preventing other tags from fitting onto the available space. Face tags also might do this. It would be beneficial to have an option to show only the names of "non-geo" tags below the image thumbnails. Or separate geo tags and face tags from "other" tags and let users choose which ones to put below the image thumbnails. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377099] Hightlight certain albums / tags in tree view
https://bugs.kde.org/show_bug.cgi?id=377099 --- Comment #1 from Jens --- Is there any chance of this getting into 6.x? Thanks! :) -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 393094] Restore support for date/time constants in KEXI SQL
https://bugs.kde.org/show_bug.cgi?id=393094 Jarosław Staniek changed: What|Removed |Added Target Milestone|--- |3.2 Version Fixed In||3.2.0 Beta Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402320] Memory hole (>1.5GB resident after 2 minutes) when detecting faces
https://bugs.kde.org/show_bug.cgi?id=402320 --- Comment #5 from Jens --- I am now using the appimage from 20181228 and the memory hole has even become worse. The digikam process now has 2GB resident memory without using face detection at all, just for having Digikam hang around in the background for half a day. When I restart it, it's back to ~200MB at the start. How can I further help debug this? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402871] New: Import: Show message when no new files are available and the "New files" filter is active
https://bugs.kde.org/show_bug.cgi?id=402871 Bug ID: 402871 Summary: Import: Show message when no new files are available and the "New files" filter is active Product: digikam Version: 6.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-MainView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT In the import view, if no new files are available and the "New Files" filter is activated, Digikam should show a message in the center of the main view saying something like "No *new* images are available for import. If you want to see all available images, select 'All Files' instead of 'New Files' in the bottom toolbar." This should not be a dialog window you have to dismiss, just a text box in the center of the main part of the Digikam window where otherwise thumbnails would be shown. I think this is better than showing nothing at all (which might also be due to slow reading from the medium, or read errors, or a medium missing, or ...) and much less confusing for new users. Empty screens should always be avoided - even an empty Album (or tag, in tag view) in Digikam should have a message in the main view saying "This album is empty" / "This tag has not been used on any images yet." or something similar. -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 393094] Restore support for date/time constants in KEXI SQL
https://bugs.kde.org/show_bug.cgi?id=393094
Jarosław Staniek changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kdb |https://commits.kde.org/kdb
|/42ecae68aa5585042a1b07c270 |/28ade683a351ef0d68c772f1e3
|891b3dfe5da520 |6b316755370939
Status|REOPENED|RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jarosław Staniek ---
Git commit 5b700dfd7c0d266f2da0fc914d1b0c0fe443d287 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add support for the Date/Time constants in the SQL parser
- improve lexer too
- obsolete previous approach for SQL default date support
- and for SQLite, add new APIs for converting date/times
https://community.kde.org/Kexi/Plugins/Queries/SQL_Constants
M +108 -4src/KDb.cpp
M +136 -15 src/KDb.h
M +16 -18 src/KDbDriver.cpp
M +43 -3src/KDbDriver.h
M +2-2src/KDbField.cpp
M +1-1src/KDbQuerySchema.cpp
M +7-2src/KDb_p.h
M +2-3src/drivers/postgresql/PostgresqlCursor.cpp
M +1-1src/drivers/sqlite/SqliteCursor.cpp
M +2-2src/drivers/sqlite/SqlitePreparedStatement.cpp
M +20 -8src/expression/KDbConstExpression.cpp
M +7-4src/parser/KDbParser.cpp
M +1-1src/parser/KDbParser.h
M +150 -2src/parser/KDbSqlParser.y
M +52 -1src/parser/KDbSqlScanner.l
M +4-1src/parser/generate_parser_code.sh
M +4-0src/parser/generated/KDbToken.cpp
M +5-1src/parser/generated/KDbToken.h
M +566 -356 src/parser/generated/sqlparser.cpp
M +13 -3src/parser/generated/sqlparser.h
M +390 -295 src/parser/generated/sqlscanner.cpp
M +1-1src/tools/KDbUtils.cpp
https://commits.kde.org/kdb/5b700dfd7c0d266f2da0fc914d1b0c0fe443d287
--- Comment #7 from Jarosław Staniek ---
Git commit 81ad5897692ccbc77f0b300602cefbf08e3ff070 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add autotests for the KDb date/time classes
GIT_SILENT
M +1-0autotests/CMakeLists.txt
A +96 -0autotests/DateTimeTest.cpp [License: LGPL (v2+)]
A +42 -0autotests/DateTimeTest.h [License: LGPL (v2+)]
https://commits.kde.org/kdb/81ad5897692ccbc77f0b300602cefbf08e3ff070
--- Comment #8 from Jarosław Staniek ---
Git commit c2fcf8a68170cb0df7757375dc35cef0896dcc15 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add autotests for date/time related KDBSQL statements
GIT_SILENT
M +44 -15 autotests/ExpressionsTest.cpp
M +247 -2autotests/parser/data/statements.txt
https://commits.kde.org/kdb/c2fcf8a68170cb0df7757375dc35cef0896dcc15
--- Comment #9 from Jarosław Staniek ---
Git commit 28ade683a351ef0d68c772f1e36b316755370939 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:06.
Pushed by staniek into branch '3.2'.
Restore support for date/time constants in KEXI SQL
Merge branch '393094-date-constants-3.2' into 3.2
- Add Date/Time classes for precise type support
- Add autotests for the KDb date/time classes
- Add support for the Date/Time constants in the SQL parser
- improve lexer too
- obsolete previous approach for SQL default date support
- and for SQLite, add new APIs for converting date/times
https://community.kde.org/Kexi/Plugins/Queries/SQL_Constants
- Add autotests for date/time related KDBSQL statements
KDb VERSION -> 3.2.0 Beta 1
Test Plan:
Precondition: KDb branch: 393094-date-constants against 3.2 branch, KEXI branch
393094-date-constants (D17847)
0. Run KDb autotests
Expected: 100% passes
1. Open a new design in KEXI Query Designer.
Note: Visual designer does not support these constants, use the SQL view.
2. Type a number of statements involving Date, Time and Date/Time constants
You can use test cases from autotests/parser/data/statements.txt, sections:
- Date Constants (KDbSQL EXTENSION)
- Time Constants (KDbSQL EXTENSION)
- Date/Time Constants (KDbSQL EXTENSION)
Use the Check Query button to try both valid and invalid constants. For example
"SELECT #12:13:01#" should work and "SELECT #2018-11-37#" should be rejected as
invalid constant.
Expected: Valid constants should be accepted and then data view should work,
there should be warning for invalid constants.
Expected: Saving of both valid and invalid statements should be possible in the
SQL view.
{F6453115}
3. Create table with columns of type date, time and date/time and add some
records.
4. Open a new design in Query SQL Designer, create statements involving both
constants and columns
e.g. SELECT #12:13:01# AS expr1, timecolumn FROM table where table.timecolumn
< #2018-11-37#
Expected: valid statement, the Data view works.
{F6453113}
5. Test all of the above for SQLite, pgsql, mysql.
Differential
[KEXI] [Bug 393094] Restore support for date/time constants in KEXI SQL
https://bugs.kde.org/show_bug.cgi?id=393094
Jarosław Staniek changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kdb |https://commits.kde.org/kdb
|/42ecae68aa5585042a1b07c270 |/28ade683a351ef0d68c772f1e3
|891b3dfe5da520 |6b316755370939
Status|REOPENED|RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jarosław Staniek ---
Git commit 5b700dfd7c0d266f2da0fc914d1b0c0fe443d287 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add support for the Date/Time constants in the SQL parser
- improve lexer too
- obsolete previous approach for SQL default date support
- and for SQLite, add new APIs for converting date/times
https://community.kde.org/Kexi/Plugins/Queries/SQL_Constants
M +108 -4src/KDb.cpp
M +136 -15 src/KDb.h
M +16 -18 src/KDbDriver.cpp
M +43 -3src/KDbDriver.h
M +2-2src/KDbField.cpp
M +1-1src/KDbQuerySchema.cpp
M +7-2src/KDb_p.h
M +2-3src/drivers/postgresql/PostgresqlCursor.cpp
M +1-1src/drivers/sqlite/SqliteCursor.cpp
M +2-2src/drivers/sqlite/SqlitePreparedStatement.cpp
M +20 -8src/expression/KDbConstExpression.cpp
M +7-4src/parser/KDbParser.cpp
M +1-1src/parser/KDbParser.h
M +150 -2src/parser/KDbSqlParser.y
M +52 -1src/parser/KDbSqlScanner.l
M +4-1src/parser/generate_parser_code.sh
M +4-0src/parser/generated/KDbToken.cpp
M +5-1src/parser/generated/KDbToken.h
M +566 -356 src/parser/generated/sqlparser.cpp
M +13 -3src/parser/generated/sqlparser.h
M +390 -295 src/parser/generated/sqlscanner.cpp
M +1-1src/tools/KDbUtils.cpp
https://commits.kde.org/kdb/5b700dfd7c0d266f2da0fc914d1b0c0fe443d287
--- Comment #7 from Jarosław Staniek ---
Git commit 81ad5897692ccbc77f0b300602cefbf08e3ff070 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add autotests for the KDb date/time classes
GIT_SILENT
M +1-0autotests/CMakeLists.txt
A +96 -0autotests/DateTimeTest.cpp [License: LGPL (v2+)]
A +42 -0autotests/DateTimeTest.h [License: LGPL (v2+)]
https://commits.kde.org/kdb/81ad5897692ccbc77f0b300602cefbf08e3ff070
--- Comment #8 from Jarosław Staniek ---
Git commit c2fcf8a68170cb0df7757375dc35cef0896dcc15 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add autotests for date/time related KDBSQL statements
GIT_SILENT
M +44 -15 autotests/ExpressionsTest.cpp
M +247 -2autotests/parser/data/statements.txt
https://commits.kde.org/kdb/c2fcf8a68170cb0df7757375dc35cef0896dcc15
--- Comment #9 from Jarosław Staniek ---
Git commit 28ade683a351ef0d68c772f1e36b316755370939 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:06.
Pushed by staniek into branch '3.2'.
Restore support for date/time constants in KEXI SQL
Merge branch '393094-date-constants-3.2' into 3.2
- Add Date/Time classes for precise type support
- Add autotests for the KDb date/time classes
- Add support for the Date/Time constants in the SQL parser
- improve lexer too
- obsolete previous approach for SQL default date support
- and for SQLite, add new APIs for converting date/times
https://community.kde.org/Kexi/Plugins/Queries/SQL_Constants
- Add autotests for date/time related KDBSQL statements
KDb VERSION -> 3.2.0 Beta 1
Test Plan:
Precondition: KDb branch: 393094-date-constants against 3.2 branch, KEXI branch
393094-date-constants (D17847)
0. Run KDb autotests
Expected: 100% passes
1. Open a new design in KEXI Query Designer.
Note: Visual designer does not support these constants, use the SQL view.
2. Type a number of statements involving Date, Time and Date/Time constants
You can use test cases from autotests/parser/data/statements.txt, sections:
- Date Constants (KDbSQL EXTENSION)
- Time Constants (KDbSQL EXTENSION)
- Date/Time Constants (KDbSQL EXTENSION)
Use the Check Query button to try both valid and invalid constants. For example
"SELECT #12:13:01#" should work and "SELECT #2018-11-37#" should be rejected as
invalid constant.
Expected: Valid constants should be accepted and then data view should work,
there should be warning for invalid constants.
Expected: Saving of both valid and invalid statements should be possible in the
SQL view.
{F6453115}
3. Create table with columns of type date, time and date/time and add some
records.
4. Open a new design in Query SQL Designer, create statements involving both
constants and columns
e.g. SELECT #12:13:01# AS expr1, timecolumn FROM table where table.timecolumn
< #2018-11-37#
Expected: valid statement, the Data view works.
{F6453113}
5. Test all of the above for SQLite, pgsql, mysql.
Differential
[krunner] [Bug 402870] New: KRunner crashed when I tried to start Steam
https://bugs.kde.org/show_bug.cgi?id=402870 Bug ID: 402870 Summary: KRunner crashed when I tried to start Steam Product: krunner Version: 5.14.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: devuran...@gmx.net Target Milestone: --- Application: krunner (5.14.4) Qt Version: 5.11.3 Frameworks Version: 5.53.0 Operating System: Linux 4.20.0-gentoo x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I was typing "steam" into KRunner and it crashed before I could press enter. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb83eaaaf40 (LWP 1951))] Thread 35 (Thread 0x7fb7997fa700 (LWP 9127)): #0 0x7fb844de236c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7fb845eddcdb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x558dae33ffe0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x558dae46be80, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fb8081d91db in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x558dae514850, th=) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/weaver.cpp:594 #4 0x7fb8081da060 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x558dae514850, th=, th@entry=0x7fb7a4003ce0, threadWasBusy=threadWasBusy@entry=true, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/weaver.cpp:554 #5 0x7fb8081ddee8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x558dae340140, th=0x7fb7a4003ce0, wasBusy=) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/workinghardstate.cpp:66 #6 0x7fb8081d913d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fb7a4003ce0, wasBusy=) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/weaver.cpp:568 #7 0x7fb8081dbfdb in ThreadWeaver::Thread::run (this=0x7fb7a4003ce0) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/thread.cpp:103 #8 0x7fb845edd6be in QThreadPrivate::start (arg=0x7fb7a4003ce0) at thread/qthread_unix.cpp:367 #9 0x7fb844ddb4f3 in start_thread () from /lib64/libpthread.so.0 #10 0x7fb845b3efbf in clone () from /lib64/libc.so.6 Thread 34 (Thread 0x7fb799ffb700 (LWP 9126)): #0 0x7fb844de236c in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7fb845eddcdb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x558dae33ffe0) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=0x558dae46be80, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fb8081d91db in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x558dae514850, th=) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/weaver.cpp:594 #4 0x7fb8081da060 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x558dae514850, th=, th@entry=0x7fb7ac003ce0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/weaver.cpp:554 #5 0x7fb8081ddee8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x558dae340140, th=0x7fb7ac003ce0, wasBusy=) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/workinghardstate.cpp:66 #6 0x7fb8081d913d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fb7ac003ce0, wasBusy=) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/weaver.cpp:568 #7 0x7fb8081ddf42 in ThreadWeaver::WorkingHardState::applyForWork (this=0x558dae340140, th=0x7fb7ac003ce0, wasBusy=) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/workinghardstate.cpp:73 #8 0x7fb8081d913d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fb7ac003ce0, wasBusy=) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/weaver.cpp:568 #9 0x7fb8081dbfdb in ThreadWeaver::Thread::run (this=0x7fb7ac003ce0) at /tmp/portage/kde-frameworks/threadweaver-5.53.0/work/threadweaver-5.53.0/src/thread.cpp:103 #10 0x7fb845edd6be in QThreadPrivate::start (arg=0x7fb7ac003ce0) at thread/qthread_unix.cpp:367 #11 0x7fb844ddb4f3 in start_thread () from
[KEXI] [Bug 393094] Restore support for date/time constants in KEXI SQL
https://bugs.kde.org/show_bug.cgi?id=393094
Jarosław Staniek changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kdb |https://commits.kde.org/kdb
|/42ecae68aa5585042a1b07c270 |/28ade683a351ef0d68c772f1e3
|891b3dfe5da520 |6b316755370939
Status|REOPENED|RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jarosław Staniek ---
Git commit 5b700dfd7c0d266f2da0fc914d1b0c0fe443d287 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add support for the Date/Time constants in the SQL parser
- improve lexer too
- obsolete previous approach for SQL default date support
- and for SQLite, add new APIs for converting date/times
https://community.kde.org/Kexi/Plugins/Queries/SQL_Constants
M +108 -4src/KDb.cpp
M +136 -15 src/KDb.h
M +16 -18 src/KDbDriver.cpp
M +43 -3src/KDbDriver.h
M +2-2src/KDbField.cpp
M +1-1src/KDbQuerySchema.cpp
M +7-2src/KDb_p.h
M +2-3src/drivers/postgresql/PostgresqlCursor.cpp
M +1-1src/drivers/sqlite/SqliteCursor.cpp
M +2-2src/drivers/sqlite/SqlitePreparedStatement.cpp
M +20 -8src/expression/KDbConstExpression.cpp
M +7-4src/parser/KDbParser.cpp
M +1-1src/parser/KDbParser.h
M +150 -2src/parser/KDbSqlParser.y
M +52 -1src/parser/KDbSqlScanner.l
M +4-1src/parser/generate_parser_code.sh
M +4-0src/parser/generated/KDbToken.cpp
M +5-1src/parser/generated/KDbToken.h
M +566 -356 src/parser/generated/sqlparser.cpp
M +13 -3src/parser/generated/sqlparser.h
M +390 -295 src/parser/generated/sqlscanner.cpp
M +1-1src/tools/KDbUtils.cpp
https://commits.kde.org/kdb/5b700dfd7c0d266f2da0fc914d1b0c0fe443d287
--- Comment #7 from Jarosław Staniek ---
Git commit 81ad5897692ccbc77f0b300602cefbf08e3ff070 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add autotests for the KDb date/time classes
GIT_SILENT
M +1-0autotests/CMakeLists.txt
A +96 -0autotests/DateTimeTest.cpp [License: LGPL (v2+)]
A +42 -0autotests/DateTimeTest.h [License: LGPL (v2+)]
https://commits.kde.org/kdb/81ad5897692ccbc77f0b300602cefbf08e3ff070
--- Comment #8 from Jarosław Staniek ---
Git commit c2fcf8a68170cb0df7757375dc35cef0896dcc15 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:03.
Pushed by staniek into branch '3.2'.
Add autotests for date/time related KDBSQL statements
GIT_SILENT
M +44 -15 autotests/ExpressionsTest.cpp
M +247 -2autotests/parser/data/statements.txt
https://commits.kde.org/kdb/c2fcf8a68170cb0df7757375dc35cef0896dcc15
--- Comment #9 from Jarosław Staniek ---
Git commit 28ade683a351ef0d68c772f1e36b316755370939 by Jaroslaw Staniek.
Committed on 04/01/2019 at 21:06.
Pushed by staniek into branch '3.2'.
Restore support for date/time constants in KEXI SQL
Merge branch '393094-date-constants-3.2' into 3.2
- Add Date/Time classes for precise type support
- Add autotests for the KDb date/time classes
- Add support for the Date/Time constants in the SQL parser
- improve lexer too
- obsolete previous approach for SQL default date support
- and for SQLite, add new APIs for converting date/times
https://community.kde.org/Kexi/Plugins/Queries/SQL_Constants
- Add autotests for date/time related KDBSQL statements
KDb VERSION -> 3.2.0 Beta 1
Test Plan:
Precondition: KDb branch: 393094-date-constants against 3.2 branch, KEXI branch
393094-date-constants (D17847)
0. Run KDb autotests
Expected: 100% passes
1. Open a new design in KEXI Query Designer.
Note: Visual designer does not support these constants, use the SQL view.
2. Type a number of statements involving Date, Time and Date/Time constants
You can use test cases from autotests/parser/data/statements.txt, sections:
- Date Constants (KDbSQL EXTENSION)
- Time Constants (KDbSQL EXTENSION)
- Date/Time Constants (KDbSQL EXTENSION)
Use the Check Query button to try both valid and invalid constants. For example
"SELECT #12:13:01#" should work and "SELECT #2018-11-37#" should be rejected as
invalid constant.
Expected: Valid constants should be accepted and then data view should work,
there should be warning for invalid constants.
Expected: Saving of both valid and invalid statements should be possible in the
SQL view.
{F6453115}
3. Create table with columns of type date, time and date/time and add some
records.
4. Open a new design in Query SQL Designer, create statements involving both
constants and columns
e.g. SELECT #12:13:01# AS expr1, timecolumn FROM table where table.timecolumn
< #2018-11-37#
Expected: valid statement, the Data view works.
{F6453113}
5. Test all of the above for SQLite, pgsql, mysql.
Differential
[kate] [Bug 402842] Can not print with kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=402842 --- Comment #1 from Potomac --- the complete error message from cups when I try to print with kate/kwrite : [CAPTFILTER] Input File Error paused - "ccp send_data error, exit" it seems that kate/kwrite use improper print options compared to my printer driver (paper format, margins for example, something that trigger an error on the printer driver) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402869] New: Add write permission to files copied from an MTP device
https://bugs.kde.org/show_bug.cgi?id=402869 Bug ID: 402869 Summary: Add write permission to files copied from an MTP device Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: martonmiklosq...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY When copying files from an MTP or PTP device (such a digital camera) the copied files will have readonly permissions for the owner as well. It is pretty inconvenient because before I edit those files I have to change permissions. I understand that it makes sense to keep the file permissions during the copy operation, but this case is different: I can delete files from the MTP/PTP filesystem. STEPS TO REPRODUCE 1. Connect an MTP device which contains some files 2. Copy a file to a location where you have write permissions OBSERVED RESULT The copied file will have readonly permissions EXPECTED RESULT The copied file should have RW permissions for the copying user SOFTWARE/OS VERSIONS Linux/KDE Plasma: 16.04.3 (available in About System) KDE Plasma Version: 16.04.3 KDE Frameworks Version: 5.36.0 Qt Version: 5.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 374882] Double clicks needed instead of single ones
https://bugs.kde.org/show_bug.cgi?id=374882 Johannes Zarl-Zierl changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||johan...@zarl-zierl.at --- Comment #1 from Johannes Zarl-Zierl --- Sorry for not responding way sooner. Somehow I overlooked and/or forgot it… I can confirm the issue, and it is not an intended change. Thanks for reporting! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402863] copy and paste stops working after a while
https://bugs.kde.org/show_bug.cgi?id=402863 Egmont Koblinger changed: What|Removed |Added CC||egm...@gmail.com --- Comment #1 from Egmont Koblinger --- Maybe the same as bug 387202? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402868] Onion skin doesn't work propelly
https://bugs.kde.org/show_bug.cgi?id=402868 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Please do not create a new bug, but provide the information as a comment in the original report. I'll paste in there for now, but please also provide a test file and the information from help/system information for bug reports. *** This bug has been marked as a duplicate of bug 402867 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402867] Onion skin doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=402867 --- Comment #2 from Boudewijn Rempt --- Information provided by reporter in the duplicate report: STEPS TO REPRODUCE 1. I made new frame 2. I drew picture 3. I drew another pisture on another frame 4. I turn on the onion skin 5. Everything is black, and the "light bulb" doesn't show 6. I only see these two black pictures like it's everything on one frame -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402867] Onion skin doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=402867 --- Comment #3 from Boudewijn Rempt --- *** Bug 402868 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402868] New: Onion skin doesn't work propelly
https://bugs.kde.org/show_bug.cgi?id=402868 Bug ID: 402868 Summary: Onion skin doesn't work propelly Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: lifeonma...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. I made new frame 2. I drew picture 3. I drew another pisture on another frame 4. I turn on the onion skin 5. Everything is black, and the "light bulb" doesn't show 6. I only see these two black pictures like it's everything on one frame OBSERVED RESULT 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.
[krita] [Bug 402867] Onion skin doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=402867 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Summary|Onion skin doesn't work |Onion skin doesn't work |propelly|properly CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- I'm sorry, but given that we do know that onion skinning does work, this is not a bug report we can do anything with. You will have to provide clear steps for reproducing the issue, a clear description of the issue and probably also a clear description of what you're expecting. If you haven't already done so, please read https://docs.krita.org/en/reference_manual/dockers/onion_skin.html -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355971] Onion skin doesn't work
https://bugs.kde.org/show_bug.cgi?id=355971 lifeonma...@gmail.com changed: What|Removed |Added CC||lifeonma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402867] New: Onion skin doesn't work propelly
https://bugs.kde.org/show_bug.cgi?id=402867 Bug ID: 402867 Summary: Onion skin doesn't work propelly Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: lifeonma...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385442] AppImage 17.08.1b and 17.12 alpha 4. Path to ffplay, question
https://bugs.kde.org/show_bug.cgi?id=385442 emohr changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 402816] Insert Zone in Project Bin not present in UI
https://bugs.kde.org/show_bug.cgi?id=402816 emohr changed: What|Removed |Added Flags||low_hanging+ Keywords||junior-jobs Severity|normal |wishlist CC||fritzib...@gmx.net Ever confirmed|0 |1 Version|17.12.3 |Appimage - Refactoring Status|REPORTED|CONFIRMED --- Comment #1 from emohr --- "Insert Zone in Project Bin" and "Insert Zone in Timeline" you find under the menu Monitor. Yes it's even not documented. It should be available by right click in the clip monitor. Thank you for reporting. I change this to wishlist if you don't mind. And change to refactoring. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 389473] Clang plugin error with latest versions
https://bugs.kde.org/show_bug.cgi?id=389473 --- Comment #38 from Tam HANNA --- Hello, and here is the build script I used: echo "Now working on CMAKE" sudo apt-get remove cmake wget http://www.cmake.org/files/v3.11/cmake-3.11.0.tar.gz tar -xvzf cmake-3.11.0.tar.gz cd cmake-3.11.0/ ./configure make -j 10 sudo make install cd .. echo "Now working on LLVM" git clone https://github.com/llvm-mirror/llvm.git cd llvm/ git checkout remotes/origin/release_70 cd tools git clone https://github.com/llvm-mirror/clang.git cd clang git checkout remotes/origin/release_70 cd .. cd .. cd projects git clone https://github.com/llvm-mirror/compiler-rt.git cd .. sudo apt-get remove clang llvm mkdir build cd build cmake -DLLVM_TARGETS_TO_BUILD=X86 -DBUILD_SHARED_LIBS=ON -DCMAKE_BUILD_TYPE=Release .. make -j 10 sudo make install cd .. cd .. echo "Now working on CLAZY" git clone https://github.com/KDE/clazy cd clazy cmake -DLLVM_INCLUDE_EXAMPLES=OFF -DLINK_CLAZY_TO_LLVM=OFF -DLLVM_TARGETS_TO_BUILD="X86" -DBUILD_SHARED_LIBS=ON -DCMAKE_BUILD_TYPE=Release make -j 10 sudo make install -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 389473] Clang plugin error with latest versions
https://bugs.kde.org/show_bug.cgi?id=389473 Tam HANNA changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #37 from Tam HANNA --- Hello, sadly, it still does not fully work. I ran the build script with the contents I will post soon, and got this: root@TAMHAN14:~/clazyspace# touch x.cpp root@TAMHAN14:~/clazyspace# clazy x.cpp -v clang version 7.0.1 (https://github.com/llvm-mirror/clang.git 4519e2637fcc4bf6e3049a0a80e6a5e7b97667cb) (https://github.com/llvm-mirror/llvm.git cd98f42d0747826062fc3d2d2fad383aedf58dd6) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /usr/local/bin Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.8 Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.8.5 Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9 Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9.4 Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/7 Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/7.4.0 Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/8 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.5 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.4 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.5.0 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/7.4.0 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/8 Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.5.0 Candidate multilib: .;@m64 Selected multilib: .;@m64 "/usr/local/bin/clang-7" -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -discard-value-names -main-file-name x.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -v -resource-dir /usr/local/lib/clang/7.0.1 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../../include/c++/6.5.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../../include/x86_64-linux-gnu/c++/6.5.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../../include/x86_64-linux-gnu/c++/6.5.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../../include/c++/6.5.0/backward -internal-isystem /usr/local/include -internal-isystem /usr/local/lib/clang/7.0.1/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -fdeprecated-macro -fdebug-compilation-dir /home/tamhan/clazyspace -ferror-limit 19 -fmessage-length 205 -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -load ClazyPlugin.so -add-plugin clazy -o /tmp/x-8ff6e6.o -x c++ x.cpp -faddrsig clang -cc1 version 7.0.1 based upon LLVM 7.0.1 default target x86_64-unknown-linux-gnu ignoring nonexistent directory "/include" ignoring duplicate directory "/usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../../include/x86_64-linux-gnu/c++/6.5.0" #include "..." search starts here: #include <...> search starts here: /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../../include/c++/6.5.0 /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../../include/x86_64-linux-gnu/c++/6.5.0 /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../../include/c++/6.5.0/backward /usr/local/include /usr/local/lib/clang/7.0.1/include /usr/include/x86_64-linux-gnu /usr/include End of search list. "/usr/bin/ld" -z relro --hash-style=gnu --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o a.out /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../x86_64-linux-gnu/crt1.o /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/6.5.0/crtbegin.o -L/usr/lib/gcc/x86_64-linux-gnu/6.5.0 -L/usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../x86_64-linux-gnu -L/lib/x86_64-linux-gnu -L/lib/../lib64 -L/usr/lib/x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../.. -L/usr/local/bin/../lib -L/lib -L/usr/lib /tmp/x-8ff6e6.o -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /usr/lib/gcc/x86_64-linux-gnu/6.5.0/crtend.o /usr/lib/gcc/x86_64-linux-gnu/6.5.0/../../../x86_64-linux-gnu/crtn.o /usr/bin/ld: /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info): relocation 0 has invalid symbol index 11 /usr/bin/ld: /usr/lib/debug/usr/lib/x86_64-linux-gnu/crt1.o(.debug_info): relocation 1 has invalid symbol index 12 /usr/bin/ld:
[kdenlive] [Bug 385442] AppImage 17.08.1b and 17.12 alpha 4. Path to ffplay, question
https://bugs.kde.org/show_bug.cgi?id=385442 --- Comment #3 from Pastjl --- Yes no problem with 18.12 and 19.04.can be closed -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist
https://bugs.kde.org/show_bug.cgi?id=397956 Ardith Metz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 Martin Flöser changed: What|Removed |Added Status|NEEDSINFO |REPORTED Component|wayland-generic |platform-drm Resolution|BACKTRACE |--- Flags||Wayland+, X11- Severity|major |crash --- Comment #10 from Martin Flöser --- Thanks, that is a really good backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402865] Drag Maximized window doesn't reduce it
https://bugs.kde.org/show_bug.cgi?id=402865 --- Comment #1 from Martin Flöser --- please provide the output of: qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387768] File system corruption after renaming folder
https://bugs.kde.org/show_bug.cgi?id=387768 --- Comment #15 from clem --- (In reply to caulier.gilles from comment #14) > Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just > released ? Have there been any commits to resolve this issue? I'd rather not try to destroy the filesystem on my production machine intentionally -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402866] New: KDevelop crashed after closing the run console.
https://bugs.kde.org/show_bug.cgi?id=402866 Bug ID: 402866 Summary: KDevelop crashed after closing the run console. Product: kdevelop Version: 5.2.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: hpm...@gmail.com Target Milestone: --- Application: kdevelop (5.2.1) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I was minding my own business, playing with (writing) Python code from a RasPi project. I clicked execute, using the default Python script execution set-up, and the Run console came up only saying "Running .py ..." but then nothing after. I clicked on the little (x) in the corner of the console to close it, and KDev crashed. Sometimes it will close successfully, but ~80% of the time, this results in a crash. Of note: The code wasn't exactly a script, and more of a simple program. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f594710c940 (LWP 12327))] Thread 8 (Thread 0x7f58fcaf6700 (LWP 12470)): #0 0x7f594378b0b4 in __GI___libc_read (fd=18, buf=0x7f58fcaf5a50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f593a6b6cd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f593a672027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f593a6724e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f593a67264c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f59440d890b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f594407d9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5943e9c22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5943ea116d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f593cf206db in start_thread (arg=0x7f58fcaf6700) at pthread_create.c:463 #10 0x7f594379c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f58f7fff700 (LWP 12355)): #0 0x7f593a66f450 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f593a6719d3 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f593a67246b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f593a67264c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f59440d890b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f594407d9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5943e9c22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f58eb42a3c5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #8 0x7f5943ea116d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f593cf206db in start_thread (arg=0x7f58f7fff700) at pthread_create.c:463 #10 0x7f594379c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f58fdba5700 (LWP 12335)): #0 0x7f594378fbf9 in __GI___poll (fds=0x7f58f8004e10, nfds=1, timeout=9960) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f593a672539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f593a67264c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f59440d890b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f594407d9ea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5943e9c22a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5943ea116d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f593cf206db in start_thread (arg=0x7f58fdba5700) at pthread_create.c:463 #8 0x7f594379c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f59054b9700 (LWP 12333)): #0 0x7f593a6719e9 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f593a67246b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f593a67264c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f59440d890b in QEventDispatcherGlib::processEvents(QFlags) () from
[digikam] [Bug 306193] desktop-file-validate fails on desktop files
https://bugs.kde.org/show_bug.cgi?id=306193 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|imaging-bugs-n...@kde.org |digikam-bugs-n...@kde.org Component|General |Tarball-Compilation Product|libkipi |digikam -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 357239] Decrease/Increase Thumbnail size Icons are misleading
https://bugs.kde.org/show_bug.cgi?id=357239 --- Comment #5 from Andreas Schleth --- Thanks, Johannes. This is a nice surprise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402764] Caps Lock as additional Super does not trigger Alt+F1 shortcut
https://bugs.kde.org/show_bug.cgi?id=402764 Martin Flöser changed: What|Removed |Added URL||https://phabricator.kde.org ||/D17967 Flags||ReviewRequest+ --- Comment #6 from Martin Flöser --- Possible, but untested patch: https://phabricator.kde.org/D17967 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402865] New: Drag Maximized window doesn't reduce it
https://bugs.kde.org/show_bug.cgi?id=402865 Bug ID: 402865 Summary: Drag Maximized window doesn't reduce it Product: kwin Version: 5.14.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: compte.ada...@gmail.com Target Milestone: --- Created attachment 117286 --> https://bugs.kde.org/attachment.cgi?id=117286=edit Maximized window dragged, unable to resize and when click on maximized button, it reduce. SUMMARY When dragging maximized window, the maximized window stay maximized on another position. STEPS TO REPRODUCE 1. Open app 2. Maximize window 3. Take title bar and drag (OPTIONNAL) 4. Tap on Maximize button OBSERVED RESULT The maximized window moved, but it is maximized. EXPECTED RESULT Maximized window reduce it before being dragged. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Kde neon 5.1 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION HARDWARE: AMD graphic card R9 M360 Intel core i7 6700 19,5 GB ram France -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 169614] Next/Previous Page should keep position on page
https://bugs.kde.org/show_bug.cgi?id=169614 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #4 from Luigi Toscano --- (In reply to gbodley from comment #3) > In presentation mode there needs to be side by side page viewing, and the > ability to navigate through the pages by just touching the screen. The > wheel works, but is too small to use to navigate accurately and quickly. I > have a folding laptop/table computer. The keyboard doesn't work when it's > configured as a tablet, and mouse at the piano is not as good as simply > touching the screen. A touch on the right side of the screen should move > the document forward, and a touch on the left side should move it to the > previous page. I think that this is unrelated to this bug, which is about the part of the window shown when navigating through the keyboard. Same for few other comments on navigation-related bugs. Please keep the comments on topic for each bug; no need to report the same issue on unrelated bugs. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 184095] All arrow keys should be usable for navigation
https://bugs.kde.org/show_bug.cgi?id=184095 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #4 from Luigi Toscano --- (In reply to gbodley from comment #3) > Need touch to be able to navigate through single or side by side pages. > Touch on the right goes forward, touch on the left goes backwards. At least > that's how it should work. Presently you can only go forward and have to > use the wheel to go backwards, but the wheel while good is too small for > quick touch navigation. I think that this is unrelated to this bug, which is about keyboard navigation. Same for few other comments on navigation-related bugs. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398288] digikam no write access to folder
https://bugs.kde.org/show_bug.cgi?id=398288 --- Comment #12 from Steve Franks --- Created attachment 117285 --> https://bugs.kde.org/attachment.cgi?id=117285=edit Digikam Database migrate dialog I thought that this would be a straightforward copy from one folder to another, but there's obviously more to it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398288] digikam no write access to folder
https://bugs.kde.org/show_bug.cgi?id=398288 --- Comment #11 from Steve Franks --- Created attachment 117284 --> https://bugs.kde.org/attachment.cgi?id=117284=edit Directory listings The database migration seems to be very slow. Look at the timestamps on the oldest and newest files. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 184095] All arrow keys should be usable for navigation
https://bugs.kde.org/show_bug.cgi?id=184095 gbod...@gmail.com changed: What|Removed |Added CC||gbod...@gmail.com --- Comment #3 from gbod...@gmail.com --- Need touch to be able to navigate through single or side by side pages. Touch on the right goes forward, touch on the left goes backwards. At least that's how it should work. Presently you can only go forward and have to use the wheel to go backwards, but the wheel while good is too small for quick touch navigation. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 169614] Next/Previous Page should keep position on page
https://bugs.kde.org/show_bug.cgi?id=169614 gbod...@gmail.com changed: What|Removed |Added CC||gbod...@gmail.com --- Comment #3 from gbod...@gmail.com --- In presentation mode there needs to be side by side page viewing, and the ability to navigate through the pages by just touching the screen. The wheel works, but is too small to use to navigate accurately and quickly. I have a folding laptop/table computer. The keyboard doesn't work when it's configured as a tablet, and mouse at the piano is not as good as simply touching the screen. A touch on the right side of the screen should move the document forward, and a touch on the left side should move it to the previous page. -- You are receiving this mail because: You are watching all bug changes.
