[kwin] [Bug 449873] Losing focus of active application window when switching
https://bugs.kde.org/show_bug.cgi?id=449873 --- Comment #3 from bastimeyer...@gmail.com --- What can I do to help getting this resolved? I use two activies on my desktop, one for regular usage and one for work related stuff, and switching activities is PAINFUL because of this bug, because focus of the active window is lost every single time, and a mouse click, alt+tab or toggling the desktop-grid is required in order to regain focus, which is incredibly annoying. Please don't ignore this bug. > Perhaps it's related to wayland-related fixes. I'm on X11, btw. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 452801] New: Yakuake doesn't show correctly on monitor with higher resolution
https://bugs.kde.org/show_bug.cgi?id=452801 Bug ID: 452801 Summary: Yakuake doesn't show correctly on monitor with higher resolution Product: yakuake Version: 21.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: h...@kde.org Reporter: yellow.koala2...@fastmail.com Target Milestone: --- Created attachment 148267 --> https://bugs.kde.org/attachment.cgi?id=148267=edit Pictures SUMMARY I think yakuake has a monitor-detecting issue. It cannot work correctly with multi monitors, especially when it works with latte titlebar. STEPS TO REPRODUCE 1. two monitors, one 1080p, another 1440p. Both of them have latte titlebar. 2. put them like P1 in display setting 3. open yakuake on 1440p monitor OBSERVED RESULT Yakuake doesn't drop down from the top of this monitor. It drops down from the line of the top of 1080p monitor. P2 I kill latte, then it can drop down from the top. But it doesn't drop down from the center top, and I have set the position 50. EXPECTED RESULT Yakuake drops down from the center top on the 1440p monitor. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Archlinux 5.17.3-zen1-1-zen (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 452800] New: Ability to set manual snapshots from signal
https://bugs.kde.org/show_bug.cgi?id=452800 Bug ID: 452800 Summary: Ability to set manual snapshots from signal Product: Heaptrack Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: m...@milianw.de Reporter: gdesm...@gnome.org Target Milestone: --- The DATA segment of my application keeps growing when I do some tasks. Ideally I'd like to be able to do something like this to help me debug it: - Send a signal (such as `SIGUSR1`) to trigger a snapshot from heaptrack. - Interact with my app to reproduce the problem. - Send another signal to trigger a second snapshot. - Be able somehow to see the memory which have been allocated (and not freed) between these two snapshots. Does this make sense? I implemented something similar in GStreamer's leaks tracer (see https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/main/subprojects/gstreamer/plugins/tracers/gstleaks.c#L810 ) and it's been quite useful. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 452799] New: Wrong notification text
https://bugs.kde.org/show_bug.cgi?id=452799 Bug ID: 452799 Summary: Wrong notification text Product: kalendar Version: 1.0.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: marco.za...@pm.me CC: c...@carlschwan.eu Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Create a new event (In my case from a synced google calendar account), both created within kalendar or synced from cloud, Setting a notification like 10 minutes before OBSERVED RESULT Wait until 10 minutes before the event: nothing happens. At the time of the event, the notification text is "Your event will start in 10 minutes". Thats wrong. EXPECTED RESULT At the time of the event, the text should say something like "The event is started". Note that the text is "L'evento inizierà tra 10 minuti", so in italian. Luckly this will be just a translation problem SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro on linux 5.17 (but the bug is the same even on the previous kernel) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Glad to help, Zanon Marco -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 452798] New: Request for simple task bar
https://bugs.kde.org/show_bug.cgi?id=452798 Bug ID: 452798 Summary: Request for simple task bar Product: kmymoney Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: pe...@prh.myzen.co.uk Target Milestone: --- I'd like a task bar that toggles between visible and hidden, whenever the mouse pointer enters its region of the display. Just a simple switch, triggered manually with the mouse and not at any other time. I'm running Gentoo Linux with the latest Plasma desktop: kde-plasma/plasma-meta-5.23.5. (I couldn't change the *Product in the first field above.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452780] Expose on the scripting api: NET_WM_BYPASS_COMPOSITOR
https://bugs.kde.org/show_bug.cgi?id=452780 --- Comment #3 from David Edmundson --- I see your point. Though I don't want to introduce a two properties on each client which are maybe in sync maybe not and still have it still awkwardly racey. What I think we would want is: - API to write directly to Compositor::suspend/resume (exposed somehow) - API to set a flag (maybe generic transient config writing) to disable whether updateClientCompositeBlocking does anything Then your script would: - disable updateClientCompositeBlocking from doing anything so your script takes over control - monitor clients - call suspend/disable as appropriate Though in your examples one could also just use Window rules? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452797] kwin_wayland crashed when firefox tried to copy something into the clipboard
https://bugs.kde.org/show_bug.cgi?id=452797 hasez...@gmail.com changed: What|Removed |Added CC||hasez...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452797] New: kwin_wayland crashed when firefox tried to copy something into the clipboard
https://bugs.kde.org/show_bug.cgi?id=452797 Bug ID: 452797 Summary: kwin_wayland crashed when firefox tried to copy something into the clipboard Product: kwin Version: 5.24.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: hasez...@gmail.com Target Milestone: --- SUMMARY Sometimes in kde (wayland) the clipboard starts to stop working (copy paste with CTRL+C CTRL+V), when that happens and a application (in this case firefox) explicitly tries to copy something to the clip-board, it crashes the whole compositor, and it also does not recover from it STEPS TO REPRODUCE i dont know how to get the base conditions, and i did not have it occur again yet, so here are the steps i had took just before the crash: 1. wait until getting the clipboard to stop working (eg meaning CTRL+C CTRL+V dont do anything anymore) 2. use a application that can explicitly copy something into the clipboard (in my case it was firefox) 3. let the application (in my case firefox) copy something into the clipboard 4. observe "kwin_wayland" to dump its core OBSERVED RESULT Full Crash without recovery EXPECTED RESULT No Crash and recovery when crash SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.17.1-3-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX Vega ADDITIONAL INFORMATION I am sorry for not being able to provide more concrete reproduction steps, but i have no clue aside from what i listed on what could have triggered this "coredumpctl gdb NUM" output: Core was generated by `/usr/bin/kwin_wayland --wayland-fd 5 --socket wayland-0 --xwayland-fd 6 --xwayl'. Program terminated with signal SIGSEGV, Segmentation fault. #0 KWaylandServer::SurfaceInterface::isMapped (this=0x0) at /usr/include/qt/QtCore/qscopedpointer.h:116 warning: Source file is more recent than executable. 116 T *operator->() const noexcept [Current thread is 1 (Thread 0x7f2c73e48a80 (LWP 1923))] (gdb) bt #0 KWaylandServer::SurfaceInterface::isMapped() const (this=0x0) at /usr/include/qt/QtCore/qscopedpointer.h:116 #1 0x7f2c7afbda1c in KWaylandServer::SurfaceInterfacePrivate::computeEffectiveMapped() const (this=, this=0x560f164646f0) at /usr/src/debug/kwayland-server-5.24.4/src/server/surface_interface.cpp:681 #2 KWaylandServer::SurfaceInterfacePrivate::updateEffectiveMapped() (this=this@entry=0x560f164646f0) at /usr/src/debug/kwayland-server-5.24.4/src/server/surface_interface.cpp:686 #3 0x7f2c7afc1060 in KWaylandServer::SurfaceInterfacePrivate::applyState(KWaylandServer::SurfaceState*) (this=0x560f164646f0, next=) at /usr/src/debug/kwayland-server-5.24.4/src/server/surface_interface.cpp:604 #4 0x7f2c76fd8d4a in () at /usr/lib/libffi.so.8 #5 0x7f2c76fd8267 in () at /usr/lib/libffi.so.8 #6 0x7f2c781fbaf2 in wl_closure_invoke (closure=closure@entry=0x560f15bcf9c0, target=, target@entry=0x560f160333c0, opcode=opcode@entry=6, data=, data@entry=0x560f15efa110, flags=) at ../wayland-1.20.0/src/connection.c:1025 #7 0x7f2c781ffe14 in wl_client_connection_data (fd=, mask=, data=0x560f15efa110) at ../wayland-1.20.0/src/wayland-server.c:437 #8 0x7f2c781fe84a in wl_event_loop_dispatch (loop=0x560f14992d50, timeout=) at ../wayland-1.20.0/src/event-loop.c:1027 #9 0x7f2c7af86b7b in KWaylandServer::Display::dispatchEvents() (this=) at /usr/src/debug/kwayland-server-5.24.4/src/server/display.cpp:114 #10 0x7f2c79277463 in () at /usr/lib/libQt5Core.so.5 #11 0x7f2c792794e4 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #12 0x7f2c79279faf in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7f2c79d041c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 --Type for more, q to quit, c to continue without paging--c #14 0x7f2c792465aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7f2c79291214 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/libQt5Core.so.5 #16 0x7f2c79292185 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x560f145807e2 in QUnixEventDispatcherQPA::processEvents(QFlags) () #18 0x7f2c7923e88b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f2c79249fd7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #20 0x560f1448f32a in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.24.4/src/main_wayland.cpp:727
[dolphin] [Bug 429579] add the "extension" column
https://bugs.kde.org/show_bug.cgi?id=429579 popov895 changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=152241 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 152241] sort by file type should rely on file extension where mime-type is the same
https://bugs.kde.org/show_bug.cgi?id=152241 popov895 changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=429579 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 452697] It is not possible to enter a currency rate lower than 0.01
https://bugs.kde.org/show_bug.cgi?id=452697 --- Comment #4 from ablanchar...@hotmail.com --- You are right, since when I originally entered 0.65, it was showing 0.00, I never realized it was still saving the value 0.65. So what I described is not a bug. But shouldn't we raise a bug for the display of exchange rate? If I enter 0.65, it should display 0.65 no matter what is the number of decimal. Isn't that correct? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452796] New: The application launcher to follow its panel opacity setting during startup
https://bugs.kde.org/show_bug.cgi?id=452796 Bug ID: 452796 Summary: The application launcher to follow its panel opacity setting during startup Product: plasmashell Version: 5.24.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: es204904...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 https://youtu.be/8O5LCzCGefM -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415111] Yakuake calculates it's size based on the smallest monitor in multi monitor setup
https://bugs.kde.org/show_bug.cgi?id=415111 yellow.koala2...@fastmail.com changed: What|Removed |Added Platform|Other |Archlinux Packages Version|3.0.5 |21.12.3 CC||yellow.koala2162@fastmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452584] Textual list of grouped apps is misplaced
https://bugs.kde.org/show_bug.cgi?id=452584 --- Comment #2 from Fushan Wen --- I wonder if GroupDialog can be created and destroyed on demand without having to always stay in the background, which may fix many bugs. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 452718] Plasma unable to show updates
https://bugs.kde.org/show_bug.cgi?id=452718 --- Comment #6 from Nate Graham --- That means there's an update in Discover that doesn't come from PackageKit. Probably Flatpak or KNS. Can you run Discover with one backend at a time to see where the update comes from? - To run it with only the Flatpak backend, run `plasma-discover --backends flatpak-backend` - To run it with only the KNewStuff backend, run `plasma-discover --backends kns-backend` - To list available backends beyond those, run `plasma-discover --listbackends` -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452795] New: Wish: ability to manually override autofocus algorithm
https://bugs.kde.org/show_bug.cgi?id=452795 Bug ID: 452795 Summary: Wish: ability to manually override autofocus algorithm Product: kstars Version: 3.5.8 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- SUMMARY *** The ekos autofocus routine sometimes struggles: it may include points far enough from critical focus that the HFR calculation goes wrong and throws off the best fit curve,. Also atmospheric conditions like wisps of cloud can sometimes interfere with the success of the routine. Often in cases where the algorithm struggles it's perfectly obvious after the first pass to a human operator where the true minimum of the focal curve is, or you know that it was perfectly well focused for the last sub but it's just doing a time-based focus check and getting confused. It would be fantastic if the ekos autofocus tab had a simple means of selecting the critical focus step, either by clicking on the curve or by entering the step number in a text entry box, and a button to override the algorithm, in effect to say "I'm giving you the true focal position, go to that position immediately and mark the autofocus job as complete". On marking focus as complete in this way a scheduled job would then move on to its next step. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391380] Folder change not always in sync with terminal component
https://bugs.kde.org/show_bug.cgi?id=391380 Patrick Silva changed: What|Removed |Added CC||stefat.fla...@gmail.com --- Comment #8 from Patrick Silva --- *** Bug 452788 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452788] The terminal does not keep up with the dolphin directory
https://bugs.kde.org/show_bug.cgi?id=452788 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 391380 *** -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452794] New: Saving a schedule does not save the associated fits file
https://bugs.kde.org/show_bug.cgi?id=452794 Bug ID: 452794 Summary: Saving a schedule does not save the associated fits file Product: kstars Version: 3.5.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- SUMMARY *** The scheduling tool allows for using a fits file to get an accurate goto reference. When loading a schedule job that had a fits file specified in the config, the fits file location is not restored. *** STEPS TO REPRODUCE 1. Create new schedule item choosing object, sequence file etc. 2. Specify a fits file using the file selector. 3. Save schedule job. 4. Clear the schedule. 5. Load the saved schedule job. 6. Schedule is listed but no longer has the reference fits file listed. OBSERVED RESULT After reloading, the reference fits file is not shown in the job details. EXPECTED RESULT The reference fits file to be used for the job should be shown. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.10 KDE Plasma Version: 5.86 KDE Frameworks Version: 5.86 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452504] KActionCollection static_cast relies on UB
https://bugs.kde.org/show_bug.cgi?id=452504 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/cbafea01e ||8e1056140642f92c7699988afa3 ||40e2 Resolution|--- |FIXED --- Comment #3 from Dmitry Kazakov --- Git commit cbafea01e8e1056140642f92c7699988afa340e2 by Dmitry Kazakov, on behalf of L. E. Segovia. Committed on 20/04/2022 at 11:28. Pushed by dkazakov into branch 'master'. Fix ASAN on KActionCollection* M +19 -17 libs/widgetutils/xmlgui/kactioncollection.cpp M +0-6libs/widgetutils/xmlgui/kactioncollection.h https://invent.kde.org/graphics/krita/commit/cbafea01e8e1056140642f92c7699988afa340e2 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 452793] New: Wish: the ability to edit schedules / sequences while one is running
https://bugs.kde.org/show_bug.cgi?id=452793 Bug ID: 452793 Summary: Wish: the ability to edit schedules / sequences while one is running Product: kstars Version: 3.5.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: aje.ba...@gmail.com Target Milestone: --- When a sequence or a schedule is running, kstars locks out big chunks of the UI until the sequence or schedule stops. This limits usability. The overall wishlist item is somewhat broad so I've tried to break it down into discrete tasks: 1. While a schedule is running, be able to add jobs to the schedule list. If have a few items in a running schedule but decide halfway through the night that I'd like to add another target to image when the scheduler can fit it in, I can't do it without stopping the scheduler, adding the job and restarting the scheduler. This incurs all the overhead of a restart - slew, refocus, plate solve, restart guiding - for no good reason. It would be great if I could drop a new job into the running scheduler. 2. Very similar: be able to edit jobs in a running scheduler. If I decide I don't want job #2 to require focus because job #1 is already focused and theair temperature is dead stable, it would be nice to just be able to turn it off rather than stopping the scheduler, changing the job, restarting and going through all the overhead. 3. Similar, but for sequences. If I'm running a sequence of 36 x 5 minute subs, it might happen that I decide I want to extend it to 48 subs. It would be nice to be able to update the running sequence to extend it rather than having to stop it, add another set of 12 subs and restart the sequence. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen
https://bugs.kde.org/show_bug.cgi?id=452648 Nate Graham changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #22 from Nate Graham --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 429747] Import VPN connection doesnt support wireguard config
https://bugs.kde.org/show_bug.cgi?id=429747 Gilberto Ferreira changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Gilberto Ferreira --- I had this issue solved after last updates. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 452445] Flatpak apps do not follow keyboard layout policy correctly
https://bugs.kde.org/show_bug.cgi?id=452445 Harald Sitter changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||sit...@kde.org Status|REPORTED|NEEDSINFO --- Comment #7 from Harald Sitter --- Are you absolutely certain this works for non-flatpak apps? I can reproduce the problem but it affects all apps and indeed glancing at the code we don't understand why this would only affect flatpak apps. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 452792] New: Environment Canada’s 7 Day Forecast is Incorrectly Displayed as 12 or 13 Day Forecast
https://bugs.kde.org/show_bug.cgi?id=452792 Bug ID: 452792 Summary: Environment Canada’s 7 Day Forecast is Incorrectly Displayed as 12 or 13 Day Forecast Product: kdeplasma-addons Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Weather Assignee: plasma-b...@kde.org Reporter: winghongc...@vivaldi.net Target Milestone: --- Created attachment 148266 --> https://bugs.kde.org/attachment.cgi?id=148266=edit Weather Widget showing a 7-day forecast as a 13-day forecast. SUMMARY In the weather applet, the Environment Canada (ECCC or ENVCAN) 7-day weather forecast is shown as a thirteen-day forecast. Environment Canada weather forecasts give daytime and nighttime conditions and temperatures, instead of one condition and highs and lows for the day. In the Plasma weather report widget, however, the daytime and nighttime conditions are shown as two separate days, leading the 7-day day and night forecast being blown up to 13 days. This is one cause of the bug where the widget is squished in the system tray https://bugs.kde.org/show_bug.cgi?id=394809 but that one aims to better fit a 13-day forecast in the square system tray popup, which is not this bug. STEPS TO REPRODUCE 1. Open the Weather Report (widget) Settings 2. Choose a Canadian city for the Location, using Environment Canada as the source. 3. View the forecast in the widget. OBSERVED RESULT The 7-day forecast incorrectly appears as a 12 or 13-day forecast. It separates daytime and nighttime conditions for each day into two columns. EXPECTED RESULT The 7-day forecast tab should be called “7 Days” and the day/night forecast for each day should not be shown as two separate days. Ideally it would show the forecasts in 2 rows (day and night) and 7 columns (days of the week), just like the Environment Canada website, which would also fit nicely into the systray popup. You may check how Environment Canada weather website displays the forecasts here: https://weather.gc.ca/canada_e.html SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.24 KDE Plasma Version: 5.24 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452780] Expose on the scripting api: NET_WM_BYPASS_COMPOSITOR
https://bugs.kde.org/show_bug.cgi?id=452780
--- Comment #2 from Alberto Salvia Novella ---
They are independent. `NET_WM_BYPASS_COMPOSITOR` (aka the hint) is what the
window requests, and `blocksCompositing` (aka the property) is what kwin is
currently doing with it.
The hint is inmutable, where the property is mutable. Changing the property
doesn't affect the hint, and reading the property doesn't tell what the hint
could be.
Furthermore the hint has three settings (unset, true, false), where the
property has only two (true, false).
This is relevant because through the kwin api you can't really tell what the
windows actually requests. You can only guess, for example, by storing the
initial status of composition for a window. But even then it has corner cases
where you can't really guess.
The rest of properties are unrelated. They are either signals or refer to
different objects. For example for Firefox I get:
resourceClass = firefox
blocksCompositing = false
isBlockingCompositing = undefined
setBlockingCompositing = undefined
blockingCompositingChanged = function() { [native code] }
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen
https://bugs.kde.org/show_bug.cgi?id=452648 --- Comment #21 from Jim Jones --- finished - https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/509 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 452648] the osd volume indicator is displayed in the top left corner of the screen instead of being displayed in the center of the screen
https://bugs.kde.org/show_bug.cgi?id=452648 --- Comment #20 from Jim Jones --- how do i create a merge request? I can only find a new button to create a new issue, checking out the source creating a new branch and trying to push the new branch leads to a You are not allowed to push code to this project. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438315] Kwin crashed in KWin::FocusChain::isUsableFocusCandidate()
https://bugs.kde.org/show_bug.cgi?id=438315 Nicolas Fella changed: What|Removed |Added CC||m...@leyva.me --- Comment #4 from Nicolas Fella --- *** Bug 452785 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452785] KWin Crashes
https://bugs.kde.org/show_bug.cgi?id=452785 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 438315 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446832] Removed file layer generate warnings when linked file doesn't exists anymore
https://bugs.kde.org/show_bug.cgi?id=446832 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/3d2223f53 ||c73b03692b8ae6429809602b6d7 ||2a12 Status|ASSIGNED|RESOLVED --- Comment #2 from Dmitry Kazakov --- Git commit 3d2223f53c73b03692b8ae6429809602b6d72a12 by Dmitry Kazakov. Committed on 20/04/2022 at 09:45. Pushed by dkazakov into branch 'master'. Let File Layers report errors with filesystem via node properties Now the user can see an exclamation mark near the file layer's name when the layer fails to access/parse the linked file. The user can hover the exclamation mark and see what actually hapened. M +16 -1libs/image/kis_layer_properties_icons.cpp M +3-0libs/image/kis_layer_properties_icons.h M +37 -0libs/ui/kis_file_layer.cpp M +13 -0libs/ui/kis_file_layer.h M +56 -31 plugins/dockers/layerdocker/NodeDelegate.cpp M +16 -0plugins/dockers/layerdocker/NodeToolTip.cpp https://invent.kde.org/graphics/krita/commit/3d2223f53c73b03692b8ae6429809602b6d72a12 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 187311] Kopete Accountlist duplicates entry with empty/wrong copies
https://bugs.kde.org/show_bug.cgi?id=187311 Mathias changed: What|Removed |Added CC||math...@public-ip.org --- Comment #28 from Mathias --- Still happens in 21.12.3-r1 on Gentoo Even if I remove .local/share/kopete and .config/kopeterc and start anew: - start kopete - login - see contacts (online and offline) correctly (with their display names and sorted in groups) - logout/close kopete - empty entries in contactlist.xml appear (all as meta-contacts, the only info in the entries is the hexadecimal ContactId) - after restarting kopete and logging in the contact list now includes the real entries and the new empty ones - every closing of kopete adds the exact number of existing real contacts in my contact groups as empty entries, so that the contact lists grows on every closing procedure - deleting the empty entries from the contact list is possible but useless All this has been happening for years. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 451667] Discover priority of flatpak is incorrect. When given beta flathub is given high priority over flathub it gets low priority and vicevera.
https://bugs.kde.org/show_bug.cgi?id=451667 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443834] Discover does not list addons installed via GHNS windows
https://bugs.kde.org/show_bug.cgi?id=443834 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448690] Discover's search is slow if you use it immediately after launching the app
https://bugs.kde.org/show_bug.cgi?id=448690 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418081] packagekit: Apps installed from a file don't get listed
https://bugs.kde.org/show_bug.cgi?id=418081 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401671] Irrelevant behavior while searching in Application Addons and Plasma Addons pages in offline mode
https://bugs.kde.org/show_bug.cgi?id=401671 postix changed: What|Removed |Added CC||pos...@posteo.eu Summary|Irrevant behavior while |Irrelevant behavior while |searching in Application|searching in Application |Addons and Plasma Addons|Addons and Plasma Addons |pages in offline mode |pages in offline mode -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450950] Discover blindly installs first file for content with multiple files available, instead of asking the user and letting them choose, as the GHNS dialog does
https://bugs.kde.org/show_bug.cgi?id=450950 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423231] Search on Updates page is not limited to only available updates
https://bugs.kde.org/show_bug.cgi?id=423231 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 452000] System and user remotes with the same name are ambiguous
https://bugs.kde.org/show_bug.cgi?id=452000 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432844] Search result column is very narrow and can't be resized in widescreen view
https://bugs.kde.org/show_bug.cgi?id=432844 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432845] Discover doesn't weigh higher keywords appearing in application titles
https://bugs.kde.org/show_bug.cgi?id=432845 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452301] resuming from a screen-lock will be a black or corrupted/unresponsive screen
https://bugs.kde.org/show_bug.cgi?id=452301 Russ Hay changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Russ Hay --- This is resolved after the most recent KDE Neon updates.. no longer occurs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452791] Black Screen When Starting Plasma (using Prime/NVIDIA on Wayland)
https://bugs.kde.org/show_bug.cgi?id=452791 --- Comment #1 from Kyrylo Bohdanenko --- Kwin seems to be running as I can open the Konsole window using the Ctrl+Alt+T hotkey. That being said, the scaling is also applied correctly on the Konsole window. Window Switcher (Alt+Tab) works. It seems the problem might be somehow related to QML components. Running ksystemsettings5 results in an abnormal exit printing the following output: $ systemsettings ... irrelevant output about keybindings ... qt.qpa.wayland: Wayland does not support QWindow::requestActivate() [destroyed object]: error 7: importing the supplied dmabufs failed The Wayland connection experienced a fatal error: Protocol error $ echo $? 1 Same 3 lines are produced while running /usr/bin/startplasma-wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452791] New: Black Screen When Starting Plasma (using Prime/NVIDIA on Wayland)
https://bugs.kde.org/show_bug.cgi?id=452791 Bug ID: 452791 Summary: Black Screen When Starting Plasma (using Prime/NVIDIA on Wayland) Product: plasmashell Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: kirill.bogdane...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY This is a result of installing the patched version of QtWayland as a workaround for the crash described in 451976. STEPS TO REPRODUCE 1. Setup * Laptop with Intel & NVIDIA graphics (NVIDIA Prime/Optimus) * Kubuntu 22.04 (Jammy) with updates from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4829 * Wayland session 2. Using prime, select either on-demand (prime-select on-demand) or nvidia (prime-select nvidia) profile 3. Log out and log in (or restart) OBSERVED RESULT User is presented with the black screen. Only cursor is visible. Scaling is not applied EXPECTED RESULT Normal Plasma startup. Scaling should be applied. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 / NVIDIA 510 (proprietary drivers) KDE Plasma Version: Plasma 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Additional QtWayland updates were installed from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4829 See discussion on Debian's GitLab for more info on the patches: https://salsa.debian.org/qt-kde-team/qt/qtwayland/-/merge_requests/5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399502] Sort order chooser for search results disappeared!
https://bugs.kde.org/show_bug.cgi?id=399502 --- Comment #14 from postix --- Created attachment 148265 --> https://bugs.kde.org/attachment.cgi?id=148265=edit Screenshot: Exact Search term not on top of the list Can confirm that I also don't see any possibility to change the order of search result in Discover 5.24.4. Also I'd prefer if there are exact matches, to let them appear on top. Please see the screenshot. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 311597] the save bar resizes the window beyond measure after exiting the fullscreen mode
https://bugs.kde.org/show_bug.cgi?id=311597 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #6 from apache --- Created attachment 148264 --> https://bugs.kde.org/attachment.cgi?id=148264=edit no tabs at the bottom, no scrollbar below miniatures I have the same right after when I click on image file in Dolphin. Gwenview opens with this wrong scaling so that no tabs at the bottom for F4 bar, no scrollbar below miniatures are visible. I use 1440x900 resolution screen. I deleted Gwenview catche and config files but with no result. Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-1-MANJARO (64-bit) Graphics Platform: X11 Graphics Processor: NVA8 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 452718] Plasma unable to show updates
https://bugs.kde.org/show_bug.cgi?id=452718 --- Comment #5 from stringent...@hotmail.com --- Ok, so Discover is still saying that there is 1 update available but pkcon returns -- Getting updates [=] Downloading list of packages [=] Finished [=] There are no updates available at this time. -- That's pretty weird to me. On 19/04/2022 16:08, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=452718 > > --- Comment #4 from Nate Graham --- > What does `pkcon get-updates` show? If it shows things, can you apply the > updates with `pkcon update`? > -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452790] Overwrite when trying to rename a file inside an archive
https://bugs.kde.org/show_bug.cgi?id=452790 Emanuele Spirito changed: What|Removed |Added CC||emaster...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 452790] New: Overwrite when trying to rename a file inside an archive
https://bugs.kde.org/show_bug.cgi?id=452790 Bug ID: 452790 Summary: Overwrite when trying to rename a file inside an archive Product: ark Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: emaster...@gmail.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- Created attachment 148262 --> https://bugs.kde.org/attachment.cgi?id=148262=edit Video recording of the unexpected behaviour SUMMARY When I try to rename a file or a folder while this is inside an archive, the name I write overwrites the previous name so it is very difficult to see what I am writing. STEPS TO REPRODUCE 1. Open an not-empty archive 2. Select a file 3. Choose "Rename" 4. Write the new name OBSERVED RESULT The new name, while writing it, is over the previous name. EXPECTED RESULT The new name, while writing it, is over blank text field. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 452758] Valgrind does not read properly DWARF5 as generated by Clang14
https://bugs.kde.org/show_bug.cgi?id=452758
--- Comment #10 from Lubos Lunak ---
The only remaining issue I can see is that DWARF5 + -gsplit-dwarf does not
output source locations in backtraces. So far I have not been able to find out
which part of Valgrind code is responsible, the furthest I know so far is that
search_one_loctab() does not find the location, possibly because
di->loctab_used is slightly smaller than in non-split case. I also don't see
any difference in DWARF info when compared to split DWARF4 or non-split DWARF5
that would seem relevant (llvm-dwarfdump claims .debug_line are the same in
both cases when generated by GCC 11).
Testcase:
$ cat a.cpp
static int func(int a, int* b)
{
if(*b)
return a + 2;
else
return a - 2;
}
int main()
{
int v;
return func(4, );
}
$ g++-11 -g -gdwarf-5 a.cpp -gsplit-dwarf
$ valgrind ./a.out
...
==22491== Conditional jump or move depends on uninitialised value(s)
==22491==at 0x400559: func(int, int*) (in /home/seli/tmp/a.out)
==22491==by 0x400583: main (in /home/seli/tmp/a.out)
$ g++-11 -g -gdwarf-5 a.cpp
$ valgrind ./a.out
...
==22512== Conditional jump or move depends on uninitialised value(s)
==22512==at 0x400559: func(int, int*) (a.cpp:3)
==22512==by 0x400583: main (a.cpp:12)
--
You are receiving this mail because:
You are watching all bug changes.
[krusader] [Bug 452789] New: Krusader crashes when F3-viewing docx file
https://bugs.kde.org/show_bug.cgi?id=452789 Bug ID: 452789 Summary: Krusader crashes when F3-viewing docx file Product: krusader Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: bugs.kde@e3q.eu CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.2 "Peace of Mind") (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.90.0 Operating System: Linux 5.15.32-gentoo-r1-a x86_64 Windowing System: X11 Distribution: Gentoo/Linux DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I F3-viewed a docx file (by mistake, but still). Obviously, F3-viewing a binary file is usually not what you want, but for example pdf files just get opened in a KPart, this might also be done for other types. If no associated KPart exists, an error message or so should pop up. In any case, crashing is not the right thing to do. - Other: I remember that there was (still is) a bug that caused Krusader to crash when F3-viewing some compressed files. Given that docx files are actually zip files, this may be related. The crash can be reproduced every time. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault [KCrash Handler] #4 0x7a4fd4f61315 in std::__atomic_base::load (__m=, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/atomic_base.h:838 #5 std::atomic::load (__m=, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/atomic:570 #6 QAtomicOps::loadRelaxed (_q_value=...) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #7 QBasicAtomicPointer::loadRelaxed (this=) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 #8 QObjectPrivate::ensureConnectionData (this=) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject_p.h:377 #9 QObjectPrivate::addConnection (this=0x778cb83d7132bf51, signal=signal@entry=3, c=c@entry=0x57e5f73e22b0) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:324 #10 0x7a4fd4f64196 in QObjectPrivate::connectImpl (sender=0x57e5f8132ff0, signal_index=3, receiver=0x57e5f8217730, slot=, slotObj=, type=, types=, senderMetaObject=) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.h:132 #11 0x7a4fd4f6466d in QObject::connectImpl (sender=0x57e5f8132ff0, signal=, receiver=0x57e5f8217730, slot=0x7ffca3243000, slotObj=0x57e5f831bdd0, type=Qt::AutoConnection, types=0x0, senderMetaObject=0x7a4f62f8f960 ) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:5001 #12 0x7a4f62f38da4 in Kerfuffle::Job::connectToArchiveInterfaceSignals() () from /usr/lib64/libkerfuffle.so.21 #13 0x7a4f62f3a3c7 in Kerfuffle::LoadJob::doWork() () from /usr/lib64/libkerfuffle.so.21 #14 0x7a4fd4f65a16 in QObject::event (this=0x57e5f8217730, e=0x57e5f435bc10) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qobject.cpp:1314 #15 0x7a4fd593396f in QApplicationPrivate::notify_helper (this=, receiver=0x57e5f8217730, e=0x57e5f435bc10) at /var/tmp/portage/dev-qt/qtwidgets-5.15.3/work/qtbase-everywhere-src-5.15.3/src/widgets/kernel/qapplication.cpp:3637 #16 0x7a4fd4f3a138 in QCoreApplication::notifyInternal2 (receiver=0x57e5f8217730, event=0x57e5f435bc10) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1064 #17 0x7a4fd4f3d7a5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x57e5f36d4400) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qcoreapplication.cpp:1821 #18 0x7a4fd4f8c853 in postEventSourceDispatch (s=0x57e5f37be010) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qeventdispatcher_glib.cpp:277 #19 0x7a4fd374a16b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #20 0x7a4fd374a428 in ?? () from /usr/lib64/libglib-2.0.so.0 #21 0x7a4fd374a4df in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #22 0x7a4fd4f8c2e4 in QEventDispatcherGlib::processEvents (this=0x57e5f37c34d0, flags=...) at /var/tmp/portage/dev-qt/qtcore-5.15.3/work/qtbase-everywhere-src-5.15.3/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #23 0x7a4fd4f38b2b in QEventLoop::exec (this=this@entry=0x7ffca3243470, flags=..., flags@entry=...) at
[kmail2] [Bug 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 --- Comment #8 from Emanuele Spirito --- I changed the kmail version of the bug to my current version 5.19.2 (aka 21.12.2) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 Emanuele Spirito changed: What|Removed |Added Version|4.9.5 |5.19.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409429] False positives at unexpected location due to failure to recognize cmpeq as a dependency breaking idiom
https://bugs.kde.org/show_bug.cgi?id=409429
Étienne Dupuis changed:
What|Removed |Added
CC||svart.ridd...@gmail.com
--- Comment #4 from Étienne Dupuis ---
The following function allows detection of whether valgrind has the bug or not,
when compiled with clang + AVX2 enabled:
[[clang::optnone]]
static bool checkValgrindBug409429Fixed()
{
if (RUNNING_ON_VALGRIND) {
alignas(32) uint8_t m[32];
__m256i r = *reinterpret_cast(m);
*reinterpret_cast<__m256i *>(m) = _mm256_cmpeq_epi8(r, r);
if ((m[0] != 0xFF) || VALGRIND_COUNT_ERRORS)
return false;
}
return true;
}
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684 --- Comment #7 from Emanuele Spirito --- Created attachment 148261 --> https://bugs.kde.org/attachment.cgi?id=148261=edit Crash log made by KDE crash handler -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 313684] kmail crashes when forwarding email
https://bugs.kde.org/show_bug.cgi?id=313684
Emanuele Spirito changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC||emaster...@gmail.com
Resolution|UNMAINTAINED|---
Ever confirmed|0 |1
--- Comment #6 from Emanuele Spirito ---
It happened to me just today. I cannot reproduce the bug. It happened when I
forwarded an email and then tried to forward another email with same object
("topic" of email, under A,CC).
System Info:
Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.18-200.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
--
You are receiving this mail because:
You are watching all bug changes.
[Spam] [Bug 452787] ** Removed for violation of the KDE Community Code of Conduct **
https://bugs.kde.org/show_bug.cgi?id=452787 Ben Cooksley changed: What|Removed |Added Assignee|zrenf...@gmail.com |n...@kde.org Component|General |Spam Product|Active Window Control |Spam -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 438237] Cannot match the cursor position after having scrolled in the editor
https://bugs.kde.org/show_bug.cgi?id=438237 Emanuele Spirito changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 452787] ** Removed for violation of the KDE Community Code of Conduct **
https://bugs.kde.org/show_bug.cgi?id=452787 Ben Cooksley changed: What|Removed |Added URL|https://www.chhavigarg.com | -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 452787] ** Removed for violation of the KDE Community Code of Conduct **
https://bugs.kde.org/show_bug.cgi?id=452787 Ben Cooksley changed: What|Removed |Added CC||bcooks...@kde.org Summary|Delhi is where I am from|** Removed for violation of |and based. I'm available|the KDE Community Code of |for professional companion, |Conduct ** |domme & switch including| |dinner dates, overnights| |and you can fly me to you. | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 437788] Kded5 asks to open kwallet everytime the system starts
https://bugs.kde.org/show_bug.cgi?id=437788 Emanuele Spirito changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452788] New: The terminal does not keep up with the dolphin directory
https://bugs.kde.org/show_bug.cgi?id=452788 Bug ID: 452788 Summary: The terminal does not keep up with the dolphin directory Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: stefat.fla...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** The terminal does not keep up with quick change of directory on dolphin. If an user quickly change directory on dolphin, e.g. from folder A to B and vice versa, the terminal is pointing at folder A even though the user is operating in folder B (or vice versa). I think the bug is severe because the user could run some commands in the wrong directory. *** STEPS TO REPRODUCE 0. Open dolphin and enable the terminal (F4) 1. Open directory A on dolphin 2. Open directory B on dolphin (e.g. second column pressing F3). 3. Quickly change directory selection with the mouse clicking left and right column (switching from folder A to B). OBSERVED RESULT The terminal can't update its directory quickly enough. EXPECTED RESULT The terminal MUST always point at the directory where the user is operating. SOFTWARE/OS VERSIONS Linux/KDE Plasma: All the distros I tested (from Ubuntu, to Arch to Fedora). (available in About System) KDE Plasma Version: from 5 and above (perhaps even in KDE 4). KDE Frameworks Version: from 5 and above ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 440794] Dolphin needs to be re-opened in order to access MTP device, after state changed between "No file transmission" and "File transmission"
https://bugs.kde.org/show_bug.cgi?id=440794 Méven Car changed: What|Removed |Added CC||meven@kdemail.net --- Comment #13 from Méven Car --- (In reply to fgrigore2003 from comment #12) > The Bug is still present in Dolphin 21.12.3. > Tested in Kubuntu 22.04 That is expected, the fix will be in KDE Gears/Dolphin/kio-extras 22.04. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452732] In Status and Notifications panel, Notifications icon sometimes does nothing
https://bugs.kde.org/show_bug.cgi?id=452732 --- Comment #12 from Kai Uwe Broulik --- I think 69702475e5ae3fda1a4c4a854100ebb4f65e338b might have uncovered a bug. Notifications has a weird popup handling where it does onPressed: wasExpanded and then onClicked: expanded = !wasExpanded; This was/is to avoid some weirdness with continuously triggering the popup or something. However, the systemtray now calls mouseArea.clicked without calling pressed before so the applet gets confused. Unfortunately, there's both a property and function pressed and calling mouseArea.pressed(mouse) ends up calling the property rather than function. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452776] krita flashing krita program windov when moving mouse cursor on window =(
https://bugs.kde.org/show_bug.cgi?id=452776 Halla Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Halla Rempt --- Also, please provide system information -- help->system information for bug reports. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452732] In Status and Notifications panel, Notifications icon sometimes does nothing
https://bugs.kde.org/show_bug.cgi?id=452732 --- Comment #11 from Kai Uwe Broulik --- Can reproduce -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452732] In Status and Notifications panel, Notifications icon sometimes does nothing
https://bugs.kde.org/show_bug.cgi?id=452732 --- Comment #10 from luca --- same behavior in the last kde neon -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #47 from David Redondo --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 451901] Cover Switch/Flip Switch doesn't look as good or perform as well as they used to
https://bugs.kde.org/show_bug.cgi?id=451901 Heinz Wiesinger changed: What|Removed |Added CC||ppr...@liwjatan.org -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 450230] Improve cover and flip switch
https://bugs.kde.org/show_bug.cgi?id=450230 Heinz Wiesinger changed: What|Removed |Added CC||ppr...@liwjatan.org -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 449180] QML Cover Switch and Flip Switch effects has low fps
https://bugs.kde.org/show_bug.cgi?id=449180 Heinz Wiesinger changed: What|Removed |Added CC||ppr...@liwjatan.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452776] krita flashing krita program windov when moving mouse cursor on window =(
https://bugs.kde.org/show_bug.cgi?id=452776 Halla Rempt changed: What|Removed |Added Severity|critical|normal CC||ha...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 450785] Image version hiding not working
https://bugs.kde.org/show_bug.cgi?id=450785 --- Comment #5 from pipo12...@gmx.de --- (In reply to Maik Qualmann from comment #3) > Well, grouping and versioning are completely different things and have > nothing to do with each other. Grouping by filename sets the image that is > smaller in file size as the leader. The idea here is that the RAW image is > larger, so the derived JPG is in front. If you make multiple edits and save, > I would only group the images manually afterwards, then you can make the > image to the leader, which is the correct one. > > Maik Hi Maik, thanks for your feedback and sorry for the late reply. Could you quickly tell me how to make a picture the leader of a group? If I e.g. have original images image.JPG and image.RAW and a jpeg edit image_v1.JPG and group those three, then image.JPG shows as leader of the group. How can I make image_v1.JPG the leader? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 452763] CPU temperature missing for amd CPU
https://bugs.kde.org/show_bug.cgi?id=452763 Artem changed: What|Removed |Added CC||kde_bts@knebergish.fastmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 452782] Temperature sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=452782 Artem changed: What|Removed |Added CC||kde_bts@knebergish.fastmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445920] GPU power sensors missing
https://bugs.kde.org/show_bug.cgi?id=445920 Artem changed: What|Removed |Added CC||kde_bts@knebergish.fastmail ||.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #46 from Martin --- (In reply to diminom...@gmail.com from comment #45) > (In reply to David Redondo from comment #44) > > I am closing this bug since the original issue was fixed. If you have > > another bug such as a missing GPU sensor please file a new bug so we can act > > on it. Like Matthias did with 445920. > > OK, I follow you suggestion, and I create the bug report: > https://bugs.kde.org/show_bug.cgi?id=452782 Oh no, I followed the suggestion too and created my own bug https://bugs.kde.org/show_bug.cgi?id=452763 -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 452787] Delhi is where I am from and based. I'm available for professional companion, domme & switch including dinner dates, overnights and you can fly me to you.
https://bugs.kde.org/show_bug.cgi?id=452787 Chhavi Garg changed: What|Removed |Added URL||https://www.chhavigarg.com -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 452787] New: Delhi is where I am from and based. I'm available for professional companion, domme & switch including dinner dates, overnights and you can fly me to you.
https://bugs.kde.org/show_bug.cgi?id=452787 Bug ID: 452787 Summary: Delhi is where I am from and based. I'm available for professional companion, domme & switch including dinner dates, overnights and you can fly me to you. Product: Active Window Control Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: thechhavig...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- https://www.chhavigarg.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 338365] New client request to fetch valgrind version
https://bugs.kde.org/show_bug.cgi?id=338365
Étienne Dupuis changed:
What|Removed |Added
CC||svart.ridd...@gmail.com
--- Comment #6 from Étienne Dupuis ---
Recently, I stumbled upon https://bugs.kde.org/show_bug.cgi?id=409429. The
issue can be workarounded by manually installing a more recent version of
valgrind on all my runners, and telling my coworkers to do the same on their
development platforms.
I would have liked to include, at the beginning of my executable something like
if (RUNNING_ON_VALGRIND && (VALGRIND_RUNNING_VERSION < 0x316))
abort("Valgrind >= 3.16 required, otherwise expect false positive!");
The patch provided in this ticket would have made that possible.
Thanks for your time!
--
You are receiving this mail because:
You are watching all bug changes.
[kasts] [Bug 451836] Unable to sync podcasts more than once
https://bugs.kde.org/show_bug.cgi?id=451836 --- Comment #18 from b...@mogwai.be --- (In reply to ccamara from comment #17) > I'm not sure of having understood what you were mentioning about keychain > and how to debug it further, but happy to do it. You can enable debug by starting kasts through the following command from the CLI: QT_LOGGING_RULES=org.kde.kasts.sync=true flatpak run org.kde.kasts This will start the flatpak version of kasts and print debug info related to the sync procedure to stdout. If you could paste the output of a sync that has succeeded (probably after deleting .var/app/org.kde.kasts and removing the entry from the keychain), and of a sync that has failed, that would hopefully help me find the root cause. PS It could be that you have to censor sensitive info before pasting it here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452786] New: WAYLAND - Secondary monitors show black screen, no wallpaper, no panels, and no windows. Only cursor.
https://bugs.kde.org/show_bug.cgi?id=452786 Bug ID: 452786 Summary: WAYLAND - Secondary monitors show black screen, no wallpaper, no panels, and no windows. Only cursor. Product: kwin Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ashleysom...@gmail.com Target Milestone: --- Created attachment 148260 --> https://bugs.kde.org/attachment.cgi?id=148260=edit webp version of video STEPS TO REPRODUCE 1. Update to latest 5.4.24-unstable on KDE-neon unstable repos 2. Have second monitor attached and configured 3. Log into Wayland session OBSERVED RESULT My primary monitor is fine, but the secondary monitors to the left and the right are not showing my desktop background, my panels, or any windows. It shows the mouse fine. The monitors are outputting the correct resolution, and the correct rotation and offset as can be seen by the mouse pointer icon. Both monitors were working well yesterday. This morning I pulled in some updates, and restarted my session, and now I'm seeing this. Video of bug: https://i.redd.it/7q58klefjmu81.gif SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.4.git+unstable KDE Frameworks Version: 5.93.0.git+unstable (Note, if this bug is filed against the wrong product, please re-assign it). -- You are receiving this mail because: You are watching all bug changes.
