[plasmashell] [Bug 393781] wallpaper cannot span multiple screens
https://bugs.kde.org/show_bug.cgi?id=393781 Johan Toft changed: What|Removed |Added CC||johan.t...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427545] Dual DisplayPort monitors (tiled, MST, e.g. 5k) are not supported by KWin
https://bugs.kde.org/show_bug.cgi?id=427545 Johan Toft changed: What|Removed |Added CC||johan.t...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 486804] New: KDE Neon systemupdate fails for several days
https://bugs.kde.org/show_bug.cgi?id=486804 Bug ID: 486804 Summary: KDE Neon systemupdate fails for several days Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: wauters.jo...@telenet.be CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- Created attachment 169339 --> https://bugs.kde.org/attachment.cgi?id=169339=edit screenshot of the actual bug. KDE Neon system update seems to fail for a few days now. Tried serveeral times, even afer a clean reboot of the system. See attachment -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481288] Gdrive invalid protocol after create a Google account to access Google Drive
https://bugs.kde.org/show_bug.cgi?id=481288
--- Comment #6 from Johan ---
I have a similar error when I try to open gdrive via dolphin.
org.kde.kgapi: Bad request, Google replied ' "{\n \"error\": {\n\"code\":
400,\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"errors\": [\n {\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"domain\": \"global\",\n\"reason\": \"invalidParameter\",\n
\"location\": \"fields\",\n\"locationType\": \"parameter\"\n
}\n]\n }\n}\n" '
org.kde.kgapi: Bad request, Google replied ' "{\n \"error\": {\n\"code\":
400,\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"errors\": [\n {\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"domain\": \"global\",\n\"reason\": \"invalidParameter\",\n
\"location\": \"fields\",\n\"locationType\": \"parameter\"\n
}\n]\n }\n}\n" '
kf.kio.core: UDSEntry for '.' not found, creating a default one. Please fix the
"kio_gdrive" KIO worker.
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 481288] Gdrive invalid protocol after create a Google account to access Google Drive
https://bugs.kde.org/show_bug.cgi?id=481288 Johan changed: What|Removed |Added CC||johangil...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #6 from Johan Sköld --- It does not, the same thing still happens. Even more weirdly, it happens when I fullscreen a transparent window as well, so I don't think direct scanout would be active either way? Although I just realized what's causing it. I remembered my second monitor technically supports VRR, but tends to flicker when it's enabled (only in Linux though, likely a driver bug). Both my monitors had VRR set to "Automatic". If I disable it on the second monitor the flicker stops. Is it possible that KWin enabled VRR on the second monitor too when fullscreening something on my main monitor? Otherwise this may also be some driver bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #4 from Johan Sköld --- Created attachment 166080 --> https://bugs.kde.org/attachment.cgi?id=166080=edit Image shifting on monitor before it turns off. Thanks for the link. I applied that patch to version 5.93.0 of kwin and built it, and while it did get rid of the journalctl spam, my monitor still flickers when I enter or exit fullscreen with some window, and occasionally while just having a window fullscreened. So the original problem is still there. If it helps, just before the monitor turns off the image shifts a bit. When entering fullscreen it shifts down, while when leaving fullscreen it shifts up. Attaching a slow-mo clip of what it looks like when entering fullscreen on my other monitor (just out of view). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #2 from Johan Sköld --- Sorry, one more thing to add that I just noticed. If I open Spectacle and press "Rectangular Region", the monitor flickers off/on every single time I move the mouse cursor. Regardless of which monitor I move it on. And I thought to check `journalctl`. Looking at the last 50 thousand lines, just about every single line says: feb 24 00:13:58 pc kwin_wayland[2937]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glUniformMatrix(matrix size mismatch) The even remotely relevant lines that don't say that are: feb 24 00:09:34 pc kwin_wayland[2937]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x592bbe8e7690) [...] feb 24 00:10:16 pc systemd[2870]: Starting Spectacle screenshot capture utility... [...] feb 24 00:10:16 pc spectacle[6436]: QApplication: invalid style override 'adwaita-dark' passed, ignoring it. Available styles: Breeze, Oxygen, Windows, Fusion [...] feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: VAAPI: Failed to initialize display feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: DRM device not found feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: VAAPI: Failed to initialize display feb 24 00:10:16 pc spectacle[6436]: kpipewire_record_logging: DRM device not found feb 24 00:10:16 pc systemd[2870]: Started Spectacle screenshot capture utility. [...] feb 24 00:10:16 pc plasmashell[3214]: QQuickItem: Cannot set FocusScope once item has children and is in a window. [...] feb 24 00:11:18 pc plasmashell[3214]: error creating screencast "Could not find window id 0" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 --- Comment #1 from Johan Sköld --- To clarify: It flickers regardless of if a window is fullscreened on my first or second monitor. I wrote most of the original summary before verifying that, and forgot to update parts of it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] Periodic flicker on secondary monitor with fullscreen window on any monitor
https://bugs.kde.org/show_bug.cgi?id=481750 Johan Sköld changed: What|Removed |Added Summary|Periodic flicker on |Periodic flicker on |secondary monitor with |secondary monitor with |fullscreen window on|fullscreen window on any |primary monitor |monitor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481750] New: Periodic flicker on secondary monitor with fullscreen window on primary monitor
https://bugs.kde.org/show_bug.cgi?id=481750 Bug ID: 481750 Summary: Periodic flicker on secondary monitor with fullscreen window on primary monitor Classification: Plasma Product: kwin Version: 5.93.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: jo...@skold.cc Target Milestone: --- SUMMARY Using wayland with two monitors: - Dell AW3423DW, 3440x1440 @ 175 Hz, DisplayPort - cocopar 133LR, 1920x1080 @ 60 Hz, HDMI My GPU is an AMD RX 6900 XT, and I'm using the RADV vulkan drivers (v. 24.0.1). The AMDVLK drivers are not installed. Whenever I have a window in fullscreen on the Dell monitor, the cocopar will flicker from time to time. As in it goes black for a second or two before coming back on. Sometimes I can go several minutes without seeing the flicker, other times it happens again within seconds. It seems to happen very frequently when toggling fullscreen on or off, so that's a fast way to repro. If I force atomic modesetting off (`KWIN_DRM_NO_AMS=1`) it's a 100% repro rate whenever toggling fullscreen on or off. STEPS TO REPRODUCE 1. Have two monitors connected and configured to extend the desktop. 2. Toggle fullscreen on or off in some application on one monitor. OBSERVED RESULT The second monitor turns off and on again. EXPECTED RESULT The second monitor does not turn off. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.6-zen1-1-zen / 6.0 RC2 KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION - The Dell monitor never flickers, it's always the cocopar. - Toggling fullscreen on or off on the cocopar also causes it to flicker. - The same setup worked in an older version of plasma (unsure of what version, but whatever was in arch's repos a few months ago), with `KWIN_DRM_NO_AMS=1`. Unsure about without. - The same setup also works in sway, with or without atomic modesetting. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466293] Cannot scroll beyond the border of the screen using Wayland
https://bugs.kde.org/show_bug.cgi?id=466293 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 155384] Easily copy properties from one image to another one
https://bugs.kde.org/show_bug.cgi?id=155384 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 411753] KDE Connect spams the desktop with a torrent of old notifications.
https://bugs.kde.org/show_bug.cgi?id=411753 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 391704] Minor problems with EPS images
https://bugs.kde.org/show_bug.cgi?id=391704 johan changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from johan --- I confirm that this bug still exists in Karbon 3.2.1 on Debian 11 Bullseye. Additionally, the image seems to be improperly placed on the canvas/page. I don't remember if this problem occurred when this bug was reported. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 391703] Some SVG elements are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=391703 johan changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from johan --- I confirm that this bug still exists in Karbon 3.2.1 on Debian 11 Bullseye. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 --- Comment #45 from Johan Sjölén --- (In reply to Bharadwaj Raju from comment #43) > (In reply to Johan Sjölén from comment #41) > > Unfortunately Bharadwaj seems to have abandoned their fix. > > I suppose if you're looking at > https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/832, it might > appear "abandoned" since there is only one code review comment on the whole > thread. Most of the discussion is in the corresponding Plasma Frameworks MR > here: > https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/442. > Please follow that for progress. Hi Bharadwaj! I saw that your more generalized PR was merged, awesome job :-). Do you happen to know whether this ticket should be considered fixed? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385998] Scam detection reads GnuPG output, giving false positives
https://bugs.kde.org/show_bug.cgi?id=385998 Karl-Johan Karlsson changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Karl-Johan Karlsson --- I checked on KMail 5.21.3, and can no longer reproduce this problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 338501] Monitor doesn't go to sleep when the screen is locked
https://bugs.kde.org/show_bug.cgi?id=338501 Johan Manuel changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE --- Comment #4 from Johan Manuel --- Unfortunately I don't have the right setup to try and reproduce this now, but I think this is in fact a duplicate of https://bugs.kde.org/show_bug.cgi?id=348529 as a comment above indicated, so I will close it as such. *** This bug has been marked as a duplicate of bug 348529 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] Turn off screen after lock screen
https://bugs.kde.org/show_bug.cgi?id=348529 Johan Manuel changed: What|Removed |Added CC||johan.man...@live.fr --- Comment #41 from Johan Manuel --- *** Bug 338501 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 --- Comment #41 from Johan Sjölén --- Thank you Nate, for directing my bug to this one. I saw that there has been a suggested fix based on "triangle mouse filtering". Such a solution seems to previously have been implemented for something else, but the other way around. So at least the technique as named seems legitimate. https://phabricator.kde.org/D13192 Unfortunately Bharadwaj seems to have abandoned their fix. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458460] New: Allow for moving mouse diagonally to select instance of app
https://bugs.kde.org/show_bug.cgi?id=458460 Bug ID: 458460 Summary: Allow for moving mouse diagonally to select instance of app Product: plasmashell Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: johan.borglin.sjo...@gmail.com Target Milestone: 1.0 Created attachment 151678 --> https://bugs.kde.org/attachment.cgi?id=151678=edit Reproducton steps SUMMARY Task manager currently swaps shown preview window too quickly. When going to select a preview instance of an app the mouse pointer will naturally touch other running app icons as part of travelling the shortest distance to the app preview. This causes the previous app preview to be lost. Best way of understanding this is watching the attached video, I think. STEPS TO REPRODUCE 1. Have a Task manager widget ready 2. Launch two of one app, one of another 2. Hover over the app with two instances, causing preview windows for the app to show 3. Attempt to take shortest route with mouse to 2nd instance to the right (that is: move diagonally) 4. This will cause the mouse to touch the app to the right of the current app in the task manager bar OBSERVED RESULT The preview windows of the 2 app will disappear, and the preview window of the other app will appear EXPECTED RESULT Some delay in showing the other app, allowing the user to select the 2nd instance of the originally previewed app. Currently, the user must first go up and then to the right, to avoid touching any other app. This is super annoying! Requiring the mouse to stand still on the app before switching preview would be great. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #35 from Johan Sköld --- It happened again this morning, so I looked at `journalctl` in a tty before unlocking it. Nothing appears to show up when I click "Unlock", but there are a few lines that appear to be potentially relevant earlier in the log. Filtered to skip device connect spam from switching back/forth between ttys: > Jul 18 11:57:58 pc kwin_wayland[2002]: QMetaProperty::read: Unable to handle > unregistered datatype 'KWin::SessionState' for property > 'KWin::EffectsHandlerImpl::sessionState' > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: > QML Connections: Detected function "onConfigurationChanged" in Connections > element. This is probably intended to be a signal handler but no signal of > the target matches the name. > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: > QML Connections: Detected function "onRepaintNeeded" in Connections element. > This is probably intended to be a signal handler but no signal of the target > matches the name. > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:67: > TypeError: Cannot read property 'wallpaper' of null > Jul 18 11:57:59 pc plasmashell[2195]: > file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:71: > TypeError: Cannot read property 'wallpaper' of null > Jul 18 11:57:59 pc plasmashell[2195]: qt.qpa.wayland: Wayland does not > support QWindow::requestActivate() > Jul 18 11:57:59 pc plasmashell[2195]: qt.qpa.wayland: Wayland does not > support QWindow::requestActivate() > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: qt.qpa.wayland: Wayland does > not support QWindow::requestActivate() > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool > Jul 18 11:57:59 pc kscreenlocker_greet[38156]: qt.qpa.wayland: Wayland does > not support QWindow::requestActivate() > Jul 18 11:58:05 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool > Jul 18 11:58:05 pc kscreenlocker_greet[38156]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: > Unable to assign [undefined] to bool There's also a bit of bismuth spam since I installed that yesterday to give it a try, but I did not have that installed yet when I ran into this yesterday so it seems unrelated and I thus filtered it out above. Operating System: EndeavourOS KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454349] Searching for something automatically selects the second item instead of the first
https://bugs.kde.org/show_bug.cgi?id=454349 Johan Sköld changed: What|Removed |Added CC||jo...@skold.cc --- Comment #8 from Johan Sköld --- I can reproduce this consistently as well in kickoff, but I also seem to have figured out what happens (but not why). 1. Open kickoff and search for something 2. Highlight one of the options with the mouse 3. Press escape to close kickoff 4. Move the cursor away 5. Open kickoff and search for something again (it doesn't have to be the same term) When I do that, it selects the same entry that I hovered with the mouse in step 2. So if I hovered the third entry, it will select the third entry. It sometimes even reproduces without searching for anything once you re-open kickoff, if you had the cursor in a position where it would highlight something in the default view. If I search for something and hover the 6th entry on the left side of the view, once I re-open kickoff it selects "Games" without me doing anything. KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453438] New: Crashed when login
https://bugs.kde.org/show_bug.cgi?id=453438
Bug ID: 453438
Summary: Crashed when login
Product: kwin
Version: 5.24.5
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: johanbe...@gmail.com
Target Milestone: ---
Application: kwin_x11 (5.24.5)
Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.13.0-40-generic x86_64
Windowing System: X11
Distribution: KDE neon User - 5.24
DrKonqi: 5.24.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Restarted after install updates.
- Unusual behavior I noticed:
None unusual behavior were noticed.
The crash can be reproduced every time.
-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
[New LWP 2682]
[New LWP 2687]
[New LWP 2689]
[New LWP 2703]
[New LWP 2709]
[New LWP 2713]
[New LWP 2726]
[New LWP 2727]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f27f7acd9cf in __GI___poll (fds=0x7ffe8f988ff8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="constructor",file="/usr/share/kwin/scripts/bismuth/contents/code/index.mjs",fullname="/usr/share/kwin/scripts/bismuth/contents/code/index.mjs",line="2024",language="js"},".
-
(beware that frames may have been optimized out)
[Current thread is 1 (Thread 0x7f27f313c9c0 (LWP 2669))]
Thread 9 (Thread 0x7f27b700 (LWP 2727)):
#0 0x7f27f7acdac6 in __ppoll (fds=0x7f27b4000d98, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44
#1 0x7f27f8bb8559 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#2 0x7f27f8bb9c03 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#3 0x7f27f8b6087b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x7f27f897a442 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x7f27f897b623 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7f27f875f609 in start_thread (arg=) at
pthread_create.c:477
#7 0x7f27f7ada163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 8 (Thread 0x7f27d48a9700 (LWP 2726)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55ec569d4230) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ec569d41e0,
cond=0x55ec569d4208) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55ec569d4208, mutex=0x55ec569d41e0) at
pthread_cond_wait.c:638
#3 0x7f27ea63a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x7f27ea63a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5 0x7f27f875f609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f27f7ada163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 7 (Thread 0x7f27d50aa700 (LWP 2713)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x55ec568a4d58) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ec568a4d08,
cond=0x55ec568a4d30) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x55ec568a4d30, mutex=0x55ec568a4d08) at
pthread_cond_wait.c:638
#3 0x7f27ea63a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x7f27ea63a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5 0x7f27f875f609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f27f7ada163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 6 (Thread 0x7f27d59ec700 (LWP 2709)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x7f27f00b8550) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f27f00b8500,
cond=0x7f27f00b8528) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x7f27f00b8528, mutex=0x7f27f00b8500) at
pthread_cond_wait.c:638
#3 0x7f27ea63a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x7f27ea63a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5 0x7f27f875f609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7f27f7ada163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 5 (Thread 0x7f27d6dee700 (LWP 2703)):
#0 0x7f27f8bb9a59 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#1 0x7f27f8b6087b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#2 0x7f27f897a442 in QThread::exec() () from
[krita] [Bug 450220] New: There's a problem about zooming or rotating my cavnas. Sometimes it's not working on the zooming one using my mouse. And sometimes the rotating one keeps going on the 15 degr
https://bugs.kde.org/show_bug.cgi?id=450220 Bug ID: 450220 Summary: There's a problem about zooming or rotating my cavnas. Sometimes it's not working on the zooming one using my mouse. And sometimes the rotating one keeps going on the 15 degrees even i didn't anything on it. It even occurs when i try to draw. Please fix Product: krita Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: floatysuck...@gmail.com Target Milestone: --- SUMMARY There's a problem about zooming or rotating my cavnas. Sometimes it's not working on the zooming one using my mouse. And sometimes the rotating one keeps going on the 15 degrees even i didn't anything on it. It even occurs when i try to draw. Please fix it. I am sick and tired of it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439332] Ghost windows and popups
https://bugs.kde.org/show_bug.cgi?id=439332 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430036] konsole no-toolbar setting missing or forgotten
https://bugs.kde.org/show_bug.cgi?id=430036 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440902] Toolbar menu command missing
https://bugs.kde.org/show_bug.cgi?id=440902 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 437223] Can't OPT-OUT of invisible scrollbar slider
https://bugs.kde.org/show_bug.cgi?id=437223 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 420485] Support JMAP
https://bugs.kde.org/show_bug.cgi?id=420485 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434785] Proposal: Operation to move subtitle to playhead
https://bugs.kde.org/show_bug.cgi?id=434785 --- Comment #3 from Johan Vromans --- Thanks for the suggestion. It surely helps, but the frequent (and necessary) switching between the subtitle edit window and the track (to make it active) is still less than optimal. Nevertheless I can live with it. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427073] Some of Krita pop up window stuck in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=427073 --- Comment #9 from Johan Tri Handoyo --- This is solved already, it's a problem with Ubuntu window manager stuff. Not a Krita bug. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 67859] [test case] Overflowed Text and Anchors don't seem to work
https://bugs.kde.org/show_bug.cgi?id=67859 Johan changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|CONFIRMED |RESOLVED --- Comment #11 from Johan --- (In reply to Justin Zobel from comment #10) > Thank you for the bug report. > > As this report hasn't seen any changes in 10 years or more, we ask if you > can please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. Hi Justin, Thank you for reminding me that I opened this bug maaany years ago. I thought it would have been automatically closed a long time ago (as it is the case on many other bug trackers) but now it is... ;-) Best regards, Johan -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 434785] New: Proposal: Operation to move subtitle to playhead
https://bugs.kde.org/show_bug.cgi?id=434785 Bug ID: 434785 Summary: Proposal: Operation to move subtitle to playhead Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jvrom...@squirrel.nl Target Milestone: --- This is an enhancement request for an operation that speeds up adding subtitles. Tentative operation name: "move subtitle to playhead", hereafter referred to as MSTP. Semantics: - When the playhead is BEFORE a subtitle, move the start of this subtitle to the playhead position. - When the playhead is IN a subtitle, move the start of the subtitle to the playhead position. - Otherwise it is ignored. Rationale: In most cases the text of the subtitles is available in some text document. You can create a subtitle and copy/paste all text lines into in. Make this subtitle long. - Now start playing until the playhead is at the point where the next subtitle should start. - Activate MSTP and the subtitles moves to the playhead. - Continue to play until the playhead reaches the end of the subtitle. - Use the scissors tool to split off the first line of the subtitles. - Start playing until the playhead is at the point where the next subtitle should start, SMTP, etc... -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 428585] Elisa is crashing when scrolling Album view
https://bugs.kde.org/show_bug.cgi?id=428585 --- Comment #4 from Johan --- Elisa is crashing when scrolling Album view happens only when Elisa is updating Music collection. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 428697] New: Elisa crashes every time when scrolling down Album list
https://bugs.kde.org/show_bug.cgi?id=428697 Bug ID: 428697 Summary: Elisa crashes every time when scrolling down Album list Product: elisa Version: 20.08.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: johanwillemd...@gmail.com Target Milestone: --- Application: elisa (20.08.2) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.9.1-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Every time I scroll down the Album list Elisa chrashes (on Xorg). The crash can be reproduced every time. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [New LWP 6908] [New LWP 6909] [New LWP 6911] [New LWP 6912] [New LWP 6913] [New LWP 6914] [New LWP 6915] [New LWP 6925] [New LWP 6926] [New LWP 6927] [New LWP 6928] [New LWP 6929] [New LWP 6933] [New LWP 6934] [New LWP 6935] [New LWP 6936] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x7fea5ce3de7f in poll () from /lib64/libc.so.6 [Current thread is 1 (Thread 0x7fea59cd4e80 (LWP 6906))] Thread 17 (Thread 0x7fe9f27fc640 (LWP 6936)): #0 0x7fea5ce43799 in syscall () from /lib64/libc.so.6 #1 0x7fea5b09e1ef in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7fea341cbdd3 in gst_base_sink_wait_preroll () from /usr/lib64/libgstbase-1.0.so.0 #3 0x7fea341cc33d in gst_base_sink_do_preroll () from /usr/lib64/libgstbase-1.0.so.0 #4 0x7fea341ef91c in ?? () from /usr/lib64/libgstbase-1.0.so.0 #5 0x7fea341f1145 in ?? () from /usr/lib64/libgstbase-1.0.so.0 #6 0x7fea341c1450 in ?? () from /usr/lib64/libgstbase-1.0.so.0 #7 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #8 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #9 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #10 0x7fea34591c9b in gst_proxy_pad_chain_default () from /usr/lib64/libgstreamer-1.0.so.0 #11 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #12 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #13 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #14 0x7fea34591c9b in gst_proxy_pad_chain_default () from /usr/lib64/libgstreamer-1.0.so.0 #15 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #16 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #17 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #18 0x7fea341cf6ad in ?? () from /usr/lib64/libgstbase-1.0.so.0 #19 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #20 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #21 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #22 0x7fea341cf6ad in ?? () from /usr/lib64/libgstbase-1.0.so.0 #23 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #24 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #25 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #26 0x7fea34591c9b in gst_proxy_pad_chain_default () from /usr/lib64/libgstreamer-1.0.so.0 #27 0x7fea345a619d in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #28 0x7fea345a96b9 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #29 0x7fea345a9abe in gst_pad_push () from /usr/lib64/libgstreamer-1.0.so.0 #30 0x7fea10687e9b in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #31 0x7fea345cf5ef in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #32 0x7fea5b0769e4 in ?? () from /usr/lib64/libglib-2.0.so.0 #33 0x7fea5b0760ee in ?? () from /usr/lib64/libglib-2.0.so.0 #34 0x7fea5ba19eb1 in start_thread () from /lib64/libpthread.so.0 #35 0x7fea5ce48ccf in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7fe9f2ffd640 (LWP 6935)): #0 0x7fea5ce43799 in syscall () from /lib64/libc.so.6 #1 0x7fea5b09e1ef in g_cond_wait () from /usr/lib64/libglib-2.0.so.0 #2 0x7fea10686f5b in ?? () from /usr/lib64/gstreamer-1.0/libgstcoreelements.so #3 0x7fea345a5b2a in gst_pad_query () from /usr/lib64/libgstreamer-1.0.so.0 #4 0x7fea345a88ab in gst_pad_peer_query () from /usr/lib64/libgstreamer-1.0.so.0 #5 0x7fea345a90d6 in ?? () from /usr/lib64/libgstreamer-1.0.so.0 #6 0x7fea345a48ae in gst_pad_forward () from /usr/lib64/libgstreamer-1.0.so.0 #7 0x7fea345a4f96 in gst_pad_query_default () from /usr/lib64/libgstreamer-1.0.so.0 #8 0x7fea345a5b2a in gst_pad_query () from /usr/lib64/libgstreamer-1.0.so.0 #9 0x7fea345a88ab in gst_pad_peer_query () from /usr/lib64/libgstreamer-1.0.so.0 #10
[systemsettings] [Bug 427007] Add manual mode to night color
https://bugs.kde.org/show_bug.cgi?id=427007 --- Comment #4 from Karl-Johan Karlsson --- It's now been a couple of weeks, including a Plasma upgrade to 5.20.0, and I have not seen night colour be permanently inhibited again. Using the plasmoid in the panel has worked the entire time. Maybe my original problem was a one-time bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427007] Add manual mode to night color
https://bugs.kde.org/show_bug.cgi?id=427007 --- Comment #2 from Karl-Johan Karlsson --- (In reply to Nate Graham from comment #1) > A better way is to set it to "Always on" in the KCM and then toggle it on > and off, you can either click on the system tray applet, or set and use a > global shortcut. Does the system tray applet bypass the inhibition system? Because that is not documented, and if not I don't see how that is different from what I said I'm already doing, which doesn't work because of the inhibition system. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427073] Some of Krita pop up window stuck in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=427073 --- Comment #6 from Johan Tri Handoyo --- "I don't see this happening with the 4.3.0 appimage on Ubuntu 20.04.1 with the MATE desktop. Did it happen with the 4.2.9 appimage and does it happen with every image you try with the 4.3.0 appimage?" Yes every image. I haven't upgrade my system to Ubuntu 20.04.1 yet, will try this on the weekend. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427073] Some of Krita pop up window stuck in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=427073 --- Comment #3 from Johan Tri Handoyo --- Krita Version: 4.3.0 Languages: en_US, en Hidpi: false Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.15.0-118-generic Pretty Productname: Ubuntu 18.04.5 LTS Product Type: ubuntu Product Version: 18.04 Desktop: ubuntu:GNOME OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 1080/PCIe/SSE2" Version: "4.6.0 NVIDIA 390.138" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 24102 Mb Number of Cores: 6 Swap Location: /tmp Current Settings Current Swap Location: /tmp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: DVI-D-0 Depth: 24 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: BNQ Model: BenQ T2200HD- Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427073] Some of Krita pop up window stuck in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=427073 --- Comment #2 from Johan Tri Handoyo --- Filter Mask and Filter Layer are both in the same problem. I'm using the appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427073] New: Some of Krita pop up window stuck in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=427073 Bug ID: 427073 Summary: Some of Krita pop up window stuck in the middle of the screen Product: krita Version: 4.3.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: johan...@gmail.com Target Milestone: --- Created attachment 131984 --> https://bugs.kde.org/attachment.cgi?id=131984=edit The screen shot. I hope the text and the picture are self explanatory SUMMARY STEPS TO REPRODUCE 1. Create a Filter Layer in Krita 4.3.0 for Ubuntu 18.05.5 2. The properties window freezes in the middle of the screen. 3. Not only that, the canvas underneath become darken a bit so its so hard to see the changes. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427007] New: Add manual mode to night color
https://bugs.kde.org/show_bug.cgi?id=427007 Bug ID: 427007 Summary: Add manual mode to night color Product: systemsettings Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: creideiki+kdeb...@ferretporn.se CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY I want to manually control when night color is activated. The closest I have been able to get is: 1. In System settings -> Display and monitor -> Night color, set activation time to "Always on". 2. In the panel, add a Night color control plasmoid. 3. Click the plasmoid when I want to turn night color on or off. This has worked so far, except for activating night color on every login, which is not a huge problem because it only happens after rebooting for kernel upgrades. However, tonight night color is inhibited by some unknown thing and forging magic cookies to "qdbus org.kde.KWin /ColorCorrect org.kde.kwin.ColorCorrect.uninhibit" doesn't enable it. I could continue fighting the inhibition system, or try adding a new DBus interface to show the inhibitor list, but instead of adding workarounds to workarounds I have a feature request: add a manual mode, which ignores the inhibitor system entirely and just features an on/off switch in the panel. Remembering the last status and re-applying that at login (instead of always activating it) would be a bonus. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 417848] Make applet activate Night Color when it's currently inactive
https://bugs.kde.org/show_bug.cgi?id=417848 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424025] Cannot render to mp4
https://bugs.kde.org/show_bug.cgi?id=424025 Johan Thelin changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from Johan Thelin --- It works after doing a dist-upgrade today (with the distro release). I suspect it has to do with the ffmpeg update made this week. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419662] The same message (i.e. calendar entry from calendar app 'etar') occours again and again until it was removed from the info bar in android
https://bugs.kde.org/show_bug.cgi?id=419662 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se --- Comment #4 from Karl-Johan Karlsson --- I'm seeing the same behaviour, also with the Etar calendar. I get a notification on my computer of a calendar event, close it on the computer but let it remain on the phone, and it returns on the computer a few seconds later. I'm not sure if it occurs with other notifications, since Etar is the only application I run on the phone which shows persistent notifications. SOFTWARE/OS VERSIONS Android: LineageOS 15.1 (Android 8.1) Linux/KDE Plasma: Gentoo unstable KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 KDE connect Android: 1.14.2 (from F-Droid) KDE connect PC: 20.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 422446] Suspending PC pauses phone
https://bugs.kde.org/show_bug.cgi?id=422446 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se --- Comment #1 from Karl-Johan Karlsson --- I'm seeing the same thing. Even worse, if the phone has a media player running but paused, it starts playing when I suspend my PC. SOFTWARE/OS VERSIONS Android: LineageOS 15.1 (Android 8.1) Linux/KDE Plasma: Gentoo unstable KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 KDE connect Android: 1.14.2 (from F-Droid) KDE connect PC: 20.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424025] New: Cannot render to mp4
https://bugs.kde.org/show_bug.cgi?id=424025 Bug ID: 424025 Summary: Cannot render to mp4 Product: kdenlive Version: 20.04.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: e8jo...@gmail.com Target Milestone: --- SUMMARY When trying to render to mp4, the UI claims that libx264 isn't available. When generating a mlt-script and hacking it, I can still render using libx264. STEPS TO REPRODUCE 1. Create video project 2. Select render 3. Attempt to render to mp4 OBSERVED RESULT "Unsupported video codec: libx264" EXPECTED RESULT No warnings or errors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian testing, dist-upgraded today (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION As mentioned, I can hack the mlt file and run it as a script, it just works. It would be nice to either have this fixed, or to being able to override this warning and just run melt even though kdenlive thinks there will be issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422083] Plastik window decorations don't render when OpenGL2ES backend is used
https://bugs.kde.org/show_bug.cgi?id=422083 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420678] Meta key not working in Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=420678 --- Comment #2 from Johan Zietsman --- Hi Nate Yes, "Alt+F1" is shown here. On Mon, Apr 27, 2020 at 11:45 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=420678 > > Nate Graham changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > Please go to [Right-click on Application Launcher] > Configure Application > Launcher > Keyboard Shortcuts. > > Do you see "Alt+F1" listed as the shortcut there? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420678] New: Meta key not working in Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=420678 Bug ID: 420678 Summary: Meta key not working in Kubuntu 20.04 Product: plasmashell Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: johan.ziets...@ex-mente.co.za CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I installed Kubuntu 20.04 on my Dell Vostro 5481 laptop today. The Meta key is not working. STEPS TO REPRODUCE 1. Sign into Kubuntu. 2. Press the Meta key. 3. Nothing happens. OBSERVED RESULT Nothing happens when I press the Meta key. EXPECTED RESULT I expect the Application Launcher menu to pop up when I press the Meta key. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411869] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=411869 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415296] Plasmashell crashes on startup
https://bugs.kde.org/show_bug.cgi?id=415296 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415686] Clicking on "Digital Clock" widget to display calendar crashes Plasma shell
https://bugs.kde.org/show_bug.cgi?id=415686 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415122] Plasma crashes on startup
https://bugs.kde.org/show_bug.cgi?id=415122 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415356] plasma crashes on startup
https://bugs.kde.org/show_bug.cgi?id=415356 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397677] Folder list shows all mails as unread
https://bugs.kde.org/show_bug.cgi?id=397677 Karl-Johan Karlsson changed: What|Removed |Added CC||creideiki+kdebugs@ferretpor ||n.se --- Comment #2 from Karl-Johan Karlsson --- I just had the same thing happen to me. KMail had been running fine for a couple of days, but suddenly started counting all mails as unread in the folder list and in the taskbar. This is on a Gentoo Linux system, running KDE apps 19.08.2, KDE frameworks 5.63.0, and Qt 5.13.2, fetching mail through IMAP from a Dovecot server to a PostgreSQL 11.5 database. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412629] New: Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists
https://bugs.kde.org/show_bug.cgi?id=412629 Bug ID: 412629 Summary: Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: creideiki+kdeb...@ferretporn.se Target Milestone: --- SUMMARY After upgrading PostgreSQL to version 12, and migrating the database according to https://userbase.kde.org/Akonadi/Postgres_update, trying to start Akonadi fails with: org.kde.pim.akonadiserver: Starting up the Akonadi Server... org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: "\nSql error: ERROR: column \"version\" of relation \"schemaversiontable\" already exists\n(42701) QPSQL: Unable to create query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: Unable to initialize database. waiting for server to shut down done server stopped This is the same error message as in bug 409234, but not the same bug, since that one is about Qt 5.13 and I am on Qt 5.12.5. I tried deleting $HOME/.local/share/akonadi/db_data/ and restarting Akonadi, which works, creating a new database. But I would prefer not having to re-download several GB of IMAP mailboxes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 19.08.1 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 400103] Feature Request remember last used directory in places (Save as dialog)
https://bugs.kde.org/show_bug.cgi?id=400103 Johan Mittermeier changed: What|Removed |Added CC||johan.mitterme...@gmx.de --- Comment #7 from Johan Mittermeier --- Oh yes, could we have that please? Just created an account to add a comment here. I was looking for a replacement for acroread and okular seems to be the only alternative that has almost all the features acroread had. But saving always starts in a tmp directory of my browser and I need many clicks to get to the directory I want to save downloads. If I click more pdfs that go in the same directory I have to do all these clicks over and over again :( Please add this feature! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #9 from johan --- So are these crash reports completely useless without debugging symbols? I can try to install symbols next but it seems to be a bit complicated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #8 from johan --- Created attachment 118384 --> https://bugs.kde.org/attachment.cgi?id=118384=edit crash dump information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #7 from johan --- Created attachment 118383 --> https://bugs.kde.org/attachment.cgi?id=118383=edit crash dump information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #6 from johan --- Created attachment 118382 --> https://bugs.kde.org/attachment.cgi?id=118382=edit crash dump information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 --- Comment #5 from johan --- Created attachment 118381 --> https://bugs.kde.org/attachment.cgi?id=118381=edit crash dump information -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403133] Plenty of flickering and graphical glitches during and after startup if compositing is enabled
https://bugs.kde.org/show_bug.cgi?id=403133 --- Comment #2 from johan --- After some updates, this does not occur anymore. I don't know if it was due to a KDE or Nouveau bug but it's gone anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 johan changed: What|Removed |Added Attachment #118203|0 |1 is obsolete|| --- Comment #3 from johan --- Created attachment 118231 --> https://bugs.kde.org/attachment.cgi?id=118231=edit dmesg and non-truncated core dump information New core dump information and some messages from dmesg attached -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404571] New: Complete desktop crash when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=404571 Bug ID: 404571 Summary: Complete desktop crash when Wayland is used Product: kwin Version: 5.15.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kurko2...@gmail.com Target Milestone: --- Flags: Wayland+, nouveau+ Created attachment 118203 --> https://bugs.kde.org/attachment.cgi?id=118203=edit dmesg and core dump information Sometimes when using KDE desktop with Wayland, the desktop crashes completely. This occurs randomly. The system typically returns to the SDDM login screen. Bug #403653 is related. Crash information of KWin was requested. A file is attached, containing some information from dmesg and coredumpctl. For some reason the core dump is truncated. I'll try to provide a complete one later. No other core dumps were created when this crash occurred. System information: Arch Linux, x86-64, kernel version: 4.20.8-arch1-1-ARCH KWin package version: 5.15.0-1 GPU: Nvidia GTX 980 Ti Driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze Please note that render loop is set to Basic in "kcmshell5 qtquicksettings" as suggested in the comments of bug #396614 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403970] Partition manager crashes just by browsing menus
https://bugs.kde.org/show_bug.cgi?id=403970 --- Comment #13 from Johan Klokkhammer Helsing --- > If you are asking whether I have tried building qt with it, then no, I have > not. TBH I don't even know how. Yeah. Sorry, I just thought "resolved upstream" meant that you knew it was now fixed at the Qt level. I see that it's just means that it's resolved as far as you're concerned and something that needs to be fixed upstream. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #7 from Johan Klokkhammer Helsing --- Ah, my bad. I was searching the tracker for wayland changes, and somehow this showed up, and I didn't really check the description itself. I guess you can probably disregard everything I said :/ Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 --- Comment #5 from Johan Klokkhammer Helsing --- > you can see here the files that have changed in qt5 5.12.1 version : https://wiki.qt.io/Qt_5.12.1_Change_Files I know, I wrote that file ;) Anyways, I was asking because I asked the archlinux maintainer to cherry-pick a patch that fixed a freeze which resulted in version 5.12.0-2, however it was reverted in 5.12.0-3, due to some clients using 100% cpu. But if you used 5.12.0-1, 5.12.1-1, then that fix is unrelated. Also, it would probably be useful for whoever is going to debug this if you could attach a log with WAYLAND_DEBUG=1 set in the environment. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 394004] Special character rendered overly small when on wayland
https://bugs.kde.org/show_bug.cgi?id=394004 --- Comment #6 from Johan Klokkhammer Helsing --- So likely either a Qt bug and/or something weird with your fontconfig... It works on X? Could you file a bug at bugreports.qt.io? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 394004] Special character rendered overly small when on wayland
https://bugs.kde.org/show_bug.cgi?id=394004
--- Comment #4 from Johan Klokkhammer Helsing ---
Weird.
Can you try running the following in qmlscene?
import QtQuick 2.6
Column {
TextEdit {
id: size
text: "32"
}
Text {
font.pixelSize: size.text
text: "Smileys Symbols ㋡ ㋛ ☺ ☹ ☻ 〠 シ ッ ツ ヅ Ü 〲 〴 ϡ ﭢ ت ⍡ ⍢ ⍣ ⍤ ⍥ ⍨ ⍩ ὃ
ὕ ὣ Ѷ Ӫ ӫ "
}
Text {
font.pointSize: size.text
text: "Smileys Symbols ㋡ ㋛ ☺ ☹ ☻ 〠 シ ッ ツ ヅ Ü 〲 〴 ϡ ﭢ ت ⍡ ⍢ ⍣ ⍤ ⍥ ⍨ ⍩ ὃ
ὕ ὣ Ѷ Ӫ ӫ "
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[policykit-kde-agent-1] [Bug 403832] Password prompts appears on random positions on Wayland
https://bugs.kde.org/show_bug.cgi?id=403832 Johan Klokkhammer Helsing changed: What|Removed |Added CC||johan.hels...@qt.io --- Comment #1 from Johan Klokkhammer Helsing --- @mthw0: At least the regular xdg-shell doesn't allow you to specify a position for toplevel windows, only relative positions for popups (menus etc). Could perhaps be done through some protocol extension? Not sure if anything like this exists... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 370518] Include acd10cd393abe04a8fd6fe3ab14055e09c85bc15 in QtWayland
https://bugs.kde.org/show_bug.cgi?id=370518 Johan Klokkhammer Helsing changed: What|Removed |Added CC||johan.hels...@qt.io --- Comment #2 from Johan Klokkhammer Helsing --- @Alexander Mentyu: The patch has been part of Qt since 5.8.0 so if you're using a newer version than that, then you already have the patch and this can be closed. Issue in Qt bug tracker: https://bugreports.qt.io/browse/QTBUG-56475 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 394004] Special character rendered overly small when on wayland
https://bugs.kde.org/show_bug.cgi?id=394004 Johan Klokkhammer Helsing changed: What|Removed |Added CC||johan.hels...@qt.io --- Comment #2 from Johan Klokkhammer Helsing --- I can't reproduce this with Qt 5.12.1 and konsole version 18.12.1. Does setting or clearing QT_WAYLAND_FORCE_DPI do any difference for you (try setting it to 96 or physical)? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403970] Partition manager crashes just by browsing menus
https://bugs.kde.org/show_bug.cgi?id=403970 Johan Klokkhammer Helsing changed: What|Removed |Added CC||johan.hels...@qt.io --- Comment #11 from Johan Klokkhammer Helsing --- @mthw0: The dropping of frames on gnome-shell is likely this bug: https://gitlab.gnome.org/GNOME/mutter/issues/199 Also, do you know which patch fixed it for you? Perhaps this one? https://codereview.qt-project.org/#/c/252117/ Popups on Qt Wayland are a mess. There are restrictions in the xdg-shell protocol that match really poorly to the APIs we provide in Qt. In this case, it is probably the restriction that a new grabbing popup has to be the child of the current grabbing popup, combined with closing and opening sometimes happening in the opposite order. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 403978] oxygen theme incompatible with qt5 5.12.1-1 libs
https://bugs.kde.org/show_bug.cgi?id=403978 Johan Klokkhammer Helsing changed: What|Removed |Added CC||johan.hels...@qt.io --- Comment #2 from Johan Klokkhammer Helsing --- Potomac: Do you know the exact Qt version that worked for you. In particular, is there a difference between 5.12.0-1 and 5.12.0-2? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403653] Random, complete desktop crashes when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=403653 --- Comment #1 from johan --- Created attachment 117687 --> https://bugs.kde.org/attachment.cgi?id=117687=edit Core dump information Another crash. Again only drkonqi appeared in core dumps. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 403654] Konversation crashed on shutdown
https://bugs.kde.org/show_bug.cgi?id=403654 --- Comment #1 from johan --- Created attachment 117686 --> https://bugs.kde.org/attachment.cgi?id=117686=edit Core dump information -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 403654] New: Konversation crashed on shutdown
https://bugs.kde.org/show_bug.cgi?id=403654 Bug ID: 403654 Summary: Konversation crashed on shutdown Product: konversation Version: 1.7.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: kurko2...@gmail.com Target Milestone: --- Created attachment 117677 --> https://bugs.kde.org/attachment.cgi?id=117677=edit report from drkonqi When Konversation is closed, it may crash. A report from drkonqi is attached. This crash occurred after clicking "yes" in the prompt that appeared when attempting to closing Konversation. This occurred when Wayland was used, but I don't know if Wayland is related to the crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403653] New: Random, complete desktop crashes when Wayland is used
https://bugs.kde.org/show_bug.cgi?id=403653 Bug ID: 403653 Summary: Random, complete desktop crashes when Wayland is used Product: plasmashell Version: 5.14.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: kurko2...@gmail.com Target Milestone: 1.0 Flags: Wayland+ Created attachment 117676 --> https://bugs.kde.org/attachment.cgi?id=117676=edit dmesg and coredump information (I'm not sure if Plasmashell is the correct category for this - please change it if needed.) When KDE desktop is used with Wayland, the desktop sometimes crashes completely and returns to the SDDM login screen. Most processes of the user are also terminated when this happens. This occurs randomly and not very often. The desktop may work for hours before it crashes. The crash may occur at any moment. I haven't noticed any specific actions that lead to crash. Please note that render loop is set to Basic in "kcmshell5 qtquicksettings" as suggested in the comments of bug #396614 Some dmesg and core dump information is attached. This time only drkonqi appeared in the core dumps. Sometimes other processes appear as well. System information: Arch Linux, x86-64, kernel version (uname -r): 4.20.3-arch1-1-ARCH Plasma package versions: 5.14.5-2 GPU: Nvidia GTX 980 Ti Driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #6 from johan --- I changed the render loop setting to basic and it seems to be more stable indeed. I haven't experienced any crashes yet, but Plasma may sometimes freeze when trying to shut down the computer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403133] New: Plenty of flickering and graphical glitches during and after startup if compositing is enabled
https://bugs.kde.org/show_bug.cgi?id=403133 Bug ID: 403133 Summary: Plenty of flickering and graphical glitches during and after startup if compositing is enabled Product: plasmashell Version: 5.14.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kurko2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Flags: X11+ When KDE desktop is being started, there's a lot of flicker and other glitches. After the startup is completed, the desktop may look normal or not. But if you move mouse over the task bar, use the applications menu, or start an application, the flickering continues. The startup splash screen often appears when this problem occurs. A workaround is to disable compositing. When compositing is off, this problem does not occur. Also, this problem does not occur with Wayland. Here's a video showing this problem: https://mega.nz/#!4pQw1AgR!Ujblms_CSSIrczLKpRapoLBiZGrM8xwXJ3JZm7-1EG8 Compositing options: Enable compositor on startup: yes Animation speed: medium Scale method: Accurate Rendering backend: OpenGL 2.0 Tearing prevention: Full screen repaints Keep window thumbnails: Only for shown windows Allow applications to block compositing: yes System information: Arch Linux, x86-64, kernel version: 4.20.0-arch1-1-ARCH Plasmashell version: 5.14.5 (also occurred with 5.14.4) GPU: Nvidia GTX 980 Ti GPU driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #4 from johan --- Another crash report attached. Plasmashell version 5.14.5. Plasmashell crashed when I used the system menu/applications menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 johan changed: What|Removed |Added Attachment #117410|Plasmashell crash report|Crash report, plasmashell description|from the KDE crash reporter |5.14.4, using the system ||menu (shutdown submenu) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #3 from johan --- Created attachment 117416 --> https://bugs.kde.org/attachment.cgi?id=117416=edit Crash report, plasmashell 5.14.5, using the system menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #2 from johan --- Plasmashell version 5.14.4 crashed today when I had the applications menu open and was about to open the shutdown menu. It restarted automatically and the crash reporter appeared. A log is attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 --- Comment #1 from johan --- Created attachment 117410 --> https://bugs.kde.org/attachment.cgi?id=117410=edit Plasmashell crash report from the KDE crash reporter -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402230] Messed up special character (──)
https://bugs.kde.org/show_bug.cgi?id=402230 Johan changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Johan --- Checking that option seems to fix it, thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380384] Plasma-Wayland completely freezing on Nouveau driver
https://bugs.kde.org/show_bug.cgi?id=380384 johan changed: What|Removed |Added CC||kurko2...@gmail.com --- Comment #11 from johan --- Could bug #396614 be related? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 358231] desktop locks up when moving files
https://bugs.kde.org/show_bug.cgi?id=358231 johan changed: What|Removed |Added CC||kurko2...@gmail.com --- Comment #19 from johan --- I can confirm this on Arch Linux. Moving as few as 10 small files using Dolphin can cause the desktop to freeze for 10 seconds or so. plasma-desktop package is 5.13.5-1 and dolphin is 18.08.1-2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396614] New: Plasmashell + Wayland - frequent hangs/crashes when opening start menu
https://bugs.kde.org/show_bug.cgi?id=396614 Bug ID: 396614 Summary: Plasmashell + Wayland - frequent hangs/crashes when opening start menu Product: plasmashell Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: kurko2...@gmail.com Target Milestone: 1.0 Flags: Wayland+ Created attachment 113990 --> https://bugs.kde.org/attachment.cgi?id=113990=edit Crash report from KDE crash reporter When opening or using the applications menu/start menu when using Wayland, Plasmashell often hangs or crashes. This can happen in several different ways but I'm not sure if these are related: 1) Plasmashell crashes and restarts, and the KDE bug reporter is started. A crash report is attached. 2) Plasmashell freezes and stops working (CPU usage goes to 100% of 1 core) but keyboard and mouse still work and can be used to switch between tasks or to access text console. 3) Plasmashell freezes and keyboard and mouse are frozen too. Only kernel SysRq keys can be used to reboot the computer or sometimes to recover from the situation without rebooting. I think this problem, and especially nr. 3), happens more often if you move the mouse over the menu immediately after clicking the menu icon, i.e. before the menu opening effect has finished. Or, move the mouse *very* fast over the opened menu. This does not seem to happen when X11 is used. System information: Arch Linux, x86-64, kernel version (uname -a): 4.17.5-1-ARCH Plasma package versions: 5.13.3-1 GPU: Nvidia GTX 980 Ti Driver: Nouveau KDE workspace themes: --Look and feel: Oxygen --Desktop theme: Oxygen --Cursor theme: Oxygen white --Splash screen: Breeze -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 395347] view email kontact chrashed
https://bugs.kde.org/show_bug.cgi?id=395347 --- Comment #3 from Johan van de Sande --- I added more info installed the dbg files and included the text as a comment :) thanks Johan Op do 14 jun. 2018 om 10:27 schreef Christophe Giboudeaux < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=395347 > > Christophe Giboudeaux changed: > >What|Removed |Added > > > Resolution|--- |BACKTRACE > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #2 from Christophe Giboudeaux --- > Yes, looks like /usr/share/kubuntu-notification-helper/whoopsie-upload-all > is > interfering, preventing drkonqi to appear. > > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports > contains information to provide useful backtraces. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 394864] repeatly crash using contact (kmail)
https://bugs.kde.org/show_bug.cgi?id=394864 --- Comment #1 from Johan van de Sande --- Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0b120d8b80 (LWP 13827))] Thread 31 (Thread 0x7f09ab217700 (LWP 13939)): #0 0x7f0b0a805ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f09ab2167e0, expected=0, futex_word=0x7f0ac00048f4) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f0b0a805ed9 in __pthread_cond_wait_common (abstime=0x7f09ab216880, mutex=0x7f0ac00048a0, cond=0x7f0ac00048c8) at pthread_cond_wait.c:533 #2 0x7f0b0a805ed9 in __pthread_cond_timedwait (cond=0x7f0ac00048c8, mutex=0x7f0ac00048a0, abstime=0x7f09ab216880) at pthread_cond_wait.c:667 #3 0x7f0aff827652 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0aff7fd799 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0aff7fdcfb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0aff7f65eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0b0a7ff6db in start_thread (arg=0x7f09ab217700) at pthread_create.c:463 #8 0x7f0b0ea8188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7f09b1e8a700 (LWP 13899)): #0 0x7f0b087c4cd9 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0b0877efc6 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0b0877f4c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0b0877f54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0b0f5da90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0b0f57f9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0b0f39e22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0b0f3a316d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0b0a7ff6db in start_thread (arg=0x7f09b1e8a700) at pthread_create.c:463 #9 0x7f0b0ea8188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f09b3183700 (LWP 13889)): #0 0x7f0b0a8059f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55db32e2d808) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0b0a8059f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55db32e2d7b8, cond=0x55db32e2d7e0) at pthread_cond_wait.c:502 #2 0x7f0b0a8059f3 in __pthread_cond_wait (cond=0x55db32e2d7e0, mutex=0x55db32e2d7b8) at pthread_cond_wait.c:655 #3 0x7f0aff7f8c95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0aff7f9177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0aff7f9f11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0aff7f65eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0b0a7ff6db in start_thread (arg=0x7f09b3183700) at pthread_create.c:463 #8 0x7f0b0ea8188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f09bb82a700 (LWP 13872)): #0 0x7f0b0a8059f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55db332c1b20) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0b0a8059f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55db332c1ad0, cond=0x55db332c1af8) at pthread_cond_wait.c:502 #2 0x7f0b0a8059f3 in __pthread_cond_wait (cond=0x55db332c1af8, mutex=0x55db332c1ad0) at pthread_cond_wait.c:655 #3 0x7f0b0f3a459b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0b0f39cc0b in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f09c09f580c in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #6 0x7f0b0f3a316d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0b0a7ff6db in start_thread (arg=0x7f09bb82a700) at pthread_create.c:463 #8 0x7f0b0ea8188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f09c184c700 (LWP 13870)): #0 0x7f0b0ea74bf9 in __GI___poll (fds=0x7f09bc0049b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0b0877f439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0b0877f54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0b0f5da90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0b0f57f9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0b0f39e22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0b0f3a316d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f
[kontact] [Bug 395347] view email kontact chrashed
https://bugs.kde.org/show_bug.cgi?id=395347 Johan van de Sande changed: What|Removed |Added Latest Commit||version 5.7.3 Component|general |mail Version|unspecified |5.7.2 --- Comment #1 from Johan van de Sande --- I believe there is a big problem here -- You are receiving this mail because: You are watching all bug changes.
