[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 --- Comment #59 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/kamera/-/merge_requests/6 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 465643] Actions and tools buttons from tools menu dont work
https://bugs.kde.org/show_bug.cgi?id=465643 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Do you have kdepim-addons installed ? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 465655] New: loopback interface shown with virtual interfaces disabled
https://bugs.kde.org/show_bug.cgi?id=465655 Bug ID: 465655 Summary: loopback interface shown with virtual interfaces disabled Classification: Plasma Product: plasma-nm Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gudvinr+...@gmail.com Target Milestone: --- SUMMARY In both editor and applet I see "lo" interface which is link/loopback with address 127.0.0.1/8 and I have "show virtual connections" checkbox disabled. And I never even enabled it, actually. STEPS TO REPRODUCE 1. Open connection list OBSERVED RESULT I see loopback interface and can interact with it EXPECTED RESULT No loopback interface is shown SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.11-zen1-1-zen (64-bit) Network Manager Version: 1.42.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 465654] New: "Motion Tracker" not in overview of effects group "Alpha, Mask and Keying"
https://bugs.kde.org/show_bug.cgi?id=465654 Bug ID: 465654 Summary: "Motion Tracker" not in overview of effects group "Alpha, Mask and Keying" Classification: Applications Product: kdenlive Version: 21.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: r...@rb-software.de Target Milestone: --- Created attachment 156185 --> https://bugs.kde.org/attachment.cgi?id=156185=edit No Motion Tracker visible SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. program start 2. enter "effects" 3. enter "Alpha, Mask and Keying" OBSERVED RESULT On select "Alpha, Mask and Keying" i can't see "Motion Tracker", but if i'm searching with "motion", then i see "Motion Tracker" in the results. EXPECTED RESULT See "Motion Tracker" on "Alpha, Mask and Keying" group SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04 LTS (available in About System) KDE Plasma Version: Plasma 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Installed OpenCV with "sudo apt install libopencv-dev python3-opencv" OpenCV Version is 4.5.4 German settings on installed Linux -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 --- Comment #58 from Alexander Lohnau --- Git commit 2c7e60447c62e955b3975012b4427ccd5aa71ee1 by Alexander Lohnau. Committed on 13/02/2023 at 07:47. Pushed by alex into branch 'master'. Add BugReportUrl to json metadata M +1-0src/konfigurator/kwalletconfig.json https://invent.kde.org/utilities/kwalletmanager/commit/2c7e60447c62e955b3975012b4427ccd5aa71ee1 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #57 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/multimedia/audiocd-kio/-/merge_requests/7 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464600] 'Report a bug in the current page...' is not available for all KCMs
https://bugs.kde.org/show_bug.cgi?id=464600 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/1192 -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 465653] New: [desktop] no way to enter private mode
https://bugs.kde.org/show_bug.cgi?id=465653 Bug ID: 465653 Summary: [desktop] no way to enter private mode Classification: Applications Product: angelfish Version: 23.01.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: justin.zo...@gmail.com Target Milestone: --- I can enter private mode on mobile but not on desktop. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464600] 'Report a bug in the current page...' is not available for all KCMs
https://bugs.kde.org/show_bug.cgi?id=464600 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/309 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464600] 'Report a bug in the current page...' is not available for all KCMs
https://bugs.kde.org/show_bug.cgi?id=464600 --- Comment #6 from Alexander Lohnau --- > Cookies I can't find a bug category for that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465623] Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager
https://bugs.kde.org/show_bug.cgi?id=465623 --- Comment #4 from Felix Kütt --- (In reply to Nate Graham from comment #3) > Looks like the problem is that Elisa has become somehow configured as your > file manager. This isn't something that's supported, and Elisa doesn't > register itself as a handler for opening folders, so it's either a > configuration issue or a packaging error. I'd recommend fixing this in > System Settings > Applications > Default Applications. Yes, my best guess is when/while I changed waterfox to be my default browser months ago I might have been hovering over the file manager setting for a moment and since my mouse has a really sensitive scroll wheel it might have accidentally switched the file manager there. But that's besides the point and not the issue I'm trying to highlight. I'm trying to highlight that a button label that I assume should be contextual doesn't really reflect the action it's going to trigger. A small and nit-picky and thus surely low priority issue. But if it reflected what application or type of application it would launch that would also immediately communicated to me as a user that I might have misconfigured it rather than being left with a confusing surprise. Or I might still be left confused why the button would even say that but I wouldn't be surprised it opened something other than a file manager. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465652] New: Rescan activated for all collection when adding new collection
https://bugs.kde.org/show_bug.cgi?id=465652 Bug ID: 465652 Summary: Rescan activated for all collection when adding new collection Classification: Applications Product: digikam Version: 7.9.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Import-Albums Assignee: digikam-bugs-n...@kde.org Reporter: tuomas.kopo...@me.com Target Milestone: --- SUMMARY I do have a collection or roughly 80 000 photos that are kept under NAS device (Nextcloud with webdav via mountainduck). I'm in the middle off consolidating all my external disks to single storage and plugged new external disk and added it as a new collection. At the same time my network disk was mounted from wrong folder (bug by mountainduck, bookmark had subpath defined). Right after I finished to add new external disk all my photos from NAS device was removed. I have configured Digikam not to scan any files automatically and I have not selected collections to monitor for changes. STEPS TO REPRODUCE 1. add new collection OBSERVED RESULT All collections were rescanned EXPECTED RESULT Only added collection to be scanned SOFTWARE/OS VERSIONS Windows: macOS: 13.2 (22D49) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This is not such huge issue as it is recoverable by scanning files again. It will take easily a full day to san 930Gb of images and some videos. Digikam has worked out well and I do now have rather decent workflow with Piwigo to send images and organise them without Apple or Google services. Only annoyance is this collection management that seems to break rather easily. This was not first time I have had the same. I was hoping that mountain duck would solve some of the issues, but it seems not to be perfect. I would just hope that I could manage how and when collections are scanned to avoid this kind of a problems. Now settings that exists does not seem to allow that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464600] 'Report a bug in the current page...' is not available for all KCMs
https://bugs.kde.org/show_bug.cgi?id=464600 Alexander Lohnau changed: What|Removed |Added Assignee|plasma-b...@kde.org |alexander.loh...@gmx.de --- Comment #5 from Alexander Lohnau --- I will look into fixing it for the remaining KCMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396085] Media Player widget scroll behavior is backwards
https://bugs.kde.org/show_bug.cgi?id=396085 el...@seznam.cz changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from el...@seznam.cz --- I just did a retest and everything works as expected. Mouse wheel sets volume of Spotify and scroll direction is correct as well. Thank you for fixing it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465651] Noticeable delay for activating hover state on task manager
https://bugs.kde.org/show_bug.cgi?id=465651 --- Comment #1 from guimarcalsi...@gmail.com --- PS: I filled another bug report a few minutes ago about another similar (but not quite the same) bug with a graphics tablet, here I'm using a standard mouse, not the tablet, so this is not caused by it. I made sure to disconnect my tablet and restart the computer before recording the video. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465651] New: Noticeable delay for activating hover state on task manager
https://bugs.kde.org/show_bug.cgi?id=465651 Bug ID: 465651 Summary: Noticeable delay for activating hover state on task manager Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: guimarcalsi...@gmail.com Target Milestone: 1.0 Created attachment 156184 --> https://bugs.kde.org/attachment.cgi?id=156184=edit Delay while hovering SUMMARY On Neon Unstable with updates as of Feb. 11th, there's a noticeable delay in activating the hover state for programs on the task manager. This happens on both X11 and Wayland and happens on Icon-only mode and task manager mode. Highlights on other widgets are normal. Also, there's no jump in CPU usage or any message on the terminal that could explain what is happening. This is not present in Plasma 5.26.5 (tested on another, slower computer). STEPS TO REPRODUCE 1. Move the mouse cursor over various icons (check the attached video) OBSERVED RESULT Up to one second of delay to transition from the normal to the highlighted state. EXPECTED RESULT Highlights should apply instantly SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-60-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15,6 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465650] [Wayland] [Graphics Tablet]: When using a stylus, some tooltips on the panel do not get dismissed properly
https://bugs.kde.org/show_bug.cgi?id=465650 --- Comment #1 from guimarcalsi...@gmail.com --- Created attachment 156183 --> https://bugs.kde.org/attachment.cgi?id=156183=edit Thumbnail/tooltip does not get dismissed properly -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465650] New: [Wayland] [Graphics Tablet]: When using a stylus, some tooltips on the panel do not get dismissed properly
https://bugs.kde.org/show_bug.cgi?id=465650 Bug ID: 465650 Summary: [Wayland] [Graphics Tablet]: When using a stylus, some tooltips on the panel do not get dismissed properly Classification: Plasma Product: kwin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: guimarcalsi...@gmail.com Target Milestone: --- SUMMARY If you use a stylus as your cursor (with a Wacom tablet), moving over some icons will show tooltips that don't get dismissed properly (specifically tooltips from app icons, like names and window thumbnails). This bug only happens on Wayland and is annoying since it interferes with navigation and activates window previews when the user doesn't want to. Check the attached video for more details. To be honest, stylus navigation on Wayland has lots of bugs. If you notice, on the video, the icons also fail to be highlighted again, and that happens independently of this bug. Using the stylus to navigate the desktop is quite convenient since it doesn't require constant switching between tablet and mouse while making annotations. I'll probably open more bug reports about it. STEPS TO REPRODUCE 1. With a drawing tablet, use your stylus to hover over an open application icon 2. Move up, activating the window thumbnail with the movement 3. Keep moving the cursor up, moving the stylus cursor out of the tooltip OBSERVED RESULT The tooltip stays open for many seconds until it fades. This behavior is different from what happens with a mouse, where the tooltip gets dismissed almost as soon as the cursor leaves it behind. EXPECTED RESULT Tooltips activated from a stylus should behave the same way as a normal mouse cursor. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-60-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 15,6 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series ADDITIONAL INFORMATION Running on Neon Unstable for testing purposes, with updates as of Feb. 11th. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 444976] Dolphin does not generate preview of .heic images
https://bugs.kde.org/show_bug.cgi?id=444976 --- Comment #14 from Yuriy Vidineev --- Installation of kimageformat-plugins doesn't help on KDE Neon user unfortunately kimageformat-plugins/jammy,now 5.102.0-0xneon+22.04+jammy+release+build12 amd64 [installed] additional image format plugins for QtGui -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 465649] New: Default credentials for RDP connections
https://bugs.kde.org/show_bug.cgi?id=465649 Bug ID: 465649 Summary: Default credentials for RDP connections Classification: Applications Product: krdc Version: 22.12.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: xema...@gmail.com CC: aa...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Connect VM 2. Credentials are not passed OBSERVED RESULT 1. Connect VM 2. Credentials are not passed EXPECTED RESULT 1. Connect VM 2. Connection does not prompt for credentials -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465552] Multiple NVIDIA GPU's and Multiple Monitor Configuration Issue.
https://bugs.kde.org/show_bug.cgi?id=465552 --- Comment #2 from kde.y1...@8shield.net --- Yes that is correct. I think I have narrowed the output issue and the screen going blank to a refresh rate issues of some sort. I have to change a couple of the monitors down to a lower refresh rate that is not used in windows. I have all my monitors set to 60 hz in Windows on this same machine and they work fine. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] In a VM, screen will not wake up after Screen Energy Saving activates due to Powerdevil crashing
https://bugs.kde.org/show_bug.cgi?id=465399 --- Comment #7 from Forest --- Another log capture with slightly different messages: Feb 13 04:38:14 neon pulseaudio[1306]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Feb 13 04:48:08 neon org_kde_powerdevil[1526]: org.kde.kscreen.dpms: Failed to query DPMS state, cannot trigger Feb 13 04:48:08 neon org_kde_powerdevil[1526]: XIO: fatal IO error 2 (No such file or directory) on X server ":0" Feb 13 04:48:08 neon org_kde_powerdevil[1526]: after 367 requests (366 known processed) with 0 events remaining. Feb 13 04:48:08 neon org_kde_powerdevil[1526]: The X11 connection broke: Unsupported extension used (code 2) Feb 13 04:48:08 neon systemd[1298]: plasma-powerdevil.service: Main process exited, code=exited, status=1/FAILURE Feb 13 04:48:08 neon systemd[1298]: plasma-powerdevil.service: Failed with result 'exit-code'. Feb 13 04:48:09 neon systemd[1298]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 1. Feb 13 04:48:09 neon systemd[1298]: Stopped Powerdevil. Feb 13 04:48:09 neon systemd[1298]: Starting Powerdevil... Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.kscreen.dpms: DPMS extension not available Feb 13 04:48:09 neon systemd[1298]: Started Powerdevil. Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: Handle button events action could not check for screen configuration Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported Feb 13 04:48:09 neon org_kde_powerdevil[1792]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 465648] Large gap in network list when connecting to a second network
https://bugs.kde.org/show_bug.cgi?id=465648 --- Comment #1 from batle...@gmail.com --- Created attachment 156182 --> https://bugs.kde.org/attachment.cgi?id=156182=edit Gap between the networks after scrolling down -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 465648] New: Large gap in network list when connecting to a second network
https://bugs.kde.org/show_bug.cgi?id=465648 Bug ID: 465648 Summary: Large gap in network list when connecting to a second network Classification: Plasma Product: plasma-nm Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: batle...@gmail.com Target Milestone: --- Created attachment 156181 --> https://bugs.kde.org/attachment.cgi?id=156181=edit Gap between the networks immediately after opening the applet (i have more than two networks) SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When you are already connected to a network and you try to connect to a second network concurrently, the nm applet renders a big gap in the network list. STEPS TO REPRODUCE 1. Connect to a network (wait until fully connected) 2. Start connecting to a second network 3. While it's still connecting (waiting for dhcp), close and re-open the nm applet OBSERVED RESULT There is a large gap between the previously connected network and the currently connecting one EXPECTED RESULT The two networks to be one under each other SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux kernel 5.15.91 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] KWin changes focus when switching virtual desktop with an app that changes its WM_NAME and _NET_WM_NAME at runtime
https://bugs.kde.org/show_bug.cgi?id=465530 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WAITINGFORINFO |--- Summary|Kwin gives unrequested |KWin changes focus when |focus |switching virtual desktop ||with an app that changes ||its WM_NAME and ||_NET_WM_NAME at runtime --- Comment #10 from Nate Graham --- Oh, TIL! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465647] New: Close button on pop-up note is barely visibly (lacks contrast)
https://bugs.kde.org/show_bug.cgi?id=465647 Bug ID: 465647 Summary: Close button on pop-up note is barely visibly (lacks contrast) Classification: Applications Product: okular Version: 22.12.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: sthenujan2...@gmail.com Target Milestone: --- Created attachment 156180 --> https://bugs.kde.org/attachment.cgi?id=156180=edit screenshot of the pop-up note SUMMARY Close button in the popup note of okular lacks contrast STEPS TO REPRODUCE 1. highlight some text in a pdf 2. right click on highlighted text 3. click open pop-up note OBSERVED RESULT Close button is white color so it can barely be seen in yellow background EXPECTED RESULT close button has a different color that gives it enough contrast SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.0.19-3-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: HP Product Name: HP Pavilion x360 Convertible 14-dw1xxx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 Oscar Fuentes changed: What|Removed |Added Resolution|DOWNSTREAM |WAITINGFORINFO --- Comment #9 from Oscar Fuentes --- (In reply to Nate Graham from comment #8) > I don't know 100%, but I do know that changing WM_NAME and _NET_WM_NAME at > runtime is considered to be always wrong by KWin and Plasma developers. Thanks. Sorry, but what you say would amount to not changing the window's title at runtime, so I think there is a misunderstanding here. BTW, Qt ends setting _NET_WM_NAME and, conditionally, also WM_NAME when QWidget::setWindowTitle is called: https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/xcb/qxcbwindow.cpp?h=dev#n2543 What the Emacs developer thinks is happening is that KWin notices that a pseudo-iconified window (I say pseudo-iconified because the window is not on the current virtual desktop) changed its title, and somehow transfers focus to that window when its virtual desktop is shown. I hope a KWin developer will chime in for valuating this hypothesis. Until that happens, can we maintain the bug report status on a suitable state for requesting the attention of such developer? Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 465597] Mini app displays duplicate wired network
https://bugs.kde.org/show_bug.cgi?id=465597 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Can confirm on Arch Linux running Plasma 5.27 beta after updating to networkmanager 1.42. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 328694] Tool tips have huge black rectangles and highlighted items have multicolored stipes when color depth is 16.
https://bugs.kde.org/show_bug.cgi?id=328694 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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.
[konqueror] [Bug 221710] Document Relations stops working after un/minimise on certain sites
https://bugs.kde.org/show_bug.cgi?id=221710 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|UNMAINTAINED|WORKSFORME --- Comment #10 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 --- Comment #8 from Nate Graham --- I don't know 100%, but I do know that changing WM_NAME and _NET_WM_NAME at runtime is considered to be always wrong by KWin and Plasma developers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 --- Comment #7 from Oscar Fuentes --- (In reply to Nate Graham from comment #5) > it depends on the UI toolkit being used, but in Qt, we typically use > QWidget::setWindowTitle(). I don't know what it does under the hood, sorry. Nate, please allow me one more question: do you *know* that the method for changing the window title described on my bug report is wrong? Because I have the impression that you know about Qt, but not about the low level X API calls. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 465646] New: Add UI affordance for reindexing the menu
https://bugs.kde.org/show_bug.cgi?id=465646 Bug ID: 465646 Summary: Add UI affordance for reindexing the menu Classification: Applications Product: kmenuedit Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com Target Milestone: --- I've run into weird issues with the menu (old application path being launched) caused by the fact that Plasma hadn't reindexed it. They were solved by running `kbuildsycoca5`. It would be helpful to have a button that essentially runs that command. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465610] Saved playlists are not loaded correctly
https://bugs.kde.org/show_bug.cgi?id=465610 --- Comment #6 from Scott --- At the moment the visual indicator is only an outline of the icon, perhaps a solid/translucent green of the icon background. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464892] Multi-monitor issues under X11
https://bugs.kde.org/show_bug.cgi?id=464892 --- Comment #10 from Arjan Asadi --- (In reply to kenny.mh.hui from comment #9) > (In reply to Arjan Asadi from comment #8) > > did you select TaskManager Settings > Behavior > Show only Tasks you select > > From current screen as I mentioned? > > If I don't select this my task manager works fine if I select it, it > > disappears > > Nope, it happens regardless. Swapping the monitor doesn't do anything as well > We might be hitting a different bug, does anything above occurs to you apart > from the task manager icon not showing? the only thing I encounter is the task manager disappearing. I click on the "From current screen" and it disappears, click on it again and apply and it appears again. very strange -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 Oscar Fuentes changed: What|Removed |Added Resolution|DOWNSTREAM |WAITINGFORINFO --- Comment #6 from Oscar Fuentes --- (In reply to Nate Graham from comment #5) > it depends on the UI toolkit being used, but in Qt, we typically use > QWidget::setWindowTitle(). I don't know what it does under the hood, sorry. Emacs does not use a UI toolkit (optionally, it uses Gtk for some tasks.) I'll try looking at the sources of Qt then, thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 --- Comment #5 from Nate Graham --- it depends on the UI toolkit being used, but in Qt, we typically use QWidget::setWindowTitle(). I don't know what it does under the hood, sorry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 Oscar Fuentes changed: What|Removed |Added Resolution|DOWNSTREAM |WAITINGFORINFO --- Comment #4 from Oscar Fuentes --- (In reply to Nate Graham from comment #3) > It doesn't need to do that; there are ways to change the window title > without messing with those values. The nonstandard thing it's doing right > now apparently proves confusing to KWin. :) Would you like to give a general indication about what is the correct way of changing the window title? I'll rely your answer to the Emacs developer who implemented that feature. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462002] Mouse cursor stuttering
https://bugs.kde.org/show_bug.cgi?id=462002 Nate Graham changed: What|Removed |Added Resolution|NOT A BUG |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465585] Laptop external display freeze by fullscreen applications
https://bugs.kde.org/show_bug.cgi?id=465585 Nate Graham changed: What|Removed |Added CC||n...@kde.org Target Milestone|1.0 |--- Product|plasmashell |kwin Component|general |multi-screen Resolution|--- |UPSTREAM URL||https://forums.developer.nv ||idia.com/t/525-78-01-nvidia ||-card-hdmi-output-freezes-a ||fter-launching-fullscreen-a ||pplications/236161/12 Status|REPORTED|RESOLVED Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org --- Comment #1 from Nate Graham --- > This bug appeared after an NVIDIA driver update during the 5xx driver version > updates This would indicate that it's the NVIDIA driver's fault. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #3 from Nate Graham --- It doesn't need to do that; there are ways to change the window title without messing with those values. The nonstandard thing it's doing right now apparently proves confusing to KWin. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 --- Comment #2 from Oscar Fuentes --- (In reply to Nate Graham from comment #1) > Why does it do that, though? That's an odd thing for a window to do. I don't know for sure, but I think that's what Emacs does to set the title bar of the iconified window (it seems some window managers support this, including KDE.) Emacs can be configured to use different strings for the iconified and the non-iconified window. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 464147] Support selecting which region to share
https://bugs.kde.org/show_bug.cgi?id=464147 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/xdg-desktop-portal-kde/c ||ommit/6a83f327e9111703fe63a ||69bb6a2ff987278bbfc --- Comment #10 from Aleix Pol --- Git commit 6a83f327e9111703fe63a69bb6a2ff987278bbfc by Aleix Pol Gonzalez, on behalf of Dominique Hummel. Committed on 13/02/2023 at 02:03. Pushed by apol into branch 'master'. Add the ability to stream a rectangular region ## Background On a large panel, current screen casting options could be found lackluster, for different reasons. Streaming the entire screen is usually undesirable, because: - it will look too small on other people's screens (some apps allow zooming, but many don't) - bandwidth is being unnecessarily consumed - large images often incur greater amounts of compression artifacts - usually (but not always), there will be irrelevant sections of the screen which will nonetheless be streamed As a workaround, it is possible to stream a single window. However, this comes with its own problems: - context menus (incl. global menu) are not visible to the viewers - popup windows (e.g. Krita's layer filters) are not visible to the viewers - switching between windows (e.g. code editor and live preview) requires ending and restarting the stream Finally, there are virtual outputs, but since they only exist in virtual space, this means the only way to observe their contents is through the app that is streaming them. Often times, this comes with significant latency and/or reduction in FPS, making it difficult for the streamer to interact with the streamed content. ## Solution This MR adds the ability to stream a rectangular subregion of the user's screen. Upon selecting the output "Rectangular Region" in portal, the user will be prompted to click & drag a rectangular region, which will then subsequently be streamed. The user has the option to reset the region by right-clicking during the drag process, as well as cancelling altogether by pressing Escape, upon which the portal dialog will be reopened. This makes it possible to do the following, without streaming the entire screen: - stream multiple windows at once - stream context menus (incl. global menu) - switch between windows without having to restart the stream ## Preview  ## ToDo's - [x] Wait for https://invent.kde.org/plasma/kwin/-/merge_requests/3561 to be merged (there's currently a KWin bug that incorrectly offsets the y-coordinate of the streamed region) - [x] Test with a multi-monitor setup - [x] ~~Force the regular fade in/-out animation for the overlay~~ not possible (yet) ## Known Issues - When changing the workspace proportions (through adding/removing a new monitor or virtual output) towards negative X or Y (= left or upwards), the streamed region is not correctly preserved, but is instead shifted towards the added space / away from the removed space. ## Relevant Tickets M +3-0CMakeLists.txt M +2-0src/CMakeLists.txt M +6-0src/outputsmodel.cpp M +1-0src/outputsmodel.h M +1-1src/quickdialog.h A +9-0src/region-select/FloatingBackground.qml * A +27 -0src/region-select/FloatingTextBox.qml * A +216 -0src/region-select/RegionSelectOverlay.qml * A +248 -0src/region-select/SelectionEditor.cpp * A +52 -0src/region-select/SelectionEditor.h * M +3-0src/resources.qrc M +5-0src/screencast.cpp M +39 -1src/screenchooserdialog.cpp M +10 -0src/screenchooserdialog.h M +15 -0src/waylandintegration.cpp M +2-0src/waylandintegration.h M +1-0src/waylandintegration_p.h The files marked with a * at the end have a non valid license. Please read: https://community.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://invent.kde.org/plasma/xdg-desktop-portal-kde/commit/6a83f327e9111703fe63a69bb6a2ff987278bbfc -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 465559] ksystemstats turns on disabled nvidia graphics card (possibly, other hardware)
https://bugs.kde.org/show_bug.cgi?id=465559 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 453283 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453283] ksystemstatsd starts nvidia-smi, which prevents GPU from entering powersave on offline use
https://bugs.kde.org/show_bug.cgi?id=453283 Nate Graham changed: What|Removed |Added CC||dvs-1...@yandex.ru --- Comment #14 from Nate Graham --- *** Bug 465559 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 465559] ksystemstats turns on disabled nvidia graphics card (possibly, other hardware)
https://bugs.kde.org/show_bug.cgi?id=465559 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465514] Full Graphical Environment Hangs/Freezes, but System Still Working
https://bugs.kde.org/show_bug.cgi?id=465514 Nate Graham changed: What|Removed |Added Component|core|wayland-generic CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465552] Multiple NVIDIA GPU's and Multiple Monitor Configuration Issue.
https://bugs.kde.org/show_bug.cgi?id=465552 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |WAITINGFORINFO Component|common |general Status|REPORTED|NEEDSINFO Product|KScreen |kwin Assignee|kscreen-bugs-n...@kde.org |kwin-bugs-n...@kde.org --- Comment #1 from Nate Graham --- So you're saying there are multiple issues here? One issue is that the screens' arrangement gets lost on reboot, and the other issue is that sometimes screens show no output despite being enabled in the KScreen KCM? Do I have that right? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Nate Graham changed: What|Removed |Added CC||timofeevsv1...@gmail.com --- Comment #32 from Nate Graham --- *** Bug 465541 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 465541] Screen Locker not blocked by Gamepad
https://bugs.kde.org/show_bug.cgi?id=465541 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 328987 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465530] Kwin gives unrequested focus
https://bugs.kde.org/show_bug.cgi?id=465530 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- Why does it do that, though? That's an odd thing for a window to do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465323] XWayland apps drawing dark pixels on rounded corners
https://bugs.kde.org/show_bug.cgi?id=465323 Nate Graham changed: What|Removed |Added Component|decorations |aurorae -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465323] XWayland apps drawing dark pixels on rounded corners
https://bugs.kde.org/show_bug.cgi?id=465323 Nate Graham changed: What|Removed |Added Component|wayland-generic |decorations Keywords||wayland Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Nate Graham --- Oh I see, you're using a 3rd-party window decoration theme. That's quite relevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465423] "Show In Activities" Taskbar Context Menu Buttons Do Nothing
https://bugs.kde.org/show_bug.cgi?id=465423 --- Comment #6 from Nate Graham --- I think see the problem; the "Move to [other activity]" menu item doesn't move it; it makes the window appear in that other activity in addition to the current one. Can you reproduce that? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 465399] In a VM, screen will not wake up after Screen Energy Saving activates due to Powerdevil crashing
https://bugs.kde.org/show_bug.cgi?id=465399 Nate Graham changed: What|Removed |Added Summary|Screen will not wake up |In a VM, screen will not |after Screen Energy Saving |wake up after Screen Energy |activates |Saving activates due to ||Powerdevil crashing Severity|normal |crash --- Comment #6 from Nate Graham --- Ok so it seems like being run in a VM is important. Seems like maybe we're sending an invalid DBus message and causing the X11 connection to crash. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465645] System tray opens in the middle on ultrawide monitor
https://bugs.kde.org/show_bug.cgi?id=465645 --- Comment #1 from Casper --- Created attachment 156179 --> https://bugs.kde.org/attachment.cgi?id=156179=edit Opens correctly when placed on the left, doesn't, to the right. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465645] New: System tray opens in the middle on ultrawide monitor
https://bugs.kde.org/show_bug.cgi?id=465645 Bug ID: 465645 Summary: System tray opens in the middle on ultrawide monitor Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ctal...@gmail.com Target Milestone: --- I recently added a new monitor to my setup, it is a 1440p ultrawide. My previous main display was standard widescreen, also 1440p. After setting things up, I noticed that expanding anything in the system tray would do so in the middle, never in the top right corner like before. If I place the system tray to the left, or onto my old monitor, it works as expected, and expands right by where it is placed. This only affects the system tray, clicking the clock to open the calendar view works correctly. STEPS TO REPRODUCE 1. Use an ultrawide monitor 2. Place system tray in one of the corners to the right (top and bottom are affected) 3. Click on any icon that should open something OBSERVED RESULT The tray opens in the middle of the panel EXPECTED RESULT It should open right next to where it is placed KDE Plasma Version: 5.26.5 KDE Frameworks Version: 2.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 465644] New: Screen no longer locks after inactivity, when external monitor unplugged and plugged back in.
https://bugs.kde.org/show_bug.cgi?id=465644 Bug ID: 465644 Summary: Screen no longer locks after inactivity, when external monitor unplugged and plugged back in. Classification: Plasma Product: kscreenlocker Version: 5.26.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kdeaa...@iforgotmy.name Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start with a 4K monitor plugged into a laptop, with the 4K monitor screen area to the upper-left of the laptop screen area (desktop is extended). 2. Observe that screen locks after N minutes of inactivity, where N is specified in settings. 3. Unplug monitor and plug it back in. OBSERVED RESULT Screen does not lock after any duration of user inactivity. Screen only locks with Cmd-L, as far as I can tell. EXPECTED RESULT Screen locks after N minutes of inactivity, where N is specified in settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.5, Manjaro (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Samsung 4K monitor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465495] systemsettings no longer shows language dialect in use (if different from rest of locale)
https://bugs.kde.org/show_bug.cgi?id=465495 --- Comment #3 from David Chmelik --- Created attachment 156178 --> https://bugs.kde.org/attachment.cgi?id=156178=edit regional -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465495] systemsettings no longer shows language dialect in use (if different from rest of locale)
https://bugs.kde.org/show_bug.cgi?id=465495 --- Comment #2 from David Chmelik --- Created attachment 156177 --> https://bugs.kde.org/attachment.cgi?id=156177=edit languages -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465641] Wrong text encoding for file names in X11
https://bugs.kde.org/show_bug.cgi?id=465641 Toby changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Toby --- Turned out to be some per-user settings messed up the charmap. Solved after deleting all user config files. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379474] KWin wakes up the monitor right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=379474 em...@thelinuxcast.org changed: What|Removed |Added CC||em...@thelinuxcast.org --- Comment #15 from em...@thelinuxcast.org --- Same issue. Fixed by disabling Kscreen 2 background service. May not be the best solution, but it works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465326] While handling an image in klipper history, Plasma freezes for a some time with 100% CPU usage then crashes
https://bugs.kde.org/show_bug.cgi?id=465326 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |41ac399c39a653cac1d63b3f191 |89d1f0e07955427a083cbc5af34 |3ed4eb2f0d2c3 |e0ae9fdcdaad4 --- Comment #21 from Fushan Wen --- Git commit 89d1f0e07955427a083cbc5af34e0ae9fdcdaad4 by Fushan Wen. Committed on 13/02/2023 at 00:46. Pushed by fusionfuture into branch 'Plasma/5.27'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and Wayland clipboard is async, so another identical image is added to clipboard. Related: bug 465225, bug 464828, bug 465603 FIXED-IN: 5.27 (cherry picked from commit 4649594aa95d601ac6449c9e8baf8201b28602c5) M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/89d1f0e07955427a083cbc5af34e0ae9fdcdaad4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |41ac399c39a653cac1d63b3f191 |89d1f0e07955427a083cbc5af34 |3ed4eb2f0d2c3 |e0ae9fdcdaad4 --- Comment #7 from Fushan Wen --- Git commit 89d1f0e07955427a083cbc5af34e0ae9fdcdaad4 by Fushan Wen. Committed on 13/02/2023 at 00:46. Pushed by fusionfuture into branch 'Plasma/5.27'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and Wayland clipboard is async, so another identical image is added to clipboard. Related: bug 465225, bug 465326, bug 464828 FIXED-IN: 5.27 (cherry picked from commit 4649594aa95d601ac6449c9e8baf8201b28602c5) M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/89d1f0e07955427a083cbc5af34e0ae9fdcdaad4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464828] plasma shell crash
https://bugs.kde.org/show_bug.cgi?id=464828 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |41ac399c39a653cac1d63b3f191 |89d1f0e07955427a083cbc5af34 |3ed4eb2f0d2c3 |e0ae9fdcdaad4 --- Comment #13 from Fushan Wen --- Git commit 89d1f0e07955427a083cbc5af34e0ae9fdcdaad4 by Fushan Wen. Committed on 13/02/2023 at 00:46. Pushed by fusionfuture into branch 'Plasma/5.27'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and Wayland clipboard is async, so another identical image is added to clipboard. Related: bug 465225, bug 465326, bug 465603 FIXED-IN: 5.27 (cherry picked from commit 4649594aa95d601ac6449c9e8baf8201b28602c5) M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/89d1f0e07955427a083cbc5af34e0ae9fdcdaad4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465225] plasmashell crashed in Klipper::saveClipboardHistory() and failed to recover
https://bugs.kde.org/show_bug.cgi?id=465225 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |41ac399c39a653cac1d63b3f191 |89d1f0e07955427a083cbc5af34 |3ed4eb2f0d2c3 |e0ae9fdcdaad4 --- Comment #14 from Fushan Wen --- Git commit 89d1f0e07955427a083cbc5af34e0ae9fdcdaad4 by Fushan Wen. Committed on 13/02/2023 at 00:46. Pushed by fusionfuture into branch 'Plasma/5.27'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and Wayland clipboard is async, so another identical image is added to clipboard. Related: bug 465326, bug 464828, bug 465603 FIXED-IN: 5.27 (cherry picked from commit 4649594aa95d601ac6449c9e8baf8201b28602c5) M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/89d1f0e07955427a083cbc5af34e0ae9fdcdaad4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464627] Windows don't combine in Icons-only Task Manager, if you uncheck "Combine into single button" in Task Manager settings
https://bugs.kde.org/show_bug.cgi?id=464627 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1384 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465610] Saved playlists are not loaded correctly
https://bugs.kde.org/show_bug.cgi?id=465610 --- Comment #5 from Nate Graham --- Heh what do you suggest? Maybe we could give the button text when there's enough room? -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465611] Improvement: Change the app to remember the last location visited or relevant to the current activity.
https://bugs.kde.org/show_bug.cgi?id=465611 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465611] Improvement: Change the app to remember the last location visited or relevant to the current activity.
https://bugs.kde.org/show_bug.cgi?id=465611 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Nate Graham --- In general apps don't let you specify the default location for open or save dialogs; instead they simply remember the last location you did browse to. And Elisa already does that. So I think this is fine the way it is, and adding a specific setting to choose a default location isn't a thing we want to do because it would be configuration overkill, especially for an app like Elisa that's designed to be simple and have behaviors consistent with other apps. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465591] Elisa does not set how much left/right arrow key should affect the time
https://bugs.kde.org/show_bug.cgi?id=465591 --- Comment #3 from Nate Graham --- Sure, feel free to submit another bug report asking for that as a new feature. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465612] Default save name for a playlist is PIAYlIST.m3u8
https://bugs.kde.org/show_bug.cgi?id=465612 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465612] Default save name for a playlist is PIAYlIST.m3u8
https://bugs.kde.org/show_bug.cgi?id=465612 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Nate Graham --- That text isn't in the codebase anywhere either. Your screenshot indicates that a file by that name is present in the history of the popup, so at *some* point, you or someone else typed it. :) Whether it exists or not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |4649594aa95d601ac6449c9e8ba |41ac399c39a653cac1d63b3f191 |f8201b28602c5 |3ed4eb2f0d2c3 --- Comment #6 from Fushan Wen --- Git commit 41ac399c39a653cac1d63b3f1913ed4eb2f0d2c3 by Fushan Wen. Committed on 13/02/2023 at 00:29. Pushed by fusionfuture into branch 'cherry-pick-4649594a'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and KSystemClipboard will emit changed signal on Wayland, so another identical image is added to clipboard. Related: bug 465225, bug 465326, bug 464828 FIXED-IN: 5.27 (cherry picked from commit 4649594aa95d601ac6449c9e8baf8201b28602c5) M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/41ac399c39a653cac1d63b3f1913ed4eb2f0d2c3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465225] plasmashell crashed in Klipper::saveClipboardHistory() and failed to recover
https://bugs.kde.org/show_bug.cgi?id=465225 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |4649594aa95d601ac6449c9e8ba |41ac399c39a653cac1d63b3f191 |f8201b28602c5 |3ed4eb2f0d2c3 --- Comment #13 from Fushan Wen --- Git commit 41ac399c39a653cac1d63b3f1913ed4eb2f0d2c3 by Fushan Wen. Committed on 13/02/2023 at 00:29. Pushed by fusionfuture into branch 'cherry-pick-4649594a'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and KSystemClipboard will emit changed signal on Wayland, so another identical image is added to clipboard. Related: bug 465326, bug 464828, bug 465603 FIXED-IN: 5.27 (cherry picked from commit 4649594aa95d601ac6449c9e8baf8201b28602c5) M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/41ac399c39a653cac1d63b3f1913ed4eb2f0d2c3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465326] While handling an image in klipper history, Plasma freezes for a some time with 100% CPU usage then crashes
https://bugs.kde.org/show_bug.cgi?id=465326 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |4649594aa95d601ac6449c9e8ba |41ac399c39a653cac1d63b3f191 |f8201b28602c5 |3ed4eb2f0d2c3 --- Comment #20 from Fushan Wen --- Git commit 41ac399c39a653cac1d63b3f1913ed4eb2f0d2c3 by Fushan Wen. Committed on 13/02/2023 at 00:29. Pushed by fusionfuture into branch 'cherry-pick-4649594a'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and KSystemClipboard will emit changed signal on Wayland, so another identical image is added to clipboard. Related: bug 465225, bug 464828, bug 465603 FIXED-IN: 5.27 (cherry picked from commit 4649594aa95d601ac6449c9e8baf8201b28602c5) M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/41ac399c39a653cac1d63b3f1913ed4eb2f0d2c3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464828] plasma shell crash
https://bugs.kde.org/show_bug.cgi?id=464828 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |4649594aa95d601ac6449c9e8ba |41ac399c39a653cac1d63b3f191 |f8201b28602c5 |3ed4eb2f0d2c3 --- Comment #12 from Fushan Wen --- Git commit 41ac399c39a653cac1d63b3f1913ed4eb2f0d2c3 by Fushan Wen. Committed on 13/02/2023 at 00:29. Pushed by fusionfuture into branch 'cherry-pick-4649594a'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and KSystemClipboard will emit changed signal on Wayland, so another identical image is added to clipboard. Related: bug 465225, bug 465326, bug 465603 FIXED-IN: 5.27 (cherry picked from commit 4649594aa95d601ac6449c9e8baf8201b28602c5) M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/41ac399c39a653cac1d63b3f1913ed4eb2f0d2c3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465326] While handling an image in klipper history, Plasma freezes for a some time with 100% CPU usage then crashes
https://bugs.kde.org/show_bug.cgi?id=465326 Fushan Wen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||4649594aa95d601ac6449c9e8ba ||f8201b28602c5 Resolution|--- |FIXED Version Fixed In||5.27 --- Comment #19 from Fushan Wen --- Git commit 4649594aa95d601ac6449c9e8baf8201b28602c5 by Fushan Wen. Committed on 12/02/2023 at 15:38. Pushed by fusionfuture into branch 'master'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and KSystemClipboard will emit changed signal on Wayland, so another identical image is added to clipboard. Related: bug 465225, bug 464828, bug 465603 FIXED-IN: 5.27 M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/4649594aa95d601ac6449c9e8baf8201b28602c5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465603] Plasmashell stresses CPU then crashes
https://bugs.kde.org/show_bug.cgi?id=465603 Fushan Wen changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||4649594aa95d601ac6449c9e8ba ||f8201b28602c5 Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.27 --- Comment #5 from Fushan Wen --- Git commit 4649594aa95d601ac6449c9e8baf8201b28602c5 by Fushan Wen. Committed on 12/02/2023 at 15:38. Pushed by fusionfuture into branch 'master'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and KSystemClipboard will emit changed signal on Wayland, so another identical image is added to clipboard. Related: bug 465225, bug 465326, bug 464828 FIXED-IN: 5.27 M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/4649594aa95d601ac6449c9e8baf8201b28602c5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465225] plasmashell crashed in Klipper::saveClipboardHistory() and failed to recover
https://bugs.kde.org/show_bug.cgi?id=465225 Fushan Wen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||4649594aa95d601ac6449c9e8ba ||f8201b28602c5 Version Fixed In||5.27 Resolution|--- |FIXED --- Comment #12 from Fushan Wen --- Git commit 4649594aa95d601ac6449c9e8baf8201b28602c5 by Fushan Wen. Committed on 12/02/2023 at 15:38. Pushed by fusionfuture into branch 'master'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and KSystemClipboard will emit changed signal on Wayland, so another identical image is added to clipboard. Related: bug 465326, bug 464828, bug 465603 FIXED-IN: 5.27 M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/4649594aa95d601ac6449c9e8baf8201b28602c5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464828] plasma shell crash
https://bugs.kde.org/show_bug.cgi?id=464828 Fushan Wen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||5.27 Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||4649594aa95d601ac6449c9e8ba ||f8201b28602c5 Resolution|--- |FIXED --- Comment #11 from Fushan Wen --- Git commit 4649594aa95d601ac6449c9e8baf8201b28602c5 by Fushan Wen. Committed on 12/02/2023 at 15:38. Pushed by fusionfuture into branch 'master'. klipper: store QImage and construct QPixmap only when necessary The mime data from Wayland clipboard is not the exact same image, so two image items are listed (first time restarting plasmashell). But after images are saved to local, they have the same uuid again. So klipper starts to become confused after the second time restarting plasmashell. This is caused by QPixmap::from(QImage).toImage() erasing metadata in the image, and KSystemClipboard will emit changed signal on Wayland, so another identical image is added to clipboard. Related: bug 465225, bug 465326, bug 465603 FIXED-IN: 5.27 M +5-5klipper/historyimageitem.cpp M +2-2klipper/historyimageitem.h M +3-4klipper/historyitem.h https://invent.kde.org/plasma/plasma-workspace/commit/4649594aa95d601ac6449c9e8baf8201b28602c5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464600] 'Report a bug in the current page...' is not available for all KCMs
https://bugs.kde.org/show_bug.cgi?id=464600 Nate Graham changed: What|Removed |Added CC||alexander.loh...@gmx.de --- Comment #4 from Nate Graham --- Other KCMs mentioned in the bug report need to be ported to use JSON metadata before we can do this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464600] 'Report a bug in the current page...' is not available for all KCMs
https://bugs.kde.org/show_bug.cgi?id=464600 --- Comment #3 from Nate Graham --- Git commit 15665a25ce68ccf756222ca77efd8bf52a2bd0db by Nate Graham. Committed on 13/02/2023 at 00:25. Pushed by ngraham into branch 'master'. Set Bug Report URL M +1-0kcm/kcm_kdeconnect.json https://invent.kde.org/network/kdeconnect-kde/commit/15665a25ce68ccf756222ca77efd8bf52a2bd0db -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464600] 'Report a bug in the current page...' is not available for all KCMs
https://bugs.kde.org/show_bug.cgi?id=464600 --- Comment #2 from Nate Graham --- Git commit b95481fddbe5ea06ca11605a2a7de7813c1d7b98 by Nate Graham. Committed on 13/02/2023 at 00:23. Pushed by ngraham into branch 'master'. Set Bug Report URL M +1-0src/kcm_sddm.json https://invent.kde.org/plasma/sddm-kcm/commit/b95481fddbe5ea06ca11605a2a7de7813c1d7b98 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 464521] Open with dialog search does not search all apps
https://bugs.kde.org/show_bug.cgi?id=464521 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/162 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 465643] New: Actions and tools buttons from tools menu dont work
https://bugs.kde.org/show_bug.cgi?id=465643 Bug ID: 465643 Summary: Actions and tools buttons from tools menu dont work Classification: Applications Product: kaddressbook Version: 5.22.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ivanaltamirano02252...@gmail.com CC: to...@kde.org Target Milestone: --- If actually needed I will provide traces but judging the nature of the bug I don't know if it's necessary and from the wiki looks like a pain. STEPS TO REPRODUCE 1. Open KAddressBook 2. Press the fourth and/or fifth button on the tool menu counting from the left OBSERVED RESULT Nothing happens. EXPECTED RESULT A sub-menu opens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.8-arch1-1 KDE Plasma Version: 5.26.5-1 KDE Frameworks Version: 5.26.5-1 Qt Version: 5.15.8+kde+r177-1 ADDITIONAL INFORMATION Also when I add a vCard as a file (.vcf downloaded from google contacts) nothing happens. Only a sub-group called aknoadi-resources... appears but no contacts. I know I will get called out for putting this here. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 461282] Add Cuba holidays
https://bugs.kde.org/show_bug.cgi?id=461282 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kholidays/-/merge_requests/62 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465610] Saved playlists are not loaded correctly
https://bugs.kde.org/show_bug.cgi?id=465610 --- Comment #4 from Scott --- Maybe a GUI tweak for the half blind and half witted. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465611] Improvement: Change the app to remember the last location visited or relevant to the current activity.
https://bugs.kde.org/show_bug.cgi?id=465611 --- Comment #2 from Scott --- To cover all situations it would be best to enable the user to specify a location other than ~/music. For example I would use /mnt/data2/Vaults/Music Vault/ as that is where my music is. On Mon, Feb 13, 2023 at 2:30 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=465611 > > Nate Graham changed: > >What|Removed |Added > > > CC||n...@kde.org > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham --- > It remembers the last-used save location. > > What location are you expecting the save dialog to show by default? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465591] Elisa does not set how much left/right arrow key should affect the time
https://bugs.kde.org/show_bug.cgi?id=465591 --- Comment #2 from Matej Starc --- I did not know of this. Cool. But I still suggest adding an option for this to control how much you want to go back/forward. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 462526] UI/UX - Don't bug user about downloading adblocker filter lists
https://bugs.kde.org/show_bug.cgi?id=462526 Jonah Brüchert changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma-mobile/angelfish/commit/ ||ed206474c41702c65e107f28357 ||b373177ff3302 --- Comment #2 from Jonah Brüchert --- Git commit ed206474c41702c65e107f28357b373177ff3302 by Jonah Brüchert. Committed on 12/02/2023 at 23:12. Pushed by jbbgameich into branch 'master'. Don't ask every time after not downloading the filterlists M +3-0lib/angelfishsettings.kcfg M +2-0src/adblockurlinterceptor.h M +4-0src/contents/ui/AdblockFilterDownloadQuestion.qml M +3-1src/contents/ui/desktop/desktop.qml https://invent.kde.org/plasma-mobile/angelfish/commit/ed206474c41702c65e107f28357b373177ff3302 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465612] Default save name for a playlist is PIAYlIST.m3u8
https://bugs.kde.org/show_bug.cgi?id=465612 Scott changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Scott --- I don't believe that is the case: scott@scottubuntu:~$ locate PlAYliST scott@scottubuntu:~$ -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 462526] UI/UX - Don't bug user about downloading adblocker filter lists
https://bugs.kde.org/show_bug.cgi?id=462526 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma-mobile/angelfish/-/merge_requests/178 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 394401] Allow to resize areas in main window
https://bugs.kde.org/show_bug.cgi?id=394401 --- Comment #5 from Nate Graham --- See https://community.kde.org/Get_Involved/Issue_Reporting#Have_realistic_expectations -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465594] GAMMA Feature request
https://bugs.kde.org/show_bug.cgi?id=465594 --- Comment #3 from Nate Graham --- Thanks, but what's the use case? Why do you want to adjust the gamma? How does it help? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 389848] baloo_file crashes in mdb_put() in LMDB
https://bugs.kde.org/show_bug.cgi?id=389848 Nate Graham changed: What|Removed |Added CC||natalie_clar...@yahoo.de --- Comment #176 from Nate Graham --- *** Bug 465529 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 465529] Baloo file extractor crashes on startup
https://bugs.kde.org/show_bug.cgi?id=465529 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 389848 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 389649] Save order of task manager when manually sorted
https://bugs.kde.org/show_bug.cgi?id=389649 Nate Graham changed: What|Removed |Added CC||alb...@gmail.com --- Comment #5 from Nate Graham --- *** Bug 464685 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
