[kwin] [Bug 433664] Desktop becomes really slow after disabling and enabling the kwin compositor again (After 5.21 Update)
https://bugs.kde.org/show_bug.cgi?id=433664 Daniel Eckl changed: What|Removed |Added CC||daniel.e...@gmx.de --- Comment #14 from Daniel Eckl --- Created attachment 147682 --> https://bugs.kde.org/attachment.cgi?id=147682=edit two screens side-by-side, one laptop below, issue is present My setup has a laptop screen below one of two monitors. This setup is affected, too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436240] Lag/hang in apps and Plasma when a notification appears while compositing is active and using a non-NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=436240 Daniel Eckl changed: What|Removed |Added CC||daniel.e...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444536] Compositor slows down to ~1fps after changing any of the compositor settings or restarting kwin
https://bugs.kde.org/show_bug.cgi?id=444536 Daniel Eckl changed: What|Removed |Added CC||daniel.e...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445673] FPS drops to 1 after compositor power off or restart
https://bugs.kde.org/show_bug.cgi?id=445673 Daniel Eckl changed: What|Removed |Added CC||daniel.e...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451125] Changing kwin related settings when OpenGL renderer is enabled makes kwin sluggish
https://bugs.kde.org/show_bug.cgi?id=451125 Daniel Eckl changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||daniel.e...@gmx.de --- Comment #2 from Daniel Eckl --- I have the same issue on Kubuntu 21.10 with KDE Backports PPA Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-37-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 I cannot reconfigure anything kwin related that restarts kwin, without having a nearly unusable system, framerate of everything drops to about 1-2 fps. My workaround then is to disable compositing by pressing CRTL-SHIFT-F12, but for re-enabling a working compositing I have to logout and back in. The issue also appears when I restart kwin on the console with using "kwin_x11 --replace". Console output: $ kwin_x11 --replace Warning: Setting a new default format with a different version or profile after the global shared context is created may cause issues with context sharing. kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5091:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5093:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:47: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5099:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5111:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5113:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5117:45: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5120:46: this compose sequence is a duplicate of another; skipping line OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 620 (KBL GT2) OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.2.6 OpenGL shading language version string: 4.60 Driver: Intel GPU class: Kaby Lake OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 21.2.6 X server version: 1.20.13 Linux kernel version: 5.13 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_core: XCB error: 10 (BadAccess), sequence: 3598, resource id: 1993, major code: 142 (Composite), minor code: 2 (RedirectSubwindows) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 451798] New: Replace all with escape sequences broken
https://bugs.kde.org/show_bug.cgi?id=451798 Bug ID: 451798 Summary: Replace all with escape sequences broken Product: kate Version: 21.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: danielrosc...@phoenitydawn.de Target Milestone: --- SUMMARY Recently "Replace All" in the replace dialog broke in certain cases when using the "Escape sequence" mode and only replaces a subset of strings to replace. Clicking "Replace all" multiple times will continue replacing strings until the desired result is eventually reached. STEPS TO REPRODUCE 1. Open an new document in Kate. 2. Add the following content to the document: 1\n 2\n 3\n 4\n 3. Open the search replace dialog (CTRL + R) 4. Ensure the search/replace mode is set to "Escape sequences" 5. Enter "\\n" into the "Find" input field and "\n" into the "Replace" input field 6. Click "Replace All" OBSERVED RESULT A toast stating "2 replacements made" and the following content in the document now: 1 2 3\n 4\n EXPECTED RESULT A toast stating "4 replacements made" and the following content in the document now: 1 2 3 4 SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 450932] Needs a reset option
https://bugs.kde.org/show_bug.cgi?id=450932 --- Comment #2 from Daniel Bergløv --- (In reply to Nate Graham from comment #1) > Can we re-focus on the issues that led you down the path of looking for > workarounds in the first place? Can you describe those issues? I can try. So I have a setup with two PC displays and a TV, all hooked up to a Radeon 580 GFX card on a Desktop PC. All 3 screens only had support for HDMI and my GFX card has two HDMI and two DP output ports, so the TV was using an HDMI/DP adaptor. It worked fine, except for the general issue that KDE has with multiple displays (still exists in Plasma 5.24 btw). Then I bought two new PC displays to replace the old ones and it worked fine as well, after replacing them and setting them up. But at some point my TV started to flicker, so I had to do some trouble shooting. At first I thought that this was due to a poor HDMI/DP adaptor, since this seamed to be the weak part of the setup. I switched the adaptor to another one that I had laying around, but now the TV only displayed a resolution of 800X600, and I could not change this. I thought that both adaptors was broken in different ways, and thought that I would go without them. The new PC displays had both HDMI and DP options, so I switched one of them to DP and removed the adaptor for the TV and plugged it in HDMI directly instead. Now one of the PC displays did not turn on no mater what I did. I tried putting everything back to the original outputs and adaptors, but now one of the displays would not go higher than 800X600. I then Removed that turned off display, and the TV got back it's resolution. I plugged the display back in, and the TV changed resolution and the display did not turn on. I now tried switching both displays to DP and again remove the adaptor for the TV. Now the TV did not turn on and one of the displays would not gain a higher resolution than 800X600. Removing the working display, turned the TV back on and fixed the resolution on the other display. I searched the web for where KDE kept it's display configs, since it was clear that something was remembered in a strange way. I found something about ~/.local/share/kscreen and deleted that. After a reboot, everything was back and I could setup all of the displays again, the way I liked it. I also found out that it was the HDMI cable from the TV that made the flickering, not the adaptor. However I now have it setup using DP to DP on the displays and HDMI to HDMI on the TV. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 437791] konsole window 1 line height when there is no konsolesrc
https://bugs.kde.org/show_bug.cgi?id=437791 Daniel Noga changed: What|Removed |Added CC||noga.d...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 451312] Shutdown doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=451312 --- Comment #13 from Daniel Bruckner --- Problem solved: In Muon I saw that 3 packages were not updated. The message appears in the toolbar at the bottom. However, the packages names were not displayed. After I typed "sudo apt full-upgrade" in the terminal, these packages were displayed: - libwayland-client0 - libwayland-cursor0 - libwayland-egl1 After that I manually upgraded the packages in Muon. -> Everything work again -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 451312] Shutdown doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=451312 --- Comment #4 from Daniel Bruckner --- This are the installed i386 libraries as I founded in Munot by searching with the keyword "i386". I don't use Wayland. Using X11-Plasma Thanks a lot! Am 09.03.22 um 15:15 schrieb francisco_t: > https://bugs.kde.org/show_bug.cgi?id=451312 > > --- Comment #3 from francisco_t --- > Do you have i386 libraries installed? I have the libwayland updates blocked > because 32 bits libraries. > And Neon doesn't support 32 bits libraries :( > -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 451312] New: Shutdwon does'nt work anymore
https://bugs.kde.org/show_bug.cgi?id=451312 Bug ID: 451312 Summary: Shutdwon does'nt work anymore Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dbruck...@posteo.de Target Milestone: --- After the last bugfix release March 2022 on KDE Plasma 5.24.3 I cannot shutdown the computer. ctrl+alt+del does not work, shutdown via application overview (starter) does not respond. If I go back to the state before the update via Timeshift, everything works. STEPS TO REPRODUCE 1. ctrl+alt+del / shutdown via starter 2. no reaction 3. OBSERVED RESULT - no reaction EXPECTED RESULT - menu with "shutdown" - "logout" - "restart" SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE-Neon 5.24 (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Kernel 5.13.0-35-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450981] New: Dolphin scrashes when adding new folder
https://bugs.kde.org/show_bug.cgi?id=450981 Bug ID: 450981 Summary: Dolphin scrashes when adding new folder Product: dolphin Version: 21.12.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: daniel.winiarski.dw+...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.12.2) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-30-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.2 [KCrashBackend] -- Information about the crash: Every attempt of adding new folder in GDrive occurs Dolphin's crash. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 1199] [New LWP 1200] [New LWP 1202] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f6982b5baff in __GI___poll (fds=0x7ffedb4550f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f697e103600 (LWP 1197))] Thread 4 (Thread 0x7f696f7fe700 (LWP 1202)): #0 __GI___libc_read (nbytes=16, buf=0x7f696f7fd9d0, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=22, buf=0x7f696f7fd9d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f6980c7fb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6980c36ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6980c37312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6980c374a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6983129a0b in QEventDispatcherGlib::processEvents (this=0x7f695c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f69830cdc9b in QEventLoop::exec (this=this@entry=0x7f696f7fdbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f6982ee7362 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f6982ee8543 in QThreadPrivate::start (arg=0x55aa71ba5e50) at thread/qthread_unix.cpp:331 #10 0x7f69816ac609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f6982b68293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f6974f5b700 (LWP 1200)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55aa71a2e688) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55aa71a2e638, cond=0x55aa71a2e660) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55aa71a2e660, mutex=0x55aa71a2e638) at pthread_cond_wait.c:638 #3 0x7f69753485eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f69753481eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f69816ac609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6982b68293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f6977fff700 (LWP 1199)): #0 __GI___libc_read (nbytes=16, buf=0x7f6977ffe9a0, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7f6977ffe9a0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f6980c7fb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6980c36ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6980c37312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6980c374a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6983129a0b in QEventDispatcherGlib::processEvents (this=0x7f697b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f69830cdc9b in QEventLoop::exec (this=this@entry=0x7f6977ffebb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7f6982ee7362 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7f6984181f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f6982ee8543 in QThreadPrivate::start (arg=0x7f6984205d80) at thread/qthread_unix.cpp:331 #11 0x7f69816ac609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f6982b68293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f697e103600 (LWP 1197)): [KCrash Handler] #4 QString::QString (other=..., this=0x7ffedb455c18) at ../../include/QtCore/../../src/corelib/text/qstring.h:1093 #5 QWidgetLineControl::text (this=0x0) at ../../include/QtWidgets/5.15.3/QtWidgets/private/../../../../../src/widgets/widgets/qwidgetlinecontrol_p.h:241 #6 QLineEdit::text (this=) at widgets/qlineedit.cpp:312
[kmail2] [Bug 447881] Replied HTML e-mail
https://bugs.kde.org/show_bug.cgi?id=447881 Daniel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Daniel --- *** This bug has been marked as a duplicate of bug 368394 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368394] Outlook replies double-spaced paragraphs
https://bugs.kde.org/show_bug.cgi?id=368394 Daniel changed: What|Removed |Added CC||lui...@gmail.com --- Comment #23 from Daniel --- *** Bug 447881 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 450932] New: Needs a reset option
https://bugs.kde.org/show_bug.cgi?id=450932 Bug ID: 450932 Summary: Needs a reset option Product: KScreen Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plasma Applet Assignee: kscreen-bugs-n...@kde.org Reporter: d.bergl...@mailbox.org Target Milestone: --- Hi. I had some display issues on a 3 display setup. I trouble shooted this issue by trying different combinations of displays, DP and HDMI outputs, cables etc. This lead to strange issues as KDE built up different configurations. At some point, one combination would keep one or two displays from turning on, depending on the combi. Another combination would restrict one of the screens from going higher than 800x600 resolution. I fixed all of these issues by removing the ~/.local/share/kscreen folder and rebooting. I am guessing that this is a symptom of KDE's ability to remember different screen layouts, which is fine. It took a lot of different combination attempts on my part to produce this issue. I also knew with a certainty what was the cause of this issue, but had to do some online search to locate the config folder in order to delete it. If this issue occurred to a user with limited knowledge, they would properly not be able to fix this without a re-install. Maybe there should be something in settings to reset all of the saved display configurations? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450629] Window geometry is no longer displayed when moving or resizing, and cannot be enabled anymore.
https://bugs.kde.org/show_bug.cgi?id=450629 Daniel Kraus changed: What|Removed |Added CC||boven...@bovender.de --- Comment #6 from Daniel Kraus --- I'm missing this feature on X11 very dearly as well. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 450719] New: "Scrolling snapshots" similar like on iOS, Android
https://bugs.kde.org/show_bug.cgi?id=450719 Bug ID: 450719 Summary: "Scrolling snapshots" similar like on iOS, Android Product: Spectacle Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: daniel-other+kde...@dadosch.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY Scrolling snapshots are a common way on modern phones as well as on Windows (with 3rd party software) for capturing parts of a window which can be scrolled. For this, a long stitched-together image is created. You can see it in action on a iPhone here: https://www.youtube.com/watch?v=M9hGEu4iQ9g "shutter" presumably supported this in some earlier version, but doesn't anymore. Also, there doesn't seem to be any alternative scrolling snapshot tool for Linux, so it would be nice to have. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449857] Lock screen password field not focused by default
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #40 from Daniel --- (In reply to Nate Graham from comment #39) > Would you mind making taking a shakycam phone video that shows the issue > happening, as well as what your hands are doing on the keyboard and > mouse/touchpad? I'd really appreciate that and I think it might shed some > light on the issue. Well, there you go: https://www.youtube.com/watch?v=Pp6TYMuEPUI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449857] Lock screen password field not focused by default
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #38 from Daniel --- (In reply to Nate Graham from comment #37) > So I'd like to ask folks if they are still seeing it with 5.24.1. Just tried, it still happens to me with 5.24.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450582] Some change between 5.24.0 and 5.24.1 broke windows shutter feature
https://bugs.kde.org/show_bug.cgi?id=450582 --- Comment #3 from Daniel Bruckner --- In German it's called "Fensterheber" Am 21.02.22 um 13:16 schrieb Vlad Zahorodnii: > https://bugs.kde.org/show_bug.cgi?id=450582 > > --- Comment #2 from Vlad Zahorodnii --- > What's window shutter? > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450641] New: Windows shutter - Fensterheber
https://bugs.kde.org/show_bug.cgi?id=450641 Bug ID: 450641 Summary: Windows shutter - Fensterheber Product: kwin Version: 5.24.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: dbruck...@posteo.de Target Milestone: --- Created attachment 146994 --> https://bugs.kde.org/attachment.cgi?id=146994=edit Window after resizeing After update to Plasma 5.24.1 the window shutter (Fensterheber) doesn't work anymore *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Window shutter (Fensterheber) with mouse wheel works as usual by retracting. By opening the window again the horizontal size is as it should be. The vertical size is shaped on the minimum (s. screenshot) STEPS TO REPRODUCE 1. shutter the window with mouse wheel works 2. resize window with mouse wheel don't work 3. OBSERVED RESULT Window don't open properly EXPECTED RESULT Reopening the window should restore the window in the previous size SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 450418] New: Duplicate templates on the home screen.
https://bugs.kde.org/show_bug.cgi?id=450418 Bug ID: 450418 Summary: Duplicate templates on the home screen. Product: calligrawords Version: 3.2.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: danielcristo...@gmail.com Target Milestone: --- Created attachment 146844 --> https://bugs.kde.org/attachment.cgi?id=146844=edit Screen where the error occurs. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. When starting the program. OBSERVED RESULT Document templates appear duplicated. EXPECTED RESULT Only one type of each template will appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.24 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION This failure happened on a clean install of KDE Neon. Even removing and re-installing the duplicate templates still persist. This did not happen in other Calligra applications. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449857] Lock screen password field not focused by default
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #35 from Daniel --- So, I made a quick video (sorry for the poor quality, screen recording did not work while unplugging a screen and I don't have the most steadiest hands): https://youtu.be/wn6hZh9GrLY You can see the lockscreen first correctly has the focus for the password input (I moved the mouse cursor so you can see it). Then I unplug the screens. Then I move the mouse cursor to show the UI again, but the bug would also happen without this step. Then I press some keys, the password input is not focused. Then I click into the password input, now everything works correctly. Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449857] Lock screen password field not focused by default
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #21 from Daniel --- (In reply to Nate Graham from comment #19) > For people experiencing this, do you have multiple monitors, or just one? Three: unplugging two, so that only one remains. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449857] Lock screen password field not focused by default
https://bugs.kde.org/show_bug.cgi?id=449857 Daniel changed: What|Removed |Added CC||daniel-other+kdebug@dadosch ||.de --- Comment #18 from Daniel --- This happens to me when a screen is removed. You then have to focus the passwort input box to be able to input the password. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 450123] New: Please add ability to crop images after scan
https://bugs.kde.org/show_bug.cgi?id=450123 Bug ID: 450123 Summary: Please add ability to crop images after scan Product: Skanpage Version: 1.0.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: alleyoops...@gmail.com Target Milestone: --- Hi, Really great to get a decent scanning app for KDE. This has a better layout and the missing features that I found lacking in Skanlite. Please include the ability to crop images in program. Kind regards, Daniel -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 348688] Hyper key getting recognized as a Meta/Win key
https://bugs.kde.org/show_bug.cgi?id=348688 Daniel changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||k...@istiophorus.org --- Comment #3 from Daniel --- Still present in Plasma 5.24.0/KF 5.90 and Qt 5.15.2. Hyper Key is also not usable for shortcuts (if bound to Caps Lock, see 222189) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 222189] SystemSettings crashed while editing Input Actions / KMix crashes when editing global shortcuts [QVariant, QDBusPendingReply, KGlobalAccel::isGlobalShortcutAvailable, KKeySequen
https://bugs.kde.org/show_bug.cgi?id=222189 Daniel changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- CC||k...@istiophorus.org Ever confirmed|0 |1 --- Comment #17 from Daniel --- (In reply to Mosin from comment #16) > The issue with hyper has been happening to me for a long time on multiple > systems… Same for me. I am using a custom symbols-file in /usr/share/X11/xkb/symbols/ based on the us intl layout which is working as expected but in Plasma. I put the Hyper_L symbol to all eight levels of caps lock. It automatically works the same as Meta (aka Super, not Alt!) does but adding new shortcuts does not work. The systemsettings do not crash but the input breaks after hitting the capslock-key and saves to the `~/.config/kglobalshortcutsrc` look like > switch-to-activity-4e86aa4e-0a7c-4a4b-82b8-c6298a5a46f9=ៀ?,none,Switch to > activity This shortcut does not work (and should not as the Meta-Behaviour is copied and opens the application dashboard) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 Daniel Eckl changed: What|Removed |Added CC||daniel.e...@gmx.de --- Comment #10 from Daniel Eckl --- I see the same issue, but my system already uses egl-wayland 1.1.7 Kubuntu 21.10 egl-wayland 1.1.7 Plasma 5.23.5 (Backports PPA) QT 5.15.2 Are there more triggers for this bug but egl-wayland? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 449254] New: KCM: Advanced Power Settings: Order of input elements wrong when cycling through with TAB key
https://bugs.kde.org/show_bug.cgi?id=449254 Bug ID: 449254 Summary: KCM: Advanced Power Settings: Order of input elements wrong when cycling through with TAB key Product: Powerdevil Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: daniel-other+kde...@dadosch.de Target Milestone: --- SUMMARY Order of input elements wrong when cycling through with TAB key in KCM "Advanced Power Settings" STEPS TO REPRODUCE 1. Open powerdevil's kcm, go to "Advanced Power settings". 2. Focus the first input field, to enter a number. 3. Press tab multiple times. OBSERVED RESULT The order is the following: low level -> critical level-> at critical level -> low level for peripheral devices -> start charging once below -> pause media players -> configure notifications -> stop charging at EXPECTED RESULT The order should be like the input elements are layout out from top to bottom: low level -> critical level-> at critical level -> low level for peripheral devices -> start charging once below -> stop charging at -> pause media players -> configure notifications -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449240] New: Can't download any theme from settings
https://bugs.kde.org/show_bug.cgi?id=449240 Bug ID: 449240 Summary: Can't download any theme from settings Product: systemsettings Version: 5.23.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: dbruck...@posteo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Settings Globale Themes - Download new Theme 2. Error: "Installation von /tmp/novGsS-Red-pastel.tar.gz fehlgeschlagen: Die Abhängigkeit kann nicht installiert werden: kns://colorschemes.knsrc/api.kde-look.org/169" 3. OBSERVED RESULT Installation von /tmp/novGsS-Red-pastel.tar.gz fehlgeschlagen: Die Abhängigkeit kann nicht installiert werden: kns://colorschemes.knsrc/api.kde-look.org/169 EXPECTED RESULT The new Themes should be downloaded SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.23 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430082] Handle information of folders with (only) hidden files differently
https://bugs.kde.org/show_bug.cgi?id=430082 Daniel changed: What|Removed |Added CC||daniel-other+kdebug@dadosch ||.de --- Comment #1 from Daniel --- Created attachment 145869 --> https://bugs.kde.org/attachment.cgi?id=145869=edit The info box used in kcm for compositor Would support this. It can easily happen (if you disabled the display of hidden files) that you might think a folder is empty and can be deleted, if though it isn't. It would also be helpful if you select 'all' (only non-hidden, displayed) files to copy them somewhere, but indeed not all files are copied. Visually, the info box which is used in the kcm for compositor could be used. It isn't too obstructive, but also can not be overlooked. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 439984] Cannot import data to kaddressbook
https://bugs.kde.org/show_bug.cgi?id=439984 Daniel Kraus changed: What|Removed |Added CC||boven...@bovender.de --- Comment #3 from Daniel Kraus --- Confirmed. In fact, I am unable to import or export anything. The context menus also don't work. Furthermore, adding an addressbook from a VCard file (File > New > Add address book > VCard file) does add a new addressbook, but that addressbook remains empty. Drag and drop does not work either. My contacts seem to be locked into KAddressbook. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416462] fuzzy search doesn't find photo which is rotated
https://bugs.kde.org/show_bug.cgi?id=416462 --- Comment #8 from Daniel --- Hi all, so I think they are 2 different cases here (both could theoretically be solved by the same solution, but probably shouldn't), and I don't think the solution (at least for similar pictures, as written at the end) needs to be complicated (maybe I'm naive). A) The image is already correctly oriented before importing, using a set exif orientation flag. If the image is imported (and autorotate is enabled), this flag gets removed and the images is fully rotated (that's my understanding). The solution to this would be to read the orientation flag when doing the fuzzy search. Before running the hash algorith on it, the pictures need to be rotated according the flag. This should be almost trivial. B) The image is rotated after it has been imported, different to the original orientation. The solution to this could be to search the hashes for all 4 (let's ignore mirrors for now) orientations of the search query picture. I don't think this would be difficult or slow (as to my experience the search algorithm is very fast/instant). This could be extended to only search for additional orientations, if no result is found. If it is technically not possible, maybe someone can explain to me why :) Ok, this would have one major drawback: It could only find similar pictures, not duplicate entries. But if you assume all images are correctly rotated in the digikam collection, finding duplicates wouldn't be a problem anymore… Daniel -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416462] fuzzy search doesn't find photo which is rotated
https://bugs.kde.org/show_bug.cgi?id=416462 --- Comment #5 from Daniel --- (In reply to caulier.gilles from comment #4) Hi Gilles, a happy new year too :) > Can you check if problem remain with digiKam 7.5.0 pre-release bundle I just checked and the problem still persists. To be a more verbose: If a image A.jpeg is imported which has exif orientation set (for example Orientation : Rotate 90 CW), digikam will rotate it and adapt the file (and lets say save it to B.jpeg). If you search with the original image A.jpeg (not touched by digikam) in the fuzzy search, the imported image (B.jpeg) is not found. So I think the main issue is that the orientation flag isn't adhered to when searching using fuzzy search. (Supported by the fact that the orientation of the image preview in the fuzzy search box of A.jpeg is wrong (just horizontal)) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 448199] Settings for screenshot annotations should be saved
https://bugs.kde.org/show_bug.cgi?id=448199 Daniel Weisser changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #4 from Daniel Weisser --- Thanks for the hint. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 448199] Settings for screenshot annotations should be saved
https://bugs.kde.org/show_bug.cgi?id=448199 Daniel Weisser changed: What|Removed |Added Platform|Other |Manjaro Version|unspecified |21.12.0 --- Comment #2 from Daniel Weisser --- (In reply to Yerrey Dev from comment #1) > On my system the settings are remembered (Version 22.03.70). For me (Version 21.12.0) that doesn't work - I have to reapply the settings every time Spectacle is reopened. Where did you get version 22.03.70 from? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 448199] Settings for screenshot annotations should be saved
https://bugs.kde.org/show_bug.cgi?id=448199 Daniel Weisser changed: What|Removed |Added CC||daniel.weis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 448199] New: Settings for screenshot annotations should be saved
https://bugs.kde.org/show_bug.cgi?id=448199 Bug ID: 448199 Summary: Settings for screenshot annotations should be saved Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: daniel.weis...@gmail.com CC: k...@david-redondo.de Target Milestone: --- When changing settings in the annotation editor of spectacle it would be nice, if the changed settings (e.g. used color, rectangle without fill) are saved and reused for the next annotation process. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 447881] New: Replied HTML e-mail
https://bugs.kde.org/show_bug.cgi?id=447881 Bug ID: 447881 Summary: Replied HTML e-mail Product: kmail2 Version: 5.15.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: lui...@gmail.com Target Milestone: --- Created attachment 145077 --> https://bugs.kde.org/attachment.cgi?id=145077=edit Example of original and replied e-mail SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open an HTML e-mail with template cursor on top and ending with %TEXT 2. Write the e-mail content without changing anything on original HTML 3. Check that the composer content is visually OK and then send the e-mail 4. Check the received e-mail that is had its HTML modified OBSERVED RESULT The sent e-mail visual content differs from what was been showed on composer, even the original HTML that got some bordered tables on olders signatures and other parts of the content. If sent e-mail is sent as text instead of HTML, original e-mail is also changed, for example, all images changes to somthing like [cid:image20c6be.PNG@dff82cd8.4ebe199b], not as a code, but as visual text EXPECTED RESULT At least the unmodified original HTML content from previous e-mail should not be changed, especially if it were left untouched SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447455] Blocks processes producing too much output when window not in active tty
https://bugs.kde.org/show_bug.cgi?id=447455 --- Comment #1 from Daniel Dawson --- Correction: kernel version is 5.15.10-gentoo. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447455] New: Blocks processes producing too much output when window not in active tty
https://bugs.kde.org/show_bug.cgi?id=447455 Bug ID: 447455 Summary: Blocks processes producing too much output when window not in active tty Product: konsole Version: 21.12.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: danielcdaw...@gmail.com Target Milestone: --- SUMMARY If I switch to a different tty from the one a Konsole window is on, I find that any child processes producing output get blocked after a certain amount is produced. STEPS TO REPRODUCE 1. Login on a virtual console (e.g. tty1). 2. Prepare a way to get output from a process. The way I did this was: $ mknod /tmp/test.pipe p $ cat /tmp/test.pipe 3. Start a graphical session, or switch back to one. 4. Start a terminal emulator, such as Konsole, and do something in it that both produces output on stdout, and sends it to the VC: $ for ((i=0;;i++)); do echo $i; sleep 0.005; done | tee /tmp/test.pipe # sleep is optional, but recommended. 5. Switch back to the VC, and watch the output. OBSERVED RESULT When using Konsole, after a couple thousand lines, the output pauses. Only once I switch back to the graphical session, does output continue. I tried this also with xterm and LXTerminal (since they happen to be installed), and this behavior does not occur with them (unless their buffers are just really huge). EXPECTED RESULT Not being in the active tty should, I believe, not affect child processes simply because of their terminal output. This is a problem if running an application under Konsole that's doing something important while writing to stderr/stdout. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.0-gentoo (64-bit) [custom config] (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION A workaround seems to be to run things that need to avoid being blocked under something like screen or tmux, since they take over as the controlling terminal, and keep running even if their front-end disappears. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447442] New: Plasma Widgets Do Not Keep Their Position and Size
https://bugs.kde.org/show_bug.cgi?id=447442 Bug ID: 447442 Summary: Plasma Widgets Do Not Keep Their Position and Size Product: plasmashell Version: 5.23.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: dboa...@posteo.net Target Milestone: 1.0 Created attachment 144815 --> https://bugs.kde.org/attachment.cgi?id=144815=edit Positions and sizes before and after computer restart SUMMARY Dear KDE Developers, I have noticed that several plasma widgets change their sizes and positions when I restart the machine. I have two monitors; all widgets are in one of them. I have attached a PDF showing the disposition and size of the widgets before and after a full restart. STEPS TO REPRODUCE 1. Arrange your widgets in the position and size you prefer 2. Restart the machine OBSERVED RESULT * All the widgets are in slight different positions, but the sizes change a lot EXPECTED RESULT * All widgets should retain their positions and sizes SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux (KDE Version) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel: 5.13.19-2 64 bits -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 447052] heratic operation of the "search results" function
https://bugs.kde.org/show_bug.cgi?id=447052 --- Comment #4 from daniel --- hello toni it worked great, thank you very much. But I cannot change the language to French. The only option is English. Best regards. Daniel I put in fixed Le 18/12/2021 à 19:59, Toni Asensi Esteve a écrit : > https://bugs.kde.org/show_bug.cgi?id=447052 > > Toni Asensi Esteve changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > CC||toni.ase...@kdemail.net > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Toni Asensi Esteve --- > Hello. The problem does not happen to me using the git version of Krusader, > which had some fixes about a similar problem. Can you follow the steps of > https://commits.kde.org/krusader?path=INSTALL > in order to build the git version of Krusader and tell us if your problem is > solved? > -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 447052] heratic operation of the "search results" function
https://bugs.kde.org/show_bug.cgi?id=447052 --- Comment #3 from daniel --- hello toni it worked great, thank you very much. But I cannot change the language to French. The only option is English. Best regards. Daniel I put in fixed Le 18/12/2021 à 19:59, Toni Asensi Esteve a écrit : > https://bugs.kde.org/show_bug.cgi?id=447052 > > Toni Asensi Esteve changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > CC||toni.ase...@kdemail.net > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Toni Asensi Esteve --- > Hello. The problem does not happen to me using the git version of Krusader, > which had some fixes about a similar problem. Can you follow the steps of > https://commits.kde.org/krusader?path=INSTALL > in order to build the git version of Krusader and tell us if your problem is > solved? > -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 447052] heratic operation of the "search results" function
https://bugs.kde.org/show_bug.cgi?id=447052 daniel changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from daniel --- hello toni it worked great, thank you very much. But I cannot change the language to French. The only option is English. Best regards. Daniel -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 447052] New: heratic operation of the "search results" function
https://bugs.kde.org/show_bug.cgi?id=447052 Bug ID: 447052 Summary: heratic operation of the "search results" function Product: krusader Version: 2.7.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: krusader-bugs-n...@kde.org Reporter: antime...@free.fr CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY heratic operation of the "search results" function *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Hello everyone I am looking for a file name or a file containing a word (for example "daddy") The result window opens. I can choose to open, edit or copy it to the clipboard. A double click on the name of the file found opens the file a few times, but most of the results window closes without any action. Cordial greetings STEPS TO REPRODUCE 1) I click on the magnifying glass icon of the menu The result window opens. I can choose to open, edit or copy it to the clipboard. 2) I double click on the name of a file found 3) the file is sometimes opened, but most of the results window closes without any action. Cordial greetings OBSERVED RESULT the file is sometimes opened EXPECTED RESULT most of the results window closes without any action. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.7 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION 2xAMD Athlon II X2 250 5.8GO -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428778] Microphone tray applet's icon not updated unless all mics are muted--not just the current one
https://bugs.kde.org/show_bug.cgi?id=428778 --- Comment #9 from Daniel --- Created attachment 144491 --> https://bugs.kde.org/attachment.cgi?id=144491=edit speaker mute icon shown in plasma 5.24.4, but not all speakers are muted -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428778] Microphone tray applet's icon not updated unless all mics are muted--not just the current one
https://bugs.kde.org/show_bug.cgi?id=428778 --- Comment #8 from Daniel --- (In reply to Oded Arbel from comment #7) > Ok, then I definitely could not reproduce a problem :-) Sorry, it is late and I'm tired :-) Comment #4 is important for reproducing it: Now that I think about it, the bug is originally about unmuted, **inactive devices** which cause the 0-vol icon beeing shown. (I just reproduced this bug on Plasma 5.23.4. btw) > If you have multiple output devices and only one of them is muted, the > speaker icon still doesn't show a mute icon. At least on Plasma 5.23.4 this is not the case, the mute icon is indeed shown (see attachment I just added). On the general behaviour of the icon after scrolling to zero volume: Showing zero vol. icon = bad: you can't see at quick glance that mic is muted (which is important) Showing mute icon = good: you can quickly see that mic is muted; bad: but not all mics might be muted (which is important to know too) Showing mute icon + muting all mics (equivalent to clicking on mic icon itself) = good: you can quickly see all mics are muted. Also I want to note that even if the 0% vol icon is shown, the "hud" volume info which appears in the center of the screen tells that the mic has been muted together with a muted icon. > that lowering the volume on one device to 0% mutes all others automatically > (which not lowering their volume?) I think is a bad UX and doesn't allow for > the use case of actually wanting one device muted but not others. This use case could still be done by opening the volume applet and adjusting it there. I'm talking about the volume control using scrolling above the tray icons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428778] Microphone tray applet's icon not updated unless all mics are muted--not just the current one
https://bugs.kde.org/show_bug.cgi?id=428778 --- Comment #6 from Daniel --- (In reply to Oded Arbel from comment #5) > with more than one microphone > connected and not muted, scrolling on the microphone icon in the system tray > (changing the volume of the first microphone) does not cause the microphone > icon to show the muted icon. So you reproduced it :) > 3. Mute microphone by scrolling on the mic icon. > OBSERVED RESULT > The mic tray icon shows 0% volume. > EXPECTED RESULT > It should show the muted-mic icon instead. I think the same behaviour as with the speakers should be done: muting to 0% should show the mute icon (and mute all microphones, different from speaker behaviour). Having a zero percent icon is very confusing as its unclear wether the mic is on or off. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 431020] kdeconnect-sms crashes when accessing a group SMS chat
https://bugs.kde.org/show_bug.cgi?id=431020 Daniel Morgan changed: What|Removed |Added CC||danielmor...@disroot.org Platform|Archlinux Packages |Manjaro --- Comment #1 from Daniel Morgan --- I get a similar segfault every time I try to use kdeconnect-sms to access a conversation that includes an MMS. Group messages are often sent as MMS messages, so this might be the same bug. I'm doing this on kdeconnect-sms 21.08.3 on Manjaro on my computer, and version 1.18.1 on LineageOS 18.1 on my phone. (In reply to J.S. Ling from comment #0) > SUMMARY > kdeconnect-sms works as expected for two party messaging. Attempts to > interact with a group SMS chat (4 members) produce a segmentation fault and > kdeconnect-sms will crash. > > STEPS TO REPRODUCE > 1. Select SMS Messages from the menu > 2. Select a group conversation to interact with > 3. Attempt to interact through the group SMS chat > > OBSERVED RESULT > kdeconnect-sms will invariably seg fault > > EXPECTED RESULT > kdeconnect-sms will allow browsing and replies to a group SMS message chat > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: Arch Linux > (available in About System) > KDE Plasma Version: 5.20.4 > KDE Frameworks Version: 5.77.0 > Qt Version: 5.15.2 > > ADDITIONAL INFORMATION > Thread 1 "kdeconnect-sms" received signal SIGSEGV, Segmentation fault. > 0x55569e85 in ?? () > (gdb) backtrace > #0 0x55569e85 in ?? () > #1 0x5556a8ed in ?? () > #2 0x7643de10 in ?? () from /usr/lib/libQt5Core.so.5 > #3 0x77f84ba1 in ?? () from /usr/lib/libkdeconnectinterfaces.so.20 > #4 0x77f85063 in ?? () from /usr/lib/libkdeconnectinterfaces.so.20 > #5 0x771f4066 in ?? () from /usr/lib/libQt5DBus.so.5 > #6 0x76433582 in QObject::event(QEvent*) () from > /usr/lib/libQt5Core.so.5 > #7 0x773b3752 in QApplicationPrivate::notify_helper(QObject*, > QEvent*) () >from /usr/lib/libQt5Widgets.so.5 > #8 0x76406a7a in QCoreApplication::notifyInternal2(QObject*, > QEvent*) () >from /usr/lib/libQt5Core.so.5 > #9 0x76409573 in > QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () > from /usr/lib/libQt5Core.so.5 > #10 0x764600a4 in ?? () from /usr/lib/libQt5Core.so.5 > #11 0x74e47a84 in g_main_context_dispatch () from > /usr/lib/libglib-2.0.so.0 > #12 0x74e9b9b1 in ?? () from /usr/lib/libglib-2.0.so.0 > #13 0x74e462b1 in g_main_context_iteration () from > /usr/lib/libglib-2.0.so.0 > #14 0x7645f6e1 in > QEventDispatcherGlib::processEvents(QFlags) > () from /usr/lib/libQt5Core.so.5 > #15 0x764053fc in > QEventLoop::exec(QFlags) () >from /usr/lib/libQt5Core.so.5 > #16 0x7640d894 in QCoreApplication::exec() () from > /usr/lib/libQt5Core.so.5 > #17 0x5556014e in ?? () > #18 0x75dd1152 in __libc_start_main () from /usr/lib/libc.so.6 > #19 0x5556062e in _start () -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 446555] System Settings crashes upon launch when qml-module-org-kde-sonnet is not installed
https://bugs.kde.org/show_bug.cgi?id=446555 Daniel Kraus changed: What|Removed |Added CC||boven...@bovender.de --- Comment #30 from Daniel Kraus --- *** Bug 446638 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446638] Plasma shell crashes when attempting to open the calendar widget's settings
https://bugs.kde.org/show_bug.cgi?id=446638 Daniel Kraus changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Daniel Kraus --- *** This bug has been marked as a duplicate of bug 446555 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446638] Plasma shell crashes when attempting to open the calendar widget's settings
https://bugs.kde.org/show_bug.cgi?id=446638 --- Comment #3 from Daniel Kraus --- Yes, definitively. I installed qml-module-org-kde-sonnet, and it immediately (without restart or anything) no longer crashes Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446638] Plasma shell crashes when attempting to open the calendar widget's settings
https://bugs.kde.org/show_bug.cgi?id=446638 --- Comment #1 from Daniel Kraus --- Created attachment 144319 --> https://bugs.kde.org/attachment.cgi?id=144319=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446638] New: Plasma shell crashes when attempting to open the calendar widget's settings
https://bugs.kde.org/show_bug.cgi?id=446638 Bug ID: 446638 Summary: Plasma shell crashes when attempting to open the calendar widget's settings Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: boven...@bovender.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.4) Qt Version: 5.15.3 Frameworks Version: 5.88.0 Operating System: Linux 5.11.0-41-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Recently, whenever I attempt to change the settings of the calendar widget, Plasma shell crashes. This happens whenever I click on the settings icon. The calendar widget itself seems to work well (except that it forgot which PIM calendars I want to see, which is why I would like to change the settings). The crash can be reproduced every time. -- Backtrace (Reduced): #4 0x7f8bdb290d22 in QV4::QQmlTypeWrapper::virtualInstanceOf(QV4::Object const*, QV4::Value const&) (typeObject=0x7ffe85ad1ab0, var=...) at qml/qqmltypewrapper.cpp:423 #5 0x7f8bdb158248 in QV4::Object::instanceOf(QV4::Value const&) const (var=..., this=0x7ffe85ad1ab0) at ../../include/QtQml/5.15.3/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:73 #6 QV4::Runtime::Instanceof::call(QV4::ExecutionEngine*, QV4::Value const&, QV4::Value const&) (engine=0x55ed5efe3d80, lval=..., rval=...) at jsruntime/qv4runtime.cpp:387 #7 0x7f8bdb1459e0 in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) (frame=0x7ffe85ad1b90, engine=0x55ed5efe3d80, code=0x7f8ba2f38a1b "L\020/\276") at jsruntime/qv4vme_moth.cpp:351 #8 0x7f8bdb14911f in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) (frame=frame@entry=0x7ffe85ad1b90, engine=engine@entry=0x55ed5efe3d80) at jsruntime/qv4vme_moth.cpp:463 Possible duplicates by query: bug 445493. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444780] Language KCM has message about "Install Missing Packages button" that does not seem to exist
https://bugs.kde.org/show_bug.cgi?id=444780 Daniel Mader changed: What|Removed |Added CC||hpqi1w...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444780] Language KCM has message about "Install Missing Packages button" that does not seem to exist
https://bugs.kde.org/show_bug.cgi?id=444780 Daniel Mader changed: What|Removed |Added CC|danielstefanmader@googlemai | |l.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444780] Language KCM has message about "Install Missing Packages button" that does not seem to exist
https://bugs.kde.org/show_bug.cgi?id=444780 Daniel Mader changed: What|Removed |Added CC||danielstefanmader@googlemai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446418] New: Kdenlive playback locks to clip view only
https://bugs.kde.org/show_bug.cgi?id=446418 Bug ID: 446418 Summary: Kdenlive playback locks to clip view only Product: kdenlive Version: 21.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: dan...@danielrosehill.co.il Target Milestone: --- SUMMARY *** I keep a clip monitor view and a project monitor view on my default view in Kdenlive. Since upgrading to the latest version of Kdenlive I've encountered a bug. When I add some clips to my timeline and hit the spacebar, to play the project, the program plays the last selected clip in the clip monitor view instead. I cannot force the project monitor to playback a preview of the project even by manually clicking on its play icon. The only way to resolve this bug is by restarting the program. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 20.10 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 446404] parser sometimes ignores custom parser options
https://bugs.kde.org/show_bug.cgi?id=446404
Daniel Santos changed:
What|Removed |Added
CC||daniel.san...@pobox.com
--- Comment #3 from Daniel Santos ---
Created attachment 144169
--> https://bugs.kde.org/attachment.cgi?id=144169=edit
very ugly patch
WARNING: very ugly patch ahead! I am in NO WAY suggesting this for merging!
I think some of this might be useful, namely not adding -nostdinc and
-nostdinc++ if it's already supplied in the arguments, but mostly not adding
the system include paths in such a case. Also, not overriding
-working-directory if already in custom parser options.
But if there's a cleaner, prettier way of using the root project's parser
settings (or nearest sub-directory) when the file is filtered, then that would
be helpful upstream.
+for (auto project : projects) {
+const auto root = project->path().path();
+if (!url.str().startsWith(root))
+continue;
+// Do something nice here
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 444009] Applications can be triggered by clicking in the top left corner of the screen on Wayland
https://bugs.kde.org/show_bug.cgi?id=444009 Daniel changed: What|Removed |Added CC||danielg...@protonmail.com --- Comment #3 from Daniel --- I am also having this issue on wayland. Also hovering on desktop in top left corner will show name of the first application in systray. Top left corner works like "mouse portal" to first application in systray. Also noticed when I have steam maximzed and on top of the steam have another application maximized it will click through your application to steam instead of first application in systray. This is very annoying with firefox because when I want to click on first tab I sometimes click to this top left corner it will focus steam(when maximized under firefox) or first application in systray -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 446404] parser sometimes ignores custom parser options
https://bugs.kde.org/show_bug.cgi?id=446404 --- Comment #2 from Daniel Santos --- So I believe this is happening because the file is in a subdirectory that is filtered: [Filters][64] inclusive=0 pattern=/drivers/staging targets=2 Some may call this a user error, but I can't afford to have the entire kernel parsed, but if I need to open a file in my filter, I can't have it mis-parsed. So for the sake of parse jobs, can we modify findProjectFileItem() so that if project->filesForPath(url) fails to find a match, we can still look for a project who's root contains the path of the file? This would solve my problem without forcing me to parse the entire kernel -- since that usually results in KDevelop crashing anyway. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 446404] parser sometimes ignores custom parser options
https://bugs.kde.org/show_bug.cgi?id=446404
--- Comment #1 from Daniel Santos ---
This appears to be the source of the problem, at
plugins/clang/clangparsejob.cpp:175:
if (auto file = findProjectFileItem(tuUrl, )) {
This is failing when it should not, as this file belongs to the project:
(gdb) p url.c_str()
$2 = 0x561feb45
"/home/daniel/proj/embedded/openwrt/linux-5.4.143/drivers/staging/mt7621-pinctrl/pinctrl-rt2880.c"
(gdb) p hasBuildSystemInfo
$3 = false
In the below backtrace, I added a little debug spew:
--- a/plugins/clang/clangparsejob.cpp
+++ b/plugins/clang/clangparsejob.cpp
@@ -177,6 +177,8 @@ ClangParseJob::ClangParseJob(const IndexedString& url,
ILanguageSupport* languag
m_environment.addFrameworkDirectories(IDefinesAndIncludesManager::manager()->frameworkDirectories(file));
m_environment.addDefines(IDefinesAndIncludesManager::manager()->defines(file));
m_environment.setParserSettings(ClangSettingsManager::self()->parserSettings(file));
+auto const = m_environment.parserSettings();
+std::cout << " " << ps << std::endl;
if (hasBuildSystemInfo) {
// Assume the builder invokes the compiler in the build directory.
m_environment.setWorkingDirectory(file->project()->buildSystemManager()->buildDirectory(file));
@@ -186,6 +188,8 @@ ClangParseJob::ClangParseJob(const IndexedString& url,
ILanguageSupport* languag
m_environment.addFrameworkDirectories(IDefinesAndIncludesManager::manager()->frameworkDirectories(tuUrl.str()));
m_environment.addDefines(IDefinesAndIncludesManager::manager()->defines(tuUrl.str()));
m_environment.setParserSettings(ClangSettingsManager::self()->parserSettings(tuUrl.str()));
+auto ps = m_environment.parserSettings();
+std::cout << " " << ps << std::endl;
}
const bool isSource = ClangHelpers::isSource(tuUrl.str());
#0 ClangParseJob::ClangParseJob(KDevelop::IndexedString const&,
KDevelop::ILanguageSupport*)
(this=this@entry=0x57849f80, url=...,
languageSupport=languageSupport@entry=0x569f5138) at
../plugins/clang/clangparsejob.cpp:191
#1 0x7fff600e11fa in ClangSupport::createParseJob(KDevelop::IndexedString
const&) (this=0x569f5110, url=...) at ../plugins/clang/clangsupport.cpp:245
#2 0x74f75e14 in
KDevelop::BackgroundParserPrivate::createParseJob(KDevelop::IndexedString
const&, DocumentParsePlan const&) (this=this@entry=
0x55e72980, url=..., parsePlan=...) at
../kdevplatform/language/backgroundparser/backgroundparser.cpp:369
#3 0x74f7740e in
KDevelop::BackgroundParserPrivate::parseDocumentsInternal()
(this=this@entry=0x55e72980) at
../kdevplatform/language/backgroundparser/backgroundparser.cpp:309
#4 0x74f7270c in KDevelop::BackgroundParser::parseDocuments()
(this=0x55c2a9d0) at
../kdevplatform/language/backgroundparser/backgroundparser.cpp:679
#5 0x74f568cd in
KDevelop::BackgroundParser::qt_static_metacall(QObject*, QMetaObject::Call,
int, void**)
(_o=, _c=, _id=,
_a=0x7fff20017628) at
kdevplatform/language/KDevPlatformLanguage_autogen/7BZAXZBZPZ/moc_backgroundparser.cpp:249
#6 0x766038c6 in QObject::event(QEvent*) (this=0x55c2a9d0,
e=0x7fff200175e0)
at
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qobject.cpp:1314
#7 0x7722adaf in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55c2a9d0, e=0x7fff200175e0)
at
/usr/src/debug/dev-qt/qtwidgets-5.15.2-r11/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/widgets/kernel/qapplication.cpp:3632
#8 0x765d8008 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55c2a9d0, event=0x7fff200175e0)
at
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qcoreapplication.cpp:1064
#9 0x765db675 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55575950)
at
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qcoreapplication.cpp:1821
#10 0x7662a6d3 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=s@entry=0x555fd700)
at
/usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase-a4f9e56975fa6ab4a1f63a9b34a4d77b1cfe4acd/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#11 0x72c20065 in g_main_dispatch (context=0x7fffdc005000) at
../glib-2.68.4/glib/gmain.c:3337
#12 g_main_context_dispatch (context=0x7fffdc005000) at
../glib-2.68.4/glib/gmain.c:4055
#13 0x72c20408 in g_main_context_iterate
(context=context@entry=0x7fffdc005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=)
at ../glib-2.68.4/
[kdevelop] [Bug 446404] New: parser sometimes ignores custom parser options
https://bugs.kde.org/show_bug.cgi?id=446404 Bug ID: 446404 Summary: parser sometimes ignores custom parser options Product: kdevelop Version: 5.6.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: daniel.san...@pobox.com Target Milestone: --- SUMMARY 16 threads and the Linux kernel sources and I sometimes end up with #include referencing /usr/include/linux/modules.h. All parse jobs run by the background parser seem correct. But when I open a file (in the project) and it's scheduled for immediate parsing, BANG, I see the debug spew using the default arguments. This essential breaks KDevelop as a usable IDE for the Linux kernel sources, because I have to 'git grep' and use elixir.bootlin.com to look up types and functions, since KDevelop can't find them. STEPS TO REPRODUCE 1. KDEV_CLANG_DISPLAY_ARGS=1 KDEV_CLANG_DISPLAY_DIAGS=1 kdevelop 2. Open sources to Linux kernel 3. set custom C parser options based upon building the kernel and sucking out the arguments. In my particular case, I'm cross-compiling and these are my arguments: --target=mipsel-openwrt-linux -mno-check-zero-division -mabi=32 -mno-abicalls -msoft-float -march=mips32r2 -mtune=34kc -std=gnu89 -nostdinc -isystem /home/daniel/proj/embedded/openwrt/v21.02.y/staging_dir/toolchain-mipsel_24kc_gcc-10.2.0_musl/lib/gcc/mipsel-openwrt-linux-musl/10.2.0/include -Iarch/mips/include -Iarch/mips/include/generated -Iinclude -Iarch/mips/include/uapi -Iarch/mips/include/generated/uapi -Iinclude/uapi -Iinclude/generated/uapi -include include/linux/kconfig.h -include include/linux/compiler_types.h -Iarch/mips/include/asm/mach-ralink -Iarch/mips/include/asm/mach-ralink/mt7620 -Iarch/mips/include/asm/mach-generic -D__KERNEL__ -D__MIPSEL__ -DVMLINUX_LOAD_ADDRESS=0x8000 -DLINKER_LOAD_ADDRESS=0x8000 -DDATAOFFSET=0 -DGAS_HAS_SET_HARDFLOAT -DTOOLCHAIN_SUPPORTS_VIRT -DTOOLCHAIN_SUPPORTS_XPA -DTOOLCHAIN_SUPPORTS_CRC -DTOOLCHAIN_SUPPORTS_DSP -DTOOLCHAIN_SUPPORTS_GINV -ferror-limit=99 -fspell-checking -Wdocumentation -Wall -Wundef -Wno-trigraphs -Wno-format-security -Wno-frame-address -Wno-address-of-packed-member -Wframe-larger-than=1024 -Wimplicit-fallthrough -Wno-unused-const-variable -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-array-bounds -Wno-uninitialized -Wno-incompatible-library-redeclaration -Wno-unknown-warning-option -Wno-implicit-fallthrough -working-directory /home/daniel/proj/embedded/openwrt/linux-5.4.143 Actually, for this to even work, I had to hack kdvelop and stop it from inserting a -working-directory argument, but I can probably just change all of my include paths to absolute and not have that problem. 4. let it start parsing and notice it's correct 5. Open a file and notice that it's incorrect (it parsed with the default options). 6. If I allow all parsing to complete before opening any files, then they are correct until some point later after editing enough. I haven't seen it incorrectly parse a file after making changes (yet) only after initially opening it (before background parsing has completed). I don't know if this is a race or not. I'm on a 8/16 Ryzen and using 16 parsing threads and 500ms delay. I've tried digging into the KDevelop sources, and I got as as finding where the job is run and where the job is scheduled. Job run from: (gdb) bt #0 ParseSessionData::ParseSessionData (this=this@entry=0x7fff39085260, unsavedFiles=..., index=index@entry=0x569dbb70, environment=..., options=..., options@entry=...) at ../plugins/clang/duchain/parsesession.cpp:272 #1 0x7fff47b68213 in ClangParseJob::createSessionData (this=this@entry=0x57c10270) at /usr/src/debug/dev-util/kdevelop-5.6.2/kdevelop-5.6.2/plugins/clang/clangparsejob.cpp:394 #2 0x7fff47b69bcc in ClangParseJob::run (this=) at /usr/src/debug/dev-util/kdevelop-5.6.2/kdevelop-5.6.2/plugins/clang/clangparsejob.cpp:300 #3 0x72bb8f99 in ThreadWeaver::IdDecorator::run (this=, self=..., thread=0x56ac2350) at /usr/src/debug/kde-frameworks/threadweaver-5.85.0/threadweaver-5.85.0/src/iddecorator.cpp:50 #4 0x72bb9597 in ThreadWeaver::Executor::run (this=, job=..., thread=) at /usr/src/debug/kde-frameworks/threadweaver-5.85.0/threadweaver-5.85.0/src/executor.cpp:33 #5 0x72bb8580 in ThreadWeaver::Job::execute (this=, self=..., th=0x56ac2350) at /usr/src/debug/kde-frameworks/threadweaver-5.85.0/threadweaver-5.85.0/src/job.cpp:64 #6 0x72bb7d82 in ThreadWeaver::Thread::run (this=0x56ac2350) at /usr/src/debug/kde-frameworks/threadweaver-5.85.0/threadweaver-5.85.0/src/thread.cpp:98 #7 0x76420c56 in QThreadPrivate::start (arg=0x56ac2350) at /usr/src/debug/dev-qt/qtcore-5.15.2-r10/qtbase
[Discover] [Bug 446369] New: Trying to update a Flatpak always crashes Discover
https://bugs.kde.org/show_bug.cgi?id=446369 Bug ID: 446369 Summary: Trying to update a Flatpak always crashes Discover Product: Discover Version: 5.23.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: zi...@lyrion.ch CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- SUMMARY Trying to update one or more Flatpak applications crashes Discover. One of them will be updated, nonetheless, and on the next launch the remaining ones are still there to update. STEPS TO REPRODUCE 1. Open Discover 2. Go to the updates section 3. Click "Update" OBSERVED RESULT Discover updates one Flatpak, then crashes. EXPECTED RESULT Discover updates all Flatpaks and all other packages without crashing. Linux/KDE Plasma: 5.15.5-1 default (64-bit) (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The KDE crash assistant made a debug trace, but it discarded it when I chose to report the issue. So I don't have a trace to provide for now. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 446145] New: Operating Window 10 Pro and Marble won't open
https://bugs.kde.org/show_bug.cgi?id=446145 Bug ID: 446145 Summary: Operating Window 10 Pro and Marble won't open Product: marble Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: soldierofthek...@yahoo.com Target Milestone: --- Created attachment 143991 --> https://bugs.kde.org/attachment.cgi?id=143991=edit marble-qt.exe - System Error SUMMARY I have downloaded and reinstalled this product three times in an effort to get the pictures I saved to download and open. I get a notice that Marble isn't loaded properly and to reinstall the hardware which I do only to get the same notice. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 444833] Plasma crashes after login when user is switched in a certain way
https://bugs.kde.org/show_bug.cgi?id=444833 --- Comment #3 from Daniel --- (In reply to Nate Graham from comment #1) > Can you please attach a backtrace of the crash? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports I am a Linux Noob: If I understand correctly, I have to rebuild the pkg on manjaro with the debugging option. Which pkg do I have to rebuild and where is the report stored afterwards? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444132] Sometimes can't type in kickoff search box (on primary display) when mouse pointer is on secondary display
https://bugs.kde.org/show_bug.cgi?id=444132 Daniel changed: What|Removed |Added CC||dwoodfi...@outlook.com --- Comment #5 from Daniel --- I'm seeing that I just can't type in the menu on the secondary display no matter what until I click the search box. The primary menu works fine no matter where my mouse pointer is. Could this be related to Bug 443131? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445676] New: Shutdown computer after renderings option grayed out on Ubuntu with LXDE
https://bugs.kde.org/show_bug.cgi?id=445676 Bug ID: 445676 Summary: Shutdown computer after renderings option grayed out on Ubuntu with LXDE Product: kdenlive Version: 21.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: dan...@danielrosehill.co.il Target Milestone: --- SUMMARY *** Installed Kdenlive via the official PPA. Running on top of Ubuntu 20.10 with LXDE as the desktop environment. In Render, the "Shutdown computer after renderings" checkbox button is grayed out and cannot be enabled. *** STEPS TO REPRODUCE 1. Install LXDE on top of Ubuntu. Boot into LXDE as the DE from the session manager. 2. Access Kdenlive 3. Click the 'Render' button OBSERVED RESULT The 'Shutdown computer after renderings' button is grayed out. EXPECTED RESULT The user should have the ability to toggle on/off a switch entitled 'Shutdown computer after renderings' which will automatically power off the computer when the render queue is concluded. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 20.10. (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: N/A. Running LXDE. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 211416] Optimise kde performance on nfs
https://bugs.kde.org/show_bug.cgi?id=211416 Daniel Moyne changed: What|Removed |Added CC||daniel.mo...@free.fr --- Comment #24 from Daniel Moyne --- not sure it is related to this bug ; since installation of version 20.04 it is impossible to establish an nfs connection betwenne 2 computers on my lan -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418864] tray icon request gajim
https://bugs.kde.org/show_bug.cgi?id=418864 --- Comment #7 from Daniel --- Created attachment 143320 --> https://bugs.kde.org/attachment.cgi?id=143320=edit current not-available icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418864] tray icon request gajim
https://bugs.kde.org/show_bug.cgi?id=418864 --- Comment #6 from Daniel --- Created attachment 143319 --> https://bugs.kde.org/attachment.cgi?id=143319=edit current absent icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418864] tray icon request gajim
https://bugs.kde.org/show_bug.cgi?id=418864 --- Comment #5 from Daniel --- Created attachment 143318 --> https://bugs.kde.org/attachment.cgi?id=143318=edit current busy icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418864] tray icon request gajim
https://bugs.kde.org/show_bug.cgi?id=418864 --- Comment #4 from Daniel --- Created attachment 143317 --> https://bugs.kde.org/attachment.cgi?id=143317=edit current network error icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418864] tray icon request gajim
https://bugs.kde.org/show_bug.cgi?id=418864 --- Comment #3 from Daniel --- Created attachment 143316 --> https://bugs.kde.org/attachment.cgi?id=143316=edit current available icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418864] tray icon request gajim
https://bugs.kde.org/show_bug.cgi?id=418864 --- Comment #2 from Daniel --- Created attachment 143315 --> https://bugs.kde.org/attachment.cgi?id=143315=edit current new message icon -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443910] [Plasma 5.23] kwin_core: Failed to initialize compositing, compositing disabled
https://bugs.kde.org/show_bug.cgi?id=443910 Daniel Roschka changed: What|Removed |Added CC||danielroschka@phoenitydawn. ||de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439332] Ghost windows and popups
https://bugs.kde.org/show_bug.cgi?id=439332 --- Comment #19 from Daniel Santos --- (In reply to Mau from comment #18) > I confirm that disabling the "translucent windows" effect solves this issue. Wow, most interesting! I rather like my translucent background windows, so I'll just keep using the work-around for now. This makes sense as I've noticed that sometimes my foreground window is translucent when it shouldn't be. I have my Konsole windows configured to be translucent always, but every thing else is only supposed to be translucent when it's in the background. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 444833] Plasma crashes after login when user is switched in a certain way
https://bugs.kde.org/show_bug.cgi?id=444833 Daniel changed: What|Removed |Added CC||daniel-he...@web.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 444833] New: Plasma crashes after login when user is switched in a certain way
https://bugs.kde.org/show_bug.cgi?id=444833 Bug ID: 444833 Summary: Plasma crashes after login when user is switched in a certain way Product: frameworks-plasma Version: 5.87.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: daniel-he...@web.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Plasma crashes after login when user is switched in a certain way. I am using the german version, therefore I will use the german terms for the Buttons, I will try translating these buttons into english, but I am not sure it is the official labeling. I hope I am reporting to the right product and component. STEPS TO REPRODUCE 1. Go into Standby or restart your Compute 2. Press "Benutzer wechseln" (switch user) 3. Press "Weitere" (More) 4. Press "Benutzer anzeigen" (show users) and log in 5. While loading Plasma Manjaro Hello Opens 6. Plasma stops loading and crashes, the mouse is still moveable OBSERVED RESULT Plasma does not load properly and crashes, a restart is necessary EXPECTED RESULT Plasma should just load, no matter how often different users a chosen before logging in SOFTWARE/OS VERSIONS Windows:- macOS: - Linux/KDE Plasma: Manjaro, Kernel 5.14.10-1 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444685] Allow free selection of accent colours
https://bugs.kde.org/show_bug.cgi?id=444685 Daniel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Daniel --- Well, then sorry for the noise and thanks for the feature :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444685] New: Allow free selection of accent colours
https://bugs.kde.org/show_bug.cgi?id=444685 Bug ID: 444685 Summary: Allow free selection of accent colours Product: systemsettings Version: 5.23.2 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: daniel-other+kde...@dadosch.de CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- SUMMARY Currently, it is only possible to select out of a few accent colours. It would be nice to be able to select the colour freely. For example, the current red is almost pink, but if someone prefers a darker red in companion with Breeze Dark, it isn't possible to select it. I don't know if it is easily possible, but it would be nice to have if it is. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 444640] New: Birthdays & Anniversaries reminder days does not update
https://bugs.kde.org/show_bug.cgi?id=444640 Bug ID: 444640 Summary: Birthdays & Anniversaries reminder days does not update Product: korganizer Version: 5.18.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: d...@danrees.me Target Milestone: --- SUMMARY Editing the reminder for "Birthdays & Anniversaries" does not update individual calendar entries for birthdays sourced from CardDav account. STEPS TO REPRODUCE 1. After activating "Birthdays & Anniversaries", right click and select Calendar Properties 2. Change the value in "Remind prior to event" input box 3. Click apply OBSERVED RESULT The dialog box stores the inputted value but this does not update individual birthdays on the calendar. EXPECTED RESULT The individual birthdays should be updated to reflect the value inputted via the Calendar Properties dialog. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444546] The dekstop freezes on an incoming or outgoing telephone call
https://bugs.kde.org/show_bug.cgi?id=444546 --- Comment #3 from Daniel Bruckner --- Hi Nicolas Thank you very much! The workaround in bug 442645 did indeed solve the problem. I have recorded this in my bug report and referred to bug 442645. Btw: *You guys are doing a great job!* That's why I've love GNU/Linux since almost 14 years, especially the KDE project! I really appreciate it - thanks again! Beste Grüsse! Have a nice evening ... Daniel Am 28.10.21 um 17:40 schrieb Nicolas Fella: > https://bugs.kde.org/show_bug.cgi?id=444546 > > Nicolas Fella changed: > > What|Removed |Added > > CC||nicolas.fe...@gmx.de > Resolution|--- |DUPLICATE > Status|REPORTED|RESOLVED > > --- Comment #1 from Nicolas Fella --- > > > *** This bug has been marked as a duplicate of bug 442645 *** > -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444546] The dekstop freezes on an incoming or outgoing telephone call
https://bugs.kde.org/show_bug.cgi?id=444546 --- Comment #2 from Daniel Bruckner --- (In reply to Nicolas Fella from comment #1) > > *** This bug has been marked as a duplicate of bug 442645 *** The workaround as mentioned in bug 442645 actually solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442645] Plasma freezes on receiving call from KDE Connect
https://bugs.kde.org/show_bug.cgi?id=442645 --- Comment #7 from Daniel Bruckner --- (In reply to Nicolas Fella from comment #6) > *** Bug 444546 has been marked as a duplicate of this bug. *** (In reply to gudvinr from comment #5) > After I disabled "Pause media during calls" issue is seemingly gone This workaround actually solved the issue. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444546] New: The dekstop freezes on an incoming or outgoing telephone call
https://bugs.kde.org/show_bug.cgi?id=444546 Bug ID: 444546 Summary: The dekstop freezes on an incoming or outgoing telephone call Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: dbruck...@posteo.de Target Milestone: --- KDE-Connect Version 21.08.2-0xneon+focal+release+build28 (focal) KDE-Connect connects to the Android smartphone (Android 10) without any problems. However, when a call comes in or a call is made, the dekstop freezes and only the mouse can be moved: no reaction to right-click; widgets do not react. The control bar also no longer reacts. After a relatively long time, everything works again. STEPS TO REPRODUCE 1. Happens reproducible with every call OBSERVED RESULT Desktop freezes EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: -- macOS: -- Linux/KDE Plasma: KDE Neon 5.23 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 KDE-Connect Version 21.08.2-0xneon+focal+release+build28 (focal) ADDITIONAL INFORMATION The problem already existed in KDE Plasma 5.22 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406489] Can not save/export images in pdf file
https://bugs.kde.org/show_bug.cgi?id=406489 Daniel changed: What|Removed |Added CC||daniel-other+kdebug@dadosch ||.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 --- Comment #21 from Daniel --- On my system (neon 20.04), switching to a different submenu in Kickoff and then going back to Favorites appears to straighten everything out. But it's still so annoying that it definitely needs resolving. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444302] New: Moving around icons in the favorites menu doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=444302 Bug ID: 444302 Summary: Moving around icons in the favorites menu doesn't work properly Product: plasmashell Version: 5.23.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: dwoodfi...@outlook.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142805 --> https://bugs.kde.org/attachment.cgi?id=142805=edit The cursed behavior in action. LibreOffice Write icon covers up Frescobaldi icon. SUMMARY When clicking and dragging to move an icon in the Favorites menu, the icon goes to the wrong place. All the other icons shuffle out of the way as though it went to the right place, however, and this causes multiple icons to overlap. After a few minutes the menu fixes itself somehow, but it's very annoying in the meantime. STEPS TO REPRODUCE 1. Open Kickoff 2. Click and drag an icon in the Favorites menu to a different position in the Favorites menu 3. Behold the ensuing chaos and cringe in horror!!! aaaAA OBSERVED RESULT Instead of moving to the correct position, the icon you dragged is placed in the farthest left column of the row it was in before you moved it. Other icons, however, shuffle to the right/down as though the dragged icon *has* assumed the correct new position, resulting in the dragged icon occupying the same space as another icon. The icon's position seems to fix itself after a minute or two, but it shouldn't do this in the first place. Expected result The icon moves to the correct position, and all the others shuffle out of the way. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Linux 5.11.0-38-lowlatency x64 (available in About System) KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Occurs on both X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 --- Comment #15 from Daniel Vrátil --- The problem only affects contacts, since Google has deprecated the Contacts API (so when we query your Google addressbook it returns empty data, or an error, or both) and replaced if with People API (which we now need to implement to get access to your contacts again). Google Calendar integration uses the Calendar API, which is not affected by the deprecation of Contacts API so it continues to work. To be completely clear - the deprecation has been announced well in advance by Google, this is purely my fault as the "Google integration" maintainer for not implementing the new API in time (mostly because I was taking a time off from KDE at that time). -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 --- Comment #13 from Daniel Vrátil --- Implementing People API in libkgapi is in progress. I'm rushing to get it in for Gear 21.12, but it's a large API to implement, so it's taking some time -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 444135] Open dolphin feature prohibits symbol output
https://bugs.kde.org/show_bug.cgi?id=444135 Daniel Holgerson changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 444135] Open dolphin feature prohibits symbol output
https://bugs.kde.org/show_bug.cgi?id=444135 Daniel Holgerson changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 444135] Open dolphin feature prohibits symbol output
https://bugs.kde.org/show_bug.cgi?id=444135 --- Comment #2 from Daniel Holgerson --- Thank you so much. Finally I have the name for this feature and can form a coherent google search. I already saw this config-page but managed to not connect the dots here. Maybe I should get into kde-development and propose an little help-icon that plays an animated gif on hover, as I already did a C++/QT5 project. To conclude this is a feature which works 100% correctly and this issue can be closed. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 444135] New: Open dolphin feature prohibits symbol output
https://bugs.kde.org/show_bug.cgi?id=444135 Bug ID: 444135 Summary: Open dolphin feature prohibits symbol output Product: konsole Version: 21.08.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: dan...@buccaneersdan.de Target Milestone: --- SUMMARY There is a feature, presumably of konsole, that if the shift key is pressed, it displays small numbered box overlays on top of files and directories and additionally underlines those files. I seems that if I press "Shift + ." (which should produce a colon-symbol) on a DE-keyboard layout, a dolphin-window with the current path is opened. STEPS TO REPRODUCE 1. Open a konsole tab 2. Press "Shift + ." (I want a colon-symbol to be printed) 3. Get a directory listing with "ls" 4. Press "Shift + ." again OBSERVED RESULT At 2. the symbol is correctly printed At 4. a directory listing is displayed so the "shift + ." triggers dolphin EXPECTED RESULT The symbol should be printed at 2. or 4. The surely useful dolphin-feature should be easyly deactivateable or the key-combo should be modifiable, which I failed to accomplish both. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Keyboard layout: DE -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439332] Ghost windows and popups
https://bugs.kde.org/show_bug.cgi?id=439332 Daniel Santos changed: What|Removed |Added CC||daniel.san...@pobox.com --- Comment #15 from Daniel Santos --- Same here, but with Radeon. Nothing in dmesg. Operating System: Gentoo Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.9 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD PITCAIRN # lspci -vs 2e:00.0 2e:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Curacao PRO [Radeon R7 370 / R9 270/370 OEM] Flags: bus master, fast devsel, latency 0, IRQ 126, IOMMU group 15 Memory at e000 (64-bit, prefetchable) [size=256M] Memory at fd40 (64-bit, non-prefetchable) [size=256K] I/O ports at f000 [size=256] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Capabilities: [200] Physical Resizable BAR Capabilities: [270] Secondary PCI Express Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Kernel driver in use: radeon Kernel modules: radeon, amdgpu x11-drivers/xf86-video-amdgpu-19.1.0::gentoo was built with the following: USE="udev" ABI_X86="(64)" CFLAGS="-march=native -O2 -ggdb3 -pipe" CXXFLAGS="-march=native -O2 -ggdb3 -pipe" LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,lazy" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443921] New: Wayland: Cursor for Stylus only shows after moving mouse and is hidden after touching screen
https://bugs.kde.org/show_bug.cgi?id=443921 Bug ID: 443921 Summary: Wayland: Cursor for Stylus only shows after moving mouse and is hidden after touching screen Product: kwin Version: 5.23.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@dasposeidon.tk Target Milestone: --- SUMMARY In Wayland, when using a stylus (wacom, etc.) to input, the default cursor is shown if it was shown previously and hidden if it was hidden previously STEPS TO REPRODUCE 1. Move cursor using mouse or touchpad 2. hover or click stylus 3. Touch touchscreen 4. hover or click stylus OBSERVED RESULT At 2. the cursor moves with the stylus, Ar 4. the cursor is invisible EXPECTED RESULT The cursor should always be shown when hovering or clicking stylus SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.12-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × AMD Ryzen 3 4300U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION Tested on HP ProBook x360 435 G7 using HP Pro Pen G1 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 355139] Option/tool to automatically fit window to image (adapt window ratio)
https://bugs.kde.org/show_bug.cgi?id=355139 Daniel Fichtner changed: What|Removed |Added CC||dan...@outlook.de --- Comment #12 from Daniel Fichtner --- I'm just starting out here, but I'd love to have a look at implementing it :) So no promises but I'll give it a try :) -- You are receiving this mail because: You are watching all bug changes.
