[dolphin] [Bug 466397] Terminal Panel keeps blinking and glitching.
https://bugs.kde.org/show_bug.cgi?id=466397 Aditya changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Aditya --- The update to dolphin 23.04.0 version fixed it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483343] New: Dolphin opens with error "Could not enter folder tags"
https://bugs.kde.org/show_bug.cgi?id=483343 Bug ID: 483343 Summary: Dolphin opens with error "Could not enter folder tags" Classification: Applications Product: dolphin Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bluen...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 167035 --> https://bugs.kde.org/attachment.cgi?id=167035&action=edit Screenshot of an error window saying "Could not enter folder tags:/." SUMMARY *** Happens every time. Both when opening normally and via file picker. *** STEPS TO REPRODUCE 1. Open Dolphin normally or via file picker. OBSERVED RESULT An error message saying "Could not enter folder tags:/." EXPECTED RESULT Dolphin opens normally. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.8.0-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483343] Dolphin opens with error "Could not enter folder tags"
https://bugs.kde.org/show_bug.cgi?id=483343 Aditya changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Aditya --- The bug disappeared after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483849] New: System Settings crashes when hovering on Window Decorations
https://bugs.kde.org/show_bug.cgi?id=483849 Bug ID: 483849 Summary: System Settings crashes when hovering on Window Decorations Classification: Applications Product: systemsettings Version: 6.0.2 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: bluen...@protonmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open System Settings 2. Navigate to Colors & Themes 3. Go to Window Decorations OBSERVED RESULT System Settings crashes. EXPECTED RESULT System Settings does not crash. SOFTWARE/OS VERSIONS Operating System: NixOS 24.05 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.21 (64-bit) Graphics Platform: Wayland Processors: 4 × 11th Gen Intel® Core™ i3-1115G4 @ 3.00GHz Memory: 11.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483849] System Settings crashes when hovering on Window Decorations
https://bugs.kde.org/show_bug.cgi?id=483849 Aditya changed: What|Removed |Added CC||bluen...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483849] System Settings crashes when hovering on Window Decorations
https://bugs.kde.org/show_bug.cgi?id=483849 --- Comment #1 from Aditya --- Created attachment 167377 --> https://bugs.kde.org/attachment.cgi?id=167377&action=edit log file -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483849] System Settings crashes when hovering on Window Decorations
https://bugs.kde.org/show_bug.cgi?id=483849 --- Comment #2 from Aditya --- Created attachment 167385 --> https://bugs.kde.org/attachment.cgi?id=167385&action=edit coredumpctl backtrace -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 483854] New: Plasma System Monitor does not display graphs
https://bugs.kde.org/show_bug.cgi?id=483854 Bug ID: 483854 Summary: Plasma System Monitor does not display graphs Classification: Applications Product: plasma-systemmonitor Version: 6.0.2 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: bluen...@protonmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 167386 --> https://bugs.kde.org/attachment.cgi?id=167386&action=edit screenshot of plasma system monitor STEPS TO REPRODUCE 1. Open Plasma System Monitor OBSERVED RESULT Plasma System Monitor with no graph. EXPECTED RESULT Plasma System Monitor displays graphs like normal. SOFTWARE/OS VERSIONS Operating System: NixOS 24.05 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.21 (64-bit) Graphics Platform: Wayland Processors: 4 × 11th Gen Intel® Core™ i3-1115G4 @ 3.00GHz Memory: 11.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 483854] Plasma System Monitor does not display graphs
https://bugs.kde.org/show_bug.cgi?id=483854 --- Comment #1 from Aditya --- Created attachment 167387 --> https://bugs.kde.org/attachment.cgi?id=167387&action=edit i ran `strings core.5603 > core.5603.txt` because the dump is over a 100 MiB core dump of ksystemstats -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463871] New: Notification overflows the screen
https://bugs.kde.org/show_bug.cgi?id=463871 Bug ID: 463871 Summary: Notification overflows the screen Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: bluen...@protonmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 155052 --> https://bugs.kde.org/attachment.cgi?id=155052&action=edit Screenshot of bug SUMMARY = Docking a panel to top right corner causes the notifications to overflow on the right side. The controls become inaccessible. STEPS TO REPRODUCE === 1. Create a panel. 2. Align to the right. 3. Add System Tray widget. 4. Send a notification. OBSERVED RESULT The notification overflows. EXPECTED RESULT === The notification aligns correctly. SOFTWARE/OS VERSIONS = Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463871] Notification overflows the screen
https://bugs.kde.org/show_bug.cgi?id=463871 --- Comment #2 from Aditya --- (In reply to Nate Graham from comment #1) > Cannot reproduce. Are you using X11 or Wayland? Does it affect all > notifications, or just some? Do you have more than one screen connected? X11. All notifications; 1 screen, multiple virtual desktops -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 403592] New: F12 shortcut doesn't work in ubuntu default desktop environment
https://bugs.kde.org/show_bug.cgi?id=403592 Bug ID: 403592 Summary: F12 shortcut doesn't work in ubuntu default desktop environment Product: yakuake Version: 3.0.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: h...@kde.org Reporter: aditsyn...@gmail.com Target Milestone: --- SUMMARY: Cannot open and retract Yakuake with f12 in ubuntu default desktop environment, can't change the shortcut as well because the change shortcut configure blocked by yakuake. STEPS TO REPRODUCE 1. install ldm 2. use ldm 3. f12 shortcut doesn't work OBSERVED RESULT I configure Yakuake to automatically start in the start up ubuntu, but everytime i press f12 it won't open yakuake. so i have to open manually and after i open i can't use f12 to close. EXPECTED RESULT f12 supposed to open and retract yakuake SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Ubuntu 18.04.01 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION In my mahcine i use ubuntu 18.04.01, i have multiple desktop environment here is the list. i put according to install order - Ubuntu(default) - Ubuntu on wayland - Plasma - Pantheon - Bungie desktop - Gnome classic > other shortcut button in yakuake are working perfectly fine > f12 also doesn't work in gnome classic > Yakuake working perfecly fine on other desktop environment > i dont remember when i install ldm, but right after that the f12 shortcut > doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455384] New: Okular blocks/hangs on print function
https://bugs.kde.org/show_bug.cgi?id=455384 Bug ID: 455384 Summary: Okular blocks/hangs on print function Product: okular Version: 22.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: ag15...@gmail.com Target Milestone: --- SUMMARY Currently, when printing a file (to a printer using lpr), okular blocks, and 1. Becomes unresponsive 2. No new files are opened, they will open only after it becomes responsive This is especially noticeable on printing a large document (>20 pages for me) STEPS TO REPRODUCE 1. Open a pdf file 2. Print to a printer (not file), may also choose Page set as Odd or even OBSERVED RESULT Okular becomes unresponsive. Cannot scroll. Cannot open new files. EXPECTED RESULT Okular keeps working, possibly showing a loading sign that "printing in process" SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 (built against 5.15.3) ADDITIONAL INFORMATION ## Possible solution I thought it should be some call which is blocking on the main thread, so looking for it, I found this call: https://invent.kde.org/graphics/okular/-/blob/master/core/fileprinter.cpp#L141 I think, instead of calling `doPrintFiles` should happen in another process (I am assuming, the pop-up window is a different process). I can't fix it, since I just don't know much Qt as of now :) -- 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.
[kdeplasma-addons] [Bug 427530] Shutdown and restart buttons are missing from fullscreen application dashboard.
https://bugs.kde.org/show_bug.cgi?id=427530 Aditya Prajapati changed: What|Removed |Added CC||aditya12...@gmail.com --- Comment #1 from Aditya Prajapati --- Hi, I am facing the same issue and have not been able to resolve it. Your workaround works for me as well and the exact behaviour is observed in my system as well. Did you happen to find a solution? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 427530] Shutdown and restart buttons are missing from fullscreen application dashboard.
https://bugs.kde.org/show_bug.cgi?id=427530 --- Comment #3 from Aditya Prajapati --- Are you facing this issue on the default KDE panel or do you use something like Latte Dock? I was using latte dock when this issue hit me, I removed latte dock and am using the default panel now where this issue does not seem to exist. If you are using a custom dock/panel, can you try switching temporarily to the default one and see if this issue persists? Maybe this is not a KDE bug/issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 427530] Shutdown and restart buttons are missing from fullscreen application dashboard.
https://bugs.kde.org/show_bug.cgi?id=427530 --- Comment #6 from Aditya Prajapati --- (In reply to Jishan Bhattacharya from comment #5) > (In reply to Aditya Prajapati from comment #3) > > > If you are using a custom dock/panel, can you try switching temporarily to > > the default one and see if this issue persists? Maybe this is not a KDE > > bug/issue. > Yes I tried switching to the default and it it does fix the problem. So it > was because of latte dock? I am not sure. It does seem like a compatibility issue. I am unaware if it is from Latte dock's side or KDE's. I think you should raise a bug report there as well. Might help speed things up. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 427530] Shutdown and restart buttons are missing from fullscreen application dashboard.
https://bugs.kde.org/show_bug.cgi?id=427530 --- Comment #9 from Aditya Prajapati --- I just updated to v5.20.0-2 and restarted my system a couple of times. I can still find the options in my power/session section. I am not sure why this is such a random issue. > Aditya have you tried with fresh new instance of the latte? Does this issue > persist there? I have uninstalled latte dock so I can't comment on that, sorry. Also, my hibernate button seems to be missing from the confirm exit screen (the one you get when you select logout/restart/shutdown) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 493156] New: Okular crashed suddenly.
https://bugs.kde.org/show_bug.cgi?id=493156 Bug ID: 493156 Summary: Okular crashed suddenly. Classification: Applications Product: okular Version: 23.08.5 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: adityazanjad...@gmail.com Target Milestone: --- Application: okular (23.08.5) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.0-41-generic x86_64 Windowing System: X11 Distribution: Ubuntu 24.04.1 LTS DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: I was reading a PDF file. While I was going through it the application Okular suddenly crashed. I don't know what caused this. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7d1cee701801 in QMenu::actionEvent(QActionEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7d1cee5b0df8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7d1cee56bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7d1ced8d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7d1cee5a6df8 in QWidget::removeAction(QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7d1ceed0f496 in KSelectAction::removeAction(QAction*) () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #10 0x7d1ceed1303b in KSelectAction::removeAllActions() () from /lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5 #11 0x7d1ce42e56b1 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #12 0x7d1ce42dd060 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #13 0x7d1ce413061c in Okular::Document::setViewport(Okular::DocumentViewport const&, Okular::DocumentObserver*, bool, bool) () from /lib/x86_64-linux-gnu/libOkular5Core.so.11 #14 0x7d1ce42f4478 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #15 0x7d1ced912e16 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7d1cee66b0f0 in QAbstractSlider::valueChanged(int) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7d1cee66b8e3 in QAbstractSlider::setValue(int) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7d1cee6656bf in QAbstractScrollArea::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7d1ced8d7e82 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7d1cee56bd35 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7d1ced8d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7d1cee92c606 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7d1cee92d265 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7d1ced6c0498 in QAbstractAnimation::setCurrentTime(int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7d1ced6c0633 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7d1ced6beddb in QUnifiedTimer::updateAnimationTimers(long long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7d1ced6c0d61 in QAnimationDriver::advanceAnimation(long long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7d1ced90624b in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7d1cee56bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7d1ced8d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7d1ced9345ab in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7d1ced934f11 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7d1cebf145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7d1cebf73717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7d1cebf13a53 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7d1ced935279 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7d1ced8d6a7b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7d1ced8df3e8 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x60835372bd1d in ?? () #40 0x7d1cece2a1ca in __libc_start_call_main (main=main@entry=0x60835372a800, argc=argc@entry=2, argv=argv@entry=0x7ffe51e68db8) at ../sysdeps/nptl/libc_start_call_main.h:58 #41 0x7d1cece2a28b in __libc_start_mai
[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.
[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] 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 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 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 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 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 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.
[kdevelop] [Bug 348915] Add Git Keyboard Shortcuts
https://bugs.kde.org/show_bug.cgi?id=348915 Aditya Rakhecha changed: What|Removed |Added CC||dashingaditya.rakhecha@gmai ||l.com --- Comment #2 from Aditya Rakhecha --- hello Michael I am interested in this bug and project can you please let me know where to start? :) -- 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.
[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.
[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.
[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.
[Breeze] [Bug 386541] New: Broken Activity, Add Widgets, Task Switcher Panel
https://bugs.kde.org/show_bug.cgi?id=386541 Bug ID: 386541 Summary: Broken Activity, Add Widgets, Task Switcher Panel Product: Breeze Version: 5.11.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: adi10...@gmail.com Target Milestone: --- Created attachment 108709 --> https://bugs.kde.org/attachment.cgi?id=108709&action=edit Contains Screenshots Hi There, I'm Aditya Shakya. I'm Using Kde Neon Since It's 5.9 Release And Also Uses Kde/Plasma Desktop Almost on Every Distro, It's My Fav Desktop Ever. But, Since It's 5.10 Release, I've Noticed A Broken Style In Breeze For Activities Panel, Add Widgets Panel And Task Switcher Panel (Broken At Bottom - Screenshot Attatched). I Thought it'll Be Fixed, But Still Not... So, I Guess You Guys Can Fix It Now, Thanks!al -- 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.
[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 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 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 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.
[plasmashell] [Bug 374394] New: plasma crashed while typing in launcher
https://bugs.kde.org/show_bug.cgi?id=374394 Bug ID: 374394 Summary: plasma crashed while typing in launcher Product: plasmashell Version: 5.8.4 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: basename-kdeb...@yahoo.in CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.9.0-0-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: I was typing in the launcher, specifically the word "battery" and while typing it, it crashed. It happened again when I typed "ba" once, but it doesn't seemed to happen everytime. Nither can I verify that it has to do something with this specific word, it's likely that there is no relation between the word and the crash. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8daacd6800 (LWP 780))] Thread 18 (Thread 0x7f8cadaea700 (LWP 1575)): #0 0x7f8d97659303 in pa_pstream_unref () at /usr/lib/pulseaudio/libpulsecommon-9.0.so #1 0x7f8d97659843 in () at /usr/lib/pulseaudio/libpulsecommon-9.0.so #2 0x7f8d9765a0aa in () at /usr/lib/pulseaudio/libpulsecommon-9.0.so #3 0x7f8d97ccab9c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0 #4 0x7f8d97ccaf9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #5 0x7f8d97ccb040 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #6 0x7f8d97cd9069 in () at /usr/lib/libpulse.so.0 #7 0x7f8d97669ed8 in () at /usr/lib/pulseaudio/libpulsecommon-9.0.so #8 0x7f8da3be4454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f8da43ea7df in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f8caed43700 (LWP 1574)): #0 0x7f8da43e148d in poll () at /usr/lib/libc.so.6 #1 0x7f8d9f6a3786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f8d9f6a389c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f8da4d0373b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f8da4cad24a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f8da4ad00f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f8da7e332d5 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f8da4ad4d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7f8da3be4454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f8da43ea7df in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f8ca700 (LWP 1216)): #0 0x7f8da3bea10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8da4ad5c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f8ce9d4b1c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f8ce9d4f988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f8ce9d4a263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f8ce9d4f9e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f8ce9d4a263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f8ce9d4f9e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f8ce9d4a263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f8ce9d4d1f9 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f8da4ad4d78 in () at /usr/lib/libQt5Core.so.5 #11 0x7f8da3be4454 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f8da43ea7df in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f8cccf3f700 (LWP 1215)): #0 0x7f8da3bea10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f8da4ad5c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f8ce9d4b1c0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f8ce9d4f988 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f8ce9d4a263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f8ce9d4f9e2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f8ce9d4a263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f8ce9d4d1f9 in ThreadWeaver::Thread::run() () at /usr/lib
[kde] [Bug 468684] New: KDE Plasma Sound Settings and Widgets don't show all devices in ALSA Mixer
https://bugs.kde.org/show_bug.cgi?id=468684 Bug ID: 468684 Summary: KDE Plasma Sound Settings and Widgets don't show all devices in ALSA Mixer Classification: I don't know Product: kde Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tarun.adi...@hotmail.com Target Milestone: --- SUMMARY - The System Settings in KDE plasma (and in extension, the Sound widget) don't show all the active sound devices and don't show all possible configurations. - I thought I had a problem with my devices, but when I opened ALSAMIXER, I saw all the connected sound devices that were "missing" from the KDE Plasma sound settings page. - While I totally understand that the page doesn't show the many unconnected sound ports on my tower (like S/PDIF, Rear Mic, Surround, Center) which are not in use (but still shown in alsamixer), the setting page also refuses to show the speakers while my headphones are connected in. - This behaviour may be obvious on things like a laptop/phone where connecting headphones mutes the speakers and only provides option for controlling headphones, but on a desktop it is irritating having to UNPLUG my headphone in order to use the speaker and even control it. - I would rather simply want the option to CHOOSE ONE OR MORE CONNECTED devices (like speaker AND headphones) to playback from (at the same time, if I want to). - I had to look in multiple places before realizing that there is a setting called "auto-mute mode" in Alsamixer which needs to be disabled in order to playback from multiple devices. The settings page can also expose this as a toggle. - HONESTLY, the alsamixer TUI is pretty well designed. The Audio settings page in KDE plasma can be modelled after it, while the "taskbar" widget can remain a bit simpler to use. PS: Sorry, I didn't know how to separate the above into "steps to reproduce", "expected result", "observed result", as it involves more than just a bug report. It is a bit of a bug and a bit of a feature request. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel: 6.2.6 ADDITIONAL INFORMATION Motherboard: http://www.gigabyte.com/products/product-page.aspx?pid=5497#ov (this has speaker output) Frontpanel on tower has headphones output -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 459411] KDE Connect freezes system after incoming call on android phone
https://bugs.kde.org/show_bug.cgi?id=459411 Tarun Aditya Thurlapati changed: What|Removed |Added CC||tarun.adi...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 459411] KDE Connect freezes system after incoming call on android phone
https://bugs.kde.org/show_bug.cgi?id=459411 --- Comment #1 from Tarun Aditya Thurlapati --- Created attachment 159289 --> https://bugs.kde.org/attachment.cgi?id=159289&action=edit New crash information added by DrKonqi kdeconnectd (22.04.3) using Qt 5.15.3 The same as described in the previous comment/report happened. I'm not sure about this, but I have never faced this issue before, until I enabled a notification alarm sound for specifically when a call comes in; so that may be related. Right now, KDE Connect notifies once (alarm plays and media stops playing) when the call starts to come in (and KDE Connect never crashes here). When I miss the call (as I almost always do), KDE Connect sends another notification (and the alarm gets played again and media pauses again) telling me that I missed the call. **THIS** is when KDE Connect _sometimes_ crashes. Another instance where it crashes is when a HUGE amount of notifications come in. KDE Connect never crashes before, but after I enbabled a notification alarm (sound), it sometimes crashes. This could be a coincidence, or it might be related. Just to clarify - the huge amount of notifications might come in in 2 cases: - when KDE Connect first connect to my phone, showing me all notifications that have plied up - my calendar app shows about 100 or more todos (that have accumulated over time) at an exact time of each day. -- Backtrace (Reduced): #4 0x7fa9ce0b009d in KNotification::id() () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 [...] #7 0x7fa9ce0abba3 in KNotificationPlugin::finished(KNotification*) () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #8 0x7fa9ccae741e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa9cd76c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fa9ccab9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481662] New: Plasmashell often crashes when an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=481662 Bug ID: 481662 Summary: Plasmashell often crashes when an external monitor is connected Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tarun.adi...@hotmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.3 Frameworks Version: 5.104.0 Operating System: Linux 6.5.0-15-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: When I connect an external monitor to my laptop, plasmashell almost always crashes. Disconnecting from an external monitor doesn't show any problem. I should add that I'm using Ubuntu 22.04 with `kubuntu-backports-extra` ppa The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f4af227d275 in QScopedPointer >::operator->() const (this=0x149) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qscopedpointer.h:118 #5 qGetPtrHelper > const>(QScopedPointer > const&) (ptr=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1143 #6 QQuickWindow::d_func() const (this=0x141) at items/qquickwindow.h:79 #7 QQuickWindow::mouseGrabberItem() const (this=0x141) at items/qquickwindow.cpp:1733 #8 0x7f4af227faef in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) (this=0x557c967a1da0, grabber=grabber@entry=0x557c96840ab0, mouse=mouse@entry=true, touch=touch@entry=true) at items/qquickwindow.cpp:1002 #9 0x7f4af225ee56 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557c96837c70, newEffectiveVisible=) at items/qquickitem.cpp:6075 #10 0x7f4af225ee8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557c96840780, newEffectiveVisible=) at items/qquickitem.cpp:6080 #11 0x7f4af225ee8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557c9686d3e0, newEffectiveVisible=) at items/qquickitem.cpp:6080 #12 0x7f4af225ee8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557c9686a440, newEffectiveVisible=) at items/qquickitem.cpp:6080 #13 0x7f4af225ee8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557c949b9740, newEffectiveVisible=) at items/qquickitem.cpp:6080 #14 0x7f4af225ee8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557c96748640, newEffectiveVisible=) at items/qquickitem.cpp:6080 #15 0x7f4af225ee8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557c95f45b80, newEffectiveVisible=) at items/qquickitem.cpp:6080 #16 0x7f4af225ee8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=0x557c96706250, newEffectiveVisible=) at items/qquickitem.cpp:6080 #17 0x7f4af225ee8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) (this=this@entry=0x557c94969110, newEffectiveVisible=) at items/qquickitem.cpp:6080 #18 0x7f4af225efb7 in QQuickItemPrivate::setVisible(bool) (this=0x557c94969110, visible=) at items/qquickitem.cpp:5983 #19 0x7f4af226c653 in QQuickItem::qt_metacall(QMetaObject::Call, int, void**) (this=0x557c94970ac0, _c=QMetaObject::WriteProperty, _id=11, _a=0x7fff6f299900) at .moc/moc_qquickitem.cpp:1048 #20 0x7f4af2ba406a in PlasmaQuick::AppletQuickItem::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libKF5PlasmaQuick.so.5 #21 0x7f4ae0328aea in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #22 0x7f4ae033655a in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #23 0x7f4af1c89e5f in QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (flags=..., value=, target=, this=) at ../../include/QtQml/5.15.3/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:379 #24 QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) (object=object@entry=0x557c94970ac0, property=..., value=..., context=, flags=..., flags@entry=...) at qml/qqmlproperty.cpp:1292 #25 0x7f4af1bad651 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) (engine=0x557c947e92a0, object=0x557c94970ac0, property=0x7f4a7c0a2f98, value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:120 #26 0x7f4af1badec2 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) (value=..., revisionMode=QV4::QObjectWrapper::IgnoreRevision, name=, object=0x557c94970ac0, qmlContext=, engine=0x557c947e92a0) at jsruntime/qv4
