[konversation] [Bug 442109] New: 21.04.3: Tab completion broken
https://bugs.kde.org/show_bug.cgi?id=442109 Bug ID: 442109 Summary: 21.04.3: Tab completion broken Product: konversation Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: inputline Assignee: konversation-de...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- After upgrading to 21.04.3, tab completion only works for a single nick in the channel. Downgrading back to 20.12.3 restores it working. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 442108] New: Application Launcher Cats must change with Mouse Click not Mouse Hover
https://bugs.kde.org/show_bug.cgi?id=442108 Bug ID: 442108 Summary: Application Launcher Cats must change with Mouse Click not Mouse Hover Product: plasma-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: character alternatives palette Assignee: uhh...@gmail.com Reporter: encoder.em...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 141352 --> https://bugs.kde.org/attachment.cgi?id=141352=edit sample sorry if im choosing wrong place for submit this , KDE has to find a better way for novices , to find categories ! in default Application Launcher in plasma5.22 , after user clicking on the launcher and open it , user need to move mouse on favorite app for launching , but on the way , mouse goes through the categories , and because of mouse hover , the selected cat for showing will change and display an unwanted category , and the user has to click on the desired category again , the solution is to change the categories only when clicked mouse , not hover . -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 441275] I get two holiday updates instead of one. And The indiannational calendar isn't working
https://bugs.kde.org/show_bug.cgi?id=441275 --- Comment #3 from Riyadul Islam Mollick --- I checked again. In Korganizer it's works fine but indiannational calender dates still not showing. The problem occurs in digital clock widget on plasma desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441429] Plasma Crashes when Eject Disks FDisk using Sometimes
https://bugs.kde.org/show_bug.cgi?id=441429 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423210] digital clock and calendar are empty if local timezone selected
https://bugs.kde.org/show_bug.cgi?id=423210 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441238] previously removed widgets reappear upon shutdown+reboot
https://bugs.kde.org/show_bug.cgi?id=441238 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441334] [KDE Neon] When changing the font, the names of localization options are not displayed correctly.
https://bugs.kde.org/show_bug.cgi?id=441334 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441336] [KDE Neon] When changing the Regular font from Noto sans arabic to Noto sans, the outline of the font names disappears
https://bugs.kde.org/show_bug.cgi?id=441336 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441268] Exporting a sequence of images for an animation layer
https://bugs.kde.org/show_bug.cgi?id=441268 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 428105] Can't find hidden files even when hidden files are set to be indexed
https://bugs.kde.org/show_bug.cgi?id=428105 --- Comment #13 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 442107] Reboot fails to install updates
https://bugs.kde.org/show_bug.cgi?id=442107 --- Comment #1 from Steven --- In my "Additional Information, I referenced the wrong bug number, though the link was correct. I meant to indicated that I found bug 438809 (I mistakenly typed the 8's as 9's). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 442107] New: Reboot fails to install updates
https://bugs.kde.org/show_bug.cgi?id=442107 Bug ID: 442107 Summary: Reboot fails to install updates Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: steven.c.how...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Updates do not install on reboot, and there is no option to "press 'c' to cancel" during startup. STEPS TO REPRODUCE 1. Boot machine 2. Receive pop-up notification that restart is needed to install updates 3. Restart 4a. Wait for reboot to complete 4b. Press arrow key (forget which one) to show detailed boot log 5. No option to "press 'c' to cancel updates" or anything like that come up for either the graphical boot or the detailed log view of the boot process 6. Return to step 2. OBSERVED RESULT Every time I boot the laptop, I get the same notification that I need to install updates. In addition to the above steps, I have tried running `sudo apt update && sudo apt -y -m dist-upgrade && sudo apt -y autoremove && sudo apt -y autoclean` to try to freshly install the updates with no change in the outcome. EXPECTED RESULT Updates would install and stop notifying me. SOFTWARE/OS VERSIONS Windows: none macOS: none Kernel Version: 5.11.0.27-generic (64-bit) (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Processor: 4 x Intel Core i5-6200U CPU @ 2.30 GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel HD Graphics 520 ADDITIONAL INFORMATION I found bug 439909 (https://bugs.kde.org/show_bug.cgi?id=438809) describing a similar behavior but the listed solution do not work for me. I do not get an option to press "c", I tried repeatedly pressing "c" anyway with no change. I tried rebooting the machine over a dozen times with no change (Well over the three reboots described by Paul Worrall). -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 442042] ksystemstats: GPU plugin reports 0 C temperature with the new libsensors-based plugins
https://bugs.kde.org/show_bug.cgi?id=442042 Luca Beltrame changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Luca Beltrame --- Yes, I confirm it's in the sensor browser, and it's displaying 0 C. My guess is that the temperature sensor fails to initialize properly (the cause of the crash before), but now we have a default sensor property with no data. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 442106] New: KDE file management has slowed to a crawl here in recent weeks
https://bugs.kde.org/show_bug.cgi?id=442106 Bug ID: 442106 Summary: KDE file management has slowed to a crawl here in recent weeks Product: frameworks-kio Version: 5.85.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: xavio...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Hi Guys, There's a nasty bug in kio v5.85.0-1 which causes slowdowns when navigating folders in KDE-based applications. To illustrate the problem, I have attached[1] a video-grab of Dolphin. As you can see, there's a delay of about half a second each time I try to enter a folder. The exception was in the first (A) case, where it took several seconds! The problem also becomes obvious towards end of the video when it walks back through the folders to the beginning. (You can see how slowly the folders are changing in the titlebar of the window, next to the mouse cursor.) I wish this problem was Dolphin-specific. Unfortunately that's not the case as it happens in other KDE applications (e.g. Gwenview and the File Open/Save-As windows while using Google Chrome) as well. Downgrading to kio v5.84.0-2 solves the problem. As you can see in this[2] forum thread, it has worked for at least one other person as well. So, whatever code changes were made in v5.85.0-1, I'm sorry to say that they need to be revised/reverted. Links [1]: https://drive.google.com/file/d/1IFjP0I6g9ildCx3eQEqvrGcCvOfx5L9x/view?usp=sharing [2]: https://bbs.archlinux.org/viewtopic.php?pid=1991655#p1991655 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 299156] Dolphin won't copy files to a ramfs - it thinks the disk is full
https://bugs.kde.org/show_bug.cgi?id=299156 g507...@nwytg.net changed: What|Removed |Added Resolution|FIXED |--- CC||g507...@nwytg.net Status|RESOLVED|REOPENED --- Comment #2 from g507...@nwytg.net --- This is broken again. Dolphin version 18.08.0. "There is not enough space on the disk to write". Not a permissions issue -- the mount is writable and manageable from other programs and file managers. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 306062] konsolepart should provide default shortcut for increasing/decreasing font size (zoom in/out) in Yakuake
https://bugs.kde.org/show_bug.cgi?id=306062 Sebastian Kuźlak changed: What|Removed |Added CC||sebastiankuz...@gmail.com --- Comment #17 from Sebastian Kuźlak --- this is an issue for almost 10 years... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442105] Cursor rendering incorrectly outside title bars
https://bugs.kde.org/show_bug.cgi?id=442105 --- Comment #1 from Weston Peterson --- Created attachment 141351 --> https://bugs.kde.org/attachment.cgi?id=141351=edit Cursor as it looks inside a title bar -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442105] New: Cursor rendering incorrectly outside title bars
https://bugs.kde.org/show_bug.cgi?id=442105 Bug ID: 442105 Summary: Cursor rendering incorrectly outside title bars Product: kwin Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: wpeterson...@gmail.com Target Milestone: --- Created attachment 141350 --> https://bugs.kde.org/attachment.cgi?id=141350=edit Cursor as it looks outside a title bar SUMMARY The cursor has a jagged look whenever it is hovering over something outside a title bar. STEPS TO REPRODUCE 1. Set display scale over 100% (Mine is set to 150%) 2. Hover over a titlebar 3. Hover over a location outside a titlebar OBSERVED RESULT Whenever the cursor moves outside a title bar it looks noticeably worse. EXPECTED RESULT The cursor looks good whether it is over a title bar or not SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 394967] Edit/Find defaults to a date range even with the date range box unchecked.
https://bugs.kde.org/show_bug.cgi?id=394967 --- Comment #5 from gjditchfi...@acm.org --- Git commit 417ce07bf6dab73ae0e4c6fd10b47686e5ad52c4 by Glen Ditchfield, on behalf of Glen Ditchfield. Committed on 07/09/2021 at 01:06. Pushed by gditchfield into branch 'master'. Clarify some labels and tooltip help in the Edit > Find... dialog M +1-1src/dialog/searchdialog.cpp M +28 -28 src/ui/searchdialog_base.ui https://invent.kde.org/pim/korganizer/commit/417ce07bf6dab73ae0e4c6fd10b47686e5ad52c4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442104] New: kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma with libinput-1.18.901-1.fc35
https://bugs.kde.org/show_bug.cgi?id=442104 Bug ID: 442104 Summary: kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma with libinput-1.18.901-1.fc35 Product: kwin Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- SUMMARY kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma 5.22.5 on Wayland in a Fedora 35 KDE Plasma installation. The screen went black and then Plasma restarted. Core was generated by `kwin_wayland --wayland_fd 4 --xwayland /usr/libexec/startplasma-waylandsession'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fe383646a95 in KWin::LibInput::Context::closeRestricted (this=0x558b8b8fb7a0, fd=33) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp:146 Downloading source file /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp... 146 kwinApp()->platform()->session()->closeRestricted(fd); [Current thread is 1 (Thread 0x7fe36d78d640 (LWP 2255))] (gdb) bt #0 0x7fe383646a95 in KWin::LibInput::Context::closeRestricted(int) (this=0x558b8b8fb7a0, fd=33) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp:146 #1 KWin::LibInput::Context::closeRestrictedCallBack(int, void*) (fd=33, user_data=0x558b8b8fb7a0) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp:97 #2 0x7fe380e19101 in close_restricted (libinput=, libinput=0x558b8b8fb7c0, fd=) at ../src/libinput.c:2054 #3 evdev_device_suspend (device=device@entry=0x558b8b9b8bf0) at ../src/evdev.c:2871 #4 0x7fe380e22e76 in evdev_device_remove (device=0x558b8b9b8bf0) at ../src/evdev.c:2961 #5 0x7fe380e129e4 in evdev_device_dispatch (data=0x558b8b9b8bf0) at ../src/evdev.c:1144 #6 0x7fe380e0e667 in libinput_dispatch (libinput=0x558b8b8fb7c0) at ../src/libinput.c:2209 #7 0x7fe383646e7d in KWin::LibInput::Context::dispatch() (this=, this=) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/context.cpp:80 #8 KWin::LibInput::Connection::handleEvent() (this=0x558b8b966300) at /usr/src/debug/kwin-5.22.5-1.fc35.x86_64/src/libinput/connection.cpp:231 #9 0x7fe381c573a9 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fe36d78c850, r=, this=0x7fe3640047b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate(QObject*, int, void**) (sender=0x7fe3640046d0, signal_index=3, argv=0x7fe36d78c850) at kernel/qobject.cpp:3886 #11 0x7fe381c52327 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7fe3640046d0, m=m@entry=0x7fe381efc460 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fe36d78c850) at kernel/qobject.cpp:3946 #12 0x7fe381c59b4a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) (this=this@entry=0x7fe3640046d0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #13 0x7fe381c5a363 in QSocketNotifier::event(QEvent*) (this=0x7fe3640046d0, e=0x7fe36d78c950) at kernel/qsocketnotifier.cpp:302 #14 0x7fe3828b3443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x7fe3640046d0, e=0x7fe36d78c950) at kernel/qapplication.cpp:3632 #15 0x7fe381c23798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7fe3640046d0, event=0x7fe36d78c950) at kernel/qcoreapplication.cpp:1064 #16 0x7fe381c755ff in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x7fe364004470) at kernel/qeventdispatcher_glib.cpp:107 #17 0x7fe37f2d233f in g_main_dispatch (context=0x7fe364000c20) at ../glib/gmain.c:3381 #18 g_main_context_dispatch (context=0x7fe364000c20) at ../glib/gmain.c:4099 #19 0x7fe37f327288 in g_main_context_iterate.constprop.0 (context=context@entry=0x7fe364000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175 #20 0x7fe37f2cf9e3 in g_main_context_iteration (context=0x7fe364000c20, may_block=1) at ../glib/gmain.c:4240 #21 0x7fe381c74b78 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fe364000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7fe381c221a2 in QEventLoop::exec(QFlags) (this=this@entry=0x7fe36d78cbd0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7fe381a652aa in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x7fe381a664a6 in QThreadPrivate::start(void*) (arg=0x558b8b9bc0d0) at thread/qthread_unix.cpp:329 #25 0x7fe3813caaaf in start_thread (arg=)
[gwenview] [Bug 442103] New: Gwenview crashes when started by clicking on .png file in Dolphin
https://bugs.kde.org/show_bug.cgi?id=442103 Bug ID: 442103 Summary: Gwenview crashes when started by clicking on .png file in Dolphin Product: gwenview Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: j...@cunning-sd.net Target Milestone: --- Created attachment 141349 --> https://bugs.kde.org/attachment.cgi?id=141349=edit Crash backtrace SUMMARY STEPS TO REPRODUCE 1. Open a directory in Dolphin 2. Click on a .png image file OBSERVED RESULT Gwenview briefly displays image then closes with crash report EXPECTED RESULT Display of .png image SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-27-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 441738] Hong Kong (English) Lunar New Year 2021 is incorrect.
https://bugs.kde.org/show_bug.cgi?id=441738 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/calendarsupport/-/merge_requests/29 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 442097] "Unsplash" picture of the day option is now translated super strangely (Plasma 5.22.x)
https://bugs.kde.org/show_bug.cgi?id=442097 Unknown changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Unknown --- SVN commit 1608387 by schwarzer: fix translation Thanks Maximilian Böhm for the report. M +98 -19kdeplasma-addons._json_.po WebSVN link: http://websvn.kde.org/?view=rev=1608387 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442102] New: Feature Request: Freeze the assistant guidelines in place while the pen is down
https://bugs.kde.org/show_bug.cgi?id=442102 Bug ID: 442102 Summary: Feature Request: Freeze the assistant guidelines in place while the pen is down Product: krita Version: 5.0.0-beta1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: jcaique...@gmail.com Target Milestone: --- When you use the 2-point perspective assistant, there are two guidelines that follow the cursor from each vanish point. It'd be useful if you could tick a box so they won't follow the cursor while drawing a line, instead fixing in place until the pen is lifted. The way it works right, with the guidelines always following the cursor, it really psyches you out when trying to use it with the "snap to assistants" turned off. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442101] Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 --- Comment #2 from fizy...@gmail.com --- Created attachment 141348 --> https://bugs.kde.org/attachment.cgi?id=141348=edit Console output -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442101] Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 --- Comment #1 from fizy...@gmail.com --- Created attachment 141347 --> https://bugs.kde.org/attachment.cgi?id=141347=edit GDB log -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442101] New: Crash when dragging a clip onto the timeline
https://bugs.kde.org/show_bug.cgi?id=442101 Bug ID: 442101 Summary: Crash when dragging a clip onto the timeline Product: kdenlive Version: 21.08.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: fizy...@gmail.com Target Milestone: --- Created attachment 141346 --> https://bugs.kde.org/attachment.cgi?id=141346=edit Example clip Whenever I try to drag a clip to the timeline in Kdenlive 21.x, it crashes. I definitely experienced the problem on 21.08.1, 21.08.0 and 21.04.3, but I remember that it started happening the first time I upgraded to 21.x, and for that reason I stayed on 20.12.3 for a long time (20.12.3 didn't crash and if I downgrade, it still doesn't). STEPS TO REPRODUCE 1. Launch Kdenlive 2. Add the attached clip (though any clip I tried worked for me so far 3. Drag the clip to the timeline OBSERVED RESULT Kdenlive crashes. EXPECTED RESULT Clip is added to the timeline. SOFTWARE/OS VERSIONS Linux: Gentoo 5.13.12 KDE: 5.85 (not a full installation, only the required packages, as I'm using i3) Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm providing an example clip that triggers the issue for me, a backtrace from gdb and the output from the console. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Michael changed: What|Removed |Added CC||kde@callthecomputerdoctor.c ||om -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 442100] New: Plasma's Calendar's PIM Event Plugin does not list any events on the current day the first time the Calendar widget is clicked/displayed
https://bugs.kde.org/show_bug.cgi?id=442100 Bug ID: 442100 Summary: Plasma's Calendar's PIM Event Plugin does not list any events on the current day the first time the Calendar widget is clicked/displayed Product: frameworks-plasma Version: 5.85.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: k...@callthecomputerdoctor.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 141345 --> https://bugs.kde.org/attachment.cgi?id=141345=edit Plasma calendar showing no events even though there are four SUMMARY The first time in a session that I click on Plasma's digital clock widget, and the "PIM Event Plugin" is enabled, and there is an event(s) on the current day, the calendar widget slides out, but on the left-hand side of the slide-out panel under where it says "Events", there are no events listed when there should be. Manually clicking on the next day then the current day "wakes up" the functionality and the events become listed on subsequent views of the calendar. STEPS TO REPRODUCE 0. Have a clean start of the Plasma shell where you haven't interacted with the clock widget yet. 1. Have KOrganizer configured with a calendar, like a Gmail calendar. 2. Create a test event for today. We are done with KOrganizer at this point. 3. Right-click on the Plasma clock widget and choose "Configure Digital Clock" 4. In the Calendar tab under available plugins, enable "PIM Events Plugin" and click Apply. 5. In the new PIM Events Plugin tab, enable the calendar that has an event for today. Click OK. 6. Left-click on the Plasma clock widget to make the calendar slide out. OBSERVED RESULT (see attached image) 7. Under where it says "Events" on the left-hand side of the slide out panel, it will say "No events for today". (If you don't see this, to get a clean, just-started Plasma shell, terminate the "plasmashell" process and re-run it from the shell by typing plasmashell &) 8. Click on tomorrow's date, then click on today's date. 9. You will see under "Events" it will display the today's test event we created in step #2. This should've been visible in step #7. 10. Press the Esc key to close the slide out panel. 11. Click on the Plasma clock widget again. 12. This time under "Events" it will automatically show today's test event, as it should've done the first time we looked at the calendar. EXPECTED RESULT The first time you click on the Plasma clock widget to see the calendar, if there is an event for today, it should be listed under the "Events" section. Not just subsequent times. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442090] Screen resolution in the display configuration module is wrong.
https://bugs.kde.org/show_bug.cgi?id=442090 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Output::logicalSize fails to take into account Capabilities. It's definitely a dupe, but I can't find the original -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442084] FR: Access to Display Configuration
https://bugs.kde.org/show_bug.cgi?id=442084 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- Why would that kcm be there, but not any other config module? If you can give an answer that isn't about copying windows, please reopen. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441803] Konsole does not allow to change default profile, but creates new profile instead, leading to cumbersome "New Tab" workflow
https://bugs.kde.org/show_bug.cgi?id=441803 Ahmad Samir changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/konsole/-/commit/5ab8 ||423139467ad97d87d00dc82a85f ||91c5a1492 Resolution|--- |FIXED CC||a.samir...@gmail.com Status|CONFIRMED |RESOLVED Version Fixed In||21.08 --- Comment #2 from Ahmad Samir --- I think this issue is fixed in https://invent.kde.org/utilities/konsole/-/commit/5ab8423139467ad97d87d00dc82a85f91c5a1492 , version 21.08 Basically when you use "Edit current profile" for the first time, you'd be editing the built-in profile, which is immutable, so the dialog actually creates a new profile (as you saw), the missing bit was setting that new profile as the current session profile: SessionManager::instance()->setSessionProfile(session(), profile); FWIW, in git master the menu text has been changed, if the dialog will create a new profile the text is "create new profile", if it's editing an existing (editable) profile, it is "edit current profile". And there is an open MR to rename the "Default" (aka Fallback, aka Built-in) profile to "Built-in" everywhere, to finally disambiguate the name of the internal immutable profile. (A "set profile as default" button sounds like a good idea, currently the only way to set a profile as default is using the profile manager (settings -> configure konsole)). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442072] Brushes I've removed from My favourites tag keep returning to that tag
https://bugs.kde.org/show_bug.cgi?id=442072 --- Comment #2 from starrynight2...@gmail.com --- (In reply to Halla Rempt from comment #1) > This is fixed in Krita 5, currently in beta. Okay, thanks. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442099] New: Create new menu item to facilitate discovery of the KHamburgerMenu's "search all commands" HUD feature
https://bugs.kde.org/show_bug.cgi?id=442099 Bug ID: 442099 Summary: Create new menu item to facilitate discovery of the KHamburgerMenu's "search all commands" HUD feature Product: dolphin Version: 21.08.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@callthecomputerdoctor.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY (This bug applies not only to Dolphin but to Kate, Kmail, Gwenview, and every other program that appears to use KHamburgerMenu. There is no bugs category for KHamburgerMenu, so I'm posting here, excuse me in advance.) There is no way to discover that Ctrl-Alt-I brings up the excellent command search HUD box. The keyboard shortcut cannot even be discovered in System Settings -> Shortcuts after intently looking for 5 minutes. STEPS TO REPRODUCE 1. Look in all menus of Dolphin (or Kate, or Kmail...) to see if there is a mention of how to discover and invoke the command search HUD via Ctrl-Alt-I. OBSERVED RESULT There is no menu item entry in any menu that would help others to find this useful feature. There is no way to know other than to be in-the-know. EXPECTED RESULT In the Help menu, have a menu item that says something like: Quick search all commands Ctrl-Alt-I SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 418189] Plasma freeze when systemd automount NFS shares are not mounted
https://bugs.kde.org/show_bug.cgi?id=418189 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #14 from Nate Graham --- Yay! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] New: Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 Bug ID: 442098 Summary: Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice Product: krita Version: git master (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: tgdev...@gmail.com Target Milestone: --- SUMMARY Issue about the ten brushes feature. Something is wrong with switching back to previous brush preset. Krita version is 5.1.0 pre alpha nighly build(git 8376871). If it's not a bug, just proceed to the appropriate action. STEPS TO REPRODUCE 1. Have a specific brush set for any of the ten brushes shortcut 2. With a canvas opened, press on one of the ten brushes shortcut 3. Press the same shortcut a second time OBSERVED RESULT The brush doesn't switch back to the previous preset EXPECTED RESULT Pressing the second time one of the shortcuts should switch back your current preset to the previous pne SOFTWARE/OS VERSIONS Windows 10 1909 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441803] Konsole does not allow to change default profile, but creates new profile instead, leading to cumbersome "New Tab" workflow
https://bugs.kde.org/show_bug.cgi?id=441803 nsprang...@gmail.com changed: What|Removed |Added CC||nsprang...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from nsprang...@gmail.com --- This is how Konsole was designed apparently. It keeps creating more profiles because you have to manually set the default: Go to "Settings > Manage Profiles", select your profile and click set as default. Now the new tab buttons and menus will use your profile (and you can change it without creating more profiles). I'm working on a commit that adds a "set as default" button to the dialog and I believe there is other work being done to overhaul the profile system... https://invent.kde.org/farruinn/konsole/-/commits/default-profile-button -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 441883] Scripty stopped updating websites-capacity/includes/i18n/*/media.inc
https://bugs.kde.org/show_bug.cgi?id=441883 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/websites/capacity/-/merge_requests/1 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 442097] "Unsplash" picture of the day option is now translated super strangely (Plasma 5.22.x)
https://bugs.kde.org/show_bug.cgi?id=442097 Maximilian Böhm changed: What|Removed |Added CC||m...@elbmurf.de -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 442097] New: "Unsplash" picture of the day option is now translated super strangely (Plasma 5.22.x)
https://bugs.kde.org/show_bug.cgi?id=442097 Bug ID: 442097 Summary: "Unsplash" picture of the day option is now translated super strangely (Plasma 5.22.x) Product: i18n Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: de Assignee: kde-i18n...@kde.org Reporter: m...@elbmurf.de Target Milestone: --- Plasma 5.22.5: The "Unplash" picture of the day provider is now named "Hintergrundbilder nicht als Startbildschirm verwenden" (??!) which is obviously a copy & paste error. EXPECTED RESULT It should just be named "Unsplash". That’s the website after all: https://unsplash.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442096] Krita crashes if SeExpr scripts are saved without a thumbnail
https://bugs.kde.org/show_bug.cgi?id=442096 amyspark changed: What|Removed |Added Status|REPORTED|ASSIGNED Severity|normal |crash URL||https://krita-artists.org/t ||/krita-crashes-while-saving ||-seexpr-script-with-empty-t ||humbnail/28511 Assignee|krita-bugs-n...@kde.org |a...@amyspark.me Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442096] New: Krita crashes if SeExpr scripts are saved without a thumbnail
https://bugs.kde.org/show_bug.cgi?id=442096 Bug ID: 442096 Summary: Krita crashes if SeExpr scripts are saved without a thumbnail Product: krita Version: git master (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: a...@amyspark.me Target Milestone: --- SUMMARY Krita crashes if SeExpr scripts are saved without a thumbnail. This is because I assumed that the QLabel would always contain a pixmap. https://krita-artists.org/t/krita-crashes-while-saving-seexpr-script-with-empty-thumbnail/28511 STEPS TO REPRODUCE Create new document (1024x1024) Create new fill layer Choose SeExpr On the Options tab choose “Save New SeExpr Preset…” Click “Clear Thumbnail” Click Save - crash happens here. OBSERVED RESULT Krita crash: Qt5Gui.dll!7ffc0dabc3f6() (Origen desconocido:0) kritaseexprgenerator.dll!KisWdgSeExprPresetsSave::savePreset() Line 154 (e:\krita-win\src\plugins\generators\seexpr\kis_wdg_seexpr_presets_save.cpp:154) Qt5Core.dll!7ffc0d651860() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e1e1541() (Origen desconocido:0) Qt5Core.dll!7ffc0d651860() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e14d1d6() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e14d0e7() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e14de04() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e09c416() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e076bad() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e074a39() (Origen desconocido:0) kritaui.dll!KisApplication::notify(QObject * receiver, QEvent * event) Line 690 (e:\krita-win\src\libs\ui\KisApplication.cpp:690) Qt5Core.dll!7ffc0d631721() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e078064() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e0c637a() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e0c4400() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e076bad() (Origen desconocido:0) Qt5Widgets.dll!7ffc0e075c0f() (Origen desconocido:0) kritaui.dll!KisApplication::notify(QObject * receiver, QEvent * event) Line 690 (e:\krita-win\src\libs\ui\KisApplication.cpp:690) Qt5Core.dll!7ffc0d631721() (Origen desconocido:0) EXPECTED RESULT Krita doesn't crash and saves the resource. SOFTWARE/OS VERSIONS Windows: 10 20H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Commit hash 2e95dd5, confirmed in 6ca8117f88. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 441887] Remove unused script extract-doc-assoc-ui-cats.py
https://bugs.kde.org/show_bug.cgi?id=441887 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://invent.kde.org/sysa ||dmin/l10n-scripty/commit/02 ||1db180ef160c01e893476dd5243 ||6cd0d865649 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Albert Astals Cid --- Git commit 021db180ef160c01e893476dd52436cd0d865649 by Albert Astals Cid. Committed on 06/09/2021 at 22:07. Pushed by ltoscano into branch 'master'. Remove unused script D +0-49 extract-doc-assoc-ui-cats.py https://invent.kde.org/sysadmin/l10n-scripty/commit/021db180ef160c01e893476dd52436cd0d865649 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 305534] Annotations don't show all non-ASCII letters
https://bugs.kde.org/show_bug.cgi?id=305534 Federico Calzoni changed: What|Removed |Added CC||federicocalzon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 442020] Don't start
https://bugs.kde.org/show_bug.cgi?id=442020 David Jarvie changed: What|Removed |Added Version Fixed In||20.08.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 417791] Snap packages of KDE apps don't work on RHEL 7
https://bugs.kde.org/show_bug.cgi?id=417791 Ivo Cavalcante changed: What|Removed |Added CC||ivo.cavalca...@gmail.com --- Comment #13 from Ivo Cavalcante --- Hi all, Some more Snaps failing on RHEL or RHEL-like version 7 systems, due to this bug. Could you please look into it? It's already been solved in Flatpak, maybe the same solution applies here? https://github.com/flathub/flathub/issues/805#issuecomment-453004369 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435474] Build fails with opencolorio 2.0
https://bugs.kde.org/show_bug.cgi?id=435474 amyspark changed: What|Removed |Added Component|* Unknown |OpenGL Canvas -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 441883] Scripty stopped updating websites-capacity/includes/i18n/*/media.inc
https://bugs.kde.org/show_bug.cgi?id=441883 Albert Astals Cid changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #1 from Albert Astals Cid --- Luigi since it seems you broke it, can you have a look? -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 441884] Stale file websites-capacity/includes/i18n/fr/root.inc, please remove
https://bugs.kde.org/show_bug.cgi?id=441884 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/webs ||ites/capacity/commit/867f8a ||07455d1a6765fcb00fb0c25d076 ||510159a --- Comment #1 from Albert Astals Cid --- Git commit 867f8a07455d1a6765fcb00fb0c25d076510159a by Albert Astals Cid. Committed on 06/09/2021 at 22:11. Pushed by aacid into branch 'master'. Remove empty useless file D +0-0includes/i18n/fr/root.inc https://invent.kde.org/websites/capacity/commit/867f8a07455d1a6765fcb00fb0c25d076510159a -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 441887] Remove unused script extract-doc-assoc-ui-cats.py
https://bugs.kde.org/show_bug.cgi?id=441887 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/sysadmin/l10n-scripty/-/merge_requests/15 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407921] LUT management with defined OCIO doesn't work on Linux
https://bugs.kde.org/show_bug.cgi?id=407921 amyspark changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |UPSTREAM URL||https://github.com/AcademyS ||oftwareFoundation/OpenColor ||IO/issues/1322 --- Comment #8 from amyspark --- This is a bug in OCIO itself. They're using sscanf to parse floating-point numbers in LUTs. This implicitly assumes the files will be parsed using the C locale, which is not the case if you have changed your environment's LANG or LC_* variables. The particular error seen here is triggered by https://github.com/AcademySoftwareFoundation/OpenColorIO/blame/7fece5efb4fecc675376d8d921affb253e52a704/src/core/FileFormatSpi1D.cpp#L131, and is reported in https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/297. I will add a patch for our app's usage as part of 435474. I'm also tagging the relevant bug report upstream. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435474] Build fails with opencolorio 2.0
https://bugs.kde.org/show_bug.cgi?id=435474 Bug 435474 depends on bug 407921, which changed state. Bug 407921 Summary: LUT management with defined OCIO doesn't work on Linux https://bugs.kde.org/show_bug.cgi?id=407921 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441659] ownCloud client icon missing in systemtray
https://bugs.kde.org/show_bug.cgi?id=441659 Andy changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Andy --- The bug seems to be fixed by an oncoming owncloud-client update. https://github.com/owncloud/client/issues/8976 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441927] Ability to have the toolbar show up on fullscreen mode
https://bugs.kde.org/show_bug.cgi?id=441927 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Albert Astals Cid --- closing as i understand you're happy with the solution -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442087] Change paper color doesn't work
https://bugs.kde.org/show_bug.cgi?id=442087 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||aa...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Albert Astals Cid --- Need the pdf file -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441783] kde wayland klipper copies empty string instead of content
https://bugs.kde.org/show_bug.cgi?id=441783 codew...@web.de changed: What|Removed |Added Version|5.22.4 |5.22.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442095] Tree view controls and text rendering
https://bugs.kde.org/show_bug.cgi?id=442095 --- Comment #1 from d3coder --- Ah, also process owners are colored in KSysGuard. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442095] New: Tree view controls and text rendering
https://bugs.kde.org/show_bug.cgi?id=442095 Bug ID: 442095 Summary: Tree view controls and text rendering Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ad...@xakeps.dk CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 141344 --> https://bugs.kde.org/attachment.cgi?id=141344=edit row process name rendering comparison SUMMARY While in tree view, process name renders too far away from row controls or STEPS TO REPRODUCE 1. Start KSysGuard and enable tree view 2. Start plasma-systemmonitor and enable tree view 3. Compare rows OBSERVED RESULT Process name rendered too far away from row controls or row ASCII EXPECTED RESULT Rows are rendered like in KSysGuard SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.13-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441956] Qthread with Python broken in Krita 5
https://bugs.kde.org/show_bug.cgi?id=441956 Lynx3d changed: What|Removed |Added CC||lynx.mw+...@gmail.com --- Comment #3 from Lynx3d --- I can't see any difference with the example plugin between 4.4.3 and 5.0 beta... Are you sure the issue has anything to do with threading? "krita 5 will move the square with rubber banding" sounds more like the widget painting became slower. Is there maybe fractional UI scaling at play? Because if the QImage and the widget don't have the same devicePixelRatio(), the image has to be scaled, which of course is a lot slower than painting it 1:1. Repainting the whole image on every cursor move is very inefficient to begin with... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 424944] Multiple Effects produce unexpected clipping
https://bugs.kde.org/show_bug.cgi?id=424944 --- Comment #6 from Cyril Giraud --- New test with kdenlive-21.08.0a-x86_64.appimage and new "Transform" effect that combines Pan, Zoom and Rotation effects. My feedback: - it solves common problems with those 3 effects... if you use only 1 effect (combining 2 "Transform" effect, one for moving, one other for rotating, initial problem is still present... but is there a good reason to do that?) - sometimes, I've got a hudge number of keyframes (stabilizing a video with automask effect, thanks to https://ferrolho.github.io/blog/2020-08-09/stabilizing-a-video-subject-in-kdenlive)... and wanted to modify constant zoom ratio --> because keyframe sets all parameters effect, I have to modifiy zoom factor for each keyframe... Cheap suggestion here: https://bugs.kde.org/show_bug.cgi?id=442094 Best suggestion: allow temporary extra video resolution between effects to avoid clipping and video quality issues. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442094] New: [ENHANCEMENT] Allow to disable some transform effects from keyframes
https://bugs.kde.org/show_bug.cgi?id=442094 Bug ID: 442094 Summary: [ENHANCEMENT] Allow to disable some transform effects from keyframes Product: kdenlive Version: 21.08.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: cgir...@free.fr Target Milestone: --- ENHANCEMENT SUMMARY STEPS TO REPRODUCE 1. Import a shaky video to project and timeline 2. add "Transform" Effect, 200% zoom and add keyframes to move video and deshake it (or use and old kdenlive version with automask effect thanks to https://ferrolho.github.io/blog/2020-08-09/stabilizing-a-video-subject-in-kdenlive) 3. change your mind for 180% zoom: 2 options 1/ modify each keyframe to move zoom from 200% to 180% (quite long if you have hudge number of keyframes) 2/ add a new Transform effect to zoom out around 90% (and lose video quality and a part of your video clip, see https://bugs.kde.org/show_bug.cgi?id=424944) OBSERVED RESULT 1/ Huge work for kdenlive user. 2/ or Missing part of video. EXPECTED RESULT Transform effect combines 4 sub-effects: Move, Zoom, Rotate and opacity. Allow kdenlive user to enable/disable keyframes action for each sub-effect. When keyframes applies to sub-effect: as actually. When keyframes does not apply to sub-effect: sub-effect parameters can be modified, but applies to the whole effect, as if no keyframe present. SOFTWARE/OS VERSIONS Linux: Ubuntu Studio 20.04.3 LTS kdenlive-21.08.0a-x86_64.appimage ADDITIONAL INFORMATION Of course, it would be better to be able to set different keyframes for each sub-effect... but it solves with multiple Transform effects on same clip... oh, no, because of effect pipelining in project video setting that clips off some video parts, see https://bugs.kde.org/show_bug.cgi?id=424944) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 438994] Button highlighted in dialog to confirm data deletion is not triggered when I press enter key
https://bugs.kde.org/show_bug.cgi?id=438994 --- Comment #10 from Kai Uwe Broulik --- 1.) it's different from any other QStyle (Fusion, even Oxygen) 2.) your patch for KMessageBox was only just merged, but Frameworks tagging for the version Plasma 5.23 will depend on has already happened 3.) The new KMessageBox behavior is different from how it has been for 20 years and how it is on e.g. Windows. Pressing Return on a "Save changes?" is now "Cancel" rather than "Yes." 4.) The "About Qt" dialog can no longer be closed by pressing Return and that is a dialog created by Qt, so they clearly consider default button behavior canonical. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 442039] Make Okular/ODT read-only
https://bugs.kde.org/show_bug.cgi?id=442039 --- Comment #2 from Albert Astals Cid --- confirmed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442003] missing plug-in for ODT
https://bugs.kde.org/show_bug.cgi?id=442003 --- Comment #6 from Albert Astals Cid --- (In reply to Albert Astals Cid from comment #5) > (In reply to Christopher Yeleighton from comment #3) > > (In reply to Christopher Yeleighton from comment #2) > > > > If the ODT back-end is not a part of Okular, why can I report a bug against > > it? > > As mentioned *calligra* Do you even read what i write? Booo me, it's me that doesn't read what you write. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442003] missing plug-in for ODT
https://bugs.kde.org/show_bug.cgi?id=442003 --- Comment #5 from Albert Astals Cid --- (In reply to Christopher Yeleighton from comment #3) > (In reply to Christopher Yeleighton from comment #2) > > If the ODT back-end is not a part of Okular, why can I report a bug against > it? As mentioned *calligra* Do you even read what i write? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 438994] Button highlighted in dialog to confirm data deletion is not triggered when I press enter key
https://bugs.kde.org/show_bug.cgi?id=438994 --- Comment #9 from Jan Blackquill --- Best way we can replicate the behaviour on macOS (arguably in a less ugly manner than the official Qt stuff for macOS), where the default button isn't jumping around due to autodefault. -- You are receiving this mail because: You are watching all bug changes.
[konquest] [Bug 442022] No longer setting window title according to -qwindowtitle option
https://bugs.kde.org/show_bug.cgi?id=442022 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442093] New: Settings dialog in Kate is humongous
https://bugs.kde.org/show_bug.cgi?id=442093 Bug ID: 442093 Summary: Settings dialog in Kate is humongous Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: k...@privat.broulik.de Target Milestone: --- Created attachment 141343 --> https://bugs.kde.org/attachment.cgi?id=141343=edit Giant dialog SUMMARY STEPS TO REPRODUCE 1. Open Kate settings OBSERVED RESULT Get a dialog that doesn't fit on a 14" screen yet is full of whitespace EXPECTED RESULT Get a dialog with reasonable size OTHER INFORMATION Seems to be with German translations, English dialog is still quite tall but not as wide SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2021-09-03 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 442052] transaction date vs post date
https://bugs.kde.org/show_bug.cgi?id=442052 mahue...@gmail.com changed: What|Removed |Added CC||mahue...@gmail.com --- Comment #1 from mahue...@gmail.com --- Just having the transaction date in addition to the posting date may not even be enough for what you need - if I'm not mistaken, all splits currently share the same posting date (so a transfer between two accounts (e.g. checking <> credit card) would always show the same posting date on both accts). One way to deal with this is to run the transactions through a separate account. E.g. for the cc payment (scenario 2), you could create a "cash in transit" (CIT) account and use the following posting logic: on the day the payment posts to your checking, post a transfer from the checking to the CIT account (dr CIT, cr checking). on the day the payment clears on the cc, post another transfer from CIT to the CC (dr CC, cr CIT). Your CIT should now be zero; and both the checking and cc accounts should show the proper dates. You could do a similar thing for the expense transactions (scenario 1) as well - you'd probably want a separate account for that (I've seen this being called "outgoing checks" in the past, you may want to look for a better term, especially if you don't do check payments). on the day you make the purchase, post the expense and set up a liability (dr expense, cr outgoing checks) on the day the charge posts to the cc, reclass the liability into the actual cc account (dr outgoing checks, cr CC). Depending on the number of transactions you're dealing with, it may not be worth the effort to do all of this (I certainly don't do it for my personal finances) - but if having the dates 100% right is a must-have for you, this may be a workaround for now. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441162] Png file with alpha removed through imagemagick show washed out colours
https://bugs.kde.org/show_bug.cgi?id=441162 Han Prower changed: What|Removed |Added CC||mafr...@gmail.com --- Comment #5 from Han Prower --- Just to make sure people don't think it's a specific ImageMagick export issue some 8bit PNGs exported from Photoshop suffer the same issue so it may be helpful to remove "imagemagick" from the title. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 438994] Button highlighted in dialog to confirm data deletion is not triggered when I press enter key
https://bugs.kde.org/show_bug.cgi?id=438994 David Edmundson changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #8 from David Edmundson --- Please answer my question in #4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 438994] Button highlighted in dialog to confirm data deletion is not triggered when I press enter key
https://bugs.kde.org/show_bug.cgi?id=438994 Jan Blackquill changed: What|Removed |Added Component|QStyle |general Product|Breeze |frameworks-kwidgetsaddons CC||kdelibs-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438994] Button highlighted in dialog to confirm data deletion is not triggered when I press enter key
https://bugs.kde.org/show_bug.cgi?id=438994 Jan Blackquill changed: What|Removed |Added CC||uhh...@gmail.com Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Jan Blackquill --- Apps need to set reasonable default buttons; this is an expectation from Qt. Fortunately, most do, as Qt's own dialog widgets set reasonable defaults. KF5 was an exception, as our widgets didn't set any default buttons. Now, we do set a reasonable default button, so the vast majority of apps should have default buttons set now. Marking as fixed since the bug was complaining about an app using KF5 widgets not having a default button, and now the KWidgetsAddons widgets set reasonable default buttons. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 442020] Don't start
https://bugs.kde.org/show_bug.cgi?id=442020 --- Comment #1 from David Jarvie --- This problem should not exist in Kubuntu 20.10 and later, because KAlarm no longer uses Akonadi to access its calendars (from KAlarm version 3.0/KDE apps 20.08 onwards). This seems likely to be a problem which will occur with any application which uses Akonadi (KMail, KOrganizer, etc.), since they all use the same Akonadi database to access their data. See for example https://askubuntu.com/questions/1255772/kmail-cant-start-akonadi-services-on-kubuntu-20-04. There is a possible solution at https://forum.kde.org/viewtopic.php?t=111828#p268167 To investigate, try the following: 1) If I remember correctly, there is a button in the application window which you can click to get more information about why Akonadi cannot run. This may help to understand what to do to fix the issue. 2) If that doesn't help, you could open a terminal window (e.g. Konsole), and type akonadictl start Then, in the terminal window, look for error messages which help you to understand why Akonadi cannot run. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 442092] New: allow infinite time before password is required to unlock after auto-locking
https://bugs.kde.org/show_bug.cgi?id=442092 Bug ID: 442092 Summary: allow infinite time before password is required to unlock after auto-locking Product: kscreenlocker Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tempel.jul...@gmail.com CC: bhus...@gmail.com Target Milestone: --- Currently, three minutes is the maximum value a user can set. However, this is still annoying when kscreenlocker is mostly used as a screensaver, as chances are you don't want to always enter your password after three minutes. Perhaps not using a password for a user can be a workaround in some scenarios, but there are quite some reasons why an option to turn off auto-locking would be the better choice: -Users shouldn't be encouraged not to use passwords. -Users want to be able to deliberately lock the screen e.g. via hotkey, but don't necessarily want auto-locking. -I assume allowing (close to) infinite values for LockGrace config setting in kscreenlockerrc should be easy to implement. -So kscreenlocker should be able to easily act as a screensaver, without really bending its purpose and not making things harder for developers in the future. -screensaver situation is dire on Linux, especially on Wayland. kscreenlocker already has all the DPMS and inactivity detection functionality implemented that is required by a screensaver, so a separate screensaver program inside KDE/Plasma would cause redundancy (and doesn't seem likely to happen). -On Windows, screensaver and screen locker are basically the same thing. Windows screensaver offers an option to lock the screen after the screensaver is stopped by activity. Which in return means you can also have a screensaver without automatic screen locking by not having the locking checkbox ticked. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442091] New: (Wayland) Plasma crashes when trying to move window with S Pen (Samsung Notebook 9 Pro)
https://bugs.kde.org/show_bug.cgi?id=442091 Bug ID: 442091 Summary: (Wayland) Plasma crashes when trying to move window with S Pen (Samsung Notebook 9 Pro) Product: plasmashell Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jlsuck...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.21.4) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-31-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: I use my computer to to math homework, and I have an S-Pen enabled device. It seems to be connected as a mouse in the input devices, however inputs such as pressure and distance work perfectly in wayland. When I click on the draggable part of a window with my S Pen, it doesn't drag but the window goes transparent. If I move my mouse, the drag begins and the crash is avoided. If I switch windows with the window transparent, it crashes. If I use touch to move the window, the crash is avoided. I boot in CSM mode if that has anything to do with it. - Unusual behavior I noticed: The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fdf21da8864 in __GI_abort () at abort.c:79 #6 0x7fdf22219c77 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdf20092d39 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #8 0x7fdf200a1f9a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #9 0x7fdf22479600 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fdf2247cbe3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fdf2247d413 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fdf2311d783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fdf224417ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fdf2249be05 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fdf2080f8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fdf20862d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fdf2080d023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fdf2249b204 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fdf2244011b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fdf22448604 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x55a862d9ae5e in ?? () #22 0x7fdf21daa565 in __libc_start_main (main=0x55a862d99f10, argc=1, argv=0x7ffcd607c548, init=, fini=, rtld_fini=, stack_end=0x7ffcd607c538) at ../csu/libc-start.c:332 #23 0x55a862d9af8e in ?? () [Inferior 1 (process 1022) detached] The reporter indicates this bug may be a duplicate of or related to bug 439321, bug 438373. Possible duplicates by query: bug 441522, bug 441421, bug 441365, bug 441234, bug 441022. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442090] New: Screen resolution in the display configuration module is wrong.
https://bugs.kde.org/show_bug.cgi?id=442090 Bug ID: 442090 Summary: Screen resolution in the display configuration module is wrong. Product: systemsettings Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: mako...@hotmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 141342 --> https://bugs.kde.org/attachment.cgi?id=141342=edit screenshot SUMMARY Screen resolution (by the way, in french the correct word is definition so the translation in the interface is incorrect) in the display configuration module is wrong. STEPS TO REPRODUCE 1. Launch system settings with display configuration OBSERVED RESULT in the blue rectangle representing screen, resolution is half of what it should be. The resolution selected below is correct though. EXPECTED RESULT resolution in the blue rectangle representing screen is correct and the same as below. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 ADDITIONAL INFORMATION Nvidia proprietary drivers (optimus setup) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 403717] When multiple instances are running, render progress is not handled consistently
https://bugs.kde.org/show_bug.cgi?id=403717 Cyril Giraud changed: What|Removed |Added OS|Microsoft Windows |Linux CC||cgir...@free.fr --- Comment #3 from Cyril Giraud --- Same problem with Ubuntu Studio 20.04 LTS and kdenlive-21.08.0a-x86_64.appimage Kdenlive multiple instances are very useful: - running different versions to test and report bugs :-) - working concurrently on multiple video sequences: one to compute stabilized video for example, one other import and use them (necessary to change video speed for example). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438994] Button highlighted in dialog to confirm data deletion is not triggered when I press enter key
https://bugs.kde.org/show_bug.cgi?id=438994 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/breeze/-/merge_requests/133 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 440801] Crash after search or during typing of search criterea [CollectionTreeItem::row()]
https://bugs.kde.org/show_bug.cgi?id=440801 --- Comment #2 from Arjan ten Hoopen --- Comment on attachment 141272 --> https://bugs.kde.org/attachment.cgi?id=141272 New crash information added by DrKonqi L.S. I haven't experienced this behaviour anymore for over a week. Don't know what has changed on my system but you can close this bug. I cannot reproduce it anymore. If there is still something you would like to know ... happy to help. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 --- Comment #1 from Riccardo Robecchi --- Created attachment 141341 --> https://bugs.kde.org/attachment.cgi?id=141341=edit Akonadi log After posting the above, I tried to open KOrganizer and found out it was not displaying my Google calendars at all. I had to stop Akonadi and then start it again for them to appear in the list (they were all deselected), but I then had to open and close KOrganizer two times in order for it to correctly display them. I'm attaching the Akonadi log. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 442089] New: Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 Bug ID: 442089 Summary: Tens of "error while trying to delete calendar item" popups appear randomly Product: korganizer Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sephiroth...@hotmail.it Target Milestone: --- Created attachment 141340 --> https://bugs.kde.org/attachment.cgi?id=141340=edit Screenshot of the issue SUMMARY At seemingly random times, tens upon tens of popups stating "error while trying to delete calendar item" appear. This seems to be connected with events changing in a linked Google calendar, but this change does not trigger the bug every time it happens. STEPS TO REPRODUCE 1. ? OBSERVED RESULT Tens of popups appear. EXPECTED RESULT A single popup, if truly necessary, appears and informs the user of what is happening beyond a very generic error message that makes it impossible to understand what's wrong. SOFTWARE/OS VERSIONS Linux: KDE neon KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442087] Change paper color doesn't work
https://bugs.kde.org/show_bug.cgi?id=442087 apache changed: What|Removed |Added Platform|Other |Manjaro CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442070] Difference of preview update frequency when using a filter that has control points
https://bugs.kde.org/show_bug.cgi?id=442070 --- Comment #3 from amyspark --- A quick debug session (hampered by GDB struggling to keep up with the debugging symbols) shows that GMic-Qt drops almost all of the mouse events because the preview widget is always at "max zoom". I'll continue tracing things later, with an update to 2.9.9, but please be aware that the preview widget code wasn't altered by my plugin porting. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 102822] import mozilla firefox passwords
https://bugs.kde.org/show_bug.cgi?id=102822 --- Comment #15 from Jack --- I've played with it a bit more, and I believe the problem is actually that the whole layout and format of the files that make up a plug-in have changed, not just one or two files. I'll keep trying to rework this in my free time, but that also assumes that the core library (.so) files will still work with the current version of kwallet. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442088] New: Mixed Clips issues with keyboard editing
https://bugs.kde.org/show_bug.cgi?id=442088 Bug ID: 442088 Summary: Mixed Clips issues with keyboard editing Product: kdenlive Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: and...@alweb.dk Target Milestone: --- SUMMARY There are two issues: 1. Adding a mix with keyboard requires a clip to be selected, even if the playhead is at a clip meeting point. Isn't that a regression? STEPS TO REPRODUCE 1. Have a timeline with two clips 2. Press Alt + arrow to go the the joint 3. Press U OBSERVED RESULT No mix applied. Kdenlive complains about missing selection EXPECTED RESULT Mix applied 2. Adding a mix with keyboard does not respect the track (de)activated state. Since all other keyboard editing does, it is unespected. STEPS TO REPRODUCE 1. Have a timeline with two AV clips 2. Deactivate the audio track 3. Press Alt + arrow to go the the joint, + to select a clip 4. Press U OBSERVED RESULT Mix is applied to both video and audio track EXPECTED RESULT Mix applied ONLY to video track, because audio track is deactivated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, up to date (available in About System) KDE Plasma Version: Current KDE Frameworks Version: Current Qt Version: Current KDE relatable ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442087] New: Change paper color doesn't work
https://bugs.kde.org/show_bug.cgi?id=442087 Bug ID: 442087 Summary: Change paper color doesn't work Product: okular Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- When I clock on icon "change paper color" nothing happens. I tried on pdf made in LO Writer. Other options for example: "change light and dark colors" or "revert colors" work. Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.61-1-MANJARO (64-bit) Graphics Platform: X11 Graphics Processor: NVA8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442051] Buttons with different heights
https://bugs.kde.org/show_bug.cgi?id=442051 --- Comment #2 from keyth_qcfx2 --- It happens to me with any amount of bundles or just the basic bundles that are undeletable. Resizing the UI is not needed to happen. There is not a scrollbar present if you look at the gif as the list size is smaller than the container. This is happening with how Krita is swapping the buttons in the UI I believe. there is a mismatching number between them (min and max) or perhaps the scaling method, that changes behavior when one of them leaves the spot. That or worse it fixed the font size and fonts in Linux and Windows have different sizing systems. They are more similar now but this not pixel perfect. or even more interesting your new icon requires a new size encasing when it is active but I doubt that. Either way something is hidden there and is clearly wrong. this should not take more than 2 minutes to check and fix the values. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405235] Slow startup and new file scan on low latency networks
https://bugs.kde.org/show_bug.cgi?id=405235 --- Comment #28 from Maik Qualmann --- Git commit 6545c2e25eb5f5104d2069f34ccc8b2d5d094273 by Maik Qualmann. Committed on 06/09/2021 at 17:50. Pushed by mqualmann into branch 'master'. added fast scan as an option in the settings M +2-1core/libs/database/collection/collectionscanner_scan.cpp M +3-0core/libs/metadataengine/engine/metaenginesettingscontainer.cpp M +1-0core/libs/metadataengine/engine/metaenginesettingscontainer.h M +47 -14 core/utilities/setup/setupmisc.cpp https://invent.kde.org/graphics/digikam/commit/6545c2e25eb5f5104d2069f34ccc8b2d5d094273 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441940] The string "Export Directory :" in Storyboard docker's Export SVG dialogue is untranslatable
https://bugs.kde.org/show_bug.cgi?id=441940 Tyson Tan changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441915] Some strings in Import Video Animation dialogue are untranslatable
https://bugs.kde.org/show_bug.cgi?id=441915 Tyson Tan changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441825] Stroke and Opaque in some brush engines need disambiguation
https://bugs.kde.org/show_bug.cgi?id=441825 Tyson Tan changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442086] New: Volume bar on obs breaks after raising maximum volume
https://bugs.kde.org/show_bug.cgi?id=442086 Bug ID: 442086 Summary: Volume bar on obs breaks after raising maximum volume Product: plasmashell Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: roma57li...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Turn on "Raise Maximum Volume" 2. Change volume to maximum (more than 100%) 3. Change volume with shortcuts such as Osd appears. OBSERVED RESULT Volume progress bar on obs is always on maximum, if volume less than 100% too. Icon changes right. Volume itself works and changes right. Also if turns "Raise Maximum Volume" off, progress bar still stays broken. It fixes after shell restart. EXPECTED RESULT Volume bar on obs should changes. SOFTWARE/OS VERSIONS Linux: 5.13.13-zen1-1-zen (64-bits) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Theme: Sweet Bug probably at plasma-workspace/shell/obs.cpp, line 45, on calling. maximum_percent must be not 100, but 150 if raising maximum volume turned on. -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 442085] New: The Snap package of Kwave is outdated.
https://bugs.kde.org/show_bug.cgi?id=442085 Bug ID: 442085 Summary: The Snap package of Kwave is outdated. Product: kwave Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: thomas.eschenbac...@gmx.de Reporter: beedellrokejulianlockh...@gmail.com Target Milestone: --- Created attachment 141339 --> https://bugs.kde.org/attachment.cgi?id=141339=edit Logs of subsequent invocation of kwave via Bash via Konsole. SUMMARY The snap for kwave (http://snapcraft.io/kwave) is very outdated. STEPS TO REPRODUCE 1. Execute "snap info kwave". OBSERVED RESULT "master+8a1ba28" is listed for "latest/edge", which may be older than the 18.04.1th version, whereas the 18.04.1th version is listed for the other open tracks. EXPECTED RESULT At least the 21.08.1th version should be submitted for all of the tracks. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419923] On dual screen setup (screen mirroring) the laptop screen sometimes has a time lag
https://bugs.kde.org/show_bug.cgi?id=419923 Gerold Jens Wucherpfennig changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Gerold Jens Wucherpfennig --- I have reactivated this laptop and updated all packages in Manjaro. I can not reproduce this bug anymore in Plasma 5.22. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 401898] Closing a tab is slow with something written on the prompt
https://bugs.kde.org/show_bug.cgi?id=401898 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/konsole/commit/3d967a |ities/konsole/commit/18dc0f |597472a75b2afbd75afb20d7f44 |de2b47b70ac65e4a0400ed0b79c |a3881f2 |12b1196 --- Comment #18 from Kurt Hindenburg --- Git commit 18dc0fde2b47b70ac65e4a0400ed0b79c12b1196 by Kurt Hindenburg, on behalf of Christoph Cullmann. Committed on 06/09/2021 at 16:35. Pushed by hindenburg into branch 'release/21.08'. improve session closing behavior the new session close behavior is again the old - first send SIGHUP and wait one second if that works - then hard kill before we tried to send an EOF character this needed workaround to not kill "non shell" programs unexpected and doesn't work e.g. if - you have some not finished command input in your shell - on e.g. FreeBSD in general When closing the session with some background process still running: - using Ctrl+D (which sends EOF) will leave that background process running (which is the expected behaviour with e.g. BASH: https://lists.gnu.org/archive/html/bug-bash/2009-03/msg00091.html) - using e.g. the close button on the titlebar will close the session and kill any background processes You can also use 'somecommand & disown', if you want to ensure background processes aren't killed when you close a konsole window. Related: bug 185140 (cherry picked from commit 3d967a597472a75b2afbd75afb20d7f44a3881f2) M +0-16 src/Pty.cpp M +0-5src/Pty.h M +7-18 src/session/Session.cpp https://invent.kde.org/utilities/konsole/commit/18dc0fde2b47b70ac65e4a0400ed0b79c12b1196 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 185140] Konsole should send EOF before closing tabs
https://bugs.kde.org/show_bug.cgi?id=185140 --- Comment #19 from Kurt Hindenburg --- Git commit 18dc0fde2b47b70ac65e4a0400ed0b79c12b1196 by Kurt Hindenburg, on behalf of Christoph Cullmann. Committed on 06/09/2021 at 16:35. Pushed by hindenburg into branch 'release/21.08'. improve session closing behavior the new session close behavior is again the old - first send SIGHUP and wait one second if that works - then hard kill before we tried to send an EOF character this needed workaround to not kill "non shell" programs unexpected and doesn't work e.g. if - you have some not finished command input in your shell - on e.g. FreeBSD in general When closing the session with some background process still running: - using Ctrl+D (which sends EOF) will leave that background process running (which is the expected behaviour with e.g. BASH: https://lists.gnu.org/archive/html/bug-bash/2009-03/msg00091.html) - using e.g. the close button on the titlebar will close the session and kill any background processes You can also use 'somecommand & disown', if you want to ensure background processes aren't killed when you close a konsole window. Related: bug 401898 (cherry picked from commit 3d967a597472a75b2afbd75afb20d7f44a3881f2) M +0-16 src/Pty.cpp M +0-5src/Pty.h M +7-18 src/session/Session.cpp https://invent.kde.org/utilities/konsole/commit/18dc0fde2b47b70ac65e4a0400ed0b79c12b1196 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442084] New: FR: Access to Display Configuration
https://bugs.kde.org/show_bug.cgi?id=442084 Bug ID: 442084 Summary: FR: Access to Display Configuration Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: lo...@b-vo.fr CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Have access to Display Configuration settings as an item in the right-click menu on the desktop. STEPS TO REPRODUCE 1. Right-click on the desktop OBSERVED RESULT No item allows to access Display Configuration settings EXPECTED RESULT Have an item to access Display Configuration settings SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Seems the item has to be added in "Standard Menu" app of which the C code is in plasma-workspace project under containmentactions --> contextmenu https://invent.kde.org/plasma/plasma-workspace/-/tree/master/containmentactions/contextmenu -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 Ingo Klöcker changed: What|Removed |Added CC||skna...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439958] Error in cryptographic signatures affixed by KMail
https://bugs.kde.org/show_bug.cgi?id=439958 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #12 from Ingo Klöcker --- I suspect the problem is caused by the protected headers feature in combination with the X-Face header. All examples with good signature were either made with a version of KMail that did not yet have the protected headers feature (openSUSE LEAP 15.3) or do not include an X-Face header (Manjaro, Artix in the morning). All other examples have a copy of the X-Face header in the signed message part. -- You are receiving this mail because: You are watching all bug changes.
