[krita] [Bug 471866] Krita crash with QT_QPA_PLATFORMTHEME=kde
https://bugs.kde.org/show_bug.cgi?id=471866 pdf changed: What|Removed |Added CC||k...@obfusc8.org --- Comment #2 from pdf --- FWIW, this happens on Fedora too, so is this a problem for all downstreams? And if it is, what path should they take to resolve it? It seems rather bizarre to me that a KDE-affiliated application crashes on start with `QT_QPA_PLATFORMTHEME=kde` to me, but maybe I don't understand the implications. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474929] Can't scroll through the Widgets Explorer with a touchscreen
https://bugs.kde.org/show_bug.cgi?id=474929 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474452] Widget Explorer opens centered on the screen when invoked for the first time after login
https://bugs.kde.org/show_bug.cgi?id=474452 David Edmundson changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/plasma-framework/-/c ||ommit/ece19f5c890ae9c02d3d9 ||2a8fc7ff1d74139f8f7 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from David Edmundson --- Git commit ece19f5c890ae9c02d3d92a8fc7ff1d74139f8f7 by David Edmundson. Committed on 30/09/2023 at 22:58. Pushed by fusionfuture into branch 'master'. Initalise PlasmaShellManager in it's ctor QtWaylandClinetExtensionTemplate can load everything on startup, it shares the registry with QGuiApplication. However because it calls a virtual function in initialize it can't be called from the base class constructor. It needs to be called in the leaf class, or explicitly after construction otherwise it falls back to the default implementation which is a metaobject invoke. A Dialog could be created before that triggers. M +1-0src/plasmaquick/waylandintegration.cpp https://invent.kde.org/frameworks/plasma-framework/-/commit/ece19f5c890ae9c02d3d92a8fc7ff1d74139f8f7 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474951] Allow the search bar to always remain visible.
https://bugs.kde.org/show_bug.cgi?id=474951
--- Comment #4 from `{third: "Beedell", first: "Roke"}`{.JSON5}
---
> But it is one click either way, right? Either you click on the search box or
> you click on the search button which focuses the search box? There is
> definitely a difference when it comes to the size of the click target though:
> If the search is already opened, the big search box is much easier to click
> than the search button. On the other hand you as a user can make the search
> button bigger by having its text always shown.
>
> Is this about the size of the click target? Or do you dislike how the view
> resizes itself to also fit the search box and you would rather have the user
> interface to move less? Something else?
Not that I'm aware of. I use Ctrl+F to invoke it (I wasn't actually aware that
a search button existed) so those considerations aren't important to me.
> I don't think this is a good comparison. As I said, this would be one click
> away either way. The only reason I wouldn't want the omnibox to hide is that
> it is also a location bar that shows essential information about where one
> is. This, however, isn't true for the search box after changing view location
> in Dolphin. We don't hide the location bar in Dolphin either for that reason.
That comparison isn't correct, because I somewhat misled you – I don't actually
use the omnibox for searching in Firefox. I use its dedicated search bar,
available via Customization. I mentioned the omnibox in case the respondent
wasn't aware that a separate search bar was available, or was more used to
Chrome.
I can't really see why this would be controversial – the ability to prevent the
search bar hiding could just be implemented as an option, right? I doubt that
I'm the only one with this issue, because the reason I reported this was that
my brother, a user of Windows 11, mentioned that I kept reopening the search
bar every time I searched, which he found absurd. Since then, I've been
noticing it, and it's bothered me.
--
You are receiving this mail because:
You are watching all bug changes.
[policykit-kde-agent-1] [Bug 475074] Allow PolicyKit to show the details pane expanded by default.
https://bugs.kde.org/show_bug.cgi?id=475074 third="Beedell", first="Roke", second="Julian Lockhart" changed: What|Removed |Added URL||https://discuss.kde.org/t/c ||an-i-have-the-policykit-det ||ails-pane-automatically-exp ||and/5620/2?u=rokejulianlock ||hart -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 475074] New: Allow PolicyKit to show the details pane expanded by default.
https://bugs.kde.org/show_bug.cgi?id=475074 Bug ID: 475074 Summary: Allow PolicyKit to show the details pane expanded by default. Classification: Plasma Product: policykit-kde-agent-1 Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rvdois+rvu...@rokejulianlockhart.anonaddy.com CC: d...@kde.org, jgrul...@redhat.com, jrez...@redhat.com Target Milestone: --- Created attachment 161984 --> https://bugs.kde.org/attachment.cgi?id=161984=edit Depiction of the dialog. SUMMARY Allow PolicyKit to show the details pane expanded by default, because the current implementation incentivises the user to ignore the prompt or enter their details without verifying what is invoking it. STEPS TO REPRODUCE 1. Invoke KDE Partition Manager OBSERVED RESULT The prompt appears, not providing any information about it. EXPECTED RESULT This might be preferable to some for whatever reason, but not for me, and certainly not for those to whom security is important. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230926 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.4-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION https://discuss.kde.org/t/can-i-have-the-policykit-details-pane-automatically-expand/5620/2?u=rokejulianlockhart -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 475073] New: Crash when selecting text within vi
https://bugs.kde.org/show_bug.cgi?id=475073 Bug ID: 475073 Summary: Crash when selecting text within vi Classification: Applications Product: konsole Version: 22.08.2 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: jcmun...@hotmail.com Target Milestone: --- Application: konsole (22.08.2) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 5.15.0-52-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.26 DrKonqi: 5.26.2 [KCrashBackend] -- Information about the crash: I tried to select text from a file open in vi pressing shift so the mouse events weren't passed to vi, and konsole crashed. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [KCrash Handler] #4 0x7f444e475070 in Konsole::Screen::setSelectionEnd(int, int, bool) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #5 0x7f444e4cf918 in Konsole::TerminalDisplay::extendSelection(QPoint const&) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #6 0x7f444e4d3232 in Konsole::TerminalDisplay::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #7 0x7f444dd2387e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f444dce0763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f444dce83a4 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f444d132fea in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f444dce6e87 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f444dd3d110 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f444dd403a5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f444dce0763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f444d132fea in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f444d5d5ae7 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f444d5a9acc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x7f444766dc4e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #19 0x7f444b1a5d1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f444b1fa6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f444b1a33c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f444d18c6f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f444d13190b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f444d139ea4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x5623307897ed in ?? () #26 0x7f444ca4cd90 in __libc_start_call_main (main=main@entry=0x562330787ce0, argc=argc@entry=1, argv=argv@entry=0x7fffaf9d1388) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f444ca4ce40 in __libc_start_main_impl (main=0x562330787ce0, argc=1, argv=0x7fffaf9d1388, init=, fini=, rtld_fini=, stack_end=0x7fffaf9d1378) at ../csu/libc-start.c:392 #28 0x56233078a055 in ?? () [Inferior 1 (process 2516) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460628] window rule to maximize windows doesn't take effect after recent updates (Wayland & X11) for gtk2/3 applications
https://bugs.kde.org/show_bug.cgi?id=460628 --- Comment #19 from Holger --- I'd like to maximize Firefox and remove the decorations. This is Kubuntu with the SNAP-Version of FF. My Window rules are: https://bugs.kde.org/attachment.cgi?id=159042 (bug 469908) a) The no decoration part of the rule works reliably. b) The maximization is not enforced (FF restoring session of 6 windows, 4 get maximized and two are random non-maximized) c) The according option in Alt+F3 Window-Menu is disabled. d) By super+right drag I can adjust the size (direct user interaction taking precedence appreciated). e) Also my FF-Windows are distributed to different virtual desktops. But some don't make it - usually the least recently opened window does not go to it's respective VD, but opens in the current VD instead (independent of which FF window / VD was use to exit FF). Versions: Firefox: 118.0 gtk-3-themes OS-ThemeNord-GTK / Adwaita Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-33-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4700MQ CPU @ 2.40GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: Micro-Star International Co., Ltd. Product Name: GE70 2OC\2OD\2OE System Version: REV:1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460064] Save grouping state (e.g. as "parent item") in the XMP sidecars to allow transfer between Digikam instances
https://bugs.kde.org/show_bug.cgi?id=460064 Maik Qualmann changed: What|Removed |Added CC||mr.dk...@gmail.com --- Comment #12 from Maik Qualmann --- *** Bug 474373 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 474373] Please consider adding "Group based on Meta/Tags" option.
https://bugs.kde.org/show_bug.cgi?id=474373 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 460064 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475072] New: Apps are displayed on the wrong screen
https://bugs.kde.org/show_bug.cgi?id=475072 Bug ID: 475072 Summary: Apps are displayed on the wrong screen Classification: Plasma Product: kwin Version: 5.27.8 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: gregmad...@yahoo.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Have a two screens setup (or more) 2. Have the primary screen on the right OBSERVED RESULT All the opened apps and games are launched and displayed on the most left screen even if it is not set as primary EXPECTED RESULT All the opened apps and games should be launched and displayed on the primary screen SOFTWARE/OS VERSIONS Linux: OpenSUSE Tumbleweed 20230927 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version : 6.5.4-1-default (64 bits) Graphical Platform : Wayland -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 475051] Remove release_announcements.po from l10n list
https://bugs.kde.org/show_bug.cgi?id=475051 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Why? It's the way to translate old announcements, no? You're free to decide not to translate them if you don't want to. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470915] Discover on Debian 12 does not show the top bar button window
https://bugs.kde.org/show_bug.cgi?id=470915 --- Comment #4 from Charlie Ramirez Animation Studios MX --- Created attachment 161983 --> https://bugs.kde.org/attachment.cgi?id=161983=edit Screenshot - Fixed Theme Change -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470915] Discover on Debian 12 does not show the top bar button window
https://bugs.kde.org/show_bug.cgi?id=470915 Charlie Ramirez Animation Studios MX changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Charlie Ramirez Animation Studios MX --- (In reply to Nate Graham from comment #1) > Well this is strange. > > Can you reproduce the issue if you use the default Breeze window decorations? > > Or after updating Debian with the latest updates? Fixed with Theme Exchange. -Apparently it can be caused by custom settings in the desktop appearance. (try using the Plastik Buttons in Dark Breeze with Adapta icons) Because it was a clean install of Debian 12 using the user's saved settings from Debian 11. The Adapta theme apparently is not installed completely (Reinstallation of Adapta was done in the global theme settings) This could have caused the problem However, during the Theme change, a slight crash of the application was generated - See [Bug 475070] I had to rebuild my custom Window Theme but there don't seem to be any more problems at the moment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475070] Soft Crash after Changing global Theme (due to graphical bug after updating debian 11 to 12)
https://bugs.kde.org/show_bug.cgi?id=475070 --- Comment #1 from Charlie Ramirez Animation Studios MX --- Created attachment 161982 --> https://bugs.kde.org/attachment.cgi?id=161982=edit Dr.KonkiBacktrace -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 475071] New: Konsole crashed when trying to open a new tab
https://bugs.kde.org/show_bug.cgi?id=475071 Bug ID: 475071 Summary: Konsole crashed when trying to open a new tab Classification: Applications Product: konsole Version: 23.04.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: dolev.ni...@gmail.com Target Milestone: --- Application: konsole (23.04.0) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.14-300.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (Thirty Eight) DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I had a konsole in which I ran "plasmashell --replace" in order to see why KDE crashes muliple times for me (including the crash handler), and after some time I tried to open a new tab using shortcuts, and Konsole crashed. The crash does not seem to be reproducible. -- Backtrace: Application: Konsole (konsole), signal: Bus error [KCrash Handler] #4 0x7f750957e444 in SharedMemory::findNamedEntry(QByteArray const&) const () from /lib64/libKF5CoreAddons.so.5 #5 0x7f7509584a02 in KSharedDataCache::find(QString const&, QByteArray*) const () from /lib64/libKF5CoreAddons.so.5 #6 0x7f7507cf5b74 in KIconLoader::loadScaledIcon(QString const&, KIconLoader::Group, double, QSize const&, int, QStringList const&, QString*, bool, std::optional const&) const () from /lib64/libKF5IconThemes.so.5 #7 0x7f7507cea66e in KIconEngine::createPixmap(QSize const&, double, QIcon::Mode, QIcon::State) () from /lib64/libKF5IconThemes.so.5 #8 0x7f7507ceac1c in KIconEngine::pixmap(QSize const&, QIcon::Mode, QIcon::State) () from /lib64/libKF5IconThemes.so.5 #9 0x7f7508fe49ed in QIcon::pixmap(QWindow*, QSize const&, QIcon::Mode, QIcon::State) const () from /lib64/libQt5Gui.so.5 #10 0x7f7508fe4b05 in QIcon::pixmap(QSize const&, QIcon::Mode, QIcon::State) const () from /lib64/libQt5Gui.so.5 #11 0x7f750a01d1dc in Konsole::TerminalDisplay::TerminalDisplay(QWidget*) () from /lib64/libkonsoleprivate.so.1 #12 0x7f7509fca64e in Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) () from /lib64/libkonsoleprivate.so.1 #13 0x7f7509fcb3de in Konsole::ViewManager::createView(Konsole::Session*) () from /lib64/libkonsoleprivate.so.1 #14 0x7f750a10ac1a in Konsole::MainWindow::createSession(QExplicitlySharedDataPointer, QString const&) () from /lib64/libkonsoleapp.so.1 #15 0x7f750a10b1d2 in Konsole::MainWindow::newTab() () from /lib64/libkonsoleapp.so.1 #16 0x7f7508ae8651 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #17 0x7f75097a7d24 in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5 #18 0x7f75097aab7b in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5 #19 0x7f75097ab79d in QAction::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f75097aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7f7508ab3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #22 0x7f7508f98d9e in QShortcutMap::dispatchEvent(QKeyEvent*) () from /lib64/libQt5Gui.so.5 #23 0x7f7508f99433 in QShortcutMap::tryShortcut(QKeyEvent*) () from /lib64/libQt5Gui.so.5 #24 0x7f7508f4df82 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /lib64/libQt5Gui.so.5 #25 0x7f7508f687b5 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /lib64/libQt5Gui.so.5 #26 0x7f7508f4aa0c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #27 0x7f75069d79e4 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #28 0x7f7506bc948c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #29 0x7f7506c27648 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #30 0x7f7506bc6b13 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #31 0x7f7508b06919 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #32 0x7f7508ab270b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #33 0x7f7508aba99b in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #34 0x556ab012e9c4 in main () [Inferior 1 (process 9870) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474476] [Crash] Random crash while drawing (QObject::killTimer: Timers cannot be stopped from another thread)
https://bugs.kde.org/show_bug.cgi?id=474476 --- Comment #16 from Protoniv --- (In reply to Dmitry Kazakov from comment #15) > Hi, Protoniv! > > I think I have fixed the bug (thank you very much for testing the custom > build, it helped a lot)! Please check the resulting build (whatever will be > build the first): > > https://invent.kde.org/graphics/krita/-/jobs/1221241 > > or > > https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/2002/ Hi, Dmitry! After following your reproduce step with RC1 and #2002 build, the crash seems no longer appears in newer builds. Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475070] New: Soft Crash after Changing global Theme (due to graphical bug after updating debian 11 to 12)
https://bugs.kde.org/show_bug.cgi?id=475070 Bug ID: 475070 Summary: Soft Crash after Changing global Theme (due to graphical bug after updating debian 11 to 12) Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com Target Milestone: --- Application: systemsettings (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-12-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: The error was triggered after trying to fix Switch to the classic Breeze theme due to Discover not correctly displaying the window button bar (close, maximize, etc.) after doing a clean install of Debian 12 using previous user settings made in Debian 11. [Discover] [Bug 470915] System Settings has closed unexpectedly, however the theme change was performed correctly. -During the attempt to Change Dark Breze to Light and come back to dark The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Preferencias del sistema (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7ff02426b96c in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7ff02426b869 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7ff02426b869 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff02426b869 in QQuickWindowPrivate::sendFilteredPointerEventImpl(QQuickPointerEvent*, QQuickItem*, QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7ff02426c674 in QQuickWindowPrivate::deliverToPassiveGrabbers(QVector > const&, QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7ff024272a4f in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7ff0242740dd in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7ff0265493f5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7ff026d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7ff0260b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7ff024d7e057 in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #15 0x7ff026da4db8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7ff026d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7ff026d6b552 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7ff0260b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7ff026d6965e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7ff026dbdbd8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7ff026dc0f60 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7ff026d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7ff0260b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7ff02653d3ed in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7ff026511cac in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #26 0x7ff023f664b0 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #27 0x7ff02471e7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7ff02471ea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7ff02471eacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7ff026109836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7ff0260b017b in QEventLoop::exec(QFlags) () from
[kde] [Bug 475069] New: Kalendar crashes
https://bugs.kde.org/show_bug.cgi?id=475069 Bug ID: 475069 Summary: Kalendar crashes Classification: I don't know Product: kde Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: michaeldrummon...@gmail.com Target Milestone: --- Application: kalendar (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-33-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Kalendar crashes every time on Kubuntu. Not sure if this matters, but I have the Krohnkite K-Win script installed. I also reinstalled my system recently and kept my Home partition in tact. The crash can be reproduced every time. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x7f88d1b68c04 in KCalendarCore::Calendar::isLoading() const () from /lib/x86_64-linux-gnu/libKF5CalendarCore.so.5abi2 #5 0x561046de8875 in ?? () #6 0x7f88cf8f39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f88cf8f798e in QTimer::timeout(QTimer::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f88cf8e7bf5 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f88d056bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f88cf8bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f88cf914201 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f88cf914b34 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f88cd71549d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f88cd770178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f88cd7141b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f88cf914e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f88cf8b97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f88cf8c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x561046da5e5a in ?? () #20 0x7f88cee23a90 in __libc_start_call_main (main=main@entry=0x561046da3d30, argc=argc@entry=1, argv=argv@entry=0x7ffe6b316d48) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7f88cee23b49 in __libc_start_main_impl (main=0x561046da3d30, argc=1, argv=0x7ffe6b316d48, init=, fini=, rtld_fini=, stack_end=0x7ffe6b316d38) at ../csu/libc-start.c:360 #22 0x561046da6e55 in ?? () [Inferior 1 (process 32468) detached] Reported using DrKonqi This report was filed against 'kde' because the product 'kalendar' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 475055] Kid3 can't find file tag
https://bugs.kde.org/show_bug.cgi?id=475055 --- Comment #2 from Mark Fraser --- (In reply to Urs Fleisch from comment #1) > Without an example file, it is a bit hard to reproduce. Could you answer the > following questions: > > - M4A files can be parsed by both TagLib and mp4v2, what metadata plugins > are enabled in your settings? Does it happen with both? Note that you have > to restart Kid3 after changing plugin settings. If the "Mp4v2Metadata" > plugin is not listed, it is because libmp4v2 is not provided by your distro > and you could try the binary kid3-3.9.4-Linux.tgz from > https://kid3.kde.org/#download. I am using TagLib and Mp4v2Metadata isn't available, but I am using kid3 from the PPA. > - Could it be that this is the same situation as in > https://invent.kde.org/multimedia/kid3/-/issues/566? Could you compare the > output of `file` with those in that report? It could be as I've been using SoundKreator to rip the CDs, but in this case I found a copy of the file on another drive and that's fine. I do have some other files that are unreadable, but the smallest is 4.2M. -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 475060] Someone has hacked my phone, I believe it's and ex-girlfriend. But since I ALONE bought paid and own it. I want to know how to get A WHOLE LOT of these apps off my phone!
https://bugs.kde.org/show_bug.cgi?id=475060 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Component|general |Spam Product|buildsystem |Spam Assignee|neund...@kde.org|n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475068] New: Kicker menu gets behind autohide panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=475068 Bug ID: 475068 Summary: Kicker menu gets behind autohide panel on Wayland Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: alexandre.catt...@gmail.com Target Milestone: 1.0 Created attachment 161981 --> https://bugs.kde.org/attachment.cgi?id=161981=edit Illustration of the issue On Plasma Wayland session, with panel set to "Auto Hide", Application Menu (Kicker) menus get behind the panel instead of covering it (as they correctly do on X11). STEPS TO REPRODUCE 1. Start a Plasma Wayland session 2. Add Application Menu to panel 3. Set panel to "Auto Hide" OBSERVED RESULT Menus go behind panel (see attachment) EXPECTED RESULT Menus should cover the panel SOFTWARE/OS VERSIONS KDE Plasma from Arch Linux: KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475067] New: plymouth-kcm
https://bugs.kde.org/show_bug.cgi?id=475067 Bug ID: 475067 Summary: plymouth-kcm Classification: Applications Product: systemsettings Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rustmil...@proton.me Target Milestone: --- Application: systemsettings (5.27.8) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.5-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: plymouth-kcm caused crash apon saving changes of boot splash screen... The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7fb84f0d039b in () at /usr/lib/libQt5Core.so.5 #5 0x7fb82a1f2c06 in () at /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_plymouth.so #6 0x7fb84fab1d06 in () at /usr/lib/libKF5KCMUtils.so.5 #7 0x7fb84fab9da8 in KCModuleProxy::save() () at /usr/lib/libKF5KCMUtils.so.5 #8 0x7fb850970ab6 in ModuleView::moduleSave(KCModuleProxy*) () at /usr/lib/libsystemsettingsview.so.3 #9 0x7fb8509756af in () at /usr/lib/libsystemsettingsview.so.3 #10 0x7fb84f0d0cf3 in () at /usr/lib/libQt5Core.so.5 #11 0x7fb8502e1527 in KAuth::ObjectDecorator::authorized(KAuth::Action const&) () at /usr/lib/libKF5Auth.so.5 #12 0x7fb84f0d0b37 in () at /usr/lib/libQt5Core.so.5 #13 0x7fb84fe5c3a7 in QAbstractButton::clicked(bool) () at /usr/lib/libQt5Widgets.so.5 #14 0x7fb84fe5ec5a in () at /usr/lib/libQt5Widgets.so.5 #15 0x7fb84fe6015c in () at /usr/lib/libQt5Widgets.so.5 #16 0x7fb84fe60300 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #17 0x7fb84fdaf1e1 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7fb84fd7893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7fb84fd7ddef in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7fb84f09bbf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7fb84fd7c12a in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #22 0x7fb84fdcced5 in () at /usr/lib/libQt5Widgets.so.5 #23 0x7fb84fdcec27 in () at /usr/lib/libQt5Widgets.so.5 #24 0x7fb84fd7893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7fb84f09bbf8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7fb84f54193c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #27 0x7fb84f52a6c5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #28 0x7fb84cf5ec75 in () at /usr/lib/libQt5WaylandClient.so.5 #29 0x7fb84d70df19 in () at /usr/lib/libglib-2.0.so.0 #30 0x7fb84d76c2b7 in () at /usr/lib/libglib-2.0.so.0 #31 0x7fb84d70c112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #32 0x7fb84f0eaa1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x7fb84f09a904 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #34 0x7fb84f09bda3 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #35 0x55756ab92bd9 in () #36 0x7fb84e845cd0 in () at /usr/lib/libc.so.6 #37 0x7fb84e845d8a in __libc_start_main () at /usr/lib/libc.so.6 #38 0x55756ab93575 in () [Inferior 1 (process 56055) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474452] Widget Explorer opens centered on the screen when invoked for the first time after login
https://bugs.kde.org/show_bug.cgi?id=474452 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/897 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475066] New: No longer possible to choose default action for Logout Screen
https://bugs.kde.org/show_bug.cgi?id=475066 Bug ID: 475066 Summary: No longer possible to choose default action for Logout Screen Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: alexandre.catt...@gmail.com Target Milestone: 1.0 In System Settings' Desktop Session module, it is no longer possible (don't know from which Plasma version exactly) to choose the default action (log out, shut down, restart ...) for Logout Screen. Has the setting been moved? SOFTWARE/OS VERSIONS KDE Plasma from Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464196] Drag and drop in GTK apps: 'drag-motion' is triggered when GTK window regains focus
https://bugs.kde.org/show_bug.cgi?id=464196 Dragoon Aethis changed: What|Removed |Added CC||k...@dragonic.eu --- Comment #8 from Dragoon Aethis --- One more +1, with more notes in this Gtk bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/5519 - I can reproduce this behavior with Zoltan's code too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475064] Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch?
https://bugs.kde.org/show_bug.cgi?id=475064 --- Comment #3 from Wesley M --- Created attachment 161980 --> https://bugs.kde.org/attachment.cgi?id=161980=edit Display Update Fix This shows where I updated the display, which fixed the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475064] Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch?
https://bugs.kde.org/show_bug.cgi?id=475064 --- Comment #2 from Wesley M --- Created attachment 161979 --> https://bugs.kde.org/attachment.cgi?id=161979=edit Wallpaper Change Test This shows a test where I changed the wallpaper. This did not affect the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475064] Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch?
https://bugs.kde.org/show_bug.cgi?id=475064 --- Comment #1 from Wesley M --- Created attachment 161978 --> https://bugs.kde.org/attachment.cgi?id=161978=edit Video Example This shows the bug after it spontaneously occurred. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462935] Touch Screen gestures should be customizable
https://bugs.kde.org/show_bug.cgi?id=462935 Maximilian Böhm changed: What|Removed |Added CC||m...@elbmurf.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402857] Touchpad gestures should be configurable
https://bugs.kde.org/show_bug.cgi?id=402857 Maximilian Böhm changed: What|Removed |Added CC||m...@elbmurf.de -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 475065] New: spectacle window misaligned in multi-monitor set up
https://bugs.kde.org/show_bug.cgi?id=475065 Bug ID: 475065 Summary: spectacle window misaligned in multi-monitor set up Classification: Applications Product: Spectacle Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: fanzhuyi...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 161977 --> https://bugs.kde.org/attachment.cgi?id=161977=edit Image showing spectacle misalignment SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Setup a dual-monitor system with the external screen on the left and the laptop screen on the right. 2. In KDE plasma, set global scale to 125% 3. Launch spectacle with rectangular region with `spectacle -r -b` OBSERVED RESULT The spectacle window on the laptop screen shows misaligned screen contents (see picture) EXPECTED RESULT The spectacle window on the laptop screen should display correctly aligned screen contents. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION The issue disappears when I run with ``` QT_SCREEN_SCALE_FACTORS=1 spectacle -r -b ``` The default value of QT_SCREEN_SCALE_FACTORS is ``` eDP-1=1.25;DP-1=1.25;DP-2=1.25;DP-1-0=1.25;DP-1-1=1.25;HDMI-1-0=1.25;DP-1-2=1.25 ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475064] New: Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch?
https://bugs.kde.org/show_bug.cgi?id=475064 Bug ID: 475064 Summary: Compositing or Virtual Screenspace Issue - Maybe wallpaper and display resolution mismatch? Classification: Plasma Product: kwin Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: wmprivacyem...@gmail.com Target Milestone: --- SUMMARY *** Wallpaper will sometimes resize on its own to a resolution smaller than the display is running, causing strange graphical glitches until the display is updated (move or resized) in the settings. *** STEPS TO REPRODUCE 1. Unknown. Happens without warning. OBSERVED RESULT It...happens? EXPECTED RESULT It shouldn't. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Fedora 38 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 474373] Please consider adding "Group based on Meta/Tags" option.
https://bugs.kde.org/show_bug.cgi?id=474373 Mr.D changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470023] QT_SCREEN_SCALE_FACTORS causes spectacle to mess up rendering the captured buffers for the selection tool.
https://bugs.kde.org/show_bug.cgi?id=470023 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 462200] plasma-systemmonitor french translation could be improved
https://bugs.kde.org/show_bug.cgi?id=462200 grouchomarx...@gmail.com changed: What|Removed |Added CC||grouchomarx...@gmail.com --- Comment #2 from grouchomarx...@gmail.com --- Hello, I have searched the translation files for the "Transfert" line. Here are the corresponding lines, and my suggestions (I have used "Envoi" and would also suggest "Réception", because "Téléversement" and "Téléchargement" are a bit long compared to "Upload" and "Download", and it seems that shorter texts are important in this app). For "Transfert": *** in ksystemstats/ksystemstats_plugins.po msgctxt "@title" msgid "Upload Rate" msgstr "Taux de transfert" - Should be "Taux d'envoi" msgctxt "@title Short for Upload Rate" msgid "Upload" msgstr "Transfert" - Should be "Envoi" msgctxt "@title" msgid "Total Uploaded" msgstr "Total transféré" - Should be "Total envoyé" msgctxt "@title Short for Total Uploaded" msgid "Uploaded" msgstr "Transféré" - Should be "Envoyé" For "Téléchargement": *** in ksystemstats/ksystemstats_plugins.po msgctxt "@title" msgid "Download Rate" msgstr "Taux de téléchargement" - Should be "Taux de réception" msgctxt "@title Short for Download Rate" msgid "Download" msgstr "Téléchargement" - Should be "Réception" msgctxt "@title" msgid "Total Downloaded" msgstr "Total téléchargé" - Should be "Total reçu" msgctxt "@title Short for Total Downloaded" msgid "Downloaded" msgstr "Téléchargé" - Should be "Reçu" *** in libksysguard/processcore.po msgctxt "@title" msgid "Download Speed" msgstr "Vitesse de téléchargement" - Should be "Vitesse de réception" msgctxt "@title" msgid "Download" msgstr "Téléchargement" - Should be "Réception" Hope this helps. Best regards -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 459912] Del-Key action is buggy in BLOCK mode
https://bugs.kde.org/show_bug.cgi?id=459912 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/-/commit ||/f275643b60ce612e4b7c30ec0b ||750dac724fbc84 Status|ASSIGNED|RESOLVED --- Comment #2 from Christoph Cullmann --- Git commit f275643b60ce612e4b7c30ec0b750dac724fbc84 by Christoph Cullmann, on behalf of Jonathan Poelen. Committed on 30/09/2023 at 20:51. Pushed by cullmann into branch 'master'. Fix key delete in block selection when range contains no characters M +33 -0autotests/src/kateview_test.cpp M +1-0autotests/src/kateview_test.h M +11 -0src/view/kateview.cpp https://invent.kde.org/frameworks/ktexteditor/-/commit/f275643b60ce612e4b7c30ec0b750dac724fbc84 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475063] New: Wishlist - Custom Tiling - Snap back to tiled position after unmaximizing.
https://bugs.kde.org/show_bug.cgi?id=475063 Bug ID: 475063 Summary: Wishlist - Custom Tiling - Snap back to tiled position after unmaximizing. Classification: Plasma Product: kwin Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: wmprivacyem...@gmail.com CC: notm...@gmail.com Target Milestone: --- SUMMARY *** Wishlist - Custom Tiling - Snap back to tiled position after unmaximizing. *** STEPS TO REPRODUCE 1. Tile a window to a defined space by holding shift while dragging the window. 2. Maximize the window. 3. Unmaximize the window. OBSERVED RESULT The window reverts to a floating state. EXPECTED RESULT Unless it is dragged/etc., the window should snap back to its tiled position after being unmaximized. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Fedora 38 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Plasma Application Launcher from opening with focus stealing prevention set to High or Extreme
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #60 from r...@alum.mit.edu --- FSP High works just fine for me either with the super key or with the KDE button. It may or may not be relevant that I use focus follows mouse (mouse precedence). The documentation for High FSP does state "This setting is probably not really usable when not using mouse focus policy". I'd really like Extreme to work correctly; I absolutely do not want windows popping up and grabbing focus (think about what happens if I'm in the middle of entering a password -- this does happen even in High FSP when I'm entering the kwallet password and something pops up and grabs focus away). What doesn't make sense is for individual users to be responsible for writing rules that are necessary for KDE components to function correctly; that's something that I think KDE should provide itself. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 475055] Kid3 can't find file tag
https://bugs.kde.org/show_bug.cgi?id=475055 --- Comment #1 from Urs Fleisch --- Without an example file, it is a bit hard to reproduce. Could you answer the following questions: - M4A files can be parsed by both TagLib and mp4v2, what metadata plugins are enabled in your settings? Does it happen with both? Note that you have to restart Kid3 after changing plugin settings. If the "Mp4v2Metadata" plugin is not listed, it is because libmp4v2 is not provided by your distro and you could try the binary kid3-3.9.4-Linux.tgz from https://kid3.kde.org/#download. - Could it be that this is the same situation as in https://invent.kde.org/multimedia/kid3/-/issues/566? Could you compare the output of `file` with those in that report? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475008] KF6TextEditTextToSpeechConfig.cmake is not provided by any package
https://bugs.kde.org/show_bug.cgi?id=475008 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Jarvie --- It turns out that the missing file is in the package kf6-ktextaddons-dev. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475062] New: Maximized flag not updated when window is dragged.
https://bugs.kde.org/show_bug.cgi?id=475062 Bug ID: 475062 Summary: Maximized flag not updated when window is dragged. Classification: Plasma Product: kwin Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: wmprivacyem...@gmail.com Target Milestone: --- Created attachment 161976 --> https://bugs.kde.org/attachment.cgi?id=161976=edit Video Example SUMMARY *** Maximized flag not updated when window is dragged. *** STEPS TO REPRODUCE 1. Maximize any window. 2. Using the titlebar or the super key, drag the window. OBSERVED RESULT The window keeps its size, shape, and maximized status, but moves with the drag operation. EXPECTED RESULT The window should no longer be maximized. It should revert to it's floating size and shape, but still change position to match the dragging operation. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Fedora 38 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474703] Too many files on Desktop, cannot sort files anymore
https://bugs.kde.org/show_bug.cgi?id=474703 --- Comment #5 from Nate Graham --- You're very welcome! To clarify though, the actual work was all done by Harald and Marco. At most, all I did was some bug triage and merge request review. :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475061] New: System Settings ignoring failsafe timeout if window is closed before time expires.
https://bugs.kde.org/show_bug.cgi?id=475061 Bug ID: 475061 Summary: System Settings ignoring failsafe timeout if window is closed before time expires. Classification: Applications Product: systemsettings Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: wmprivacyem...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 161975 --> https://bugs.kde.org/attachment.cgi?id=161975=edit Video Example SUMMARY *** System Settings ignoring failsafe timeout if window is closed before time expires. *** STEPS TO REPRODUCE 1. Open display settings. 2. Adjust a setting that uses a timeout failsafe to revert changes if the applied changes break the system and the user is unable to interact with settings window within the timeout period. 3. Close the display settings window before the timeout period expires. OBSERVED RESULT When the window is closed, the changes appear to be permanently saved. EXPECTED RESULT The changes should be reverted, as the user did not approve the applied changes during the failsafe timeout period. If the window is accidentally closed, crashes, the desktop environment restarts, or the system is shut down; then it should revert to the last known-good settings, instead of potentially trapping the user in a misconfigured or unusable system. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Fedora 38 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Note that the video example shows a different issue with OBS recording the cursor position incorrectly after the resolution change. It is unrelated to this bug report. However, it can be used to show the resolution was changed and did not revert after the window closed. -- You are receiving this mail because: You are watching all bug changes.
[buildsystem] [Bug 475060] Someone has hacked my phone, I believe it's and ex-girlfriend. But since I ALONE bought paid and own it. I want to know how to get A WHOLE LOT of these apps off my phone!
https://bugs.kde.org/show_bug.cgi?id=475060 Raphael Kubo da Costa changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||rak...@freebsd.org -- You are receiving this mail because: You are watching all bug changes.
[buildsystem] [Bug 475060] New: Someone has hacked my phone, I believe it's and ex-girlfriend. But since I ALONE bought paid and own it. I want to know how to get A WHOLE LOT of these apps off my phon
https://bugs.kde.org/show_bug.cgi?id=475060 Bug ID: 475060 Summary: Someone has hacked my phone, I believe it's and ex-girlfriend. But since I ALONE bought paid and own it. I want to know how to get A WHOLE LOT of these apps off my phone! Classification: Developer tools Product: buildsystem Version: unspecified Platform: Android OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neund...@kde.org Reporter: itsmefruge...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Someone has hacked my phone, I believe it's and ex-girlfriend. But since I ALONE bought paid and own it. I want to know how to get A WHOLE LOT of these apps off my phone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466380] kwin_x11 crashes in KWin::X11Window::finishCompositing() when disabling compositing
https://bugs.kde.org/show_bug.cgi?id=466380 --- Comment #17 from Holger --- (In reply to Holger from comment #14) > Still, Firefox does not enforce the maximized window status. Was already reported as bug 460628 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 422628] Shortcut is not working in different layout
https://bugs.kde.org/show_bug.cgi?id=422628 Christoph Cullmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||cullm...@kde.org Resolution|--- |NOT A BUG --- Comment #2 from Christoph Cullmann --- I don't think we can limit the default shortcuts to letters/symbols that are accessible on all keyboards. You can reconfigure these shortcuts if it doesn't fit your keyboard. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 431693] Foldable sections in markdown files
https://bugs.kde.org/show_bug.cgi?id=431693 Christoph Cullmann changed: What|Removed |Added Component|syntax |syntax Version|20.12.1 |unspecified CC||cullm...@kde.org, ||walter.von.entferndt@posteo ||.net Product|kate|frameworks-syntax-highlight ||ing -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 396623] Script categorization could use improvement
https://bugs.kde.org/show_bug.cgi?id=396623 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||cullm...@kde.org --- Comment #8 from Christoph Cullmann --- I don't think just moving this into one level is useful, then you have all Emmet stuff that is not always useful mixed up with others. We provide a hud now with ctrl-alt-i that let's you explore all actions list like. I don't see an urgent need to alter that menu layout. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 475059] New: Screenshot of Present Windows or Present Virtual desktops
https://bugs.kde.org/show_bug.cgi?id=475059 Bug ID: 475059 Summary: Screenshot of Present Windows or Present Virtual desktops Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: al.neo...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Since Plasma 5.26 it's not possible to take desktop-wide screenshot of Present Windows or Present Virtual desktops. Can't capture them either with SHIFT+PRINT SCREEN or by using delay timeout. STEPS TO REPRODUCE 1. Run Present Windows 2. Hit OBSERVED RESULT Spectacle fails to capture screen. EXPECTED RESULT Captures screen successfully. 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.
[kate] [Bug 450729] Neither KWrite or Kate allow margins for printing.
https://bugs.kde.org/show_bug.cgi?id=450729 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Christoph Cullmann --- For me the Qt page layout dialog we use for printing allows to configure margins. 'properties' button in the print dialog. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 450724] Add .md.html as a Markdown extension
https://bugs.kde.org/show_bug.cgi?id=450724 Christoph Cullmann changed: What|Removed |Added Component|general |syntax CC||cullm...@kde.org, ||walter.von.entferndt@posteo ||.net Product|kate|frameworks-syntax-highlight ||ing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Plasma Application Launcher from opening with focus stealing prevention set to High or Extreme
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #59 from Sami Saarinen --- @Nate Martin Flöser offered three possible solutions in his comment 26 . None of these have been implemented at September 2023. Please select one of his options - as the current situation for everyday user is harmful. "I can offer some solutions: 1) remove focus stealing prevention HIGH and EXTREME. Reasoning: we are not able to make it work in a Plasma session and don't have the expertise to maintain it 2) We remove the GUI setting and make it an advanced option 3) We show a warning that this breaks Plasma panels if selected If I would have to pick one I would go for 3 as we do that in other places as well. For example if you want to use "Focus Under Mouse" it says that Alt+Tab cannot work. Or the Compositor settings show a warning when selecting any of the "dangerous" settings." -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 474877] The home page is empty and all the reports with texts are empty (graphs visible).
https://bugs.kde.org/show_bug.cgi?id=474877 --- Comment #2 from fam.hoogerw...@sunrise.ch --- The difference with the other bug report is that no text can be selected. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447225] Cursor "jumps" one character to the right when inputting dead keys ' and " in US alt. intl. keyboard layout
https://bugs.kde.org/show_bug.cgi?id=447225 Christoph Cullmann changed: What|Removed |Added Version Fixed In||23.08 CC||cullm...@kde.org Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Christoph Cullmann --- Works for me as intended with 23.08. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 453423] Numpad shortcuts don't work in wayland sessions.
https://bugs.kde.org/show_bug.cgi?id=453423 rkeating changed: What|Removed |Added CC||rqkeat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447737] Xmllint fails to format files with filename containing space
https://bugs.kde.org/show_bug.cgi?id=447737 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/util ||ities/kate/-/commit/bd4b230 ||a914238c12852471e56e2e796ac ||241b0d --- Comment #2 from Christoph Cullmann --- Git commit bd4b230a914238c12852471e56e2e796ac241b0d by Christoph Cullmann. Committed on 30/09/2023 at 19:29. Pushed by cullmann into branch 'master'. workaround for names with spaces M +1-1addons/externaltools/externaltools-config/xml_format_full_file https://invent.kde.org/utilities/kate/-/commit/bd4b230a914238c12852471e56e2e796ac241b0d -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443242] Add support for Unicode character composition to Kate and KWrite
https://bugs.kde.org/show_bug.cgi?id=443242 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Christoph Cullmann --- I think this is something an input method should take care of. See e.g. https://wiki.archlinux.org/title/IBuse That will work for all GTK and Qt things at least and provides what you ask for. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 442798] Kate recreates a file when saving it on sshfs, which removes hardlinks
https://bugs.kde.org/show_bug.cgi?id=442798 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Christoph Cullmann --- I am sorry that this doesn't fit your use case, but I don't see that we alter this. We do like vim an atomic rename to avoid that we might loose data. This is for me more important than this scenario. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 465509] Wish status bar color change with vi input mode
https://bugs.kde.org/show_bug.cgi?id=465509 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Christoph Cullmann --- I am not sure that is a good thing, we now integrated the view status bar into the one of the window, I don't think recoloring that full area that includes the tool views will work well or look good with the styles we use. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 470293] Kate clears sessions upon close
https://bugs.kde.org/show_bug.cgi?id=470293 Christoph Cullmann changed: What|Removed |Added CC||fe...@whiteley.ie --- Comment #9 from Christoph Cullmann --- *** Bug 467877 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467877] On close of application sometimes Kate wipes the katesession file it was working on
https://bugs.kde.org/show_bug.cgi?id=467877 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||cullm...@kde.org --- Comment #4 from Christoph Cullmann --- *** This bug has been marked as a duplicate of bug 470293 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 459912] Del-Key action is buggy in BLOCK mode
https://bugs.kde.org/show_bug.cgi?id=459912 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/frameworks/ktexteditor/-/merge_requests/607 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475058] When opening a folder containing Chinese characters in Dolphin, garbled code may appear in the location bar
https://bugs.kde.org/show_bug.cgi?id=475058 ycj...@163.com changed: What|Removed |Added CC||ycj...@163.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475058] New: When opening a folder containing Chinese characters in Dolphin, garbled code may appear in the location bar
https://bugs.kde.org/show_bug.cgi?id=475058
Bug ID: 475058
Summary: When opening a folder containing Chinese characters in
Dolphin, garbled code may appear in the location bar
Classification: Applications
Product: dolphin
Version: 23.08.1
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: bars: location
Assignee: dolphin-bugs-n...@kde.org
Reporter: ycj...@163.com
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. open the dolphin file manager
2. click folder like this:
/run/media/imic/backup/新建文件夹/新建文件夹/新建文件夹/海说明/vpn申请等/2022-abcd_中国
3. you may get a error
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro 23.0.2 Uranos
(available in About System)
KDE Plasma Version: KDE 5.110.0 / Plasma 5.27.8
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
██ imic@imic-21fca000cd
██ OS: Manjaro 23.0.2 Uranos
██ Kernel: x86_64 Linux 6.5.3-1-MANJARO
██ Uptime: 16m
Packages: 1251
Shell: bash
Resolution: 1920x1200
DE: KDE 5.110.0 / Plasma 5.27.8
WM: KWin
GTK Theme: Breeze [GTK2/3]
Icon Theme: WhiteSur
Disk: 206G / 820G (26%)
CPU: 13th Gen Intel Core i7-13700H @ 20x
4.8GHz [38.0°C]
GPU: NVIDIA RTX A500 Laptop GPU
RAM: 3353MiB / 31770MiB
--
You are receiving this mail because:
You are watching all bug changes.
[Tokodon] [Bug 475057] New: Tokodon crashes when accepting follow requests
https://bugs.kde.org/show_bug.cgi?id=475057
Bug ID: 475057
Summary: Tokodon crashes when accepting follow requests
Classification: Applications
Product: Tokodon
Version: 23.08.1
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: ngomp...@gmail.com
CC: c...@carlschwan.eu, j...@redstrate.com
Target Milestone: ---
Application: tokodon (23.08.1)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.5.5-301.fc39.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 39 (KDE Plasma Prerelease)
DrKonqi: 5.27.8 [KCrashBackend]
-- Information about the crash:
When I attempt to accept a follow request, the application immediately crashes.
The follow request acceptance seems to go through, regardless.
The crash can be reproduced every time.
-- Backtrace:
Application: Tokodon (tokodon), signal: Segmentation fault
[KCrash Handler]
#4 0x55fa824b3d45 in QString::QString (other=..., this=,
this=, other=...) at /usr/include/qt5/QtCore/qstring.h:1093
#5 Post::content (this=0x0) at
/usr/src/debug/tokodon-23.08.1-1.fc39.x86_64/src/timeline/post.cpp:436
#6 NotificationHandler::handle (this=0x55fa831b1fa0,
notification=std::shared_ptr (use count 4, weak count 0) = {...},
account=0x55fa831ebd40) at
/usr/src/debug/tokodon-23.08.1-1.fc39.x86_64/src/account/notificationhandler.cpp:46
#7 0x55fa824a5f4c in operator() (__closure=,
notification=...) at
/usr/src/debug/tokodon-23.08.1-1.fc39.x86_64/src/account/account.cpp:43
#8 QtPrivate::FunctorCall,
QtPrivate::List >, void, Account::Account(const
AccountConfig&, QNetworkAccessManager*,
QObject*)::)> >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#9 QtPrivate::Functor)>,
1>::call >, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#10 QtPrivate::QFunctorSlotObject)>, 1,
QtPrivate::List >, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=,
ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#11 0x7f97cdae84f1 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#12 0x55fa824e7eec in AbstractAccount::notification
(_t1=std::shared_ptr (use count 4, weak count 0) = {...},
this=0x55fa831ebd40) at
/usr/src/debug/tokodon-23.08.1-1.fc39.x86_64/redhat-linux-build/src/tokodon_static_autogen/GJU2H5Y2LV/moc_abstractaccount.cpp:596
#13 AbstractAccount::handleNotification (doc=..., this=0x55fa831ebd40) at
/usr/src/debug/tokodon-23.08.1-1.fc39.x86_64/src/account/abstractaccount.cpp:442
#14 Account::streamingSocket(QString const&)::{lambda(QString
const&)#1}::operator()(QString const&) const [clone .isra.0]
(__closure=0x55fa839f5db0, message=...) at
/usr/src/debug/tokodon-23.08.1-1.fc39.x86_64/src/account/account.cpp:240
#15 0x7f97cdae84f1 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#16 0x7f97d0344d1c in QWebSocket::textMessageReceived(QString const&) ()
from /lib64/libQt5WebSockets.so.5
#17 0x7f97cdae84f1 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#18 0x7f97d03483b5 in QWebSocketDataProcessor::process(QIODevice*) () from
/lib64/libQt5WebSockets.so.5
#19 0x7f97d033d917 in QWebSocketPrivate::processData() () from
/lib64/libQt5WebSockets.so.5
#20 0x7f97cdaded9b in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#21 0x7f97ce7aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#22 0x7f97cdab4218 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#23 0x7f97cdab76c5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#24 0x7f97cdb06c6f in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#25 0x7f97ccfe9dfc in g_main_context_dispatch_unlocked.lto_priv () from
/lib64/libglib-2.0.so.0
#26 0x7f97cd044d58 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#27 0x7f97ccfe7a73 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#28 0x7f97cdb06759 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#29 0x7f97cdab2bdb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#30 0x7f97cdabae6b in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#31 0x55fa8247ee76 in main (argc=, argv=) at
/usr/src/debug/tokodon-23.08.1-1.fc39.x86_64/src/main.cpp:259
[Inferior 1 (process 212543) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Plasma Application Launcher from opening with focus stealing prevention set to High or Extreme
https://bugs.kde.org/show_bug.cgi?id=377914 --- Comment #58 from Sami Saarinen --- (In reply to Sami Saarinen from comment #57) > I can confirm that this bug still exists at 30th of September 2023. > > The Launcher does not open even with Meta/Super/Windows - key - if ANY of > applications is opened. > > The only situation when App Launcher opens is when all of the applications > are closed/ minimized to panel. > > I think this is a really harming bug. For example I re-insalled the whole OS > and WHEN EVEN that did not help I accidentally found this bug report. > Something like This should not be happening. > > I recommend removing the options for Focus Stealing Prevention set to High > or Extreme in System Settings. > As it's obvious with this bug - they are un-usable anyway. > > Kubuntu 23.04 > Plasma 5.27.4 > Frameworks 5.104.0 > Qt 5.15.8 > X11 Window System After reading Martin Flöser's comment I understand his point of view. This feature may be needed in special environments - like factory automation control - but for a basic home user this feature is potentially "dangerous" - as it is in the middle of non-critical settings. I suggest High and Extreme Focus Stealing Prevention should be separated from other focus stealing options - and clearly marked as "For Advanced Users Only - Be aware what you are doing before selecting these options ". -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 474151] KPhotoAlbum crashes when Annotations are not saved and then user right-clicks Show Info in Viewer
https://bugs.kde.org/show_bug.cgi?id=474151
Victor Lobo changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED|REOPENED
--- Comment #6 from Victor Lobo ---
Reopening this bug since the same crash still occurs in the following scenario
in git master.
STEPS TO REPRODUCE
1. Open KPhotoAlbum
2. Go to Thumbnail View
3. Go to Annotations window for any image or video (CTRL + 1)
4. Add a positionable tag in the Annotation Window
5. Click DONE in Annotations window
6. Open any image or video in Viewer (press Enter)
7. Go to Info in the right-click context menu in Viewer. ("Discard Changes?"
popup dialog is displayed)
8. Click Discard or Cancel in "Discard Changes?" popup dialog
9. Crash
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 377914] KWin prevents Plasma Application Launcher from opening with focus stealing prevention set to High or Extreme
https://bugs.kde.org/show_bug.cgi?id=377914 Sami Saarinen changed: What|Removed |Added CC||samijm...@gmail.com --- Comment #57 from Sami Saarinen --- I can confirm that this bug still exists at 30th of September 2023. The Launcher does not open even with Meta/Super/Windows - key - if ANY of applications is opened. The only situation when App Launcher opens is when all of the applications are closed/ minimized to panel. I think this is a really harming bug. For example I re-insalled the whole OS and WHEN EVEN that did not help I accidentally found this bug report. Something like This should not be happening. I recommend removing the options for Focus Stealing Prevention set to High or Extreme in System Settings. As it's obvious with this bug - they are un-usable anyway. Kubuntu 23.04 Plasma 5.27.4 Frameworks 5.104.0 Qt 5.15.8 X11 Window System -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475053] blurred elements look buggy when zoom effect is used
https://bugs.kde.org/show_bug.cgi?id=475053 Andreas Sturmlechner changed: What|Removed |Added CC||ast...@gentoo.org --- Comment #1 from Andreas Sturmlechner --- Please note that at the time you have filed this bug, Gentoo is providing these - way more - up to date versions *in stable* that you should update to, then try and reproduce that bug: KDE Plasma 5.27.8 KDE Frameworks 5.110 Qt 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 475056] [Plasma 6] Deleting and recreating a command keyboard shortcut generates a new .desktop file every time
https://bugs.kde.org/show_bug.cgi?id=475056 Thiago Sueto changed: What|Removed |Added Summary|Deleting and recreating a |[Plasma 6] Deleting and |command keyboard shortcut |recreating a command |generates a new .desktop|keyboard shortcut generates |file every time |a new .desktop file every ||time -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 475056] Deleting and recreating a command keyboard shortcut generates a new .desktop file every time
https://bugs.kde.org/show_bug.cgi?id=475056 Thiago Sueto changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 475056] New: Deleting and recreating a command keyboard shortcut generates a new .desktop file every time
https://bugs.kde.org/show_bug.cgi?id=475056
Bug ID: 475056
Summary: Deleting and recreating a command keyboard shortcut
generates a new .desktop file every time
Classification: Frameworks and Libraries
Product: frameworks-kglobalaccel
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: herzensch...@gmail.com
Target Milestone: ---
SUMMARY
If you create a new keyboard shortcut that triggers a command, assign it a
shortcut (so it appears in ~/.config/kglobalshortcutsrc), delete it, and
recreate it, it generates a new .desktop file in ~/.local/share/applications
following the naming scheme executable{,-1,-2,-3,...,-n}.desktop.
The curious thing is that the entries in ~/.config/kglobalshortcutsrc do
disappear fine when you delete a shortcut, it's just the .desktop file that
doesn't.
So if the user keeps testing to figure whether a command works well or not,
they might end up with several redundant .desktop files.
STEPS TO REPRODUCE
1. Go to Shortcuts -> Add Command...
2. Create a new command /usr/bin/kdialog --msgbox "Sup"
3. Assign a shortcut to it, for example, Meta+K
4. Click Apply
5. Verify that ~/.config/kglobalshortcutsrc contains a kdialog entry, it should
point to kdialog.desktop
6. Delete the shortcut via System Settings
7. Create a new one that also uses kdialog
8. Verify that ~/.config/kglobalshortcutsrc contains a kdialog entry, it should
point to kdialog-2.desktop
OBSERVED RESULT
Every time you recreate the shortcut, a new desktop entry gets added to
~/.local/share/applications without removing the original.
EXPECTED RESULT
Every time you delete the shortcut, the original desktop entry gets deleted,
and every time you create a new shortcut using the same executable, the new
desktop entry reuses its name.
--
You are receiving this mail because:
You are watching all bug changes.
[kid3] [Bug 475055] New: Kid3 can't find file tag
https://bugs.kde.org/show_bug.cgi?id=475055 Bug ID: 475055 Summary: Kid3 can't find file tag Classification: Applications Product: kid3 Version: 3.9.x Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: mfraz74+...@gmail.com Target Milestone: --- SUMMARY I've viewed an album in mp4 format in Kid3 and it says that some tracks have no tags even though they are visible when using ffmpeg. STEPS TO REPRODUCE 1. Open directory in Kid3 2. See that some tracks say "No Tag" 3. Run ffmpeg -i and see that the tags are visible. ffmpeg -i 03Look\ What\ You\ Dun.m4a ffmpeg version 6.0-0ubuntu1~22.04.sav3 Copyright (c) 2000-2023 the FFmpeg developers [mov,mp4,m4a,3gp,3g2,mj2 @ 0x55ac5e1ca6c0] stream 0, timescale not set Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '03Look What You Dun.m4a': Metadata: major_brand : M4A minor_version : 512 compatible_brands: isomiso2 album_artist: Slade disc: 1 track : 3/20 artist : Slade album : The Very Best Of Slade date: 2005 genre : Glam Rock title : Look What You Dun Duration: 00:02:58.82, start: 0.00, bitrate: 147 kb/s Stream #0:0[0x1](eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 141 kb/s (default) Metadata: handler_name: SoundHandler vendor_id : [0][0][0][0] Stream #0:1[0x0]: Video: mjpeg (Baseline), yuvj444p(pc, bt470bg/unknown/unknown), 600x589, 90k tbr, 90k tbn (attached pic) SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-84-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 473363] Avatar page is not scrollable until resizing the window
https://bugs.kde.org/show_bug.cgi?id=473363 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/302 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343690] Missing windows tabbing
https://bugs.kde.org/show_bug.cgi?id=343690 Elias Probst changed: What|Removed |Added CC||m...@eliasprobst.eu -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475022] Tokodon does not show Follows in Notifications
https://bugs.kde.org/show_bug.cgi?id=475022 --- Comment #4 from anus...@mpi-inf.mpg.de --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474832] SDDM greeter does not launch when logging out.
https://bugs.kde.org/show_bug.cgi?id=474832 --- Comment #4 from Pablo --- (In reply to Nate Graham from comment #3) > So to be clear, nothing is actually crashing? Alright, sorry. So it seems that SDDM greeter is not starting. What I should do now? I have changed summary. I would edit importance too, but I am not able to do so now. Should I change "product" or "component" fields? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 438721] Crashes when the phone trys to connect
https://bugs.kde.org/show_bug.cgi?id=438721 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #15 from Oded Arbel --- I have this crash occurring frequently, after a Neon testing update a few days ago. This is the backtrace: #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7faf25242866 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #4 0x7faf267070cd in KCrash::defaultCrashHandler(int) () from /lib/x86_64-linux-gnu/libKF5Crash.so.5 #5 #6 Device::reloadPlugins (this=this@entry=0x5565731fcfd0) at ./core/device.cpp:184 #7 0x7faf274a1591 in Device::addLink (this=0x5565731fcfd0, link=) at ./core/device.cpp:292 #8 0x7faf2749c3a1 in Daemon::onNewDeviceLink (this=0x7ffc614e1aa0, link=0x5565732e3980) at ./core/daemon.cpp:170 #9 0x7faf25cf4924 in QtPrivate::QSlotObjectBase::call (a=0x7ffc614e0110, r=0x7ffc614e1aa0, this=0x55657323ef60) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x556573131a20, signal_index=3, argv=0x7ffc614e0110) at kernel/qobject.cpp:3925 #11 0x7faf25ced9f7 in QMetaObject::activate (sender=sender@entry=0x556573131a20, m=m@entry=0x7faf274b37e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc614e0110) at kernel/qobject.cpp:3985 #12 0x7faf2747b903 in LinkProvider::onConnectionReceived (this=this@entry=0x556573131a20, _t1=, _t1@entry=0x5565732e3980) at ./obj-x86_64-linux-gnu/core/kdeconnectcore_autogen/CSWKE6ESUK/moc_linkprovider.cpp:178 #13 0x7faf274867c4 in LanLinkProvider::addLink (this=this@entry=0x556573131a20, socket=, deviceInfo=...) at ./core/backends/lan/lanlinkprovider.cpp:614 #14 0x7faf274873cf in LanLinkProvider::encrypted (this=0x556573131a20) at ./core/backends/lan/lanlinkprovider.cpp:377 #15 0x7faf25cf4924 in QtPrivate::QSlotObjectBase::call (a=0x7ffc614e0410, r=0x556573131a20, this=0x5565732b24a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x556572f71c50, signal_index=16, argv=0x7ffc614e0410) at kernel/qobject.cpp:3925 #17 0x7faf25ced9f7 in QMetaObject::activate (sender=sender@entry=0x556572f71c50, m=m@entry=0x7faf251fa0e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3985 #18 0x7faf25164604 in QSslSocket::encrypted (this=this@entry=0x556572f71c50) at .moc/moc_qsslsocket.cpp:317 #19 0x7faf251847d3 in QSslSocketBackendPrivate::continueHandshake (this=0x55657312c350) at ssl/qsslsocket_openssl.cpp:2045 #20 0x7faf2518b13b in QSslSocketBackendPrivate::startHandshake (this=this@entry=0x55657312c350) at ssl/qsslsocket_openssl.cpp:1480 #21 0x7faf2518b903 in QSslSocketBackendPrivate::transmit (this=0x55657312c350) at ssl/qsslsocket_openssl.cpp:1136 #22 0x7faf25cf4958 in doActivate (sender=0x5565732bcc00, signal_index=3, argv=0x7ffc614e1670) at kernel/qobject.cpp:3937 #23 0x7faf25ced9f7 in QMetaObject::activate (sender=sender@entry=0x5565732bcc00, m=m@entry=0x7faf25f5a960 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3985 #24 0x7faf25be7394 in QIODevice::readyRead (this=this@entry=0x5565732bcc00) at .moc/moc_qiodevice.cpp:190 #25 0x7faf2513a21f in QAbstractSocketPrivate::emitReadyRead (channel=0, this=0x556573027620) at socket/qabstractsocket.cpp:1323 #26 QAbstractSocketPrivate::canReadNotification (this=0x556573027620) at socket/qabstractsocket.cpp:748 #27 0x7faf2514d359 in QReadNotifier::event (this=, e=) at socket/qnativesocketengine.cpp:1274 #28 0x7faf2696c763 in QApplicationPrivate::notify_helper (this=, receiver=0x55657327c390, e=0x7ffc614e17b0) at kernel/qapplication.cpp:3640 #29 0x7faf25cbce7a in QCoreApplication::notifyInternal2 (receiver=0x55657327c390, event=0x7ffc614e17b0) at kernel/qcoreapplication.cpp:1064 #30 0x7faf25cbd052 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #31 0x7faf25d16f75 in socketNotifierSourceDispatch (source=0x556572fab550) at kernel/qeventdispatcher_glib.cpp:107 #32 0x7faf2471949d in g_main_dispatch (context=0x7faf1c000ee0) at ../../../glib/gmain.c:3460 #33 g_main_context_dispatch (context=0x7faf1c000ee0) at ../../../glib/gmain.c:4200 #34 0x7faf24774178 in g_main_context_iterate.constprop.0 (context=0x7faf1c000ee0, block=, dispatch=1, self=) at ../../../glib/gmain.c:4276 #35 0x7faf247181b0 in g_main_context_iteration (context=0x7faf1c000ee0, may_block=1) at ../../../glib/gmain.c:4343 #36 0x7faf25d163de in QEventDispatcherGlib::processEvents (this=0x556572fab430, flags=...) at
[plasmashell] [Bug 474832] SDDM greeter does not launch when logging out.
https://bugs.kde.org/show_bug.cgi?id=474832 Pablo changed: What|Removed |Added Summary|Plasma Crash when logging |SDDM greeter does not |out.|launch when logging out. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 475054] New: KDEconnect daemon constantly crashes
https://bugs.kde.org/show_bug.cgi?id=475054 Bug ID: 475054 Summary: KDEconnect daemon constantly crashes Classification: Applications Product: kdeconnect Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: o...@geek.co.il CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.1) Qt Version: 5.15.10 Frameworks Version: 5.111.0 Operating System: Linux 6.5.4-060504-generic x86_64 Windowing System: Wayland Distribution: KDE neon Testing Edition DrKonqi: 5.27.8 [CoredumpBackend] -- Information about the crash: Probably when trying to connect to my phone The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault PID: 197137 (kdeconnectd) UID: 1000 (odeda) GID: 1000 (odeda) Signal: 11 (SEGV) Timestamp: Sat 2023-09-30 17:49:26 IDT (23s ago) Command Line: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd Executable: /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/dbus.service Unit: user@1000.service User Unit: dbus.service Slice: user-1000.slice Owner UID: 1000 (odeda) Boot ID: d89a9fce62bf44e7be4a9888301e22d4 Machine ID: 2f91240764fb4d21be2697e4579e16de Hostname: vesho Storage: /var/lib/systemd/coredump/core.kdeconnectd.1000.d89a9fce62bf44e7be4a9888301e22d4.197137.169608536600.zst (present) Size on Disk: 3.0M Message: Process 197137 (kdeconnectd) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.5-2ubuntu3.1.amd64 Module libudev.so.1 from deb systemd-252.5-2ubuntu3.1.amd64 Stack trace of thread 197137: #0 0x7f270fab __pthread_kill_implementation (libc.so.6 + 0xb) #1 0x7f270fa42866 __GI_raise (libc.so.6 + 0x42866) #2 0x7f27107970cd _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x80cd) #3 0x7f270fa42910 __restore_rt (libc.so.6 + 0x42910) #4 0x7f2711acc87e _ZN6Device13reloadPluginsEv (libkdeconnectcore.so.23 + 0x3c87e) #5 0x7f2711acd591 _ZN6Device7addLinkEP10DeviceLink (libkdeconnectcore.so.23 + 0x3d591) #6 0x7f2711ac83a1 _ZN6Daemon15onNewDeviceLinkEP10DeviceLink (libkdeconnectcore.so.23 + 0x383a1) #7 0x7f27104f4924 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2f4924) #8 0x7f2711aa7903 _ZN12LinkProvider20onConnectionReceivedEP10DeviceLink (libkdeconnectcore.so.23 + 0x17903) #9 0x7f2711ab27c4 _ZN15LanLinkProvider7addLinkEP10QSslSocketRK10DeviceInfo (libkdeconnectcore.so.23 + 0x227c4) #10 0x7f2711ab33cf _ZN15LanLinkProvider9encryptedEv (libkdeconnectcore.so.23 + 0x233cf) #11 0x7f27104f4924 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2f4924) #12 0x7f270f9847d3 _ZN24QSslSocketBackendPrivate17continueHandshakeEv (libQt5Network.so.5 + 0x1387d3) #13 0x7f270f98b13b _ZN24QSslSocketBackendPrivate14startHandshakeEv (libQt5Network.so.5 + 0x13f13b) #14 0x7f270f98b903 _ZN24QSslSocketBackendPrivate8transmitEv (libQt5Network.so.5 + 0x13f903) #15 0x7f27104f4958 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2f4958) #16 0x7f270f93a21f _ZN22QAbstractSocketPrivate13emitReadyReadEi (libQt5Network.so.5 + 0xee21f) #17 0x7f270f94d359 _ZN13QReadNotifier5eventEP6QEvent (libQt5Network.so.5 + 0x101359) #18 0x7f271116c763 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16c763) #19 0x7f27104bce7a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2bce7a) #20 0x7f2710516f75 socketNotifierSourceDispatch (libQt5Core.so.5 + 0x316f75) #21 0x7f270ed1949d g_main_context_dispatch (libglib-2.0.so.0 + 0x5b49d) #22 0x7f270ed74178 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xb6178) #23 0x7f270ed181b0 g_main_context_iteration (libglib-2.0.so.0 + 0x5a1b0) #24 0x7f27105163de _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3163de) #25 0x7f27104bb79b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2bb79b) #26 0x7f27104c3d44 _ZN16QCoreApplication4execEv
[kwin] [Bug 475053] New: blurred elements look buggy when zoom effect is used
https://bugs.kde.org/show_bug.cgi?id=475053 Bug ID: 475053 Summary: blurred elements look buggy when zoom effect is used Classification: Plasma Product: kwin Version: 5.27.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: w...@mail.ru Target Milestone: --- https://youtu.be/ete-A5q07io STEPS TO REPRODUCE 1. turn on blur 2. turn on zoom effect 3. zoom in on any blurred part OBSERVED RESULT looks bad EXPECTED RESULT looks good SOFTWARE/OS VERSIONS Linux/KDE Plasma: gentoo KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 473149] xdg-desktop-portal-kde crashed in NotificationPortal::notificationClosed() after finishing a screen recording with Kooha
https://bugs.kde.org/show_bug.cgi?id=473149 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com --- Comment #1 from Fushan Wen --- Cannot reproduce -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474384] Cannot select text with double click on the search field anymore
https://bugs.kde.org/show_bug.cgi?id=474384 Fushan Wen changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=473125 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 473125] Switching between System Settings pages with a stylus doesn't work most of the time in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=473125 Fushan Wen changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=474384 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474384] Cannot select text with double click on the search field anymore
https://bugs.kde.org/show_bug.cgi?id=474384 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #1 from Fushan Wen --- Likely fixed in Qt 6.5.3 https://bugreports.qt.io/browse/QTBUG-114258 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 473125] Switching between System Settings pages with a stylus doesn't work most of the time in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=473125 Fushan Wen changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM CC||qydwhotm...@gmail.com --- Comment #2 from Fushan Wen --- Fixed in Qt 6.5.3 https://bugreports.qt.io/browse/QTBUG-114258 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343690] Missing windows tabbing
https://bugs.kde.org/show_bug.cgi?id=343690 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474452] Widget Explorer opens centered on the screen when invoked for the first time after login
https://bugs.kde.org/show_bug.cgi?id=474452 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/896 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475052] New: Crop artefacts
https://bugs.kde.org/show_bug.cgi?id=475052 Bug ID: 475052 Summary: Crop artefacts Classification: Applications Product: krita Version: 5.1.5 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: vya...@yandex.ru Target Milestone: --- Created attachment 161974 --> https://bugs.kde.org/attachment.cgi?id=161974=edit Example of problem SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open jpg file or create new document larger than 2000x2000 px. 2. Crop it to smaller. 3. Resize and drag canvas in view OBSERVED RESULT Broken canvas with transparent grid artefacts. EXPECTED RESULT Just crop of image. SOFTWARE/OS VERSIONS Windows: macOS: Sonoma 14.0 Apple M1 Pro 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.
[www.kde.org] [Bug 475051] New: Remove release_announcements.po from l10n list
https://bugs.kde.org/show_bug.cgi?id=475051 Bug ID: 475051 Summary: Remove release_announcements.po from l10n list Classification: Websites Product: www.kde.org Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: emir_s...@icloud.com Target Milestone: --- Hello, Looks like the release_announcements.po file is no longer updated with release information, nowadays everything goes under www_www.po, with the announcements subfolder. Current contents of this file should be made static, and removed from the l10n pipeline. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 475024] Unlocking by password not possible until "Verification Timed Out" message appears (22 seconds) when fingerprint auth is set up
https://bugs.kde.org/show_bug.cgi?id=475024 --- Comment #4 from postix --- (In reply to Nate Graham from comment #3) > Same basic issue as Bug 455578, but affecting the lock screen rather than > the polkit dialog. It's expected at the moment until > https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/163 is > merged--hopefully for Plasma 6. Great to see that there's already some work happening! In terms of UX it would be good if it were fixed sooner than later. :) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 475047] Akregator crashed while i was dragging feeds out of the folder to the root
https://bugs.kde.org/show_bug.cgi?id=475047 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473848] The cursor in vim running in konsole should not move if I accidentally touch the laptop's touchpad
https://bugs.kde.org/show_bug.cgi?id=473848 --- Comment #2 from ak...@iname.com --- This is a kludge to fix this issue: unset TERM vim still works but its cursor is not moving any more if I make two finger gestures on the touchpad. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 475049] Kamoso crash on camera unplugging
https://bugs.kde.org/show_bug.cgi?id=475049 --- Comment #1 from Egor Kuznetsov --- Crash report with debugging symbols here. Looks like what needed? [KCrash Handler] #4 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x563fd78178f0, fundamental_type=fundamental_type@entry=80) at ../gobject/gtype.c:4184 #5 0x7f53ab4e6428 in g_object_notify (object=0x563fd78178f0, property_name=0x7f53654608c9 "zoom") at ../gobject/gobject.c:1583 #6 0x7f53ab4df468 in g_closure_invoke (closure=0x563fd78d5010, return_value=0x0, n_param_values=2, param_values=0x7ffebf06a440, invocation_hint=0x7ffebf06a390) at ../gobject/gclosure.c:832 #7 0x7f53ab4f261c in signal_emit_unlocked_R (node=node@entry=0x7ffebf06a510, detail=detail@entry=2562, instance=instance@entry=0x563fd779dea0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffebf06a440) at ../gobject/gsignal.c:3980 #8 0x7f53ab4f4031 in signal_emit_valist_unlocked (instance=instance@entry=0x563fd779dea0, signal_id=signal_id@entry=1, detail=detail@entry=2562, var_args=var_args@entry=0x7ffebf06a670) at ../gobject/gsignal.c:3612 #9 0x7f53ab4f9ce2 in g_signal_emit_valist (instance=0x563fd779dea0, signal_id=1, detail=2562, var_args=0x7ffebf06a670) at ../gobject/gsignal.c:3355 #10 0x7f53ab4f9d8f in g_signal_emit (instance=instance@entry=0x563fd779dea0, signal_id=, detail=) at ../gobject/gsignal.c:3675 #11 0x7f53ab4e36e4 in g_object_dispatch_properties_changed (object=0x563fd779dea0, n_pspecs=, pspecs=) at ../gobject/gobject.c:1427 #12 0x7f53a96ec1e4 in gst_object_dispatch_properties_changed (object=0x563fd779dea0, n_pspecs=1, pspecs=0x7ffebf06a7e0) at ../gst/gstobject.c:455 #13 0x7f53ab4e4038 in g_object_notify_queue_thaw (object=0x563fd779dea0, nqueue=) at ../gobject/gobject.c:358 #14 0x7f53ab4e7ee6 in g_object_set_valist (var_args=0x7ffebf06a970, first_property_name=, object=) at ../gobject/gobject.c:2792 #15 g_object_set_valist (object=, first_property_name=, var_args=0x7ffebf06a970) at ../gobject/gobject.c:2741 #16 0x7f53ab4e8ac3 in g_object_set (_object=0x563fd779dea0, first_property_name=first_property_name@entry=0x7f53654608c9 "zoom") at ../gobject/gobject.c:2956 #17 0x7f536545ccb1 in gst_camera_bin_create_elements (camera=0x563fd7ae7b20) at ../gst/camerabin2/gstcamerabin2.c:1742 #18 gst_camera_bin_change_state (element=0x563fd7ae7b20, trans=GST_STATE_CHANGE_NULL_TO_READY) at ../gst/camerabin2/gstcamerabin2.c:1891 #19 0x7f53a971a47b in gst_element_change_state (element=element@entry=0x563fd7ae7b20, transition=transition@entry=GST_STATE_CHANGE_NULL_TO_READY) at ../gst/gstelement.c:3093 #20 0x7f53a971ad0b in gst_element_set_state_func (element=0x563fd7ae7b20, state=GST_STATE_READY) at ../gst/gstelement.c:3047 #21 0x563fd5874a30 in WebcamControl::playDevice (this=0x7ffebf06b060, device=0x563fd732f050) at /usr/include/qt5/QtCore/qscopedpointer.h:138 #22 0x563fd5875d3d in WebcamControl::onBusMessage (message=, this=) at /usr/src/debug/kamoso-23.08.1/src/video/webcamcontrol.cpp:308 #23 webcamWatch (message=, user_data=0x7ffebf06b060) at /usr/src/debug/kamoso-23.08.1/src/video/webcamcontrol.cpp:244 #24 0x7f53a9702131 in gst_bus_source_dispatch (source=0x563fd7058060, callback=0x563fd5875ad0 , user_data=0x7ffebf06b060) at ../gst/gstbus.c:821 #25 0x7f53a95bcef0 in ?? () from /lib64/libglib-2.0.so.0 #26 0x7f53a95beb18 in ?? () from /lib64/libglib-2.0.so.0 #27 0x7f53a95bf1cc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #28 0x7f53a9b464a6 in QEventDispatcherGlib::processEvents (this=0x563fd6e62e10, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #29 0x7f53a9aebffb in QEventLoop::exec (this=this@entry=0x7ffebf06ae70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #30 0x7f53a9af4490 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #31 0x563fd587077d in main (argc=, argv=) at /usr/src/debug/kamoso-23.08.1/src/main.cpp:47 [Inferior 1 (process 15274) detached] -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 475050] New: Discover says "Unable to load applications, Please verify Internet connectivity" on fresh Neon install
https://bugs.kde.org/show_bug.cgi?id=475050 Bug ID: 475050 Summary: Discover says "Unable to load applications, Please verify Internet connectivity" on fresh Neon install Classification: Applications Product: Discover Version: 5.27.8 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: domojes...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 161973 --> https://bugs.kde.org/attachment.cgi?id=161973=edit What the Discover Homepage looks like SUMMARY I've just installed a fresh KDE Neon instance onto my laptop with the hopes of migrating from Kubuntu, but with newer KDE software. Unfortunately, I've run into two bugs, one of which I'm mentioning here (the other is just that the KDE Neon staart symbol turns into the KDE multicolored logo when trying to set it to my app launcher symbol, but that's besides the point). When I open Discover, the Home page tells me that I'm not connected, and the "Editor's choice" thing is weirdly not at the top of the window, possibly because of some default reserved space I don't know about. Everything else about Discover is seemingly working fine, it's *just* the Home page that isn't working. Per the recommendation of a different user with a similar bug but on Arch (and from a while ago), I tried reinstalling appstream, but that just broke Discover altogether with no way to fix it. So, I tried reinstalling again, and the original issue persisted. This is the laptop I intend to use for school, so I'm hoping this issue isn't all that important. Though worst-case scenario, I'll just switch back to Kubuntu LTS. I still get KDE, so I'm happy. STEPS TO REPRODUCE 1. Download the current available Neon iso from official page and install to computer 2. Open Discover OBSERVED RESULT Home reports connectivity errors, everything else is fine. EXPECTED RESULT Discover works as intended (home page loads apps) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27.8 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475048] Kdenlive sometimes doesn't change speed
https://bugs.kde.org/show_bug.cgi?id=475048 --- Comment #1 from aron...@gmail.com --- Screencast: https://t.me/kdenlive/73557 -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 475049] New: Kamoso crash on camera unplugging
https://bugs.kde.org/show_bug.cgi?id=475049 Bug ID: 475049 Summary: Kamoso crash on camera unplugging Classification: Applications Product: kamoso Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: egor.kuznetsov...@gmail.com Target Milestone: --- SUMMARY *** When I start Kamoso with plugged USB camera, it can show picture, but when I unplug it with open Kamoso, it crashed with some logs in terminal *** STEPS TO REPRODUCE 1. Open Kamoso 2. Plug USB webcam 3. Unplug USB webcam OBSERVED RESULT Kamoso crashed with next log: (kamoso:14078): GLib-GObject-CRITICAL **: 16:07:58.798: g_object_notify: assertion 'G_IS_OBJECT (object)' failed Fatal glibc error: pthread_mutex_lock.c:130 (___pthread_mutex_lock): assertion failed: mutex->__data.__owner == 0 20 -- exe=/usr/bin/kamoso 17 -- platform=wayland 15 -- appname=kamoso 17 -- apppath=/usr/bin 9 -- signal=6 10 -- pid=14078 19 -- appversion=23.08.1 19 -- programname=Kamoso 31 -- bugaddress=sub...@bugs.kde.org KCrash: Application 'kamoso' crashing... KCrash: Attempting to start /usr/libexec/drkonqi kf5idletime_wayland: This plugin does not support polling idle time [1] + 14078 suspended (signal) kamoso EXPECTED RESULT Nothing crashed, Kamoso black screen again SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230926 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.4-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475048] New: Kdenlive sometimes doesn't change speed
https://bugs.kde.org/show_bug.cgi?id=475048 Bug ID: 475048 Summary: Kdenlive sometimes doesn't change speed Classification: Applications Product: kdenlive Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: aron...@gmail.com Target Milestone: --- When I speed up a clip, I can't change it back to be slower afterwards. It happens randomly, and changing the position and length of the clip sometimes fixes it. KDE Neon, Plasma 5.27.8, Kdenlive 23.08.1 repo package + appimage -- You are receiving this mail because: You are watching all bug changes.
