[kdenlive] [Bug 448178] crash on Wayland when clicking on Logging (Kubuntu/PPA)
https://bugs.kde.org/show_bug.cgi?id=448178 --- Comment #8 from Jean-Baptiste Mardelle --- Git commit 1d5847a4ffd6f330a65187723d0d826dacb71dce by Jean-Baptiste Mardelle. Committed on 28/02/2022 at 07:47. Pushed by mardelle into branch 'release/21.12'. Fix Wayland crash on layout switch. M +1-1src/layoutmanagement.cpp M +8-0src/mainwindow.cpp M +2-0src/mainwindow.h https://invent.kde.org/multimedia/kdenlive/commit/1d5847a4ffd6f330a65187723d0d826dacb71dce -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450454] Crash when previewing online resource from Freesound
https://bugs.kde.org/show_bug.cgi?id=450454 --- Comment #2 from mau --- Works again (tested with first link), thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 448501] Graphical representation of keyframe level disappears at Zoom Level 18
https://bugs.kde.org/show_bug.cgi?id=448501 --- Comment #4 from Jean-Baptiste Mardelle --- Git commit a582fd66d71e2a55351fab5eab26f8e9bae69d6e by Jean-Baptiste Mardelle. Committed on 28/02/2022 at 07:35. Pushed by mardelle into branch 'release/21.12'. Fix timeline keyframes sometimes disappearing from view. M +22 -4src/timeline2/view/qml/Clip.qml M +19 -3src/timeline2/view/qml/Composition.qml M +19 -5src/timeline2/view/qml/KeyframeView.qml https://invent.kde.org/multimedia/kdenlive/commit/a582fd66d71e2a55351fab5eab26f8e9bae69d6e -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 450426] OFX import fails: Unable to find the DTD named opensp.dcl
https://bugs.kde.org/show_bug.cgi?id=450426 --- Comment #14 from Thomas Baumgart --- Git commit 3022d9b0db11d01a96457ecae3a469282d8dd7ab by Thomas Baumgart. Committed on 28/02/2022 at 07:40. Pushed by tbaumgart into branch 'master'. Fix path to DTD on Windows M +6-0kmymoney/plugins/ofx/import/ofximporter.cpp https://invent.kde.org/office/kmymoney/commit/3022d9b0db11d01a96457ecae3a469282d8dd7ab -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450692] Vectorscope manual page has invalid links
https://bugs.kde.org/show_bug.cgi?id=450692
--- Comment #2 from mau ---
Second link ("here") is working fine, but there is still the first one ("See
Granjow’s blog here") which is pointing to the page itself (doesn't make
sense).
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 450927] Equities with zero balance option does not work
https://bugs.kde.org/show_bug.cgi?id=450927 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Thomas Baumgart --- To me it looks like the Asset and Liability section with a lot of columns disabled (via settings). In addition to Jack's questions: What type of account are these? I doubt that these are equity accounts but can think of them being investment accounts. Equity accounts are always sub-accounts of investment accounts. And a probably unrelated question: why do you have the same (investment) account name multiple times? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 185570] changing account type not possible
https://bugs.kde.org/show_bug.cgi?id=185570 --- Comment #7 from Thomas Baumgart --- It is probably easier to explain what can be changed. You can change freely between 'Cash', 'Savings' and 'Checkings'. All others are fixed. We can certainly add more powers here but this might cause other trouble down the line. The code is located (currently) at https://invent.kde.org/office/kmymoney/-/blob/master/kmymoney/dialogs/knewaccountdlg.cpp#L273 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443434] Window resizing broken when using wobbly windows + resize effects
https://bugs.kde.org/show_bug.cgi?id=443434 Timothy B changed: What|Removed |Added CC||yule2...@live.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450942] Save button improvement
https://bugs.kde.org/show_bug.cgi?id=450942 Christoph Cullmann changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- It is a design decision to always be able to save, e.g. to touch a file. Therefore sorry, we will not disable the save action. There are enough other indicators like changed window/tab caption. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 450952] New: unhandled instruction bytes on a program which executes normally outside valgrind
https://bugs.kde.org/show_bug.cgi?id=450952 Bug ID: 450952 Summary: unhandled instruction bytes on a program which executes normally outside valgrind Product: valgrind Version: 3.18.1 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: rincebr...@gmail.com Target Milestone: --- Created attachment 147181 --> https://bugs.kde.org/attachment.cgi?id=147181=edit the erroring function after being passed through gcc -E SUMMARY I was running a benchmark of some different hashes, and encountered a strange error at the very end. So I fired up valgrind, and instead, about halfway through the benchmark, it dies with SIGILL on: vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xEE 0xC5 0xA1 0x73 0xD1 0x2C 0xC5 vex amd64->IR: REX=0 REX.W=0 REX.R=1 REX.X=0 REX.B=0 vex amd64->IR: VEX=1 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==2654301== valgrind: Unrecognised instruction at address 0x4aec8b4. ==2654301==at 0x4AEC8B4: _mm_set_epi64x (emmintrin.h:592) ==2654301==by 0x4AEC8B4: _mm_set_epi64 (emmintrin.h:598) ==2654301==by 0x4AEC8B4: _mm_loadl_epi64 (emmintrin.h:709) ==2654301==by 0x4AEC8B4: sseu2KeccakPermutationOnWordsAfterXoring1344bits (KeccakF-1600-opt64.c:302) ==2654301==by 0x4AE96B3: Keccak256_sseu2_Absorb (Keccak-sseu2-common.inc:204) [...] The binary was compiled with -march=native -O3 -ftree-vectorize on gcc 9.3, the code is from the sseu2 implementation of Keccak in SUPERCOP (https://bench.cr.yp.to/supercop.html). The segment that it seems upset about appears to be in the middle here (there are no other c5 79 d6 ee in the function): 29d867: c4 c1 61 73 d3 3f vpsrlq $0x3f,%xmm11,%xmm3 29d86d: c4 c1 01 73 f3 01 vpsllq $0x1,%xmm11,%xmm15 29d873: c5 b9 6c e1 vpunpcklqdq %xmm1,%xmm8,%xmm4 29d877: c5 01 eb fb vpor %xmm3,%xmm15,%xmm15 29d87b: c5 01 ef f9 vpxor %xmm1,%xmm15,%xmm15 29d87f: c5 c9 73 d4 3f vpsrlq $0x3f,%xmm4,%xmm6 29d884: c5 f9 70 c9 ee vpshufd $0xee,%xmm1,%xmm1 29d889: c5 d9 73 f4 01 vpsllq $0x1,%xmm4,%xmm4 29d88e: c5 d9 eb e6 vpor %xmm6,%xmm4,%xmm4 29d892: c5 c9 73 d1 3f vpsrlq $0x3f,%xmm1,%xmm6 29d897: c5 f1 73 f1 01 vpsllq $0x1,%xmm1,%xmm1 29d89c: c4 c1 59 ef db vpxor %xmm11,%xmm4,%xmm3 29d8a1: c5 f1 eb ce vpor %xmm6,%xmm1,%xmm1 29d8a5: c4 c1 71 ef e0 vpxor %xmm8,%xmm1,%xmm4 29d8aa: c5 79 70 c3 ee vpshufd $0xee,%xmm3,%xmm8 29d8af: c5 b9 ef 4d a0 vpxor -0x60(%rbp),%xmm8,%xmm1 29d8b4: c5 79 d6 ee vmovq %xmm13,%xmm6 29d8b8: c5 a1 73 d1 2c vpsrlq $0x2c,%xmm1,%xmm11 29d8bd: c5 f1 73 f1 14 vpsllq $0x14,%xmm1,%xmm1 29d8c2: c4 c1 71 eb cb vpor %xmm11,%xmm1,%xmm1 29d8c7: c5 c9 ef f4 vpxor %xmm4,%xmm6,%xmm6 29d8cb: c4 c1 21 73 dd 08 vpsrldq $0x8,%xmm13,%xmm11 29d8d1: c5 c9 6c f1 vpunpcklqdq %xmm1,%xmm6,%xmm6 The preprocessed version of this function (which I'm sharing because the code in question is a morass of twelve degrees of preprocessor macros) can be found attached. OBSERVED RESULT SIGILL EXPECTED RESULT Running application SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 with a homebuilt 3.18.1 after the distro-provided 3.15.0 died the same way. ADDITIONAL INFORMATION I'm sorry if this is a dupe, it's difficult to sift through the unhandled opcodes bugs, for me, but I couldn't immediately turn up a similar one. Closest I found was https://bugs.kde.org/show_bug.cgi?id=417572. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450613] wayland: wakeup after screenlock does not refresh the screen properly
https://bugs.kde.org/show_bug.cgi?id=450613 vryko...@hotmail.com changed: What|Removed |Added CC||vryko...@hotmail.com Platform|Fedora RPMs |Manjaro --- Comment #4 from vryko...@hotmail.com --- (In reply to galder from comment #3) > Hello, > I followed your steps and worked as expected. I'm not sure what could it be. > Lets see if other users reports same issue. > Regards I confirm this issue with wayland 1.20.0-1, using KDE Plasma. I noticed it within the last ~1 week (maybe after a recent update)? To test, I switched to X11 compositor (instead of wayland), and the screen unlock did NOT have a problem. So it seems (to me) the issue is with wayland, while X11 worked fine. To reproduce: 1) lock screen (meta-L) 2) unlock screen -wayland didn't show my desktop (only mouse cursor). A workaround is to press CTRL+ESC, and then it opens task manager and the desktop properly. -X11 was able to unlock fine. I'm not a developer, and I'd say I'm beginner to medium experience (not advanced, not a developer). Using T490 on Linux Manjaro, kernel 5.15.21-1-MANJARO x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448336] Monitor Not Showing Login Screen & Fonts Don't Display Properly if Monitor is Turned on after PC
https://bugs.kde.org/show_bug.cgi?id=448336 cachand...@runbox.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from cachand...@runbox.com --- This issue seems to have been resolved with KDE 5.24. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450951] New: Syntax highlighting mode not persisting across file (auto)reload when set in status bar menu
https://bugs.kde.org/show_bug.cgi?id=450951
Bug ID: 450951
Summary: Syntax highlighting mode not persisting across file
(auto)reload when set in status bar menu
Product: kate
Version: Git
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: david.av.schlos...@gmail.com
Target Milestone: ---
SUMMARY
After manually selecting the file mode from the status bar menu, thus
implicitly selecting the syntax highlighting mode, the syntax highlighting mode
does not get persisted across file reloading or auto-reloading, despite the
file mode and the status bar menu button text remaining unchanged. If the
document's file type can't be determined automatically, i.e. it has no known
file extension nor a recognizable mime-type, the highlighting disappears
altogether (set to None), even though the user probably feels like they made
their preference pretty explicit.
STEPS TO REPRODUCE
1. Open kate/kwrite and fill a new file with something unrecognizable to
mime-magic (or /usr/bin/file), but still valid for syntax highlighting. INI for
example:
```
[Some Group]
SomeEntry=Some Value
```
2. Save the file without a file extension (e.g. /tmp/testrc)
3. Select the mode corresponding to the syntax from the status bar menu.
(Configuration/INI Files, in this case)
4. Reload the file (F5)
OBSERVED RESULT
The syntax highlighting disappears (reverts to None, more precisely), despite
the status bar menu still displaying the correct mode.
EXPECTED RESULT
The selected syntax highlighting mode persists after the file is reloaded.
SOFTWARE/OS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-32-generic (64-bit)
Graphics Platform: X11
ADDITIONAL INFORMATION
This issue arose while watching changes to *rc configs live using autoreload,
and their file type (INI) is often not detected automatically.
While this issue can be fixed by manually selecting the highlighting mode from
Tools/Highlighting in the menu bar, that's not probably not immediately obvious
to most users, at least it wasn't to me, and probably leads people to tediously
select the same, seemingly already selected mode from the status bar menu after
the reload, as I first did.
My suggestion is simply to mark the highlighting mode, in addition to the file
mode, as having been user selected (`m_hlSetByUser = true;`), when chosen from
the status bar menu. Otherwise, the menu's tooltip ("Syntax highlighting") is
rather misleading, even to those who understand the distinction between file
mode and highlighting mode, because it actually selects the file mode and only
sets the highlighting mode indirectly.
Here's a very simple fix I propose:
In ktexteditor/src/mode/katemodemenulist.cpp:506
```
// Apply syntax highlighting
KTextEditor::DocumentPrivate *doc = m_doc;
if (doc && item->hasMode()) {
+++ // Mark highlighting mode as being user-selected
+++ doc->setDontChangeHlOnSave();
doc->updateFileType(item->getMode()->name, true);
}
```
As an aside, the function `setDontChangeHlOnSave` could probably use a more
general name, or just be made into generic setter. It just marks the
highlighting as being user-selected and can be applied outside of just saving,
like reloading in this case.
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 450950] New: Discover installs older version of "Win7 Volume Mixer" instead of latest available
https://bugs.kde.org/show_bug.cgi?id=450950 Bug ID: 450950 Summary: Discover installs older version of "Win7 Volume Mixer" instead of latest available Product: Discover Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KNewStuff Backend Assignee: lei...@leinir.dk Reporter: ber...@codewiz.org CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open plasma-discover 2. Search for "win7 volume" 3. Note how the version reported in the UI is "26, released on 01/12/2020" 3. Click Install 4. A new volume applet will appear in the System Tray 5. Right-click on it and select "Audio Volume Settings..." 6. In the settings dialog, go to About OBSERVED RESULT "Audio Volume (Win7 Mixer) 25" .local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/metadata.desktop also contains "X-KDE-PluginInfo-Version=26" EXPECTED RESULT Version 26 should have been installed. If you download volumewin7mixer-v26-plasma5.12.plasmoid from https://store.kde.org/p/1100894/ and unzip it in the right place, you'll get version 26. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.25.80 (git) KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 + kde -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450949] New: Discover crashed in KNSBackend while uninstalling a plasma widget
https://bugs.kde.org/show_bug.cgi?id=450949
Bug ID: 450949
Summary: Discover crashed in KNSBackend while uninstalling a
plasma widget
Product: Discover
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: discover
Assignee: lei...@leinir.dk
Reporter: ber...@codewiz.org
CC: aleix...@kde.org
Target Milestone: ---
Application: plasma-discover (5.24.80)
(Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.92.0
Operating System: Linux 5.16.11-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.24.80 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
1. Open plasma-discover from a terminal
2. Search for "win7 volume" (previously installed in a separate Discover
instance)
3. Click on the installed result
4. Click "Remove"
5. Discover crashes as shown in the stack trace
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted
Content of s_kcrashErrorMessage: {_M_t = { >> = {_M_t = std::tuple containing = {[1] = 0x0,
[2] = {}}}, }}
[KCrash Handler]
#5 0x7fd738e7b34c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#6 0x7fd738e2e4b8 in raise () at /usr/lib/libc.so.6
#7 0x7fd738e18534 in abort () at /usr/lib/libc.so.6
#8 0x7fd7393beee4 in qt_assert(char const*, char const*, int) () at
/usr/lib/libQt5Core.so.5
#9 0x7fd7393bef44 in qt_assert_x(char const*, char const*, char const*,
int) () at /usr/lib/libQt5Core.so.5
#10 0x7fd7057d6ad0 in KNSBackend::setResponsePending(bool)
(this=0x5619cf0d86a0, pending=false) at
/home/bernie/kde/src/discover/libdiscover/backends/KNSBackend/KNSBackend.cpp:240
#11 0x7fd7057d8c6e in operator()() const (__closure=0x5619d00fba40) at
/home/bernie/kde/src/discover/libdiscover/backends/KNSBackend/KNSBackend.cpp:724
#12 0x7fd7057dc6e5 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, KNSBackend::findResourceByPackageName(const
QUrl&):: >::call(struct {...} &, void
**) (f=..., arg=0x5619d140bac8) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#13 0x7fd7057dc261 in
QtPrivate::Functor, 0>::call,
void>(struct {...} &, void *, void **) (f=..., arg=0x5619d140bac8) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#14 0x7fd7057dbec0 in
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=1, this_=0x5619d00fba30, r=0x5619cf0d86a0, a=0x5619d140bac8, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#15 0x7fd7395cfdc6 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#16 0x7fd73a9a31a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#17 0x7fd7395abb9a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#18 0x7fd7395ac699 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#19 0x7fd7395f3bd8 in () at /usr/lib/libQt5Core.so.5
#20 0x7fd737e70ee3 in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#21 0x7fd737ec70f9 in () at /usr/lib/libglib-2.0.so.0
#22 0x7fd737e6e455 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#23 0x7fd7395f7ada in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#24 0x7fd7395a3e6b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#25 0x7fd7395af5c7 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#26 0x5619cd9abee7 in main(int, char**) (argc=1, argv=0x7ffc55a1ed38) at
/home/bernie/kde/src/discover/discover/main.cpp:217
[Inferior 1 (process 5835) detached]
Possible duplicates by query: bug 445052, bug 419428, bug 330999, bug 330615,
bug 330486.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 425265] Discover shows error messages and gets stuck in "installing" state after I cancel update of SDDM theme from KDE Store
https://bugs.kde.org/show_bug.cgi?id=425265 --- Comment #2 from Bernie Innocenti --- Related bugs: #450948 and #413516 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413516] There's no API for cancelling installation of KNS assets
https://bugs.kde.org/show_bug.cgi?id=413516 --- Comment #2 from Bernie Innocenti --- Related bugs: #450948 and #425265 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450948] New: No installable candidates in the KNewStuff entry "..." with id "..." on the backend "plasmoids.knsrc"
https://bugs.kde.org/show_bug.cgi?id=450948 Bug ID: 450948 Summary: No installable candidates in the KNewStuff entry "..." with id "..." on the backend "plasmoids.knsrc" Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KNewStuff Backend Assignee: lei...@leinir.dk Reporter: ber...@codewiz.org CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover finds the "Win7 Volume Mixer" plasmoid, but is unable to install it. The installation gets stuck as described in bug #413516 and bug #425265. STEPS TO REPRODUCE 1. Run plasma-discover from a terminal and search for "win7 volume" 2. Click Install 3. (I think I uninstalled and re-installed a second time, but not so sure) Discover will print this on stdout: No installable candidates in the KNewStuff entry "Win7 Volume Mixer" with id "1100894" on the backend "plasmoids.knsrc" There should always be at least one downloadable item in an OCS entry, and if there isn't, we should consider it broken. OCS can technically show them, but if there is nothing to install, it cannot be installed. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.80 (git) KDE Frameworks Version: 5.92.0 (git) Qt Version: 5.15.2 + kde (ArchLinux) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 425265] Discover shows error messages and gets stuck in "installing" state after I cancel update of SDDM theme from KDE Store
https://bugs.kde.org/show_bug.cgi?id=425265 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org Status|REPORTED|CONFIRMED Component|discover|KNewStuff Backend Ever confirmed|0 |1 --- Comment #1 from Bernie Innocenti --- This seems to be a KNewStuff backend bug. It just happened to me with Discover and KF built from git master today. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413516] There's no API for cancelling installation of KNS assets
https://bugs.kde.org/show_bug.cgi?id=413516 Bernie Innocenti changed: What|Removed |Added CC||ber...@codewiz.org --- Comment #1 from Bernie Innocenti --- The UI has changed in Discover 5.24.80, but the problem remains: an addon failed to install, and the corresponding task hung with no way to cancel it. I'll file a separate bug for the installation failing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450052] Plasma flashes black around app when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=450052 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352130] helgrind reports false races for printfs using mempcpy manipulating FILE* state
https://bugs.kde.org/show_bug.cgi?id=352130
--- Comment #3 from Godmar Back ---
I am seeing the same or a very similar issues in valgrind 3.18.1 on Ubuntu
20.04 LTS with GNU LibC 2.5
The attached test program results in:
```c
==952377== Helgrind, a thread error detector
==952377== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al.
==952377== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==952377== Command: ./ptest
==952377==
thread1
==952377== ---Thread-Announcement--
==952377==
==952377== Thread #1 is the program's root thread
==952377==
==952377== ---Thread-Announcement--
==952377==
==952377== Thread #2 was created
==952377==at 0x49BE282: clone (clone.S:71)
==952377==by 0x48812EB: create_thread (createthread.c:101)
==952377==by 0x4882E0F: pthread_create@@GLIBC_2.2.5 (pthread_create.c:817)
==952377==by 0x4846FBA: pthread_create_WRK (hg_intercepts.c:445)
==952377==by 0x48480BD: pthread_create@* (hg_intercepts.c:478)
==952377==by 0x109203: main (in /home/gback/cs3214/dutchblitz/ptest)
==952377==
==952377==
==952377==
==952377== Possible data race during write of size 1 at 0x5292193 by thread #1
==952377== Locks held: none
==952377==at 0x484C812: mempcpy (vg_replace_strmem.c:1668)
==952377==by 0x492E7B1: _IO_new_file_xsputn (fileops.c:1236)
==952377==by 0x492E7B1: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1197)
==952377==by 0x4923677: puts (ioputs.c:40)
==952377==by 0x10920F: main (in /home/gback/cs3214/dutchblitz/ptest)
==952377== Address 0x5292193 is 3 bytes inside a block of size 1,024 alloc'd
==952377==at 0x483E8D5: malloc (vg_replace_malloc.c:381)
==952377==by 0x4920E83: _IO_file_doallocate (filedoalloc.c:101)
==952377==by 0x493104F: _IO_doallocbuf (genops.c:347)
==952377==by 0x49300AF: _IO_file_overflow@@GLIBC_2.2.5 (fileops.c:745)
==952377==by 0x492E834: _IO_new_file_xsputn (fileops.c:1244)
==952377==by 0x492E834: _IO_file_xsputn@@GLIBC_2.2.5 (fileops.c:1197)
==952377==by 0x4923677: puts (ioputs.c:40)
==952377==by 0x1091C4: thread1 (in /home/gback/cs3214/dutchblitz/ptest)
==952377==by 0x48471B2: mythread_wrapper (hg_intercepts.c:406)
==952377==by 0x4882608: start_thread (pthread_create.c:477)
==952377==by 0x49BE292: clone (clone.S:95)
==952377== Block was alloc'd by thread #2
==952377==
main
==952377==
==952377== Use --history-level=approx or =none to gain increased speed, at
==952377== the cost of reduced accuracy of conflicting-access information
==952377== For lists of detected and suppressed errors, rerun with: -s
==952377== ERROR SUMMARY: 4 errors from 1 contexts (suppressed: 19 from 19)
```
The bug fix Mark proposed in 2015 included a suppression. I have been looking
for related suppressions in the 3.18.1 codebase, finding
```
{
helgrind-glibc-io-xsputn-mempcpy
Helgrind:Race
fun:__GI_mempcpy
fun:_IO_*xsputn*
obj:*/lib*/libc-2.*so*
}
```
and
```
Ubuntu804-hack-1
Memcheck:Overlap
fun:mempcpy
fun:_IO_default_xsputn
obj:/lib*/libc-2.*so*
}
```
Running with `--gen-suppressions=yes` however, generates:
```
{
Helgrind:Race
fun:mempcpy
fun:_IO_new_file_xsputn
fun:_IO_file_xsputn@@GLIBC_2.2.5
fun:puts
fun:main
}
```
which appears incompatible with those suppressions if I read this correctly.
Should this bug be reopened or a new bug be filed, or is there some other
explanation?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 445877] Kickoff shows up in the bottom middle instead of bottom left corner (only with Wayland)
https://bugs.kde.org/show_bug.cgi?id=445877 Nate Graham changed: What|Removed |Added Summary|K-Menu shows up in the |Kickoff shows up in the |bottom middle instead of|bottom middle instead of |bottom left corner (only|bottom left corner (only |with Wayland) |with Wayland) -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 312325] password dialog should always move to front
https://bugs.kde.org/show_bug.cgi?id=312325 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 312325] password dialog should always move to front
https://bugs.kde.org/show_bug.cgi?id=312325 Nate Graham changed: What|Removed |Added Priority|NOR |HI Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 312325] password dialog should always move to front
https://bugs.kde.org/show_bug.cgi?id=312325 Nate Graham changed: What|Removed |Added CC||luc...@gmail.com --- Comment #20 from Nate Graham --- *** Bug 420786 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420786] Password request window should be application-modal
https://bugs.kde.org/show_bug.cgi?id=420786 --- Comment #4 from Nate Graham --- *** This bug has been marked as a duplicate of bug 312325 *** -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 312325] password dialog should always move to front
https://bugs.kde.org/show_bug.cgi?id=312325 Nate Graham changed: What|Removed |Added CC||shubham.chaudhary@kdemail.n ||et --- Comment #19 from Nate Graham --- *** Bug 407592 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 407592] Authentication popup does not always appear on top of the window that spawned it
https://bugs.kde.org/show_bug.cgi?id=407592 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Nate Graham --- Oh, you're right! *** This bug has been marked as a duplicate of bug 312325 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352130] helgrind reports false races for printfs using mempcpy manipulating FILE* state
https://bugs.kde.org/show_bug.cgi?id=352130 Godmar Back changed: What|Removed |Added CC||god...@gmail.com --- Comment #2 from Godmar Back --- Created attachment 147180 --> https://bugs.kde.org/attachment.cgi?id=147180=edit test that calls printfs in a thread and in main -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 450947] New: Load averages in System Monitor are not rounded or truncated
https://bugs.kde.org/show_bug.cgi?id=450947 Bug ID: 450947 Summary: Load averages in System Monitor are not rounded or truncated Product: plasma-systemmonitor Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: a...@alexdelorenzo.dev CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 147179 --> https://bugs.kde.org/attachment.cgi?id=147179=edit Screenshot of System Monitor's load averages SUMMARY Load averages in System Monitor are not rounded or truncated STEPS TO REPRODUCE 1. Open System Monitor 2. Navigate to a page with a CPU Load average text-only sensor, or add one to a page OBSERVED RESULT CPU Load averages will display as a float that's formatted like '1.923423423234' EXPECTED RESULT System Monitor should round or truncate the Load average float into something user-friendly, like '1.92' SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11 Graphics Platform: Wayland ADDITIONAL INFORMATION I've attached an image that shows the issue. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 450946] New: Window Close Button doesn't take up the entire corner
https://bugs.kde.org/show_bug.cgi?id=450946 Bug ID: 450946 Summary: Window Close Button doesn't take up the entire corner Product: Breeze Version: 5.24.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jchevar...@gmail.com 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. Open any window like Dolphin or Firefox 2. Full Screen it. 3. Move cursor to top right corner OBSERVED RESULT The 'Close Window' button isn't highlighted, its basically just title bar EXPECTED RESULT The 'Close Window' button should be highlight lighted and the window close if you click it SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-arch1-1 (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 ADDITIONAL INFORMATION So, noticed that if I have a window that the close button in the top right no longer activates essentially with the entire area of the window title bar, now it is just the little circle around the X, even in full screen mode. I vaguely remember a previous bug about this where it was determined that essentially the entire right corner should be able to active 'close', at least in full screen windows? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 148045] Unicode in Chinese characters are displayed as squares instead of the corresponding Chinese characters
https://bugs.kde.org/show_bug.cgi?id=148045 linli changed: What|Removed |Added CC||nvdilinli...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 siauder...@hotmail.com changed: What|Removed |Added Status|RESOLVED|VERIFIED CC||siauder...@hotmail.com --- Comment #40 from siauder...@hotmail.com --- Hi, when is the desktop cube coming back? I see that cover switch is back already (albeit uglier, laggier and with NO REFLECTIONS?!). Surely it must be time for the cube now? By the way, these are not "rarely used" features. The vast majority of Linux aficionados use these. It gives us confidence in the superiority of Linux over the dull and boring Windows and MacOS which have no such special effects. I would say the indispensable special effects are (not in order of priority and not exhaustive): Cover switch Desktop cube Wobbly Windows Magic lamp -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kunitconversion] [Bug 450908] Adding New Units to Krunner - Tablespoon and Teaspoon
https://bugs.kde.org/show_bug.cgi?id=450908 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/frameworks/kunitconversion/-/merge_requests/19 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450940] [Wayland] Full desktop freezes with GTK+ apps
https://bugs.kde.org/show_bug.cgi?id=450940 --- Comment #3 from Iván Ávalos --- ADDITIONAL INFORMATION The duration of each freeze ranges from 50 seconds to 1:30 minutes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 450945] New: Oxygen desktoptheme: Notifications are dark grey on black
https://bugs.kde.org/show_bug.cgi?id=450945 Bug ID: 450945 Summary: Oxygen desktoptheme: Notifications are dark grey on black Product: frameworks-plasma Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: plasma-b...@kde.org Reporter: luke-jr+kdeb...@utopios.org CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: --- Not sure which update changed it, but notifications are unreadable with the Oxygen desktoptheme, using a very dark grey foreground and black background. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450944] Dolphin git plugin doesn't show the files status badges until you open a new tab
https://bugs.kde.org/show_bug.cgi?id=450944 Hosameldin changed: What|Removed |Added CC||hosam.awada...@outlook.com Summary|git plugin doesn't show the |Dolphin git plugin doesn't |files status badges until |show the files status |you open a new tab |badges until you open a new ||tab -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450944] New: git plugin doesn't show the files status badges until you open a new tab
https://bugs.kde.org/show_bug.cgi?id=450944 Bug ID: 450944 Summary: git plugin doesn't show the files status badges until you open a new tab Product: dolphin Version: 21.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: plugins: git Assignee: sebast...@sebastian-doerner.de Reporter: hosam.awada...@outlook.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 147178 --> https://bugs.kde.org/attachment.cgi?id=147178=edit a picture shows two split screens, one with the files badges and other is without them. 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. Enable the git plugin go to Settings > Configure Dolphin... > Services. 2. Open Dolphin and navigate to a git directory. OBSERVED RESULT The badges don't appear (99% of the time), and the right-click menu doesn't show the plugin-related options. Open a new tab (or split-screen), and see the badge appear again in the newly opened window and also the related options. EXPECTED RESULT When opening a new instance of Dolphin and going to a git directory, the badges should appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.24.2 (available in About System) KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450065] Custom default look and feel isn't fully applying on Plasma 5.24, in particular the panel theme
https://bugs.kde.org/show_bug.cgi?id=450065 --- Comment #3 from Neal Gompa --- So, I don't fully understand why, but I needed to refresh the downstream Fedora patch for setting the default theme to set in startkde/startplasma.cpp: https://src.fedoraproject.org/rpms/plasma-workspace/c/1857efd5370f81b74025578a9fbc0250bde7abf8?branch=1857efd5370f81b74025578a9fbc0250bde7abf8 It fixes the problem for me, but I feel like the setting I made in kde-settings should have worked, though it didn't: https://pagure.io/fedora-kde/kde-settings/c/3cd46daaf3a2fcfb8266364eed37ab7744760eb7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450871] KDE Plasma Multi-Monitor BUG - No Video Output on one Monitor (No Output Signal) & Display Issue on other monitor after update to 5.24.2
https://bugs.kde.org/show_bug.cgi?id=450871 pipipe.pe...@gmail.com changed: What|Removed |Added CC||pipipe.pe...@gmail.com --- Comment #3 from pipipe.pe...@gmail.com --- can replicate the issue in my setup with Arch, with 2 GPUs I have 1 display connected to each GPU. since 5.24.2 only the second GPU has signal, display settings can't be changed if the issue is present and if the second display is disconnected the system crashes. a workaround is to start the session with only the main display connected and then connecting the second display and it'll work as expected, downgrading to kwin 5.24.1 is also a workaround GPUs: AMD RX 470 (HDMI Display) AMD HD 6950 (DVI Display) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450679] Kwin Wayland session hangs when monitor is turned off / goes to sleep.
https://bugs.kde.org/show_bug.cgi?id=450679 Shmerl changed: What|Removed |Added Version|5.24.1 |5.24.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450943] Screensharing of fullscreen programs doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=450943 Jan Blackquill changed: What|Removed |Added CC||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450943] New: Screensharing of fullscreen programs doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=450943 Bug ID: 450943 Summary: Screensharing of fullscreen programs doesn't work under Wayland Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Keywords: regression Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: uhh...@gmail.com Target Milestone: --- If you attempt to use screensharing functionality on fullscreen programs under Wayland; the fullscreen programs behave as if they didn't exist at all in the capture output. Seems to be caused by 30464e5c8b3643d19176aa2c521c9dd3eb6609dd. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450679] Kwin Wayland session hangs when monitor is turned off / goes to sleep.
https://bugs.kde.org/show_bug.cgi?id=450679 maringrl...@gmail.com changed: What|Removed |Added CC||maringrl...@gmail.com --- Comment #2 from maringrl...@gmail.com --- Can comment that this still persists in 5.24.2 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 450841] KPatience High-Res scaling problem Xorg X11 when winning a game
https://bugs.kde.org/show_bug.cgi?id=450841 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/games/kpat/-/merge_requests/25 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434877] High CPU usage
https://bugs.kde.org/show_bug.cgi?id=434877 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #16 from Lemuel Simon --- To add to this bug report, I believe System Monitor's whole UI is affected by this, regardless of a graph being present or not. Updating window content via moving graphs or just scrolling the processes list is very expensive to the CPU. Going on the default 'Processes' page and scrolling the processes page (with no graphs enabled) will easily spike the CPU usage to 40%+. Doing the same thing in KSysGuard will only raise ~7% at most. Is it that GPU rendering isn't happening at all? Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-150300.59.49-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #59 from Petr --- (In reply to Brian Kaye from comment #56) > My laptop (Lenovo P50) crashed and I fired up an old IBM P42 Thinkpad. It is > running Fedora 29 and the bug appears there as well. Don't remember it doing > that but it is probbably six or seven years since I fired that laptop up. > I ran the command "ksmserver --version" and it returned the exact same > version number (0.4) that is running on my Fedora 35 system. well, this behavior (not remembering desktops and other selected settings properly) only started last summer. and if kmserver is the same version (0.4) since years, it might probably be another component misbehaving. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 450841] KPatience High-Res scaling problem Xorg X11 when winning a game
https://bugs.kde.org/show_bug.cgi?id=450841 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433769] Disk state not available in System Monitor
https://bugs.kde.org/show_bug.cgi?id=433769 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- (In reply to lnxusr from comment #0) > ADDITIONAL INFORMATION > Ksysguard displays this info in the CPU column which would be acceptable but > I think a separate column for disk state would be a better option. Forgive my ignorance, but what kind information does 'disk state' convey exactly? I'm aware of I/O rates and disk temperatures. I can't remember seeing it in KSysGuard. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450942] New: Save button improvement
https://bugs.kde.org/show_bug.cgi?id=450942 Bug ID: 450942 Summary: Save button improvement Product: kate Version: 21.12.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- It would be cool if the save button in toolbar becomes disabled after saving and return enabled upon any further edit, the current indicator at left bottom is hard to see and make my neck hurts by looking at bottom then clicking on save button at top. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442095] process names indented too far in Tree View
https://bugs.kde.org/show_bug.cgi?id=442095 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #12 from Lemuel Simon --- Hmm...I think this happens because an 'icon' is expected within that gap. Say, if look a program with an icon (Firefox, Kate,ect), the icon will fill the gap. However, most processes don't have one (systemd,KWin,plasmashell), and there isn't a 'fallback' or 'placeholder' icon for such processes in System Monitor. I suggest that the generic 'terminal/console' icon be used for that (if icons are enabled). I think it would appropriate since its 'command line' or background processes anyway. Thoughts? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450940] [Wayland] Full desktop freezes with GTK+ apps
https://bugs.kde.org/show_bug.cgi?id=450940 --- Comment #2 from Iván Ávalos --- ADDITIONAL INFORMATION No Qt apps seem to cause the freezes, that's why this bug's title contains “GTK+”. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450941] New: Upgrade process re-enable GTK3/4 animations
https://bugs.kde.org/show_bug.cgi?id=450941 Bug ID: 450941 Summary: Upgrade process re-enable GTK3/4 animations Product: plasmashell Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 After upgrading from 5.23.4 to 5.24.2, both GTK 3 and 4 animations are re-enabled even if KDE Plasma animations property is set to "Instant", only after changing it to another value then resetting it to Instant fixes the problem and GTK animations become disabled. Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.4.181-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450940] [Wayland] Full desktop freezes with GTK+ apps
https://bugs.kde.org/show_bug.cgi?id=450940 --- Comment #1 from Iván Ávalos --- ADDITIONAL INFORMATION No suspicious dmesg or journalctl logs are present whatsoever. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429563] Icon / Menu for System Tray
https://bugs.kde.org/show_bug.cgi?id=429563 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m --- Comment #1 from Lemuel Simon --- (In reply to Richard Llom from comment #0) > Since there is now a unified background service (KSystemStats) for sensor > data, it would be nice to also have a system tray menu, which would use that > service. The menu would be used to give some stats on a quick glance. > > For reference, this is what gnome has: > https://github.com/xtranophilist/gnome-shell-extension-sensors > Technically, this existed in Plasma 5.21 and onwards with the 'System Monitor Sensor' widget that you can place in the panel or desktop area. You can add any amount of 'sensors' offered by KSystemStats as a pie chart, bar graph or plain text. You can also launch System Monitor there as well. Is there something in particular that isn't provided by the widget? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450940] New: [Wayland] Full desktop freezes with GTK+ apps
https://bugs.kde.org/show_bug.cgi?id=450940 Bug ID: 450940 Summary: [Wayland] Full desktop freezes with GTK+ apps Product: plasmashell Version: 5.24.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ava...@disroot.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Recently, I have experienced desktop freezes in the Wayland session, where after doing certain specific things in GTK+ apps, the whole desktop freezes for some minutes, and then unfreezes, and then freezes again. During the freezes, I'm unable to use the keyboard (no switch to different TTY, no volume up/down, no Ctrl+Alt+Del, etc.), but even with the display frozen, I'm still able to control the system remotely (e.g. KDE Connect) and music still plays. I really did an effort to figure out what was causing the issue, and came to the conclusion that it is definitely Plasma. At first, I thought it had something to do with webkit2gtk, because Tangram was causing the freezes. Then I discovered Gajim and Claws Mail also caused them. Then, I thought it was related to Wayland, so I tried doing the same things in X11, and no freezes! It had to be Wayland! Finally, I tried using Enlightenment and Weston under Wayland, and no freezes! It must be KDE! STEPS TO REPRODUCE 1. Open Tangram. 2. Wait for Pinafore to load the posts. 3. Before it loads the posts, freeze! 4. After some minutes, unfreeze! 1. Open Tangram. 2. Wait for WhatsApp to load. 3. Switch to a different chat, freeze! 4. After some minutes, unfreeze! 5. Go to 3. 1. Open GNOME Web. 2. Do random stuff. 3. Sometimes, out of nowhere, freeze! 4. After some minutes, unfreeze! 5. Go to 2. 1. Open Gajim. 2. Open a chat window. 3. Write in the message box. 4. After some characters, freeze! 5. After some minutes, unfreeze! 6. Go to 4. (It has stopped happening.) 1. Open Claws Mail. 2. Do random stuff in the second account from top to bottom. 3. Click a mailbox (e.g. Inbox) in the first account from top to bottom. 4. Freeze! OBSERVED RESULT The entire desktop freezes. EXPECTED RESULT No freezes! SOFTWARE/OS VERSIONS Operating System: Parabola KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.15.12-gnu-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION The freezes are not related to memory or CPU. The same will happen either right after booting my system or with tons of apps (including Android Studio) open. No significant memory or CPU overhead seem to be present. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 450939] New: Unable to parse file when importing .OFX files
https://bugs.kde.org/show_bug.cgi?id=450939 Bug ID: 450939 Summary: Unable to parse file when importing .OFX files Product: kmymoney Version: 5.1.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: tomwie...@yahoo.ca 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. Import .OFX file 2. 3. OBSERVED RESULT Unable to import c:/xxx/xxx/xxx.ofx using the OFX importer plugin. The plugin returned the following error: Unable to parse file EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I am using Windows 10. This works correctly in version 5.0.6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 450938] New: Changing avatar fails
https://bugs.kde.org/show_bug.cgi?id=450938 Bug ID: 450938 Summary: Changing avatar fails Product: systemsettings Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com CC: uhh...@gmail.com Target Milestone: --- Created attachment 147177 --> https://bugs.kde.org/attachment.cgi?id=147177=edit Changing avatar fails If I select another avatar then enter password I got error message, and running journalctl -b0 -f at same time shows some errors, one of them points to second user path while I'm changing current user. Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.4.181-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450786] Privacy problem: deleted annotations are not deleted
https://bugs.kde.org/show_bug.cgi?id=450786 Albert Astals Cid changed: What|Removed |Added Severity|grave |normal Ever confirmed|0 |1 CC||aa...@kde.org Status|REPORTED|CONFIRMED --- Comment #1 from Albert Astals Cid --- Yeah, i guess we should warn users about it. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 449661] Exporting to docbook/XHMTL error
https://bugs.kde.org/show_bug.cgi?id=449661 Oliver Kellogg changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||2.33.80 (KDE releases ||22.03.80) Latest Commit||de636719fdfc7245f5498ae9717 ||cf4462dfaa01d --- Comment #4 from Oliver Kellogg --- Remaining problems were addressed by fixing bug 409411. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450896] Okular doesn't take middle clicks for internal links
https://bugs.kde.org/show_bug.cgi?id=450896 Albert Astals Cid changed: What|Removed |Added Severity|normal |wishlist Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Albert Astals Cid --- I don't agree, but i guess a wish is a wish. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 409411] Export to XHTML generates empy html file
https://bugs.kde.org/show_bug.cgi?id=409411 Oliver Kellogg changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit|https://commits.kde.org/umb |https://invent.kde.org/sdk/ |rello/c6002b5c68592932a64bb |umbrello/commit/de636719fdf |194449d2e884725631f |c7245f5498ae9717cf4462dfaa0 ||1d Resolution|--- |FIXED Version Fixed In|2.28.3 (KDE Applications|2.33.80 (KDE releases |19.04.3)|22.03.80) --- Comment #3 from Oliver Kellogg --- Git commit de636719fdfc7245f5498ae9717cf4462dfaa01d by Oliver Kellogg. Committed on 27/02/2022 at 21:42. Pushed by okellogg into branch 'master'. Address reopening https://bugs.kde.org/show_bug.cgi?id=409411#c2 , > [...] > libxslt apparently performs a consistency check on the xmlns URI > between the stylesheet and the XML input file. > On the version mismatch, xsltApplyStylesheet() does not return an > error but silently refuses to carry out the transformations. umbrello/docgenerators/xmi2docbook.xsl - In the attributes change xmlns:UML="http://schema.omg.org/spec/UML/1.3; to xmlns:UML="http://schema.omg.org/spec/UML/1.4; for synchronizing with Umbrello versions since 2.21 (Apps 17.03.80). - Other changes: - Remove whitespace at line ends. - Join Xpath expressions spread over two lines to single line. - In , - in fix Xpath expression of "select"; - in , - at entity fix attribute name in "select"; - in , - fix typo at "Abstract"; - at "Visibility" update ancient expressions. - In , - at "Visibility" update ancient expressions; - at "Default" remove non-ASCII/non-UTF8 unidentified characters. - In update ancient expressions intended for decoding "visibility". umbrello/docgenerators/docbookgeneratorjob.cpp - Enclose additions of commit c6002b5 in #ifdef USE_SDOCBOOK_LOCAL_COPY. Reason: The docbook generation appears to function properly without them. - In function run() : - Remove local variables for "write the XMI model in an in-memory char* string", they appear to be unused. - Test return value from xsltParseStylesheetFile(), xmlParseFile(), xsltApplyStylesheet() and log an error if null. - On freeing up pointers deallocate `cur' last. Reason: Heap segments shall be freed in the opposite order of their allocation. FIXED-IN:2.33.80 (KDE releases 22.03.80) M +30 -9umbrello/docgenerators/docbookgeneratorjob.cpp M +230 -236 umbrello/docgenerators/xmi2docbook.xsl https://invent.kde.org/sdk/umbrello/commit/de636719fdfc7245f5498ae9717cf4462dfaa01d -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 450937] New: It is hard to switch away from an audio playback device when it becomes inactive
https://bugs.kde.org/show_bug.cgi?id=450937 Bug ID: 450937 Summary: It is hard to switch away from an audio playback device when it becomes inactive Product: plasma-pa Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: k...@sdht.in CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY The "simple" version of the audio applet, where the options to change the playback device are hidden, makes it hard to set the right audio output when an external device is connected and disconnected, as described below. STEPS TO REPRODUCE 1. Connect an external hdmi device with audio output. The audio applet shows two playback devices: "Laptop Speaker" and "HDMI Output". 2. Select HDMI Output as default or change playback output of a stream to HDMI in the "Applications" tab. Audio plays through the HDMI. 3. Disconnect HDMI. OBSERVED RESULT No audio can be heard, since output does not automatically switch back from HDMI to Speaker. Moreover, the audio applet becomes "simple", as there is only one output, so the applet decides to hide the options to set the default device or switch the playback device in the application tab. To fix the issue, I now have to open "Configure audio devices" to set the correct playback stream for an application. Also, I have to click on "Show inactive devices" before I can set the default back to "Speaker" again. EXPECTED RESULT I don't know if switching the default or playback stream of an application to "Speaker" automatically is the right solution. But perhaps the audio applet can continue to show the "advanced" options of selecting the default device or the corresponding options in the Applications tab as long as an inactive device is selected and only hide when none of the outputs is to an inactive device? SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-arch1-1 (64-bit) Graphics Platform: X11 Audio Server Name: PulseAudio (on PipeWire 0.3.47) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450743] Rendering "stalled" when disk full
https://bugs.kde.org/show_bug.cgi?id=450743 Julius Künzel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #2 from Julius Künzel --- *** This bug has been marked as a duplicate of bug 400699 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400699] UI should warn when rendering to filesystem low on disk space
https://bugs.kde.org/show_bug.cgi?id=400699 Julius Künzel changed: What|Removed |Added CC||b-m...@gmx.ch --- Comment #3 from Julius Künzel --- *** Bug 450743 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450884] Slight stuttering in game with VRR at higher FPS than set "regular" refresh rate of the display
https://bugs.kde.org/show_bug.cgi?id=450884 --- Comment #5 from torokat...@gmail.com --- Oh dear, you are absolutely right. I did not know that Adaptive Sync had this limitation. I just booted Windows to check if it has the same thing, and when setting the refresh rate to 120 Hz, even the reported VRR range of the display shrinks to only 48 - 120 Hz. It still seems so silly to me that this is how it works. Thank you for the information and sorry for the spam! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432570] kwin_x11 crash randomly in KWin::SceneOpenGL::createScene()
https://bugs.kde.org/show_bug.cgi?id=432570 --- Comment #24 from Mathias Panzenböck --- Created attachment 147176 --> https://bugs.kde.org/attachment.cgi?id=147176=edit New crash information added by DrKonqi kwin_x11 (5.20.5) using Qt 5.15.2 - What I was doing when the application crashed: I watched a YouTube video in Firefox. - Unusual behavior I noticed: Image froze, no keyboard inputs registered anymore, but audio continued. I switched to a text terminal and back (Ctrl+Alt+F2 then Ctrl+Alt+F1) at which point kwin crashed, restarted and the UI was useable again, though compositing was deactivated. -- Backtrace (Reduced): #5 0x7f559ed1b564 in KWin::SceneOpenGL::createScene(QObject*) () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #6 0x7f559ed2a41d in KWin::OpenGLFactory::create(QObject*) const () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #8 0x7f55bd11903e in KWin::X11Compositor::start() () at /lib64/libkwin.so.5 #9 0x7f55bd116e57 in KWin::Compositor::reinitialize() () at /lib64/libkwin.so.5 #10 0x7f55bbde3386 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432570] kwin_x11 crash randomly in KWin::SceneOpenGL::createScene()
https://bugs.kde.org/show_bug.cgi?id=432570 Mathias Panzenböck changed: What|Removed |Added CC||grosser.meister.morti@gmx.n ||et -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 450936] New: Discover replicates the visual content of the last opened window while loading
https://bugs.kde.org/show_bug.cgi?id=450936 Bug ID: 450936 Summary: Discover replicates the visual content of the last opened window while loading Product: Discover Version: 5.24.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: fake.n...@posteo.net CC: aleix...@kde.org Target Milestone: --- SUMMARY When opened, Discover displays the visual content of a previously opened window, refit into the bounds of the Discover window itself. This lasts for a few seconds before the content of Discover itself loads and replaces the phantom visual. It also happens if nothing but the desktop has been displayed; in said case, the Discover window shows the desktop, but reduced into a size that fits in the discover window. STEPS TO REPRODUCE 1. Turn on computer 2. Open an app, then close it 3. Open discover OBSERVED RESULT For a brief while, Discover resembles the previous app. EXPECTED RESULT The discover app should load directly to its own content. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.16.11, Zen kernel KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #58 from Attila --- (In reply to Brian Kaye from comment #56) > My laptop (Lenovo P50) crashed and I fired up an old IBM P42 Thinkpad. It is > running Fedora 29 and the bug appears there as well. Don't remember it doing > that but it is probbably six or seven years since I fired that laptop up. > I ran the command "ksmserver --version" and it returned the exact same > version number (0.4) that is running on my Fedora 35 system. I have found an old IBM Thinkpad T60 running Fedora 29. It is a 32Bit installation of Fedora because of the CPU. Unfortunately, I can not confirm this bug on Fedora 29. Session restore works as expected, but I don't know why. I guess you are using a 64Bit Fedora? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450301] On KWin 5.24 X11 Nvidia, when reenabling compositing, windows begin flickering and flipping upside-down
https://bugs.kde.org/show_bug.cgi?id=450301 --- Comment #4 from nyanpasu64 --- I tried to take a trace-cmd sample using https://github.com/mikesart/gpuvis/tree/master/sample and open it in gpuvis, but I only got CPU information. I can share my traces if anyone is interested. Interestingly killing plasmashell (not kwin_x11) stopped the flickering. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak
https://bugs.kde.org/show_bug.cgi?id=428394 Kenneth Perry changed: What|Removed |Added CC||thothone...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 409411] Export to XHTML generates empy html file
https://bugs.kde.org/show_bug.cgi?id=409411 Oliver Kellogg changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 409411] Export to XHTML generates empy html file
https://bugs.kde.org/show_bug.cgi?id=409411
Oliver Kellogg changed:
What|Removed |Added
Ever confirmed|0 |1
CC||okellogg@users.sourceforge.
||net
Status|RESOLVED|REOPENED
Resolution|FIXED |---
--- Comment #2 from Oliver Kellogg ---
(In reply to Ralf Habacker from comment #1)
> [...]
> https://commits.kde.org/umbrello/c6002b5c68592932a64bb194449d2e884725631f
The sections "actors", "usecases", "interfaces", "classes" in the generated
docbook continue to be empty after that change:
Actors
Use Cases
Interfaces
Classes
[...]
umbrello/umldoc.cpp commit 847b6e0d (2017-02-20) set the supported UML version
in XMI file header to 1.4:
@@ -2015,13 +2015,13 @@ void UMLDoc::saveToXMI1(QIODevice& file)
QDateTime now = QDateTime::currentDateTime();
root.setAttribute(QLatin1String("timestamp"), now.toString(Qt::ISODate));
root.setAttribute(QLatin1String("verified"), QLatin1String("false"));
-root.setAttribute(QLatin1String("xmlns:UML"),
QLatin1String("http://schema.omg.org/spec/UML/1.3;));
+root.setAttribute(QLatin1String("xmlns:UML"),
QLatin1String("http://schema.omg.org/spec/UML/1.4;));
doc.appendChild(root);
However, the umbrello/docgenerators/xmi2docbook.xsl continues to use
http://www.w3.org/1999/XSL/Transform;
version="1.0"
xmlns:UML="http://schema.omg.org/spec/UML/1.3;
exclude-result-prefixes="UML">
libxslt apparently performs a consistency check on the xmlns URI between the
stylesheet and the XML input file.
On the version mismatch, xsltApplyStylesheet() does not return an error but
silently refuses to carry out the transformations.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 450935] New: App crashed
https://bugs.kde.org/show_bug.cgi?id=450935
Bug ID: 450935
Summary: App crashed
Product: systemsettings
Version: 5.24.2
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: alphar...@protonmail.com
Target Milestone: ---
Application: systemsettings (5.24.2)
Qt Version: 5.15.2
Frameworks Version: 5.91.0
Operating System: Linux 5.16.10-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.24.2 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Discover was fetching the updates and I switched from icon view to sidebar
view. I clicked the software update notification's configure button that popped
up. It opened the Configure Notifications System Settings Module which I
canceled. After the cancellation of the window the Discover app has crashed.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 QWeakPointer::~QWeakPointer (this=, this=) at /usr/include/c++/11/bits/atomic_base.h:385
#7 QPointer::~QPointer (this=,
this=) at /usr/include/qt5/QtCore/qpointer.h:53
#8 Breeze::GenericData::~GenericData (this=, this=) at
/usr/src/debug/breeze-5.24.2-1.1.x86_64/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezegenericdata.h:20
#9 Breeze::WidgetStateData::~WidgetStateData (this=,
this=) at
/usr/src/debug/breeze-5.24.2-1.1.x86_64/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezewidgetstatedata.h:32
#10 Breeze::EnableData::~EnableData (this=, this=) at
/usr/src/debug/breeze-5.24.2-1.1.x86_64/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezeenabledata.h:16
#11 Breeze::EnableData::~EnableData (this=, this=) at
/usr/src/debug/breeze-5.24.2-1.1.x86_64/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezeenabledata.h:16
#12 0x7f901825524f in QObject::event (this=0x55895f2a03a0,
e=0x55895f1b0b40) at kernel/qobject.cpp:1301
#13 0x7f9018edca7f in QApplicationPrivate::notify_helper (this=, receiver=0x55895f2a03a0, e=0x55895f1b0b40) at
kernel/qapplication.cpp:3632
#14 0x7f9018228e3a in QCoreApplication::notifyInternal2
(receiver=0x55895f2a03a0, event=0x55895f1b0b40) at
kernel/qcoreapplication.cpp:1064
#15 0x7f901822be77 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55895edce480) at
kernel/qcoreapplication.cpp:1821
#16 0x7f9018280d03 in postEventSourceDispatch (s=s@entry=0x55895ef57440) at
kernel/qeventdispatcher_glib.cpp:277
#17 0x7f9015d3ee22 in g_main_dispatch (context=0x7f900c005010) at
../glib/gmain.c:3381
#18 g_main_context_dispatch (context=0x7f900c005010) at ../glib/gmain.c:4099
#19 0x7f9015d3f1b8 in g_main_context_iterate
(context=context@entry=0x7f900c005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#20 0x7f9015d3f26f in g_main_context_iteration (context=0x7f900c005010,
may_block=1) at ../glib/gmain.c:4240
#21 0x7f9018280384 in QEventDispatcherGlib::processEvents
(this=0x55895ef5e4f0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7f901822783b in QEventLoop::exec (this=this@entry=0x7fffbf89a4c0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x7f901822fb10 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x7f901877e25c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#25 0x7f9018edc9f5 in QApplication::exec () at kernel/qapplication.cpp:2824
#26 0x55895cf23e97 in main (argc=, argv=) at
/usr/src/debug/systemsettings5-5.24.2-1.1.x86_64/app/main.cpp:183
[Inferior 1 (process 2701) detached]
The reporter indicates this bug may be a duplicate of or related to bug 450565.
Possible duplicates by query: bug 450754, bug 450565.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 432286] transparency+blur glitching with obscured animated windows underneath
https://bugs.kde.org/show_bug.cgi?id=432286 p1n...@ya.ru changed: What|Removed |Added Version|5.20.90 |5.24.2 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Brian Kaye changed: What|Removed |Added Version|5.23.3 |5.24.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432286] transparency+blur glitching with obscured animated windows underneath
https://bugs.kde.org/show_bug.cgi?id=432286 p1n...@ya.ru changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from p1n...@ya.ru --- Operating System: Arch Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-9100F CPU @ 3.60GHz Memory: 31.3 ГиБ of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #57 from Brian Kaye --- Downloaded Fedora KDE Live 31 the newest version available for old versions. Created and booted a UDB stick. Created 4 virtual desktops, put an application on each desktop, set the system to restore previous. Logout/login 5 times and all desktops had their previous applications on their correct virtual desktop EVERY time. I did not delete the files in .config/session or the file .ksmserverrc. Running the command "ksmserver --version" returned the value 0.4. However here is an anomaly. When I ran "ls - /usr/ksmserver" It showed a size of 16568 bytes as opposed to the size of 163288 bytes on my fedora 35 system. This difference made me go back and check. Surprising unless the ls command is different the two releases (31 vs 35). I guess I need to find an old version of Fedora 33. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405624] no bouncy cursor when opening apps
https://bugs.kde.org/show_bug.cgi?id=405624 Driglu4it changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Driglu4it --- (In reply to Driglu4it from comment #9) > (In reply to Nate Graham from comment #7) > > This has been implemented by Aleix Pol Gonzalez and is working for Plasma > > 5.23! > > > But not working on Manjaro. Same as Benjamin Smith. > > Operating System: Manjaro Linux > KDE Plasma Version: 5.24.2 > KDE Frameworks Version: 5.91.0 > Qt Version: 5.15.2 > Kernel Version: 5.16.11-2-MANJARO (64-bit) > Graphics Platform: Wayland Now I found out that for sure (at least for me) - the animation depends ONLY on the speed of the application launch (in krusader, I brought a deliberately wrong network address to one of the panels to slow down the rendering of the interface - now there is always animation). How it works programmatically - I do not know. Kpat also does not show animation if it is closed and immediately opened, but if it was unloaded from memory + the processor is loaded at that time, there is animation ... -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 450934] New: Under Wayland the Kolourpaint 21.12.2 doesn't display the correct cursor for each element
https://bugs.kde.org/show_bug.cgi?id=450934 Bug ID: 450934 Summary: Under Wayland the Kolourpaint 21.12.2 doesn't display the correct cursor for each element Product: kolourpaint Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: quanticcpu2...@gmail.com Target Milestone: --- Created attachment 147175 --> https://bugs.kde.org/attachment.cgi?id=147175=edit Kolourpaint Screenshot SUMMARY - Under Wayland the Kolourpaint 21.12.2 and others version doesn't display the correct cursor for each element in the toolbar mainly for brush. Some tools doesn't match with the cursor position. STEPS TO REPRODUCE 1. Open the Kolourpaint in the KDE Plasma Wayland 5.23.5 or 5.24.2; 2. Edit an image; 3. Use all tools in the toolbar you can notice different behavior in the cursor when compare to under X.org. OBSERVED RESULT - Noticed different behavior in the cursor when compare to under X.org. EXPECTED RESULT - Cursor with same behavior in the Wayland like running under X.org. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 35 KDE Plasma Version: Plasma 5.23.5 and 5.24.2 KDE Frameworks Version: 5.91 Qt Version: 5.15.2 ADDITIONAL INFORMATION * -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 447881] Replied HTML e-mail
https://bugs.kde.org/show_bug.cgi?id=447881 Daniel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Daniel --- *** This bug has been marked as a duplicate of bug 368394 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 Daniel changed: What|Removed |Added CC||lui...@gmail.com --- Comment #23 from Daniel --- *** Bug 447881 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450250] Game window looks ugly, mouse behaves incorrect
https://bugs.kde.org/show_bug.cgi?id=450250 --- Comment #5 from Lach Sławomir --- I see that Age of Wonders: Planetfall working. This is game working through Proton. I will test more Windows games in near future. If all Windows games will working, I will test more native games. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 450915] [wayland / nvidia proprietary] - dock does not appear
https://bugs.kde.org/show_bug.cgi?id=450915 --- Comment #10 from galder --- I compiled current master 5.24.80. It looks like latte works fine. Hopefully this issue should be fixed in the next patch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405624] no bouncy cursor when opening apps
https://bugs.kde.org/show_bug.cgi?id=405624 Driglu4it changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||d...@i-glu4it.ru --- Comment #9 from Driglu4it --- (In reply to Nate Graham from comment #7) > This has been implemented by Aleix Pol Gonzalez and is working for Plasma > 5.23! But not working on Manjaro. Same as Benjamin Smith. Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-2-MANJARO (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450896] Okular doesn't take middle clicks for internal links
https://bugs.kde.org/show_bug.cgi?id=450896 --- Comment #4 from David --- (In reply to Albert Astals Cid from comment #3) > Okular is not a web browser nor a terminal not a file manager, any document > viewer with that behaviour? I am not familiar with any other document viewer with support for tabs, other than Konqueror if you want to consider it as such, which does open links in new tabs when middle-clicked. PDF viewers in web browsers (at least chromium-based ones) also open internal links in a new tab when middle clicked, if you count them as document viewers. Sioyek (PDF viewer without tabs) opens internal links in a web browser when middle-clicked. Evince doesn't support tabs, but offers the option to open internal links in a new window when right-clicked, which is probably the closest thing. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 449902] Brave browser's portal dialog using wrong application style (Fusion instead of Breeze)
https://bugs.kde.org/show_bug.cgi?id=449902 *bleep bleep* changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from *bleep bleep* --- UPDATE: Everything is working as intended now!! Thanks KDE team <3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450914] Wayland, games on Nvidia are force vsynced
https://bugs.kde.org/show_bug.cgi?id=450914 --- Comment #2 from Alexander Streng --- Ah, I just thought that it might be a bug with kwin since I've heard that Gnome doesn't have this issue in Wayland session 樂 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450914] Wayland, games on Nvidia are force vsynced
https://bugs.kde.org/show_bug.cgi?id=450914 Zamundaaa changed: What|Removed |Added Resolution|--- |UPSTREAM CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Zamundaaa --- KWin is not involved with application VSync, beyond providing infrastructure so that they can match timing. This is most likely a bug in the NVidia driver, or (rather unlikely though) in Xwayland -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450692] Vectorscope manual page has invalid links
https://bugs.kde.org/show_bug.cgi?id=450692 emohr changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||fritzib...@gmx.net --- Comment #1 from emohr --- Thank you for reporting. I have updated the documentation with all "Granjow's blog" sites and links. Please check if I have forgotten anything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Christoph Sarnowski changed: What|Removed |Added CC||christ...@sarnowski.de --- Comment #92 from Christoph Sarnowski --- Hi everyone, I also want to provide some more (maybe useful) information. I am using plasma-desktop 5.24.2-1 on arch linux and also experience this bug (randomly either showing the battery monitor, or not). Hardware is a Thinkpad T460s. But in addition to the battery icon missing, also my hotkeys for adjusting the display brightness do not work. I killed & restarted org_kde_powerdevil, and that made my hotkeys work again, but still no battery icon (just a display icon). Hovering that icon, it said something like "No batteries". Restarting plasmashell, as mentioned above, fixed everything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448511] eclipse not receiving pasted text from kate under wayland
https://bugs.kde.org/show_bug.cgi?id=448511 --- Comment #5 from Dietmar Czekay --- update to Plasma 5.24 did not change the behavior. copy and paste did not work in both directions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450933] Kwin crash in KWin::AnimationEffect::postPaintScreen()
https://bugs.kde.org/show_bug.cgi?id=450933 Matej Mrenica changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #1 from Matej Mrenica --- Copy from above link: #0 0x7f1a819d9ca8 in vtable for KWaylandServer::SurfaceInterfacePrivate () at /usr/lib/libKWaylandServer.so.5 #1 0x7f1a81849233 in KWin::AnimationEffect::postPaintScreen() (this=0x55a4b4469fc0) at /usr/src/debug/kwin-5.24.2/src/libkwineffects/kwinanimationeffect.cpp:668 #2 0x7f1a81c7aae5 in KWin::EffectsHandlerImpl::postPaintScreen() (this=0x55a4b386c860) at /usr/src/debug/kwin-5.24.2/src/effects.cpp:414 #3 0x7f1a81ce99ca in KWin::Scene::paintScreen(QRegion const&, QRegion const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) (this=0x55a4b35bb090, damage=, repaint=..., updateRegion=0x7fffa4b15b30, validRegion=0x7fffa4b15b28, renderLoop=, projection=...) at /usr/src/debug/kwin-5.24.2/src/scene.cpp:288 #4 0x7f1a81db0037 in KWin::SceneOpenGL::paint(KWin::AbstractOutput*, QRegion const&, QList const&, KWin::RenderLoop*) (this=0x55a4b35bb090, output=0x55a4b48b1440, damage=..., toplevels=, renderLoop=0x55a4b4603270) at /usr/src/debug/kwin-5.24.2/src/scenes/opengl/scene_opengl.cpp:259 #5 0x7f1a81c4c7f4 in KWin::Compositor::composite(KWin::RenderLoop*) (this=0x55a4b35f9070, renderLoop=0x55a4b4603270) at /usr/src/debug/kwin-5.24.2/src/composite.cpp:633 #6 0x7f1a7fbef9d3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffa4b15d90, r=, this=0x55a4b377a0d0, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate(QObject*, int, void**) (sender=0x55a4b4603270, signal_index=5, argv=0x7fffa4b15d90) at kernel/qobject.cpp:3886 #8 0x7f1a81c0a7a7 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) (this=, _t1=) at /usr/src/debug/build/src/kwin_autogen/EWIEGA46WW/moc_renderloop.cpp:206 #9 0x7f1a81cdbec8 in KWin::RenderLoopPrivate::dispatch() (this=0x55a4b45e9a20) at /usr/src/debug/kwin-5.24.2/src/renderloop.cpp:150 #10 0x7f1a7fbef9d3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffa4b15eb0, r=, this=0x55a4b39c3080, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate(QObject*, int, void**) (sender=0x55a4b45e9a38, signal_index=3, argv=0x7fffa4b15eb0) at kernel/qobject.cpp:3886 #12 0x7f1a7fbf1c0f in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #13 0x7f1a7fbe2d56 in QObject::event(QEvent*) (this=0x55a4b45e9a38, e=0x7fffa4b16050) at kernel/qobject.cpp:1291 #14 0x7f1a8067b1a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55a4b45e9a38, e=0x7fffa4b16050) at kernel/qapplication.cpp:3632 #15 0x7f1a7fbbeb9a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55a4b45e9a38, event=0x7fffa4b16050) at kernel/qcoreapplication.cpp:1064 #16 0x7f1a7fc0a335 in QTimerInfoList::activateTimers() (this=0x55a4b32f0bf8) at kernel/qtimerinfo_unix.cpp:643 #17 0x7f1a7fc0a7d2 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:516 #18 0x55a4b2b376e2 in QUnixEventDispatcherQPA::processEvents(QFlags) () --Type for more, q to quit, c to continue without paging-- #19 0x7f1a7fbb6e6b in QEventLoop::exec(QFlags) (this=0x7fffa4b161f0, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #20 0x7f1a7fbc25c7 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #21 0x7f1a7ff8d332 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1867 #22 0x7f1a8067952a in QApplication::exec() () at kernel/qapplication.cpp:2824 #23 0x55a4b2a462da in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.24.2/src/main_wayland.cpp:727 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450933] New: Kwin crash in KWin::AnimationEffect::postPaintScreen()
https://bugs.kde.org/show_bug.cgi?id=450933 Bug ID: 450933 Summary: Kwin crash in KWin::AnimationEffect::postPaintScreen() Product: kwin Version: 5.24.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matejm98m...@gmail.com Target Milestone: --- SUMMARY I was using Firefox, when my (Plasma) session crashed with the following log: https://pastebin.com/ChnsNkje -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 450928] Dead keys are ignored
https://bugs.kde.org/show_bug.cgi?id=450928 --- Comment #6 from lc...@april.org --- Moi qui croyais rapporter un bogue qui prendrait du temps à être résolu, je suis stupéfait par votre réactivité. Merci encore pour votre travail. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450884] Slight stuttering in game with VRR at higher FPS than set "regular" refresh rate of the display
https://bugs.kde.org/show_bug.cgi?id=450884 Zamundaaa changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #4 from Zamundaaa --- No. Adaptive Sync enables the system to lower the refresh rate below what the monitor is set to, not above it; there isn't even a driver API to target a specific refresh rate right now. If you want to go above 120Hz, you need to set your monitor to run at above 120Hz. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 443566] Make it easier for user to re-use existing security when adding to new investment account
https://bugs.kde.org/show_bug.cgi?id=443566 Jack changed: What|Removed |Added CC||rd_wo...@hotmail.com --- Comment #1 from Jack --- *** Bug 448006 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 448006] Duplicated security symbol will be created twice in different account
https://bugs.kde.org/show_bug.cgi?id=448006 Jack changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jack --- I believe this is actually documented in the Manual. *** This bug has been marked as a duplicate of bug 443566 *** -- You are receiving this mail because: You are watching all bug changes.
