[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #15 from Maik Qualmann --- Can you download and start DebugView from Microsoft and then post the output when you set metadata to RAW files and write metadata? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #14 from Lars Grabner --- Sorry, on windows explorer it wasn´t shown. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396978] Stable xml file output
https://bugs.kde.org/show_bug.cgi?id=396978 Thomas Baumgart changed: What|Removed |Added Version Fixed In||5.0.4 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/600af541035959ace4bdd ||21b74d078764f02516e Status|CONFIRMED |RESOLVED --- Comment #3 from Thomas Baumgart --- Git commit 600af541035959ace4bdd21b74d078764f02516e by Thomas Baumgart. Committed on 20/04/2019 at 05:49. Pushed by tbaumgart into branch '5.0'. Make XML files comparable again Since commit e4d384d34a91eb6024800 (which later made it into v5.0.2), the order of attributes in the XML file is random each time the file is saved. This leads to the fact that it is extremly hard to compare two files because one does not see the forest for the trees. This change removes the randomness and thus brings back comparability. FIXED-IN: 5.0.4 M +11 -10 kmymoney/plugins/xml/mymoneystoragenames.cpp https://commits.kde.org/kmymoney/600af541035959ace4bdd21b74d078764f02516e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #13 from Lars Grabner --- In picasa (and windows explorer) the metatags are not shown. yet. In version 4... or 5.. it was ok. And yes at JPG images the tags are shown. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #12 from Maik Qualmann --- Specifically, why do you think the metadata was not written in the RAW images? And the problem does not occur with JPG images? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #11 from Maik Qualmann --- Even with this setting, the metadata in both image and sidecar are written here. If you change tags, color labels or comments etc. in the right side bar, you have to click on "Apply" first. An additional writing of the metadata is not necessary. The "More..." functions read and write only existing metadata from the images to the database or vice versa. To synchronize the selected images or the database. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 Lars Grabner changed: What|Removed |Added Attachment #119516|0 |1 is obsolete|| --- Comment #10 from Lars Grabner --- Created attachment 119517 --> https://bugs.kde.org/attachment.cgi?id=119517=edit picture Now I´ve disabled sidecars but it doesn´t work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #9 from Lars Grabner --- Created attachment 119516 --> https://bugs.kde.org/attachment.cgi?id=119516=edit picture I think so. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #8 from Maik Qualmann --- Have you possibly activated writing to sidecars? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #7 from Maik Qualmann --- When I see the screenshot of Comment 4, it reminds me again to report the wrong German spelling to the translator team (Fall => Falls). I also can not reproduce the problem with EOS400 RAW files. Metadata previously only in the database are correctly written into the RAW files. Which metadata are not written with you and how do you test the error at the RAW files? Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401940] More than one Assistant Tool causes black rectangle to appear
https://bugs.kde.org/show_bug.cgi?id=401940 gvgeo changed: What|Removed |Added Resolution|WAITINGFORINFO |BACKTRACE --- Comment #10 from gvgeo --- With only 2 people reporting, it looks like, this bug will remain unfixed. With all the info provided, and no more specific info asked, instead of changing to REPORTED again, will change the status from NEEDSINFO - WAITINGFORINFO to NEEDSINFO - BACKTRACE. -- You are receiving this mail because: You are watching all bug changes.
[calligragemini] [Bug 346772] Git plugin build fails
https://bugs.kde.org/show_bug.cgi?id=346772 Иван Туманов changed: What|Removed |Added CC||tu4manj...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403265] [HUION] Shortcuts not working with Python Scripts with 1060 Plus (8192)
https://bugs.kde.org/show_bug.cgi?id=403265 --- 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.
[plasmashell] [Bug 404342] HP Mini 210-2204er + OpenSUSE Leap-15.0 + slideshow = plasmashell CRASH
https://bugs.kde.org/show_bug.cgi?id=404342 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401940] More than one Assistant Tool causes black rectangle to appear
https://bugs.kde.org/show_bug.cgi?id=401940 --- Comment #9 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.
[Touchpad-KCM] [Bug 368156] No touchpad found
https://bugs.kde.org/show_bug.cgi?id=368156 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401759] Animation does not render properly when I change the end frame
https://bugs.kde.org/show_bug.cgi?id=401759 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 403942] crash by right click
https://bugs.kde.org/show_bug.cgi?id=403942 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #6 from Lars Grabner --- Created attachment 119515 --> https://bugs.kde.org/attachment.cgi?id=119515=edit picture Then I select the files and klick on "more" and "Write metadata to all Files" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #5 from Lars Grabner --- It is the option called "If possible, write metatags to RAW File" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #4 from Lars Grabner --- Created attachment 119514 --> https://bugs.kde.org/attachment.cgi?id=119514=edit Picture I want to find out, where my mistakes are... in the picture, the "klicked" option in settings. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406694] New: Will Not Notify Paired Device When Phone Has Incoming Call
https://bugs.kde.org/show_bug.cgi?id=406694 Bug ID: 406694 Summary: Will Not Notify Paired Device When Phone Has Incoming Call Product: kdeconnect Version: unspecified Platform: Android OS: Android 8.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: tryme...@tutanota.com Target Milestone: --- SUMMARY I have a Samsung Galaxy S6 and Samsung Galaxy S8. When I pair the devices and have it so the S8 will notify the S6 when it has a incoming call. It does notify when there is a missed call. On my Samsung S8 a Phone notificiation does appear when a incoming call is displayed. I do have the phone app checked off in the notification app whitelist. STEPS TO REPRODUCE 1. Install KDE Connect on Samsung Galaxy S6 from F-Droid 2. Install KDE Connect on Samsung Galaxy S8 from F-Droid 3. Pair devices 4. Ensure on Samsung Galaxy S8 that notification app whitelist selects Phone app. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406693] New: Cannot Pair Samsung Galaxy Tab S4
https://bugs.kde.org/show_bug.cgi?id=406693 Bug ID: 406693 Summary: Cannot Pair Samsung Galaxy Tab S4 Product: kdeconnect Version: unspecified Platform: Android OS: Android 8.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: tryme...@tutanota.com Target Milestone: --- SUMMARY I have paired my Samsung Galaxy S6 and Samsung Galaxy S8 phones successfully but was not able to pair my Samsung Galaxy Tab S4 to my Samsung Galaxy S8. STEPS TO REPRODUCE 1. Have Samsung Galaxy S8 2. Have Samsung Galaxy Tab S4 3. Install KDE Connect app from F-Droid on both devices OBSERVED RESULT To be able to pair the two devices together EXPECTED RESULT The devices cannot be found, therefore cannot be paired. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406540] Add Metatags to Canon Raw
https://bugs.kde.org/show_bug.cgi?id=406540 --- Comment #3 from Lars Grabner --- EOS 400D -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406415] Dock does not always hide
https://bugs.kde.org/show_bug.cgi?id=406415 --- Comment #11 from Michail Vourlakos --- (In reply to attila.koszo.official from comment #10) > In a Wayland session the bug couldn't be reproduced. Apparently it's an Xorg > bug. > Does it mean that the issue is resolved? Not quite. First I will need to investigate what is the reason of the faulty behavior under X11. If Latte can handle the case e.g. when the slide in animation ends, Latte could make a check if the dock should be hidden or not, and act accordingly -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave
https://bugs.kde.org/show_bug.cgi?id=406684 Иван Туманов changed: What|Removed |Added CC||tu4manj...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 406684] backend is not compatible with up-to-date flatpak package of octave
https://bugs.kde.org/show_bug.cgi?id=406684 Иван Туманов changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 378814] Consider switching to the GSignond stack
https://bugs.kde.org/show_bug.cgi?id=378814 Иван Туманов changed: What|Removed |Added CC||tu4manj...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405057] Text selection inside the KDE Connect Plasmoid
https://bugs.kde.org/show_bug.cgi?id=405057 Иван Туманов changed: What|Removed |Added Flags||Translation_missing+, ||Usability+ CC||tu4manj...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399234] Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 winsauce...@gmail.com changed: What|Removed |Added CC||winsauce...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 George R. Goffe changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED --- Comment #16 from George R. Goffe --- I'm hoping that this post will resolve the needs info flag on this bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406485] KDE forgets my display settings after reboot
https://bugs.kde.org/show_bug.cgi?id=406485 --- Comment #2 from Brian --- Refresh rate (143.98 HZ in my case) is also affected without even rebooting. Clicking on apply will show the setting's new value until you reopen the display settings, where it will then revert back to auto. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406485] KDE forgets my display settings after reboot
https://bugs.kde.org/show_bug.cgi?id=406485 Brian changed: What|Removed |Added CC||brianabe...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Brian --- Can confirm this bug affects Solus as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405978] Crash when changing scaling
https://bugs.kde.org/show_bug.cgi?id=405978 --- Comment #3 from Aleix Pol --- Sorry, I don't have access to debug packages for wayland as I'm on archlinux. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 406692] New: 'st' incorrectly saved as 'st' to .bib file
https://bugs.kde.org/show_bug.cgi?id=406692 Bug ID: 406692 Summary: 'st' incorrectly saved as 'st' to .bib file Product: KBibTeX Version: 0.8.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Loading/saving files Assignee: fisc...@unix-ag.uni-kl.de Reporter: kde-bugtrack...@choreutes.de Target Milestone: --- Created attachment 119513 --> https://bugs.kde.org/attachment.cgi?id=119513=edit An entry from my .bib file (managed by kbibtex) containing the bug SUMMARY The letter combination 'st' is incorrectly written as the unicode ligature symbol 'st' to the .bib file for most entry fields STEPS TO REPRODUCE 1. Open a .bib file in kbibtex 2. Create a new item containing the combination 'st', e.g. in the title or the author field, if none is already present 3. Save changes to .bib file 4. Inspect the .bib file with a text editor OBSERVED RESULT All appearances of 'st' are substituted by 'st' (see attached example) EXPECTED RESULT Letter combination 'st' should be saved unchanged as the ligature symbol might not be displayed in a resulting .pdf file SOFTWARE/OS VERSIONS Linux: 5.0.7 (Arch Linux) KDE Plasma Version: -- (not installed) KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I recently made the switch from i3wm (x11) to sway (wayland) as my window manager. I'm mentioning this just for the sake of completeness although I'm pretty sure the problem did not occur before I updated kbibtex to version 0.8.2 and my window manager should have nothing to do with the file management of kbibtex anyway. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396363] Text tool SIGABRT when inserting a tab followed by multiple letters
https://bugs.kde.org/show_bug.cgi?id=396363 vanyossi changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com CC||ghe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406691] Can't follow symbolic links in SFTP locations
https://bugs.kde.org/show_bug.cgi?id=406691 aslam karachiwala changed: What|Removed |Added CC||as...@mythicflow.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406691] New: Can't follow symbolic links in SFTP locations
https://bugs.kde.org/show_bug.cgi?id=406691 Bug ID: 406691 Summary: Can't follow symbolic links in SFTP locations Product: dolphin Version: 17.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: as...@mythicflow.com Target Milestone: --- SUMMARY In an SFTP location, defined either by adding an entry to Places or by adding a new network, attempts to follow a symbolic link fail with the message, "Could not read file sftp://...; This happens with links that point to locations within the user's home directory as well as locations outside it (IOW, this is not caused by a chroot restriction). This started occurring recently, most likely after an update from the kubuntu-backports repo. If the SFTP location is mounted (using 'mount'), symbolic links can be followed as expected. STEPS TO REPRODUCE 1. Create an SFTP entry in Places, or add it as a new network in Networks. 2. Navigate to the location created in #1 and click on a symbolic link within the location. OBSERVED RESULT Error dialog appears saying, "Could not read file sftp://...; EXPECTED RESULT Access the directory/file that the symbolic link points to. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406409] Regression: New tab behavior "Put New Tab After Current Tab" no longer works
https://bugs.kde.org/show_bug.cgi?id=406409 Sok Ann Yap changed: What|Removed |Added CC||sok...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 405213] [regression] Closing a tab doesn't select the previously focused tab any more
https://bugs.kde.org/show_bug.cgi?id=405213 Sok Ann Yap changed: What|Removed |Added CC||sok...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403059] shrinking size of tabs
https://bugs.kde.org/show_bug.cgi?id=403059 Sok Ann Yap changed: What|Removed |Added CC||sok...@gmail.com --- Comment #3 from Sok Ann Yap --- Hi Tomaz, in https://bugs.kde.org/show_bug.cgi?id=396726#c4, you said: > Any rework brings new bugs so I'm not worried and I'm activelly trying to fix > the ones that are open and I would consider this as a regression bug. Similar to slybzh, my workflow involves opening 15~20 tabs, and relying on the previous auto-shrinking behavior to have all tabs visible without scrolling. Tabs would be spatially "grouped" together, allowing me to have let's say (from the left to right) root tabs + ansible tabs + project A tabs + project B tabs, all available and selectable visually, without having to do any manual renaming. I am not that familiar with the code base. Are you saying that after the change to use QTabBar, it is technically not possible to get back the previous auto-shrinking behavior (e.g. due to Qt limitation)? Thanks -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406669] vex amd64->IR: unhandled instruction bytes: 0xC5 0xD4 0xC2 0xED 0xF 0xC5 0xFC 0x29 0xAC 0x24
https://bugs.kde.org/show_bug.cgi?id=406669 Mark Wielaard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Mark Wielaard --- *** This bug has been marked as a duplicate of bug 399287 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399287] amd64 front end: Illegal Instruction vcmptrueps
https://bugs.kde.org/show_bug.cgi?id=399287 Mark Wielaard changed: What|Removed |Added CC||pa...@luccalug.it --- Comment #4 from Mark Wielaard --- *** Bug 406669 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 401397] kmymoney changes group permissions
https://bugs.kde.org/show_bug.cgi?id=401397 --- Comment #5 from bu...@pobox.com --- i ran the AppImage at https://binary-factory.kde.org/job/KMyMoney_Stable_Appimage_Build/lastBuild/artifact/KMyMoney-5.0.3-bd01a5c-x86_64.AppImage and it seems fixed in there -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406669] vex amd64->IR: unhandled instruction bytes: 0xC5 0xD4 0xC2 0xED 0xF 0xC5 0xFC 0x29 0xAC 0x24
https://bugs.kde.org/show_bug.cgi?id=406669 --- Comment #2 from peoro --- Oh, I'm sorry, I wasn't able to find the other bug report. I just built valgrind 3.15.0 and indeed it doesn't fail. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400658] Impossible to walk through all apps or all windows of the current app on Wayland while numlock is enabled
https://bugs.kde.org/show_bug.cgi?id=400658 Rainer Finke changed: What|Removed |Added CC||m...@rainer-finke.de -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 401397] kmymoney changes group permissions
https://bugs.kde.org/show_bug.cgi?id=401397 --- Comment #4 from bu...@pobox.com --- (In reply to Jack from comment #3) > It seems the patch was committed through Phabricator, but the Bug number > there missed one digit, so this bug was not automatically closed. thanks for catching that and sorry -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 406690] New: ksmserver crashes when resuming from suspend, if kiosk mode is used
https://bugs.kde.org/show_bug.cgi?id=406690 Bug ID: 406690 Summary: ksmserver crashes when resuming from suspend, if kiosk mode is used Product: ksmserver Version: 5.15.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kpapad-b...@travelguide.gr Target Milestone: --- Created attachment 119512 --> https://bugs.kde.org/attachment.cgi?id=119512=edit Kiosk settings file placed in /etc/xdg/ SUMMARY ksmserver crashes when resuming from suspend, if kiosk settings are used STEPS TO REPRODUCE 1. Put the attached file in /etc/xdg/kdeglobals 2. Suspend PC 3. Resume by pressing any key OBSERVED RESULT ksmserver crashes upon resume from suspend, all previously open applications are closed. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-47-generic OS Type: 64-bit Processors: 2 × AMD GX-217GA SOC with Radeon(tm) HD Graphics Memory: 3,3 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406319] Hangs/freezes when drag windows to top, right or left edges of the screen
https://bugs.kde.org/show_bug.cgi?id=406319 --- Comment #8 from Vladislav Rubtsov --- Any updates on this bug's status? I suffer from this bug too and I originally opened Bug 406307 with similar report (which was marked as duplicate, though posted earlier). Setting Compositor Rendering backend to "Xrender" as others suggested doesn't fully fix the issue on my end. It just makes freezes occur somewhat less. I would say with "OpenGL" window dragging animations exhibit freezes 90% of the times (was far less frequent before the 5.15.4 update), and with "Xrender" it's only 10-15%, which is of course a lot better, but the bug is still there. Graphics: Card-1: Intel HD Graphics 530 bus-ID: 00:02.0 Card-2: NVIDIA GM107M [GeForce GTX 950M] bus-ID: 01:00.0 Display Server: X.Org 1.20.1 drivers: nvidia FAILED: modesetting Resolution: 1360x768@59.96hz, 1920x1080@60.00hz OpenGL: renderer: GeForce GTX 950M/PCIe/SSE2 version: 4.6.0 NVIDIA 390.116 Direct Render: Yes -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406415] Dock does not always hide
https://bugs.kde.org/show_bug.cgi?id=406415 --- Comment #10 from attila.koszo.offic...@gmail.com --- In a Wayland session the bug couldn't be reproduced. Apparently it's an Xorg bug. Does it mean that the issue is resolved? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #15 from George R. Goffe --- Created attachment 119511 --> https://bugs.kde.org/attachment.cgi?id=119511=edit flat file containing all "kde" rpms and their "current" levels Thank you VERY MUCH for your help/interest/support/WAY COOL CODE. George... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401808] kde fails to actualize a desktop at startup
https://bugs.kde.org/show_bug.cgi?id=401808 --- Comment #14 from George R. Goffe --- Christoph, Thanks for your response AND your question. I have tried several of the .iso images provided by the Fedora project (fc27, fc28, fc29, fc31). I implemented the "nomodeset" change and "my" .xinitrc file with NO problems up to fc31). The problem seems to have started with fc30 which I gave up on in favor of fc31 (rawhide). I have responded with several comments 4, 7, 10 and 12. I am currently running a FC31 system with KDE et. al. at their "current/latest" version(s). I'll add a list of all(?) my kde components to this upgrade. What do you mean by "stock liveCD"? Only one provided by KDE.org? Given my current status, I don't think a out of the box liveCD would show/prove anything. It seems to me that comment 12 and possibly 10 show where I am at this point but I'll summarize with my latest state/info since I do have an update: Current system is FC31 (rawhide). nomodeset is active in the kernel commandline at boot. The startx command works just fine (I'm at runlevel 3 (NO DM active). my .xinitrc is NOT active (I disabled it as part of a debugging effort). To get to this state I disabled all "my" modifications and put them back one at a time. So far, no problems. My next step is to activate my .xinitrc which contains ONLY a "/usr/bin/bash -xv /usr/bin/bash/startkde" command. All these hoops seem to point out the need for something from KDE.org to query all KDE "services or daemons" that should be running AND verify their status (i.e., running). Possibly, some way to start inactive/broken services. Some way to turn on a global and/or individual logging activity within the KDE components. This would help the debugging effort immensely. I will post the results of this change later today. Thanks again for your attention to this problem. George... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 357206] baloo_file crashes in Baloo::PostingDB::get()
https://bugs.kde.org/show_bug.cgi?id=357206 --- Comment #32 from Brett Keller --- Created attachment 119510 --> https://bugs.kde.org/attachment.cgi?id=119510=edit New crash information added by DrKonqi baloo_file (5.44.0) using Qt 5.9.5 - What I was doing when the application crashed: Happens immediately after login. I don't really even have that many files on this system to index: $ balooctl indexSize Actual Size: 12.02 MiB Expected Size: 6.77 MiB PostingDB: 1.18 MiB17.426 % PosistionDB: 1.39 MiB20.542 % DocTerms: 1.05 MiB15.522 % DocFilenameTerms: 1.03 MiB15.176 % DocXattrTerms:0 B 0.000 % IdTree: 168.00 KiB 2.424 % IdFileName: 924.00 KiB13.329 % DocTime: 644.00 KiB 9.290 % DocData:0 B 0.000 % ContentIndexingDB:0 B 0.000 % FailedIdsDB:0 B 0.000 % MTimeDB: 220.00 KiB 3.174 % -- Backtrace (Reduced): #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:427 #7 0x7f42e75a0973 in memcpy (__len=18446744073126832784, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f42dd446a47, arr=...) at ./src/codecs/postingcodec.cpp:42 #9 0x7f42e75923e4 in Baloo::PostingDB::get (this=this@entry=0x7f42dd446b30, term=...) at ./src/engine/postingdb.cpp:100 #10 0x7f42e759e060 in Baloo::WriteTransaction::commit (this=0x7f02d0003400) at ./src/engine/writetransaction.cpp:259 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 357206] baloo_file crashes in Baloo::PostingDB::get()
https://bugs.kde.org/show_bug.cgi?id=357206 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406689] New: many trashbin icons multiple trash icon too many trashbins
https://bugs.kde.org/show_bug.cgi?id=406689 Bug ID: 406689 Summary: many trashbin icons multiple trash icon too many trashbins Product: plasmashell Version: 5.15.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: k...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 119509 --> https://bugs.kde.org/attachment.cgi?id=119509=edit picture of desktop My desktop shows multiple trashbin icons, but only one of them can be clicked. https://i.imgur.com/CavnBLA.jpg Not sure how to reproduce. I'm using the Nvidia proprietary driver, and often get the message that the graphical effects have been reset. The trashbins don't go away when i right-click on the desktop and select "Arbeitsfläche neu aufbauen", which i would translate as "Rebuild desktop". -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 405313] kalarm freezes in gnome
https://bugs.kde.org/show_bug.cgi?id=405313 --- Comment #15 from stepnj...@gmail.com --- Additional information that 'might' help David.. Found some files in /tmp/akonadi-pierre.ChXM9m srwxrwxr-x 1 pierre pierre0 avr 17 16:27 akonadiserver-cmd.socket srwxrwxr-x 1 pierre pierre0 avr 17 16:27 akonadiserver-ntf.socket -rw-r- 1 pierre pierre5 avr 17 16:27 mysql.pid srwxrwxrwx 1 pierre pierre0 avr 17 16:27 mysql.socket -rw--- 1 pierre pierre5 avr 17 16:27 mysql.socket.lock -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 406456] Falkon crashes on NEON with HWE enabled and nouveau driver
https://bugs.kde.org/show_bug.cgi?id=406456 Juraj changed: What|Removed |Added CC||sgd.or...@gmail.com --- Comment #2 from Juraj --- It does not like nouveau. https://bugs.kde.org/show_bug.cgi?id=397389#c6 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 406688] New: Konversation crashed on opening laptop lid
https://bugs.kde.org/show_bug.cgi?id=406688 Bug ID: 406688 Summary: Konversation crashed on opening laptop lid Product: konversation Version: 1.7.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: si...@ergotech.com Target Milestone: --- Application: konversation (1.7.5) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 5.0.7-200.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: - What I was doing when the application crashed: My laptop had the lid closed (not suspended) and I was moving from my advisor's office to my desk I sat down at my desk, plugged in the laptop, and logged in, to find that Konversation had crashed The wifi in my building is acheived with the use of many access points, and my advisor's office is at the end of a hall, so possibly my laptop switched APs somewhere in my walk The crash does not seem to be reproducible. -- Backtrace: Application: Konversation (konversation), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f39aee43940 (LWP 5305))] Thread 5 (Thread 0x7f3998c9e700 (LWP 5720)): #0 0x7f39b1f8172c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f39990928bb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7f39990925fb in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7f39b1f7b58e in start_thread () from /lib64/libpthread.so.0 #4 0x7f39b228f683 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f399adee700 (LWP 5541)): #0 0x7f39b2933288 in timerSourcePrepareHelper (src=, timeout=0x7f399adeda84) at kernel/qeventdispatcher_glib.cpp:133 #1 0x7f39b2933312 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:165 #2 0x7f39af6fd8e9 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7f39af6fe2db in ?? () from /lib64/libglib-2.0.so.0 #4 0x7f39af6fe4d0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f39b29335ab in QEventDispatcherGlib::processEvents (this=0x7f398c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f39b28e1e0b in QEventLoop::exec (this=this@entry=0x7f399adedc60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f39b2749e86 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f39b27532fb in QThreadPrivate::start (arg=0x5563938de930) at thread/qthread_unix.cpp:367 #9 0x7f39b1f7b58e in start_thread () from /lib64/libpthread.so.0 #10 0x7f39b228f683 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f399bfff700 (LWP 5524)): #0 0x7f39b293325c in timerSourcePrepareHelper (src=0x7f3994004c90, timeout=0x7f399bffea54) at kernel/qeventdispatcher_glib.cpp:137 #1 0x7f39b2933312 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:165 #2 0x7f39af6fd8e9 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7f39af6fe2db in ?? () from /lib64/libglib-2.0.so.0 #4 0x7f39af6fe4d0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f39b29335ab in QEventDispatcherGlib::processEvents (this=0x7f3994000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f39b28e1e0b in QEventLoop::exec (this=this@entry=0x7f399bffec30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f39b2749e86 in QThread::exec (this=this@entry=0x7f39b2c04060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f39b2b88f89 in QDBusConnectionManager::run (this=0x7f39b2c04060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7f39b27532fb in QThreadPrivate::start (arg=0x7f39b2c04060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #10 0x7f39b1f7b58e in start_thread () from /lib64/libpthread.so.0 #11 0x7f39b228f683 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f39a1bbc700 (LWP 5438)): #0 0x7f39b22843f1 in poll () from /lib64/libc.so.6 #1 0x7f39b197b39f in ?? () from /lib64/libxcb.so.1 #2 0x7f39b197d01a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f39a1d30bf9 in ?? () from /lib64/libQt5XcbQpa.so.5 #4 0x7f39b27532fb in QThreadPrivate::start (arg=0x5563937eb9d0) at thread/qthread_unix.cpp:367 #5 0x7f39b1f7b58e in start_thread () from /lib64/libpthread.so.0 #6 0x7f39b228f683 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f39aee43940 (LWP 5305)): [KCrash Handler] #6
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 kaito.li...@gmail.com changed: What|Removed |Added CC||kaito.li...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406687] New: Plasma crashes when I click "Audio volume" section of plasma-pa settings
https://bugs.kde.org/show_bug.cgi?id=406687 Bug ID: 406687 Summary: Plasma crashes when I click "Audio volume" section of plasma-pa settings Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. open plasma-pa settings 2. click "Audio volume" section 3. OBSERVED RESULT plasma crashes EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 Thread 14 (Thread 0x7f5c137fe700 (LWP 19965)): #0 0x7f5c657e29f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b4c76c3e54) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b4c76c3e00, cond=0x55b4c76c3e28) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b4c76c3e28, mutex=0x55b4c76c3e00) at pthread_cond_wait.c:655 #3 0x7f5c68cceb4b in QWaitConditionPrivate::wait (deadline=..., this=0x55b4c76c3e00) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55b4c76b3c60, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f5c68ccee59 in QWaitCondition::wait (this=this@entry=0x55b4c76b3c68, mutex=mutex@entry=0x55b4c76b3c60, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f5c6d00bda8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55b4c76b3c58) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55b4c76b3be0) at scenegraph/qsgthreadedrenderloop.cpp:709 #8 0x7f5c6d00c1da in QSGRenderThread::run (this=0x55b4c76b3be0) at scenegraph/qsgthreadedrenderloop.cpp:738 #9 0x7f5c68cc7bc2 in QThreadPrivate::start (arg=0x55b4c76b3be0) at thread/qthread_unix.cpp:361 #10 0x7f5c657dc6db in start_thread (arg=0x7f5c137fe700) at pthread_create.c:463 #11 0x7f5c685c788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f5c116b1700 (LWP 19964)): #0 0x7f5c685babf9 in __GI___poll (fds=0x7f5c040031e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5c62422539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5c6242264c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5c68efd13f in QEventDispatcherGlib::processEvents (this=0x7f5c04003c20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4 0x7f5c68e9e64a in QEventLoop::exec (this=this@entry=0x7f5c116b0d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f5c68cc641a in QThread::exec (this=this@entry=0x55b4c171d410) at thread/qthread.cpp:531 #6 0x7f5c6cac12e5 in QQmlThreadPrivate::run (this=0x55b4c171d410) at qml/ftw/qqmlthread.cpp:148 #7 0x7f5c68cc7bc2 in QThreadPrivate::start (arg=0x55b4c171d410) at thread/qthread_unix.cpp:361 #8 0x7f5c657dc6db in start_thread (arg=0x7f5c116b1700) at pthread_create.c:463 #9 0x7f5c685c788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f5c38d0d700 (LWP 19819)): #0 0x7f5c657e29f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b4c1810964) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b4c1810910, cond=0x55b4c1810938) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b4c1810938, mutex=0x55b4c1810910) at pthread_cond_wait.c:655 #3 0x7f5c68cceb4b in QWaitConditionPrivate::wait (deadline=..., this=0x55b4c1810910) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55b4c4075700, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f5c68ccee59 in QWaitCondition::wait (this=this@entry=0x55b4c4075708, mutex=mutex@entry=0x55b4c4075700, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f5c6d00bda8 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55b4c40756f8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55b4c4075680) at scenegraph/qsgthreadedrenderloop.cpp:709 #8 0x7f5c6d00c1da in QSGRenderThread::run (this=0x55b4c4075680) at scenegraph/qsgthreadedrenderloop.cpp:738 #9 0x7f5c68cc7bc2 in QThreadPrivate::start (arg=0x55b4c4075680) at thread/qthread_unix.cpp:361 #10 0x7f5c657dc6db in start_thread (arg=0x7f5c38d0d700) at pthread_create.c:463 #11 0x7f5c685c788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f5c13fff700 (LWP 19813)): #0
[kwin] [Bug 406686] The kwin plugin qpa don't build
https://bugs.kde.org/show_bug.cgi?id=406686 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Severity|critical|normal Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- It currently builds on our CI and my system. It's in your /usr/include/c++/8.3.0/cstdlib when it fails, which means we're getting to the right path from kwin. I don't see anything that kwin is doing wrong. I'm afraid you're going to have investigate this. If you find anything, please open a followup. We can probably remove the fixx11 includes, it seems a bit pointless to include them from a wayland only QPA. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 398975] Muted designation is inconsistent
https://bugs.kde.org/show_bug.cgi?id=398975 --- Comment #9 from Patrick Silva --- This issue seems solved on neon dev unstable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406686] New: The kwin plugin qpa don't build
https://bugs.kde.org/show_bug.cgi?id=406686 Bug ID: 406686 Summary: The kwin plugin qpa don't build Product: kwin Version: 5.15.4 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: scene-qpainter Assignee: kwin-bugs-n...@kde.org Reporter: gustavo.schen...@gmail.com Target Milestone: --- SUMMARY The kwin plugin qpa don't build OBSERVED RESULT [ 86%] Building CXX object plugins/qpa/CMakeFiles/KWinQpaPlugin.dir/KWinQpaPlugin_autogen/mocs_compilation.cpp.o In file included from /usr/include/c++/8.3.0/bits/stl_algo.h:59, from /usr/include/c++/8.3.0/algorithm:62, from /usr/include/qt5/QtCore/qglobal.h:142, from /usr/include/qt5/QtCore/QtGlobal:1, from /usr/include/KF5/KWindowSystem/fixx11h.h:28, from /tmp/kde_build/plasma/kwin-5.15.4/build/plugins/qpa/KWinQpaPlugin_autogen/EWIEGA46WW/../../../../../plugins/qpa/integration.h:26, from /tmp/kde_build/plasma/kwin-5.15.4/build/plugins/qpa/KWinQpaPlugin_autogen/EWIEGA46WW/moc_integration.cpp:9, from /tmp/kde_build/plasma/kwin-5.15.4/build/plugins/qpa/KWinQpaPlugin_autogen/mocs_compilation.cpp:2: /usr/include/c++/8.3.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next ^~ compilation terminated. make[2]: *** [plugins/qpa/CMakeFiles/KWinQpaPlugin.dir/build.make:63: plugins/qpa/CMakeFiles/KWinQpaPlugin.dir/KWinQpaPlugin_autogen/mocs_compilation.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:7925: plugins/qpa/CMakeFiles/KWinQpaPlugin.dir/all] Error 2 make: *** [Makefile:130: all] Error 2 plasma:kwin failed to build. EXPECTED RESULT The plugin be built SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware Current 5.15.4 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57 Qt Version: 5.12.3 ADDITIONAL INFORMATION I tried apply the patch https://cgit.kde.org/kwin.git/commit/?id=6e1655e3cce082b2e7d0daf21dc58bbe3d4524f2 to check if it would make through, but nothing changed. I am using multilib package but I tried remove it and install only pure gcc, but again nothing changed. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 406685] New: KDE Instability of application termination
https://bugs.kde.org/show_bug.cgi?id=406685 Bug ID: 406685 Summary: KDE Instability of application termination Product: ktorrent Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: shopma...@btinternet.com Target Milestone: --- Application: ktorrent (5.1.0) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-47-generic x86_64 Distribution: Ubuntu 18.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Killing orphaned Ktorrent process, as otherwise Ktorrent wound not start. I have to do this every time after cloasing Ktorrent. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63091ef800 (LWP 12125))] Thread 3 (Thread 0x7f62eadee700 (LWP 12131)): #0 0x7f6303336bf9 in __GI___poll (fds=0x7f62dc002ee0, nfds=1, timeout=9503) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f62fd135539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fd13564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f63042359bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f63041daa1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6303ff923a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6303ffe17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f62fec396db in start_thread (arg=0x7f62eadee700) at pthread_create.c:463 #8 0x7f630334388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f62ebfff700 (LWP 12129)): #0 0x7f63033320b4 in __GI___libc_read (fd=11, buf=0x7f62ebffeb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f62fd179cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f62fd135027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f62fd1354e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f62fd13564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f63042359bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f63041daa1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6303ff923a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6305662d45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f6303ffe17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f62fec396db in start_thread (arg=0x7f62ebfff700) at pthread_create.c:463 #11 0x7f630334388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f63091ef800 (LWP 12125)): [KCrash Handler] #6 0x7f6303336bf9 in __GI___poll (fds=0x5624c78e58e0, nfds=5, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 #7 0x7f62fd135539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f62fd13564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f630423599f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f63041daa1a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f63041e3ac4 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x5624c62d202a in () #13 0x7f6303243b97 in __libc_start_main (main=0x5624c62cfd60, argc=1, argv=0x7fffb1835fd8, init=, fini=, rtld_fini=, stack_end=0x7fffb1835fc8) at ../csu/libc-start.c:310 #14 0x5624c62d2a0a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #6 from Laurent Montel --- Git commit 5f46365914929620906d3ed565fe058bc71f6c7e by Laurent Montel. Committed on 19/04/2019 at 18:43. Pushed by mlaurent into branch 'master'. Fix markdown group config M +2-2 kmail/editorconvertertextplugins/markdown/markdownconfigurewidget.cpp M +1-1kmail/editorconvertertextplugins/markdown/markdowninterface.cpp M +1-0kmail/grammarplugins/languagetool/CMakeLists.txt A +14 -0 kmail/grammarplugins/languagetool/kconf_update/languagetool_kmail.upd https://commits.kde.org/kdepim-addons/5f46365914929620906d3ed565fe058bc71f6c7e -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #5 from Laurent Montel --- > By the way, having the possibility to easily change the LanguageTools > language setting in composer would be great as many users write emails in 2+ > languages :) Ok it seems a good idea. I will look at how to implement it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406682] cannot change to next/previous track by moving the mouse wheel on a systray icon
https://bugs.kde.org/show_bug.cgi?id=406682 --- Comment #2 from David Edmundson --- Replied on their ticket -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #4 from Laurent Montel --- (In reply to avlas from comment #0) > I've download and set up a local server for LanguageTools to test this new > functionality (which is very cool, btw). > > This works fine, but Kmail setting about the location of the server is lost > after quitting in favor of the default remote one. > > Also, it seems I cannot set English (US) instead of English. When I do, the > change reverts itself. Indeed It seems that there is a bug. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel --- > But I did find a typo in Markdown settings that appear in the [Mardown] > section (note the missing 'k') Indeed but it's not a problem as all code use Mardown. I will fix it soon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406682] cannot change to next/previous track by moving the mouse wheel on a systray icon
https://bugs.kde.org/show_bug.cgi?id=406682 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- We send the SNI scroll. If they don't pick it up that's an application bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406648] Crash when creating a text
https://bugs.kde.org/show_bug.cgi?id=406648 --- Comment #1 from acc4commissi...@gmail.com --- Ugh... It seems to happen a lot when I have to use the text tool intensively but I can't figure out what particular status makes it happen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often
https://bugs.kde.org/show_bug.cgi?id=406426 Oded Arbel changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #19 from Oded Arbel --- (In reply to Wolfgang Bauer from comment #18) > Maybe fixed by > https://cgit.kde.org/kglobalaccel.git/commit/ > ?id=78a711361db3a5156f511eab89ff7ebbc86b9125 then? > (it changes ./src/runtime/component.cpp:163...) Could be, I thought that this patch is included in libkf5globalaccel5-5.57.0+p19.04+git20190418.0604-0, but looking at the trace again - the above mentioned fix increases the line count so if expect the line number in the trace to change from my first crash to the last one, such it didn't. I'll test again. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406575] Stopping an Activity should not attempt to close Okular, even with tabs opened
https://bugs.kde.org/show_bug.cgi?id=406575 --- Comment #3 from Øystein Steffensen-Alværvik --- "possible when using Okular *windowed*" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406575] Stopping an Activity should not attempt to close Okular, even with tabs opened
https://bugs.kde.org/show_bug.cgi?id=406575 --- Comment #2 from Øystein Steffensen-Alværvik --- Why was this marked not a bug? It prevents stopping an Activity when using Okular with tabs, so the user can't resume the Activity with the documents (which is possible when using Okular *without* -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 406672] Application startup delay with KDE runtime
https://bugs.kde.org/show_bug.cgi?id=406672 --- Comment #2 from Peter Eszlari --- Now I tested this under GNOME with xdg-desktop-portal-gtk and there I have no delay at all, also with the 5.12 runtime. So the problematic combination is: xdg-desktop-portal-kde + KDE runtime 5.12 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 395695] [Privacy] Private activity usage is displayed by KRunner in standard activities
https://bugs.kde.org/show_bug.cgi?id=395695 Øystein Steffensen-Alværvik changed: What|Removed |Added Version|5.13.1 |5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 406321] ERR-8/ERR-5 importing qfx file, "More than one object returned in 'v_account' for 't_number='''"
https://bugs.kde.org/show_bug.cgi?id=406321 Stephane MANKOWSKI changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://commits.kde.org/skr |https://commits.kde.org/skr |ooge/2471a3eadff09f3754e02f |ooge/600a94a733a4bb32b29e97 |9e2745213c68ccb298 |329a36d9f34dc88b72 Status|REOPENED|RESOLVED --- Comment #13 from Stephane MANKOWSKI --- Git commit 600a94a733a4bb32b29e97329a36d9f34dc88b72 by Stephane MANKOWSKI. Committed on 19/04/2019 at 17:06. Pushed by smankowski into branch 'master'. M +3-3plugins/import/skrooge_import_ofx/skgimportpluginofx.cpp A +12 -0tests/input/skgtestimportofx/406321_2.ofx M +14 -0tests/skgbankmodelertest/skgtestimportofx.cpp https://commits.kde.org/skrooge/600a94a733a4bb32b29e97329a36d9f34dc88b72 -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 406684] New: backend is not compatible with up-to-date flatpak package of octave
https://bugs.kde.org/show_bug.cgi?id=406684 Bug ID: 406684 Summary: backend is not compatible with up-to-date flatpak package of octave Product: cantor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: octave-backend Assignee: alexander.se...@web.de Reporter: jsar...@gmail.com CC: alexanderrie...@gmail.com Target Milestone: --- there are problems with dependencies and system folders that are not visible because of how flatpak containers work, so wondering if the easiest way may be offering a flatpak version of cantor... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406683] New: 4 "undefined" entries on Edit Metadata dialog.
https://bugs.kde.org/show_bug.cgi?id=406683 Bug ID: 406683 Summary: 4 "undefined" entries on Edit Metadata dialog. Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: libreaj...@gmail.com Target Milestone: --- Created attachment 119508 --> https://bugs.kde.org/attachment.cgi?id=119508=edit a screenshot of the bug Edit Metadata dialog has 4 "Undefined" entries on the Light source dropdown list STEPS TO REPRODUCE 1. Choose Layer - Edit Metadata - Exif - Postprogressing 2. Click on "Light source" dropdown list. SOFTWARE/OS VERSIONS Krita Version: 4.2.0-pre-alpha Languages: en Hidpi: true Qt Version (compiled): 5.9.5 Version (loaded): 5.9.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.15.0-48-lowlatency Pretty Productname: Ubuntu 18.04.2 LTS Product Type: ubuntu Product Version: 18.04 Hardware Information GPU Acceleration: auto Memory: 15923 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406637] Duplicates "Search in" Doesn't Show Collection Name Upon First Selection
https://bugs.kde.org/show_bug.cgi?id=406637 Maik Qualmann changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam/6d1190d864e8f1cc0be406 ||f8e6e146ebcddbf94e Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Maik Qualmann --- Git commit 6d1190d864e8f1cc0be406f8e6e146ebcddbf94e by Maik Qualmann. Committed on 19/04/2019 at 16:49. Pushed by mqualmann into branch 'master'. Workaround for QLineEdit text when QComboBox loses focus FIXED-IN: 6.2.0 M +8-0core/libs/album/widgets/albumselectcombobox.cpp https://commits.kde.org/digikam/6d1190d864e8f1cc0be406f8e6e146ebcddbf94e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406682] cannot change to next/previous track by moving the mouse wheel on a systray icon
https://bugs.kde.org/show_bug.cgi?id=406682 Patrick Silva changed: What|Removed |Added Summary|cannot change to|cannot change to |next/previous track by |next/previous track by |moving the mouse whell on a |moving the mouse wheel on a |systray icon|systray icon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406682] New: cannot change to next/previous track by moving the mouse whell on a systray icon
https://bugs.kde.org/show_bug.cgi?id=406682 Bug ID: 406682 Summary: cannot change to next/previous track by moving the mouse whell on a systray icon Product: plasmashell Version: 5.15.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 SUMMARY I use Strawberry player, it has a feature called "Scroll over icon to change track". As you can read in the bug report below, such feature works on XFCE but it does not on KDE Plasma. https://github.com/jonaski/strawberry/issues/51 Maybe there is a bug with Plasma? STEPS TO REPRODUCE 1. make sure that both tray icon and "Scroll over icon to change track" option are enabled in strawberry settings (ctrl+P) 2. add some music files to strawberry playlist and play any of them 3. hover over strawberry icon in systray and move the mouse wheel OBSERVED RESULT nothing happens EXPECTED RESULT stranwberry changes to the next/previous track SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402161] Backtab (Shift+Tab) is inhibited in Yakuake
https://bugs.kde.org/show_bug.cgi?id=402161 --- Comment #1 from NiLuJe --- This is still happening with Konsole 19.04.0, Frameworks 5.57.0, Plasma 5.15.4 & Qt 5.12.2 With a few things to note: In Konsole, I obviously had to disable the "Next View Container" shortcut, because it defaults to Shift+Tab ;). In Yakuake, Ctrl+Shift+Tab behaves as Shift+Tab ought to. This isn't the case in Konsole, where Shift+Tab does still work, once the conflicting shortcut is gone, but Ctrl+Shift+Tab does not. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402161] Backtab (Shift+Tab) is inhibited in Yakuake
https://bugs.kde.org/show_bug.cgi?id=402161 NiLuJe changed: What|Removed |Added Version|18.12.1 |19.04.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406569] Elide tab title on the left when displaying full paths
https://bugs.kde.org/show_bug.cgi?id=406569 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Nate Graham --- Yep, I get it. Here's a patch: https://phabricator.kde.org/D20689 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406681] New: Unrecognized instruction _dispatch_kq_poll (in /usr/lib/system/libdispatch.dylib)
https://bugs.kde.org/show_bug.cgi?id=406681 Bug ID: 406681 Summary: Unrecognized instruction _dispatch_kq_poll (in /usr/lib/system/libdispatch.dylib) Product: valgrind Version: 3.15 SVN Platform: Compiled Sources OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: eub...@virginia.edu Target Milestone: --- Created attachment 119507 --> https://bugs.kde.org/attachment.cgi?id=119507=edit Full output of valgrind -v SUMMARY Trying to memcheck my executable compiled under mpicxx gives the following error: ==68279== valgrind: Unrecognised instruction at address 0x100764b7b. ==68279==at 0x100764B7B: _dispatch_kq_poll (in /usr/lib/system/libdispatch.dylib) My code runs fine outside valgrind, it is stable, and there are no warnings about bad jumps before the error in valgrind. The instruction seems to be in a system library, so I think the instruction is legitimate. OBSERVED RESULT Full output of valgrind -v is attached. EXPECTED RESULT SOFTWARE/OS VERSIONS Valgrind 3.15.0 downloaded and built today, tested with 'valgrind ls -L'. mpicxx --version: Apple LLVM version 10.0.0 (clang-1000.11.45.5) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin My executable compiled with: mpicxx -std=c++11 -g -O3 ... -lstdc++ uname -a: Darwin Biocomplexitys-Eubank.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Dec 20 21:47:19 PST 2018; root:xnu-4570.71.22~1/RELEASE_X86_64 x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 406657] Add XSD support to XML plugins
https://bugs.kde.org/show_bug.cgi?id=406657 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Severity|normal |wishlist --- Comment #1 from Christoph Cullmann --- Valid wish, patches welcome. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 406673] Security: Sudo Restriction Bypass
https://bugs.kde.org/show_bug.cgi?id=406673 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED CC||cullm...@kde.org Resolution|--- |NOT A BUG --- Comment #1 from Christoph Cullmann --- This message and error handling is only to avoid accidental use as root. If you actively workaround by resetting the env var, it will not work. I don't see an issue with that, most other X11 applications don't warn at all and let it be the users responsibility to don't run them as root. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405828] Budget problems
https://bugs.kde.org/show_bug.cgi?id=405828 --- Comment #3 from Mattia --- Created attachment 119506 --> https://bugs.kde.org/attachment.cgi?id=119506=edit Budget widget screenshot (In reply to Thomas Baumgart from comment #2) > I may not completely understand your comment, but showing overruns in this > widget was never intended. Can you elaborate why you think it is not > working? How would you envision the overrun should be identified? In KMyMoney 4.x the widget used to show the monthly summary and the categories for which the budget was overrun in the month. Now it only shows the monthly summary, but in the categories table it always shows "No budget categories have been overrun" even if there are actually some categories for which the budget has been overrun. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405317] Cannot find file just created in home directory
https://bugs.kde.org/show_bug.cgi?id=405317 --- Comment #23 from dagobert...@mailbox.org --- (In reply to Stefan Brüns from comment #22) > > $> cat /proc//fd > > That should have been "ls /proc//fd" > > Separate the strace output from the baloo_file output by using: > > $> strace -einotify_add_watch -o baloo_file_strace.txt baloo_file I don't really know, what I am doing right now but I try to do it anyway: ~$ ps -e | grep -i baloo 1302 ?00:00:10 baloo_file 1813 ?00:00:00 baloorunner ~$ ls /proc/1302/fd 0 1 10 11 12 15 17 18 2 3 4 5 6 7 8 9 ~$ killall baloo_file ~$ strace -einotify_add_watch -o baloo_file_strace.txt baloo_file KCatalog being used without a Q*Application instance. Some translations won't work -- You are receiving this mail because: You are watching all bug changes.
[kmail] [Bug 178402] JJ: custom font settings overwritten new message list settings
https://bugs.kde.org/show_bug.cgi?id=178402 Peter Hatina changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #19 from Peter Hatina --- Any updates? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406637] Duplicates "Search in" Doesn't Show Collection Name Upon First Selection
https://bugs.kde.org/show_bug.cgi?id=406637 --- Comment #3 from hardy.pub...@gmail.com --- Created attachment 119505 --> https://bugs.kde.org/attachment.cgi?id=119505=edit Demo of problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406637] Duplicates "Search in" Doesn't Show Collection Name Upon First Selection
https://bugs.kde.org/show_bug.cgi?id=406637 hardy.pub...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from hardy.pub...@gmail.com --- I tried both the following but no improvement: digiKam-6.1.0-Win64.exe digiKam-6.2.0-git-20190417T114700-Win64.exe -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting
https://bugs.kde.org/show_bug.cgi?id=406256 Carl Love changed: What|Removed |Added Attachment #119258|0 |1 is obsolete|| --- Comment #3 from Carl Love --- Created attachment 119504 --> https://bugs.kde.org/attachment.cgi?id=119504=edit Updated patch to fix issues with dnormal values Updated patch, needs review by Julian -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 406627] Allow the user to define default settings in print dialog
https://bugs.kde.org/show_bug.cgi?id=406627 --- Comment #6 from wolfgang.h...@123jederzeit.de --- Hallo Nate, thanks for asking: for me are important: page margins (left, right, top, down) page orientation Alsowould it be nice to have one more placeholder for header-line or footer-line like %y, %U, %p, ... additional variable %PageCount - >for example page %p of %PageCount printed as for example page 3 of 6 Regards Wolfgang -Urspr�ngliche Nachricht- Von: Nate Graham An: wolfgang.h...@123jederzeit.de Gesendet: Donnerstag, 18. April 2019 21:14 Betreff: [kate] [Bug 406627] Allow the user to define default settings in print dialog > https://bugs.kde.org/show_bug.cgi?id=406627 > Nate Graham changed: >What|Removed |Added > > Summary|UBUNTU 18.04 - Kate - would |Allow the user to define >|be nice to have more|default settings in print >|control in parameter for|dialog >|printouts | > --- Comment #5 from Nate Graham --- > Thanks, that's helpful. Can you tell me which settings you would like to > define > defaults for? Just the printer margins? Or any others? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 401397] kmymoney changes group permissions
https://bugs.kde.org/show_bug.cgi?id=401397 Jack changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||f328d389f6af43cadf16fd094f2 ||cbfd12e020d22 Version Fixed In||5.0.4 Status|REPORTED|RESOLVED --- Comment #3 from Jack --- It seems the patch was committed through Phabricator, but the Bug number there missed one digit, so this bug was not automatically closed. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 220496] Preview of pictures when content type does not match extension
https://bugs.kde.org/show_bug.cgi?id=220496 --- Comment #26 from Nate Graham --- That's odd. Thanks folks. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 406679] joystick icon looks a black ball
https://bugs.kde.org/show_bug.cgi?id=406679 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Yeah, it kind of does. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406680] LanguageTools: kmail restart loses configuration of local server address in favor of default remote
https://bugs.kde.org/show_bug.cgi?id=406680 --- Comment #2 from avlas --- (In reply to avlas from comment #1) > In the meantime, to work around this, how should I manually add the > LanguageTools server and language setting to kontactrc? Tried to figure it out checking kontactrc, but couldn't find the way. But I did find a typo in Markdown settings that appear in the [Mardown] section (note the missing 'k') -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 406632] Feature request for Discover
https://bugs.kde.org/show_bug.cgi?id=406632 --- Comment #5 from Nate Graham --- Discover shouldn't interfere with other network activities. Aleix, any idea what might be going on here? -- You are receiving this mail because: You are watching all bug changes.
