[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 Miroslav Franc changed: What|Removed |Added Attachment #164984|0 |1 is obsolete|| --- Comment #20 from Miroslav Franc --- Created attachment 165137 --> https://bugs.kde.org/attachment.cgi?id=165137=edit implement --disable-seccomp=[no|yes] and seccomp syscall v4 Sorry, for the spam. I added another testcase and improved the remaining ones. The seccomp4 test is especially important, because it shows that valgrind will still work with seccomp filter active unless something important is blacklisted (I'm using alarm syscall there). Tested on x86_64 (kernel 6.6) and s390x (kernel 5.14). > $ perl tests/vg_regtest none/tests/linux/seccomp? > seccomp1:valgrind -q --disable-seccomp=yes ./seccomp1 > seccomp2:valgrind -q ./seccomp2 > seccomp3:valgrind -q ./seccomp3 > seccomp4:valgrind -q ./seccomp4 > > == 4 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == I would be grateful for any kind of review. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 Miroslav Franc changed: What|Removed |Added Attachment #164961|0 |1 is obsolete|| --- Comment #19 from Miroslav Franc --- Created attachment 164984 --> https://bugs.kde.org/attachment.cgi?id=164984=edit --disable-seccomp=yes feature v3 I added two testcases and fixed linking of postwrappers. > $ perl tests/vg_regtest none/tests/linux/seccomp? > seccomp1:valgrind -q --disable-seccomp=yes ./seccomp1 > seccomp2:valgrind -q ./seccomp2 > seccomp3:valgrind -q ./seccomp3 > > == 3 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 > stdoutB failures, 0 post failures == -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 Miroslav Franc changed: What|Removed |Added Attachment #160505|0 |1 is obsolete|| --- Comment #18 from Miroslav Franc --- Created attachment 164961 --> https://bugs.kde.org/attachment.cgi?id=164961=edit --disable-seccomp=yes feature v2 Second version of the patch. It's not final, as I should throw in a few test cases. Disabling seccomp still allows SECCOMP_GET_ACTION_AVAIL and SECCOMP_GET_NOTIF_SIZES operations as those should never stop valgrind from working. I implemented some basic seccomp syscall checks (and left prctl as it was), then I thought I would throw in a few warnings based on how seccomp syscall api should be used, but I must say that the verbosity of the warnings surprised me. The default behviour: > $ valgrind file /bin/ls > ==17247== Memcheck, a memory error detector > ==17247== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. > ==17247== Using Valgrind-3.23.0.GIT and LibVEX; rerun with -h for copyright > info > ==17247== Command: file /bin/ls > ==17247== > ==17247== WARNING: in STRICT SECCOMP mode 2nd argument (flags) should always > be 0 > ==17247== WARNING: valgrind is unlikely to work in STRICT SECCOMP mode > ==17247== WARNING: in FILTER SECCOMP mode 3nd argument (args) should point to > struct sock_fprog > ==17247== WARNING: valgrind might not work in FILTER SECCOMP mode > ==17247== WARNING: in FILTER SECCOMP mode 3nd argument (args) should point to > struct sock_fprog > ==17247== WARNING: valgrind might not work in FILTER SECCOMP mode > ==17247== WARNING: in FILTER SECCOMP mode 3nd argument (args) should point to > struct sock_fprog > ==17247== WARNING: valgrind might not work in FILTER SECCOMP mode > ==17247== WARNING: in FILTER SECCOMP mode 3nd argument (args) should point to > struct sock_fprog > ==17247== WARNING: valgrind might not work in FILTER SECCOMP mode > ==17247== WARNING: in FILTER SECCOMP mode 3nd argument (args) should point to > struct sock_fprog > ==17247== WARNING: valgrind might not work in FILTER SECCOMP mode > ==17247== WARNING: valgrind might not work in FILTER SECCOMP mode > Bad system call It seems to me that those warnings are not imaginary: > $ strace -e seccomp file /bin/ls > seccomp(SECCOMP_SET_MODE_STRICT, 0x1, NULL) = -1 EINVAL (Invalid argument) > seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT > (Bad address) > seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_LOG, NULL) = -1 EFAULT > (Bad address) > seccomp(SECCOMP_GET_ACTION_AVAIL, 0, 0x7ffdbdae238c) = 0 > seccomp(SECCOMP_GET_ACTION_AVAIL, 0, 0x7ffdbdae238c) = 0 > seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_SPEC_ALLOW, NULL) = -1 > EFAULT (Bad address) > seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_NEW_LISTENER, NULL) = -1 > EFAULT (Bad address) > seccomp(SECCOMP_GET_NOTIF_SIZES, 0, 0x7ffdbdae2392) = 0 > seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC_ESRCH, NULL) = -1 > EFAULT (Bad address) > seccomp(SECCOMP_SET_MODE_FILTER, 0, 0x564b7a15e490) = 0 > /bin/ls: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically > linked, interpreter /lib64/ld-linux-x86-64.so.2, > BuildID[sha1]=22f5cfe4926547861d47486e96c0dceb360dec09, for GNU/Linux 3.2.0, > stripped > +++ exited with 0 +++ Disabling it works just fine: > $ valgrind --disable-seccomp=yes file /bin/ls > ==17584== Memcheck, a memory error detector > ==17584== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. > ==17584== Using Valgrind-3.23.0.GIT and LibVEX; rerun with -h for copyright > info > ==17584== Command: file /bin/ls > ==17584== > /bin/ls: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically > linked, interpreter /lib64/ld-linux-x86-64.so.2, > BuildID[sha1]=22f5cfe4926547861d47486e96c0dceb360dec09, for GNU/Linux 3.2.0, > stripped > ==17584== > ==17584== HEAP SUMMARY: > ==17584== in use at exit: 0 bytes in 0 blocks > ==17584== total heap usage: 838 allocs, 838 frees, 8,364,592 bytes allocated > ==17584== > ==17584== All heap blocks were freed -- no leaks are possible > ==17584== > ==17584== For lists of detected and suppressed errors, rerun with: -s > ==17584== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414
--- Comment #17 from Miroslav Franc ---
(In reply to Mark Wielaard from comment #15)
> Also note this patch that implements more of seccomp:
> https://sourceforge.net/p/valgrind/mailman/message/46305485/
To be honest. I was not trying to implement seccomp. I was trying to find a
way to turn it off. :-)
I took a look at the patch from the mailing list. Seeing "[PATCH 1/2]", is
there a second part to it? I see only one. I'm not subscribed to
valgrind-devel and the sourceforge web interface isn't the nicest one I have
seen.
If I read the valgrind-devel patch correctly, it does...
for SECCOMP_SET_MODE_STRICT
1/ make seccomp call visible two --trace-syscalls=yes
2/ say nothing about it's arguments
for SECCOMP_SET_MODE_FILTER
1/ make seccomp call visible two --trace-syscalls=yes
2/ tell valgrind it reads 3 arguments from registers
3/ tell valgrind it reads a memory from the third argument pointer (size of 1?)
I doesn't deal with SECCOMP_GET_ACTION_AVAIL and SECCOMP_GET_NOTIF_SIZES at
all.
In other words it does slightly less then what is currently being done for the
same operations invoked via older prctl syscall, because that tells valgrind it
reads 2 arguments from registers in case of SECCOMP_MODE_STRICT additionally.
To be fair, strict mode is a lost cause anyway for the simplests of programs,
unless they are specifically designed to run in it. It breaks even "int
main(void) {}" if you link against glibc, since glibc started invoking
exit_group(0) for all programs at some point (which is a syscall not allowed in
seccomp strict mode).
When I was writing the patch, I tried to preserve the prctl syscall case while
mark seccomp syscall as unimplemented. What I could do is basically copy paste
the prctl syscall case onto seccomp syscall case and tweak it and see how to
handle additional SECCOMP_GET_ACTION_AVAIL and SECCOMP_GET_NOTIF_SIZES
operations.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 472875] none/tests/s390x/dfp-1 failure
https://bugs.kde.org/show_bug.cgi?id=472875 --- Comment #5 from Miroslav Franc --- (In reply to Andreas Arnez from comment #3) > Your patch should be sufficient for solving this issue. Perhaps for Fedora > this can be picked as-is. I saw the failure on openSUSE Tumbleweed. > Upstream I'd like to fix other issues with the DFP > test cases as well, which will require a much larger patch. It's great to hear. :-) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 472875] none/tests/s390x/dfp-1 failure
https://bugs.kde.org/show_bug.cgi?id=472875 Miroslav Franc changed: What|Removed |Added CC||mfr...@gmx.com --- Comment #2 from Miroslav Franc --- Created attachment 160744 --> https://bugs.kde.org/attachment.cgi?id=160744=edit zero condition code before instruction test I noticed this failure too when I was testing an unrelated patch. My stupid solution, since the test is expecting zeroes unless the tested instruction changes it, would be to simply prepend an instruction that zeroes condition code, such as comparing the register being used with itself, which should always yield zero cc. I just tried it and it seems to work. But, if you already have a fix or better idea, feel free to ignore it. $ perl tests/vg_regtest none/tests/s390x/dfp-1 dfp-1: valgrind ./dfp-1 == 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 --- Comment #14 from Miroslav Franc --- (In reply to Paul Floyd from comment #13) > Is that safe to do? > > Valgrind, a bit like GDB, is a security risk. No doubt about that. But you can always make things safer by disallowing stuff. > On FreeBSD sysctl security.bsd.unprivileged_proc_debug controls whether > applications like gdb or valgrind can run. Does Linux have an equivalent? I haven't used FreeBSD for like 18 years, and I'm not sure what exactly it does, but there's a possibility of doing `sysctl -w kernel.yama.ptrace_scope=2` or similar on Linux to restrict what you can do with ptrace. But I don't think that restrict valgrind though, just gdb, strace etc. Is Valgrind using ptrace for something? > FreeBSD Valgrind does support Capsicum (it's capability mode interface), but > it just passes on syscalls (after printing a warning when calling > cap_enter). The means some Valgrind functionality is lost (specifically > opening files after entering capability mode which at least one of the tools > uses). The trouble is that it's a bit random about what is disallowed by seccomp. The default filter will kill valgrind for sure and otherwise it's about analyzing random cBPF filter that might be completely different per application. But, bear in mind is that I'm not proposing this to be the default behaviour. Nothing really changes except that you have now a choice to disable sandboxing. It's, I think, reasonably well described in the man page including the security implications. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 345414] Missing seccomp support (WARNING: unhandled syscall: 317)
https://bugs.kde.org/show_bug.cgi?id=345414 Miroslav Franc changed: What|Removed |Added CC||mfr...@gmx.com --- Comment #12 from Miroslav Franc --- Created attachment 160505 --> https://bugs.kde.org/attachment.cgi?id=160505=edit --disable-seccomp=yes feature I propose an option --disable-seccomp=[no|yes] feature to Valgrind, which would fake "seccomp" syscall (and an old style "prctl(PR_SET_SECCOMP...)") success if set to "yes" and would otherwise default to "no". "prctl" case remains the same unless "yes" is selected and "seccomp" case now returns ENOSYS unless "yes" is selected. The patch also adds the option to the --help output, man page, and "none/tests/linux/seccomp" test case to the testsuite. The usecase is that some programs only allow switching seccomp off at compile time. This way, they can be analyzed without recompilation (at the cost of sandboxing being turned off, because Valgrind is efefctivelly faking seccomp filter installation without doing anything). The proper emulation of the seccomp feature is impossible since Linux kernel doesn't allow switching between two different filters dynamically and partial solution with Valgrind analyzing cBPF program and whitelisting syscalls it needs for itself is too much work for very little gain. I tested the patch with the entire testsuite on x86_64 and s390x architectures (OpenSUSE Tumbleweed). Expected behaviour: $ valgrind -q --disable-seccomp=yes file /etc/passwd /etc/passwd: ASCII text $ valgrind -q --disable-seccomp=no file /etc/passwd Bad system call $ valgrind -q file /etc/passwd Bad system call $ perl tests/vg_regtest none/tests/linux/seccomp seccomp: valgrind -q --disable-seccomp=yes ./seccomp == 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Miroslav Ďurian changed: What|Removed |Added CC||aas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459315] Dolphin crashes when clicking properties in context menu in "/"
https://bugs.kde.org/show_bug.cgi?id=459315 --- Comment #1 from Miroslav --- Created attachment 153297 --> https://bugs.kde.org/attachment.cgi?id=153297=edit New crash information added by DrKonqi dolphin (22.08.2) using Qt 5.15.6 Crashes after clicking Properties option on root disk -- Backtrace (Reduced): #6 0x7f375840cd9d in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/12.2.0/bits/atomic_base.h:488 #7 QAtomicOps::loadRelaxed (_q_value=) at /usr/include/qt/QtCore/qatomic_cxx11.h:239 #8 QBasicAtomicInteger::loadRelaxed (this=0x0) at /usr/include/qt/QtCore/qbasicatomic.h:107 [...] #10 QString::~QString (this=, this=) at /usr/include/qt/QtCore/qstring.h:1311 #11 QList::node_destruct (n=0x55b9c37b5bd8, this=0x7ffe9cce2768) at /usr/include/qt/QtCore/qlist.h:482 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459315] Dolphin crashes when clicking properties in context menu in "/"
https://bugs.kde.org/show_bug.cgi?id=459315 Miroslav changed: What|Removed |Added CC||qu4l...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429002] New: RFE: search box when choosing the printer driver
https://bugs.kde.org/show_bug.cgi?id=429002 Bug ID: 429002 Summary: RFE: search box when choosing the printer driver Product: systemsettings Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: miros...@suchy.cz CC: plasma-b...@kde.org Target Milestone: --- When you add a new printer (eg. ipp://192.168.1.100 ) and click on Next you get to the "Choose driver" dialog. Here it is separated to the Vendor list on the left and printer list on the right. Some venodors have only few printers (e.g., Fujitsu), but e.g. HP has a long list and it is hard to find the printer (try to find LaserJet Pro M252dw). It would be nice if there can be a search box so I can filter using a string (e.g. M252). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414471] wayland: wrong position for kickoff when taskbar is on the top of the screen (dual screen setup)
https://bugs.kde.org/show_bug.cgi?id=414471 Miroslav Spehar changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414471] New: wayland: wrong position for kickoff when taskbar is on the top of the screen (dual screen setup)
https://bugs.kde.org/show_bug.cgi?id=414471 Bug ID: 414471 Summary: wayland: wrong position for kickoff when taskbar is on the top of the screen (dual screen setup) Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mspe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY when taskbar is on the top, kickoff is shown on the wrong side of the screen https://i.imgur.com/lZTzmMk.png STEPS TO REPRODUCE 1. dual screen setup, move taskbar on the top left screen 2. start kickoff OBSERVED RESULT kickoff is top-right on the left screen EXPECTED RESULT kickoff is top-left on the left screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: fedora 31, kernel 5.3.11 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414470] New: wayland: wrong window position on maximize
https://bugs.kde.org/show_bug.cgi?id=414470 Bug ID: 414470 Summary: wayland: wrong window position on maximize Product: kwin Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- SUMMARY in dual screen setup (with hidpi), maximizing windows on the screen without taskbar is maximized only until the size up to the line where taskbar would be. check screenshot https://i.imgur.com/lZTzmMk.png STEPS TO REPRODUCE 1. maximize window on the screen without taskbar (in dual screen setup) OBSERVED RESULT maximizes screen up to the position of taskbar leaving part of the screen empty EXPECTED RESULT maximize over full screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.11 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414452] plasma crashes with reference to libc
https://bugs.kde.org/show_bug.cgi?id=414452 Miroslav Spehar changed: What|Removed |Added Version|master |5.16.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394899] System Settings crashes when selecting activities on wayland
https://bugs.kde.org/show_bug.cgi?id=394899 Miroslav Spehar changed: What|Removed |Added CC||mspe...@gmail.com --- Comment #4 from Miroslav Spehar --- Created attachment 124103 --> https://bugs.kde.org/attachment.cgi?id=124103=edit activities-kcm on fedora it does not crash, but shows as it is on the attached pic fedora 31 kf 5.61.0 qt 5.12.5 plasma 5.16.5 kernel 5.3.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414452] plasma crashes with reference to libc
https://bugs.kde.org/show_bug.cgi?id=414452 --- Comment #1 from Miroslav Spehar --- actually, better view on the dump is here https://paste.fedoraproject.org/paste/iAubV2NI8FruUkRjppWE0g -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414452] New: plasma crashes with reference to libc
https://bugs.kde.org/show_bug.cgi?id=414452 Bug ID: 414452 Summary: plasma crashes with reference to libc Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: 1.0 SUMMARY Plasma session crashes with no aparent bug trigger (left the pc alone). was using firefox before and once, just by using firefox it crashed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31, kernel 5.3.11 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.12.5 ADDITIONAL INFORMATION systemd-journald dump relevant for the crash Nov 24 12:28:13 r7 systemd-coredump[15128]: Process 13812 (plasmashell) of user 1000 dumped core. Stack trace of thread 13812: #0 0x7fea78e95625 raise (libc.so.6) #1 0x7fea7a7e7481 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x7fea78e956b0 __restore_rt (libc.so.6) #3 0x7fea78e95625 raise (libc.so.6) #4 0x7fea78e7e8d9 abort (libc.so.6) #5 0x7fea792a3b1b _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) #6 0x7fea752cb08b _ZNK15QtWaylandClient15QWaylandDisplay10checkErrorEv.cold (libQt5WaylandClient.so.5) #7 0x7fea752d6a4e _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5) #8 0x7fea794aadfb _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #9 0x7fea794b708c _ZN15QSocketNotifier9activatedEiNS_14QPrivateSignalE (libQt5Core.so.5) #10 0x7fea794b73f1 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5) #11 0x7fea79f71ad6 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #12 0x7fea79f7b150 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #13 0x7fea79480de8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #14 0x7fea794d6667 _ZL28socketNotifierSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5) #15 0x7fea77bd84a0 g_main_context_dispatch (libglib-2.0.so.0) #16 0x7fea77bd8830 g_main_context_iterate.isra.0 (libglib-2.0.so.0) #17 0x7fea77bd88d3 g_main_context_iteration (libglib-2.0.so.0) #18 0x7fea794d5cb5 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #19 0x7fea7947fceb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #20 0x7fea79487a16 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #21 0x55c421ce57e4 main (plasmashell) #22 0x7fea78e801a3 __libc_start_main (libc.so.6) #23 0x55c421ce5c6e _start (plasmashell) Stack trace of thread 14047: #0 0x7fea7877ad45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7fea6d72cebb util_queue_thread_func (radeonsi_dri.so) #2 0x7fea6d72cacb impl_thrd_routine (radeonsi_dri.so) #3 0x7fea787744e2 start_thread (libpthread.so.0) #4 0x7fea78f5a693 __clone (libc.so.6) Stack trace of thread 14078: #0 0x7fea7877ad45 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7fea6d72cebb util_queue_thread_func (radeonsi_dri.so) #2 0x7fea6d72cacb impl_thrd_routine (radeonsi_dri.so) #3 0x7fea787744e2 start_thread (libpthread.so.0) #4
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #5 from Miroslav Spehar --- Created attachment 122102 --> https://bugs.kde.org/attachment.cgi?id=122102=edit 25% cpu kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #4 from Miroslav Spehar --- after reinstallation of virtual machine, same situation again. post installaton steps: - update all packages - remove plasma-discover - install openssh-server - apt autoremove - configure autologin to wayland session in plasma settings status after reinstall: - cpu is ~25% while lockscreen is on - after monitors are turned off, session cannot be recovered via gui if i kill one of the other processes, session crashes. fwiw, i do not start manually those kwin processes, they are started by sddm it seems. i added a screenshot of htop with hierarchy. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #2 from Miroslav Spehar --- *disabled baloo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 --- Comment #1 from Miroslav Spehar --- Created attachment 122091 --> https://bugs.kde.org/attachment.cgi?id=122091=edit kubuntu htop showing cpu usage same thing happens on kubuntu with latest updates. i uninstalled plasma-discover and disabled ubuntu. cpu spike is triggered when kscreen locker kicks in -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410856] New: wayland: kwin uses 100% cpu when idle
https://bugs.kde.org/show_bug.cgi?id=410856 Bug ID: 410856 Summary: wayland: kwin uses 100% cpu when idle Product: kwin Version: 5.16.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Created attachment 122090 --> https://bugs.kde.org/attachment.cgi?id=122090=edit htop showing cpu usage SUMMARY 100% cpu usage when left to be idle in VM. when screen is activated, cpu usage drops. STEPS TO REPRODUCE 1. install basic archlinux desktop with kde plasma 2. login into wayland session 3. disable baloo 4. leave the machine for a while OBSERVED RESULT 100% cpu usage in kwin EXPECTED RESULT minimal cpu usage for kwin SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60 Qt Version: 5.13 ADDITIONAL INFORMATION journal | grep kwin Aug 03 18:03:17 vm-arch kernel: kwin_wayland[450]: segfault at 128 ip 7f645d812e9c sp 7ffd89473ee0 error 4 in libkwin.so.5.16.4[7f645d66f000+1eb000] Aug 03 18:03:17 vm-arch kernel: audit: type=1701 audit(1564848197.113:57): auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 03 18:03:17 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 03 18:05:32 vm-arch kernel: audit: type=1701 audit(1564848332.356:38): auid=1000 uid=1000 gid=998 ses=2 pid=448 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 03 18:05:32 vm-arch audit[448]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=448 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:22:16 vm-arch audit[3307]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=3307 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:22:16 vm-arch kernel: audit: type=1701 audit(1565518936.686:44): auid=1000 uid=1000 gid=998 ses=2 pid=3307 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:36:50 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:36:50 vm-arch kernel: audit: type=1701 audit(1565519810.083:42): auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aug 11 12:49:23 vm-arch kdeinit5[750]: kio_smb: dirp->name kwin.txt "kwin.txt" ' "" ' 8 Aug 11 12:49:23 vm-arch kdeinit5[750]: kio_smb: updateCache "/red/kwin.txt" Aug 11 12:49:24 vm-arch kdeinit5[743]: kio_smb: dirp->name kwin.txt "kwin.txt" ' "" ' 8 Aug 11 12:49:24 vm-arch kdeinit5[743]: kio_smb: updateCache "/red/kwin.txt" Aug 11 12:51:10 vm-arch systemsettings5[758]: org.kde.kcoreaddons: Error loading plugin "kcm_kwindecoration" "The shared library was not found." Aug 11 12:51:10 vm-arch systemsettings5[758]: Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations. Aug 11 12:51:13 vm-arch systemsettings5[758]: KActivitiesStats( 0x55c343144b00 ) ResultModelPrivate::onResultScoreUpdated result added: "kcm:kwindecoration.desktop" score: 0 last: 1565520673 first: 1565520673 Aug 11 12:55:09 vm-arch audit[451]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=451 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 12:55:09 vm-arch kernel: audit: type=1701 audit(1565520909.576:44): auid=1000 uid=1000 gid=998 ses=2 pid=451 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 13:27:19 vm-arch audit[450]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 13:27:19 vm-arch kernel: audit: type=1701 audit(1565522839.420:45): auid=1000 uid=1000 gid=998 ses=2 pid=450 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 13:28:03 vm-arch audit[453]: ANOM_ABEND auid=1000 uid=1000 gid=998 ses=2 pid=453 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Aug 11 13:28:03 vm-arch kernel: audit: type=1701 audit(1565522883.836:42): auid=1000 uid=1000 gid=998 ses=2 pid=453 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=11 res=1 Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aug 11 13:29:02 vm-arch systemsettings5[660]: org.kde.kcoreaddons: Error loading plugin "kcm_kwindecoration" "The
[plasmashell] [Bug 410652] New: Changing icons theme in settings does not change category icons in Kickoff
https://bugs.kde.org/show_bug.cgi?id=410652 Bug ID: 410652 Summary: Changing icons theme in settings does not change category icons in Kickoff Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mspe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Changing icons theme in settings does not change category icons in Kickoff. This gets changed only when look-and-feel is changed. STEPS TO REPRODUCE 1. Install papirus icon theme 2. Change icon theme 3. Start Kickoff and verify that icons Favorites, Applications, Computer... have not been updated OBSERVED RESULT After changing icon theme, category icons in Kickoff are not updated EXPECTED RESULT After changing icon theme, category icons in Kickoff are used from the newly selected theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: arch KDE Plasma Version: 5.16 ADDITIONAL INFORMATION Same happens with Kicker -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383901] PTP_ENABLE_PPS ioctl
https://bugs.kde.org/show_bug.cgi?id=383901 Miroslav Lichvar changed: What|Removed |Added CC||mlich...@redhat.com --- Comment #2 from Miroslav Lichvar --- FWIW, I've submitted a patch adding a complete support for PTP ioctls in bug #409206. It does the same thing for the PTP_ENABLE_PPS ioctl as this patch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409206] [PATCH] Support for Linux PPS and PTP ioctls
https://bugs.kde.org/show_bug.cgi?id=409206 --- Comment #2 from Miroslav Lichvar --- Created attachment 121156 --> https://bugs.kde.org/attachment.cgi?id=121156=edit Add support for Linux PTP HW clock ioctls -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409206] [PATCH] Support for Linux PPS and PTP ioctls
https://bugs.kde.org/show_bug.cgi?id=409206 --- Comment #1 from Miroslav Lichvar --- Created attachment 121155 --> https://bugs.kde.org/attachment.cgi?id=121155=edit Add support for Linux Pulse-Per-Second ioctls -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409206] New: [PATCH] Support for Linux PPS and PTP ioctls
https://bugs.kde.org/show_bug.cgi?id=409206 Bug ID: 409206 Summary: [PATCH] Support for Linux PPS and PTP ioctls Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: mlich...@redhat.com Target Milestone: --- valgrind currently doesn't support Linux ioctls used on PTP hardware clock devices and Pulse-Per-Second devices. They are typically used by various NTP and PTP implementations (e.g. ntpd, linuxptp, chrony). -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 401488] New: .
https://bugs.kde.org/show_bug.cgi?id=401488 Bug ID: 401488 Summary: . Product: Active Window Control Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: unity.ege...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open up panel for adding widgets 2. Click button Get New Widgets three times 3. On third click, crash happens OBSERVED RESULT Crashed on third button press... EXPECTED RESULT Expected not to crash... :) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux 9 KDE Plasma Version: 5.8.6 KDE Frameworks Version: 5.28.0 Qt Version: 5.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 324736] Konversation can not reconnect when I enter VPN
https://bugs.kde.org/show_bug.cgi?id=324736 Miroslav Suchy changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from Miroslav Suchy --- As of Fedora 29 this is not happening. Closing. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365080] broken state after deleting a single item of a event series
https://bugs.kde.org/show_bug.cgi?id=365080 --- Comment #2 from Miroslav Vujicic --- *** Bug 397408 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 397408] Deleting calendar event in DAV groupware resource fails
https://bugs.kde.org/show_bug.cgi?id=397408 Miroslav Vujicic changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Miroslav Vujicic --- *** This bug has been marked as a duplicate of bug 365080 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365080] broken state after deleting a single item of a event series
https://bugs.kde.org/show_bug.cgi?id=365080 Miroslav Vujicic changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 365080] broken state after deleting a single item of a event series
https://bugs.kde.org/show_bug.cgi?id=365080 Miroslav Vujicic changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||miros...@vujicic.com --- Comment #1 from Miroslav Vujicic --- *** This bug has been marked as a duplicate of bug 397408 *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 397408] Deleting calendar event in DAV groupware resource fails
https://bugs.kde.org/show_bug.cgi?id=397408 Miroslav Vujicic changed: What|Removed |Added CC||tom-kde.b...@monster-box.de --- Comment #1 from Miroslav Vujicic --- *** Bug 365080 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 397408] New: Deleting calendar event in DAV groupware resource fails
https://bugs.kde.org/show_bug.cgi?id=397408 Bug ID: 397408 Summary: Deleting calendar event in DAV groupware resource fails Product: korganizer Version: 5.8.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: groupware Assignee: kdepim-b...@kde.org Reporter: miros...@vujicic.com Target Milestone: --- I can create and edit events in CalDav resources, but deleting fails. If I try and delete an event I created, the event disappears from the local calendar view, but when I try to update the calendar folder I get "Before syncing it is necessary to have the resource online. Do you want to make it online?", and I click "Go Online". If I try to update the calendar again the same happens again - which means the upstream resource was not updated. When I look in akonadiconsole, in Agents tab, next to the resource there is a Status Message: "There was a problem with the request. The item has not been deleted from the server. The file or folder does not exist. (0)." Once this happens, the only thing I can do (what I found so far) is delete the agent and re-create it. I got the line from the calendar log: Code: Select all 2404:130:0:1000:4186:4465:8a69:1b4c - [23/Apr/2018:06:27:11 +1200] "DELETE /caldav.php//1518548964.R513.ics/ HTTP/1.1" 404 407 "-" "Mozilla/5.0 (X11; Linux x86_64) KHTML/5.38.0 (like Gecko) Konqueror/5 KIO/5.38" I was told that trailing slash after 1518548964.R513.ics is probably the culprit. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 397136] wayland: after energy saving turns monitors off and i try to wake them on with a mouse, one monitor is unusable
https://bugs.kde.org/show_bug.cgi?id=397136 Miroslav Spehar changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 397136] New: wayland: after energy saving turns monitors off and i try to wake them on with a mouse, one monitor is unusable
https://bugs.kde.org/show_bug.cgi?id=397136 Bug ID: 397136 Summary: wayland: after energy saving turns monitors off and i try to wake them on with a mouse, one monitor is unusable Product: Powerdevil Version: 5.13.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- this happens on wayland: two monitors, both hidpi, one connected via hdmi (primary), the other one with displyport. after energy saving turns monitor off and i wake them on by interacting with mouse, one monitor (display port, secondary) gets turned off. Picture is only shown on the primary and this one has wrong scaling set. Mouse can be moved to the 'other' monitor, which is now in a wrong position (left side instead of right) and picture cannot be seen. Have to restart computer to get back proper setup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396316] New: wayland: journal error on mouse over icons when using icons only task manager
https://bugs.kde.org/show_bug.cgi?id=396316 Bug ID: 396316 Summary: wayland: journal error on mouse over icons when using icons only task manager Product: plasmashell Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: mspe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 on every mouseover event for icons pinned in icons only task manager, error is reported in system journal: plasmashell[1327]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:342: Unable to assign [undefined] to int reproducible: always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396315] New: wayland: journal is filling up with kf5idletime_kwayland: This plugin does not support polling idle time
https://bugs.kde.org/show_bug.cgi?id=396315 Bug ID: 396315 Summary: wayland: journal is filling up with kf5idletime_kwayland: This plugin does not support polling idle time Product: plasmashell Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: 1.0 journal is filling up with the following error: kf5idletime_kwayland: This plugin does not support polling idle time -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396272] wayland: kwin crashes after energy saving turns monitors off and i try to wake them on with a mouse
https://bugs.kde.org/show_bug.cgi?id=396272 --- Comment #4 from Miroslav Spehar --- is this connected? https://bugs.kde.org/show_bug.cgi?id=385743 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396314] New: wayland: systemsettings5 crashes upon selecting window decorations when one monitor is scaled
https://bugs.kde.org/show_bug.cgi?id=396314 Bug ID: 396314 Summary: wayland: systemsettings5 crashes upon selecting window decorations when one monitor is scaled Product: systemsettings Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: enter systemsettings5 -> application style -> window decorations this happens in dual screen setup with one monitor being standard dpi and the other one is hidpi AND while systemsettings5 is currently on the standard dpi monitor - Unusual behavior I noticed: in dual screen setup, when one monitor is hidpi and scaled to 2, the other on is standard dpi with scale of 1, entering systemsettings5 -> application style -> window decoration crashes systemsettings5 this happens only when systemsettings5 is found on the standard dpi monitor. if systemsettings5 is found to be on the hidpi monitor, then it opens window decorations without crashing. additionally to this, apply button is disabled until the window is resized manually. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9e790cbcc0 (LWP 2017))] Thread 19 (Thread 0x7f9e06030700 (LWP 2038)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x562cbf5c1c54) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562cbf5c1c00, cond=0x562cbf5c1c28) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x562cbf5c1c28, mutex=0x562cbf5c1c00) at pthread_cond_wait.c:655 #3 0x7f9e74e2afab in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x562cbf5c1c00) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait(QMutex*, unsigned long) () at thread/qwaitcondition_unix.cpp:215 #5 0x7f9e7301b2a9 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x562cbf658e98) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:245 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x562cbf658e20) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:709 #7 0x7f9e7301b4da in QSGRenderThread::run() () at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:738 #8 0x7f9e74e2a8ec in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #9 0x7f9e6fffc554 in start_thread (arg=) at pthread_create.c:463 #10 0x7f9e7470fccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f9e06831700 (LWP 2037)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x562cbf6c5a88) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562cbf6c5a38, cond=0x562cbf6c5a60) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x562cbf6c5a60, mutex=0x562cbf6c5a38) at pthread_cond_wait.c:655 #3 0x7f9e5b40f69b in cnd_wait (mtx=0x562cbf6c5a38, cond=0x562cbf6c5a60) at ../../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x562cbf651040) at u_queue.c:255 #5 0x7f9e5b40f3c7 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #6 0x7f9e6fffc554 in start_thread (arg=) at pthread_create.c:463 #7 0x7f9e7470fccf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f9e35c90700 (LWP 2036)): #0 0x7f9e747052c9 in __GI___poll (fds=0x7f9e0c004e00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9e6d9482c6 in g_main_context_poll (priority=, n_fds=1, fds=0x7f9e0c004e00, timeout=, context=0x7f9e0c000bf0) at gmain.c:4204 #2 g_main_context_iterate (context=context@entry=0x7f9e0c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3898 #3 0x7f9e6d9483ec in g_main_context_iteration (context=0x7f9e0c000bf0, may_block=may_block@entry=1) at gmain.c:3964 #4 0x7f9e75012b3b in QEventDispatcherGlib::processEvents (this=0x7f9e0c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f9e74fc2b3b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f9e74e21326 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f9e72b14085 in
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 --- Comment #4 from Miroslav Spehar --- Created attachment 113839 --> https://bugs.kde.org/attachment.cgi?id=113839=edit gdb backtrace actually i figure out how to get the backtrace, it's attached. explanation how did it work: 1. when i try to enter application style on standard dpi monitor, systemsettings5 crashes 2. when i try to enter application style on hidpi monitor, it works i'll open another bug with this issue(s) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 Miroslav Spehar changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Miroslav Spehar --- bt added -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 --- Comment #3 from Miroslav Spehar --- (In reply to David Edmundson from comment #2) > Crashes need backtraces unfortunatelly, now also going in that area of systemsettings5 also crashes, so i can't reach the problem with closing the window to get the backtrace. would it help if i provide backtrace of systemsettings5 crashing? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393649] Monitor reports no signal if turned off and back on with wayland session
https://bugs.kde.org/show_bug.cgi?id=393649 --- Comment #6 from Miroslav Spehar --- (In reply to Roman Gilg from comment #5) > Btw can you check from the virtual terminal if the KWin process is still > running and get a trace of the last calls it did. i opened a new bug since description when it happens is a bit different https://bugs.kde.org/show_bug.cgi?id=396272 backtrace is attached there -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396308] wayland: clearing clipboard history crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396308 Miroslav Spehar changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396308] New: wayland: clearing clipboard history crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396308 Bug ID: 396308 Summary: wayland: clearing clipboard history crashes plasma Product: kwin Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Created attachment 113830 --> https://bugs.kde.org/attachment.cgi?id=113830=edit gdb-backtrace clearing clipboard history on wayland crashes plasma steps to reproduce: 1. click in tray on clipboard contents 2. click clear history 3. confirming it on a popup dialog happens every time. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 396306] New: wayland: in dual screen, unlocking is possible only on one monitor
https://bugs.kde.org/show_bug.cgi?id=396306 Bug ID: 396306 Summary: wayland: in dual screen, unlocking is possible only on one monitor Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com CC: bhus...@gmail.com Target Milestone: --- in dual screen configuration, when screen is locked and i try to unclock it, it is possible only from one screen (in my case it's hidpi screen). other screen, even though it shows password field, clicking it or typing is automatically entered on the other screen. it is happening every time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395492] Crash when opening system settings > application style > window decorations
https://bugs.kde.org/show_bug.cgi?id=395492 Miroslav Spehar changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|BACKTRACE |--- --- Comment #4 from Miroslav Spehar --- (In reply to Martin Flöser from comment #2) > Unfortunately the backtrace is lacking debug symbols. If you are able to > reproduce please install debug packages and attach a new backtrace. Would attached bt work? Drkonqi complained about some missing debuginfo packages, but when 'install dependencies' was clicked, it didnt install anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395492] Crash when opening system settings > application style > window decorations
https://bugs.kde.org/show_bug.cgi?id=395492 --- Comment #3 from Miroslav Spehar --- Created attachment 113815 --> https://bugs.kde.org/attachment.cgi?id=113815=edit New crash information added by DrKonqi systemsettings5 (5.13.2) using Qt 5.11.1 - What I was doing when the application crashed: open systemsettings5 -> click on application style -> window decorations -- Backtrace (Reduced): #6 0x7fd1130d4024 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x10011) at /usr/include/c++/8/bits/atomic_base.h:390 #7 QAtomicOps::load (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:227 #8 QBasicAtomicInteger::load (this=0x10011) at /usr/include/qt5/QtCore/qbasicatomic.h:103 #9 QtPrivate::RefCount::isShared (this=0x10011) at /usr/include/qt5/QtCore/qrefcount.h:101 [...] #11 QHash::operator[] (akey=@0x7ffd0482d148: 0x5573de58f090, this=0x5573de57f7f8) at /usr/include/qt5/QtCore/qhash.h:753 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 Miroslav Spehar changed: What|Removed |Added Version|5.12.4 |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396272] wayland: kwin crashes after energy saving turns monitors off and i try to wake them on with a mouse
https://bugs.kde.org/show_bug.cgi?id=396272 Miroslav Spehar changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396272] New: wayland: kwin crashes after energy saving turns monitors off and i try to wake them on with a mouse
https://bugs.kde.org/show_bug.cgi?id=396272 Bug ID: 396272 Summary: wayland: kwin crashes after energy saving turns monitors off and i try to wake them on with a mouse Product: kwin Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Created attachment 113814 --> https://bugs.kde.org/attachment.cgi?id=113814=edit gdb backtrace - What I was doing when the application crashed: Every time after resume from screen energy saving mode, plasma is wither non-responsive or just turns on the backlight of monitors without picture showing. Reproducible: Always Steps to Reproduce: 1. From System settings-> power management, set the "Screen energy saving" to 10 mins 2. Leave the screen to go blank and wait around 10 more mins (sometimes more) 3. Move the mouse so screen gets back There are two related bugs reported https://bugs.kde.org/show_bug.cgi?id=364526 https://bugs.kde.org/show_bug.cgi?id=348487 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when trying to close any window
https://bugs.kde.org/show_bug.cgi?id=396258 Miroslav Spehar changed: What|Removed |Added Summary|wayland: using window |wayland: using window |decorations installed from |decorations installed from |store crashes plasma when |store crashes plasma when |any window is closed|trying to close any window -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396235] wayland: alt-tab or selecting help -> about on a maximized window resizes that window
https://bugs.kde.org/show_bug.cgi?id=396235 --- Comment #2 from Miroslav Spehar --- in further testing, it seems that it does this resize whenever some dialog gets shown. window doesn't even have to be maximized: reproduce: shift-del in dolphin will resize dolphin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] wayland: using window decorations installed from store crashes plasma when any window is closed
https://bugs.kde.org/show_bug.cgi?id=396258 Miroslav Spehar changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396258] New: wayland: using window decorations installed from store crashes plasma when any window is closed
https://bugs.kde.org/show_bug.cgi?id=396258 Bug ID: 396258 Summary: wayland: using window decorations installed from store crashes plasma when any window is closed Product: plasmashell Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: 1.0 when using window decoration theme from kde store, it crashes plasma whenever window is being closed. afterwards i cannot access terminal. reproduce: install window decorations like lindows, change theme to that one and try to close the window hint: might be connected to sddm since sddm hangs during reboot until timeout is reached (remotely triggered) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396235] wayland: alt-tab or selecting help -> about on a maximized window resizes that window
https://bugs.kde.org/show_bug.cgi?id=396235 --- Comment #1 from Miroslav Spehar --- seems to happen also when active window gets changed with a mouse -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 --- Comment #5 from Miroslav Spehar --- Created attachment 113807 --> https://bugs.kde.org/attachment.cgi?id=113807=edit New crash information added by DrKonqi plasmashell (5.13.2) using Qt 5.11.1 - What I was doing when the application crashed: changing desktop configuration -> from folder to desktop view -- Backtrace (Reduced): #6 0x7f0b12d90a27 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at kernel/qobject.cpp:2680 [...] #8 0x7f0a02339349 in Kirigami::PlatformTheme::qmlAttachedProperties(QObject*) () from /usr/lib64/libKF5Kirigami2.so.5 #9 0x7f0b165cd2ed in QtQml::qmlAttachedPropertiesObjectById (id=, object=0x556d7b5140b0, create=create@entry=true) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/qqmlengine.cpp:1576 #10 0x7f0b16665a93 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/qqmlobjectcreator.cpp:799 #11 0x7f0b166679f4 in QQmlObjectCreator::setupBindings (this=this@entry=0x7ffc23d07b20, applyDeferredBindings=applyDeferredBindings@entry=false) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/qqmlobjectcreator.cpp:777 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 Miroslav Spehar changed: What|Removed |Added Version|5.13.1 |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 Miroslav Spehar changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from Miroslav Spehar --- Done. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 Miroslav Spehar changed: What|Removed |Added CC||mspe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396238] wayland: picture of the day in multiscreen (standardpi+hidpi) is not properly scaled on hidpi screen
https://bugs.kde.org/show_bug.cgi?id=396238 Miroslav changed: What|Removed |Added Version|5.13.1 |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396235] wayland: alt-tab or selecting help -> about on a maximized window resizes that window
https://bugs.kde.org/show_bug.cgi?id=396235 Miroslav changed: What|Removed |Added Version|5.13.1 |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396236] wayland: systemsettings changing order and scale of monitor is not persisted between reboots
https://bugs.kde.org/show_bug.cgi?id=396236 Miroslav changed: What|Removed |Added Version|5.13.1 |5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 --- Comment #1 from Miroslav --- this happens in multiscreen configuration with one monitor being standard dpi, the other one hidpi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396238] New: wayland: picture of the day in multiscreen (standardpi+hidpi) is not properly scaled on hidpi screen
https://bugs.kde.org/show_bug.cgi?id=396238 Bug ID: 396238 Summary: wayland: picture of the day in multiscreen (standardpi+hidpi) is not properly scaled on hidpi screen Product: plasmashell Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: mspe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 wallpaper is not scaled properly on wayland when in multiscreen configuration when one monitor is standard dpi and the other one is hidpi. picture on hidpi monitor seems 1/4 of the full picture. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396237] New: wayland: changing from folder view to desktop view and vice versa crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396237 Bug ID: 396237 Summary: wayland: changing from folder view to desktop view and vice versa crashes plasma Product: plasmashell Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: mspe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 in desktop settings, when changing between folder view and desktop view on wayland, plasma shell crashes. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 396236] New: wayland: systemsettings changing order and scale of monitor is not persisted between reboots
https://bugs.kde.org/show_bug.cgi?id=396236 Bug ID: 396236 Summary: wayland: systemsettings changing order and scale of monitor is not persisted between reboots Product: KScreen Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Monitor settings (left-right position) and scaling is not persisted between reboots. Solved in archlinux in Bug 389490, but still there on opensuse tw. Reported in opensuse bugzilla here: https://bugzilla.opensuse.org/show_bug.cgi?id=1096815 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396235] wayland: alt-tab or selecting help -> about on a maximized window resizes that window
https://bugs.kde.org/show_bug.cgi?id=396235 Miroslav changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396235] wayland: alt-tab or selecting help -> about on a maximized window resizes that window
https://bugs.kde.org/show_bug.cgi?id=396235 Miroslav changed: What|Removed |Added Version|5.13.2 |5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396235] New: wayland: alt-tab or selecting help -> about on a maximized window resizes that window
https://bugs.kde.org/show_bug.cgi?id=396235 Bug ID: 396235 Summary: wayland: alt-tab or selecting help -> about on a maximized window resizes that window Product: plasmashell Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: 1.0 in opensuse, when having a maximized window, choosing help->about resizes that window. also happens on alt-tab. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393649] Monitor reports no signal if turned off and back on with wayland session
https://bugs.kde.org/show_bug.cgi?id=393649 Miroslav changed: What|Removed |Added CC||mspe...@gmail.com --- Comment #4 from Miroslav --- By turn-off i believe you meant when system turns off monitor after 5min of inactivity? If so, i have a similar issue, but on opensuse tw i couldn't even activate tty. Reported the issue here: https://bugzilla.opensuse.org/show_bug.cgi?id=1096816 And here is the journal extract for relevant period: https://bugzilla.opensuse.org/attachment.cgi?id=776295 Just guessing here, but could here also be problem with sddm? I could remotely shutdown the pc since sshd was working, but during shutdown it says "shutting down sddm" and then waits for timeout. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396214] New: wayland: crash when opening systemsettings5 -> fonts after setting 'antialiasing' to enabled
https://bugs.kde.org/show_bug.cgi?id=396214 Bug ID: 396214 Summary: wayland: crash when opening systemsettings5 -> fonts after setting 'antialiasing' to enabled Product: systemsettings Version: 5.13.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: starting systemsettings5, then selecting fonts - Unusual behavior I noticed: at first i could open this part of the settings. after changing settings 'aliasing' to 'enabled', this part of the settings crashes the whole systemsettings5 app The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f67b9caecc0 (LWP 2097))] Thread 17 (Thread 0x7f675696b700 (LWP 2116)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f6757fff700 (LWP 2113)): #0 0x7f67b52e52c9 in poll () from /lib64/libc.so.6 #1 0x7f67ae5292c6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f67ae5293ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f67b5bf2b3b in QEventDispatcherGlib::processEvents (this=0x7f674c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f67b5ba2b3b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f67b5a01326 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f67b36f4085 in QQmlThreadPrivate::run (this=0x564bf428d300) at /usr/src/debug/libqt5-qtdeclarative-5.11.1-1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148 #7 0x7f67b5a0a8ec in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #8 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #9 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f6765f4f700 (LWP 2112)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f6766a8c700 (LWP 2111)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f67677fe700 (LWP 2110)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f6767fff700 (LWP 2109)): #0 0x7f67b0be24dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f679b40f69b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f679b40f3c7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f67b0bdc554 in start_thread () from /lib64/libpthread.so.0 #4 0x7f67b52efccf in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f676df61700 (LWP 2108)): #0 0x7f67b52e52c9 in poll () from /lib64/libc.so.6 #1 0x7f67ae5292c6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f67ae5293ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f67b5bf2b3b in QEventDispatcherGlib::processEvents (this=0x7f6768000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f67b5ba2b3b in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f67b5a01326 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f67b36f4085 in QQmlThreadPrivate::run (this=0x564bf3be1080) at
[systemsettings] [Bug 347288] Audio Hardware Setup settings are not preserved
https://bugs.kde.org/show_bug.cgi?id=347288 Miroslav changed: What|Removed |Added CC||mspe...@gmail.com --- Comment #3 from Miroslav --- I have the same issue with plasma 5.13 One audio device is on the motherboard, 2nd one is on the graphics card. After every reboot, settings default to the digital stereo output which of course doesnt work since i have just regular speaker connected to lineout -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395492] Crash when opening system settings > application style > window decorations
https://bugs.kde.org/show_bug.cgi?id=395492 Miroslav changed: What|Removed |Added CC||mspe...@gmail.com --- Comment #1 from Miroslav --- I have the same issue. Most of the times i select window decorations, systemsettings5 dies. Maybe worth to mention, for me this happens on wayland and it seems that kcm is not adjusted yet to work on wayland (there are some scaling issues with this part of systemsettings). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395541] New: Left handed mouse control ignored on startup
https://bugs.kde.org/show_bug.cgi?id=395541 Bug ID: 395541 Summary: Left handed mouse control ignored on startup Product: systemsettings Version: 5.13.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: miros...@vujicic.com CC: unassigned-b...@kde.org Target Milestone: --- On startup, left handed mouse controls are ignored, and the mouse works like right handed. When I go to Settings -> Input Devices -> Mouse it shows 'Left handed' as selected, so at that stage I have to select 'Right handed', click Apply, and then select 'Left handed' again. Only then it starts behaving as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394786] [Wayland] New blur effect shows weird background glitches
https://bugs.kde.org/show_bug.cgi?id=394786 Miroslav changed: What|Removed |Added Assignee|mspe...@gmail.com |kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394786] [Wayland] New blur effect shows weird background glitches
https://bugs.kde.org/show_bug.cgi?id=394786 Miroslav changed: What|Removed |Added Ever confirmed|0 |1 Assignee|kwin-bugs-n...@kde.org |mspe...@gmail.com Status|UNCONFIRMED |CONFIRMED CC||mspe...@gmail.com --- Comment #2 from Miroslav --- Created attachment 113318 --> https://bugs.kde.org/attachment.cgi?id=113318=edit kde-blur-issue-plasma-5.13 same thing happens on release 5.13 i have dual screen setup where left screen is standard dpi (and it blurs things properly), but the right one is hidpi and this one is not rendering properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 --- Comment #13 from Miroslav <mspe...@gmail.com> --- Since latest update on Archlinux, the content of e.g. Kate is now properly rendered. The problem remains with menus (e.g. when i click 'edit' in kate, text in dropdown menu is still pixelated) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392584] systemsettings -> desktop behavior -> screen locking; crashes when changing color
https://bugs.kde.org/show_bug.cgi?id=392584 Miroslav <mspe...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Miroslav <mspe...@gmail.com> --- upgraded to arch and qt5.10 now it seems to work. -- You are receiving this mail because: You are watching all bug changes.
[kdepimlibs] [Bug 393245] New: Wrong day for Teachers day in Slovak holiday calendar
https://bugs.kde.org/show_bug.cgi?id=393245 Bug ID: 393245 Summary: Wrong day for Teachers day in Slovak holiday calendar Product: kdepimlibs Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kholidays Assignee: jl...@kde.org Reporter: aas...@gmail.com CC: kdepim-b...@kde.org Target Milestone: --- Holiday for Slovakia (sk_sk) has wrong date for Teachers day. It should be 28.March, not 28.April. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 --- Comment #12 from Miroslav <mspe...@gmail.com> --- at the following link: https://paste.kde.org/pcvzovpsh -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 --- Comment #10 from Miroslav <mspe...@gmail.com> --- That is, now qt 5.10.1 is installed and it is still doesnt work -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 Miroslav <mspe...@gmail.com> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|UPSTREAM|--- --- Comment #9 from Miroslav <mspe...@gmail.com> --- Installed archlinux with KDE. Same behaviour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 Miroslav <mspe...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #7 from Miroslav <mspe...@gmail.com> --- "about system" says qt: 5.9.4 plasma version: 5.12.4 frameworks: 5.44 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 Miroslav <mspe...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Miroslav <mspe...@gmail.com> --- Requested INFO added -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 --- Comment #4 from Miroslav <mspe...@gmail.com> --- GS_LIB=/home/mspehar/.fonts KDE_FULL_SESSION=true LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36: LC_MEASUREMENT=de_AT.UTF-8 LESSCLOSE=/usr/bin/lesspipe %s %s LC_PAPER=de_AT.UTF-8 LC_MONETARY=de_AT.UTF-8 LANG=en_US.UTF-8 PROFILEHOME= DISPLAY=:1 SHELL_SESSION_ID=733eca4e85234415a478f47867eda9f7 COLORTERM=truecolor XDG_VTNR=2 PAM_KWALLET5_LOGIN=/run/user/1000/kwallet5.socket XKB_DEFAULT_LAYOUT=hr LC_NAME=de_AT.UTF-8 XDG_SESSION_ID=3 USER=mspehar DESKTOP_SESSION=plasmawayland TEXTDOMAINDIR=/usr/share/locale/ WAYLAND_DISPLAY=wayland-0 PWD=/home/mspehar HOME=/home/mspehar TEXTDOMAIN=im-config XDG_SESSION_TYPE=wayland XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop KONSOLE_DBUS_SESSION=/Sessions/1 XDG_SESSION_DESKTOP=KDE LC_ADDRESS=de_AT.UTF-8 LC_NUMERIC=de_AT.UTF-8 KONSOLE_DBUS_WINDOW=/Windows/1 QT_WAYLAND_FORCE_DPI=96 TERM=xterm-256color SHELL=/bin/bash KONSOLE_DBUS_SERVICE=:1.49 XDG_SESSION_CLASS=user XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 XKB_DEFAULT_MODEL=pc105 IM_CONFIG_PHASE=2 XCURSOR_THEME=breeze_cursors XDG_CURRENT_DESKTOP=KDE KONSOLE_PROFILE_NAME=default QT_WAYLAND_DISABLE_WINDOWDECORATION=1 XDG_SEAT=seat0 SHLVL=1 COLORFGBG=15;0 LANGUAGE= WINDOWID=1 LC_TELEPHONE=de_AT.UTF-8 PLASMA_USE_QT_SCALING=1 QT_QPA_PLATFORM=wayland LOGNAME=mspehar DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-FtfFLAj75h,guid=ea47b744f9cd31b1bdd5192b5ac26fb0 XDG_RUNTIME_DIR=/run/user/1000 PAM_KWALLET_LOGIN=/run/user/1000/kwallet.socket XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1 QT_AUTO_SCREEN_SCALE_FACTOR=0 PATH=/home/mspehar/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin LC_IDENTIFICATION=de_AT.UTF-8 KDE_SESSION_UID=1000 KDE_SESSION_VERSION=5 SESSION_MANAGER=local/r7:@/tmp/.ICE-unix/1712,unix/r7:/tmp/.ICE-unix/1712 LESSOPEN=| /usr/bin/lesspipe %s LC_TIME=de_AT.UTF-8 _=/usr/bin/env -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 Miroslav <mspe...@gmail.com> changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 --- Comment #2 from Miroslav <mspe...@gmail.com> --- ok, just tested it, the behavior is like this in two monitor setup, where one monitor is standard dpi and the other one is hidpi, the order in kscreen matters. - when left (1st) monitor is standard dpi, picture on hidpi monitor is pixelated - when left (1st) monitor is hidpi, the picture on hidpi monitor is ok described case fixes pixelated text in case applications are running natively on wayland (tested on dolphin, kate, konsole) it doesn't work with applications which are running through xorg (firefox, intellij as snap, intellij as downloaded app) not sure about falkon though: configuration menu is not pixelated, but tab titles are. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 --- Comment #1 from Miroslav <mspe...@gmail.com> --- what i've noticed is that when new user account is created and default monitor arrangement is used, the pixelation doesnt happen. once i switch monitor left/right i systemsettings, the pixelation starts to happen. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 392579] wrongly reported energy information about battery
https://bugs.kde.org/show_bug.cgi?id=392579 --- Comment #2 from Miroslav <mspe...@gmail.com> --- root@r7:/home# upower -d Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_0 native-path: hidpp_battery_0 model:M705 serial: 101b-f2-7f-a2-d3 power supply: no updated: So 01 Apr 2018 11:43:56 CEST (106 seconds ago) has history: yes has statistics: yes mouse present: yes rechargeable:yes state: discharging warning-level: none percentage: 90% icon-name: 'battery-full-symbolic' History (charge): 1522575835 90,000 discharging 1522575835 0,000 unknown History (rate): 1522575835 0,000 unknown Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: So 01 Apr 2018 11:43:43 CEST (119 seconds ago) has history: no has statistics: no unknown warning-level: none icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.7 on-battery: no lid-is-closed: no lid-is-present: no critical-action: PowerOff -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 392585] New: under wayland spectacle with capture mode "active window" captures nothing
https://bugs.kde.org/show_bug.cgi?id=392585 Bug ID: 392585 Summary: under wayland spectacle with capture mode "active window" captures nothing Product: Spectacle Version: 17.12.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: mspe...@gmail.com Target Milestone: --- under wayland spectacle with capture mode "active window" captures nothing -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392584] New: systemsettings -> desktop behavior -> screen locking; crashes when changing color
https://bugs.kde.org/show_bug.cgi?id=392584 Bug ID: 392584 Summary: systemsettings -> desktop behavior -> screen locking; crashes when changing color Product: systemsettings Version: 5.12.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- in systemsettings -> desktop behavior -> screen locking -> appearance when clicked on color, systemsettings crashes (under wayland) -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 392579] wrongly reported energy information about battery
https://bugs.kde.org/show_bug.cgi?id=392579 Miroslav <mspe...@gmail.com> changed: What|Removed |Added Version|unspecified |5.12.4 Platform|Other |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 392579] New: wrongly reported energy information about battery
https://bugs.kde.org/show_bug.cgi?id=392579 Bug ID: 392579 Summary: wrongly reported energy information about battery Product: kinfocenter Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Energy Information Assignee: k...@privat.broulik.de Reporter: mspe...@gmail.com Target Milestone: --- Created attachment 111762 --> https://bugs.kde.org/attachment.cgi?id=111762=edit kinfocenter screenshot i'm using a desktop pc and energy information shows that i have a discharging battery and no power supply. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392578] New: cannot change primary monitor under wayland
https://bugs.kde.org/show_bug.cgi?id=392578 Bug ID: 392578 Summary: cannot change primary monitor under wayland Product: systemsettings Version: 5.12.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: --- i have two monitors, one standard dpi and one hidpi. by default, standard dpi monitor has been selected as primary. changing default monitor to other, hidpi one and clicking apply does nothing. every time, after apply, the monitor defaults to hdmi instead of keeping one connected to display port which is visible after changing to some other settings category and then coming back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392577] New: In dual screen setup, hidpi monitor has pixelated font and icon rendering
https://bugs.kde.org/show_bug.cgi?id=392577 Bug ID: 392577 Summary: In dual screen setup, hidpi monitor has pixelated font and icon rendering Product: plasmashell Version: 5.12.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: mspe...@gmail.com Target Milestone: 1.0 Created attachment 111761 --> https://bugs.kde.org/attachment.cgi?id=111761=edit plasma picture with bad font rendering in dual screen setup, where one monitor is hidpi and the other one is standard dpi, on hidpi monitor fonts and icons are rendered pixelated. please check attached picture taken with phone. only titlebar font is displayed ok, everything else is pixelated: - all fonts (check titlebar of kate and text written in kate for comparison) - text in konsole (with default font) - text in all menu bars (file, edit, etc.) - icons in dolphin settings, toolbar, etc. this issue is linked to Bug 390639 where only icon in titlebar was fixed, but fonts and other icons are still bad. tested on kubuntu 18.04 daily with latest updates applied. same situation existed in neon when i opened bug 390639 if font settings are important, anti-aliasing is set to "system settings" -- You are receiving this mail because: You are watching all bug changes.
