[kde] [Bug 465993] KDE 5.27 Visual Ghosting (Wayland)
https://bugs.kde.org/show_bug.cgi?id=465993 Evan changed: What|Removed |Added CC||evanmol...@gmail.com --- Comment #1 from Evan --- I experience similar - weird ghosting issues in the alt-tab application switcher. The view that lets you see all windows on all desktops similar to Mac (I think it's called "overview") also has lots of strange ghosting. Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465993] KDE 5.27 Visual Ghosting (Wayland)
https://bugs.kde.org/show_bug.cgi?id=465993 --- Comment #2 from Evan --- Aha. my issues with ghosting (and a few other issues) went away after switching the rendering backend from "software" to "automatic" in the menu spawned by this command: `kcmshell5 qtquicksettings` Not sure how it ever got set to software rendering, but this has fixed many bugs for me ranging from missing widet thumbnails, broken sysmonitor graphs, and broken titlebars (the last one only happened under wayland). My ghosting issues are all resolved now it seems... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466749] Glitching cursor and browser content when Firefox is in full screen using a fractional scaling factor
https://bugs.kde.org/show_bug.cgi?id=466749 Evan changed: What|Removed |Added CC||evanc...@gmail.com --- Comment #2 from Evan --- This is happening for me as well on 2 machines, one with 4k 150% scaling and the other 1080p 125% scaling -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468295] New: 5.27.4 Night color remains on at sunrise, can't disable
https://bugs.kde.org/show_bug.cgi?id=468295 Bug ID: 468295 Summary: 5.27.4 Night color remains on at sunrise, can't disable Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: evanc...@gmail.com CC: kwin-bugs-n...@kde.org 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 *** If automatic night color schedule is enabled, sometimes it remains enabled when it is supposed to be turned off (at sunrise). The tray icon hides like plasma thinks its disabled but the filter is still on. Trying to toggle night color off via the tray icon or in system settings does nothing, night color filter remains on until re-logging. This has happened twice on 2 different systems and distros since upgrading to 5.27.4, both times the systems were either suspended or screen offed. That may have something to do with it. Doesn't always happen. STEPS TO REPRODUCE 1. Enable night color automatic switching times based on sunrise/sunset 2. Use system at night so night color is enabled automatically 3. Put system in suspend / screen off until sunrise (unsure if needed) 4. Wake computer, night color is still enabled with no way to disable OBSERVED RESULT Night color is still enabled and can't be disabled EXPECTED RESULT Night color is toggled off SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux and Fedora Kinoite 37 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable
https://bugs.kde.org/show_bug.cgi?id=468295 --- Comment #1 from Evan --- Update: When night color won't disable, changing the night color temperature in system settings then exiting without saving fixes it until the next night/day cycle. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483076] New: Applets should not close if a new window is created in the background
https://bugs.kde.org/show_bug.cgi?id=483076 Bug ID: 483076 Summary: Applets should not close if a new window is created in the background Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: evanc...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 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 *** If an applet such as Kickoff is open and an application creates a new window, the open applet menu is force closed. This is especially annoying when trying to open multiple apps quickly with Kickoff because previously opened apps will cause Kickoff to keep closing itself. STEPS TO REPRODUCE 1. Open an app that takes a while to load (such as Steam or Discord) 2. Open the Kickoff menu 3. Wait for the app opened in step 1 to load OBSERVED RESULT The Kickoff menu is forcibly closed EXPECTED RESULT The Kickoff menu remains open. Nothing should cause applets to close themselves unless the user explicitly does so. SOFTWARE/OS VERSIONS Linux: Arch Linux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Evan changed: What|Removed |Added CC||evanc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481793] ddcutil constantly locked by powerdevil
https://bugs.kde.org/show_bug.cgi?id=481793 Evan changed: What|Removed |Added CC||evanc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480648] Display Stuck in HDR After Disabling HDR
https://bugs.kde.org/show_bug.cgi?id=480648 Evan changed: What|Removed |Added CC||evanc...@gmail.com --- Comment #12 from Evan --- I'm also seeing this with my Innocn 27m2v, but it doesn't switch between HDR and SDR in either direction. It works fine in Windows. I also have 2 Gigabyte m28u monitors that switch correctly on Linux. HDR set in Plasma: Colorspace: BT2020_RGB, HDR_OUTPUT_METADATA: 144 HDR disabled in Plasma: Colorspace: Default, HDR_OUTPUT_METADATA: 0 Monitor mode makes no difference in drm_info Colorspace/HDR_OUTPUT_METADATA Plasma 6.0.2 Arch Linux Kernel 6.8.1-zen1-1-zen -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483801] New: Night Color wrong temperature when HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=483801 Bug ID: 483801 Summary: Night Color wrong temperature when HDR is enabled Classification: Plasma Product: kdeplasma-addons Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Night Color Control Assignee: plasma-b...@kde.org Reporter: evanc...@gmail.com CC: kwin-bugs-n...@kde.org, vlad.zahorod...@kde.org 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 *** Night color is too warm when HDR is enabled on the display. STEPS TO REPRODUCE 1. Enable HDR on a display 2. Enable night color OBSERVED RESULT Night color filter is too warm EXPECTED RESULT Night color filter is the correct temperature SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439815] Window randomly become transparent, when close ghost image remains
https://bugs.kde.org/show_bug.cgi?id=439815 Evan changed: What|Removed |Added CC||e...@evanjt.com --- Comment #18 from Evan --- I've been having this problem for a while and have been doing a kwin_x11 --replace to fix it. More interesting is that on a new install on a laptop with different hardware on a blank install (same versions as below), I experience the same problem. Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408099] SVG File layers are not rendered
https://bugs.kde.org/show_bug.cgi?id=408099 Evan changed: What|Removed |Added CC||e...@neatlogic.co.nz -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408099] SVG File layers are not rendered
https://bugs.kde.org/show_bug.cgi?id=408099 Evan changed: What|Removed |Added CC|e...@neatlogic.co.nz| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable
https://bugs.kde.org/show_bug.cgi?id=468295 --- Comment #11 from Evan --- Slightly different command output when night color should be inactive but is not (day). Command output is the same before and after clicking on the night color temp slider. Configured settings: switching times: switch at sunrise/sunset day temp: 6500K night temp: 3200K Before: night color filter is visibly ON but settings say it should be off ╰─ qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect available: true currentTemperature: 6500 enabled: true inhibited: false mode: 0 previousTransitionDateTime: 1690361907 previousTransitionDuration: 2992668 running: true scheduledTransitionDateTime: 1690415773 scheduledTransitionDuration: 2992669 targetTemperature: 6500 After: Clicking the "night color temperature" slider at 3200K (where it was already at before), which causes the visible night filter to go away. ╰─ qdbus org.kde.KWin /ColorCorrect GetAll org.kde.kwin.ColorCorrect available: true currentTemperature: 6500 enabled: true inhibited: false mode: 0 previousTransitionDateTime: 1690361907 previousTransitionDuration: 2992668 running: true scheduledTransitionDateTime: 1690415773 scheduledTransitionDuration: 2992669 targetTemperature: 6500 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 Evan changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #49 from Evan --- Upgraded to 5.27.7 and these square artifacts are still appearing with blur desktop effect enabled. The artifact has the color of the desktop wallpaper behind it. https://bugsfiles.kde.org/attachment.cgi?id=156344 Linux: Arch Linux KDE Plasma Version: 5.27.7 (wayland) KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 GPU: AMD 7900XTX (mesa-git 23.3) Display scaling: 150% -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #51 from Evan --- I will reopen https://bugs.kde.org/show_bug.cgi?id=465891 then which was marked as a dup of this bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465891] Square artifacts following cursor on some UI elements
https://bugs.kde.org/show_bug.cgi?id=465891 Evan changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #3 from Evan --- This was not fixed by https://bugs.kde.org/show_bug.cgi?id=465158 so I am reopening this bug. Upgraded to 5.27.7 and these square artifacts are still appearing with blur desktop effect enabled. The artifact has the color of the desktop wallpaper behind it. Linux: Arch Linux KDE Plasma Version: 5.27.7 (wayland) KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 GPU: AMD 7900XTX (mesa-git 23.3) Display scaling: 150% -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454179] Mouse Mark: Make it fully featured like Spectacles' annotation tools
https://bugs.kde.org/show_bug.cgi?id=454179 Evan changed: What|Removed |Added CC||e...@boehs.org --- Comment #3 from Evan --- I'm not sure how this would work with the `meta+shift`? What I'm imagining is reusing spectacle components, just without the screenshot functionality. I feel like if this was to be done, mousemark would probably no longer be a desktop effect, and instead a desktop app. I can't imagine how the current shortcuts would fit in -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425141] Setting startup folder to "state from last time" makes .zshrc not load
https://bugs.kde.org/show_bug.cgi?id=425141 Evan changed: What|Removed |Added CC||e...@evanjt.com --- Comment #3 from Evan --- I can confirm this affects me too and just started happening after the update to 20.08.0. The workaround of setting the home folder in "Show on startup:" in Dolphin's startup preferences fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433493] New: [wayland] Cannot Drag Windows Across Desktops in 5.21 Wayland using KWin Shortcuts
https://bugs.kde.org/show_bug.cgi?id=433493
Bug ID: 433493
Summary: [wayland] Cannot Drag Windows Across Desktops in 5.21
Wayland using KWin Shortcuts
Product: kwin
Version: 5.21.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: evanmol...@gmail.com
Target Milestone: ---
SUMMARY
In wayland on 5.21, you cannot drag a window to another desktop using KWin
shortcuts to switch the desktop. The shortcuts don't work while holding a
window, but function fine if you aren't.
Shortcut located at:
Settings -> Workspace -> Shortcuts -> System Services -> KWin -> "Switch One
Desktop to the Right"
STEPS TO REPRODUCE
1. Bind Switch One Desktop to the Right to any key, I use Meta+Tab.
2. Next, try to "drag" a window to a different desktop by holding a window and
then hitting the next-desktop key.
3. When you press your "Switch One Desktop to the Right" key, nothing will
happen if you are holding a window. If you are not holding a window, then the
desktop will switch as expected.
OBSERVED RESULT
Switch-Desktop shortcut keys do not work while holding/dragging a window in
Wayland. The key functions as expected otherwise.
EXPECTED RESULT
Switch Desktop shortcut keys should switch to your next desktop while dragging
a window, allowing you to drag a window to a different desktop.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
GPU: Radeon RX 590
Two monitors: {1920x1080@60hz-Left, 2560x1440@144hz-Right}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 433493] Cannot move windows across desktops using KWin shortcuts while the window is being dragged
https://bugs.kde.org/show_bug.cgi?id=433493 --- Comment #2 from Evan --- Yes, if you are NOT holding/dragging a window, then the desktop will switch as expected. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 410942] Frequent segfaults when mouse-overing C typedefs in KDevelop
https://bugs.kde.org/show_bug.cgi?id=410942 evan changed: What|Removed |Added CC||evan...@protonmail.com --- Comment #2 from evan --- i think i have a similar problem, this code below is enough to reproduce it. #include "SDL2/SDL.h" SDL_Texture *foo; for me hovering on the SDL_Texture will always crashes it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 evan changed: What|Removed |Added CC||evan...@protonmail.com --- Comment #25 from evan --- excuse me, it says this bug is fixed but i still have this problem, am i missing something? i have krita 4.2.6 on kde neon 5.16.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 --- Comment #27 from evan --- (In reply to Boudewijn Rempt from comment #26) > Is that the neon package, or the appimage? it is the neon package, the appimage version works fine even with version 4.2.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 --- Comment #30 from evan --- (In reply to David Edmundson from comment #29) > If you have a debug build handy can you add a breakpoint on > > QPlatformTheme::QPlatformTheme > > and see if you hit it more than once. where can i find that line? i've never compiled krita from source before, but i'll try it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 --- Comment #32 from evan --- ok, so i tried to run krita using newly created user and the global menu works! so this is clearly a configuration issue. thought i've tried removing my kritarc file but it doesn't seems to have any effect, i also purged and reinstalled krita later but it still doesnt work. it could be the global menu's config, i don't know, can anyone help me? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 --- Comment #36 from evan --- i also use fcitx for japanese input, that could be what my problem is as well. how do you change QT_IM_MODULE value? i wanna test it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 --- Comment #38 from evan --- i can't seem to find .pam_environment file but i did disabled fcitx and the global menu works. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 --- Comment #41 from evan --- (In reply to Vladimir Yerilov from comment #40) > evan, a quick and ugly workaround is to alter krita launch command from > `krita %F` to `QT_IM_MODULE=ibus krita %F`. i see, thanks for the info. but this will disable japanese input inside krita, right? also the other workaround is to use KDE_NO_GLOBAL_MENU=1 when launching krita to disable global menu and make the menu bar shows up. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411125] New: Kontact: the akonadi PIM service is not operational
https://bugs.kde.org/show_bug.cgi?id=411125
Bug ID: 411125
Summary: Kontact: the akonadi PIM service is not operational
Product: kontact
Version: 5.12.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: evan...@protonmail.com
Target Milestone: ---
Application: kontact (5.12.0)
Qt Version: 5.12.3
Frameworks Version: 5.61.0
Operating System: Linux 4.15.0-45-generic x86_64
Distribution: KDE neon User Edition 5.16
-- Information about the crash:
- What I was doing when the application crashed:
I opened Kontact and clicked on "to-do list" in the side bar, then it
crashed.
if I click on something else like task lists or journal it doesn't crash
but the error message is still there and I can't use the component.
feeds work fine thought, I assume it is because it doesn't use the pim
service.
- Unusual behavior I noticed:
the Akonadi service failed to start, this is what it says when i try to
start it manually from terminal:
===
ev@potato-E6400:~$ akonadictl start
ev@potato-E6400:~$ Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: database server stopped unexpectedly
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial
connection!
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld-akonadi"
org.kde.pim.akonadiserver: arguments:
("--defaults-file=/home/ev/.local/share/akonadi/mysql.conf",
"--datadir=/home/ev/.local/share/akonadi/db_data/",
"--socket=/run/user/1000/akonadi/mysql.socket",
"--pid-file=/run/user/1000/akonadi/mysql.pid")
org.kde.pim.akonadiserver: stdout: ""
org.kde.pim.akonadiserver: stderr: "mysqld-akonadi: [ERROR] Could not open
required defaults file:
/home/ev/.local/share/akonadi/mysql.conf\nmysqld-akonadi: [ERROR] Fatal error
in defaults handling. Program aborted!\n"
org.kde.pim.akonadiserver: exit code: 1
org.kde.pim.akonadiserver: process error: "Unknown error"
org.kde.pim.akonadiserver: Failed to remove runtime connection config file
org.kde.pim.akonadiserver: Shutting down AkonadiServer...
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...
QFileSystemWatcher::removePaths: list is empty
QFileSystemWatcher::removePaths: list is empty
(the programm does not end unless i press ctrl+c)
===
Kontact shows an error message that says "the akonadi personal information
management service is not operational."
also when I click on the "details..." button below that message it doesn't
do anything.
i've tried removing my Akonadi config folder but it still won't work.
this is my first time reporting a bug, so sorry if the info i provided is not
so usefull, please guide me.
also sorry if this is a duplicate report
The crash can be reproduced every time.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f81ef7aebc0 (LWP 442))]
Thread 27 (Thread 0x7f80c8722700 (LWP 537)):
#0 0x7f81ec0c0bb9 in __GI___poll (fds=0x7f81b004d120, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7f81e5af05c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f81e5af06dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f81ecc1bdcb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x7f81ecbbd03a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x7f81ec9e44ca in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x7f81ec9e5c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x7f81e79bd6db in start_thread (arg=0x7f80c8722700) at
pthread_create.c:463
#8 0x7f81ec0cd88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 26 (Thread 0x7f80c8f23700 (LWP 533)):
#0 0x7f81ec0c0bf9 in __GI___poll (fds=0x7f81ac003de0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7f81e5af05c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7f81e5af06dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7f81ecc1bdcb in
QEventDispatcherGlib::processEven
[kwin] [Bug 411251] New: KWin crashed while navigating with keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=411251 Bug ID: 411251 Summary: KWin crashed while navigating with keyboard shortcuts Product: kwin Version: 5.16.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: the.fed...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.4) Qt Version: 5.13.0 Frameworks Version: 5.61.0 Operating System: Linux 5.2.9-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Switched desktops with keyboard shortcut (Ctrl+Alt+arrow), then changed music in Gnome Music Player Client 11.8.16 with keyboard shortcut (Ctrl+Right Arrow). All greebles and panels disappeared from desktop, then KWin restarted automatically at the first virtual desktop, with no apparent harm. The crash does not seem to be reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f350d122d00 (LWP 5039))] Thread 7 (Thread 0x7f35068a9700 (LWP 21723)): #0 0x7f351562a756 in ppoll () at /usr/lib/libc.so.6 #1 0x7f3514142913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f3514143fa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f35140ed5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3513f202f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f35128428f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f3513f21520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f351551c57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f35156350e3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f346a2b7700 (LWP 6462)): #0 0x7f3515522415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f346a562e9c in () at /usr/lib/dri/i965_dri.so #2 0x7f346a562a98 in () at /usr/lib/dri/i965_dri.so #3 0x7f351551c57f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f35156350e3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f34f7fff700 (LWP 5318)): #0 0x7f3515522415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f35139a9edc in () at /usr/lib/libQt5Script.so.5 #2 0x7f35139a9ef9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f351551c57f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f35156350e3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f3505c97700 (LWP 5226)): #0 0x7ffd525f8605 in () #1 0x7f3515642ee3 in clock_gettime () at /usr/lib/libc.so.6 #2 0x7f35141462a2 in () at /usr/lib/libQt5Core.so.5 #3 0x7f3514144b8a in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7f3514145156 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7f35141441d5 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f35140ed5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f3513f202f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f35128428f9 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f3513f21520 in () at /usr/lib/libQt5Core.so.5 #10 0x7f351551c57f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f35156350e3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f3507b43700 (LWP 5072)): #0 0x7f351562a756 in ppoll () at /usr/lib/libc.so.6 #1 0x7f3514142913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f3514143fa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f35140ed5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3513f202f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f3512273b37 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f3513f21520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f351551c57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f35156350e3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f350c9c7700 (LWP 5069)): #0 0x7f351562a667 in poll () at /usr/lib/libc.so.6 #1 0x7f3513e41630 in () at /usr/lib/libxcb.so.1 #2 0x7f3513e432db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f350cc99049 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f3513f21520 in () at /usr/lib/libQt5Core.so.5 #5 0x7f351551c57f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f35156350e3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f350d122d00 (LWP 5039)): [KCrash Handler] #6 0x7f35152b5289 in KWin::AbstractClient::setDesktops(QVector) () at /usr/lib/libkwin.so.5 #7 0x7f351539702
[kwin] [Bug 413371] KWin crashed when moving borderless window between virtual desktops on desktop grid
https://bugs.kde.org/show_bug.cgi?id=413371 Evan changed: What|Removed |Added CC||the.fed...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413371] KWin crashed when moving borderless window between virtual desktops on desktop grid
https://bugs.kde.org/show_bug.cgi?id=413371 --- Comment #1 from Evan --- Created attachment 127550 --> https://bugs.kde.org/attachment.cgi?id=127550&action=edit New crash information added by DrKonqi kwin_x11 (5.18.4) using Qt 5.14.2 - What I was doing when the application crashed: Moving a gwenview window between virtual desktops in grid view. Keyboard shortcut to open grid view, then mouse drag window. - Custom settings of the application: 16 virtual desktops with 10 open applications. -- Backtrace (Reduced): #6 0x7f62c3cf7749 in KWin::AbstractClient::setDesktops(QVector) () at /usr/lib/libkwin.so.5 #7 0x7f62c3d5b072 in KWin::EffectsHandlerImpl::windowToDesktops(KWin::EffectWindow*, QVector const&) () at /usr/lib/libkwin.so.5 #8 0x7f62c24300b9 in () at /usr/lib/libkwin4_effect_builtins.so.1 #9 0x7f62c3d5c8a7 in KWin::EffectsHandlerImpl::checkInputWindowEvent(QMouseEvent*) () at /usr/lib/libkwin.so.5 #10 0x7f62bb42f58d in () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376415] The ability to insert non-keyframes
https://bugs.kde.org/show_bug.cgi?id=376415 --- Comment #2 from Evan --- (In reply to Scott Petrovic from comment #1) > There are a number of animation actions that were recently added. They will > be in Krita 4.1 > > The one you are looking for will be called "insert hold frame". There are > also quite a few additional actions for pushing and pull frames around that > you will probably like. That's exciting to hear! Thanks for the response! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376415] New: The ability to insert non-keyframes
https://bugs.kde.org/show_bug.cgi?id=376415 Bug ID: 376415 Summary: The ability to insert non-keyframes Product: krita Version: 3.1.2 Platform: Windows CE OS: Windows CE Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: adrawnno...@gmail.com Target Milestone: --- Currently, to extend the length of a keyframe in the middle of an animation, I have to alt+drag the frames that follow. Ideally, when I hit the "add frame" hotkey on an existing non-keyframe, it should insert a new regular frame, increasing the length of the keyframe by one. The current behavior is that hitting "add frame" on an existing frame does nothing at all. Having the hotkey insert new frames would help me quickly time out sequences without having to switch from the keyboard to the mouse. Thanks :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 381373] New: video will not export
https://bugs.kde.org/show_bug.cgi?id=381373
Bug ID: 381373
Summary: video will not export
Product: kdenlive
Version: unspecified
Platform: Other
OS: MS Windows
Status: UNCONFIRMED
Severity: critical
Priority: NOR
Component: Video Display & Export
Assignee: j...@kdenlive.org
Reporter: evancarverme...@gmail.com
Target Milestone: ---
when I try to export my video I get this error message
Rendering of C:/Users/evanc/Desktop/japanese final.mp4 crashed
mlt_repository_init: failed to dlopen
C:\Users\evanc\Desktop\kdenlive-windows\lib\mlt/libmltvidstab.dll
("C:\Users\evanc\Desktop\kdenlive-windows\lib\mlt\libmltvidstab.dll": The
specified module could not be found.)
medium: [ ref=1, _mlt_properties_load=medium, __mlt_properties_load=medium ]
[mp4 @ 05a9fcc0] Using AVStream.codec to pass codec parameters to
muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 05a9fcc0]
Using AVStream.codec to pass codec parameters to muxers is deprecated, use
AVStream.codecpar instead.
this obviously makes it so I cannot use kdenlive at all because anything I
create is stuck in kdenlive
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 499637] Lockscreen sometimes prompts for password immediately after locking, and sometimes doesn't
https://bugs.kde.org/show_bug.cgi?id=499637 Evan changed: What|Removed |Added CC||evanc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499893] No fingerprint auth option when laptop wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=499893 Evan changed: What|Removed |Added CC||evanc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 507677] New: KWin Crash when Running SteamVR with Valve Index
https://bugs.kde.org/show_bug.cgi?id=507677
Bug ID: 507677
Summary: KWin Crash when Running SteamVR with Valve Index
Classification: Plasma
Product: kwin
Version First 6.4.3
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: emall...@proton.me
Target Milestone: ---
Application: kwin_x11 (6.4.3)
ApplicationNotResponding [ANR]: false
Qt Version: 6.9.1
Frameworks Version: 6.16.0
Operating System: Linux 6.15.7-200.fc42.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 42 (KDE Plasma Desktop Edition)"
DrKonqi: 6.4.3 [CoredumpBackend]
-- Information about the crash:
The crash consistently occurs when attempting to launch SteamVR through Steam,
with a Valve Index headset connected, while using Fedora 42 with the X11 Plasma
desktop. Steam was installed through Discover with "From Fedora Linux" (e.g.,
not the FlatPak version). I am using an NVidia RTX 2080 Super with proprietary
drivers.
The crash occurs immediately when launching SteamVR for the first time on a
given session, at which point the desktop seems to relaunch itself, although
Steam is unable to detect the headset. Subsequent launches of SteamVR do not
seem to trigger the crash, although Steam is still unable to detect the
headset. This is when running with X11.
When running through Wayland, SteamVR is semi-functional: the actual VR
rendering works fine, but some features do not work, such as audio through the
headset, or display capture to render the desktops in VR through the SteamVR
Dashboard. I was trying X11 in the hopes that these features might work, but
alas.
The headset and SteamVR are completely functional in Windows. I do not know if
this is a bug on Valve's end with Steam/SteamVR, or if this is a bug in KWin,
so I apologize if this bug report is not relevant.
Thank you very much for your time.
The crash can be reproduced every time.
-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading 34.52 M separate debug info for /usr/bin/kwin_x11...
Downloading 6.99 M separate debug info for
/home/feath/.cache/debuginfod_client/39b9e5d8a86b622d4da2771ec96be009b7125b10/debuginfo...
warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed
mapping note processing
warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed
mapping note processing
warning: Can't open file /memfd:/.nvidia_drv.XX (deleted) during
file-backed mapping note processing
warning: Can't open file /memfd:/.glXX (deleted) during file-backed mapping
note processing
warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during
file-backed mapping note processing
[New LWP 2632]
[New LWP 2641]
[New LWP 4827]
[New LWP 2882]
[New LWP 2752]
[New LWP 4828]
[New LWP 4830]
[New LWP 4829]
[New LWP 2642]
Downloading 52.16 K separate debug info for
/home/feath/.cache/debuginfod_client/01dbc2c963c9ebf309cbbaa8d03966f404f03000/debuginfo...
Downloading 773.89 K separate debug info for /lib64/libxkbcommon.so.0...
Downloading 31.16 K separate debug info for /lib64/libxcb-composite.so.0...
Downloading separate debug info for
/home/feath/.cache/debuginfod_client/691261d5796ec19272118bc62c38b012688a2359/debuginfo...
Downloading separate debug info for /lib64/libxcb-xfixes.so.0...
Downloading 149.34 K separate debug info for /lib64/libxcb-render.so.0...
Downloading 37.16 K separate debug info for /lib64/libxcb-shape.so.0...
Downloading separate debug info for /lib64/libxcb-keysyms.so.1...
Downloading 180.94 K separate debug info for /lib64/libxcb-randr.so.0...
Downloading 522.61 K separate debug info for /lib64/libxcb.so.1...
Downloading 293.73 K separate debug info for /lib64/libXi.so.6...
Downloading 4.40 M separate debug info for /lib64/libKF6Svg.so.6...
Downloading 618.44 K separate debug info for
/home/feath/.cache/debuginfod_client/f185a9e54981450cc8f4bf143ba887ef7dc15dee/debuginfo...
Downloading 201.50 K separate debug info for /lib64/libcanberra.so.0...
Downloading 45.70 K separate debug info for
/home/feath/.cache/debuginfod_client/fbded2a9c1ac7a443d361282d1d03c1f82a83f0e/debuginfo...
Downloading 166.51 M separate debug info for /lib64/libkwin-x11.so.6...
Downloading 190.06 M separate debug info for /lib64/libQt6Quick.so.6...
Downloading 45.99 M separate debug info for
/home/feath/.cache/debuginfod_client/f0a9538f6914a820847d783bf516da9ae65d7551/debuginfo...
Downloading 184.13 M separate debug info for /lib64/libQt6Qml.so.6...
Downloading 9.15 M separate debug info for /lib64/libKF6Service.so.6...
Downloading 392.09 K separate debug info for
/home/feath/.cache/debuginfod_client/353b1512fcd10101ad373332166f4b78f4801188/debuginfo...
Downloading 5.47 M separate debug
[krita] [Bug 372767] New: I am unable to draw anything at all.
https://bugs.kde.org/show_bug.cgi?id=372767 Bug ID: 372767 Summary: I am unable to draw anything at all. Product: krita Version: 3.0.1.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: evan...@hotmail.com Target Milestone: --- Created attachment 102376 --> https://bugs.kde.org/attachment.cgi?id=102376&action=edit Picture of the drawing/software I currently own a Wacom Intuous CTH-480 small tablet and it worked fine with Krita for about a week. However, not brush strokes won't show up at all while using the tablet. It isn't the tablet's fault as all drivers are updated and it works with literally everything else. I can even use it to choose the options for the brush but when I try drawing with it nothing shows up. Any solutions? -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 279451] app doesn't remember app width, if app width > screen width()
https://bugs.kde.org/show_bug.cgi?id=279451 Evan Berube changed: What|Removed |Added CC||berubeevan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 467126] New: App Doesn't Show Any Devices
https://bugs.kde.org/show_bug.cgi?id=467126 Bug ID: 467126 Summary: App Doesn't Show Any Devices Classification: Applications Product: kdeconnect Version: 22.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: berubeevan...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Launch Discover from the Fedora Applications menu. 2. Click on Search and type KDE Connect 3. Click on Launch 4. Select find devices OBSERVED RESULT No devices found. No settings to change to connect any devices. EXPECTED RESULT Devices that are on the same network show up under the list of devices. 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.
[kcalc] [Bug 487837] Starting a binary number with zero shifts the first '1' 2 positions to the left
https://bugs.kde.org/show_bug.cgi?id=487837 --- Comment #3 from Evan Teran --- It is interpreting the string "0101" as the OCTAL value "101", which is 64 decimal, or 0100 0001 binary. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487837] Starting a binary number with zero shifts the first '1' 2 positions to the left
https://bugs.kde.org/show_bug.cgi?id=487837 --- Comment #6 from Evan Teran --- I wouldn't say it is a "bug" as it is working as expected, but perhaps a mis-feature since you're not the first to report this behavior as undesirable, for example, 020 in octal *is* 16 decimal. The reason for this behavior is that conventionally the following prefixes mean: 0xNNN -> hex 0bNNN -> binary 0NNN -> octal 0oNNN -> a new, less ambiguous notation for octal, but not universally prevalent The reason for this behavior is that people copy and paste numbers and previously we've had bug reports where people said "I pasting 0x1234 in decimal mode results in NaN!" So there unfortunately seems to be no behavior that will be intuitive for everyone. Some people want it to respect the source input format, some want to respect the chosen mode. All of that being said, while I was the maintainer for kcalc 20 years ago, it's been a LONG time since I've even looked at the code. I just wanted to chime in since I saw the email and thought I could shed light on WHY it is happening so that other contributors who are more active will know where to start. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487493] kcalc miscalculates equasions
https://bugs.kde.org/show_bug.cgi?id=487493 --- Comment #2 from Evan Teran --- (In reply to Antonio Rojas from comment #1) > > 2. calculate 50 = 50 *2 > > what exactly is this meant to compute? I'm assuming that the reporter meant "50+50*2" because that would indeed produce 150. If that's so, this is not a big as kcalc implements proper order of operations, making 200 NOT the correct answer. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 444032] New: Ark zstd tarball compress failed due to non-ascii character in filenames
https://bugs.kde.org/show_bug.cgi?id=444032 Bug ID: 444032 Summary: Ark zstd tarball compress failed due to non-ascii character in filenames Product: ark Version: 21.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: evan_gree...@protonmail.com CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY If the one of the filenames contains non-ascii characters, like Chinese, Korean, Japanese, then the compressing will terminated immediately, and no tarball generated. STEPS TO REPRODUCE 1. Choose a filename with Chinese character like `文件.txt` 2. right click it and `Compress` -> `Compress to...` 3. Select `Tar-archive (Zstandard compressed)` 4. OK then the problem will occurs. OBSERVED RESULT suddenly exit (no output file) EXPECTED RESULT generate tarball 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.
[choqok] [Bug 472338] New: No longer loading twitter timelines
https://bugs.kde.org/show_bug.cgi?id=472338 Bug ID: 472338 Summary: No longer loading twitter timelines Classification: Applications Product: choqok Version: 1.7.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Twitter Assignee: scarp...@kde.org Reporter: ecogn...@michevan.id.au Target Milestone: --- SUMMARY For about a week now, Choqok no longer loads any Twitter timelines. (Realising this may be due to the various shenanigans that have been going on with the Twitter service.) STEPS TO REPRODUCE 1. Start Choqok 2. Click the Update Timelines button. OBSERVED RESULT No new posts for any Twitter account loaded. Last post within Choqok is from five days ago. EXPECTED RESULT Expect recent Twitter posts to be loaded and displayed. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461484] Unable to save unchecked timelines for Mastodon account
https://bugs.kde.org/show_bug.cgi?id=461484 --- Comment #3 from Evan McLean --- As a workaround, would there be a way to fiddle the Choqok config file to remove the Local and Federated timelines? Because they keep contributing to the unread count in the tray icon, it makes it difficult to know when there's something new in the timelines I'm more interested in. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 419005] Add a keyboard shortcut to mark current timeline as read
https://bugs.kde.org/show_bug.cgi?id=419005 Evan McLean changed: What|Removed |Added CC||ecogn...@michevan.id.au -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461484] New: Unable to save unchecked timelines for Mastodon account
https://bugs.kde.org/show_bug.cgi?id=461484 Bug ID: 461484 Summary: Unable to save unchecked timelines for Mastodon account Classification: Applications Product: choqok Version: Git Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Mastodon Assignee: scarp...@kde.org Reporter: ecogn...@michevan.id.au Target Milestone: --- SUMMARY I am trying to uncheck the Local and Federated timelines from my Mastodon account (only really want to display Home) however when I save, it does not have any effect. When I reopen the account settings, all timelines are still checked. STEPS TO REPRODUCE 1. Select Settings -> Configure Choqok from the main window's menu. 2. Select Accounts panel in configuration window. 3. Click on your Mastodon account. 4. Click Modify... 5. Click the Timelines Configuration tab. 6. Uncheck the Local and Federated timelines. 7. Click OK to save account settings. 8. Click OK in the Configuration window to save and close it. OBSERVED RESULT You'll notice in the main window that the Local and Federated timelines are still visible. If you repeat steps 1 to 5, you'll also see that all the timelines are still checked. EXPECTED RESULT The Local and Federated timelines would not be visible or retrieved. The checkboxes for those two timelines would be unchecked in the account settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7+kde+r168 (also 6.4.0) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461484] Unable to save unchecked timelines for Mastodon account
https://bugs.kde.org/show_bug.cgi?id=461484 Evan McLean changed: What|Removed |Added CC||ecogn...@michevan.id.au -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal
https://bugs.kde.org/show_bug.cgi?id=447347 --- Comment #1 from Evan Teran --- Yeah, this is a long standing thing where there's two camps. Some people people want the input data's apparent base to be respected. So pasting in `0x1234` will past in a hex value, even if you're in decimal mode Some people want the input data's apparent base to be ignored in favor of the user's selected mode. Unfortunately, I'm not sure there is a way to satisfy everyone on this one. But maybe we should lean towards the user's select mode :shrug: -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal
https://bugs.kde.org/show_bug.cgi?id=447347 --- Comment #3 from Evan Teran --- Understood, unfortunately the convention for octal numbers is "starts with a 0". Admittedly, this is considered confusing to many, so much so that python added 0o1234 as an alternative octal prefix. Perhaps kcalc could thread this needle by accepting 0o as an octal prefix, 0x as a hex prefix, 0b as a binary prefix and otherwise, assume decimal. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 448769] KCalc becomes unresponsive during computationally complex calculations
https://bugs.kde.org/show_bug.cgi?id=448769 --- Comment #3 from Evan Teran --- Right. So addressing this "right" is suprisingly complex. Basically the issue is that the code for doing arbitrary precision math has no "cancellation points". The conventional solution to this kind of thing is to do the work in a background thread, and have that thread periodically check "did the user cancel"... But the library we use (GMP) just does the work, start to finish. It doesn't ask the caller "should I continue?" at any point during a long calculation. Killing a thread mid-process is considered so dangerous, that many OSes don't even provide clean APIs to do it... The other solution, which GMP also doesn't offer, is to have the work done in small bits you can call repeatedly until complete, allowing the caller an oportunity to run the event loop themselves (and/or just stop calling the "do some work" function if the user wishes to cancel). One can imagine the math being done in a virtual machine of sorts where the caller can run as many or as few instructions towards solving the problem at a time as they please. Either way, Neither of these are really easily options for us. So what's the solution? Well, probably to literally have the work done in a seperate process which CAN be killed via a signal and communicate the results with a pipe. It will be complicated to do this nicely, but it's doable and would fully address this issue of long running calculations freezing the UI. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 461484] Unable to save unchecked timelines for Mastodon account
https://bugs.kde.org/show_bug.cgi?id=461484 --- Comment #2 from Evan McLean --- There seems to be an additional bug with the Edit Account configuration window: On the first tab, it does not remember the domain part of your credentials. So add the '@domain' part back and it then click Ok and it will close without an error message (although it still does not save the details properly). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462927] New: File won't save most of the time.
https://bugs.kde.org/show_bug.cgi?id=462927 Bug ID: 462927 Summary: File won't save most of the time. Classification: Applications Product: krita Version: 5.1.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: evandixon2...@gmail.com Target Milestone: --- This has been happening to me every time I use the software. Whenever I try to save my drawing after working on it for a while, an error would occur and it would refuse to save my file. I would always have to reset my computer to get the save function to work again. Please reply back when you can. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462927] File won't save most of the time.
https://bugs.kde.org/show_bug.cgi?id=462927 --- Comment #3 from Evan Dixon --- SESSION: 11 Dec 2022 11:08:11 -0800. Executing D:\Krita (x64)\bin\krita.exe Krita Version: 5.1.3, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 20104 -- -- -- -- -- -- -- -- 11 Dec 2022 11:08:11 -0800: Style: fusion. Available styles: windowsvista, Windows, Fusion 11 Dec 2022 11:08:13 -0800: Database is up to date. Version: 0.0.17, created by Krita 5.1.0, at Sun Oct 23 19:10:25 2022 11 Dec 2022 11:08:13 -0800: Non-store package - creating updater 11 Dec 2022 11:08:17 -0800: Importing application/x-krita to application/x-krita. Location: C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra. Real location: C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra. Batchmode: 0 11 Dec 2022 11:08:17 -0800: Loaded image from application/x-krita. Size: 3500 * 5000 pixels, 50 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 4 11 Dec 2022 11:14:36 -0800: Saving Document C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra as C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra (mime: application/x-krita). 3500 * 5000 pixels, 4 layers. 101 frames, 24 framerate. Export configuration: No configuration 11 Dec 2022 11:14:36 -0800: Create a simple backup for C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra in the same location as the file. 11 Dec 2022 11:14:36 -0800: Converting from application/x-krita to application/x-krita. Location: C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra. Real location: C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra. Batchmode: 0. Configuration: none 11 Dec 2022 11:14:38 -0800: Completed saving C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra (mime: application/x-krita). Result: Could not save merged image.. Warning: . Size: 5133488 11 Dec 2022 11:14:47 -0800: Saving Document C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra as C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra (mime: application/x-krita). 3500 * 5000 pixels, 4 layers. 101 frames, 24 framerate. Export configuration: No configuration 11 Dec 2022 11:14:47 -0800: Create a simple backup for C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra in the same location as the file. 11 Dec 2022 11:14:47 -0800: Converting from application/x-krita to application/x-krita. Location: C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra. Real location: C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra. Batchmode: 0. Configuration: none 11 Dec 2022 11:14:48 -0800: Completed saving C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra (mime: application/x-krita). Result: Could not save image profile.. Could not save merged image.. Could not save animation meta data.. Warning: . Size: 5133488 11 Dec 2022 11:14:51 -0800: Saving Document C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra as C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra (mime: application/x-krita). 3500 * 5000 pixels, 4 layers. 101 frames, 24 framerate. Export configuration: No configuration 11 Dec 2022 11:14:51 -0800: Create a simple backup for C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra in the same location as the file. 11 Dec 2022 11:14:51 -0800: Converting from application/x-krita to application/x-krita. Location: C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra. Real location: C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra. Batchmode: 0. Configuration: none 11 Dec 2022 11:14:53 -0800: Completed saving C:\Users\Evan Dixon\Desktop\Animation Objects\Planet Tombstone Comic\Crank Hotel Christmas\CHCPg4.kra (mime: application/x-krita). Result: Could not save image profile.. Could not save merged image.. Could not save animation meta data.. Warning: . Size: 5133488 11 Dec 2022 11:14:57 -0800: CLOSING SESSION SESSION: 11 Dec 2022 11:16:46 -0800. Executing D:\Krita (x64)\bin\krita.exe Krita Version: 5.1.3
[krita] [Bug 462927] File won't save most of the time.
https://bugs.kde.org/show_bug.cgi?id=462927 --- Comment #5 from Evan Dixon --- Yes, I confirm. On Sun, Dec 11, 2022 at 12:09 PM David REVOY wrote: > https://bugs.kde.org/show_bug.cgi?id=462927 > > --- Comment #4 from David REVOY --- > Hi, thanks. > I can read this line when the saving failed: > > > Could not save animation meta data.. Warning: . Size: 5133488 > > Can you confirm you have enough free space available to save your project? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462927] File won't save most of the time.
https://bugs.kde.org/show_bug.cgi?id=462927 --- Comment #7 from Evan Dixon --- Got it, thanks! On Sun, Dec 11, 2022, 1:03 PM David REVOY wrote: > https://bugs.kde.org/show_bug.cgi?id=462927 > > David REVOY changed: > >What|Removed |Added > > > Status|NEEDSINFO |REPORTED > Resolution|WAITINGFORINFO |--- > > --- Comment #6 from David REVOY --- > Ok, I switch the ticket to reported. > (note: It might take time until someone with more technical skill check > your > log and give you more answers if meanwhile, you find any information about > why > a specific couldn't be saved, or a precise description of step to > reproduce the > bug all the time, feel free to plug this information in this thread.) > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 407318] Finish MPFR support
https://bugs.kde.org/show_bug.cgi?id=407318 --- Comment #5 from Evan Teran --- I wrote the knumber library that wraps gmp in kcalc. It is definitely in need of some modernization and perhaps arblib is worth looking into as a replacement for it's big number capabilities. I'll look into it! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 411055] New: Windows Installation and use of folders is incorrect
https://bugs.kde.org/show_bug.cgi?id=411055 Bug ID: 411055 Summary: Windows Installation and use of folders is incorrect Product: kate Version: unspecified Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: e...@anobium.co.uk Target Milestone: --- Created attachment 122239 --> https://bugs.kde.org/attachment.cgi?id=122239&action=edit Bug SUMMARY Installed 64-bit Windows version. I am wanting to add new Highlighting option. The defintion files should be on Windows® these files are located %USERPROFILE%/AppData/Local/org.kde.syntax-highlighting/syntax. %USERPROFILE% usually expands to C:\\Users\\user. see https://docs.kde.org/stable5/en/applications/katepart/highlight.html 1. Files are not in the correct folder. See image 2. So, are the Highlighting files? STEPS TO REPRODUCE Install and then check APPDATA OBSERVED RESULT Cannot edit the XML. EXPECTED RESULT Need to added new Highlighting. 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.
[plasmashell] [Bug 405548] Dark breeze: invalid tooltip/widget colors with compositing enabled
https://bugs.kde.org/show_bug.cgi?id=405548 Evan Teran changed: What|Removed |Added CC||ete...@alum.rit.edu -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 419005] New: Add a keyboard shortcut to mark current timeline as read
https://bugs.kde.org/show_bug.cgi?id=419005 Bug ID: 419005 Summary: Add a keyboard shortcut to mark current timeline as read Product: choqok Version: 1.7.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: scarp...@kde.org Reporter: ecogn...@michevan.id.au Target Milestone: --- There is currently a shortcut to mark ALL timelines as read (ctrl-R by default). It would be very handy to be able to mark the currently viewed timeline as read. Equivalent to the little button that appears above the scrollbar in the top right. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 382391] Accept both decimal separators (comma and dot) from clipboard with locales where it is straightforward
https://bugs.kde.org/show_bug.cgi?id=382391 --- Comment #4 from Evan Teran --- It has been a while since I was terribly active with kcalc. Fortunately, Christopher has been awesome about handling the occasiobal issue that crops up (thanks!). I've always had mixed feeling about how to handle the separator issue. How shall we parse 1,234? 1234? Or 1 + (234/1000) You solution seems mostly reasonable, but we should be careful about the corner cases if any come up. Thanks for looking into this issue! On Thu, Feb 15, 2018, 3:19 PM martonmiklos wrote: > https://bugs.kde.org/show_bug.cgi?id=382391 > > --- Comment #3 from martonmiklos --- > Thanks Cristoph for the hint, I have created the D10555 phabricator issue. > I have no idea who should I add as reviewer. Evan Teran no longer seems to > be > active here and I have not been able to find him in the reviewer list. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 375681] Not correctly handle binary numbers
https://bugs.kde.org/show_bug.cgi?id=375681 --- Comment #1 from Evan Teran --- So, the issue here is that the number is being interpreted as Octal due to the string format. Typical conventions (that are used by kcalc) echo those of programming languages. Which are that numbers which start with "0x" are hexdecimal, "0" are octal", "0b" binary. Otherwise, it assumes the current mode. So there are two workarounds for this behavior: 1. prepend a leading 0b 2. omit the leading 0's and paste while in binary mode -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 375681] Not correctly handle binary numbers
https://bugs.kde.org/show_bug.cgi?id=375681 --- Comment #3 from Evan Teran --- Yea, this one is tough because I can see both implementations as being reasonable. As a programmer, I would expect a value of 0777 to be interpreted as octal no matter what ... because it is an octal number by convention. But you may a good point, and not everyone is a programmer. Perhaps a compromise would be to prefer using the current mode, but if that produces an invalid number (like 0x12345 in decimal mode), then fallback on the current behavior. I dunno, I'm not sure if I love that either :-/ Certainly, it is possible to make this a configurable option. So maybe that's reasonable. I'd been a while since I have been terribly active in kcalc, so bear with me while I get a bit reacquainted with the source :-). -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 403017] Qt-binding-generator "No such file or directory (os error 2)" on run
https://bugs.kde.org/show_bug.cgi?id=403017 Evan Stoll changed: What|Removed |Added CC||evan...@gmail.com --- Comment #1 from Evan Stoll --- An strace reveals that Cargo.toml cannot be found. openat(AT_FDCWD, "Cargo.toml", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) write(2, "No such file or directory", 25No such file or directory) = 25 The fix listed here: https://bugs.kde.org/show_bug.cgi?id=402528 --https://gitlab.com/rhn_mk1/rust-qt-bindings-generator/commit/d67e428ad34b5e9abb5f3d45782a1b5a62cc7dc2 -- seemed to fix the issue for me. NixOS 19.03pre167327.11cf7d6e1ff (Koi) x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 398849] Unusual behavior with pasted numbers starting with zero
https://bugs.kde.org/show_bug.cgi?id=398849 --- Comment #4 from Evan Teran --- This particular feature has always been a bit of a sticking point because it makes complete sense if you expect it, and is nothing but confusing if you don't expect it. I like S. Umar's logic in that "pasting should have the same effect as typing", except that model doesn't fit pasting hex values such as 0x1234. Really, probably the ideal solution is to add a new set of options to manage this, I can imagine at least two: 1. "Use C conventions while pasting numbers with prefixes that indicate the base" (we can work on the wording :-P). Basically, just let the user shut this feature off, but default to on to maintain current behavior. 2. "Switch modes to match the base of pasted numbers", basically we can have it switch to hex if they paste "0x1234" automatically, which would be less confusing if expected as it would show the number they actually pasted. However, it could be VERY confusing if the user pastes 010, and expects to get 10 instead of 2... If this were to exist, it should of course default to off by default. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 376655] Operations on Modulus operator were causing other operators to be erroneous
https://bugs.kde.org/show_bug.cgi?id=376655 Evan Teran changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Evan Teran --- Ah, this is an understandable misunderstanding :-). In kcalc, % is the "percent" operator, not mod! If you want the actual modulus operator, please use the "Mod" button found in both Scientific and Statistic mode (top row, just left of center). For more information on the "percent" operator, please see the manual: https://docs.kde.org/trunk5/en/kdeutils/kcalc/percent.html -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 376655] Operations on Modulus operator were causing other operators to be erroneous
https://bugs.kde.org/show_bug.cgi?id=376655 Evan Teran changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #3 from Evan Teran --- @Looserof7, One aspect of your report was that "What I mean to say is using Modulus operator is leading other calculations to be erroneous." While "%" is not the modulus operator in kcalc, it WAS in fact causing subsequent calculations to be wrong. A one line patch to resolve this has been approved, and should fix the next version of kcalc that is released. Thanks for your report :-) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 495811] New: Issues with addChildNode followed by setActiveNode
https://bugs.kde.org/show_bug.cgi?id=495811
Bug ID: 495811
Summary: Issues with addChildNode followed by setActiveNode
Classification: Applications
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: evan.lee...@gmail.com
Target Milestone: ---
Version: 5.3.0-prealpha (git e031c83)
Following code causes an internal error:
```python
from krita import *
doc = Krita.instance().activeDocument()
node = doc.createNode('test', 'paintlayer')
root = doc.rootNode()
root.addChildNode(node, None)
doc.setActiveNode(node)
doc.refreshProjection()
```
Krita has encountered an internal error:
SAFE ASSERT (krita): "shape" in file
C:/builds/graphics/krita/libs/ui/kis_node_manager.cpp, line 162
If node for setActiveNode is different from addChildNode, setActiveNode is
somehow overridden by addChildNode so the new child node is always the active
node instead of the specified node. There is no internal error in this case.
Related: https://bugs.kde.org/show_bug.cgi?id=482315
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 482315] Selecting created layer does not select it
https://bugs.kde.org/show_bug.cgi?id=482315 Evan Lee changed: What|Removed |Added CC||evan.lee...@gmail.com --- Comment #2 from Evan Lee --- Related bug: https://bugs.kde.org/show_bug.cgi?id=495811 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 495811] Issues with addChildNode followed by setActiveNode
https://bugs.kde.org/show_bug.cgi?id=495811
--- Comment #1 from Evan Lee ---
I tried to find a workaround with setChildNodes but it resulted in a similar
internal error.
I ran this script on the default document which consists of two layers: "Paint
Layer 1" and "Background".
```python
from krita import *
doc = Krita.instance().activeDocument()
activeNode = doc.activeNode()
parentNode = activeNode.parentNode()
node = doc.createNode('test', 'paintlayer')
childNodes = parentNode.childNodes()
i = childNodes.index(activeNode)
childNodes.insert(i+1, node)
print([node.name() for node in childNodes])
parentNode.setChildNodes([])
parentNode.setChildNodes(childNodes)
doc.setActiveNode(node)
doc.refreshProjection()
```
Krita has encountered an internal error:
SAFE ASSERT (krita): "shape" in file
C:/builds/graphics/krita/libs/ui/kis_node_manager.cpp, line 162
If the node for setActiveNode is different from the one inserted, setActiveNode
is ignored and the active node is set to the top child.
When `parentNode.setChildNodes([])` is commented, we get the below error
followed by the one from above.
Krita has encountered an internal error:
SAFE ASSERT (krita): "!newNode->parent()" in file
C:/builds/graphics/krita/libs/image/kis_node.cpp, line 473
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 495708] New: Node.scaleNode doesn't work when parent node is None
https://bugs.kde.org/show_bug.cgi?id=495708
Bug ID: 495708
Summary: Node.scaleNode doesn't work when parent node is None
Classification: Applications
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: evan.lee...@gmail.com
Target Milestone: ---
Version: 5.3.0-prealpha (git e031c83)
OS: Windows 11
Node.scaleNode fails to work on freshly created nodes not yet added to the
document node tree. It doesn't work if I scale the node then add it to the
tree. It works as expected if I add the node to the tree then scale it.
```python
from krita import *
def loadImageToNode(image: QImage, node: Node) -> None:
# The format is hardcoded. Maybe condition on it later.
image.convertToFormat(QImage.Format_ARGB32)
w = image.width()
h = image.height()
size = 4*w*h
imageData = image.constBits().asstring(size)
node.setPixelData(imageData, 0, 0, w, h)
doc = Krita.instance().activeDocument()
image = QImage('')
node = doc.createNode('asdf', 'paintlayer')
loadImageToNode(image, node)
activeNode = doc.activeNode()
parentNode = activeNode.parentNode()
parentNode.addChildNode(node, activeNode)
r = node.bounds()
node.scaleNode(QPointF(0,0), int(r.width()*0.48), int(r.height()*0.48),
'Bicubic')
print(int(r.width()*0.48), int(r.height()*0.48))
doc.refreshProjection()
```
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 495708] Node.scaleNode doesn't work when parent node is None
https://bugs.kde.org/show_bug.cgi?id=495708 --- Comment #1 from Evan Lee --- https://invent.kde.org/graphics/krita/-/blob/master/libs/libkis/Node.cpp#L700 This line is pretty common `if (!d->node->parent()) return;`. Is it really needed though? I would expect most transformations to be independent of the parent. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 495708] Node.scaleNode doesn't work when parent node is None
https://bugs.kde.org/show_bug.cgi?id=495708 --- Comment #3 from Evan Lee --- (In reply to Halla Rempt from comment #2) > If the node doesn't have a parent, then exactBounds() might fail, iirc. I browsed the code. It looks like that's true for mask layers which is reasonable. For non-mask layers, it doesn't seem like parent is required. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486679] Dolphin Suddenly Lost Media Type (Formerly MIME Type) Association on Its Own
https://bugs.kde.org/show_bug.cgi?id=486679 Evan McLean changed: What|Removed |Added CC||ecogn...@michevan.id.au -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 501955] New: Unable to view sent message for a short time after sending
https://bugs.kde.org/show_bug.cgi?id=501955 Bug ID: 501955 Summary: Unable to view sent message for a short time after sending Classification: Applications Product: NeoChat Version: 24.12.3 Platform: Solus OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: maddock.e...@vivaldi.net CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- Created attachment 179707 --> https://bugs.kde.org/attachment.cgi?id=179707&action=edit Screenshot showing the resulting bubble when I send a message *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Often, after sending a message to a Matrix channel, a bubble will appear in the timeline, but the text will be "This message was either not found, you do not have permission to view it, or it was sent by an ignored user" instead of the actual sent message. After a few seconds, it will update to show the actual message you sent. STEPS TO REPRODUCE 1. Open Neochat 2. Visit a room 3. Send a message OBSERVED RESULT A message bubble saying "This message was either not found, you do not have permission to view it, or it was sent by an ignored user". EXPECTED RESULT A message bubble with the message I actually sent. SOFTWARE/OS VERSIONS Solus 4.7 Endurance (Wayland) libQuotient: 0.9.1 (built against 0.9.1) KDE Frameworks: 6.12.0 Qt: Using 6.8.2 and built against 6.8.1 Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.12.19-315.current ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 501955] Unable to view sent message for a short time after sending
https://bugs.kde.org/show_bug.cgi?id=501955 --- Comment #1 from Evan Maddock --- I should note that I'm using this on Budgie and Xfce. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 481090] Neochat Scroll "bounces"/glitches
https://bugs.kde.org/show_bug.cgi?id=481090 Evan Maddock changed: What|Removed |Added CC||maddock.e...@vivaldi.net --- Comment #6 from Evan Maddock --- This still happens with extreme reliability for me on Solus, using Budgie and Xfce. NeoChat: 24.12.3 Solus 4.7 Endurance (Wayland) libQuotient: 0.9.1 (built against 0.9.1) KDE Frameworks: 6.12.0 Qt: Using 6.8.2 and built against 6.8.1 Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.12.19-315.current -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 502687] New: Neochat crashes when opening notification window
https://bugs.kde.org/show_bug.cgi?id=502687
Bug ID: 502687
Summary: Neochat crashes when opening notification window
Classification: Applications
Product: NeoChat
Version: 24.12.3
Platform: Solus
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: maddock.e...@vivaldi.net
CC: c...@carlschwan.eu, j...@redstrate.com
Target Milestone: ---
SUMMARY
When clicking the "Open All Notifications" button at the top left of NeoChat, a
window appears, and NeoChat crashes a few seconds later.
STEPS TO REPRODUCE
1. Open NeoChat
2. Click the Open All Notifications button
OBSERVED RESULT
A blank window appears for a few seconds, then NeoChat crashes.
EXPECTED RESULT
The window to populate with notifications.
SOFTWARE/OS VERSIONS
NeoChat: 24.12.3
Solus 4.7 Endurance (Wayland)
libQuotient: 0.9.3 (built against 0.9.1)
KDE Frameworks: 6.12.0
Qt: Using 6.8.3 and built against 6.8.1
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.12.21-316.current
ADDITIONAL INFORMATION
GDB backtrace:
#0 NotificationsModel::loadData()::$_0::operator()() const (this=) at
/home/build/YPKG/root/neochat/build/neochat-24.12.3/src/models/notificationsmodel.cpp:127
#1 QtPrivate::FunctorCall, QtPrivate::List<>, void,
NotificationsModel::loadData()::$_0>::call(NotificationsModel::loadData()::$_0&,
void**)::{lambda()#1}::operator()() const
(this=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:141
#2 QtPrivate::FunctorCallBase::call_internal, QtPrivate::List<>, void,
NotificationsModel::loadData()::$_0>::call(NotificationsModel::loadData()::$_0&,
v
#3 QtPrivate::FunctorCall, QtPrivate::List<>, void,
NotificationsModel::loadData()::$_0>::call(NotificationsModel::loadData()::$_0&,
void**) (f=, arg=)
at /usr/include/qt6/QtCore/qobjectdefs_impl.h:140
#4
QtPrivate::FunctorCallable::call,
void>(NotificationsModel::loadData()::$_0&, void*, void**) (f=,
arg=)
at /usr/include/qt6/QtCore/qobjectdefs_impl.h:362
#5 QtPrivate::QCallableObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*)
(which=, this_=, r=,
a=, ret=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:572
#6 0x7493e354 in QtPrivate::QSlotObjectBase::call
(this=0x5deb3da0, r=0x5d52eea0, a=0x7fffd0c0)
at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qobjectdefs_impl.h:486
#7 doActivate (sender=0x5e53a8c0, signal_index=8,
argv=0x7fffd0c0) at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qobject.cpp:4123
#8 0x7681186f in Quotient::BaseJob::finished (this=0x5e53a8c0,
_t1=0x5e53a8c0) at QuotientQt6_autogen/T4CFEN5LXH/moc_basejob.cpp:523
#9 Quotient::BaseJob::finishJob (this=0x5e53a8c0) at
/home/build/YPKG/root/libquotient/build/libQuotient-0.9.3/Quotient/jobs/basejob.cpp:611
#10 0x7493e354 in QtPrivate::QSlotObjectBase::call
(this=0x5bda71c0, r=0x5e53a8c0, a=0x7fffd198)
at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qobjectdefs_impl.h:486
#11 doActivate (sender=0x5d2b2ec0, signal_index=12,
argv=0x7fffd198) at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qobject.cpp:4123
#12 0x74f9117c in QNetworkReply::finished (this=0x5d2b2ec0) at
src/network/Network_autogen/include/moc_qnetworkreply.cpp:438
#13 QNetworkReplyHttpImplPrivate::finished (this=0x5d2b4d70) at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/network/access/qnetworkreplyhttpimpl.cpp:2158
#14 0x74933d0a in QObject::event (this=0x5d2b2ec0,
e=0x7fff2c0562d0) at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qobject.cpp:1418
#15 0x75e4d310 in QApplicationPrivate::notify_helper (this=, receiver=0x5d2b2ec0, e=0x7fff2c0562d0)
at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/widgets/kernel/qapplication.cpp:3296
#16 0x75e4e553 in QApplication::notify (this=,
receiver=0x5d2b2ec0, e=0x7fff2c0562d0)
at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/widgets/kernel/qapplication.cpp:2689
#17 0x748dc27f in QCoreApplication::notifyInternal2
(receiver=0x5d2b2ec0, event=0x7fff2c0562d0)
at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qcoreapplication.cpp:1177
#18 0x748dd593 in QCoreApplication::sendEvent (receiver=0x5d2b2ec0,
event=)
at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qcoreapplication.cpp:1617
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x55b75b30)
at
/home/build/YPKG/root/qt6-base/build/qtbase-everywhere-src-6.8.3/src/corelib/kernel/qcor
[kate] [Bug 502580] New: Show total result count in search bar when using Ctrl+F
https://bugs.kde.org/show_bug.cgi?id=502580 Bug ID: 502580 Summary: Show total result count in search bar when using Ctrl+F Classification: Applications Product: kate Version: 24.12.3 Platform: Solus OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: maddock.e...@vivaldi.net Target Milestone: --- SUMMARY When performing a text search with Ctrl+F, the search bar at the bottom of Kate does not show the current match or the total matches, like in the dedicated Search interface when pressing the Search button. It would be really handy to display the number of results like when you Ctrl+F in a web browser, or other text editors, for example, 3/12 for the third result out of 12 total results. STEPS TO REPRODUCE 1. Open a file 2. Hit Ctrl+F on the keyboard 3. Search for a text string OBSERVED RESULT The interface does not show the number of matches EXPECTED RESULT The interface to show the number of matches, and which match the cursor is currently at. SOFTWARE/OS VERSIONS Solus 4.7 Endurance (Wayland) KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482902] New: Data loss on remote mount when using rmdir in terminal
https://bugs.kde.org/show_bug.cgi?id=482902 Bug ID: 482902 Summary: Data loss on remote mount when using rmdir in terminal Classification: Applications Product: dolphin Version: 23.08.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: evan+kdeb...@cheshirehall.net CC: kfm-de...@kde.org Target Milestone: --- I just lost a fair amount of data (luckily non-critical) because dolphin in 5.x (I checked three recent versions) behaves in the following manner: 1. If a remote directory is not explored, it appears empty within the filesystem (displaying 0 items in the panel) 2. If you then use `rmdir *` in the terminal to clear empty directories, leaving those that have files, the remote mounted filesystem has the same structure, so rmdir dutifully removes all directories including all files. **Reproduction:** This can be reproduced via this on the remote system (via ssh or some other "hidden from dolphin" method): `mkdir -p $HOME/test/foo/bar ; echo MyData >$HOME/test/foo/bar/file.txt` Then go to $HOME/test using sftp: url in dolphin, open the terminal and type `rmdir foo` **Observed behavior:** All data and files are removed from the mounted filesystem. **Expected behavior:** rmdir should see files inside the directory and not remove the directory. --- I have not tested under KDE 6, but did test under a couple other 5.x Plasma desktops and observed the same behavior. [Administrivia note: I searched for this bug and the appropriate classification; I assume dolphin may be incorrect, but couldn't determine the correct classification. Please reclassify to the correct software!] -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 482902] Data loss on remote mount when using rmdir in terminal
https://bugs.kde.org/show_bug.cgi?id=482902 --- Comment #4 from Evan 'JabberWokky' Edwards --- (In reply to Fabian Vogt from comment #1) > I'm assuming you're using the sftp:// url in dolphin while the terminal sees > the kio-fuse mount, e.g. /run/user/1000/kio-fuse > Can you post a screenshot of such a situation for clarity? This is accurate. I will post a screenshot shortly. > > 1. If a remote directory is not explored, it appears empty within the > > filesystem (displaying 0 items in the panel) > > Do you mean the terminal panel or the dolphin panel? It's intentional that > directories are not populated unless necessary to avoid potentially slow > network requests. I mean the dolphin view of the filesystem -- the Details View Mode. I realize now that I am assuming without evidence that it displaying "0 items" under size is related to the behavior in the terminal panel. I have no direct reason to know that the two are related, and I completely understand why directory contents are not scanned until opened on remote filesystems. > rmdir is supposed to fail on nonempty directories, so the question is which > layer is wrong here. kio-fuse translates the rmdir call on directories to > KIO::del, unless it already knows that it has items. KIO::del appears to do > a recursive deletion by default, which is wrong in this context. For > directories, KIO::rmdir is probably more appropriate. This makes sense to me. I do not know fuse (other than as a user), and I may have erroneously assumed the error was related to presenting a empty directory within the mount. Thank you all for a prompt response; I've been using KDE since prior to the release of KDE 1.0, and I have always appreciated the work everybody has done and will do. I will take screenshots and any other requested documentation in the next couple hours when I am able to do so. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 368697] some float numbers raised to a power equal infinity
https://bugs.kde.org/show_bug.cgi?id=368697 --- Comment #1 from Evan Teran --- I believe that this is an older version of kcalc as I cannot reproduce this on my version. However, it it worth noting that for many floating point operations, kcalc, in its current implementation temporarily converts back and forth between the infinite precision and "long doubles" so that it can use libc's trig routines. I would love to switch this to an infinite precision trig library (particularly MPFR is my preference), but this is not implemented yet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356708] New: Crash while deleting large directory using bluetooth keyboard
https://bugs.kde.org/show_bug.cgi?id=356708 Bug ID: 356708 Summary: Crash while deleting large directory using bluetooth keyboard Product: plasmashell Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: eshill...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.0) Qt Version: 5.5.1 Operating System: Linux 4.2.6-301.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: I was using a bluetooth keyboard to delete a large directory from an NTFS USB 3.0 external hard drive. I dragged the directory structure from a Dolphin window to the Trash icon. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f05bbc7b940 (LWP 1923))] Thread 7 (Thread 0x7f0598f20700 (LWP 2014)): #0 0x7f05b3674ffd in poll () from /lib64/libc.so.6 #1 0x7f05ae79a16c in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f05ae79a27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f05b44b4f0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f05b445bf0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f05b4278424 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f05b859bb45 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f05b427d3ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f05b231c60a in start_thread () from /lib64/libpthread.so.0 #9 0x7f05b3680a9d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f058bfff700 (LWP 2028)): #0 0x7f05b3670bdd in read () from /lib64/libc.so.6 #1 0x7f05ae7dd390 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f05ae799c64 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f05ae79a110 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f05ae79a27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f05b44b4f0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f05b445bf0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f05b4278424 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f05b859bb45 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #9 0x7f05b427d3ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f05b231c60a in start_thread () from /lib64/libpthread.so.0 #11 0x7f05b3680a9d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f058aa4a700 (LWP 2031)): #0 0x7f05ae7de71b in g_mutex_lock () from /lib64/libglib-2.0.so.0 #1 0x7f05ae79a12e in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f05ae79a27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f05b44b4f0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f05b445bf0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f05b4278424 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f05b859bb45 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f05b427d3ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f05b231c60a in start_thread () from /lib64/libpthread.so.0 #9 0x7f05b3680a9d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f05890ea700 (LWP 2033)): #0 0x7f05b2321b10 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f05bb3ff514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f05bb3ff559 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f05b231c60a in start_thread () from /lib64/libpthread.so.0 #4 0x7f05b3680a9d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f05815a9700 (LWP 2054)): #0 0x7f05ae797209 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7f05ae7996ab in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f05ae79a09b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f05ae79a27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f05b44b4f0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f05b445bf0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f05b4278424 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f05b91458d6 in QQuickPixmapReader::run() () from /lib64/libQt5Quick.so.5 #8 0x7f05b427d3ce in QThreadPrivate:
[plasmashell] [Bug 356713] New: Crash while connecting to VPN in Connection Editor
https://bugs.kde.org/show_bug.cgi?id=356713 Bug ID: 356713 Summary: Crash while connecting to VPN in Connection Editor Product: plasmashell Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: eshill...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.0) Qt Version: 5.5.1 Operating System: Linux 4.2.6-301.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: I was clicking on a VPN connection disabling it and enabling it trying to find a state where I could select auto-start -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4cc3c8d940 (LWP 1982))] Thread 16 (Thread 0x7f4ca397d700 (LWP 2008)): #0 0x7f4cbb686ffd in poll () from /lib64/libc.so.6 #1 0x7f4cc1b21272 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f4cc1b22ee7 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f4ca5901da9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f4cbc28f3ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f4cba32e60a in start_thread () from /lib64/libpthread.so.0 #6 0x7f4cbb692a9d in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f4ca0f32700 (LWP 2015)): #0 0x7f4cbb686ffd in poll () from /lib64/libc.so.6 #1 0x7f4cb67ac16c in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f4cb67ac27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f4cbc4c6f0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f4cbc46df0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f4cbc28a424 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f4cc05adb45 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f4cbc28f3ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f4cba32e60a in start_thread () from /lib64/libpthread.so.0 #9 0x7f4cbb692a9d in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f4c93fff700 (LWP 2047)): #0 0x7f4cbb686ffd in poll () from /lib64/libc.so.6 #1 0x7f4cb67ac16c in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7f4cb67ac27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7f4cbc4c6f0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f4cbc46df0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f4cbc28a424 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f4cc05adb45 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f4cbc28f3ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f4cba32e60a in start_thread () from /lib64/libpthread.so.0 #9 0x7f4cbb692a9d in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f4c92a71700 (LWP 2053)): #0 0x7f4cb67a9192 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7f4cb67ab6ab in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f4cb67ac09b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f4cb67ac27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f4cbc4c6f0b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f4cbc46df0a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f4cbc28a424 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f4cc05adb45 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #8 0x7f4cbc28f3ce in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f4cba32e60a in start_thread () from /lib64/libpthread.so.0 #10 0x7f4cbb692a9d in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7f4c91101700 (LWP 2064)): #0 0x7f4cba333b10 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4cc3411514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7f4cc3411559 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7f4cba32e60a in start_thread () from /lib64/libpthread.so.0 #4 0x7f4cbb692a9d in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f4c895a9700 (LWP 2167)): #0 0x7f4cbb6a0590 in __libc_enable_asynccancel () from /lib64/libc.so.6 #1 0x7f4cbb682bd2 in read () from /lib64/libc.so.6 #2 0x7f4cb67ef390 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #3 0x7f4cb67abc64 in g_main_context_check () from /lib64/libglib-2.0.so.0 #4 0x7f4cb67ac110 in g_main_con
[plasmashell] [Bug 217950] Ability to set desktop wallpaper via a dbus command
https://bugs.kde.org/show_bug.cgi?id=217950 --- Comment #39 from Evan McLean --- Well, the patch[1] I have been using for the last few years ago is now no good as I've moved to Plasma 5. Until it is possible to do this via dbus again, I've found a workaround that is acceptable for my use, at least. Thought I would document it here in case anyone else finds it useful: 1. Go to Desktop Settings/Wallpaper for the screen. 2. Change Wallpaper Type to Slideshow. 3. Change timeout to a short value, I use ten seconds. 4. Add a folder that only contains the currently desired wallpaper image. Then, when you want to change wallpapers, delete the current image in the folder, and move/link[2] the new image. The new image should have a different file name to the previous one. For more than one screen, do this for each screen, each with its own folder. Have been using this technique seamlessly for a few weeks now from my wallpaper managing shell script[3]. [1] https://bugs.kde.org/show_bug.cgi?id=217950#c15 [2] Best not to copy the image. The move or linking is (effectively) an atomic operation, whereas the desktop my try to load an incomplete image file while it is being copied. [3] http://www.michevan.id.au/content/wallpaper-system-info-management-script/ (outdated) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 217950] Ability to set desktop wallpaper via a dbus command
https://bugs.kde.org/show_bug.cgi?id=217950 --- Comment #44 from Evan McLean --- Any chance of an example of how to use this? Say, from the command line with dbus-send? -- You are receiving this mail because: You are watching all bug changes.
