[neon] [Bug 372829] New: System crash after ungrade from 5.8.3 to 5.8.4
https://bugs.kde.org/show_bug.cgi?id=372829 Bug ID: 372829 Summary: System crash after ungrade from 5.8.3 to 5.8.4 Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: Packages Dev Edition [stable] Assignee: neon-b...@kde.org Reporter: manuelbailenhernan...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Before choose user the screen turns black. I am using nvidia-304 driver The problem is solver downgrading the driver version from 304.132-0ubuntu0.16.04.2 (xenial-updates) to 304.131-0ubuntu3 (xenial) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 372829] System crash after ungrade from 5.8.3 to 5.8.4
https://bugs.kde.org/show_bug.cgi?id=372829 Manuel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Manuel --- The bug comes from Ubuntu -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 Manuel changed: What|Removed |Added CC||miaumen...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466017] Tiling Shortcut (Shift) not working with Keyboard-Layout German (Neo, QWERTZ)
https://bugs.kde.org/show_bug.cgi?id=466017 manuel changed: What|Removed |Added CC||maenje...@gmail.com --- Comment #6 from manuel --- Was surprised that tiling stopped working when changing from X11 to Wayland session. Also using Neo2 Layout. At first, thought it might be due to manual fiddling with virtual desktop config. But reverting my changes did not do anything. Then tried having Neo2 and German standard layout both available, but switching between them did not fix the issue neither. Moreover, back in X11, tiling also did not work anymore (!) until I removed layout selection and changed back to Neo2 only. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487563] New: Changing the "Adaptive Sync" option to "Always" drastically lowers the monitor frequency
https://bugs.kde.org/show_bug.cgi?id=487563 Bug ID: 487563 Summary: Changing the "Adaptive Sync" option to "Always" drastically lowers the monitor frequency Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mngo...@gmail.com Target Milestone: --- Created attachment 169839 --> https://bugs.kde.org/attachment.cgi?id=169839&action=edit OSD comparison SUMMARY Changing the "Adaptive Sync" option to "Always" drastically lowers the monitor frequency noticeable with cursor stutters STEPS TO REPRODUCE 1. Use a freesync display 2. Set Adaptive Sync to always 3. Mouse stutters and your display frequency is low OBSERVED RESULT Your cursor will stutter, it seems to lower the monitor frequency to 48hz EXPECTED RESULT Smooth cursor like the other options(?) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (6.9.1-arch1-2) (available in About System) Nvidia 555.42.02 KDE Plasma Version: 6.0.9 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Spectacle recordings are corrupted and can't be played, using obs to record makes the issue go away, the only "proof" is that my monitor OSD show that it runs at 48hz when setting adaptive sync to on (attached ) -- 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 Manuel changed: What|Removed |Added CC||mdom...@gmail.com Version|5.22.90 |5.23.0 --- Comment #16 from Manuel --- Please, restore the Desktop Cube switching effect. The cube effect is NECESSARY for KDE to be the KOOL Desktop Environment. Please put the Cube effect back on. My desk is not the same without it. Without excuses. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440653] New: vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0xC2 0xC8 0x8 0x2C 0x0 0x0 0x0 0x3
https://bugs.kde.org/show_bug.cgi?id=440653 Bug ID: 440653 Summary: vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0xC2 0xC8 0x8 0x2C 0x0 0x0 0x0 0x3 Product: valgrind Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: manu06ahum...@gmail.com Target Milestone: --- uname -a Linux edfdf05b67cf 5.10.25-linuxkit #1 SMP Tue Mar 23 09:27:39 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux SUMMARY vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0xC2 0xC8 0x8 0x2C 0x0 0x0 0x0 0x3 STEPS TO REPRODUCE 1. Try to use the instruction CMPPD with and imm8 greater or equal than 8, for example the following main.asm: global _start section .text _start: cmppd xmm1, xmm0, 0x8 2. nasm -f elf64 -g -F DWARF main.asm 3. ld -o main main.o 4. valgrind -v ./main OBSERVED RESULT vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0xC2 0xC8 0x8 0x2C 0x0 0x0 0x0 0x3 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 EXPECTED RESULT No invalide instruction SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 20.04.2 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION valgrind version: 3.18.0.GIT -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440653] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0xC2 0xC8 0x8 0x2C 0x0 0x0 0x0 0x3
https://bugs.kde.org/show_bug.cgi?id=440653 Manuel changed: What|Removed |Added CC||manu06ahum...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440653] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0xC2 0xC8 0x8 0x2C 0x0 0x0 0x0 0x3
https://bugs.kde.org/show_bug.cgi?id=440653 --- Comment #1 from Manuel --- Created attachment 140556 --> https://bugs.kde.org/attachment.cgi?id=140556&action=edit A patch that solves the bug I have been looking at the code that handles this instruction and it's seems like it is preventing any imm8 greater or equal than 8, but for processors with avx the instruction can handle those imm8. I think that this patch should solve it, please let me know if I'm missing something. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 426271] New: Copy file name to title track doesn't work
https://bugs.kde.org/show_bug.cgi?id=426271 Bug ID: 426271 Summary: Copy file name to title track doesn't work Product: kid3 Version: 3.8.x Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: c...@dumont.top Target Milestone: --- Created attachment 131461 --> https://bugs.kde.org/attachment.cgi?id=131461&action=edit Copy file name to title track doesn't work SUMMARY STEPS TO REPRODUCE 1. button "Etiquette 2 depuis le nom de fichier" 2. 3. OBSERVED RESULT Doesn't work EXPECTED RESULT Copy file name to Title SOFTWARE/OS VERSIONS macOS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 434695] New: Spectacle screenshot
https://bugs.kde.org/show_bug.cgi?id=434695 Bug ID: 434695 Summary: Spectacle screenshot Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: manuelserranomt...@outlook.com Target Milestone: --- Application: latte-dock (0.9.86) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.4.0-67-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: When taking a screenshot with Spectacle, the Latte dock app stops. The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 1518] [New LWP 1519] [New LWP 1520] [New LWP 1521] [New LWP 1526] [New LWP 1735] [New LWP 1768] [New LWP 1789] [New LWP 1790] [New LWP 1949] [New LWP 1954] [New LWP 1984] [New LWP 2313] [New LWP 2316] [New LWP 2317] [New LWP 2318] [New LWP 2319] [New LWP 2320] [New LWP 2321] [New LWP 2322] [New LWP 2323] [New LWP 2324] [New LWP 2325] [New LWP 6323] [New LWP 17272] [New LWP 17674] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f5f9f287aff in __GI___poll (fds=0x7ffc71b87a68, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f5f9b9758c0 (LWP 1488))] Thread 27 (Thread 0x7f5ee67fc700 (LWP 17674)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557546824774) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x557546824720, cond=0x557546824748) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x557546824748, mutex=0x557546824720) at pthread_cond_wait.c:638 #3 0x7f5f9f769d5b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557546824720) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x557543219150, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f5fa18ea814 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f5fa18eac89 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f5f9f763bec in QThreadPrivate::start(void*) (arg=0x5575432190b0) at thread/qthread_unix.cpp:329 #8 0x7f5f9e965609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5f9f294293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f5f6700 (LWP 17272)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5575462fe5f4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5575462fe5a0, cond=0x5575462fe5c8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5575462fe5c8, mutex=0x5575462fe5a0) at pthread_cond_wait.c:638 #3 0x7f5f9f769d5b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5575462fe5a0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5575432c3e50, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f5fa18ea814 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f5fa18eac89 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f5f9f763bec in QThreadPrivate::start(void*) (arg=0x5575432c3db0) at thread/qthread_unix.cpp:329 #8 0x7f5f9e965609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5f9f294293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f5f667fc700 (LWP 6323)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557542abb7b0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x557542abb760, cond=0x557542abb788) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x557542abb788, mutex=0x557542abb760) at pthread_cond_wait.c:638 #3 0x7f5f9f769d5b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x557542abb760) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x557543090420, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f5fa18ea814 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f5fa18eac89 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f5f9f763bec in QThreadPrivate::start(void*) (arg=0x557543090380) at thread/qthread_unix.cpp:329 #8 0x7f5f9e965609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5f9f294293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f5eedffb700 (LWP 2325)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55754567e0e4)
[konsole] [Bug 407915] New: The "Custom character color" option is required in "Cursor" tab
https://bugs.kde.org/show_bug.cgi?id=407915 Bug ID: 407915 Summary: The "Custom character color" option is required in "Cursor" tab Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: mdom...@gmail.com Target Milestone: --- SUMMARY --- The "Custom character color" option is required. When you go to "Edit current profile" -> "Appearance" -> "Cursor" -> "Color" you can choose between "Match current character" or "Custom cursor color" If you choose "Custom color cursor" there should be the possibility to also choose the color of the character under the cursor. Without this option it is impossible to have configurations such as: Dark background, clear letter, clear cursor or: Light background, dark letter, dark cursor. Because choosing "Custom color cursor" takes the color of the character under the cursor of the rest of the characters. This makes this option quite useless, because it will almost always produce very low contrast results. Either the cursor will have little contrast to the background, or the cursor will have little contrast to the character under the cursor itself. STEPS TO REPRODUCE -- 1. Go to "Edit current profile" -> "Appearance" 2. In "Color scheme & font" tab choose a scheme with dark background (Breeze, for example) 3. Then go to "Cursor" tab and choose "Block" for "Shape" option 4. Finally go to "Color" option, choose "Custom color cursor" and set it to yellow (or any light color) OBSERVED RESULT The character under the cursor has very low contrast to the cursor. It is not possible to choose a cursor color that contrasts simultaneously with the background and with the character under the cursor. EXPECTED RESULT -- There should be an option that allows you to customize the color of the character under the cursor. SOFTWARE/OS VERSIONS --- Windows: macOS: Linux/KDE Plasma: Arch Linux, kernel 5.1.4 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376011] New: Plasma deja de funcionar al cambiar a otra pantalla
https://bugs.kde.org/show_bug.cgi?id=376011 Bug ID: 376011 Summary: Plasma deja de funcionar al cambiar a otra pantalla Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manuelk...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Conecte un monitor a traves del HDMI, y luego cambie el video para que aparezca solamente en el monitor conectado, en ese momento el monitor conectado quedo negro y de a poco fueron apareciendo, los iconos y luego el panel inferior. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f55ec671900 (LWP 1666))] Thread 8 (Thread 0x7f551c5cd700 (LWP 2100)): #0 0x7f55e24987d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f55e24571cd in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f55e245742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f55e669c32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f55e6649fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f55e6484f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f55e97909b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f55e64899e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f55e5598734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f55e5d97d3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f5534443700 (LWP 1880)): #0 0x7f55e5d8f49d in poll () at /lib64/libc.so.6 #1 0x7f55e2457314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f55e245742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f55e669c32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f55e6649fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f55e6484f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f55ea313632 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f55e64899e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f55e5598734 in start_thread () at /lib64/libpthread.so.0 #9 0x7f55e5d97d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f55beb9e700 (LWP 1850)): #0 0x7f55e559d0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f55ebd4c93b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f55ebd4c969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f55e5598734 in start_thread () at /lib64/libpthread.so.0 #4 0x7f55e5d97d3d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f55cc9f8700 (LWP 1806)): #0 0x7f55e24987d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f55e24569e8 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f55e2457230 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f55e245742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f55e669c32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f55e6649fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f55e6484f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f55e97909b8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7f55e64899e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f55e5598734 in start_thread () at /lib64/libpthread.so.0 #10 0x7f55e5d97d3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f55ce3ae700 (LWP 1766)): #0 0x7f55e5d8b51d in read () at /lib64/libc.so.6 #1 0x7f55e2497670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f55e2456e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f55e24572a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f55e245742c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f55e669c32b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f55e6649fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f55e6484f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f55e97909b8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f55e64899e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f55e5598734 in start_thread () at /lib64/libpthread.so.0 #11 0x7f55e5d97d3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f55cfdf5700 (LWP 1731)): #0 0x7f55e669c0f0 in () at /usr/lib64/libQt5Core.so.5 #1
[okular] [Bug 373133] 16.12.0 Okular duplex printing on but no duplex printing done
https://bugs.kde.org/show_bug.cgi?id=373133 Manuel changed: What|Removed |Added CC||manuelbailenhernandez@gmail ||.com --- Comment #4 from Manuel --- Confirmed en KDE Neon I can't change print quality Okular 1.0.1 KDE Frameworks 5.30.0 Qt 5.7.1 (compilado con 5.7.0) El sistema de ventanas xcb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394936] New: I can`t save anything i draw
https://bugs.kde.org/show_bug.cgi?id=394936 Bug ID: 394936 Summary: I can`t save anything i draw Product: krita Version: 4.0.3 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: manuel.riedler...@gmail.com Target Milestone: --- I drew a picture in 60ß0x600 and i can`t save it and there is a crsh-report but it doesn`t say anything -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 306591] KDevelop crashed while saving via ssh
https://bugs.kde.org/show_bug.cgi?id=306591 --- Comment #3 from Manuel --- Soory, the crash is too old and I changed my system since then. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond
https://bugs.kde.org/show_bug.cgi?id=343383 Manuel changed: What|Removed |Added CC||manuelbailenhernandez@gmail ||.com --- Comment #18 from Manuel --- In my case I can deal with it pressing Ctrl key + middle button since I started with KDE-Neon 5.7, could it be a Distribution problem? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 384512] New: calibre-bin can not be installed because of dependency
https://bugs.kde.org/show_bug.cgi?id=384512 Bug ID: 384512 Summary: calibre-bin can not be installed because of dependency Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: manuelbailenhernan...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- calibre-bin : Depende: qtbase-abi-5-5-1 Depende: sip-api-11.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379519] New: Improvement to the color adjustment curves
https://bugs.kde.org/show_bug.cgi?id=379519 Bug ID: 379519 Summary: Improvement to the color adjustment curves Product: krita Version: 3.1.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: manuel.geno...@gmail.com Target Milestone: --- Hi. I think that would be great for the color adjustment curves this list of improvements: 1-Flexible histogram layout. Right now the histogram has a fixed size, and is a very little size. A flexible size that adapts to the parent window size would be better. 2-Logarythmic scale. Sometimes is necessary 3-Reset channel button, now for resetting the curves I need to cancel the operation and reopen the tool, loosing the other curves in other channels 4-Histogram view in the RGBA and Luminosity channels All of this is in the Gimp's adjustment curves tool, and are little details that made using the tool more easily -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond
https://bugs.kde.org/show_bug.cgi?id=343383 --- Comment #24 from Manuel --- I have the problem since I started with KDE Neon plasma 5.6 the problem looked like solved in Arch, see https://www.reddit.com/r/kde/comments/4gffxp/mouse_gestures_break_middle_click/ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 499736] New: Font features settings are not saved
https://bugs.kde.org/show_bug.cgi?id=499736 Bug ID: 499736 Summary: Font features settings are not saved Classification: Applications Product: konsole Version: 24.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: mdom...@gmail.com Target Milestone: --- SUMMARY Font features settings are not saved. STEPS TO REPRODUCE 1. Go to "Edit current profile" -> "Appearence" -> "Font" -> "Choose" - "Comma separated font features (e. g. liga, calt):" 2. Type: "zero" (without quotes). 3. Click the OK button. 4. Click the OK button (or Apply and OK). 5. Close Konsole 6. Open Konsole OBSERVED RESULT In the third step you can see how the terminal font adopts the established features and they are maintained while the program is open. But those changes are not saved. When I close and reopen Konsole, I can see that those font features are not preserved. I have observed that this option works correctly in other programs, such as Kwrite. I am on Artix Linux, but the exact same error occurs in other distributions such as Debian testing. EXPECTED RESULT That the changes are maintained, just as they do in other programs such as Kwrite. SOFTWARE/OS VERSIONS Operating System: Artix Linux (kernel 6.13.1-artix1-1) KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.1-artix1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499903] screen record not working fedora kde plasma
https://bugs.kde.org/show_bug.cgi?id=499903 Manuel changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Manuel --- The problem happend in different apps, ArmCord, OBS Studio, Discord (the app) and Discord in the browser (Brave and Firefox). I've also tried restarting the system -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499903] screen record not working fedora kde plasma
https://bugs.kde.org/show_bug.cgi?id=499903 --- Comment #2 from Manuel --- (In reply to Nicolas Fella from comment #1) > Which recording application are you using? I've tried in different apps, ArmCord, OBS Studio, Discord (the app) and Discord in the browser (Brave and Firefox) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499903] screen record not working fedora kde plasma
https://bugs.kde.org/show_bug.cgi?id=499903 Manuel changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499903] screen record not working fedora kde plasma
https://bugs.kde.org/show_bug.cgi?id=499903 --- Comment #4 from Manuel --- After making a test on VM it seems that bug only happens on Fedora 40,, but not on Fedora 41 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499903] New: screen record not working fedora kde plasma
https://bugs.kde.org/show_bug.cgi?id=499903 Bug ID: 499903 Summary: screen record not working fedora kde plasma Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Activities in general Assignee: plasma-b...@kde.org Reporter: manuelcam.conta...@protonmail.com CC: ivan.cu...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Use KDE Plasma 6.3.0 on Fedora 2. Try screen sharing or recording the hole screen 3. Notice it dosn't work OBSERVED RESULT You can't share/record the screen EXPECTED RESULT You can share/record the screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.3.0 (I think) Qt Version: 6.8.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444233] Option to sync, display and call using phone's contact list
https://bugs.kde.org/show_bug.cgi?id=444233 Manuel changed: What|Removed |Added CC||miaumen...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466812] New: Scroling direction is inconsistent between horizontal and vertical scrolling when using the scroll wheels the mouse
https://bugs.kde.org/show_bug.cgi?id=466812 Bug ID: 466812 Summary: Scroling direction is inconsistent between horizontal and vertical scrolling when using the scroll wheels the mouse Classification: Plasma Product: kwin Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: deve...@manuel-voegele.de Target Milestone: --- SUMMARY When using a mouse that has a dedicated horizontal scroll wheel like the Lotitech MX Master series has, the scrolling direction of the horizontal and vertical scrolling is inconsistent. When "inverted scrolling" is disabled: Scrolling vertically moves the scrollbar in the same direction as the finger on the mouse wheel Scrolling horizontally moves the scrollbar in the *inverted* direction of the finger movement Activating "inverted scrolling" switches both options around: Scrolling vertically moves the scrollbar in the *inverted* direction of the finger movement Scrolling horizontally moves the scrollbar in the same direction as the finger on the mouse wheel EXPECTED RESULT When "inverted scrolling" is disabled, both scrolling directions should be moving the scroll bar in the direction of the finger and when "inverted scrolling" is enabled, both scroll directions should be moving the scroll bar in the direction opposed to the finger movement. I think ideally, there should be dedicated settings for "inverted vertical scrolling" and "inverted horizontal scrolling" so users can mix and match to get their ideal scrolling style. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: LENOVO Product Name: 20NFCTO1WW System Version: ThinkPad E595 ADDITIONAL INFORMATION I'm using the Logitech MX Master 3s -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 412478] Kdevelop crashing when trying to configure meson project
https://bugs.kde.org/show_bug.cgi?id=412478 Manuel Mommertz <2...@gmx.de> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Manuel Mommertz <2...@gmx.de> --- I tried it with version 22.04.3 and cannot reproduce it anymore. Thanks for this nice peace of software. And thanks for still taking care of this old report. :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 444085] Popup menus from menu bar show up in wrong place.
https://bugs.kde.org/show_bug.cgi?id=444085 Manuel Schönheinz changed: What|Removed |Added CC||schoenhe...@googlemail.com --- Comment #6 from Manuel Schönheinz --- I have the same problem. It seems to be a wayland related issue since if I log in with X11 it is normal. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 329918] KDE Systrem Settings window crashes repeatably.
https://bugs.kde.org/show_bug.cgi?id=329918 Manuel Mommertz <2...@gmx.de> changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #10 from Manuel Mommertz <2...@gmx.de> --- Yes, I can reproduce with current stable version on gentoo -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 PrinterModel::updateDest (this=this@entry=0x55ff16eccba0, destItem=0x0, printer=...) at /usr/src/debug/kde-apps/print-manager-22.04.3/print-manager-22.04.3/libkcups/PrinterModel.cpp:249 #5 0x7f54aa698017 in PrinterModel::getDestsFinished (this=0x55ff16eccba0, request=0x55ff16bbdb50) at /usr/src/debug/kde-apps/print-manager-22.04.3/print-manager-22.04.3/libkcups/PrinterModel.cpp:137 #6 0x7f5528e2b22f in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f5529a6979f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #8 0x7f5528e00938 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f5528e03e2e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #10 0x7f5528e51143 in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7f5526b6cd5b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7f5526b6d008 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7f5526b6d0bf in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x7f5528e50bf4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #15 0x7f5528dff3cb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #16 0x7f5528e07710 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #17 0x55ff15a44be0 in ?? () #18 0x7f55287a220a in __libc_start_call_main () from /lib64/libc.so.6 #19 0x7f55287a22bc in __libc_start_main () from /lib64/libc.so.6 #20 0x55ff15a454b1 in ?? () [Inferior 1 (process 24007) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488824] New: Meta Key Won't Open Application Menu
https://bugs.kde.org/show_bug.cgi?id=488824 Bug ID: 488824 Summary: Meta Key Won't Open Application Menu Classification: Plasma Product: plasmashell Version: 6.1.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@nuth.ch CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 170704 --> https://bugs.kde.org/attachment.cgi?id=170704&action=edit Both default, broken version and fixed version of the `kglobalshortcutsrc` file. SUMMARY In the most recent version of plasma released on Arch Linux (6.1.0-1), the Application Menu won't open when pressing an individual Meta key. My keyboard has two Meta keys - one on the left and one on the right. When pressing both at once, the Application Menu opens properly. STEPS TO REPRODUCE 1. Connect a keyboard with two Meta keys. 2. Reset Global Shortcuts in Plasma's System Settings app 3. Take note that the Application Menu will only open if you press both Meta keys at once OBSERVED RESULT The Application Menu only opens if you press both Meta keys at the same time. EXPECTED RESULT The Application Menu should open when one Meta key is pressed individually. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.5-arch1-1 (64-bit) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION When removing `Meta` from `plasmashell`'s global shortcut list, the Meta key opens the Application Menu properly again. There is a `kglobalshortcutsrc` file with the current defaults and a `kglobalshortcutsrc` file with the aforementioned fix applied in the `.tar.gz` file in the attachments. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488824] Meta Key Won't Open Application Menu
https://bugs.kde.org/show_bug.cgi?id=488824 --- Comment #5 from Manuel Thalmann --- (In reply to fanzhuyifan from comment #2) > Can this be reproduced for a newly created user? Is this on x11 or wayland? Thanks you so much for coming back at me! I just gave it a quick go and I could reproduce it on X11, too However, on X11 I can see a translucent pane sliding up/appearing and immediately sliding down/disappearing again for about 1 second. I also just gave it a try for a newly created user and I could reproduce the error. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488824] Meta Key Won't Open Application Menu
https://bugs.kde.org/show_bug.cgi?id=488824 --- Comment #6 from Manuel Thalmann --- Created attachment 170825 --> https://bugs.kde.org/attachment.cgi?id=170825&action=edit The Pane that is temporarily visible instead of opening up the Application Menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488824] Meta Key Won't Open Application Menu
https://bugs.kde.org/show_bug.cgi?id=488824 --- Comment #9 from Manuel Thalmann --- (In reply to fanzhuyifan from comment #8) > FWIW I still cannot reproduce by replacing my kglobalshortcutsrc with the > provided kglobalshortcutsrc.broken on wayland, arch linux, plasma 6.1 So > probably some other factor is involved here, not just the kglobalshortcutsrc > file. Because of the error occuring on my PC but not on my laptop, I assumed that it might be for the keyboard having 2 Meta keys. But this does not seem to be the case, then. Is there anything I could try out or analyze? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487703] New: workspace.activateWindow missing
https://bugs.kde.org/show_bug.cgi?id=487703 Bug ID: 487703 Summary: workspace.activateWindow missing Classification: Plasma Product: kwin Version: 6.0.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: rud...@rudd-o.com Target Milestone: --- Cannot call activateWindow on workspacewrapper JS object, despite being documented here: https://develop.kde.org/docs/plasma/kwin/api/#read-only-properties-4 raiseWindow does not focus the supplied window so this is not the same as activating and is not enough. Sample code at https://rudd-o.com/linux-and-free-software/how-to-raise-a-window-under-wayland-or-x11-when-using-kde-kwin-plasma/ see commented try/catch block. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487703] workspace.activateWindow missing
https://bugs.kde.org/show_bug.cgi?id=487703 --- Comment #2 from Manuel Amador (Rudd-O) --- Yep it appears the comment is wrong and it should be fixed, but activeWindow property works. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 487719] kdeconnect's mdns server causes naming conflicts with avahi-daemon
https://bugs.kde.org/show_bug.cgi?id=487719 Manuel C changed: What|Removed |Added CC||manuel.manu.del...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 322922] Dolphin should not store .directory files inside the actual directory to avoid cluttering and polluting the filesystem; should instead store this data in extended attributes
https://bugs.kde.org/show_bug.cgi?id=322922 Manuel C changed: What|Removed |Added CC||manuel.manu.del...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[ksystemstats] [Bug 486946] New: Wrong amount of total disk space
https://bugs.kde.org/show_bug.cgi?id=486946 Bug ID: 486946 Summary: Wrong amount of total disk space Classification: Frameworks and Libraries Product: ksystemstats Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: manuelalcaraz...@gmail.com CC: ahiems...@heimr.nl Target Milestone: --- SUMMARY System Monitor reports a wrong amount of total available disk space. It says that I have 2,0 TiB of total space when I only have two drives of 1 TB + 256 GB. STEPS TO REPRODUCE 1. Open System Monitor. 2. See the Disk card with the total available space. OBSERVED RESULT It shows that I have 2 TiB of total space. EXPECTED RESULT It shows that I have around 1,2-1,3 TiB of total space. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-arch1-2 (64-bit) ADDITIONAL INFORMATION df -h (loop devices removed for clarity) S.ficherosTamaño Usados Disp Uso% Montado en /dev/mapper/vg--root-lv--root 684G86G 598G 13% / devtmpfs4,0M 0 4,0M 0% /dev tmpfs16G41M 16G 1% /dev/shm efivarfs128K51K 73K 42% /sys/firmware/efi/efivars tmpfs 6,2G 9,8M 6,2G 1% /run tmpfs16G13M 16G 1% /tmp /dev/nvme0n1p2 1022M 183M 840M 18% /boot /dev/mapper/home230G 109G 120G 48% /home tmpfs 3,1G68K 3,1G 1% /run/user/1000 lsblk (loop devices removed for clarity) NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS nvme0n1 259:00 931,5G 0 disk ├─nvme0n1p1 259:10 230G 0 part │ └─md127 9:127 0 229,9G 0 raid1 │ └─home 254:30 229,9G 0 crypt /home ├─nvme0n1p2 259:20 1G 0 part /boot └─nvme0n1p3 259:30 700G 0 part └─root254:00 700G 0 crypt ├─vg--root-lv--swap 254:1016G 0 lvm [SWAP] └─vg--root-lv--root 254:20 684G 0 lvm / nvme1n1 259:40 232,9G 0 disk └─nvme1n1p1 259:50 230G 0 part └─md127 9:127 0 229,9G 0 raid1 └─home 254:30 229,9G 0 crypt /home -- You are receiving this mail because: You are watching all bug changes.
[ksystemstats] [Bug 486946] Wrong amount of total disk space
https://bugs.kde.org/show_bug.cgi?id=486946 --- Comment #1 from Manuel Alcaraz --- Bug https://bugs.kde.org/show_bug.cgi?id=477983 seems to be related but I'm not sure if it's the same issue as it says that it got fixed in 6.1 (not sure if that is Frameworks version or Plasma version) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] New: Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 Bug ID: 445587 Summary: Response to mouse clicks broken Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- SUMMARY Since today's kde/qt updates, the Overview effect does not respond to mouse clicks anymore. (This used to work correctly prior to the update.) STEPS TO REPRODUCE 1. Trigger the Overview effect (e. g. using active corner or shortcut) 2. (Left-)click on the area of a window OBSERVED RESULT Nothing happens. EXPECTED RESULT The effect should be closed and the clicked window should be shown. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Might be Wayland-only. I haven't used X since a longer time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 Manuel Geißer changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #1 from Manuel Geißer --- Created attachment 143622 --> https://bugs.kde.org/attachment.cgi?id=143622&action=edit Screencast -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #2 from Manuel Geißer --- Same problem on X - I have made you a screencast. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #3 from Manuel Geißer --- By the way, the purple description background is really strange. That's only on X, not on Wayland, though. Is this on purpose, or should I file a separate issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #4 from Manuel Geißer --- Created attachment 143624 --> https://bugs.kde.org/attachment.cgi?id=143624&action=edit Update log -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 412477] meson support not working when meson is a symlink
https://bugs.kde.org/show_bug.cgi?id=412477 --- Comment #6 from Manuel Mommertz <2...@gmx.de> --- (In reply to Igor Kushnir from comment #5) > Can anyone verify that > https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/251 fixes this > issue? Yes, works perfectly! :) Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455913] [Wayland + Nvidia] Krunner stops showing after opening / closing it a few times
https://bugs.kde.org/show_bug.cgi?id=455913 Clarence Manuel changed: What|Removed |Added CC||rencedm...@gmail.com --- Comment #5 from Clarence Manuel --- Same thing with my PC, but for Application Launcher. I'm using Fedora 36 KDE Plasma Spin. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 442027] New: Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027
Bug ID: 442027
Summary: Variables inside f-strings are not highlighted and not
recognised for renaming
Product: kdev-python
Version: 5.6.2
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language support
Assignee: m...@svenbrauch.de
Reporter: geisse...@gmail.com
Target Milestone: ---
SUMMARY
In Python 3.6 f-strings got introduced. They're a simple and well-readable way
to include variables in messages. If a string is preceded with an f character,
variables can be stated inside curly brackets and will automatically get
formatted as a string.
Example:
```python3
x0 = 5
y0 = 20
multiplied = x0 * y0
message = f"Position: ({x0}, {y0}); multiplied {multiplied}"
```
There are lots of nice guides concerning f-string, e. g.
https://www.geeksforgeeks.org/formatted-string-literals-f-strings-python/
Variables inside the f-string curly brackets are apparently not recognised by
KDevelop. There is no syntax highlighting for these variables and they are also
not considered for renaming operations. Renaming either of `x0` or `y0` in the
above example would ignore the occurrence inside the f-string.
This is a likely cause for UnboundLocalErrors: The user renames the variable,
clicks on KDevelop's auto-rename feature and thinks all variables are replaced,
but suddenly the code crashes at f-string formatting becaues the old variable
name is still there.
STEPS TO REPRODUCE
1. Paste any f-string code into KDevelop, for instance the above example. Save
the file for highligthing and semantic analysis to get active.
2. Rename a variable, e. g. `x0` to `xpos`
3. Use the auto-rename feature
OBSERVED RESULT
- Variables inside f-strings are not highlighted
- While all occurrences of a variable outside f-string are replaced properly,
the occurrences inside f-string curly brackets are ignored.
EXPECTED RESULT
- Variables should always be highlighted, also inside f-strings
- Renaming operations should also replace occurrences of the variable in
f-strings
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-27-generic (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
/
--
You are receiving this mail because:
You are watching all bug changes.
[kdev-python] [Bug 442027] Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027 --- Comment #1 from Manuel Geißer --- outside f-string*s -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] New: [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Bug ID: 442029 Summary: [Feature request] Add file exclude options for quick open Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: QuickOpen Assignee: kdevelop-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- SUMMARY Quick open is a useful feature. However, I am missing an option to exclude certain directories or file extensions. For example, my repository contains Sphinx documentation, and quick open also shows all documentation build artifacts. This can be quite problematic: If I have a file named `api.rst`, building the docs would also generate an artifact named `api.rst.txt`. Now it could happen that you accidentally open and edit the `.txt` file which has the same content as the `.rst` equivalent, but it will be overwritten with the next build cycle and all changes are lost. So it would be quite helpful to be able to exclude the build directory from quick open, not only to prevent inadvertently opening the wrong file, but also to get a cleaner overview. My quick open panel is often spammed with compiled objects. STEPS TO REPRODUCE 1. Clone a repository that contains Sphinx documentation 2. Import it into KDevelop 3. Build the documentation (`make html`) 4. Trigger quick open OBSERVED RESULT All documentation build artifacts will show up. EXPECTED RESULT Only relevant project files should be displayed. Therefore, an option in the settings would be required to exclude certain file types or directories. (Alternatively, though more complex, it could also be possible to read the .gitignore file and not show objects that aren't part of the revision control, but as KDevelop also supports versioning systems other than git this might not be a straightforward solution.) SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Since KDevelop is a large application, the option I am requesting might already exist at some hidden place. If so, please point me at it and forgive the false issue :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 442027] Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027 --- Comment #3 from Manuel Geißer --- Thanks for the response. Unfortunately I can't contribute to KDevelop myself, as I only know Python an no C++. I'm currently learning PySide2 but my Qt skills are still very limited. I also don't have the time to get my feet wet on a new software project at the moment... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 --- Comment #2 from Manuel Geißer --- Aha, thank you! I only searched the settings and the plugin, but overlooked the project configuration. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Manuel Geißer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 --- Comment #4 from Manuel Geißer --- Thanks for the help! I'm rather new to KDevelop and haven't unraveled its full capabilities yet. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] New: [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Bug ID: 442226 Summary: [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions Product: kate Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- Created attachment 141422 --> https://bugs.kde.org/attachment.cgi?id=141422&action=edit Pop-up window SUMMARY When typing in a string into either of the "Search" or "Replace" fields, there are sometimes strange floating windows instead of a dropdown menu for completition propositions. These windows are rather annoying, because they steal focus from the text input field. Then I usually press ESC with the intention to get rid of the pop-up, but instead it closes the search/replace plugin... I think this issue affects Wayland only. STEPS TO REPRODUCE 1. Open Kate 2. Open the "Search and Replace" plugin 3. Type in a string into the "Search" or "Replace" field 4. Keep editing the text until the bug occurs. OBSERVED RESULT Sometimes a separate, centered pop-up window appears instead of a dropdown menu. EXPECTED RESULT There should never be pop-ups for this. It should always be a dropdown menu. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-34-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Manuel Geißer changed: What|Removed |Added Keywords||regression, wayland CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 Manuel Geißer changed: What|Removed |Added CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 --- Comment #2 from Manuel Geißer --- It is "regression from earlier on wayland". -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] New: Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
Bug ID: 442280
Summary: Okular does not take /UserUnit into account (page size
incorrect)
Product: okular
Version: 21.08.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: PDF backend
Assignee: okular-de...@kde.org
Reporter: geisse...@gmail.com
Target Milestone: ---
Created attachment 141453
--> https://bugs.kde.org/attachment.cgi?id=141453&action=edit
userunit_10.pdf
SUMMARY
[PDF background]
In the PDF format, coordinates are given in PDF points, where by default 1
point is equivalent to 1/72 of an inch (1in -> 2.54cm). However, PDFs can
define custom units on a per-page basis, using the /UserUnit key.
/UserUnit is a float or decimal that scales the default conversion fraction of
1/72, so for a /UserUnit of 10, 1pt would mean 10/72in.
[What Okular does]
It seems that Okular (like many other open-source PDF software) does not take
/UserUnit into account for the displayed page size.
The attached test document `userunit_10.pdf` defines a /UserUnit of 10.
The document's /MediaBox looks like this:
```python3
[ Decimal('0.0'), Decimal('0.0'), Decimal('1785.6'), Decimal('1785.6')
```
Now the default conversion with 1pt -> 1/72in returns 630x630mm, which is what
Okular displays. However, this is incorrect. In reality, the size is 6300mm, 10
times larger!
(In particular, /UserUnit is used by Adobe Illustrator and possibly other PDF
software to circumvent the maximum number of 14400pt imposed by Adobe Reader
and some other PDF renderers.)
STEPS TO REPRODUCE
1. Open the attached file in Okular
2. Go to File -> Properties
3. See the displayed page size
4. Inspect the document with the pikepdf python library, or and other PDF
library of your choice
5. Print the /MediaBox and /UserUnit of page 0
OBSERVED RESULT
Displayed page size is too small by factor 10.
EXPECTED RESULT
Displayed page size should always reflect the real page size and take /UserUnit
into account.
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-34-generic (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added CC||aa...@kde.org, ||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 --- Comment #1 from Manuel Geißer --- Ping. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #1 from Manuel Geißer ---
Python shell code to reproduce (replace TestFiles.userunit_10 with the path
string where you saved the file, and skip the first import which depends on
custom test infrastructure of the lib I am developing):
```python3
Python 3.8.10 (default, Jun 2 2021, 10:49:15)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from tests_pdfnodegraph.testfiles import TestFiles
>>> import pikepdf
>>> pdf = pikepdf.Pdf.open(TestFiles.userunit_10)
>>> page = pdf.pages[0]
>>> page.MediaBox
pikepdf.Array([ Decimal('0.0'), Decimal('0.0'), Decimal('1785.6'),
Decimal('1785.6') ])
>>> page.UserUnit
Decimal('10.0')
>>> 1785.6 * 1/72 * 25.4
629.91998
>>> 1785.6*10 * 1/72 * 25.4
6299.2
```
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #2 from Manuel Geißer --- Created attachment 141454 --> https://bugs.kde.org/attachment.cgi?id=141454&action=edit userunit_screenshot -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #3 from Manuel Geißer --- To clarify, I think it is not only the displayed size number that is incorrect, but also the space reserved for rendering the actual page: The screenshot I just added illustrates it better: The first page is from the userunit_10 file. The other 2 pages are ANSI A and A4 size, which is very roughly 200mm width - put one of the smaller pages three times next to each other, and it approximately matches the width of the larger page, although in fact it should be a lot larger - roughly thirty times the width of the smaller page! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #4 from Manuel Geißer --- > the space reserved for rendering the actual page or better formulated: the proportions of different pages to each other -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #5 from Manuel Geißer ---
Created attachment 141455
--> https://bugs.kde.org/attachment.cgi?id=141455&action=edit
Proportions pdf
For you to confirm the UserUnit is set on the first page of the document in the
screenshot, but not on the other pages.
```python3
>>> from tests_pdfnodegraph.pathtools import TestOutput
>>> pdf = pikepdf.open(join(TestOutput,'out_14.pdf'))
>>> page = pdf.pages[0]
>>> page.UserUnit
Decimal('10.0')
>>> page_2 = pdf.pages[1]
>>> page_2.UserUnit
Traceback (most recent call last):
File "", line 1, in
File "/home/manuel/.local/lib/python3.8/site-packages/pikepdf/_methods.py",
line 1143, in __getattr__
return getattr(self.obj, name)
AttributeError: /UserUnit
>>>
```
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added Summary|Okular does not take|Okular does not take |/UserUnit into account |/UserUnit into account |(page size incorrect) |(page size incorrect for ||certain files) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #6 from Manuel Geißer --- List of other affected PDF software: * Chromium integrated PDF viewer (uses PDFium) * Firefox integrated PDF viewer (uses pdf.js) * Inkscape PDF importer (uses Poppler) * Scribus PDF importer * PDFStitcher (uses pikepdf) * PDF Arranger (uses pikepdf) * even the proprietary Master PDF Editor 4 and 5 Probably more ... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #7 from Manuel Geißer --- Created attachment 141456 --> https://bugs.kde.org/attachment.cgi?id=141456&action=edit adobe_reader ... only Adobe Reader gets the proportions right -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added CC|aa...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #9 from Manuel Geißer --- Sorry. I just thought you'd be the maintainer of Okular, and wondered why you are not in the CC list, but apparently this has its reason. Sorry, really. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 Manuel Geißer changed: What|Removed |Added CC|aa...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #11 from Manuel Geißer --- Pdfinfo from poppler-utils does not show regular units like centimetres or inches, but it keeps the PDF points. Pdfinfo is a low-level tool that does not perform unit conversion on its own. However, it does not display the UserUnit value, so you could say it's somewhat wrong in the sense that it withholds information. So to judge who is at fault, it would be relevant to know how Okular obtains the displayed page size. Does it inspect CropBox/MediaBox and convert to units itself, or does it retrieve finished unit values from Poppler? In the first case, the source of the bug would be in Okular, in the second case it would be in Poppler. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #12 from Manuel Geißer --- I've searched a bit in the code, and at least the rendering proportions issue is Okular's fault I think: https://github.com/KDE/okular/blob/3a513f34b8bbba87bd96718dc96089e079578d55/generators/poppler/generator_pdf.cpp#L721 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #13 from Manuel Geißer --- Another possibly relevant code passage: https://github.com/KDE/okular/blob/3a513f34b8bbba87bd96718dc96089e079578d55/generators/poppler/generator_pdf.cpp#L1303 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #15 from Manuel Geißer --- >From the referenced code we can see that Okular uses the Poppler::Page::pageSizeF() function to obtain the page size: https://poppler.freedesktop.org/api/qt5/classPoppler_1_1Page.html#a598c287971839a113552176fc387ab30 This function is based on CropBox and returns points. What about the following solution: - the pageSize() and pageSizeF() functions should be changed to take /UserUnit into account, as the docs suggest the returned value is always given in 1/72in units - Additionally there should be some way to obtain the /UserUnit value with poppler. I couldn't find any such option in the documentation, though I only skimmed it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #16 from Manuel Geißer --- > I think you should report at PDFium, pdf.js, Poppler, and pikepdf. Be careful - there are considerable differences between these libraries. I don't really know about pdf.js and PDFium, but pikepdf is quite low-level and does not provide a function to obtain page size on its own - this needs to be done downstream using CropBox/MediaBox, UserUnit, and Rotate. > There is also a muPDF backend for Okular. Did you try that? `mutool info > userunit_10.pdf` reports `[ 0 0 17856 17856 ]`. Yes, I am aware that MuPDF directly takes /UserUnit into account. I noticed this during the tests for my lib (which also has a (Py)MuPDF rendering backend). How do I obtain the MuPDF backend for Okular, though? Is it possible that KDE Neon does not provide it? (I already have the okular-extra-backends package installed...) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #17 from Manuel Geißer --- > I think you should report at PDFium, pdf.js, Poppler, and pikepdf. I think it might be better if the Okular developers would report to Poppler, since I never used the Poppler library interface myself and thus don't have the required background. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #18 from Manuel Geißer --- > I think it might be better if the Okular developers would report to Poppler, > since I never used the Poppler library interface myself and thus don't have > the > required background. I now filed an issue at Poppler nevertheless, as nobody else seems to have felt any responsibility to do so. The report essentially just references this thread, as it should contain all relevant information. https://gitlab.freedesktop.org/poppler/poppler/-/issues/1139 @OkularDevelopers: Please verify/confirm whether changing pageSize() and pageSizeF() would really be sufficient to fix the UserUnit issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #19 from Manuel Geißer --- > There is also a muPDF backend for Okular. Did you try that? The Ubuntu Focal mupdf package currently fails to open the file (https://bugs.launchpad.net/ubuntu/+source/mupdf/+bug/1943366). This likely is fixed in newer versions of mupdf or affects the MuPDF GUI only, though. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 442900] New: [Feature request] Optional reStructuredText syntax highlighting for inline Python documentation
https://bugs.kde.org/show_bug.cgi?id=442900 Bug ID: 442900 Summary: [Feature request] Optional reStructuredText syntax highlighting for inline Python documentation Product: frameworks-syntax-highlighting Version: 5.86.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: geisse...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- SUMMARY Many Python projects use inline code documentation with sphinx-autodoc, since this is a lot less maintenance work than separate code documentation. This way, it is much easier to keep code and docs consistent, especially as method parameter headers are generated automatically. STEPS TO REPRODUCE 1. Open a Python file with inline Sphinx reStructuredText documentation in Kate OBSERVED RESULT The Python code is syntax-highlighted. The inline rst markup is not highlighted, however. EXPECTED RESULT It would be nice to have optional rst syntax highlighting for inline code documentation indicated with `""" documentation text here """`. SOFTWARE/OS VERSIONS 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.11.0-36-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7.2 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION Perhaps this idea is a bit far-fetched and/or hard to implement, so this is really just a suggestion. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #19 from Manuel Geißer --- Not sure whether the driver really is the cause. Yes, it may be possible, but I think you shouldn't rule out a cause in Plasma or Qt without further investigation. I'd rather not consider this issue resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 439478] Menu/tooltip background is transparent
https://bugs.kde.org/show_bug.cgi?id=439478 --- Comment #21 from Manuel Geißer --- Switching the compositing method does not affect the bug in any way. I already tried that long ago... I rather thought in the direction of a damaged configuration file issue. I've already had that a few times. If it were random rendering glitches, I would also suspect the graphics driver, but the issue with transparent instead of black background is so systematic that this seems kind of unlikely to me. However, I will file a bug with the graphics developer when I have time. I also thought of reinstalling the system at some point and see whether that fixes some of my impossible-to-reproduce issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 --- Comment #23 from Manuel Geißer --- > Present Windows effect is what is causing the issue here. Disabled it and I > can > see the background once again. Wow, good catch! Disabling Present Windows indeed solves the problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #20 from Manuel Geißer --- > There is also a muPDF backend for Okular. Did you try that? Is this at all still current? I checked out okular from https://invent.kde.org/graphics/okular.git and built with CMake, but couldn't find any hints on a MuPDF backend. `ls generators/` only shows ``` chm CMakeLists.txt comicbook djvu dvi epub fax fictionbook kimgio markdown mobipocket plucker poppler spectre tiff txt xps ``` -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #21 from Manuel Geißer --- `grep -r mupdf` on the Okular source tree doesn't find anything, either -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #23 from Manuel Geißer --- I guess you are referring to https://invent.kde.org/sandsmark/okular-mupdf-backend ? The thing is, there are multiple unofficial Okular MuPDF generators around... Moreover, why is this not officially part of Okular and not packaged in Debian, Ubuntu, and KDE Neon? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #24 from Manuel Geißer --- So I installed the dependencies and tried to build okular-mupdf-backend (from git master), but it fails with some "Variable not declared in this scope" error. Also there have been no commits to the repository since a year. Is this backend still functional? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #25 from Manuel Geißer --- Created attachment 142205 --> https://bugs.kde.org/attachment.cgi?id=142205&action=edit (unrelated) okular-mupdf-backend build error -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #27 from Manuel Geißer --- Sure. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442226] [search/replace + Wayland] Strange pop-ups instead of a dropdown menu for completition propositions
https://bugs.kde.org/show_bug.cgi?id=442226 --- Comment #4 from Manuel Geißer --- I think this is perhaps rather an issue with Qt(-Wayland) than with Kate -- A question: Is it possible to deactivate completition, or dismiss the completition history as a workaround? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #91 from Manuel Geißer --- > Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and > they > are going to chisel and polish it for further MONTHS before this fix is > available to end users. Yeah, if developers had acknowledged what an annoyance this dimming is, they could just have commented out the problematic line and release an updated package nine years ago, or they could have merged PR 885 five months ago... It appears that fixing usability issues is just regarded as an unimportant side-effect of the Present Windows replacement; primarily it's just the move to a different underlying technology. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #93 from Manuel Geißer --- > What do you mean? Nate said the effect is being shipped with Plasma 5.23 > though > it "may" (which I guess is now "will") not replace it until later. Is this > wrong? The problem we're talking about is that it will take even longer for this usability issue to be fixed, due to Plasma 5.23 getting additional months of polishing and QA. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #95 from Manuel Geißer --- > Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and > they > are going to chisel and polish it for further MONTHS before this fix is > available to end users. Well, actually that turns out to be wrong. It got released today (that is, in KDE Neon). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423551] Regression in some XWayland popups
https://bugs.kde.org/show_bug.cgi?id=423551 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #3 from Manuel Geißer --- Well, I sometimes experienced this issue with xwayland Firefox on current KDE Neon User, for instance with the popup for creating new bookmarks. If it happens, the only thing that helps is to terminate the whole program, otherwise the popup is still visible on top of all other applications. I'm now using native wayland firefox which doesn't have those problems. Are you sure this issue regarding xwayland popups is fixed in newer versions? -- You are receiving this mail because: You are watching all bug changes.
