[kate] [Bug 490976] New: [WISH] Download editor color themes using KNewStuff
https://bugs.kde.org/show_bug.cgi?id=490976 Bug ID: 490976 Summary: [WISH] Download editor color themes using KNewStuff Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: di...@sinestesia.co Target Milestone: --- SUMMARY There are some editor themes for kate at: https://store.kde.org/browse?cat=472&ord=latest It'd be great if kate had a button to download more themes using KNewStuff like we can do with widgets, wallpapers, app color schemes, etc. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490369] [WISH] Open LSP Symbols and bookmarks through Quick Open (pluggable QO?)
https://bugs.kde.org/show_bug.cgi?id=490369 --- Comment #4 from Diego Gangl --- Sorry for the delay. Just tested this. It does work the Typescript server. I couldn't get anything from Dart or Pyright (but that's a custom config anyways). I guess that part of this request is done, even if it is with a different shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490369] [WISH] Open LSP Symbols and bookmarks through Quick Open (pluggable QO?)
https://bugs.kde.org/show_bug.cgi?id=490369 --- Comment #2 from Diego Gangl --- Thanks, I didn't know that one. However it works a bit different to what I'm proposing, since it only lists symbols in the current document rather than the entire project -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490379] [wish] Don't move the next/prev location arrows into the tab bar
https://bugs.kde.org/show_bug.cgi?id=490379 --- Comment #1 from Diego Gangl --- Created attachment 171720 --> https://bugs.kde.org/attachment.cgi?id=171720&action=edit Proposed -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490379] New: [wish] Don't move the next/prev location arrows into the tab bar
https://bugs.kde.org/show_bug.cgi?id=490379 Bug ID: 490379 Summary: [wish] Don't move the next/prev location arrows into the tab bar Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: di...@sinestesia.co Target Milestone: --- Created attachment 171719 --> https://bugs.kde.org/attachment.cgi?id=171719&action=edit How the arrows currently look SUMMARY This is a cosmetic change. When we open a single file in kate the arrow buttons to move to previous/next location are in the navigation bar, which makes sense. However once we open a second tab, they go up into the tab bar. Once you open several tabs you get another set of arrows on the opposite side of the tab bar. So, now you have two sets of roughly similar arrows on two ends of the tab bar that do very different things. I've grown used to this now, but it was baffling while I was initally testing Kate. My proposal is to always leave the navigation arrows in the navigation bar. I think they make more sense there, and it would make the UI cleaner. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490369] New: [WISH] Open LSP Symbols and bookmarks through Quick Open (pluggable QO?)
https://bugs.kde.org/show_bug.cgi?id=490369 Bug ID: 490369 Summary: [WISH] Open LSP Symbols and bookmarks through Quick Open (pluggable QO?) Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: di...@sinestesia.co Target Milestone: --- SUMMARY It would be awesome to be able to navigate the project's LSP symbols (functions, classes, etc) through the Quick Open (ctrl+alt+o) dialog, as well as bookmarks. Maybe the way forward for this would be to make QO pluggable, so the LSP and bookmark plugins can register models or callbacks for it. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 490195] New: [wish] gc to toggle comments
https://bugs.kde.org/show_bug.cgi?id=490195 Bug ID: 490195 Summary: [wish] gc to toggle comments Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Vi Input Mode Assignee: kwrite-bugs-n...@kde.org Reporter: di...@sinestesia.co Target Milestone: --- SUMMARY Kate has an action to toggle commenting using "ctrl+/". In Vim and NeoVim this is done using the "gc" movement. It would be nice to have this movement in VIMode in kate, since it's muscle memory for many vimmers. References: https://github.com/neovim/neovim/pull/28176 https://github.com/numToStr/Comment.nvim https://github.com/tpope/vim-commentary (the original) Motions aren't super necessary as long as it also works from visual mode. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 489696] [WISH] Mark modified files (in git) in project file browser
https://bugs.kde.org/show_bug.cgi?id=489696 --- Comment #3 from Diego Gangl --- Hi, yes I use commit/staging widget but what I meant was inside the file browser (the one that comes with the projects plugin). Maybe it has a different name? The tooltip only says "Projects". I attached a screenshot from VSCode to clarify: https://bugs.kde.org/attachment.cgi?id=171554 Note the M on a modified file and U on a new one (and the different colors) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 489696] [WISH] Mark modified files (in git) in project file browser
https://bugs.kde.org/show_bug.cgi?id=489696 --- Comment #2 from Diego Gangl --- Created attachment 171554 --> https://bugs.kde.org/attachment.cgi?id=171554&action=edit Example from VSCode -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 489696] New: [WISH] Mark modified files (in git) in project file browser
https://bugs.kde.org/show_bug.cgi?id=489696 Bug ID: 489696 Summary: [WISH] Mark modified files (in git) in project file browser Classification: Applications Product: kate Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: di...@sinestesia.co Target Milestone: --- SUMMARY It would be great to see at a glance which files were modified or are untracked in git in the projects file browser. It could be a different color for the text or an icon to the right side. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 489692] New: [WISH] Show changes in git in gutter
https://bugs.kde.org/show_bug.cgi?id=489692 Bug ID: 489692 Summary: [WISH] Show changes in git in gutter Classification: Applications Product: kate Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: di...@sinestesia.co Target Milestone: --- SUMMARY There's an option to mark which lines have changed or unsaved lines in the left side border, but this only accounts for the time the file has been open and edited in kate. This isn't super useful when working with a VCS, and it's often confusing since one might think there are uncommited changes but it's really a line that was changed at some point and it's already saved and commited. It would be nice to have the same highlights but showing what has changed in Git (or any VCS the project plugin supports). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 301447] Desktop grid effect changes activities
https://bugs.kde.org/show_bug.cgi?id=301447 --- Comment #14 from Diego Gangl --- Thanks Vlad, and thanks Marcin for bringing this back to life! -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394575] New: Enqueue and play
https://bugs.kde.org/show_bug.cgi?id=394575 Bug ID: 394575 Summary: Enqueue and play Product: elisa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: dnico...@gmail.com Target Milestone: --- I think I've found a blind spot in elisa's UI/UX. There's no way to play a track immediately without losing the entire playlist or enqueuing it and then having to scroll down to find it. There's also no search function in the playlist, which means the only way to play a specific track, even if it is in the playlist, is to find it in a view, add it and then scroll all the way to the bottom to play it. I recently noticed this with a 6000 track playlist and it's a bummer :) It'd be nice to have search in the playlist and and option to enqueue and play. I don't think it needs to be an extra button though, maybe holding ctrl turns the enqueue button's text to "enqueue and play" and then clicking adds and plays the song right away. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394332] Albums with the same name get merged
https://bugs.kde.org/show_bug.cgi?id=394332 --- Comment #2 from Diego Gangl --- Here's a couple of them (using ffprobe): --- Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '01 Gimme All Your Lovin'.m4a': Metadata: major_brand : M4A minor_version : 0 compatible_brands: M4A mp42isom creation_time : 2006-11-30 11:21:03 track : 1/18 disc: 1/1 genre : Rock album : Greatest Hits album_artist: ZZ Top artist : ZZ Top composer: Beard/Gibbons/Hill --- Input #0, mp3, from 'Mystify.mp3': Metadata: replaygain_track_gain: -0.00 dB replaygain_track_peak: 0.428690 title : Mystify album : Greatest Hits artist : INXS Duration: 00:03:16.52, start: 0.025056, bitrate: 218 kb/s --- Input #0, mp3, from 'Another One Bites The Dust.mp3': Metadata: replaygain_track_gain: +1.06 dB replaygain_track_peak: 0.722210 title : Another One Bites The Dust album : Greatest Hits artist : Queen Duration: 00:03:37.07, start: 0.00, bitrate: 134 kb/s --- Input #0, mp3, from '01 American Girl.mp3': Metadata: track : 1 replaygain_track_gain: -0.87 dB replaygain_track_peak: 0.499961 title : American Girl artist : Tom Petty & The Heartbreakers album : Greatest Hits genre : Rock date: 1993 Duration: 00:03:32.88, start: 0.00, bitrate: 321 kb/s Is there a quick way to list them all? There's about 5-6 albums mixed in. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394333] New: Better shuffle
https://bugs.kde.org/show_bug.cgi?id=394333 Bug ID: 394333 Summary: Better shuffle Product: elisa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: dnico...@gmail.com Target Milestone: --- Right now when shuffle is enabled Elisa seems to pick a random song every time we skip/finish playing a track. The problem with this is that sometimes we end up with the same song twice in a row (or more), or the same song being played multiple times in a short span of time. Another problem is that if we accidentally skipped a song we wanted to hear, we can't go back because the previous button picks a new song. A better solution would be to pre-shuffle the list internally and then play it in sequence. That ensures that songs are only played once per playlist playthrough and we can go back to previous songs. When the end of the list is reached, re-shuffle it and start again (if repeat is enabled). -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 394332] New: Albums with the same name get merged
https://bugs.kde.org/show_bug.cgi?id=394332 Bug ID: 394332 Summary: Albums with the same name get merged Product: elisa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: dnico...@gmail.com Target Milestone: --- When you have two or more albums with the same but from different artists they end up getting "merged" in the DB. I noticed this because I have multiple "Greatest Hits" albums that ended up merged in a single album with the artist set to "Various Artists". Version: Elisa from master -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 392989] Spacebar should always play/pause irrespective of focus
https://bugs.kde.org/show_bug.cgi?id=392989 Diego Gangl changed: What|Removed |Added Severity|normal |wishlist CC||dnico...@gmail.com --- Comment #1 from Diego Gangl --- Agree, I think we should have far more global hotkeys in Elisa. It would more ergonomic and customizable. Matthieu, what do you think about making a task in phabricator to track this? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 392781] Allow hiding the playlist panel
https://bugs.kde.org/show_bug.cgi?id=392781 Diego Gangl changed: What|Removed |Added CC||dnico...@gmail.com --- Comment #5 from Diego Gangl --- Why not put it in the main menu? It's not something users will be changing very often. I'd put it above "Configure Elisa". -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 389136] Some songs are not shown(git)
https://bugs.kde.org/show_bug.cgi?id=389136 Diego Gangl changed: What|Removed |Added CC||dnico...@gmail.com --- Comment #4 from Diego Gangl --- I came here to mention post this bug too. MP3s without an album don't show up at all. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 390644] New: The filter bar can be seen in the album view when there is only one song
https://bugs.kde.org/show_bug.cgi?id=390644 Bug ID: 390644 Summary: The filter bar can be seen in the album view when there is only one song Product: elisa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: dnico...@gmail.com Target Milestone: --- Created attachment 110761 --> https://bugs.kde.org/attachment.cgi?id=110761&action=edit The filter bar sneaking under the listview The contents filter bar can be seen leaking below the listview when looking at the tracks in an album. This only happens when the album has a single song and the bar is collapsed (See image). -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 380442] Coverart saved in file is not displayed.
https://bugs.kde.org/show_bug.cgi?id=380442 Diego Gangl changed: What|Removed |Added CC||kdeb...@fratti.ch --- Comment #4 from Diego Gangl --- *** Bug 390326 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 390326] elisa should extract cover art from file metadata
https://bugs.kde.org/show_bug.cgi?id=390326 Diego Gangl changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Diego Gangl --- *** This bug has been marked as a duplicate of bug 380442 *** -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 390326] elisa should extract cover art from file metadata
https://bugs.kde.org/show_bug.cgi?id=390326 Diego Gangl changed: What|Removed |Added CC||dnico...@gmail.com --- Comment #2 from Diego Gangl --- Bandcamp albums work for me too. The other bit about the tracks metadata has already been reported and is being tracked in task T6255 (https://phabricator.kde.org/T6255) -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 389697] Calling the elisa binary while it's also running makes it crash
https://bugs.kde.org/show_bug.cgi?id=389697 --- Comment #3 from Diego Gangl --- Thanks! I can confirm it's fixed -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 389697] New: Calling the elisa binary while it's also running makes it crash
https://bugs.kde.org/show_bug.cgi?id=389697 Bug ID: 389697 Summary: Calling the elisa binary while it's also running makes it crash Product: elisa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: dnico...@gmail.com Target Milestone: --- Running elisa and then trying to run another instance makes the first elisa crash (and the second one never start). This is what I get when trying to run another instance: --- "Message recipient disconnected from message bus without replying" --- This is what the original instance prints when it dies: --- AbstractFileListing::emitNewFiles 501 AbstractFileListing::emitNewFiles 501 AbstractFileListing::emitNewFiles 501 AbstractFileListing::emitNewFiles 454 ASSERT: "!isEmpty()" in file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, line 351 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = elisa path = /home/januz/code/Elisa Music Player/build/src pid = 9107 KCrash: Arguments: /home/januz/code/Elisa Music Player/build/src/elisa KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 pa_write() failed while trying to wake up the mainloop: Bad file descriptor pa_write() failed while trying to wake up the mainloop: Bad file descriptor pa_write() failed while trying to wake up the mainloop: Bad file descriptor Invalid write to eventfd: Bad file descriptor Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post(). Aborting. Unable to start Dr. Konqi -- 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 #5 from Diego Gangl --- Just got the update, I can confirm it works now. Thanks! -- 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/sy
[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.
