[valgrind] [Bug 433507] FreeBSD support, part 10
https://bugs.kde.org/show_bug.cgi?id=433507 --- Comment #4 from Paul Floyd --- (In reply to Mark Wielaard from comment #3) > Because some of the earlier patches changed some things don't apply anymore, > like .gitignore but that seems harmless. > > The configure.ac filter AC_CONFIG_FILES don't apply anymore, but it is clear > where they should go. The new memcheck/tests/freebsd/Makefile, > memcheck/tests/amd64-freebsd/Makefile and > memcheck/tests/x86-freebsd/Makefile are missing in configure.ac as > AC_CONFIG_FILES. Yes, I keep merging conflicts between patches for these. It'll all come out in the rinse. > Is the filename memcheck/tests/dw4.stderr.exp-freebad a joke or a typo? I > like the joke, but if you decide to "fix" it don't forget to also fix it in > memcheck/tests/Makefile.am EXTRA_DIST. Typo, will fix. > memcheck/tests/addressable.c I think you can just unconditionally include > signal.h. But that would mean changing the .exp files again. So probably > don't bother. > > memcheck/tests/err_disable4.c pthread_attr_setstacksize isn't freebsd > specific. Why was it added? That's a longstanding FreeBSD bug. PTHREAD_STACK_MIN is too small and any such thread will crash. > > memcheck/tests/Makefile.am > memcheck/tests/x86/more_x86_fp.c > memcheck/tests/x86/pushfpopf_s.S > memcheck/tests/str_tester.c > memcheck/tests/vbit-test/util.c > memcheck/tests/vbit-test/vbits.c > are made executable, they shouldn't Will fix. > > memcheck/tests/x86/filter_pushfpopf should be deleted (now that there is an > .in file) Well spotted. I've had the same problem several times - removed or renamed in git, but then accidentally added back after running tests and the filter was regenerated. > The posix_fadvise and posix_fallocate tests might be made non-freebsd > specific (they are posix after all). But maybe afterwards. > > The naming of filter_varinfo3 is somewhat unfortunate now that it is used by > multiple other vgtests too. > > I didn't review all of the new freebsd tests, but assume they are fine (they > don't execute locally on Fedora) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443452] [Wayland] Cursor position is offset when going over various actions on multi monitor and multi scaling setup
https://bugs.kde.org/show_bug.cgi?id=443452 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Vlad Zahorodnii --- > Move the mouse around on a non-HIDPI monitor Is the window on both hidpi and non-hidpi monitors? Can you also please run a native wayland program with WAYLAND_DEBUG=1 envvar and post the log output here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433436] Cursor offset issue
https://bugs.kde.org/show_bug.cgi?id=433436 Vlad Zahorodnii changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=443452 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443452] [Wayland] Cursor position is offset when going over various actions on multi monitor and multi scaling setup
https://bugs.kde.org/show_bug.cgi?id=443452 Vlad Zahorodnii changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=433436 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433510] FreeBSD support, part 12
https://bugs.kde.org/show_bug.cgi?id=433510
--- Comment #4 from Paul Floyd ---
(In reply to Mark Wielaard from comment #3)
> We really should rename coregrind/m_aspacemgr/aspacemgr-linux.c one day...
>
> This code formatting is really ugly/unreadable:
{ VKI_MAP_STACK }
I'll see what I can do. Just defining this to 0 in FreeBSD should also work,
with a comment to explain that it doesn't really exist.
> - TRACE_SYMTAB("rx_map: avma %#lx size %lu foff %ld\n",
> + TRACE_SYMTAB("rx_map: avma %#lx size %lu foff %lld\n",
^^^ generates warnings
I think that both versions probably generate warnings on either 32bit or 64bit
systems, and that we should use a macro to choose l or ll.
>
> In coregrind/m_debuginfo/storage.c we have:
>
> +#if defined(VGO_freebsd)
> + if (sym->size == 0)
> + sym->size = 1;
> +#endif
>
> Why? Do we not want to ignore zero-sized syms? Are those really size 1?
I don't know why this was done, it predates my work and I can#t see the change
in any git or mercurial repo that I have access to. I'll do some more testing
to see if it is still needed.
>
> coregrind/pub_core_gdbserver.h What is the padding in padding? I see it is
> actually set in coregrind/m_gdbserver/remote-utils.c remote_open. But why?
I don't remember exactly what the problem was, but this is the implicit padding
that is there anyway. The memory gets initialized with brace intialization
leaving the padding uninitialized. This code makes sure that the entire struct
gets initialized, even the unused last 4 bytes.
> The logic and the defines feel swapped in VG_(is32on64)(void). But I might
> misunderstand why the check for that file is done.
It's very hard to tell when a 32bit process is running on an amd64 kernel (for
instance, all sysctls behave like a true 32bit system). When compiling the
amd64 binary it returns false - that can only ever be 64on64. When compiling
for x86 that is either on an x86 system or and amd64 system building both amd64
and x86. I'm using the link loader to tell them apart. This isn't totally bomb
proof. Someone could try to run an x86 built Valgrind on amd64 or add a
/libexec/ld-elf32.so.1 on an x86 system, but I'm not going to try to handle
user foolishness like that.
>
> /* Number of file descriptors that Valgrind tries to reserve for
> its own use - just a small constant. */
> +#if defined(VGO_freebsd)
> +#define N_RESERVED_FDS (20)
> +#else
> #define N_RESERVED_FDS (12)
> +#endif
>
> Why does FreeBSD need 8 more?
Again that predates my work and I'll recheck.
> I don't understand what SIGSYS is/does. This patch adds/clears it
> unconditionally, not just for freebsd. Is that correct?
SIGSYS gets sent for a non-existent syscall. I'll write a small test and see if
it's needed on Linux and FreeBSD.
> Why this in coregrind/m_main.c
>
> +void *memcpy(void *dest, const void *src, size_t n);
> +void *memcpy(void *dest, const void *src, size_t n) {
> + return VG_(memcpy)(dest, src, n);
> +}
> +void* memmove(void *dest, const void *src, SizeT n);
> +void* memmove(void *dest, const void *src, SizeT n) {
> + return VG_(memmove)(dest,src,n);
> +}
> +void* memset(void *s, int c, SizeT n);
> +void* memset(void *s, int c, SizeT n) {
> + return VG_(memset)(s,c,n);
> +}
That's clang's fault. clang can convert things like
structA = {0};
and
structA = structB;
into memset and memcoy calls, so FreeBSD needs them in the tool exe.
> aha, this is where the realloc support is added. Dont forget to close bug
> #407589.
>
> Was this deliberate?
>
> diff --git a/coregrind/m_scheduler/sema.c b/coregrind/m_scheduler/sema.c
> index 61e10dcf0..5954cdf8f 100644
> --- a/coregrind/m_scheduler/sema.c
> +++ b/coregrind/m_scheduler/sema.c
> @@ -108,8 +108,8 @@ void ML_(sema_down)( vg_sema_t *sema, Bool as_LL )
> INNER_REQUEST(ANNOTATE_RWLOCK_ACQUIRED(sema, /*is_w*/1));
>
> if (ret != 1)
> - VG_(debugLog)(0, "scheduler",
> - "VG_(sema_down): read returned %d\n", ret);
> + VG_(debugLog)(1, "scheduler",
> + "ML_(sema_down): read returned %d\n", ret);
Yes, that was deliberate, it was causing too much noise with debug 0 on
FreeBSD.
> This change:
>
> @@ -2459,9 +2528,9 @@ void async_signalhandler ( Int sigNo,
> info->si_code = sanitize_si_code(info->si_code);
>
> if (VG_(clo_trace_signals))
> - VG_(dmsg)("async signal handler: signal=%d, tid=%u, si_code=%d, "
> + VG_(dmsg)("async signal handler: signal=%d, vgtid=%u, tid=%u,
> si_code=%d, "
> "exitreason %s\n",
> -sigNo, tid, info->si_code,
> +sigNo, VG_(gettid)(), tid, info->si_code,
> VG_(name_of_VgSchedReturnCode)(tst->exitreason));
>
> /* See similar logic in VG_(poll_signals). */
>
> Causes this warning:
I'll fix that.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 443461] New: 音量增加后输出视频开头部分有很大噪音
https://bugs.kde.org/show_bug.cgi?id=443461 Bug ID: 443461 Summary: 音量增加后输出视频开头部分有很大噪音 Product: kdenlive Version: 21.08.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: 825117...@qq.com Target Milestone: --- 21.08.1版本 64位 Windows 10 专业版 mp4视频音效使用3个1000%gain 1个标准化（所有参数都跳到最低） 视频开始部分噪音很大 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443244] find next/previous icon inconsistence
https://bugs.kde.org/show_bug.cgi?id=443244 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||21.12 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441983] The clip monitor should show the clips in the timeline
https://bugs.kde.org/show_bug.cgi?id=441983 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441819] I can't launch Krita: it freezes on start-up
https://bugs.kde.org/show_bug.cgi?id=441819 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428245] When I use the either of the mirror tools sometimes they don't work. It will work one day just for a certain amount of time then not work at all.
https://bugs.kde.org/show_bug.cgi?id=428245 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425527] Color Picker is acting weird
https://bugs.kde.org/show_bug.cgi?id=425527 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442165] Wayland session: Changing the window decoration makes desktop environment crash
https://bugs.kde.org/show_bug.cgi?id=442165 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442153] Steam doesn't display an icon
https://bugs.kde.org/show_bug.cgi?id=442153 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430344] Minimized and then reopen the main window cause canvas rotation
https://bugs.kde.org/show_bug.cgi?id=430344 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433361] Krita crashes after changing the font size of the SVG text tool
https://bugs.kde.org/show_bug.cgi?id=433361 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 441735] Files view: Only show "Play" button if folder contains media
https://bugs.kde.org/show_bug.cgi?id=441735 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424908] After closing document the cursor (and outline) is not visible until one leaves/enters the canvas
https://bugs.kde.org/show_bug.cgi?id=424908 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440703] [Wayland] Selected text in Firefox (wayland native mode) cannot be middle-click-pasted into other apps
https://bugs.kde.org/show_bug.cgi?id=440703 --- Comment #21 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433083] Searching for the first time sometimes breaks the layouting
https://bugs.kde.org/show_bug.cgi?id=433083 --- Comment #14 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 442056] shortcut stop working
https://bugs.kde.org/show_bug.cgi?id=442056 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424097] 5.1.0 appimage crashes when manually adding security prices
https://bugs.kde.org/show_bug.cgi?id=424097 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 443460] New: Gwenview crashed on opening new PNG file from within Dolphin file browser
https://bugs.kde.org/show_bug.cgi?id=443460
Bug ID: 443460
Summary: Gwenview crashed on opening new PNG file from within
Dolphin file browser
Product: gwenview
Version: 19.12.3
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: el...@theliddingtons.nz
Target Milestone: ---
Application: gwenview (19.12.3)
Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.11.0-37-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.04.3 LTS
-- Information about the crash:
- What I was doing when the application crashed:
Opening a newly created .PNG file (newly created with 'Spectacle' screenshot
app)
- Unusual behavior I noticed:
Border (Maximised) surrounding Dolphin file browser changed to Gwenview (header
etc), but still showing file browser contents.
Resize window to 2/3 screen shows same result (slightly corrupted view, ie few
lines within window).
Closed Gwenview via upper right (X) button.
Tried opening same file again, exact same result.
Closed Gwenview.
Opened same file ("Open with..." menu) with Firefox, loaded instantly.
Tried Gwenview (already set as PNG default viewer) five minutes later, opens
original file successfully.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fde59b38440 (LWP 4190))]
Thread 13 (Thread 0x7fde3c845700 (LWP 4203)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x56385ae1c610) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56385ae1c5c0,
cond=0x56385ae1c5e8) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x56385ae1c5e8, mutex=0x56385ae1c5c0) at
pthread_cond_wait.c:638
#3 0x7fde4a834e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7fde4a834a7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x7fde5dba7609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7fde5f49a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 12 (Thread 0x7fde3d046700 (LWP 4202)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x56385ae1c610) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56385ae1c5c0,
cond=0x56385ae1c5e8) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x56385ae1c5e8, mutex=0x56385ae1c5c0) at
pthread_cond_wait.c:638
#3 0x7fde4a834e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7fde4a834a7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x7fde5dba7609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7fde5f49a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 11 (Thread 0x7fde3d847700 (LWP 4201)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x56385ae1bf08) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56385ae1beb8,
cond=0x56385ae1bee0) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x56385ae1bee0, mutex=0x56385ae1beb8) at
pthread_cond_wait.c:638
#3 0x7fde4a834e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7fde4a834a7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x7fde5dba7609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7fde5f49a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 10 (Thread 0x7fde3e048700 (LWP 4200)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x56385ae1bf08) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56385ae1beb8,
cond=0x56385ae1bee0) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x56385ae1bee0, mutex=0x56385ae1beb8) at
pthread_cond_wait.c:638
#3 0x7fde4a834e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7fde4a834a7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5 0x7fde5dba7609 in start_thread (arg=) at
pthread_create.c:477
#6 0x7fde5f49a293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 9 (Thread 0x7fde3e849700 (LWP 4199)):
#0 futex_wait_cancelable (private=, expected=0,
futex_word=0x56385ae1bf08) at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56385ae1beb8,
cond=0x56385ae1bee0) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x56385ae1bee0, mutex=0x56385ae1beb8) at
pthread_cond_wait.c:638
#3 0x7fde4a834e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4 0x7fde4a
[Discover] [Bug 406295] State of checkboxes is not immediately updated after I enable/disable a firmwares source in "Settings" page
https://bugs.kde.org/show_bug.cgi?id=406295 Patrick Silva changed: What|Removed |Added CC||ad...@happyassassin.net --- Comment #2 from Patrick Silva --- *** Bug 443456 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443456] Toggling repo in Discover doesn't redraw the checkbox, confusing users
https://bugs.kde.org/show_bug.cgi?id=443456 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 406295 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 443459] New: The Akonadi personal information management service is not running. This application cannot be used without it.
https://bugs.kde.org/show_bug.cgi?id=443459 Bug ID: 443459 Summary: The Akonadi personal information management service is not running. This application cannot be used without it. Product: kmail2 Version: 5.15.3 Platform: Other OS: Other Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: hunt94...@gmail.com Target Milestone: --- The Akonadi personal information management service is not running. This application cannot be used without it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 Wing Hong Chan changed: What|Removed |Added CC||winghongc...@vivaldi.net -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441184] SUGGESTION Krita 5 - Recorder [Export timelapse] - Option: "Hold Last Frame for: X seconds"
https://bugs.kde.org/show_bug.cgi?id=441184 Reinold Rojas changed: What|Removed |Added CC||rojasrein...@gmail.com Assignee|krita-bugs-n...@kde.org |rojasrein...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 443458] New: Virtual Desktop on Taskbar Maybe Triggered by KScreen 2
https://bugs.kde.org/show_bug.cgi?id=443458 Bug ID: 443458 Summary: Virtual Desktop on Taskbar Maybe Triggered by KScreen 2 Product: KScreen Version: 5.18.7 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: linuxv...@yahoo.com Target Milestone: --- SUMMARY My setup is two monitors. One monitor is setup through a KVM switch, so I can switch between two computers on that one monitor. By default, System Settings->Startup and Shutdown->Background Services has Startup Services/KScreen 2 running. KScreen 2 allows KDE to reconfigure the desktop screens, as necessary, whenever a monitor is added or disconnected, a very handy feature. In my situation, I do not want KScreen 2 to do what it does normally, as whenever I switch the KVM to the other computer, the main computer will reconfigure the desktop to a single monitor. By disabling KScreen 2, I can use the KVM switch to peek at the other computer screen without disruption of the monitors or desktops. This has been working well... with one exception... On the taskbar, there's a mini representation of the desktop, Virtual Desktop, which in two monitor mode, shows it as a wide desktop over two monitors, as expected, BUT whenever I use the KVM switch to peek at the other computer, the mini representation of the desktop squishes back to a single desktop on one monitor, even though KScreen 2 isn't running. There is still something in the interface that is triggering the mini desktop representation to update, even without it actually updating, as I am not using KScreen 2 and have a fixed desktop config of two monitors. Could it be that there's something in the background with KScreen 2 triggering the Virtual Desktop update? STEPS TO REPRODUCE 1. Turn off KScreen 2 on dual monitor setup and configure for one wide desktop across two monitors 2. Switch input for one monitor to another computer OBSERVED RESULT Virtual Desktop on Taskbar halves EXPECTED RESULT Virtual Desktop on Taskbar is unchanged SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Leap 15.2 (available in About System) KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION Maybe it's a taskbar issue? But where to report that? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443151] Some fill pattern cannot be selected.
https://bugs.kde.org/show_bug.cgi?id=443151 --- Comment #13 from healer.ha...@gmail.com --- Hello Halla Rempt, I tried Krita 5.0.0 379571f (build 1260) but the problem still persist. Did you able to select those patterns on your Windows machine? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443457] Handling padding when scaling
https://bugs.kde.org/show_bug.cgi?id=443457 --- Comment #2 from varlesh --- Created attachment 142248 --> https://bugs.kde.org/attachment.cgi?id=142248&action=edit 100% scale with No Borders option -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443457] Handling padding when scaling
https://bugs.kde.org/show_bug.cgi?id=443457 --- Comment #1 from varlesh --- Created attachment 142247 --> https://bugs.kde.org/attachment.cgi?id=142247&action=edit 150% scale with No Borders option -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443457] New: Handling padding when scaling
https://bugs.kde.org/show_bug.cgi?id=443457 Bug ID: 443457 Summary: Handling padding when scaling Product: kwin Version: 5.22.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: varl...@gmail.com Target Milestone: --- KWin not right handling padding when scaling with not rounded values - 125%, 150%, 175%, 225% and etc... STEP FOR REPRODUCE: - Install any Aurorae Theme - Set Scale to 150% - Set No Borders on Systemsettings - LogOut and LogIn - Result X11 1.20.11 KWin 5.22.5 Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.14.0-9.5-liquorix-amd64 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i5-10400F CPU @ 2.90GHz Memory: 7.7 ГиБ of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 More info here: https://github.com/PapirusDevelopmentTeam/materia-kde/issues/127 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443449] Exporting with global themes does not save new adaptive location configuration
https://bugs.kde.org/show_bug.cgi?id=443449 doncb...@gmail.com changed: What|Removed |Added CC||doncb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443449] Exporting with global themes does not save new adaptive location configuration
https://bugs.kde.org/show_bug.cgi?id=443449 --- Comment #3 from doncb...@gmail.com --- Also, for whatever reason, this bug disappeared from my list of open bugs so I could not find it when I went to that page. Is this an intentional function of needsinfo? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443449] Exporting with global themes does not save new adaptive location configuration
https://bugs.kde.org/show_bug.cgi?id=443449 --- Comment #2 from doncb...@gmail.com --- (In reply to Nate Graham from comment #1) > I you add this value manually to the exported config file, does it take > effect as expected? > > In other words, is this an issue with the applet itself, or with Global > Theme Explorer's exporting functionality? When I set that applet and export it, in the layout.js I see "dateDisplayFormat" has "BesideTime" and, well, when set to the default has no value in the layout.js. Theme Explorer seems to have it. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433510] FreeBSD support, part 12
https://bugs.kde.org/show_bug.cgi?id=433510
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #3 from Mark Wielaard ---
We really should rename coregrind/m_aspacemgr/aspacemgr-linux.c one day...
This code formatting is really ugly/unreadable:
@@ -2165,13 +2248,21 @@ VG_(am_notify_client_mmap)( Addr a, SizeT len, UInt
prot, UInt flags,
needDiscard = any_Ts_in_range( a, len );
init_nsegment( &seg );
- seg.kind = (flags & VKI_MAP_ANONYMOUS) ? SkAnonC : SkFileC;
+ seg.kind = (flags & (VKI_MAP_ANONYMOUS
+#if defined(VGO_freebsd)
+ | VKI_MAP_STACK
+#endif
+)) ? SkAnonC : SkFileC;
seg.start = a;
seg.end= a + len - 1;
seg.hasR = toBool(prot & VKI_PROT_READ);
seg.hasW = toBool(prot & VKI_PROT_WRITE);
seg.hasX = toBool(prot & VKI_PROT_EXEC);
- if (!(flags & VKI_MAP_ANONYMOUS)) {
+ if (!(flags & (VKI_MAP_ANONYMOUS
+#if defined(VGO_freebsd)
+ | VKI_MAP_STACK
+#endif
+))) {
// Nb: We ignore offset requests in anonymous mmaps (see bug #126722)
seg.offset = offset;
if (ML_(am_get_fd_d_i_m)(fd, &dev, &ino, &mode)) {
Can't you define something like MAP_STACK_ ANONYMOUS to either
VKI_MAP_ANONYMOUS or VKI_MAP_ANONYMOUS | VKI_MAP_STACK and use that?
In coregrind/m_debuginfo/readelf.c there are various changes like:
@@ -1939,13 +2014,13 @@ Bool ML_(read_elf_debug_info) ( struct _DebugInfo* di )
for (i = 0; i < VG_(sizeXA)(di->fsm.maps); i++) {
const DebugInfoMapping* map = VG_(indexXA)(di->fsm.maps, i);
if (map->rx)
- TRACE_SYMTAB("rx_map: avma %#lx size %lu foff %ld\n",
+ TRACE_SYMTAB("rx_map: avma %#lx size %lu foff %lld\n",
map->avma, map->size, map->foff);
}
for (i = 0; i < VG_(sizeXA)(di->fsm.maps); i++) {
const DebugInfoMapping* map = VG_(indexXA)(di->fsm.maps, i);
if (map->rw)
- TRACE_SYMTAB("rw_map: avma %#lx size %lu foff %ld\n",
+ TRACE_SYMTAB("rw_map: avma %#lx size %lu foff %lld\n",
map->avma, map->size, map->foff);
}
@@ -2166,7 +2246,7 @@ Bool ML_(read_elf_debug_info) ( struct _DebugInfo* di )
for (i = 0; i < VG_(sizeXA)(di->fsm.maps); i++) {
const DebugInfoMapping* map = VG_(indexXA)(di->fsm.maps, i);
if (map->rx)
- TRACE_SYMTAB("rx: at %#lx are mapped foffsets %ld .. %lu\n",
+ TRACE_SYMTAB("rx: at %#lx are mapped foffsets %lld .. %llu\n",
map->avma, map->foff, map->foff + map->size - 1 );
}
TRACE_SYMTAB("rx: contains these svma regions:\n");
@@ -2179,7 +2259,7 @@ Bool ML_(read_elf_debug_info) ( struct _DebugInfo* di )
for (i = 0; i < VG_(sizeXA)(di->fsm.maps); i++) {
const DebugInfoMapping* map = VG_(indexXA)(di->fsm.maps, i);
if (map->rw)
- TRACE_SYMTAB("rw: at %#lx are mapped foffsets %ld .. %lu\n",
+ TRACE_SYMTAB("rw: at %#lx are mapped foffsets %lld .. %llu\n",
map->avma, map->foff, map->foff + map->size - 1 );
}
TRACE_SYMTAB("rw: contains these svma regions:\n");
@@ -,7 +2302,7 @@ Bool ML_(read_elf_debug_info) ( struct _DebugInfo* di )
}
}
- TRACE_SYMTAB(" [sec %2ld] %s %s al%4u foff %6ld .. %6lu "
+ TRACE_SYMTAB(" [sec %2ld] %s %s al%4u foff %6lld .. %6llu "
" svma %p name \"%s\"\n",
i, inrx ? "rx" : " ", inrw ? "rw" : " ", alyn,
foff, (size == 0) ? foff : foff+size-1, (void *) svma,
name);
Which causes warnings like:
m_debuginfo/readelf.c:2017:23: warning: format ‘%lld’ expects argument of type
‘long long int’, but argument 4 has type ‘OffT’ {aka ‘long int’} [-Wformat=]
2017 | TRACE_SYMTAB("rx_map: avma %#lx size %lu foff %lld\n",
| ^~~~
2018 | map->avma, map->size, map->foff);
| ~
||
|OffT {aka long int}
m_debuginfo/priv_storage.h:1199:44: note: in definition of macro ‘TRACE_SYMTAB’
1199 |if (TRACE_SYMTAB_ENABLED) { VG_(printf)(format, ## args); }
|^~
m_debuginfo/readelf.c:2017:63: note: format string is defined here
2017 | TRACE_SYMTAB("rx_map: avma %#lx size %lu foff %lld\n",
|~~~^
| |
| long long
int
|%ld
In file included from m_debuginfo/readelf.c:53:
m_debuginfo/readelf.c
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 Andrey changed: What|Removed |Added URL||https://github.com/xkbcommo ||n/libxkbcommon/issues/262 --- Comment #40 from Andrey --- I opened upstream issue: https://github.com/xkbcommon/libxkbcommon/issues/262 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433508] FreeBSD support, part 11
https://bugs.kde.org/show_bug.cgi?id=433508 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #3 from Mark Wielaard --- Make sure to add launcher-freebsd.c in coregrind/Makefile.am (valgrind_SOURCES) which was removed in commit f22758d6dad9bae9b7531046e42ce105f12e1ead I didn't really review the 450K of new files. But they look plausible and are nicely separated from the other platform code (things build and work fine on my non-freebsd system). You might want to update the Copyright notices, while they are clearly derived from the other existing code, it would be good to mention the major copyright holders (I assume that is you and some of the people mentioned in the credits of README.freebsd). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443456] New: Toggling repo in Discover doesn't redraw the checkbox, confusing users
https://bugs.kde.org/show_bug.cgi?id=443456 Bug ID: 443456 Summary: Toggling repo in Discover doesn't redraw the checkbox, confusing users Product: Discover Version: 5.23.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ad...@happyassassin.net CC: aleix...@kde.org Target Milestone: --- This is an upstream report of downstream Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=2011333 . As reported there, if you go to Settings and toggle a repository from enabled to disabled or vice versa, the operation does actually happen, but the checkbox is not redrawn until you leave the Settings tab, go somewhere else, and come back. This is very confusing and could lead users not to know what repositories are actually enabled after trying to change the states. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 371539] Only listens to IPv6
https://bugs.kde.org/show_bug.cgi?id=371539 tudo75 changed: What|Removed |Added CC||tud...@hotmail.com --- Comment #34 from tudo75 --- Also for me I have only ipv6 connection netstat -tulpen | grep kdeconnectd tcp6 0 0 :::1716 :::*LISTEN 1000 45539 3799/kdeconnectd udp6 0 0 :::1716 :::* 1000 45538 3799/kdeconnectd Package: kdeconnect Version: 1.4-0ubuntu5 OS: Linux Mint 20.2 x86_64 Kernel: 5.4.0-88-generic DE: Xfce -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443455] New: Flatpak remotes are always shown as enabled and greyed out, disabled ones can't be successfully removed
https://bugs.kde.org/show_bug.cgi?id=443455 Bug ID: 443455 Summary: Flatpak remotes are always shown as enabled and greyed out, disabled ones can't be successfully removed Product: Discover Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: ad...@happyassassin.net CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- This is an upstream report of Fedora downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=2011291 . As described there, configured Flatpak remotes are always shown as enabled but greyed out - whether they are actually disabled or not. This is misleading. The 'remove' button is available, and works for enabled repos, but for disabled repos it fails with a "Can't fetch summary from disabled remote" error. This bug is still present in 5.23.0, I just tested that today. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433507] FreeBSD support, part 10
https://bugs.kde.org/show_bug.cgi?id=433507 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #3 from Mark Wielaard --- Because some of the earlier patches changed some things don't apply anymore, like .gitignore but that seems harmless. The configure.ac filter AC_CONFIG_FILES don't apply anymore, but it is clear where they should go. The new memcheck/tests/freebsd/Makefile, memcheck/tests/amd64-freebsd/Makefile and memcheck/tests/x86-freebsd/Makefile are missing in configure.ac as AC_CONFIG_FILES. Is the filename memcheck/tests/dw4.stderr.exp-freebad a joke or a typo? I like the joke, but if you decide to "fix" it don't forget to also fix it in memcheck/tests/Makefile.am EXTRA_DIST. memcheck/tests/addressable.c I think you can just unconditionally include signal.h. But that would mean changing the .exp files again. So probably don't bother. memcheck/tests/err_disable4.c pthread_attr_setstacksize isn't freebsd specific. Why was it added? memcheck/tests/Makefile.am memcheck/tests/x86/more_x86_fp.c memcheck/tests/x86/pushfpopf_s.S memcheck/tests/str_tester.c memcheck/tests/vbit-test/util.c memcheck/tests/vbit-test/vbits.c are made executable, they shouldn't memcheck/tests/x86/filter_pushfpopf should be deleted (now that there is an .in file) The posix_fadvise and posix_fallocate tests might be made non-freebsd specific (they are posix after all). But maybe afterwards. The naming of filter_varinfo3 is somewhat unfortunate now that it is used by multiple other vgtests too. I didn't review all of the new freebsd tests, but assume they are fine (they don't execute locally on Fedora) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443454] New: Folder View does not launch Application type .desktop/.kdelnk
https://bugs.kde.org/show_bug.cgi?id=443454 Bug ID: 443454 Summary: Folder View does not launch Application type .desktop/.kdelnk Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: ryu.ketsu...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY This has been happening for a while and recently it got broken on everywhere I could test with Folder View. Plasma prompts to open the .desktop and .kdelnk set as type Application as files instead of launching the program, usually opening Kate. If no default program is set, it prompts the user to select a program to open the file with. This issue happens with existing .desktop and .kdelnk files as well as the ones created using Plasma's own daemon to create a Link to Application. But again, that only happens with Application type. The Link type launches Dolphin just fine, as it is expected to STEPS TO REPRODUCE 1. Just try double clicking any .desktop or .kdelnk file from a Folder View OBSERVED RESULT Plasma either opens the file to be edited on the default plain text editor or prompts the user to open on another application EXPECTED RESULT The desired application to be launched SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211005 KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.6-2-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-7020U CPU @ 2.30GHz Memory: 11.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION Build coming from KDE Unstable Repos for openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443437] Make it optional to deepen the shadow for the active window
https://bugs.kde.org/show_bug.cgi?id=443437 --- Comment #8 from Satyam --- Thank you, I really believe it's worth it. To be clear, I'm not in any way objecting to the in focus window having distinction. I used to like the blue glow of oxygen. Or the blue outline within the focus element in Dolphin. My objection is using drop shadows as the way to indicate focus. The way it is now if I have 4 windows open side by side, 75 percent of my windows don't have enough drop shadow. With ultra wide monitors I often have 10 windows open, making 90 percent of the windows on the screen without enough drop shadows. Having the majority of windows on my screen without drop shadows is perceptually off when viewed as a whole. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027
--- Comment #39 from Andrey ---
Here is the relevant part of /usr/share/X11/xkb/symbols/level3 which might be
the reason:
// The right Alt key never chooses the third level.
// This option attempts to undo the effect of a layout's inclusion of
// 'ralt_switch'. You may want to also select another level3 option
// to map the level3 shift to some other key.
partial modifier_keys
xkb_symbols "ralt_alt" {
key {
type[Group1]="TWO_LEVEL",
type[Group2]="TWO_LEVEL",
type[Group3]="TWO_LEVEL",
type[Group4]="TWO_LEVEL",
symbols[Group1] = [ Alt_R, Meta_R ],
symbols[Group2] = [ Alt_R, Meta_R ],
symbols[Group3] = [ Alt_R, Meta_R ],
symbols[Group4] = [ Alt_R, Meta_R ]
};
modifier_map Mod1 { };
};
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 --- Comment #38 from Yaroslav Sidlovsky --- Created attachment 142246 --> https://bugs.kde.org/attachment.cgi?id=142246&action=edit My ~/.config/kxkbrc file -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027 --- Comment #37 from Yaroslav Sidlovsky --- Created attachment 142245 --> https://bugs.kde.org/attachment.cgi?id=142245&action=edit Source code of app to parse xkb-files Just unzip it and `cmake . && make -j`. xkb-file should be placed in `~/kwin.xkb` (path is hardcoded). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #8 from Patrick Silva --- dupe of bug 438883 ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443441] Shift+Del -> Enter doesn't confirm the dialog
https://bugs.kde.org/show_bug.cgi?id=443441 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 438994 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 438994] Button highlighted in dialog to confirm data deletion is not triggered when I press enter key
https://bugs.kde.org/show_bug.cgi?id=438994 Patrick Silva changed: What|Removed |Added CC||ivan.merc...@gmail.com --- Comment #16 from Patrick Silva --- *** Bug 443441 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443443] Plasma crashes sometimes when I try to set/change a widget, like the Memory Usage widget.
https://bugs.kde.org/show_bug.cgi?id=443443 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- possibly duplicate of bug 436664 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434184] Duplicate emojis
https://bugs.kde.org/show_bug.cgi?id=434184 --- Comment #7 from Adam Fontenot --- (In reply to Nate Graham from comment #6) > This is very likely outside of the scope of what we can feasible do and > maintain. I think a more fruitful approach might be to go fix the bugs in > IBus instead. Fair point. I was worried that if we were waiting on IBus to implement better APIs we'd have to wait (at least) until they release a new stable version. They seem to do only one or two a year. That said, I've filed an upstream bug so we can get their feedback on possible improvements to the API: https://github.com/ibus/ibus/issues/2356 Not adding it to the URL field since you can't have multiple URLs in Bugzilla and we're not closing this as an upstream bug since it requires more work on our end. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440027] Wayland crashes after login
https://bugs.kde.org/show_bug.cgi?id=440027
--- Comment #36 from Andrey ---
(In reply to Yaroslav Sidlovsky from comment #35)
> Created attachment 142240 [details]
> kwin_wayland.xkb
>
> Just dumped XKB config from KWin running on Wayland.
> When parsing this file with xkbcommon - it returns 4 keyboard layouts:
>
> 0. 'English (US)'
> 1. 'Russian'
> 2. ''
> 3. ''
How exactly did you dump/parse it, and what was in kxkbrc file?
I can guess here is the relevant lines:
key{
type= "TWO_LEVEL",
symbols[Group1]= [ Alt_R, Meta_R ],
symbols[Group2]= [ Alt_R, Meta_R ],
symbols[Group3]= [ Alt_R, Meta_R ],
symbols[Group4]= [ Alt_R, Meta_R ]
--
You are receiving this mail because:
You are watching all bug changes.
[kpat] [Bug 435720] Simple Simon will not auto-drop
https://bugs.kde.org/show_bug.cgi?id=435720 John changed: What|Removed |Added CC||johnsarou...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439156] Diagonal lines produce aliasing at certain zoom level
https://bugs.kde.org/show_bug.cgi?id=439156 Leonardo changed: What|Removed |Added CC||odraenco...@gmail.com --- Comment #7 from Leonardo --- The problem is that Krita has weird zoom levels: 100%, 141%, 200%, 283%, 400%, 566%, 800% Normally, to avoid this exact issue, you'd use mainly integer zoom levels. For reference, zoom levels in other graphics software: SAI: 100%, 150%, 200%, 300%, 400%, 500%, 600%, 800%. Fire Alpaca: 100%, 150%, 200%, 300%, 400%, 600%, 800%. MyPaint: 100%, 150%, 200%, 300%, 400%, 550%, 800%. Photoshop: 100%, 200%, 300%, 400%, 500%, 600%, 700%, 800%. Gimp: 100%, 150%, 200%, 300%, 400%, 550%, 800%. iirc Krita's weird zoom levels come from KDE. They probably aren't an issue in other KDE software, but because Krita is a drawing software it becomes an issue here. I suggest changing Krita's zoom levels to match MyPaint: 100%, 150%, 200%, 300%, 400%, 550%, 800%, 1100%, 1600%, 2300%, 3200%, 4500%, 6400%. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438448] EVERY Login Discover-Notifier tells me to restart
https://bugs.kde.org/show_bug.cgi?id=438448 --- Comment #12 from notrealname --- removing /var/lib/PackageKit/offline-update-action fixed it for me -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 443453] New: The arrow that indicates nested items changes it's color to white even though it shouldn't
https://bugs.kde.org/show_bug.cgi?id=443453 Bug ID: 443453 Summary: The arrow that indicates nested items changes it's color to white even though it shouldn't Product: frameworks-qqc2-desktop-style Version: 5.86.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: kinof...@gmail.com CC: ahiems...@heimr.nl, k...@davidedmundson.co.uk, noaha...@gmail.com Target Milestone: --- Created attachment 142244 --> https://bugs.kde.org/attachment.cgi?id=142244&action=edit Screenshot showing observed result The arrow that indicates nested items changes it's color to white even though it shouldn't, now that breeze implemented more of blue ocean, highlighted list items' text maintain it's color (black) so the arrow should do the same thing. STEPS TO REPRODUCE 1. Open some kirigami app that has a nested menu or a menubar (tok, kalendar) 2. hover over some list item that has child items OBSERVED RESULT The arrow that indicates it has nested items change it's color to white. EXPECTED RESULT The arrow should not change it's color. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 34 (available in About System) KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86 Qt Version: 5.15.2 ADDITIONAL INFORMATION Not sure if this is the right product to report this bug to... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 Albert Astals Cid changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #7 from Albert Astals Cid --- Clearly you don't understand how to use the configure toolbars dialog, this is out of scope here. I'd suggest you ask in the forums or chat https://kde.org/support/ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441447] Consider reverting replacement of zoom buttons with background color selector
https://bugs.kde.org/show_bug.cgi?id=441447 Krystian changed: What|Removed |Added CC||krystian.zaj...@gmail.com --- Comment #7 from Krystian --- Just wanted to say that I really miss those zoom buttons. Personally, I've used them a lot. The current solution is slow and kind of finicky. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443452] [Wayland] Cursor position is offset when going over various actions on multi monitor and multi scaling setup
https://bugs.kde.org/show_bug.cgi?id=443452 --- Comment #1 from Tony Stipanic --- Created attachment 142243 --> https://bugs.kde.org/attachment.cgi?id=142243&action=edit Phone recording of mouse cursor bug -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 van.sny...@sbcglobal.net changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #6 from van.sny...@sbcglobal.net --- Settings -> Configure toolbars adds a "configure toolbars" icon to the tool bar. Once it's there, it offers to configure the toolbar (exactly like Settings -> Configure toolbar). The dialogue offered by Configure Toolbars offers nothing to add "forward" and "backward" actions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443452] New: [Wayland] Cursor position is offset when going over various actions on multi monitor and multi scaling setup
https://bugs.kde.org/show_bug.cgi?id=443452 Bug ID: 443452 Summary: [Wayland] Cursor position is offset when going over various actions on multi monitor and multi scaling setup Product: kwin Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tony+...@stipanic.ch Target Milestone: --- SUMMARY When having a multi monitor setup with at least two monitors which both have different scaling, the cursor seems to not keep the offset correctly. When hovering over various actions like links, draggable lines, etc. the offset always changes. This only happens to one of two monitors. For example, if one monitor is scaled 200%, no jumping happens. But trying to use a 100% second monitor makes the cursor jump a lot. This seems to be a lot worse for the user using the monitor. When trying to record the screen, the recording seems to be less severe. For this reason, there is a phone recording to show the effect better. This happens on Wayland. The jumping happens on both XWayland as well as Native Wayland programs. STEPS TO REPRODUCE 1. Have one monitor be scaled 200% (for example HIDPI monitor). Have the other monitor be scaled 100% (non-HIDPI). 2. Open any program - easiest to test with Firefox on a website 3. Move the mouse around on a non-HIDPI monitor. OBSERVED RESULT The mouse jumps around and you can click on objects the mouse isn't visually on. EXPECTED RESULT The cursor doesn't jump around. For example when moving down, the cursor only moves on the y-axis. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Endeavour OS, using kde-unstable repo KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 Albert Astals Cid changed: What|Removed |Added Resolution|--- |NOT A BUG CC||aa...@kde.org Status|REPORTED|RESOLVED --- Comment #5 from Albert Astals Cid --- Settings -> Configure toolbars is what you want, it's on the okular_part toolbar. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443451] krita crashes while loading main window (text brush related)
https://bugs.kde.org/show_bug.cgi?id=443451 til.schmit...@gmx.de changed: What|Removed |Added Summary|krita crashes while loading |krita crashes while loading |resources |main window (text brush ||related) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443451] krita crashes while loading resources
https://bugs.kde.org/show_bug.cgi?id=443451 --- Comment #2 from til.schmit...@gmx.de --- this seems to be related to text brushes. i think krita crashes while trying to load my pmc.kpp brush into the brush preset docker. i renamed pmc.kpp to pmc.kpp.old and krita works again previous related bug report: https://bugs.kde.org/show_bug.cgi?id=443308 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443442] Change order favorites
https://bugs.kde.org/show_bug.cgi?id=443442 --- Comment #3 from Nate Graham --- Yeah it's gonna be great! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443451] krita crashes while loading resources
https://bugs.kde.org/show_bug.cgi?id=443451 til.schmit...@gmx.de changed: What|Removed |Added Summary|playing "the last campfire" |krita crashes while loading |breaks krita until restart |resources -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443451] playing "the last campfire" breaks krita until restart
https://bugs.kde.org/show_bug.cgi?id=443451 --- Comment #1 from til.schmit...@gmx.de --- actually nvm, restarting didn't help. krita crashes before the main window can open... there seems to be a different reason with loading my resources. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443442] Change order favorites
https://bugs.kde.org/show_bug.cgi?id=443442 --- Comment #2 from Iyán Méndez Veiga --- Sorry about the duplicate bug... I did spend some time trying to find similar issues already reported, but I was filtering by "open", and I join later to the party :S Excited to update to 5.23 in a few days :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443449] Exporting with global themes does not save new adaptive location configuration
https://bugs.kde.org/show_bug.cgi?id=443449 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- I you add this value manually to the exported config file, does it take effect as expected? In other words, is this an issue with the applet itself, or with Global Theme Explorer's exporting functionality? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443451] New: playing "the last campfire" breaks krita until restart
https://bugs.kde.org/show_bug.cgi?id=443451 Bug ID: 443451 Summary: playing "the last campfire" breaks krita until restart Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: til.schmit...@gmx.de Target Milestone: --- 5.1.0 git 46ec385 ok this one is kinda weird but after playing the last campfire on steam krita encounters several inconsistent problems until i restart my pc: -krita crashes while trying to load the main window -krita crashes on creating a new canvas -krita crashes on opening a png only happens while i play the game and after i close it, so it is avoidable. reproducible about 90% of the time. this doesn't seem to happen on my old 4.4.3-alpha installation. Error occurred on Thursday, October 7, 2021 at 22:38:52. krita.exe caused an Access Violation at location 7FF9E6F0F960 in module libkritaresources.dll Reading from location 0031. AddrPC Params 7FF9E6F0F960 005F4B10 005F4AD0 005F4B00 libkritaresources.dll!0x4f960 KisMemoryStorage::resourceMd5+0xa0 7FF9E6EE4B55 26A24600 7FF9E09311E0 0006 libkritaresources.dll!0x24b55 KisResourceStorage::resourceMd5+0x15 7FF9E6EDB180 25676900 7FF9E064 1B58A6B0 libkritaresources.dll!0x1b180 KisResourceLocator::addResource+0x2d0 7FF9E6EDB6A7 26A0C050 0075 005F4DE0 libkritaresources.dll!0x1b6a7 KisResourceLocator::loadRequiredResources+0x177 7FF9E6EDBE70 005F4ED0 7FF9E0B69068 005F4EB0 libkritaresources.dll!0x1be70 KisResourceLocator::resource+0x6d0 7FF9E6EDC71A 0075 005F4EF9 0003 libkritaresources.dll!0x1c71a KisResourceLocator::resourceForId+0x4a 7FF9E6EF0993 001A 7FF9E6F483B8 7FF9DF4CB2D0 libkritaresources.dll!0x30993 KisAllResourcesModel::resourcesForName+0x393 7FF9E6F49FE1 000B 15178860 151788A0 libkritaresources.dll!0x89fe1 (anonymous namespace)::GlobalResourcesSource::resourcesForName+0x11 7FF9DF2DA216 0001 7FF9DF4CB2D0 005F5098 libkritaui.dll!0x4aa216 KisResourcesInterface::ResourceSourceAdapter::bestMatch+0x686 7FF9DF2AC93E 1A206B50 7FF9E078DBE0 1B4FE710 libkritaui.dll!0x47c93e KoResourceServer::resource+0xbe 7FF9DF20382B 2565AD70 1A209550 libkritaui.dll!0x3d382b KisViewManager::setCurrentView+0x13cb 7FF9DF1C8C43 0298D260 7FF9E09FE8A0 005F57C0 libkritaui.dll!0x398c43 KisMainWindow::setActiveView+0xa3 7FF9DF1D2DA8 26180810 005F57C0 libkritaui.dll!0x3a2da8 KisMainWindow::setActiveSubWindow+0x78 7FF9DF1D3F11 7FF9E09FE8A0 005F57C0 26284910 libkritaui.dll!0x3a3f11 KisMainWindow::subWindowActivated+0xc1 7FF9DF1DA7C9 0001 7FF9E002EB9E 0A3536F0 libkritaui.dll!0x3aa7c9 KisMainWindow::qt_static_metacall+0x539 7FF9E07B9298 15071B40 7FF9E0797419 0050 Qt5Core.dll!0x229298 QMetaObject::activate+0x7b8 7FF9E0163566 26371310 Qt5Widgets.dll!0x143566 QMdiArea::childEvent+0x2f6 7FF9E0164235 2565AD70 2565AD70 10477DC0 Qt5Widgets.dll!0x144235 QMdiArea::scrollContentsBy+0x155 7FF9E0165028 0003 7FF9E0933580 005F57C0 Qt5Widgets.dll!0x145028 QMdiArea::qt_static_metacall+0x258 7FF9E07B9298 26284910 001A 00022537D6F8 Qt5Core.dll!0x229298 QMetaObject::activate+0x7b8 7FF9E016FAB0 26180FF0 7FF9BC685750 22BA51B0 Qt5Widgets.dll!0x14fab0 QMdiSubWindow::qt_metacast+0xa10 7FF9E01706E3 26180D50 26180D50 26180D50 Qt5Widgets.dll!0x1506e3 QMdiSubWindow::eventFilter+0x463 7FF9E078C850 005FFB80 005FFB80 Qt5Core.dll!0x1fc850 QCoreApplication::applicationVersionChanged+0x1a0 7FF9E0027BC5 0A3536F0 7FF9E0933580 005F5D40 Qt5Widgets.dll!0x7bc5 QApplicationPrivate::notify_helper+0x75 7FF9E002EB9E 005F5C50 7FF9E05B259F 0400 Qt5Widgets.dll!0xeb9e QApplication::notify+0x31e 7FF9DF1A0A96 2565AD70 6FD0728C 00C00100 libkritaui.dll!0x370a96 KisApplication::notify+0x16 7FF9E078DD88 0C0C Qt5Core.dll!0x1fdd88 QCoreApplication::sendEvent+0x1a8 7FF9E006265A 0001 005F5E48 Qt5Widgets.dll!0x4265a QWidgetPrivate::show_helper+0x17a 7FF9E0065DC4 0
[plasmashell] [Bug 443448] Some Java Swing, GTK2 and Electron based apps lose their icons after changing icon theme
https://bugs.kde.org/show_bug.cgi?id=443448 Nate Graham changed: What|Removed |Added Component|Icon|Application Launcher ||(Kickoff) Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk CC||mikel5...@gmail.com, ||n...@kde.org, ||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443443] Plasma crashes sometimes when I try to set/change a widget, like the Memory Usage widget.
https://bugs.kde.org/show_bug.cgi?id=443443 Nate Graham changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Can you please attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Also note that you are using an older version of Plasma, and this issue may have been fixed in Plasma 5.22 or 5.23 (which is due to be released in a week). So it might also be good to upgrade and see if it might already be fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440308] Can't drag-and-drop apps anymore (e.g. for re-arranging, for dropping onto the desktop or panel, etc)
https://bugs.kde.org/show_bug.cgi?id=440308 Nate Graham changed: What|Removed |Added CC||m...@iyanmv.com --- Comment #12 from Nate Graham --- *** Bug 443442 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443442] Change order favorites
https://bugs.kde.org/show_bug.cgi?id=443442 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 440308 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433506] FreeBSD support, part 9
https://bugs.kde.org/show_bug.cgi?id=433506 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433506] FreeBSD support, part 9
https://bugs.kde.org/show_bug.cgi?id=433506 --- Comment #13 from Paul Floyd --- Code committed with commit 53dd9bd255d7add6f5a502ec9cd4895d3ed21452 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 443450] New: AdBlock: Add support for uBlock Origin lists
https://bugs.kde.org/show_bug.cgi?id=443450 Bug ID: 443450 Summary: AdBlock: Add support for uBlock Origin lists Product: Falkon Version: unspecified Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: prob...@puredarwin.org Target Milestone: --- SUMMARY Please consider adding support for uBlock Origin lists. The code exists (see below). uBlock Origin lists are much more effective in filtering certain ads and anti-adblocker nag screens. STEPS TO REPRODUCE 1. Try to add the first 4 lists from https://github.com/LeFroid/Viper-Browser/blob/123305d7f2f8f323f8672e16071f4cb4f55be3b1/src/app/assets/adblock_recommended.json OBSERVED RESULT uBlock Origin lists cannot be used. EXPECTED RESULT uBlock Origin lists can be used in addition to Adblock Plus lists. ADDITIONAL INFORMATION https://github.com/LeFroid/Viper-Browser/ has the code needed for uBlock Origin lists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420541] Critical notifications (and *only* critical notifications) should be more attention-getting
https://bugs.kde.org/show_bug.cgi?id=420541 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1098 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420541] Critical notifications (and *only* critical notifications) should be more attention-getting
https://bugs.kde.org/show_bug.cgi?id=420541 --- Comment #12 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/348 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443244] find next/previous icon inconsistence
https://bugs.kde.org/show_bug.cgi?id=443244 qydwhotm...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/konsole/commit/49ccf0 ||99c130be28da5a1972b247f1480 ||d9d7159 --- Comment #6 from qydwhotm...@gmail.com --- Git commit 49ccf099c130be28da5a1972b247f1480d9d7159 by Fushan Wen. Committed on 07/10/2021 at 14:33. Pushed by hindenburg into branch 'master'. Make "Find Next/Previous" icons in Edit menu consistent with those in the search bar There is an inconsistence in "Find Next/Previous" icons in Edit menu and the search bar. Make sure they are consistent whenever "Search backwards" is checked or not. M +13 -0src/session/SessionController.cpp M +1-0src/session/SessionController.h M +1-0src/widgets/IncrementalSearchBar.cpp M +5-0src/widgets/IncrementalSearchBar.h https://invent.kde.org/utilities/konsole/commit/49ccf099c130be28da5a1972b247f1480d9d7159 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433504] FreeBSD support, part 8
https://bugs.kde.org/show_bug.cgi?id=433504 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Paul Floyd --- Code committed with commit 3d25fd4a6c188f6183e69693920f81e3bc4e474f (nightly) commit a6096335c3f0d01c57b87538430de805aa632260 (docs) commit b128b20e66adbf00e87cf43e00e07ffe04f2ba8b (tests) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 --- Comment #4 from van.sny...@sbcglobal.net --- Maybe my version (20.12.3) is too old -- there is no "preferences" menu item, nor a "preferences" item on any menu. I tried Settings -> Configure Toolbars and Settings -> Configure Okular and Settings -> Configure Okular -> Configure Annotations, and found nothing about "forward" and "backward" actions. Maybe I'm still looking in the wrong place. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 422203] PDF viewer hijacks spacebar, even when not in focus
https://bugs.kde.org/show_bug.cgi?id=422203 Christoph Roick changed: What|Removed |Added Status|REOPENED|RESOLVED Version Fixed In||5.7.0 Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/4fadf2 ||c99c8a8826f0ca82e25e0718d83 ||23c7ad8 Resolution|--- |FIXED --- Comment #4 from Christoph Roick --- Git commit 4fadf2c99c8a8826f0ca82e25e0718d8323c7ad8 by Christoph Roick. Committed on 07/10/2021 at 19:43. Pushed by croick into branch 'master'. Restrict KParts keyboard shortcuts to their own view Fix keyboard shortcuts being applied across multiple split views. Without limiting the shortcuts owned by the respective KPart (such as an Okular view), actions are called even if the Part is not currently active (like scrolling the Okular document when pressing space in another view). FIXED-IN: 5.7.0 M +14 -6kdevplatform/shell/partcontroller.cpp https://invent.kde.org/kdevelop/kdevelop/commit/4fadf2c99c8a8826f0ca82e25e0718d8323c7ad8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #12 from Christoph Cullmann --- macOS Okular should build again: https://binary-factory.kde.org/view/MacOS/job/Okular_Release_macos/758/console -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415583] Global Themes with SDDM Themes fail to install if SDDM is not installed
https://bugs.kde.org/show_bug.cgi?id=415583 doncb...@gmail.com changed: What|Removed |Added CC||doncb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443449] New: Exporting with global themes does not save new adaptive location configuration
https://bugs.kde.org/show_bug.cgi?id=443449 Bug ID: 443449 Summary: Exporting with global themes does not save new adaptive location configuration Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: doncb...@gmail.com Target Milestone: 1.0 SUMMARY An option for a location was added under appearance in Digital Clock. When exported with the Global Themes Explorer, this setting is not remembered. Applying a desktop layout that had it sets it to the default value instead. STEPS TO REPRODUCE 1. Set the clock to show "Always beside time" 2. Export it as a layout 3. Apply the layout OBSERVED RESULT The clock will be shown with the default value of "adaptive location" EXPECTED RESULT The setting for "Always beside time" should be preserved SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.80 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #11 from Christoph Cullmann --- Git commit 005c41914edd500bd86b7365af456eec1f7016da by Christoph Cullmann. Committed on 07/10/2021 at 19:38. Pushed by cullmann into branch 'master'. add kpty, macOS compiles fails because it is missing M +2-1kde/applications/okular/okular.py https://invent.kde.org/packaging/craft-blueprints-kde/commit/005c41914edd500bd86b7365af456eec1f7016da -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442060] Mac OS Trackpad scroll buggy
https://bugs.kde.org/show_bug.cgi?id=442060 --- Comment #10 from Christoph Cullmann --- I think some dependency is missing, as e.g. libKF5Pty is not found (at least if I read the fail right). I could take a look. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433473] FreeBSD support, part 5
https://bugs.kde.org/show_bug.cgi?id=433473 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Paul Floyd --- Code committed with commit 85bbe2853e813bbd83aa17bc17c2b73d82f6bc3e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430366] Crash when creating an 32x32 pixel image
https://bugs.kde.org/show_bug.cgi?id=430366 --- Comment #14 from vanyossi --- Im on it -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 --- Comment #3 from Oliver Sander --- I think you can already have such a button. Go to preference -> toolbar settings -> anotation toolbar, and there should be 'forward' and 'backward' actions. [The menu names may be slightly different, I translated them from my German UI.] -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443447] Some images are partly covered with blank space
https://bugs.kde.org/show_bug.cgi?id=443447 --- Comment #2 from van.sny...@sbcglobal.net --- The steps F7 -> Annotation tab -> select -> delete did not reveal the complete image. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443189] Crash when attempting to undo while drawing liquify strokes
https://bugs.kde.org/show_bug.cgi?id=443189 Ahab Greybeard changed: What|Removed |Added Ever confirmed|0 |1 CC||ahab.greybe...@hotmail.co.u ||k Status|REPORTED|CONFIRMED --- Comment #1 from Ahab Greybeard --- I can replicate this with the 5.0.0-beta1 and the Oct 07 5.1.0-prealpha (git f2ad3000) appimages on Debian 10. It doesn't happen with the 4.4.8 appimage. I don't need to use Undo. A crash happens during the second Liquify stroke or sometimes the first liquify stroke. For both versions: The terminal says "Aborted". The log file says "ASSERT (krita): "row < 0x7FFF && col < 0x7FFF" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/image/tiles3/kis_tile_hash_table2.h, line 129" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 --- Comment #2 from van.sny...@sbcglobal.net --- shift+alt+left and shift+alt+right indeed do what I want. I would not have guessed these, and I would never have found them without Oliver's comment. Can there be an optional tool button so that others do not also need Oliver's advice? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443448] New: Some Java Swing, GTK2 and Electron based apps lose their icons after changing icon theme
https://bugs.kde.org/show_bug.cgi?id=443448 Bug ID: 443448 Summary: Some Java Swing, GTK2 and Electron based apps lose their icons after changing icon theme Product: plasmashell Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icon Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: 1.0 Created attachment 142242 --> https://bugs.kde.org/attachment.cgi?id=142242&action=edit Some Java Swing, GTK2 and Electron based apps lose their icons after changing icon theme No matter what I do I cannot recover those lost icons, and this problem appears on all kind of app launchers : Kickoff, Kicker, Simple Menu... see attached video for more info. Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.4.144-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443447] Some images are partly covered with blank space
https://bugs.kde.org/show_bug.cgi?id=443447 Yuri Chornoivan changed: What|Removed |Added CC||yurc...@ukr.net --- Comment #1 from Yuri Chornoivan --- There is an annotation on page 1 by Randall Neff. It can be deleted (F7 -> annotation tab -> Select -> Press Delete) to make Fig. 1 completely shown. Does this solve the problem? Thanks in advance for your answer. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443447] New: Some images are partly covered with blank space
https://bugs.kde.org/show_bug.cgi?id=443447 Bug ID: 443447 Summary: Some images are partly covered with blank space Product: okular Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: van.sny...@sbcglobal.net Target Milestone: --- Created attachment 142241 --> https://bugs.kde.org/attachment.cgi?id=142241&action=edit A page from a document that shows an image partly covered by blank space SUMMARY Some images in some documents are not completely displayed. Instead, they are partly covered by blank space that looks like a piece of paper with one corner folded down. STEPS TO REPRODUCE 1. Open the attachment 2. Look at Figure 1. 3. Do it again using, e.g., Adobe acroread or xpdf OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Have you tried shift+alt+left? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] New: Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 Bug ID: 443446 Summary: Add "previous view" and "next view" buttons Product: okular Version: 20.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: van.sny...@sbcglobal.net Target Milestone: --- SUMMARY Navigation in the Adobe acrobat reader is eased by having "next view" and "previous view" (not "next page" and "previous page") buttons. These are like "undo" and "redo" in an editor, not "page up" and "page down" keys on the keyboard. In Aaroread, these are not normally configured, but one can add them to the toolbar. Try it out and you'll agree it's easier than keeping a pencil and paper handy (or an editor page open) to write down page numbers. STEPS TO REPRODUCE 1. Read some page of a document 2. Read something on a distant page of a document 3. Wish to get back to step 1. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
