[krita] [Bug 486080] Krita text tool font render too large on image
https://bugs.kde.org/show_bug.cgi?id=486080 --- Comment #3 from Rory --- Created attachment 168903 --> https://bugs.kde.org/attachment.cgi?id=168903=edit text added as 10 point font is huge, way off the page I have a XCF image of specific dimensions (1094x1233) with lots of text that fits neatly centered on that image. When I copy/paste this same stuff into Krita at 10pt font the text is HUGE and goes WAY off the page. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486080] Krita text tool font render too large on image
https://bugs.kde.org/show_bug.cgi?id=486080 --- Comment #2 from Rory --- Created attachment 168874 --> https://bugs.kde.org/attachment.cgi?id=168874=edit text on image is very large -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486080] Krita text tool font render too large on image
https://bugs.kde.org/show_bug.cgi?id=486080 --- Comment #1 from Rory --- Created attachment 168873 --> https://bugs.kde.org/attachment.cgi?id=168873=edit text tool shows 10 point font as small -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486080] New: Krita text tool font render too large on image
https://bugs.kde.org/show_bug.cgi?id=486080 Bug ID: 486080 Summary: Krita text tool font render too large on image Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: rory.ash...@gmail.com Target Milestone: --- SUMMARY When I add text 10 point font size in Krita it renders very large. STEPS TO REPRODUCE 1. make new image 2. add text element 10 point font OBSERVED RESULT font size is 40+ EXPECTED RESULT text with 10 point font SOFTWARE/OS VERSIONS Krita Version: 5.1.5 Hidpi: true Qt Version (compiled): 5.15.8 Version (loaded): 5.15.8 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 6.1.0-17-amd64 Pretty Productname: Debian GNU/Linux 12 (bookworm) Product Type: debian Product Version: 12 Desktop: KDE Locale Languages: en_US, en, en_Latn_US C locale: en_US.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) Xe Graphics (TGL GT2)" Version: "4.6 (Compatibility Profile) Mesa 23.1.2-1~mx23ahs" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false supportsBufferMapping: true supportsBufferInvalidation: true forceDisableTextureBuffers: false Extensions: "GL_ARB_texture_rgb10_a2ui" "GL_ARB_shader_atomic_counters" "GL_ARB_blend_func_extended" "GL_ARB_fragment_shader_interlock" "GL_EXT_gpu_shader4" "GL_NV_blend_square" "GL_EXT_texture_compression_dxt1" "GL_ARB_depth_clamp" "GL_EXT_timer_query" "GL_ARB_arrays_of_arrays" "GL_MESA_pack_invert" "GL_ANGLE_texture_compression_dxt3" "GL_KHR_blend_equation_advanced" "GL_ARB_direct_state_access" "GL_AMD_depth_clamp_separate" "GL_ARB_shader_atomic_counter_ops" "GL_ARB_shader_group_vote" "GL_EXT_texture_env_combine" "GL_ARB_internalformat_query" "GL_EXT_separate_specular_color" "GL_IBM_rasterpos_clip" "GL_ARB_provoking_vertex" "GL_EXT_rescale_normal" "GL_ARB_shader_viewport_layer_array" "GL_ARB_texture_env_add" "GL_ARB_depth_buffer_float" "GL_ARB_indirect_parameters" "GL_ARB_texture_env_dot3" "GL_ARB_explicit_attrib_location" "GL_EXT_texture_array" "GL_EXT_shader_framebuffer_fetch_non_coherent" "GL_EXT_draw_range_elements" "GL_KHR_parallel_shader_compile" "GL_KHR_robustness" "GL_EXT_blend_minmax" "GL_EXT_framebuffer_blit" "GL_ARB_robust_buffer_access_behavior" "GL_EXT_vertex_array" "GL_ATI_fragment_shader" "GL_ARB_multi_bind" "GL_EXT_shader_integer_mix" "GL_ARB_uniform_buffer_object" "GL_ARB_depth_texture" "GL_ARB_transform_feedback_instanced" "GL_KHR_blend_equation_advanced_coherent" "GL_EXT_texture_compression_rgtc" "GL_ARB_texture_multisample" "GL_ARB_texture_barrier" "GL_ARB_texture_mirrored_repeat" "GL_EXT_draw_buffers2" "GL_ARB_transform_feedback_overflow_query" "GL_EXT_texture_sRGB_decode" "GL_NV_fog_distance" "GL_EXT_bgra" "GL_ARB_robustness" "GL_EXT_memory_object" "GL_MESA_shader_integer_functions" "GL_OES_EGL_image" "GL_ARB_shader_image_load_store" "GL_ARB_fragment_program_shadow" "GL_EXT_framebuffer_multisample_blit_scaled" "GL_EXT_abgr" "GL_AMD_shader_trinary_minmax" "GL_IBM_texture_mirrored_repeat" "GL_NV_texture_env_combine4" "GL_ARB_shading_language_packing" "GL_ARB_shader_storage_buffer_object" "GL_ARB_explicit_uniform_location" "GL_SGIS_texture_lod" "GL_NV_alpha_to_coverage_dither_control" "GL_EXT_blend_subtract" "GL_MESA_framebuffer_flip_y" "GL_ARB_window_pos" "GL_EXT_EGL_image_storage" "GL_ARB_compute_shader" "GL_ARB_texture_env_combine"
[Falkon] [Bug 483358] Step 2 in Flatpak install is out of date
https://bugs.kde.org/show_bug.cgi?id=483358 --- Comment #2 from Rory --- (In reply to Nick from comment #1) > Hi - any chance you can provide more details as to where these instructions > are located so we can see if they can be updated? Thanks. https://www.falkon.org/download/ -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 483358] New: Step 2 in Flatpak install is out of date
https://bugs.kde.org/show_bug.cgi?id=483358 Bug ID: 483358 Summary: Step 2 in Flatpak install is out of date Classification: Applications Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: rory.ash...@gmail.com Target Milestone: --- SUMMARY *** flatpak remote-add --if-not-exists kdeapps --from https://distribute.kde.org/kdeapps.flatpakrepo This URL no longer exist distribute.kde.org The Falkon nightly is now here https://cdn.kde.org/flatpak/falkon-nightly/ So it looks like step 2 should be flatpak remote-add --if-not-exists kdeapps --from https://cdn.kde.org/flatpak/falkon-nightly/falkon-nightly.flatpakrepo *** OBSERVED RESULT error: Can't load uri https://distribute.kde.org/kdeapps.flatpakrepo: Error resolving “distribute.kde.org”: Name or service not known EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 465056] New: Tokodon crash when opening "conversation"
https://bugs.kde.org/show_bug.cgi?id=465056
Bug ID: 465056
Summary: Tokodon crash when opening "conversation"
Classification: Applications
Product: Tokodon
Version: 23.01.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: falsemir...@protonmail.com
CC: c...@carlschwan.eu
Target Milestone: ---
Application: tokodon (23.01.0)
Qt Version: 5.15.7
Frameworks Version: 5.101.0
Operating System: Linux 6.1.7-100.fc36.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.26.4 [KCrashBackend]
-- Information about the crash:
Each time I select the Conversation tab, tokodon crashed before it loads.
Specific conversations can be accesed through "notification" without a crash.
Server is running Mastodon v4.0.2
The crash can be reproduced every time.
-- Backtrace:
Application: Tokodon (tokodon), signal: Segmentation fault
[KCrash Handler]
#4 0x55b44498260b in ConversationModel::data(QModelIndex const&, int)
const ()
#5 0x7f7b52f6d980 in QQmlDMCachedModelData::metaCall(QMetaObject::Call,
int, void**) () from /lib64/libQt5QmlModels.so.5
#6 0x7f7b535bea66 in loadProperty(QV4::ExecutionEngine*, QObject*,
QQmlPropertyData const&) () from /lib64/libQt5Qml.so.5
#7 0x7f7b535bfb2c in
QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*,
QV4::ExecutionEngine*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5
#8 0x7f7b535df67a in QV4::Moth::VME::interpret(QV4::CppStackFrame*,
QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5
#9 0x7f7b535e4077 in QV4::Moth::VME::exec(QV4::CppStackFrame*,
QV4::ExecutionEngine*) () from /lib64/libQt5Qml.so.5
#10 0x7f7b53575586 in QV4::Function::call(QV4::Value const*, QV4::Value
const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5
#11 0x7f7b537043b1 in QQmlJavaScriptExpression::evaluate(QV4::CallData*,
bool*) () from /lib64/libQt5Qml.so.5
#12 0x7f7b5370a808 in QQmlBinding::evaluate(bool*) () from
/lib64/libQt5Qml.so.5
#13 0x7f7b5370eb17 in
QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&,
QFlags, QV4::Scope&) () from /lib64/libQt5Qml.so.5
#14 0x7f7b5370c5b4 in
QQmlBinding::update(QFlags) () from
/lib64/libQt5Qml.so.5
#15 0x7f7b53719d3b in
QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from
/lib64/libQt5Qml.so.5
#16 0x7f7b536af1c2 in
QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from
/lib64/libQt5Qml.so.5
#17 0x7f7b536af645 in QQmlEnginePrivate::incubate(QQmlIncubator&,
QQmlContextData*) () from /lib64/libQt5Qml.so.5
#18 0x7f7b52f8174f in
QQmlDelegateModelPrivate::object(QQmlListCompositor::Group, int,
QQmlIncubator::IncubationMode) () from /lib64/libQt5QmlModels.so.5
#19 0x7f7b53d58744 in QQuickItemViewPrivate::createItem(int,
QQmlIncubator::IncubationMode) () from /lib64/libQt5Quick.so.5
#20 0x7f7b53d68361 in QQuickListViewPrivate::addVisibleItems(double,
double, double, double, bool) () from /lib64/libQt5Quick.so.5
#21 0x7f7b53d56f2b in QQuickItemViewPrivate::refill(double, double) () from
/lib64/libQt5Quick.so.5
#22 0x7f7b53d5b479 in QQuickItemViewPrivate::regenerate(bool) [clone
.part.0] () from /lib64/libQt5Quick.so.5
#23 0x7f7b53d5b79a in QQuickItemView::modelUpdated(QQmlChangeSet const&,
bool) () from /lib64/libQt5Quick.so.5
#24 0x7f7b51cdbdaf in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#25 0x7f7b52f5474a in QQmlInstanceModel::modelUpdated(QQmlChangeSet const&,
bool) () from /lib64/libQt5QmlModels.so.5
#26 0x7f7b52f752cc in non-virtual thunk to
QQmlDelegateModelPrivate::emitModelUpdated(QQmlChangeSet const&, bool) () from
/lib64/libQt5QmlModels.so.5
#27 0x7f7b52f7b8c3 in QQmlDelegateModelGroupPrivate::emitModelUpdated(bool)
() from /lib64/libQt5QmlModels.so.5
#28 0x7f7b52f7bcc8 in QQmlDelegateModelPrivate::emitChanges() () from
/lib64/libQt5QmlModels.so.5
#29 0x7f7b52f87402 in QQmlDelegateModel::_q_modelReset() () from
/lib64/libQt5QmlModels.so.5
#30 0x7f7b52f8802b in QQmlDelegateModel::qt_metacall(QMetaObject::Call,
int, void**) () from /lib64/libQt5QmlModels.so.5
#31 0x7f7b51cdbafe in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#32 0x7f7b51c59081 in
QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from
/lib64/libQt5Core.so.5
#33 0x55b444983408 in
ConversationModel::fetchConversation(AbstractAccount*)::{lambda(QNetworkReply*)#1}::operator()(QNetworkReply*)
const ()
#34 0x55b44496aab9 in
QtPrivate::QFunctorSlotObject) const::{lambda()#1}, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) [clone .lto_priv.0] ()
#35
[lattedock] [Bug 432385] Idea for panel priority
https://bugs.kde.org/show_bug.cgi?id=432385 --- Comment #3 from Rory --- (In reply to Michail Vourlakos from comment #2) > Personally I am not interested in this. May I ask why top and bottom panels take priority over the screen space in the corners? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 432385] Idea for panel priority
https://bugs.kde.org/show_bug.cgi?id=432385 --- Comment #1 from Rory --- Created attachment 135353 --> https://bugs.kde.org/attachment.cgi?id=135353=edit Showing possible panel arrangements -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 432385] New: Idea for panel priority
https://bugs.kde.org/show_bug.cgi?id=432385 Bug ID: 432385 Summary: Idea for panel priority Product: lattedock Version: 0.9.11 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: roracl...@gmail.com Target Milestone: --- SUMMARY An option to give a panel priority over the occupied corners of the monitor for panels that intersect each other. Idea: With this example, we will use a proverbial panel located on the left side of the screen with another panel across the top. 1. R-click left panel, select "Panel Settings" 2. New option under "Behavior" called "Priority" is available 3. The available options will change to one of two options: -- If Position is "Top" or "Bottom", Priority options are "Left" and "Right" -- OR -- If Position is "Left" or "Right", Priority options are "Top" and "Bottom" 4. Both Priority options can be enabled or disabled. Priority Options: Both disabled defaults to top and bottom panels taking priority (current behavior as of 0.9.11). Let's take our example left side panel and enable "Top" under Priority. Now take the example top panel and disable "Left" under Priority. The result is, the left panel will fill up to the top, and the top panel will stop where the left panel starts. If the left panel gets hidden, the top bar can maximize to the edge of the left side of the screen. IF TWO PANELS HAVE PRIORITY OF THE SAME CORNER the best way to handle this is to default to the horizontal panel having priority. This should allow for even more customization of personal desktop space, furthering Latte-dock and Plasma as the most customizable desktop environment on the planet! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #25 from Rory --- Well I've upgraded to 5.16 and the issue persists -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 Rory changed: What|Removed |Added Version|5.15.4 |5.16.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #24 from Rory --- I'm currently upgrading to 5.16, hopefully it's fixed already in this. 爛 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #23 from Rory --- (In reply to Vlad Zagorodniy from comment #22) > Switch to the XRender rendering backnd and check whether you can reproduce > this bug. Switching to xrender, the corner icon got REALLY small almost couldn't see it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #21 from Rory --- (In reply to Vlad Zagorodniy from comment #20) > Open System Settings app and type "xrender" in the search field. This morning's bootup: the problem is not there. To respond to you, it's set to OpenGL 2.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #19 from Rory --- (In reply to Vlad Zagorodniy from comment #18) > Does this bug occur if you switch to XRender render backend? How can I check that? To be completely fair, KDE settings are so terribly organized, but in all my efforts I can't imagine a better way to do them lol -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #17 from Rory --- Aaaand switching back to Nvidia driver it's normal again! What is going on here?! Is it only me having this problem? It can't be, not when it's done this on two different operating systems! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #16 from Rory --- Just for clarification, I changed back to the open source display driver and the problem was still there, so it's not too do with the Nvidia drivers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #15 from Rory --- Created attachment 120800 --> https://bugs.kde.org/attachment.cgi?id=120800=edit kwinrc file -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #13 from Rory --- (In reply to Vlad Zagorodniy from comment #12) > Could you post your kwinrc? As soon as I get home I will do that, but I need to know how to do that please. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #11 from Rory --- (In reply to Nate Graham from comment #8) > So now that it's reproducing again, does it go away if you switch to the > Oxygen plasma theme? I have yet to try Oxygen. I'm running errands and will try when I get home -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #10 from Rory --- (In reply to Vlad Zagorodniy from comment #9) > What desktop theme do you use? Breeze dark. I've tried other themes and the problem persists regardless of the theme. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #7 from Rory --- Alrighty, started up the computer just now and the big splotch is back this morning. What the actual hell is going on? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #6 from Rory --- (In reply to Nate Graham from comment #5) > Yikes, that's weird. However I'm not clear on when this started happening. > You said: > > after a KDE update, this started happening > > And also: > > This happened after installing nvidia drivers. (nvidia-drivers-418) > > Which is it? Also, does it go away if you change your Plasma theme to, say, > Oxygen? It was hard to tell, because regardless, it kept doing it! But get this: this morning, I booted up my system, no updates at all the past day or two, and on a whim, I turn on the hot corner (expected it to be huge, change gfx driver, see if it persisted) and would you believe it, it's back to being small again!? I'm floored by this one. Basically, after all updates and chages I made, the problem was there. There were ZERO changes between it happening and this morning, but it has magically been fixed. Then I updated my system. I'll come back to this if I come about the issue again. This is stupidly strange. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #4 from Rory --- (In reply to David Edmundson from comment #1) > Please check with the default breeze theme. I have switched themes around and the problem persists. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #3 from Rory --- By the way, this happened in Kubuntu and openSuSE -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408462] Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 --- Comment #2 from Rory --- I'm relatively new to KDE, skipped the 4.x series completely (and do you blame me?) so I'm not exactly sure where to look here. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408462] New: Hot Corners activate too early and are huge
https://bugs.kde.org/show_bug.cgi?id=408462 Bug ID: 408462 Summary: Hot Corners activate too early and are huge Product: systemsettings Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_lookandfeel Assignee: plasma-b...@kde.org Reporter: roracl...@gmail.com Target Milestone: --- Created attachment 120707 --> https://bugs.kde.org/attachment.cgi?id=120707=edit image of the issue SUMMARY The blue splash of the hot corners are extremly large. They only activate if you go to the corner, but the splash activates in the middle of the screen, as if the resolution was wrong, but it isn't. This happened after installing nvidia drivers. (nvidia-drivers-418) STEPS TO REPRODUCE 1. install nvidia drivers on kubuntu 2. reboot 3. observe OBSERVED RESULT huge blue things on screen corners EXPECTED RESULT small, simple blue splashes that only show when i go into the corner of the screen. this might have been affected by an update, as well, as i was running a stable system a few weeks ago, and after a KDE update, this started happening. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.04, Plasma 5.15.4 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION no additional info -- You are receiving this mail because: You are watching all bug changes.
