[kdevelop] [Bug 389418] Option to not close open program does not work
https://bugs.kde.org/show_bug.cgi?id=389418 Christoph Roickchanged: What|Removed |Added Latest Commit||d896e7489b743d8691e480378c8 ||6f2b1ee0524b0 CC||chris...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Christoph Roick --- There is a fix for this in the current master branch, but it is not part of 5.2. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 389962] Lock screen does not show Picture of the Day
https://bugs.kde.org/show_bug.cgi?id=389962 --- Comment #7 from Shmerl--- And I suppose since lock screen has no network access, in order to enable something like picture of the day, there should be an explicit KDE service / scheduled job "picture of the day" that user can enable, and lock screen can rely on that service to update the image appropriately. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 390652] Capturing the active window fails if compositing is off and the window touches a screen border
https://bugs.kde.org/show_bug.cgi?id=390652 --- Comment #5 from Nate Graham--- Excellent idea. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390760] New: Wayland crashes to SDDM greeter
https://bugs.kde.org/show_bug.cgi?id=390760 Bug ID: 390760 Summary: Wayland crashes to SDDM greeter Product: kwin Version: 5.12.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: nortex...@gmail.com Target Milestone: --- Every couple of days or so, my wayland session crashes to the SDDM greeter. This *never* happens in an X session. I think it's caused by xwayland, but this is just a hunch, since I have *no* debugging info. My hunch is caused by what I'm often doing when I get kicked out of a session, which is often something in Firefox or Thunderbird. xlsclients lists dropbox, telegram, thunderbird, and firefox. I am happy to provide any information I can. This has been happening to me for a good number of plasma versions. Hardware: Intel i5 7200U (Kaby Lake), modesetting driver. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 389413] Krusader crashes when entering directories with read errors
https://bugs.kde.org/show_bug.cgi?id=389413 --- Comment #6 from Nikita Melnichenko--- Interesting. What does `readlink core` output? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 390718] Tab switching is not working
https://bugs.kde.org/show_bug.cgi?id=390718 Nikita Melnichenkochanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||nikita+...@melnichenko.name --- Comment #1 from Nikita Melnichenko --- It works fine on stable v2.6.0. Please try this version and report back. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 389019] No Bluetooth devices in tray after suspend
https://bugs.kde.org/show_bug.cgi?id=389019 Dr. Chapatinchanged: What|Removed |Added CC||bugsefor...@gmx.com Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Dr. Chapatin --- closing because comment 3. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 381407] SDDM's Breeze theme should have a prettier background than just a flat blue color
https://bugs.kde.org/show_bug.cgi?id=381407 Michael Dchanged: What|Removed |Added CC||nortex...@gmail.com --- Comment #5 from Michael D --- The default blue is ugly, however, the Breeze Dark window background color, $31363b, looks quite nice for both SDDM theme and lock screen. I prefer a solid color over a potentially noisy wallpaper--the right color just needs to be chosen. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 390761] New: Expose Libinput middle click button/ emulation settings
https://bugs.kde.org/show_bug.cgi?id=390761 Bug ID: 390761 Summary: Expose Libinput middle click button/ emulation settings Product: Touchpad-KCM Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm Assignee: rajeeshknamb...@gmail.com Reporter: n...@kde.org Target Milestone: --- The libinput touchpad KCM needs user-visible settings to: - Turn on and off Libinput's virtual middle-click button - Turn on and off middle-click emulation (e.g. simulate middle click when both physical touchpad buttons (if available) are pressed at the same time On X11, these settings can be toggled via `xinput`, but on Wayland, the only way to do it is if the GUI configuration tool exposes the features. See also https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/82 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383567] Details section is empty in 'Do not know which files to compare.' window
https://bugs.kde.org/show_bug.cgi?id=383567 Nikita Melnichenkochanged: What|Removed |Added CC||nikita+...@melnichenko.name Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Nikita Melnichenko --- To repro: set current items on both sides to parent dir "..", issue Compare by Content action, then press Details in the error dialog. Details should be visible. The layout of the dialog is ugly even after resize. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383668] Krusader blocks ejecting of removable drive by self 'krusader' process if drive is opened in it's tab
https://bugs.kde.org/show_bug.cgi?id=383668 --- Comment #5 from Alexander Mentyu--- Created attachment 110833 --> https://bugs.kde.org/attachment.cgi?id=110833=edit navigator-bar-safely-remove -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383668] Krusader blocks ejecting of removable drive by self 'krusader' process if drive is opened in it's tab
https://bugs.kde.org/show_bug.cgi?id=383668 --- Comment #3 from Alexander Mentyu--- Firstly mount the drive and open it in Krusader - than by left clicking on Media Button - and then right click on mounted drive and choosing 'Unmount' or by left clicking on Navigator bar and choosing 'Safely Remove' menu option -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383668] Krusader blocks ejecting of removable drive by self 'krusader' process if drive is opened in it's tab
https://bugs.kde.org/show_bug.cgi?id=383668 --- Comment #4 from Alexander Mentyu--- Created attachment 110832 --> https://bugs.kde.org/attachment.cgi?id=110832=edit media-button-unmount -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 390763] New: Stuck at authorizing token
https://bugs.kde.org/show_bug.cgi?id=390763 Bug ID: 390763 Summary: Stuck at authorizing token Product: Akonadi Version: 5.7.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Gmail resource Assignee: dvra...@kde.org Reporter: ovidiu@gmail.com CC: kdepim-b...@kde.org Target Milestone: --- While trying to setup a new email account on a fresh Fedora install, after logging into Google and authorizing Akonadi to access my email, the wizzard stops at the last step showing: Authorizing token. This should take just a moment... I've left it over night just in case. Nothing changed. Please let me know what to investigate to provide better feedback on the issue. I've tried deleting the agent from akonadiconsole, and adding it again. The same thing happens every time. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383668] Krusader blocks ejecting of removable drive by self 'krusader' process if drive is opened in it's tab
https://bugs.kde.org/show_bug.cgi?id=383668 Nikita Melnichenkochanged: What|Removed |Added CC||nikita+...@melnichenko.name Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Nikita Melnichenko --- How do you eject a drive from Krusader itself? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 390300] Amarok Crashes on Kubuntu 16.04.3 LTS with KDE 5.8.8 LTS
https://bugs.kde.org/show_bug.cgi?id=390300 --- Comment #2 from David Muya--- The bug reporting mechanism reports that a useful backtrace could not be generated. But I managed to get these. Please find attached. On Sun, Feb 18, 2018 at 2:28 AM, Myriam Schweingruber < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=390300 > > Myriam Schweingruber changed: > >What|Removed |Added > > > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |BACKTRACE > > --- Comment #1 from Myriam Schweingruber --- > We would need a backtrace for that crash, without it this report is pretty > useless. > > See also > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_ > useful_crash_reports > > Make sure to put the backtrace directly in the comment, not as an > attachment as > attachments are not searchable in the bug database. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 390761] Expose Libinput middle click button/emulation settings
https://bugs.kde.org/show_bug.cgi?id=390761 Nate Grahamchanged: What|Removed |Added Alias||libinput-touchpad-kcm-mmb-e ||mulation -- 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 Nate Grahamchanged: What|Removed |Added Depends on||390761 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=390761 [Bug 390761] Expose Libinput middle click button/emulation settings -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 390761] Expose Libinput middle click button/emulation settings
https://bugs.kde.org/show_bug.cgi?id=390761 Nate Grahamchanged: What|Removed |Added Blocks||383379 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=383379 [Bug 383379] Modernize Input Devices section to work with Libinput -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383582] krusader x11 forwarding hangs when deleting files
https://bugs.kde.org/show_bug.cgi?id=383582 Nikita Melnichenkochanged: What|Removed |Added CC||nikita+...@melnichenko.name Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nikita Melnichenko --- Could you please try to repro with the latest X server, KF5 libs and krusader git? It's likely some X or KWin related problem. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389240] Changing output 'device profile' directly from plasmoid
https://bugs.kde.org/show_bug.cgi?id=389240 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 384292 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 384292] Add possibility to select output device from tray menu
https://bugs.kde.org/show_bug.cgi?id=384292 Christoph Feckchanged: What|Removed |Added CC||karlosmun...@gmail.com --- Comment #3 from Christoph Feck --- *** Bug 389240 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 375382] Wish: DBus Function for copy to clipboard
https://bugs.kde.org/show_bug.cgi?id=375382 David Pedersenchanged: What|Removed |Added CC||lim...@me.com -- 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 --- Comment #26 from Shmerl--- (In reply to Nate Graham from comment #25) > yes, they have to be, because xinput isn't supported on Wayland. See Bug > 390761. Just for the reference, I'm talking about the mouse, not touchpad here, but I suppose the idea is similar. -- 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 Nate Grahamchanged: What|Removed |Added URL||https://phabricator.kde.org ||/T7964 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 371768] Screenshot of "Window under cursor" of plasma applet show other part of the desktop
https://bugs.kde.org/show_bug.cgi?id=371768 --- Comment #7 from Nate Graham--- I can't reproduce this with git master, following the original steps to reproduce. Henrik, do they still reproduce for you, or are you doing something different? -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 390752] Kdebugsettings overwrites default debug level for all log categories
https://bugs.kde.org/show_bug.cgi?id=390752 --- Comment #1 from Laurent Montel--- "As can be seen from the output of https://lxr.kde.org/search?_filestring=frameworks&_string=Q_LOGGING_CATEGORY the default log level for different debug categories varies from QtCriticalMsg to QtInfoMsg." all module which doesn't use debug categories files will not override by kdebugsettings => so kdebugsettings will not change settings for these modules. But indeed it will change settings for other modules. But default all module uses same settings generated by categories ecm macro. => QtInfoMsg see #if QT_VERSION >= QT_VERSION_CHECK(5, 4, 0) Q_LOGGING_CATEGORY(RUQOLA_DDPAPI_COMMAND_LOG, "org.kde.ruqola.ddpapi.command", QtInfoMsg) #else Q_LOGGING_CATEGORY(RUQOLA_DDPAPI_COMMAND_LOG, "org.kde.ruqola.ddpapi.command") #endif " => it's normal. " 3. Setting the log level to QtInfoMsg increases the log level for every category which defaults to Critical or Warning" it's wrong as we can't change settings from module which doesn't use debug categories file. "4. it lowers the log level for categories defaulting to Debug" wrong too. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390748] Deleting a file freezes dolphin UI during the deletion
https://bugs.kde.org/show_bug.cgi?id=390748 --- Comment #2 from Méven Car--- I am indeed. I will start tomorrow probably. My workaround could be a start, but I need to do some tests to avoid regression and keep a good user experience. It might require some UI work in dolphin to make it clear that a file is being deleted. Otherwise If a user removes a big file, he will only notice that it worked when the deletion completes and the file disappear in the UI. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390725] Using setColorSpace on a document in python leads to safe-asserts and memory leaks.
https://bugs.kde.org/show_bug.cgi?id=390725 --- Comment #2 from wolthera--- Actually, disabling the use of setColorSpace doesn't solve the safeAssert, it just solves the refresh warning. The safe assert is caused by the following: 1. Open a document in python 2. get the rootNode of the object. 3. Write a function to itterate over the child nodes, setting their labels or whatever, and if a child node has children, apply the function on those. Put the root node in this. 4. close the document. 3 in particular seems to cause the document not to close, with a simple script like this: - def removeLayers(self, labels, node): if node.colorLabel() in labels: node.remove() else: if node.childNodes(): for child in node.childNodes(): self.removeLayers(labels, node=child) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369676] White lockscreen text's readability depends on background
https://bugs.kde.org/show_bug.cgi?id=369676 Michael Dchanged: What|Removed |Added CC||nortex...@gmail.com --- Comment #9 from Michael D --- Why not have configurable font color, or have the background detected and automatically select text color based on that (which I imagine is way harder to implement)? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 390761] Expose Libinput middle click button/emulation settings
https://bugs.kde.org/show_bug.cgi?id=390761 Nate Grahamchanged: What|Removed |Added Keywords||usability -- 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 --- Comment #25 from Nate Graham--- yes, they have to be, because xinput isn't supported on Wayland. See Bug 390761. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 390761] Expose Libinput middle click button/emulation settings
https://bugs.kde.org/show_bug.cgi?id=390761 Nate Grahamchanged: What|Removed |Added Summary|Expose Libinput middle |Expose Libinput middle |click button/ emulation |click button/emulation |settings|settings -- 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 Shmerlchanged: What|Removed |Added CC||shm...@mykolab.com --- Comment #24 from Shmerl --- I just tried Wayland session with KDE Plasma 5.12.0 (Debian testing), and xinput wasn't working anymore and my setting for middle click emulation with right click + left click disappeared. So for now I switched back to X session. Will such libinput features be accessible through System Settings > Input Devices in the future? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 390762] New: Window Under Cursor mode includes any windows that are partially overlapping the window that's under your cursor
https://bugs.kde.org/show_bug.cgi?id=390762 Bug ID: 390762 Summary: Window Under Cursor mode includes any windows that are partially overlapping the window that's under your cursor Product: Spectacle Version: 17.12.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: n...@kde.org Target Milestone: --- See attached screenshot. The cursor was over the Kate window, and the Konsole window was partially overlapping the Kate window. "Window Under Cursor" mode undesirably captured the overlapping part of the Konsole window, too. 100% reproducible when any case of Window X partially overlapping window Y, and you take a screenshot of window Y with Window Under Cursor mode. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 390706] Two-finger touchscreen zoom gesture needs final refresh
https://bugs.kde.org/show_bug.cgi?id=390706 --- Comment #4 from Oliver Sander--- Okay, now I understand. However, I cannot reproduce the problem. Does anybody have an idea? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 390652] Capturing the active window fails if compositing is off and the window touches a screen border
https://bugs.kde.org/show_bug.cgi?id=390652 Nate Grahamchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Nate Graham --- Never mind, my VM composits! Who knew? Can confirm the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389818] Warn that global shortcut does not include modifier
https://bugs.kde.org/show_bug.cgi?id=389818 --- Comment #8 from ras...@gmail.com --- What I was trying to say is that it wasn't working that way for me. But upon further investigation, it seems I was wrong about what's happening after all... again. Any key combination will start 'window switching mode' as expected, but the key combination that switches between windows while in this mode doesn't change until I restart kwin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389495] When GTK3 applications request SSD, decorations are not shown
https://bugs.kde.org/show_bug.cgi?id=389495 Martin Flöserchanged: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INVALID --- Comment #29 from Martin Flöser --- No, no. That is not how the protocol works. Default mode is sent by KWin. It is the state of a declaration till the declaration requests another mode. But no decoration is created. The request from client to server to create a decoration for the surface is just missing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget
https://bugs.kde.org/show_bug.cgi?id=368838 TYY331changed: What|Removed |Added CC||sebastian.p...@gmail.com --- Comment #41 from TYY331 --- The memory leak also occurs while displaying application's icons. Displaying application's icons in the launcher constantly increases plasma's memory usage. Steps to reproduce. 1. Display application's icon (application menu, application launcher and application dashboard trigger the memory leak) Bear in mind since icons are low size files the memory leak per icon is quite low, the problem becomes evident while displaying a lot of icons over time, that's why you have to rapidly navigate the menus due to time constrains, normal use would take a couple of days. The problem is that there is no workaround since application's icons are always present and can't be disabled. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383668] Krusader blocks ejecting of removable drive by self 'krusader' process if drive is opened in it's tab
https://bugs.kde.org/show_bug.cgi?id=383668 Nikita Melnichenkochanged: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #6 from Nikita Melnichenko --- Thanks for the explanation! I confirm this issue. Dolphin handles this case pretty well (if you press Eject in the Device Notifier, I'm haven't checked if they have an action within Dolphin). AFAIR, Total Commander also able to eject even if the folder on the device is open, however it changes the dir to default drive. BTW, +1 error message appear only if you select "Unmount". For "Safely Remove" it is fine. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 390652] Capturing the active window fails if compositing is off and the window touches a screen border
https://bugs.kde.org/show_bug.cgi?id=390652 --- Comment #4 from Henrik Fehlauer--- Thanks for testing ;) Telling whether compositing is off should be easy, because there are no shadows… Also, make sure to test once in a while in this mode, because especially the performance might be totally different (e.g. moving windows, moving region capture in Spectacle etc.). -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 390761] Expose Libinput middle click button/emulation settings
https://bugs.kde.org/show_bug.cgi?id=390761 Shmerlchanged: What|Removed |Added CC||shm...@mykolab.com --- Comment #1 from Shmerl --- This should apply to mice too, not just touchpads. For example, under X I use this: Example (for my case), to query: xinput --list-props "Logitech G400s Optical Gaming Mouse" Device 'Logitech G400s Optical Gaming Mouse': ... libinput Middle Emulation Enabled (288):1 ... To set: xinput set-prop "Logitech G400s Optical Gaming Mouse" "libinput Middle Emulation Enabled" 1 Something on Wayland to do that would be useful. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 390762] Window Under Cursor mode includes any windows that are partially overlapping the window that's under your cursor
https://bugs.kde.org/show_bug.cgi?id=390762 --- Comment #1 from Nate Graham--- Created attachment 110831 --> https://bugs.kde.org/attachment.cgi?id=110831=edit Overlapping window mistakenly captured, too -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390760] Wayland crashes to SDDM greeter
https://bugs.kde.org/show_bug.cgi?id=390760 Martin Flöserchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Flöser --- We need a backtrace of the crashing KWin. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389859] Changing project profile shortens and cuts clips
https://bugs.kde.org/show_bug.cgi?id=389859 Ovidiu-Florin BOGDANchanged: What|Removed |Added CC||ovidiu@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 390763] Stuck at authorizing token
https://bugs.kde.org/show_bug.cgi?id=390763 Ovidiu-Florin BOGDANchanged: What|Removed |Added CC||ovidiu@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369676] White lockscreen text's readability depends on background
https://bugs.kde.org/show_bug.cgi?id=369676 --- Comment #10 from Rog131--- (In reply to Michael D from comment #9) > Why not have configurable font color, or have the background detected and > automatically select text color based on that (which I imagine is way harder > to implement)? The Breeze plasma lockscreen is using plasma complementary color group. The Breeze text color can be set from the KDE system settings > Colors > Complementary > Normal text. Image - Imgur: https://imgur.com/jrC4bR8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383407] Lack of support for relative/mouse mode for tablet
https://bugs.kde.org/show_bug.cgi?id=383407 --- Comment #4 from Boudewijn Rempt--- Yes, we consider adding things to Krita that Krita didn't do before new features, so this gets to be classified as a wish, not a bug. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 369676] White lockscreen text's readability depends on background
https://bugs.kde.org/show_bug.cgi?id=369676 Krzysztof Nowickichanged: What|Removed |Added CC||kri...@op.pl -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390584] Opening a .psd, then saving as .psd, then opening file again creates internal error
https://bugs.kde.org/show_bug.cgi?id=390584 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/4c31962dd75f0087824ce4c0 ||eace5cabfc0d2098 Status|CONFIRMED |RESOLVED --- Comment #7 from Boudewijn Rempt --- Git commit 4c31962dd75f0087824ce4c0eace5cabfc0d2098 by Boudewijn Rempt. Committed on 20/02/2018 at 07:17. Pushed by rempt into branch 'master'. PSD: save layers with an empty name as "Unnamed Layer" Photoshop does not support layers with no names; you cannot even create them in Photoshop. Saving layers to PSD with an empty name results in an invalid PSD file, so subsitute "Unnamed Layer". M +1-1plugins/impex/psd/psd_layer_section.cpp https://commits.kde.org/krita/4c31962dd75f0087824ce4c0eace5cabfc0d2098 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 390718] Tab switching is not working
https://bugs.kde.org/show_bug.cgi?id=390718 --- Comment #2 from Andrej Valek--- KDE Frameworks 5.28.0 Qt 5.7.1 (built against 5.7.1) The xcb windowing system I have tested this versions: - 2.4.0 - works fine - 2.5.0 - problematic - 2.6.0 "Stiff Challenges" - problematic - after creating new tab - "QWidget::insertAction: Attempt to insert null action" All of the packages have been taken from official Debian repo. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 382195] Not all installed languages are visible on Windows
https://bugs.kde.org/show_bug.cgi?id=382195 --- Comment #4 from Ralf Habacker--- Looking at the implementation of KLocale on Windows shows that there is currently no support for choosing a different language beside the users default language (see https://cgit.kde.org/kdelibs.git/tree/kdecore/localization/klocale_win.cpp?h=KDE/4.14#n39) A forward look to KF5: 1. The issue has not been fixed in the KF5 variant of KLocale (https://cgit.kde.org/kdelibs4support.git/tree/src/kdecore/klocale_win.cpp#n39) 2. The Qt equivalent class QLocale is also limited to the default language of the current user (see https://code.woboq.org/qt5/qtbase/src/corelib/tools/qlocale_win.cpp.html#171) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355772] Navigation controls stop working when in text edit mode
https://bugs.kde.org/show_bug.cgi?id=355772 Boudewijn Remptchanged: What|Removed |Added CC||b...@valdyas.org Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt --- This tool has been replaced in 4.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355771] Unable use the '.' character on the keyboard's number pad in Text Editing
https://bugs.kde.org/show_bug.cgi?id=355771 Boudewijn Remptchanged: What|Removed |Added CC||b...@valdyas.org Resolution|--- |UNMAINTAINED Component|Layers/Vector |Tool/Text Status|CONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt --- This tool has been replaced with the new text tool. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383407] Lack of support for relative/mouse mode for tablet
https://bugs.kde.org/show_bug.cgi?id=383407 Wadechanged: What|Removed |Added CC||wadeschlue...@gmail.com --- Comment #3 from Wade --- Mouse mode isn't a new feature, though making support in Krita for it might be considered a new feature. I got my first Wacom tablet 12/31/2008 and had decided immediately that pen mode made no sense for people drawing on a non-screen surface and staring at a monitor. This is especially true for people who have multiple monitor setups (even though you can set it to one monitor for the mapping, it's still preferable for me to use mouse mode). I for one, would like to see Krita support mouse mode which as far as I understand would only work in WinTab, especially given that other programs support it. I would also like to see this as a feature since not everyone uses Pen mode for their tablet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 355773] Duplicating Artistic Text will remove multiple spaces
https://bugs.kde.org/show_bug.cgi?id=355773 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #3 from Boudewijn Rempt --- This tool has been replaced in 4.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357801] Sometimes parts of the image data gets blanked out
https://bugs.kde.org/show_bug.cgi?id=357801 Boudewijn Remptchanged: What|Removed |Added Component|Tools |Layer Stack -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 390718] KrViewer: Tab scrolling using arrows is not working when too many tabs are open
https://bugs.kde.org/show_bug.cgi?id=390718 Nikita Melnichenkochanged: What|Removed |Added Status|NEEDSINFO |CONFIRMED Version|2.5.0 |Git Severity|normal |major Summary|Tab switching is not|KrViewer: Tab scrolling |working |using arrows is not working ||when too many tabs are open Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #3 from Nikita Melnichenko --- I missed that the report is for KrViewer tabs, not for the folder tabs in main window, sorry. I confirm, it's very buggy. It seems like it's trying to always show an active tab. As a workaround you may use Ctrl+Tab, Ctrl+Shift+Tab or Ctrl+], Ctrl+[ for tab switching. Thanks for the report! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383424] Path dropdown inconsistencies for removable drives
https://bugs.kde.org/show_bug.cgi?id=383424 Nikita Melnichenkochanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||nikita+...@melnichenko.name Ever confirmed|0 |1 --- Comment #6 from Nikita Melnichenko --- Although it reproduces sometimes, it was not hard to catch and it seems to be deterministic based on the dir path, so should be not very hard to debug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390584] Opening a .psd, then saving as .psd, then opening file again creates internal error
https://bugs.kde.org/show_bug.cgi?id=390584 --- Comment #6 from Boudewijn Rempt--- Or Gimp... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 389962] Lock screen does not show Picture of the Day
https://bugs.kde.org/show_bug.cgi?id=389962 Rog131changed: What|Removed |Added CC||samrog...@hotmail.com --- Comment #8 from Rog131 --- (In reply to Shmerl from comment #7) > And I suppose since lock screen has no network access, in order to enable > something like picture of the day, there should be an explicit KDE service / > scheduled job "picture of the day" that user can enable, and lock screen can > rely on that service to update the image appropriately. There could be a 'POTD' widget. : https://forum.kde.org/viewtopic.php?f=289=142331 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390584] Opening a .psd, then saving as .psd, then opening file again creates internal error
https://bugs.kde.org/show_bug.cgi?id=390584 --- Comment #5 from Boudewijn Rempt--- Looks like I cannot create layers with an empty name in Photoshop itself... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375904] Icon misalignment for the Brush HUD on Retina displays
https://bugs.kde.org/show_bug.cgi?id=375904 Boudewijn Remptchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Boudewijn Rempt --- This is fixed by now. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 383420] MountMan - inconsistencies in dropdown menu
https://bugs.kde.org/show_bug.cgi?id=383420 Nikita Melnichenkochanged: What|Removed |Added CC||nikita+...@melnichenko.name Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Severity|normal |wishlist --- Comment #1 from Nikita Melnichenko --- For #1: 'Show only removable devices' checkbox is only quick filter for main window of MountMan, not a global setting. For #2: the dropdown is referred in the Handbook as 'Quickmode for MountMan' and explicitly says it's about reading fstab. I agree it's a nice feature to have though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390722] Plasma Shell Crash
https://bugs.kde.org/show_bug.cgi?id=390722 Antonio Rojaschanged: What|Removed |Added Resolution|--- |DUPLICATE CC||aro...@archlinux.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 363136 *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 363136] Bookmarks runner crashes in QSqlite
https://bugs.kde.org/show_bug.cgi?id=363136 --- Comment #38 from Antonio Rojas--- *** Bug 390722 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389725] for monospace fonts bold does not work
https://bugs.kde.org/show_bug.cgi?id=389725 --- Comment #4 from David Edmundson--- Yes. More precisely, I'm asking you to test without loading the Plasma QPT. Unsetting envs XDG_CURRENT_DESKTOP and KDE_FULL_SESSION would also suffice -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390722] Plasma Shell Crash
https://bugs.kde.org/show_bug.cgi?id=390722 --- Comment #1 from Mani--- after typing more than 3 letter it will crash. after the crash I use: "kbuildsycoca5 && kquitapp plasmashell && kstart plasmashell" to run the plasma shell and start typing again and this is the output of the terminal after re-crash: KAStatsFavoritesModel::setFavorites is ignored KActivities: Database connection: "kactivities_db_resources_139989309798400_readonly" query_only: QVariant(qlonglong, 1) journal_mode:QVariant(QString, "wal") wal_autocheckpoint: QVariant(qlonglong, 100) synchronous: QVariant(qlonglong, 0) Closing SQL connection: "kactivities_db_resources_139989309798400_readonly" trying to show an empty dialog KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... QSocketNotifier: Invalid socket 25 and type 'Read', disabling... QSocketNotifier: Invalid socket 31 and type 'Read', disabling... QSocketNotifier: Invalid socket 34 and type 'Read', disabling... The X11 connection broke (error 1). Did the X11 server die? KCrash: Application 'plasmashell' crashing... KCrash: Attempting to start /usr/lib/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 20 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... The X11 connection broke: I/O error (code 1) XIO: fatal IO error 9 (Bad file descriptor) on X server ":0" after 2262 requests (2225 known processed) with 0 events remaining. QProcess: Destroyed while process ("/usr/bin/redshift") is still running. The X11 connection broke: I/O error (code 1) XIO: fatal IO error 9 (Bad file descriptor) on X server ":0" after 2262 requests (2225 known processed) with 0 events remaining. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 390708] Allow to move backward in presentations using touch
https://bugs.kde.org/show_bug.cgi?id=390708 --- Comment #3 from Oliver Sander--- We are talking about touch screens, right? Not about touch pad gestures? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390723] make xtree dump files world wide readable, similar to log files
https://bugs.kde.org/show_bug.cgi?id=390723 Ivo Raisrchanged: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390723] make xtree dump files world wide readable, similar to log files
https://bugs.kde.org/show_bug.cgi?id=390723 Ivo Raisrchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED CC||iv...@ivosh.net -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390726] New: KisImage.cc and by extend the Document Libkis Object miss apidox for lock/unlock/tryBarrierLock/isIdle
https://bugs.kde.org/show_bug.cgi?id=390726 Bug ID: 390726 Summary: KisImage.cc and by extend the Document Libkis Object miss apidox for lock/unlock/tryBarrierLock/isIdle Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- Reporting a bug for this because manipulating images is a really important part of scripting, and handling the multi-threading is so even more. It's not possible to figure out how and when to use these as there s no docs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390715] Not a valid Krita File
https://bugs.kde.org/show_bug.cgi?id=390715 Boudewijn Remptchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org Resolution|--- |INVALID --- Comment #1 from Boudewijn Rempt --- Sorry, but this is a bug tracker, not a user support forum. I've looked at the file, and it's not a valid zip file. If even ziprepair (https://www.diskinternals.com/zip-repair/, haven't tried that since I'm on linux atm) cannot repair it, it is lost. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 390708] Allow to move backward in presentations using touch
https://bugs.kde.org/show_bug.cgi?id=390708 --- Comment #2 from Stefan Brüns--- (In reply to Oliver Sander from comment #1) > You can go back and forth in presentations using left/right swiping > gestures. Note that Qt swipe gestures need three(!) fingers. Has no effect for me. The event device reports up to ten fingers. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 387502] Wifi Password Entered Twice
https://bugs.kde.org/show_bug.cgi?id=387502 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 390723] New: make xtree dump files world wide readable, similar to log files
https://bugs.kde.org/show_bug.cgi?id=390723 Bug ID: 390723 Summary: make xtree dump files world wide readable, similar to log files Product: valgrind Version: 3.14 SVN Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: iv...@ivosh.net Target Milestone: --- There is no reason why xtree dump files should not be world wide readable, similar to log files. Users can always set the corresponding umask to tighten the permissions. diff --git a/coregrind/m_xtree.c b/coregrind/m_xtree.c index 7d5766222..217cad9da 100644 --- a/coregrind/m_xtree.c +++ b/coregrind/m_xtree.c @@ -377,7 +377,7 @@ static VgFile* xt_open (const HChar* outfilename) VgFile* fp; fp = VG_(fopen)(outfilename, VKI_O_CREAT|VKI_O_WRONLY|VKI_O_TRUNC, - VKI_S_IRUSR|VKI_S_IWUSR); + VKI_S_IRUSR|VKI_S_IWUSR|VKI_S_IRGRP|VKI_S_IROTH); if (fp == NULL) { VG_(message)(Vg_UserMsg, "Error: can not open xtree output file `%s'\n", -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 384075] korganizer crashes when selecting a calendar to be shown in agenda/day/week/month view (regression 17.08.*)
https://bugs.kde.org/show_bug.cgi?id=384075 Denis Kurzchanged: What|Removed |Added Component|general |todoview Version|5.7.1 |5.7.2 --- Comment #11 from Denis Kurz --- Here we are again. KOrganizer crashes every time upon startup. I had some duplicated items in the offending calendar, but this time, they were VEVENTS, which are not involved in the code that crashes (IncidenceTreeModel). I deleted the duplicated events, but KOrganizer still crashed. What helped, though, was clearing the Akonadi cache for that collection. This is PIM 5.7.2 a.k.a PIM as of KDE Applications 17.12.2. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390725] New: Batch exporting a list of documents via python(like exporting a comic) leads to safe-asserts and memory leaks.
https://bugs.kde.org/show_bug.cgi?id=390725 Bug ID: 390725 Summary: Batch exporting a list of documents via python(like exporting a comic) leads to safe-asserts and memory leaks. Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- Decided to make a seperate bug task for this one. To Reproduce 1. Download this sample comic project https://share.kde.org/index.php/s/hv1S25gBVq4pTwh, unzip it somewhere. 2. Enable the Comic Project Management Tools under settings->configure Krita->python manager. 3. (Re)start Krita in terminal. 4. Open the comics manager docker 5. "Open Project"->Navigate to the sample comic project folder, and select the comicConfig.json 6. Then, when the comic is loaded, press "export comic" 7. Keep your eyes on the terminal, once the comic is done exporting it should show this for each page in the docker: SAFE ASSERT (krita): "!sanityCheckPointer.isValid()" in file /home/wolthera/krita/src/libs/ui/KisDocument.cpp, line 490 Other - I spent some time with boud trying to figure out what caused this last august, but we couldn't figure out what did. I suspect it may have something to do with that the documents are never added to the Krita GUI, which is not good because that means headless exporting doesn't work at all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390712] image
https://bugs.kde.org/show_bug.cgi?id=390712 Boudewijn Remptchanged: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Boudewijn Rempt --- I'm sorry, I cannot reproduce this issue. * Which version of Krita are you using? * Does this happen with all images, or only with a specific image? If so, please attach that image. * Can you try to make a crash log: see https://docs.krita.org/Dr._Mingw_debugger -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 390501] disappearing alarms
https://bugs.kde.org/show_bug.cgi?id=390501 David Jarviechanged: What|Removed |Added Component|kalarmd |general --- Comment #1 from David Jarvie --- What version of Ubuntu and KAlarm are you using? What were the previous versions before the update? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390722] New: Plasma Shell Crash
https://bugs.kde.org/show_bug.cgi?id=390722 Bug ID: 390722 Summary: Plasma Shell Crash Product: plasmashell Version: 5.12.1 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mani.za...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.1) (Compiled from sources) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.3-2-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Plasma shell will crash if I click on the application menu and start searching for any search pharse more than 2 characters The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc1d90b7800 (LWP 4549))] Thread 24 (Thread 0x7fc0b37fe700 (LWP 6028)): #0 0x7fc1d1e343bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc1d2c7b02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc1182e842f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fc1182ed479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fc1182eac83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fc1d2c79b4d in () at /usr/lib/libQt5Core.so.5 #11 0x7fc1d1e2e08c in start_thread () at /usr/lib/libpthread.so.0 #12 0x7fc1d2581e7f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fc0abfff700 (LWP 6027)): #0 0x7fc1d1e343bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc1d2c7b02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fc1182e842f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fc1182ed479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #21 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #22 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #23 0x7fc1182ed4d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #24 0x7fc1182e7924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #25 0x7fc1182ed4d2 in () at
[okular] [Bug 390708] Allow to move backward in presentations using touch
https://bugs.kde.org/show_bug.cgi?id=390708 --- Comment #4 from Stefan Brüns--- (In reply to Oliver Sander from comment #3) > We are talking about touch screens, right? Not about touch pad gestures? Yes, touch screens. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 390623] GUI wrong button language, wrong environment variable?
https://bugs.kde.org/show_bug.cgi?id=390623 Frederik Schwarzerchanged: What|Removed |Added CC||schwar...@kde.org --- Comment #3 from Frederik Schwarzer --- >From what I can understand here, the German translators are not the right assignee. If anyone has a better place to assign this to, please do so. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 390708] Allow to move backward in presentations using touch
https://bugs.kde.org/show_bug.cgi?id=390708 --- Comment #5 from Oliver Sander--- Hmm. What's your Okular version? Does three-finger swiping work for you in other Qt applications? Are you able to build Okular yourself to do some debugging? Actually, though, the change-slides-by-swiping code in Okular is extremely short (method PresentationWidget::gestureEvent, in file presentationwidget.cc:589). If that doesn't work it is unlikely to be an Okular problem, simply because all the difficult things happen in Qt and below. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 389991] Powerdevil global shortcuts not working after 5.12 config migration
https://bugs.kde.org/show_bug.cgi?id=389991 David Edmundsonchanged: What|Removed |Added Ever confirmed|0 |1 Summary|Sleep key no longer |Powerdevil global shortcuts |initiates sleep |not working after 5.12 ||config migration Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390724] New: kscreen 90 counterclockwise second monitor shows mouse pointer, but no windows
https://bugs.kde.org/show_bug.cgi?id=390724 Bug ID: 390724 Summary: kscreen 90 counterclockwise second monitor shows mouse pointer, but no windows Product: KScreen Version: 5.12.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: archenr...@gmail.com Target Milestone: --- I am running Gentoo system and experienced some situation which can be resolved, but is possible bug. I have installed following kscreen version: [I] kde-plasma/kscreen Available versions: (5) 5.11.5^t (~)5.12.1^t {debug test} Installed versions: 5.12.1(5)^t(09:24:18 02/15/18)(-debug -test) Homepage:https://cgit.kde.org/kscreen.git Description: KDE Plasma screen management Unexpected situation description: 1. I have 2 monitors connected to nvidia 1080 ti both via display port, 43" and 24". 2. Second 24" monitor I configured ?< 90* Counterclockwise and all works - screenshot from systemsetting attached (kde-plasma_system-settings_displays.png) 3. I restart the system 4. After boot, main monitor is OFF and second display is displaying terminal in NON <90* Counterclockwise, but XDM is off, so I understand this. Question: Why is main monitor OFF - not sure if right place to ask for it as XDM is off in that moment. 5. I log in and start manually /etc/init.d/xdm start 6. After start of XDM login screen appear on still NON clockwised secondary monitor - note I use DISPLAYMANAGER="sddm", primary monitor is still OFF Question: I would expect in this moment the monitor should rotate < 90 Counterclockwise as windows system is in control, but not sure. Is SDDM using plasma monitor settings or not? 7. After plasma desktop is loaded main monitor is finally switched ON and displays correctly desktop while the second monitor is reportedly on (have signal from GPU), the screen is black and have following behaviour: A. When I move mouse over the second monitor, the cursor is visible B. When I try to move some window from main monitor to second one, I can see only mouse cursor, but no window of moved application C. The desktop background is not visible, background is simply black 8. After I just try to little bit move alignment in systemsettings-display and do Apply (button) the second monitor remain still in the same kind of state (all previously 3 described behaviours apply) 9. To fix this situation I just switch the second monitor to other orientation and then back to expected < 90* Counterclockwise 10. All is back to expected state Same behaviour after each restart. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect
https://bugs.kde.org/show_bug.cgi?id=359159 Luca Weisschanged: What|Removed |Added CC||l...@z3ntu.xyz -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 390700] Unable to convert Fujifilm RAF RAW to DNG
https://bugs.kde.org/show_bug.cgi?id=390700 --- Comment #4 from caulier.gil...@gmail.com --- It's probably a libraw issue as the camera is not on the list. For each RAW camera, libraw as a corresponding matrix to process bayer sensor, reverse engineered if i remember some talk with libraw team in the past. In all cases, if the camera is not in the list, this cannot work as expected. the libraw 0.19 is in the way, as i can see in github forum. So, we need to wait a little bit. I will backport code quickly in DK core. Gilles -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 390709] Create a reader mode/horizontal continous mode
https://bugs.kde.org/show_bug.cgi?id=390709 Albert Astals Cidchanged: What|Removed |Added CC||aa...@kde.org Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390711] Make screen edge gesture more discoverable
https://bugs.kde.org/show_bug.cgi?id=390711 Stefan Brünschanged: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e --- Comment #2 from Stefan Brüns --- If I look at my phone (Android), I get a very strong visual hint. Please read https://bugs.kde.org/show_bug.cgi?id=380428 to get an impression what the effect of the current scheme is. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389479] Plasma not mount disk
https://bugs.kde.org/show_bug.cgi?id=389479 Ben Creasychanged: What|Removed |Added CC||b...@bencreasy.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 389635] Hidden items pollute places dropdown-menu
https://bugs.kde.org/show_bug.cgi?id=389635 Kai Uwe Broulikchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kio ||/03be39f3709e1c3229554a6555 ||e49d16688441c2 Status|CONFIRMED |RESOLVED --- Comment #5 from Kai Uwe Broulik --- Git commit 03be39f3709e1c3229554a6555e49d16688441c2 by Kai Uwe Broulik. Committed on 19/02/2018 at 09:09. Pushed by broulik into branch 'master'. [KUrlNavigatorPlacesSelector] Put categories into submenus Avoids letting the menu get huge. This is a straight port from Plasma's task manager 6effcdf11d1a64017593c5cef434b80122936854 Also hide hidden items. Differential Revision: https://phabricator.kde.org/D10329 M +37 -6src/filewidgets/kurlnavigatorplacesselector.cpp https://commits.kde.org/kio/03be39f3709e1c3229554a6555e49d16688441c2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389725] for monospace fonts bold does not work
https://bugs.kde.org/show_bug.cgi?id=389725 --- Comment #3 from Erik Quaeghebeur--- (In reply to David Edmundson from comment #2) > and you have the issue if you run kate/konsole in openbox? To be clear: are you asking us to install openbox and test in openbox? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 Kai Uwe Broulikchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Kai Uwe Broulik --- Just press the down arrow when KRunner is opened. I agree that there should be a visual cue for that. I'll see if I can put an arrow in there. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable
https://bugs.kde.org/show_bug.cgi?id=332512 Petr Sedlacekchanged: What|Removed |Added CC||p...@sedlacek.biz --- Comment #71 from Petr Sedlacek --- (In reply to Thomas Meiner from comment #70) > I can not understand, what's the big problem to bring the behaviour of KDE4 > back? Thomas, it's usually a problem of priorities - the development capacity is limited and issues are dealt with based on severity. I know this issue is annoying but let's be honest, it's not a big deal. It is a bit of a pity this issue has been sitting here for nearly 4 years but I'm not shouting about it as I'm always getting an extremely good deal for my money ;-) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 390229] Falkon Freezes My System
https://bugs.kde.org/show_bug.cgi?id=390229 --- Comment #2 from Alberto Díaz López--- (In reply to David Rosca from comment #1) > Can you try to get a backtrace when it freezes? You need to run falkon in > gdb and ctrl+c when it freezes. > Although you say that the whole system except cursor freezes, so this is > most likely issue with your graphics driver. I tried to open again QupZilla after update a lot of packages on my Manjaro KDE system, the past 17th February, including QupZilla, not a new version, but an update, after all, KDE Plasma, KDE Frameworks, and now it doesn't freeze the system, but still sometimes when i do something (open a new window with something at fullscreen), KWin crashes and shows me a message that says something like this "KWin crashed and stopped the effects", with the consecuence that the panel that i have stops to work properly and freezes like when my system freezed when i did some things with QupZilla or just with open it. Looks like as you said, that it's something with the graphics driver, i've got an NVIDIA GPU and privative drivers, i fear. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 390229] Falkon Freezes My System
https://bugs.kde.org/show_bug.cgi?id=390229 David Roscachanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from David Rosca --- I have no experience with nvidia drivers, but the situation you describe with kwin happens with Intel when there is a gpu hang and needs to be reset. So I am closing this bug as the problem is in gpu drivers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #39 from Antonio Orefice--- Me, the OP, reported the issue on QT 5.7.x times, so the bug here: https://bugreports.qt.io/browse/QTBUG-61754 does not apply at all. Is there any chance to bring the title of this back to the original, the 'thread' has derailed... It originally was: "[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it." The "NVIDIA BLOB" part is irrelevant. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390727] Plasmashell does not cover 1440p monitor and behaves strangely
https://bugs.kde.org/show_bug.cgi?id=390727 Huan Truongchanged: What|Removed |Added CC||htru...@tnhh.net --- Comment #2 from Huan Truong --- Created attachment 110811 --> https://bugs.kde.org/attachment.cgi?id=110811=edit KWin supportInformation KWin supportInformation is attached here. -- You are receiving this mail because: You are watching all bug changes.