[dolphin] [Bug 468412] New: Custom date format in details view
https://bugs.kde.org/show_bug.cgi?id=468412 Bug ID: 468412 Summary: Custom date format in details view Classification: Applications Product: dolphin Version: 22.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: markusba...@users.sourceforge.net CC: kfm-de...@kde.org Target Milestone: --- Currently dolphin in the details view uses the date format from the regional settings to format its dates. I would like to define my own format here, different from the global settings. Then it would for example be possible to add seconds to the displayed modified date. The setting could be a third option to the already existing date format settings. The clock widget could serve as reference as it already has such a setting. But for me a simple entry in the configuration file would be enough. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 270360] "Create new folder" in the folder panel
https://bugs.kde.org/show_bug.cgi?id=270360 Markus changed: What|Removed |Added CC||markusbauer@users.sourcefor ||ge.net --- Comment #6 from Markus --- I second the request. This option is still not available in version 22.12.3. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 295575] Standard directory context menu options not available in folder panel
https://bugs.kde.org/show_bug.cgi?id=295575 Markus changed: What|Removed |Added CC||markusbauer@users.sourcefor ||ge.net --- Comment #5 from Markus --- I also think those two context menus should be the same. But what I miss in particular are the "create new" and "action" menu entries. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 156042] seperate preview window for gwenview
https://bugs.kde.org/show_bug.cgi?id=156042 Markus changed: What|Removed |Added CC||markusbauer@users.sourcefor ||ge.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469265] Wrong window moves while draging from pager
https://bugs.kde.org/show_bug.cgi?id=469265 Markus changed: What|Removed |Added CC||m4rkus...@web.de --- Comment #1 from Markus --- Also seeing this with plasma 6.1 on wayland. Never noticed it with xorg. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488627] plasma desktop background disturbed after reconnect displays
https://bugs.kde.org/show_bug.cgi?id=488627 Markus changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Markus --- Sorry, I was running 6.0.90 at that point. Running 6.1.1 for a few days now. Didnt happen again so far, so you seem to be right. ;) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375
Markus changed:
What|Removed |Added
CC||m...@markusweimar.de
--- Comment #39 from Markus ---
For me, powerdevil only crashes when an Apple Cinema Display (model A1267) is
connected. Brightness control of this display requires acdcontrol
(https://github.com/jenrik/acdcontrol).
Linux/KDE Plasma: Arch Linux (current)
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
This line is printed in gdb when running /usr/lib/org_kde_powerdevil:
org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
# gdb.txt
Starting program: /usr/lib/org_kde_powerdevil
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7f2794c276c0 (LWP 23350)]
[New Thread 0x7f2786c0 (LWP 23351)]
[New Thread 0x7f278f7fe6c0 (LWP 23354)]
[New Thread 0x7f278effd6c0 (LWP 23355)]
[New Thread 0x7f278e7fc6c0 (LWP 23356)]
[Detaching after vfork from child process 23376]
[Detaching after vfork from child process 23378]
[Detaching after vfork from child process 23380]
[Detaching after vfork from child process 23382]
[Thread 0x7f2794c276c0 (LWP 23350) exited]
Thread 1 "org_kde_powerde" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6,
no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
Thread 6 (Thread 0x7f278e7fc6c0 (LWP 23356) "gdbus"):
#0 0x7f279a720f6f in __GI___poll (fds=0x7f2778000b90, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
#1 0x7f279976c276 in () at /usr/lib/libglib-2.0.so.0
#2 0x7f279970eb97 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3 0x7f279563414c in () at /usr/lib/libgio-2.0.so.0
#4 0x7f279973f9f5 in () at /usr/lib/libglib-2.0.so.0
#5 0x7f279a6aa9eb in start_thread (arg=) at
pthread_create.c:444
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139808071132944,
-7240220390079944981, -232, 11, 140730525680576, 139807862800384,
7334830064921388779, 7334856633901295339}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7f279a72e7cc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 5 (Thread 0x7f278effd6c0 (LWP 23355) "gmain"):
#0 0x7f279a720f6f in __GI___poll (fds=0x5615360b3ec0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
#1 0x7f279976c276 in () at /usr/lib/libglib-2.0.so.0
#2 0x7f279970c162 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3 0x7f279970c1b2 in () at /usr/lib/libglib-2.0.so.0
#4 0x7f279973f9f5 in () at /usr/lib/libglib-2.0.so.0
#5 0x7f279a6aa9eb in start_thread (arg=) at
pthread_create.c:444
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139808071132944,
-7240220390079944981, -232, 2, 140730525680688, 139807871193088,
7334828969167857387, 7334856633901295339}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7f279a72e7cc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 4 (Thread 0x7f278f7fe6c0 (LWP 23354) "pool-spawner"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f27997672b7 in g_cond_wait () at /usr/lib/libglib-2.0.so.0
#2 0x7f27996d91b4 in () at /usr/lib/libglib-2.0.so.0
#3 0x7f2799741a7e in () at /usr/lib/libglib-2.0.so.0
#4 0x7f279973f9f5 in () at /usr/lib/libglib-2.0.so.0
#5 0x7f279a6aa9eb in start_thread (arg=) at
pthread_create.c:444
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139808071132944,
-7240220390079944981, -232, 2, 140730525680896, 139807879585792,
7334832267165869803, 7334856633901295339}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#6 0x7f279a72e7cc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 3 (Thread 0x7f2786c0 (LWP 23351) "QXcbEventQueue"):
#0 0x7f279a720f6f in __GI___poll (fds=fds@entry=0x7f278fffebc8,
nfds=nfds@entry=1, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
sc_ret = -516
sc_cancel_oldtype = 0
#1 0x7f279aa9f20b in poll (__timeout=-1, __nfds=1, __fds=0x7f278fffebc8)
at /usr/include/bits/poll2.h:39
ret =
fd = {fd = 6, events = 1, reven
[plasmashell] [Bug 488627] New: plasma desktop background disturbed after reconnect displays
https://bugs.kde.org/show_bug.cgi?id=488627 Bug ID: 488627 Summary: plasma desktop background disturbed after reconnect displays Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: m4rkus...@web.de CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 170572 --> https://bugs.kde.org/attachment.cgi?id=170572&action=edit Screenshot of the bug SUMMARY After switching off and on of the displays the background not scaled correctly, but huge black borders are visible. Before (plasma 5.27.11) the problem already existed, but the black border was actually currupted, in a way that everything that was drawn there from some window remained in that area across desktops. STEPS TO REPRODUCE 1. Use wayland with a fhd display @100% and a 4k display @150%. 2. Switch both displays off and on again. OBSERVED RESULT Background of the 4k screen has a huge black border on bottom and right. (See attached screenshot.) Changing the background picture itself does not recover it. But changing between e.g. picture and folder background solves it for the moment. EXPECTED RESULT Background is displayed as before, correctly over the full screen area. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 473700] Support passkeys with kwalletmanager
https://bugs.kde.org/show_bug.cgi?id=473700 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475879] Re-Bind Additional Mouse Buttons menu does not accept bindings to other mouse buttons
https://bugs.kde.org/show_bug.cgi?id=475879 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 486015] New: "The name org.kde.kwalletd6 was not provided by any .service files")
https://bugs.kde.org/show_bug.cgi?id=486015
Bug ID: 486015
Summary: "The name org.kde.kwalletd6 was not provided by any
.service files")
Classification: Applications
Product: kwalletmanager
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: va...@kde.org
Reporter: reichelt.mar...@icloud.com
Target Milestone: ---
Created attachment 168834
--> https://bugs.kde.org/attachment.cgi?id=168834&action=edit
Screenshot
Guten Tag,
Kwallet startet nicht, folgende Meldung erscheint:
Couldn't start kwalletd:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
org.kde.kwalletd6 was not provided by any .service files")
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Couldn't start kwalletd:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name
org.kde.kwalletd6 was not provided by any .service files")
Beste Grüße
Markus
***
OS: openSUSE Leap 15.5 x86_64
Host: MS-7A70 1.0
Kernel: 5.14.21-150500.55.52-default
Uptime: 16 mins
Packages: 2501 (rpm), 10 (flatpak), 7 (snap)
Shell: bash 4.4.23
Resolution: 1920x1080
DE: Plasma 5.27.9
WM: KWin
WM Theme: ROUNDED
Theme: [Plasma], Breeze [GTK2/3]
Icons: [Plasma], breeze [GTK2/3]
Terminal: konsole
CPU: Intel i5-7500 (4) @ 3.800GHz
GPU: AMD ATI FirePro W4100
Memory: 2425MiB / 32058MiB
--
You are receiving this mail because:
You are watching all bug changes.
[kwalletmanager] [Bug 486015] "The name org.kde.kwalletd6 was not provided by any .service files")
https://bugs.kde.org/show_bug.cgi?id=486015 Markus changed: What|Removed |Added Alias||testbuero57 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 --- Comment #20 from Markus --- Should be fixed in 21.04.2 and 21.08.0, so this can be closed, right? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 442636] New: konqueror-21.08.1 with kio-5.86.0: Opens every url in separate window
https://bugs.kde.org/show_bug.cgi?id=442636 Bug ID: 442636 Summary: konqueror-21.08.1 with kio-5.86.0: Opens every url in separate window Product: konqueror Version: 21.08.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: m4rkus...@web.de Target Milestone: --- SUMMARY Since the last update of kde frameworks, konqueror opens every entered url or selected bookmark in a new window. STEPS TO REPRODUCE 1. Open konqueror (window A). 2a. Enter URL in the bar and hit enter. 2b. Select a bookmark. OBSERVED RESULT A new window (window B) is opened with the new website loading. Window A is still open. EXPECTED RESULT Load the entered url or selected bookmark in the current window, as with kio-5.85.0. Downgrading kio-5.85.0 is sufficient to make the problem disappear. I am unsure if this is a problem in kio (that should be fixed there) or if its konquerors fault. I observed it first in konqueror, so I filed it here. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 KDE Apps Version: 21.08.1 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 442636] konqueror-21.08.1 with kio-5.86.0: Opens every url in separate window
https://bugs.kde.org/show_bug.cgi?id=442636 --- Comment #1 from Markus --- Reload, upwards and home will also open a new window. Back and forward will operate in the same window. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 442636] konqueror-21.08.1 with kio-5.86.0: Opens every url in separate window
https://bugs.kde.org/show_bug.cgi?id=442636 Markus changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Markus --- I could track it back to this commit: https://invent.kde.org/frameworks/kio/-/commit/5fa55a2395cbfb6504e56bf71c869c8e49902e13 Reverting that patch ontop of kio 5.86, makes konqueror work again. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 442636] konqueror-21.08.1 with kio-5.86.0: Opens every url in separate window
https://bugs.kde.org/show_bug.cgi?id=442636 --- Comment #6 from Markus --- @David Faure: Appling your two patches (kio and konqueror) also work for me. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406479] Can you pls add noise suppression effect, like in OBS studio?
https://bugs.kde.org/show_bug.cgi?id=406479 Markus changed: What|Removed |Added CC||davir1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444295] New: OBS Studio in Wayland Crash
https://bugs.kde.org/show_bug.cgi?id=444295 Bug ID: 444295 Summary: OBS Studio in Wayland Crash Product: kwin Version: 5.23.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: davir1...@gmail.com Target Milestone: --- SUMMARY Hello i found a bug in Plasma Wayland: OBS Studio crashing with a seg fault. STEPS TO REPRODUCE Just try open OBS Studio. OBSERVED RESULT On startup, opens for 3 seconds and closes. Terminal output (seg fault): https://pastebin.com/JbJVaVzs NOTES In Sway and Plasma X11 it works 100%, it isn't really OBS Studio Bug Gdb debug: https://pastebin.com/vZYhd0kD SOFTWARE VERSIONS OS: Arch Linux Plasma Version: 5.23.1 KDE Frameworks: 5.87.0 Qt Version: 5.15.2 Kernel version: 5.10.75-1-lts Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444295] OBS Studio in Wayland Crash
https://bugs.kde.org/show_bug.cgi?id=444295 Markus changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 426886] New: config/panel is lost after wake-up with 2 monitors
https://bugs.kde.org/show_bug.cgi?id=426886 Bug ID: 426886 Summary: config/panel is lost after wake-up with 2 monitors Product: frameworks-kconfig Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: mm-...@freenet.de CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. start PC 2. login 3. configure panel / icons / background for left monitor and right monitor 4. sleep or hibernate 5. wake-up OBSERVED RESULT panel from right monitor is on the left monitor panel from left monitor is gone into nirvana all icons are on the left monitor background of right monitor is gone This forces me every time -> to log out -> reset the config -> configure all again EXPECTED RESULT that the configuration stays the same as before sleep/hibernation SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSuSE leap 15.2 with all updates (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.
[frameworks-kconfig] [Bug 426886] config/panel is lost after wake-up with 2 monitors
https://bugs.kde.org/show_bug.cgi?id=426886 --- Comment #1 from Markus --- Kernel: 5.3.18-lp152.41 Qt: 5.12.7 KDE Frameworks: 5.71.0 KDE Plasma: 5.18.5 Note: I assume, that the right monitor turns its signals off, when there is no signal from PC. This leads to the problem, that KDE has started before the right monitor sends its signal back. Proposed solutions: Possible lock of the configuration for each monitor, independent if monitor-signal is available. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460 --- Comment #2 from Markus --- When I check a new ics calendar in "Akonadi Console": In "Agents": Under "Configure->Configure Remotely...", the config does not match with what was configured in the add-dialog. (e.g. DisplayName and Path is empty.) Also checking in the "DB Browser" ind "collectiontable": The resource does not have a remoteId and the name is still the "akonadi_ical_resource_#". Is it the same for you, too? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 427290] Imported .ics calendar is named akonadi_ical_resource_* and looks empty
https://bugs.kde.org/show_bug.cgi?id=427290 Markus changed: What|Removed |Added CC||m4rkus...@web.de --- Comment #3 from Markus --- Possible duplicate of bug 425460? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 427358] New: akonadi_ical_resource stuck in InvalideCacheForCollection
https://bugs.kde.org/show_bug.cgi?id=427358 Bug ID: 427358 Summary: akonadi_ical_resource stuck in InvalideCacheForCollection Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ICal file resource Assignee: kdepim-b...@kde.org Reporter: m4rkus...@web.de Target Milestone: --- SUMMARY Running some remote ics calendars. In the past they updated automatically, but current it just stucks in InvalideCacheForCollection. STEPS TO REPRODUCE Reproducing is currently not possible, due to bug 425460. OBSERVED RESULT When I look in akonadi console in the task list of the resource it is always sitting in the current task "InvalideCacheForCollection". (With a "SyncAll" queued up but never executed.) In the code I see that "InvalidateCacheJobPrivate::itemStoreResult" is calling "emitResult", but "ResourceScheduler::taskDone" or "ResourceScheduler::executeNext" is never called again. SOFTWARE/OS VERSIONS Linux: 5.8 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 KDE Apps Version: 20.08.1 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 427358] akonadi_ical_resource stuck in InvalideCacheForCollection
https://bugs.kde.org/show_bug.cgi?id=427358 --- Comment #1 from Markus --- I recover (for the moment) by putting the agent offline, restart it, abort all activities, put it online again and manually start synchronize all. Restarting the agent again, will block in InvalideCacheForCollection again, when the (ics) file changed: "The hash has changed." I checked in resourcebase.cpp, the commit removed the connect of the result? https://github.com/KDE/akonadi/commit/97fcc9bebd790289b02680c3db7e621bb6a1a9a0#diff-b2f3b083990c6ceb5ed429b2a5fd820fL698 Reverting that bit makes InvalideCacheForCollection finish again. Was it removed on purpose? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460 --- Comment #4 from Markus --- ICalConfig seems to correctly save the data, but ICalResource does not load it. Adding "mSettings->load();" to SingleFileResource::readFile seems to work. (Although I doubt its a clean solution.) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 437161] New: konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 Bug ID: 437161 Summary: konqueror not loading anything from address bar Product: konqueror Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: m4rkus...@web.de Target Milestone: --- SUMMARY Since the last update of frameworks, konqueror is not loading anything from the address bar. I can enter urls or shortcuts, but neither pressing enter nor pressing the goto button has any reaction. (Shortcuts are not resolved to urls.) I can open urls from commandline and bookmarks. Web pages seem to work normal as well. STEPS TO REPRODUCE 1. Open konqueror. 2. Enter url. 3. Press enter or "go to" button. OBSERVED RESULT Nothing happens. EXPECTED RESULT Url should load. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 KDE Apps Version: 21.04.1 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 --- Comment #3 from Markus --- I can confirm Antonio Rojas findings: * Downgrade to kcompletion-5.81.0 works. * Revert QT_DISABLE_DEPRECATED_BEFORE=0x050e00 in kcompletion-5.82.0 works. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcompletion] [Bug 437161] konqueror not loading anything from address bar
https://bugs.kde.org/show_bug.cgi?id=437161 --- Comment #6 from Markus --- Unpatched kcompletion-5.82.0 with patched konqueror-21.04.1 works. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477707] New: Face detection stays on 0% and cannot be canceled
https://bugs.kde.org/show_bug.cgi?id=477707 Bug ID: 477707 Summary: Face detection stays on 0% and cannot be canceled Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: markusd...@web.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. start face detection 2. wait as long as you want 3. press the cancel button right of the progress bar OBSERVED RESULT There is no progress visible, the bar remains on 0%. When pressing the cancel button, nothing happens: the task won't be canceled, I have to kill the digikam process hard to continue work. EXPECTED RESULT There should be some progress visible, the cancel button should really cancel the action SOFTWARE/OS VERSIONS Windows: 11 Pro KDE Frameworks Version: 5.106.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477707] Face detection stays on 0% and cannot be canceled
https://bugs.kde.org/show_bug.cgi?id=477707 --- Comment #3 from Markus --- Thanks, with 8.2.0 it seems to work: the progress bar is now around 3% and the cancel button works as well. Great, thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450447] Synology Drive Client doesn't autostart
https://bugs.kde.org/show_bug.cgi?id=450447 Markus changed: What|Removed |Added CC||m.b.p...@web.de --- Comment #18 from Markus --- For anyone still having this issue, I found a workaround. Create a script which starts synology drive client and add a sleep infinity at the end. Add the script to your autostart. It's not pretty but it works for me. I've tried shorter sleeps, but this causes the drive client to close after the sleep is over. My script looks like this: #! /bin/sh synology-drive autostart sleep infinity -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 422413] Browser Identification doesn't work with WebEngine browser engine
https://bugs.kde.org/show_bug.cgi?id=422413 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423909] New: KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible
https://bugs.kde.org/show_bug.cgi?id=423909 Bug ID: 423909 Summary: KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible Product: kmail2 Version: 5.14.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: no-spam-...@q.com Target Milestone: --- SUMMARY KMail perceives cursor location to be vertically offset by one inch from where Wacom Bamboo graphic tablet's cursor is visible. STEPS TO REPRODUCE 1. Start Kmail 2. Move the graphic tablet's cursor into the KMail window Reproducible 100% of the time. OBSERVED RESULT KMail perceives cursor location to be vertically offset by one inch from where Wacom Bamboo graphic tablet's cursor is visible. EXPECTED RESULT The area where KMail perceives the cursor to be should be exactly the same as where the graphic tablet's cursor is visible. SOFTWARE/OS VERSIONS KMail2 Version 5.14.2 (20.04.2) Linux Kernel Version: 5.3.18-lp152.19-default KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 xf86-input-wacom Version: 0.34.2-lp152.4.6 libwacom2 Version: 1.1-lp152.2.5 libwacom-data Version: 1.1-lp152.2.5 Distro: openSUSE Leap 15.2 for X86_64 WACOM GRAPIC TABLET DETAILS Wacom Bamboo Pen Model MTE-450A set to Absolute Mode (problem also happens in Relative mode) Wacom Bamboo USB Vendor ID: 0x56a Wacom Bamboo USB Product ID: 0x65 Wacom Bamboo USB Revision: 0.00 ADDITIONAL INFORMATION I did a fresh install of openSUSE Leap 15.2 on 2020-Jul-04 (the latest and most current openSUSE version as of this report) and discovered there is a problem using a Wacom Bamboo tablet with KMail Version 5.14.2 (20.04.2). Whenever the graphic tablet's cursor is in the KMail window, the area where KMail perceives I am pointing is vertically offset by one inch below where the graphic tablet's cursor is visible on my 23 inch screen. For example, when I see my tablet's cursor hovering over the topmost message in the Message List, KMail highlights the message 3 rows below, showing KMail perceives I am pointing at the forth row from the top in the Message List, instead of perceiving I am pointing at the topmost message as it should. The same behavior presents in the Folders column. This makes KMail unusable with the graphic tablet, as I can not select any email message higher than the forth row. The icons in the toolbar are completely inaccessible by the graphic tablet's pointer and can not be activated. The menu bar is completely inaccessible by the graphic tablet's pointer and can not be activated. The same offset behavior happens when using the scroll bar button (thumb bar). The graphic tablet's pointer offset behavior is not presenting in any other application I used. This behavior was not present in any version of KMail from openSUSE Leap 15.0 or older. When I connect a mouse to my system, the area where KMail perceives the mouse is pointing is the same as where the mouse cursor is visible, as it should be, and all functionality is accessible. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423909] KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible
https://bugs.kde.org/show_bug.cgi?id=423909 --- Comment #1 from Markus --- Created attachment 129921 --> https://bugs.kde.org/attachment.cgi?id=129921&action=edit Screenshot of KMail offset behavior showing highlighted message NOT under Wacom Bamboo graphic tablet cursor -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423909] KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible
https://bugs.kde.org/show_bug.cgi?id=423909 --- Comment #3 from Markus --- (In reply to Nate Graham from comment #2) > Are you using X11 or Wayland? X11 Thank you for your prompt reply! :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423909] KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible
https://bugs.kde.org/show_bug.cgi?id=423909 --- Comment #4 from Markus --- (In reply to Nate Graham from comment #2) > Are you using X11 or Wayland? X11 and the NVIDIA accelerated driver -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423909] KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible
https://bugs.kde.org/show_bug.cgi?id=423909 --- Comment #5 from Markus --- Started KMail from KRunner and the problem persists. Started Kontact from KRunner and the problem persists. Then Tested starting KMail from the command line in Konsole with: QT_XCB_TABLET_LEGACY_COORDINATES=1 kontact Problem appears resolved. Tested starting Kontact from the command line in Konsole with: QT_XCB_TABLET_LEGACY_COORDINATES=1 kontact Problem appears resolved. So, I used Application Launcher > Edit Applications to edit the launch commands for KMail and Kontact so that they are preceded with "QT_XCB_TABLET_LEGACY_COORDINATES=1" as shown above. So, now when KMail or Kontact are started from a panel icon, or an icon in the Application Launcher, the problem persists. And When KMail or Kontact are launched from KRunner, the problem appears resolved. I REALLY don't want to use KRunner every time to start KMail or Kontact. I want to be able to start KMail and Kontact from a panel icon as I have for 15+ years. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423909] KMail perceives cursor location to be vertically offset from where Wacom Bamboo graphic tablet's cursor is visible
https://bugs.kde.org/show_bug.cgi?id=423909 --- Comment #6 from Markus --- After having used Application Launcher > Edit Applications to edit the launch commands for KMail and Kontact so that they are preceded with "QT_XCB_TABLET_LEGACY_COORDINATES=1" as shown above, I launched Kontact from KRunner, logged out, logged back in and let the session manager start Kontact. The problem persists. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425460] ical Calendar resource cannot be created
https://bugs.kde.org/show_bug.cgi?id=425460 --- Comment #6 from Markus --- Created attachment 133604 --> https://bugs.kde.org/attachment.cgi?id=133604&action=edit kdepim-runtime patch Missed to add the patch mentioned in comment#4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426886] config/panel is lost after wake-up with 2 monitors
https://bugs.kde.org/show_bug.cgi?id=426886 --- Comment #3 from Markus --- CAN anybody help?!?!?!? It's very annoying, that every day I've to turn off the running PC as the system does not recognize the monitors correctly. Once the left side is gone, then the right side. Then "systemsettings > monitor > identify" leads to the result, that both recognized monitors are the left monitor and the right monitor is on, but "nothing". Configuration is not available, right-click-menue is not available. Result > shutdown of PC and restart > remove all config-files > set up everything again. I'm using Linux no for about 20 years, but this is the biggest crap ever. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413208] New: Transform tool deleted parts of drawing
https://bugs.kde.org/show_bug.cgi?id=413208 Bug ID: 413208 Summary: Transform tool deleted parts of drawing Product: krita Version: 4.2.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: mcmarkusthegr...@gmail.com Target Milestone: --- SUMMARY After using the transform tool on a group, one layer got a chunk of it deleted. Krita crashed after saving and upon reopening the file, the layer seemed to be permanently affected. STEPS TO REPRODUCE 1. 3000x3000 canvas , 300ppi 2. Transform tool on group 3. crash OBSERVED RESULT half of the drawing deleted, krita crashes EXPECTED RESULT transform SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413224] New: plasma - control bar - desktop switcher - resized font when moving window
https://bugs.kde.org/show_bug.cgi?id=413224 Bug ID: 413224 Summary: plasma - control bar - desktop switcher - resized font when moving window Product: plasmashell Version: 5.17.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: m4rkus...@web.de Target Milestone: 1.0 Created attachment 123353 --> https://bugs.kde.org/attachment.cgi?id=123353&action=edit screenshot of desktop switcher with broken labels I have a control bar with a height of 36. Within it I added a desktop switcher (two rows, named by numbers). At the start everything is displayed correctly. But when I move a window with the mouse in the desktop switcher from one desktop to another, the fonts are scaled up and and drawed on a wrong position (shifted down). (Its a dualhead setup, dont know if it matters.) At least 5.16 and 5.17 have this problem. STEPS TO REPRODUCE 1. Control bar with heigth 36 and desktop switcher with two rows and labeled desktops. 2. Move window in desktop switcher from one desktop to another. OBSERVED RESULT Labels are scaled up and and shifted down. EXPECTED RESULT No change to label. SOFTWARE/OS VERSIONS Linux: 5.3.7 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413208] Transform tool deleted parts of drawing
https://bugs.kde.org/show_bug.cgi?id=413208 --- Comment #2 from Markus --- Created attachment 123373 --> https://bugs.kde.org/attachment.cgi?id=123373&action=edit i think this is the crash log? -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 410714] New: clazy-detaching-temporary: Don't warn on detaching pointer values
https://bugs.kde.org/show_bug.cgi?id=410714 Bug ID: 410714 Summary: clazy-detaching-temporary: Don't warn on detaching pointer values Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: markus.haberlander...@gmail.com CC: smart...@kde.org Target Milestone: --- SUMMARY I am currently fixing deprecation warnings for QChart in Qt 5.12. The following link shows the suggested change (Qt examples changed with adding the deprecation message): https://codereview.qt-project.org/c/qt/qtcharts/+/227902/4/examples/charts/scatterinteractions/chartview.cpp Doing this gives me a warning: warning: Don't call QList::first() on temporary [-Wclazy-detaching-temporary] I believe calling QList::first() is no problem here, it only means that a pointer is copied, which is not a problem IMHO. STEPS TO REPRODUCE Run clazy on the Scatter Interactions Sample in Qt 5.12. OBSERVED RESULT Clazy returns clazy-detaching-temporary EXPECTED RESULT Clazy should not return an error here. SOFTWARE/OS VERSIONS Running clazy from QtC 4.9.2, Qt version is 5.12.4. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 410714] clazy-detaching-temporary: Don't warn on detaching pointer values
https://bugs.kde.org/show_bug.cgi?id=410714 --- Comment #2 from Markus --- (In reply to Sergio Martins from comment #1) > That QList is not a pointer > > It's doing axes(Qt::Horizontal).first(), not axes(Qt::Horizontal)->first() This is of course correct, sorry for being unclear in my description. I was referring to the contents of the QList - the QList contains pointers to the axes, and it is safe and intended to manipulate these via the returned temporary QList directly. I reported this because it just didn't make sense to me to see a warning in this case, for the following reasons: * The warning is specific to the call to QList::first(), which is likely to get called on small lists. Here it's a case where typically only one item is returned. * If the list contents are pointers, it's not so expensive to have a detaching copy, nor is it so problematic since the pointers in the list are still pointing to valid objects. * The warning is about a "detaching-temporary". This first made me think that "axes(..).first()" points to a temporary and not the real pointee. But this is not the case. * It seems to be the suggested way to use the API of QChart ... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415108] Plasma crash on initialization of Latte Dock
https://bugs.kde.org/show_bug.cgi?id=415108 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419143] Plasma Shell crashes after some time while copying files and progress dialog is visible
https://bugs.kde.org/show_bug.cgi?id=419143 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405885] Akonadi fail to sync cal
https://bugs.kde.org/show_bug.cgi?id=405885 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] New: [REGRESSION] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 Bug ID: 420010 Summary: [REGRESSION] konqueror + kf 5.69: Crash when opening bookmark folder Product: konqueror Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bookmarks Assignee: konq-b...@kde.org Reporter: m4rkus...@web.de Target Milestone: --- SUMMARY I have some bookmarks organized in folder. When I open such a folder (either in the bookmark bar or in bookmark menu) konqueror will crash. STEPS TO REPRODUCE 1. Create a bookmark folder. 2. Try to open in bar or menu. OBSERVED RESULT Konqueror crashs. EXPECTED RESULT Open the bookmark folder. SOFTWARE/OS VERSIONS Linux: Gentoo KDE Plasma Version: 5.18.4.1 KDE Frameworks Version: 5.69.0 KDE Applications Version: 19.12.3 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] [REGRESSION] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 Markus changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=419981 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kbookmarks] [Bug 419981] With KBookmarks >= 5.69, Ctrl+B standard KDE shortcut overrides Konsole shortcut settings
https://bugs.kde.org/show_bug.cgi?id=419981 Markus changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=420010 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419666] [REGRESSION] konqueror does not close tabs when pressing the (x)
https://bugs.kde.org/show_bug.cgi?id=419666 Markus changed: What|Removed |Added Summary|konqueror does not close|[REGRESSION] konqueror does |tabs when pressing the (x) |not close tabs when ||pressing the (x) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] [REGRESSION] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 --- Comment #1 from Markus --- Created attachment 127485 --> https://bugs.kde.org/attachment.cgi?id=127485&action=edit Crash report -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] [REGRESSION] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 --- Comment #3 from Markus --- Thanks for the patch. I had to adapt it and apply it to kbookmarks. (konqueror from kapps 19.12.3 does not yet include it.) Now the bookmark menu works. But the folders in the bookmark bar still cause a crash. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] [REGRESSION] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 --- Comment #5 from Markus --- Created attachment 127526 --> https://bugs.kde.org/attachment.cgi?id=127526&action=edit Patch for konqbookmarkmenu in kbookmarks 5.69 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] [REGRESSION] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 --- Comment #6 from Markus --- Created attachment 127527 --> https://bugs.kde.org/attachment.cgi?id=127527&action=edit Patch for konqbookmarkbar in konqueror-19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] [REGRESSION] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 --- Comment #7 from Markus --- The last patch also fixes the crash when opening a folder in the bookmark bar. I tried to adapt the konqbookmarkmenu patch to the bar, so I am not sure if its a clean solution. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419666] [REGRESSION] konqueror does not close tabs when pressing the (x)
https://bugs.kde.org/show_bug.cgi?id=419666 --- Comment #1 from Markus --- Created attachment 127529 --> https://bugs.kde.org/attachment.cgi?id=127529&action=edit Possible fix tabCloseRequested signal was not connected. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419666] konqueror does not close tabs when pressing the (x)
https://bugs.kde.org/show_bug.cgi?id=419666 Markus changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419666] konqueror does not close tabs when pressing the (x)
https://bugs.kde.org/show_bug.cgi?id=419666 Markus changed: What|Removed |Added Summary|[REGRESSION] konqueror does |konqueror does not close |not close tabs when |tabs when pressing the (x) |pressing the (x)| -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420010] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 Markus changed: What|Removed |Added Summary|[REGRESSION] konqueror + kf |konqueror + kf 5.69: Crash |5.69: Crash when opening|when opening bookmark |bookmark folder |folder Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420407] New: Crash in systemsetting
https://bugs.kde.org/show_bug.cgi?id=420407 Bug ID: 420407 Summary: Crash in systemsetting Product: systemsettings Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: angschm...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.3.0-46-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: Clicked on the settings button of transparency in the desktop effects section. Crashes Systemsettings every time. - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f482b557800 (LWP 15794))] Thread 6 (Thread 0x7f47f2b14700 (LWP 15812)): #0 0x7f48269a80b4 in __GI___libc_read (fd=31, buf=0x7f47f2b13b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f48200692b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f48200240b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4820024570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f48200246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f48273130db in QEventDispatcherGlib::processEvents (this=0x7f47e00a8b30, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f48272b263a in QEventLoop::exec (this=this@entry=0x7f47f2b13d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f48270c3317 in QThread::exec (this=this@entry=0x55c5ab2f55f0) at thread/qthread.cpp:536 #8 0x7f4824c09605 in QQmlThreadPrivate::run (this=0x55c5ab2f55f0) at qml/ftw/qqmlthread.cpp:155 #9 0x7f48270c47ec in QThreadPrivate::start (arg=0x55c5ab2f55f0) at thread/qthread_unix.cpp:342 #10 0x7f48223e46db in start_thread (arg=0x7f47f2b14700) at pthread_create.c:463 #11 0x7f48269b988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f47fa4ad700 (LWP 15799)): #0 0x7f482006a629 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4820023470 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4820024485 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f48200246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f48273130db in QEventDispatcherGlib::processEvents (this=0x7f47f4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f48272b263a in QEventLoop::exec (this=this@entry=0x7f47fa4acd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f48270c3317 in QThread::exec (this=this@entry=0x55c5a5e96d30) at thread/qthread.cpp:536 #7 0x7f4824c09605 in QQmlThreadPrivate::run (this=0x55c5a5e96d30) at qml/ftw/qqmlthread.cpp:155 #8 0x7f48270c47ec in QThreadPrivate::start (arg=0x55c5a5e96d30) at thread/qthread_unix.cpp:342 #9 0x7f48223e46db in start_thread (arg=0x7f47fa4ad700) at pthread_create.c:463 #10 0x7f48269b988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f4803378700 (LWP 15798)): #0 0x7f48269acbf9 in __GI___poll (fds=0x7f47fc0029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f48200245c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f48200246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f48273130db in QEventDispatcherGlib::processEvents (this=0x7f47fc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f48272b263a in QEventLoop::exec (this=this@entry=0x7f4803377d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f48270c3317 in QThread::exec (this=this@entry=0x55c5a5ac7790) at thread/qthread.cpp:536 #6 0x7f4824c09605 in QQmlThreadPrivate::run (this=0x55c5a5ac7790) at qml/ftw/qqmlthread.cpp:155 #7 0x7f48270c47ec in QThreadPrivate::start (arg=0x55c5a5ac7790) at thread/qthread_unix.cpp:342 #8 0x7f48223e46db in start_thread (arg=0x7f4803378700) at pthread_create.c:463 #9 0x7f48269b988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f480bc10700 (LWP 15797)): #0 0x7f48269a80b4 in __GI___libc_read (fd=7, buf=0x7f480bc0fb60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f48200692b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f48200240b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libgli
[konqueror] [Bug 420010] konqueror + kf 5.69: Crash when opening bookmark folder
https://bugs.kde.org/show_bug.cgi?id=420010 Markus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Markus --- Seems fixed in 20.04. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419665] konqueror input focus
https://bugs.kde.org/show_bug.cgi?id=419665 Markus changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Markus --- Seems fixed in 20.04. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419666] konqueror does not close tabs when pressing the (x)
https://bugs.kde.org/show_bug.cgi?id=419666 Markus changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Markus --- Seems fixed in 20.04. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 420718] New: juk segfaut on every startup
https://bugs.kde.org/show_bug.cgi?id=420718 Bug ID: 420718 Summary: juk segfaut on every startup Product: juk Version: 20.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: m4rkus...@web.de CC: mp...@kde.org Target Milestone: --- SUMMARY Just start juk, it will fail with segfault. STEPS TO REPRODUCE 1. Start juk. OBSERVED RESULT Segfault. EXPECTED RESULT It should work. SOFTWARE/OS VERSIONS Linux: 5.6.7 KDE Plasma Version: 5.18.4.1 KDE Frameworks Version: 5.69.0 KDE Application Version: 20.04.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 420718] juk segfaut on every startup
https://bugs.kde.org/show_bug.cgi?id=420718 --- Comment #1 from Markus --- Created attachment 127957 --> https://bugs.kde.org/attachment.cgi?id=127957&action=edit Backtrace from debug build -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 420718] juk segfaut on every startup
https://bugs.kde.org/show_bug.cgi?id=420718 Markus changed: What|Removed |Added Keywords||regression --- Comment #2 from Markus --- Downgrade just juk to 19.12.3 makes it work again. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 420718] juk segfaut on every startup
https://bugs.kde.org/show_bug.cgi?id=420718
--- Comment #3 from Markus ---
QStringList allColHeaders;
allColHeaders.reserve(numColumnsToReserve + standardColHeaders.size());
std::fill_n(allColHeaders.begin(), numColumnsToReserve, i18n("JuK"));
Introduced here:
https://cgit.kde.org/juk.git/commit/playlist.cpp?id=a800c1b3ffeb1672cf889e707baf2b181d7fc8f1
https://phabricator.kde.org/R344:a800c1b3ffeb1672cf889e707baf2b181d7fc8f1
--
You are receiving this mail because:
You are watching all bug changes.
[juk] [Bug 420718] juk segfaut on every startup
https://bugs.kde.org/show_bug.cgi?id=420718 --- Comment #4 from Markus --- Created attachment 128055 --> https://bugs.kde.org/attachment.cgi?id=128055&action=edit use back_inserter with fill_n on empty list fill_n is more a overwrite than an insert. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413686] Wrong offset of the virtual desktop numbers in the virtual desktop switcher applet after activating the option
https://bugs.kde.org/show_bug.cgi?id=413686 --- Comment #11 from Markus --- Still present in 5.18.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414907] New: [regression] plasma - control bar - desktop switcher - only shows windows of secondary screen
https://bugs.kde.org/show_bug.cgi?id=414907 Bug ID: 414907 Summary: [regression] plasma - control bar - desktop switcher - only shows windows of secondary screen Product: plasmashell Version: 5.17.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: m4rkus...@web.de Target Milestone: 1.0 Created attachment 124346 --> https://bugs.kde.org/attachment.cgi?id=124346&action=edit A window on the left, secondary screen. And then just moved to be displayed on both screen. (The preview in the desktop switcher does not show the window on the primary screen.) In 5.17.3 and before, the desktop switcher displayed windows of all screens on the preview. In 5.17.4 only the windows on the secondary screen are displayed. A window overlapping both screens will only be displayed on the desktop switcher with the part that is visible in the secondary screen. plasma 5.17.4 / frameworks 5.64 / qt 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413224] plasma - control bar - desktop switcher - resized font when moving window
https://bugs.kde.org/show_bug.cgi?id=413224 --- Comment #1 from Markus --- Still valid in 5.17.4. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 386716] akonadi apparmor error: denied access to /etc/mysql/mariadb.cnf
https://bugs.kde.org/show_bug.cgi?id=386716 Markus changed: What|Removed |Added CC||m4rkus...@web.de --- Comment #4 from Markus --- Maybe also add: /usr/share/mariadb/** r, Because I see: apparmor="DENIED" operation="open" profile="mysqld_akonadi" name="/usr/share/mariadb/english/errmsg.sys" pid=10950 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 apparmor="DENIED" operation="open" profile="mysqld_akonadi" name="/usr/share/mariadb/errmsg.sys" pid=10950 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414907] [regression] plasma - control bar - desktop switcher - only shows windows of secondary screen
https://bugs.kde.org/show_bug.cgi?id=414907 --- Comment #2 from Markus --- Updated to frameworks 5.65 yesterday. Now it works again for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413224] plasma - control bar - desktop switcher - resized font when moving window
https://bugs.kde.org/show_bug.cgi?id=413224 --- Comment #2 from Markus --- Still valid for plasma 5.17.4 / frameworks 5.65 / qt 5.13.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414935] Pager widget with dual monitors only shows outline of apps for left monitor
https://bugs.kde.org/show_bug.cgi?id=414935 Markus changed: What|Removed |Added CC||m4rkus...@web.de --- Comment #3 from Markus --- It was solved by recent update of frameworks 5.65 for me. How about you? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419258] New: multiydisplay; config error; startup crash
https://bugs.kde.org/show_bug.cgi?id=419258 Bug ID: 419258 Summary: multiydisplay; config error; startup crash Product: krita Version: 4.2.8 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: www@gmx.at Target Milestone: --- Created attachment 127025 --> https://bugs.kde.org/attachment.cgi?id=127025&action=edit kritaconfig_crash SUMMARY 3display setup .. i moved the basewindow out of the maindisplay. after closing the programm when startet new it crashes. configuration file reset fixes it; includes kritarc that leads to crash STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 3 Displays, Mainwindow midl, Nivida GTX 1080 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419665] New: konqueror input focus
https://bugs.kde.org/show_bug.cgi?id=419665 Bug ID: 419665 Summary: konqueror input focus Product: konqueror Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: m4rkus...@web.de Target Milestone: --- SUMMARY Input sometimes does not appear in the selected input field. STEPS TO REPRODUCE 1. Open konqueror, enter some url, select some input on the website. Typing works as expected into that input. 2. Open a second tab in konqueror, enter some url, select some input on the website. Typing will always appear in the address bar. No matter how often or which input I select. Only way to solve: Manually select the address bar and then some input again. Now the typing works. OBSERVED RESULT Sometimes input is placed in address bar. EXPECTED RESULT Input should be placed in the currently selected input. SOFTWARE/OS VERSIONS Linux: Gentoo KDE Plasma Version: 5.18.4.1 KDE Frameworks Version: 5.68.0 KDE Applications Version: 19.12.3 Qt Version: 5.14.1 ADDITIONAL INFORMATION I have tabs enabled and also tried qtwebkit. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419666] New: konqueror does not close tabs when pressing the (x)
https://bugs.kde.org/show_bug.cgi?id=419666 Bug ID: 419666 Summary: konqueror does not close tabs when pressing the (x) Product: konqueror Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbing Assignee: konq-b...@kde.org Reporter: m4rkus...@web.de Target Milestone: --- SUMMARY Closing the tabs with the (x) on the tab itself does not work. Only the global (x) on the right side works. STEPS TO REPRODUCE 1. Open some tabs. 2. Try to close a tab by its own close-(x) button. OBSERVED RESULT The button has no result. EXPECTED RESULT The tab the button belongs to should be closed. SOFTWARE/OS VERSIONS Linux: Gentoo KDE Plasma Version: 5.18.4.1 KDE Frameworks Version: 5.68.0 KDE Applications Version: 19.12.3 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 386737] konqueror "back" history incomplete
https://bugs.kde.org/show_bug.cgi?id=386737 Markus changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Markus --- Cannot reproduce anymore, seems to be fixed somewhen... -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 114398] Should set IF_MODIFIED_SINCE and/or IF_NONE_MATCH headers
https://bugs.kde.org/show_bug.cgi?id=114398 Markus changed: What|Removed |Added CC||m4rkus...@web.de --- Comment #4 from Markus --- Still valid for 5.8.2. syndication and akregator 18.04.2 -- You are receiving this mail because: You are watching all bug changes.
[syndication] [Bug 372006] [Patch] Support feed deltas
https://bugs.kde.org/show_bug.cgi?id=372006 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 393726] New: Parallelized translation build slower then seriallized build
https://bugs.kde.org/show_bug.cgi?id=393726 Bug ID: 393726 Summary: Parallelized translation build slower then seriallized build Product: frameworks-ki18n Version: 5.45.0 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: caslav.i...@gmx.net Reporter: darkvis...@gmx.eu CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 112344 --> https://bugs.kde.org/attachment.cgi?id=112344&action=edit output of ps aux | grep msgfmt With ki18n-5.44 building plasma-workspace takes less then 10min on a AMD 6-core-FX3100MHz CPU. With 5.45 and this commit https://cgit.kde.org/ki18n.git/commit/?id=5a70e96795f1e8529780f49ab30b19fcfab12a11 build takes ages to finish (unsure how long the build takes, after 1h i cancelled the build). I reverted that commit and recompiled 5.45 and everything is fine. That commit should improve build times but for some packages, at least on my system, build will take much, much longer. Some other packages affected by that are plasma-desktop and konqueror. Using make -j6 to build the package. make -j1 does not make any difference. Any suggestions on how to debug that issue? make VERBOSE=1 does not give any more detailed output except 'make' prints some msgfmt commands which take lots of time to finish. While the package plasma-workspace compiles i tried the following command on another console: ps aux | grep -c msgfmt Sometimes i get more then 3000 active commands. Might that be the problem? Attached is a logfile of 'ps aux | grep msgfmt' that shows lots of msgfmt commands. Without the commit above i get about a maximum of 2-3 msgfmt commands at the same time and build finishes much faster. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #10 from Markus --- Yes I still have this problem. Those pipeline setting prevents it. (At cost of performance.) I still think its at least two bugs: 1. Recovery from the graphics reset is not working. (kwin bug?) 2. Graphics reset itself: Intended behaviour of driver: "Typically these are application-level bugs, but can also be driver bugs or hardware bugs." So it can be nvidia and/or "application" (kwin, or what ever application uses the hw directly) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #13 from Markus --- nvidia-settings => "X Server Display Configuration" => Button "Advanced..." => Now you should see the two checkboxes. (The setting is per device, so you need to set it twice if you use dualhead/twinview.) The cause for Xid 31 (comment#7) is very vague, so it can be kwin, it can be the application (like konqueror/akreagtor) or the nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 386737] konqueror "back" history incomplete
https://bugs.kde.org/show_bug.cgi?id=386737 --- Comment #1 from Markus --- Thats only a problem for qtwebengine. Switching back to qtwebkit its working as expected again. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454 --- Comment #9 from Markus --- Same issue here. Slackware Linux 14.2/-current with KDE 5.41.0 / Plasma 5.11.4. With Linux-4.14.12 i can not mount my mobile phone using mtp:/. Switching back to LTS-4.4.110 and everything is fine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392406] New: Krita 4.1 pre Alpha and 4.0 crash on startup on Windows 10
https://bugs.kde.org/show_bug.cgi?id=392406
Bug ID: 392406
Summary: Krita 4.1 pre Alpha and 4.0 crash on startup on
Windows 10
Product: krita
Version: 4.1
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: m...@u-plan.ch
Target Milestone: ---
After a while during startup, I get this skript error and then Krita Crashes.
IndexError
Python 3.6.2: python
Tue Mar 27 14:02:43 2018
A problem occurred in a Python script. Here is the sequence of
function calls leading up to the error, in the order they occurred.
C:\Program Files\Krita (x64)\lib\krita-python-libs\krita\dockwidgetfactory.py
in createDockWidget(self=)
10 super().__init__(_id, _dockPosition)
11 self.klass = _klass
12
13 def createDockWidget(self):
14 return self.klass()
self =
self.klass =
C:\Program Files\Krita
(x64)\share\krita\pykrita\palette_docker\palette_docker.py in
__init__(self=)
48 self.cmb_palettes.model().sort(0)
49
50 self.currentPalette =
Palette(allPalettes[list(allPalettes.keys())[0]])
51
self.cmb_palettes.currentTextChanged.connect(self.slot_paletteChanged)
52 layout.addWidget(self.cmb_palettes) # add combobox to the layout
self =
self.currentPalette undefined
global Palette =
allPalettes = {}
builtinlist =
allPalettes.keys =
IndexError: list index out of range
__cause__ = None
__class__ =
__context__ = None
__delattr__ =
__dict__ = {}
__dir__ =
__doc__ = 'Sequence index out of range.'
__eq__ =
__format__ =
__ge__ =
__getattribute__ =
__gt__ =
__hash__ =
__init__ =
__init_subclass__ =
__le__ =
__lt__ =
__ne__ =
__new__ =
__reduce__ =
__reduce_ex__ =
__repr__ =
__setattr__ =
__setstate__ =
__sizeof__ =
__str__ =
__subclasshook__ =
__suppress_context__ = False
__traceback__ =
args = ('list index out of range',)
with_traceback =
The above is a description of an error in a Python program. Here is
the original traceback:
Traceback (most recent call last):
File "C:\Program Files\Krita
(x64)\lib\krita-python-libs\krita\dockwidgetfactory.py", line 14, in
createDockWidget
return self.klass()
File "C:\Program Files\Krita
(x64)\share\krita\pykrita\palette_docker\palette_docker.py", line 50, in
__init__
self.currentPalette = Palette(allPalettes[list(allPalettes.keys())[0]])
IndexError: list index out of range
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 392227] 4.0.0.100 Does not load: Throws a python error
https://bugs.kde.org/show_bug.cgi?id=392227 --- Comment #5 from Markus --- (In reply to Alvin Wong from comment #1) > Do you somehow have none of the default palettes installed or have got them > all blacklisted? I can reproduce this crash by manually causing Krita to not > able to find any palettes. It must be something like this. I now re-installed version 4.0 Beta - it starts but doesn't find any palettes. Where are the standard palettes lokated and how do I fix this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392227] 4.0.0.100 Does not load: Throws a python error
https://bugs.kde.org/show_bug.cgi?id=392227 --- Comment #6 from Markus --- (In reply to Boudewijn Rempt from comment #4) > I'm beginning to suspect that for some people the palette docker gets loaded > before the resources are loaded. Maybe because they have a slower disk? My system runs on an SSD so speed is probably not an issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392227] 4.0.0.100 Does not load: Throws a python error
https://bugs.kde.org/show_bug.cgi?id=392227 --- Comment #7 from Markus --- (In reply to Alvin Wong from comment #1) > Do you somehow have none of the default palettes installed or have got them > all blacklisted? I can reproduce this crash by manually causing Krita to not > able to find any palettes. What do you mean by "blacklisted?" how could I fix this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392227] 4.0.0.100 Does not load: Throws a python error
https://bugs.kde.org/show_bug.cgi?id=392227 --- Comment #9 from Markus --- (In reply to Alvin Wong from comment #1) > Do you somehow have none of the default palettes installed or have got them > all blacklisted? I can reproduce this crash by manually causing Krita to not > able to find any palettes. I cannot even import any new palette bundle! If I choose the bundle file it afterwords does not appear in the dialog - so nothing happens. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392227] 4.0.0.100 Does not load: Throws a python error
https://bugs.kde.org/show_bug.cgi?id=392227 --- Comment #10 from Markus --- (In reply to Alvin Wong from comment #1) > Do you somehow have none of the default palettes installed or have got them > all blacklisted? I can reproduce this crash by manually causing Krita to not > able to find any palettes. How do you cause this exactly, step by step? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392227] 4.0.0.100 Does not load: Throws a python error
https://bugs.kde.org/show_bug.cgi?id=392227 --- Comment #12 from Markus --- (In reply to Boudewijn Rempt from comment #11) > Git commit c7d6d313e4dd72590bc2803e08c6f0b6371d3b99 by Boudewijn Rempt. > Committed on 27/03/2018 at 13:16. > Pushed by rempt into branch 'master'. > > Check whether there are any palettes in the python palette docker init > > It's entirely possible that there are none, for instance if the user > has blacklisted them all. > > M +15 -3plugins/python/palette_docker/palette_docker.py > > https://commits.kde.org/krita/c7d6d313e4dd72590bc2803e08c6f0b6371d3b99 Thank you Boudewijn. Since I am just a normal Krita user I am completely lost and confused with this issue - what does all this mean for me? I have no idea what "blacklisted" means, how this could have happended and how to resolve it. Now, in addition, my pen tablet refuses to work properly together with krita. Everything was stable before... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392227] 4.0.0.100 Does not load: Throws a python error
https://bugs.kde.org/show_bug.cgi?id=392227 --- Comment #13 from Markus --- Additional detail: clicking on the folder icon in the palette docker makes Krita crash. If you mean read/write protection by blacklisting (?): the Palette.kpl-File (and the other palettes) in \AppData\Roaming\krita\palettes is fully accessible. Is this the standard palette file? As said, I got the docker but no palettes in it. -- You are receiving this mail because: You are watching all bug changes.
