[plasmashell] [Bug 492873] New: Graphical issues with floating panel enabled when un-maximizing windows
https://bugs.kde.org/show_bug.cgi?id=492873 Bug ID: 492873 Summary: Graphical issues with floating panel enabled when un-maximizing windows Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: NixOS OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: prasol...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 173474 --> https://bugs.kde.org/attachment.cgi?id=173474&action=edit Video recording of the bug *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Graphical issues with floating panel enabled when un-maximizing windows. These issues do not occur with floating panel disabled. STEPS TO REPRODUCE 1. Make sure the Floating panel is enabled 2. Maximize firefox (seems to only affect couple of apps, notably vscode and firefox) 3. Maximize another window on top 4. unmaximize window 5. notice how firefox window looks broken during the animation OBSERVED RESULT Firefox window looks broken during the animation EXPECTED RESULT It should look fine SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492873] Graphical issues with floating panel enabled when un-maximizing windows
https://bugs.kde.org/show_bug.cgi?id=492873 prasol...@gmail.com changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492873] Graphical issues with floating panel enabled when un-maximizing windows
https://bugs.kde.org/show_bug.cgi?id=492873 prasol...@gmail.com changed: What|Removed |Added CC||prasol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492873] Graphical issues with floating panel enabled when un-maximizing windows
https://bugs.kde.org/show_bug.cgi?id=492873 --- Comment #1 from prasol...@gmail.com --- (Disabling floating panel and re-maximizing windows is a workaround) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492873] Graphical issues with floating panel enabled when un-maximizing windows
https://bugs.kde.org/show_bug.cgi?id=492873 --- Comment #2 from prasol...@gmail.com --- Possibly a bug in kwin rather than plasmashell? Maximizing firefox/vscode whille the panel is NOT floated (aka overlaps with a window) also leads to animation looking fine -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492979] New: Plasma crashed while rebuilding NixOS
https://bugs.kde.org/show_bug.cgi?id=492979 Bug ID: 492979 Summary: Plasma crashed while rebuilding NixOS Classification: I don't know Product: kde Version: unspecified Platform: NixOS OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: prasol...@gmail.com Target Milestone: --- Application: (6.1.4) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.10.8 x86_64 Windowing System: Wayland Distribution: NixOS 24.11 (Vicuna) DrKonqi: 6.1.4 [CoredumpBackend] -- Information about the crash: Plasma crashed during a nixos rebuild... seems to be related to icons in some way but i have no idea what went wrong The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7f4c5c3c3f9a in KIconLoader::iconPath (this=0x7f4c5c3e2550 >::instance()::holder>, _name=..., group_or_size=group_or_size@entry=0, canReturnNull=canReturnNull@entry=true, scale=scale@entry=1) at /build/kiconthemes-6.5.0/src/kiconloader.cpp:924 #6 0x7f4c5c3c4489 in KIconLoader::iconPath (this=, _name=..., group_or_size=group_or_size@entry=0, canReturnNull=canReturnNull@entry=true) at /build/kiconthemes-6.5.0/src/kiconloader.cpp:889 #7 0x7f4c5c3c45ec in KIconLoaderPrivate::preferredIconPath (this=0x3dd98c90, name=...) at /build/kiconthemes-6.5.0/src/kiconloader.cpp:850 #8 0x7f4c5c3c46c7 in KIconLoader::hasIcon (this=, name=...) at /build/kiconthemes-6.5.0/src/kiconloader.cpp:1435 #9 0x7f4c5c3b8e87 in KIconEngine::isNull (this=) at /build/kiconthemes-6.5.0/src/kiconengine.cpp:218 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492979] Plasma crashed while rebuilding NixOS
https://bugs.kde.org/show_bug.cgi?id=492979 --- Comment #1 from prasol...@gmail.com --- Created attachment 173556 --> https://bugs.kde.org/attachment.cgi?id=173556&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 492979] Plasma crashed while rebuilding NixOS
https://bugs.kde.org/show_bug.cgi?id=492979 prasol...@gmail.com changed: What|Removed |Added CC||prasol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 492401] New: Bird's eye view is obviously broken
https://bugs.kde.org/show_bug.cgi?id=492401 Bug ID: 492401 Summary: Bird's eye view is obviously broken Classification: Applications Product: gwenview Version: 24.08.0 Platform: NixOS OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: prasol...@gmail.com Target Milestone: --- Created attachment 173122 --> https://bugs.kde.org/attachment.cgi?id=173122&action=edit (screenshot of obviously wrong birds eye view) *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Open any image with gwenview 2. Zoom in (with enabled bird's eye view) 3. It obviously doesn't match up with the part of the image being viewed OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION I'm using Wayland with Fractional Scaling set to 1.25x -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 492401] Bird's eye view is obviously broken
https://bugs.kde.org/show_bug.cgi?id=492401 prasol...@gmail.com changed: What|Removed |Added CC||prasol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 492401] Bird's eye view is obviously broken
https://bugs.kde.org/show_bug.cgi?id=492401 prasol...@gmail.com changed: What|Removed |Added Keywords||wayland --- Comment #1 from prasol...@gmail.com --- can confirm, issue only happens on Wayland Setting WAYLAND_DISPLAY="" and launching gwenview results in correct birds eye view. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 492401] Bird's eye view is obviously broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=492401 prasol...@gmail.com changed: What|Removed |Added Summary|Bird's eye view is |Bird's eye view is |obviously broken|obviously broken on Wayland -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 492401] Bird's eye view is obviously broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=492401 --- Comment #2 from prasol...@gmail.com --- Seems like the birds eye view is just unaffected by fractional DPI scale on Wayland, which causes it to render using the wrong bounding box size??? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 494140] New: kde connect crashes on sleep
https://bugs.kde.org/show_bug.cgi?id=494140
Bug ID: 494140
Summary: kde connect crashes on sleep
Classification: I don't know
Product: kde
Version: unspecified
Platform: NixOS
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: prasol...@gmail.com
Target Milestone: ---
Application: (24.08.1)
Qt Version: 6.7.2
Frameworks Version: 6.6.0
Operating System: Linux 6.11.1 x86_64
Windowing System: Wayland
Distribution: NixOS 24.11 (Vicuna)
DrKonqi: 6.1.5 [CoredumpBackend]
-- Information about the crash:
Putting the device to sleep and then waking it up crashes the kde connect
daemon almost every time
The crash can be reproduced every time.
-- Backtrace:
Application: KDE Connect Daemon (), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[New LWP 8585]
[New LWP 8589]
[New LWP 8586]
[New LWP 8587]
[New LWP 8588]
[New LWP 8591]
[New LWP 8592]
[New LWP 8590]
[New LWP 8593]
[New LWP 8594]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/nix/store/3dyw8dzj9ab4m8hv5dpyx7zii8d0w6fi-glibc-2.39-52/lib/libthread_db.so.1".
Core was generated by
`/nix/store/kp2wcpd0dliylw9cp13mg0647sfkkrbp-kdeconnect-kde-24.08.1/bin/.kdeconn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7f6fc782d400 (LWP 8585))]
To enable execution of this file add
add-auto-load-safe-path
/nix/store/pjxrn2wn0sn533p48jz5qxgjld84hn3i-glib-2.80.4/lib/libgobject-2.0.so.0.8000.4-gdb.py
line to your configuration file "/home/user/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/user/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"
Cannot QML trace cores :(
Unexpectedly stumbled over an objfile
(/nix/store/0dmcwcb25b97h4hqp0yrl44xa6yyv1k2-libjxl-0.10.3/lib/libjxl.so.0.10.3)
without build_id. Not creating payload.
[Current thread is 1 (Thread 0x7f6fc782d400 (LWP 8585))]
Thread 10 (Thread 0x7f6fb56006c0 (LWP 8594)):
#0 0x7f6fcca960ce in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x1d5d2910) at
futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x1d5d2910,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x7f6fcca9616f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x1d5d2910, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3 0x7f6fcca98c20 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x1d5d28b8, cond=0x1d5d28e8) at pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x1d5d28e8, mutex=0x1d5d28b8) at
pthread_cond_wait.c:618
#5 0x7f6fbcf2b879 in cnd_wait (cond=, mtx=)
at ../src/c11/impl/threads_posix.c:135
#6 0x7f6fbcf097ab in util_queue_thread_func (input=input@entry=0x1ce0d820)
at ../src/util/u_queue.c:290
#7 0x7f6fbcf2b7a7 in impl_thrd_routine (p=) at
../src/c11/impl/threads_posix.c:67
#8 0x7f6fcca99a42 in start_thread (arg=) at
pthread_create.c:447
#9 0x7f6fccb1905c in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 9 (Thread 0x7f6fb60006c0 (LWP 8593)):
#0 0x7f6fcca960ce in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x1d57ea10) at
futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x1d57ea10,
expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0,
private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x7f6fcca9616f in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x1d57ea10, expected=expected@entry=0,
clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at
futex-internal.c:139
#3 0x7f6fcca98c20 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x1d57e9b8, cond=0x1d57e9e8) at pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x1d57e9e8, mutex=0x1d57e9b8) at
pthread_cond_wait.c:618
#5 0x7f6fbcf2b879 in cnd_wait (cond=, mtx=)
at ../src/c11/impl/threads_posix.c:135
#6 0x7f6fbcf097ab in util_queue_thread_func (input=input@entry=0x1cce5550)
at ../src/util/u_queue.c:290
#7 0x7f6fbcf2b7a7 in imp
[kde] [Bug 494140] kde connect crashes on sleep
https://bugs.kde.org/show_bug.cgi?id=494140 --- Comment #1 from prasol...@gmail.com --- I'm aware bluetooth support is in beta, but this is exactly why im reporting this -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 493300] New: Crash after switching to double row
https://bugs.kde.org/show_bug.cgi?id=493300 Bug ID: 493300 Summary: Crash after switching to double row Classification: I don't know Product: kde Version: unspecified Platform: NixOS OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: prasol...@gmail.com Target Milestone: --- Application: (6.1.5) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.10.9 x86_64 Windowing System: Wayland Distribution: NixOS 24.11 (Vicuna) DrKonqi: 6.1.5 [CoredumpBackend] -- Information about the crash: KDE Plasma froze and crashed after switching the taskbar from single row to two rows. The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #6 0x7fb76829b843 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #7 0x7fb768249516 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fb768231935 in __GI_abort () at abort.c:79 #9 0x7fb7682327f3 in __libc_message_impl (fmt=fmt@entry=0x7fb7683b52e6 "%s\n") at ../sysdeps/posix/libc_fatal.c:132 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 493300] Crash after switching to double row
https://bugs.kde.org/show_bug.cgi?id=493300 --- Comment #1 from prasol...@gmail.com --- Created attachment 173807 --> https://bugs.kde.org/attachment.cgi?id=173807&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
