[kate] [Bug 454748] errors when starting kate from command line
https://bugs.kde.org/show_bug.cgi?id=454748 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 456634] Opening a module and then decreasing its width/height until it disappears will still show the module as being selected
https://bugs.kde.org/show_bug.cgi?id=456634 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com --- Comment #1 from Waqar Ahmed --- The only fix that I have in mind for this is completely removing this drag to close functionality. It offers little practical benefit. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453234] Kate crashes with specific tab and menu selections
https://bugs.kde.org/show_bug.cgi?id=453234 Waqar Ahmed changed: What|Removed |Added CC||akarshan.bis...@gmail.com --- Comment #9 from Waqar Ahmed --- *** Bug 457184 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457184] Kate crashes everytime when opening settings
https://bugs.kde.org/show_bug.cgi?id=457184 Waqar Ahmed changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||waqar@gmail.com --- Comment #2 from Waqar Ahmed --- *** This bug has been marked as a duplicate of bug 453234 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 435628] Crash trying to open a displaced closed folding marker
https://bugs.kde.org/show_bug.cgi?id=435628 Waqar Ahmed changed: What|Removed |Added Resolution|--- |FIXED CC||waqar@gmail.com Status|REPORTED|RESOLVED --- Comment #7 from Waqar Ahmed --- This has been fixed now in the way that Foldings are not restored if the document isn't exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457349] Crash upon pushing enter
https://bugs.kde.org/show_bug.cgi?id=457349 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Waqar Ahmed --- Your Kate and frameworks version is too old -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405923] crash on armv7 Illegal opcode
https://bugs.kde.org/show_bug.cgi?id=405923 fengyd2...@163.com changed: What|Removed |Added CC||fengyd2...@163.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393781] wallpaper cannot span multiple screens
https://bugs.kde.org/show_bug.cgi?id=393781 Fushan Wen changed: What|Removed |Added Status|ASSIGNED|CONFIRMED --- Comment #5 from Fushan Wen --- Feel free to submit a merge request. The original author of the MR above is unable to continue the work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454834] System Settings crashes on startup / can no longer use settings
https://bugs.kde.org/show_bug.cgi?id=454834 --- Comment #2 from edA-qa mort-ora-y --- Created attachment 151241 --> https://bugs.kde.org/attachment.cgi?id=151241=edit New crash information added by DrKonqi systemsettings5 (5.12.8) using Qt 5.9.5 Tried to start systemsettings5 -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f9cc8fe47f1 in __GI_abort () at abort.c:79 #8 0x7f9cc97b4fb7 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #11 0x7f9cc7e9cf8e in QQuickWidget::resizeEvent(QResizeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #12 0x7f9cca9f7be2 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454834] System Settings crashes on startup / can no longer use settings
https://bugs.kde.org/show_bug.cgi?id=454834 edA-qa mort-ora-y changed: What|Removed |Added CC||eda...@disemia.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457744] New: Opacity slider in pop-up palette brush editor is inaccurate
https://bugs.kde.org/show_bug.cgi?id=457744 Bug ID: 457744 Summary: Opacity slider in pop-up palette brush editor is inaccurate Product: krita Version: 5.1.0-RC1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: thetwo...@foxmail.com Target Milestone: --- Created attachment 151240 --> https://bugs.kde.org/attachment.cgi?id=151240=edit gif SUMMARY https://krita-artists.org/t/opacity-slider-in-pop-up-palette-brush-editor-is-inaccurate/45509 A user of Ka forum encountered this problem on 5.1 beta 2. I can confirm it on RC1. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 451506] (SEGV) Crash in NotificationInhibition::NotificationInhibition
https://bugs.kde.org/show_bug.cgi?id=451506 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #16 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443008] Cursor and brush do not line up. Cursor Brush Offset
https://bugs.kde.org/show_bug.cgi?id=443008 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 457202] crash on open
https://bugs.kde.org/show_bug.cgi?id=457202 --- 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 446604] Crash in ColorDialog
https://bugs.kde.org/show_bug.cgi?id=446604 --- Comment #27 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.
[kdeplasma-addons] [Bug 457743] New: Panel is being displayed when Application Dashboard is opened after clicking Show Desktop icon
https://bugs.kde.org/show_bug.cgi?id=457743 Bug ID: 457743 Summary: Panel is being displayed when Application Dashboard is opened after clicking Show Desktop icon Product: kdeplasma-addons Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: raninepa...@gmail.com Target Milestone: --- Created attachment 151239 --> https://bugs.kde.org/attachment.cgi?id=151239=edit Screenshot of Application Dashboard with panel being displayed SUMMARY When Application Dashboard is opened , it usually occupies full screen , but Panel is being displayed when Application Dashboard is opened after clicking Show Desktop icon. STEPS TO REPRODUCE 1. Switch from default Application Launcher to Application Dashboard. 2. Click on Show Desktop Icon. 3. Click on Plasma icon in the panel or press Meta Key on Keyboard for opening Application Dashboard. OBSERVED RESULT Panel is being displayed with Application Dashboard. EXPECTED RESULT Application Dashboard should have uniform behavior for being always full-screen without display of panel. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Kernel Version: 5.18.16-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3-7020U CPU @ 2.30GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: HP Product Name: HP Laptop 15-bs0xx -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457742] New: Plasmashell crashes when unlocking
https://bugs.kde.org/show_bug.cgi?id=457742 Bug ID: 457742 Summary: Plasmashell crashes when unlocking Product: plasmashell Version: 5.25.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: macr...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.16-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: Currently I have 4 monitors connected to my system, 3 at my desk and one located a distance away. They are set up such that when my right-most monitor is turned on, the three on my desk are enabled while the remote monitor is disabled and vice-versa. I am currently using X11 rather than Wayland despite using Fedora36 as any attempts to use wayland result in a much worse crash. To reproduce the crash all I need to do is lock the computer and leave it for long enough for the screens to go into sleep mode. Upon attempting to log in I will rarely be able to log in successfully, but more often than not I am presented with a button that says " unlock" but does nothing when pressed. To get logged in I then need to manually turn off the right-most screen and then turn it on again, which allows me to attempt to log in again on a different monitor, however this time it will let me in. Whether or not I log in on the first time I will see a notification from drkonqi that plasmashell has crashed, but the vast majority of the time drkonqi closes itself before I can save any information and fails to save any reference of the crash. It appears as though drkonqi closing coincides with plasmashell relaunching, but with this most recent crash drkonqi did not close. If I attempt to use wayland the system becomes unstable and I must switch to a terminal session and forcefully close any running programs on the session that has frozen before rebooting the system. All of my monitors are from different manufactureres, with my desk screens being manufactured by Dell, acer, and samsug, in order, left to right, while my leftmost screen is rotated 90 degrees to the left. The screens also have different resolutions, from left to right being 1080, 1440, and 2160. I am currently using an AMD Radeon VII as a GPU and have the 3 desktop monitors connected via display port. I attempted to ensure that all relevant debug symbols were installed when generating the trace, but still received a warning that some were missing, but I would be happy to provide any other information if necessary. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f66a80e8bd3 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () at /usr/lib64/qt5/qml/org/kde/kirigami.2/libKirigamiPlugin.so #5 0x7f66d6a258c6 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #6 0x7f66d683c155 in QFutureWatcherBase::event(QEvent*) () at /lib64/libQt5Core.so.5 #7 0x7f66d76b2d22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #8 0x7f66d69f2228 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #9 0x7f66d69f5594 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #10 0x7f66d6a43467 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #11 0x7f66d4d7bfaf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #12 0x7f66d4dd12c8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #13 0x7f66d4d79940 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #14 0x7f66d6a42f5a in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #15 0x7f66d69f0c7a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #16 0x7f66d69f8d42 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #17 0x5588a795b165 in main () [Inferior 1 (process 371019) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393781] wallpaper cannot span multiple screens
https://bugs.kde.org/show_bug.cgi?id=393781 Roy changed: What|Removed |Added CC||roy-orbi...@devo.net.au --- Comment #4 from Roy --- What if, rather than another Positioning option as proposed in the above MR, a boolean setting was added to span screens? It could be placed at the end of this form layout so it applies to all Positioning options: https://github.com/KDE/plasma-workspace/blob/0fa3bbc4c63e84d5902e0950e4fa0559fe1988cf/wallpapers/image/imagepackage/contents/ui/config.qml#L90 If set to true, make the calculation for the wallpaper based on the dimensions of the entire desktop, rather than the single screen, then crop it to that screen's portion of the desktop based on its x, y, w & h. The exception is the Tiled option where it could simply change the offsets. It looks like the necessary dimensions are exposed: https://doc.qt.io/qt-5/qscreen.html#virtualGeometry-prop and its virtualGeometryChanged signal would allow the wallpaper to be "re-sliced" upon layout changes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439911] Allow text input to applications that do not support text-input-v2 or v3
https://bugs.kde.org/show_bug.cgi?id=439911 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com --- Comment #7 from Chris --- (In reply to kel...@yahoo.com from comment #5) > (In reply to Thiago Sueto from comment #0) > > GNOME's virtual keyboard allows to show the virtual keyboard by swiping from > > the bottom edge upwards while keeping focus in the current window, and > > swiping from the top of the virtual keyboard downwards hides the keyboard. > > > > The first works around misbehaving apps who do not cooperate with virtual > > keyboards and never show them even if running natively on wayland (like > > Chrome/ium). > > > > With Maliit only the second action is possible. > > > > My first instinct is that this could be implemented as another action in the > > Touchscreen KCM. This also seems like consistent behavior in case the user > > wants to hide the keyboard to see the whole screen before getting back to > > writing, but perhaps this is best implemented in maliit itself. > > Thiago, you are on a roll! This is the thing I've quoted you on today. > > This is the only major issue that I have with Plasma Wayland right now on my > Surface Pro 4 tablet. There are several applications that I need/want to use > that Maliit won't work with, forcing me to connect an external keyboard, or > log into GNOME Wayland. Those applications include, but are not limited, > Spotify, OpenRocket, MATLAB, Chrome Web Browser, Discord, Bluejeans, and > Steam, to name a few. Firefox is really the only non-Qt/Plasma application > that I use that works with the virtual keyboard, which is a real letdown. I > like Maliit, but compared to the Qt Virtual Keyboard, Onboard (on Xorg), and > GNOME's virtual keyboard it's too limited. I don't know what trickery the > GNOME folks are using, but EVERY application works with their virtual > keyboard in Wayland. Maybe your input folks might want to talk to their > input folks? There is another point to consider, most applications rely on keyboard shortcuts, and Maliit does not provide them, and hence it is basically useless: you have a keyboard, that does output text, but that can't really interact with your application. So you have to plug an external keyboard and Maliit becomes useless. For example, Okular requires Ctrl+Shift+F to leave full screen mode, or alternatively an external mouse with a proper right click, but if you have one you probably have an external keyboard too. For the time being I had to switch to Gnome with this keyboard: https://extensions.gnome.org/extension/4413/improved-osk/ I also had opportunities for glimpses at Squeekboard when I tried Phosh, and the layout seemed nice. Maliit only allows for text, it does not allow to operate the applications: what good is text if you can't use the applications it's meant for. For the present Maliit is the only offer for kde users, and it's hindering the whole experience. We could wish applications would work with only a touch screen and a keyboard allowing for text only and emoji, but it is not the case. -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 457477] Can't add timer
https://bugs.kde.org/show_bug.cgi?id=457477 --- Comment #3 from Devin Lin --- Hmm, that's weird, I am currently unable to reproduce this on my laptop with Manjaro. Your package versions seem to be correct, I am not totally sure why this is happening... Does this occur if you try the Flatpak version? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 457741] New: Konquer browser crashed on opening a URL in the konsole
https://bugs.kde.org/show_bug.cgi?id=457741 Bug ID: 457741 Summary: Konquer browser crashed on opening a URL in the konsole Product: konqueror Version: 21.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: ronald.holshau...@gmail.com Target Milestone: --- Application: konqueror (21.12.3) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-43-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Ran a build that created a test failure report and printed the URL to the report in the console. CTRL clicked on the URL, and that led to the crash. Output in console: * What went wrong: Execution failed for task ':provider:junit5spring:test'. > There were failing tests. See the report at: > file:///home/ronald/Development/Projects/Pact/pact-jvm/provider/junit5spring/build/reports/tests/test/index.html Clicked on the link above multiple times, each click resulted in the crash. The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139767521692096) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139767521692096) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139767521692096, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f1e301b3476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f1e301997f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f1e2e095ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f1e2dce4e95 in ?? () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #11 0x7f1e2dce51ff in ?? () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #12 0x7f1e2dce58f6 in QQuickWidget::showEvent(QShowEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #13 0x7f1e1ae8b5c8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5 #14 0x7f1e2efa24ee in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f1e2ef5f713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f1e2e2bee2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f1e2ef9ee47 in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f1e2ef9eda9 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f1e2ef9ee23 in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f1e2efa1fe3 in QWidgetPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f1e2ef9ed89 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f1e2ef9ee23 in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f1e2ef9eda9 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f1e2ef9ee23 in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f1e2ef9eda9 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f1e2ef9ee23 in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f1e2efa1fe3 in QWidgetPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f1e2ef9ed89 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f1e2ef9ee23 in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f1e2ef9eda9 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7f1e2ef9ee23 in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7f1e2efa1fe3 in QWidgetPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7f1e3045058a in ?? () from /lib/x86_64-linux-gnu/libkdeinit5_konqueror.so #34 0x7f1e304531a7 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_konqueror.so #35 0x7f1e3019ad90 in __libc_start_call_main (main=main@entry=0x55e97bfaa060, argc=argc@entry=4, argv=argv@entry=0x7fff0c2fff98) at ../sysdeps/nptl/libc_start_call_main.h:58 #36 0x7f1e3019ae40 in __libc_start_main_impl (main=0x55e97bfaa060, argc=4, argv=0x7fff0c2fff98, init=, fini=, rtld_fini=, stack_end=0x7fff0c2fff88) at ../csu/libc-start.c:392 #37
[kwin] [Bug 445240] Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue
https://bugs.kde.org/show_bug.cgi?id=445240 --- Comment #3 from Alex Folland --- OK, I've tried both of those commands. Here are the logs from them. from `XDG_SESSION_TYPE=wayland dbus-run-session kwin_wayland --exit-with-session=konsole` ``` kf.service.services: The desktop entry file "/usr/share/applications/kcm_krunnersettings.desktop" has Type= "Application" but no Exec line kf.service.sycoca: Invalid Service : "/usr/share/applications/kcm_krunnersettings.desktop" kf.service.services: The desktop entry file "/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line kf.service.sycoca: Invalid Service : "/usr/share/applications/qemu.desktop" dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=2172192 comm="startplasma-wayland --exit-with-session=konsole") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activating service name='org.freedesktop.systemd1' requested by ':1.3' (uid=1000 pid=2172221 comm="/usr/bin/kwin_wayland_wrapper --xwayland") dbus-daemon[2172191]: [session uid=1000 pid=2172191] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 kdeinit5: preparing to launch '/usr/lib/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 2172230, result = 0 (kwin_wayland:217): Gtk-WARNING **: 18:13:45.725: cannot open display: (kwin_wayland:2172233): Gtk-WARNING **: 18:13:45.810: cannot open display: (kwin_wayland:2172234): Gtk-WARNING **: 18:13:45.887: cannot open display: (kwin_wayland:2172235): Gtk-WARNING **: 18:13:45.964: cannot open display: (kwin_wayland:2172236): Gtk-WARNING **: 18:13:46.039: cannot open display: (kwin_wayland:2172237): Gtk-WARNING **: 18:13:46.116: cannot open display: (kwin_wayland:2172240): Gtk-WARNING **: 18:13:46.200: cannot open display: (kwin_wayland:2172241): Gtk-WARNING **: 18:13:46.281: cannot open display: (kwin_wayland:2172242): Gtk-WARNING **: 18:13:46.378: cannot open display: (kwin_wayland:2172243): Gtk-WARNING **: 18:13:46.462: cannot open
[frameworks-kglobalaccel] [Bug 457387] Compose Key only works in certain applications
https://bugs.kde.org/show_bug.cgi?id=457387 --- Comment #6 from Lucas <0lc6wm...@mozmail.com> --- I like using caps lock but I tried a variety of keys and observed the same behaviour. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457102] Eject / Unmount icon is invisible
https://bugs.kde.org/show_bug.cgi?id=457102 tcb...@protonmail.com changed: What|Removed |Added CC||tcb...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] bad keyboard layout counts
https://bugs.kde.org/show_bug.cgi?id=457550 David Chmelik changed: What|Removed |Added Summary|Option to not switch|bad keyboard layout counts |layouts on click; require | |the use of the context menu | |to switch with a pointing | |device | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457550] Option to not switch layouts on click; require the use of the context menu to switch with a pointing device
https://bugs.kde.org/show_bug.cgi?id=457550 --- Comment #7 from David Chmelik --- (In reply to Andrey from comment #5) > I think we could remove min two main layouts restriction as I can't recall > if it gives us any real benefits. Such number of minimum to (possible/past) maximum layouts are the issue (as in original bug description/title) and minimum two main ones has only ever been hindrance for me and everyone I know. When labels could be flags only without text it was exacerbated due to dialects: no way knowing one is using their country's English or international layout only for dialect/characters elsewhere (unfortunately requiring same flag). For that case for average users who forget, they accidentally press it and don't notice anything until things start going wrong. They use Wayland, but I don't; proper technical writing is full term then define acronym afterwards, but anything 'on layout change' is zero help if a user comes to a PC after change was made. I've always only known main layouts as those not allowing drop-down and spare layouts as those requiring; this issue never has primarily been about drop-down which is only an effect of specific numbers of layouts. Rewriting the issue to a derived aspect is over-simplification but in fact complication. I never asked to require drop-down for main layouts, just that being forced to have two minimum (and any maximum other than all) is a bad number (as described and not everyone is bilingual nor necessarily even uses more than one dialect) (so I won't be writing a duplicate report what I already very clearly put as first part of original description/title). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436174] Feature Request: Shortcuts for horizontal timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=436174 acidrums4 changed: What|Removed |Added CC||acidrums4+st...@gmail.com --- Comment #4 from acidrums4 --- Not really sure if this is the place to say this or if I should open a new bug, but I wish the timeline supports scrolling with a horizontal mouse wheel, i.e. I have a mouse with one of those and now intuitively use it to scroll horizontally on most KDE stuff but now that I needed to edit a video that ability is notoriously lacking in kdenlive. Which is a bummer, 'cause the only way I found was clicking the scroll handle and dragging it, zooming in/out (!) or directly setting a time in the timeline monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457708] Lost the ability to display the layout's label on top of the flag
https://bugs.kde.org/show_bug.cgi?id=457708 --- Comment #2 from David Chmelik --- (In reply to Nate Graham from comment #1) > The ability to set a custom label is still there, it just moved into System > Settings Label doesn't mean only plaintext but its entire area including all other text/graphics (see typical labels in clothes, on food packages, etc.). > Any specific reason you want it back? Already stated can be re-added (bug 444864) after new report. Only flags are quickly-noticeable but, due to dialects, useless/hindrance on their own; black on grey (or dark themes maybe unreadable black on dark grey) isn't noticeable, so without both (or everything custom for dialects) it takes longer before users notice/recall which layout is set. It's comically absurd to create things users use and then remove them and then ask use case (happening since KDE3's end and indicates critical problems in a project). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453054] MYPAINT:Missing "dab per basic radius"
https://bugs.kde.org/show_bug.cgi?id=453054 thetwo changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from thetwo --- These three parameters are opposite to "space". The larger the value, the closer the DAB is. If they are all 0, the brush will not be able to draw. Because three of them work at the same time, the other two need to be turned off during the test. I think the difference between "basic radius" and "actual radius" is whether the radius changes. "Basic radius" should only refer to basic values. https://ufile.io/e2lqh7px I made the brushs and added the hue change. You can download it from the link above. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457379] Task Manager (not icons-only version ) icon size undesirably increased when widget is located on ≥ 40px thickness vertical panel
https://bugs.kde.org/show_bug.cgi?id=457379 --- Comment #13 from loca...@tutanota.com --- Also, if I set the panel width to 800px (eight hundred px) the Task Manager icons strangely become smaller and the Task Manager *vertically* starts to look the way it did before the change. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457739] Okular handbook confused on annotations
https://bugs.kde.org/show_bug.cgi?id=457739 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- No, that sentence can not be removed, but there's defenitely a wording issue. Would you understand it better if it said " This option may be disabled if the current document does not allow removing annotations. " ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 430724] "Devices" section is missing from places panel while Gparted is running
https://bugs.kde.org/show_bug.cgi?id=430724 Patrick Silva changed: What|Removed |Added CC||sto...@stoned.io --- Comment #8 from Patrick Silva --- *** Bug 457736 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457736] Devices Panel Empty When gParted open in background!
https://bugs.kde.org/show_bug.cgi?id=457736 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 430724 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457740] Main screen area displayed over external monitor
https://bugs.kde.org/show_bug.cgi?id=457740 --- Comment #2 from piotr.juzw...@pm.me --- Created attachment 151238 --> https://bugs.kde.org/attachment.cgi?id=151238=edit "Drag and drop" setting used -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457740] Main screen area displayed over external monitor
https://bugs.kde.org/show_bug.cgi?id=457740 --- Comment #1 from piotr.juzw...@pm.me --- Created attachment 151237 --> https://bugs.kde.org/attachment.cgi?id=151237=edit Another picture of the issue -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457740] New: Main screen area displayed over external monitor
https://bugs.kde.org/show_bug.cgi?id=457740 Bug ID: 457740 Summary: Main screen area displayed over external monitor Product: KScreen Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: piotr.juzw...@pm.me Target Milestone: --- Created attachment 151236 --> https://bugs.kde.org/attachment.cgi?id=151236=edit Picture of laptop and monitors in tthe background showing overlapping area. 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. In a multimonitor scenario drag the "main" screen over the external monitors so they overlap 2. The main screen's area is displayed over the external screen's area 3. OBSERVED RESULT The laptop's area is displayed/rendered on the external monitor(s) EXPECTED RESULT I would imagine it shouldn't display/render laptop's "area" on the external monitors SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96 Qt Version: 5.15.5 ADDITIONAL INFORMATION Using amdgpu, connecting to monitors via USB-C to DP cable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455532] kwin_wayland_drm: Failed to find a working setup for new outputs!
https://bugs.kde.org/show_bug.cgi?id=455532 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/978fbd276366 ||ab59cb7190778cf9521e5f2ff63 ||c Version Fixed In||5.25.5 Status|REPORTED|RESOLVED --- Comment #26 from Nate Graham --- Great! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457739] New: Okular handbook confused on annotations
https://bugs.kde.org/show_bug.cgi?id=457739 Bug ID: 457739 Summary: Okular handbook confused on annotations Product: okular Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: skierp...@gmail.com Target Milestone: --- SUMMARY I tried to remove a text annotation I made, and couldn't (because I wasn't in Browse mode). I read the "Annotations" section of the Okular handbook (Help > Okular Handbook and at https://docs.kde.org/trunk5/en/okular/okular/annotations.html ), and it has misleading Notes that indicate annotations don't work e.g. "document does not allow removing annotations". STEPS TO REPRODUCE 1. Open a document with text annotations. 2. Switch to some Tool/mouse mode other than Browse such as Tools > Text Selection or annotation > Typewriter. 3. Try to delete a text annotation. 4. Read the Okular Handbook. OBSERVED RESULT The Annotations chapter's introduction says Note Due to DRM limitations (typically with PDF documents), adding, editing some properties or removing annotations could not be possible. "Removing Annotations" says Note This option could not be enabled because the document does not allow removing annotations. But in fact you can remove annotations fine so long as you are in Tools > Browse mode. EXPECTED RESULT Clearer documentation. The annotation chapter should either prominently say you need to be using the Browse tool/mode to edit, adjust properties of, or remove annotations, or add this step to all instructions to click; and it should explain the limitations of DRM documents better. I don't know the preferred terminology (Browse mode? Browse tool?) and this is incomplete, but the following changes would improve the handbook: In the Tools Menu chapter, change the section on Browse from: The mouse will have its normal behavior, for dragging the document and following links and for adding bookmarks and fit to width. to something like: The mouse will have its normal behavior: for dragging the document, following links, and selecting annotations; and for adding bookmarks, fit to width, and opening a context menu for annotations. In the Annotations chapter, change to: Note It may not be possible to add, edit, or remove annotations in some documents (typically PDF documents) due to DRM limitations. ... To edit an annotation, switch to the Browse tool (Tools Browse), then click on it with the right mouse button and select Properties ... To remove an annotation, switch to the Browse tool (Tools Browse). Then either click on it with the , ... Remove the note "This option could not be enabled because..." altogether. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version:5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15 on Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455532] kwin_wayland_drm: Failed to find a working setup for new outputs!
https://bugs.kde.org/show_bug.cgi?id=455532 Marco Rebhan changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #25 from Marco Rebhan --- (In reply to Zamundaaa from comment #24) > Does the patch only fix the specific crash you mentioned, or is the session > working properly now? Yep, the session is working properly now. It also isn't segfaulting anymore when I change tty. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 449234] I'm getting a code 100 error every time I try to open a directory through a program or my super menu, after switching from XFCE
https://bugs.kde.org/show_bug.cgi?id=449234 --- Comment #18 from Mike --- Looks like I was able to resolve the issue by removing any line that mentions "exo" from files within: ~/.local/share/applications For example: exo-file-manager.desktop:Exec=exo-open --launch FileManager %u mimeapps.list:x-scheme-handler/file=exo-file-manager.desktop -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 457738] New: Hangs on "Requesting passphrase" step of generating new key
https://bugs.kde.org/show_bug.cgi?id=457738 Bug ID: 457738 Summary: Hangs on "Requesting passphrase" step of generating new key Product: kgpg Version: 22.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@opensource.sf-tec.de Reporter: gabek...@fastmail.com Target Milestone: --- Application: kgpg (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.15-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: I am unable to generate a new key, as the application hangs on the "Requesting passphrase" step of creation (as seen in the desktop notification) Steps to reproduce: * Launch kgpg (either through command line or KDE desktop) * Keys > New Keypair * Follow all prompts and enter options (non expert) * Enter passphrase, hit next * Notification continues to spin, no progress is made The crash can be reproduced every time. -- Backtrace: Application: KGpg (kgpg), signal: Segmentation fault [KCrash Handler] #4 0x0040 in ?? () #5 0x7f3351356186 in QMainWindowLayout::statusBar (this=) at widgets/qmainwindowlayout.cpp:2363 #6 0x7f3351350e89 in QMainWindow::statusBar (this=this@entry=0x555d6fb5e120) at widgets/qmainwindow.cpp:586 #7 0x555d6f738a42 in KeysManager::changeMessage (keep=false, msg=..., this=0x555d6fb5e120) at /usr/src/debug/kgpg-22.04.3-1.1.x86_64/keysmanager.cpp:558 #8 KeysManager::slotGenerateKeyDone (this=0x555d6fb5e120, job=0x555d700319e0) at /usr/src/debug/kgpg-22.04.3-1.1.x86_64/keysmanager.cpp:568 #9 0x7f3350681e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffd3a56d190, r=0x555d6fb5e120, this=0x555d6fdea210) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x555d700319e0, signal_index=6, argv=0x7ffd3a56d190) at kernel/qobject.cpp:3886 #11 0x7f335067b22f in QMetaObject::activate (sender=sender@entry=0x555d700319e0, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd3a56d190) at kernel/qobject.cpp:3946 #12 0x7f3351a51615 in KJob::result (this=this@entry=0x555d700319e0, _t1=, _t1@entry=0x555d700319e0, _t2=...) at /usr/src/debug/kcoreaddons-5.96.0-1.1.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633 #13 0x7f3351a557cb in KJob::finishJob (this=0x555d700319e0, emitResult=) at /usr/src/debug/kcoreaddons-5.96.0-1.1.x86_64/src/lib/jobs/kjob.cpp:98 #14 0x7f3350681e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffd3a56d2c0, r=0x555d700319e0, this=0x555d700355a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #15 doActivate (sender=0x555d6fe004b0, signal_index=3, argv=0x7ffd3a56d2c0) at kernel/qobject.cpp:3886 #16 0x7f335067b22f in QMetaObject::activate (sender=, m=m@entry=0x555d6f7b2e20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd3a56d2c0) at kernel/qobject.cpp:3946 #17 0x555d6f712b21 in KGpgTransaction::done (_t1=, this=) at /usr/src/debug/kgpg-22.04.3-1.1.x86_64/build/kgpg_lib_autogen/HHLLV3HBLL/moc_kgpgtransaction.cpp:159 #18 KGpgTransactionPrivate::processDone (this=0x555d6ffe59d0) at /usr/src/debug/kgpg-22.04.3-1.1.x86_64/transactions/kgpgtransactionprivate.cpp:308 #19 0x7f3350681e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffd3a56d380, r=0x555d6ffe59d0, this=0x555d6ffe6590) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 doActivate (sender=0x555d7002d990, signal_index=20, argv=0x7ffd3a56d380) at kernel/qobject.cpp:3886 #21 0x7f3350681e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffd3a56d4a0, r=0x555d7002d990, this=0x555d70035870) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #22 doActivate (sender=0x555d7002d990, signal_index=11, argv=0x7ffd3a56d4a0) at kernel/qobject.cpp:3886 #23 0x7f335067b22f in QMetaObject::activate (sender=sender@entry=0x555d7002d990, m=m@entry=0x7f3350920480, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd3a56d4a0) at kernel/qobject.cpp:3946 #24 0x7f33505b6758 in QProcess::finished (this=this@entry=0x555d7002d990, _t1=, _t2=) at .moc/moc_qprocess.cpp:339 #25 0x7f33505bc1a3 in QProcessPrivate::_q_processDied (this=this@entry=0x7f334400e270) at io/qprocess.cpp:1184 #26 0x7f33505c0ac5 in QProcessPrivate::waitForFinished (this=0x7f334400e270, msecs=3) at io/qprocess_unix.cpp:878 #27 0x7f33505b7db5 in QProcess::waitForFinished (this=this@entry=0x555d7002d990, msecs=, msecs@entry=3) at io/qprocess.cpp:1930 #28 0x7f33505b86ed in QProcess::~QProcess (this=this@entry=0x555d7002d990, __in_chrg=) at io/qprocess.cpp:1266 #29 0x7f3351a569ac in KProcess::~KProcess (this=, this=) at
[frameworks-kio] [Bug 449234] I'm getting a code 100 error every time I try to open a directory through a program or my super menu, after switching from XFCE
https://bugs.kde.org/show_bug.cgi?id=449234 Mike changed: What|Removed |Added CC||mike.ben...@gmail.com --- Comment #17 from Mike --- I recently upgraded from Ubuntu 20.04 to 22.04 (KDE: 5.92 ) and I'm seeing the same problem. $XDG_CURRENT_DESKTOP=KDE But when I try to open files (ie: view downloaded images from Chrome), or even open the "Home" icon my desktop, I get an error: Unknown error code 100 Could not find the program 'exo-open' $ xdg-mime query default inode/directory org.kde.dolphin.desktop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457379] Task Manager (not icons-only version ) icon size undesirably increased when widget is located on ≥ 40px thickness vertical panel
https://bugs.kde.org/show_bug.cgi?id=457379 --- Comment #12 from loca...@tutanota.com --- > But I can reproduce the issue of the icons being too large starting at 40px > thickness. Is it the same for you? Kind of. I think the icon size at 20-25px is how the icons looked before the change. -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 457737] New: Version 20.12.1 (Debian 11 Bullseye), Syntax(?) or character set trouble in German translation -> comma unknown
https://bugs.kde.org/show_bug.cgi?id=457737
Bug ID: 457737
Summary: Version 20.12.1 (Debian 11 Bullseye), Syntax(?) or
character set trouble in German translation -> comma
unknown
Product: kturtle
Version: unspecified
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: c...@kde.nl
Reporter: j.hel...@gnubux.de
Target Milestone: ---
Created attachment 151235
--> https://bugs.kde.org/attachment.cgi?id=151235=edit
Screenshot
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. Use Kturtle with German script language.
2. Enter a function that takes more than one parameter like:
lerne rechteck $x, $y {
wiederhole 2 {
vorwärts $x
rechtsdrehen 90
vorwärts $y
rechtsdrehen 90 }
}
OBSERVED RESULT
Error message: line 1 - "," was not understood - source code 100
EXPECTED RESULT
Evaluate the function and recognize the comma like you do with the English
script language.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Debian 11 Bullseye (Gnome)
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
I tried two utf-8 variants ff0c an 2c unfortunately with the same result.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 457736] New: Devices Panel Empty When gParted open in background!
https://bugs.kde.org/show_bug.cgi?id=457736 Bug ID: 457736 Summary: Devices Panel Empty When gParted open in background! Product: dolphin Version: 21.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: sto...@stoned.io CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If gParted is open in background, Dolphin fails to enumerate/show disks/devices on side panel STEPS TO REPRODUCE Open Dolphin. You will see Devices panel on left, with local disks. Close Dolphin. Open `sudo gparted` Open Dolphin. You will see Devices panel on left is empty, does not show disks/devices any longer. Close Dolphin. Close gParted. Start Dolphin. Now the devices/disks are showing up again. OBSERVED RESULT If gParted is open in background, Dolphin fails to enumerate/show disks/devices on side panel EXPECTED RESULT If gParted is open in background, Dolphin should still continue to show devices/partitions. This does not happen in KDE Partition Manager, but only if gParted is open. SOFTWARE/OS VERSIONS Ubuntu 22.04 LTS latest updates Linux/KDE Plasma: 5.24.2 KDE Plasma Version: KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457675] AboutItem freezes with certain font/content combinations
https://bugs.kde.org/show_bug.cgi?id=457675 Connor Carney changed: What|Removed |Added Attachment #151226|0 |1 is obsolete|| --- Comment #7 from Connor Carney --- Created attachment 151234 --> https://bugs.kde.org/attachment.cgi?id=151234=edit formlayout-freeze-notosans Here's a case that freezes for me with Noto Sans. It's interesting that Noto Sans is much less prone to this issue than the Ubuntu font. I could find cases for Ubuntu by just randomly typing stuff; with Noto Sans I had to actually write a script to find one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457735] New: Low fps on the secondary display when playing games
https://bugs.kde.org/show_bug.cgi?id=457735 Bug ID: 457735 Summary: Low fps on the secondary display when playing games Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: rob.tet...@outlook.com Target Milestone: --- SUMMARY When playing a game on that display the framerate is bad even though the game is reporting 60fps. When I run the same game at the same settings on the internal laptop display everything works as expected. OBSERVED RESULT Kwin has trouble running games on the external monitor smoothly - mangohud reports 62fps but the gameplay feels more like 30. This issue disappears when running the game on the internal laptop screen. EXPECTED RESULT KWin should run the game same way on the external display like on the internal display. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 36 (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Device: Lenovo Yoga Slim 7 ProX 14IAH7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457734] New: Freeze upon disconnecting primary display
https://bugs.kde.org/show_bug.cgi?id=457734 Bug ID: 457734 Summary: Freeze upon disconnecting primary display Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: rob.tet...@outlook.com 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 *** I am using eGPU but it is still present when the eGPU is unplugged. KWin freezes when a display set as primary is disconnected. The Kwin should recognize this and adjust remaining displays accordingly. STEPS TO REPRODUCE 1. Connect external monitor 2. Change the external monitor to primary 3. Disconnect the monitor OBSERVED RESULT Freeze upon disconnecting the primary monitor. EXPECTED RESULT KWin should logically change different available monitor to primary and adjust according to that to avoid crash/freeze. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 36 (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Device: Lenovo Yoga Slim 7 ProX 14IAH7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457733] New: Tablet just makes scribbles
https://bugs.kde.org/show_bug.cgi?id=457733 Bug ID: 457733 Summary: Tablet just makes scribbles Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: All Status: REPORTED Severity: critical Priority: NOR Component: Tablets (tablet issues are only very rarely bugs in Krita!) Assignee: krita-bugs-n...@kde.org Reporter: zoteb...@gmail.com Target Milestone: --- Created attachment 151233 --> https://bugs.kde.org/attachment.cgi?id=151233=edit The result of trying to draw using my tablet 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. Start Krita 2. Use Graphics Tablet 3. Get nothing but scribbles OBSERVED RESULT You get nothing but scribbles EXPECTED RESULT It draws normally SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I'm using a Veikk VK1200. I 100% know it's an issue with Krita because the tablet works normal on all other art software. I've also configured and reconfigured the Driver as much as I can and it does absolutely nothing to help. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448609] Duplicated applets under Plasma system service of Shortcuts KCM
https://bugs.kde.org/show_bug.cgi?id=448609 matthias.schru...@freenet.de changed: What|Removed |Added CC||matthias.schrumpf@freenet.d ||e --- Comment #18 from matthias.schru...@freenet.de --- Is there a known solution to this problem? I ran into the same issue after setting my desktop layout back to default (Breeze). I tried deleting both kglobalshortcutsrc and plasma-org.kde.plasma.desktop-appletsrc to no avail. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457379] Task Manager (not icons-only version ) icon size undesirably increased when widget is located on ≥ 40px thickness vertical panel
https://bugs.kde.org/show_bug.cgi?id=457379 --- Comment #11 from Nate Graham --- Right, text doesn't start appearing until it's thicker. But I can reproduce the issue of the icons being too large starting at 40px thickness. Is it the same for you? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457379] Task Manager (not icons-only version ) icon size undesirably increased when widget is located on ≥ 40px thickness vertical panel
https://bugs.kde.org/show_bug.cgi?id=457379 --- Comment #10 from loca...@tutanota.com --- Glad it got sorted out. > ≥ 40px thickness vertical panel In my case the panel width is 200px. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 457717] Spectacle screenshots itself
https://bugs.kde.org/show_bug.cgi?id=457717 Dan Duris changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457379] Task Manager (not icons-only version ) icon size undesirably increased when widget is located on ≥ 40px thickness vertical panel
https://bugs.kde.org/show_bug.cgi?id=457379 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457379] Task Manager (not icons-only version ) icon size undesirably increased when widget is located on ≥ 40px thickness vertical panel
https://bugs.kde.org/show_bug.cgi?id=457379 Nate Graham changed: What|Removed |Added Summary|After upgrading from KDE|Task Manager (not |plasma v5.24.4 to v5.25.3, |icons-only version ) icon |the size of icons on the|size undesirably increased |3rd-party Task Manager v4.0 |when widget is located on ≥ |widget has doubled |40px thickness vertical ||panel Keywords||regression Resolution|DOWNSTREAM |--- Severity|normal |minor Status|RESOLVED|REPORTED CC||niccolo.venera...@gmail.com ||, qydwhotm...@gmail.com --- Comment #9 from Nate Graham --- Oh my mistake, when you said you were using "Task Manager v4.0" I assumed that was a 3rd-party widget since nobody really uses that name for the default one. I can confirm the issue when using a traditional Task Manager on a vertical panel. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457732] New: Opening bottom panel widgets while OSK is open moves them to top of screen
https://bugs.kde.org/show_bug.cgi?id=457732 Bug ID: 457732 Summary: Opening bottom panel widgets while OSK is open moves them to top of screen Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: dobey.p...@gmail.com Target Milestone: --- Created attachment 151232 --> https://bugs.kde.org/attachment.cgi?id=151232=edit Screenshot showing issue SUMMARY When the OSK is open, if one clicks on a widget on the bottom panel, such as clock, network, kickoff, etc… the widget window will be pushed to the top of the screen, rather than sticking to the bottom panel as expected. STEPS TO REPRODUCE 1. Open konsole or similar, and focus to ensure on screen keyboard is open. 2. Click on clock in bottom panel. OBSERVED RESULT Widget window is opened at top of screen. EXPECTED RESULT Widget window is aligned to bottom panel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon unstable KDE Plasma Version: neon unstable KDE Frameworks Version: neon unstable Qt Version: neon unstable Screenshot is from Plasma 5.23 on Steam Deck, but I have also reproduced on neon unstable in a VM. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457379] After upgrading from KDE plasma v5.24.4 to v5.25.3, the size of icons on the 3rd-party Task Manager v4.0 widget has doubled
https://bugs.kde.org/show_bug.cgi?id=457379 --- Comment #8 from loca...@tutanota.com --- > Whoever developed your 3rd-party Task Manager fork. Eike Hein was the > developer of the built-in Task manager widget, but he's not active in Plasma > development anymore. I was under impression that I was using one of the built-in Task Manager widgets (the other one is Icons-Only Task Manager), I didn't download anything special. On the "About" tab of the Task Manager I'm using it shows the following URL https://userbase.kde.org/Plasma/Tasks and lists Hein h...@kde.org as the contact. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 457731] Vault still appears in list after deleting it
https://bugs.kde.org/show_bug.cgi?id=457731 Ivan Čukić changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456825] Multiple monitors: virtual keyboard opens on wrong monitor
https://bugs.kde.org/show_bug.cgi?id=456825 Rodney Dawes changed: What|Removed |Added CC||dobey.p...@gmail.com --- Comment #3 from Rodney Dawes --- I don't think window system matters in this case, and this is an issue in maliit itself, as it only uses the primary screen. I'm also not sure what the best way to solve this would be, yet, as it was designed around single screen phone/tablet use case and not for multiple monitors on traditional PC setup use case. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] System monitor pie chart scaling error with non-zero manual data range
https://bugs.kde.org/show_bug.cgi?id=457248 --- Comment #9 from Roman Lebedev --- https://invent.kde.org/frameworks/kquickcharts/-/merge_requests/46 I haven't touched multi-item source handling, i don't really understand how it's supposed to behave, and i think it might not be handled correctly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452960] No mouse cursor in OBS window capture
https://bugs.kde.org/show_bug.cgi?id=452960 Nate Graham changed: What|Removed |Added Version Fixed In||5.26 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 457731] New: Vault still appears in list after deleting it
https://bugs.kde.org/show_bug.cgi?id=457731 Bug ID: 457731 Summary: Vault still appears in list after deleting it Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: robloka...@gmail.com Target Milestone: --- SUMMARY After deleting the vault through Configure -> Delete, the vault still appears in the vault list but cannot be interacted with. STEPS TO REPRODUCE 1. Create a vault 2. Delete the vault by going to Configure -> Delete OBSERVED RESULT The vault stays in the list and it cannot be clicked on. EXPECTED RESULT After deleting the vault, no trace of it is left on my system. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.0-43-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Deleting the [EncryptedDevices] entry and [old_vault_path_directory] section in ~/.config/plasmavaultrc and logging back into Plasma solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 436480] Deleting folded lines does not remove code folding marker
https://bugs.kde.org/show_bug.cgi?id=436480 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/commit/2 ||8d9cbc32fdda5ced60626c0487d ||d69c7f5a8b49 --- Comment #2 from Christoph Cullmann --- Git commit 28d9cbc32fdda5ced60626c0487dd69c7f5a8b49 by Christoph Cullmann, on behalf of Waqar Ahmed. Committed on 10/08/2022 at 20:02. Pushed by cullmann into branch 'master'. Update folding ranges on text modification M +28 -0src/buffer/katetextfolding.cpp M +2-0src/buffer/katetextfolding.h M +1-0src/view/kateview.cpp https://invent.kde.org/frameworks/ktexteditor/commit/28d9cbc32fdda5ced60626c0487dd69c7f5a8b49 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457583] Selecting search field on touch screen does not open virtual keyboard
https://bugs.kde.org/show_bug.cgi?id=457583 --- Comment #5 from Nate Graham --- I can reproduce it on my Lenovo ThinkPad X1 Yoga while in touch mode. The virtual keyboard appears correctly for other text fields, so there's something wrong with the WindowHeap-based effects here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457583] Selecting search field on touch screen does not open virtual keyboard
https://bugs.kde.org/show_bug.cgi?id=457583 Rodney Dawes changed: What|Removed |Added CC||dobey.p...@gmail.com --- Comment #4 from Rodney Dawes --- Is this on a MS Surface device? Or some other device? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 390830] Files in plasma vault indexed and available when the vault is closed
https://bugs.kde.org/show_bug.cgi?id=390830 robloka...@gmail.com changed: What|Removed |Added CC||robloka...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 384459] Text folding becomes invalid after file external update
https://bugs.kde.org/show_bug.cgi?id=384459 Christoph Cullmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/commit/e ||4e165278048fe11c5c9279c1ec4 ||f3d8565ca37b Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #5 from Christoph Cullmann --- Git commit e4e165278048fe11c5c9279c1ec4f3d8565ca37b by Christoph Cullmann, on behalf of Waqar Ahmed. Committed on 10/08/2022 at 19:39. Pushed by cullmann into branch 'master'. Ignore folding ranges if document has changed M +10 -2src/buffer/katetextfolding.cpp https://invent.kde.org/frameworks/ktexteditor/commit/e4e165278048fe11c5c9279c1ec4f3d8565ca37b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Deleted widgets return after a reboot
https://bugs.kde.org/show_bug.cgi?id=457588 --- Comment #10 from Mohammad Amin Chitgarha --- Good! Thanks for your time. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457701] Add .mp4 support
https://bugs.kde.org/show_bug.cgi?id=457701 --- Comment #2 from WS --- I could, but are you sure it is okay to attach a copyrighted song here? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 457724] Add option to not group results by category
https://bugs.kde.org/show_bug.cgi?id=457724 Alexander Lohnau changed: What|Removed |Added Assignee|plasma-b...@kde.org |alexander.loh...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 457724] Add option to not group results by category
https://bugs.kde.org/show_bug.cgi?id=457724 --- Comment #3 from Alexander Lohnau --- Could you please also add a screenshot of the issue? -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 457526] First time crash in Skanlite
https://bugs.kde.org/show_bug.cgi?id=457526 --- Comment #3 from Kåre Särs --- Thanks for the update! :) Regards, Kåre -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433352] Kate tries to open .otf files by default
https://bugs.kde.org/show_bug.cgi?id=433352 TraceyC changed: What|Removed |Added CC||kdeb...@tlcnet.info -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457646] Ctrl key not respected in shortcuts that include it when using XKB option to swap Caps Lock and Ctrl key
https://bugs.kde.org/show_bug.cgi?id=457646 --- Comment #9 from Andrey --- Can you also try on Gnome maybe? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402922] Spell check
https://bugs.kde.org/show_bug.cgi?id=402922 --- Comment #31 from Maik Qualmann --- Album name input should also not have a spell checker. I've just seen a screenshot of a user using any codes for names, it would just have red lines when typing. Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432007] Okular: No scrolling with non-continuous view
https://bugs.kde.org/show_bug.cgi?id=432007 Wolfgang Scherer changed: What|Removed |Added CC||wolfgang.sche...@gmx.de --- Comment #6 from Wolfgang Scherer --- I agree with David Hurks, taht the circular progress indicator from presentation view would be a real enhancement to non-continous page view. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402922] Spell check
https://bugs.kde.org/show_bug.cgi?id=402922 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #30 from Maik Qualmann --- I don't think we should replace QLineEdit that uses a QCompleter. The QCompleter popup in manual face input above the preview is quite a hack. Especially since the spell checker probably fails anyway when entering the tag and face names. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457585] Changing a color scheme resets DPI scaling in the current session
https://bugs.kde.org/show_bug.cgi?id=457585 --- Comment #6 from pktris...@tutanota.com --- (In reply to Nate Graham from comment #4) > Any chance you can grit your teeth and try Wayland to see if it happens > there? I'd love to help, I tried but my framrate on wayland is measurable in fpm rather than fps -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 456819] Commenting out code in C++ source files adds // to the very beginning of the line
https://bugs.kde.org/show_bug.cgi?id=456819
--- Comment #6 from Ahmad Samir ---
Git commit fceb6fef10932a5b6aaf698c102f05bbed04e12a by Ahmad Samir.
Committed on 10/08/2022 at 18:20.
Pushed by cullmann into branch 'master'.
KateDocument: always add space after single line comment start marker
So that if you have code:
if (foo) {
do_something();
}
commenting out the second line, it would become (assuming the
position="afterwhitespace" option is set in c.xml):
if (foo) {
// do_something();
}
This works better with clang-format, which insists on reformatting this:
//do_something();
to
// do_something();
to the version with the space, "// ".
Fix unittests.
M +1-1autotests/src/katedocument_test.cpp
M +1-2src/document/katedocument.cpp
https://invent.kde.org/frameworks/ktexteditor/commit/fceb6fef10932a5b6aaf698c102f05bbed04e12a
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 457730] New: Additional %u in recently-used.xbel exec attributes
https://bugs.kde.org/show_bug.cgi?id=457730 Bug ID: 457730 Summary: Additional %u in recently-used.xbel exec attributes Product: frameworks-kio Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Places Assignee: kio-bugs-n...@kde.org Reporter: fab...@ritter-vogt.de CC: k...@privat.broulik.de, kdelibs-b...@kde.org, meven@kdemail.net Target Milestone: --- While looking at recently-used.xbel for another bug, I noticed that all exec entries had "%u" appended unconditionally, e.g. The specification only allows "%u" and "%f", which makes sense in this context. I don't know what effects this can have. Maybe this can be passed through KIO::DesktopExecParser with "%u" or "%f" as "local path" to get a valid command? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457723] Desktop freezes when trying to add a widget
https://bugs.kde.org/show_bug.cgi?id=457723 --- Comment #2 from Valter Mura --- Hi, this is what I retrieved with coredumpctl: Tue 2022-08-09 17:08:09 CEST 1930 1000 1000 11 present /usr/bin/plasmashell Tue 2022-08-09 17:12:19 CEST 1915 1000 1000 11 present /usr/bin/plasmashell Wed 2022-08-10 17:42:45 CEST 1963 1000 1000 11 present /usr/bin/plasmashell Wed 2022-08-10 20:14:26 CEST 9272 1000 1000 6 present /usr/bin/plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 --- Comment #30 from Oswald Buddenhagen --- this suggests that this might have something to do with partial repaints. maybe it's picking the wrong buffer for updating. this is consistent with my observation that for me this usually affects only the panel when the clock is ticking away. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454615] Plasma had mixed up notification positions (middle of the primary display) and crashes after: plasmashell --replace
https://bugs.kde.org/show_bug.cgi?id=454615 vor...@z-ray.de changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from vor...@z-ray.de --- This did not happened in quite some time now maybe since 5.25 release not sure. Guess it was fixed along the way with some recent Plasma updates :) Many thanks for the awesome work you all doing :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457636] Feature to map pen and tablet buttons to keys / sequence of keys or commands
https://bugs.kde.org/show_bug.cgi?id=457636 Nate Graham changed: What|Removed |Added Summary|Ability to map pen and |Feature to map pen and |tablet buttons to keys /|tablet buttons to keys / |sequence of keys or |sequence of keys or |commands doesn't exist in |commands |tablet KCM [wayland]| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457705] Feature to change the pressure curve of the graphic tablet in the tablet KCM
https://bugs.kde.org/show_bug.cgi?id=457705 Nate Graham changed: What|Removed |Added Severity|normal |wishlist Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org Summary|There is no option to |Feature to change the |edit/adjust and set the |pressure curve of the |pressure curve of the |graphic tablet in the |graphic tablet in the |tablet KCM |tablet KCM [wayland]| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457727] Wayland blur artifacts on nVidia (closed source driver)
https://bugs.kde.org/show_bug.cgi?id=457727 --- Comment #1 from vor...@z-ray.de --- Created attachment 151231 --> https://bugs.kde.org/attachment.cgi?id=151231=edit Blur effect without artifacts on X11 + nVidia as counter test -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457704] Dragging handle button down in custom area selection option scrolls the KCM page instead of resizing the selection
https://bugs.kde.org/show_bug.cgi?id=457704 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 Severity|normal |minor Summary|Drag handle button in |Dragging handle button down |custom area selection |in custom area selection |option scrolls the KCM page |option scrolls the KCM page |instead of resizing the |instead of resizing the |selection [wayland] |selection Keywords||usability --- Comment #1 from Nate Graham --- Yeah it seems like you have to drag left or right first, and then you can drag it up or down. If you drag down immediately, it triggers scrolling code that shouldn't be triggered. Might be an issue in Kirigami, but needs investigation here first. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442287] Replace fill layer's properties dialog color button with a color picker with instant preview
https://bugs.kde.org/show_bug.cgi?id=442287 --- Comment #2 from Leonardo --- When I created this ticket I was unaware of how poorly implemented fill layers were. See https://krita-artists.org/t/fill-layers-appear-poorly-optimized/34387 In summary: a single color fill layer ALWAYS performs worse memory-wise than a normal layer filled with a flat color. They can't be used like firealpacas's or Clip Studio Paint's 8 bit layers at all. Regardless, I mean, just look at the dialog. The "color" tab shows one color button to open a dialog to pick the color. The other tabs, which are far more complex, have all the settings on the tab. Like "pattern" shows a list of patterns for you to click on. You don't have a "select pattern" button that opens a dialog for you to choose a pattern. So I still think there you should be able to pick a color straight from the layer's properties without opening a second dialog, though iirc it was made this way because some users preferred the system color picker, so if it were changed it would have to have a convenient way to select the color on the layer dialog PLUS a button that works like currently to open the system color pick dialog for users who need it for some reason. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457703] Feature to to map an area on the tablet surface to the entire screen
https://bugs.kde.org/show_bug.cgi?id=457703 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Summary|There is no option to |Feature to to map an area |select an area on the |on the tablet surface to |tablet to map it to the |the entire screen |entire screen [wayland] | CC||n...@kde.org Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 457724] Add option to not group results by category
https://bugs.kde.org/show_bug.cgi?id=457724 --- Comment #2 from Natalie Clarius --- (In reply to Alexander Lohnau from comment #1) > >from the VSCode project runner extension > > Could you please link to the project? Maybe the sorting can be improved. https://github.com/alex1701c/krunner-vscodeprojects, but I don't think it can. That some less relevant results of one category will outrank some more relevant ones of a different category is simply the nature of grouping all results of a category together. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Faerbit changed: What|Removed |Added CC|faer...@posteo.net | -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457701] Add .mp4 support
https://bugs.kde.org/show_bug.cgi?id=457701 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Can you attach one such file so I can test, verify, and (hopefully) fix it? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457675] AboutItem freezes with certain font/content combinations
https://bugs.kde.org/show_bug.cgi?id=457675 --- Comment #6 from Connor Carney --- That QML file explicitly sets Ubuntu 10 pt on the ApplicationWindow, so it shouldn't depend on your font settings, although it does depend on having that font installed. I normally use kwin-wayland @ 100%, but it also happens in an X session. It takes some trial and error to find specific combinations of font+size+text that trigger the issue for me, but when I find one it freezes consistently. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 457729] plasma-systemmonitor gets stuck/frozen on resizing with Wayland and nVidia
https://bugs.kde.org/show_bug.cgi?id=457729 vor...@z-ray.de changed: What|Removed |Added Attachment #151230|Terminal ouptu of |Terminal output of description|plasma-systemmonitor when |plasma-systemmonitor when |resized |resized -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457698] Changing display scale on Wayland requires users to log out and log back in.
https://bugs.kde.org/show_bug.cgi?id=457698 Nate Graham changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-78327 CC||n...@kde.org Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This issue affects all Qt apps (not just Plasma) and is unfortunately caused by a Qt bug: https://bugreports.qt.io/browse/QTBUG-78327. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 457729] New: plasma-systemmonitor gets stuck/frozen on resizing with Wayland and nVidia
https://bugs.kde.org/show_bug.cgi?id=457729 Bug ID: 457729 Summary: plasma-systemmonitor gets stuck/frozen on resizing with Wayland and nVidia Product: plasma-systemmonitor Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: vor...@z-ray.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 151230 --> https://bugs.kde.org/attachment.cgi?id=151230=edit Terminal ouptu of plasma-systemmonitor when resized SUMMARY On Wayland with nVidia plasma-systemmoitor gets stuck upon resizing the window STEPS TO REPRODUCE 1. Run Plasma in Wayland on nVidia (closed source drivers) 2. open plasma-systemmonitor 3. Resize window OBSERVED RESULT The plasma-systemmonitor gets stuck/frozen as soon as it is resized. EXPECTED RESULT To properly resize plasma-systemmonitor SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220809 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.15-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 1800X Eight-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A33 System Version: 2.0 nVidia driver: 515.65.01 ADDITIONAL INFORMATION Other applications can be resized as expected. Tested dolphin and kinfocenter -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417114] Removed widget re-appears back after relogin if I do logout while "Undo" notification is visible
https://bugs.kde.org/show_bug.cgi?id=417114 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453054] MYPAINT:Missing "dab per basic radius"
https://bugs.kde.org/show_bug.cgi?id=453054 Tiar changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457588] Deleted widgets return after a reboot
https://bugs.kde.org/show_bug.cgi?id=457588 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #9 from Nate Graham --- Yep, that's currently the expected behavior. It's still buggy and weird from a user perspective and should be fixed, though. *** This bug has been marked as a duplicate of bug 417114 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417114] Removed widget re-appears back after relogin if I do logout while "Undo" notification is visible
https://bugs.kde.org/show_bug.cgi?id=417114 Nate Graham changed: What|Removed |Added CC||machitga...@outlook.com --- Comment #4 from Nate Graham --- *** Bug 457588 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
