[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 Anton changed: What|Removed |Added CC||anton.kiessl...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483927] Window delay behind the cursor
https://bugs.kde.org/show_bug.cgi?id=483927 --- Comment #3 from Anton --- (In reply to Anton from comment #2) > same bug Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Pentium® Gold 7505 @ 2.00GHz Memory: 15.3 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop X515EA_F515EA System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483927] Window delay behind the cursor
https://bugs.kde.org/show_bug.cgi?id=483927 Anton changed: What|Removed |Added CC||opensourcemail...@proton.me --- Comment #2 from Anton --- same bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483351] plasma-emojier high memory usage
https://bugs.kde.org/show_bug.cgi?id=483351 --- Comment #4 from Anton K --- The bug is relevant after the update: Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 6500 XT -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483351] plasma-emojier memory leak
https://bugs.kde.org/show_bug.cgi?id=483351 Anton K changed: What|Removed |Added CC||kvanton@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483351] New: plasma-emojier memory leak
https://bugs.kde.org/show_bug.cgi?id=483351 Bug ID: 483351 Summary: plasma-emojier memory leak Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Emoji Selector Assignee: plasma-b...@kde.org Reporter: kvanton@yandex.ru Target Milestone: 1.0 Created attachment 167046 --> https://bugs.kde.org/attachment.cgi?id=167046=edit htop screenshot SUMMARY plasma-emojier memory leak STEPS TO REPRODUCE 1. open plasma-emojier (I use a keyboard hot key) 2. switch different groups and use the search 3. observe the leak SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.5-060505-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482850] Screenshot control buttons disappear after using commenting tools
https://bugs.kde.org/show_bug.cgi?id=482850 --- Comment #1 from Anton --- I have the same thing -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482850] Screenshot control buttons disappear after using commenting tools
https://bugs.kde.org/show_bug.cgi?id=482850 Anton changed: What|Removed |Added CC||dlymailag...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482603] Player widget can't rewind Spotify songs.
https://bugs.kde.org/show_bug.cgi?id=482603 --- Comment #4 from Anton --- (In reply to Nate Graham from comment #3) > Maybe Spotify doesn't expose this functionality to us but we don't have away > of disabling the UI for it? In plasma 5 rewinding worked -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482603] Player widget can't rewind Spotify songs.
https://bugs.kde.org/show_bug.cgi?id=482603 Anton changed: What|Removed |Added CC||dlymailag...@mail.ru --- Comment #1 from Anton --- Comment on attachment 166518 --> https://bugs.kde.org/attachment.cgi?id=166518 Player widget can't rewind Spotify songs, the slider is dragged, but the song itself does not rewind. same -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482466] New: Clipboard manager hot key doesn't open on mouse position
https://bugs.kde.org/show_bug.cgi?id=482466 Bug ID: 482466 Summary: Clipboard manager hot key doesn't open on mouse position Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kapitoh...@gmail.com Target Milestone: --- Created attachment 166425 --> https://bugs.kde.org/attachment.cgi?id=166425=edit Two screenshots. One (ok) when all windows are hidden, second (not ok) when any windows is not hidden SUMMARY Clipboard manager doesn't open windows on mouse position. Instead it opens it in the bottom of the screen, so it's impossible to choose all previous items. However it has this behavior only if some other window is opened. STEPS TO REPRODUCE 1. Open any window. For instance Dolphin 2. Push hot key combination META + V OBSERVED RESULT Clipboard manager window is always centered in the bottom of the screen EXPECTED RESULT It should appear on mouse position SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Kernel version: 6.5.0-21-generic (64-bit) Graphics platform: Wayland Graphics processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 482447] KMail crash at startup
https://bugs.kde.org/show_bug.cgi?id=482447 Anton K changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Anton K --- It seems that the problem is somehow related to the amd gpu, I tried to update the driver, and now it works. I don't have a file right now: /opt/amdgpu/lib/x86_64-linux-gnu/libva.so.2 maybe I have an amd gpu installed somehow wrong, I haven't figured it out yet, but everything seems to work. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 482447] New: KMail crash at startup
https://bugs.kde.org/show_bug.cgi?id=482447 Bug ID: 482447 Summary: KMail crash at startup Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: misc Assignee: kdepim-b...@kde.org Reporter: kvanton@yandex.ru Target Milestone: --- SUMMARY Crash of the program during startup. But I get notifications about new mail. I don't remember if this happened immediately after switching to plasma 6, but it looks like it happened after some kind of update, because it used to work. STEPS TO REPRODUCE 1. start kmail OBSERVED RESULT start the program EXPECTED RESULT crash the program SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.5-060505-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION (gdb) run Starting program: /usr/bin/kmail [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe13ff640 (LWP 10852)] [New Thread 0x7fffdbfff640 (LWP 10853)] [New Thread 0x7fffdb7fe640 (LWP 10854)] [New Thread 0x7fffd97ff640 (LWP 10855)] [New Thread 0x7fffd8ffe640 (LWP 10856)] [New Thread 0x7fffc67ff640 (LWP 10857)] [New Thread 0x7fffc5ffe640 (LWP 10858)] [New Thread 0x7fffc57fd640 (LWP 10859)] [New Thread 0x7fffc4ffc640 (LWP 10860)] [New Thread 0x7fffa640 (LWP 10861)] [New Thread 0x7fffaf7fe640 (LWP 10862)] [Thread 0x7fffaf7fe640 (LWP 10862) exited] [Thread 0x7fffa640 (LWP 10861) exited] [Thread 0x7fffc4ffc640 (LWP 10860) exited] [Thread 0x7fffc57fd640 (LWP 10859) exited] [New Thread 0x7fffc57fd640 (LWP 10863)] [New Thread 0x7fffc4ffc640 (LWP 10864)] [New Thread 0x7fffa640 (LWP 10865)] [New Thread 0x7fffaf7fe640 (LWP 10866)] [New Thread 0x7fffaeffd640 (LWP 10867)] [New Thread 0x7fffae7fc640 (LWP 10868)] [New Thread 0x7fffadffb640 (LWP 10869)] [New Thread 0x7fffad7fa640 (LWP 10870)] [Thread 0x7fffad7fa640 (LWP 10870) exited] [Thread 0x7fffadffb640 (LWP 10869) exited] [Thread 0x7fffae7fc640 (LWP 10868) exited] [Thread 0x7fffaeffd640 (LWP 10867) exited] qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "stateChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMState qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "connectivityChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMConnectivityState qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "deviceTypeChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMDeviceType qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "meteredChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMMetered [New Thread 0x7fffaeffd640 (LWP 10871)] [New Thread 0x7fffae7fc640 (LWP 10872)] [Detaching after fork from child process 10875] [Detaching after fork from child process 10877] [New Thread 0x7fffadffb640 (LWP 10879)] [New Thread 0x7fffad7fa640 (LWP 10881)] [Detaching after fork from child process 10882] [Detaching after fork from child process 10883] [Detaching after fork from child process 10884] [New Thread 0x7fff97bff640 (LWP 10887)] [New Thread 0x7fff973fe640 (LWP 10888)] [New Thread 0x7fff96bfd640 (LWP 10889)] [New Thread 0x7fff963fc640 (LWP 10890)] [New Thread 0x7fff95bfb640 (LWP 10891)] [New Thread 0x7fff953fa640 (LWP 10892)] [New Thread 0x7fff94bf9640 (LWP 10893)] [New Thread 0x7fff77fff640 (LWP 10895)] [New Thread 0x7fff777fe640 (LWP 10894)] [New Thread 0x7fff6640 (LWP 10896)] [New Thread 0x7fff76ffd640 (LWP 10897)] [New Thread 0x7fff767fc640 (LWP 10898)] [New Thread 0x7fff75ffb640 (LWP 10899)] [New Thread 0x7fff757fa640 (LWP 10900)] warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts of file /lib/x86_64-linux-gnu/libadblockplugin.so.6. Use `info auto-load python-scripts [REGEXP]' to list them. [New Thread 0x7fff66dff640 (LWP 10908)] [Thread 0x7fff66dff640 (LWP 10908) exited] [New Thread 0x7fff66dff640 (LWP 10909)] [New Thread 0x7fff74ff9640 (LWP 10910)] [Thread 0x7fff74ff9640 (LWP 10910) exited] [Thread 0x7fff66dff640 (LWP 10909) exited] [New Thread 0x7fff66dff640 (LWP 10911)] [New Thread 0x7fff74ff9640 (LWP 10912)] [Thread 0x7fff74ff9640 (LWP 10912) exited] [Thread 0x7fff66dff640 (LWP 10911) exited] [New Thread 0x7fff66dff640 (LWP 10913)] [New Thread 0x7fff74ff9640 (LWP 10914)] [Thread 0x7fff74ff9640 (LWP 10914) exited] [Thread 0x7fff66dff640 (LWP 10913) exited] [New Thread 0x7fff66dff640 (LWP 10915)] [New Thread 0x7fff74ff9640 (LWP 10916)] kf.config.core: Watching absolute paths is not supported "/usr/share/color-schemes/BreezeDark.colors" [New Thread 0x7fff6f7fe640 (LWP 10925)]
[systemsettings] [Bug 481663] After changing the user password the suggestion to change KWallet password is shown beneath all windows
https://bugs.kde.org/show_bug.cgi?id=481663 --- Comment #3 from Anton --- Created attachment 166093 --> https://bugs.kde.org/attachment.cgi?id=166093=edit Screen recording of the bug Recorded the bug, attached the video. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481663] After changing the user password the suggestion to change KWallet password is shown beneath all windows
https://bugs.kde.org/show_bug.cgi?id=481663 --- Comment #2 from Anton --- Please note that I specifically mention it's the KWallet password change window, not the user's password change. If still unclear, I can create some screenshots/recordings a bit later. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481663] New: After changing the user password the suggestion to change KWallet password is shown beneath all windows
https://bugs.kde.org/show_bug.cgi?id=481663 Bug ID: 481663 Summary: After changing the user password the suggestion to change KWallet password is shown beneath all windows Classification: Applications Product: systemsettings Version: 5.27.10 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: antkaid+bugs...@gmail.com CC: uhh...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Create a "Standard" (non-"Administrator") user account (say, user1); 2. Log in as user1, open Settings > Users and go through the password change flow; OBSERVED RESULT KDE suggests to also change KWallet password, but this suggestion appears beneath the Users window and is thus unnoticed. EXPECTED RESULT KWallet password change suggestion is shown above all windows and thus fits into the password change flow as designed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 378984] Root password required for user Password change
https://bugs.kde.org/show_bug.cgi?id=378984 Anton changed: What|Removed |Added CC||antkaid+bugs...@gmail.com --- Comment #7 from Anton --- Still present in Debian 12 with KDE Plasma 5.27.10. While passwd only requires the user to know their own password to change it, KDE for some reason requires the presence of the admin. This is at the same time bad and surprising. 1) If possible, please address the "bad" part: remove the need for the user to enter the admin's password in this use case; 2) If not, please address the "surprising" part: 2.1) State VERY explicitly in the PolicyKit1 KDE Agent window for the "Standard" user that it's the admin's password that's required. Users keep entering their passwords only to get auth failures, thinking they've made a mistake, this creates a lot of frustration; 2.2) Admins creating "Standard" users don't know about this bug beforehand. Please state this explicitly, as early as the user is created (at least, if created through KDE). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 480462] New: kded crashes if there is a hard disk with bad SMART
https://bugs.kde.org/show_bug.cgi?id=480462 Bug ID: 480462 Summary: kded crashes if there is a hard disk with bad SMART Classification: Frameworks and Libraries Product: frameworks-kded Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: antosha...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY kded (5.249.0) crashes if there is a hard disk with a bad SMART state in the system. Apparently it is trying to display a warning that the disk is about to die (although this is not true in my case, but that's not the point). However, if you disable the SMART service in service management, it stops crashing. If you remove a bad SMART hard disk from the system, it stops crashing too. When it crashes, the console displays the following: Registering ":1.161/StatusNotifierItem" to system tray ASSERT: "kcm" in file ./src/smartnotifier.cpp, line 43 KCrash: appFilePath points to nullptr! KCrash: Application '' crashing... crashRecursionCounter = 2 Aborted (core dumped) STEPS TO REPRODUCE 1. Have a disk with bad SMART status in system 2. Start kded6 with "SMART" service enabled in service management 3. crash OBSERVED RESULT kded6 crashes silently after some time EXPECTED RESULT A new notification would appear that the disk was in a bad state (This is what happens in KDE Plasma 5) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition (both neon-unstable-20240128-1119.iso and neon-unstable-20240122-1334.iso) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Here is a video of the problem - https://drive.google.com/file/d/1oHzS7y_TQfiYIVGELeK_po2xTBVL2qOV/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480202] Falha após UPDATE
https://bugs.kde.org/show_bug.cgi?id=480202 Anton Yablokov changed: What|Removed |Added CC||stsav...@mail.ru --- Comment #1 from Anton Yablokov --- I do confirm the crash after the recent update. The downgrade of `kdeconnect` does not solve the issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477718] New: Buttons do not update when ConfigModule.buttons property is changed,
https://bugs.kde.org/show_bug.cgi?id=477718 Bug ID: 477718 Summary: Buttons do not update when ConfigModule.buttons property is changed, Classification: Applications Product: systemsettings Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: golube...@altlinux.org Target Milestone: --- I'm creating a KCM module, and would like to sometimes hide the "Defaults" button. Main KCM class inherits from ConfigModule, which has a public property "buttons". But when changing this property, visually nothing happens, like the signal does not reach ModuleView::updateButtons. And there doesn't seem to be a good way to manually update this. But, for example, changing the needsSave property leads to updating the buttons and some button may “unexpectedly” disappear or appear. This is how I use it - I invert needsSave twice to update the buttons, but this, of course, is wrong. Here I posted a minimal example to reproduce (see main.qml): https://gitlab.com/golubevan/kcm-minimal/-/tree/update-buttons SOFTWARE/OS VERSIONS Linux 6.5.12 (X11) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 473854] KDE Invent - the Merkuro description is confusing
https://bugs.kde.org/show_bug.cgi?id=473854 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[solid] [Bug 226022] weather widget doesn't retry to update the weater from internet
https://bugs.kde.org/show_bug.cgi?id=226022 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 459551] Oauth2 failure on connecting google groupware
https://bugs.kde.org/show_bug.cgi?id=459551 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386253] Impossible to set Alt+Print shortcut
https://bugs.kde.org/show_bug.cgi?id=386253 Anton changed: What|Removed |Added CC||antkaid+bugs...@gmail.com --- Comment #19 from Anton --- For some reason I cannot vote for this... If I could, I would. Any news? In regards to the SysRq references... I believe SysRq commands can successfully co-exist with Alt-PrtSc taking screenshots. I'm observing this on Xubuntu 22.04 with Xfce 4.16: even though PrtSc is indeed working as SysRq, so with "SysRq, h" I can send help messages into dmesg (even from the X session), Xfce still perfectly handles Alt+PrtSc for the screenshots. Could KDE just do the same if the user wants to use Alt+PrtSc? -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 263174] Fingerprint support for kwallet
https://bugs.kde.org/show_bug.cgi?id=263174 Anton changed: What|Removed |Added CC||anton.gorenkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475237] New: Crash during activating Firefox by special hotkey
https://bugs.kde.org/show_bug.cgi?id=475237
Bug ID: 475237
Summary: Crash during activating Firefox by special hotkey
Classification: I don't know
Product: kde
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: a...@nmetau.edu.ua
Target Milestone: ---
Application: kglobalaccel5 (5.110.0)
Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.5-300.xf40.x86_64 x86_64
Windowing System: X11
Distribution: XF 40 (Workstation Edition Prerelease)
DrKonqi: 5.27.8 [KCrashBackend]
-- Information about the crash:
I have a separate hotkey (win+F) to activate Firefox. After last large update
when I press this hotkey, crash occured and bottom panel is redrawed.
The crash can be reproduced every time.
-- Backtrace:
Application: KDE Global Shortcuts Service (kglobalaccel5), signal: Aborted
[KCrash Handler]
#4 0x7f45d26add64 in __pthread_kill_implementation () from
/lib64/libc.so.6
#5 0x7f45d265b8de in raise () from /lib64/libc.so.6
#6 0x7f45d26438ff in abort () from /lib64/libc.so.6
#7 0x7f45d1c73cf2 in _dbus_abort.cold () from /lib64/libdbus-1.so.3
#8 0x7f45d1c9c102 in _dbus_warn_check_failed () from /lib64/libdbus-1.so.3
#9 0x7f45d1c8aab1 in dbus_message_new_method_call () from
/lib64/libdbus-1.so.3
#10 0x7f45d2b3f1fc in QDBusMessagePrivate::toDBusMessage(QDBusMessage
const&, QFlags, QDBusError*) () from
/lib64/libQt5DBus.so.5
#11 0x7f45d2b38635 in
QDBusConnectionPrivate::sendWithReplyAsync(QDBusMessage const&, QObject*, char
const*, char const*, int) () from /lib64/libQt5DBus.so.5
#12 0x7f45d2b24ea1 in QDBusConnection::asyncCall(QDBusMessage const&, int)
const () from /lib64/libQt5DBus.so.5
#13 0x7f45d39a9c74 in
KServiceActionComponent::emitGlobalShortcutPressed(GlobalShortcut
const&)::{lambda(QString const&)#1}::operator()(QString const&) const () from
/lib64/libKF5GlobalAccelPrivate.so.5
#14 0x7f45d39ab567 in
KServiceActionComponent::emitGlobalShortcutPressed(GlobalShortcut const&) ()
from /lib64/libKF5GlobalAccelPrivate.so.5
#15 0x7f45d39b1a5c in GlobalShortcutsRegistry::keyPressed(int) () from
/lib64/libKF5GlobalAccelPrivate.so.5
#16 0x7f45d0f02bce in KGlobalAccelImpl::nativeEventFilter(QByteArray
const&, void*, long*) () from
/usr/lib64/qt5/plugins/org.kde.kglobalaccel5.platforms/KF5GlobalAccelPrivateXcb.so
#17 0x7f45d2eb12ac in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
from /lib64/libQt5Core.so.5
#18 0x7f45ceef1946 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*)
() from /lib64/libQt5XcbQpa.so.5
#19 0x7f45ceef307f in
QXcbConnection::processXcbEvents(QFlags) () from
/lib64/libQt5XcbQpa.so.5
#20 0x7f45cef1b4cf in xcbSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5XcbQpa.so.5
#21 0x7f45d1912e1c in g_main_context_dispatch_unlocked.lto_priv () from
/lib64/libglib-2.0.so.0
#22 0x7f45d196dd78 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#23 0x7f45d1910a93 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#24 0x7f45d2f06759 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#25 0x7f45d2eb2bdb in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#26 0x7f45d2ebae6b in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#27 0x55a53a7ac8ab in main ()
[Inferior 1 (process 1957) detached]
Reported using DrKonqi
This report was filed against 'kde' because the product 'kglobalaccel5' 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.
[Akonadi] [Bug 470762] During Boot up Google groupware throws a app restart request
https://bugs.kde.org/show_bug.cgi?id=470762 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 452565] Akonadi is creating "Unknown Organization" in $HOME/.config
https://bugs.kde.org/show_bug.cgi?id=452565 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 428348] Google Calendar synchronization setup is broken
https://bugs.kde.org/show_bug.cgi?id=428348 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 473897] Cannot add Google Groupware, "Configured account does not exist" then "Resource is not configured"
https://bugs.kde.org/show_bug.cgi?id=473897 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 444288] Akonadi "losing connection" to Google Calendars after some uptime / waking from sleep until either akonadictrl restart is used or Google Groupware is restarted in Korganizer.
https://bugs.kde.org/show_bug.cgi?id=444288 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452303] Dolphin doesn't remember Bitlocker partition's password
https://bugs.kde.org/show_bug.cgi?id=452303 Anton changed: What|Removed |Added CC||anton.gorenkov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Anton Schenker changed: What|Removed |Added CC||anton.schen...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474633] New: Some of mouse actions are not detected in re-bind tool (Logi Anywhere 2S)
https://bugs.kde.org/show_bug.cgi?id=474633 Bug ID: 474633 Summary: Some of mouse actions are not detected in re-bind tool (Logi Anywhere 2S) Classification: Applications Product: systemsettings Version: 5.27.8 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: anton.dadi...@yandex.ru CC: natalie_clar...@yahoo.de Target Milestone: --- SUMMARY The new tool for remapping extra mouse buttons is not working for mouse wheel left/right and middle button actions (using Logi Anywhere 2S mouse). Nevertheless left-side buttons are being detected. xbindkeys supports all actions fine, so this is not a hardware problem. STEPS TO REPRODUCE 1. Go to settings > Input Devices > Mouse 2. Select the correct device and push the Re-Bind button 3. Click Add Binding then push the extra button to remap OBSERVED RESULT Not detecting and mouse events SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 (Wayland) 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.
[kstars] [Bug 473402] New: The INDI Driver Astrophysics in EKOS has disappeared in Version 3.6.6
https://bugs.kde.org/show_bug.cgi?id=473402 Bug ID: 473402 Summary: The INDI Driver Astrophysics in EKOS has disappeared in Version 3.6.6 Classification: Applications Product: kstars Version: 3.6.6 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: a.heidem...@wanadoo.fr 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 EKOS 2. Edit Mount 3. Search Astrophysics OBSERVED RESULT : the Driver Astrophysics has disappeared in Version 3.6.6 EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 318357] GROUP : group by regular expression [patch].
https://bugs.kde.org/show_bug.cgi?id=318357 --- Comment #39 from Christoph Anton Mitterer --- I still think that allowing the full power of selection via regular expressions for experts would be very desirable, while at the same time there should be some presets or so, that allow usage by average users not familiar with regexps (e.g. grouping by filename extension... maybe even for both only the final one, that is everything after the last `.`, or any, that is everything after the first `.`). -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 344696] Kig crashes when launched
https://bugs.kde.org/show_bug.cgi?id=344696 --- Comment #3 from Anton Guda --- Created attachment 159015 --> https://bugs.kde.org/attachment.cgi?id=159015=edit New crash information added by DrKonqi kig (23.04.1) using Qt 5.15.9 Crash during start appears in Fedora kig-23.04.1-1.fc39.x86_64 -- Backtrace (Reduced): #4 0x7f157aba3d80 in KParts::ReadOnlyPart::url() const () from /lib64/libKF5Parts.so.5 #5 0x5612e1e517c7 in Kig::saveProperties(KConfigGroup&) () #6 0x7f157aa78950 in KMainWindow::savePropertiesInternal(KConfig*, int) () from /lib64/libKF5XmlGui.so.5 #7 0x7f157aa78a68 in KMWSessionManager::saveState(QSessionManager&) () from /lib64/libKF5XmlGui.so.5 #8 0x7f15792e86c1 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 344696] Kig crashes when launched
https://bugs.kde.org/show_bug.cgi?id=344696 Anton Guda changed: What|Removed |Added CC||a...@nmetau.edu.ua -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 441256] Feature request: switch to force single instance
https://bugs.kde.org/show_bug.cgi?id=441256 Anton Smirnov changed: What|Removed |Added CC||sand...@sandfox.me -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 467664] New: save and close
https://bugs.kde.org/show_bug.cgi?id=467664 Bug ID: 467664 Summary: save and close Classification: Applications Product: tellico Version: 3.4.6 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: kvanton@yandex.ru Target Milestone: --- Application: tellico (3.4.6) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.6-060206-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: crash after close and click on save Even before that, it sometimes crashed when I changed the group near the fields The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Tellico (tellico), signal: Segmentation fault [KCrash Handler] #4 0x7f3ad2f8313a in QBoxLayoutItem::~QBoxLayoutItem (this=0x7f3ab4006540, __in_chrg=) at kernel/qboxlayout.cpp:56 #5 QBoxLayoutPrivate::deleteAll (this=0x56413cae8b30) at kernel/qboxlayout.cpp:121 #6 QBoxLayout::~QBoxLayout (this=0x56413c975920, __in_chrg=) at kernel/qboxlayout.cpp:574 #7 0x7f3ad2f8338d in QHBoxLayout::~QHBoxLayout (this=0x56413c975920, __in_chrg=) at kernel/qboxlayout.cpp:1290 #8 0x7f3ad2faae6b in QWidget::~QWidget (this=0x56413ca74580, __in_chrg=) at kernel/qwidget.cpp:1438 #9 0x56413b782982 in ?? () #10 0x7f3ad20e711e in QObjectPrivate::deleteChildren (this=this@entry=0x56413c975740) at kernel/qobject.cpp:2137 #11 0x7f3ad2fab056 in QWidget::~QWidget (this=0x56413ca243c0, __in_chrg=) at kernel/qwidget.cpp:1524 #12 0x56413b78226f in ?? () #13 0x7f3ad20e711e in QObjectPrivate::deleteChildren (this=this@entry=0x56413cb473b0) at kernel/qobject.cpp:2137 #14 0x7f3ad2fab056 in QWidget::~QWidget (this=0x56413cb44e70, __in_chrg=) at kernel/qwidget.cpp:1524 #15 0x7f3ad2fab3ad in QWidget::~QWidget (this=0x56413cb44e70, __in_chrg=) at kernel/qwidget.cpp:1548 #16 0x7f3ad20e711e in QObjectPrivate::deleteChildren (this=this@entry=0x56413cb44c70) at kernel/qobject.cpp:2137 #17 0x7f3ad2fab056 in QWidget::~QWidget (this=0x56413ca476b0, __in_chrg=) at kernel/qwidget.cpp:1524 #18 0x7f3ad2fab3ad in QWidget::~QWidget (this=0x56413ca476b0, __in_chrg=) at kernel/qwidget.cpp:1548 #19 0x7f3ad20e711e in QObjectPrivate::deleteChildren (this=this@entry=0x56413c1afe40) at kernel/qobject.cpp:2137 #20 0x7f3ad2fab056 in QWidget::~QWidget (this=0x56413c1b1d90, __in_chrg=) at kernel/qwidget.cpp:1524 #21 0x7f3ad312a44d in QStackedWidget::~QStackedWidget (this=0x56413c1b1d90, __in_chrg=) at widgets/qstackedwidget.cpp:147 #22 0x7f3ad20e711e in QObjectPrivate::deleteChildren (this=this@entry=0x56413bf0d9b0) at kernel/qobject.cpp:2137 #23 0x7f3ad2fab056 in QWidget::~QWidget (this=0x56413c1b1bd0, __in_chrg=) at kernel/qwidget.cpp:1524 #24 0x56413b77c691 in ?? () #25 0x7f3ad20e711e in QObjectPrivate::deleteChildren (this=this@entry=0x56413c1ba6d0) at kernel/qobject.cpp:2137 #26 0x7f3ad2fab056 in QWidget::~QWidget (this=0x56413c01af40, __in_chrg=) at kernel/qwidget.cpp:1524 #27 0x56413b608abd in ?? () #28 0x7f3ad20e711e in QObjectPrivate::deleteChildren (this=this@entry=0x56413bb174d0) at kernel/qobject.cpp:2137 #29 0x7f3ad2fab056 in QWidget::~QWidget (this=0x56413babc6e0, __in_chrg=) at kernel/qwidget.cpp:1524 #30 0x56413b638c60 in ?? () #31 0x56413b638ccd in ?? () #32 0x7f3ad20e9883 in QObject::event (this=0x56413babc6e0, e=0x56413cc3eed0) at kernel/qobject.cpp:1334 #33 0x7f3ad3c8166d in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #34 0x7f3ad2f6c793 in QApplicationPrivate::notify_helper (this=, receiver=0x56413babc6e0, e=0x56413cc3eed0) at kernel/qapplication.cpp:3640 #35 0x7f3ad20bc07a in QCoreApplication::notifyInternal2 (receiver=0x56413babc6e0, event=0x56413cc3eed0) at kernel/qcoreapplication.cpp:1064 #36 0x7f3ad20bf167 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x56413b934440) at kernel/qcoreapplication.cpp:1821 #37 0x7f3ad2116487 in postEventSourceDispatch (s=0x56413ba982e0) at kernel/qeventdispatcher_glib.cpp:277 #38 0x7f3ac731ad3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x7f3ac736f6c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #40 0x7f3ac73183e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #41 0x7f3ad2115ad8 in QEventDispatcherGlib::processEvents (this=0x56413baae3a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #42 0x7f3ad20ba99b in QEventLoop::exec (this=this@entry=0x7ffc662915f0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #43 0x7f3ad20c2f34 in QCoreApplication::exec () at
[krusader] [Bug 462307] No folder or file icons are shown
https://bugs.kde.org/show_bug.cgi?id=462307 Anton Smirnov changed: What|Removed |Added CC||sand...@sandfox.me -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 313976] kdeinit4 --no-kded --suicide leaves behind processes
https://bugs.kde.org/show_bug.cgi?id=313976 Christoph Anton Mitterer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Christoph Anton Mitterer --- Well I couldn't really test it anymore, since even when starting digikam alone, there no longer seem to be any kdeinit4 processes. So I guess this can be closed now. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 296218] Doesn't display menus after restoring from tray.
https://bugs.kde.org/show_bug.cgi?id=296218 Anton Yablokov changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #5 from Anton Yablokov --- Oh, it's been ages. Since then, Unity DE was abandoned and resurrected back. I moved from Unity in 2014, I think. Since then, it would take too much effort to check whether something changed. So, I wish I close the bug for good. Please forgive me for not answering back in 2018. -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 452907] Kmag garbled and glitched with two monitors
https://bugs.kde.org/show_bug.cgi?id=452907 Anton Anikin changed: What|Removed |Added Version Fixed In||22.12 -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 452907] Kmag garbled and glitched with two monitors
https://bugs.kde.org/show_bug.cgi?id=452907 Anton Anikin changed: What|Removed |Added Latest Commit||d8e6757b -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 452907] Kmag garbled and glitched with two monitors
https://bugs.kde.org/show_bug.cgi?id=452907 Anton Anikin changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454129] [Wayland] Pixelated artifacts when resuming from suspend, which partially reveals content
https://bugs.kde.org/show_bug.cgi?id=454129 Anton K changed: What|Removed |Added CC||kvanton@yandex.ru --- Comment #12 from Anton K --- Same problem only on Wayland, no problem with X11. Switching between consoles (ctrl+alt+f1 and then ctrl+alt+f2) restores the display and everything continues to work as usual. VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] "/dev/dri/card0", driven by "radeon" output 0: card0-HDMI-A-1 output 1:card0-DVI-I-1 I don’t see anything interesting in the logs, except for this (but I’m not sure if this is useful): 08.12.2022 20:35pc kwin_wayland[1584689] qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead. 08.12.2022 20:35pc kwin_wayland[1584689] This plugin does not support raise() 08.12.2022 20:35pc plasmashell[1598891]qt.qpa.wayland: Wayland does not support QWindow::requestActivate() 08.12.2022 20:36pc kscreenlocker_greet[1655244]qt.qpa.wayland: Wayland does not support QWindow::requestActivate() 08.12.2022 20:36pc kernel [122990.358834] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 08.12.2022 20:36pc kernel [122990.362833] radeon :01:00.0: WB enabled 08.12.2022 20:36pc kernel [122990.362836] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 08.12.2022 20:36pc kernel [122990.362838] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c 08.12.2022 20:36pc kernel [122990.363579] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 08.12.2022 20:36pc kernel [122990.363835] debugfs: File 'radeon_ring_gfx' in directory '0' already present! 08.12.2022 20:36pc kernel [122990.363839] debugfs: File 'radeon_ring_dma1' in directory '0' already present! 08.12.2022 20:36pc kernel [122990.379066] debugfs: File 'radeon_ring_uvd' in directory '0' already present! Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: Wayland Graphics Processor: AMD TURKS -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 452907] Kmag garbled and glitched with two monitors
https://bugs.kde.org/show_bug.cgi?id=452907 Anton Anikin changed: What|Removed |Added Assignee|sar...@users.sourceforge.ne |an...@anikin.xyz |t | -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 452907] Kmag garbled and glitched with two monitors
https://bugs.kde.org/show_bug.cgi?id=452907 Anton Anikin changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Anton Anikin --- My fix is ready for review: https://invent.kde.org/accessibility/kmag/-/merge_requests/6 -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 457416] KMag mouse-focus shift while using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=457416 Anton Anikin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||an...@anikin.xyz Status|REPORTED|RESOLVED --- Comment #2 from Anton Anikin --- *** This bug has been marked as a duplicate of bug 452907 *** -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 452907] Kmag garbled and glitched with two monitors
https://bugs.kde.org/show_bug.cgi?id=452907 --- Comment #2 from Anton Anikin --- *** Bug 457416 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 452907] Kmag garbled and glitched with two monitors
https://bugs.kde.org/show_bug.cgi?id=452907 Anton Anikin changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||an...@anikin.xyz -- 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 --- Comment #6 from Anton Skorokhod --- (In reply to Patrick Silva from comment #5) > Cannot reproduce on Arch Linux. I can set ctrl+1 and ctrl+2, for example, > and they work. > I use brazilian portuguese (abnt2) keyboard layout. It's not about ctrl+1 or ctrl+2, but about different mapping of ctrl+1 on numbers above leteters and ctrl+1 when "1" is pressed on additional numeric keyboard. On X11 it works (it's different) but on Wayland that "1" is the same on basic and additional part of keyboard :( -- 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 --- Comment #4 from Anton Skorokhod --- kde frameworks 5.99 and 5.26.2, problem still exists -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 460314] New: Not work drag and drop to Telegram (flatpack)
https://bugs.kde.org/show_bug.cgi?id=460314 Bug ID: 460314 Summary: Not work drag and drop to Telegram (flatpack) Classification: Applications Product: gwenview Version: 22.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: kvanton@yandex.ru Target Milestone: --- SUMMARY when dragging an image to telegram - only the first image is dragged, the subsequent ones are replaced by the first one Short demo: https://youtu.be/GGXxxXKsAPA STEPS TO REPRODUCE 1. Open image in gwenview 2. Drag first image to Telegram message 3. . Drag second (other) image to Telegram message OBSERVED RESULT To send, we receive by giving the same images (first) EXPECTED RESULT Get different images according to drag and drop to send to telegram SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Graphics Platform: X11 flatpak org.telegram.desktop:4.2.4 ADDITIONAL INFORMATION It used to work fine, the error appeared some time ago (maybe in the fall), I don’t know the exact version. I'm sorry, but I don't know if it's related to Gwenview or Telegram or something, but through Dolphin everything works correctly -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460237] New: Keyboard shortcuts for panning and zooming change kicker size
https://bugs.kde.org/show_bug.cgi?id=460237 Bug ID: 460237 Summary: Keyboard shortcuts for panning and zooming change kicker size Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: aarnold@antonarnold.de Target Milestone: 1.0 SUMMARY Global keyboard shortcuts for panning and zooming change kicker size if open. This is probably not wanted and cannot be reverted without editing config files. See: https://docs.kde.org/trunk5/en/khelpcenter/fundamentals/kbd.html#kbd-activity-pan-zoom STEPS TO REPRODUCE 1. Open and focus Kicker [META] 2. Pan Left Keyboard Shortcut [META + LEFT] OBSERVED RESULT Kicker size and position changes and cannot be restored unless manually editing config files EXPECTED RESULT Kicker size and position do not change or can be restored easily SOFTWARE/OS VERSIONS Linux: 5.10.146 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458740] New: Crash when opening picture from libreoffice ("edit in external tool")
https://bugs.kde.org/show_bug.cgi?id=458740
Bug ID: 458740
Summary: Crash when opening picture from libreoffice ("edit in
external tool")
Product: gwenview
Version: 22.04.1
Platform: Debian unstable
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: anton...@web.de
Target Milestone: ---
Application: gwenview (22.04.1)
Qt Version: 5.15.4
Frameworks Version: 5.97.0
Operating System: Linux 5.18.0-4-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.25.4 [KCrashBackend]
-- Information about the crash:
Libreoffice might've deleted/moved/changed the file, causing a crash. I don't
know.
Distro is Debian Sid
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Gwenview (gwenview), signal: Aborted
[KCrash Handler]
#4 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
#5 0x7f289548989f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
#6 0x7f289543da52 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#7 0x7f2895428469 in __GI_abort () at ./stdlib/abort.c:79
#8 0x7f289547dc18 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7f28955b4440 "*** %s ***: terminated\n") at
../sysdeps/posix/libc_fatal.c:155
#9 0x7f2895518c62 in __GI___fortify_fail (msg=msg@entry=0x7f28955b4428
"stack smashing detected") at ./debug/fortify_fail.c:26
#10 0x7f2895518c40 in __stack_chk_fail () at ./debug/stack_chk_fail.c:24
#11 0x7f2895ac652a in cmsCreate_sRGBProfileTHR () from
/lib/x86_64-linux-gnu/liblcms2.so.2
#12 0x7f2897bde1cd in Gwenview::Cms::Profile::getSRgbProfile() () from
/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#13 0x7f2897c09238 in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5
#14 0x7f2897c09622 in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5
#15 0x7f2897c09f3e in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5
#16 0x7f2896ea18a1 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7f2896ea20fa in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f2896ea15fb in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f2896ea20fa in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f2896ea15fb in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f2896e660e4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f2896f0ba54 in QGraphicsEffectSource::draw(QPainter*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x7f2896ea24f3 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x7f2896ea2b22 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7f2896ec699f in QGraphicsView::paintEvent(QPaintEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#26 0x7f2896ba4cb8 in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x7f2896c5019e in QFrame::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x7f2895eb139b in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f2896b62f3e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#30 0x7f2895eb1618 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7f2896b9d015 in QWidgetPrivate::sendPaintEvent(QRegion const&) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#32 0x7f2896b9d8d1 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion
const&, QPoint const&, QFlags, QPainter*,
QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#33 0x7f2896b741a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#34 0x7f2896ba4f78 in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#35 0x7f28974ebe97 in KXmlGuiWindow::event(QEvent*) () from
/lib/x86_64-linux-gnu/libKF5XmlGui.so.5
#36 0x7f2896b62f4e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#37 0x7f2895eb1618 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#38 0x7f2895eb45b1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#39 0x7f2896e94203 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#40 0x7f2895edd2a0 in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#41 0x7f2896b62f4e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /l
[kdenlive] [Bug 458623] New: Pasting multiple copies of clips doesn't work
https://bugs.kde.org/show_bug.cgi?id=458623 Bug ID: 458623 Summary: Pasting multiple copies of clips doesn't work Product: kdenlive Version: 22.08.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: findemnfi...@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. Add multiple copies of a video clip to a track. In my case, I'm trying to loop a 22 second clip to cover 90 minutes of video 2. Hold the shift key and select multiple (>5) copies of the video clip 3. Try to paste the copies into a later section of the track OBSERVED RESULT You get the error "Could not paste items in timeline" EXPECTED RESULT Paste the selected copies at the location specified SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 22.08.0 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 318357] GROUP : group by file-names [patch]
https://bugs.kde.org/show_bug.cgi?id=318357 --- Comment #35 from Christoph Anton Mitterer --- There could simply be a default regexp which groups files with any known picture extensions together, so anyone not familiar with them could just switch the option on and use the default, while anyone needing more powerful stuff could customise the regexp. -- 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 Anton Skorokhod changed: What|Removed |Added CC||an...@nsl.cz --- Comment #2 from Anton Skorokhod --- also confirming this issue on KDE Neon, Plasma 5.25.2, kde frameworks 5.95.0 with X11 session everything works, on Wayland it's impossible to use numpad as separate keys in any keyboard layout (tried US, CZ and RU) it's not "one layout issue" as I have more layouts configured in system -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417929] Crash in KFileItemModel::expandedParentsCount() while opening folders in tree view and deleting them
https://bugs.kde.org/show_bug.cgi?id=417929 Anton K changed: What|Removed |Added Version|19.04.3 |22.04.1 Platform|Ubuntu Packages |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417929] Crash in KFileItemModel::expandedParentsCount() while opening folders in tree view and deleting them
https://bugs.kde.org/show_bug.cgi?id=417929 Anton K changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417929] Crash in KFileItemModel::expandedParentsCount() while opening folders in tree view and deleting them
https://bugs.kde.org/show_bug.cgi?id=417929 --- Comment #6 from Anton K --- Created attachment 148773 --> https://bugs.kde.org/attachment.cgi?id=148773=edit New crash information added by DrKonqi dolphin (22.04.1) using Qt 5.15.3 - What I was doing when the application crashed: I was opening folders in tree view and deleting them. Crash (segmentation fault) occurred twice. The crash can be reproduced sometimes. -- Backtrace (Reduced): #4 0x7fd7219b89d3 in QHash::value (akey=..., this=0x5576d3a9c898) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:653 #5 KFileItemModel::expandedParentsCount (data=) at ./src/kitemviews/kfileitemmodel.cpp:1628 #6 0x7fd7219eab59 in KItemListView::hasSiblingSuccessor (this=this@entry=0x5576d24912f0, index=0) at ./src/kitemviews/kitemlistview.cpp:2708 #7 0x7fd7219ec7da in KItemListView::updateSiblingsInformation (this=this@entry=0x5576d24912f0, firstIndex=0, firstIndex@entry=-1, lastIndex=47, lastIndex@entry=-1) at ./src/kitemviews/kitemlistview.cpp:2692 #8 0x7fd7219f3c32 in KItemListView::slotItemsRemoved (this=0x5576d24912f0, itemRanges=...) at ./src/kitemviews/kitemlistview.cpp:1268 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417929] Crash in KFileItemModel::expandedParentsCount() while opening folders in tree view and deleting them
https://bugs.kde.org/show_bug.cgi?id=417929 Anton K changed: What|Removed |Added CC||kvanton@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 452727] New: Cannot load library kio_file.so as Qt_5.15 when running Kate from snap
https://bugs.kde.org/show_bug.cgi?id=452727 Bug ID: 452727 Summary: Cannot load library kio_file.so as Qt_5.15 when running Kate from snap Product: kate Version: 21.12.1 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: kozlovsky@gmail.com Target Milestone: --- Created attachment 148216 --> https://bugs.kde.org/attachment.cgi?id=148216=edit FS tree is empty but there are files SUMMARY When I'm starting Kate installed from snap store it produces an error in the terminal and the cursor will spin forever. FS tree won't load. STEPS TO REPRODUCE 1. Install Kate from Snap store on Kubuntu 20.04 2. Open Konsole 3. Run kate "snap run kate" OBSERVED RESULT -> % snap run kate Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. sonnet.plugins.hspell: HSpellDict::HSpellDict: Init failed could not open /snap/kate/126/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_file.so: Cannot load library /snap/kate/126/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_file.so: (/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15' not found (required by /snap/kate/126/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/kio_file.so)) Attaching screenshot EXPECTED RESULT The application is up and fully functional, no error in a terminal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.8 (available in About System) KDE Plasma Version: 5.18.8 KDE Frameworks Version: 5.68 Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Anton K changed: What|Removed |Added CC|kvanton@yandex.ru | -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 451636] New: Neochat crash (on start)
https://bugs.kde.org/show_bug.cgi?id=451636 Bug ID: 451636 Summary: Neochat crash (on start) Product: kde Version: unspecified Platform: Mandriva RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: anton...@web.de Target Milestone: --- Application: neochat (21.12) Qt Version: 5.15.3 Frameworks Version: 5.90.0 Operating System: Linux 5.16.13-desktop-1omv4003 x86_64 Windowing System: X11 Distribution: "OpenMandriva Lx 4.3" DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Just chatting with somebody - How I can reproduce the crash: Just by opening the application so that chat gets loaded The crash can be reproduced every time. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 0x7f40f8e883af in Quotient::Connection::Private::consumeToDeviceEvents(std::vector >, std::allocator > > >&&) () from /usr/lib64/libQuotient.so.0.7 #5 0x7f40f8e84b1f in Quotient::Connection::onSyncSuccess(Quotient::SyncData&&, bool) () from /usr/lib64/libQuotient.so.0.7 #6 0x7f40f8e8dc4d in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/libQuotient.so.0.7 #7 0x7f40f6c371de in void doActivate(QObject*, int, void**) () from /usr/lib64/libQt5Core.so.5 #8 0x7f40f6c42cac in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQt5Core.so.5 #9 0x7f40f8ef32c1 in Quotient::BaseJob::finishJob() () from /usr/lib64/libQuotient.so.0.7 #10 0x7f40f8ef6387 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/libQuotient.so.0.7 #11 0x7f40f6c371de in void doActivate(QObject*, int, void**) () from /usr/lib64/libQt5Core.so.5 #12 0x7f40f6c42cac in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQt5Core.so.5 #13 0x7f40f7ed1460 in QNetworkReplyHttpImplPrivate::finished() () from /usr/lib64/libQt5Network.so.5 #14 0x7f40f7f6f0c9 in QNetworkReplyHttpImpl::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libQt5Network.so.5 #15 0x7f40f6c33f8e in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib64/libQt5Core.so.5 #16 0x7f40f6c35c0f in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #17 0x7f40f7718c09 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f40f771669d in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f40f6bffefd in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x7f40f6c0077e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #21 0x7f40f6c6f322 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5Core.so.5 #22 0x7f40f60f0cb5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x7f40f60f1052 in g_main_context_iterate () from /usr/lib64/libglib-2.0.so.0 #24 0x7f40f60f111d in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x7f40f6c6f8ff in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #26 0x7f40ef314246 in QXcbGlibEventDispatcher::processEvents(QFlags) () from /usr/lib64/libQt5XcbQpa.so.5 #27 0x7f40f6bf7cc7 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #28 0x7f40f6c00311 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #29 0x7f40f6f592e6 in QGuiApplication::exec() () from /usr/lib64/libQt5Gui.so.5 #30 0x7f40f771d333 in QApplication::exec() () from /usr/lib64/libQt5Widgets.so.5 #31 0x00325794 in main () [Inferior 1 (process 7833) detached] Reported using DrKonqi This report was filed against 'kde' because the product 'neochat' 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.
[frameworks-plasma] [Bug 448391] panel popups glitches
https://bugs.kde.org/show_bug.cgi?id=448391 Anton A. changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #4 from Anton A. --- Exactly the same issue after update. Operating System: Manjaro Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.1-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-3120M CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 448687] New: wayland: can not attach windows
https://bugs.kde.org/show_bug.cgi?id=448687 Bug ID: 448687 Summary: wayland: can not attach windows Product: kdenlive Version: 21.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: vdu...@gmail.com Target Milestone: --- Created attachment 145603 --> https://bugs.kde.org/attachment.cgi?id=145603=edit reproduction of the bug SUMMARY Can not attach kdenlive windows to main window while using plasma wayland session. STEPS TO REPRODUCE 1. Unattach window 2. Try to attach it back OBSERVED RESULT Kdenline windows has default titlebar. And its not possible to attach windows back to main window. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.12-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-3120M CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION see attachment -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448391] panel popups glitches
https://bugs.kde.org/show_bug.cgi?id=448391 --- Comment #2 from Anton A. --- Created attachment 145427 --> https://bugs.kde.org/attachment.cgi?id=145427=edit reproduction -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448391] panel popups glitches
https://bugs.kde.org/show_bug.cgi?id=448391 --- Comment #1 from Anton A. --- SUMMARY When moving cursor over panel on the components that contains pop-up, instead of immediately showing pop-up, it shows 1-4 extra frames. The first contains scrollbar. And other frames is a random resize animation. STEPS TO REPRODUCE 1. Disable Desktop Effects -> Morphing popups -> Off 2. Set Animation Speed -> Instant 3. Move cursor panel components OBSERVED RESULT Animation glitches EXPECTED RESULT Single frame animation SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.12-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-3120M CPU @ 2.50GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION see attachments -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448391] New: panel popups glitches
https://bugs.kde.org/show_bug.cgi?id=448391 Bug ID: 448391 Summary: panel popups glitches Product: plasmashell Version: 5.23.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: vdu...@gmail.com Target Milestone: 1.0 SUMMARY When moving cursor over panel on the components that contains pop-up, instead of immediately showing pop-up, it shows 1-4 extra frames. The first contains scrollbar. And other frames is a random resize animation. STEPS TO REPRODUCE 1. Disable Desktop Effects -> Morphing popups 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446213] Calendar app showing "0 %2(I18N_ARGUMENT_MISSING)"
https://bugs.kde.org/show_bug.cgi?id=446213 Anton Kreuzkamp changed: What|Removed |Added CC||akreuzk...@web.de --- Comment #1 from Anton Kreuzkamp --- Try to reconfigure your time zone in systemsettings. Apparently something broke that setting. I had the same issue and found out (via plasmaengineexplorer, if you want to check it out on your system) that plasma's time-DataSource reported an empty DataTime for the "Local" time but a correct time for all time zones. So I went for the time zone dialog in systemsettings and set the time zone to the correct one and at least here the digital clock shows a correct time again and the calendar widget shows correct dates. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442355] Window Decorations Titlebar Buttons Issue in Sidebar view after KDE 5.86 upgrade
https://bugs.kde.org/show_bug.cgi?id=442355 Anton changed: What|Removed |Added CC|anton.li...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443917] Limited Minimum Window Width with extremely wide screenshot
https://bugs.kde.org/show_bug.cgi?id=443917 --- Comment #2 from Anton K --- (In reply to Antonio Prcela from comment #1) > Can you please post steps to reproduce? > Wayland or X? Probably there is no difference, but exactly on x11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443922] Telegram from the tray always opens on the monitor with a tray, and not where it was before the closure
https://bugs.kde.org/show_bug.cgi?id=443922 --- Comment #4 from Anton K --- (In reply to Vlad Zahorodnii from comment #3) > If an app uses the plasma shell protocol, kwin will think that the > corresponding window belongs to desktop shell so it will disable window > rules for it. https://i.imgur.com/k6EA8jn.png I can create rules through the settings and it seems they even work somehow. But they do not fire when you click on the tray icon. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439986] Maximized windows does not follow cursor.
https://bugs.kde.org/show_bug.cgi?id=439986 Anton K changed: What|Removed |Added Status|RESOLVED|REPORTED CC||kvanton@yandex.ru Ever confirmed|1 |0 Resolution|FIXED |--- --- Comment #7 from Anton K --- This correction could not cause this problem (https://bugs.kde.org/show_bug.cgi?id=443922)? I do not know how it was before. Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443922] Telegram from the tray always opens on the monitor with a tray, and not where it was before the closure
https://bugs.kde.org/show_bug.cgi?id=443922 --- Comment #1 from Anton K --- (In reply to Anton K from comment #0) > SOFTWARE/OS VERSIONS > Operating System: KDE neon 5.23 > KDE Plasma Version: 5.23.0 > KDE Frameworks Version: 5.87.0 > Qt Version: 5.15.3 It turns out that I can configure to configure on the settings on the screen in the window rules, but it is ignored when clicking on the icon in the tray. Maybe these are the consequences of these fixes (https://bugs.kde.org/show_bug.cgi?id=439986)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443922] Telegram from the tray always opens on the monitor with a tray, and not where it was before the closure
https://bugs.kde.org/show_bug.cgi?id=443922 Anton K changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443922] New: Telegram from the tray always opens on the monitor with a tray, and not where it was before the closure
https://bugs.kde.org/show_bug.cgi?id=443922 Bug ID: 443922 Summary: Telegram from the tray always opens on the monitor with a tray, and not where it was before the closure Product: kwin Version: 5.23.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kvanton@yandex.ru Target Milestone: --- SUMMARY Now the Telegram (flatpak or appimage) from the tray always opens on the monitor with the tray. For example, if the tray is on the left monitor, but before closing (click on the icon in the tray), the telegrams were on the screen on the right, but it still opens on the left. And I can't configure on what screen to open a Telegram - in the settings of individual windows. (only "Screen" option is ignored) It seems close bug: https://bugs.kde.org/show_bug.cgi?id=439022 I think such a problem may be not only with Telegram? But there is no such problem with the VLC. The error is relevant only on Wayland, on x11 Telegrams open at the previous place (which is expected). I do not know how it is in previous versions. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 443917] New: Limited Minimum Window Width
https://bugs.kde.org/show_bug.cgi?id=443917 Bug ID: 443917 Summary: Limited Minimum Window Width Product: Spectacle Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: kvanton@yandex.ru CC: k...@david-redondo.de Target Milestone: --- Created attachment 142542 --> https://bugs.kde.org/attachment.cgi?id=142542=edit spectacle full screen mode SUMMARY Limited minimum window width. For example, the window does not fit on the vertical screen 1920 * 1080 (i.e. the minimum width of more than 1080 pixels) even in full screen mode https://i.imgur.com/zMoRHyz.png https://i.imgur.com/Smm7FzM.jpg SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 443892] multiscreen kscreenlocker moves to one screen in a pile.
https://bugs.kde.org/show_bug.cgi?id=443892 Anton K changed: What|Removed |Added Summary|multiscreen kscreenlocker |multiscreen kscreenlocker |moves to one screen in a|moves to one screen in a |bunch. |pile. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 443892] multiscreen kscreenlocker moves to one screen in a bunch.
https://bugs.kde.org/show_bug.cgi?id=443892 Anton K changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 443892] New: multiscreen kscreenlocker moves to one screen in a bunch.
https://bugs.kde.org/show_bug.cgi?id=443892 Bug ID: 443892 Summary: multiscreen kscreenlocker moves to one screen in a bunch. Product: kscreenlocker Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: kvanton@yandex.ru CC: bhus...@gmail.com Target Milestone: --- Created attachment 142532 --> https://bugs.kde.org/attachment.cgi?id=142532=edit screenshot SUMMARY When you click on the session termination button (in multiscreen configurations) all kscreenlocker open on one screen. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Anton K changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Anton K changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||kvanton@yandex.ru Ever confirmed|0 |1 --- Comment #13 from Anton K --- It seems still relevant Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 427069] [wayland] Krunner starts on the most left screen.
https://bugs.kde.org/show_bug.cgi?id=427069 --- Comment #7 from Anton K --- (In reply to smit from comment #5) > Is this kwin bug ? > Because krunner open correctly on correct monitor (which has mouse pointer) > under swaywm Yes, it seems this is kwin, I have the same problem with the Telegram -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 427069] [wayland] Krunner starts on the most left screen.
https://bugs.kde.org/show_bug.cgi?id=427069 Anton K changed: What|Removed |Added Version|5.19.90 |5.23.0 Keywords||multiscreen CC||kvanton@yandex.ru --- Comment #6 from Anton K --- Confirmed Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442355] Window Decorations Titlebar Buttons Issue in Sidebar view after KDE 5.86 upgrade
https://bugs.kde.org/show_bug.cgi?id=442355 --- Comment #6 from Anton --- Hi, K.J. Petrie. Yes. Switching to "Icon View" fixes a problem. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442355] Window Decorations Titlebar Buttons Issue after KDE 5.86 upgrade
https://bugs.kde.org/show_bug.cgi?id=442355 Anton changed: What|Removed |Added CC||anton.li...@gmail.com --- Comment #2 from Anton --- The same on KDE neon User Edition 5.22 --- KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378694] Kicker's sub-menus are covered up by Plasma panels
https://bugs.kde.org/show_bug.cgi?id=378694 --- Comment #37 from Anton --- Created attachment 141256 --> https://bugs.kde.org/attachment.cgi?id=141256=edit plasma 5.22.4 with latte-dock -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378694] Kicker's sub-menus are covered up by Plasma panels
https://bugs.kde.org/show_bug.cgi?id=378694 --- Comment #36 from Anton --- bug still persists Operating System: Manjaro Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.6-xanmod2-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441913] New: kicker menu goes under latte-dock
https://bugs.kde.org/show_bug.cgi?id=441913 Bug ID: 441913 Summary: kicker menu goes under latte-dock Product: plasmashell Version: 5.22.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: tony.smi...@yandex.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 141248 --> https://bugs.kde.org/attachment.cgi?id=141248=edit screenshot of kicker's menu going under the dock SUMMARY kicker torn-off menu goes under latte-dock if dock has "auto-hide" and "keep above fullscreen" STEPS TO REPRODUCE 1. add simple menu plasmoid to latte dock 2. configure latte dock to hide (almost any option in dock produces bug) 3. open any list in a menu that is longer than height of a list item in a menu OBSERVED RESULT (see attachment) last items in a list are hidden behind the dock, probably because latte dock has biggest z-height possible in such configuration EXPECTED RESULT list goes over dock or list is higher than list's item in menu or lower edge of a list is inline with lower edge of menu SOFTWARE/OS VERSIONS Linux/KDE Plasma: manjaro kde (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION the only option that doesn't produce bug is "windows can cover" In that case though, dock can't be above fullscreen window -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439513] Klipper interferes with XWayland: Copying text works only every second time
https://bugs.kde.org/show_bug.cgi?id=439513 --- Comment #12 from Anton Kreuzkamp --- I don't always see a blank entry appear, but there is always exactly one blank entry floating around in my klipper history (and pasting doesn't work when it's the upper most). The stdout-output of klipper clearly indicates that more than one entry is created (probably afterwards filtered by some duplication removal). The bug only happens with the "Prevent empty clipboard" is activated (above I wrote "only when IgnoreSelection is set", that was by mistake) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439513] Klipper interferes with XWayland: Copying text works only every second time
https://bugs.kde.org/show_bug.cgi?id=439513 --- Comment #11 from Anton Kreuzkamp --- Created attachment 140498 --> https://bugs.kde.org/attachment.cgi?id=140498=edit klipperrc Here is the config of klipper. The bug happens only when IgnoreSelection is set to true. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439070] Unable to copy/paste when using Wayland
https://bugs.kde.org/show_bug.cgi?id=439070 --- Comment #12 from Anton Kreuzkamp --- After update to 5.22.3 pasting images into krita (xwayland) works fine, pasting into Chrome (91.0, XWayland) still fails. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439513] Klipper interferes with XWayland: Copying text works only every second time
https://bugs.kde.org/show_bug.cgi?id=439513 Anton Kreuzkamp changed: What|Removed |Added Version|5.22.2 |5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439070] Unable to copy/paste when using Wayland
https://bugs.kde.org/show_bug.cgi?id=439070 --- Comment #10 from Anton Kreuzkamp --- Note the related issue #439513 Copying images (and text) from Chrome (XWayland) to Dolphin (Wayland native) works when Klipper is not running but fails sometimes when Klipper is running (at least on my machine). The issue mentioned here (copy and pasting from wayland-native to Chrome/Krita) happens independently of Klipper. -- You are receiving this mail because: You are watching all bug changes.
