[PicoWizard] [Bug 462372] Crash at text entering on raspberry pi 4
https://bugs.kde.org/show_bug.cgi?id=462372 Aditya Mehra changed: What|Removed |Added CC||ai...@outlook.com --- Comment #2 from Aditya Mehra --- This crash is caused by the Qt VirtualKeyboard package on the Manjaro image, which on activation causes Pico Wizard or any Qt based application to crash when focusing on Text Fields. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 454119] New: Kirigami Overlay Drawers by default set the interactive policy to false on non mobile, causing escape key to not close the drawer or follow closePolicy
https://bugs.kde.org/show_bug.cgi?id=454119
Bug ID: 454119
Summary: Kirigami Overlay Drawers by default set the
interactive policy to false on non mobile, causing
escape key to not close the drawer or follow
closePolicy
Product: frameworks-kirigami
Version: 5.94.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: ai...@outlook.com
Target Milestone: Not decided
SUMMARY
- Kirigami Overlay Drawers do not close when the escape key is pressed.
explicitly adding the closePolicy does not seem to help either.
- Escape Key and closePolicy only works when setting the interactive property
explicitly to true in non mobile environment
- Interactive property of the overlay drawer seems to be set to false by
default on non mobile platforms or touch enabled platforms.
STEPS TO REPRODUCE:
Sample Code:
- The overlay drawer has been given a closePolicy, but does not react to escape
key press unless interactive property is set to true
Kirigami.AbstractApplicationWindow {
width: 640
height: 480
visible: true
Button {
anchors.bottom: parent.bottom
width: parent.width
height: Kirigami.Units.gridUnit * 2
text: "Open Drawer"
onClicked: {
exampleOverlayDrawer.open()
}
}
Kirigami.OverlayDrawer {
id: exampleOverlayDrawer
width: parent.width
height: parent.height * 0.5
edge: Qt.TopEdge
closePolicy: Popup.CloseOnEscape | Popup.CloseOnPressOutside
dim: true
// if this property is not set to true explicitly on non mobile
platforms closePolicy does not apply and escape key is not caught
// interactive: true
onOpened: {
sampleButton.forceActiveFocus()
}
contentItem: Item {
Button {
id: sampleButton
width: parent.width
height: Kirigami.Units.gridUnit * 2
text: "Close Drawer"
background: Rectangle {
color: sampleButton.activeFocus ?
Kirigami.Theme.highlightColor : "white"
}
onClicked: {
exampleOverlayDrawer.close()
}
}
}
}
}
SOFTWARE/OS VERSIONS
Distribution: KDE Neon
KDE Plasma Version: 5.24.80
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.3
Graphics Platform: X11
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-mycroft] [Bug 417397] Time Stamp of questions and answers shows a 48 minute difference from current time
https://bugs.kde.org/show_bug.cgi?id=417397 Aditya Mehra changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #3 from Aditya Mehra --- should be fixed in the following branch https://cgit.kde.org/plasma-mycroft.git/log/?h=Archive/1.x -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 401139] Localization tags do not work inside list elements
https://bugs.kde.org/show_bug.cgi?id=401139 Aditya Mehra changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Aditya Mehra --- Fixed with commit "e05b9600d5ea4eb00bd40936d2f4978183f2de72" -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 401139] New: Localization tags do not work inside list elements
https://bugs.kde.org/show_bug.cgi?id=401139 Bug ID: 401139 Summary: Localization tags do not work inside list elements Product: plasma-mycroft Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Plasmoid Assignee: ai...@outlook.com Reporter: ai...@outlook.com Target Milestone: --- Created attachment 116371 --> https://bugs.kde.org/attachment.cgi?id=116371&action=edit Screenshot of the error message SUMMARY Localization tags do not work inside list elements and should not be used there, Commit "70ef9a2d0ce12ad70e03e3c35cc9fd19ad576567", "Fix i18n" breaks the plasmoid RESOLUTION Reverting last commit to fix bug -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 395747] The mute mic button in plasmoid does not indicate current system state
https://bugs.kde.org/show_bug.cgi?id=395747 --- Comment #2 from Aditya Mehra --- Update: Partially fixed in commit https://phabricator.kde.org/R846:d4c7a3e76997495e7c7837a34b361609622ebf16 Complete fix requires: https://github.com/MycroftAI/mycroft-core/pull/1656 to land in Mycroft-Core -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 395747] The mute mic button in plasmoid does not indicate current system state
https://bugs.kde.org/show_bug.cgi?id=395747 Aditya Mehra changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Aditya Mehra --- Mycroft shouldn't be muting the whole system audio capture in the first place, and should only be muting Mycroft mic capture internally. Fix in progress -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 391943] Weather temperatures displayed as degrees k, not F
https://bugs.kde.org/show_bug.cgi?id=391943 Aditya Mehra changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Aditya Mehra --- Thanks for reporting this working on the fix. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 377778] Fedora Install Script Broken
https://bugs.kde.org/show_bug.cgi?id=38 Aditya Mehra changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Aditya Mehra --- I am closing this issue as it was fixed sometime ago, the new install scripts for fedora are located at: https://github.com/MycroftAI/installers -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 388032] How to integrate Plasmoid-mycroft with Mycroft Docker service?
https://bugs.kde.org/show_bug.cgi?id=388032 Aditya Mehra changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #3 from Aditya Mehra --- (In reply to stardiviner from comment #2) > Created attachment 109457 [details] > attachment-6190-0.html > > > You're right, I did need to bind Docker container inside IP (from command > "ip addr") to Plasmoid mycroft. It's connected now. Thanks. BTW, can you > improve Plasmoid mycroft to change the default skills location? Instead of > install in /home/USER, install into ~/.config/plasmoid-mycroft/ or > something similar? > > > [stardiviner] GPG key ID: 47C32433 > IRC(freeenode): stardiviner Twitter: @numbchild > Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433 > Blog: http://stardiviner.github.io/ > > On Wed, Dec 20, 2017 at 3:17 AM, Aditya Mehra > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=388032 > > > > Aditya Mehra changed: > > > >What|Removed |Added > > > > > > Resolution|--- |WAITINGFORINFO > > Status|UNCONFIRMED |NEEDSINFO > > > > --- Comment #1 from Aditya Mehra --- > > (In reply to stardiviner from comment #0) > > > I pulled Mycroft docker image. Want to configure plasmoid-mycroft to use > > > docker service. > > > I set plasmoid-mycroft core path to `ws://0.0.0.0:8181/core`. > > > And launch mycroft docker image with command: > > > ``` > > > docker run -itd -p 8181:8181 -v ~/.mycroft:/root/.mycroft > > > mycroftai/docker-mycroft > > > ``` > > > Then I execute command: > > > ``` > > > $ docker exec -it "elastic_thompson" /bin/bash > > > > ./start.sh > > > ``` > > > > > > Then I check out plasmoid-mycroft again, it report yellow message: > > "Mycroft > > > is disabled" > > > > Is 0.0.0.0 your docker image's IP address, 0.0.0.0 should be your local > > system > > rather than dockers IP address. Have you tried "ip addr" in the docker > > image > > itself to get its assigned address ? you might be required to even manually > > assign the ip for your mycroft-docker image and you should set that ip in > > the > > settings area where "ws://0.0.0.0:8181/core" would change to > > "ws://192.168.1.1:8181/core" (192.168.1.1 as an example, replace by > > docker IP) > > > > The docker image / mycroft need to be started first before connecting from > > the > > plasmoid. > > > > -- > > You are receiving this mail because: > > You reported the bug. Default skill locations are set and controlled by Mycroft, the plasmoid has no control over where your skills are installed, As i understand you are using a docker image for mycroft, you will be required to install the skills in the docker image from msm command line, the plasmoid feature to install skills will not work, Certain plasmoid features are originally meant to support only system installs of mycroft, and there might not be any workarounds to this limitation. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 388032] How to integrate Plasmoid-mycroft with Mycroft Docker service?
https://bugs.kde.org/show_bug.cgi?id=388032 Aditya Mehra changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Aditya Mehra --- (In reply to stardiviner from comment #0) > I pulled Mycroft docker image. Want to configure plasmoid-mycroft to use > docker service. > I set plasmoid-mycroft core path to `ws://0.0.0.0:8181/core`. > And launch mycroft docker image with command: > ``` > docker run -itd -p 8181:8181 -v ~/.mycroft:/root/.mycroft > mycroftai/docker-mycroft > ``` > Then I execute command: > ``` > $ docker exec -it "elastic_thompson" /bin/bash > > ./start.sh > ``` > > Then I check out plasmoid-mycroft again, it report yellow message: "Mycroft > is disabled" Is 0.0.0.0 your docker image's IP address, 0.0.0.0 should be your local system rather than dockers IP address. Have you tried "ip addr" in the docker image itself to get its assigned address ? you might be required to even manually assign the ip for your mycroft-docker image and you should set that ip in the settings area where "ws://0.0.0.0:8181/core" would change to "ws://192.168.1.1:8181/core" (192.168.1.1 as an example, replace by docker IP) The docker image / mycroft need to be started first before connecting from the plasmoid. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 378193] Use systemd to start Mycroft service
https://bugs.kde.org/show_bug.cgi?id=378193 Aditya Mehra changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |FIXED --- Comment #5 from Aditya Mehra --- User Issue Resolved -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 378193] Use systemd to start Mycroft service
https://bugs.kde.org/show_bug.cgi?id=378193 --- Comment #3 from Aditya Mehra --- That is the second option in the screenshot "Installed Using Mycroft Package" -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 377779] Plasmoid could not import Qt.WebSockets 1.0
https://bugs.kde.org/show_bug.cgi?id=39 Aditya Mehra changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WORKSFORME --- Comment #1 from Aditya Mehra --- Works for me on up to date Fedora 25 x64. Your distribution and plasma version? -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 377778] Fedora Install Script Broken
https://bugs.kde.org/show_bug.cgi?id=38 Aditya Mehra changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasma-mycroft] [Bug 378193] Use systemd to start Mycroft service
https://bugs.kde.org/show_bug.cgi?id=378193 Aditya Mehra changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Aditya Mehra --- (In reply to stardiviner from comment #0) > Arch Linux now use systemd now. So the > `/usr/share/plasma/plasmoids/org.kde.plasma.mycroftplasmoid/contents/code/*. > sh` scripts should change from `service` to `systemctrl`. The plasmoid already has an option to use Systemd service under the settings tab. Are you on the latest version ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375922] libkf5plasma5-dev: depends: plasma-framework (= 5.30.0+p16.04+git20170126.1521-0) but 5.30.0-0neon+16.04+build29 is to be installed
https://bugs.kde.org/show_bug.cgi?id=375922 Aditya Mehra changed: What|Removed |Added Summary|libkfplasma5-dev: depends: |libkf5plasma5-dev: depends: |plasma-framework (= |plasma-framework (= |5.30.0+p16.04+git20170126.1 |5.30.0+p16.04+git20170126.1 |521-0) but |521-0) but |5.30.0-0neon+16.04+build29 |5.30.0-0neon+16.04+build29 |is to be installed |is to be installed -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375922] New: libkfplasma5-dev: depends: plasma-framework (= 5.30.0+p16.04+git20170126.1521-0) but 5.30.0-0neon+16.04+build29 is to be installed
https://bugs.kde.org/show_bug.cgi?id=375922 Bug ID: 375922 Summary: libkfplasma5-dev: depends: plasma-framework (= 5.30.0+p16.04+git20170126.1521-0) but 5.30.0-0neon+16.04+build29 is to be installed Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: ai...@outlook.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Unable to install libkf5plasma-dev on user edition / user lts edition with similar errors: libkfplasma5-dev: depends: plasma-framework (= 5.30.0+p16.04+git20170126.1521-0) but 5.30.0-0neon+16.04+build29 is to be installed -- You are receiving this mail because: You are watching all bug changes.
