[kstars] [Bug 475499] Confusing behavior when setting Az/Alt coordinates manually
https://bugs.kde.org/show_bug.cgi?id=475499 Brett changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Brett --- My merge request was accepted. I've tested on Version 3.6.8 Stable and it works. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 475499] Confusing behavior when setting Az/Alt coordinates manually
https://bugs.kde.org/show_bug.cgi?id=475499 Brett changed: What|Removed |Added Version Fixed In||3.6.8 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 475499] New: Confusing behavior when setting Az/Alt coordinates manually
https://bugs.kde.org/show_bug.cgi?id=475499 Bug ID: 475499 Summary: Confusing behavior when setting Az/Alt coordinates manually Classification: Applications Product: kstars Version: 3.6.7 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: bgott...@gmail.com Target Milestone: --- SUMMARY If there are valid values in the RA/Dec tab of the "Set Coordinates Manually" dialog it will *always* use those ones, even when the Az/Alt tab has focus when the "OK" button is clicked. Only if the RA/Dec values can’t be parsed correctly (e.g., because they are blank) will it use the Az/Alt tab values. This is a very unintuitive behavior; I had to inspect the source code to figure out how to use Az/Alt coordinates. STEPS TO REPRODUCE 1. Open Pointing > Set Coordinates Manually 2. Note or set the RA/Dec coordinates 3. Switch to Az/Alt tab 4. Set Az/Alt coordinates (choose something that is obviously a different location in the sky from the RA/Dec coordinates) 5. Click OK OBSERVED RESULT The display is centered at the RA/Dec coordinates (even though that tab was not active when "OK" was clicked). EXPECTED RESULT The display is centered at the Az/Alt coordinates entered. SOFTWARE/OS VERSIONS Linux Mint 21.2 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I think the check at this if statement is not the best condition to check: https://invent.kde.org/education/kstars/-/blob/master/kstars/dialogs/focusdialog.cpp#L123 If I understand correctly, that condition just checks that the values in the RA and Dec text boxes were parseable. So the code path that uses the Az/Alt coordinates is only executed if the RA and Dec values could not be parsed successfully. It would be more intuitive if the if statement checked which tab in the dialog is active when the user clicks OK. I'm not fluent in KDE / Qt GUI programming but if desired I can try to come up with a fix. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 475499] Confusing behavior when setting Az/Alt coordinates manually
https://bugs.kde.org/show_bug.cgi?id=475499 --- Comment #1 from Brett --- Merge request: https://invent.kde.org/education/kstars/-/merge_requests/1021 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407798] New: Kdenlive crashes after loading a file with 'invalid transitions'
https://bugs.kde.org/show_bug.cgi?id=407798 Bug ID: 407798 Summary: Kdenlive crashes after loading a file with 'invalid transitions' Product: kdenlive Version: 19.04.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: daloo...@gmail.com Target Milestone: --- Created attachment 120221 --> https://bugs.kde.org/attachment.cgi?id=120221&action=edit kdenlive file with invalid transition that causes crash SUMMARY I was working on a project that now won't open anymore due to 'invalid transitions'. There is no way to open a kdenlive project without disabling transitions, so the program crashes. STEPS TO REPRODUCE 1. Open the Kdenlive attached file 2. 3. OBSERVED RESULT Error message regarding invalid transition on track 5 and then crash EXPECTED RESULT Kdenlive removes the invalid transition without crashing SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 4.15 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407798] Kdenlive crashes after loading a file with 'invalid transitions'
https://bugs.kde.org/show_bug.cgi?id=407798 --- Comment #2 from Brett --- Looks good. By the way, in the future if I find another bug should I open an issue directly on GitLab instead of posting on this forum? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407798] Kdenlive crashes after loading a file with 'invalid transitions'
https://bugs.kde.org/show_bug.cgi?id=407798 --- Comment #4 from Brett --- OK sounds good! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408298] New: Kdenlive crashes after loading old project
https://bugs.kde.org/show_bug.cgi?id=408298 Bug ID: 408298 Summary: Kdenlive crashes after loading old project Product: kdenlive Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: daloo...@gmail.com Target Milestone: --- Created attachment 120568 --> https://bugs.kde.org/attachment.cgi?id=120568&action=edit old project which crashes kdenlive when using substitute clips SUMMARY Kdenlive is normally backwards compatible in my experience, but Kdenlive crashes when loading this old project file if I don't load all of the missing clips. While attempting to load this project, if you select 'use substitute clips" to get past the missing clip dialog box, the program will crash before loading the file. STEPS TO REPRODUCE 1. Load the attached Kdenlive project file 2. Try "use substitute clips" when loading up the project OBSERVED RESULT Experience a KDenlive crash EXPECTED RESULT Kdenlive opens the project normally with substitute clips SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Inserted clip in track 132 at 7240 Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::save: Painter not active QPainter::setClipRect: Painter not active QPainter::setWorldTransform: Painter not active QPainter::opacity: Painter not active QPainter::worldTransform: Painter not active QPainter::setWorldTransform: Painter not active QPainter::save: Painter not active QPainter::setOpacity: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::restore: Unbalanced save/restore QPainter::setWorldTransform: Painter not active QPainter::setOpacity: Painter not active QPainter::restore: Unbalanced save/restore QPainter::end: Painter not active, aborted ASSERT: "mImg == qImg->constBits()" in file common.cpp, line 63 QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::save: Painter not active Abandon (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408298] Kdenlive crashes after loading old project
https://bugs.kde.org/show_bug.cgi?id=408298 --- Comment #2 from Brett --- I didn't know about the nightly builds. Thank you for the link. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414646] New: Kdenlive in Windows crashes when opening a project created under a different Locale
https://bugs.kde.org/show_bug.cgi?id=414646 Bug ID: 414646 Summary: Kdenlive in Windows crashes when opening a project created under a different Locale Product: kdenlive Version: 19.08.3 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: daloo...@gmail.com Target Milestone: --- SUMMARY Kdenlive in Windows shows a visual C++ Runtime error and crashes when attempting to open a project that was created and saved under a different locale. The issue seems to be due to the fact that some locales use a comma instead of a period in their timestamps. STEPS TO REPRODUCE 1. Create a project with a machine using the locale fr_CA and save it. See http://txt.do/1oxnn for an example project. 2. Move to a machine running Windows and with the locale en_US. Attempt to open the previous project. OBSERVED RESULT Crash: Runtime Error! This program has requested yadda yadda yadda... EXPECTED RESULT Kdenlive gives a warning about the project being created in a different locale and offers to save it in the current locale. SOFTWARE/OS VERSIONS Windows: 8 macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Here is a workaround: 1. Open the project in a text editor 2. Change LC_NUMERIC="fr_CA.UTF-8" to LC_NUMERIC="en_US" 3. Use find and replace to transform all of the commas into periods in the timestamps. For example: in the original file now becomes this: 4. The project will now open properly without crashing Kdenlive -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 414646] Kdenlive in Windows crashes when opening a project created under a different Locale
https://bugs.kde.org/show_bug.cgi?id=414646 --- Comment #1 from Brett --- Relevant forum discussion: https://forum.kde.org/viewtopic.php?f=265&t=163455 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 400989] New: Add keywords to .desktop file.
https://bugs.kde.org/show_bug.cgi?id=400989 Bug ID: 400989 Summary: Add keywords to .desktop file. Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: b...@i--b.com Target Milestone: --- The .desktop file for Spectacle doesn't have a "Keywords" entry. It would probably do well to provide Spectacle as a result when users search for 'Snipping Tool' as that's the Windows variant. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 395938] New: Typing and erasing 3d in effects search crashes flatpak Kdenlive 18.04.2
https://bugs.kde.org/show_bug.cgi?id=395938 Bug ID: 395938 Summary: Typing and erasing 3d in effects search crashes flatpak Kdenlive 18.04.2 Product: kdenlive Version: 18.04.2 Platform: Flatpak OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: daloo...@gmail.com Target Milestone: --- If I search for 3d under the effects tab in the flatpak'd version of Kdenlive 18.04.2, the effect Hqdn3d shows up. However if I then erase the letter d and then the number 3 by typing backspace, Kdenlive will crash. This bug doesn't seem to be present on the 18.04.1 App Image, only the 18.04.2 flatpak. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380475] New: Dctdnoiz effect crashes Kdenlive
https://bugs.kde.org/show_bug.cgi?id=380475 Bug ID: 380475 Summary: Dctdnoiz effect crashes Kdenlive Product: kdenlive Version: 17.04.1 Platform: Mint (Debian based) OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: daloo...@gmail.com Target Milestone: --- The Dctdnoiz effect under the Misc effects in Kdenlive is very unstable and crashes the program. All one needs to do is to select some values for av.sigma and av.s then quickly select some random values with the mouse on av.overlap (click about 5 or 6 times quickly to select values between 1 and 12 or so). This will crash Kdenlive 17.04.01 running on Linux Mint. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 400989] Add keywords to .desktop file.
https://bugs.kde.org/show_bug.cgi?id=400989 Brett changed: What|Removed |Added Status|CONFIRMED |ASSIGNED Assignee|m...@baloneygeek.com |b...@i--b.com --- Comment #1 from Brett --- Patch submitted at https://phabricator.kde.org/D17396 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467745] New: Subtitles: cannot use both "Opaque background" and "Custom Position" at the same time
https://bugs.kde.org/show_bug.cgi?id=467745 Bug ID: 467745 Summary: Subtitles: cannot use both "Opaque background" and "Custom Position" at the same time Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: blkel...@comcast.net 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 *** Under subtitle style options, when "Opaque background" and "Custom Position" are both checked, instead of seeing the combined effect of both options, *neither* option has any effect. Each option is effective on its own, just not together. STEPS TO REPRODUCE 1. Add a subtitle 2. Under the subtitle's style options, check the box for "Custom Position" and set the position to "Center" 3. Check the box for "Opaque background" OBSERVED RESULT Notice that the subtitle is shown *without* an opaque background, and its position has returned to the default of bottom center. EXPECTED RESULT The subtitle should both have an opaque background and be in the center position. SOFTWARE/OS VERSIONS I'm using the Flatpak version of the application. It reports the following: KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 (built against 5.15.8) MLT Version: 7.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467745] Subtitles: cannot use both "Opaque background" and "Custom Position" at the same time
https://bugs.kde.org/show_bug.cgi?id=467745 --- Comment #2 from Brett Keller --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481148] New: Main Enter key not responsive at login screen
https://bugs.kde.org/show_bug.cgi?id=481148 Bug ID: 481148 Summary: Main Enter key not responsive at login screen Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: cgho...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Upon loging in the KDE Neon Plasma version 6.0.80 the main Enter key is unresponsive. It works perfectly fine after logging in. Using the Enter key on the Numpad works fine. 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. every login session 2. Enter key works as normal once logged in. OBSERVED RESULT Enter key on main section of keyboard not sending enter signaL to system. Regular keys to enter my password work fine. Only the Enter key on the numpad will result in me beina able to login to plasma. EXPECTED RESULT This is not an intermittent result, it happens everytimer I login in, the Enter key issue and the HDMI connected monitor reverting back to a 1024x768 resolution SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Unstable Edition (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Possibly related (already reported) on my dual 49" widescreen displays (NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2) the HDMI connected monitor is sometimes not detected(seems to bge fixed lately), and always reverts back to 1024x768 resolution from 5120x1440. I'm logging in with X11 and I have saved Xorg.conf to etc/X11 but not sure its being used.(nvidia-settings asks for root password when saving xorg.conf) Keryboard layout is standard US keyboard. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481148] Main Enter key not responsive at login screen
https://bugs.kde.org/show_bug.cgi?id=481148 Brett Morgan changed: What|Removed |Added CC||cgho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405284] baloo_file_extractor crashes in Baloo::DocumentDB::del()
https://bugs.kde.org/show_bug.cgi?id=405284 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464223] New: Discover Notifier segfaults when automatic updates are installed
https://bugs.kde.org/show_bug.cgi?id=464223 Bug ID: 464223 Summary: Discover Notifier segfaults when automatic updates are installed Classification: Applications Product: Discover Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: plasma-b...@kde.org Reporter: blkel...@comcast.net CC: aleix...@kde.org Target Milestone: --- Application: DiscoverNotifier (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-57-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Nothing -- my session was idle. I have automatic updates configured on Kubuntu 22.04, and looking back through the logs, I could see that PackageKit was installing updates in the background when Discover Notifier crashed. Once Discover Notifier has crashed, I no longer receive any automatic updates until I either restart Notifier again manually or I reboot, so this bug effectively breaks automatic updates for me. I'm seeing the problem on at least two different machines, both of which are clean installs of 22.04 where not much customization has been done. In case it helps, here are the PackageKit logs from the systemd journal: ``` Jan 12 17:41:59 kubuntu2204-test PackageKit[1316]: get-updates transaction /267_dccdaacd from uid 1000 finished with success after 683ms Jan 12 17:42:00 kubuntu2204-test PackageKit[1316]: new update-packages transaction /268_cbeb scheduled from uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package linux-headers-5.15.0-58;5.15.0-58.64;all;+auto:ubuntu-jammy-updates-main was installing for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package linux-headers-5.15.0-58-generic;5.15.0-58.64;amd64;+auto:ubuntu-jammy-updates-main was installing for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package linux-image-5.15.0-58-generic;5.15.0-58.64;amd64;+auto:ubuntu-jammy-updates-main was installing for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package linux-modules-5.15.0-58-generic;5.15.0-58.64;amd64;+auto:ubuntu-jammy-updates-main was installing for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package linux-modules-extra-5.15.0-58-generic;5.15.0-58.64;amd64;+auto:ubuntu-jammy-updates-main was installing for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package alsa-ucm-conf;1.2.6.3-1ubuntu1.1;all;ubuntu-jammy-updates-main was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package apport;2.20.11-0ubuntu82.3;all;ubuntu-jammy-updates-main was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package apport-kde;2.20.11-0ubuntu82.3;all;ubuntu-jammy-updates-universe was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package bluedevil;4:5.24.7-0ubuntu0.1;amd64;ubuntu-jammy-updates-universe was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package distro-info-data;0.52ubuntu0.2;all;ubuntu-jammy-updates-main was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package firmware-sof-signed;2.0-1ubuntu4;all;ubuntu-jammy-updates-restricted was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package fwupd;1.7.9-1~22.04.1;amd64;ubuntu-jammy-updates-main was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package gdb;12.1-0ubuntu1~22.04;amd64;ubuntu-jammy-updates-main was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package gir1.2-gdkpixbuf-2.0;2.42.8+dfsg-1ubuntu0.2;amd64;ubuntu-jammy-updates-main was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package initramfs-tools;0.140ubuntu13.1;all;ubuntu-jammy-updates-main was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package initramfs-tools-bin;0.140ubuntu13.1;amd64;ubuntu-jammy-updates-main was updating for uid 1000 Jan 12 17:42:01 kubuntu2204-test PackageKit[1316]: in /268_cbeb for update-packages package initramfs-tools-core;0.140ubuntu13.1;all;ubuntu-jammy-upda
[Discover] [Bug 464223] Discover Notifier segfaults when automatic updates are installed
https://bugs.kde.org/show_bug.cgi?id=464223 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367456] Plasma shell crashes whiel attempting to switch applications using Icons-only Task Manager
https://bugs.kde.org/show_bug.cgi?id=367456 Brett Keller changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #3 from Brett Keller --- Oh, wow. Hello there, Justin! I reported this bug over four years ago, never heard any follow up until now, and over that time I had completely forgotten about it. I can't really verify anything about the current state of this bug because the particular installation I was running at the time that I reported it was long ago given a gold watch and retired to a small cottage up north where it likes to spend its time fishing. I don't have any systems where I run plasmashell 5.5.x anymore. The earliest version I still have running anywhere is 5.12.x, and I do use the Icons-only Task Manager on that. I haven't encountered any problems like this bug on that system, so... I guess this was fixed? Maybe? Sure, let's call it fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 357206] baloo_file crashes in Baloo::PostingDB::get()
https://bugs.kde.org/show_bug.cgi?id=357206 --- Comment #32 from Brett Keller --- Created attachment 119510 --> https://bugs.kde.org/attachment.cgi?id=119510&action=edit New crash information added by DrKonqi baloo_file (5.44.0) using Qt 5.9.5 - What I was doing when the application crashed: Happens immediately after login. I don't really even have that many files on this system to index: $ balooctl indexSize Actual Size: 12.02 MiB Expected Size: 6.77 MiB PostingDB: 1.18 MiB17.426 % PosistionDB: 1.39 MiB20.542 % DocTerms: 1.05 MiB15.522 % DocFilenameTerms: 1.03 MiB15.176 % DocXattrTerms:0 B 0.000 % IdTree: 168.00 KiB 2.424 % IdFileName: 924.00 KiB13.329 % DocTime: 644.00 KiB 9.290 % DocData:0 B 0.000 % ContentIndexingDB:0 B 0.000 % FailedIdsDB:0 B 0.000 % MTimeDB: 220.00 KiB 3.174 % -- Backtrace (Reduced): #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:427 #7 0x7f42e75a0973 in memcpy (__len=18446744073126832784, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f42dd446a47, arr=...) at ./src/codecs/postingcodec.cpp:42 #9 0x7f42e75923e4 in Baloo::PostingDB::get (this=this@entry=0x7f42dd446b30, term=...) at ./src/engine/postingdb.cpp:100 #10 0x7f42e759e060 in Baloo::WriteTransaction::commit (this=0x7f02d0003400) at ./src/engine/writetransaction.cpp:259 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 357206] baloo_file crashes in Baloo::PostingDB::get()
https://bugs.kde.org/show_bug.cgi?id=357206 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 372655] baloo_file crashes in Baloo::IdFilenameDB::del()
https://bugs.kde.org/show_bug.cgi?id=372655 --- Comment #11 from Brett Keller --- Created attachment 121455 --> https://bugs.kde.org/attachment.cgi?id=121455&action=edit New crash information added by DrKonqi baloo_file (5.44.0) using Qt 5.9.5 - What I was doing when the application crashed: This happens just about every time I boot up and login to a Plasma desktop session, right after login before I even click on anything. -- Backtrace (Reduced): #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f8f221ce801 in __GI_abort () at abort.c:79 #8 0x7f8f1ff8b932 in mdb_assert_fail (env=0x55b1261bc5c0, expr_txt=expr_txt@entry=0x7f8f1ff8d22f "rc == 0", func=func@entry=0x7f8f1ff8db78 <__func__.7016> "mdb_page_dirty", line=line@entry=2121, file=0x7f8f1ff8d210 "mdb.c") at mdb.c:1536 #9 0x7f8f1ff807b5 in mdb_page_dirty (txn=0x55b1261b81e0, mp=) at mdb.c:2121 #10 0x7f8f1ff819bb in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7ffc8530a5c8, mc=) at mdb.c:2302 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 372655] baloo_file crashes in Baloo::IdFilenameDB::del()
https://bugs.kde.org/show_bug.cgi?id=372655 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 405977] New: Spectacle snap crashes on startup
https://bugs.kde.org/show_bug.cgi?id=405977 Bug ID: 405977 Summary: Spectacle snap crashes on startup Product: neon Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Snaps Assignee: sit...@kde.org Reporter: blkel...@comcast.net CC: neon-b...@kde.org Target Milestone: --- SUMMARY I tried installing and using the Spectacle snap on Kubuntu 18.04 (I wanted to try the latest version), but it crashes on startup due to a missing library. STEPS TO REPRODUCE 1. $ sudo snap install spectacle 2. $ snap run spectacle OBSERVED RESULT "spectacle: error while loading shared libraries: libxcb-cursor.so.0: cannot open shared object file: No such file or directory" EXPECTED RESULT Launches Spectacle. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION $ snap info spectacle name: spectacle summary: Screenshot capture utility, replaces KSnapshot publisher: KDE✓ contact: https://bugs.kde.org/enter_bug.cgi?product=neon&component=Snaps license: unset description: | Spectacle captures images of the screen. It can capture the whole screen, a specified region, an individual window, or only part of a window. commands: - spectacle snap-id: tg12Jrs93ndp40AEQnlbuMbtmVJ6ZPpk tracking: stable refresh-date: today at 16:20 CDT channels: stable:18.12.32019-03-26 (12) 299kB - candidate: 18.12.32019-03-26 (12) 299kB - beta: ↑ edge: master+aa9600c 2019-03-26 (11) 180kB - installed: 18.12.3 (12) 299kB - -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388919] Plasma crashed after a modification in systray settings.
https://bugs.kde.org/show_bug.cgi?id=388919 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 Brett Gardner changed: What|Removed |Added CC||br...@gardnerfamily.id.au --- Comment #40 from Brett Gardner --- I'm also seeing this under 5.17.5. I tried to work around it by having a service which would randomly copy an image from my actual image directory into the directory I configured the slideshow wallpaper to source from, but ran into multiple other bugs. 1. If I purge the existing files from the directory, the slideshow plugin will go to a black screen with the error "file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationContainmentAppearance.qml:85:9: Unable to assign [undefined] to QQmlListProperty" 2. If I configure slideshow's order to "Date modified, newest first" I get strange behaviour, When I click "Apply", it correctly shows the newest image, but as soon as I close the config window, it reverts to the previous image, with no output in the journal -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 396218] Crash on log-in
https://bugs.kde.org/show_bug.cgi?id=396218 --- Comment #2 from Brett Keller --- Created attachment 114363 --> https://bugs.kde.org/attachment.cgi?id=114363&action=edit New crash information added by DrKonqi baloo_file (5.44.0) using Qt 5.9.5 - What I was doing when the application crashed: Noticed this just after untarring a file via Dolphin's context menu, but this was not long after login, so it may have simply been triggered by login. -- Backtrace (Reduced): #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370 #7 0x7f4dbd4d7973 in memcpy (__len=2050, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at ./src/codecs/postingcodec.cpp:42 #9 0x7f4dbd4c93e4 in Baloo::PostingDB::get (this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100 #10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160) at ./src/engine/writetransaction.cpp:259 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 396218] Crash on log-in
https://bugs.kde.org/show_bug.cgi?id=396218 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 396218] Crash on log-in
https://bugs.kde.org/show_bug.cgi?id=396218 --- Comment #2 from Brett Keller --- Created attachment 114363 --> https://bugs.kde.org/attachment.cgi?id=114363&action=edit New crash information added by DrKonqi baloo_file (5.44.0) using Qt 5.9.5 - What I was doing when the application crashed: Noticed this just after untarring a file via Dolphin's context menu, but this was not long after login, so it may have simply been triggered by login. -- Backtrace (Reduced): #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370 #7 0x7f4dbd4d7973 in memcpy (__len=2050, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at ./src/codecs/postingcodec.cpp:42 #9 0x7f4dbd4c93e4 in Baloo::PostingDB::get (this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100 #10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160) at ./src/engine/writetransaction.cpp:259 --- Comment #3 from Brett Keller --- Created attachment 114365 --> https://bugs.kde.org/attachment.cgi?id=114365&action=edit New crash information added by DrKonqi baloo_file (5.44.0) using Qt 5.9.5 - What I was doing when the application crashed: Noticed this just after untarring a file via Dolphin's context menu, but this was not long after login, so it may have simply been triggered by login. -- Backtrace (Reduced): #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:370 #7 0x7f4dbd4d7973 in memcpy (__len=2050, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f4db3377a77, arr=...) at ./src/codecs/postingcodec.cpp:42 #9 0x7f4dbd4c93e4 in Baloo::PostingDB::get (this=this@entry=0x7f4db3377b60, term=...) at ./src/engine/postingdb.cpp:100 #10 0x7f4dbd4d5060 in Baloo::WriteTransaction::commit (this=0x7f4dac035160) at ./src/engine/writetransaction.cpp:259 -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 385306] K3b - System Configuration Problem
https://bugs.kde.org/show_bug.cgi?id=385306 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net --- Comment #1 from Brett Keller --- I can confirm this on my system as well. Installing wodim fixed the problem. Please add wodim as a dependency to the k3b package. $ lsb_release -a No LSB modules are available. Distributor ID: neon Description:KDE neon LTS User Edition 5.8 Release:16.04 Codename: xenial $ k3b --version k3b 18.03.70 $ apt-cache policy k3b k3b: Installed: 17.11.0+p16.04+git20171219.1130-0 Candidate: 17.11.0+p16.04+git20171219.1130-0 Version table: *** 17.11.0+p16.04+git20171219.1130-0 500 500 http://archive.neon.kde.org/user/lts xenial/main amd64 Packages 100 /var/lib/dpkg/status 17.08.0+p16.04+git20171219.0023-0 500 500 http://archive.neon.kde.org/user/lts xenial/main amd64 Packages 17.08.0+p16.04+git20171210.0026-0 500 500 http://archive.neon.kde.org/user/lts xenial/main amd64 Packages 17.08.0+p16.04+git20171209.0025-0 500 500 http://archive.neon.kde.org/user/lts xenial/main amd64 Packages 2.0.3-0ubuntu5 500 500 http://mirrors.gigenet.com/ubuntuarchive xenial/universe amd64 Packages -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 381059] New: Discover crash
https://bugs.kde.org/show_bug.cgi?id=381059 Bug ID: 381059 Summary: Discover crash Product: Discover Version: 5.10.0 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: mrbrettst...@gmail.com Target Milestone: --- Application: plasma-discover (5.10.0) Qt Version: 5.8.0 Frameworks Version: 5.34.0 Operating System: Linux 4.9.30-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed:Using Chromium and Konsole. Discover crashes reguardless of what I'm doing. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f87332747c0 (LWP 21799))] Thread 73 (Thread 0x7f866bfdf700 (LWP 21886)): #0 0x7f872e9dc2bd in poll () at /usr/lib/libc.so.6 #1 0x7f872926b9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f872926bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f872f319f0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f872f2c13aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f872f0d944a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f872f0dde9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f872b1d8297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f872e9e625f in clone () at /usr/lib/libc.so.6 Thread 72 (Thread 0x7f866c7e0700 (LWP 21885)): #0 0x7f872e9dc2bd in poll () at /usr/lib/libc.so.6 #1 0x7f872926b9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f872926bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f872f319f0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f872f2c13aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f872f0d944a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f872f0dde9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f872b1d8297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f872e9e625f in clone () at /usr/lib/libc.so.6 Thread 71 (Thread 0x7f866cfe1700 (LWP 21884)): #0 0x7f872e9dc2bd in poll () at /usr/lib/libc.so.6 #1 0x7f872926b9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f872926bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f872f319f0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f872f2c13aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f872f0d944a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f872f0dde9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f872b1d8297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f872e9e625f in clone () at /usr/lib/libc.so.6 Thread 70 (Thread 0x7f866d7e2700 (LWP 21883)): #0 0x7f872e9dc2bd in poll () at /usr/lib/libc.so.6 #1 0x7f872926b9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f872926bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f872f319f0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f872f2c13aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f872f0d944a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f872f0dde9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f872b1d8297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f872e9e625f in clone () at /usr/lib/libc.so.6 Thread 69 (Thread 0x7f866dfe3700 (LWP 21882)): #0 0x7f872e9dc2bd in poll () at /usr/lib/libc.so.6 #1 0x7f872926b9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f872926bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f872f319f0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f872f2c13aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f872f0d944a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f872f0dde9c in () at /usr/lib/libQt5Core.so.5 #7 0x7f872b1d8297 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f872e9e625f in clone () at /usr/lib/libc.so.6 Thread 68 (Thread 0x7f866e7e4700 (LWP 21881)): #0 0x7f872e9dc2bd in poll () at /usr/lib/libc.so.6 #1 0x7f872926b9b6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f872926bacc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f872f319f0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f872f2c13aa in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f872f0d944a in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f872f0dde9c in () at /
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net --- Comment #8 from Brett Keller --- Seeing this as well on a fresh install of KDE Neon User LTS. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 369301] Muon doesn't find packages after installing a package
https://bugs.kde.org/show_bug.cgi?id=369301 Brett Keller changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 484712] SMB4K crashed when iPhone is connected on Fedora 40
https://bugs.kde.org/show_bug.cgi?id=484712 Brett Hagen changed: What|Removed |Added CC||hagen...@gmail.com --- Comment #5 from Brett Hagen --- This has happened to me as well. What traces could I include to help with this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367456] New: Plasma shell crashes whiel attempting to switch applications using Icons-only Task Manager
https://bugs.kde.org/show_bug.cgi?id=367456 Bug ID: 367456 Summary: Plasma shell crashes whiel attempting to switch applications using Icons-only Task Manager Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: blkel...@comcast.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-34-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Moved mouse cursor down to Icons-only Task Manager in my bottom panel in an attempt to change the active window, but before I can complete the action, Plasma crashes and restarts. This is occasionally reproducible, just enough to be annoying. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2bdc2938c0 (LWP 3284))] Thread 12 (Thread 0x7f2b0fdb8700 (LWP 3559)): #0 0x7f2bd69949cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2bd3771740 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7f2b0fdb7ac0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 0x7f2bd3771740 in g_wakeup_acknowledge (wakeup=0x7f2b1c002570) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gwakeup.c:210 #3 0x7f2bd372de84 in g_main_context_check (context=context@entry=0x7f2b08000990, max_priority=2147483647, fds=fds@entry=0x7f2b080048c0, n_fds=n_fds@entry=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3632 #4 0x7f2bd372e340 in g_main_context_iterate (context=context@entry=0x7f2b08000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3837 #5 0x7f2bd372e4ac in g_main_context_iteration (context=0x7f2b08000990, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #6 0x7f2bd72c5a9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2bd726cdea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2bd70898a4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2b122977d7 in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #10 0x7f2bd708e84e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2bd617b6fa in start_thread (arg=0x7f2b0fdb8700) at pthread_create.c:333 #12 0x7f2bd69a4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f2ba6131700 (LWP 3351)): #0 0x7f2bd69949cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f2bd3771740 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7f2ba6130a90, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 0x7f2bd3771740 in g_wakeup_acknowledge (wakeup=0x7f2ba0002780) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gwakeup.c:210 #3 0x7f2bd372de84 in g_main_context_check (context=context@entry=0x7f2b1c000990, max_priority=2147483647, fds=fds@entry=0x7f2b1c003120, n_fds=n_fds@entry=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3632 #4 0x7f2bd372e340 in g_main_context_iterate (context=context@entry=0x7f2b1c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3837 #5 0x7f2bd372e4ac in g_main_context_iteration (context=0x7f2b1c000990, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #6 0x7f2bd72c5a9b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2bd726cdea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2bd70898a4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2bda2b7ed6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f2bd708e84e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2bd617b6fa in start_thread (arg=0x7f2ba6131700) at pthread_create.c:333 #12 0x7f2bd69a4b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f2bacb13700 (LWP 3348)): #0 0x7f2bd61813a0 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2bdbcd6bd4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f2bdbcd6c19 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f2bd617b6fa in start_thread (arg=0x7f2bacb13700) at pthread_create.c:333 #4 0x7f2bd69a4b5d in clone () at ../sysdeps/unix/sysv/linux/x86
