[plasma-pa] [Bug 399954] New: Default audio device is ignored
https://bugs.kde.org/show_bug.cgi?id=399954 Bug ID: 399954 Summary: Default audio device is ignored Product: plasma-pa Version: 5.14.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: now...@gmail.com Reporter: et...@ethanhussong.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY My default audio device is ignored. STEPS TO REPRODUCE 1. Set default audio device to one other than the one that is selected after a fresh installation. 2. Open an application and start playing audio (e.g. Clementine, Vivaldi browser) OBSERVED RESULT Application begins playing through the original default device and not the newly selected one. By selecting a different default, then selecting the desired default all playing applications will then begin playing through that device. EXPECTED RESULT Selected default device should play audio. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.0 KDE Frameworks Version: 53.51.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Certain applications will seem to retain settings once they are selected in the "Applications" section of the Audio settings. e.g. I can open Clementine and experience the bug, but if I set it on the application page it will start playing through that device even if the application is closed and reopened. Other applications lose this any time that the application stops playing long enough to disappear from the "Applications" settings page. e.g. Vivaldi can have a video playing and will default to the incorrect device. If it is set on the application page it will work fine. If the video is paused for a few moments and the application output disappears from the "Applications" page it will then start playing audio back to the incorrect (original default, before being changed) output device and needs to be set again every time the audio stream is restarted. Behavior is consistent across multiple distributions. Kubuntu 18.04.1 does not appear to have this issue, but Fedora 28, Manjaro KDE, and now KDE Neon do. Possibly related to Bug 396296 as I end up often seeing similar issues as described in this bug, but am not reporting on the same thing. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 381472] New: Crash when searching calendar
https://bugs.kde.org/show_bug.cgi?id=381472 Bug ID: 381472 Summary: Crash when searching calendar Product: kontact Version: 5.2.3 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: et...@ethanhussong.com Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.35.0 Operating System: Linux 4.4.0-81-generic x86_64 Distribution: Linux Mint 18.1 Serena -- Information about the crash: - What I was doing when the application crashed: Started typing in the "search" field for a calendar. This is a recently imported calendar. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f91602940 (LWP 5112))] Thread 16 (Thread 0x7f0f117fa700 (LWP 5137)): #0 0x7f0fa8ead70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0fa261639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0fa26164ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0fa99eb37b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0fa9993ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0fa97bc9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0fa97c1808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0fa2e406ba in start_thread (arg=0x7f0f117fa700) at pthread_create.c:333 #8 0x7f0fa8eb93dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7f0f11ffb700 (LWP 5135)): #0 0x7f0fa265aae4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0fa2615920 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0fa26162cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0fa26164ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0fa99eb37b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0fa9993ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0fa97bc9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0fa97c1808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0fa2e406ba in start_thread (arg=0x7f0f11ffb700) at pthread_create.c:333 #9 0x7f0fa8eb93dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7f0f127fc700 (LWP 5133)): #0 0x7f0fa265aac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0fa2616498 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0fa99eb37b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f0fa9993ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0fa97bc9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0fa97c1808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0fa2e406ba in start_thread (arg=0x7f0f127fc700) at pthread_create.c:333 #7 0x7f0fa8eb93dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 13 (Thread 0x7f0f12ffd700 (LWP 5131)): #0 0x7f0fa2615ce4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0fa2616340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0fa26164ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0fa99eb37b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0fa9993ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0fa97bc9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0fa97c1808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0fa2e406ba in start_thread (arg=0x7f0f12ffd700) at pthread_create.c:333 #8 0x7f0fa8eb93dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f0f137fe700 (LWP 5129)): #0 0x7f0fa8ead70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0fa261639c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0fa26164ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0fa99eb37b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0fa9993ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linu
[kontact] [Bug 381473] New: Clicking "Read Manual" in Kontact Introduction sends to 404 page
https://bugs.kde.org/show_bug.cgi?id=381473 Bug ID: 381473 Summary: Clicking "Read Manual" in Kontact Introduction sends to 404 page Product: kontact Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: et...@ethanhussong.com Target Milestone: --- When clicking on the Help -> Kontact Introduction -> Read Manual links it sends you to the following page: https://docs.kde.org/stable5/en/pim/kontact//ontact/index.html This page returns a 404 error. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 381473] Clicking "Read Manual" in Kontact Introduction sends to 404 page
https://bugs.kde.org/show_bug.cgi?id=381473 --- Comment #3 from Ethan Hussong --- This is going to sound crazy but after rebooting again today the interface is different. The menu is different. The version number hasn't changed (still 5.2.3 which I think is what I opened this as last night) but now that link is gone. Instead there's a link that now just says "KMail has many powerful features that are described in the documentation." When you click on the hyperlink of "documentation" it opens a popup that says "Error -- KIOExec" as the subject and "File not found: help:/kmail/index.html" as the body. I promise I'm not making this up! :) I'm using English under Linux Mint 18.1 KDE version -- You are receiving this mail because: You are watching all bug changes.
