[kdenlive] [Bug 464439] Chinese characters are wrongly separated with spaces using speech to text
https://bugs.kde.org/show_bug.cgi?id=464439 --- Comment #2 from sunruikang2...@gmail.com --- (In reply to erjiang from comment #1) > I think i’ve noticed this too in the past. My guess is that it’s just what > vosk (the speech recognizer) outputs, but maybe we can just detect if the > language is Chinese and remove the spaces in Kdenlive. A workaround is to > edit the subtitle file in a text editor and remove the spaces. Yes, using text editor is a temporary method. But still a little bit difficult because ".srt" format maybe wrongly changed by users. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 --- Comment #7 from Maik Qualmann --- Michael, is the problem also reproducible after calling the maintenance dialog or the renaming dialog (F2)? Maik -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 468986] google contacts in kaddressbook, missing address, website, notes, etc.
https://bugs.kde.org/show_bug.cgi?id=468986 Philippe ROUBACH changed: What|Removed |Added Assignee|dvra...@kde.org |claudio.cam...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 468986] New: google contacts in kaddressbook, missing address, website, notes, etc.
https://bugs.kde.org/show_bug.cgi?id=468986 Bug ID: 468986 Summary: google contacts in kaddressbook, missing address, website, notes, etc. Classification: Frameworks and Libraries Product: libkgapi Version: 5.23.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: dvra...@kde.org Reporter: philippe.roub...@free.fr CC: kdepim-b...@kde.org Target Milestone: --- Operating System: openSUSE Tumbleweed 20230424 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 missing : address website notes anniversary partner's name photo of the contact assistant's name profession -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 468970] google contacts in kaddressbook, missing address, website, note
https://bugs.kde.org/show_bug.cgi?id=468970 Philippe ROUBACH changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from Philippe ROUBACH --- I replaced this report by another one -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 --- Comment #6 from caulier.gil...@gmail.com --- Ah yes, it's fedora, not suse. I needs a coffee... I will build the new AppImage this evening Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 --- Comment #5 from Maik Qualmann --- Hi Gilles, everything is always OK with openSUSE. ((:-)) Can you create a new AppImage so that Michael can quickly test whether the strange behavior under Fedora and Wayland is fixed with the setup dialog? Maik -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 468985] New: Crash at kde startup
https://bugs.kde.org/show_bug.cgi?id=468985 Bug ID: 468985 Summary: Crash at kde startup Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: amaury.deganse...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.23.0 (23.04.0)) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.12-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Just start kde as usual. I was doing nothing special The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x5566e4f86b23 in Akonadi::Server::Tracer::error (this=0x0, componentName=0x5566e4fd3de9 "DataStore (Database Error)", msg=...) at /usr/src/debug/akonadi-23.04.0/src/server/tracer.cpp:135 #5 0x5566e4f46fa1 in Akonadi::Server::DataStore::debugLastDbError (this=, actionDescription=) at /usr/src/debug/akonadi-23.04.0/src/server/storage/datastore.cpp:1295 #6 0x5566e4f3606a in Akonadi::Server::DataStore::open (this=0x5566e69947d0) at /usr/src/debug/akonadi-23.04.0/src/server/storage/datastore.cpp:116 #7 0x5566e4f3a3db in Akonadi::Server::DataStore::database (this=0x5566e69947d0) at /usr/src/debug/akonadi-23.04.0/src/server/storage/datastore.cpp:138 #8 0x5566e4eca8fe in Akonadi::Server::AkonadiServer::setupDatabase (this=) at /usr/src/debug/akonadi-23.04.0/src/server/akonadi.cpp:257 #9 0x5566e4ecc75d in Akonadi::Server::AkonadiServer::init (this=0x7ffc5c1419d0) at /usr/src/debug/akonadi-23.04.0/src/server/akonadi.cpp:107 #10 0x7f88ae718c50 in QObject::event (this=0x7ffc5c1419d0, e=0x5566e6991180) at kernel/qobject.cpp:1347 #11 0x7f88ae6ec94d in doNotify (event=0x5566e6991180, receiver=0x7ffc5c1419d0) at kernel/qcoreapplication.cpp:1154 #12 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1140 #13 QCoreApplication::notifyInternal2 (receiver=0x7ffc5c1419d0, event=0x5566e6991180) at kernel/qcoreapplication.cpp:1064 #14 0x7f88ae6eff71 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5566e698a620) at kernel/qcoreapplication.cpp:1821 #15 0x7f88ae746713 in postEventSourceDispatch (s=0x5566e698d6b0) at kernel/qeventdispatcher_glib.cpp:277 #16 0x7f88aca6c8d8 in g_main_dispatch (context=0x5566e698d450) at ../glib/gmain.c:3460 #17 g_main_context_dispatch (context=context@entry=0x5566e698d450) at ../glib/gmain.c:4200 #18 0x7f88aca6cce8 in g_main_context_iterate (context=context@entry=0x5566e698d450, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4276 #19 0x7f88aca6cd7c in g_main_context_iteration (context=0x5566e698d450, may_block=1) at ../glib/gmain.c:4343 #20 0x7f88ae745f26 in QEventDispatcherGlib::processEvents (this=0x5566e698c250, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f88ae6eb40b in QEventLoop::exec (this=this@entry=0x7ffc5c141840, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f88ae6f38a0 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x5566e4ec6688 in AkApplicationBase::exec (this=0x7ffc5c1419a0) at /usr/src/debug/akonadi-23.04.0/src/shared/akapplication.cpp:107 #24 main (argc=, argv=) at /usr/src/debug/akonadi-23.04.0/src/server/main.cpp:65 [Inferior 1 (process 2760) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 468984] New: Video file name including emoji does not work
https://bugs.kde.org/show_bug.cgi?id=468984 Bug ID: 468984 Summary: Video file name including emoji does not work Classification: Applications Product: Haruna Version: 0.10.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: zorina...@protonmail.com Target Milestone: --- SUMMARY *** Hi, When i try to open video file including emoji character, the file does not work. Examples: 001 ▶️ File 1 002 ⚙️ File 2 P.S: I open these files using VLC and it worked. Thanks, *** STEPS TO REPRODUCE 1. Rename any video file like example above OBSERVED RESULT The video file does not played EXPECTED RESULT I hope these files work on haruna. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468983] Kdenlive 23.04.0 doesn't detect my 1050Ti GPU for the Whisper A.I. Speech to Text on Windows 11.
https://bugs.kde.org/show_bug.cgi?id=468983 --- Comment #1 from rjs205 --- Created attachment 158432 --> https://bugs.kde.org/attachment.cgi?id=158432&action=edit A screenshot of Kdenlive's configure tab on the whisper page. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468983] New: Kdenlive 23.04.0 doesn't detect my 1050Ti GPU for the Whisper A.I. Speech to Text on Windows 11.
https://bugs.kde.org/show_bug.cgi?id=468983 Bug ID: 468983 Summary: Kdenlive 23.04.0 doesn't detect my 1050Ti GPU for the Whisper A.I. Speech to Text on Windows 11. Classification: Applications Product: kdenlive Version: 23.04.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: j...@kdenlive.org Reporter: robjamesp...@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. On Windows 11, go to Kdenlive's configure windows and select speech to text. 2. Then select Whisper 3. On Whisper, The "Device" dropdown should be stuck to "Probing". Normally your GPU would appear here. OBSERVED RESULT It should be stuck to probing. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 11 Home macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION My Graphics Card drivers are 531.41 Game Ready Drivers from NVIDIA. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468962] Clip on timeline changes identity/name, gets exchanged random
https://bugs.kde.org/show_bug.cgi?id=468962 Julius Künzel changed: What|Removed |Added Ever confirmed|0 |1 CC||jk.kde...@smartlab.uber.spa ||ce Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 468970] google contacts in kaddressbook, missing address, website, note
https://bugs.kde.org/show_bug.cgi?id=468970 --- Comment #4 from Philippe ROUBACH --- missing assistant's name, profession -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468212] Clicking an Artist's name when viewing an Album should add to the ContentView's history
https://bugs.kde.org/show_bug.cgi?id=468212 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/multimedia/elisa/-/merge_requests/452 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 --- Comment #4 from Maik Qualmann --- Git commit f275e7cdfb5cef02528be5692c549789cb6aeb0c by Maik Qualmann. Committed on 26/04/2023 at 06:09. Pushed by mqualmann into branch 'master'. try with application parent for the setup dialog M +14 -14 core/utilities/setup/setup.cpp https://invent.kde.org/graphics/digikam/commit/f275e7cdfb5cef02528be5692c549789cb6aeb0c -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468798] Digikam not starting after upgrade to 8.0
https://bugs.kde.org/show_bug.cgi?id=468798 --- Comment #4 from Dominique Lebrun --- I confirm that the last update fixed the problem. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Portability-Runtime -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- Hi, yes Maik is right, it's a Suse* bug. Here with Kubuntu and Wayland, there is no problem to render the application on screen. Please report this problem a DOWNSTREAM bug to Suse bugzilla. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 468970] google contacts in kaddressbook, missing address, website, note
https://bugs.kde.org/show_bug.cgi?id=468970 Philippe ROUBACH changed: What|Removed |Added Platform|Other |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 468970] google contacts in kaddressbook, missing address, website, note
https://bugs.kde.org/show_bug.cgi?id=468970 --- Comment #3 from Philippe ROUBACH --- missing photo of the contact -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- This is a bug that we probably won't be able to fix. It's a problem between Qt and Wayland. Here on openSUSE (I use X11 by default) when I start a native Wayland session I can't reproduce the problem. Maik -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 468970] google contacts in kaddressbook, missing address, website, note
https://bugs.kde.org/show_bug.cgi?id=468970 --- Comment #2 from Philippe ROUBACH --- missing anniversary, partner's name -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Version|5.27.3 |5.27.4 --- Comment #16 from Raman Gupta --- Still an issue on 5.27.4. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization
https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #8 from Igor Kushnir --- (In reply to Alessandro Carinelli from comment #5) > I had an idea: after we get trimmedText we move backwards starting from the > character right before the '.' checking every character until we find > something different from a letter (upper or lowercase), an underscore or a > digit, in this way we should find the first character in the identifier or > literal that precedes the '.', if such first character is a digit we know > that we are dealing with a floating point literal and skip the substitution. > I tried it and it seems to work without noticeable performance issues. This proposed workaround is too narrow for my liking. What if the user types a name of a constant of a built-in type instead of an integer literal? But I guess if there is no more general fix that is acceptable, this workaround might do. -- You are receiving this mail because: You are watching all bug changes.
[docs.kde.org] [Bug 468982] New: Enable Arabic
https://bugs.kde.org/show_bug.cgi?id=468982 Bug ID: 468982 Summary: Enable Arabic Classification: Websites Product: docs.kde.org Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: docs.kde.org Assignee: kde-doc-engl...@kde.org Reporter: zayed.alsa...@gmail.com Target Milestone: --- Please enable Arabic support in https://docs.kde.org/ . Currently, Kturtule's Handbook is fully translated to Arabic. Please also, add the right RTL support in the CSS. After enabling Arabic, I can report any issue in the standard-rtl.css . I what I can see, it lacks direction:rtl; in the body{}. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization
https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #7 from Igor Kushnir --- When I apply the attached patch, I get the following output while reproducing the bug: RESULTS: 1 ; kind: OverloadCandidate kind: 2 chunk text: "Test" kind: 10 chunk text: "{" kind: 3 chunk text: "int a" kind: 14 chunk text: ", " kind: 5 chunk text: "float b" kind: 11 chunk text: "}" I don't quite understand what's the meaning and purpose of this completion. Someone will have to investigate this further and maybe experiment/test whether this completion cursor kind is ever useful. If not, KDevelop could also return early from ClangCodeCompletionContext() when there is a single completion result after the tentative arrow and its cursor kind is OverloadCandidate. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization
https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #6 from Igor Kushnir --- Created attachment 158431 --> https://bugs.kde.org/attachment.cgi?id=158431&action=edit Patch to print completion info and assist in investigation -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 468981] New: KOrganizer crashes after adding new recurring yearly event (into Google Calendar) and clicking apply
https://bugs.kde.org/show_bug.cgi?id=468981 Bug ID: 468981 Summary: KOrganizer crashes after adding new recurring yearly event (into Google Calendar) and clicking apply Classification: Applications Product: korganizer Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: damik...@gmail.com Target Milestone: --- Application: korganizer (5.22.3 (22.12.3)) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.2.11-300.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: # Bug summary: KOrganizer crashes after adding new recurring yearly event (into Google Calendar backend) and clicking apply. # Reproduction steps: 1. Add new recurring yearly event by right-clicking the day in Monthly View and selecting Add Event 2. Only title, no location; in the Repeat tab repeat set to every year starting from 26th of April 2023. 3. Click on Apply. 4. 5. Bug appearance rate: Tried only once for now, I will try to reproduce further later. # System info: Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.11-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-2520M CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 3000 Manufacturer: Hewlett-Packard Product Name: HP EliteBook 8460p System Version: A0001D02 # Additional information: gdb backtrace included (I hope, using dr. konqi). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 0x7f3df128b759 in QSortFilterProxyModelPrivate::proxy_to_source(QModelIndex const&) const () from /lib64/libQt5Core.so.5 #5 0x7f3df128d6f5 in QSortFilterProxyModelPrivate::store_persistent_indexes() const () from /lib64/libQt5Core.so.5 #6 0x7f3df128f9cb in QSortFilterProxyModelPrivate::_q_sourceLayoutAboutToBeChanged(QList const&, QAbstractItemModel::LayoutChangeHint) () from /lib64/libQt5Core.so.5 #7 0x7f3df12e87d8 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f3df1262247 in QAbstractItemModel::layoutAboutToBeChanged(QList const&, QAbstractItemModel::LayoutChangeHint) () from /lib64/libQt5Core.so.5 #9 0x7f3df1ce3c44 in IncidenceEditorNG::IncidenceAttendee::load(QSharedPointer const&) () from /lib64/libKF5IncidenceEditor.so.5 #10 0x7f3df1cd3e0e in IncidenceEditorNG::CombinedIncidenceEditor::load(QSharedPointer const&) () from /lib64/libKF5IncidenceEditor.so.5 #11 0x7f3df1d3174b in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] () from /lib64/libKF5IncidenceEditor.so.5 #12 0x7f3df12e8651 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7f3df1cd78ae in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libKF5IncidenceEditor.so.5 #14 0x7f3df12e8651 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f3df26f8f06 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #16 0x7f3df26feaeb in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #17 0x7f3df12df73b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f3df1faeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f3df12b3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f3df12b71f5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #21 0x7f3df1306e2f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #22 0x7f3deeb11f58 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7f3deeb71cd8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #24 0x7f3deeb13233 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x7f3df1306919 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #26 0x7f3df12b270b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f3df12ba99b in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #28 0x55a798fad1dc in main () [Inferior 1 (process 26254) detached] The reporter indicates this bug may be a duplicate of or related to bug 465625. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 433619] Images which are referenced using relative routes are not seen
https://bugs.kde.org/show_bug.cgi?id=433619 Kåre Särs changed: What|Removed |Added Resolution|--- |UPSTREAM CC||kare.s...@iki.fi Status|REOPENED|RESOLVED --- Comment #5 from Kåre Särs --- Hi, The Okular part does not seem to like the relative path or something. Please install markdownpart (sudo apt install markdownpart) and either remove the Okular markdown backend or move it down the list in file associations in System Settings. The markdown part works nicer with Kate as it has much less keyboard shortcuts that might conflict. If you want to continue using the Okular kpart, you need to file this bug to Okular. I hope this helps -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 402680] akonadiserver do not start
https://bugs.kde.org/show_bug.cgi?id=402680 Alexandr Zamaraev (aka Tonal) changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #5 from Alexandr Zamaraev (aka Tonal) --- $ akonadictl --version akonadictl 5.23.0 (23.04.0) $ akonadictl start org.kde.pim.akonadictl: Starting Akonadi Server... org.kde.pim.akonadictl:done. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadiserver: Starting up the Akonadi Server... org.kde.pim.akonadiserver: Running DB initializer tonal@hius2:~/lang/projects/promsoft/epool$ org.kde.pim.akonadiserver: DB initializer done Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadiserver: Unable to connect to dbus service: "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.145\" (uid=1000 pid=413638 comm=\"/usr/bin/akonadiserver \" label=\"/usr/bin/akonadiserver (enforce)\") interface=\"org.freedesktop.DBus\" member=\"RequestName\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.DBus\" (bus)" org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited normally... Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-41-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 31.2 ГиБ of RAM Graphics Processor: NVIDIA GeForce 940MX/PCIe/SSE2 Manufacturer: Acer Product Name: TravelMate P259-MG System Version: V1.51 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461620] fcitx5-frontend-qt5 broken again in Kde neon
https://bugs.kde.org/show_bug.cgi?id=461620 Jumpei Ogawa changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #7 from Jumpei Ogawa --- Thanks, I will check it later! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392008] Inconsistent behavior of "People" Tag
https://bugs.kde.org/show_bug.cgi?id=392008 caulier.gil...@gmail.com changed: What|Removed |Added Version|7.0.0 |8.1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468952] plasmashell crashes after logging in and reconnecting display
https://bugs.kde.org/show_bug.cgi?id=468952 --- Comment #2 from Waqar Ahmed --- Unfortunately, even with debuginfo installed the symbols for those two are not found #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7ff7c6ea0953 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7ff7c6e51ea8 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7ff7c976a37c in KCrash::defaultCrashHandler(int) () at /usr/lib/libKF5Crash.so.5 #4 0x7ff7c6e51f50 in () at /usr/lib/libc.so.6 #5 0x7ff7c924a8b9 in QQuickWindowPrivate::queryPointerEventInstance(QQuickPointerDevice*, QEvent::Type) const () at /usr/lib/libQt5Quick.so.5 #6 0x7ff7c924ad14 in QQuickWindow::mouseGrabberItem() const () at /usr/lib/libQt5Quick.so.5 #7 0x7ff7c924e92f in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) () at /usr/lib/libQt5Quick.so.5 #8 0x7ff7c92319c5 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #9 0x7ff7c92319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #10 0x7ff7c92319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #11 0x7ff7c92319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #12 0x7ff7c92319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #13 0x7ff7c92319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #14 0x7ff7c92319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #15 0x7ff7c92319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #16 0x7ff7c92319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () at /usr/lib/libQt5Quick.so.5 #17 0x7ff7c9231b39 in QQuickItemPrivate::setVisible(bool) () at /usr/lib/libQt5Quick.so.5 #18 0x7ff7c923fd43 in QQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libQt5Quick.so.5 #19 0x7ff7c9b899ba in PlasmaQuick::AppletQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libKF5PlasmaQuick.so.5 #20 0x7ff7bbfddb3a in () at /usr/lib/qt/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #21 0x7ff7bbfecb39 in () at /usr/lib/qt/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #22 0x7ff7c8c3c823 in () at /usr/lib/libQt5Qml.so.5 #23 0x7ff7c8b752f2 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #24 0x7ff7c8b75876 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #25 0x7ff7c8b759d7 in QV4::QObjectWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt5Qml.so.5 #26 0x7ff7c8b23a75 in QV4::Lookup::setterFallback(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value&, QV4::Value const&) () at /usr/lib/libQt5Qml.so.5 #27 0x7ff7c8b8eaff in () at /usr/lib/libQt5Qml.so.5 #28 0x7ff7c8b94804 in () at /usr/lib/libQt5Qml.so.5 #29 0x7ff7c8b36c36 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 #30 0x7ff7c8c971ad in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 #31 0x7ff7c8c537f1 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 #32 0x7ff7c8c5476c in () at /usr/lib/libQt5Qml.so.5 #33 0x7ff7c8c7647f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #34 0x7ff7c76be740 in () at /usr/lib/libQt5Core.so.5 #35 0x7ff7c8c31fcb in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib/libQt5Qml.so.5 #36 0x7ff7c769ea0c in QMetaProperty::write(QObject*, QVariant const&) const () at /usr/lib/libQt5Core.so.5 #37 0x7ff7c76baf52 in QObject::setProperty(char const*, QVariant const&) () at /usr/lib/libQt5Core.so.5 #38 0x7ff7c9b981af in () at /usr/lib/libKF5PlasmaQuick.so.5 #39 0x557a0c0814b4 in ShellCorona::createWaitingPanels() (this=) at /usr/src/debug/plasma-workspace/plasma-workspace-5.27.4.1/shell/shellcorona.cpp:1488 #40 0x7ff7c76bea71 in () at /usr/lib/libQt5Core.so.5 #41 0x7ff7c76c0fcf in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 --Type for more, q to quit, c to continue without paging-- #42 0x7ff7c76b1b56 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #43 0x7ff7c8378b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #44 0x7ff7c768df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr
[kate] [Bug 463524] Markdown Syntax Highlighting - Dividing Line (underscore)
https://bugs.kde.org/show_bug.cgi?id=463524 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.
[plasmashell] [Bug 456670] Both my desktops configurations are appearing on the same monitor
https://bugs.kde.org/show_bug.cgi?id=456670 --- 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.
[KPipeWire] [Bug 468384] Plasma crashes in PipeWireSourceStream::createStream() during interaction after reboot
https://bugs.kde.org/show_bug.cgi?id=468384 --- 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.
[plasmashell] [Bug 435747] Truncated panel button tooltip
https://bugs.kde.org/show_bug.cgi?id=435747 --- 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.
[plasmashell] [Bug 446591] Workspace icons rearrange at display reconnect
https://bugs.kde.org/show_bug.cgi?id=446591 --- 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.
[kwin] [Bug 453482] Plasma Wayland won't wake up from sleep
https://bugs.kde.org/show_bug.cgi?id=453482 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 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 466711] crash when creating 2 concurrent folders/files
https://bugs.kde.org/show_bug.cgi?id=466711 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 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 459715] Wallpaper disappears and only black background shown when external display connected (wayland)
https://bugs.kde.org/show_bug.cgi?id=459715 --- Comment #12 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 466727] Plasmashell doesn't start properly under Wayland.
https://bugs.kde.org/show_bug.cgi?id=466727 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 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.
[krita] [Bug 468023] Krita Version: 5.1.5 Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CP
https://bugs.kde.org/show_bug.cgi?id=468023 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 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.
[NeoChat] [Bug 468370] NeoChat crashes every time I start it.
https://bugs.kde.org/show_bug.cgi?id=468370 --- 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.
[kwin] [Bug 453668] Windows moved and window sizes are squashed when unplugging/replugging screen with differing resolution from the primary one
https://bugs.kde.org/show_bug.cgi?id=453668 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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 468380] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=468380 --- 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 467405] Desktop Icons that were arranged in a custom order become alphabetically sorted automatically after a period of time
https://bugs.kde.org/show_bug.cgi?id=467405 --- Comment #18 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 456500] KWin_Wayland crashes in KWin::DrmBackend::createDmaBufTexture() due to pipewire
https://bugs.kde.org/show_bug.cgi?id=456500 --- 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.
[plasmashell] [Bug 433867] Icons on secondary screen move around on boot / wake. Possibly because of screen rotation
https://bugs.kde.org/show_bug.cgi?id=433867 --- Comment #7 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 400432] 2 LCD - on primary screen maximazed windows is covered by Task Manager
https://bugs.kde.org/show_bug.cgi?id=400432 --- 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.
[neon] [Bug 405229] Failed to start Remove kde-frameworks-5 snap if it is unused
https://bugs.kde.org/show_bug.cgi?id=405229 --- 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.
[plasmashell] [Bug 391531] No containment shown on given screen in overlapping setup
https://bugs.kde.org/show_bug.cgi?id=391531 --- Comment #24 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.
[Discover] [Bug 461385] When trying to install an update including packages that want to prompt the user to agree to a EULA, the update fails silently
https://bugs.kde.org/show_bug.cgi?id=461385 --- Comment #40 from jonzn4SUSE --- Created attachment 158430 --> https://bugs.kde.org/attachment.cgi?id=158430&action=edit pkmon output 25APR23 Today there are 22 more updates and the refresh is happening again. I'll attach logs and another video showing the issue. https://youtu.be/SJjdb6iY_Ng -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 461385] When trying to install an update including packages that want to prompt the user to agree to a EULA, the update fails silently
https://bugs.kde.org/show_bug.cgi?id=461385 --- Comment #39 from jonzn4SUSE --- Operating System: openSUSE Tumbleweed 20230420 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1535M v6 @ 3.10GHz Memory: 62.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P630 Manufacturer: HP Product Name: HP ZBook 17 G4 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 461385] When trying to install an update including packages that want to prompt the user to agree to a EULA, the update fails silently
https://bugs.kde.org/show_bug.cgi?id=461385 --- Comment #38 from jonzn4SUSE --- There is only the root password prompt 2 times, 1st prompt for the system and the 2nd prompt is for EULA. Here is a screen recording showing the issue. It did work the second time I hit update all, but there was no prompt for passwords. https://youtu.be/cEKkgEVN9Cc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446055] System tray moves itself to the left of the global menu when plasma starts
https://bugs.kde.org/show_bug.cgi?id=446055 Sawyer changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Sawyer --- (In reply to Nate Graham from comment #1) > Is this still happening in Plasma 5.27.4 or later? Hello Nate, Sorry about not getting back to you earlier. I did not revive a email message that you responded earlier until the janitor service sent a reminder. Anyways as of plasma 5.27.4 this is no longer happening, as now no matter what I do when I try to shift the system tray to the right, it would always automatically change itself to the left upon trying it to move it to the right. I noticed I can get around this limitation if I add a spacer between the global menu and the system tray, so I was able to find a work around -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 JojoR changed: What|Removed |Added CC||rjie...@gmail.com --- Comment #88 from JojoR --- Excellent work, it's a long time :) Is there any schedule for upstreaming about this feature ? these patches looks like a prototype implementation ? I opened another thread about RISC-V vector, some issues should be common in VEX or plugin Memcheck, even more vector ISA generator :) Any suggestions for these ? @Tanya @Julian Seward BTW, is there anyone interested in ARM's SVE or RISC-V vector ? See more details from https://bugs.kde.org/show_bug.cgi?id=468979 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 michael2macdon...@gmail.com changed: What|Removed |Added CC||michael2macdon...@gmail.com --- Comment #1 from michael2macdon...@gmail.com --- Created attachment 158429 --> https://bugs.kde.org/attachment.cgi?id=158429&action=edit "Filters" sidebar menu is still showing items from "Tools" sidebar menu Here is another screenshot of the "Filters" sidebar menu still showing items from "Tools" sidebar menu -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] New: Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 Bug ID: 468980 Summary: Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM) Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: michael2macdon...@gmail.com Target Milestone: --- Created attachment 158428 --> https://bugs.kde.org/attachment.cgi?id=158428&action=edit Glitchy/Broken image thumbnails view SUMMARY After opening Flatpack or AppImage Digikam/Showfoto or RPM Showfoto on Fedora, the applications work fine. But after you open the configuration/settings window and then exit the window, the Digikam/ShowPhoto interface becomes buggy/glitchy/laggy. For example, when opening/closing a menu or scrolling on a menu or main image area, the interface will not update until you hover over each individual image or menu item. After hovering your mouse over an item, it will partially "render", but leave parts of the previous image/view still showing. STEPS TO REPRODUCE 1. On Fedora, open the Flatpack or AppImage version of Digikam or Showfoto, or open the RPM version of ShowFoto 2. Use Digikam/ShowFoto (It works fine) 3. Open the settings/configuration page of Digikam/ShowFoto 4. Close the settings/configuration page of Digikam/ShowFoto 5. Use Digikam/ShowFoto (It does not work; the interface is buggy and laggy) OBSERVED RESULT When scrolling or opening sidebars/windows/views/etc, the displayed view on the screen is not changed until you hover your mouse over a selectable item such as an image thumbnail or sidebar/menu item. Once you hover over an item, that item, and that item only, will only partially render/display leaving gaps and floating text/segments from the previously displayed item (before you scrolled). EXPECTED RESULT Digikam/ShowFoto Works Normally SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This was an issue in previous versions of Fedora and Digikam. It does not seem to be new. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468023] Krita Version: 5.1.5 Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CP
https://bugs.kde.org/show_bug.cgi?id=468023 --- Comment #3 from resh501...@gmail.com --- The bug is a forceful exist when an archive is open or generated on Krita. This being the done as the only operation that is causing this problem. And this is persistent for all openings of archives from the computer or a new one to use the program. And it only happens when the option of open is press. It forces the program to close, that would be the main problem of the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 463687] No details shown in Applications tab for Firefox
https://bugs.kde.org/show_bug.cgi?id=463687 Justin Zobel changed: What|Removed |Added Version|master |5.27.4 --- Comment #7 from Justin Zobel --- Can confirm still on Fedora Kinoite 38 (system monitor installed into the image by default) with 5.27.4. status: ``` Name: Web Content Umask: 0022 State: S (sleeping) Tgid: 2834221 Ngid: 0 Pid:2834221 PPid: 655637 TracerPid: 0 Uid:1000100010001000 Gid:1000100010001000 FDSize: 1024 Groups: 10 1000 NStgid: 2834221 NSpid: 2834221 NSpgid: 497652 NSsid: 97053 VmPeak: 2631200 kB VmSize: 2630968 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 77568 kB VmRSS: 77568 kB RssAnon: 12160 kB RssFile: 64512 kB RssShmem:896 kB VmData:38368 kB VmStk: 132 kB VmExe: 524 kB VmLib:127064 kB VmPTE: 496 kB VmSwap:0 kB HugetlbPages: 0 kB CoreDumping:0 THP_enabled:1 Threads:20 SigQ: 0/127696 SigPnd: ShdPnd: SigBlk: SigIgn: 00011002 SigCgt: 000f408004c8 CapInh: CapPrm: CapEff: CapBnd: 01ff CapAmb: NoNewPrivs: 1 Seccomp:2 Seccomp_filters:1 Speculation_Store_Bypass: thread vulnerable SpeculationIndirectBranch: conditional enabled Cpus_allowed: fff Cpus_allowed_list: 0-11 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches:33 nonvoluntary_ctxt_switches: 13 ``` stat ``` 2834268 (Web Content) S 655637 497652 97053 34825 497652 4194560 4523 0 0 0 4 11 0 0 20 0 20 0 74247324 2694111232 19584 18446744073709551615 94104109252608 94104109787229 140728579931744 0 0 0 0 69634 1082131656 0 0 0 17 3 0 0 0 0 0 94104109910720 94104109916280 94104141377536 140728579936874 140728579937112 140728579937112 140728579940317 0 ``` statm ``` 657742 19392 16320 131 0 9625 0 ``` -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 468979] New: Add support for RISC-V vector instructions
https://bugs.kde.org/show_bug.cgi?id=468979 Bug ID: 468979 Summary: Add support for RISC-V vector instructions Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: rjie...@gmail.com Target Milestone: --- We consider to add RVV/Vector [1] feature in valgrind, there are some challenges. RVV like ARM's SVE [2] programming model, it's scalable/VLA, that means the vector length is agnostic. ARM's SVE is not supported in valgrind :( See more details from RFC [3] [1] https://github.com/riscv/riscv-v-spec [2] https://community.arm.com/arm-research/b/articles/posts/the-arm-scalable-vector-extension-sve [3] https://sourceforge.net/p/valgrind/mailman/valgrind-developers/thread/84b7a55c-1868-ca14-2626-ffb88925741a%40linux.alibaba.com/#msg37834524 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468978] New: Creating tag does not work
https://bugs.kde.org/show_bug.cgi?id=468978 Bug ID: 468978 Summary: Creating tag does not work Classification: Applications Product: dolphin Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mashkal2...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Created tags don't appear STEPS TO REPRODUCE 1. Right click file 2. Click assign tags > create new. This opens the new tag dialog. 3. Enter name, click OK 4. Right click same file, hover assign tags OBSERVED RESULT created tag does not appear EXPECTED RESULT created tag appears SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-40-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Also, file is not tagged until the view is refreshed (F5) -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 348502] Own nick highlight notifications/sound not working
https://bugs.kde.org/show_bug.cgi?id=348502 Justin Zobel changed: What|Removed |Added Version|1.7.5 |1.9.230390 CC||justin.zo...@gmail.com Status|REOPENED|CONFIRMED --- Comment #3 from Justin Zobel --- Happening on 23.04.0 flatpak and in Fedora, downstream bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=1950269 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 468977] New: Extra large icon in sidebar with specifically crafted message
https://bugs.kde.org/show_bug.cgi?id=468977 Bug ID: 468977 Summary: Extra large icon in sidebar with specifically crafted message Classification: Applications Product: NeoChat Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: justin.zo...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 158427 --> https://bugs.kde.org/attachment.cgi?id=158427&action=edit Screenshot Message content { "content": { "body": "Today’s post on Akademy’s channels about e-banners \"\" Are you coming to #Akademy2023? Show your excitement by using one of our e-Banners on your social media, blog, or website! https://akademy.kde.org/2023/e-banners/\nAnd if you haven't registered yet, what are you waiting for? Sign up today! https://akademy.kde.org/2023/register/ \"\"", "format": "org.matrix.custom.html", "formatted_body": "Today’s post on Akademy’s channels about e-banners "" Are you coming to #Akademy2023? Show your excitement by using one of our e-Banners on your social media, blog, or website! https://akademy.kde.org/2023/e-banners/\nAnd if you haven't registered yet, what are you waiting for? Sign up today! https://akademy.kde.org/2023/register/ """, "msgtype": "m.text" }, "event_id": "$fcXDV3YHYmtkRKoUglXIrRKrlperpkXDAn_3LsCYO58", "origin_server_ts": 1682423825043, "sender": "@aniqakhokhar:kde.org", "type": "m.room.message", "unsigned": { "m.relations": { "m.replace": "$DkEl81Ozad9KxR_vf5gzkCHDHeg7fw5PtGqAEN8xD8c" } } } -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468810] Tooltips sometimes fail to display when hovering mouse over their icons
https://bugs.kde.org/show_bug.cgi?id=468810 --- Comment #2 from Clementine --- Sorry,but after a system update to tumbleweed 20230422, I cannot reproduce it again. It has just been fixed, magically. Before that, only system tray icons have this issue. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468959] Context menu move transaction selector window too small
https://bugs.kde.org/show_bug.cgi?id=468959 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #1 from jesse --- I agree it is annoying but still kMyMoney is highly useable. I have been using it for the past several years. Hopefully it does get addressed. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 468976] New: rotated EXIF images in video track is ignored in preview when using proxy clip, but it is rendered correctly.
https://bugs.kde.org/show_bug.cgi?id=468976 Bug ID: 468976 Summary: rotated EXIF images in video track is ignored in preview when using proxy clip, but it is rendered correctly. Classification: Applications Product: kdenlive Version: 23.04.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: debianb...@saahbs.net Target Milestone: --- Created attachment 158426 --> https://bugs.kde.org/attachment.cgi?id=158426&action=edit with-proxy-clip-unrotated-preview-but-correct-thumbnail SUMMARY EXIF for images in video track is ignored in preview when using proxy clip, but rendered correctly. STEPS TO REPRODUCE 1. use a vertical jpeg image with EXIF 2. insert image into project bin and V1 track, observing that EXIF takes effect and image is shown vertically (CORRECT) 3. enable proxy for the image in project bin, observing that thumbnail is stil vertical, but in V1 it is now horizontal (INCORRECT) 4. render the project, observing that it is rendered vertically (CORRECT) OBSERVED RESULT rotated EXIF image in preview with proxy clip is displayed un-rotated. EXPECTED RESULT rotated EXIF image in preview with proxy clip should be displayed rotated SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian oldstable (but using Appimage Kdenlive) KDE Plasma Version: not using KDE desktop KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 468946] Kast does not start
https://bugs.kde.org/show_bug.cgi?id=468946 kev.metalw...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG Status|CONFIRMED |RESOLVED --- Comment #5 from kev.metalw...@gmail.com --- (In reply to bart from comment #4) > Nevermind, I missed that you mentioned it's Neon. > > I've had a look at the listed dependencies, and it indeed seems to be > missing kirigami-addons as runtime dep. > I'll open an MR to get that corrected. In the meantime, you should be able > to solve it by manually installing it on your system. I installed kirigami-addons-dev and Kasts now opens and works. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468936] Home Page and Reports display completely black - Cannot Read
https://bugs.kde.org/show_bug.cgi?id=468936 --- Comment #2 from Jim Ladino --- Created attachment 158425 --> https://bugs.kde.org/attachment.cgi?id=158425&action=edit Output from Console when starting KMyMoney -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468937] SMS not working
https://bugs.kde.org/show_bug.cgi?id=468937 --- Comment #3 from Justin --- (In reply to Justin from comment #2) > (In reply to Simon Redman from comment #1) > > Hi Justin, > > > > Please share your Android app version. There was an issue with 1.24.0 which > > broke SMS, which was fixed with 1.24.1 a few days later. > > > > Thanks, > > Simon > > Apologies! I have version 1.24.1 from F-Droid. I just tested again - and it worked. huh. Is there a word limit? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468937] SMS not working
https://bugs.kde.org/show_bug.cgi?id=468937 --- Comment #2 from Justin --- (In reply to Simon Redman from comment #1) > Hi Justin, > > Please share your Android app version. There was an issue with 1.24.0 which > broke SMS, which was fixed with 1.24.1 a few days later. > > Thanks, > Simon Apologies! I have version 1.24.1 from F-Droid. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468975] New: When machine wakes up with different number of screens than it fell asleep with, the screen locker can break ("wl_display@1: error 1: invalid arguments for wl_display@1.get_re
https://bugs.kde.org/show_bug.cgi?id=468975 Bug ID: 468975 Summary: When machine wakes up with different number of screens than it fell asleep with, the screen locker can break ("wl_display@1: error 1: invalid arguments for wl_display@1.get_registry") Classification: Plasma Product: kwin Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: n...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Have a laptop and an external screen (in my case, an HDMI screen plugged into a Thunderbolt dock) 2. Put the machine to sleep with Kickoff > Sleep 3. Unplug the external screen 4. Wake the machine up OBSERVED RESULT Roughly 25% of the time, the screen locker breaks with the typical "the lock screen is broken" message. EXPECTED RESULT The lock screen appears. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.11-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: LENOVO System Version: ThinkPad X1 Yoga 4th ADDITIONAL INFORMATION There are no crash logs in `coredumpctl`. Journal logs from kwin_wayland reveal the following: Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Everything else failed. Need to put Greeter in emergency mode. Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter process exit unregular. Restarting lock. Apr 25 16:40:14 Liberator kscreenlocker_greet[41400]: The Wayland connection broke. Did the Wayland compositor die? Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter process exit unregular. Restarting lock. Apr 25 16:40:14 Liberator kscreenlocker_greet[41385]: The Wayland connection broke. Did the Wayland compositor die? Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter process exit unregular. Restarting lock. Apr 25 16:40:14 Liberator kscreenlocker_greet[41367]: The Wayland connection experienced a fatal error: Invalid argument Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: wl_display@1: error 1: invalid arguments for wl_display@1.get_registry Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received delete_id for unknown id (22) Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received delete_id for unknown id (23) Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received delete_id for unknown id (46) Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received delete_id for unknown id (45) Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received delete_id for unknown id (56) Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received delete_id for unknown id (47) Apr 25 16:40:14 Liberator kwin_wayland_wrapper[41367]: error: received delete_id for unknown id (54) Apr 25 16:40:14 Liberator kwin_wayland_wrapper[1664]: error in client communication (pid 1664) Apr 25 16:40:14 Liberator kwin_wayland_wrapper[1664]: not a valid new object id (2), message get_registry(n) Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter process exit unregular. Restarting lock. Apr 25 16:40:14 Liberator kwin_wayland[1664]: kscreenlocker: Greeter Process encountered an unhandled error: QProcess::Crashed -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468818] "Take New Screenshot/Screen Recording" labels are unnecessary when tab bar is visible
https://bugs.kde.org/show_bug.cgi?id=468818 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/spectacle/commit/9ef2d |hics/spectacle/commit/65027 |cdf477020fd2ba8ecb4f2678e09 |f4bbfd6eb5e169f2dfb65176886 |7c75b365|dd85dff6 --- Comment #8 from Nate Graham --- Git commit 65027f4bbfd6eb5e169f2dfb65176886dd85dff6 by Nate Graham. Committed on 25/04/2023 at 22:54. Pushed by ngraham into branch 'release/23.04'. Hide redundant header on Wayland On Wayland where screen recording is supported, the right column has a tab bar on top with the text "Screenshot" and "Recording" for the tabs. On each of the tabs, right below that tab bar is a header that says a wordier version of the same thing, which is rather redundant. Hide the labels on Wayland when the tab bar is visible. FIXED-IN: 23.04.1 (cherry picked from commit 9ef2dcdf477020fd2ba8ecb4f2678e097c75b365) M +3-0src/Gui/CaptureOptions.qml M +6-12 src/Gui/RecordOptions.qml https://invent.kde.org/graphics/spectacle/commit/65027f4bbfd6eb5e169f2dfb65176886dd85dff6 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468818] "Take New Screenshot/Screen Recording" labels are unnecessary when tab bar is visible
https://bugs.kde.org/show_bug.cgi?id=468818 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/spectacle/commit/9ef2d ||cdf477020fd2ba8ecb4f2678e09 ||7c75b365 Version Fixed In||23.04.1 Resolution|--- |FIXED --- Comment #7 from Nate Graham --- Git commit 9ef2dcdf477020fd2ba8ecb4f2678e097c75b365 by Nate Graham. Committed on 25/04/2023 at 22:52. Pushed by ngraham into branch 'master'. Hide redundant header on Wayland On Wayland where screen recording is supported, the right column has a tab bar on top with the text "Screenshot" and "Recording" for the tabs. On each of the tabs, right below that tab bar is a header that says a wordier version of the same thing, which is rather redundant. Hide the labels on Wayland when the tab bar is visible. FIXED-IN: 23.04.1 M +3-0src/Gui/CaptureOptions.qml M +6-12 src/Gui/RecordOptions.qml https://invent.kde.org/graphics/spectacle/commit/9ef2dcdf477020fd2ba8ecb4f2678e097c75b365 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468974] New: Overview effect is not launched when Chromium flatpak is in full-screen mode
https://bugs.kde.org/show_bug.cgi?id=468974 Bug ID: 468974 Summary: Overview effect is not launched when Chromium flatpak is in full-screen mode Classification: Plasma Product: kwin Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: rafael.palma.l...@gmail.com Target Milestone: --- SUMMARY If you have Chromium flatpak installed and you use it in full screen mode (F11), it is not possible to launch the overview effect (Meta+W). This works with Firefox (snap) in full screen. STEPS TO REPRODUCE 1. Install Chromium flatpak 2. Open a website and switch to full screen (F11) 3. Try to launch the overview effect (Meta+W); notice that it won't work 4. Exit full screen (F11 again) 5. Launch the overview effect; now it will work OBSERVED RESULT With Chromium in full screen mode, the overview effect does not work. EXPECTED RESULT The overview effect should work with Chromium in full-screen mode, since Firefox already does. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 (available in About System) KDE Plasma Version: Plasma 5.27.4 (backports) KDE Frameworks Version: 5.104 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 468098] Function ''Mean'' does not function (in SpreadSheet) with numbers of more 5 figures
https://bugs.kde.org/show_bug.cgi?id=468098 Stefan Gerlach changed: What|Removed |Added Latest Commit|https://invent.kde.org/educ |https://invent.kde.org/educ |ation/labplot/commit/983ed7 |ation/labplot/commit/c47ff9 |16b2d4a6741e3f25d8f549094e0 |90e51d74c82ba9eef2057336793 |ebf534e |9d95a27 --- Comment #3 from Stefan Gerlach --- Git commit c47ff990e51d74c82ba9eef20573367939d95a27 by Stefan Gerlach. Committed on 25/04/2023 at 22:14. Pushed by sgerlach into branch 'release/2.10'. Fix group separator problem in formulas FIXED-IN: 2.10.1 M +13 -8src/backend/core/column/ColumnPrivate.cpp M +5-1src/backend/gsl/ExpressionParser.cpp https://invent.kde.org/education/labplot/commit/c47ff990e51d74c82ba9eef20573367939d95a27 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 468098] Function ''Mean'' does not function (in SpreadSheet) with numbers of more 5 figures
https://bugs.kde.org/show_bug.cgi?id=468098 Stefan Gerlach changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||2.10.1 Latest Commit||https://invent.kde.org/educ ||ation/labplot/commit/983ed7 ||16b2d4a6741e3f25d8f549094e0 ||ebf534e --- Comment #2 from Stefan Gerlach --- Git commit 983ed716b2d4a6741e3f25d8f549094e0ebf534e by Stefan Gerlach. Committed on 25/04/2023 at 22:11. Pushed by sgerlach into branch 'master'. Fix group separator problem in formulas FIXED-IN: 2.10.1 M +13 -8src/backend/core/column/ColumnPrivate.cpp M +5-1src/backend/gsl/ExpressionParser.cpp https://invent.kde.org/education/labplot/commit/983ed716b2d4a6741e3f25d8f549094e0ebf534e -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 468973] New: Kalendar crashed when trying to run it
https://bugs.kde.org/show_bug.cgi?id=468973 Bug ID: 468973 Summary: Kalendar crashed when trying to run it Classification: Applications Product: kalendar Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: cjsbei...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (23.04.0) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 5.19.0-41-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Several unsuccessful attempts. The crash can be reproduced every time. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7ff445e5377b in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7ff445e537ed in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff445fdf2f7 in QAccessibleQuickItem::role() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7ff43e17387a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7ff43e1765f8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7ff43e177e22 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7ff445e61dbb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7ff445e69686 in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7ff445e69bd1 in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7ff3fb4f4b62 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #15 0x7ff443ee722e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7ff443ef22b6 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7ff3fb4f4ed2 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #18 0x7ff443ee9993 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7ff444b6c793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7ff443ebc18a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7ff443ebf277 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7ff443f16597 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7ff441b20d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7ff441b756c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7ff441b1e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7ff443f15be8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7ff443ebaaab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7ff443ec3044 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x5590a0e6e51c in ?? () #30 0x7ff443429d90 in __libc_start_call_main (main=main@entry=0x5590a0e6c500, argc=argc@entry=1, argv=argv@entry=0x7ffee8b627c8) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7ff443429e40 in __libc_start_main_impl (main=0x5590a0e6c500, argc=1, argv=0x7ffee8b627c8, init=, fini=, rtld_fini=, stack_end=0x7ffee8b627b8) at ../csu/libc-start.c:392 #32 0x5590a0e6f4c5 in ?? () [Inferior 1 (process 10534) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 468337] Baloo ignores corrupted DB
https://bugs.kde.org/show_bug.cgi?id=468337 tagwer...@innerjoin.org changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from tagwer...@innerjoin.org --- Did you get anywhere? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468863] Plasma automatically switching from unoccupied desktops to occupied desktops
https://bugs.kde.org/show_bug.cgi?id=468863 --- Comment #5 from Alex --- (In reply to Natalie Clarius from comment #4) > Are you using multiple screens? Maybe it is some strange interaction with > screen focus, as workspaces are tied to screens on i3, right? Thanks for the help! I'm just using my laptop screen. I double checked the output of xrandr and it reports that everything other than eDP-1 is disconnected. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 468972] New: Can't load new comet, or asteroids data
https://bugs.kde.org/show_bug.cgi?id=468972 Bug ID: 468972 Summary: Can't load new comet, or asteroids data Classification: Applications Product: kstars Version: 3.3.6 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: wroba...@protonmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Get a error message when trying to up date -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468873] plasmashell always crashes on start with X11OutputOrderWatcher::refresh() when xrandr isn't available
https://bugs.kde.org/show_bug.cgi?id=468873 --- Comment #4 from Nate Graham --- Hah, that's not what I had remembered. Let me ask around and figure this out. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468818] "Take New Screenshot/Screen Recording" labels are unnecessary when tab bar is visible
https://bugs.kde.org/show_bug.cgi?id=468818 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/spectacle/-/merge_requests/234 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468873] plasmashell always crashes on start with X11OutputOrderWatcher::refresh() when xrandr isn't available
https://bugs.kde.org/show_bug.cgi?id=468873 --- Comment #3 from Maciej Poleski --- I'm having difficulty wrapping my head around this: https://planet.kde.org/vlad-zahorodnii-2022-07-23-xinerama-becomes-hard-requirement-of-kwin/. Was Xinerama support dropped in 5.27? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454621] Plasmashell doesn't start on all monitors in a multi xscreen environment
https://bugs.kde.org/show_bug.cgi?id=454621 --- Comment #16 from Allistar --- My fix as provided in the patch works for me but it's not a good general purpose fix. I filter out monitors by their serial number as that's unique, but the only easy way I could find the serial number was to add debugging in the code to output this from the QScreen instances. This isn't suitable for most people. The "Display and Monitor -> Display Configuration" system settings app correctly only shows monitors from the current xscreen. Another fix would be to just filter out monitors not in the current xscreen in the screenpool.cpp file. I looked at the QScreen class and couldn't see an easy way to get this information. Should QApp::getScreens only provide monitors in the current xscreen? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428392] Impossible to "eject" a mounted ISO image via Places panel
https://bugs.kde.org/show_bug.cgi?id=428392 witchhunter changed: What|Removed |Added CC||witchhunterpro@protonmail.c ||om --- Comment #5 from witchhunter --- As a workaround one could implement the following Dolphin service: [Desktop Action unmount] Exec=bash -c 'readarray -t images < <(losetup -nO NAME); [ -n "${images[@]}" ] && for item in "${images[@]}"; do udisksctl loop-delete -b "$item"; done ' Icon=edit-clear Name=Clear ISOs [Desktop Entry] Actions=unmount; Icon=application-x-iso MimeType=all/all ServiceTypes=KonqPopupMenu/Plugin Type=Service X-KDE-StartupNotify=false As a benefit you wont have to search for unmounted ISO's. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434239] "Communication with the local password server failed" error when attempting to connect to remote Samba server
https://bugs.kde.org/show_bug.cgi?id=434239 80p3fy7...@cloud-mail.top changed: What|Removed |Added CC||80p3fy7...@cloud-mail.top --- Comment #2 from 80p3fy7...@cloud-mail.top --- Has anyone ever found a solution? I'm having the same issue when trying to access any machine via the FISH protocol. MTP in Dolphin is also broken with my Android phone. This all started after I switched from KDE Plasma to AwesomeWM. I removed all Plasma packages but kept Dolphin and Ark installed. No issue whatsoever before that. - Distro: Arch Linux - kio 5.105.0-1 - kio-extras 23.04.0-1 $ KDE_FORK_SLAVES=1 dolphin kf.coreaddons: "Could not load plugin from /usr/lib/qt/plugins/ffmpegthumbs.so: Failed to extract plugin meta data from '/usr/lib/qt/plugins/ffmpegthumbs.so'" kf.kio.core: Can't communicate with kiod_kpasswdserver (for checkAuthInfo)! kf.kio.core: Can't communicate with kiod_kpasswdserver (for checkAuthInfo)! kf.kio.core: Can't communicate with kiod_kpasswdserver (for queryAuthInfo)! kf.kio.core: Can't communicate with kiod_kpasswdserver (for queryAuthInfo)! kf.kio.core: "Communication with the local password server failed" I tried to reinstall Dolphin, kio and kio-extras on my host and remote machines (all running Arch Linux), to no avail. SSH works as expected and so does adb (regarding the MTP in Dolphin being broken). Any insight is appreciated. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 468971] (KDE / NVidia / Wayland) Monitor freezes when another monitor is turned on
https://bugs.kde.org/show_bug.cgi?id=468971 nick...@outlook.com changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 468971] (KDE / NVidia / Wayland) Monitor freezes when another monitor is turned on
https://bugs.kde.org/show_bug.cgi?id=468971 --- Comment #1 from nick...@outlook.com --- Created attachment 158424 --> https://bugs.kde.org/attachment.cgi?id=158424&action=edit JournalCTL Log. The "kscreen_osd_ser" core dump begins at line - 11814 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 468971] New: (KDE / NVidia / Wayland) Monitor freezes when another monitor is turned on
https://bugs.kde.org/show_bug.cgi?id=468971 Bug ID: 468971 Summary: (KDE / NVidia / Wayland) Monitor freezes when another monitor is turned on Classification: Plasma Product: KScreen Version: 5.27.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: OSD Assignee: kscreen-bugs-n...@kde.org Reporter: nick...@outlook.com Target Milestone: --- SUMMARY I am running into a issue on KDE / NVidia / Wayland where if I turn on a third monitor, one of my existing monitors freezes up completely (See Video for more info - https://youtu.be/H2KAJl2yJWI). No windows can be moved, no mouse movements show up on it, etc. It's like the monitor is completely frozen on a screenshot of the desktop. When looking into journalctl, it seems like the process "kscreen_osd_ser" is crashing right around the time the third monitor is turned on (see in additional information below). The output of running "coredumpctl info" and "coredumpctl gdb" with debuginfod is shown in the "Additional Information" section below. A journalctl log of all the messages since boot is also attached below STEPS TO REPRODUCE 1. Boot into KDE with nvidia drivers installed and wayland session. Have 1 or 2 monitors already on. 2. Turn on a third screen/monitor 3. One of the screens will freeze up OBSERVED RESULT A monitor that is completely frozen. No windows can be moved, and no mouse movements are visible. It's essentially frozen on a screenshot of the desktop. EXPECTED RESULT The monitor is expected not to freeze when another monitor is turned on SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 NVidia Packages: - nvidia-dkms 530.41.03-1 - nvidia-settings 530.41.03-1 - nvidia-utils 530.41.03-1 Wayland Related Packages: - egl-wayland 2:1.1.11-4 - kwayland 5.105.0-1 - kwayland-integration 5.27.4-1 - plasma-wayland-session 5.27.4.1-1 - qt5-wayland 5.15.9+kde+r55-1 - wayland 1.22.0-1 - wayland-utils 1.1.0-1 - xorg-xwayland 23.1.1-1 Kernel Version: 6.2.12-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 ADDITIONAL INFORMATION -- kscreen_osd_ser core dump -- Apr 25 13:41:13 nickarchlinux systemd-coredump[12900]: [🡕] Process 12435 (kscreen_osd_ser) of user 1000 dumped core. Stack trace of thread 12435: #0 0x7f096dca08ec n/a (libc.so.6 + 0x878ec) #1 0x7f096dc51ea8 raise (libc.so.6 + 0x38ea8) #2 0x7f096dc3b53d abort (libc.so.6 + 0x2253d) #3 0x7f096ca9fede _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x9fede) #4 0x7f096d0fa6d2 n/a (libQt5Gui.so.5 + 0xfa6d2) #5 0x7f096d157cf9 _ZN7QCursorC2EN2Qt11CursorShapeE (libQt5Gui.so.5 + 0x157cf9) #6 0x7f096d157e99 _ZN14QWindowPrivate9setCursorEPK7QCursor (libQt5Gui.so.5 + 0x157e99) #7 0x7f096e035361 _ZN17QQuickItemPrivate11derefWindowEv (libQt5Quick.so.5 + 0x235361) #8 0x7f096e0351b6 _ZN17QQuickItemPrivate11derefWindowEv (libQt5Quick.so.5 + 0x2351b6) #9 0x7f096e0351b6 _ZN17QQuickItemPrivate11derefWindowEv (libQt5Quick.so.5 + 0x2351b6) #10 0x7f096e0351b6 _ZN17QQuickItemPrivate11derefWindowEv (libQt5Quick.so.5 + 0x2351b6) #11 0x7f096e029b4b _ZN10QQuickItem13setParentItemEPS_ (libQt5Quick.so.5 + 0x229b4b) #12 0x7f096e02a162 _ZN10QQuickItemD1Ev (libQt5Quick.so.5 + 0x22a162) #13 0x7f094eb7a00b n/a (libqtquicktemplates2plugin.so + 0x3500b) #14 0x7f096e0ba459 _ZN10QQuickViewD2Ev (libQt5Quick.so.5 + 0x2ba459) #15 0x7f096e0ba47e _ZN10QQuickViewD0Ev (libQt5Quick.so.5 + 0x2ba47e) #16 0x564f104a7876 n/a (kscreen_osd_service + 0xa876) #17 0x564f104a78dd n/a (kscreen_osd_service + 0xa8dd)
[kasts] [Bug 468946] Kast does not start
https://bugs.kde.org/show_bug.cgi?id=468946 b...@mogwai.be changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from b...@mogwai.be --- Nevermind, I missed that you mentioned it's Neon. I've had a look at the listed dependencies, and it indeed seems to be missing kirigami-addons as runtime dep. I'll open an MR to get that corrected. In the meantime, you should be able to solve it by manually installing it on your system. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468630] .cbz files containing .webp or .tiff cannot be opened
https://bugs.kde.org/show_bug.cgi?id=468630 --- Comment #6 from Albert Astals Cid --- Yes that was the problem and is getting fixed soon-ish -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 468970] google contacts in kaddressbook, missing address, website, note
https://bugs.kde.org/show_bug.cgi?id=468970 --- Comment #1 from Philippe ROUBACH --- Operating System: openSUSE Tumbleweed 20230424 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 468970] New: google contacts in kaddressbook, missing address, website, note
https://bugs.kde.org/show_bug.cgi?id=468970 Bug ID: 468970 Summary: google contacts in kaddressbook, missing address, website, note Classification: Applications Product: kontact Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: kdepim-b...@kde.org Reporter: philippe.roub...@free.fr Target Milestone: --- SUMMARY missing : address website note -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468889] way to force printer to use drivers by deleting driverless option
https://bugs.kde.org/show_bug.cgi?id=468889 David Chmelik changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from David Chmelik --- (In reply to Nate Graham from comment #3) > But do you know that your driverless printer actually supports using > drivers? Does this work? I described using drivers, so it's clear they do. The problem is you can't get rid of the driverless option, which isn't as good. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468889] way to force printer to use drivers by deleting driverless option
https://bugs.kde.org/show_bug.cgi?id=468889 David Chmelik changed: What|Removed |Added Summary|way to force driverless |way to force printer to use |printer to use drivers |drivers by deleting ||driverless option -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 468969] New: Implement STOP Command in Plate Solve when Camera is Busy
https://bugs.kde.org/show_bug.cgi?id=468969 Bug ID: 468969 Summary: Implement STOP Command in Plate Solve when Camera is Busy Classification: Applications Product: kstars Version: 3.6.4 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: rmiller...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT When a Plate Solve is initiated, and the system detects the camera as busy, the Plate Solve routine goes into a series of waits at 10 sec, 20 sec, 40 sec, etc etc waiting for the camera to become unbusy. Often times (more like usually) the camera is not busy. The system thinks the camera is busy, but there is no apparent indication to the user. The problem is that, when the Plate Solver starts these delays as the user searches for why the system thinks the camera is busy, the STOP button is grayed out! Sometimes the only solution is to quit the session, then restart. The simple solution would seem to be to let the user STOP the process as soon as the Plate Solve routine says the camera is busy so the user can find where the system thinks the camera is busy before the Ekos embarks on a long wait sequence. One example of where the system thinks the camera is busy when it is not is the Focus module. If the camera is doing loop capture and the STOP button is hit in the Focus module, the Plate Solve module will always say the camera is busy. After hitting STOP when doing Focus looping, run the camera once in a Single Shot mode. That usually clears the conflict. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 468605] auto-correction incorrectly changes dot to arrow in floating-point literals when using uniform initialization
https://bugs.kde.org/show_bug.cgi?id=468605 --- Comment #5 from Alessandro Carinelli --- Thanks for the help. Unfortunately both clang_getDiagnosticCategoryText and clang_getDiagnosticSpelling seem to return empty strings in this case (while in the case of a floating point literal with a leading '.' they are respectively "Parse Issue" and "expected expression"). I noticed that when reproducing the bug as soon as the '.' gets replaced with "->" an autocompletion suggestion pops up containing only the name of the struct and this makes sense with the single completion result provided by clang. Only after a while an error shows up saying "Expected unqualified-id". Is it possible that this lag is the reason why it looks like everything is fine with the arrow and the program proceeds with the substitution? I had an idea: after we get trimmedText we move backwards starting from the character right before the '.' checking every character until we find something different from a letter (upper or lowercase), an underscore or a digit, in this way we should find the first character in the identifier or literal that precedes the '.', if such first character is a digit we know that we are dealing with a floating point literal and skip the substitution. I tried it and it seems to work without noticeable performance issues. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 468946] Kast does not start
https://bugs.kde.org/show_bug.cgi?id=468946 b...@mogwai.be changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from b...@mogwai.be --- So the problem is that you don't have kirigami-addons installed (or it's not recognized). This package is a dependency of Kasts. You mentioned that you installed through discover. I'm assuming that it's installing the distro package. If so, which distribution are you using? Because they seem to be missing a dependency. This particular one is easy to miss since it's only a runtime dependency, i.e. the package will compile just fine without kirigami-addons, but you won't be able to run the app. -- You are receiving this mail because: You are watching all bug changes.