[systemsettings] [Bug 444520] New: Baloo content indexing resurrects itself after being killed *and* disabled
https://bugs.kde.org/show_bug.cgi?id=444520 Bug ID: 444520 Summary: Baloo content indexing resurrects itself after being killed *and* disabled Product: systemsettings Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_baloo Assignee: baloo-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Just in time for Halloween, Baloo returns from the dead to haunt the living. Suppose a user encounters one of the many common performance issues caused by Baloo, like the one I describe here: https://bugs.kde.org/show_bug.cgi?id=380456#c14 They are likely to try to pause Baloo using system settings, but this (frequently? always?) doesn't work, as I describe in this bug: https://bugs.kde.org/show_bug.cgi?id=443693 So they're likely to try disable indexing file content (while leaving "Enable File Search" checked. They may even `kill -9 baloo_file_extractor` and reboot just to be sure it's dead. Sooner or later, whenever Baloo kicks back in, it may also restart indexing file content, despite being disabled. On the computer this happened on, I caught baloo_file_extractor hanging (again) with 100% CPU use and several GB of memory eaten on one particular PDF file, the same issue that triggered my comment here: https://bugs.kde.org/show_bug.cgi?id=380456#c14 To state the obvious, Baloo should *never* resurrect an already-killed file extraction if "index file content" is disabled. STEPS TO REPRODUCE 1. Enable File Search and content indexing in system settings. 2. Add a file to a directory indexed by Baloo which will cause baloo_file_extractor to hang for a while and consume system resources. (There are lots of examples of such files; because Baloo uses external libraries to extract file contents, e.g. poppler, it's dependent on them to be well behaved with the files they open.) 3. While baloo_file_extractor is trying to extract text from the file, kill it manually and disable file content indexing in the settings. 4. Wait a while. (In my case, at least one reboot had gone by since disabling content indexing.) OBSERVED RESULT Baloo appears to resume the partially completed indexing process that the user previously killed, including indexing files - in particular the file or files that were causing problems for the indexer. EXPECTED RESULT Baloo should respect the changed settings and not try to index the content of any files. SOFTWARE/OS VERSIONS Linux: Arch Linux x86_64 (kernel 5.14.14) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365091] "Start the Input Actions daemon on login" does nothing
https://bugs.kde.org/show_bug.cgi?id=365091 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om --- Comment #5 from Adam Fontenot --- If I'm not mistaken, this option should be removed entirely, since it no longer has any function. (Those looking to enable or disable this daemon should use "Startup and Shutdown" > "Background Services" > "Input Actions".) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437618] Suddenly one character of keyboard input is missing
https://bugs.kde.org/show_bug.cgi?id=437618 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444521] New: Crash when changing Virtual Desktop setttings on wayland
https://bugs.kde.org/show_bug.cgi?id=444521 Bug ID: 444521 Summary: Crash when changing Virtual Desktop setttings on wayland Product: systemsettings Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: simon.th...@viveris.fr Target Milestone: --- Application: systemsettings5 (5.22.5) Qt Version: 5.15.2 Frameworks Version: 5.87.0 Operating System: Linux 5.14.11-300.fc35.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.5 Distribution: Fedora Linux 35 (Workstation Edition) -- Information about the crash: - What I was doing when the application crashed: Updating the display time of the virtual desktop changing animation from 500ms to 400ms. The crash can be reproduced every time. -- Backtrace: Application: Configuration du système (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f80e31da940 (LWP 5013))] [KCrash Handler] #6 0x7f80e5d356a4 in QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x55b72ba64d30, registry=0x55b72983d1d0, id=47, interface=..., version=1) at global/qwaylandclientextension.cpp:67 #7 0x7f80e5d221b9 in QtWaylandClient::QWaylandDisplay::registry_global (this=, id=, interface=..., version=) at /usr/src/debug/qt5-qtwayland-5.15.2-14.fc35.x86_64/src/client/qwaylanddisplay.cpp:397 #8 0x7f80e5d3eaf3 in QtWayland::wl_registry::handle_global (data=0x55b729839490, object=, name=47, interface=0x55b72a96ab80 "org_kde_kwin_blur_manager", version=1) at /usr/src/debug/qt5-qtwayland-5.15.2-14.fc35.x86_64/src/client/qwayland-wayland.cpp:94 #9 0x7f80e35d4c04 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #10 0x7f80e35d4108 in ffi_call (cif=cif@entry=0x7ffec2b202d0, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffec2b203a0) at ../src/x86/ffi64.c:525 #11 0x7f80e5c8fd10 in wl_closure_invoke (closure=closure@entry=0x55b72a96aaa0, target=, target@entry=0x55b72983d1d0, opcode=opcode@entry=0, data=, flags=) at ../src/connection.c:1018 #12 0x7f80e5c9041b in dispatch_event (display=display@entry=0x55b72983d080, queue=, queue=) at ../src/wayland-client.c:1452 #13 0x7f80e5c9060c in dispatch_queue (queue=0x55b72983d150, display=0x55b72983d080) at ../src/wayland-client.c:1598 #14 wl_display_dispatch_queue_pending (display=0x55b72983d080, queue=0x55b72983d150) at ../src/wayland-client.c:1840 #15 0x7f80e5d1a6a3 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55b729839480) at /usr/src/debug/qt5-qtwayland-5.15.2-14.fc35.x86_64/src/client/qwaylanddisplay.cpp:222 #16 0x7f80e83293f0 in doActivate (sender=0x55b72985abd0, signal_index=3, argv=0x7ffec2b20670) at kernel/qobject.cpp:3898 #17 0x7f80e8324327 in QMetaObject::activate (sender=sender@entry=0x55b72985abd0, m=m@entry=0x7f80e85ce460 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffec2b20670) at kernel/qobject.cpp:3946 #18 0x7f80e832bb4a in QSocketNotifier::activated (this=this@entry=0x55b72985abd0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #19 0x7f80e832c363 in QSocketNotifier::event (this=0x55b72985abd0, e=0x7ffec2b20770) at kernel/qsocketnotifier.cpp:302 #20 0x7f80e8ece443 in QApplicationPrivate::notify_helper (this=, receiver=0x55b72985abd0, e=0x7ffec2b20770) at kernel/qapplication.cpp:3632 #21 0x7f80e82f5798 in QCoreApplication::notifyInternal2 (receiver=0x55b72985abd0, event=0x7ffec2b20770) at kernel/qcoreapplication.cpp:1064 #22 0x7f80e83475ff in socketNotifierSourceDispatch (source=0x55b7298615e0) at kernel/qeventdispatcher_glib.cpp:107 #23 0x7f80e609133f in g_main_dispatch (context=0x55b7298929f0) at ../glib/gmain.c:3381 #24 g_main_context_dispatch (context=0x55b7298929f0) at ../glib/gmain.c:4099 #25 0x7f80e60e6288 in g_main_context_iterate.constprop.0 (context=context@entry=0x55b7298929f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175 #26 0x7f80e608e9e3 in g_main_context_iteration (context=0x55b7298929f0, may_block=1) at ../glib/gmain.c:4240 #27 0x7f80e8346b78 in QEventDispatcherGlib::processEvents (this=0x55b7298b9070, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f80e82f41a2 in QEventLoop::exec (this=this@entry=0x7ffec2b209e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f80e82fc6e4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x55b7294dc58c in main (argc=, argv=0x7ffec2b20b00) at /usr/src/debug/plasma-systemsettings-5.22.5-1.fc35.x86_64/app/main.cpp:208 [Inferior 1 (process 5013) detached] The reporter indicates this bug may be a duplicate of or related to bug 442318. Possible duplicates by query
[systemsettings] [Bug 444519] System Settings crash upon opening Window Decoration Module
https://bugs.kde.org/show_bug.cgi?id=444519 Tony changed: What|Removed |Added CC||jodr...@live.com Assignee|aleix...@kde.org|plasma-b...@kde.org Product|kde-cli-tools |systemsettings Component|general |general --- Comment #1 from Tony --- Can't repreduce. If by any chance you have any other decoration installed remove them and try again. You can find them here : ~/.local/share/aurorae/themes/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428272] Unmaximize does not restore window size/position correctly if KWin's Quicktile shortcuts were used before
https://bugs.kde.org/show_bug.cgi?id=428272 Sebastian changed: What|Removed |Added CC||echsbe...@gmx.de --- Comment #4 from Sebastian --- Any update on that bug? I absolutely second cysliders justification, this bug really messes up KDE shortcut based workflows. Not sure what is meant by "totally intended behavior", could you elaborate on this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444522] New: "Send Keyboard Input" shortcut inputs the keys using the wrong keyboard layout
https://bugs.kde.org/show_bug.cgi?id=444522 Bug ID: 444522 Summary: "Send Keyboard Input" shortcut inputs the keys using the wrong keyboard layout Product: systemsettings Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: adam.m.fontenot+...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Seemingly khotkeys "types" the input as if the corresponding keys on the physical keyboard were pressed, but it ought to type the text provided by the user. (Rationale: suppose the user switches between keyboard layouts frequently. In this case, their shortcuts will be broken half the time.) Easy to reproduce. This is not the same issue as https://bugs.kde.org/show_bug.cgi?id=355046 STEPS TO REPRODUCE 1. Set your keyboard layout to something other than your physical keyboard's layout. E.g. Dvorak or Colemak. 2. Create a new Custom Shortcut. Make the trigger whatever you like, and the Action "t:e:s:t" (no quotes). 3. Open KWrite, and press the keyboard combination. OBSERVED RESULT KWrite prints ".oy" With a Dvorak layout, when I press the physical keys "test" on my US Qwerty keyboard, "y.oy" is printed. Thus, khotkeys is entering text as if it was physically typed on the buttons given in the Action, instead of respecting the keyboard layout. The reason ".oy" instead of "y.oy" is printed is because of https://bugs.kde.org/show_bug.cgi?id=437618 Specifically, I used the trigger Alt+Y, but the button I press for Y on Dvorak is the physical T button on the keyboard, so the first "t" of keyboard input gets eaten because of that bug. EXPECTED RESULT KWrite prints "test" SOFTWARE/OS VERSIONS Linux: Arch Linux x86_64 (kernel 5.14.14) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 444523] New: Gwenview is not able to install plugins due to a typo
https://bugs.kde.org/show_bug.cgi?id=444523 Bug ID: 444523 Summary: Gwenview is not able to install plugins due to a typo Product: gwenview Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: pa...@pakusland.net Target Milestone: --- Created attachment 142959 --> https://bugs.kde.org/attachment.cgi?id=142959&action=edit The Discover's error SUMMARY STEPS TO REPRODUCE 1. Go to Plugins > Install Plugins OBSERVED RESULT A Discover window is open but it shows an error: "Couldn't open appstream://org.kde.kipi_plguins" Notice the typo in the word "plugins". EXPECTED RESULT The kipi plugins section should be open. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355046] Shortcut settings do not respect active keyboard layout.
https://bugs.kde.org/show_bug.cgi?id=355046 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c ||om --- Comment #5 from Adam Fontenot --- I can't reproduce on the latest release. Does anyone still see this issue? I do see a related issue: text typed using the "Send Keyboard Input" feature of a custom shortcut doesn't respect the active layout. I reported that here: https://bugs.kde.org/show_bug.cgi?id=444522 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #27 from p d --- (In reply to Méven Car from comment #25) > (In reply to p d from comment #23) > > With "Hide Titles" kwin script > > That's this one I guess: > https://store.kde.org/p/1354715/ > https://github.com/bahamondev/hide-titles/blob/master/contents/code/main.js > > > the issue still happens some of the time. > > Do you know if that is when you click the maximize button or drap up a > window, or double click on a window title bar ? It happens sometimes with any of those actions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #28 from p d --- (In reply to Méven Car from comment #26) > (In reply to Méven Car from comment #25) > > (In reply to p d from comment #23) > > > With "Hide Titles" kwin script > > > > That's this one I guess: > > https://store.kde.org/p/1354715/ > > https://github.com/bahamondev/hide-titles/blob/master/contents/code/main.js > > > > > the issue still happens some of the time. > > > > Do you know if that is when you click the maximize button or drap up a > > window, or double click on a window title bar ? > > That's a different bug this one concerned specifically the > "BorderlessMaximizedWindows" case. Then why was my bug ( https://bugs.kde.org/show_bug.cgi?id=440380 ) marked duplicate of this bug, if it's a different bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 David Edmundson changed: What|Removed |Added CC||simon.th...@viveris.fr --- Comment #37 from David Edmundson --- *** Bug 444521 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444521] Crash when changing Virtual Desktop setttings on wayland
https://bugs.kde.org/show_bug.cgi?id=444521 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 437455 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 421974] [Wayland] Spectacle Doesn't Copy To The Clipboard The Screenshot Automatically
https://bugs.kde.org/show_bug.cgi?id=421974 --- Comment #25 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/619 -- You are receiving this mail because: You are watching all bug changes.
[plasma-redshift-control] [Bug 444524] New: Redshift shouldn't override a custom color profile if disabled
https://bugs.kde.org/show_bug.cgi?id=444524 Bug ID: 444524 Summary: Redshift shouldn't override a custom color profile if disabled Product: plasma-redshift-control Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: avaman...@gmail.com Target Milestone: --- SUMMARY I have a custom ICC color profile for my display. But having redshift running or even going near its control resets the profile to the default one. To the user it seems that shortly after applying an iCC profile, it unsets itself. STEPS TO REPRODUCE 1. Set a custom color profile 2. Have redshift running but disabled, or not running and hover over the control 3. Wrong color profile gets set OBSERVED RESULT Color profile is reset to default, colord is not aware (UI state is inconsistent) EXPECTED RESULT When a custom color profile is set, redshift restores that custom color profile if its disabled. Alternatively, it refuses to touch the profiles if it detects a custom one. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444525] New: can't always choose a different splash screen than global theme
https://bugs.kde.org/show_bug.cgi?id=444525 Bug ID: 444525 Summary: can't always choose a different splash screen than global theme Product: systemsettings Version: 5.23.2 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_style Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com CC: m...@genda.life Target Milestone: --- SUMMARY I still prefer/use P4/Oxygen style but had been using Breeze splash screen to remember I'm not use KDE3 or P4. This seems no longer possible. I keep selecting Breeze splash screen but it keeps showing Oxygen splash screen when I start, instead. This happens on both Slackware GNU/Linux and KDE Neon GNU/Linux. STEPS TO REPRODUCE 1. Choose global theme (is Oxygen in my case). 2. Choose different splash screen (tried Breeze). 3. Restart, watch splash screen match global theme instead of what's chosen. OBSERVED RESULT You can't always choose a different splash screen than your global theme. Well you can choose it but it won't work (will match global theme). EXPECTED RESULT You should be able to choose a different splash screen than your global theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64-current & KDE Neon GNU/Linux / 5.23 KDE Plasma Version: 5.23.1, 5.23.2 KDE Frameworks Version: 5.87.0, ... Qt Version: 5.15.3, ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Robin Bankhead changed: What|Removed |Added CC||kde.b...@headbank.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444526] New: Resolution of external 4k monitor sometimes changes to FHD
https://bugs.kde.org/show_bug.cgi?id=444526 Bug ID: 444526 Summary: Resolution of external 4k monitor sometimes changes to FHD Product: kwin Version: 5.21.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: frederic.parre...@univ-grenoble-alpes.fr Target Milestone: --- SUMMARY I have an XPS13 laptop with a 4k screen, and an external monitor also with a 4k screen. Sometimes, when I connect the external monitor, its resolution is changed to FHD, so I need to reset it to 4k. STEPS TO REPRODUCE Unfortunately, I have not found a clear repro procedure. OBSERVED RESULT The resolution sometimes automatically changes to FHD for the external monitor. EXPECTED RESULT The resolution of the external monitor should stay to 4k. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 Robin Bankhead changed: What|Removed |Added CC||kde.b...@headbank.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 Méven Car changed: What|Removed |Added Ever confirmed|0 |1 CC||meve...@gmail.com Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443757] Please bring back cover switch effect
https://bugs.kde.org/show_bug.cgi?id=443757 Robin Bankhead changed: What|Removed |Added CC||kde.b...@headbank.co.uk -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 444526] Resolution of external 4k monitor sometimes changes to FHD
https://bugs.kde.org/show_bug.cgi?id=444526 David Edmundson changed: What|Removed |Added Component|multi-screen|common Resolution|--- |WAITINGFORINFO Assignee|kwin-bugs-n...@kde.org |kscreen-bugs-n...@kde.org Product|kwin|KScreen Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Please can you run `kscreen-console ` whilst connecting and try and get a working and non-working output please. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 --- Comment #2 from Méven Car --- Script example: https://store.kde.org/p/1354715/ https://github.com/bahamondev/hide-titles/blob/master/contents/code/main.js -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 Méven Car changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #29 from Méven Car --- (In reply to p d from comment #28) > (In reply to Méven Car from comment #26) > > (In reply to Méven Car from comment #25) > > > (In reply to p d from comment #23) > > > > With "Hide Titles" kwin script > > > > > > That's this one I guess: > > > https://store.kde.org/p/1354715/ > > > https://github.com/bahamondev/hide-titles/blob/master/contents/code/main.js > > > > > > > the issue still happens some of the time. > > > > > > Do you know if that is when you click the maximize button or drap up a > > > window, or double click on a window title bar ? > > > > That's a different bug this one concerned specifically the > > "BorderlessMaximizedWindows" case. > > Then why was my bug ( https://bugs.kde.org/show_bug.cgi?id=440380 ) marked > duplicate of this bug, if it's a different bug? Because bug triaging is an art and not science ^^ Mistakes happens I have reopened your bug with the script scenario. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 Méven Car changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 444526] Resolution of external 4k monitor sometimes changes to FHD
https://bugs.kde.org/show_bug.cgi?id=444526 --- Comment #2 from frederic.parre...@univ-grenoble-alpes.fr --- OK, I will run that and let you know the result when the problem occurs again. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 259352] Wish: Don't collapse Help topic tree in Documenation view
https://bugs.kde.org/show_bug.cgi?id=259352 Timon van der Berg changed: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |tmnvanderb...@gmail.com CC||tmnvanderb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 444523] Gwenview is not able to install plugins due to a typo
https://bugs.kde.org/show_bug.cgi?id=444523 --- Comment #1 from Paco Orozco --- I've seen that it's fixed in the master branch: https://github.com/KDE/gwenview/blob/df4c9a9fbacc81acea07e1bc300ce6d56f1cdefd/app/kipiinterface.cpp#L57 Maybe it's just releasing a bugfix for my version :sweat: -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 444526] Resolution of external 4k monitor sometimes changes to FHD
https://bugs.kde.org/show_bug.cgi?id=444526
--- Comment #3 from frederic.parre...@univ-grenoble-alpes.fr
---
This is already the output when in a normal state:
START: Requesting Config
Received config. Took 25 milliseconds
Screen:
maxSize: QSize(16384, 16384)
minSize: QSize(320, 200)
currentSize: QSize(3840, 2160)
-
Id: 66
Name: "eDP-1"
Type: "Panel (Laptop)"
Connected: true
Enabled: false
Primary: false
Rotation: KScreen::Output::None
Pos: QPoint(0,0)
MMSize: QSize(294, 165)
FollowPreferredMode: false
Scale: 1
Clones: None
Mode: ""
Preferred Mode: "70"
Preferred modes: ("70")
Modes:
"100""" QSize(1680, 1050) 59.8833
"101""" QSize(1600, 1024) 60.1691
"102""" QSize(1400, 1050) 59.9756
"103""" QSize(1600, 900) 59.9883
"104""" QSize(1600, 900) 59.9416
"105""" QSize(1600, 900) 59.946
"106""" QSize(1600, 900) 59.8248
"107""" QSize(1280, 1024) 60.0197
"108""" QSize(1440, 900) 59.8874
"109""" QSize(1400, 900) 59.9641
"110""" QSize(1400, 900) 59.8798
"111""" QSize(1280, 960) 60
"112""" QSize(1440, 810) 59.996
"113""" QSize(1440, 810) 59.9747
"114""" QSize(1368, 768) 59.882
"115""" QSize(1368, 768) 59.8532
"116""" QSize(1360, 768) 59.799
"117""" QSize(1360, 768) 59.96
"118""" QSize(1280, 800) 59.9866
"119""" QSize(1280, 800) 59.9716
"120""" QSize(1280, 800) 59.8103
"121""" QSize(1280, 800) 59.9095
"122""" QSize(1152, 864) 59.9971
"123""" QSize(1280, 720) 60.0008
"124""" QSize(1280, 720) 59.9911
"125""" QSize(1280, 720) 59.8551
"126""" QSize(1280, 720) 59.7447
"127""" QSize(1024, 768) 60.0373
"128""" QSize(1024, 768) 60.0038
"129""" QSize(960, 720) 60
"130""" QSize(928, 696) 60.0507
"131""" QSize(896, 672) 60.0144
"132""" QSize(1024, 576) 59.9534
"133""" QSize(1024, 576) 59.9593
"134""" QSize(1024, 576) 59.8992
"135""" QSize(1024, 576) 59.8195
"136""" QSize(960, 600) 59.9327
"137""" QSize(960, 600) 59.9988
"138""" QSize(960, 540) 59.9628
"139""" QSize(960, 540) 59.9879
"140""" QSize(960, 540) 59.629
"141""" QSize(960, 540) 59.8182
"142""" QSize(800, 600) 60
"143""" QSize(800, 600) 60.3165
"144""" QSize(800, 600) 56.25
"145""" QSize(840, 525) 60.0094
"146""" QSize(840, 525) 59.8833
"147""" QSize(864, 486) 59.9153
"148""" QSize(864, 486) 59.5703
"149""" QSize(800, 512) 60.1685
"150""" QSize(700, 525) 59.9756
"151""" QSize(800, 450) 59.946
"152""" QSize(800, 450) 59.8248
"153""" QSize(640, 512) 60.0197
"154""" QSize(720, 450) 59.8874
"155""" QSize(700, 450) 59.9641
"156""" QSize(700, 450) 59.8798
"157""" QSize(640, 480) 60
"158""" QSize(640, 480) 59.9405
"159""" QSize(720, 405) 59.5062
"160""" QSize(720, 405) 58.9879
"161""" QSize(684, 384) 59.882
"162""" QSize(684, 384) 59.8532
"163""" QSize(680, 384) 59.799
"164""" QSize(680, 384) 59.96
"165""" QSize(640, 400) 59.8824
"166""" QSize(640, 400) 59.9824
"167""" QSize(576, 432) 60.0642
"168""" QSize(640, 360) 59.8551
"169""" QSize(640, 360) 59.8255
"170""" QSize(640, 360) 59.8404
"171""" QSize(640, 360) 59.3249
"172""" QSize(512, 384) 60.0038
"173""" QSize(512, 288) 59.9994
"174""" QSize(512, 288) 59.9206
"175""" QSize(480, 270) 59.629
"176""" QSize(480, 270) 59.8182
"177""" QSize(400, 300) 60.3165
"178""" QSize(400, 300) 56.3401
"179""" QSize(432, 243) 59.9153
"180""" QSize(432, 243) 59.5703
"181""" QSize(320, 240) 60.0525
"182""" QSize(360, 202) 59.5062
"183""" QSize(360, 202) 59.129
"184""" QSize(320, 180) 59.8404
"185""" QSize(320, 180) 59.3249
"70""" QSize(3840, 2160) 59.9966
"71""" Q
[dolphin] [Bug 442850] Option for Information Panel to always show "real" date for recent file timestamps, not "Just Now", "Today", etc.
https://bugs.kde.org/show_bug.cgi?id=442850 Méven Car changed: What|Removed |Added CC||meve...@gmail.com Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #1 from Méven Car --- Best UI for information display criterias are IMHO Readability (fast to read), density (clear, easy to the eye), informativeness (keeps important data visible, while hiding superfluous ones). This date short format is easier to read than numbers, it shortens the strings so it is less dense and does not loose any information. So for those criteria it is as best as can be. "11/05/2446 00:38" (french date formatting here) at the opposite is harder to read and denser, for instance. There is no information loss to the user, when display "2 days ago 10:14" compared to "26/10/2021 10:14". Btw in the information panel we have a toggle to display date in a wider format (Right click). In the form "Tuesday 26th October, 20:14" >From your own POV you admit, this looks pretty and fits your use. So I don't see any issue here, just an overzealous missing setting feeling for other potential users. In fact I am thinking about shortening the dates in dolphin UI, hiding hours since they are very often of use while making UI denser, this would be a setting though. In the settings it could be like (with the default I am thinking about): Dates display : With hours: [ ] Display time of day with dates relative:[x] Use "Two days ago", "Just a moment ago" shortened: [x] Use days of the current week like "Tuesday" and skipping years for months of this year "10th of October" We would have the exact date in a tooltip on hover still and ordering wouldn't be affected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439919] kio_http_cache_cleaner is not terminated after the main application is finished
https://bugs.kde.org/show_bug.cgi?id=439919 --- Comment #2 from Ralf Habacker --- see also https://invent.kde.org/frameworks/kio/-/merge_requests/499 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442947] Some text in the Overview effect is blurry
https://bugs.kde.org/show_bug.cgi?id=442947 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/1576 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 398908] Dolphin uses up huge amounts of memory over time
https://bugs.kde.org/show_bug.cgi?id=398908 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #106 from Méven Car --- (In reply to Knut Hildebrandt from comment #103) > Back with a short summery of my observations. > > 1. with the moment of its start a dolphin instance begins to constantly > allocate memory > 2. the amount of memory allocated as well as the CPU time used correlates > with the number of tabs and views open and grows over time > 3. the memory allocation does not depend on user interaction. Opening files > several GB big does not cause any jump in memory usage. On the other hand > the memory usage increases constantly even without any user interaction at > all. > 4. hibernating the machine brings the used memory down to about 20 to 30 MB > for each instance, but within minutes, sometimes seconds, it is back to the > level before hibernation and than further rising > 5. over time and with many dolphins, tabs and views open not only the > dolphin instances get very slow but the machine too, due to constant swapping > > For me there arise a few questions: > > 1. why does dolphin constantly allocate memory even though there is no user > interaction? > 2. what does dolphin need the saved data for, since it obviously works well > with memory usage far below 100 MB even if there are many tabs open? > 3. Why once allocated memory never gets freed? > > All the data I mention here I gathered in KSysGuard. I've no idea what tools > I have to use to collect more useful data. > > One last thing. The original title of the bug report was something like > "Dolphin uses huge amounts of memory" and has been changed since a potential > memory leak has been identified. Since this bug was fixed the bug report has > been closed even though the problem I reported three years ago still exists. > Thus I'd propose to reopen the bug and change it's title back to the > original one. valgrind would be nice to use to check for memory leak. `valgrind dolphin` would suffice to learn a Does closing tabs or views release memory? To some extent dolphin will always use more memories for each tab and views, since each need an independent KCoreDirLister, that is a cache to read and access the filesystem and enrich the data, and those will use proportionally memory as the directory they access are big. We still have room for optimization for sure. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 435230] Media Player widget shows two tabs with one played Youtube video
https://bugs.kde.org/show_bug.cgi?id=435230 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 389914] dark theme -> export graph -> white on white export path text
https://bugs.kde.org/show_bug.cgi?id=389914 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/education/rkward/-/merge_requests/8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Roman Šmakal changed: What|Removed |Added CC||schmakeri...@gmail.com --- Comment #12 from Roman Šmakal --- Also, some laptops does not have low enough brigthness level. It would be cool to also add gray filter on screen to further reduce eye strain (pretty much exactly what blue light filter does, only with gray tones). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439919] kio_http_cache_cleaner is not terminated after the main application is finished
https://bugs.kde.org/show_bug.cgi?id=439919 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/620 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 Martin Senftleben changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #8 from Martin Senftleben --- OK, you lost me. I followed those duplicate bug links to some level (each one ended somewhere with "this is a duplicate bug of..."), and I am only little wiser than before. I did the obvious and tried to downgrade mariadb, but there are dependencies which don't allow me to downgrade. If I remove the entire package with its dependencies, I can only install the actual package, which I can't downgrade, because those dependencies are required by so many packages, that I would render my PC almost useless, if I uninstall all those packages (which I would have to do to get rid of those dependencies). So I rather do not use digikam any more - at least until this problem is solved. :-( -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 444527] New: Plasma browser integration should export one MPRIS instance per tab
https://bugs.kde.org/show_bug.cgi?id=444527 Bug ID: 444527 Summary: Plasma browser integration should export one MPRIS instance per tab Product: plasma-browser-integration Version: unspecified Platform: Netrunner OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Plasma Browser Integration does always export a single MPRIS instance. This is problematic if multiple tabs with audio exist. E.g., one tab soundcloud, another tab youtube. In this case the MPRIS interface only controls the tab for which the audio/video was started last. Thus, speaking in the above example it is impossible to control the soundcloud tab after starting a youtube video. This is a typical use case for me, where I want to stop or resume music when starting youtube videos. When I forgot to stop the music in advance, I am unable to stop it via MPRIS anymore. Therefore I propose to export one MPRIS interface per media tab. (Since some users might be annoyed or confused by to many instances, it might be a good way to make this optional) Operating System: Gentoo Linux Plasma Browser Integration: 1.8.0.1 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-gentoo (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 330378] battery plasma widget says no battery available although solid device and plasma engine show battery data
https://bugs.kde.org/show_bug.cgi?id=330378 Roman Šmakal changed: What|Removed |Added CC||schmakeri...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444528] New: No battery detected by battery widget
https://bugs.kde.org/show_bug.cgi?id=444528 Bug ID: 444528 Summary: No battery detected by battery widget Product: plasmashell Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: schmakeri...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142960 --> https://bugs.kde.org/attachment.cgi?id=142960&action=edit Direct comparison widget to kinfocenter Battery widget does not show any active battery, even though (for example) kinfocenter knows about them. Operating System: Garuda Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ m5-6Y57 CPU @ 1.10GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 515 Toshiba Z20t-C detachable tablet It seems like battery widget fetches battery status too early and does not update it anymore. As soon as i undock keyboard and dock it back, it gets informations about keyboard battery, but tablet battery remains undetected. Feel free to contact me for more logs (i have no idea what logs may be necessary). This did not happen on earlier versions of Plasma desktop, but i cant really confirm at which version exactly this thing started. From checking package cache it seems like i had 5.22.5 installed before upgrade, but i can't confirm this for sure. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 444527] Plasma browser integration should export one MPRIS instance per tab
https://bugs.kde.org/show_bug.cgi?id=444527 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 395461 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 395461] multiple video support
https://bugs.kde.org/show_bug.cgi?id=395461 Kai Uwe Broulik changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de --- Comment #5 from Kai Uwe Broulik --- *** Bug 444527 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 403802] leak_cpp_interior fails with some reachable blocks different than expected
https://bugs.kde.org/show_bug.cgi?id=403802 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444409] When you call the menu with the right button in the workrave program, Plasma consumes 100% of the CPU
https://bugs.kde.org/show_bug.cgi?id=09 Łukasz Żarnowiecki changed: What|Removed |Added CC||luk...@zarnowiecki.pl --- Comment #1 from Łukasz Żarnowiecki --- I have the same problem with plasma 5.23.2 and workrave 1.10.48. It does not happen all the time, but when you close workrave window, reopen from tray it would render plasma unusable and only sddm restart can help. It used to work fine with plasma < 5.23 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444529] New: [Wayland] Menus sometimes open at the wrong horizontal position on dual-monitor setups
https://bugs.kde.org/show_bug.cgi?id=444529 Bug ID: 444529 Summary: [Wayland] Menus sometimes open at the wrong horizontal position on dual-monitor setups Product: kwin Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: sjurberengal+...@gmail.com Target Milestone: --- SUMMARY On a dual-monitor setup where the left monitor is smaller than the right, menus opened on the right monitor have the wrong horizontal position if the window coordinate of the click is outside the range of possible screen coordinates of the left monitor. The range of possible coordinates take into account the vertical position relative to the right monitor, so if for example the top of the left monitor is set to 100px below the top of the right monitor, the vertical span of the left monitor is 100-1180 (on a 1080p monitor). The horizontal coordinate seems to always start at 0. It's the window coordinate of the open window that matters, not the screen coordinate on the right screen. This makes the bug very noticeable if the left monitor isn't top-aligned vertically since every menubar menu opens on the far right and is very hard to use. But the bug still appears when clicking to the right or below the left monitor size. You just need a large enough window and a reason to open a menu in those extreme positions. The vertical position is correct, but the horizontal position is set equal to the max horizontal position of the left monitor. STEPS TO REPRODUCE 1. Have two monitors with different resolutions (scaling works) 2. Put the smallest monitor left of the larger in the display configuration system setting. It's easiest to see if the top of the left monitor is below the top of the right monitor. 3. Open Kate (or another KDE program) on the right monitor and open a menu (from the menubar, right-click or dropdown) in different positions on the window OBSERVED RESULT The opened menu sometimes opens far to the right, at the max horizontal position of the left monitor. EXPECTED RESULT The opened menu always appears under or right next to the mouse. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (5.14.14-arch1-1) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This doesn't happen on X11. Most programs have this issue, but not all of them. Every KDE app I've tried has this bug, but firefox and KeePassXC doesn't, and right-clicking on the desktop also works as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444529] [Wayland] Menus sometimes open at the wrong horizontal position on dual-monitor setups
https://bugs.kde.org/show_bug.cgi?id=444529 --- Comment #1 from sjurberengal+...@gmail.com --- Created attachment 142961 --> https://bugs.kde.org/attachment.cgi?id=142961&action=edit Demonstration of the wrong menu position -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 396016] KMYMoney GPG option is grayed out even though GPG installed
https://bugs.kde.org/show_bug.cgi?id=396016 --- Comment #27 from Ralf Habacker --- (In reply to Nigel from comment #26) > Created attachment 142958 [details] > Screenshot of processes > > I see these processes when I try to do an online update Looks good. Another workaround could be this recipe: 1. Start cmd.exe in the `bin` dir of the kmymoney installation 2. enter set KIO_FORK_SLAVES=1 kmymoney and press return 4. try to update online quotes -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 342056] Ridiculously slow file copy (multiple small files)
https://bugs.kde.org/show_bug.cgi?id=342056 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441222] Change folder icon not work on Windows
https://bugs.kde.org/show_bug.cgi?id=441222 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441219] Shortcut file (.lnk) not work on Windows.
https://bugs.kde.org/show_bug.cgi?id=441219 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407713] Program shows incorrect partition table for NTFS formatted device created in Windows
https://bugs.kde.org/show_bug.cgi?id=407713 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 413026] [Dolphin]: no completion and wrong dirseparators in the location bar on MS Windows
https://bugs.kde.org/show_bug.cgi?id=413026 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444479] digikam doesn't start, instead "cannot process schema initialization"
https://bugs.kde.org/show_bug.cgi?id=79 --- Comment #9 from Maik Qualmann --- With the current MariaDB you will not be spared to carry out a "mariadb-upgrade" in the future either. Go to a terminal, become "root" and enter "mariadb-upgrade". Then digiKam should update the database schema without any problems. Whether digiKam will then crash sporadically depends on whether your distribution has already integrated the corresponding Qt patches. You should then report the problem to your distribution with the corresponding bug report from digiKam. Maik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444241] The installer that is for Windows that is for Dolphin is outdated.
https://bugs.kde.org/show_bug.cgi?id=444241 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 433698] Setting keys from the numpad as a shortcut is buggy
https://bugs.kde.org/show_bug.cgi?id=433698 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 430171] Cannot open a file if the file path is long (exceeds 260 characters) on Windows platforms
https://bugs.kde.org/show_bug.cgi?id=430171 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411443] Close button (Alt+F4) greyed out
https://bugs.kde.org/show_bug.cgi?id=411443 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 369085] Umbrello/KF5 does not show icons
https://bugs.kde.org/show_bug.cgi?id=369085 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-threadweaver] [Bug 414343] Getting "terminate called after throwing an instance of 'std::bad_alloc'"
https://bugs.kde.org/show_bug.cgi?id=414343 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413025] Dolphin: titlebar close button and Alt-F4 disabled
https://bugs.kde.org/show_bug.cgi?id=413025 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 388184] wrong folder to store user settings under Windows
https://bugs.kde.org/show_bug.cgi?id=388184 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 429943] Window size broken on Windows
https://bugs.kde.org/show_bug.cgi?id=429943 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 428574] 2nd drive not appearing
https://bugs.kde.org/show_bug.cgi?id=428574 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 391922] kdeinit5 is not reloactable as it ignores files outside of CMAKE_INSTALL_PREFIX
https://bugs.kde.org/show_bug.cgi?id=391922 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[calligragemini] [Bug 444531] New: Crash when trying to insert MATLAB formula
https://bugs.kde.org/show_bug.cgi?id=444531 Bug ID: 444531 Summary: Crash when trying to insert MATLAB formula Product: calligragemini Version: 3.2.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: hicham.barou...@live.com Target Milestone: --- Application: calligragemini (3.2.1) Qt Version: 5.15.2 Frameworks Version: 5.87.0 Operating System: Linux 5.14.14-1-ck x86_64 Windowing System: X11 Distribution: Arch Linux DrKonqi: 5.23.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was trying to insert a formula in MATLAB syntax. To reproduce the bug, I repeated a few more times, and it always happened. The crash can be reproduced every time. -- Backtrace: Application: Calligra Gemini (calligragemini), signal: Segmentation fault [KCrash Handler] #4 0x7f77e08d5638 in Cauchy::DeclarationsRegistry::constant(Cauchy::String const&) const () from /usr/lib/libCauchy.so.0.0 #5 0x7f77e08e0c01 in Cauchy::VariablesManager::getVariable(Cauchy::String const&, bool) () from /usr/lib/libCauchy.so.0.0 #6 0x7f77e08da127 in Cauchy::Parser::parsePrimaryExpression() () from /usr/lib/libCauchy.so.0.0 #7 0x7f77e08daa6c in Cauchy::Parser::parseExpression(Cauchy::Parser::ExpressionParseMode) () from /usr/lib/libCauchy.so.0.0 #8 0x7f77e08dc353 in Cauchy::Parser::parseArguments[abi:cxx11]() () from /usr/lib/libCauchy.so.0.0 #9 0x7f77e08da1c2 in Cauchy::Parser::parsePrimaryExpression() () from /usr/lib/libCauchy.so.0.0 #10 0x7f77e08daa6c in Cauchy::Parser::parseExpression(Cauchy::Parser::ExpressionParseMode) () from /usr/lib/libCauchy.so.0.0 #11 0x7f77e08dae8b in Cauchy::Parser::parseStatement() () from /usr/lib/libCauchy.so.0.0 #12 0x7f77e08dc1c1 in Cauchy::Parser::parseBody() () from /usr/lib/libCauchy.so.0.0 #13 0x7f77e08dc274 in Cauchy::Parser::parse() () from /usr/lib/libCauchy.so.0.0 #14 0x7f77e08d0ca5 in Cauchy::Source::compile() () from /usr/lib/libCauchy.so.0.0 #15 0x7f78040021db in m2mml(std::__cxx11::basic_string, std::allocator > const&, std::__cxx11::basic_string, std::allocator >&, std::__cxx11::basic_string, std::allocator >*) () from /usr/lib/libm2mml.so.0.0 #16 0x7f77e09941b7 in ?? () from /usr/lib/qt/plugins/calligra/shapes/calligra_shape_formula.so #17 0x7f781d95a7e0 in ?? () from /usr/lib/libQt5Core.so.5 #18 0x7f781d95a7e0 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x7f781e55335b in QWidgetLineControl::processKeyEvent(QKeyEvent*) () from /usr/lib/libQt5Widgets.so.5 #20 0x7f781e5462dc in QLineEdit::keyPressEvent(QKeyEvent*) () from /usr/lib/libQt5Widgets.so.5 #21 0x7f781e43cf98 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #22 0x7f781e3f8d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #23 0x7f781e400c07 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #24 0x7f781d9233fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #25 0x7f781e458e10 in ?? () from /usr/lib/libQt5Widgets.so.5 #26 0x7f781e3f8d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #27 0x7f781d9233fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #28 0x7f781dcf8084 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /usr/lib/libQt5Gui.so.5 #29 0x7f781dcd17d5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #30 0x7f781811ffcc in ?? () from /usr/lib/libQt5XcbQpa.so.5 #31 0x7f781b8074dc in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #32 0x7f781b85b749 in ?? () from /usr/lib/libglib-2.0.so.0 #33 0x7f781b804bc1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #34 0x7f781d97c026 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #35 0x7f781d921d6c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #36 0x7f781d92a2d4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #37 0x55bcec83d646 in ?? () #38 0x7f781d2adb25 in __libc_start_main () from /usr/lib/libc.so.6 #39 0x55bcec83d7de in _start () [Inferior 1 (process 31972) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443956] can't change the storage location
https://bugs.kde.org/show_bug.cgi?id=443956 b...@mogwai.be changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from b...@mogwai.be --- Further analysis revealed that the QML FolderDialog component has issues when the folder has been picked through xdg-desktop-portal (which is the case with flatpak versions). It seems like this is an upstream Qt problem. We'll try to file an issue upstream for this. In the meantime, it seems that the FileDialog from QtQuick.Dialogs can be used as workaround. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444532] New: ten brushes seemed to occur an error
https://bugs.kde.org/show_bug.cgi?id=444532 Bug ID: 444532 Summary: ten brushes seemed to occur an error Product: krita Version: 4.4.8 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: shishimaru...@gmail.com Target Milestone: --- Created attachment 142962 --> https://bugs.kde.org/attachment.cgi?id=142962&action=edit >From Krita's error dialogue SUMMARY After adding a pattern in a brush (ink 3 g-pen in my case), changing to the brush became too slow. STEPS TO REPRODUCE (might) 1. add a pattern to a pen 2. tweaked brush setting (I checked rotation etc) 3. overwrote brush OBSERVED RESULT Too slow only to open the ten brushes' dialog of the pen when clicking 'Edit brush setting' in the tool bar or typing Ctrl+Alt+3 (in my case). EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: windows10 21H1 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.
[systemsettings] [Bug 354109] Custom shortcuts: Window Data autodetect (conditions > new > active window) removes mouse button function
https://bugs.kde.org/show_bug.cgi?id=354109 Adam Fontenot changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||adam.m.fontenot+kde@gmail.c ||om Ever confirmed|0 |1 --- Comment #8 from Adam Fontenot --- This issue has seemingly been around since around the time of the switch from QT4 to QT5. The main issue is here: https://invent.kde.org/plasma/khotkeys/-/blob/master/kcm_hotkeys/helper_widgets/window_selector.cpp#L36 QT5 passes xinput events here, but the filter only looks for the XCB_BUTTON_PRESS response type. Proper handling would involve looking for a XCB_GE_GENERIC response type as well, casting to a xcb_ge_generic_event_t, and checking that event for the XCB_INPUT_BUTTON_PRESS event type. I wrote an ugly proof of concept showing that this does fix the basic problem, but I didn't fully get the feature working again. Among other issues, clicking on a window that doesn't belong to the KCM seemingly gives a different event type, and the crosshair cursor is not used over these windows either. Probably KWin has changed how windows are given access to other windows they don't own, or something along those lines. Wasn't sure how to investigate this further. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444519] System Settings crash upon opening Window Decoration Module
https://bugs.kde.org/show_bug.cgi?id=444519 --- Comment #2 from ryu.ketsu...@outlook.com --- I don't have Aurorae Window Decorations installed, only Breeze forks compiled from source and installed using 'make install', more specifically ClassikStyles and Lightly. Recently I have built the two against the commits I have of their respective dependencies so I'm not sure what could be causing the crash, if they really are being caused by a window decoration. Both Lightly and ClassikStyles also have an Application Style, also forked from Breeze but those don't crash System Settings. However, they do with Window Decorations. Is there a way of finding out which of the two, or if both are causing the issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444361] A lot of GTK based apps have broken fonts
https://bugs.kde.org/show_bug.cgi?id=444361 --- Comment #10 from Bacteria --- The ArchWiki suggests to put GTK_USE_PORTAL=1 to force Firefox to use KDE's file picker instead of GTK one. But this seems to be having a side effect on the Breeze GTK theme. This was all fine on X but Wayland seems to have altered the behavior. So this might just be an upstream change. I had set GTK_USE_PORTAL=1 as per ArchWiki's recommendation because of which this was happening and this also explains why GTK_USE_PORTAL=0 fixed the issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444519] System Settings crash upon opening Window Decoration Module
https://bugs.kde.org/show_bug.cgi?id=444519 --- Comment #3 from ryu.ketsu...@outlook.com --- That and the two are working perfectly fine without any crashes on their own and making changes to their respective configuration files. The issue must be on how System Settings is seeing them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444533] New: Shadow gradients in wrong direction
https://bugs.kde.org/show_bug.cgi?id=444533 Bug ID: 444533 Summary: Shadow gradients in wrong direction Product: plasmashell Version: 5.22.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: hoffmann_lor...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142963 --> https://bugs.kde.org/attachment.cgi?id=142963&action=edit Screenshot of the system tray panel SUMMARY On Wayland, I often see shadow gradients going in the wrong way, from transparent to dark. STEPS TO REPRODUCE 1. Open a panel from the system tray, the application menu or place or whatever. OBSERVED RESULT The shadow is in the wrong direction EXPECTED RESULT Shadow should go from dark to transparent. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.10.70-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION As far as I can see, the direction is only wrong on the top and right side of panels. The shadows behind windows look fine. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 443956] can't change the storage location
https://bugs.kde.org/show_bug.cgi?id=443956 b...@mogwai.be changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma-mobile/kasts/commit/5b15 ||f4c7b99df14bd11323edd6e43cd ||07ae5ee33 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from b...@mogwai.be --- Git commit 5b15f4c7b99df14bd11323edd6e43cd07ae5ee33 by Bart De Vries. Committed on 28/10/2021 at 11:12. Pushed by bdevries into branch 'master'. Solve issue with FolderDialog FolderDialog has issues retrieving the selected folder if that folder has been selected through xdg-desktop-portal (i.e. flatpaks). Reverting to FileDialog from QtQuick.Dialogs. M +5-5src/qml/SettingsPage.qml https://invent.kde.org/plasma-mobile/kasts/commit/5b15f4c7b99df14bd11323edd6e43cd07ae5ee33 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444519] System Settings crash upon opening Window Decoration Module
https://bugs.kde.org/show_bug.cgi?id=444519 --- Comment #4 from ryu.ketsu...@outlook.com --- One quick note. Anticipating this kind of suggestion, I attempted to uninstall ClassikStyles and Lightly using their respective 'make uninstall' and it crashed KWin immediately after restarting and the problem on System Settings crashing when attempting to open the Window Decoration section persists -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392059] Failed to run Ten Brushes script
https://bugs.kde.org/show_bug.cgi?id=392059 Ziyad Rahmani changed: What|Removed |Added CC||mziyad...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 Andrey changed: What|Removed |Added CC||butir...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=411884 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=440380 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442098] Krita 5.1.0 prealpha :Ten Brushes, can't switch back to previous preset after pressing key twice
https://bugs.kde.org/show_bug.cgi?id=442098 Ziyad Rahmani changed: What|Removed |Added CC||mziyad...@gmail.com Component|Shortcuts and Canvas Input |Scripting |Settings| --- Comment #6 from Ziyad Rahmani --- (In reply to stephen from comment #5) > (In reply to Halla Rempt from comment #3) > > No, only developers should change the status of a bug. > > > > Resolved/Worksforme means: it works for me, I cannot investigate this report > > anymore since there's nothing left for me to try and test or debug. > > New update : > The issue seems to be caused from the retrieval of brush settings from the > sqlite database of a previous Krita version. Especially coming from 5.0.0 > beta 1 to later versions. A break happens in the process apparently, causing > the brush history to not work as expected with the Ten brushes script. > I tried to completely remove any sqlite backup before starting Krita and the > ten brushes script worked fine. How to do that? I'm sorry, I don't have understanding about these things -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 444534] New: Akonadi crashes when Gmail root folder clicked in KMail
https://bugs.kde.org/show_bug.cgi?id=444534 Bug ID: 444534 Summary: Akonadi crashes when Gmail root folder clicked in KMail Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: skonjic...@gmail.com Target Milestone: --- Application: akonadiserver (5.14.2 (20.04.2)) Qt Version: 5.12.7 Frameworks Version: 5.71.0 Operating System: Linux 5.3.18-lp152.95-preempt x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.2" -- Information about the crash: - What I was doing when the application crashed: For some reason, KMail shows a large number of unread mails on root of IMAP account (Gmail). It happened without any obvious reason, and nothing was changed in account settings. Each time when I click to see the list of unread messages, Akonadi crashes. Restarting Akonadi, Kontact or laptop doesn't change the behavior. - Custom settings of the application: Just Gmail account. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x7fe0c311c1ec in QString::operator=(QString const&) () from /usr/lib64/libQt5Core.so.5 #5 0x5626e3327855 in ?? () #6 0x7fe0c329ef4f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #7 0x5626e3378764 in ?? () #8 0x5626e332afee in ?? () #9 0x7fe0c329ef4f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #10 0x7fe0c39dbd5f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib64/libQt5DBus.so.5 #11 0x7fe0c329f9e2 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #12 0x7fe0c326f311 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #13 0x7fe0c3271ee7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #14 0x7fe0c32ccd93 in ?? () from /usr/lib64/libQt5Core.so.5 #15 0x7fe0bee3d624 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #16 0x7fe0bee3d9c0 in ?? () from /usr/lib64/libglib-2.0.so.0 #17 0x7fe0bee3da4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #18 0x7fe0c32cc3af in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #19 0x7fe0c326d57a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #20 0x7fe0c309290a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #21 0x7fe0c30940b2 in ?? () from /usr/lib64/libQt5Core.so.5 #22 0x7fe0c143b539 in start_thread () from /lib64/libpthread.so.0 #23 0x7fe0c2713ecf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fe0b3fff700 (LWP 28139) "CacheCleaner-Th"): #1 0x7fe0bee3d939 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe0bee3da4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe0c32cc3cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe0c326d57a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe0c309290a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe0c30940b2 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fe0c143b539 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe0c2713ecf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fe0b8d5c700 (LWP 28138) "NotificationMan"): #1 0x7fe0bee3d939 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe0bee3da4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe0c32cc3cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe0c326d57a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe0c309290a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe0c30940b2 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fe0c143b539 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe0c2713ecf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe0b9a3d700 (LWP 28135) "QDBusConnection"): #1 0x7fe0bee3d371 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe0bee3d8e0 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe0bee3da4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe0c32cc3cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe0c326d57a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe0c309290a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7fe0c3981e65 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7fe0c30940b2 in ?? () from /usr/lib64/
[systemsettings] [Bug 444535] New: Window filtering conditions for custom shortcuts (usually) don't work
https://bugs.kde.org/show_bug.cgi?id=444535 Bug ID: 444535 Summary: Window filtering conditions for custom shortcuts (usually) don't work Product: systemsettings Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: adam.m.fontenot+...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY This is potentially annoying to debug because it seems to rarely function just fine. It's just that usually, it doesn't. I'm happy to follow any debugging suggestions given, I can even recompile khotkeys if necessary. STEPS TO REPRODUCE 1. Create a new custom shortcuts group. 2. Set the action to be anything involving an active window. I set mine so that the window title has to contain "a". 3. Add a global shortcut that sends keyboard input to the group. Set the trigger to whatever you like, and the action to insert some arbitrary text. 4. Click in a window that matches the requirements you set in 2. OBSERVED RESULT The window behaves as if there was no shortcut. If I set the shortcut to Alt+O, for example, then "o" is printed in the textbox that has focus. If the program that owns the window has its own shortcuts, those execute instead of the global shortcut. EXPECTED RESULT The window does not receive the key events at all. Instead, whatever text was entered in step 3 is typed into the window instead. SOFTWARE/OS VERSIONS Linux: Arch Linux x86_64 (kernel 5.14.14) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 OTHER NOTES: Certain shortcuts triggers disappear when I close and reopen system settings. I assume that issue is https://bugs.kde.org/show_bug.cgi?id=300532 There seems no pattern to which shortcuts don't work - none of them, to my knowledge, is otherwise bound as a global shortcut. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444399] disInstr(arm64): unhandled instruction 0xC87F2D89
https://bugs.kde.org/show_bug.cgi?id=444399
Hans Kratz changed:
What|Removed |Added
CC||h...@appfour.com
--- Comment #3 from Hans Kratz ---
This seems to be bug in valgrind. Support for some ld*p instructions (which are
ARMv8.0) is not implemented. Simple reproducer in C++ for stxp:
--- snip ---
#include
int main() {
std::atomic<__int128_t> x;
x.store(23, std::memory_order_relaxed);
}
--- snip ---
$ clang++-12 main.cxx -o main
$ valgrind ./main
==25164== Memcheck, a memory error detector
==25164== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==25164== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==25164== Command: ./main
==25164==
ARM64 front end: load_store
disInstr(arm64): unhandled instruction 0xC87F3168
disInstr(arm64): 1100'1000 0111' 0011'0001 0110'1000
==25164== valgrind: Unrecognised instruction at address 0x400690.
==25164==at 0x400690: std::atomic<__int128>::store(__int128,
std::memory_order) (in /data/dev/clangtest/main)
==25164==by 0x4005F7: main (in /data/dev/clangtest/main)
==25164== Your program just tried to execute an instruction that Valgrind
==25164== did not recognise. There are two possible reasons for this.
==25164== 1. Your program has a bug and erroneously jumped to a non-code
==25164==location. If you are running Memcheck and you just saw a
==25164==warning about a bad jump, it's probably your program's fault.
==25164== 2. The instruction is legitimate but Valgrind doesn't handle it,
==25164==i.e. it's Valgrind's fault. If you think this is the case or
==25164==you are not sure, please let us know and we'll try to fix it.
==25164== Either way, Valgrind will now raise a SIGILL signal which will
==25164== probably kill your program.
==25164==
==25164== Process terminating with default action of signal 4 (SIGILL)
==25164== Illegal opcode at address 0x400690
==25164==at 0x400690: std::atomic<__int128>::store(__int128,
std::memory_order) (in /data/dev/clangtest/main)
==25164==by 0x4005F7: main (in /data/dev/clangtest/main)
==25164==
==25164== HEAP SUMMARY:
==25164== in use at exit: 0 bytes in 0 blocks
==25164== total heap usage: 1 allocs, 1 frees, 72,704 bytes allocated
==25164==
==25164== All heap blocks were freed -- no leaks are possible
==25164==
==25164== For lists of detected and suppressed errors, rerun with: -s
==25164== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction (core dumped)
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 444536] New: Compositor slows down to ~1fps after changing any of the compositor settings or restarting kwin
https://bugs.kde.org/show_bug.cgi?id=444536 Bug ID: 444536 Summary: Compositor slows down to ~1fps after changing any of the compositor settings or restarting kwin Product: kwin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: yabo...@gmail.com Target Milestone: --- SUMMARY Compositor slows down to ~1fps after changing any of the compositor settings. It can also be triggered by running `kwin --replace`. The only way I found of fixing this is to log out and back in. STEPS TO REPRODUCE 1. Log in to KDE. The compositor runs smoothly 2. Change compositor settings or restart kwin with `kwin --replace`. 3. Compositor now runs extremely slowly, around 1 fps. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 21.04 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Video demonstrating the issue: https://photos.app.goo.gl/373CiNmyF4MGjUZU6 There is no significant CPU or GPU utilization when the problem is triggered. The only way I found to make the desktop usable again without logging out is to change the compositor engine to XRender. kwin --replace prints the following: pmitas@pmitas-ThinkPad-T490 ~ kwin --replace & [1] 54579 ⚙ pmitas@pmitas-ThinkPad-T490 ~ kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line ⚙ pmitas@pmitas-ThinkPad-T490 ~ OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (WHL GT2) OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3 OpenGL shading language version string: 4.60 Driver: Intel GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 21.0.3 X server version: 1.20.11 Linux kernel version: 5.11 Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_core: XCB error: 10 (BadAccess), sequence: 3883, resource id: 1998, major code: 142 (Composite), minor code: 2 (RedirectSubwindows) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 444537] New: when toggling keyboard layout, shortcuts continue to use the old layout
https://bugs.kde.org/show_bug.cgi?id=444537 Bug ID: 444537 Summary: when toggling keyboard layout, shortcuts continue to use the old layout Product: frameworks-kglobalaccel Version: 5.87.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- SUMMARY I use Dvorak and Qwerty layouts interchangeably. KDE ships with a bunch of shortcuts by default, for example opening Dolphin has the default shortcut Meta+E. When I log in to KDE with one layout set as default, then toggle to the other layout, shortcuts continue to use the original layout. STEPS TO REPRODUCE 1. Set your input methods to include both Dvorak and Qwerty, with Dvorak set as default. Make sure the keyboard layout toggle widget is visible in your taskbar. Make sure Dolphin is set to open with the Meta+E shortcut (should be the default). 2. Reboot and log in. 3. Press Meta+E (because your keyboard layout is now Dvorak, that's the physical keys Meta+D on a standard US Qwerty keyboard). 4. Close Dolphin if it appears. 5. Toggle your keyboard layout to Qwerty. 6. Press Meta+D (same as the physical keys, because you're now using Qwerty) OBSERVED RESULT Dolphin appears both times. EXPECTED RESULT Dolphin should appear the first time, but not appear the second time. The keyboard shortcut has not changed (it's Meta+E), but you are now pressing the keys Meta+D. SOFTWARE/OS VERSIONS Linux: Arch Linux x86_64 (kernel 5.14.14) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I think this *might* be caused by the keyboard layout switcher not changing the layout configured via the X keyboard extension. When I switch to Qwerty, I still see the following: $ setxkbmap -query rules: evdev model: pc101 layout: dvorak,us So probably X still thinks I'm using Dvorak, so maybe the keycodes that kglobalaccel sees are still the Dvorak keys. If that's the issue and this belongs in a different component, I'd appreciate someone helping me move it there. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444296] digiKam starts but does not open a window. Showfoto does the same.
https://bugs.kde.org/show_bug.cgi?id=444296 --- Comment #12 from Tom van Dijk --- I have added another user account on my PC and the program worked OK. This new user did not have access to the NAS server. Is that where the problem may exist? Regards, Tom -Oorspronkelijk bericht- Van: Maik Qualmann Verzonden: dinsdag 26 oktober 2021 8:00 Aan: tomvd...@home.nl Onderwerp: [digikam] [Bug 444296] digiKam starts but does not open a window. Showfoto does the same. https://bugs.kde.org/show_bug.cgi?id=444296 --- Comment #10 from Maik Qualmann --- We won't find a solution here. I remember we had the same problem with a user some time ago. His problem only existed on one user account, the problem did not occur on other user accounts. Maik -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. You reported the bug.= -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 436888] Change subtitle color & Sharpen video
https://bugs.kde.org/show_bug.cgi?id=436888 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 444538] New: 'Report bug...' button does not work
https://bugs.kde.org/show_bug.cgi?id=444538 Bug ID: 444538 Summary: 'Report bug...' button does not work Product: Haruna Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: bugsefor...@gmx.com Target Milestone: --- SUMMARY I'm using master branch on neon unstable. Nothing happens when I click on 'Report bug..." button present in 'About' section of Haruna settings. EXPECTED RESULT open the page to report a bug with default internet browser. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 444539] New: Video opens paused if 'Auto load videos from same folder' in unchecked n Haruna settings
https://bugs.kde.org/show_bug.cgi?id=444539 Bug ID: 444539 Summary: Video opens paused if 'Auto load videos from same folder' in unchecked n Haruna settings Product: Haruna Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: bugsefor...@gmx.com Target Milestone: --- STEPS TO REPRODUCE 1. open Haruna settings 2. click on 'Playlist' in the left side 3. uncheck 'Auto load videos from same folder' 4. close Haruna 5. open a video with Haruna via file manager OBSERVED RESULT video opens paused EXPECTED RESULT video plays on opening SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-38-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444296] digiKam starts but does not open a window. Showfoto does the same.
https://bugs.kde.org/show_bug.cgi?id=444296 --- Comment #13 from Maik Qualmann --- It will not be related to access to a network drive. I could imagine that you have installed another software that is also based on Qt and that software has set path variables or something similar. But it is difficult to give help from outside how you can look for the cause. Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406489] Can not save/export images in pdf file
https://bugs.kde.org/show_bug.cgi?id=406489 Daniel changed: What|Removed |Added CC||daniel-other+kdebug@dadosch ||.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443330] Undoing/redoing merged strokes from Cumulative Undo tends to result in safe asserts and leftover artifacts
https://bugs.kde.org/show_bug.cgi?id=443330 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1127 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444540] New: [feature request] support paste multiple contents once
https://bugs.kde.org/show_bug.cgi?id=444540 Bug ID: 444540 Summary: [feature request] support paste multiple contents once Product: plasmashell Version: master Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: 2797516...@qq.com Target Milestone: 1.0 hope that klipper can choose several clipboard contents and paste them all -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444532] ten brushes occurred an error
https://bugs.kde.org/show_bug.cgi?id=444532 Kate Hayashi changed: What|Removed |Added Summary|ten brushes seemed to occur |ten brushes occurred an |an error|error --- Comment #1 from Kate Hayashi --- Self reply After posting this error, I checked Krita's configure files. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 435732] memcheck/tests/leak_cpp_interior fails with gcc11
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #6 from Paul Floyd ---
We should be looking at leak_cpp_interior.stderr.diff-64bit rather than
leak_cpp_interior.stderr.diff (same for 403802)
With g++ 9.2 on RHEL 7 I get a similar failure, but without the still reachable
that I get with g++ 5.3.
Running the test standalone as follows
../../vg-in-place
--leak-check-heuristics=multipleinheritance,stdstring,newarray,length64
--suppressions=libstdc++.supp --leak-check=full --show-reachable=yes
./leak_cpp_interior
it looks like the problem is due to mismatches of the suppressions in
libstdc++.supp and those produced by different GCC/libstc++ versions.
The following diff may be a fix
diff --git a/memcheck/tests/libstdc++.supp b/memcheck/tests/libstdc++.supp
index 520e6613a..475e2d9fa 100644
--- a/memcheck/tests/libstdc++.supp
+++ b/memcheck/tests/libstdc++.supp
@@ -81,10 +81,7 @@
fun:pool
fun:__static_initialization_and_destruction_0
fun:_GLOBAL__sub_I_eh_alloc.cc
- fun:call_init.part.0
- fun:call_init
- fun:_dl_init
- obj:*lib*/ld-2.*.so
+ obj:*lib*/libstdc++.so*
}
{
malloc-leaks-cxx-stl-string-classes-debug2
--
You are receiving this mail because:
You are watching all bug changes.
[Haruna] [Bug 444538] 'Report bug...' button does not work
https://bugs.kde.org/show_bug.cgi?id=444538 george fb changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/mult ||imedia/haruna/commit/96777e ||e4a1f19cca2ad153d31f64c0fd1 ||b96eeb9 --- Comment #1 from george fb --- Git commit 96777ee4a1f19cca2ad153d31f64c0fd1b96eeb9 by George Florea Bănuș. Committed on 28/10/2021 at 13:05. Pushed by georgefb into branch 'master'. fix: report bug button in about page not working M +2-1src/application.cpp https://invent.kde.org/multimedia/haruna/commit/96777ee4a1f19cca2ad153d31f64c0fd1b96eeb9 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444242] s390x: Valgrind crashes on EXRL with negative offset
https://bugs.kde.org/show_bug.cgi?id=444242 Andreas Arnez changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Andreas Arnez --- Applied as commit b77dbefe72e4a5c7bcf1576a02c909010bd56991. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438880] Image Sequence animation is ignored when rendering to video file
https://bugs.kde.org/show_bug.cgi?id=438880 Paul Worrall changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||p.r.worr...@gmail.com --- Comment #3 from Paul Worrall --- I can reproduce this with version 21.08.2 installed from KDE Neon User Edition packages, except that in my case the animations are not visible in the Project or Clip Monitors either. Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-38-generic (64-bit) Graphics Platform: X11 Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: AMD CEDAR -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444532] ten brushes occurred an error
https://bugs.kde.org/show_bug.cgi?id=444532 --- Comment #2 from Kate Hayashi --- following above. I found out a funny record in C:\Users\\AppData\Roaming\krita\kis_brushes.blacklist. The pattern name I added was being registered as .png. As I used 'UTF-8'(kanji).png, Krita seemed not to be able to process it. I delete it and re-register the pattern as .png then deleted files relevant to this bug. Now Krita looks like running well. I hope to be able to use UTF-8 code. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 444539] Video opens paused if 'Auto load videos from same folder' in unchecked n Haruna settings
https://bugs.kde.org/show_bug.cgi?id=444539 --- Comment #1 from george fb --- Make sure you're not opening a file that you opened before. If you opened before then it resumes from last time (can be disabled in settings > playback) and is paused. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 444523] Gwenview is not able to install plugins due to a typo
https://bugs.kde.org/show_bug.cgi?id=444523 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||nicolas.fe...@gmx.de --- Comment #2 from Nicolas Fella --- This is fixed in version 20.08. your version (20.04) is no longer supported *** This bug has been marked as a duplicate of bug 421015 *** -- You are receiving this mail because: You are watching all bug changes.
