[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 --- Comment #7 from Petr Nehez --- For those who want to set a minimum height, open /usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/FullRepresentation.qml and update it. For me to set "Layout.minimumHeight: units.gridUnit * 42" is enough. But again - it would be really helpful if KDE would remember the size across sessions. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 388049] On lockscreen pasting user notes is not inhibited
https://bugs.kde.org/show_bug.cgi?id=388049 --- Comment #4 from Federico --- I can't see any reverting patch here: https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/kscreenlocker. The only patch i see is https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/kscreenlocker&id=3cde934f21af20462b85db6e36cc6a718b3c188f. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #10 from Markus --- Yes I still have this problem. Those pipeline setting prevents it. (At cost of performance.) I still think its at least two bugs: 1. Recovery from the graphics reset is not working. (kwin bug?) 2. Graphics reset itself: Intended behaviour of driver: "Typically these are application-level bugs, but can also be driver bugs or hardware bugs." So it can be nvidia and/or "application" (kwin, or what ever application uses the hw directly) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388056] New: Plasma crashed on standby resume - multi-screen
https://bugs.kde.org/show_bug.cgi?id=388056 Bug ID: 388056 Summary: Plasma crashed on standby resume - multi-screen Product: plasmashell Version: 5.8.7 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: i...@pnb.co.za CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.7) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.103-36-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: On a Dell Precision 3510 with a extra monitor connected via HDMI, plasma crashed after logging on. Initially it placed the laptop screen over the external screen, once I changed that back to its setting prior to standby, it crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8e2c94b900 (LWP 2538))] Thread 8 (Thread 0x7f8d46a29700 (LWP 2666)): #0 0x7f8e25e2d28d in read () at /lib64/libc.so.6 #1 0x7f8e22522750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8e224e1e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8e224e22a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8e224e242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8e2673e1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f8e266ebbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8e26526f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f8d47e528f7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #9 0x7f8e2652ba29 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f8e2563a744 in start_thread () at /lib64/libpthread.so.0 #11 0x7f8e25e39aad in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f8d71c4c700 (LWP 2653)): #0 0x7f8e25e3120d in poll () at /lib64/libc.so.6 #1 0x7f8e224e2314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8e224e242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8e2673e1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8e266ebbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8e26526f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8e2a3b8822 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f8e2652ba29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f8e2563a744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8e25e39aad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f8d73b3d700 (LWP 2651)): #0 0x7f8e25e3120d in poll () at /lib64/libc.so.6 #1 0x7f8e224e2314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8e224e242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8e2673e1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8e266ebbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8e26526f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8e2652ba29 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f8e2563a744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f8e25e39aad in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f8e01855700 (LWP 2649)): #0 0x7f8e2563f0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8e2c01d93b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f8e2c01d969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f8e2563a744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f8e25e39aad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f8e08c96700 (LWP 2648)): #0 0x7f8e22523899 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f8e224e2205 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8e224e242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8e2673e1ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8e266ebbfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8e26526f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8e298343d8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f8e2652ba29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f8e2563a744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8e25e39aad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f8e0a4e4700 (LWP 2615)): #0 0x7f8e25e3120d in poll () at /lib64/libc.so.6 #1 0x7f8e224e2314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8e224e242c in g_main_context_iteration () at /usr/lib64/libglib-2.
[plasma-mycroft] [Bug 388032] How to integrate Plasmoid-mycroft with Mycroft Docker service?
https://bugs.kde.org/show_bug.cgi?id=388032 --- Comment #4 from stardiviner --- Really thanks for your help. [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 12:59 PM, Aditya Mehra wrote: > 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 reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387702] Permit Scripter to load scripts which don't have a main()
https://bugs.kde.org/show_bug.cgi?id=387702 Brendan changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387764] Gphoto2 camera drivers not installed by PKG Installer
https://bugs.kde.org/show_bug.cgi?id=387764 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Gphoto2 cameras driver not |Gphoto2 camera drivers not |found in PKG Installer |installed by PKG Installer -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 388048] Messenger-like "Send"
https://bugs.kde.org/show_bug.cgi?id=388048 --- Comment #4 from Ilya Bizyaev --- In the latest breeze-icons, I can't find anything like that... (apart from document-share, which is a classic share icon) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 388055] New: Last command gets carried over when in bottom line
https://bugs.kde.org/show_bug.cgi?id=388055 Bug ID: 388055 Summary: Last command gets carried over when in bottom line Product: konsole Version: 16.04.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: perlan...@gmail.com Target Milestone: --- This only appears to be happening when Konsole window is maximized. When the cursor ends up at the bottom-most line, then the last command sometimes gets carried over. So to illustrate: .-. | $ ls -l | | (output ...)| | (output ...)| | (output ...)| | (output ...)| | (output ...)| | (output ...)| | (output ...)| | (output ...)| | $ ls -l | '-' After I type the first `ls -l` and the shell prompt is printed at the bottom line, the `ls -l` will already be there even though I have not typed it. This does not happen all the time. Also sometimes the last 2-3 bottom lines of output are not shown (just black/background color) and only shown after I press Enter to scroll one line. Really annoying, to be honest. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388036] Include support for autocrypt
https://bugs.kde.org/show_bug.cgi?id=388036 Dennis Schridde changed: What|Removed |Added CC||devuran...@gmx.net -- 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.
[Spectacle] [Bug 374009] Spectacle sometimes hangs the whole system when doing rectangular captures
https://bugs.kde.org/show_bug.cgi?id=374009 Christoph Feck changed: What|Removed |Added CC||fabrice.salva...@orange.fr --- Comment #11 from Christoph Feck --- *** Bug 386629 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 386629] Can't exit rectangular region
https://bugs.kde.org/show_bug.cgi?id=386629 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #4 from Christoph Feck --- No response, assume it is indeed a duplicate. *** This bug has been marked as a duplicate of bug 374009 *** -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 337141] Crash on close
https://bugs.kde.org/show_bug.cgi?id=337141 Christoph Feck changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- Thanks for the update; closing. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 388054] New: Crash when changing subtitle template
https://bugs.kde.org/show_bug.cgi?id=388054 Bug ID: 388054 Summary: Crash when changing subtitle template Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lu...@aiken.cz Target Milestone: --- Application: kdenlive (16.04.3) Qt Version: 5.6.1 Frameworks Version: 5.36.0 Operating System: Linux 4.4.0-53-generic x86_64 Distribution: Linux Mint 18.2 Sonya -- Information about the crash: - What I was doing when the application crashed: Changing the subtitle template when some subtitle objects already existed. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc3530368c0 (LWP 19592))] Thread 63 (Thread 0x7fc2aaffd700 (LWP 29023)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc30d21995d in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so #2 0x7fc34ac4c6ba in start_thread (arg=0x7fc2aaffd700) at pthread_create.c:333 #3 0x7fc34c5f43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 62 (Thread 0x7fc2c8d26700 (LWP 29022)): #0 0x7fc33e3c424d in pa_pstream_unref () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #1 0x7fc33e3c4789 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #2 0x7fc33e3c501a in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #3 0x7fc344e590b7 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fc344e594bc in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fc31ac64feb in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #6 0x7fc31ac37920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #7 0x7fc31ac410b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #8 0x7fc31ac80f59 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0 #9 0x7fc34ac4c6ba in start_thread (arg=0x7fc2c8d26700) at pthread_create.c:333 #10 0x7fc34c5f43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 61 (Thread 0x7fc2be7fc700 (LWP 29021)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc352018933 in ?? () from /usr/lib/x86_64-linux-gnu/libmlt.so.6 #2 0x55927d0adf6d in RenderThread::run (this=0x7fc2d8a0ba00) at /build/kdenlive-KhSDhU/kdenlive-16.04.3/src/monitor/glwidget.cpp:1230 #3 0x7fc34d002808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc34ac4c6ba in start_thread (arg=0x7fc2be7fc700) at pthread_create.c:333 #5 0x7fc34c5f43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 60 (Thread 0x7fc2b27f4700 (LWP 29020)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc30d21a30f in ?? () from /usr/lib/x86_64-linux-gnu/mlt/libmltsdl.so #2 0x7fc34ac4c6ba in start_thread (arg=0x7fc2b27f4700) at pthread_create.c:333 #3 0x7fc34c5f43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 59 (Thread 0x7fc2aa7fc700 (LWP 27766)): #0 0x7fc3466aba94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc3466672ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc34666749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc34d22c37b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc34d1d4ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc34cffd9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc34d002808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc34ac4c6ba in start_thread (arg=0x7fc2aa7fc700) at pthread_create.c:333 #8 0x7fc34c5f43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 58 (Thread 0x7fc2ca529700 (LWP 27759)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc322124cdb in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56 #2 0x7fc34ac4c6ba in start_thread (arg=0x7fc2ca529700) at pthread_create.c:333 #3 0x7fc34c5f43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 57 (Thread 0x7fc2cad2a700 (LWP 27758)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc322124cdb in ?? () from /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56 #2 0x7fc34ac4c6ba in start_thread (arg=0x7fc2cad2a700
[krita] [Bug 384850] Series of transform mask bugs with large images
https://bugs.kde.org/show_bug.cgi?id=384850 --- Comment #5 from reptilli...@live.com --- I just found another issue with transform mask. If you apply transform mask to a image, and scale it to 1x1, and apply it again, you get "Waiting for image operation" forever. The purpose of this was to find how to generate average color non-destructively. That is not supposed to happen. -- 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 --- Comment #2 from stardiviner --- 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. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 380114] crash on exit in ~NotifyByAudio()
https://bugs.kde.org/show_bug.cgi?id=380114 Christoph Feck changed: What|Removed |Added CC||jcarricksm...@gmail.com --- Comment #26 from Christoph Feck --- *** Bug 387237 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 387237] Mahjongg closed unexpectedly just after saving a game
https://bugs.kde.org/show_bug.cgi?id=387237 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 380114 *** -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 387484] Can't decrypt files .txt (PGP)
https://bugs.kde.org/show_bug.cgi?id=387484 --- Comment #2 from Christoph Feck --- If you can provide the information requested in comment #1, please add it. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 386061] Fehler bei der Schlüsselgenerierung
https://bugs.kde.org/show_bug.cgi?id=386061 --- Comment #3 from Christoph Feck --- To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment. -- You are receiving this mail because: You are watching all bug changes.
[kjots] [Bug 387239] kjots error MGA5
https://bugs.kde.org/show_bug.cgi?id=387239 Christoph Feck changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- KDEPIM version 4 is no longer maintained. Please ask for help in a forum of your distribution how to update your system to recent versions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 387481] Save file dialog doesn't return selected filter properly
https://bugs.kde.org/show_bug.cgi?id=387481 Christoph Feck changed: What|Removed |Added Product|kfile |frameworks-frameworkintegra ||tion Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 327760] Notify user when debug symbols are missing
https://bugs.kde.org/show_bug.cgi?id=327760 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Keywords||junior-jobs --- Comment #3 from Kevin Funk --- Preliminary patch: https://git.reviewboard.kde.org/r/125664 If someone wants to pick this up -- you're welcome! -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 362697] Attachments with Koi-8 encoded file names are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=362697 Christoph Feck changed: What|Removed |Added Version|5.1.* |5.6.3 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355396] dual monitor become single after reboot
https://bugs.kde.org/show_bug.cgi?id=355396 --- Comment #6 from Morbid --- The same situation. For 2 years already. Manjaro Plasma: 5.11.4 Linux 4.14.5 nVidia-bumblebee, Intel used for Plasma. If there is any other information needed then please do contact me. I will try helping as much as I can. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 388053] New: Cannot run Ubuntu Software Center
https://bugs.kde.org/show_bug.cgi?id=388053
Bug ID: 388053
Summary: Cannot run Ubuntu Software Center
Product: neon
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Packages User Edition
Assignee: neon-b...@kde.org
Reporter: thomas.pfeif...@kde.org
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
Target Milestone: ---
When trying tu run Ubuntu Software Center, it doesn't open. When trying to
start it from the command line, I get the following output:
/usr/bin/software-center:25: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to ensure
that the right version gets loaded.
from gi.repository import Gtk, GObject
ERROR:root:DebFileApplication import
Traceback (most recent call last):
File "/usr/share/software-center/softwarecenter/db/__init__.py", line 6, in
from .debfile import DebFileApplication, DebFileOpenError
File "/usr/share/software-center/softwarecenter/db/debfile.py", line 25, in
from softwarecenter.db.application import Application, AppDetails
File "/usr/share/software-center/softwarecenter/db/application.py", line 28,
in
ImportError: No module named neon
import softwarecenter.distro
File "/usr/share/software-center/softwarecenter/distro/__init__.py", line
201, in
distro_instance = _get_distro()
File "/usr/share/software-center/softwarecenter/distro/__init__.py", line
176, in _get_distro
module = __import__(distro_module_name, globals(), locals(), [], level)
ImportError: No module named neon
Traceback (most recent call last):
File "/usr/bin/software-center", line 128, in
from softwarecenter.ui.gtk3.app import SoftwareCenterAppGtk3
File "/usr/share/software-center/softwarecenter/ui/gtk3/app.py", line 54, in
from softwarecenter.db.application import Application
File "/usr/share/software-center/softwarecenter/db/application.py", line 28,
in
import softwarecenter.distro
File "/usr/share/software-center/softwarecenter/distro/__init__.py", line
201, in
distro_instance = _get_distro()
File "/usr/share/software-center/softwarecenter/distro/__init__.py", line
176, in _get_distro
module = __import__(distro_module_name, globals(), locals(), [], level)
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 388052] New: Konsole crashed after suspend
https://bugs.kde.org/show_bug.cgi?id=388052 Bug ID: 388052 Summary: Konsole crashed after suspend Product: konsole Version: 17.04.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: houstonjo...@gmail.com Target Milestone: --- Application: konsole (17.04.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.76-1-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: I was using rsync on two remote nfs shares, each rsync command was in a seperate tab, pulling from the same location to the same location, each copying a directory -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f43e3e65900 (LWP 41517))] Thread 2 (Thread 0x7f43c7972700 (LWP 41519)): #0 0x7f43e379220d in poll () at /lib64/libc.so.6 #1 0x7f43db1af314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f43db1af42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f43dfd961ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f43dfd43bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f43dfb7ef5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f43ddf43295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f43dfb83a29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f43db6cc744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f43e379aaad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f43e3e65900 (LWP 41517)): [KCrash Handler] #6 0x015b4220 in () #7 0x7f43df52fbde in () at /usr/lib64/libKF5Notifications.so.5 #8 0x7f43df52fc79 in () at /usr/lib64/libKF5Notifications.so.5 #9 0x7f43dfd6e6c5 in QObjectPrivate::deleteChildren() () at /usr/lib64/libQt5Core.so.5 #10 0x7f43dfd77c7e in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5 #11 0x7f43df50e769 in () at /usr/lib64/libKF5Notifications.so.5 #12 0x7f43e36e8139 in __run_exit_handlers () at /lib64/libc.so.6 #13 0x7f43e36e8185 in () at /lib64/libc.so.6 #14 0x7f43e36d16ec in __libc_start_main () at /lib64/libc.so.6 #15 0x00400789 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 387447] KDE Connect file transfers do not finish for small files
https://bugs.kde.org/show_bug.cgi?id=387447 --- Comment #1 from Christoph Feck --- A fix for bug 386246 was just committed. It is possibly a duplicate. Please test when packages are updated including the referenced commit. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 387134] Shouldn't there be some default audio file included with the package
https://bugs.kde.org/show_bug.cgi?id=387134 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Christoph Feck --- Standard sounds are at /usr/share/sounds/ Distributions install desktop notification sounds there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385291] entire desktop freezing, cursor works and i can still drag windows around but framebuffer is frozen
https://bugs.kde.org/show_bug.cgi?id=385291 younker...@gmail.com changed: What|Removed |Added CC||younky.y...@yahoo.com --- Comment #12 from younker...@gmail.com --- I have the same issue on AMD threadripper platform with GTX1080Ti card and also a Dell XPS 8910 desktop with NVIDIA 1070 card. Just wonder to know is this the error caused by driver or the application which invoke some opengl functions? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 younker...@gmail.com changed: What|Removed |Added CC||younky.y...@yahoo.com --- Comment #9 from younker...@gmail.com --- (In reply to Markus from comment #8) > https://devtalk.nvidia.com/default/topic/1023621/linux/frequent-kwin- > compositing-failure-with-associated-xid-31-error/post/5207959/ > Setting "Force Composition Pipeline" and "Force Full Composition Pipeline" > in nvidia-settings works as workaround. (reduce performance) Do you still have the issue? I still have the issues which is annoying. I have posted some update on the devtalk.nvidia thread, but seems no nvidia people care about it. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 372417] Entering fullscreen will switch to other monitor when Gwenview is already maximized
https://bugs.kde.org/show_bug.cgi?id=372417 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- Version|Other (add details in bug |17.04.3 |description)| --- Comment #6 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361859] kickoff doesn't keep user defined size
https://bugs.kde.org/show_bug.cgi?id=361859 Aleksey Kontsevich changed: What|Removed |Added CC||akontsev...@gmail.com --- Comment #6 from Aleksey Kontsevich --- KDE 5 become much worse than KDE 4. What were you developing for so much years?! For whom?! People or for MS to make Linux less popular?! Reopen this bug! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388051] New: Pulling the DP cable when logging off has gui in inconsistent state
https://bugs.kde.org/show_bug.cgi?id=388051 Bug ID: 388051 Summary: Pulling the DP cable when logging off has gui in inconsistent state Product: plasmashell Version: 5.11.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: slartibar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Hi, maybe this is the wrong topic to place this error to, but in lack of a better category I have a multimonitor setup, a lenovo t470p and an external, display-port connected fullHD monitor. Plasma5 is working fine, no problems at all (besides the lack of proper dpi settings for the external screen) When i finish working, i log off - ready to put my laptop to sleep by closing the lid and putting it into my backpack. Most of the time i forget that the external monitor is still connected to the DP port, which i normally discover _after_ giving the command to log off of plasma. Pulling the cord in this specific moment (after logging off and before the sddm greeter is displayed) results in a total black screen on the laptop. Virtual consoles (2 and up) are still available, but i couldn't figure out how to get a graphical login on vk1 back again to life. If i pull the cord before logging of, all is fine. Any idea how to resolve this problem? Or, at least, how to get the sddm gui login working again? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 386246] File transfer does not complete
https://bugs.kde.org/show_bug.cgi?id=386246 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/kio ||/d9c5673c20ea4c76880b8d4e10 ||44523c80ab1fe4 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #13 from Albert Astals Cid --- Git commit d9c5673c20ea4c76880b8d4e1044523c80ab1fe4 by Albert Astals Cid. Committed on 19/12/2017 at 23:00. Pushed by aacid into branch 'master'. TransferJob: fix for when the readChannelFinished has already been emitted before start is called() Summary: This fixes a regression by the removal of the busy loop call from bcdbe62660a9ca91b0d15f3a9a06a758ec8fdcda Test Plan: New test passes with the new code, didn't pass before Sending very small files with kde connect works again Reviewers: dfaure, apol, albertvaka Reviewed By: dfaure, apol Subscribers: ngraham, nicolasfella, anthonyfieroni, #frameworks Tags: #frameworks Differential Revision: https://phabricator.kde.org/D9190 M +36 -0autotests/jobtest.cpp M +1-0autotests/jobtest.h M +5-2src/core/job_p.h M +18 -1src/core/transferjob.cpp M +1-0src/core/transferjob.h https://commits.kde.org/kio/d9c5673c20ea4c76880b8d4e1044523c80ab1fe4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387764] Gphoto2 cameras driver not found in PKG Installer
https://bugs.kde.org/show_bug.cgi?id=387764 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.7.0 |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387764] Gphoto2 cameras driver not found in PKG Installer
https://bugs.kde.org/show_bug.cgi?id=387764 caulier.gil...@gmail.com changed: What|Removed |Added Summary|support for older cameras |Gphoto2 cameras driver not ||found in PKG Installer -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385813] Video timings change when changing video profile
https://bugs.kde.org/show_bug.cgi?id=385813 --- Comment #1 from Jesús Jiménez --- I can confirm the bug, has happened to me since always. Perhaps the option to switch a project profile should be disabled, right now it's very easy to corrupt a full project just by switching profile. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 387764] support for older cameras
https://bugs.kde.org/show_bug.cgi?id=387764 caulier.gil...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #4 from caulier.gil...@gmail.com --- The problem come from gphoto2 driver, included in digiKam PKG installer for MacOS which are not found by the library at run-time. Probably the drivers are not at the right place in the bundle, or a path is missing. I will investiguate. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 386364] crash in HTTP
https://bugs.kde.org/show_bug.cgi?id=386364 Aleix Pol changed: What|Removed |Added Latest Commit|https://commits.kde.org/kio |https://commits.kde.org/kio |/c3ec3e9609f08a5a69c4d2af95 |/ca2364d9c2032e9e08e5c733b4 |0d3c5bffe6ef63 |5efb97bd37f0ad Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #12 from Aleix Pol --- Git commit ca2364d9c2032e9e08e5c733b45efb97bd37f0ad by Aleix Pol. Committed on 19/12/2017 at 22:44. Pushed by apol into branch 'master'. Fix crash, presumably since Qt 5.10? Summary: We are opening the stream as read only and skipRawData would complain that it's a write-only device, and skipping needs reading: QIODevice::skip (QBuffer): WriteOnly device It was a weird optimization anyway, so just pass the information like the rest of the data and it works just fine. Test Plan: The check on the bug report passes now, and akregator fetches all feeds again. Reviewers: #frameworks, dfaure Reviewed By: dfaure Subscribers: anthonyfieroni, ngraham Tags: #frameworks Differential Revision: https://phabricator.kde.org/D9399 M +1-1src/ioslaves/http/http.cpp https://commits.kde.org/kio/ca2364d9c2032e9e08e5c733b45efb97bd37f0ad -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 385813] Video timings change when changing video profile
https://bugs.kde.org/show_bug.cgi?id=385813 Jesús Jiménez changed: What|Removed |Added CC||jesjime...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 387291] drkonqi fails to report crashes when affected component version does not match bugzilla
https://bugs.kde.org/show_bug.cgi?id=387291 Christoph Feck changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- That is intentional. Developers can decide for which versions they want to get bug reports, and mark all others 'inactive'. KWin has no 'unspecified' version entry, because its developer deleted it on purpose to not get bug reports without valid version information. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 387139] drkonqi segfault on Fedora 27 while reporting a crash
https://bugs.kde.org/show_bug.cgi?id=387139 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 381644 *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 381644] Dr. Konqi Crashes During Crash Report
https://bugs.kde.org/show_bug.cgi?id=381644 Christoph Feck changed: What|Removed |Added CC||arca...@ivanov.biz --- Comment #4 from Christoph Feck --- *** Bug 387139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 387327] Dragon Player does not play Video DVD
https://bugs.kde.org/show_bug.cgi?id=387327 Christoph Feck changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Crash is in libgstreamer, please report this issue directly to libgstreamer developers via https://gstreamer.freedesktop.org/bugs/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387938] Compositing turned off on unlock
https://bugs.kde.org/show_bug.cgi?id=387938 --- Comment #6 from beojan --- (In reply to Martin Flöser from comment #5) > Sorry, but that's impossible. We don't have any code to open that dialog. Well that's what happens. It appears this may be linked to using an additional external display on a laptop, since I don't experience the issue when not using such a display. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 387203] Crash of Dolphin
https://bugs.kde.org/show_bug.cgi?id=387203 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Christoph Feck --- Version 15.12 of Dolphin is no longer supported. Please ask in a forum of your distribution how to update your system to recent KDE software. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387873] can no longer drag/drop a message from message list to favorites
https://bugs.kde.org/show_bug.cgi?id=387873 David Faure changed: What|Removed |Added Latest Commit||https://commits.kde.org/mai ||lcommon/ace9cfb46008e4fcd2b ||973111fbc508110bbd9c9 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from David Faure --- Git commit ace9cfb46008e4fcd2b973111fbc508110bbd9c9 by David Faure. Committed on 19/12/2017 at 22:11. Pushed by dfaure into branch 'master'. Fix dropping of emails onto favorites Summary: and dropping a collection to define a new favorite. Test Plan: Tested all three features, reordering, adding, and dropping a mail. Two issues left: - adding a new favourite at a specific position (patch pending for akonadi's favoritecollectionsmodel) - the "+" when moving to reorder shouldn't appear, should be MoveAction only, don't know if that's possible here though. Reviewers: dvratil, mlaurent, mkoller Reviewed By: dvratil Subscribers: #kde_pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D9403 M +0-10 src/folder/favoritecollectionorderproxymodel.cpp M +0-2src/folder/favoritecollectionorderproxymodel.h M +47 -9src/widgets/favoritecollectionwidget.cpp M +2-0src/widgets/favoritecollectionwidget.h https://commits.kde.org/mailcommon/ace9cfb46008e4fcd2b973111fbc508110bbd9c9 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386838] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=386838 --- Comment #20 from Christoph Feck --- inotify_add_watch() fails with "No space left on device" when the number of allowed kernel inotify watches has been reached. Please ask in a forum of your distribution how to increase this limit. -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 379810] qca compilation fails with openssl 1.1
https://bugs.kde.org/show_bug.cgi?id=379810 Fabian Vogt changed: What|Removed |Added Attachment #109428|0 |1 is obsolete|| --- Comment #11 from Fabian Vogt --- Created attachment 109456 --> https://bugs.kde.org/attachment.cgi?id=109456&action=edit Patch for OpenSSL 1.1.0 support (v4) To easily fit QCA's license, I exchanged the libcrypto-compat files with a compatibility header written by Gabriel Souza Franco and adjusted the code to use that instead. No changes otherwise. I also uploaded it to phab: https://phabricator.kde.org/D9416 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 388048] Messenger-like "Send"
https://bugs.kde.org/show_bug.cgi?id=388048 andreas changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from andreas --- I would recommend an paper plane icon with the icon name document-sent -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 387772] Stuck at configuring
https://bugs.kde.org/show_bug.cgi?id=387772 --- Comment #13 from Matthieu Gallien --- (In reply to now-im from comment #12) > okay, I left elisa open and after some time it stopped searching for track > but every time I open the app, same configure thing. > Right now there is no option to add track path. I could not open any AAC > file, thus tried to open a MP3 file. I could not open that either. > Most of my music files are in AAC format. So, it is vital that elisa can > open that. The support for file format depends on Qt Multimedia that uses gstreamer. Please if you use a build different from the flatpak one, checks that you have the needed support for gstreamer. I have created https://phabricator.kde.org/T7603 to optimize the next run of the application after the first indexing and when not using baloo. You can follow it to know when it is done. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 386416] Crash after update
https://bugs.kde.org/show_bug.cgi?id=386416 Christoph Feck changed: What|Removed |Added Resolution|BACKTRACE |INVALID Status|NEEDSINFO |RESOLVED --- Comment #4 from Christoph Feck --- No response, changing status. If you have new information, please add it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 388048] Messenger-like "Send"
https://bugs.kde.org/show_bug.cgi?id=388048 --- Comment #2 from Ilya Bizyaev --- Created attachment 109455 --> https://bugs.kde.org/attachment.cgi?id=109455&action=edit Kaidan chat page Currently we use a simple button, but we'd like to go modern :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351008] Automatic change of Timezone based on location
https://bugs.kde.org/show_bug.cgi?id=351008 --- Comment #13 from Peter Tselios --- In Gnome 3 it's already there and enabled by default, even in RHEL (not just Fedora). Also, in the latest update of KDE in my Fedora 26 I noticed that there geolocation libraries (plasma-workspace-geolocation & plasma-workspace-geolocation-libs). I suspect that all the necessary bits are in place. I really hope that you will implement it :) I wished I could help, but unfortunately, I am out of coding years know :( -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354819] Specific pictures not showing up in digikam
https://bugs.kde.org/show_bug.cgi?id=354819 --- Comment #8 from caulier.gil...@gmail.com --- I recommend to test with 5.8.0 pre-release Linux AppImage bundle where some code have been fixed around the non single image ID provided by Samsung camera. File is here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 387137] Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=387137 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #2 from Christoph Feck --- ArchLinux has no debug symbols, but if this crash is reproducible, even an incomplete backtrace might still reveal important information. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354819] Specific pictures not showing up in digikam
https://bugs.kde.org/show_bug.cgi?id=354819 --- Comment #7 from Gernot Hillier --- Ok, after checking the digikam debug output on stdout, I found that digikam says this when the problematic image is added: digikam.database: Recognized "/home/gernot/sync/digibilder/to_sort/aa/testcase.jpg" as identical to item 94617. So, I'm likely hit by #375483. My smartphone producing those images is a Galaxy S5 and all images have the same ImageUniqueID. As the initial sample picture from Andreas in this report has no ImageUniqueID, my problem is likely distince and I probably shouldn't have added my issue here, sorry. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 388048] Messenger-like "Send"
https://bugs.kde.org/show_bug.cgi?id=388048 --- Comment #1 from andreas --- screenshot please -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388050] New: KMail sometimes crashes when opening an email
https://bugs.kde.org/show_bug.cgi?id=388050 Bug ID: 388050 Summary: KMail sometimes crashes when opening an email Product: kmail2 Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@tobias-wichtrey.de Target Milestone: --- Application: kmail (5.5.3) Qt Version: 5.9.1 Frameworks Version: 5.40.0 Operating System: Linux 4.13.0-19-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: KMail sometimes crashes when clicking on an email. This is, what I did before this crash. KMail also randomly crashes when resizing its window and on startup. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbe7a93fb80 (LWP 16874))] Thread 25 (Thread 0x7fbdb0845700 (LWP 16956)): #0 0x7fbe6d551072 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fbe5f1c8fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fbe5f1c8f68, cond=0x7fbe5f1c8f90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fbe5f1c8f90, mutex=0x7fbe5f1c8f68) at pthread_cond_wait.c:655 #3 0x7fbe5eed4bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fbe5eed4c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fbe6d54a7fc in start_thread (arg=0x7fbdb0845700) at pthread_create.c:465 #6 0x7fbe77a31b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fbde1ffb700 (LWP 16907)): #0 0x7fbe519d6213 in pa_pstream_unref () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #1 0x7fbe519d6739 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #2 0x7fbe519d6fbf in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #3 0x7fbe5a1d60d8 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fbe5a1d64ae in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fbe5a1d6530 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fbe5a1e4399 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7fbe519e6ed8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so #8 0x7fbe6d54a7fc in start_thread (arg=0x7fbde1ffb700) at pthread_create.c:465 #9 0x7fbe77a31b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fbde27fc700 (LWP 16906)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7fbe77a41f34 in ___fprintf_chk (fp=0x7fbe77cf9870 <_IO_stdfile_2_lock>, flag=1, format=0x7fbe57df3528 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7fbe57ddb74a in event_logv_ () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7fbe57ddb924 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7fbe57ddd278 in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7fbe57dd3019 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7fbe62456b4d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fbe62452dc8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fbe6246f9bb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fbe624876b6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fbe624837bb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7fbe6d54a7fc in start_thread (arg=0x7fbde27fc700) at pthread_create.c:465 #12 0x7fbe77a31b0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fbde2ffd700 (LWP 16905)): #0 0x7fbe6d551072 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fbde2ffc748) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fbde2ffc6f8, cond=0x7fbde2ffc720) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fbde2ffc720, mutex=0x7fbde2ffc6f8) at pthread_cond_wait.c:655 #3 0x7fbe6247bb59 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fbe6247bb87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fbe624564fb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fbe62452dc8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fbe6246f9bb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fbe624876b6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore
[kscreenlocker] [Bug 388049] On lockscreen pasting user notes is not inhibited
https://bugs.kde.org/show_bug.cgi?id=388049 --- Comment #3 from Martin Flöser --- It might be that Arch reverted the changes. IIRC some distros reverted them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354819] Specific pictures not showing up in digikam
https://bugs.kde.org/show_bug.cgi?id=354819 --- Comment #6 from Gernot Hillier --- Created attachment 109454 --> https://bugs.kde.org/attachment.cgi?id=109454&action=edit testcase for picture missing from preview list Test picture, can be displayed with gthumb, dolphin, GIMP, etc. without problems, but digikam 5.7 on OpenSUSE 42.3 refuses to show it in the preview list. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354819] Specific pictures not showing up in digikam
https://bugs.kde.org/show_bug.cgi?id=354819 Gernot Hillier changed: What|Removed |Added CC||ger...@hillier.de --- Comment #5 from Gernot Hillier --- I have a similar issue since several digikam releases including 5.7. I'm running it on OpenSUSE 42.3. It seems only pictures taken with my smartphone SM-G900FD are affected. Sometimes, it helps to rename the problematic photos, but with the image attached here as "testcase.jpg", the problem persists, independent of filename. When I copy it in a new directory, this just looks like an empty album in Digikam. When I copy it in an existing album, digikam will show all other photos, but not "testcase.jpg". -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 388049] On lockscreen pasting user notes is not inhibited
https://bugs.kde.org/show_bug.cgi?id=388049 --- Comment #2 from Federico --- Sorry, forgot that! $ pacman -Q kscreenlocker kscreenlocker 5.11.4-1 I'm on X11. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 388049] On lockscreen pasting user notes is not inhibited
https://bugs.kde.org/show_bug.cgi?id=388049 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- What Plasma version is this? The clipboard should be cleared if you lock the screen [1] and [2]. [1] https://cgit.kde.org/kscreenlocker.git/commit/?id=cae1e82fc94f23f735ae3c189030505a95810cb5 [2] https://cgit.kde.org/kscreenlocker.git/commit/?id=b69465e5b115717f4dbe7fb1d0a496926816a690 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 388049] New: On lockscreen pasting user notes is not inhibited
https://bugs.kde.org/show_bug.cgi?id=388049 Bug ID: 388049 Summary: On lockscreen pasting user notes is not inhibited Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nierr...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- While on lockscreen, pressing ctrl-v or clicking mid mouse button will copy selected text (if any) from clipboard. Then, it can be showed by pressing the "show" button. This is a privacy issue (i guess) as an extraneous person can access user clipboard (even if only most recent item). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 388041] Can not open Root only files
https://bugs.kde.org/show_bug.cgi?id=388041 michael changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 388048] Messenger-like "Send"
https://bugs.kde.org/show_bug.cgi?id=388048 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 388048] New: Messenger-like "Send"
https://bugs.kde.org/show_bug.cgi?id=388048 Bug ID: 388048 Summary: Messenger-like "Send" Product: Breeze Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: bizy...@zoho.com CC: kain...@gmail.com Target Milestone: --- Hello! :) Seems like there's no general "Send" icon (not for mail, attachments etc., something that could be used in a messenger app, e.g. a paper airplane). I would like to use this icon in Kaidan, a Jabber/XMPP client built on Kirigami. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387393] akonadiserver 17.08.03 during idle
https://bugs.kde.org/show_bug.cgi?id=387393 --- Comment #2 from Till Schäfer --- This is not reproducible... I have only seen it once. Should we close the bug then? -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 388047] New: Kleopatra crashes when encrypting a text file
https://bugs.kde.org/show_bug.cgi?id=388047 Bug ID: 388047 Summary: Kleopatra crashes when encrypting a text file Product: kleopatra Version: 3.0.1 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: nasan...@gmail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- kleopatra gives the following error when trying to encrypt/decrypt/sign a text file kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" [1]18003 segmentation fault kleopatra encrypting contents of the clipboard is encrypted successfully. sample files where created with kpgp for testing decrypt. if you need further information kindly inform me as to how i gather same. i am running kde neon - Linux (x86_64) kernel release 4.10.0-42-generic kleopatra has been updated to 4:17.12 from the neon reposistories kleopatra (4:17.12.0-0neon+16.04+xenial+build38) this bug was present in 4:17.08 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387393] akonadiserver 17.08.03 during idle
https://bugs.kde.org/show_bug.cgi?id=387393 --- Comment #1 from Christoph Feck --- Thread 18 detected memory corruption, could be caused previously by any other thread. Probably only a valgrind log could help to isolate the cause of the issue. If this is reproducible, please try to generate a valgrind log. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 388046] New: Akregator crashes on startup
https://bugs.kde.org/show_bug.cgi?id=388046 Bug ID: 388046 Summary: Akregator crashes on startup Product: akregator Version: 5.7.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ketelsen.ma...@gmail.com Target Milestone: --- Application: akregator (5.7.0) Qt Version: 5.9.3 Frameworks Version: 5.41.0 Operating System: Linux 4.10.0-42-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: I started the app and it crashed immediately without having the app open. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4f396a4980 (LWP 3893))] Thread 20 (Thread 0x7f4eb22dc700 (LWP 3923)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f4f224cad04 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f4f224cad49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f4f2f8ce6ba in start_thread (arg=0x7f4eb22dc700) at pthread_create.c:333 #4 0x7f4f355a43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 19 (Thread 0x7f4eb6ffb700 (LWP 3918)): #0 0x7f4f35ec4e13 in roundToMillisecond (val=...) at kernel/qtimerinfo_unix.cpp:210 #1 QTimerInfoList::timerWait (this=0x7f4ed0004060, tm=...) at kernel/qtimerinfo_unix.cpp:405 #2 0x7f4f35ec643e in timerSourcePrepareHelper (timeout=0x7f4eb6ffaa74, src=) at kernel/qeventdispatcher_glib.cpp:132 #3 timerSourcePrepare (source=, timeout=0x7f4eb6ffaa74) at kernel/qeventdispatcher_glib.cpp:165 #4 0x7f4f2db5b91d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4f2db5c2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f4f2db5c49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f4f35ec66cb in QEventDispatcherGlib::processEvents (this=0x7f4ed0001c50, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f4f35e6ee2a in QEventLoop::exec (this=this@entry=0x7f4eb6ffac40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #9 0x7f4f35c978f4 in QThread::exec (this=) at thread/qthread.cpp:515 #10 0x7f4f35c9c709 in QThreadPrivate::start (arg=0x1144940) at thread/qthread_unix.cpp:368 #11 0x7f4f2f8ce6ba in start_thread (arg=0x7f4eb6ffb700) at pthread_create.c:333 #12 0x7f4f355a43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7f4ebf7fe700 (LWP 3917)): #0 0x7f4f3559424d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4f15a23f61 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #2 0x7f4f1c78da2e in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f4f1c78e4a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f4f1c78e560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f4f1c79c7a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f4f15a52078 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so #7 0x7f4f2f8ce6ba in start_thread (arg=0x7f4ebf7fe700) at pthread_create.c:333 #8 0x7f4f355a43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7f4eb700 (LWP 3916)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f4f25d8cd12 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f4f25d55274 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f4f25d303a8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f4f25d2c3b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f4f25d48eea in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4f25d60d86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f4f25d5cf2d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f4f2f8ce6ba in start_thread (arg=0x7f4eb700) at pthread_create.c:333 #9 0x7f4f355a43dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7f4ed4ff9700 (LWP 3915)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f4f25d5f35f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f4f25d5faf7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f4f25d608c0 in ?? () from
[kate] [Bug 388041] Can not open Root only files
https://bugs.kde.org/show_bug.cgi?id=388041 Nate Graham changed: What|Removed |Added CC||pointedst...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387846] Consumes 2x 90% CPU time, even when idle
https://bugs.kde.org/show_bug.cgi?id=387846 --- Comment #6 from iGadget --- Yes, 17.12.0b doesn't have the problem any more. Checked on 2 separate systems. Great job guys! -- 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.
[kmail2] [Bug 387931] KMail 5.7.0 is missing the message structure option
https://bugs.kde.org/show_bug.cgi?id=387931 --- Comment #6 from Laurent Montel --- (In reply to Till Schäfer from comment #5) > I use it as an end user, e.g. to verify that a newsletter format of my > wordpress instance is correct. For sure you are the first people which searched it. > > I also think, that "toolbar" \subseteq "menu" is a typical pattern and > therefore is the expectation of users. Thus, having items randomly appearing > only for the on or the other place will only create more confusion. > > I also do not think that this menu item is very confusing for other users. > Alternatively it may be possible to hide advanced features and only show > them if you choose the advanced mode? I.e. similar to the vlc approach. An advanced mode no it will be very hard to test 2 modes. But I can create a plugin (disable by default) which can add action in menu. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385755] preview for md document doesn't work
https://bugs.kde.org/show_bug.cgi?id=385755 --- Comment #6 from Michael D --- I get a text-only preview. Seems to be the bug you link to concerning not being able to pass mime type to okular. Unfortunately I've no time to go through the whole report here or the marked-as-duplicate one. I'm swamped--sorry! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385755] preview for md document doesn't work
https://bugs.kde.org/show_bug.cgi?id=385755 --- Comment #5 from Friedrich W. H. Kossebau --- (In reply to Michael D from comment #4) > I can't get markdown preview in KDE Neon either. Works fine if I open the > document in Okular. Thanks for taking the time to do your report. Sadly though it does not add information as "can't get markdown preview in KDE Neon either" can mean anything. You could get "text only" preview like it currently happens possibly due to a bug in Okular (see https://phabricator.kde.org/D8690 for a potential fix), or no preview at all. So please read through the existing comments on this bug report and also the one for which this one was closed as duplicate. Then tell what you experience yourself and how it relates to the reported issues. TIA. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 387979] Plasmashell and latte dock crashes due abnormal behavior of kactivitymanagerd
https://bugs.kde.org/show_bug.cgi?id=387979 Michail Vourlakos changed: What|Removed |Added CC||mvourla...@gmail.com --- Comment #5 from Michail Vourlakos --- the user uses latest plasma from unstable repos in openSUSE Somehow managed to broke its system... no idea how... from its debug output there are plenty: [warning 9:57:59.479479] - KActivities: FATAL ERROR: Failed to contact the activity manager daemon and there was a constant message for changing into a specific activity: [debug 9:57:59.525525] - activity changed :: "32ce0942-edce-41b4-b5a5-fab3a366926b" [debug 9:57:59.529529] - activity changed :: "32ce0942-edce-41b4-b5a5-fab3a366926b" [debug 9:57:59.532532] - activity changed :: "32ce0942-edce-41b4-b5a5-fab3a366926b" I asked from the user to drop Latte usage in order to reproduce with plasma panels and also what is happening when he is requesting to see the Activities switcher... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388045] New: Sorting by date does not apply to mail groups
https://bugs.kde.org/show_bug.cgi?id=388045 Bug ID: 388045 Summary: Sorting by date does not apply to mail groups Product: kmail2 Version: 5.7.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: hi-an...@yandex.ru Target Milestone: --- Using "Aggregation = mailing list" and "Sorting = by date and time" results in threads ordered only by date of the first mail. This is a major inconvenience, because for looking into mailing list you can't tell which threads was updated and which wasn't. In contrast, e.g. Thunderbird for sorting takes into attention all mails within a thread, i.e. if some old thread got a new mail, the mail group gets bumped. # Steps to reproduce: 1. Set "View → Message List → Sorting → • By Date/Time" and "View → Message List → Aggregation → • Standard Mailing List" 2. Send yourself a mail "TestOlder" 3. Send yourself a mail "TestNewer" 4. Reply to "TestOlder" # Expected: Thread TestOlder gets bumped # Actual TestOlder stays in the same order. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 388043] Zanshin crashes at startup
https://bugs.kde.org/show_bug.cgi?id=388043 --- Comment #1 from Diego Gangl --- Here's a backtrace: --- Application: Zanshin Todo (zanshin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4da0b64980 (LWP 29176))] Thread 6 (Thread 0x7f4d70af9700 (LWP 29184)): #0 0x7f4d9a10370d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4d9232138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4d9232149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4d9ac406cb in QEventDispatcherGlib::processEvents (this=0x7f4d5c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4d9abe8e2a in QEventLoop::exec (this=this@entry=0x7f4d70af8c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f4d9aa118f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f4d9aa16709 in QThreadPrivate::start (arg=0x2021e00) at thread/qthread_unix.cpp:368 #7 0x7f4d946de6ba in start_thread (arg=0x7f4d70af9700) at pthread_create.c:333 #8 0x7f4d9a10f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f4d71985700 (LWP 29183)): #0 0x7f4d92321234 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4d9232149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4d9ac406cb in QEventDispatcherGlib::processEvents (this=0x7f4d680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f4d9abe8e2a in QEventLoop::exec (this=this@entry=0x7f4d71984c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #4 0x7f4d9aa118f4 in QThread::exec (this=) at thread/qthread.cpp:515 #5 0x7f4d9aa16709 in QThreadPrivate::start (arg=0x201e720) at thread/qthread_unix.cpp:368 #6 0x7f4d946de6ba in start_thread (arg=0x7f4d71985700) at pthread_create.c:333 #7 0x7f4d9a10f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f4d72186700 (LWP 29181)): #0 0x7f4d92320929 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4d923212bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4d9232149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4d9ac406cb in QEventDispatcherGlib::processEvents (this=0x7f4d640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4d9abe8e2a in QEventLoop::exec (this=this@entry=0x7f4d72185c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f4d9aa118f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f4d9aa16709 in QThreadPrivate::start (arg=0x1fa7520) at thread/qthread_unix.cpp:368 #7 0x7f4d946de6ba in start_thread (arg=0x7f4d72186700) at pthread_create.c:333 #8 0x7f4d9a10f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f4d72987700 (LWP 29179)): #0 0x7f4d9a10370d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4d9232138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4d9232149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4d9ac406cb in QEventDispatcherGlib::processEvents (this=0x7f4d6c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4d9abe8e2a in QEventLoop::exec (this=this@entry=0x7f4d72986c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f4d9aa118f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f4d9aa16709 in QThreadPrivate::start (arg=0x1d798d0) at thread/qthread_unix.cpp:368 #7 0x7f4d946de6ba in start_thread (arg=0x7f4d72987700) at pthread_create.c:333 #8 0x7f4d9a10f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f4d7b74c700 (LWP 29178)): #0 0x7f4d9a0ff24d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f4d923646f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4d92320e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4d92321330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4d9232149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4d9ac406cb in QEventDispatcherGlib::processEvents (this=0x7f4d740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f4d9abe8e2a in QEventLoop::exec (this=this@entry=0x7f4d7b74bc10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f4d9aa118f4 in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f4d9b0bf315 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f4d9aa16709 in QThreadPrivate::start (arg=0x7f4d9b333d40) at thread/qthread_unix.cpp:368 #10 0x7f4d946de6ba in start_thread (arg=0x7f4d7b74c700) at pthread_create.c:333 #11 0x7f4d9a10f3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/c
[kate] [Bug 385755] preview for md document doesn't work
https://bugs.kde.org/show_bug.cgi?id=385755 Michael D changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #4 from Michael D --- I can't get markdown preview in KDE Neon either. Works fine if I open the document in Okular. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387970] Drill down backwards (via link) from a report to all transactions that support the report's number
https://bugs.kde.org/show_bug.cgi?id=387970 --- Comment #5 from Robin Gross --- Created attachment 109453 --> https://bugs.kde.org/attachment.cgi?id=109453&action=edit This is the 'drill down' to the Education category >From this drill down a variety of data points can be edited. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387970] Drill down backwards (via link) from a report to all transactions that support the report's number
https://bugs.kde.org/show_bug.cgi?id=387970 --- Comment #4 from Robin Gross --- Created attachment 109452 --> https://bugs.kde.org/attachment.cgi?id=109452&action=edit Shows annual summary of expenses - really nothing usual here -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 388044] Renku 0.4.1 is unusable on KDE Neon due to lack of setup/documentation
https://bugs.kde.org/show_bug.cgi?id=388044 --- Comment #1 from G --- This is the original console output before I installed akonadi and akonadi-mysql-backend in an effort to get this to work: org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/user/.local/share/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/user/.local/share/akonadi/akonadiserver-cmd.socket" kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "ldap" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387280] Make 4.8.2 release
https://bugs.kde.org/show_bug.cgi?id=387280 --- Comment #2 from Ralf Habacker --- If nobody has any objections I would schedule release 4.8.2 for the beginning of February 2018. If anyone wants to work on the translation issues listed in this or this assigned ticket, this should happen as soon as possible, as experience has shown that it takes some time for the solutions to arrive in the appropriate translations -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 388044] New: Renku 0.4.1 is unusable on KDE Neon due to lack of setup/documentation
https://bugs.kde.org/show_bug.cgi?id=388044 Bug ID: 388044 Summary: Renku 0.4.1 is unusable on KDE Neon due to lack of setup/documentation Product: zanshin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: er...@kde.org Reporter: ironst...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Renku installs and starts on KDE Neon, however it is completely unusable because it seems to require a storage/resource backend or something that does not exist on a default install (akonadi? ldap?). The app sits there looking pretty, if you click "New item" it tells you to type something in the box and hit enter to create an item. When the user does this nothing happens, the item is not created, there is no error message, the textbox is just cleared to indicate the input was accepted and seemingly just discarded. There's a Settings->Configure Renku screen that seems to suggest a resource might be required to act as backend storage, but there's no information on what RESOURCE or what format is expected in the "Add resource" field. Requiring users to have developer knowledge of Renku in order to get it to work is a surefire reason why nobody is going to use it no matter how cool it is. Here's the output to the console while running Renku: helix:~$ renku org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/user/.local/share/akonadi/akonadiserver-cmd.socket" Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/user/.local/share/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadiserver: Did not find MySQL server default configuration (mysql-global.conf) org.kde.pim.akonadiserver: Failed to remove runtime connection config file org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally... kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "ldap" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 382195] Not all installed languages are visible on Windows
https://bugs.kde.org/show_bug.cgi?id=382195 Ralf Habacker changed: What|Removed |Added Blocks|381786 |387280 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=381786 [Bug 381786] Make release 4.8.1 https://bugs.kde.org/show_bug.cgi?id=387280 [Bug 387280] Make 4.8.2 release -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 381786] Make release 4.8.1
https://bugs.kde.org/show_bug.cgi?id=381786 Ralf Habacker changed: What|Removed |Added Depends on|382195 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=382195 [Bug 382195] Not all installed languages are visible on Windows -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387280] Make 4.8.2 release
https://bugs.kde.org/show_bug.cgi?id=387280 Ralf Habacker changed: What|Removed |Added Depends on||382195 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=382195 [Bug 382195] Not all installed languages are visible on Windows -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387280] Make 4.8.2 release
https://bugs.kde.org/show_bug.cgi?id=387280 Ralf Habacker changed: What|Removed |Added Depends on||387040 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=387040 [Bug 387040] Git commit c829ec79 broke investment price chart -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 381786] Make release 4.8.1
https://bugs.kde.org/show_bug.cgi?id=381786 Ralf Habacker changed: What|Removed |Added Depends on|387040 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=387040 [Bug 387040] Git commit c829ec79 broke investment price chart -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 387040] Git commit c829ec79 broke investment price chart
https://bugs.kde.org/show_bug.cgi?id=387040 Ralf Habacker changed: What|Removed |Added Blocks|381786 |387280 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=381786 [Bug 381786] Make release 4.8.1 https://bugs.kde.org/show_bug.cgi?id=387280 [Bug 387280] Make 4.8.2 release -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 381786] Make release 4.8.1
https://bugs.kde.org/show_bug.cgi?id=381786 --- Comment #18 from Ralf Habacker --- The completed translation state has not been changed very much in the last month, so I'm planning to release an 4.8.1 source tarball (from tag 4.8.1) with recent translations at the end of this week. The plan is to submit the tarball at 2017/12/23 to upload.kde.org with the hope that it will be available at 2017/12/24. It would be nice if someone can prepare a news entry for the website and send it to me or push it into the websites/kmymoney-org at that time. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 388040] Extra dependencies on kamoso/master
https://bugs.kde.org/show_bug.cgi?id=388040 --- Comment #1 from Aleix Pol --- Also libudev-dev. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 388042] New: Renku Documentation Handbook is a 404
https://bugs.kde.org/show_bug.cgi?id=388042 Bug ID: 388042 Summary: Renku Documentation Handbook is a 404 Product: zanshin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: er...@kde.org Reporter: ironst...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Help -> Renku Documentation Handbook takes the user to a page basically saying that there is no KDE documentation for this project. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 388043] New: Zanshin crashes at startup
https://bugs.kde.org/show_bug.cgi?id=388043 Bug ID: 388043 Summary: Zanshin crashes at startup Product: zanshin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: er...@kde.org Reporter: dnico...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Zanshin has started crashing at startup after updating to applications 17.12. It crashes both standalone and inside kontact. KDE Frameworks 5.41.0 Qt 5.9.3 (built against 5.9.3) I think there was something about a new connect API for akonadi in the release notes for kontact. Maybe that's the issue? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 387979] Plasmashell and latte dock crashes due abnormal behavior of kactivitymanagerd
https://bugs.kde.org/show_bug.cgi?id=387979 --- Comment #4 from Ivan Čukić --- > I have also observed that in concomitance of the docks' show and hide in an > endless loop, I see too open and close cyclically a process called > kactivitymanagerd i and although I have closed all the main Can you explain this? Could you test the communication between plasma and kactivitymanagerd using bustle (a tool for inspecting d-bus messages)? I'll leave this assigned to kactivitymanagerd for the time being although I'm 99% sure it is just an innocent bystander in this bug since it has nothing to do with plasma panels/docks :) -- You are receiving this mail because: You are watching all bug changes.
