[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 --- Comment #23 from Phil Brown --- (In reply to fanzhuyifan from comment #22) > (In reply to Phil Brown from comment #21) > > Comment on attachment 169966 [details] > > demo3 > > > > OK, so you have it calculating a result with every keystroke, unlike every > > other calculator since the invention of the electronic calculator > > That was intentionally implemented in > https://invent.kde.org/utilities/kcalc/-/merge_requests/84 as a feature. > Please keep the discussion here on topic about chaining results into the > next calculation, which seems to be fully implemented in the demos. the only reason this is broken is because of the faulty design. No other calculator implements this "feature". AFAICT you are the only person who wanted this "feature". All it does is waste CPU cycles. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 --- Comment #21 from Phil Brown --- Comment on attachment 169966 --> https://bugs.kde.org/attachment.cgi?id=169966 demo3 OK, so you have it calculating a result with every keystroke, unlike every other calculator since the invention of the electronic calculator -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 --- Comment #18 from Phil Brown --- Comment on attachment 169965 --> https://bugs.kde.org/attachment.cgi?id=169965 demo 2 The point of my question was what happens when *all* the operands have multiple digits. Do a demo where they are all 3 digit numbers -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 --- Comment #17 from Phil Brown --- Comment on attachment 169965 --> https://bugs.kde.org/attachment.cgi?id=169965 demo 2 do 20*15/8.5 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 Phil Brown changed: What|Removed |Added CC||phillip.brow...@gmail.com --- Comment #14 from Phil Brown --- Comment on attachment 169923 --> https://bugs.kde.org/attachment.cgi?id=169923 Proposed behavior Gabriel, how does your proposal work with multi digit numbers if it is calculating the answer every time you enter a digit? It should work like a real calculator, and only calculate the answer when you hit an operator -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 487419] New: KOrganizer crashed whilst deleting an entry from a Caldav Calendar
https://bugs.kde.org/show_bug.cgi?id=487419 Bug ID: 487419 Summary: KOrganizer crashed whilst deleting an entry from a Caldav Calendar Classification: Applications Product: korganizer Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: b...@700c.org Target Milestone: --- Application: korganizer (6.0.2 (24.02.2)) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.5.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 6.0 DrKonqi: 6.0.4 [KCrashBackend] -- Information about the crash: I started my computer and logged in. A notification appeared for an event that I had forgotten to delete, so I opened KOrganizer to delete it. When I clicked on delete from the right click context menu for that event KOrganizer crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #4 QScopedPointer >::get (this=, this=) at ./src/corelib/tools/qscopedpointer.h:110 #5 qGetPtrHelper > > (ptr=..., ptr=...) at ./src/corelib/global/qtclasshelpermacros.h:79 #6 QObject::d_func (this=0x0) at ./src/corelib/kernel/qobject.h:107 #7 QObject::deleteLater (this=0x0) at ./src/corelib/kernel/qobject.cpp:2456 #8 0x72a05a47f221 in Akonadi::IncidenceChangerPrivate::handleInvitationsAfterChange (this=, change=...) at ./src/incidencechanger.cpp:658 #9 0x72a05a480688 in Akonadi::IncidenceChangerPrivate::handleDeleteJobResult (this=0x58505fe204f0, job=) at ./src/incidencechanger.cpp:358 #10 0x72a05b1fa272 in QObject::event (this=0x58505fe204f0, e=0x58506378eb50) at ./src/corelib/kernel/qobject.cpp:1446 #11 0x72a05c40992b in QApplicationPrivate::notify_helper (this=, receiver=0x58505fe204f0, e=0x58506378eb50) at ./src/widgets/kernel/qapplication.cpp:3287 #12 0x72a05b2a1c38 in QCoreApplication::notifyInternal2 (receiver=0x58505fe204f0, event=event@entry=0x58506378eb50) at ./src/corelib/kernel/qcoreapplication.cpp:1134 #13 0x72a05b2a1c7d in QCoreApplication::sendEvent (receiver=, event=event@entry=0x58506378eb50) at ./src/corelib/kernel/qcoreapplication.cpp:1575 #14 0x72a05b2a23e0 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x58505f992460) at ./src/corelib/kernel/qcoreapplication.cpp:1932 #15 0x72a05b078277 in postEventSourceDispatch (s=0x58505fa52ce0) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:244 #16 0x72a05908dd3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x72a0590e32b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x72a05908b3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x72a05b076570 in QEventDispatcherGlib::processEvents (this=0x58505fa2d690, flags=...) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:394 #20 0x72a05b2a3e3b in QEventLoop::exec (this=this@entry=0x7c117760, flags=..., flags@entry=...) at ./src/corelib/global/qflags.h:34 #21 0x72a05b2a5a6c in QCoreApplication::exec () at ./src/corelib/global/qflags.h:74 #22 0x72a05b6e4330 in QGuiApplication::exec () at ./src/gui/kernel/qguiapplication.cpp:1926 #23 0x72a05c4078d9 in QApplication::exec () at ./src/widgets/kernel/qapplication.cpp:2555 #24 0x58505e99d96c in main (argc=, argv=) at ./src/main.cpp:62 [Inferior 1 (process 4266) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 486577] Consider adding the number of supporting members to kde.org/donations
https://bugs.kde.org/show_bug.cgi?id=486577 --- Comment #1 from Paul Brown --- (In reply to Nate Graham from comment #0) > Right now https://kde.org/fundraisers/plasma6member shown the number of > supporting numbers, and a list of their names. This has proved unexpectedly > useful for fundraising: > > 1. "Number goes up" psychology encourages people to help raise the number of > supporting members > 2. People like seeing their own names listed there, and are therefore > incentivized to become supporting members > > However that web page is specific to the 2023 Plasma 6 fundraising drive and > will diminish in profile over time. I think it would be useful to migrate > the details about supporting members to https://kde.org/donations. Yes. There was talk of making the current page re-direct to _donations_ and include some elements of the old page there. This should include the number of donors as you suggest. This is a good idea. > And > ideally it would be auto-generated from something so it doesn't have to be > updated by hand. KDE e.V. does pay for DonorBox API access, so this should > be feasible. We do? We definitely should automate it then. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 484116] Cannot automatically fix path relocation after creating a project under Windows and open it on Linux
https://bugs.kde.org/show_bug.cgi?id=484116 James Brown changed: What|Removed |Added Summary|Cannot automatically fix|Cannot automatically fix |path relocation after |path relocation after |creating projects under |creating a project under |Windows and open it on |Windows and open it on |Linux |Linux -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 484116] New: Cannot automatically fix path relocation after creating projects under Windows and open it on Linux
https://bugs.kde.org/show_bug.cgi?id=484116 Bug ID: 484116 Summary: Cannot automatically fix path relocation after creating projects under Windows and open it on Linux Classification: Applications Product: kdenlive Version: 24.02.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: randomvoidm...@foxmail.com Target Milestone: --- SUMMARY If one creates a project under Windows, with all files and project file on removable media, when plugging that media to Linux and open the project, Kdenlive failed to fix the relocated paths. STEPS TO REPRODUCE 1. Create a project under removable media with Windows 2. Plug that media to Linux and open the project 3. Resource relocation cannot be fixed OBSERVED RESULT Paths being changed into something like: /:\ EXPECTED RESULT Path being correctly fixed. SOFTWARE/OS VERSIONS Windows 11 Pro Insider Preview Linux: Ubuntu 22.04 -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 483740] Include labplot in KDE for students
https://bugs.kde.org/show_bug.cgi?id=483740 Paul Brown changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Paul Brown --- Done. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 483740] Include labplot in KDE for students
https://bugs.kde.org/show_bug.cgi?id=483740 Paul Brown changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 483740] Include labplot in KDE for students
https://bugs.kde.org/show_bug.cgi?id=483740 Paul Brown changed: What|Removed |Added URL||https://kde.org/for/student ||s/ CC||paul.br...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Paul Brown --- (In reply to Lorenz Hoffmann from comment #0) > SUMMARY > > I noticed that LabPlot is missing from the "KDE for students" page > (https://kde.org/for/students/). I think it would be a good fit and deserves > a mention there! You are right. We'll see how we can fit it in. -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 483209] Scheduled Backup fails to start on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483209 --- Comment #2 from Simon Brown --- If I connect and decrypt the storage volume before starting the backup when prompted, it appears to run successfully. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 483542] Megarelease 6 announcement missing links for Spectacle
https://bugs.kde.org/show_bug.cgi?id=483542 Paul Brown changed: What|Removed |Added CC||paul.br...@kde.org Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Paul Brown --- Modifying that section would break translations, which is much more problematic and for more people than fixing what is a very minor issue. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 483543] Megarelease 6 announcement rearrange Plasma Mobile paragraphs
https://bugs.kde.org/show_bug.cgi?id=483543 Paul Brown changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||paul.br...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0
https://bugs.kde.org/show_bug.cgi?id=481993 --- Comment #17 from Quinn Brown --- I had the same thing where discover would open after sleeping again, so I took a screenshot this time. After I restarted from the update this time I clicked on Discover again in the app menu and it opened. I closed it and clicked the update notifier and nothing would open again. I tried to kill the processes in System Monitor and nothing worked. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0
https://bugs.kde.org/show_bug.cgi?id=481993 --- Comment #16 from Quinn Brown --- Created attachment 167002 --> https://bugs.kde.org/attachment.cgi?id=167002=edit Discover opening while a terminal shows uptime -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 483209] New: Scheduled Backup fails to start on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483209 Bug ID: 483209 Summary: Scheduled Backup fails to start on Plasma 6 Classification: Applications Product: kup Version: 0.9.1 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: simon.pers...@mykolab.com Reporter: b...@700c.org Target Milestone: --- SUMMARY I have a backup profile set that prompts me to backup after a set number of active hours. After upgrade to Plasma 6 I still get the pop-up asking if I'd like to backup now, but on pressing yes nothing happens. I now get the prompt every time I log-in. STEPS TO REPRODUCE 1. Install Neon with plasma 5 2. Setup a backup profile based on a set number of active hours 3. Upgrade to Plasma 6 4. When prompted to start a backup, press yes OBSERVED RESULT Nothing happens EXPECTED RESULT 1. A prompt window asking to unlock my encrypted volume 2. Backup process starts SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION X11 -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 482737] New: KAddressbook crash editing entry
https://bugs.kde.org/show_bug.cgi?id=482737 Bug ID: 482737 Summary: KAddressbook crash editing entry Classification: Applications Product: kaddressbook Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: b...@700c.org Target Milestone: --- Application: kaddressbook (6.0.0 (24.02.0)) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.5.0-21-generic x86_64 Windowing System: X11 Distribution: KDE neon 6.0 DrKonqi: 6.0.0 [KCrashBackend] -- Information about the crash: I can reproduce the bug with: - Reboot computer - Log into Plasma X11 session - Open KAddressbook using launcher application menu - search for entry - select entry - click on edit contact - the edit window appears for a moment, then the app crashes. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KAddressBook (kaddressbook), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140461839114816) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140461839114816) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140461839114816, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fbfd8e42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fbfd8e287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7fbfd9adb017 in qAbort () at ./src/corelib/global/qglobal.cpp:161 #10 0x7fbfd9ad64e5 in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2003 #11 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7ffe3bcc2940) at ./src/corelib/global/qlogging.cpp:378 #12 0x7fbfd9adba43 in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:901 #13 0x7fbfd9aa9cf4 in qt_assert_x (where=where@entry=0x7fbfd91c6fc2 "QList::insert", what=what@entry=0x7fbfd91c6544 "index out of range", file=file@entry=0x7fbfd91c6430 "/usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h", line=line@entry=868) at ./src/corelib/global/qassert.cpp:77 #14 0x7fbfd916153b in QList::emplace (this=, i=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h:868 #15 QList::emplace (this=, i=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h:866 #16 0x7fbfd915fee7 in QList::insert (t=, i=, this=0x55e1341ed530) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h:471 #17 Akonadi::PhoneComboBoxType::setType (this=0x55e1341ed500, type=...) at ./src/akonadi-contacts-widgets/editor/generalinfoeditor/phone/phonecomboboxtype.cpp:42 #18 0x7fbfd915e89c in Akonadi::PhoneWidget::loadPhone (this=0x55e1341dce50, number=...) at ./src/akonadi-contacts-widgets/editor/generalinfoeditor/phone/phonewidget.cpp:76 #19 0x7fbfd915cf47 in Akonadi::PhoneWidgetLister::loadContact (this=, contact=...) at ./src/akonadi-contacts-widgets/editor/generalinfoeditor/phone/phonewidgetlister.cpp:37 #20 0x7fbfd915f6ed in Akonadi::PhoneListWidget::loadContact (this=, contact=...) at ./src/akonadi-contacts-widgets/editor/generalinfoeditor/phone/phonelistwidget.cpp:38 #21 0x7fbfd916e2e9 in Akonadi::GeneralInfoWidget::loadContact (this=0x55e133f5da00, contact=...) at ./src/akonadi-contacts-widgets/editor/generalinfoeditor/generalinfowidget.cpp:104 #22 0x7fbfd9188657 in ContactEditorWidget::loadContact (this=0x55e133e9e160, contact=..., metaData=...) at ./src/akonadi-contacts-widgets/editor/contacteditorwidget.cpp:196 #23 0x7fbfd919455c in Akonadi::AkonadiContactEditorPrivate::loadContact (metaData=..., addr=..., this=0x55e133f0d830) at ./src/akonadi-contacts-widgets/contacteditor.cpp:185 #24 Akonadi::AkonadiContactEditorPrivate::parentCollectionFetchDone (this=0x55e133f0d830, job=) at ./src/akonadi-contacts-widgets/contacteditor.cpp:137 #25 0x7fbfd9a2b7ce in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ./src/corelib/kernel/qobjectdefs_impl.h:433 #26 doActivate (sender=0x7fbfc4009ed0, signal_index=6, argv=0x7ffe3bcc2d30) at ./src/corelib/kernel/qobject.cpp:4039 #27 0x7fbfdb169870 in KJob::result (this=this@entry=0x7fbfc4009ed0, _t1=, _t1@entry=0x7fbfc4009ed0, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF6CoreAddons_autogen/include/moc_kjob.cpp:793 #28 0x7fbfdb16d63b in KJob::finishJob (this=0x7fbfc4009ed0, emitResult=) at ./src/lib/jobs/kjob.cpp:98 #29 0x7fbfd99c9572 in QObject::event (this=0x7fbfc4009ed0, e=0x55e134a17b40) at ./src/corelib/kernel/qobject.cpp:1437 #30 0x7fbfdabf40eb in QApplicationPrivate::notify_helper (this=, receiver=0x7fbfc4009ed0, e=0x55e134a17b40) at ./src/widgets/kernel/qapplication.cpp:3296 #31 0x7fbfd9a63e18 in
[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0
https://bugs.kde.org/show_bug.cgi?id=481993 --- Comment #12 from Quinn Brown --- I had something really weird happen: my surface was running for a day or 2 a sleep, I turn it on and I forget that Discover is broken. I click the updates available systray icon, Discover magically opens. I update my system and restart and now it won't open again? It's so odd. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481993] Discover fails to launch after upgrade to Neon 6.0
https://bugs.kde.org/show_bug.cgi?id=481993 Quinn Brown changed: What|Removed |Added CC||incognitobox1...@gmail.com --- Comment #1 from Quinn Brown --- (In reply to bmhieserich from comment #0) > 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 > *** > After fixing the other issues with the upgrade to Plasma 6 on KDE Neon > through the terminal, Discover will not launch via attempting to launch > through any method (launcher, krunner, terminal, etc). An instance of the > application shows as running in the System Monitor, but there is no window > or other visible sign that an instance of Discover is running. > > STEPS TO REPRODUCE > 1. Attempt to launch Discover by any means (click on launcher, run > "plasma-discover" in terminal, launch from krunner, etc) > 2. Wait for Discover to finish launching to find no window opens > 3. Open System Monitor to notice that it shows Discover as running > > OBSERVED RESULT > Discover fails to provide any usable interface to do anything with. > > EXPECTED RESULT > Discover launches and is usable. > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: KDE Neon 6.0 > (available in About System) > KDE Plasma Version: 6.0.0 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.2 > > ADDITIONAL INFORMATION I had the same situation myself. In addition to what they said, I had an update notifier from Discover in my systray that worked, but I couldn't launch the app from it. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 481605] Support Plasma 6! Donations page - new members listed multiple times
https://bugs.kde.org/show_bug.cgi?id=481605 Paul Brown changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Paul Brown --- (In reply to Paul Brown from comment #3) > (In reply to Oliver Beard from comment #2) > > For Welcome Center, I have de-duplicated the names. I believe Paul should do > > the same for the website. > > Okay. Will do. Thanks for the heads up. I hadn't realised. Duplicates now get removed from list on website. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 481605] Support Plasma 6! Donations page - new members listed multiple times
https://bugs.kde.org/show_bug.cgi?id=481605 --- Comment #3 from Paul Brown --- (In reply to Oliver Beard from comment #2) > For Welcome Center, I have de-duplicated the names. I believe Paul should do > the same for the website. Okay. Will do. Thanks for the heads up. I hadn't realised. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479273] On Wayland, Vertical Scroll mouse actions do not work in Folder containment, only Desktop containment
https://bugs.kde.org/show_bug.cgi?id=479273 --- Comment #5 from Paul Brown --- Thanks! Great job. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479273] New: Vertical Scroll under Mouse Action in Desktop Settings does not perform the assigned action
https://bugs.kde.org/show_bug.cgi?id=479273 Bug ID: 479273 Summary: Vertical Scroll under Mouse Action in Desktop Settings does not perform the assigned action Classification: Plasma Product: plasmashell Version: 5.91.0 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: paul.br...@kde.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY The "vertical scroll" input does not seem to trigger any action on the empty desktop. STEPS TO REPRODUCE 1. Right click on an empty area in workspace, choose "Desktop and Wallpaper" from popup menu 2. Choose "Mouse Actions" from tabs 3. Add an action and scroll the wheel to associate "Vertical-Scroll" and add it to the list of actions 4. Assign an action from the drop down and click "ok" OBSERVED RESULT When you scroll the mouse wheel when hovering over an empty area of the workspace no action happens EXPECTED RESULT When you scroll the mouse wheel when hovering over an empty are of the workspace the associated action should happen. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I have found several reports for similar, sometimes identical, bugs, but for much older versions of the plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #17 from Michael Brown --- (In reply to Oded Arbel from comment #16) > (In reply to Michael Brown from comment #15) > > The fix I made also includes wayland copy functionality. > > So that that there now is full wayland copy/paste clipboard support in > > Eclipse for the 2023-12 release pipeline. > > In copying functionality, I don't see a different behavior with the new > build - `wl-paste -l` shows an almost identical output with the old build, > except that the new build has the type "text/plain;charset=utf-8" listed > twice. I'm guessing that now both the SWT code advertises the > Wayland-mandated type, as well as the GTK Wayland compatibility workaround. > But it works fine, so 路 LGTM. Yeah I found it necessary to also do the paste fix in eclipse to cater for the ubuntu 22.04 distributions that will be stuck in gtk v3.24.33 that is without the gtk workaround. I'm running one of those: KDE Neon on my preferred workstation I guess you are running something with a newer gtk version ? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #15 from Michael Brown --- (In reply to Oded Arbel from comment #14) > (In reply to Michael Brown from comment #12) > > However I have yet no idea yet of what updating to the latest I-Build means > > Here's how I test: > > 1. I go to https://download.eclipse.org/eclipse/downloads/index.html > 2. Under "Integration Builds" there's a list of builds, ordered by date, > descending. I pick the first (latest) that doesn't have scary red > exclamation points. ATM it is I20231109-0710, and click that. > 3. In the page that opens, under "Platform Runtime Binary", I download the > "Linux (64 bit version)", and extract it to somewhere useful on my system - > I like to maintain a bunch of Eclipse installations under ~/.local/eclipse, > so I extract the tarball there, then rename the newly created "eclipse" > folder to "eclipse-", then update the eclipse menu entry in > ~/.local/share/applications/eclipse.desktop to point to the right one). > 4. Launch the "eclipse" binary from the new installation. It would probably > not have any useful tool other than a plain text editor - which should be > enough to test copy and paste with. > > I can now verify that I20231109-0710 supports Wayland paste - I can paste > into that installation, and if I close it and open the older installation, I > cannot paste into it. > > If you want to continue working with the integration test build - you can, > just go to "Help" -> "Install new software" and install all the tools you > need into the integration build. It should also automatically update to the > new 2023-12 release when it is published. Thanks for the info: > I can now verify that I20231109-0710 supports Wayland paste - I can paste > into that installation, and if I close it and open the older installation, I > cannot paste into it. The fix I made also includes wayland copy functionality. So that that there now is full wayland copy/paste clipboard support in Eclipse for the 2023-12 release pipeline. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #13 from Michael Brown --- BTW https://github.com/eclipse-platform/eclipse.platform.swt/commits/master -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #12 from Michael Brown --- @Oded Arbel I'm told repeatedly by the main developers of swt eclipse that: "your patches were merged yesterday and there has been a successful build since then thanks to . You can just update to latest I-Build or download" However I have yet no idea yet of what updating to the latest I-Build means ...:-) https://github.com/eclipse-platform/eclipse.platform.swt/issues/868#issuecomment-1804359275 Be sure to let me know when you can confirm that the wayland clipboard fixes have arrived in the pipeline. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #10 from Michael Brown --- @Oded Arbel Thank you for your info. However I'm curious as how the merge already can be in the pipeline as the original PR was build successfully but the PR then needed to be force pushed several times and then the final PR merge build ended up in a failed state ? https://ci.eclipse.org/releng/job/eclipse.platform.swt/job/PR-863/lastBuild/console -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #7 from Michael Brown --- btw the fix: https://github.com/eclipse-platform/eclipse.platform.swt/pull/863 works with gtk 3.24.33 so no need for the gtk update -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431100] [Wayland] Copy paste from konsole to eclipse and from eclipse to konsole does not work
https://bugs.kde.org/show_bug.cgi?id=431100 --- Comment #24 from Michael Brown --- This Issue is now reloved with https://github.com/eclipse-platform/eclipse.platform.swt/pull/863 works with gtk 3.24.33 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #6 from Michael Brown --- Well I thought of attempting to do it myself and with success: https://github.com/eclipse-platform/eclipse.platform.swt/pull/863 I also managed to provide a fix for copying from Eclipse to KDE/QT apps in wayland... I expect the fixes will be released in eclipse 2023-12 Then Eclipse clipboard functionality for text/plain:utf8 will be fully functional under wayland :-) This bug report can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #3 from Michael Brown --- I just want to correct that the latest gtk version is v3.24.38 not 3.24.37 as I have written. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #2 from Michael Brown --- This bug is also a possible unresolved duplicate: https://bugs.kde.org/show_bug.cgi?id=448511 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431100] [Wayland] Copy paste from konsole to eclipse and from eclipse to konsole does not work
https://bugs.kde.org/show_bug.cgi?id=431100 --- Comment #23 from Michael Brown --- Ok sorry bad my mistake I have opened the issue here instead: https://bugs.kde.org/show_bug.cgi?id=476522 But my issue also includes the konsole app -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 --- Comment #1 from Michael Brown --- I would like to add some info I wrote in my first effort to document this bug: --- There seems to be some confusion in regards to the current state of being able to copy/paste from eclipse (2023-09) to: kde apps like: konsole kate kwrite and qt-creator (probably more). First I would like to link to a recent issue created in the eclipse github where this issue is already confirmed and by one of the developers: https://github.com/eclipse-platform/eclipse.platform.swt/issues/851 The current gtk-version in kde-Neon is based on Ubuntu-LTS (2022.04) and is gtk v3.24.33 (the version before any wayland clipboard patches). So I have to strongly disagree with the statements: >> *not* present in > > KDE Neon or Ubuntu LTS. in the closed thread thread: https://bugs.kde.org/show_bug.cgi?id=431100 Today on a standard kde neon setup it is not possible to copy and paste between any of the above listed kde apps in a wayland session. However as stated in the github thread I have linked to the issue is partially solved in gtk versions 3.24.34 and 3.24.36. Manually recompiling and upgrading the gtk packages in kde-neon to the newest from mantic (23.10) gives version 3.24.37. This adds the functionality of being able to copy from eclipse to the above mentioned apps. However it is still not possible to paste from these apps into eclipse. I have also tested on fedore KDE 38 and kubuntu 23.10 which also run gtk 3.24.37. Same result you can now copy From eclipse, but not paste TO eclipse. the wayland clipboard illustrates what the problem is: With all the above mentioned apps selection and right clicking copy gives the result: text/plain text/plain;charset=utf-8 and no paste functionality in eclipse. running the command: wl-paste -n -t text/plain | wl-copy -t STRING shows the result: (base) mib@neon-ws:~$ wl-paste -n -t text/plain | wl-copy -t STRING (base) mib@neon-ws:~$ wl-paste -l STRING text/plain text/plain;charset=utf-8 TEXT STRING UTF8_STRING and makes it possible to paste in eclipse. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476522] New: Cannot copy from KDE Applications to Eclipse in Wayland
https://bugs.kde.org/show_bug.cgi?id=476522 Bug ID: 476522 Summary: Cannot copy from KDE Applications to Eclipse in Wayland Classification: Applications Product: kate Version: 23.08.1 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: produ...@holotronic.dk Target Milestone: --- Cannot copy from KDE Applications to Eclipse in Wayland *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. have eclipse open with a selected editable source file. 2. open either konsole or kate or kwrite and select some text and right click copy 3. try to paste into the source file in eclipse. OBSERVED RESULT There is no content pasted. EXPECTED RESULT Content gets pasted SOFTWARE/OS VERSIONS Windows: ? macOS: ? Linux/KDE Plasma: Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.2.0-35-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Bug acknowledged in eclipse github: https://github.com/eclipse-platform/eclipse.platform.swt/issues/851 possible duplicate of: https://bugs.kde.org/show_bug.cgi?id=431100 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431100] [Wayland] Copy paste from konsole to eclipse and from eclipse to konsole does not work
https://bugs.kde.org/show_bug.cgi?id=431100 Michael Brown changed: What|Removed |Added Resolution|FIXED |--- CC||produ...@holotronic.dk Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 475556] New: Verifying backups and generating recovery information now too slow to be used
https://bugs.kde.org/show_bug.cgi?id=475556 Bug ID: 475556 Summary: Verifying backups and generating recovery information now too slow to be used Classification: Applications Product: kup Version: 0.9.1 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: simon.pers...@mykolab.com Reporter: b...@700c.org Target Milestone: --- SUMMARY I have a normal modern laptop (AMD 7840) and a modest amount of data (~1TB). When creating a first backup on a clean fast SSD drive generating recovery information is now taking hours. Then on subsequent backups verifying the previous backups again takes hours. Kup seems to be limited to 4 threads, whereas my laptop advertises 12 cores. IO top tells me that the max read/write speed is in the 10s of MBs whereas the drive supports 100s. For now I am forced to disable these extra protections, so that I can be sure that the backup will complete in a reasonable amount of time. I'd love to see kup go faster. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468681] Firefox U2F keys support problem
https://bugs.kde.org/show_bug.cgi?id=468681 --- Comment #4 from Simon Brown --- It is app armour. sudo aa-disable usr.bin.firefox allows my security key to work as it should. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468681] Firefox U2F keys support problem
https://bugs.kde.org/show_bug.cgi?id=468681 --- Comment #3 from Simon Brown --- I have just tested with the tarball release from Mozilla.org and my key works correctly with that package -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468681] Firefox U2F keys support problem
https://bugs.kde.org/show_bug.cgi?id=468681 Simon Brown changed: What|Removed |Added Ever confirmed|0 |1 CC||b...@700c.org Status|REPORTED|CONFIRMED --- Comment #2 from Simon Brown --- This bug is still present in Firefox 118.0.2 on a clean install of Neon. My yubikey works successfully with Chromium from a PPA, but with Firefox it behaves as if it were disabled. I have compared against another machine that runs Kubuntu 22.04 with the same mozilla team package and it works successfully. So it isn't the package, but the environment. I have verified that the about:config webauthn settings are the same on both machines. I had to set apparmor to complain with firefox in order to get my password manager to work, so I wonder if this is a confinement problem? Marking as confirmed as it affects at least three people. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 468681] Firefox U2F keys support problem
https://bugs.kde.org/show_bug.cgi?id=468681 Simon Brown changed: What|Removed |Added CC||lego37y...@outlook.com --- Comment #1 from Simon Brown --- *** Bug 469787 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 469787] Firefox installed with APT repository provided by default not working with USB security keys
https://bugs.kde.org/show_bug.cgi?id=469787 Simon Brown changed: What|Removed |Added CC||b...@700c.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Simon Brown --- This bug is a duplicate of #468681 *** This bug has been marked as a duplicate of bug 468681 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475118] New: The PIM plugin of the Digital Clock widget causes plasmasheel to crash when enabled
https://bugs.kde.org/show_bug.cgi?id=475118 Bug ID: 475118 Summary: The PIM plugin of the Digital Clock widget causes plasmasheel to crash when enabled Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: paul.br...@kde.org Target Milestone: 1.0 SUMMARY Enabling the PIM plugin in the Digital Clock configutarion cause plasmashell to crash. b) bt #0 __GI___pthread_sigmask (how=1, newmask=, oldmask=0x0) at pthread_sigmask.c:43 #1 0x7f4fa585c90d in __GI___sigprocmask (how=, set=, oset=) at ../sysdeps/unix/sysv/linux/sigprocmask.c:25 #2 0x7f4fa808927b in KCrash::setCrashHandler(void (*)(int)) (handler=handler@entry=0x0) at /usr/src/debug/kcrash5/kcrash-5.110.0/src/kcrash.cpp:419 #3 0x7f4fa808b886 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash5/kcrash-5.110.0/src/kcrash.cpp:630 #4 0x7f4fa585c710 in () at /usr/lib/libc.so.6 #5 0x7f4fa60d065f in doActivate(QObject*, int, void**) (sender=0x559896673fe0, signal_index=4, argv=0x7ffc606d5be0) at kernel/qobject.cpp:3957 #6 0x7f4fa4eed6a4 in QQmlDelegateModelItem::rowChanged() (this=0x559896673fe0) at .moc/moc_qqmldelegatemodel_p_p.cpp:221 #7 QQmlDelegateModelItem::setModelIndex(int, int, int, bool) (this=0x559896673fe0, idx=, newRow=, newColumn=, alwaysEmit=false) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:2433 #8 0x7f4fa4eeae19 in QQmlDelegateModel::_q_itemsInserted(int, int) (this=, index=0, count=27) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qmlmodels/qqmldelegatemodel.cpp:1609 #9 0x7f4fa4ef35c3 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x559895831180, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0x7ffc606d5e00) at .moc/moc_qqmldelegatemodel_p.cpp:371 #10 0x7f4fa60d076f in doActivate(QObject*, int, void**) (sender=0x559895831930, signal_index=13, argv=0x7ffc606d5e00) at kernel/qobject.cpp:3951 #11 0x7f4fa6057403 in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (this=this@entry=0x559895831930, _t1=..., _t2=, _t3=, _t4=...) at .moc/moc_qabstractitemmodel.cpp:592 #12 0x7f4fa6057567 in QAbstractItemModel::endInsertRows() (this=0x559895831930) at itemmodels/qabstractitemmodel.cpp:2780 #13 0x7f4fa607574e in QSortFilterProxyModelPrivate::insert_source_items(QVector&, QVector&, QVector const&, QModelIndex const&, Qt::Orientation, bool) (this=this@entry=0x559895831a30, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=orient@entry=Qt::Vertical, emit_signal=) at itemmodels/qsortfilterproxymodel.cpp:950 #14 0x7f4fa6075ce1 in QSortFilterProxyModelPrivate::handle_filter_changed(QVector&, QVector&, QModelIndex const&, Qt::Orientation) (this=this@entry=0x559895831a30, source_to_proxy=..., proxy_to_source=..., source_parent=..., orient=orient@entry=Qt::Vertical) at itemmodels/qsortfilterproxymodel.cpp:1376 #15 0x7f4fa6076120 in QSortFilterProxyModelPrivate::filter_changed(QModelIndex const&) (this=0x559895831a30, source_parent=...) at itemmodels/qsortfilterproxymodel.cpp:1305 #16 0x7f4fa6083a92 in QSortFilterProxyModel::setFilterFixedString(QString const&) (this=, pattern=) at itemmodels/qsortfilterproxymodel.cpp:2882 #17 0x7f4fa60851f3 in QSortFilterProxyModel::qt_metacall(QMetaObject::Call, int, void**) (this=this@entry=0x559895831930, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=12, _a=_a@entry=0x7ffc606d63c0) at .moc/moc_qsortfilterproxymodel.cpp:429 #18 0x7f4ec001944a in KSortFilterProxyModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x559895831930, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7ffc606d63c0) at /usr/src/debug/kitemmodels5/build/src/qml/itemmodelsplugin_autogen/include/moc_ksortfilterproxymodel.cpp:349 #19 0x7f4fa76784b4 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const (this=0x7ffc606d6660, type=QMetaObject::InvokeMetaMethod, index=, argv=) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlobjectorgadget.cpp:51 #20 0x7f4fa7578ac1 in CallMethod (callType=, callArgs=, engine=, argTypes=, argCount=, returnType=, index=, object=) at /usr/include/qt/QtCore/qvarlengtharray.h:189 #21 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=, data=, engine=, callArgs=, callType=) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:1553 #22 0x7f4fa757def6 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const (this=, thisObject=0x7f4f803bb538, argv=, argc=1) at
[kwin] [Bug 472332] Fractionally Scaled Aurorae Themes Become Pixelated
https://bugs.kde.org/show_bug.cgi?id=472332 --- Comment #1 from Quinn Brown --- Created attachment 160339 --> https://bugs.kde.org/attachment.cgi?id=160339=edit a photo of my desktop, comparing the decorations to the window-decorations widget Notice the blurry edges compared to the Window-Decorations widget in my top panel, which seems to work for some reason. No multi-monitor display screenshots will be provided as I'm experiencing another bug where when I connect my surface tablet to a non-fractionally scaled monitor the screen overall becomes slightly blurry, alongside the window decorations themselves. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472332] New: Fractionally Scaled Aurorae Themes Become Pixelated
https://bugs.kde.org/show_bug.cgi?id=472332 Bug ID: 472332 Summary: Fractionally Scaled Aurorae Themes Become Pixelated Classification: Plasma Product: kwin Version: 5.27.6 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: aurorae Assignee: kwin-bugs-n...@kde.org Reporter: incognitobox1...@gmail.com Target Milestone: --- SUMMARY Fractionally Scaled Aurorae Themes Become Pixelated. SEVERITY: Normal STEPS TO REPRODUCE 1. Enable the Plasma Wayland session. 2. Enable Fractional Scaling for a display. 3. Install any Window Decoration theme from the System Settings page for them. 4. Enable that theme, and drag a window to the scaled display. OBSERVED RESULT The window controls shown onscreen don’t match the preview images shown in KDE Store screenshots, and they are pixelated as well as visibly distorted. In some themes, both the titlebar design and buttons are distorted, in others it is just the control buttons. In a multi-display set-up, the decorations seem to appear normal on a non-fractionally-scaled display if you move a window there but become distorted again when returning the window to the scaled display. EXPECTED RESULT Non-distorted window controls on the fractionally scaled display. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: KDE Neon OS 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Graphics Platform: Wayland Display Size: 1920x1200 at 10.1 inches (Microsoft Surface Go 2) Fractional Scaling: 150% Graphics Processor: Intel Mesa UHD Graphics 615 (Probably Irrelevant, unless Aurorae works through XWayland→)Legacy Applications (X11): Applications scale themselves -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377399] kontact loses imap connections constantly
https://bugs.kde.org/show_bug.cgi?id=377399 Paul Brown changed: What|Removed |Added Status|RESOLVED|REOPENED CC||paul.br...@kde.org Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #7 from Paul Brown --- (In reply to Justin Zobel from comment #3) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Happening now every few minutes in Arch with KMail version 5.23.2, Akonadi version 23.04.2. Akonadi message is: org.kde.pim.imapresource: Get metadata failed: "Connection to server lost." -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 470284] New: Cursor disappears when moving over main pane in Wayland
https://bugs.kde.org/show_bug.cgi?id=470284 Bug ID: 470284 Summary: Cursor disappears when moving over main pane in Wayland Classification: Applications Product: kstars Version: 3.6.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: paul.br...@kde.org Target Milestone: --- SUMMARY When you move the cursor from outside the window of from the menu and toll bar to the main pane showing the star map, the cursor disappears. Left clicking and holding to drag, makes a 4-arrowed directional cursor appear and the regular, simple cursors may appear for a few seconds after dragging, but there doe snot seem to be a pattern to this and the cursors always disappears again. STEPS TO REPRODUCE 1. Use Plasma Wayland 2. Open KStars 3. Move cursor over star map pane OBSERVED RESULT The cursor disappears and becomes invisible. EXPECTED RESULT That the cursor remain visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422006] [Dolphin] Emptying trash does not trigger view refresh
https://bugs.kde.org/show_bug.cgi?id=422006 Terrance Brown changed: What|Removed |Added CC|terran...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 465739] New: Optional 5.26-style Toggle
https://bugs.kde.org/show_bug.cgi?id=465739 Bug ID: 465739 Summary: Optional 5.26-style Toggle Classification: Plasma Product: Breeze Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: incognitobox1...@gmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Suggestion: I prefer the now old style of window decorations. Recognizing that alot of work gets put into development, simply removing the new style would be disrespectful to whomever made it. Therefore, as a compromise: the old style should be toggleable, or atleast made into a seperate decoration package like Oxygen is. There is already a color gradient toggle, one swapping the border for the rim highlight seems reasonable. It is still being used in the Breeze gtk theme at the moment, so until those match either way Breeze lacks coherence. The code for both styles of decoration already exists as well, the issue would be one of integrating them into a combined package. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402033] Okular "typewriter" annotation tool - can't change text font or colour
https://bugs.kde.org/show_bug.cgi?id=402033 --- Comment #19 from Paul Brown --- (In reply to Albert Astals Cid from comment #18) > Closing as per Rajeesh comment, Paul please if you have the versions > mentioned in the comment and you still think there's a bug please reopen this Works for me. Thanks folks! -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 464891] New: The transition to the next line (Enter) does not work
https://bugs.kde.org/show_bug.cgi?id=464891 Bug ID: 464891 Summary: The transition to the next line (Enter) does not work Classification: Applications Product: ktouch Version: 22.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: zdwteu...@mozmail.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. Enter does not work 2. 3. OBSERVED RESULT he does not work EXPECTED RESULT Enter work SOFTWARE/OS VERSIONS Windows: not macOS: not Linux/KDE Plasma: Arch Linux 6.16-zen1-1-zen (64bit) (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 460269] Feature suggestion: Fountain support in Ghostwriter
https://bugs.kde.org/show_bug.cgi?id=460269 --- Comment #5 from Paul Brown --- (In reply to megan.conkle from comment #4) > I'm afraid Fountain support is out of scope. While perhaps supporting > syntax highlighting might be "easy", other features that are expected from a > screenwriting software (such as tracking items needed across scenes) will > inevitably be requested. This is a can of worms I don't want to open. I, for one, don't want any of that crap. When I write, I write, and only want to write. That other stuff I can deal with later, if at all. I think it would be a plus (at least it would be a plus for me) if ghostwriter _ONLY_ implemented the markup, took the non-distraction credo to its ultimate consequences, and deliberately refused to implement any of the dingle-dongles that make using other script-writing software so annoying. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 458494] Plasma Does Not Integrate With Snap Firefox
https://bugs.kde.org/show_bug.cgi?id=458494 --- Comment #4 from Andrew Brown --- No keep this ticket open and carry on. I have moved over to installing Firefox from launchpad or somewhere, but I would like to move back to snap as it seems the architected way to go with respect to Canonical. With all the things that were wrong with snap, though, I do think Canonical arranged what looked like a shotgun wedding between Mozilla and ubuntu. Best regards, Andrew Andrew Brown The Blackheath Art Club ☞ G.P.O. Film Unit<http://www.english-heritage.org.uk/visit/blue-plaques/g.p.o.-film-unit> / The Crown Film Unit<http://www.bfi.org.uk/films-tv-people/4ce2b941e0766/> From: Erik Sent: Sunday, December 11, 2022 8:54:59 PM To: Andrew J. Brown Subject: [plasma-browser-integration] [Bug 458494] Plasma Does Not Integrate With Snap Firefox https://bugs.kde.org/show_bug.cgi?id=458494 --- Comment #3 from Erik --- Would it be possible to re-open this bug or should I create a new one? Browser Integration still doesn't seem to work with the Snap version of Firefox 107.0.1. Support for native messaging is added to the stable version of the snap now so therefore I expected Browser Integration to work as well. Got a prompt when starting Firefox to allow Plasma Browser Integration and I clicked OK. When inspecting from Firefox's about:debugging I see the following error message in the console: Uncaught (in promise) Error: Attempt to postMessage on disconnected port sendPortMessage moz-extension://f2a3fa37-c27f-4678-90f5-94eadb4bc46c/extension-utils.js:51 sendSettings moz-extension://f2a3fa37-c27f-4678-90f5-94eadb4bc46c/extension.js:45 -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462515] Toolbar disappears when you switch layout
https://bugs.kde.org/show_bug.cgi?id=462515 --- Comment #2 from Paul Brown --- Wow. That was fast. Thanks j-b. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 462515] New: Toolbar disappears when you switch layout
https://bugs.kde.org/show_bug.cgi?id=462515 Bug ID: 462515 Summary: Toolbar disappears when you switch layout Classification: Applications Product: kdenlive Version: 22.11.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: paul.br...@kde.org Target Milestone: --- SUMMARY When you switch layouts from, say, Logging Editing to Effects, the main toolbar disappears. Even if you enable the toolbar on one layout, move to another and then move book, the toolbar will have disappeared from the original layout. STEPS TO REPRODUCE 1. Go to Settings > Toolbars shown and check "Main toolbar". Kdenlive's main toolbar appears. 2. Switch layout, choosing any of the layouts shown in the upper right hand corner of the window OBSERVED RESULT Toolbar disappears EXPECTED RESULT Toolbar should remain SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon unstable edition / Arch Linux KDE Plasma Version: 5.26.80 / 5.26.4 KDE Frameworks Version: 5.101.0 / 5.100.0 Qt Version: 5.15.7 / 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 323300] Keyboard shortcuts do not respect the keymap [KAction]
https://bugs.kde.org/show_bug.cgi?id=323300 Simon Brown changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Simon Brown --- Wow, I reported this a long time ago. It's been fixed for some time. -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 460269] Feature suggestion: Fountain support in Ghostwriter
https://bugs.kde.org/show_bug.cgi?id=460269 Paul Brown changed: What|Removed |Added CC||paul.br...@kde.org --- Comment #3 from Paul Brown --- (In reply to farid from comment #2) > I second this feature request. We lack a good screenwriting software for > linux. Trelby has been discontinued for years! Thirded! Giving ghostwriter script-writing capabilities would be amazing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 458494] New: Plasma Does Not Integrate With Snap Firefox
https://bugs.kde.org/show_bug.cgi?id=458494 Bug ID: 458494 Summary: Plasma Does Not Integrate With Snap Firefox Product: plasma-browser-integration Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: a...@pinmill.net Target Milestone: --- Created attachment 151698 --> https://bugs.kde.org/attachment.cgi?id=151698=edit Screenshot of my Firefox browser showing the plasma-browser-integration icon with a strike through it. SUMMARY *** KDE's plasma-browser-integration does not integrate with snap installed Firefox. *** I have both plasma-browser-integration and firefox installed: apt list plasma-browser-integration: plasma-browser-integration/jammy,now 5.24.4-0ubuntu1 amd64 [installed] snap list: firefox 104.0-3 1749 latest/stable mozilla✓ - STEPS TO REPRODUCE 1. Install the latest firefox snap. 2. Install KDE's plasma-browser-integration as an add-on. 3. Make sure that KDE's Plasma 5.13 or later is running. I am running KDE Plasma Version: 5.24.4 OBSERVED RESULT The addon complains with: "Failed to connect to the native host. Make sure the 'plasma-browser-integration' package is installed correctly and that you are running Plasma 5.13 or later. No such native application org.kde.plasma.browser_integration". EXPECTED RESULT That plasma-browser-integration does integrate. SOFTWARE/OS VERSIONS Firefox Browser 104.0 (64-bit) (Mozilla Firefox Snap for Ubuntu canonical-002 - 1.0 Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-46-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 458255] Cannot install Yakuake from the link on the KDE page for it.
https://bugs.kde.org/show_bug.cgi?id=458255 --- Comment #3 from Keith Brown --- (In reply to Nicolas Fella from comment #1) > It is correct that Yakuake is not available from Flathub, packaging terminal > apps as Flatpak is somewhat complex > > However, Discover should offer you to install it from your distribution, > assuming it is packaged there. What distribution is that and does it have a > package for Yakuake? Tried first on my Steam Deck using Arch-Based SteamOS 3.0. After that failed, I tried on my laptop running Kubuntu 22.04. I know the Ubuntu repos include yakuake, as I've had it on my laptop for a year now. It reports an error about being unable to open appstream://org.kde.yakuake because it was not found in any repository. I can see that being a thing on the steamdeck, as that relies on the flathub repo, but for ubuntu, that caught me as odd. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 458255] Cannot install Yakuake from the link on the KDE page for it.
https://bugs.kde.org/show_bug.cgi?id=458255 --- Comment #2 from Keith Brown --- Created attachment 151557 --> https://bugs.kde.org/attachment.cgi?id=151557=edit Screenshot from Discovery in Kubuntu 22.04 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 458255] New: Cannot install Yakuake from the link on the KDE page for it.
https://bugs.kde.org/show_bug.cgi?id=458255 Bug ID: 458255 Summary: Cannot install Yakuake from the link on the KDE page for it. Product: yakuake Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: spamt...@hellmark.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Click the "Install to Linux" link on the yakuake page OBSERVED RESULT Receive an error that yakuake cannot be installed due to being not found. EXPECTED RESULT Yakuake installs via KDE Discovery SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 15.5.3 ADDITIONAL INFORMATION Have tried on multiple systems, same results. I think it is mostly due to there not being a version of yakuake on flathub and similar repos that the KDE org makes use of officially. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455126] New: Spectacle takes a photo of itself when capturing a full screen with no delay
https://bugs.kde.org/show_bug.cgi?id=455126 Bug ID: 455126 Summary: Spectacle takes a photo of itself when capturing a full screen with no delay Product: Spectacle Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: paul.br...@kde.org CC: k...@david-redondo.de Target Milestone: --- Created attachment 149598 --> https://bugs.kde.org/attachment.cgi?id=149598=edit Screen capture taken with Spectacle, showing Spectacle in the process of minimising SUMMARY When capturing a full screen without any delay, Spectacle captures a picture of itself as it minimises. See attached image STEPS TO REPRODUCE 1. Open Spectacle 2. Chose "Area:" > "Full Screen" 3. Choose "Delay:" > "No Delay" 4. Click "Take a New Screenshot" OBSERVED RESULT You will see a "ghost" of Spectacle as it is in the process of minimising. EXPECTED RESULT No ghost of Spectacle should be visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon (available in About System) KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Maybe Spectacle should minimise immediately without an intermediate animation. The current workaround is to give it a delay of, say, 1 second. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 446839] Add Steam Deck to https://kde.org/hardware
https://bugs.kde.org/show_bug.cgi?id=446839 Paul Brown changed: What|Removed |Added CC||paul.br...@kde.org --- Comment #8 from Paul Brown --- The composite image is the one that is going to work for us, as we need to isolate it and also in the other alternatives, the desktop is obscured. > but they'd like to see it and approve it first. So if you end up going that > way, can you send it to me so I can send it to them? Of course, no problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446321] Cursor invisible on Plasma Wayland when sharing with Barrier
https://bugs.kde.org/show_bug.cgi?id=446321 --- Comment #4 from Paul Brown --- Understood. This is not a deal-breaker. I was actually surprised that it worked to a certain degree at all, as, in the past, it has not. That said, I do look forward to the day when all these things work fully, though. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 446322] New: Dolphin resets to default location and layout and "forgets" location in directory tree, split windows and open panels after restart on plugin change
https://bugs.kde.org/show_bug.cgi?id=446322 Bug ID: 446322 Summary: Dolphin resets to default location and layout and "forgets" location in directory tree, split windows and open panels after restart on plugin change Product: dolphin Version: 21.11.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: paul.br...@kde.org CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When you change a plugin that needs a restart (e.g.: enabling/disabling Dropbox or Git) in Dolphin, if you pick "Restart" from the dialogue, Dolphin will restart _and_ reset to its default settings, "forgetting" any tabs, splits or panels you had open and defaulting back to showing the user's home directory, instead of the one the user may have had open at the moment of the restart. STEPS TO REPRODUCE 1. Open the terminal panel, split the screen, navigate to a directory that isn't home, etc. 2. Open _Configure Dolphin_ > _Context Menu_. 3. Enable or disable a plugin that requires restart when applied (for example, Git support) and click "Apply" 4. From the dialogue that appears, click "Restart" OBSERVED RESULT Dolphin resets to default location and layout. EXPECTED RESULT Should retain layout, tabs and location prior to the restart. SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Workaround: When the dialogue pops up asking if you want to restart Dolphin now or "Later", choose later. Then stop Dolphin the regular way (say, clicking on the close button or selecting _File_ > _Quit_) and start it up again. Prior settings will be retained. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446321] New: Cursor invisible on Plasma Wayland when sharing with Barrier
https://bugs.kde.org/show_bug.cgi?id=446321 Bug ID: 446321 Summary: Cursor invisible on Plasma Wayland when sharing with Barrier Product: kwin Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: paul.br...@kde.org Target Milestone: --- SUMMARY When using Barrier (https://github.com/debauchee/barrier), the freer version of Synergy, when you share the cursor from the server machine on a client machine running Plasma on Wayland, the cursor itself is invisible, although moving and clicking does affect elements on the desktop. STEPS TO REPRODUCE 1. Run barrier as a client on a machine running Plasma Wayland 2. Share the cursor from your server machine OBSERVED RESULT Cursor is invisible, although it is "present" as you can see the effects of hovering and clicking on elements. EXPECTED RESULT Cursor should be visible. SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-41-generic (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® HD Graphics 5500 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444974] Feature request: Configuration files that can be managed as machine-independent text
https://bugs.kde.org/show_bug.cgi?id=444974 --- Comment #8 from Jeff Brown --- (In reply to Nicolas Fella from comment #6) > The title is somewhat unrelated to the actual issues raised though. The > configurations being text don't have much to do with them being > machine-dependant You're completely right. I've edited the title accordingly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444974] Feature request: Configuration files that can be managed as machine-independent text
https://bugs.kde.org/show_bug.cgi?id=444974 Jeff Brown changed: What|Removed |Added Summary|Feature request:|Feature request: |Configuration files that|Configuration files that |can be managed as text |can be managed as ||machine-independent text -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444974] Feature request: Configuration files that can be managed as text
https://bugs.kde.org/show_bug.cgi?id=444974 --- Comment #2 from Jeff Brown --- Thanks for responding so fast. Maybe this is all perfectly readable and human-editable and I just haven't found the documentation specifying how changes in the GUI map to changes in the configuration language. Is that the case? I wish I could modify those config files, or copy them (or passages from them) from elsewhere, and expect it to work. There are two reasons I currently can't: (1) I tried it and broke KDE. I had to reinstall my OS. I wish I could easily repeat variations on that experiment but I can't. (2) It's not clear which files to copy or modify, or where, or how. Where are the zoom settings kept? The language settings? The number and layout of desktops settings? The setting that swaps Capslock and Esc? If I grep for the word "shortcut" I only find this passage in `~/.config/plasma-org.kde.plasma.desktop-appletsrc`. I've configured a lot of shortcuts and none of them are here: ``` [Containments][2][Applets][3][Configuration][Shortcuts] global=Alt+F1 [Containments][2][Applets][3][Shortcuts] global=Alt+F1 ``` Searching for "desktop" is even harder to make sense of: ``` find . -iname "*plasma*" -print0 | xargs -0 grep -i desktop ./plasmashellrc:performed=/run/current-system/sw/share/plasma/shells/org.kde.plasma.desktop/contents/updates/unlock_widgets.js,/run/current-system/sw/share/plasma/shells/org.kde.plasma.desktop/contents/updates/systemloadviewer_systemmonitor.js,/run/current-system/sw/share/plasma/shells/org.kde.plasma.desktop/contents/updates/maintain_existing_desktop_icon_sizes.js,/run/current-system/sw/share/plasma/shells/org.kde.plasma.desktop/contents/updates/containmentactions_middlebutton.js,/run/current-system/sw/share/plasma/shells/org.kde.plasma.desktop/contents/updates/obsolete_kickoffrc.js,/run/current-system/sw/share/plasma/shells/org.kde.plasma.desktop/contents/updates/move_desktop_layout_config.js ./plasmanotifyrc:[Applications][telegramdesktop] ./plasma-org.kde.plasma.desktop-appletsrc:wheel:Vertical;NoModifier=org.kde.switchdesktop ./plasma-org.kde.plasma.desktop-appletsrc:plugin=org.kde.plasma.showdesktop ``` My system is currently configured for two activities. If I search for "activity" there are four hits in ~/.config/plasma-org.kde.plasma.desktop-appletsrc. What do they mean? ``` [Containments][1] ItemGeometriesHorizontal= activityId=cb054e74-0743-40ef-a67e-796691eb4c30 formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.plasma.folder wallpaperplugin=org.kde.image [Containments][19] ItemGeometriesHorizontal= activityId=74ea37e7-0d78-4216-9788-e9b9ededb800 formfactor=0 immutability=1 lastScreen=0 location=0 plugin=org.kde.plasma.folder wallpaperplugin=org.kde.image [Containments][2] activityId= formfactor=2 immutability=1 lastScreen=0 location=4 plugin=org.kde.panel wallpaperplugin=org.kde.image [Containments][8] activityId= formfactor=2 immutability=1 lastScreen=0 location=4 plugin=org.kde.plasma.private.systemtray wallpaperplugin=org.kde.image ``` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444974] New: Feature request: Configuration files that can be managed as text
https://bugs.kde.org/show_bug.cgi?id=444974 Bug ID: 444974 Summary: Feature request: Configuration files that can be managed as text Product: systemsettings Version: unspecified Platform: Other OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jeffbrown@gmail.com Target Milestone: --- # The wish I would like to manage Plasma configuration via text files rather than the GUI. That way one could copy the text file to a new machine, as opposed to spending around an hour clicking through the Settings. One could even try out someone else's settings -- something that's not practical when it takes a lot of work to change them. # What doesn't work I tried blindly copying all my KDE config files once, and it broke Plasma. According to someone on the NixOS forum[1] that's to be expected, because KDE config files are a mix of human-readable and machine-generated text. # Scope A number of people on that NixOS forum wish for the same thing. There are a few other apps to which the same issue applies -- off the top of my head, Dolphin and Konsole. But at least for me, the lion's share of the configuration work for a new system is in configuring Plasma itself. I believe this applies to all versions of Plasma on all flavors of Linux. [1] https://discourse.nixos.org/t/declarative-kde-configuration/15901 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444542] Discover crashes in kde neon newly updated to 5.23.2
https://bugs.kde.org/show_bug.cgi?id=444542 --- Comment #3 from Michael Brown --- (In reply to Nate Graham from comment #1) > Can you please attach a backtrace of the crash? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports I added it as an comment ok ? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444542] Discover crashes in kde neon newly updated to 5.23.2
https://bugs.kde.org/show_bug.cgi?id=444542 --- Comment #2 from Michael Brown --- Application: Discover (plasma-discover), signal: Segmentation fault [New LWP 8808] [New LWP 8809] [New LWP 8810] [New LWP 8811] [New LWP 8812] [New LWP 8813] [New LWP 8814] [New LWP 8815] [New LWP 8816] [New LWP 8817] [New LWP 8818] [New LWP 8819] [New LWP 8820] [New LWP 8821] [New LWP 8822] [New LWP 8823] [New LWP 8824] [New LWP 8825] [New LWP 8826] [New LWP 8827] [New LWP 8828] [New LWP 8829] [New LWP 8830] [New LWP 8831] [New LWP 8832] [New LWP 8833] [New LWP 8834] [New LWP 8835] [New LWP 8836] [New LWP 8837] [New LWP 8838] [New LWP 8839] [New LWP 8840] [New LWP 8841] [New LWP 8842] [New LWP 8843] [New LWP 8844] [New LWP 8845] [New LWP 8846] [New LWP 8847] [New LWP 8848] [New LWP 8850] [New LWP 8852] [New LWP 8853] [New LWP 8854] [New LWP 8855] [New LWP 8856] [New LWP 8857] [New LWP 8858] [New LWP 8859] [New LWP 8860] [New LWP 8861] [New LWP 8862] [New LWP 8863] [New LWP 8864] [New LWP 8865] [New LWP 8866] [New LWP 8867] [New LWP 8868] [New LWP 8871] [New LWP 8873] [New LWP 8912] [New LWP 8913] [New LWP 8915] [New LWP 8921] [New LWP 8951] [New LWP 8954] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7a69d3aaff in __GI___poll (fds=0x7ffef6a199f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f7a64c66bc0 (LWP 8807))] Thread 68 (Thread 0x7f79617fa700 (LWP 8954)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f79617f9950, clockid=, expected=0, futex_word=0x55e4ef4b25c0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f79617f9950, clockid=, mutex=0x55e4ef4b2570, cond=0x55e4ef4b2598) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55e4ef4b2598, mutex=0x55e4ef4b2570, abstime=0x7f79617f9950) at pthread_cond_wait.c:656 #3 0x7f7a6a0cf558 in QWaitConditionPrivate::wait_relative (this=0x55e4ef4b2570, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x55e4ef4b2570) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x55e4efdb98f0, mutex=mutex@entry=0x55e4ef4dda28, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f7a6a0cca61 in QThreadPoolThread::run (this=0x55e4efdb98e0) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f7a6a0c945c in QThreadPrivate::start (arg=0x55e4efdb98e0) at thread/qthread_unix.cpp:329 #8 0x7f7a69463609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f7a69d47293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 67 (Thread 0x7f7961ffb700 (LWP 8951)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f7961ffa950, clockid=, expected=0, futex_word=0x55e4efedf984) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f7961ffa950, clockid=, mutex=0x55e4efedf930, cond=0x55e4efedf958) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x55e4efedf958, mutex=0x55e4efedf930, abstime=0x7f7961ffa950) at pthread_cond_wait.c:656 #3 0x7f7a6a0cf558 in QWaitConditionPrivate::wait_relative (this=0x55e4efedf930, deadline=...) at thread/qwaitcondition_unix.cpp:136 #4 QWaitConditionPrivate::wait (deadline=..., this=0x55e4efedf930) at thread/qwaitcondition_unix.cpp:144 #5 QWaitCondition::wait (this=this@entry=0x55e4eff86920, mutex=mutex@entry=0x55e4ef4dda28, deadline=...) at thread/qwaitcondition_unix.cpp:225 #6 0x7f7a6a0cca61 in QThreadPoolThread::run (this=0x55e4eff86910) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:275 #7 0x7f7a6a0c945c in QThreadPrivate::start (arg=0x55e4eff86910) at thread/qthread_unix.cpp:329 #8 0x7f7a69463609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f7a69d47293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 66 (Thread 0x7f790dffb700 (LWP 8921)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f7a68aa0746 in g_cond_wait_until () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7a68a23581 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a68a23ba6 in g_async_queue_timeout_pop () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7a68a7d419 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7a68a7cad1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f7a69463609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f7a69d47293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 65 (Thread 0x7f790f7fe700 (LWP 8915)): #0 __GI___libc_read (nbytes=16, buf=0x7f790f7fd7d0, fd=139) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=139, buf=0x7f790f7fd7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f7a68a9bb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7a68a52ebe in g_main_con
[Discover] [Bug 444542] New: Discover crashes in kde neon newly updated to 5.23.2
https://bugs.kde.org/show_bug.cgi?id=444542 Bug ID: 444542 Summary: Discover crashes in kde neon newly updated to 5.23.2 Product: Discover Version: 5.23.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: produ...@holotronic.dk CC: aleix...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. run kde neon newly updated to 5.23.2 2. open discover in any way 3. wait OBSERVED RESULT Discover crashes EXPECTED RESULT Discover stays open and can show found updates status SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415044] Kdenlive does not handle image sequences correctly
https://bugs.kde.org/show_bug.cgi?id=415044 Paul Brown changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415044] Kdenlive does not handle image sequences correctly
https://bugs.kde.org/show_bug.cgi?id=415044 Paul Brown changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415044] Kdenlive does not handle image sequences correctly
https://bugs.kde.org/show_bug.cgi?id=415044 --- Comment #8 from Paul Brown --- (In reply to Julius Künzel from comment #7) > As mentioned above this should be fixed. Please test with the latest version > and close this if there are now problems anymore. Otherwise please give more > details on what is still not working. Thanks again for your report! Everything works as it should! Thank you so much. Excellent work. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440280] New: Underlining does not work with mv'ed or copied files
https://bugs.kde.org/show_bug.cgi?id=440280 Bug ID: 440280 Summary: Underlining does not work with mv'ed or copied files Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: paul.br...@kde.org Target Milestone: --- SUMMARY If you mv (rename) a file in an open directory or cp a file, underlining will not work on the newly named or new files. If you close the tab and access the directory containing the mv'ed or cp'ed files, then underlining will work. STEPS TO REPRODUCE 1. mv or cp an underlineable file within a directory 2. ls the contents of the directory 3. hover the cursor over the mv'ed or cp'ed files OBSERVED RESULT Underlining does not work. EXPECTED RESULT That underlining work SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.4-1-MANJARO (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440279] Find box partially obscured by panes' titlebars
https://bugs.kde.org/show_bug.cgi?id=440279 Paul Brown changed: What|Removed |Added Platform|Other |Manjaro -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440279] New: Find box partially obscured by panes' titlebars
https://bugs.kde.org/show_bug.cgi?id=440279 Bug ID: 440279 Summary: Find box partially obscured by panes' titlebars Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: paul.br...@kde.org Target Milestone: --- Created attachment 140332 --> https://bugs.kde.org/attachment.cgi?id=140332=edit Image showing tha bug SUMMARY If you open a customised split view layout from a file or click on any of the "Load new tab with layout..." buttons and then click on "Find" in any of the panes, the find box will be partially obscured by the pane's titlebar. This does not happen if you split the view manually. STEPS TO REPRODUCE 1. Load a split view from a file or use any of the preset layouts (2x2, 2x1, 2x1) 2. Click on "Find" OBSERVED RESULT The find search box will be partially obscured by the pane's titlebar. EXPECTED RESULT That the box not be obscured, like when you split the view manually. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.4-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 440164] Entries coming from PeerTube feeds should show the thumbnail of the video in the web feed
https://bugs.kde.org/show_bug.cgi?id=440164 --- Comment #1 from Paul Brown --- Created attachment 140264 --> https://bugs.kde.org/attachment.cgi?id=140264=edit PeerTube entries lacka a preview and paragraphs are mangles -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 440164] New: Entries coming from PeerTube feeds should show the thumbnail of the video in the web feed
https://bugs.kde.org/show_bug.cgi?id=440164 Bug ID: 440164 Summary: Entries coming from PeerTube feeds should show the thumbnail of the video in the web feed Product: Planet KDE Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: feeds Assignee: j...@jriddell.org Reporter: paul.br...@kde.org Target Milestone: --- Created attachment 140263 --> https://bugs.kde.org/attachment.cgi?id=140263=edit Entries coming from YouTube show a clickable thumbnail of the video SUMMARY The web feed at https://planet.kde.org/ should show a preview or thumbnail of a PeerTube video as it does with YouTube videos. It should also not mangle the paragraphing of the description of the video as it currently does. Maybe this can be avoided by just showing the title of the video, instead of the full description. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439877] Dolphin crashes when right-clicking on file or folder to summon the contextual menu
https://bugs.kde.org/show_bug.cgi?id=439877 --- Comment #4 from Paul Brown --- (In reply to Harald Sitter from comment #2) > Git commit 07d54af0b6e3f074a9e679db506fc538f52cc410 by Harald Sitter. > Committed on 15/07/2021 at 14:01. > Pushed by sitter into branch 'release/21.08'. > > don't auto deduce QStringBuilder > > see 'auto QString(Builder) considered VERY HARMFUL' thread on kde-devel > https://markmail.org/message/mbrp5ypyhcfk7zjn > > What happens is that the type of str ends up being QStringBuilder > instead of QString. The QStringBuilder is destroyed after the semicolon, > and all access to "str" produces undefined behavior. > > Never use auto for QString concatenation! > > M +1-1 > activities/fileitemplugin/FileItemLinkingPluginActionLoader.cpp > > https://invent.kde.org/network/kio-extras/commit/ > 07d54af0b6e3f074a9e679db506fc538f52cc410 Thanks, Harald! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439877] Dolphin crashes when right-clicking on file or folder to summon the contextual menu
https://bugs.kde.org/show_bug.cgi?id=439877 Paul Brown changed: What|Removed |Added Summary|Dolphin crashes when|Dolphin crashes when |right-clicking on file oro |right-clicking on file or |folder to summon the|folder to summon the |contextual menu |contextual menu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439877] New: Dolphin crashes when right-clicking on file oro folder to summon the contextual menu
https://bugs.kde.org/show_bug.cgi?id=439877 Bug ID: 439877 Summary: Dolphin crashes when right-clicking on file oro folder to summon the contextual menu Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: paul.br...@kde.org CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.11.70) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.22.80 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: Open Dolphin, right click on a file to summon the contextual menu. After a second or less, Dolphin crahses evert time. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [New LWP 1547] [New LWP 1404] [New LWP 1409] [New LWP 1410] [New LWP 1411] [New LWP 1412] [New LWP 1401] [New LWP 1413] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/dolphin'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f979fbc3700 (LWP 1547))] [Current thread is 1 (Thread 0x7f979fbc3700 (LWP 1547))] Thread 8 (Thread 0x7fd7c4856700 (LWP 1413)): #0 0x7fd7dfc23aff in __GI___poll (fds=0x7fd7a4005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd7ddbf836e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fd7ddbf84a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fd7e01f0fb2 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd7e019525b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd7dffaec22 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd7dffafdbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd7de676609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fd7dfc30293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fd7db1ed600 (LWP 1401)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fd7dffb2061 in QSemaphore::acquire(int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd7e01cd6e2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd7e01c6c03 in QObject::destroyed(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd7e01cb9d5 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd7e2184ede in KBookmarkManager::~KBookmarkManager() () from /lib/x86_64-linux-gnu/libKF5Bookmarks.so.5 #6 0x7fd7e218501d in KBookmarkManager::~KBookmarkManager() () from /lib/x86_64-linux-gnu/libKF5Bookmarks.so.5 #7 0x7fd7e218482e in ?? () from /lib/x86_64-linux-gnu/libKF5Bookmarks.so.5 #8 0x7fd7dfb57a27 in __run_exit_handlers (status=1, listp=0x7fd7dfcf9718 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #9 0x7fd7dfb57be0 in __GI_exit (status=) at exit.c:139 #10 0x7fd7da892d97 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7fd7da8c5e77 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #12 0x7fd7ddbf817d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7fd7ddbf8400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd7ddbf84a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd7e01f0fb2 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fd7e019525b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fd7e0dfea88 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fd7e0dfebb3 in QMenu::exec(QPoint const&, QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x55a96c9b4af9 in DolphinContextMenu::openItemContextMenu (this=this@entry=0x55a96e9c30f0) at ./src/dolphincontextmenu.cpp:298 #20 0x55a96c9b5148 in DolphinContextMenu::open (this=this@entry=0x55a96e9c30f0) at ./src/dolphincontextmenu.cpp:112 #21 0x55a96c9aa67d in DolphinMainWindow::openContextMenu (this=0x55a96d969de0, pos=..., item=..., url=..., customActions=...) at /usr/include/c++/9/bits/atomic_base.h:413 #22 0x7fd7e01cd77e in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fd7e2315488 in DolphinView::requestContextMenu (this=this@entry=0x55a96e2f47d0, _t1=...,
[Discover] [Bug 438834] Discover Notifier Icon incorrectly shows up with "Updates Available" notification.
https://bugs.kde.org/show_bug.cgi?id=438834 Terrance Brown changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||terran...@gmail.com --- Comment #2 from Terrance Brown --- I can confirm. Brand-new installation of KDE Neon still shows the update notification on startup despite being fully updated. I've also run pkcon to double-check, and there are indeed no outstanding updated. My Arch laptop running Plasma also has the same issue. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438834] Discover Notifier Icon incorrectly shows up with "Updates Available" notification.
https://bugs.kde.org/show_bug.cgi?id=438834 Terrance Brown changed: What|Removed |Added CC||h3zvqfca@jonathanh55.anonad ||dy.com --- Comment #1 from Terrance Brown --- *** Bug 438826 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438826] wrong update
https://bugs.kde.org/show_bug.cgi?id=438826 Terrance Brown changed: What|Removed |Added Resolution|--- |DUPLICATE CC||terran...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Terrance Brown --- *** This bug has been marked as a duplicate of bug 438834 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 438829] plasma version missing
https://bugs.kde.org/show_bug.cgi?id=438829 --- Comment #2 from Terrance Brown --- Created attachment 139452 --> https://bugs.kde.org/attachment.cgi?id=139452=edit Info Centre Info Centre as currently shown in Arch Linux on latest Plasma version. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 438829] plasma version missing
https://bugs.kde.org/show_bug.cgi?id=438829 Terrance Brown changed: What|Removed |Added CC||terran...@gmail.com --- Comment #1 from Terrance Brown --- (In reply to slartibart70 from comment #0) > The info center does not show the plasma version any more since 5.22, only > the frameworks version. > (in 5.21 we had plasma version, then frameworks version, then QT, ...) I can't seem to reproduce this. Info Centre seems to show me all the same info as before on Arch Linux. Which distribution are you running? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435569] Add Pixabay videos to the list of online resources
https://bugs.kde.org/show_bug.cgi?id=435569 --- Comment #2 from Paul Brown --- (In reply to Julius Künzel from comment #1) > Thanks for your report! Unfortunately I don't have time to work on this at > the moment, but it is not to hard to add new providers and you can now > (after the recent rewrite) add providers with a config file (as you > requested). I wrote a instruction here Thank you, Julius, and thanks for working on Kdenlive. > Hint: We can only add providers that offer a api. Pixabay does that > (https://pixabay.com/api/docs/) and Internet Archive too (even if the api is > not very nice…), but Free Music Archive not :( Ah! What a pity. I understand. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435569] New: Add Pixabay videos to the list of online resources
https://bugs.kde.org/show_bug.cgi?id=435569 Bug ID: 435569 Summary: Add Pixabay videos to the list of online resources Product: kdenlive Version: unspecified Platform: Appimage OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: paul.br...@kde.org Target Milestone: --- The Online Resources panel currently lists 5 resources: Freesound, Internet Archive Movies, Pexel Photos, Pexel Videos and Pixabay Photos. I would also be good to add Pixabay Videos (https://pixabay.com/videos/), Internet Archive audio and still photos, and maybe audio files available at the Free Music Archive (https://freemusicarchive.org/). It would also be good if users could add their own resources, either with a form or by editing a simple text config file, although I have no idea how hard this would be. Either way, good job developing Kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429795] Kdenlive does not change the speed of image sequences correctly
https://bugs.kde.org/show_bug.cgi?id=429795 --- Comment #10 from Paul Brown --- (In reply to Julius Künzel from comment #9) > Is this a duplicate of https://bugs.kde.org/show_bug.cgi?id=392670 ? No. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432593] Battery indicator gone until plasma restart
https://bugs.kde.org/show_bug.cgi?id=432593 --- Comment #5 from Terrance Brown --- Same issue for me. I have to run 'plasmashell --replace' to get it back, but it will disappear again as soon as I reboot. Operating System: Arch Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.10.24-1-lts OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4300M CPU @ 2.60GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432593] Battery indicator gone until plasma restart
https://bugs.kde.org/show_bug.cgi?id=432593 Terrance Brown changed: What|Removed |Added CC||terran...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 423253] Caret gets stuck when moving vertically through soft-wrapped lines.
https://bugs.kde.org/show_bug.cgi?id=423253 Pat Brown changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/commit/8 ||0762d259b20373876db6a8622cf ||17329db7221c --- Comment #5 from Pat Brown --- Git commit 80762d259b20373876db6a8622cf17329db7221c by Tom N Harris, on behalf of Pat Brown. Committed on 17/03/2021 at 03:20. Pushed by cullmann into branch 'master'. Restrict horizontal range of cursor to avoid unintentionally wrapping. When converting a x position to cursor column for a wrapped text line, the last column should not be used or else the cursor will jump to the next line. M +4-0src/render/katerenderer.cpp https://invent.kde.org/frameworks/ktexteditor/commit/80762d259b20373876db6a8622cf17329db7221c -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 434220] Footer link to peertube throws security error
https://bugs.kde.org/show_bug.cgi?id=434220 Paul Brown changed: What|Removed |Added CC||paul.br...@kde.org --- Comment #1 from Paul Brown --- (In reply to Mathew from comment #0) > SUMMARY > The link in the footer to peertude; > https://peertube.mastodon.host/accounts/kde/videos; will throw a security > error as the certificate has expired. Further to that, the link responds > with a 502 Gatewway Error > > STEPS TO REPRODUCE > 1. Go to footer > 2. Open the peertube link > 3. > > OBSERVED RESULT > Link is broken > > EXPECTED RESULT > Goes to working peertube instance > > SOFTWARE/OS VERSIONS > N/A > ADDITIONAL INFORMATION Yes, we are currently seeking a new instance where we can host our videos, since the first one run into technical problems and its admin closed it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433766] New: Flickr export does not work (7.1.0 appimage)
https://bugs.kde.org/show_bug.cgi?id=433766 Bug ID: 433766 Summary: Flickr export does not work (7.1.0 appimage) Product: digikam Version: 7.1.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Plugin-WebService-Flickr Assignee: digikam-bugs-n...@kde.org Reporter: brownphotograp...@gmail.com Target Milestone: --- Created attachment 136268 --> https://bugs.kde.org/attachment.cgi?id=136268=edit error SUMMARY Flickr export does not work (7.1.0 appimage) STEPS TO REPRODUCE 1. Select export to flickr 2. In 'Choose the flickr account to use for exporting images', dropdown is blank, so I select 'Add another account' 3. A popup error immediately appears (see below) OBSERVED RESULT This site can’t be reachedThe webpage at https://www.flickr.com/services/oauth/authorize?perms=write_token=7215771847137-a154f3e0addabb35_callback=https://www.flickr.com might be temporarily down or it may have moved permanently to a new web address. ERR_CERT_AUTHORITY_INVALID EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
