[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Dan changed: What|Removed |Added CC||dcoffey...@gmail.com --- Comment #46 from Dan --- Would be very helpful if this was added -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 468140] New: Songs in a playlist created automatically from files in folder don't play sporadically, can be only fixed by scrolling forward.
https://bugs.kde.org/show_bug.cgi?id=468140 Bug ID: 468140 Summary: Songs in a playlist created automatically from files in folder don't play sporadically, can be only fixed by scrolling forward. Classification: Applications Product: Haruna Version: 0.10.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: ors...@li.ru Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. double click on an audio file in the directory which creates a playlist automatically in haruna 2. switch songs by clicking or just leave it play automatically 3. OBSERVED RESULT some songs don't play automatically 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.
[Haruna] [Bug 468140] Songs in a playlist created automatically from files in folder don't play sporadically, can be only fixed by scrolling forward.
https://bugs.kde.org/show_bug.cgi?id=468140 --- Comment #2 from Dan --- I have changed the following options from default as far as I remember: open last played file on startup, seek to last playback position. remember last playlist state and auto load videos from same folder. this is really weird problem. looks like when I don't use my wireless headphones, the bug doesn't appear. to describe it a little further, some songs start with a big delay, about 3-5 seconds, some don't start at all, and if I let it be for a minute or more, it eventually jumps to the playing next song. in some cases I noticed that the song actually starts, but only first few milliseconds of it and it's stuck in a loop, as if something doesn't let it play. and what's weird is that other songs play normally. the bug doesn't happen in celluloid. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468741] New: [Spectacle suggestion] Kpipewire as an optional dependency
https://bugs.kde.org/show_bug.cgi?id=468741 Bug ID: 468741 Summary: [Spectacle suggestion] Kpipewire as an optional dependency Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: da...@protonmail.com CC: k...@david-redondo.de Target Milestone: --- Since Spectacle 23.04, Kpipewire is a required dependency. Would it be possible to turn Kpipewire into a optional dependency instead? I ask it because I don't use Pipewire and I don't need this feature in Spectacle. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 469395] New: Reddit RSS: "error occurred while parsing element" on line 1
https://bugs.kde.org/show_bug.cgi?id=469395 Bug ID: 469395 Summary: Reddit RSS: "error occurred while parsing element" on line 1 Classification: Applications Product: akregator Version: 5.23.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-b...@kde.org Reporter: da...@protonmail.com Target Milestone: --- STEPS TO REPRODUCE 1. https://www.reddit.com/r/kde/.rss OBSERVED RESULT Akregator returns in the log: "error occurred while parsing element" on line 1 EXPECTED RESULT It should get the feed without error. This error started to happen 5 days ago, so I don't know if Reddit changed something that broke Akregator feed parsing code or something else. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 469395] Reddit RSS: "error occurred while parsing element" on line 1
https://bugs.kde.org/show_bug.cgi?id=469395 Dan changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Dan --- (In reply to Laurent Montel from comment #1) > Work fine here. So I'll investigate a bit more. Thanks for replying! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460404] New: [Regression]: Kwin 5.26.0 uses software renderer instead of GLX
https://bugs.kde.org/show_bug.cgi?id=460404 Bug ID: 460404 Summary: [Regression]: Kwin 5.26.0 uses software renderer instead of GLX Classification: Plasma Product: kwin Version: git-stable-Plasma/5.26 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: glx Assignee: kwin-bugs-n...@kde.org Reporter: da...@protonmail.com Target Milestone: --- KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.5 Kernel Version: 6.0.1 (64-bit) Graphics Platform: X11 Graphics Processor: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 With Kwin 5.25.5, the compositor works fine with GLX, but after upgrading to 5.26.0, Kwin will use only the software renderer and warn about degraded performance. So it's probably a regression, since it was working with 5.25.5 and nothing was changed, except for the Plasma upgrade. Any hints? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 460414] New: Show URL when hovering mouse over link
https://bugs.kde.org/show_bug.cgi?id=460414 Bug ID: 460414 Summary: Show URL when hovering mouse over link Classification: Applications Product: akregator Version: GIT (master) Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: da...@protonmail.com Target Milestone: --- I upgraded Akregator and I noticed it won't show anymore the URL when I hover the mouse over the link. Is there a way to restore this feature? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 460414] Show URL when hovering mouse over link
https://bugs.kde.org/show_bug.cgi?id=460414 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Dan --- Forget it. I edited the ~/.config/akregatorrc file and I noticed StatusBar was disabled. So: StatusBar=Enabled fixed it. I just don't understand why it was disabled and there's no option in the menu to enable it... Anyway, I'll change this bug to NOT A BUG... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460404] [Regression]: Kwin 5.26.0 uses software renderer instead of GLX
https://bugs.kde.org/show_bug.cgi?id=460404 --- Comment #3 from Dan --- (In reply to Arjen Hiemstra from comment #2) > instead of just disabling it once. Also, does EGL work correctly? Hi Arjen, there's no LastFailureTimestamp in the group Compositing. In my case, EGL doesn't work because of the bug 456372 I reported some time ago, so I'm stuck with GLX. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460404] [Regression]: Kwin 5.26.0 uses software renderer instead of GLX
https://bugs.kde.org/show_bug.cgi?id=460404 --- Comment #8 from Dan --- (In reply to Arjen Hiemstra from comment #6) > Can either of you share the console output of KWin? I'm curious if it > mentions any errors. My Kwin output: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 520.56.06 OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 520.56.6 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.21.1 Linux kernel version: 6.0.2 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no QObject::killTimer: Timers cannot be stopped from another thread QObject::~QObject: Timers cannot be stopped from another thread kf.kirigami: Failed to find a Kirigami platform plugin file:///usr/kde5.26/lib/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" Application::crashHandler() called with signal 11; recent crashes: 2 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kwin_x11 path = /usr/kde5.26/bin pid = 15015 KCrash: Arguments: /usr/kde5.26/bin/kwin_x11 --crashes 1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456372] kwin_x11 (EGL): Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()"
https://bugs.kde.org/show_bug.cgi?id=456372 --- Comment #2 from Dan --- (In reply to Arjen Hiemstra from comment #1) > Note that "KWIN_COMPOSE=O2ES" means you're forcing KWin into OpenGLES > rendering, which happens to also use EGL as platform layer but has a lot > more impact than just the platform layer. The correct environment variable > for selecting EGL is `KWIN_OPENGL_INTERFACE=egl`. I tried just with "KWIN_OPENGL_INTERFACE=egl`" and I got the same output: kwin_core: Forcing EGL native interface through environment variable kwin_core: Attempting to load the OpenGL scene kwin_platform_x11_standalone: Global share context format: QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions|ResetNotification), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 0, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) kwin_scene_opengl: Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()" kwin_core: Starting without compositing... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482628] Allow disabling toolBar accelerator
https://bugs.kde.org/show_bug.cgi?id=482628 dan changed: What|Removed |Added CC||dda...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482628] Allow disabling toolBar accelerator
https://bugs.kde.org/show_bug.cgi?id=482628 --- Comment #12 from dan --- how did this get by testing? do most KDE/Plasma users really not use the terminal at all? I feel like Alt+F is a very commonly used shortcut. I don't get why so many terminal emulatorss have so many shortcuts enabled by default at all to be honest. Maybe a few ctrl+alt+ shortcuts, ok, but so many TUI apps, like htop, get shortcuts like F1 thru F10 stolen by the terminal emulator. It would be nice if the toolBar accelerators were somehow more customizable, similar to the general shortcuts, but I would happily settle for at least just a checkbox to disable them in general. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 405886] opening/comparing large text files is slow (80MB)
https://bugs.kde.org/show_bug.cgi?id=405886 Dan changed: What|Removed |Added CC||roze...@volny.cz --- Comment #3 from Dan --- As for the version kdiff3 1.10.5 (64 bit), the comparison of large files is still far too slow. Whak diff can make in seconds, kdiff makes in minutes (or more). I understand that it has low priority (kdiff3 works nicely after all), but improvement in this area would be highly appreciated. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] New: Sorting os very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Bug ID: 478250 Summary: Sorting os very slow Classification: Applications Product: kate Version: 23.04.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: scripting Assignee: kwrite-bugs-n...@kde.org Reporter: roze...@volny.cz Target Milestone: --- SUMMARY *** The sorting plugins: Tool->Scripts->Editing->Sort Selected Text ... ...-> Remove Duplicates and sort ...) are *very* slow. What sort can make is seconds, kate/kwrite need hour(s) to achieve. *** STEPS TO REPRODUCE 1. Create very large text file (50MB+) 2. Make it sort (and unique) 3. Compare times with `sort -u` on the same file OBSERVED RESULT Kate is not responding for a very long time EXPECTED RESULT *Much* faster result SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.7 KDE Frameworks Version 5.108.0 Qt Version: 5.15.10 (built against 5.15.10) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Dan changed: What|Removed |Added Summary|Sorting os very slow|Sorting is very slow -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 --- Comment #2 from Dan --- Hi, thanks for the reaction. Will try in a few days (need update but not interrupt the work ...) Dan. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456372] kwin_x11 (EGL): Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()"
https://bugs.kde.org/show_bug.cgi?id=456372 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #5 from Dan --- Clsoing this one, since the issue doesn't happen with Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 456843] [Feature request]: skip summary when entering a feed and go directly to next unread message
https://bugs.kde.org/show_bug.cgi?id=456843 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from Dan --- Closing this one, since nobody replied and I don't use Akregator anymore. -- You are receiving this mail because: You are watching all bug changes.
[massif-visualizer] [Bug 479434] Snap of massif-visualizer is not configured properly with dot/graphviz
https://bugs.kde.org/show_bug.cgi?id=479434 --- Comment #4 from Dan --- Ping. Who is the person to responsible for maintaining official KDE nap packages https://snapcraft.io/publisher/kde ? Could this issue be reassigned to them? -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 482594] Screen sharing/recording fails with error message "Failed to connect PipeWire context"
https://bugs.kde.org/show_bug.cgi?id=482594 Dan changed: What|Removed |Added CC||da...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[massif-visualizer] [Bug 479434] Snap of massif-visualizer is not configured properly with dot/graphviz
https://bugs.kde.org/show_bug.cgi?id=479434 --- Comment #3 from Dan --- (In reply to Milian Wolff from comment #2) > and I'm not maintaining any snap packages, please reach out to your > distribution or packager Who is maintaining https://snapcraft.io/massif-visualizer ? It says it's an official KDE account and "Contact publisher" leads to https://kde.org/support/ which leads to a bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455766] New: Brush changes Pencil-6 Quick Shade everytime i use pen (Parblo Ninos M)
https://bugs.kde.org/show_bug.cgi?id=455766 Bug ID: 455766 Summary: Brush changes Pencil-6 Quick Shade everytime i use pen (Parblo Ninos M) Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: mr.danp...@gmail.com Target Milestone: --- Flags: version_5_applied+, Backport-, Brainstorm-, corner_case-, Translation_missing-, Usability+ Created attachment 150030 --> https://bugs.kde.org/attachment.cgi?id=150030&action=edit I start program, try to change brush, it changes, pick my pen and start drawing, brush changes to Pencil-6 Quick Shade, try to change brush again, starts drawing, Brush changes to Pencil-6 Quick Shade SUMMARY Brush changes to Pencil-6 Quick Shade everytime i use pen (Parblo Ninos M) NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Change brush to any brush 2. Use my pen to draw something with tablet (Parbolo Ninos M) 3. Start Drawing OBSERVED RESULT Brush changes to "Pencil-6 Quick Shade" and drawing EXPECTED RESULT Drawing with other brush SOFTWARE/OS VERSIONS Windows: Windows 10 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.
[amarok] [Bug 288148] Possible Senzari support?
https://bugs.kde.org/show_bug.cgi?id=288148 Dan changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 338283] Rdio.com support (with API)
https://bugs.kde.org/show_bug.cgi?id=338283 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 288303] Feature: allow some contacts to see me when I'm invisible
https://bugs.kde.org/show_bug.cgi?id=288303 Dan changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 419729] Link from tweet time opens wrong URL (reproducible)
https://bugs.kde.org/show_bug.cgi?id=419729 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 456101] New: 'org.kde.KSplash' failed: Process org.kde.KSplash received signal 1
https://bugs.kde.org/show_bug.cgi?id=456101 Bug ID: 456101 Summary: 'org.kde.KSplash' failed: Process org.kde.KSplash received signal 1 Product: ksplash Version: 5.25.2 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: da...@protonmail.com Target Milestone: --- Plasma starts perfectly when using X11, but when I try to use Wayland it fails with the following: dbus-daemon[760]: [session uid=501 pid=760] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=501 pid=761 comm="/usr/local/kde5/bin/startplasma-wayland") No backend specified through command line argument, trying auto resolution dbus-daemon[760]: [session uid=501 pid=760] Reloaded configuration dbus-daemon[760]: [session uid=501 pid=760] Reloaded configuration dbus-daemon[760]: [session uid=501 pid=760] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash received signal 1 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash qt.qpa.wayland: Creating a fake screen in order for Qt not to crash The Wayland connection broke. Did the Wayland compositor die? The Wayland connection broke. Did the Wayland compositor die? kdeinit5: Communication error with launcher. Exiting! Operating System: Linux KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 Kernel Version: 5.18.7 (64-bit) Graphics Processor: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 Any idea how I can debug this? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456337] New: kwin_wayland stuck at black screen
https://bugs.kde.org/show_bug.cgi?id=456337 Bug ID: 456337 Summary: kwin_wayland stuck at black screen Product: kwin Version: 5.25.2 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: da...@protonmail.com Target Milestone: --- When I try to use kwin_wayland 5.25.2, it stalls with a black screen. Is there a better way to debug this? I tested with Weston on the same laptop and Weston works perfectly, so it's probably a bug in Kwin. Operating System: Linux KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.9 (64-bit) Graphics Processor: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 kwin_wayland_drm: drmModeAddFB2WithModifiers is supported on GPU "/dev/dri/card1" kwin_wayland_drm: Using Atomic Mode Setting on gpu "/dev/dri/card1" kwin_wayland_drm: Number of planes on GPU "/dev/dri/card1" : 12 kwin_wayland_drm: Plane 33 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=251658240, "SRC_H"=141557760, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=3840, "CRTC_H"=2160, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=34 kwin_wayland_drm: Plane 36 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=16777216, "SRC_H"=16777216, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=256, "CRTC_H"=256, "FB_ID"=0, "CRTC_ID"=0, "rotation" not found, "IN_FORMATS"=37 kwin_wayland_drm: Plane 41 has properties "type"="Overlay", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=42 kwin_wayland_drm: Plane 46 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=47 kwin_wayland_drm: Plane 49 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation" not found, "IN_FORMATS"=50 kwin_wayland_drm: Plane 54 has properties "type"="Overlay", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=55 kwin_wayland_drm: Plane 59 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=60 kwin_wayland_drm: Plane 62 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation" not found, "IN_FORMATS"=63 kwin_wayland_drm: Plane 67 has properties "type"="Overlay", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=68 kwin_wayland_drm: Plane 72 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=73 kwin_wayland_drm: Plane 75 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation" not found, "IN_FORMATS"=76 kwin_wayland_drm: Plane 80 has properties "type"="Overlay", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=81 kwin_wayland_drm: Crtc 40 has properties "MODE_ID"=0, "ACTIVE"=0, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" not found kwin_wayland_drm: Crtc 53 has properties "MODE_ID"=0, "ACTIVE"=0, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" not found kwin_wayland_drm: Crtc 66 has properties "MODE_ID"=0, "ACTIVE"=0, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" not found kwin_wayland_drm: Crtc 79 has properties "MODE_ID"=0, "ACTIVE"=0, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" not found kwin_xkbcommon: XKB: created compose table from locale en_US.UTF-8 with path /usr/xorg/share/X11/locale/en_US.UTF-8/Compose kf.globalaccel.kglobalacceld: Failed to register service org.kde.kglobalaccel kwin_core: Init of kglobalaccel failed kwin_core: Compositing forced to OpenGL mode by environment variable kwin_core: Attempting to load the OpenGL scene kwin_scene_opengl: Egl Initialize succeeded kwin_scene_opengl: EGL version: 1 . 5 kwin_scene_opengl: Created EGL context with attributes: Version requested: true Version:3.1 Robust: true Reset on video memory purge:true Forward compatible: false Core profile: false Compatibility profile: false High priority: true kwin_scene_opengl
[kwin] [Bug 456337] "kwin_wayland_drm: Failed to create gamma blob! Invalid argument"
https://bugs.kde.org/show_bug.cgi?id=456337 Dan changed: What|Removed |Added Summary|kwin_wayland stuck at black |"kwin_wayland_drm: Failed |screen |to create gamma blob! ||Invalid argument" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456337] "kwin_wayland_drm: Failed to create gamma blob! Invalid argument"
https://bugs.kde.org/show_bug.cgi?id=456337 --- Comment #1 from Dan --- Maybe it's because of the following line? kwin_wayland_drm: Failed to create gamma blob! Invalid argument -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456372] New: kwin_x11 (EGL): Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()"
https://bugs.kde.org/show_bug.cgi?id=456372 Bug ID: 456372 Summary: kwin_x11 (EGL): Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()" Product: kwin Version: 5.25.2 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: egl Assignee: kwin-bugs-n...@kde.org Reporter: da...@protonmail.com Target Milestone: --- kwin_x11 works perfectly with KWIN_COMPOSE=O2 (GLX) and everything works, but if I use KWIN_COMPOSE=O2ES (EGL), it fails with "Invalid QOpenGLContext::globalShareContext()". Operating System: Linux KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.9 (64-bit) Graphics Processor: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 kwin_core: Compositing forced to OpenGL mode by environment variable kwin_core: Forcing EGL native interface as OpenGL ES requested through KWIN_COMPOSE environment variable. kwin_core: Attempting to load the OpenGL scene kwin_platform_x11_standalone: Global share context format: QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions|ResetNotification), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 0, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) kwin_scene_opengl: Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()" kwin_core: Starting without compositing... Any idea? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456337] "kwin_wayland_drm: Failed to create gamma blob! Invalid argument"
https://bugs.kde.org/show_bug.cgi?id=456337 --- Comment #3 from Dan --- (In reply to Zamundaaa from comment #2) > I see that you force OpenGl 2.0. Can you try again without any kwin specific > environment variables? Yes, here is the log removing KWIN_COMPOSE=O2: kwin_wayland_drm: drmModeAddFB2WithModifiers is supported on GPU "/dev/dri/card1" kwin_wayland_drm: Using Atomic Mode Setting on gpu "/dev/dri/card1" kwin_wayland_drm: Number of planes on GPU "/dev/dri/card1" : 12 kwin_wayland_drm: Plane 33 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=34 kwin_wayland_drm: Plane 36 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation" not found, "IN_FORMATS"=37 kwin_wayland_drm: Plane 41 has properties "type"="Overlay", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=42 kwin_wayland_drm: Plane 46 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=47 kwin_wayland_drm: Plane 49 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation" not found, "IN_FORMATS"=50 kwin_wayland_drm: Plane 54 has properties "type"="Overlay", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=55 kwin_wayland_drm: Plane 59 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=60 kwin_wayland_drm: Plane 62 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation" not found, "IN_FORMATS"=63 kwin_wayland_drm: Plane 67 has properties "type"="Overlay", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=68 kwin_wayland_drm: Plane 72 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=73 kwin_wayland_drm: Plane 75 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation" not found, "IN_FORMATS"=76 kwin_wayland_drm: Plane 80 has properties "type"="Overlay", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=81 kwin_wayland_drm: Crtc 40 has properties "MODE_ID"=0, "ACTIVE"=0, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" n
[systemsettings] [Bug 456460] New: Night Color stops working after closing System Settings
https://bugs.kde.org/show_bug.cgi?id=456460 Bug ID: 456460 Summary: Night Color stops working after closing System Settings Product: systemsettings Version: 5.25.2 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: da...@protonmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Activate Night Color with Activation time: "Always on" (for testing, because it happens with other options) and Apply 2. Close System Settings 3. Night Color stops working The only way I can use Night Color is to activate it in System Settings, restarting the whole system and avoid opening System Settings again. Maybe there's something wrong with System Settings conflicting with Night Color. I noticed the following log messages, but I don't know if they're harmless, since my QT_PLUGIN_PATH is correctly set to /usr/local/qt/plugins:/usr/local/kde/lib/plugins. kf.coreaddons: "Could not load plugin from kcm_kscreen: The shared library was not found." kf.kirigami: Failed to find a Kirigami platform plugin SOFTWARE/OS VERSIONS Operating System: Linux KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.9 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-9980HK CPU @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 Any hints? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456460] Night Color stops working after closing System Settings
https://bugs.kde.org/show_bug.cgi?id=456460 Dan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Dan --- *** This bug has been marked as a duplicate of bug 413134 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413134] Night color conflicts with color correction
https://bugs.kde.org/show_bug.cgi?id=413134 Dan changed: What|Removed |Added CC||da...@protonmail.com --- Comment #20 from Dan --- *** Bug 456460 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413134] Night color conflicts with color correction
https://bugs.kde.org/show_bug.cgi?id=413134 --- Comment #21 from Dan --- In my case, Night Color stops working when leaving/entering System Settings. So if at least System Settings could be fixed to not interfere with Night Color, it would solve the issue for me... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456337] kwin_wayland_drm stalls with a black screen (only backlight is activated)
https://bugs.kde.org/show_bug.cgi?id=456337 Dan changed: What|Removed |Added Summary|"kwin_wayland_drm: Failed |kwin_wayland_drm stalls |to create gamma blob! |with a black screen (only |Invalid argument" |backlight is activated) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456337] kwin_wayland_drm stalls with a black screen (only backlight is activated)
https://bugs.kde.org/show_bug.cgi?id=456337 --- Comment #4 from Dan --- (In reply to Zamundaaa from comment #2) > No, that's because NVidia doesn't support setting gamma ramps on Wayland. It > won't have a negative effect, except that color correction and night color > won't work. Ok, so I changed the bug report title, since the main issue is the black screen (with the backlight activated). Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451167] New: Wrong menu positioning under wayland
https://bugs.kde.org/show_bug.cgi?id=451167 Bug ID: 451167 Summary: Wrong menu positioning under wayland Product: kwin Version: 5.24.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: appmenu Assignee: kwin-bugs-n...@kde.org Reporter: roze...@volny.cz Target Milestone: --- Created attachment 147300 --> https://bugs.kde.org/attachment.cgi?id=147300&action=edit The screenshot with wrong menu position SUMMARY *** The applications menu is not positioned correctly. Strange is that it appears on my laptop computer only, while on the work computer (with the same KDE version) the menu is rendered correctly. *** STEPS TO REPRODUCE 1. start a KDE application 2. trigger menu item OBSERVED RESULT See the attached screenshot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: plasma-workspace 5.24.2-1 (plasma) Qt Version: extra/qt5-base 5.15.2+kde+r305-1 Running on a Mesa DRI Intel(R) HD Graphics 4400 (HSW GT2) from Intel Open Source Technology Center -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451167] Wrong menu positioning under wayland
https://bugs.kde.org/show_bug.cgi?id=451167 --- Comment #2 from Dan --- (In reply to Nate Graham from comment #1) > What Qt version are you using? >From pacman: extra/qt5-base 5.15.2+kde+r302-1 (qt qt5) [installed] A cross-platform application and UI framework extra/qt5-declarative 5.15.2+kde+r46-1 (qt qt5) [installed] Classes for QML and JavaScript languages extra/qt5-graphicaleffects 5.15.2-2 (qt qt5) [installed] Graphical effects for use with Qt Quick 2 extra/qt5-multimedia 5.15.2-2 (qt qt5) [installed] Classes for audio, video, radio and camera functionality ... Do you need a version of a particular package? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451167] Wrong menu positioning under wayland
https://bugs.kde.org/show_bug.cgi?id=451167 --- Comment #3 from Dan --- Sorry, that was on my work desktop, where there is qt5-base 5.15.2+kde+*r302-1* but on my laptop (where the bug appears) is extra/qt5-base 5.15.2+kde+*r305-1*. I will re-check it at home, but expect the 5.15.2 QT version. (In reply to Dan from comment #2) > (In reply to Nate Graham from comment #1) > > What Qt version are you using? > > From pacman: > > extra/qt5-base 5.15.2+kde+r302-1 (qt qt5) [installed] > A cross-platform application and UI framework > extra/qt5-declarative 5.15.2+kde+r46-1 (qt qt5) [installed] > Classes for QML and JavaScript languages > extra/qt5-graphicaleffects 5.15.2-2 (qt qt5) [installed] > Graphical effects for use with Qt Quick 2 > extra/qt5-multimedia 5.15.2-2 (qt qt5) [installed] > Classes for audio, video, radio and camera functionality > ... > > Do you need a version of a particular package? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451167] Wrong menu positioning under wayland
https://bugs.kde.org/show_bug.cgi?id=451167 --- Comment #4 from Dan --- (In reply to Nate Graham from comment #1) > What Qt version are you using? Hi Nate, here is the list of installed packages on my laptop. Not all are relevant, probably. extra/qt5-base 5.15.3+kde+r136-1 (qt qt5) extra/qt5-declarative 5.15.3+kde+r20-1 (qt qt5) extra/qt5-graphicaleffects 5.15.3+kde+r0-1 (qt qt5) extra/qt5-location 5.15.3+kde+r1-1 (qt qt5) extra/qt5-multimedia 5.15.3+kde+r0-1 (qt qt5) extra/qt5-networkauth 5.15.3+kde+r0-1 (qt qt5) extra/qt5-quickcontrols 5.15.3+kde+r0-1 (qt qt5) extra/qt5-quickcontrols2 5.15.3+kde+r4-1 (qt qt5) extra/qt5-script 5.15.8-4 (qt qt5) extra/qt5-sensors 5.15.3+kde+r0-1 (qt qt5) extra/qt5-speech 5.15.3+kde+r1-1 (qt qt5) extra/qt5-svg 5.15.3+kde+r12-1 (qt qt5) extra/qt5-tools 5.15.3+kde+r1-1 (qt qt5) extra/qt5-translations 5.15.3+kde+r2-1 (qt qt5) extra/qt5-wayland 5.15.3+kde+r40-1 (qt qt5) extra/qt5-webchannel 5.15.3+kde+r3-1 (qt qt5) extra/qt5-webengine 5.15.8-10 (qt qt5) extra/qt5-webkit 5.212.0alpha4-12 extra/qt5-x11extras 5.15.3+kde+r0-1 (qt qt5) extra/qt5-xmlpatterns 5.15.3+kde+r0-1 (qt qt5) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451167] Wrong menu positioning under wayland
https://bugs.kde.org/show_bug.cgi?id=451167 --- Comment #6 from Dan --- (In reply to Nate Graham from comment #5) > Ok, I think that's up-to-date enough. Thanks. Sorry, I forgot to add that it is in multi-monitor setup - Laptop screen + external HDMI monitor (1920x1200). It is is relevant information ... However, the working desktop (at work) uses also multi-monitor setup, with two (different) HP monitor models, both running on 1920x1200. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 456843] New: [Feature request]: skip summary when entering a folder and go directly to next unread message
https://bugs.kde.org/show_bug.cgi?id=456843 Bug ID: 456843 Summary: [Feature request]: skip summary when entering a folder and go directly to next unread message Product: akregator Version: GIT (master) Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: da...@protonmail.com Target Milestone: --- I have several folders in Akregator, each one with many feeds. So I use a lot the keyboard shortcut to skip to next unread message. The problem is that it goes first to the summary of the folder and then I have to use the shortcut again to finally see the next unread message. This breaks the flow of reading feeds. Is there a way to go directly to the next unread message instead of seeing the summary? Because it doesn't matter how many unread messages there're in a folder, since we can view this number at the left panel. If it's not possible, it would be nice if there's an option to disable this behaviour. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 456843] [Feature request]: skip summary when entering a feed and go directly to next unread message
https://bugs.kde.org/show_bug.cgi?id=456843 Dan changed: What|Removed |Added Summary|[Feature request]: skip |[Feature request]: skip |summary when entering a |summary when entering a |folder and go directly to |feed and go directly to |next unread message |next unread message -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 456843] [Feature request]: skip summary when entering a feed and go directly to next unread message
https://bugs.kde.org/show_bug.cgi?id=456843 --- Comment #1 from Dan --- What I mean is when entering a feed. There's a summary showing how many unread messages before we can read the first unread message. If we can skip this summary, it would be nice. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455766] Brush changes Pencil-6 Quick Shade everytime i use pen (Parblo Ninos M)
https://bugs.kde.org/show_bug.cgi?id=455766 Dan changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #3 from Dan --- (In reply to Halla Rempt from comment #1) > I'm sorry, but that is something local... I cannot reproduce this. Please > check with a clean configuration or a different user? I cleaned configuration, it helped, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456337] kwin_wayland_drm stalls with a black screen (only backlight is activated)
https://bugs.kde.org/show_bug.cgi?id=456337 --- Comment #5 from Dan --- There're 2 more things I'd like to add when trying to run directly from console: 1) if I run "kwin_wayland --drm --lockscreen" it shows the lockscreen instead of a black screen and if I "login", it will go to the black screen 2) if I run "dbus-run-session startplasma-wayland", it starts the following and stalls at klauncher: 1182 tty1 Sl+0:00 /usr/kde5.25/bin/plasma_session --no-lockscreen 1185 tty1 Sl+0:00 /usr/kde/bin/kwin_wayland_wrapper --xwayland 1186 tty1 Sl+0:00 /usr/kde/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland 1189 ?S 0:00 /usr/kde/bin/ksplashqml 1190 tty1 S+ 0:00 /usr/kde5.25/bin/kdeinit5 --oom-pipe 4 1191 tty1 Z+ 0:00 [start_kdeinit_w] 1192 tty1 S+ 0:00 /usr/kde5.25/lib/libexec/kf5/start_kdeinit 1193 ?Ss 0:00 /usr/kde5.25/bin/kdeinit5 --oom-pipe 4 1194 ?S 0:00 /usr/kde5.25/lib/libexec/kf5/klauncher --fd=9 And it stays at the console... So I wonder why it is stuck at klauncher... -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 456101] [SOLVED] 'org.kde.KSplash' failed: Process org.kde.KSplash received signal 1
https://bugs.kde.org/show_bug.cgi?id=456101 Dan changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED Summary|'org.kde.KSplash' failed: |[SOLVED] 'org.kde.KSplash' |Process org.kde.KSplash |failed: Process |received signal 1 |org.kde.KSplash received ||signal 1 --- Comment #1 from Dan --- In the end it was the DISPLAY environment variable that was preventing wayland from starting. If DISPLAY or WAYLAND_DISPLAY is set, Kwin will not use the DRM backend, so I'm closing this as "NOT A BUG". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456337] [SOLVED] kwin_wayland_drm stalls with a black screen (only backlight is activated)
https://bugs.kde.org/show_bug.cgi?id=456337
Dan changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |NOT A BUG
Summary|kwin_wayland_drm stalls |[SOLVED] kwin_wayland_drm
|with a black screen (only |stalls with a black screen
|backlight is activated) |(only backlight is
||activated)
--- Comment #6 from Dan ---
In the end it was the DISPLAY environment variable that was preventing wayland
from starting. If DISPLAY or WAYLAND_DISPLAY is set, Kwin will not use the DRM
backend. I found it after looking at main_wayland.cpp:
static QString automaticBackendSelection()
{
if (qEnvironmentVariableIsSet("WAYLAND_DISPLAY")) {
return s_waylandPlugin;
}
if (qEnvironmentVariableIsSet("DISPLAY")) {
return s_x11Plugin;
}
return s_drmPlugin;
}
Maybe it would help if it was more verbose? Since many users are reporting
getting the "black screen", I wonder how many of them have DISPLAY set before
trying to login into Wayland... After the "No backend specified through command
line argument, trying auto resolution" message, Kwin could log something like
"DISPLAY environment variable detected. Using X11 backend". ;-)
So I'm closing this as "NOT A BUG". I hope it helps other users. Thanks
everyone!
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 457491] New: automaticBackendSelection() could be more verbose
https://bugs.kde.org/show_bug.cgi?id=457491
Bug ID: 457491
Summary: automaticBackendSelection() could be more verbose
Product: kwin
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: da...@protonmail.com
Target Milestone: ---
There're many reports of users trying to use Wayland and just seeing a black
screen. Since I was one of these users and I found the solution on Bug 456337,
here is a suggestion to improve the situation.
In the src/main_wayland.cpp, the automaticBackendSelection() will select the
backend based on WAYLAND_DISPLAY or DISPLAY environment variables. So, if the
user sets the DISPLAY variable, automaticBackendSelection() will use the X11
backend (and never use DRM backend), so the user will be stuck with a black
screen:
static QString automaticBackendSelection()
{
if (qEnvironmentVariableIsSet("WAYLAND_DISPLAY")) {
return s_waylandPlugin;
}
if (qEnvironmentVariableIsSet("DISPLAY")) {
return s_x11Plugin;
}
return s_drmPlugin;
}
It would be nice if it could be more verbose, like "DISPLAY environment
variable detected. Using X11 backend" or "WAYLAND_DISPLAY environment detected.
Using Wayland backend". So the log will help the user to understand that if
(s)he wants to use the DRM backend, (s)he cannot set those environment
variables.
Thank you!
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 456337] [SOLVED] kwin_wayland_drm stalls with a black screen (only backlight is activated)
https://bugs.kde.org/show_bug.cgi?id=456337 --- Comment #8 from Dan --- (In reply to Nate Graham from comment #7) > Being more verbose about this would make tons of sense. Can you please file > a new bug report about that? Thanks a lot! Done: bug 457491. Thank you Nate! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373440] konsole --new-tab opens window instead
https://bugs.kde.org/show_bug.cgi?id=373440 dan changed: What|Removed |Added CC||dda...@gmail.com --- Comment #42 from dan --- Hello, I noticed this also when right-clicking Konsole in the taskbar and choosing "Open a new tab". It opens a new window instead of a tab. I am guessing it is the same issue and that the taskbar action is probably just running `konsole --new-tab`. If I turn on "Run all Konsole windows in a single process", which is off by default, then it opens a new tab. I have near 0 experience coding for Qt/Plasma, so I apologize if I am ignorantly over-simplifying the issue here, but could you possibly simplify the "new tab" action and just tell the running process to open a new tab over something like dbus? Thanks, Dan -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 433349] New: Allow clicking on the New Tab option under File menu to open the default profile when there are multiple available, instead of having to choose a profile
https://bugs.kde.org/show_bug.cgi?id=433349 Bug ID: 433349 Summary: Allow clicking on the New Tab option under File menu to open the default profile when there are multiple available, instead of having to choose a profile Product: konsole Version: 20.12.2 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: dda...@gmail.com Target Milestone: --- This is a pretty minor annoyance... sorry. Konsole is a great terminal emulator, thank you for all the work put into it! Currently if I add profile so that I now have 2 profiles (the Default and Profile 1 which is set as the default), when I open the File menu I have to hover over New Tab and then select a profile to open the new tab with (Default or Profile 1). It would be nice if the New Tab option itself was still clickable and just opened the profile that is set as the default (Not to be confused with the "Default" profile that is the hard-coded fallback profile). Thanks, Dan -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 433349] Allow clicking on the New Tab option under File menu to open the default profile when there are multiple available, instead of having to choose a profile
https://bugs.kde.org/show_bug.cgi?id=433349 --- Comment #2 from dan --- "Settings->Show Tool Bar" is not an option. "Show Menubar" is, but that was already checked by default. I'm not sure how that helps though, that just hides or shows the menus at top, or did you mean in the Configure window that I can have the Tab Bar always shown instead of only after I have more than 1 tab? I did find out that I can turn on the new tab button, which I think is what you meant by "click on new tab icon", which works as expected to open a new tab with the profile set as the default. It was turned off by default though, surprisingly. I would think the new tab button would be on by default... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392956] database corrupt
https://bugs.kde.org/show_bug.cgi?id=392956 Dan changed: What|Removed |Added CC||roze...@volny.cz --- Comment #1 from Dan --- I have similar symptomps with kmail (kontact 5.15.1 (20.08.1), KDE Frameworks 5.47.0 on Arch Linux. Apart of mail duplication, the akonadi server consumes all the memory after some time ... Here is a part of the log obtained when `akonadictl restart` is called (is it safe to send it whole?): org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f6950303b30) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f6950303b30) ) org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f69502afe90) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f695020df90) identified as "AgentBaseChangeRecorder - 94582020480560" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f6950303b30) identified as "Archive Mail Kernel ETM - 94582020541536" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f69502afe90) identified as "ArchiveMailCollectionMonitor - 94582020801040" org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f6950306c30) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f6950306c30) identified as "SpecialCollectionsMonitor - 94167298158096" org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f6950311c90) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f695020dc40) identified as "AgentBaseChangeRecorder - 94321149800128" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f6950270b20) identified as "AgentBaseChangeRecorder - 94041219792608" org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f6950311c90) identified as "UnifiedMailboxChangeRecorder - 140722923724944" terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f695022b260) identified as "AgentBaseChangeRecorder - 94159610622528" org.kde.kgapi: Unauthorized. Access token has expired or is invalid. org.kde.pim.google: Got error: KGAPI2::CalendarFetchJob(0x55a33e2bc560) "Neplatné ověření." org.kde.kgapi: Unauthorized. Access token has expired or is invalid. org.kde.pim.google: Got error: KGAPI2::TaskListFetchJob(0x55a33e2a7dc0) "Neplatné ověření." org.kde.kgapi: Unauthorized. Access token has expired or is invalid. org.kde.pim.google: Got error: KGAPI2::ContactsGroupFetchJob(0x55a33e25c040) "Neplatné ověření." org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 94510664681936" disconnected org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_indexing_agent" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_indexing_agent' crashed! 1 restarts left. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f6950190250) ) org.kde.pim.akonadi_indexer_agent: Database Corrupted - What did you do? org.kde.pim.akonadi_indexer_agent: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f6950190250) identified as "AgentBaseChangeRecorder - 94316572205968" terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 94316572205968" disconnected org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_indexing_agent" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_indexing_agent' crashed! 0 restarts left. org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7f6950334170) ) org.kde.pim.akonadi_indexer_agent: Database Corrupted - What did you do? org.kde.pim.akonadi_indexer_agent: org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7f6950334170) identified as "AgentBaseChangeRecorder - 94020415634304" terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 94020415634304" disconnected org.kde.pim.akonadicontrol: ProcessControl: Applicati
[KScreen] [Bug 354544] Windows move after power savings mode
https://bugs.kde.org/show_bug.cgi?id=354544 Dan changed: What|Removed |Added CC||parn...@gmail.com --- Comment #2 from Dan --- This problem still occurs on Kubuntu 20.04 (KDE Plasma 5.18.5). It appears to be due to my two DP monitors waking up at different speeds: The secondary monitor wakes up first and KScreen re-arranges with it as the primary, sole display. This results in many of the windows moving around. Then the actual primary monitor wakes up so KScreen switches back to a dual-screen configuration and returns the windows to their original displays - but those on the secondary display are all now in the wrong positions. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430902] Plasma crashes while searching in samba share
https://bugs.kde.org/show_bug.cgi?id=430902 dan changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED Version|20.12.0 |21.04.2 CC||dda...@gmail.com --- Comment #6 from dan --- I am running in to this bug too. I am using Fedora 34 (Dolphin 21.04.2) and tested with both Wayland and X11. I will attach my journalctl output that I think may have some useful info. Thanks, Dan -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430902] Plasma crashes while searching in samba share
https://bugs.kde.org/show_bug.cgi?id=430902 --- Comment #7 from dan --- Created attachment 140370 --> https://bugs.kde.org/attachment.cgi?id=140370&action=edit journal output of when dolphin and plasma crashed -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430902] Plasma crashes while searching in samba share
https://bugs.kde.org/show_bug.cgi?id=430902 --- Comment #8 from dan --- Note, increasing my max number of open files (soft limit) to 12000 made the search run a lot longer before it crashed. I imagine if I kept increasing it at some point the crash wouldn't happen. It's still probably a bug none the less... I'm not sure why that many files would need to be opened at once. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435902] New: error massage = insufficient privileges on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 Bug ID: 435902 Summary: error massage = insufficient privileges on the database... Product: digikam Version: 7.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Database Assignee: digikam-bugs-n...@kde.org Reporter: daniel.pur...@delwp.vic.gov.au Target Milestone: --- SUMMARY Once Digikam 7.1.0 is installed, I open the application and get the following message -'You have insufficient privileges on the database. Following privileges are not assigned to you: CREATE TABLE Check you privileges on the database and restart digikam' I cannot open Digikam to alter the settings. I do not know which digikam folder to look into fix this. STEPS TO REPRODUCE 1. install digikam 7.1.0 2. open digikam 7.1.0 3. above message received OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 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.
[digikam] [Bug 435902] error massage = insufficient privileges on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 --- Comment #2 from Dan --- HI. Yes I think it is mysql. Internal version - assuming that means I've downloaded it to my laptop and opening it off there. Unofficial -Original Message- From: bugzilla_nore...@kde.org Sent: Monday, 19 April 2021 2:58 PM To: Daniel C Purdey (DELWP) Subject: [digikam] [Bug 435902] error massage = insufficient privileges on the database... EXTERNAL SENDER: Links and attachments may be unsafe. https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.kde.org_show-5Fbug.cgi-3Fid-3D435902&d=DwIFaQ&c=JnBkUqWXzx2bz-3a05d47Q&r=_DGlHQHjrtzMShQxTxL106BOdYz9cYPuftwsNXesUhs&m=5ONp4Gz0fDPTS1r4akobZlCEmreXzIBCV3MiHo2Qyhg&s=eZ3tCqlx5wwVlAktn6cFFIBsiXmHTGsOZYUbjmESZmk&e= --- Comment #1 from caulier.gil...@gmail.com --- database type is Mysql ? if yes, do you use Internal version or Server ? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435902] error massage = insufficient privileges on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 --- Comment #3 from Dan --- (In reply to caulier.gilles from comment #1) > database type is Mysql ? if yes, do you use Internal version or Server ? HI. Yes I think it is mysql. Internal version - assuming that means I've downloaded it to my laptop and opening it off there. Have you heard of this issue/error message before? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435902] error massage = insufficient privileges on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 --- Comment #4 from Dan --- (In reply to caulier.gilles from comment #1) > database type is Mysql ? if yes, do you use Internal version or Server ? My colleagues have successfully downloaded and used this application, and love it, on similar their work laptops without experiencing this error -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435902] error massage = insufficient privileges on the database...
https://bugs.kde.org/show_bug.cgi?id=435902 --- Comment #7 from Dan --- (In reply to caulier.gilles from comment #5) > Check in Setup/Database dialog page to be sure. > > Why did you use 7.1.0 and not last stable 7.2.0 released few weeks ago ? Apologies. I have 7.2.0. I didn't see it was updated. I've been downloading the latest from the digikam site several times over the pat 2 weeks and didn't notice the update. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Dan changed: What|Removed |Added Status|RESOLVED|VERIFIED Resolution|FIXED |REMIND --- Comment #5 from Dan --- (In reply to Waqar Ahmed from comment #1) > Hi, would it be possible for you to try the latest Kate? You seem to be on > Arch, so the latest version should be available Hi, I have tried it with the latest version available in Arch: * kate 23.08.4 * KDE Frameworks 5.113.0 * Qt 5.15.11 *Still too slow*: * sort ~ 2sec * kate >> minute -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 --- Comment #7 from Dan --- (In reply to Kåre Särs from comment #6) > Hi, > > This has been improved in master and will be released with 24.02.0 in > February. > > If you need the improvement _now_, you have to compile your self or use some > bleeding development edge distribution that packages beta versions of KDE > software. > > Instructions for building it your self: > https://kate-editor.org/build-it/ > > Br, > Kåre Hi, no need to hurry. Thank you for the info. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 479434] New: Snap of massif-visualizer is not configured properly with dot/graphviz
https://bugs.kde.org/show_bug.cgi?id=479434 Bug ID: 479434 Summary: Snap of massif-visualizer is not configured properly with dot/graphviz Classification: Developer tools Product: valgrind Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: massif Assignee: n...@valgrind.org Reporter: d.malju...@yandex.ru Target Milestone: --- SUMMARY Opening callgraph tab in massif-visualizer snap leads to a crash STEPS TO REPRODUCE 1. install massif-visualizer snap (sudo snap install massif-visualizer) 2. snap run massif-visualizer 3. open some massif profile 4. Try to open callgraph tab OBSERVED RESULT Program crashes with ``` creating new dot file in "/tmp/massif-visualizer.VVnjIJ" show dot graph in output file "/tmp/massif-visualizer.VVnjIJ" Error: Layout type: "dot" not recognized. Use one of: Error: Layout was not done ``` EXPECTED RESULT Callgraph tab is opened (and shows something) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Rocky Linux 8 snap info massif-visualzer: snap-id: 1ChRFuKzm7aeJVDVCLzRXHf3CwXz00Xx tracking: latest/stable refresh-date: 8 days ago, at 21:01 +04 channels: latest/stable:0.7.0 2023-11-01 (10) 178MB - latest/candidate: 0.7.0 2023-11-01 (10) 178MB - latest/beta: ↑ latest/edge: master+6003291 2019-01-16 (3) 34MB - installed: 0.7.0 (10) 178MB - ADDITIONAL INFORMATION Perhaps it's missing explicit gvAddLibrary? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468609] Loads heif only with 8 bits color depth
https://bugs.kde.org/show_bug.cgi?id=468609
Dan changed:
What|Removed |Added
CC||dkb...@tofubar.com
--- Comment #2 from Dan ---
My canon HEIF images appear washed out and I thought this might be the solution
but am now convinced otherwise. I'm now slowly going down the education path on
colour profiles. I think this patch fixes the bit depth problem as a start. It
works for my canon images but I haven't tested for the full combination of
alpha and bit depth.
diff --git a/core/dplugins/dimg/heif/dimgheifloader_load.cpp
b/core/dplugins/dimg/heif/dimgheifloader_load.cpp
index eb8862c91f..f3d0bdc071 100644
--- a/core/dplugins/dimg/heif/dimgheifloader_load.cpp
+++ b/core/dplugins/dimg/heif/dimgheifloader_load.cpp
@@ -335,7 +335,7 @@ bool DImgHEIFLoader::readHEICImageByHandle(struct
heif_image_handle* image_handl
{
int lumaBits = heif_image_handle_get_luma_bits_per_pixel(image_handle);
int chromaBits =
heif_image_handle_get_chroma_bits_per_pixel(image_handle);
-
+int colorDepth = lumaBits;
if ((lumaBits == -1) || (chromaBits == -1))
{
qCWarning(DIGIKAM_DIMG_LOG_HEIF) << "HEIC luma or chroma bits
information not valid!";
@@ -352,8 +352,8 @@ bool DImgHEIFLoader::readHEICImageByHandle(struct
heif_image_handle* image_handl
struct heif_decoding_options* const decode_options =
heif_decoding_options_alloc();
decode_options->ignore_transformations = 1;
m_hasAlpha =
heif_image_handle_has_alpha_channel(image_handle);
-heif_chroma chroma = m_hasAlpha ?
heif_chroma_interleaved_RGBA
-:
heif_chroma_interleaved_RGB;
+heif_chroma chroma = m_hasAlpha ?
((colorDepth==8) ? heif_chroma_interleaved_RGBA :
heif_chroma_interleaved_RRGGBBAA_LE)
+:
((colorDepth==8) ? heif_chroma_interleaved_RGB :
heif_chroma_interleaved_RRGGBB_LE );
// Trace to check image size properties before decoding, as these values
can be different.
@@ -385,8 +385,6 @@ bool DImgHEIFLoader::readHEICImageByHandle(struct
heif_image_handle* image_handl
}
heif_decoding_options_free(decode_options);
-
-int colorDepth = heif_image_get_bits_per_pixel_range(heif_image,
heif_channel_interleaved);
imageWidth() = heif_image_get_width(heif_image,
heif_channel_interleaved);
imageHeight() = heif_image_get_height(heif_image,
heif_channel_interleaved);
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 468609] Loads heif only with 8 bits color depth
https://bugs.kde.org/show_bug.cgi?id=468609 --- Comment #4 from Dan --- One of the images I've used for testing is: https://drive.google.com/file/d/1R8nlefUAu5fgwKc57Sd0AzU4R_nE-ZoA/view?usp=drive_link With the patch it does 10 bit to 16bit scaling shift fine rather than the direct to 8 bit conversion before. The colours are a bit washed out as with 8 bit. My reading regarding the colour profile: ITU-R BT.2100 PQ is that this is a non linear conversion. I think canon are using nclx so dropping through to the "Unknown HEIF color profile type discarded" warning. There is more reading/hacking before I get my head around that part. Dan -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477249] New: Sever failure of Capture RectangularRegion
https://bugs.kde.org/show_bug.cgi?id=477249 Bug ID: 477249 Summary: Sever failure of Capture RectangularRegion Classification: Applications Product: Spectacle Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: es...@ieee.org CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open app 2. choose capture rectangular region 3. click take screenshot 4. Screen goes completely black 5 . After a minute or two some of the desktop reappears but none of the desktop launchers display. 6. Log off and on 7. Screen returns to normal 8. Uninstall Spectacle 9. Report Bug OBSERVED RESULT EXPECTED RESULT duh... SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 KDE Plasma Version: Latest - just installed KDE Frameworks Version: Latest - just installed Qt Version: Latest - just installed ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477249] Sever failure of Capture RectangularRegion
https://bugs.kde.org/show_bug.cgi?id=477249 --- Comment #2 from Dan --- That is useful information. But, I installed it from the Software Center. Are you telling me that doing it that way does not always install the latest version? sudo apt install spectacle says: package not found. What am I missing? thx -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477249] Sever failure of Capture RectangularRegion
https://bugs.kde.org/show_bug.cgi?id=477249 --- Comment #4 from Dan --- I couldn'tfind an appimage, snap or a flatpak. i coud probably figure out the last 2 but prefer appimage rather than loading a massive subsystem just to install one app On Sun, Nov 19, 2023, at 4:31 PM, Noah Davis wrote: > https://bugs.kde.org/show_bug.cgi?id=477249 > > --- Comment #3 from Noah Davis --- > (In reply to Dan from comment #2) >> That is useful information. But, I installed it from the Software Center. >> Are you telling me that doing it that way does not always install the latest >> version? >> >> sudo apt install spectacle says: >> package not found. >> >> What am I missing? >> >> thx > > In short, certain kinds of Linux distributions such as Debian Stable and > Ubuntu > have long upgrade cycles where very few changes happen in between distribution > versions. This leads to their users being stuck with outdated versions. The > solutions available to you are the following: > > - Try to use a Flatpak, Snap, AppImage or other distribution independent > package that provides a newer version of the software you want to use. > - Add a repository that provides a newer Debian package for the software you > want to use. You might not have this option with Debian since extra > repositories aren't as common for Debian as they are for other stable Linux > distributions, AFAIK. > - Install a newer version by building it from source code. I don't expect most > users to do this, let alone stable Linux distribution users. For users with > the > latest software versions from a distro like Arch Linux it's not so hard, but > stable linux distribution users would probably need to set up a whole KDE > development environment because their developer package versions are too old. > - Install a Linux distribution that provides newer packages. You can consider > this a last resort, but it might solve a lot of problems if you eventually > find > yourself needing a lot of newer software versions. > > You can ignore the following if the info above was all you needed to read: > > Linux distributions that don't change much between versions are called > "stable" > Linux distributions. That is helpful for system administrators who need to > manage hundreds or thousands of computers. It's a common misconception among > Linux users who install Linux on their personal computers to think that > "stable" means fewer bugs when stable distributions are usually just as buggy > as any other kind. The difference is that the bugs you have to deal with > remain > the same for a long time. If you have a support contract with a company like > Canonical, SUSE or RedHat, you may get patches specific to their supported > Linux distributions to fix some of the bugs. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 468140] Songs in a playlist created automatically from files in folder don't play sporadically, can be only fixed by scrolling forward.
https://bugs.kde.org/show_bug.cgi?id=468140 --- Comment #4 from Dan --- works nicely 👍 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 472099] New: Kalendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=472099 Bug ID: 472099 Summary: Kalendar crashes on startup Classification: Applications Product: kalendar Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: dobin...@protonmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-24-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: When executing Kalendar it immediatly crashes The crash can be reproduced every time. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x7fd8e8406c04 in KCalendarCore::Calendar::isLoading() const () at /lib/x86_64-linux-gnu/libKF5CalendarCore.so.5abi2 #5 0x564555bb9875 in () #6 0x7fd8e60f39af in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd8e60f798e in QTimer::timeout(QTimer::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd8e60e7bf5 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fd8e6d6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fd8e60bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fd8e6114201 in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fd8e6114b34 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fd8e3f1549d in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd8e3f70178 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd8e3f141b0 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd8e6114e7a in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fd8e60b97cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fd8e60c1c1a in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x564555b76e5a in () #20 0x7fd8e5623a90 in __libc_start_call_main (main=main@entry=0x564555b74d30, argc=argc@entry=1, argv=argv@entry=0x7ffc4dc32b68) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7fd8e5623b49 in __libc_start_main_impl (main=0x564555b74d30, argc=1, argv=0x7ffc4dc32b68, init=, fini=, rtld_fini=, stack_end=0x7ffc4dc32b58) at ../csu/libc-start.c:360 #22 0x564555b77e55 in () [Inferior 1 (process 21703) detached] The reporter indicates this bug may be a duplicate of or related to bug 468031, bug 467600, bug 469065. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 472338] No longer loading twitter timelines
https://bugs.kde.org/show_bug.cgi?id=472338 Dan changed: What|Removed |Added CC||da...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 395083] Empty contact
https://bugs.kde.org/show_bug.cgi?id=395083 --- Comment #3 from Dan --- (In reply to Justin Zobel from comment #1) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Hi. The issue is still present, but the version of kopete did not change since my report. Kopete is still at version 1.13.0 from arch, reported as extra/kopete 22.08.0-1 (kde-applications kde-network) [installed], though Thank you very much. D. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460404] [Regression]: Kwin 5.26.0 uses software renderer instead of GLX
https://bugs.kde.org/show_bug.cgi?id=460404 --- Comment #10 from Dan --- (In reply to Simon Vogl from comment #9) > Hmm.. since kwin does not crash at all on my end, I'm asking myself whether > I'm even experiencing the same bug as OP or a different one? In fact Kwin doesn't crash. The kcrash message is unrelated to this issue (I don't know why the kcrash appeared in the logs). > @Dan does your issue go away when you put > > [QtQuickRendererSettings] > SceneGraphBackend=opengl > > in .config/kdeglobals ? You're correct! This fixed the issue for me. Now it's working perfectly as before ;-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460404] [Regression]: Kwin 5.26.0 uses software renderer instead of GLX
https://bugs.kde.org/show_bug.cgi?id=460404 --- Comment #12 from Dan --- (In reply to Simon Vogl from comment #11) > OK, looks like we indeed face the same issue. > Now the question is why is there a slowdown when SceneGraphBackend under > [QtQuickRendererSettings] is not set to any value / doesn't exist? Good question. but I also tested without SceneGraphBackend and it works fine here. When I had the problem, SceneGraphBackend was set to "software", but I don't remember setting it to "software" (since it was working with 5.25, maybe Plasma 5.26 set it after the upgrade for some reason?). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461029] New: [Regression with bisect]: "kwin_core: precision lost! floating value sent to X..."
https://bugs.kde.org/show_bug.cgi?id=461029 Bug ID: 461029 Summary: [Regression with bisect]: "kwin_core: precision lost! floating value sent to X..." Classification: Plasma Product: kwin Version: 5.26.2 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: da...@protonmail.com Target Milestone: --- After updating from Kwin 5.26.1 to 5.26.2 I got the following on the log: kwin_core: precision lost! floating value sent to X 2039.5 kwin_core: precision lost! floating value sent to X 1942.5 kwin_core: precision lost! floating value sent to X 1942.5 kwin_core: precision lost! floating value sent to X 1942.5 kwin_core: precision lost! floating value sent to X 2039.5 At the same time, there's corruption on the screen (the windows were not being repainted when maximized). So I did a bisect and here's the result: da10d8481af24f7ff7092e5a2da5c5262fdd4011 is the first bad commit commit da10d8481af24f7ff7092e5a2da5c5262fdd4011 Author: Arjen Hiemstra Date: Mon Oct 24 16:03:52 2022 +0200 Add a helper function to convert QPointF to QPoint using floor instead of round In a bunch of cases, we want to floor when converting to QPoint rather than rounding. As it gets tedious to repeat the same code over and over, add a helper function. (cherry picked from commit 2f900d84abd2b3d99c85a63eb7b743eb0761e9bf) src/libkwineffects/kwineffects.h | 11 +++ 1 file changed, 11 insertions(+) git bisect start # status: waiting for both good and bad commits # bad: [649a573e358f32193715237849ebf5d7e28e14e9] fix compile git bisect bad 649a573e358f32193715237849ebf5d7e28e14e9 # status: waiting for good commit(s), bad commit known # good: [1af6a1a708c5e37e7d6d21dcad74806fb72f20f3] Update version number for 5.26.1 GIT_SILENT git bisect good 1af6a1a708c5e37e7d6d21dcad74806fb72f20f3 # good: [870aee8cdc82fdae7440589ea61dfdb0c79f84e9] inputpanelv1window: never hide overlay panels git bisect good 870aee8cdc82fdae7440589ea61dfdb0c79f84e9 # bad: [d78187005432ed02159963fd76554678a9db2e67] Window: Floor rather than round when doing hitTest for the decoration git bisect bad d78187005432ed02159963fd76554678a9db2e67 # good: [f28e547330ae4c3c6c4ac97cd6fb7930d8e2e148] Implement a enableRequested signal for text-input-v3 git bisect good f28e547330ae4c3c6c4ac97cd6fb7930d8e2e148 # bad: [da10d8481af24f7ff7092e5a2da5c5262fdd4011] Add a helper function to convert QPointF to QPoint using floor instead of round git bisect bad da10d8481af24f7ff7092e5a2da5c5262fdd4011 # good: [3c07db610bf70796f612016c6c5354ca5c565ebd] wayland: Fix missing relative motion events git bisect good 3c07db610bf70796f612016c6c5354ca5c565ebd # first bad commit: [da10d8481af24f7ff7092e5a2da5c5262fdd4011] Add a helper function to convert QPointF to QPoint using floor instead of round * Does it make sense? So I downgraded to 5.26.1 and everything is working fine. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461029] [Regression with bisect]: "kwin_core: precision lost! floating value sent to X..."
https://bugs.kde.org/show_bug.cgi?id=461029 --- Comment #1 from Dan --- My setup if it's relevant: KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.5 Kernel Version: 6.0.3 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i9-9980HK CPU @ 2.40GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461032] With 150% scale, when maximising a window, kwin_x11 fails to redraw the window content
https://bugs.kde.org/show_bug.cgi?id=461032 Dan changed: What|Removed |Added CC||da...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461029] [Regression with bisect]: "kwin_core: precision lost! floating value sent to X..."
https://bugs.kde.org/show_bug.cgi?id=461029 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Dan --- Ok, with commit c65264e1, it solves the issue: https://invent.kde.org/plasma/kwin/-/commit/c65264e15355397931df8ad7fa58619b26487c17#b95537a58887ab61b7f3b4e00f79b22e65d81374 So I'm marking this as a duplicate of 461032. Thanks! *** This bug has been marked as a duplicate of bug 461032 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461032] With 150% scale, when maximising a window, kwin_x11 fails to redraw the window content
https://bugs.kde.org/show_bug.cgi?id=461032 --- Comment #2 from Dan --- *** Bug 461029 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 395083] Empty contact
https://bugs.kde.org/show_bug.cgi?id=395083 Dan changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 450658] Dark theme is unusable
https://bugs.kde.org/show_bug.cgi?id=450658 Dan changed: What|Removed |Added CC||es...@ieee.org --- Comment #9 from Dan --- I have checked all of the above suggestions. I have no .profile. qqc2-desktop-style is installed. I have tried all of the available "light" theme variations that are shown on the "Application Style" page in System Settings. None of them affect the appearance of the plasma system monitor it's still black (dark blue?) text on a black background. Totally unusable. Why isn't there a settings option within the app to set or override the theme? As it is it is totally useless -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447250] New: System settings crashes when try to install new global theme
https://bugs.kde.org/show_bug.cgi?id=447250 Bug ID: 447250 Summary: System settings crashes when try to install new global theme Product: systemsettings Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: dan...@yahoo.com Target Milestone: --- Application: systemsettings5 (5.18.5) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.106-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.2 -- Information about the crash: - What I was doing when the application crashed: Open "System Settings": - select "Global Theme" - press button "Get New Global Themes..." - select "Sweet KDE" theme and press "Install" button System settings starts to download and crashes after while. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f4454fbc8f4 in KJob::error() const () from /usr/lib64/libKF5CoreAddons.so.5 #5 0x7f4430107f63 in KNSCore::KPackageJoboperator() (job=0x5604bdfae700, __closure=0x5604bdd87f10) at /usr/src/debug/knewstuff-5.71.0-lp152.2.3.1.x86_64/src/core/jobs/kpackagejob.cpp:142 #6 QtPrivate::FunctorCall, QtPrivate::List, void, KNSCore::KPackageJob::start():: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #7 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #8 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1, this_=0x5604bdd87f00, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:439 #9 0x7f44532e69e2 in QObject::event (this=0x5604bdd881d0, e=) at kernel/qobject.cpp:1261 #10 0x7f44543cdf2c in QApplicationPrivate::notify_helper (this=this@entry=0x5604bd2c2b00, receiver=receiver@entry=0x5604bdd881d0, e=e@entry=0x5604be4e34e0) at kernel/qapplication.cpp:3701 #11 0x7f44543d5540 in QApplication::notify (this=0x7ffecd14baf0, receiver=0x5604bdd881d0, e=0x5604be4e34e0) at kernel/qapplication.cpp:3447 #12 0x7f44532b6328 in QCoreApplication::notifyInternal2 (receiver=0x5604bdd881d0, event=0x5604be4e34e0) at kernel/qcoreapplication.cpp:1088 #13 0x7f44532b64fe in QCoreApplication::sendEvent (receiver=, event=event@entry=0x5604be4e34e0) at kernel/qcoreapplication.cpp:1476 #14 0x7f44532b8ee7 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x5604bd2b9dc0) at kernel/qcoreapplication.cpp:1825 #15 0x7f44532b9488 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1679 #16 0x7f4453313d93 in postEventSourceDispatch (s=0x5604bd3b2720) at kernel/qeventdispatcher_glib.cpp:276 #17 0x7f444be9f624 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #18 0x7f444be9f9c0 in ?? () from /usr/lib64/libglib-2.0.so.0 #19 0x7f444be9fa4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #20 0x7f44533133af in QEventDispatcherGlib::processEvents (this=0x5604bd2cb8d0, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #21 0x7f44532b457a in QEventLoop::exec (this=this@entry=0x7ffecd14ba10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #22 0x7f44532bd780 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1389 #23 0x5604bb265e00 in ?? () #24 0x7f445289c3ea in __libc_start_main () from /lib64/libc.so.6 #25 0x5604bb265e8a in _start () [Inferior 1 (process 8716) detached] Possible duplicates by query: bug 431793, bug 423766, bug 278769, bug 272154. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447250] System settings crashes when try to install new global theme
https://bugs.kde.org/show_bug.cgi?id=447250 Dan changed: What|Removed |Added CC||dan...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 449271] New: A dollar sign in a URL in an href from hyperref will trigger math mode. Escaping (\&) doesn't work.
https://bugs.kde.org/show_bug.cgi?id=449271 Bug ID: 449271 Summary: A dollar sign in a URL in an href from hyperref will trigger math mode. Escaping (\&) doesn't work. Product: kile Version: 2.9.93 Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: editor Assignee: michel.lud...@kdemail.net Reporter: autop...@protonmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Call the hyperref package. 2. Insert an \href, using a URL with a dollar sign in it. 3. Add content below. OBSERVED RESULT All content after the lone $ is highlighted red, as if I am in math mode. EXPECTED RESULT The lone dollar sign should not have triggered math mode highlighting. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian 11 Stable (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425959] New: Dark Themes do not display text correctly
https://bugs.kde.org/show_bug.cgi?id=425959 Bug ID: 425959 Summary: Dark Themes do not display text correctly Product: kid3 Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: d...@mawddach.me.uk Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set Theme on PC to Controls/Mint-Y-Dark 2. In Kid3 QT use Setting/sAppearence untick Use Custom Application Style 3. Restart Kid3 QT OBSERVED RESULT Tool bar has wrong icons and any text in the Tag boxes does not display correctly once you try to make an amendment. EXPECTED RESULT The Dark theme should work and there should be no difficulty reading amended text in the Tag fileds SOFTWARE/OS VERSIONS Linux Min 20.0 (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: 5.12.8. ADDITIONAL INFORMATION If you instead use a Dark Custom theme from Kid3 QT selection, the same effect can be observed -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425959] Dark Themes do not display text correctly
https://bugs.kde.org/show_bug.cgi?id=425959 --- Comment #2 from Dan --- Using QT Settings and using fusion-fixes.qss perfectly solves the text entry issue. However, I cannot restore the icons in the toolbar. Using the Kid3 System default for appearence, shows the dark them I am using, i.e. Mint-y-Dark. The icons are set to Mint-X-Dark. - Changing to the qt5ct style sheet, does not have any effect on the toolbar. How do I ensure QT_QPA_PLATFORMTHEME=qt5ct is set properly? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 374504] yakuake starts on the wrong screen
https://bugs.kde.org/show_bug.cgi?id=374504 --- Comment #4 from Dan --- Created attachment 138856 --> https://bugs.kde.org/attachment.cgi?id=138856&action=edit Window rule settings for workaround -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 374504] yakuake starts on the wrong screen
https://bugs.kde.org/show_bug.cgi?id=374504 Dan changed: What|Removed |Added CC||dpurcelljr+...@gmail.com --- Comment #5 from Dan --- This may be kwin issue with multiple monitors using varying resolutions rather than Yakuake specific. https://bugs.kde.org/show_bug.cgi?id=427875 https://www.reddit.com/r/kde/comments/9ijm5z/multi_monitors_remember_the_window_position/ Can confirm a variant of the suggested workaround in that Reddit post works for this. To get Yakuake to opening on the desired screen: Open System Settings > Window Management > Window Rules Add New Set "Window Class (application)" to "Substring Match" and enter text value "yakuake". (Alternatively you can open Yakuake, pin the window so it stays open on focus loss, and use the "Detect Window Properties" to capture the desired matcher) Set Match whole window class to "Yes" Set Window types to "All selected" Click Add Property, choose "Screen" Set combo selection to "Force" and number selection to the screen you want Yakuake to open on. (In my case, 0 made it to open on the center screen.) Click Apply Close Yakuake, reopen, and check if it opens on the desired screen. You may have to experiment to yet it to stick to the right screen. Added attachment for workaround example. My Info: Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-17-generic (64-bit) Graphics Platform: X11 Graphics Processor: GeForce RTX 2070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434604] New: Multiple monitor configuration gets broken
https://bugs.kde.org/show_bug.cgi?id=434604
Bug ID: 434604
Summary: Multiple monitor configuration gets broken
Product: plasmashell
Version: master
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: Multi-screen support
Assignee: aleix...@kde.org
Reporter: dan...@wolstenholme.net
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
I have a Dell E6440 laptop with a dual-monitor docking station, with two
monitors connected to it via mini-DisplayPort. I recently upgraded both
monitors (but separately, I bought one, then a couple weeks later got another).
Between various unplugging and re-plugging of all the different monitors, I
saw multiple problems where, when a particular monitor was plugged in, the
system would simply not use that monitor, and would continually say a new
monitor was plugged in, then quickly say a monitor has been unplugged, over and
over endlessly. It seemed like one of my monitors had gone bad. But then I saw
the same thing with one of the new monitors.
I was able to debug this problem, and determined that the screen configuration
was being stored in ~/.local/share/kscreen (which I found odd, and made it
really hard to find this, because it seems like most KDE config stuff is in
~/.config these days). In that directory is one randomly-named JSON file with
entries for all the connected monitors, including their ID number, name,
refresh rate, size, and position, and other info. In the "outputs"
subdirectory within this directory are files named with those ID numbers, and
containing basically the exact same info.
What I found ultimately was that, in the top-level file, there was still an
entry for one of my old monitors, and in addition (and I believe this was the
actual source of the bug), my two new monitors had the same name (they were
both called "DP-1").
I cleaned up this directory, deleting the references to the old monitor, and
renaming the two new monitors so they had unique names ("DP-1" and "DP-2", and
"eDP-1" for the laptop's screen), and restarted. Ever since then, I haven't
had any trouble, though I have not yet tried undocking and redocking, or
unplugging and re-plugging the monitors.
It seems to me that what's needed here is for some logic to ensure that any
newly-detected monitor does not have the same name as any other that's already
been detected, or if such logic exists, there must be some bug with it.
STEPS TO REPRODUCE
1. Plug in 2 monitors
2. Unplug one, plug in a 3rd
3. Play around with unplugging and replugging the monitors, using different
ports
OBSERVED RESULT
System will refuse to use one of the monitors, and constantly change
configuration as if a monitor is being plugged in and immediately unplugged 2
seconds later.
EXPECTED RESULT
System should be able to handle any combination of monitor plugging and
unplugging into any port.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Kubuntu 20.04.2
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-67-generic
ADDITIONAL INFORMATION
Dell Latitude E6440, Radeon GPU
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 366112] [regression] Akonadi does not load remote calendar source
https://bugs.kde.org/show_bug.cgi?id=366112 Dan changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Dan --- (In reply to Justin Zobel from comment #4) > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Yes, the issue is still present. Just verified with Kontact 5.15.3 (20.08.3). -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 156916] User-defined functions in kspread 2.x
https://bugs.kde.org/show_bug.cgi?id=156916 Dan changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdesvn] [Bug 345086] Add ssh keys handling
https://bugs.kde.org/show_bug.cgi?id=345086 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Dan changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #9 from Dan --- Hi, I have tried it in: * kate 24.05.1 * KDE Frameworks 6.3.0 * Qt 6.7.2 Still too slow (take >> minute). Could you please elaborate on the "accessibility" a bit more? How do I disable it for Kate? Thank you very much, D. -- You are receiving this mail because: You are watching all bug changes.
