[digikam] [Bug 453165] Digikam crashes before starting faces detection
https://bugs.kde.org/show_bug.cgi?id=453165 --- Comment #13 from Maik Qualmann --- Gilles creates weekly snapshots here: https://files.kde.org/digikam/ @Gilles, can you please start creating a new AppImage? Maik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453159] Unable to set custom top-level icon in Service Menu
https://bugs.kde.org/show_bug.cgi?id=453159 Jayes changed: What|Removed |Added CC||pecu...@xs4all.nl --- Comment #1 from Jayes --- I can confirm this for Kubuntu 22.04, also when using the backports ppa. The menu's icon is ignored. Instead the icon for the first sub-item is shown. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 453255] Set "needs attention" state and/or raise window when showing the "confirm update?" sheet or else users can miss it
https://bugs.kde.org/show_bug.cgi?id=453255 --- Comment #2 from Paolo Zamponi --- Do you think it makes sense to add a "Don't ask me again" checkbox too in the sheet? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453369] New: Request to connect IBus InputContext to Plasma Wayland compositor
https://bugs.kde.org/show_bug.cgi?id=453369
Bug ID: 453369
Summary: Request to connect IBus InputContext to Plasma Wayland
compositor
Product: kwin
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: fujiw...@redhat.com
Target Milestone: ---
Hi, I'm a maintainer of IBus input method framework.
Wayland does not provide the input cursor position to the application clients
and IBus cannot show the candidate popup window at the cursor position.
Currently IBus is available with
%{_libdir}/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
Probably I think it would be good to implement IBus InputContext in Plasma
Wayland compositor so that compositor provides the correct cursor position to
ibus-daemon and systemsettings5 provides the IBus input method engines likes
GNOME desktop.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 452195] Apps cause screen-tearing when scrolling
https://bugs.kde.org/show_bug.cgi?id=452195 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451607] Application are not restored where they were when clicking on the systray icon
https://bugs.kde.org/show_bug.cgi?id=451607 --- Comment #10 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 453367] Can't start KMail, KContacts, KOrganizer or any app from that suite.
https://bugs.kde.org/show_bug.cgi?id=453367 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Kvantum::Style::advanceProgressbar() () at /usr/lib/x86_64-linux-gnu/qt5/plugins/styles/libkvantum.so it seems that it's a bug in this style. Please report bug on this style. (change style for fixing it) Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452753] Issues with KDE Plasma under different video cards
https://bugs.kde.org/show_bug.cgi?id=452753 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453266] Flipping the pen no longer erases
https://bugs.kde.org/show_bug.cgi?id=453266 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452258] Plasma crashes in PlasmaAppletItem::matches() when opening plasma widgets
https://bugs.kde.org/show_bug.cgi?id=452258 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 386283] KDE Neon - Can't shutdown/logout! Have to kill!
https://bugs.kde.org/show_bug.cgi?id=386283 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 449902] Brave browser's portal dialog using wrong application style (Fusion instead of Breeze)
https://bugs.kde.org/show_bug.cgi?id=449902 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #14 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452736] Plasma crashes when trying to load broken CKB-Next application that has a system tray item
https://bugs.kde.org/show_bug.cgi?id=452736 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450858] Add Configuration to Adjust Timeout
https://bugs.kde.org/show_bug.cgi?id=450858 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443449] KCM does not apply `dateDisplayFormat` key for digital clock applet specified in layout.js
https://bugs.kde.org/show_bug.cgi?id=443449 --- Comment #10 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447487] In search view, sub-categories column has inconsistent behavior
https://bugs.kde.org/show_bug.cgi?id=447487 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432059] Nvidia Wayland - Yakuake Window Position Is Wrong
https://bugs.kde.org/show_bug.cgi?id=432059 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429627] open firefox causes crash of kde plasmashell during resume after hibernate on wayland
https://bugs.kde.org/show_bug.cgi?id=429627 --- Comment #28 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432884] plasma crash after resume from hibernate
https://bugs.kde.org/show_bug.cgi?id=432884 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425521] Error al descargar tema global
https://bugs.kde.org/show_bug.cgi?id=425521 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426391] Installing of global theme crash
https://bugs.kde.org/show_bug.cgi?id=426391 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 340716] [RFE] Option to select the BSSID (AP) with the same SSID / preference 5GHz
https://bugs.kde.org/show_bug.cgi?id=340716 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453368] New: searching for PID ,or any other info other than program name, in search bar of process tab doesn't show anything.
https://bugs.kde.org/show_bug.cgi?id=453368 Bug ID: 453368 Summary: searching for PID ,or any other info other than program name, in search bar of process tab doesn't show anything. Product: plasma-systemmonitor Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: rezad1...@protonmail.ch CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- searching for PID ,or any other info other than program name, in search bar of process tab doesn't show anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453320] kwin_wayland DRM backend crashes on simpledrm again
https://bugs.kde.org/show_bug.cgi?id=453320 --- Comment #8 from bluescreenaven...@gmail.com --- Sorry about generating more so many comments at once, more investigating with Mesa, one of the only GBM variables is the backend, which the only one I have is the default gbm_dri, no NVIDIA is involved here I tried setting GALLIUM_DRIVER to softpipe instead of llvmpipe, the other GBM_ALWAYS_SOFTWARE=1, I tried that, that doesn't work as well -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 453367] New: Can't start KMail, KContacts, KOrganizer or any app from that suite.
https://bugs.kde.org/show_bug.cgi?id=453367
Bug ID: 453367
Summary: Can't start KMail, KContacts, KOrganizer or any app
from that suite.
Product: kaddressbook
Version: unspecified
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: mattias.hogfj...@outlook.com
CC: to...@kde.org
Target Milestone: ---
Application: kaddressbook (5.19.3 (21.12.3))
Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.0-28-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I just did a system update to 22.04 and thought I'd try to start one of theese
apps again and see if they had been fixed,
The crash can be reproduced every time.
-- Backtrace:
Application: KAddressBook (kaddressbook), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f3e4bf3ff3d in Kvantum::Style::advanceProgressbar() () at
/usr/lib/x86_64-linux-gnu/qt5/plugins/styles/libkvantum.so
#7 0x7f3e59d8a783 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff23ef87b0, r=0x557fc1dda000, this=0x557fc1f27ab0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8 doActivate(QObject*, int, void**) (sender=0x557fc1dd95b0,
signal_index=3, argv=0x7fff23ef87b0) at kernel/qobject.cpp:3886
#9 0x7f3e59d83a97 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f3e59ff1300
, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff23ef87b0) at kernel/qobject.cpp:3946
#10 0x7f3e59d8e7ee in QTimer::timeout(QTimer::QPrivateSignal)
(this=, _t1=...) at .moc/moc_qtimer.cpp:205
#11 0x7f3e59d8032f in QObject::event(QEvent*) (this=0x557fc1dd95b0,
e=0x7fff23ef8930) at kernel/qobject.cpp:1336
#12 0x7f3e5a842713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f3e59d52e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x557fc1dd95b0, event=0x7fff23ef8930) at
kernel/qcoreapplication.cpp:1064
#14 0x7f3e59dab3db in QTimerInfoList::activateTimers()
(this=0x557fc1984850) at kernel/qtimerinfo_unix.cpp:643
#15 0x7f3e59dabcdc in timerSourceDispatch(GSource*, GSourceFunc, gpointer)
(source=) at kernel/qeventdispatcher_glib.cpp:183
#16 0x7f3e5792dd1b in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f3e579826f8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f3e5792b3c3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f3e59dac0a8 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x557fc198a4e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#20 0x7f3e59d5174b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fff23ef8b70, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#21 0x7f3e59d59ce4 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#22 0x557fc0f274ea in main(int, char**) (argc=,
argv=) at ./src/main.cpp:90
[Inferior 1 (process 57169) detached]
Possible duplicates by query: bug 453237, bug 453092, bug 452621, bug 452453,
bug 452167.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 453366] New: HSV slider arrows don't respond to value changes made with the textboxes
https://bugs.kde.org/show_bug.cgi?id=453366 Bug ID: 453366 Summary: HSV slider arrows don't respond to value changes made with the textboxes Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- git ec92085 SUMMARY The HSV slider arrows of the Specific Color Selector docker don't respond if the user types values into the textboxes or clicks through steps. However, the actual color does change. This issue does not occur with the RGB slider. STEPS TO REPRODUCE 1. Click the rightside step (arrow) buttons on the sides of the HSV sliders, or enter values. OBSERVED RESULT Arrows under the sliders don't respond. EXPECTED RESULT The arrows should respond to the new value. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.12.12 (appimage) ADDITIONAL INFORMATION Another inconsistency I noticed is that holding the steps in the RGB slider will stop at 1 step but holding the steps in the HSV slider will keep going through steps. The latter behavior is probably preferable? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453103] Image Thumbnails Aren't Generated
https://bugs.kde.org/show_bug.cgi?id=453103 --- Comment #5 from electronicsarch...@protonmail.com --- (In reply to Nate Graham from comment #4) > If it's working now, I don't know if there's any way we can diagnose the > original problem, unfortunately. Well yeah, thanks anyways~ -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453292] KOrganizer shows wrong month form in headers
https://bugs.kde.org/show_bug.cgi?id=453292 gjditchfi...@acm.org changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from gjditchfi...@acm.org --- KOrganizer uses the "month" form in many places which may be incorrect. Could you tell me whether they should also be changed to "standalone"? * In the Month view, the first and last days of each month have a month name, but in a short form that may accidentally look correct. * In the Agenda view, the column headers likewise use the short form. * On the Recurrence tab of the incidence editor, if the event repeats yearly, the month names in the "on" pull-down menu. * If an event repeats yearly, the month names in the pop-up text that appears when you hold the cursor over the event, and in the Item Viewer (Settings > Sidebar > Show Item Viewer) when you select the event. * File > Print Preview, then choose "Print month": the month names in the "Start month" and "End month" pull-down menus, and the month names in the headers of the preview pages. * File > Print Preview, then choose "Print year": the month names in the preview pages. * File > Print Preview, then choose "Print week" and "Print as split week view": the month names in the headers of the preview pages. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 453333] KPMcore doesn't seem to work when the LBA Format of the NVME SSD's namespace is 4096bytes.
https://bugs.kde.org/show_bug.cgi?id=45 --- Comment #2 from daiaji --- (In reply to Andrius Štikonas from comment #1) > Would be nice to support this, but I don't have any hardware with LBA of > 4096, so it would be nice if somebody who has it could add this and send > merge request. Does this mean that parted has similar flaws? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430465] Add Crop option in annotation tool
https://bugs.kde.org/show_bug.cgi?id=430465 --- Comment #15 from Prajna Sariputra --- As mentioned in comment 13 kImageAnnotator 0.6.0 is needed, however that hasn't been released yet. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430465] Add Crop option in annotation tool
https://bugs.kde.org/show_bug.cgi?id=430465 Ash changed: What|Removed |Added CC||ashleysom...@gmail.com --- Comment #14 from Ash --- It appears this feature was added to the kImageAnnotator library, but I still don't see a crop feature in Spectacle. Is it not shipped yet, or is there some secret to enable it? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 453365] Breeze cursor script generates png files that are too small
https://bugs.kde.org/show_bug.cgi?id=453365 Jan Blackquill changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/breeze/commit/a907a4aa17 ||7d8c102b0c1c1fcfb28f4242fb1 ||c1e Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Jan Blackquill --- Git commit a907a4aa177d8c102b0c1c1fcfb28f4242fb1c1e by Jan Blackquill, on behalf of Chris Chris. Committed on 04/05/2022 at 00:17. Pushed by cblack into branch 'master'. Fix cursor build script generating pngs that are too small The cursor build scripts generate pngs that are too small when using Inkscape 0.92 or later due to Inkscape changing its default dpi from 90 to 96. Changed script to use width and height flags as they produce png files with correct dimensions on all Inkscape versions. M +9-9cursors/Breeze/build.sh M +9-9cursors/Breeze_Snow/build.sh https://invent.kde.org/plasma/breeze/commit/a907a4aa177d8c102b0c1c1fcfb28f4242fb1c1e -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 453365] Breeze cursor script generates png files that are too small
https://bugs.kde.org/show_bug.cgi?id=453365 --- Comment #1 from Chris --- I submitted a pull request (https://invent.kde.org/plasma/breeze/-/merge_requests/218/) to correct this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453320] kwin_wayland DRM backend crashes on simpledrm again
https://bugs.kde.org/show_bug.cgi?id=453320 --- Comment #7 from bluescreenaven...@gmail.com --- the renderer is llvmpipe. I'll explore some Mesa environment variables -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452786] WAYLAND - Secondary monitors show black screen, no wallpaper, no panels, and no windows. Only cursor.
https://bugs.kde.org/show_bug.cgi?id=452786 Ash changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Ash --- I've updated to plasma 5.24.5 from Neon unstable repo this morning, and testing again, this bug is no longer occurring for me. I'm guessing this was some kind of version mismatch issue when I last updated, and it has rectified itself now when I've updated. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453320] kwin_wayland DRM backend crashes on simpledrm again
https://bugs.kde.org/show_bug.cgi?id=453320 --- Comment #6 from bluescreenaven...@gmail.com --- That works. This is the info for simpledrm https://drmdb.emersion.fr/snapshots/bbc4de19efa5 dang, why would my gbm be missing modifier support? That comes from Mesa, correct? Maybe something is wrong in the way I built Mesa... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453233] Wayland: virt-manager doesn't hide cursor in graphical console
https://bugs.kde.org/show_bug.cgi?id=453233 jackygu...@hotmail.com changed: What|Removed |Added CC||jackygu...@hotmail.com Version|unspecified |5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453320] kwin_wayland DRM backend crashes on simpledrm again
https://bugs.kde.org/show_bug.cgi?id=453320 --- Comment #5 from Zamundaaa --- Does it work with the environment variable KWIN_DRM_USE_MODIFIERS=0 set? I suspect that simpledrm supports modifiers, but your gbm implementation does not -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 453365] New: Breeze cursor script generates png files that are too small
https://bugs.kde.org/show_bug.cgi?id=453365 Bug ID: 453365 Summary: Breeze cursor script generates png files that are too small Product: Breeze Version: master Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: chris...@purelymail.com Target Milestone: --- SUMMARY *** The cursor build scripts (breeze/cursors/Breeze/build.sh and breeze/cursors/Breeze_Snow/build.sh) generate png files that are a few pixels smaller than the ones tracked in the repo. The cursors built from the smaller png files do not line up correctly with the hotspots defined in the cursor configuration files. *** STEPS TO REPRODUCE 1. Delete the build directory in a cursor folder. 2. On a system with Inkscape >= 0.92, run build.sh to generate new cursors. 3. Check dimensions of the png files. OBSERVED RESULT The pngs in build/x1 are 30 by 30 pixels. The pngs in build/x1_5 are 45 by 45 pixels. The pngs in build/x2 are 60 by 60 pixels. EXPECTED RESULT The pngs should be 32 by 32, 48 by 48, and 64 by 64 pixels. SOFTWARE/OS VERSIONS Latest master commit of Breeze repo. Inkscape >= 0.92 ADDITIONAL INFORMATION The build script controls the png size with the -d (export-dpi) flag, Inkscape switched from 90dpi as a default to 96dpi in version 0.92 (https://inkscape.org/release/inkscape-0.92/). A couple LTS distros, like Ubuntu 14.04 and 16.04, still use Inkscape versions prior to 0.92. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453364] New: url with coma is incorrectly highlighted and opened (like cut) in web browser (after using Ctrl+left click)
https://bugs.kde.org/show_bug.cgi?id=453364 Bug ID: 453364 Summary: url with coma is incorrectly highlighted and opened (like cut) in web browser (after using Ctrl+left click) Product: konsole Version: 22.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY Below please find example of url with coma which was cut in moment of opening it in web browser (Firefox). Of course in result I got "Page not found". Of course it was also incorrectly highlighted. https://www.filmweb.pl/film/C%27mon+C%27mon-2021-850352/discussion/Wszystko%2C+czego+powinni%C5%9Bmy+si%C4%99+nauczy%C4%87,3263273 STEPS TO REPRODUCE 1. In Settings please check highlighting the urls 2. Put url with coma in text file 3. Open it / view 4. move mouse to be over given url and alternatively click into it holding Ctrl key OBSERVED RESULT url is highlighted till coma (not included) EXPECTED RESULT highlighting should include also coma and part after it SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.93 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453363] New: Latte Dock crashes on wyland when turn on external monitor: a TV connected via HDMI
https://bugs.kde.org/show_bug.cgi?id=453363 Bug ID: 453363 Summary: Latte Dock crashes on wyland when turn on external monitor: a TV connected via HDMI Product: lattedock Version: 0.10.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: cellst...@gmail.com Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.5-zen1-1-zen x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Latte Dock crashes on wyland when turn on external monitor: a TV connected via HDMI Happens every time, even when cycling TV off/on/off/on/ It does not happen in X11 - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f061763bcf7 in QtWayland::wl_output::handle_done(void*, wl_output*) () at /usr/lib/libQt5WaylandClient.so.5 #5 0x7f0616a6a536 in () at /usr/lib/libffi.so.8 #6 0x7f0616a67037 in () at /usr/lib/libffi.so.8 #7 0x7f0617e545e2 in () at /usr/lib/libwayland-client.so.0 #8 0x7f0617e54d73 in () at /usr/lib/libwayland-client.so.0 #9 0x7f0617e54f8c in wl_display_dispatch_queue_pending () at /usr/lib/libwayland-client.so.0 #10 0x7f0617619586 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/libQt5WaylandClient.so.5 #11 0x7f061877b7d6 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f061944c2c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f06187575aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7f06187580a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #15 0x7f061879f678 in () at /usr/lib/libQt5Core.so.5 #16 0x7f0616bec163 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #17 0x7f0616c429e9 in () at /usr/lib/libglib-2.0.so.0 #18 0x7f0616be96c5 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #19 0x7f06187a357a in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7f061874f88b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #21 0x7f061875afd7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #22 0x55cd781a6b46 in () #23 0x7f0617fde310 in __libc_start_call_main () at /usr/lib/libc.so.6 #24 0x7f0617fde3c1 in __libc_start_main_impl () at /usr/lib/libc.so.6 #25 0x55cd781ad99e in _start () [Inferior 1 (process 16693) detached] Possible duplicates by query: bug 438987, bug 436129. Report to https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453165] Digikam crashes before starting faces detection
https://bugs.kde.org/show_bug.cgi?id=453165 --- Comment #12 from vfr...@gmail.com --- Created attachment 148547 --> https://bugs.kde.org/attachment.cgi?id=148547=edit backtrace of my own compilation with the patch Thanks for submitting the patch. I've downloaded the code, installed all the needed libraries, compiled the code, but I must have an inadequate exiv2 library, as I am unable to start the program. Find attached the backtrace I get from gdb. Is any online build available to test the changes? Usually the appimage format runs ok on my system. I don't even know how to generate it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453070] Night Color not working on Wayland session with legacy mode
https://bugs.kde.org/show_bug.cgi?id=453070 --- Comment #13 from Behzad A --- (In reply to Nate Graham from comment #11) > That merge request fixes the issue for me. If you have the capacity to test > it out and see if it fixes the issue for you too, that would be much > appreciated. (In reply to Zamundaaa from comment #12) > Git commit b5aebc83eef72fb0d43dc82e647381e514636dd8 by Xaver Hugl. > Committed on 02/05/2022 at 15:39. > Pushed by zamundaaa into branch 'master'. > > backends/drm: fix gamma ramps with legacy > > With legacy, gamma ramps wouldn't be calculated from the color > transformation, > which made them not be applied. > > M +1-4src/backends/drm/drm_pipeline.cpp > > https://invent.kde.org/plasma/kwin/commit/ > b5aebc83eef72fb0d43dc82e647381e514636dd8 The problem solved with this commit. Thanks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453362] New: Incorrect work of the trash with symlinks on different physical disks
https://bugs.kde.org/show_bug.cgi?id=453362 Bug ID: 453362 Summary: Incorrect work of the trash with symlinks on different physical disks Product: frameworks-kio Version: 5.93.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Trash Assignee: fa...@kde.org Reporter: balykin_nik...@live.ru CC: kdelibs-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Make symlink from 1-st harddrive to 2-nd harddrive. For example: "/" is mounted on SSD. So "/home/user/" is also on ssd. HDD is mounted in "/mnt/HDD/". Folder /mnt/HDD/video have symlink in home directory: "/home/user/video". This folder is on HDD. 2. Remove some files from /home/user/video OBSERVED RESULT Files from HDD will go to the SSD trash EXPECTED RESULT files from the HDD must go to the hdd. even if there is a symlink Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × AMD Ryzen 3 PRO 2200G with Radeon Vega Graphics Memory: 13.6 ГиБ of RAM Graphics Processor: AMD Radeon Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453317] Touchpad does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=453317 --- Comment #5 from Josh L --- Extra/updated information: The 5.24.5 update hit the Arch repos today and did not fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453317] Touchpad does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=453317 --- Comment #4 from Josh L --- (In reply to Nate Graham from comment #2) > Do you have libinput installed? I do have `libinput` installed. This would also not explain why it works for two sessions and then stops working on the third log in, would it? Thank you for you help. I really appreciate it! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453361] Crash when add widget [x11]
https://bugs.kde.org/show_bug.cgi?id=453361 MrNekit changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from MrNekit --- *** This bug has been marked as a duplicate of bug 451743 *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451743] [x11] crash when starting to add widgets
https://bugs.kde.org/show_bug.cgi?id=451743 --- Comment #3 from MrNekit --- *** Bug 453361 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451743] [x11] crash when starting to add widgets
https://bugs.kde.org/show_bug.cgi?id=451743 MrNekit changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||balykin_nik...@live.ru --- Comment #2 from MrNekit --- I have the same issue! https://bugs.kde.org/show_bug.cgi?id=453361 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453361] Crash when add widget [x11]
https://bugs.kde.org/show_bug.cgi?id=453361 MrNekit changed: What|Removed |Added Summary|Crash when add widget |Crash when add widget [x11] -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453361] New: Crash when add widget
https://bugs.kde.org/show_bug.cgi?id=453361 Bug ID: 453361 Summary: Crash when add widget Product: lattedock Version: 0.10.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: balykin_nik...@live.ru Target Milestone: --- Created attachment 148546 --> https://bugs.kde.org/attachment.cgi?id=148546=edit Coredump 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. Try to add vidget in system 2. Wait for random crash SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × AMD Ryzen 3 PRO 2200G with Radeon Vega Graphics Memory: 13.6 ГиБ of RAM Graphics Processor: AMD Radeon Vega 8 Graphics (and amdgpu kernel module). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452188] While playing Apex Legends player's aim (mouse) spins and looks straight downwards.
https://bugs.kde.org/show_bug.cgi?id=452188 emozde...@protonmail.com changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453320] kwin_wayland DRM backend crashes on simpledrm again
https://bugs.kde.org/show_bug.cgi?id=453320 --- Comment #4 from bluescreenaven...@gmail.com --- That fixes the crash, but now it hangs about with a blank screen and it prints some kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Failed to create a gbm surface! kwin_wayland_drm: Checking test buffer failed for (0) kwin_wayland_drm: Failed to find a working setup for new outputs! kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented kwin_wayland_drm: Could not create gbm surface! Function not implemented -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424798] Standard double click and drag text selection to select words, triple click to select whole lines
https://bugs.kde.org/show_bug.cgi?id=424798 shenlebantongying changed: What|Removed |Added CC||shenlebantongy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453273] KScreen 2 behavior when I close my laptop lid should be configurable in the control center
https://bugs.kde.org/show_bug.cgi?id=453273 --- Comment #2 from kittenwolf --- (In reply to Nate Graham from comment #1) > Can you paste the output of `grep IgnoreLid /etc/UPower/UPower.conf`? If it > says "IgnoreLid=true", then it's an upstream bug in upower, and this may be > a duplicate of Bug 448400. That bug looks quite different from mine. I *want* closing the lid to do nothing. The poster in the bug you referenced wants closing the lid to suspend the laptop. I don't want that. Disabling KScreen 2 and setting up arandr to manage my screens solved all of my issues related to this particular problem, so this seems to me to be solidly a KScreen 2 problem, not an upstream upower problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453123] Add shortcut to focus/unfocus places (and possibly other panels)
https://bugs.kde.org/show_bug.cgi?id=453123 --- Comment #2 from tomash...@gmail.com --- (In reply to Nate Graham from comment #1) > We should fix the tab ordering issue first Is that some particular issue in particular you have in mind? One could highlight better what element is in focus right now, but the fact that you need to cycle through several elements to get to places and then to several elements back to the area where files and folders are displayed is inherent. I do not see a rationale why places should be the element that is one tab away from there instead of something else. I think the default ordering of where tab should go is spatial, no? I guess I should have added a use case. The use case it to access a place in places quickly using keyboard. Another option to achieve that would be to have the places accessible in menu, so one could hit ALT (when using the HUD) and type their name. However, given terminal has its own focus shortcut, it does not seem consistent to me not to have one (at least optionally) for other panels. Maybe another alternative would be bookmarks, but as far as I can see, they cannot be displayed visually in the places panel (and altogether seem puzzling to me:-)). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453109] Allow scrolling in the overview to switch between virtual desktops
https://bugs.kde.org/show_bug.cgi?id=453109 --- Comment #2 from Prajna Sariputra --- (In reply to Nate Graham from comment #1) > Scroll where? Over the activities bar? Or anywhere? In GNOME it's practically anywhere, although I personally wouldn't mind if it's going to be limited to just the activities bar (assuming that's referring to the virtual desktop previews at the top). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453360] New: Cannot reboot/logoff using enter key
https://bugs.kde.org/show_bug.cgi?id=453360 Bug ID: 453360 Summary: Cannot reboot/logoff using enter key Product: plasmashell Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: boe...@gmx.de CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY I tried to reboot via menu but it does not work as expected. Enter key does not work on session-buttons like sleep, hibernate, restart, shutdown. Space does work. Enter should work. STEPS TO REPRODUCE 1. open menu with SUPER KEY 2. Navigate to reboot with arrrow-keys 3. Press Enter/Return OBSERVED RESULT Button does not react. Only spacebar works. EXPECTED RESULT Enter does work on all other entries. I acutually expect it to work there, too! SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.24.5-1 on archlinux but also on Ubuntu 22.04 LTS where I found it first. (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453359] New: KDEconnect crash during edit executable commands
https://bugs.kde.org/show_bug.cgi?id=453359
Bug ID: 453359
Summary: KDEconnect crash during edit executable commands
Product: kde
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: rafalkozlowsk...@gmail.com
Target Milestone: ---
Application: kdeconnect-settings (22.04.0)
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.17.4-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.4 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
Choosed my phone. Edit "Execute commands". Instantly got error about kdeconnect
crash.
The crash can be reproduced every time.
-- Backtrace:
Application: Ustawienia KDE Connect (kdeconnect-settings), signal: Segmentation
fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f2c095dc1c9 in std::__uniq_ptr_impl >::_M_ptr (this=) at
/usr/include/c++/11/bits/unique_ptr.h:173
#7 std::unique_ptr >::get (this=) at
/usr/include/c++/11/bits/unique_ptr.h:422
#8 std::unique_ptr >::operator-> (this=)
at /usr/include/c++/11/bits/unique_ptr.h:416
#9 qGetPtrHelper > const> (ptr=...) at
/usr/include/qt5/QtCore/qglobal.h:1143
#10 KSycocaEntry::d_func (this=) at
/usr/src/debug/kservice-5.93.0-1.1.x86_64/src/sycoca/ksycocaentry.h:139
#11 KSycocaEntry::property (this=0x0, name=...) at
/usr/src/debug/kservice-5.93.0-1.1.x86_64/src/sycoca/ksycocaentry.cpp:104
#12 0x7f2bec082424 in KdeConnectPluginKcm::KdeConnectPluginKcm
(this=, parent=, args=..., componentName=...,
this=, parent=, args=..., componentName=...) at
/usr/src/debug/kdeconnect-kde-22.04.0-1.1.x86_64/kcmplugin/kdeconnectpluginkcm.cpp:26
#13 0x7f2bec28c339 in RunCommandConfig::RunCommandConfig (args=...,
parent=0x5596abddc990, this=0x5596abdfc700) at
/usr/src/debug/kdeconnect-kde-22.04.0-1.1.x86_64/plugins/runcommand/runcommand_config.cpp:29
#14 KPluginFactory::createInstance
(parentWidget=, parent=, args=...) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:875
#15 0x7f2c0afc5ce2 in KPluginFactory::create (this=0x5596abdfc590,
iface=0x7f2c0957c9a0 "KCModule",
parentWidget=0x5596abddc990, parent=0x5596abddc990, args=..., keyword=...) at
/usr/src/debug/kcoreaddons-5.93.0-1.1.x86_64/src/lib/plugin/kpluginfactory.cpp:232
#16 0x7f2c0b0a30d9 in KPluginFactory::create (args=...,
parent=0x5596abddc990, keyword=..., this=0x5596abdfc590) at
/usr/include/KF5/KCoreAddons/kpluginfactory.h:936
#17 KCModuleLoader::loadModule (metaData=..., parent=0x5596abddc990, args=...)
at /usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kcmoduleloader.cpp:98
#18 0x7f2c0b0a5cdd in KCModuleProxyPrivate::loadModule
(this=0x5596abdfbf00) at
/usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kcmoduleproxy.cpp:119
#19 0x7f2c0b0a6308 in KCModuleProxy::realModule (this=) at
/usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kcmoduleproxy.cpp:59
#20 0x7f2c0b0b90c9 in PluginDelegate::configure
(this=this@entry=0x5596ab945a50, index=...) at
/usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kpluginwidget.cpp:486
#21 0x7f2c0b0b987b in PluginDelegate::slotConfigureClicked
(this=0x5596ab945a50) at
/usr/src/debug/kcmutils-5.93.0-1.1.x86_64/src/kpluginwidget.cpp:471
#22 0x7f2c09e9d453 in QtPrivate::QSlotObjectBase::call (a=0x7ffdcb874880,
r=0x5596ab945a50, this=0x5596abdc0dd0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate (sender=0x5596abdc4bd0, signal_index=9,
argv=0x7ffdcb874880) at kernel/qobject.cpp:3886
#24 0x7f2c09e967af in QMetaObject::activate
(sender=sender@entry=0x5596abdc4bd0, m=m@entry=0x7f2c0af35180
,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffdcb874880)
at kernel/qobject.cpp:3946
#25 0x7f2c0ab090d2 in QAbstractButton::clicked
(this=this@entry=0x5596abdc4bd0, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#26 0x7f2c0ab0934a in QAbstractButtonPrivate::emitClicked
(this=0x5596abdc4c10) at widgets/qabstractbutton.cpp:415
#27 0x7f2c0ab0af10 in QAbstractButtonPrivate::click (this=0x5596abdc4c10)
at widgets/qabstractbutton.cpp:408
#28 0x7f2c0ab0b133 in QAbstractButton::mouseReleaseEvent
(this=0x5596abdc4bd0, e=0x7ffdcb874e20) at widgets/qabstractbutton.cpp:1044
#29 0x7f2c0aa57cde in QWidget::event (this=0x5596abdc4bd0,
event=0x7ffdcb874e20) at kernel/qwidget.cpp:9020
#30 0x7f2c0aa15b0f in QApplicationPrivate::notify_helper
(this=this@entry=0x5596ab67f270, receiver=receiver@entry=0x5596abdc4bd0,
e=e@entry=0x7ffdcb874e20) at kernel/qapplication.cpp:3632
#31 0x7f2c0aa1d614 in QApplication::notify (this=,
receiver=0x5596abdc4bd0, e=0x7ffdcb874e20) at kernel/qapplication.cpp:3076
#32 0x7f2c09e66b5a in QCoreApplication::notifyInternal2
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 --- Comment #12 from Ralf Habacker --- Git commit 90221ff9aecbaf4f94c621b8192ba4777ae3464d by Ralf Habacker. Committed on 03/05/2022 at 20:28. Pushed by sitter into branch 'master'. Add command line parameter '--ancestor=TAG' to logme.rb M +25 -3logme.rb https://invent.kde.org/sdk/releaseme/commit/90221ff9aecbaf4f94c621b8192ba4777ae3464d -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453216] no icon/image anymore on interface
https://bugs.kde.org/show_bug.cgi?id=453216 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #2 from Ralf Habacker --- (In reply to Ralf Habacker from comment #1) > Git commit 90221ff9aecbaf4f94c621b8192ba4777ae3464d by Ralf Habacker. Sorry for this unrelated post, I used an incorrect bug number -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453216] no icon/image anymore on interface
https://bugs.kde.org/show_bug.cgi?id=453216 --- Comment #1 from Ralf Habacker --- Git commit 90221ff9aecbaf4f94c621b8192ba4777ae3464d by Ralf Habacker. Committed on 03/05/2022 at 20:28. Pushed by sitter into branch 'master'. Add command line parameter '--ancestor=TAG' to logme.rb M +25 -3logme.rb https://invent.kde.org/sdk/releaseme/commit/90221ff9aecbaf4f94c621b8192ba4777ae3464d -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453358] New: [Feature Request/ Idea] Fingerprint reader from smartphone using KDE Connect
https://bugs.kde.org/show_bug.cgi?id=453358 Bug ID: 453358 Summary: [Feature Request/ Idea] Fingerprint reader from smartphone using KDE Connect Product: kdeconnect Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: marc_altm...@live.de Target Milestone: --- Hey guys, I hope this is the right place to share my idea. If not, please tell me. I know many users already had similar ideas (for example Bug 398931 and the duplicates), so many people want this feature. I hope now is the right time for this, because earlier no dev seriously reacted to this idea. Idea: My idea is to use the fingerprint reader of the smartphone (or other another device with supported fingerprint reader like an laptop) for authentication using KDE Connect. When you need to enter your password, KDE Connect on PC sends a request to KDE Connect on your Smartphone, KDE on Smartphone asks for authentication using fingerprint reader, if authenticated KDE Connect sends an time-based OTP to KDE Connect on PC. If it matches, KDE enters password or authenticates you. Why: PC users usually don't have a fingerprint reader and there are just a few laptops with it (and even less fingerprint readers are supported by libfprint). Always entering your password is stressful and you maybe use a shorter (and weaker) password instead. Use cases: 1. Maybe for login into your DE (this will probably not work after booting, but maybe it can be implemented when you are re-logging in after locking or suspending your session). 2. Maybe it is possible to integrate it in sudo/polkit so you don't have to always enter your password when using it. 3. Maybe it is possible to authenticate directly through KDE Connect using an API or something if other applications implement this feature. In general it is useful for programs where you need to enter your password multiple times (for example KeePassXC). I know that KeePassXC is working on supporting fingerprint sensors. However, libfprint supports just a few fingerprint sensors and just a few people even have one. Maybe KeePassXC can also implement polkit authentication or even directly the KDE Connect api. Let me here your thoughts on my idea! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448312] Tooltips may become corrupt if the hover is too quick
https://bugs.kde.org/show_bug.cgi?id=448312 Stefan Zurucker changed: What|Removed |Added Platform|Archlinux Packages |unspecified Version|5.23.5 |5.24.4 --- Comment #7 from Stefan Zurucker --- Updating, just in case somebody awesome finds the time to look into this report. The issue still occurs in Plasma 5.24.4 on X11 and AMD graphics. Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-37-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448312] Tooltips may become corrupt if the hover is too quick
https://bugs.kde.org/show_bug.cgi?id=448312 Stefan Zurucker changed: What|Removed |Added CC||s...@posteo.at --- Comment #6 from Stefan Zurucker --- Created attachment 148545 --> https://bugs.kde.org/attachment.cgi?id=148545=edit Icons-Only Task Manager tool tips flickering -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 453322] Add support for saving a discount card in the application
https://bugs.kde.org/show_bug.cgi?id=453322 --- Comment #2 from Côme Chilliet --- (In reply to Volker Krause from comment #1) > For the BahnCards we for example know when a ticket was booked with such a > card, can check if you have a suitable card stored in the app and directly > offer that for the ticket then. I'm not familiar with SNCF's discount > system, but I'd guess it's a very similar workflow there? Yes it’s the same, a passenger on a ticket is noted as having a given card, or accompanying a holder of the card. > What's in the barcodes of those discount cards, anything that would allow to > at least detect the type of the card? Do the corresponding tickets contain > any indication the card is required? I will send you an example by email -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 451975] Feature requests
https://bugs.kde.org/show_bug.cgi?id=451975 --- Comment #6 from Côme Chilliet --- (In reply to Volker Krause from comment #5) > * Calendar integration: yep, needed and wanted for sure :) Great to hear > * Storing PDF tickets: This should actually happen already, on the details > page of a train trip the context menu on the right contains a "Documents" > entry, and that should get you to a page that lists the corresponding PDF. Oh, nice. It does not work though with muPDF. I see the document list with the name of what I imported. clicking the name does nothing. Clicking the dots shows an open icon, and clicking this icon asks me with what I want to open the document. I select mupdf, and I get «Cannot open document». If I select Pdf Viewer Plus it does open the PDF. The colors are inverted but I suspect this is a feature of this application, I never use it. > * Okular integration: Talked to Albert from the Okular team, Okular > currently has no infrastructure for doing that kind of content analysis and > showing extra content somehow embedded in the document view. So this would > need some work on Okular itself first. Ok. Reading https://www.volkerkrause.eu/2020/01/18/kde-itinerary-nextcloud-hub-integration.html it says "During the Nextcloud Hackweek last week we also extend the command line tool to produce iCal output, to avoid some code duplication for the calendar integration and ensure compatibility with the KDE Itinerary app. These changes didn’t make it into the current release packages, but should become available with the next update." Were those changes merged in? If there is a command line tool to process a PDF and add it to a calendar, it would help integrating that with applications that allow calling script (I thought it was the case of Dolphin but I cannot find the option right now… but I could use open with -> and a script I suppose. Or a terminal.) -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 --- Comment #11 from Harald Sitter --- Patches welcome :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453269] Screen display offset from desktop after boot and login until resolution is changed and switched back
https://bugs.kde.org/show_bug.cgi?id=453269 --- Comment #2 from bartek...@gmail.com --- This is on X11 -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 --- Comment #10 from Ralf Habacker --- (In reply to Harald Sitter from comment #9) > Git commit c5108733b76738f481bcd40bc7641b048b954e03 by Harald Sitter. > reorder documention Thanks. In case the tag already exists, it would be helpful to have a command line parameter to specify the predecessor e.g. --ancestor= or even better if logme.rb would be able to detect this case itself. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 453357] New: Political map Kosovo/Serbia clicks
https://bugs.kde.org/show_bug.cgi?id=453357 Bug ID: 453357 Summary: Political map Kosovo/Serbia clicks Product: marble Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: uzivatel...@seznam.cz Target Milestone: --- Application: marble (2.2.20 (2.3 development version)) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-150300.59.63-default x86_64 Windowing system: X11 Distribution: "openSUSE Leap 15.3" -- Information about the crash: - What I was doing when the application crashed: I was clicking at Kosovo and Serbia in political view in hope for some details. Maybe there was some rotation also around it. -- Backtrace: Application: Marble Virtual Globe (marble), signal: Segmentation fault [KCrash Handler] #4 0x7fe2b5e56fb4 in Marble::GeoGraphicsItem::setHighlighted(bool) () from /usr/lib64/libmarblewidget-qt5.so.28 #5 0x7fe2b604139d in Marble::GeoGraphicsScene::applyHighlight(QVector const&) () from /usr/lib64/libmarblewidget-qt5.so.28 #6 0x7fe2b22e6e75 in QMetaObject::activate (sender=0x55c8833a7f50, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3804 #7 0x7fe2b5e67f66 in Marble::GeometryLayer::handleHighlight(double, double, Marble::GeoDataCoordinates::Unit) () from /usr/lib64/libmarblewidget-qt5.so.28 #8 0x7fe2b5e680db in Marble::GeometryLayer::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.106] () from /usr/lib64/libmarblewidget-qt5.so.28 #9 0x7fe2b22e6e75 in QMetaObject::activate (sender=0x55c8833317e0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3804 #10 0x7fe2b5ea6d11 in Marble::MarbleMap::highlightedPlacemarksChanged(double, double, Marble::GeoDataCoordinates::Unit) () from /usr/lib64/libmarblewidget-qt5.so.28 #11 0x7fe2b5eae98e in Marble::MarbleMap::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libmarblewidget-qt5.so.28 #12 0x7fe2b22e6e75 in QMetaObject::activate (sender=0x55c8832ea980, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3804 #13 0x7fe2b5e98fd1 in Marble::MarbleWidget::highlightedPlacemarksChanged(double, double, Marble::GeoDataCoordinates::Unit) () from /usr/lib64/libmarblewidget-qt5.so.28 #14 0x7fe2b5e9b900 in Marble::MarbleWidget::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libmarblewidget-qt5.so.28 #15 0x7fe2b22e6e75 in QMetaObject::activate (sender=0x55c88397e460, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3804 #16 0x7fe2b5ef2181 in Marble::MarbleInputHandler::mouseClickGeoPosition(double, double, Marble::GeoDataCoordinates::Unit) () from /usr/lib64/libmarblewidget-qt5.so.28 #17 0x7fe2b5ef3712 in Marble::MarbleDefaultInputHandler::lmbTimeout() () from /usr/lib64/libmarblewidget-qt5.so.28 #18 0x7fe2b22e6e75 in QMetaObject::activate (sender=sender@entry=0x55c883c68560, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe48d16f30) at kernel/qobject.cpp:3804 #19 0x7fe2b22e7587 in QMetaObject::activate (sender=sender@entry=0x55c883c68560, m=m@entry=0x7fe2b2765d20 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe48d16f30) at kernel/qobject.cpp:3657 #20 0x7fe2b22f3d97 in QTimer::timeout (this=this@entry=0x55c883c68560, _t1=...) at .moc/moc_qtimer.cpp:204 #21 0x7fe2b22f40f8 in QTimer::timerEvent (this=0x55c883c68560, e=) at kernel/qtimer.cpp:255 #22 0x7fe2b22e79db in QObject::event (this=0x55c883c68560, e=) at kernel/qobject.cpp:1283 #23 0x7fe2b313cf9c in QApplicationPrivate::notify_helper (this=this@entry=0x55c882fad1a0, receiver=receiver@entry=0x55c883c68560, e=e@entry=0x7ffe48d172a0) at kernel/qapplication.cpp:3701 #24 0x7fe2b31445b0 in QApplication::notify (this=0x7ffe48d176f0, receiver=0x55c883c68560, e=0x7ffe48d172a0) at kernel/qapplication.cpp:3447 #25 0x7fe2b22b7368 in QCoreApplication::notifyInternal2 (receiver=0x55c883c68560, event=0x7ffe48d172a0) at kernel/qcoreapplication.cpp:1088 #26 0x7fe2b2313859 in QTimerInfoList::activateTimers (this=0x55c882fb5b90) at kernel/qtimerinfo_unix.cpp:643 #27 0x7fe2b2314059 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:182 #28 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:229 #29 0x7fe2aade0624 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #30 0x7fe2aade09c0 in ?? () from /usr/lib64/libglib-2.0.so.0 #31 0x7fe2aade0a4c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #32 0x7fe2b23143ef in QEventDispatcherGlib::processEvents (this=0x55c8830a1370, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #33 0x7fe2b22b55ba in
[Elisa] [Bug 418800] Elisa does not show cover art for files with embedded album art
https://bugs.kde.org/show_bug.cgi?id=418800 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||22.08 --- Comment #28 from Nate Graham --- I believe Tranter Madi has fixed all of the cases of this with those commits! It seems to for me and my music collection, at least Testing from people who were affected would be appreciated. You'll need to build Elisa from source, or use a distro that provides git master packages, such as Neon Testing or openSUSE Krypton. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359783] Right-column-aligned desktop icons move all the way to the left when icons are added or moved
https://bugs.kde.org/show_bug.cgi?id=359783 --- Comment #76 from Patrick Silva --- Created attachment 148544 --> https://bugs.kde.org/attachment.cgi?id=148544=edit video recorded on neon unstable -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 Harald Sitter changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Latest Commit||https://invent.kde.org/sdk/ ||releaseme/commit/c5108733b7 ||6738f481bcd40bc7641b048b954 ||e03 --- Comment #9 from Harald Sitter --- Git commit c5108733b76738f481bcd40bc7641b048b954e03 by Harald Sitter. Committed on 03/05/2022 at 19:39. Pushed by sitter into branch 'master'. reorder documention lest we get confused about the order of commands (although I believe this message never was meant to communicate order) M +3-3lib/releaseme/data/release_help.txt.erb https://invent.kde.org/sdk/releaseme/commit/c5108733b76738f481bcd40bc7641b048b954e03 -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 Ralf Habacker changed: What|Removed |Added Resolution|NOT A BUG |WAITINGFORINFO --- Comment #8 from Ralf Habacker --- (In reply to Harald Sitter from comment #7) > You'd have to fetch the log before tagging. The latest tag is always assumed > to be the ancestor. https://community.kde.org/ReleasingSoftware#Creating_a_Tarball refers to run tarme.rb, which suggests the opposite order $ ./releaseme/tarme.rb --origin stable --version 8.1.1 alkimia ... Tarball Done! # Next Steps Create a maintenance branch ./branchme.rb --help Tag the release ./tagme.rb --help Create a changelog ./logme.rb --help See https://invent.kde.org/sdk/releaseme/-/blob/master/lib/releaseme/data/release_help.txt.erb -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417964] Artist and Album names are case sensitive
https://bugs.kde.org/show_bug.cgi?id=417964 Cor Blom changed: What|Removed |Added CC||corne...@solcon.nl -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 453143] Translation of update process in German confusing
https://bugs.kde.org/show_bug.cgi?id=453143 Frederik Schwarzer changed: What|Removed |Added CC||schwar...@kde.org --- Comment #1 from Frederik Schwarzer --- Thanks for reaching out. :) I agree, these two buttons are weird next to each other. I will probably use the "Auf Aktualisierungen prüfen" for the Refresh button. What about "Apply Updates"? Is that a suggestion for the original string? Here the button is labeled "Update all". For the German translation, I would like to keep the "Alle aktualisieren" for "Update all" to not go too far from the original and to not have two quite long strings there extending the button layout. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453356] New: Unable to click/activate notification from history
https://bugs.kde.org/show_bug.cgi?id=453356 Bug ID: 453356 Summary: Unable to click/activate notification from history Product: plasmashell Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: mequer...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY If you receive a notification that has some sort of action, you can click to activate it. E.g. a notification from Firefox that takes you to a webpage. But when you're too late and the notification disappears and you go to the notification history to see it, you can't click to activate it. Clicking it does nothing and there doesn't seem to be any other way to activate it. So the action/link is lost. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 453355] New: error when install themes
https://bugs.kde.org/show_bug.cgi?id=453355 Bug ID: 453355 Summary: error when install themes Product: frameworks-qqc2-desktop-style Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: andypa...@gmail.com CC: ahiems...@heimr.nl, k...@davidedmundson.co.uk, noaha...@gmail.com Target Milestone: --- Created attachment 148543 --> https://bugs.kde.org/attachment.cgi?id=148543=edit Error when installed theme 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. Go to preferences 2. Global themes 3. try to install one OBSERVED RESULT Error on install themes EXPECTED RESULT You can chose the theme and use it SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 (available in About System) KDE Plasma Version: 5.24.4 ADDITIONAL INFORMATION This error happens on Kubuntu 22.04 and Kubuntu 21.10 La instalación de /tmp/BNubxq-Nordic.tar.xz ha fallado: No se ha podido instalar la dependencia: «kns://sddmtheme.knsrc/api.kde-look.org/1366843» -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453110] folderview to linked activity files does not work
https://bugs.kde.org/show_bug.cgi?id=453110 Robby Engelmann changed: What|Removed |Added CC||robby.engelmann@r-engelmann ||.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Robby Engelmann --- same here since perhaps 2-3 weeks... Operating System: openSUSE Tumbleweed 20220502 KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: TUXEDO Product Name: TUXEDO System Version: Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 Harald Sitter changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #7 from Harald Sitter --- You'd have to fetch the log before tagging. The latest tag is always assumed to be the ancestor. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346
--- Comment #6 from Ralf Habacker ---
(In reply to Ralf Habacker from comment #5)
> (In reply to Harald Sitter from comment #3)
> > How did you run releaseme
> .$ ./releaseme/tarme.rb --origin stable --version 8.1.1 alkimia
and then
$ ./releaseme/tagme.rb --version 8.1.1
> $ cat release_data
> alkimia;8.1;b516a00ebd392abf8bd9174343d34cdd85d136d7;alkimia-8.1.1.tar.xz;
> 59f11fb7a8ef1fe79ca2e6650ac34b215386f8cc8393e4ec1e6a2ae6bc306d69
The commit id in column 3 refers to the tagged commit [1]
commit b516a00ebd392abf8bd9174343d34cdd85d136d7 (tag: v8.1.1, origin/8.1)
Author: Ralf Habacker
Date: Tue May 3 13:38:33 2022 +0200
Update version to 8.1.1
and in logme.rb there is:
def parse(rev)
ancestor = `git describe --abbrev=0 --tags`.strip
lines = `git log #{ancestor}..#{rev} --oneline --no-merges`
As `ancestor` there is returned
$ git describe --abbrev=0 --tags
v8.1.1
and the given parameter rev points to [1], which is the same commit.
I think `ancestor` needs instead to point to the previous release tag, which
would be v8.1.0 in this case.
--
You are receiving this mail because:
You are watching all bug changes.
[gwenview] [Bug 442510] I can't see avif images, kimageformat-plugins package updated to 5.86 with support for avif file
https://bugs.kde.org/show_bug.cgi?id=442510 --- Comment #7 from Eridani Rodríguez --- Not OP, but can confirm that adding qt-avif-image-plugin.xml and running update-mime-database enabled Gwenview to open avif images and Dolphin to generate thumbnails. Tested in daily driver KDE Neon with: KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 And neondocker:latest: KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 As a side note, this workaround was unneeded for Open SUSE Tumbleweed, as it properly opened avif images after installing kimageformats-5.93.0-248.3. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453081] Cant open my NAS,synology212j in Dolphin.message: file or map smb://diskstation212j.local/ doesnt exists. Installed filemanager PCManFM and this manager works effortless.
https://bugs.kde.org/show_bug.cgi?id=453081 --- Comment #2 from fransis...@gmail.com --- thanks for your help. I resolved the problem: via webdav i can connect with the NAS. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453351] Number Field Not Maintained on Transfers
https://bugs.kde.org/show_bug.cgi?id=453351 --- Comment #4 from Jesse --- Not necessarily splits (I just use those to say part of the purchase was food and another was for medication or something), but my main use case is paying bills. I can understand that a check number only applies to the checking account, but when paying credit cards online they give you a confirmation number. I use that number to show on my checking account, but also on the credit card to show the payment was successful and to dispute if they say a payment wasn't made (or late). I suppose technically that number only applies to the credit card account. No big deal, I guess I just got so used to using it that way in other systems, and seeing it on either side was easiest without switching between accounts. I would agree to mark this as "working as intended." Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 --- Comment #5 from Ralf Habacker --- (In reply to Harald Sitter from comment #3) > How did you run releaseme .$ ./releaseme/tarme.rb --origin stable --version 8.1.1 alkimia $ cat release_data alkimia;8.1;b516a00ebd392abf8bd9174343d34cdd85d136d7;alkimia-8.1.1.tar.xz;59f11fb7a8ef1fe79ca2e6650ac34b215386f8cc8393e4ec1e6a2ae6bc306d69 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453351] Number Field Not Maintained on Transfers
https://bugs.kde.org/show_bug.cgi?id=453351 --- Comment #3 from Jack --- I'm curious what type of number you use that really applies to both (or more?) splits of a transaction. If it's a valid use case, I can change this to a WISHLIST, so the request doesn't get lost. If using the memo field works OK for you, I can close as INTENTIONAL, meaning it's working as designed. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 --- Comment #4 from Harald Sitter --- tarme that is -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 453346] logme.rb does not produce any output on releasing libalkimia
https://bugs.kde.org/show_bug.cgi?id=453346 Harald Sitter changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Harald Sitter --- How did you run releaseme -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453081] Cant open my NAS,synology212j in Dolphin.message: file or map smb://diskstation212j.local/ doesnt exists. Installed filemanager PCManFM and this manager works effortless.
https://bugs.kde.org/show_bug.cgi?id=453081 Harald Sitter changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Harald Sitter --- upgrade your nas, enable smb1, or setup a helper service (https://apachelog.wordpress.com/2020/03/17/no-smb1-to-share-devices/) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 442510] I can't see avif images, kimageformat-plugins package updated to 5.86 with support for avif file
https://bugs.kde.org/show_bug.cgi?id=442510 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 453338] Theme not installing
https://bugs.kde.org/show_bug.cgi?id=453338 --- Comment #5 from Alexander Lohnau --- Thanks for the additional info! Could you please tell us which your configured locale and KDE Frameworks version is? Some time back we had issues with the KDE store server on certain locales. >One more thing I am using awesomeWm and not plasma, if that affects anyway. >From looking at the code, we are doing some authorization, copy files and write config. I do not think it makes a difference. >kf.newstuff.core: Command ' "sddmthemeinstaller -i >/tmp/ArchAbstract_Sddm.tar.gz" ' failed with code 255 Does the file exist and could you open it with ark? What might be worth a try is downloading the file from the KDE store and then calling sddmthemeinstaller manually. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359783] Right-column-aligned desktop icons move all the way to the left when icons are added or moved
https://bugs.kde.org/show_bug.cgi?id=359783 --- Comment #75 from Nate Graham --- If all of you who are using git master software can still reproduce the issue, it must be real and I'm just failing to reproduce it myself. Can one of you make a screen recording that shows a specific set of steps to reproduce it? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453081] Cant open my NAS,synology212j in Dolphin.message: file or map smb://diskstation212j.local/ doesnt exists. Installed filemanager PCManFM and this manager works effortless.
https://bugs.kde.org/show_bug.cgi?id=453081 Nate Graham changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |plasma-b...@kde.org Component|general |Samba Product|dolphin |kio-extras CC||n...@kde.org, ||sit...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 447773] Plasma crashes in Plasma::Containment::lastScreen() after switching from intel to nvidia graphics
https://bugs.kde.org/show_bug.cgi?id=447773 --- Comment #1 from Nate Graham --- *** Bug 453097 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453097] Plasma crashes after switching graphicscards (integrated intel and nvidia) when logging in
https://bugs.kde.org/show_bug.cgi?id=453097 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 447773 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453100] Icons-Only Task Manager Can Mis-Report Currently Running Applications
https://bugs.kde.org/show_bug.cgi?id=453100 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453102] Icons-Only Task Manager has a minimum width/height even when not showing anything
https://bugs.kde.org/show_bug.cgi?id=453102 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Summary|Icons-Only Task Manager |Icons-Only Task Manager has |taking up space when there |a minimum width/height even |is nothing to show |when not showing anything CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 453090] Can't connect to a Windows samba share with samba-libs 4.16
https://bugs.kde.org/show_bug.cgi?id=453090 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453107] Some applications open a separate window and then it switches back to the icon.
https://bugs.kde.org/show_bug.cgi?id=453107 Nate Graham changed: What|Removed |Added Component|general |Task Manager and Icons-Only ||Task Manager Target Milestone|--- |1.0 Resolution|--- |DOWNSTREAM Product|kde |plasmashell Version|unspecified |5.24.4 Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- This means that the application changes its window ID after launch. That's a naughty thing to do, as it breaks this behavior of the task Manager, which requires that a launcher and the window it creates will have the same window IDs from the start so that it can group them both together. You'll need to report this to the Brave developers. -- You are receiving this mail because: You are watching all bug changes.
