[okular] [Bug 434777] [Snap] Okular does not open in new tab but window
https://bugs.kde.org/show_bug.cgi?id=434777 Mateusz Stachowski changed: What|Removed |Added CC||mateusz.stachow...@wp.pl --- Comment #7 from Mateusz Stachowski --- I tested this in live session of KDE Neon and it worked. I installed the snap Okular, and then I opened it with snap run okular to make sure that I'm on the snap version. I enabled the Open in new tabs setting, and then in KDE System Settings switched the default handler for PDF files from the .deb version (24.02.0) to the snap version (23.08.4). snap info okular channels: latest/stable:23.08.4 2023-12-10 (148) 195MB - latest/candidate: 23.08.5 2024-02-16 (150) 196MB - latest/beta: ↑ latest/edge: ↑ Then I opened first PDF, then second one and third, and they opened in new tabs. I closed the Okular snap and again opened PDF's, by double clicking on them in Dolphin, and again they opened in new tabs of the snap packaged Okular. I also just tested it in my regular install of Ubuntu 24.04 development version and it works. I double click PDF files in Nautilus and they open in new tabs of snap Okular. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 463994] Okular fails to open HTTPS URLs to PDF files
https://bugs.kde.org/show_bug.cgi?id=463994 --- Comment #11 from Mateusz Stachowski --- I also checked that siwtching the default browser works. I had Okular snap open with two PDF files, and I opened unity-control-center under Information there is a default programs setting (WWW, Mail, Calendar, Music, Video). I changed WWW which is setting for default browser to Chromium. Then in Okular snap I clicked link which opened in Chromium. Then I switched back to Vivaldi as default and the link opened in this browser. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482500] Installing Okular from snap breaks home directory
https://bugs.kde.org/show_bug.cgi?id=482500 Mateusz Stachowski changed: What|Removed |Added CC||mateusz.stachow...@wp.pl --- Comment #2 from Mateusz Stachowski --- There is also a bug report on Launchpad. https://bugs.launchpad.net/ubuntu/+source/okular/+bug/2036597 And discussion on snapcrafters forum. https://forum.snapcraft.io/t/setting-home-in-snap-to-user-home-seems-to-cause-all-empty-user-dirs-to-become-broken-symlinks/39463/7 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443358] Okular does not open files in tabs
https://bugs.kde.org/show_bug.cgi?id=443358 Mateusz Stachowski changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #2 from Mateusz Stachowski --- *** This bug has been marked as a duplicate of bug 434777 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 434777] [Snap] Okular does not open in new tab but window
https://bugs.kde.org/show_bug.cgi?id=434777 Mateusz Stachowski changed: What|Removed |Added CC||medbenziane1...@gmail.com --- Comment #6 from Mateusz Stachowski --- *** Bug 443358 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443358] Okular does not open files in tabs
https://bugs.kde.org/show_bug.cgi?id=443358 Mateusz Stachowski changed: What|Removed |Added CC||mateusz.stachow...@wp.pl Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Mateusz Stachowski --- There is already bug opened about this issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 463994] Okular fails to open HTTPS URLs to PDF files
https://bugs.kde.org/show_bug.cgi?id=463994 Mateusz Stachowski changed: What|Removed |Added CC||mateusz.stachow...@wp.pl --- Comment #10 from Mateusz Stachowski --- I don't know if that bug was reported in relation to snap package of Okular, but it showed up when I searched for okular snap. I'm on Ubuntu 24.04 development release and using snapd from the edge channel. snap version snap2.62+git2055.gb131534 snapd 2.62+git2055.gb131534 series 16 ubuntu 24.04 kernel 6.8.4-x64v3-xanmod1 I checked the example file and all three links opened in my default browser Vivaldi. I also used a link from three PDF files on my system and those also worked. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 375331] Black screen after resuming from hibernation
https://bugs.kde.org/show_bug.cgi?id=375331 Mateusz changed: What|Removed |Added Resolution|LATER |FIXED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 375331] Black screen after resuming from hibernation
https://bugs.kde.org/show_bug.cgi?id=375331 Mateusz changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463229] New: KWin crash after screen switch off and waking up from sleep state
https://bugs.kde.org/show_bug.cgi?id=463229 Bug ID: 463229 Summary: KWin crash after screen switch off and waking up from sleep state Classification: Plasma Product: kwin Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: matkoz...@gmail.com Target Milestone: --- SUMMARY *** Right after returning from a screen switch off or waking up from sleep state all applications are closed and a new session is opened *** STEPS TO REPRODUCE 1. Wait selected amount of time until sleep switches off or enter sleep manually 2. Press keyboard button or mouse to wake up from sleep, in case of screen switch off just move mouse 3. See that all applications are closed and a new plasma session is started OBSERVED RESULT all applications are closed and a new plasma session is started EXPECTED RESULT Applications are brought back to the state they were left SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.26.4 (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: Qt Version: kvantum-qt5-git 1.0.7 ADDITIONAL INFORMATION Stacktrace from the moment I woke up PC from sleep: Dec 18 20:43:18 hypeitpc systemd[1]: Starting System Suspend... Dec 18 20:43:18 hypeitpc systemd-sleep[27120]: Entering sleep state 'suspend'... Dec 18 20:43:18 hypeitpc kernel: PM: suspend entry (deep) Dec 18 20:43:18 hypeitpc wpa_supplicant[597]: wlp9s0f3u1: CTRL-EVENT-DSCP-POLICY clear_all Dec 18 20:43:18 hypeitpc wpa_supplicant[597]: wlp9s0f3u1: CTRL-EVENT-DSCP-POLICY clear_all Dec 18 20:43:18 hypeitpc wpa_supplicant[597]: nl80211: deinit ifname=wlp9s0f3u1 disabled_11b_rates=0 Dec 18 21:28:43 hypeitpc kernel: Filesystems sync: 0.057 seconds Dec 18 21:28:43 hypeitpc kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. Dec 18 21:28:43 hypeitpc kernel: OOM killer disabled. Dec 18 21:28:43 hypeitpc kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. Dec 18 21:28:43 hypeitpc kernel: printk: Suspending console(s) (use no_console_suspend to debug) Dec 18 21:28:43 hypeitpc kernel: RTW: suspend start Dec 18 21:28:43 hypeitpc kernel: RTW: rtw_suspend_normal: ### ERROR driver in IPS ERROR###!!! Dec 18 21:28:43 hypeitpc kernel: serial 00:05: disabled Dec 18 21:28:43 hypeitpc kernel: RTW: rtw_dev_unload: driver in IPS-FWLPS Dec 18 21:28:43 hypeitpc kernel: RTW: rtw suspend success in 6 ms Dec 18 21:28:43 hypeitpc kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Dec 18 21:28:43 hypeitpc kernel: sd 0:0:0:0: [sda] Stopping disk Dec 18 21:28:43 hypeitpc kernel: [drm] free PSP TMR buffer Dec 18 21:28:43 hypeitpc kernel: amdgpu :07:00.0: amdgpu: MODE1 reset Dec 18 21:28:43 hypeitpc kernel: amdgpu :07:00.0: amdgpu: GPU mode1 reset Dec 18 21:28:43 hypeitpc kernel: amdgpu :07:00.0: amdgpu: GPU smu mode1 reset Dec 18 21:28:43 hypeitpc kernel: ACPI: PM: Preparing to enter system sleep state S3 Dec 18 21:28:43 hypeitpc kernel: ACPI: PM: Saving platform NVS memory Dec 18 21:28:43 hypeitpc kernel: Disabling non-boot CPUs ... Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 1 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 2 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 3 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 4 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 5 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 6 is now offline Dec 18 21:28:43 hypeitpc kernel: Spectre V2 : Update user space SMT mitigation: STIBP off Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 7 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 8 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 9 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 10 is now offline Dec 18 21:28:43 hypeitpc kernel: smpboot: CPU 11 is now offline Dec 18 21:28:43 hypeitpc kernel: ACPI: PM: Low-level resume complete Dec 18 21:28:43 hypeitpc kernel: ACPI: PM: Restoring platform NVS memory Dec 18 21:28:43 hypeitpc kernel: LVT offset 0 assigned for vector 0x400 Dec 18 21:28:43 hypeitpc kernel: Enabling non-boot CPUs ... Dec 18 21:28:43 hypeitpc kernel: x86: Booting SMP configuration: Dec 18 21:28:43 hypeitpc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 Dec 18 21:28:43 hypeitpc kernel: microcode: CPU1: patch_level=0x08701021 Dec 18 21:28:43 hypeitpc kernel: ACPI: \_SB_.PLTF.C002: Found 2 idle states Dec 18 21:28:43 hypeitpc kernel: CPU1 is up Dec 18 21:28:43 hypeitpc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4 Dec 18 21:28:43 hypeitpc kernel: microcode: CPU2: patch_level=0x08701021 Dec 18 21:28:43 hypeitpc kernel: ACPI: \_SB_.PLTF.C004: Found 2 idle states Dec 18 21:28:43 hypeitpc kernel: CPU2 is up Dec 18 21:28:43 hypeitpc kernel: smpboot: Booting
[plasmashell] [Bug 456599] On boot, icons positioned at the bottom move down one row, causing the desktop to become scrollable
https://bugs.kde.org/show_bug.cgi?id=456599 --- Comment #4 from Mateusz --- (In reply to Nate Graham from comment #3) > Aha, I see now. Your icons have moved down and made the desktop scrollable. > > Are you using the "right alignment" setting? If so it could be Bug 359783. I use left not right. it is set to the left at the default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456599] When task bar going up on boot it dissapear one right-down icon and create itself scroolbar
https://bugs.kde.org/show_bug.cgi?id=456599 --- Comment #2 from Mateusz --- (In reply to Nate Graham from comment #1) > Can you please attach a screenshot that shows the problem? https://drive.google.com/drive/folders/11gJ8lhd2vrw2RC0X1nXy2B3SfIFTl3bX Hi, there are 2 videos which show the problem and how it arises. Regards, Mateusz -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 456599] New: When task bar going up on boot it dissapear one right-down icon and create itself scroolbar
https://bugs.kde.org/show_bug.cgi?id=456599 Bug ID: 456599 Summary: When task bar going up on boot it dissapear one right-down icon and create itself scroolbar Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mateusz.rozmyslow...@protonmail.com Target Milestone: --- SUMMARY When task bar going up on boot it dissapear one right-down icon and create itself scroolbar STEPS TO REPRODUCE 1.Changing resolution manually/forcing it 2.Reinstalling whole system 3.Changing desktop icon size OBSERVED RESULT If i change icons to default value that is moderately small this issue gone but with others problem exist EXPECTED RESULT Remove this weird scroolbar from desktop its very annoying, i want use small icons but cant because of this SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux/KDE Plasma X11 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION My pc specs: cpu- amd ryzen 5 2600 gpu- nvidia gtx 1070 ti ram- g.skill aegis 2x16gb=32gb ddr4 3000mhz psu- corsair 650w motherboard- asrock B450 Fatal1ty Gaming ITX/AC ssd- samsung 980 pro 500gb hdd- one wd blue 1tb and two 230gb samsungs network card- intel dual band 3168 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449350] DrmGpu::findWorkingCombination failed to find any functional combinations
https://bugs.kde.org/show_bug.cgi?id=449350
--- Comment #5 from Mateusz Warzynski ---
(In reply to Zamundaaa from comment #2)
> As 5.23 is end of life and the relevant code received quite a bit of
> attention with 5.24, could you try the beta or git master with a live boot,
> to see if it's still happening?
TLDR, it works with KDE Plasma Version: 5.23.90. (It does not work with KDE
Plasma Version 5.23.5.)
---
Thanks for the suggestion.
Firstly, I've used the `neon-testing-20220201-1820.iso` as this is the most
recent iso I could find at https://neon.kde.org/download.
It worked fine on Wayland (and Xorg too). I found that KDE Plasma Version in
this ISO is 5.23.90. (To be honest, I thought it will be 5.24 or newer -- as
you suggested this version to check.)
The next step was to check the same version of KDE Plasma on my normal
day-to-day system.
This particular version is available for ArchLinux at `kde-unstable`
repository:
https://wiki.archlinux.org/title/Official_repositories#kde-unstable. I've added
this repository to pacman configuration and upgraded KDE (including Plasma):
> sudo pacman -S $(pacman -Sl kde-unstable | grep installed | awk '{print $2}')
double check:
> pacman -Ss plasma | grep kde-unstable | grep installed
> kde-unstable/plasma-desktop 5.23.90-1 (plasma) [installed]
So, at this point, I have the same Plasma version as I had with the KDE Testing
ISO.
I tested it a few times by disconnecting and connecting the dock or just the
external monitor (HDMI). It didn't crash.
I am satisfied with the current result. Should we mark this bug as resolved?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 449350] DrmGpu::findWorkingCombination failed to find any functional combinations
https://bugs.kde.org/show_bug.cgi?id=449350 --- Comment #3 from Mateusz Warzynski --- (In reply to Zamundaaa from comment #2) > As 5.23 is end of life and the relevant code received quite a bit of > attention with 5.24, could you try the beta or git master with a live boot, > to see if it's still happening? Of, I will check it out. Thanks for the reply! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449350] DrmGpu::findWorkingCombination failed to find any functional combinations
https://bugs.kde.org/show_bug.cgi?id=449350 --- Comment #1 from Mateusz Warzynski --- In addition, this crash might be caused by different parts of the code. I reproduced it once again and this time it crashed with ABRT. coredump info: >PID: 76934 (kwin_wayland) >UID: 1000 (mwarzynski) >GID: 1000 (mwarzynski) > Signal: 6 (ABRT) > Timestamp: Sun 2022-01-30 02:39:11 CET (31min ago) > Command Line: /usr/bin/kwin_wayland --wayland_fd 5 --socket wayland-0 > --xwayland-fd 7 --xwayland-fd 6 --xwayland-display :14 --xwayland-xauthority > /run/user/1000/xauth_aKwnFp --xwayland /usr/lib/startplasma-way> > Executable: /usr/bin/kwin_wayland > Control Group: /user.slice/user-1000.slice/session-1.scope > Unit: session-1.scope > Slice: user-1000.slice >Session: 1 > Owner UID: 1000 (mwarzynski) >Boot ID: 193f064636b3431cbcd6cdbdc1a17c74 > Machine ID: 4fa290243f6a492fa8fbd786b758cf66 > Hostname: mia >Storage: > /var/lib/systemd/coredump/core.kwin_wayland.1000.193f064636b3431cbcd6cdbdc1a17c74.76934.164350675100.zst > (present) > Disk Size: 4.4M >Message: Process 76934 (kwin_wayland) of user 1000 dumped core. > Stack trace of thread 76934: > #0 0x7fa1eb29cd22 raise (libc.so.6 + 0x3cd22) > #1 0x7fa1eb28690e abort (libc.so.6 + 0x2690e) > #2 0x7fa1eb2ded28 __libc_message (libc.so.6 + 0x7ed28) > #3 0x7fa1eb2e692a malloc_printerr (libc.so.6 + 0x8692a) > #4 0x7fa1eb2e9f4c _int_malloc (libc.so.6 + 0x89f4c) > #5 0x7fa1eb2eb4e1 malloc (libc.so.6 + 0x8b4e1) > #6 0x7fa1eb4d244d _Znwm (libstdc++.so.6 + 0xa644d) > #7 0x7fa1ec12f9db > _ZNK18QRasterPaintEngine11createStateEP13QPainterState (libQt5Gui.so.5 + > 0x3a39db) > #8 0x7fa1ec144cca _ZN8QPainter5beginEP12QPaintDevice > (libQt5Gui.so.5 + 0x3b8cca) > #9 0x7fa1e4a9892b _ZN4KWin9DrmOutput12updateCursorEv > (KWinWaylandDrmBackend.so + 0x2e92b) > #10 0x7fa1e4a89077 _ZN4KWin10DrmBackend12updateCursorEv > (KWinWaylandDrmBackend.so + 0x1f077) > #11 0x7fa1e4a8976c > _ZN4KWin10DrmBackend15handleUdevEventEv (KWinWaylandDrmBackend.so + 0x1f76c) > #12 0x7fa1ebb2ada3 n/a (libQt5Core.so.5 + 0x2bcda3) > #13 0x7fa1ebb2ca64 > _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE > (libQt5Core.so.5 + 0x2bea64) > #14 0x7fa1ebb2cbaf _ZN15QSocketNotifier5eventEP6QEvent > (libQt5Core.so.5 + 0x2bebaf) > #15 0x7fa1ec7161a6 > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 > + 0x1791a6) > #16 0x7fa1ebafa17a > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + > 0x28c17a) > #17 0x7fa1ebb440f4 > _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt5Core.so.5 > + 0x2d60f4) > #18 0x7fa1ebb45065 > _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE > (libQt5Core.so.5 + 0x2d7065) > #19 0x5620fd55aa42 > _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE > (kwin_wayland + 0x8ea42) > #20 0x7fa1ebaf245b > _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + > 0x28445b) > #21 0x7fa1ebafdba7 _ZN16QCoreApplication4execEv > (libQt5Core.so.5 + 0x28fba7) > #22 0x5620fd4f68cb main (kwin_wayland + 0x2a8cb) > #23 0x7fa1eb287b25 __libc_start_main (libc.so.6 + 0x27b25) > #24 0x5620fd4f72ce _start (kwin_wayland + 0x2b2ce) backtrace: > (gdb) bt > #0 0x7fa1eb29cd22 in raise () at /usr/lib/libc.so.6 > #1 0x7fa1eb28690e in abort () at /usr/lib/libc.so.6 > #2 0x7fa1eb2ded28 in __libc_message () at /usr/lib/libc.so.6 > #3 0x7fa1eb2e692a in () at /usr/lib/libc.so.6 > #4 0x7fa1eb2e9f4c in _int_malloc () at /usr/lib/libc.so.6 > #5 0x7fa1eb2eb4e1 in malloc () at /usr/lib/libc.so.6 > #6 0x7fa1eb4d244d in operator new(unsigned long) (sz=1040) at > /build/gcc/src/gcc/libstdc++-v3/libsupc++/new_op.cc:50 > #7 0x7fa1ec12f9db in QRasterPaintEngine::createState(QPainterState*) > const () at /usr/lib/libQt5Gui.so.5 > #8 0x7fa1ec144cca in QPainter::begin(QPaintDevice*) () at > /usr/lib/libQt5Gui.so.5 > #9 0x7fa1e4a9892b in KWin::DrmOutput::updateCursor() > (this=0x5620ff0c95e0) at >
[kwin] [Bug 449350] New: DrmGpu::findWorkingCombination failed to find any functional combinations
https://bugs.kde.org/show_bug.cgi?id=449350 Bug ID: 449350 Summary: DrmGpu::findWorkingCombination failed to find any functional combinations Product: kwin Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: mathew.warzyn...@gmail.com Target Milestone: --- Created attachment 146060 --> https://bugs.kde.org/attachment.cgi?id=146060=edit debug log output Possibly related to https://bugs.kde.org/show_bug.cgi?id=438789. However, fix proposed in the comments were pushed to 5.22 and I observe a similar issue at 5.23. SUMMARY While having KDE running, when I connect an external monitor to the dock the `kwin_wayland` crashes. It works fine if I start KDE with the external monitor already connected. `kwin_wayland_drm` seems to be unable to find a functional combination after a new external monitor via dock is connected. STEPS TO REPRODUCE 1. Disconnect external monitor (or dock), 2. Start KDE with Wayland (`XDG_SESSION_TYPE=wayland dbus-run-session startplasma-wayland`), 3. Connect external monitor (or dock), 4. -- crash -- OBSERVED RESULT KDE exits to tty, loads up again (from scratch) with external monitor working fine. Since the whole KDE exits it also closes all working GUI applications (like web browser), so that I have to open all of them once again. EXPECTED RESULT KDE should not crash. KDE should use the new monitor. SOFTWARE/OS VERSIONS OS: ArchLinux ``` ~ uname -a Linux mia 5.16.3-arch1-1 #1 SMP PREEMPT Thu, 27 Jan 2022 14:18:25 + x86_64 GNU/Linux ``` KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Graphics Platform: Wayland ADDITIONAL INFORMATION Interesting logs from "debug log output": ``` kwin_wayland_drm: DrmGpu::findWorkingCombination failed to find any functional combinations! Reverting to the old configuration! kwin_wayland_drm: Could not set cursor: Bad file descriptor kwin_wayland_drm: Could not set cursor: Bad file descriptor kwin_wayland_drm: Could not set cursor: Bad file descriptor kwin_wayland_drm: Failed to update cursor on output "eDP-1" kwin_wayland_drm: Could not set cursor: Bad file descriptor kwin_wayland_drm: New gpu found: "" kwin_wayland_drm: failed to open drm device at "" kwin_wayland_drm: Received change event for monitored drm device "/dev/dri/card0" The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? kdeinit5: PID 76335 terminated. (EE) failed to read Wayland events: Broken pipe kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__13) failed: : No such file or directory Error: Can not contact kdeinit5! startplasma-waylandsession: Starting up...startplasma-waylandsession: Shutting down... startplasma-waylandsession: Done. ``` (I pasted full log as an attachment as context might be helpful.) Crash backtrace: ``` (gdb) bt #0 0x7f57303271ea in QVector::clear() (this=) at /usr/include/qt/QtCore/qvector.h:442 #1 KWin::DrmConnector::updateModes() (this=0x18) at /usr/src/debug/kwin-5.23.5/src/plugins/platforms/drm/drm_object_connector.cpp:319 #2 0x7f573032f28c in KWin::DrmOutput::updateModes() (this=this@entry=0x5624de19cc40) at /usr/src/debug/kwin-5.23.5/src/plugins/platforms/drm/drm_output.cpp:331 #3 0x7f5730337f3d in KWin::DrmGpu::updateOutputs() (this=this@entry=0x5624dd95cac0) at /usr/src/debug/kwin-5.23.5/src/plugins/platforms/drm/drm_gpu.cpp:222 #4 0x7f573031f101 in KWin::DrmBackend::updateOutputs() (this=0x5624dd93d6d0) at /usr/src/debug/kwin-5.23.5/src/plugins/platforms/drm/drm_backend.cpp:356 #5 0x7f5730320763 in KWin::DrmBackend::handleUdevEvent() (this=0x5624dd93d6d0) at /usr/src/debug/kwin-5.23.5/src/plugins/platforms/drm/drm_backend.cpp:259 #6 0x7f57373c1da3 in () at /usr/lib/libQt5Core.so.5 #7 0x7f57373c3a64 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #8 0x7f57373c3baf in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7f5737fad1a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f573739117a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #11 0x7f57373db0f4 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/libQt5Core.so.5 #12 0x7f57373dc065 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #13 0x5624dcc58a42 in QUnixEventDispatcherQPA::processEvents(QFlags) () #14 0x7f573738945b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #15 0x7f5737394ba7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #16 0x5624dcbf48cb in main(int, char**)
[kamoso] [Bug 448829] New: Kamoso crashes at startup while zoom is running and using camera
https://bugs.kde.org/show_bug.cgi?id=448829 Bug ID: 448829 Summary: Kamoso crashes at startup while zoom is running and using camera Product: kamoso Version: 21.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: mateusz.ti...@gmail.com Target Milestone: --- SUMMARY *** NOTE : It is my first bug report ever, i'm trying to do it well. *** STEPS TO REPRODUCE 1. Start zoom meeting 2. Use camera. 3. Start kamoso. 4. Kamoso crashes. OBSERVED RESULT kamoso crashed EXPECTED RESULT kamoso runs. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch 5.16.1 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 X11 ADDITIONAL INFORMATION : krash log Application: kamoso (21.12.1) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.16.1-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Kamoso (kamoso), signal: Segmentation fault [KCrash Handler] #4 0x7fb82087e222 in QSGBatchRenderer::Renderer::prepareOpaqueBatches() () at /usr/lib/libQt5Quick.so.5 #5 0x7fb820887eea in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #6 0x7fb8208745e5 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #7 0x7fb820874aa4 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #8 0x7fb8208ceb55 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #9 0x7fb82092b2b1 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #10 0x7fb8208da721 in () at /usr/lib/libQt5Quick.so.5 #11 0x7fb8208df010 in () at /usr/lib/libQt5Quick.so.5 #12 0x7fb81ec0688c in () at /usr/lib/libQt5Core.so.5 #13 0x7fb81d99a259 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7fb81e5405e3 in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7fb799ffb640 (LWP 176270) "kamoso:gdrv0"): #1 0x7fb81d9a0270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7fb80a50edac in () at /usr/lib/dri/iris_dri.so #3 0x7fb80a507a5c in () at /usr/lib/dri/iris_dri.so #4 0x7fb81d99a259 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fb81e5405e3 in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7fb79a7fc640 (LWP 176267) "preview-appsrc:"): #1 0x7fb81e8e5af5 in g_cond_wait () at /usr/lib/libglib-2.0.so.0 #2 0x7fb7dc090488 in () at /usr/lib/libgstapp-1.0.so.0 #3 0x7fb80805dc4e in () at /usr/lib/libgstbase-1.0.so.0 #4 0x7fb8080608df in () at /usr/lib/libgstbase-1.0.so.0 #5 0x7fb81ea8cbe1 in () at /usr/lib/libgstreamer-1.0.so.0 #6 0x7fb81e8c88d7 in () at /usr/lib/libglib-2.0.so.0 #7 0x7fb81e8c5905 in () at /usr/lib/libglib-2.0.so.0 #8 0x7fb81d99a259 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fb81e5405e3 in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7fb79affd640 (LWP 176266) "Integrated_Webc"): #1 0x7fb81e8e5af5 in g_cond_wait () at /usr/lib/libglib-2.0.so.0 #2 0x7fb81ea8cddc in () at /usr/lib/libgstreamer-1.0.so.0 #3 0x7fb81e8c88d7 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb81e8c5905 in () at /usr/lib/libglib-2.0.so.0 #5 0x7fb81d99a259 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fb81e5405e3 in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7fb79b7fe640 (LWP 176265) "viewfinderbin-q"): #1 0x7fb81e8e5af5 in g_cond_wait () at /usr/lib/libglib-2.0.so.0 #2 0x7fb8080597d4 in gst_base_sink_wait_preroll () at /usr/lib/libgstbase-1.0.so.0 #3 0x7fb808059d41 in gst_base_sink_do_preroll () at /usr/lib/libgstbase-1.0.so.0 #4 0x7fb80807e423 in () at /usr/lib/libgstbase-1.0.so.0 #5 0x7fb80804efe8 in () at /usr/lib/libgstbase-1.0.so.0 #6 0x7fb808052f2c in () at /usr/lib/libgstbase-1.0.so.0 #7 0x7fb80804e872 in () at /usr/lib/libgstbase-1.0.so.0 #8 0x7fb81ea635dd in () at /usr/lib/libgstreamer-1.0.so.0 #9 0x7fb81ea63c7e in () at /usr/lib/libgstreamer-1.0.so.0 #10 0x7fb81ea64155 in () at /usr/lib/libgstreamer-1.0.so.0 #11 0x7fb81ea59f71 in () at /usr/lib/libgstreamer-1.0.so.0 #12 0x7fb81ea6732b in gst_pad_push_event () at /usr/lib/libgstreamer-1.0.so.0 #13 0x7fb81ea635dd in () at /usr/lib/libgstreamer-1.0.so.0 #14 0x7fb81ea63c7e in () at /usr/lib/libgstreamer-1.0.so.0 #15 0x7fb81ea64155 in () at /usr/lib/libgstreamer-1.0.so.0 #16 0x7fb81ea59f71 in () at /usr/lib/libgstreamer-1.0.so.0 #17 0x7fb81ea6732b in gst_pad_push_event () at /usr/lib/libgstreamer-1.0.so.0 #18 0x7fb81ea635dd in () at
[systemsettings] [Bug 427919] New: system settings crash when I try to remove a cursor icon theme
https://bugs.kde.org/show_bug.cgi?id=427919 Bug ID: 427919 Summary: system settings crash when I try to remove a cursor icon theme Product: systemsettings Version: 5.20.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mateusz.wa...@protonmail.com Target Milestone: --- Application: systemsettings5 (5.20.0) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.8.14-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: as in the title, I was trying to remove a cursor icon theme. Every single time I try to do that system settings crash : ( The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 6366] [New LWP 6367] [New LWP 6391] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fd17fc8de7f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fd17d3ba840 (LWP 6364))] Thread 4 (Thread 0x7fd15b9ea640 (LWP 6391)): #0 0x7fd17deceea9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fd17de814f0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd17de8170f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd18024e5cb in QEventDispatcherGlib::processEvents (this=0x7fd154000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fd1801f5a1b in QEventLoop::exec (this=this@entry=0x7fd15b9e9ca0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fd1800167ce in QThread::exec (this=this@entry=0x7fd174005f00) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fd17f2c52d5 in QQmlThreadPrivate::run (this=0x7fd174005f00) at /usr/src/debug/libqt5-qtdeclarative-5.15.1-2.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:155 #7 0x7fd180017911 in QThreadPrivate::start (arg=0x7fd174005f00) at thread/qthread_unix.cpp:329 #8 0x7fd17e847eb1 in start_thread () from /lib64/libpthread.so.0 #9 0x7fd17fc98ccf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fd17a431640 (LWP 6367)): #0 0x7fd17fc8de7f in poll () from /lib64/libc.so.6 #1 0x7fd17de815ee in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd17de8170f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd18024e5cb in QEventDispatcherGlib::processEvents (this=0x7fd16c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fd1801f5a1b in QEventLoop::exec (this=this@entry=0x7fd17a430c70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fd1800167ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fd17ef44a27 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fd180017911 in QThreadPrivate::start (arg=0x7fd17efb1d80) at thread/qthread_unix.cpp:329 #8 0x7fd17e847eb1 in start_thread () from /lib64/libpthread.so.0 #9 0x7fd17fc98ccf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fd17b2dd640 (LWP 6366)): #0 0x7fd17fc8de7f in poll () from /lib64/libc.so.6 #1 0x7fd17e88d862 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fd17e88f26c in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fd17b4e0270 in QXcbEventQueue::run (this=0x5646768a6780) at qxcbeventqueue.cpp:228 #4 0x7fd180017911 in QThreadPrivate::start (arg=0x5646768a6780) at thread/qthread_unix.cpp:329 #5 0x7fd17e847eb1 in start_thread () from /lib64/libpthread.so.0 #6 0x7fd17fc98ccf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fd17d3ba840 (LWP 6364)): [KCrash Handler] #4 QString::QString (other=..., this=0x7ffedcea14f8) at /usr/include/qt5/QtCore/qstring.h:1088 #5 CursorTheme::name (this=0x0) at /usr/src/debug/plasma5-workspace-5.20.0-2.1.x86_64/kcms/cursortheme/xcursor/cursortheme.h:65 #6 operator() (roles=..., end=..., start=..., __closure=0x564676bdd380) at /usr/src/debug/plasma5-workspace-5.20.0-2.1.x86_64/kcms/cursortheme/kcmcursortheme.cpp:103 #7 QtPrivate::FunctorCall, QtPrivate::List&>, void, CursorThemeConfig::CursorThemeConfig(QObject*, const QVariantList&)::&)> >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #8 QtPrivate::Functor&)>, 3>::call const&>, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #9 QtPrivate::QFunctorSlotObject&)>, 3, QtPrivate::List&>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x564676bdd370, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #10 0x7fd18022d646 in
[systemsettings] [Bug 427915] New: system settings sometimes / almost always crash when I install new themes (global themes/icons etc)
https://bugs.kde.org/show_bug.cgi?id=427915 Bug ID: 427915 Summary: system settings sometimes / almost always crash when I install new themes (global themes/icons etc) Product: systemsettings Version: 5.20.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mateusz.wa...@protonmail.com Target Milestone: --- Application: systemsettings5 (5.20.0) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.8.14-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was just installing new Global Themes. I think it's say to say most of the time I get a crash (after providing root password for the popup that updates SDDM). Nothing else to say here, really, just scrolling down the list of themes and installing the ones I like. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 4555] [New LWP 4568] [New LWP 4827] [New LWP 4828] [New LWP 4829] [New LWP 4837] [New LWP 4838] [New LWP 4839] [New LWP 4840] [New LWP 4847] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fa6609e3e7f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fa65e110840 (LWP 4552))] Thread 11 (Thread 0x7fa6213fa640 (LWP 4847)): #0 0x7fa65ebd37fd in () at /usr/lib64/libglib-2.0.so.0 #1 0x7fa65ebd5515 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa65ebd6a33 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa65ebd751b in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa65ebd770f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fa660fa45cb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa604000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fa660f4ba1b in QEventLoop::exec(QFlags) (this=this@entry=0x7fa6213f9c80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7fa660d6c7ce in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7fa6602ce926 in () at /usr/lib64/libQt5Quick.so.5 #9 0x7fa660d6d911 in QThreadPrivate::start(void*) (arg=0x55bc328cdd30) at thread/qthread_unix.cpp:329 #10 0x7fa65f59deb1 in start_thread () at /lib64/libpthread.so.0 #11 0x7fa6609eeccf in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fa621bfb640 (LWP 4840)): #0 0x7fa65ec24ec4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fa65ebd75e3 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa65ebd770f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa660fa45cb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa61b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa660f4ba1b in QEventLoop::exec(QFlags) (this=this@entry=0x7fa621bfacc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7fa660d6c7ce in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7fa660d6d911 in QThreadPrivate::start(void*) (arg=0x55bc33274ae0) at thread/qthread_unix.cpp:329 #7 0x7fa65f59deb1 in start_thread () at /lib64/libpthread.so.0 #8 0x7fa6609eeccf in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fa6223fc640 (LWP 4839)): #0 0x7fa6609df8dc in read () at /lib64/libc.so.6 #1 0x7fa65ec2018f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa65ebd713e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa65ebd7595 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa65ebd794b in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #5 0x7fa650e287a6 in () at /usr/lib64/libgio-2.0.so.0 #6 0x7fa65ec009fe in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fa65f59deb1 in start_thread () at /lib64/libpthread.so.0 #8 0x7fa6609eeccf in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fa622bfd640 (LWP 4838)): #0 0x7fa6609df8dc in read () at /lib64/libc.so.6 #1 0x7fa65ec2018f in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fa65ebd713e in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fa65ebd7595 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fa65ebd770f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fa65ebd7761 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7fa65ec009fe in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fa65f59deb1 in start_thread () at /lib64/libpthread.so.0 #8 0x7fa6609eeccf in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fa6237fe640 (LWP 4837)): #0 0x7fa6609e3e7f in poll
[yakuake] [Bug 319172] Ambigous shortcut detected with pressing Ctrl+Shift+w
https://bugs.kde.org/show_bug.cgi?id=319172 Mateusz Mikuła changed: What|Removed |Added CC||mati...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 214547] Kosole KPart needs an API to retrieve $PWD
https://bugs.kde.org/show_bug.cgi?id=214547 Mateusz Mikuła changed: What|Removed |Added CC||mati...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404356] Terminator (terminal) application opens on all virtual desktops.
https://bugs.kde.org/show_bug.cgi?id=404356 Mateusz Warzynski changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Mateusz Warzynski --- (In reply to Vlad Zagorodniy from comment #1) > Most likely Terminator requests to change virtual desktop. Go to Preferences > and uncheck "Show on all workspaces". Thank you, it works. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404356] Terminator (terminal) application opens on all virtual desktops.
https://bugs.kde.org/show_bug.cgi?id=404356 Mateusz Warzynski changed: What|Removed |Added Summary|Terminator (terminal) |Terminator (terminal) |application opens on all|application opens on all |desktops. |virtual desktops. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404356] New: Terminator (terminal) application opens on all desktops.
https://bugs.kde.org/show_bug.cgi?id=404356 Bug ID: 404356 Summary: Terminator (terminal) application opens on all desktops. Product: kwin Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: mathew.warzyn...@gmail.com Target Milestone: --- Created attachment 118076 --> https://bugs.kde.org/attachment.cgi?id=118076=edit Virtual desktops preview after terminator launch. SUMMARY I use terminator as my default terminal application. As to have always initial settings applied I set a window rule specifically for this application. Unfortunately, spawning a terminal application results with 'All desktops' setting set. It's annoying, because I must change it back manually to just the current virtual desktop every time I open the terminal. Window rule that I use: [Application settings for terminator] Description=Application settings for terminator clientmachine=mymachine clientmachinematch=0 maximizehoriz=true maximizehorizrule=3 maximizevert=true maximizevertrule=3 wmclass=terminator wmclasscomplete=false wmclassmatch=1 I also checked if there is any other rule that would interfere with this one. There isn't. STEPS TO REPRODUCE 1. Open 'terminator'. Uhm, I do know this step is insufficient description. It's just I don't have any better idea how to describe it. Is there anything I may look into to provide you more information/debug this? OBSERVED RESULT Terminator opens on all virtual desktops. EXPECTED RESULT Terminator opens on current virtual desktop. SOFTWARE/OS VERSIONS Linux: Arch Linux 4.20.8-arch1-1-ARCH KDE Plasma Version: 5.15.0-1 KDE Frameworks Version: 5.55.0 Qt Version: Qt 5.12.1 (built against 5.12.1) I use Xorg. ADDITIONAL INFORMATION Most probably the last KDE (kwin?) upgrade on Arch Linux introduced this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Mateusz Mikuła changed: What|Removed |Added CC||mati...@gmail.com --- Comment #1 from Mateusz Mikuła --- Nokia 7 Plus, stock Android 9, default Messages app (by Google) with updates installed. Relevant part of logcat: https://hastebin.com/rigevixipa.cs -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the show message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 Mateusz Kowalewski changed: What|Removed |Added CC||mateusz.f.kowalewski@gmail. ||com --- Comment #25 from Mateusz Kowalewski --- (In reply to Laurent Montel from comment #9) > (In reply to Kamil Dudka from comment #8) > > Laurent, could you please stop removing or hiding kmail's features which you > > think are not useful or important? > > > > Those features were originally implemented for a reason and kmail's users > > have been successfully using them for quite some time. If you keep the > > current pace of downgrading user experience with each subsequent release of > > kmail, you are going loose existing users of kmail for no real benefit. > > > > You should really focus on fixing existing bugs instead of removing existing > > stable features that nobody complains about. > > Just a question: > Are you the kmail maintainer ? > no I don't think. > I am. > > So if I think that it's better to reduce menu or hide not useful feature for > enduser it's my choice. > > You work on redhat so make your work as packager and stop to cry. > > Thanks. Dear maintainer, There is another problem with your "choice" here: The documentation did not reflect this change! That's an absolute no go! I'm currently looking for some other bug in Kmail/Akonadi and reading the mailing-list archives. I discovered this bug report by chance now. Some time ago I (as an end-user) needed to look up the message structure of one mail. I was very upset as I saw the menu entry I knew was there for years was gone. I tired to "google" for this issue but did not find this bug report then. I also did not find any information about a removal of this feature. The documentation says it is still in the menu! I thought it is a very strange bug. I even started to look for the relevant code in Kmail (but did not push this endeavor any further than out of lack of time). In the end I exported the raw mail an used some tools on it to extract the part of the mail I was interested in. Looking into this issue and coming up with a workaround was a waste of several hours! "Hiding" or removing features "for power users" is a think I would expect form the Gnome people. But never ever from a KDE app! Please don't do something like that again! There are some usability standards under KDE now for years: Everything you can find in the GUI is also available as a toolbar. But not the other way around! Till said: "'toolbar' \subseteq 'menu' is a typical pattern". I think it's not only a "typical pattern" it's how things work all over KDE apps since most likely pre V1.0 versions. (Maybe I don't recall correctly the version but it works like that since "ever")! It's not anything you could make a "choice" about. You just wasted the time of several people by making a "choice" like that. But there was no gain whatsoever in doing so! KDE isn't for people who like "hidden" or striped down features. Thank you for being now aware that with "choices" like that you will annoy a lot of long time KDE users. Best regards, Mateusz -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398452] New: Kate crashes while selecing 64tass syntax.
https://bugs.kde.org/show_bug.cgi?id=398452 Bug ID: 398452 Summary: Kate crashes while selecing 64tass syntax. Product: kate Version: 18.08.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: mats...@interia.pl Target Milestone: --- Created attachment 114873 --> https://bugs.kde.org/attachment.cgi?id=114873=edit 64tass syntax Kate crashes while selecing 64tass syntax. ArchLinux updated to 2018.09.09. KDEPlasma version: 5.13.5-1 Architecture: pc x86-64. Kate version: 18.08.1. The unfortunatelly syntax is in attachment. Console output: org.kde.ksyntaxhighlighting: Context: Unknown format "Normal Text" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Keyword" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Keyword" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Data Type" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Preprocessor" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Comment" in context "Base" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Context: Unknown format "Normal Text" in context "Opcode2" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Keyword" in context "Opcode2" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule: Unknown format "Keyword" in context "Opcode2" of definition "6502 assembly (64tass)" org.kde.ksyntaxhighlighting: Rule:
[amarok] [Bug 398451] New: Amarok crashes at end of the music file while playing
https://bugs.kde.org/show_bug.cgi?id=398451 Bug ID: 398451 Summary: Amarok crashes at end of the music file while playing Product: amarok Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: mats...@interia.pl Target Milestone: kf5 Created attachment 114871 --> https://bugs.kde.org/attachment.cgi?id=114871=edit Debug output and stack trace. Amarok crashes at end of the music file while playing As in title. Amarok unexpectedly crashes at end of music file while playing. Before crash, slider to choose position unable to set position in last few seconds in music, and after playing Amarok just crashes. But, very likely it is dynamic library incompatibility problem. I am using: Arch Linux updated to 2018.09.02. KDE Plasma: 5.13.4-1 Architecture: pc x86-64 Amarok: 2.9.0 Debug output and stack trace is in attachment. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396473] Can't enable blur or configure translucency
https://bugs.kde.org/show_bug.cgi?id=396473 Mateusz Mikuła changed: What|Removed |Added CC||mati...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397589] Crash while first starting Kmail
https://bugs.kde.org/show_bug.cgi?id=397589 --- Comment #2 from Mateusz Szpakowski --- First message in console while starting: - Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) - After second (or two) kmail prints these messages (likely after/while akonadi startup): --- akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontableOK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelationOK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) "No file selected." org.kde.pim.akonadicontrol: Reference to unknown agent type "akonadi_notes_agent" in agentsrc QDBusConnection: name 'org.freedesktop.Akonadi.Control' had owner '' but we thought it was ':1.46' QDBusConnection: name 'org.freedesktop.Akonadi.Control' had owner '' but we thought it was ':1.46' org.kde.pim.maildispatcher: Item 28483 has invalid transport. org.kde.pim.maildispatcher: Item 28339 has invalid transport. org.kde.pim.maildispatcher: Item 28338 has invalid transport. org.kde.pim.maildispatcher: Item 28333 has invalid transport. org.kde.pim.maildispatcher: Item 28332 has invalid transport. org.kde.pim.maildispatcher: Item 28331 has invalid transport. org.kde.pim.maildispatcher: Item 28326 has invalid transport. org.kde.pim.maildispatcher: Item 28152 has invalid transport. org.kde.pim.maildispatcher: Item 28151 has invalid transport. org.kde.pim.maildispatcher: Item 4827 has invalid transport. org.kde.pim.maildispatcher: Item 335 has invalid transport. org.kde.pim.maildispatcher: Item 334 has invalid transport. QDBusConnection: name 'org.freedesktop.Akonadi.Control' had owner '' but we thought it was ':1.46' org.kde.pim.akonadiserver: Received ModifySubscription command before RegisterSubscriber org.kde.pim.akonadicore: "QLocalSocket: Remote closed" "/tmp/akonadi-mat.hhTBw6/akonadiserver-ntf.socket" Error loading text-to-speech plug-in "speechd" QDBusConnection: name 'org.freedesktop.Akonadi.Control' had owner '' but we thought it was ':1.46' - -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397589] Crash while first starting Kmail
https://bugs.kde.org/show_bug.cgi?id=397589 Mateusz Szpakowski changed: What|Removed |Added Version|unspecified |5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 397589] New: Crash while first starting Kmail
https://bugs.kde.org/show_bug.cgi?id=397589 Bug ID: 397589 Summary: Crash while first starting Kmail Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mats...@interia.pl Target Milestone: --- Application: KMail2 KDE Plaform version: 5.13.4-1 (plasma version) Akonadi version: 5.8.3 KMail version: 5.8.3 Operating system: Arch Linux updated to 2018.08.12, kernel 4.17.11 mariadb version: 10.1.35-1 ---Information about crash--- Application: akonadi_control (akonadi_control), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7d9646fc80 (LWP 6997))] Thread 2 (Thread 0x7f7d92f54700 (LWP 7001)): #0 0x7f7d9c96e991 in poll () from /usr/lib/libc.so.6 #1 0x7f7d99e28180 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f7d99e29e4b in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f7d95d03e1a in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f7d9ccaf005 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f7d9c864a8d in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f7d9c979823 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f7d9646fc80 (LWP 6997)): [KCrash Handler] #6 0x7f7d9c8b5b5f in raise () from /usr/lib/libc.so.6 #7 0x7f7d9c8a0452 in abort () from /usr/lib/libc.so.6 #8 0x7f7d9cc6b7fc in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #9 0x5640ac5ac0cf in ?? () #10 0x5640ac5cf7f5 in ?? () #11 0x5640ac5ac16d in ?? () #12 0x7f7d9c8a2003 in __libc_start_main () from /usr/lib/libc.so.6 #13 0x5640ac5ac89a in _start () --- end info--- -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396330] New: KDevelop crash at startup
https://bugs.kde.org/show_bug.cgi?id=396330 Bug ID: 396330 Summary: KDevelop crash at startup Product: kdevelop Version: 5.2.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mats...@interia.pl Target Milestone: --- Application: kdevelop (5.2.3) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.15.18older-1-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: I just run KDevelop and it was loading and analyzing sources of my project. I was doing nothing at this time. - Environment: I am using OpenSUSE Tumbleweed from 2018.07. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f154d2f39c0 (LWP 4566))] Thread 29 (Thread 0x7f14a57fa700 (LWP 4786)): #0 0x7f14f2ba9240 in clang::DeclarationName::getCXXOverloadedOperator() const () at /usr/lib64/../lib64/libclangAST.so.6 #1 0x7f14f21bdca2 in clang::Sema::ActOnFunctionDeclarator(clang::Scope*, clang::Declarator&, clang::DeclContext*, clang::TypeSourceInfo*, clang::LookupResult&, llvm::MutableArrayRef, bool&) () at /usr/lib64/../lib64/libclangSema.so.6 #2 0x7f14f21ba146 in clang::Sema::HandleDeclarator(clang::Scope*, clang::Declarator&, llvm::MutableArrayRef) () at /usr/lib64/../lib64/libclangSema.so.6 #3 0x7f14f228666f in clang::Sema::ActOnCXXMemberDeclarator(clang::Scope*, clang::AccessSpecifier, clang::Declarator&, llvm::MutableArrayRef, clang::Expr*, clang::VirtSpecifiers const&, clang::InClassInitStyle) () at /usr/lib64/../lib64/libclangSema.so.6 #4 0x7f14f1c19707 in clang::Parser::ParseCXXClassMemberDeclaration(clang::AccessSpecifier, clang::AttributeList*, clang::Parser::ParsedTemplateInfo const&, clang::ParsingDeclRAIIObject*) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #5 0x7f14f1c1b1ca in clang::Parser::ParseCXXClassMemberDeclarationWithPragmas(clang::AccessSpecifier&, clang::Parser::ParsedAttributesWithRange&, clang::TypeSpecifierType, clang::Decl*) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #6 0x7f14f1c15fd5 in clang::Parser::ParseCXXMemberSpecification(clang::SourceLocation, clang::SourceLocation, clang::Parser::ParsedAttributesWithRange&, unsigned int, clang::Decl*) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #7 0x7f14f1c146a6 in clang::Parser::ParseClassSpecifier(clang::tok::TokenKind, clang::SourceLocation, clang::DeclSpec&, clang::Parser::ParsedTemplateInfo const&, clang::AccessSpecifier, bool, clang::Parser::DeclSpecContext, clang::Parser::ParsedAttributesWithRange&) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #8 0x7f14f1bf83b8 in clang::Parser::ParseDeclarationSpecifiers(clang::DeclSpec&, clang::Parser::ParsedTemplateInfo const&, clang::AccessSpecifier, clang::Parser::DeclSpecContext, clang::Parser::LateParsedAttrList*) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #9 0x7f14f1c7c7bd in clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec&, clang::AccessSpecifier) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #10 0x7f14f1c7c49a in clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*, clang::AccessSpecifier) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #11 0x7f14f1c7b876 in clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #12 0x7f14f1c0e51b in clang::Parser::ParseInnerNamespace(std::vector >&, std::vector >&, std::vector >&, unsigned int, clang::SourceLocation&, clang::ParsedAttributes&, clang::BalancedDelimiterTracker&) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #13 0x7f14f1c0e07f in clang::Parser::ParseNamespace(clang::DeclaratorContext, clang::SourceLocation&, clang::SourceLocation) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #14 0x7f14f1bf7ab1 in clang::Parser::ParseDeclaration(clang::DeclaratorContext, clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #15 0x7f14f1c7ae0c in clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&, clang::ParsingDeclSpec*) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #16 0x7f14f1c7a735 in clang::Parser::ParseTopLevelDecl(clang::OpaquePtr&) () at /usr/lib64/../lib64/../lib64/libclangParse.so.6 #17 0x7f14f1bea4a6 in clang::ParseAST(clang::Sema&, bool, bool) () at
[kwin] [Bug 392273] New: Nvidia, alt-tab crashed kwin
https://bugs.kde.org/show_bug.cgi?id=392273 Bug ID: 392273 Summary: Nvidia, alt-tab crashed kwin Product: kwin Version: 5.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mati...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.3) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.15.12-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Alt-tabbed between PyCharm and Firefox. - Unusual behavior I noticed: Alt-tab preview froze for a second or two and then crash occured. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1116337840 (LWP 9729))] Thread 7 (Thread 0x7f10f31d1700 (LWP 29811)): #0 0x7f110eccd3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1112e6d02c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f110de8c49a in () at /usr/lib/libQt5Quick.so.5 #3 0x7f110de8c924 in () at /usr/lib/libQt5Quick.so.5 #4 0x7f1112e6bb4d in () at /usr/lib/libQt5Core.so.5 #5 0x7f110ecc708c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1115cdce7f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f10dd9ec700 (LWP 10181)): #0 0x7f1115cd2a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f11130b0e73 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f11130b260f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f11130573db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1112e667ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f110d790379 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f1112e6bb4d in () at /usr/lib/libQt5Core.so.5 #7 0x7f110ecc708c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1115cdce7f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f10dd1e3700 (LWP 9914)): #0 0x7f110eccd3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff84f77 in () at /usr/lib/libQt5Script.so.5 #2 0x7ff84fb9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f110ecc708c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f1115cdce7f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f10f2513700 (LWP 9887)): #0 0x7f1115cd2a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f11130b0e73 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f11130b260f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f11130573db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1112e667ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f110d790379 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f1112e6bb4d in () at /usr/lib/libQt5Core.so.5 #7 0x7f110ecc708c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1115cdce7f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f10f8de9700 (LWP 9883)): #0 0x7f1115cd2a76 in ppoll () at /usr/lib/libc.so.6 #1 0x7f11130b0e73 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f11130b260f in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f11130573db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1112e667ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f110c632416 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f1112e6bb4d in () at /usr/lib/libQt5Core.so.5 #7 0x7f110ecc708c in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f1115cdce7f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f10fc4b0700 (LWP 9759)): #0 0x7f1115cd297b in poll () at /usr/lib/libc.so.6 #1 0x7f1114bcf180 in () at /usr/lib/libxcb.so.1 #2 0x7f1114bd0e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f10fd59d82a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f1112e6bb4d in () at /usr/lib/libQt5Core.so.5 #5 0x7f110ecc708c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1115cdce7f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f1116337840 (LWP 9729)): [KCrash Handler] #6 0x40298319 in () #7 0x7f10df3f5c39 in () at /usr/lib/libnvidia-glcore.so.390.42 #8 0x7f10df3fc8c4 in () at /usr/lib/libnvidia-glcore.so.390.42 #9 0x7f10df405914 in () at /usr/lib/libnvidia-glcore.so.390.42 #10 0x7f10defc0415 in () at /usr/lib/libnvidia-glcore.so.390.42 #11
[krita] [Bug 392240] Krita crashing while clicking save in text edit tool
https://bugs.kde.org/show_bug.cgi?id=392240 Mateusz Przybyłowicz <uam...@gmail.com> changed: What|Removed |Added Version|unspecified |4.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392240] New: Krita crashing while clicking save in text edit tool
https://bugs.kde.org/show_bug.cgi?id=392240 Bug ID: 392240 Summary: Krita crashing while clicking save in text edit tool Product: krita Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: uam...@gmail.com Target Milestone: --- Application: krita (4.0.0) Qt Version: 5.10.0 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-11.1-liquorix-amd64 x86_64 Distribution: KDE neon User Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I was changing colors, spacing in text edit tool and clicked "Save" button, I've managed to reproduce this error once before, I've used "Enter" key in text tool to add some space and clicked "Save" The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbbfec2c900 (LWP 32145))] Thread 15 (Thread 0x7fbbad442700 (LWP 32179)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbbd918dd7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fbbd918da88 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fbbf50406ba in start_thread (arg=0x7fbbad442700) at pthread_create.c:333 #4 0x7fbbfb5c341d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7fbba7fff700 (LWP 32178)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbbd918dd7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fbbd918da88 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fbbf50406ba in start_thread (arg=0x7fbba7fff700) at pthread_create.c:333 #4 0x7fbbfb5c341d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7fbba77fe700 (LWP 32177)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbbd918dd7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fbbd918da88 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fbbf50406ba in start_thread (arg=0x7fbba77fe700) at pthread_create.c:333 #4 0x7fbbfb5c341d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fbbc74c4700 (LWP 32160)): #0 0x7ffd6a7e0a09 in ?? () #1 0x7ffd6a7e0cba in clock_gettime () #2 0x7fbbfb5d1876 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7fbbc74c3a00) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7fbbfc0ffed1 in qt_clock_gettime (ts=0x7fbbc74c3a00, clock=) at kernel/qelapsedtimer_unix.cpp:111 #4 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #5 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #6 0x7fbbfc0fe6c9 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7fbbb0002cd0) at kernel/qtimerinfo_unix.cpp:91 #7 0x7fbbfc0fec35 in QTimerInfoList::timerWait (this=0x7fbbb0002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:388 #8 0x7fbbfc10033e in timerSourcePrepareHelper (timeout=0x7fbbc74c3ad4, src=) at kernel/qeventdispatcher_glib.cpp:132 #9 timerSourcePrepare (source=, timeout=0x7fbbc74c3ad4) at kernel/qeventdispatcher_glib.cpp:165 #10 0x7fbbf37d991d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7fbbf37da2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7fbbf37da49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fbbfc1005cb in QEventDispatcherGlib::processEvents (this=0x7fbbb8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #14 0x7fbbfc0a764a in QEventLoop::exec (this=this@entry=0x7fbbc74c3ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #15 0x7fbbfbec7554 in QThread::exec (this=) at thread/qthread.cpp:522 #16 0x7fbbe05cca35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7fbbfbecc6eb in QThreadPrivate::start (arg=0xb1e7060) at thread/qthread_unix.cpp:376 #18 0x7fbbf50406ba in start_thread (arg=0x7fbbc74c4700) at pthread_create.c:333 #19 0x7fbbfb5c341d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7fbbb68eb700 (LWP 32159)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fbbfbecd67b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0xa89b150) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=, mutex=mutex@entry=0xa89b130, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7fbbfbec61ef in
[kwin] [Bug 386018] New: KDE Crash while switching applications with alt+tab
https://bugs.kde.org/show_bug.cgi?id=386018 Bug ID: 386018 Summary: KDE Crash while switching applications with alt+tab Product: kwin Version: 5.11.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: uam...@gmail.com Target Milestone: --- Application: kwin_x11 (5.11.1) Qt Version: 5.9.2 Frameworks Version: 5.39.0 Operating System: Linux 4.13.7-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Alt-tabbing pretty quickly with Chrome, Discord, Dolphin, there was heavy IO operation in the background, I'm using the latest version avaiable on Archlinux repos. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9ed931f840 (LWP 954))] Thread 30 (Thread 0x7f9dc7fff700 (LWP 15442)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f9de0fda700 (LWP 15441)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f9db6ffd700 (LWP 15423)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 27 (Thread 0x7f9db77fe700 (LWP 15422)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7f9db7fff700 (LWP 14414)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7f9dc4b44700 (LWP 14413)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7f9dc5345700 (LWP 14398)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7f9dc5b46700 (LWP 14397)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7f9eb75ef700 (LWP 14241)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f9ea3076728 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f9ed1c5508a in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f9ed8cb024f in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7f9e997aa700 (LWP 14240)): #0 0x7f9ed1c5b38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f9ea307681c in () at
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #34 from Mateusz <matt.drza...@gmail.com> --- This got even worse in 5.10.1 plasma version with KDE Frameworks 5.34.0 and Qt 5.9.0. Restarting Plasmashell and Kwin does not help;( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #32 from Mateusz <matt.drza...@gmail.com> --- Does anyone know what can cause this problem? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376945] New: Segfault when clicking Get new comics in Comic Strip widget after analog clock removed
https://bugs.kde.org/show_bug.cgi?id=376945 Bug ID: 376945 Summary: Segfault when clicking Get new comics in Comic Strip widget after analog clock removed Product: plasmashell Version: 5.9.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: uam...@gmail.com Target Milestone: 1.0 Created attachment 104228 --> https://bugs.kde.org/attachment.cgi?id=104228=edit journald logs To reproduce: - add analog clock to the desktop - add comic strip - delete analog clock - enter comic strip's settings - click "Get new comics" Result: Plasmashell will either hang for a while or throw segfault, analog clock will reappear on the desktop How it looks: https://i.imgur.com/KTJdSCo.png >From dmesg: "[ 450.144557] plasmashell[4405]: segfault at 28 ip 7f24be27d62e sp 7ffe99ffa0b0 error 4 in libQt5Widgets.so.5.8.0[7f24be0e6000+628000]" Journald logs in the attachment -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376633] Pager moves windows without user request.
https://bugs.kde.org/show_bug.cgi?id=376633 --- Comment #8 from Mateusz <matt.drza...@gmail.com> --- I added dragging = false to my main.qml and it works. Thank you. I will let you know if I find anything suspicious about Pager;) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376769] New: Crash on changing workspace theme to Maia
https://bugs.kde.org/show_bug.cgi?id=376769 Bug ID: 376769 Summary: Crash on changing workspace theme to Maia Product: systemsettings Version: 5.9.2 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: uam...@gmail.com Target Milestone: --- Application: systemsettings5 (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.9-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Changed workspace theme to Maia My distro is Manjaro, everything up-to-date -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f786ae0b5c0 (LWP 23277))] Thread 12 (Thread 0x7f77cbfff700 (LWP 24186)): #0 0x7f7866b1f48d in poll () at /usr/lib/libc.so.6 #1 0x7f7860c4b786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f7860c4b89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f786744306b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f78673ec89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f786720ea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f7865513025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f78672136d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f7862b6c454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f7866b287df in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f781ec07700 (LWP 21259)): #0 0x7f7866b1f48d in poll () at /usr/lib/libc.so.6 #1 0x7f7860c4b786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f7860c4b89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f786744306b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f78673ec89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f786720ea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f7865513025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f78672136d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f7862b6c454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f7866b287df in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f781f81f700 (LWP 21203)): #0 0x7f7860c4ad58 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7f7860c4b6ab in () at /usr/lib/libglib-2.0.so.0 #2 0x7f7860c4bb12 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7f7831fbb316 in () at /usr/lib/libgio-2.0.so.0 #4 0x7f7860c730d5 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f7862b6c454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f7866b287df in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f78392d6700 (LWP 21202)): #0 0x7f7866b1f48d in poll () at /usr/lib/libc.so.6 #1 0x7f7860c4b786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f7860c4b89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f7860c4b8e1 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f7860c730d5 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f7862b6c454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f7866b287df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f783e766700 (LWP 23285)): #0 0x7f7862b7210f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f784493e9eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f784493e847 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f7862b6c454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f7866b287df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f783ef67700 (LWP 23284)): #0 0x7f7862b7210f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f784493e9eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f784493e847 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f7862b6c454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f7866b287df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f783f768700 (LWP 23283)): #0 0x7f7862b7210f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f784493e9eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f784493e847 in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #3 0x7f7862b6c454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f7866b287df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f783ff69700 (LWP 23282)): #0 0x7f7862b7210f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f784493e9eb in () at /usr/lib/xorg/modules/dri/radeonsi_dri.so #2 0x7f784493e847 in () at
[plasmashell] [Bug 376633] Pager moves windows without user request.
https://bugs.kde.org/show_bug.cgi?id=376633 --- Comment #5 from Mateusz <matt.drza...@gmail.com> --- I checked different case and windows are always moved to the first workspace in pager, no matter which workspace you start from. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376633] Pager moves windows without user request.
https://bugs.kde.org/show_bug.cgi?id=376633 --- Comment #3 from Mateusz <matt.drza...@gmail.com> --- It's a little different, because I don't remember it to move windows on its own. I recorded video. You can hear mouse clicks so it will be easier to reproduce;) http://sendvid.com/peevedf3 I am using: KDE Plasma version: 5.9.2 KDE Frameworks version: 5.31.0 Qt Version: 5.8.0. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 364251] Korganizer crashes when deleting timezone
https://bugs.kde.org/show_bug.cgi?id=364251 Mateusz <matt.drza...@gmail.com> changed: What|Removed |Added Resolution|FIXED |INVALID -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 364251] Korganizer crashes when deleting timezone
https://bugs.kde.org/show_bug.cgi?id=364251 Mateusz <matt.drza...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376633] New: Pager moves windows without user request.
https://bugs.kde.org/show_bug.cgi?id=376633 Bug ID: 376633 Summary: Pager moves windows without user request. Product: plasmashell Version: 5.9.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: matt.drza...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 104103 --> https://bugs.kde.org/attachment.cgi?id=104103=edit Visual description of a bug See attached gif for better description. As it is hard to describe it verbally. What happened there is I clicked and dragged window rectangle outside pager and then clicked on window rectangle in the second workspace which caused this window to be moved to the first workspace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373920] Pager window rectangle stays in wrong workspace.
https://bugs.kde.org/show_bug.cgi?id=373920 --- Comment #5 from Mateusz <matt.drza...@gmail.com> --- I couldn't find that commit;) Now I understand. Thanks for explaining. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373920] Pager window rectangle stays in wrong workspace.
https://bugs.kde.org/show_bug.cgi?id=373920 Mateusz <matt.drza...@gmail.com> changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373920] Pager window rectangle stays in wrong workspace.
https://bugs.kde.org/show_bug.cgi?id=373920 --- Comment #2 from Mateusz <matt.drza...@gmail.com> --- This bug still exist in: KDE Plasma version: 5.8.5 KDE Frameworks version: 5.30.0 Qt Version: 5.7.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375331] New: Black screen after resuming from hibernation
https://bugs.kde.org/show_bug.cgi?id=375331 Bug ID: 375331 Summary: Black screen after resuming from hibernation Product: plasmashell Version: 5.8.5 Platform: Android OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: matt.drza...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Steps to reproduce: 1. Work as usual with external display connected via HDMI. 2. Hibernate laptop. 3. Disconnect HDMI cable. 4. Resume from hibernation. After that I get black screen, no mouse cursor. Can't get to tty unless I close the lid and resume from suspend, then CTRL+ALT+F[1-6] starts working. Temporary solution is to blindly login to desktop, launch terminal and xrandr to primary display using: xrandr --output HDMI1 --off --output LVDS1 --auto -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373843] kmail 5.4.0 "Act on new/unread mail in this folder" option not working
https://bugs.kde.org/show_bug.cgi?id=373843 Mateusz <matt.drza...@gmail.com> changed: What|Removed |Added CC||matt.drza...@gmail.com --- Comment #2 from Mateusz <matt.drza...@gmail.com> --- It doesn't work in 5.4.1 too. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362575] Cannot unsubscribe IMAP folder
https://bugs.kde.org/show_bug.cgi?id=362575 --- Comment #5 from Mateusz <matt.drza...@gmail.com> --- I just checked and it works as expected. Thanks to everyone involved in fixing this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373920] New: Pager window rectangle stays in wrong workspace.
https://bugs.kde.org/show_bug.cgi?id=373920 Bug ID: 373920 Summary: Pager window rectangle stays in wrong workspace. Product: plasmashell Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: h...@kde.org Reporter: matt.drza...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 102885 --> https://bugs.kde.org/attachment.cgi?id=102885=edit Badly positioned rectangle. Steps to reproduce: 1. Press and hold on window rectangle in Pager. 2. Drag rectangle outside Pager. 3. Release mouse. 4. Move mouse to Pager. You can see that rectangle is still following mouse cursor. 5. Click somewhere in Pager. 6. Rectangle stays there. Rectangle should be snapped to the nearest workspace but that doesn't happen. I uploaded video that shows how to reproduce. https://sendvid.com/qqve9knw -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #27 from Mateusz <matt.drza...@gmail.com> --- Still exists in. KDE Plasma Version: 5.8.4 KDE Frameworks Version: 5.28.0 Qt Version: 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373202] Can't return from 'Show Desktop Grid' and 'Toggle Present Windows' actions.
https://bugs.kde.org/show_bug.cgi?id=373202 Mateusz <matt.drza...@gmail.com> changed: What|Removed |Added CC||matt.drza...@gmail.com --- Comment #2 from Mateusz <matt.drza...@gmail.com> --- Temporary solution thanks to Thomas Lübking. Try running "kwin_x11 --replace &" After that, shortcuts should work again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371699] No system tray after booting with second monitor connected.
https://bugs.kde.org/show_bug.cgi?id=371699 --- Comment #1 from Mateusz <matt.drza...@gmail.com> --- Doesn't seem to occur in Plasma 5.8.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371699] New: No system tray after booting with second monitor connected.
https://bugs.kde.org/show_bug.cgi?id=371699 Bug ID: 371699 Summary: No system tray after booting with second monitor connected. Product: plasmashell Version: 5.8.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: matt.drza...@gmail.com Target Milestone: 1.0 When I boot to Plasma 5.8.2 with external monitor there is no system tray. Buttons increase/decrease, mute sound don't work. I ps grepped plasmashell and found that: matt 4873 8.0 0.8 3084488 107544 ? Sl 09:02 0:01 plasmashell --shut-up matt 5317 0.0 0.0 10864 2176 pts/1S+ 09:02 0:00 grep --color=auto plasmashell The solution is to killall plasmashell and then kstart5 plasmashell, after that everything works fine. After that when ps grep plasmashell: matt 5344 22.8 1.2 3631636 154152 ? Sl 09:02 0:03 /usr/bin/plasmashell matt 5369 0.0 0.0 10864 2204 pts/2R+ 09:03 0:00 grep --color=auto plasmashell Why doesn't plasmashell start properly with second monitor connected? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369634] all windows minimize when clicking desktop
https://bugs.kde.org/show_bug.cgi?id=369634 Mateusz <matt.drza...@gmail.com> changed: What|Removed |Added CC||matt.drza...@gmail.com --- Comment #3 from Mateusz <matt.drza...@gmail.com> --- Can confirm. Antergos Plasma 5.7.5 Kde Frameworks 5.26.0 Qt Version 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #24 from Mateusz <matt.drza...@gmail.com> --- Yes, I'm on Antergos. KDE Plasma Version: 5.7.3 KDE Frameworks Version: 5.25.0 Qt Version: 5.7.0 Solution that Thomas provided is still working ;) -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 366596] Some KDE applications processes remain as background (zombie) processes after closing
https://bugs.kde.org/show_bug.cgi?id=366596
--- Comment #5 from Mateusz Mikuła <mati...@gmail.com> ---
Hi,
Kevin Funk maybe it's not related to KDE since I'm trying to "integrate" KDE
with MSYS2 (could bebug with Qt, MinGW or whateber else).
I'm getting deadlock at return in every app that calls "KIconLoader::global()".
Minimal test case:
//includes...
int main() {
KIconLoader::global();
return 0; //freeze at this point
}
I've tried to use gdb with QtCreator but it didn't provide anything usefull (at
least for me). How can I obtain more info about this deadlock?
Tools: CMake 3.6.1, MinGW-w64 6.1.0, Qt 5.6.1
--
You are receiving this mail because:
You are watching all bug changes.
[kde-windows] [Bug 366596] Some KDE applications processes remain as background (zombie) processes after closing
https://bugs.kde.org/show_bug.cgi?id=366596 Mateusz Mikuła <mati...@gmail.com> changed: What|Removed |Added CC||mati...@gmail.com --- Comment #1 from Mateusz Mikuła <mati...@gmail.com> --- I'm porting KDE using MSYS2 (native building using mingw-w64). Instead of Emerge I've created PKGBUILD's (just like on Arch Linux) to build the stuff. KDE Framework apps are also affected. For an example kiconfinder5 from the KIconThemes is a small app (easier to work with) that is affected by this issue. It only hangs when arguments are provided, I did a small debugging and found out that it freezes when "return 0" or "return 1" is called. That led me to think it must be problem with resource freeing. More specifically if "const QString icon = KIconLoader::global()" is called the process will hang on return. kiconfinder5 code https://github.com/KDE/kiconthemes/blob/master/src/tools/kiconfinder/kiconfinder.cpp -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362804] Can't unsubscribe folder
https://bugs.kde.org/show_bug.cgi?id=362804 --- Comment #3 from Mateusz <matt.drza...@gmail.com> --- I remember that it worked in Kubuntu 15.10. I workarounded(it's not a verb isn't it?) this by unchecking 'Show in IMAP' option in Gmail settings. I hope someone will fix thix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #22 from Mateusz <matt.drza...@gmail.com> --- Thank you very much, this made it working again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #20 from Mateusz <matt.drza...@gmail.com> --- Suspending/resuming the compositor does not help. Additionally, I just booted to Kubuntu and I cant undo the effects again. This time I didn't change display configuration. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362804] Can't unsubscribe folder
https://bugs.kde.org/show_bug.cgi?id=362804 --- Comment #1 from Mateusz <matt.drza...@gmail.com> --- Kubuntu 16.04 with backports. KDE Plasma Version: 5.6.4 KDE Framworks Version: 5.22.0 Qt Version: 5.5.1 Kernel Version: 4.6 User still cannot unsubscribe desired folder. Doesn't work not only with Gmail but with others too. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362804] Can't unsubscribe folder
https://bugs.kde.org/show_bug.cgi?id=362804 Mateusz <matt.drza...@gmail.com> changed: What|Removed |Added Summary|Can't unsubscribe folder - |Can't unsubscribe folder |Gmail account. | -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 364251] Korganizer crashes when deleting timezone
https://bugs.kde.org/show_bug.cgi?id=364251 --- Comment #1 from Mateusz <matt.drza...@gmail.com> --- Really? No one gives a shit about this? ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #18 from Mateusz <matt.drza...@gmail.com> --- I run some tests and here are results. Dell monitor is connected via HDMI cable. Rebooted few times to make sure it's working or not working. OK means that effects are working. #Laptop Screen #Primary: Laptop Screen: OK #Primary: No Primary Screen: OK #Laptop Screen + Dell monitor #Primary: Laptop Screen: OK #Primary: Dell Monitor: OK #Primary: No Primary Screen: OK #Dell monitor #Primary: Dell Monitor: OK #Primary: No Primary Screen: OK I found a way to replicate this bug(It's clearly a bug;)) Each time I change display settings from 2 display setup to one display, doesn't matter if it's laptop display or Dell monitor, those effects stop working. I have to reboot to make them working again. Plus sometimes I have this feeling that after some time they just stop working, because everything works fine just after reboot. When the effects stop working, changing display settings to 2 display setup makes them working again. Again, changing back to one display makes them not working, again. Do you have any idea how to investigate further? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #17 from Mateusz <matt.drza...@gmail.com> --- It also happens on Kubuntu 16.04 with backports. This is really annoying bug. You can't use Plasma effects freely because of that. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 364251] New: Korganizer crashes when deleting timezone
https://bugs.kde.org/show_bug.cgi?id=364251 Bug ID: 364251 Summary: Korganizer crashes when deleting timezone Product: korganizer Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: timezones Assignee: korganizer-de...@kde.org Reporter: matt.drza...@gmail.com Korganizer crashes after every time after I popup 'Add Timezones' dialog and click delete button. I think that current index is wrong just after opening this dialog. Clicking existing entry on list and then delete button does not cause crash. Opening dialog and immediately clicking delete button causes crash. Reproducible: Always Steps to Reproduce: 1. Click 'Add Timezones' 2. Click red button to delete timezone. 3. Crash. Actual Results: Korganizer crashes. Expected Results: Korganizer doesn't crash. Kubuntu 16.04 with backports. Korganizer version: Version 5.1.3 KDE Frameworks 5.22.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362804] Can't unsubscribe folder - Gmail account.
https://bugs.kde.org/show_bug.cgi?id=362804 Mateusz <matt.drza...@gmail.com> changed: What|Removed |Added Summary|Can't unsubscribe folder - |Can't unsubscribe folder - |Gmail account |Gmail account. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #15 from Mateusz <matt.drza...@gmail.com> --- This also happens on Kubuntu 16.04. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362804] New: Can't unsubscribe folder - Gmail account
https://bugs.kde.org/show_bug.cgi?id=362804 Bug ID: 362804 Summary: Can't unsubscribe folder - Gmail account Product: kmail2 Version: 5.1.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: matt.drza...@gmail.com When I right click on my gmail e-mail account and select 'Manage Local Subscriptions' dialog 'Local Subscriptions --Kmail' is being shown. After that, I select folders I wouldn't like to be shown in my mail tree for example labels 'Important' and 'All Mail', I click 'Unsubscribe' and then 'Ok'. This changes nothing, both 'Important' and 'Unsubscribe' labels are visible. Reproducible: Always Steps to Reproduce: 1. Right click on my e-mail account and select 'Manage Local Subscriptions' 2. Unsubscribe desired folder. 3. Click Ok Actual Results: Nothing became unsubscribed. No visual changes were made AFAICT. Expected Results: Folders selected to be unsubscribed should be unsubscribed. Kubuntu 16.04 KDE Plasma Version: 5.5.5 Qt Version: 5.5.1 Kernel Version: 4.4.0-22-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #11 from Mateusz <matt.drza...@gmail.com> --- It's strange. I think it happens more often when I have second display connected using HDMI. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #9 from Mateusz <matt.drza...@gmail.com> --- Sorry, I must have deactivated effect before time ran out;) Fortunately sleep was found;P == Version === KWin version: 5.5.4 Qt Version: 5.5.1 Qt compile version: 5.5.1 XCB compile version: 1.11 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11702000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 2 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 101 glPlatformInterface: 1 Screen Edges desktopSwitching: false desktopSwitchingMovingClients: true cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: HDMI1 Geometry: 0,0,1920x1080 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile OpenGL version string: 3.3 (Core Profile) Mesa 11.0.2 OpenGL platform interface: GLX OpenGL shading language version string: 3.30 Driver: Intel GPU class: SandyBridge OpenGL version: 3.3 GLSL version: 3.30 Mesa version: 11.0.2 X server version: 1.17.2 Linux kernel version: 4.2 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom slidingpopups kwin4_effect_login slide screenshot minimizeanimation kwin4_effect_windowaperture kwin4_effect_translucency desktopgrid kwin4_effect_maximize kwin4_effect_fade presentwindows kwin4_effect_dialogparent highlightwindow blur contrast logout startupfeedback screenedge kscreen Currently Active Effects: - desktopgrid blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_login: slide: screenshot: minimizeanimation: kwin4_effect_windowaperture: kwin4_effect_translucency: desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true kwin4_effect_maximize: kwin4_effect_fade: presentwindows: layoutMode: 0 showCaptions: true showIcons: true doNotCloseWindows: false ignoreMinimized: false accuracy: 20 fillGaps: true fadeDuration: 150 showPanel: false leftButtonWindow: 1 rightButtonWindow: 2 middleButton
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #7 from Mateusz <matt.drza...@gmail.com> --- Here are the informations. KWin Support Information: The following information should be used when requesting support on e.g. http://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like http://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.5.4 Qt Version: 5.5.1 Qt compile version: 5.5.1 XCB compile version: 1.11 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11702000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 2 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 101 glPlatformInterface: 1 Screen Edges desktopSwitching: false desktopSwitchingMovingClients: true cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: HDMI1 Geometry: 0,0,1920x1080 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile OpenGL version string: 3.3 (Core Profile) Mesa 11.0.2 OpenGL platform interface: GLX OpenGL shading language version string: 3.30 Driver: Intel GPU class: SandyBridge OpenGL version: 3.3 GLSL version: 3.30 Mesa version: 11.0.2 X server version: 1.17.2 Linux kernel version: 4.2 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom slidingpopups kwin4_effect_login slide screenshot minimizeanimation kwin4_effect_windowaperture kwin4_effect_translucency desktopgrid kwin4_effect_maximize kwin4_effect_fade presentwindows kwin4_effect_dialogparent highlightwindow blur contrast logout startupfeedback screenedge kscreen Currently Active Effects: - blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_login: slide: screenshot: minimizeanimation: kwin4_effect_windowaperture: kwin4_effect_translucency: desktopgrid: zoomDuration: 300 border: 10 desktopNameAli
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #4 from Mateusz <matt.drza...@gmail.com> --- Thanks. According to [13.208] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration profile 1 [13.208] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration factor: 2.000 [13.208] (**) AlpsPS/2 ALPS DualPoint TouchPad: (accel) acceleration threshold: 4 [13.208] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: touchpad found [13.208] (II) config/udev: Adding input device AlpsPS/2 ALPS DualPoint TouchPad (/dev/input/mouse2) [13.208] (**) AlpsPS/2 ALPS DualPoint TouchPad: Ignoring device from InputClass "touchpad ignore duplicates" [13.210] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event10) [13.210] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall" [13.210] (II) Using input driver 'evdev' for 'Dell WMI hotkeys' [13.210] (**) Dell WMI hotkeys: always reports core events [13.210] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event10" [13.210] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0 [13.210] (--) evdev: Dell WMI hotkeys: Found keys [13.210] (II) evdev: Dell WMI hotkeys: Configuring as keyboard [13.210] (**) Option "config_info" "udev:/sys/devices/virtual/input/input11/event10" [13.210] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 15) [13.210] (**) Option "xkb_rules" "evdev" [13.210] (**) Option "xkb_model" "pc105" [13.210] (**) Option "xkb_layout" "pl" [13.713] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm [15.073] (II) intel(0): EDID vendor "CMO", prod id 5220 [15.073] (II) intel(0): Printing DDC gathered Modelines: [15.073] (II) intel(0): Modeline "1366x768"x0.0 71.00 1366 1414 1446 1498 768 769 773 790 +hsync -vsync (47.4 kHz eP) [15.073] (II) intel(0): Modeline "1366x768"x0.0 47.91 1366 1418 1453 1512 768 769 773 792 +hsync -vsync (31.7 kHz e) [ 8255.550] (II) Printing all currently active device grabs: [ 8255.550] (II) End list of active device grabs [ 8372.349] (II) Printing all currently active device grabs: [ 8372.349] (II) End list of active device grabs [ 8476.936] (II) AIGLX: Suspending AIGLX clients for VT switch [ 8513.527] (II) Printing all currently active device grabs: [ 8513.527] Active grab 0x240 (core) on device 'Virtual core keyboard' (3): [ 8513.527] client pid 1402 kwin_x11 [ 8513.527] at 8474615 (from active grab) (device thawed, state 1) [ 8513.527] core event mask 0x3 [ 8513.527] owner-events false, kb 1 ptr 1, confine 0, cursor 0x0 [ 8513.527] (II) End list of active device grabs [ 8543.920] (II) AIGLX: Resuming AIGLX clients after VT switch [ 8543.920] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 1, position (0, 0), rotation normal, reflection none [ 8543.921] (EE) intel(0): sna_mode_check: invalid state found on pipe 0, disabling CRTC:21 [ 8544.302] (--) synaptics: AlpsPS/2 ALPS DualPoint TouchPad: touchpad found 'Virtual core keyboard' has active grab. Is there something I could do to make it work? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #2 from Mateusz <matt.drza...@gmail.com> --- Martin Gräßlin No, I am unable to do that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] New: Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 Bug ID: 360841 Summary: Unable to unshow/unpresent windows using the same keyboard shortcut Product: kwin Version: 5.5.4 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: matt.drza...@gmail.com When I use keyboard shortcut(either custom or default) to 'Show Desktop Grid' or 'Present Windows' I am unable to unshow/unpresent them the same way, which is using keyboard shortcut. Grid is shown and Windows are presented, but no matter how many times I press keys nothing happens. It feels like shortcuts are disconnected when action is triggered. I am able to go back to whatever I was doing by simply clicking mouse anywhere. Reproducible: Sometimes Steps to Reproduce: 1. Toggle Show Desktop Grid or Present Windows 2. Enjoy shown desktop grid or presented windows 3. Toggle again to hide grid or windows 4. Nothing happens Actual Results: Grid is shown, windows are presented. Expected Results: Toggling action 'Show Desktop Grid' or 'Present Windows' should 'unshown' or 'unpresent' them when toggled second time. Kubuntu 15.10 KDE Plasma Version 5.5.4 Qt Version 5.5.1 Kernel Version 4.2.0-34-generic Os Type: 64-bit Laptop model: Dell Latitude E6420, i5-2520M -- You are receiving this mail because: You are watching all bug changes.
