[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.
[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.
[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.
[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
[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 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.
[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.
[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.
[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=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 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=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.
[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=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.
[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=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=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 --- Comment #2 from Brett Keller --- Created attachment 114363 --> https://bugs.kde.org/attachment.cgi?id=114363=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.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Brett Keller <blkel...@comcast.net> 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 <blkel...@comcast.net> changed: What|Removed |Added CC||blkel...@comcast.net --- Comment #1 from Brett Keller <blkel...@comcast.net> --- 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.
[muon] [Bug 369301] Muon doesn't find packages after installing a package
https://bugs.kde.org/show_bug.cgi?id=369301 Brett Keller <blkel...@comcast.net> changed: What|Removed |Added CC||blkel...@comcast.net -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376344] cant write to smb shares which has write access
https://bugs.kde.org/show_bug.cgi?id=376344 Brett Keller <blkel...@comcast.net> changed: What|Removed |Added CC||blkel...@comcast.net --- Comment #8 from Brett Keller <blkel...@comcast.net> --- 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.
[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
