[ring-kde] [Bug 419933] cannot install banji
https://bugs.kde.org/show_bug.cgi?id=419933 --- Comment #1 from Emmanuel Lepage Vallée --- I don't really expect it to work right now. The problem with Banji is that many of the dependencies are moving targets with unstable APIs. It works for a while then break until I fix it. I gave up on making the build reliable (and given up trying too). I plan to fix it as a one-off in a few weeks to upgrade some dependency. My old appimages are getting rusty. I mainly use it for the SIP part. Is there any specific reason why you want Banji? I mean, for SIP or for GNU_Jami/Ring.CX network? -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404263] It is not possible to accept/reject contact requests in the Banji interface
https://bugs.kde.org/show_bug.cgi?id=404263 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 383936] [feature] Fully support contact request
https://bugs.kde.org/show_bug.cgi?id=383936 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404675] When there is no selected individual, the sidebar should not be enabled.
https://bugs.kde.org/show_bug.cgi?id=404675 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404257] All "online" labels are hardcoded
https://bugs.kde.org/show_bug.cgi?id=404257 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404351] The timeline scrollbar has usability issues on mobile
https://bugs.kde.org/show_bug.cgi?id=404351 --- Comment #1 from Emmanuel Lepage Vallée --- It was removed from the mobile layout for now. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404260] The contact list element have alignment issues
https://bugs.kde.org/show_bug.cgi?id=404260 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404258] The "answer" button regressed
https://bugs.kde.org/show_bug.cgi?id=404258 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Emmanuel Lepage Vallée --- I think the root cause was identified and fixed. I cannot reproduce anymore. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404254] Finger scrolling on Android is nearly unusable
https://bugs.kde.org/show_bug.cgi?id=404254 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404010] Inappropriately uses the material style by default when run on a KDE Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=404010 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Emmanuel Lepage Vallée --- The material style is no longer used on desktop Linux. There is now the proper infrastructure to compile different qtquickcontrols2 config file for each platforms. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404004] After quitting, app doesn't exit cleanly
https://bugs.kde.org/show_bug.cgi?id=404004 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Emmanuel Lepage Vallée --- It seems most issues have been dealt with. There might still be a few. They should be in their own bug report with the step to reproduce them. Note that closing the window doesn't quit. If it did you could not receive calls. There should be a status notifier icon in the systray. But there's a quit button in the global drawer and it doesn't make the app crash (which was why it wasn't there before). -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 383974] The account own "contact" is sometime visible in the timeline
https://bugs.kde.org/show_bug.cgi?id=383974 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 383972] The peerstimeline proxy order is unstable/racy
https://bugs.kde.org/show_bug.cgi?id=383972 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404014] Left drawer has an item with no label and a rightward-pointing arrow
https://bugs.kde.org/show_bug.cgi?id=404014 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404024] Wizard create new account page: After clicking "Next", there are two redundant progress spinners
https://bugs.kde.org/show_bug.cgi?id=404024 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404008] Welcome screen: search field in toolbar doesn't look like a search field
https://bugs.kde.org/show_bug.cgi?id=404008 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Emmanuel Lepage Vallée --- Turns out this is a regression in Qt 5.12 From https://doc.qt.io/qt-5/qml-qtquick-controls2-textfield.html#background-prop > Note: If the background item has no explicit size specified, it automatically > follows the control's size. In most cases, there is no need to specify width > or > height for a background item. This is currently not true with the Material theme on 5.12. The size was 0x0 until I set "height: search.height; width: search.width" on the background item. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396411] Make the header more flexible
https://bugs.kde.org/show_bug.cgi?id=396411 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Emmanuel Lepage Vallée --- Fixed in git -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404673] Adding someone using a ringid alone regressed
https://bugs.kde.org/show_bug.cgi?id=404673 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404361] Not all multimedia actions can work on mobile
https://bugs.kde.org/show_bug.cgi?id=404361 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404676] New: When searching is not going to work, don't let the user search
https://bugs.kde.org/show_bug.cgi?id=404676 Bug ID: 404676 Summary: When searching is not going to work, don't let the user search Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- When the following is met: * There is not contacts *AND* no chat history *AND* no bookmarks Along with: * There is no account *OR* there is no enabled accounts *OR* no Internet Currently you can search, but there is no results and no message nor a close button. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404677] New: The sidebar profile list doesn't get updated
https://bugs.kde.org/show_bug.cgi?id=404677 Bug ID: 404677 Summary: The sidebar profile list doesn't get updated Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- If the account is no up when Banji starts, it never appears in the drawer. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404675] New: When there is no selected individual, the sidebar should not be enabled.
https://bugs.kde.org/show_bug.cgi?id=404675 Bug ID: 404675 Summary: When there is no selected individual, the sidebar should not be enabled. Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- Otherwise you can do actions on null. It doesn't crash, but is very wrong. Also, there should be a message welcoming the user since it can only happen before using the apps for the first time. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404674] New: Failed calls sometime keeps the appearance of being ongoing
https://bugs.kde.org/show_bug.cgi?id=404674 Bug ID: 404674 Summary: Failed calls sometime keeps the appearance of being ongoing Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- When calling someone who was very recently online, but closed their computer, calls have the little initialization wheel going on for ever, long after the daemon gave up completing the handshake. That problem might be in the daemon, it needs to be investigated. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404673] New: Adding someone using a ringid alone regressed
https://bugs.kde.org/show_bug.cgi?id=404673 Bug ID: 404673 Summary: Adding someone using a ringid alone regressed Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- It can be done by adding a contact manually, which is hidden deep, but still possible. However it was intended to work by pasting it in the searchbox, but this somehow no longer pass the validation and the result is "disabled" and you cannot click on it with a wrong "this is invalid" message. Some validation code is having false negatives again. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404672] New: Knowing the RingId of the peer or ourself is cumbersome.
https://bugs.kde.org/show_bug.cgi?id=404672 Bug ID: 404672 Summary: Knowing the RingId of the peer or ourself is cumbersome. Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- There used to be a "share" dialog with the ability to print QR codes, send them by email or copy the. This is gone. Going into the account setting page is hit and miss with all its bugs. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404671] New: When a message fails to be delivered, be clear about it
https://bugs.kde.org/show_bug.cgi?id=404671 Bug ID: 404671 Summary: When a message fails to be delivered, be clear about it Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- At some point it was in the statusbar, but there is no statusbar anymore. At some other points it was next to each message, but that was noisy, slow and was removed. So now you send messages, they may fail and internally it is known, but it isn't displayed. A new error disclosure message is definitely needed. Maybe also playing with the color or opacity of the outgoing messages. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404561] Make sure importing Jami account works
https://bugs.kde.org/show_bug.cgi?id=404561 --- Comment #1 from Emmanuel Lepage Vallée --- " yeah, went to import, then got back, then went to create, got back, clicked import again, it crashed" -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404561] New: Make sure importing Jami account works
https://bugs.kde.org/show_bug.cgi?id=404561 Bug ID: 404561 Summary: Make sure importing Jami account works Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- This hasn't been tried in a long time and was reported to crash. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404555] Make sure the pagerow always works properly
https://bugs.kde.org/show_bug.cgi?id=404555 --- Comment #1 from Emmanuel Lepage Vallée --- Forgot: Calls ends while the call page is not visible * Remove silently without an animation -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404555] New: Make sure the pagerow always works properly
https://bugs.kde.org/show_bug.cgi?id=404555 Bug ID: 404555 Summary: Make sure the pagerow always works properly Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- What should work: * Adding a new contact * hide call when inactive * show chat expanded * select in the list page * Clicking on a timeline contact * Show the chat on mobile, keep the current state in wide mode * Click chat action during a call * Keep the call page, but show the chat page on the left (not expanded) * Click chat action without an active call * Remove the call page * Click the call / screen share / video chat without an active call * Show and expand the call page (with animation) * Click on the call / screen share / video chat actions during a call * Expand the chat page * When a call ends * No animation * When a new incoming call arrives * Show the call page, not expanded * When accepting a new call with the chat page visible * Expand the call page * When scrolling on mobile with an active call * [list] [chat] [call] * When scrolling on mobile from the call page without an active call * Delete the call page, then [list] [chat] -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404349] The "call group" section of the chat doesn't scale either way
https://bugs.kde.org/show_bug.cgi?id=404349 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Emmanuel Lepage Vallée --- Not pixel perfect, but functionally done. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404261] The network error (and all other possible runtime issues) box is nearly invisible
https://bugs.kde.org/show_bug.cgi?id=404261 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Emmanuel Lepage Vallée --- It is now misaligned, but use a very bright and visible orange in the sidebar. The header one not being visible enough is not irrelevant. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404257] All "online" labels are hardcoded
https://bugs.kde.org/show_bug.cgi?id=404257 --- Comment #1 from Emmanuel Lepage Vallée --- Progress has been made -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404013] Nothing on the left drawer works
https://bugs.kde.org/show_bug.cgi?id=404013 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Emmanuel Lepage Vallée --- The global drawer no longer uses the mockup values. While the config dialog it uses wasn't designed for mobile and doesn't really work on it, it will do until a simpler version is implemented. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404023] Wizard (all pages) back button is not left-aligned
https://bugs.kde.org/show_bug.cgi?id=404023 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Emmanuel Lepage Vallée --- This has been fixed in Kirigami (new feature to disable bottom heavyness on Android for already bottom heavy apps). The new feature is now used in Banji. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404256] The Emoji chatbox is not working on Android
https://bugs.kde.org/show_bug.cgi?id=404256 Emmanuel Lepage Vallée changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Emmanuel Lepage Vallée --- This has been fixed -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404116] Text input field doesn't scroll or get tallerwhen multiline text is really long
https://bugs.kde.org/show_bug.cgi?id=404116 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Emmanuel Lepage Vallée --- This has been fixed in the branch -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404361] New: Not all multimedia actions can work on mobile
https://bugs.kde.org/show_bug.cgi?id=404361 Bug ID: 404361 Summary: Not all multimedia actions can work on mobile Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- Some actions are unsupported on some platforms by the upstream libring ring-kde relies on for the Android and AppImage support. Some other actions also makes no sense or have no corresponding GUI components in the simpler Banji client. To work around this, the solution will be to add a new UserActionFilter QML component. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404355] New: The chat contains some events the user might not care about.
https://bugs.kde.org/show_bug.cgi?id=404355 Bug ID: 404355 Summary: The chat contains some events the user might not care about. Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- There is about a dozens type of events being shown in the chat view. Some users might not be interested in them and they slow down the UI on mobile due to the extra computing required. On top of that, the sidebar summary proposed by the VDG is slower because it computes too much elements that ends up not being displayed. The fix will be to provide a timeline filter model to remove the noise and a bunch of new KConfig/QmlActions to turn on and off some categories in the context drawer. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404351] New: The timeline scrollbar has usability issues on mobile
https://bugs.kde.org/show_bug.cgi?id=404351 Bug ID: 404351 Summary: The timeline scrollbar has usability issues on mobile Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- When the chat contains event placed across multiple days, a logarithmic scale time categories list is displayed. It works great in wide mode, but hide parts of the message (and it laggy) in non-wide mode. It is also very useful to help locate messages. But is (pretty) visual noise when you are not trying to locate some messages. In wide mode, it falls in the, "what the hell, there's plenty of room and it's pretty" category, but on mobile it's annoying. To fix this, I plan to add a special mode where this thing is only displayed when you press on a special mobile scrollbar handle. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404349] New: The "call group" section of the chat doesn't scale either way
https://bugs.kde.org/show_bug.cgi?id=404349 Bug ID: 404349 Summary: The "call group" section of the chat doesn't scale either way Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- Currently, calls done in the same event group (consecutive instance of the same category of events within a restricted amount of time) are added as small icons. It works best with 3-10 calls in the same group, but isn't useful with a single call or a large amount of calls. At some point you get a huge rectangle with dozens of icons. Hopefully it never happens "in real life" since the odds of calling the same person dozens of time in a row isn't worth considering. However that leaves the single call case, which is by far the most common case. This alone makes this bugs worth fixing. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404269] New: Incoming messages are always `unread` even in live chat
https://bugs.kde.org/show_bug.cgi?id=404269 Bug ID: 404269 Summary: Incoming messages are always `unread` even in live chat Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- At some point there was code to detect when the window had focus, but this needs to be improved. The old client also had a "mark all messages as read" button and it has no equivalent in Banji. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404263] New: It is not possible to accept/reject contact requests in the Banji interface
https://bugs.kde.org/show_bug.cgi?id=404263 Bug ID: 404263 Summary: It is not possible to accept/reject contact requests in the Banji interface Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: emmanuel.lep...@kde.org Reporter: emmanuel.lep...@kde.org Target Milestone: --- There is nowhere to do it yet -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404262] New: Find a way to display anonymous without a long HEX string
https://bugs.kde.org/show_bug.cgi?id=404262 Bug ID: 404262 Summary: Find a way to display anonymous without a long HEX string Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- Many accounts are anonymous, they have no display name. Right now it will display a wide hexadecimal string to identify them. Once upon a time it was using "Unknown" but people complained. Maybe "Anonymous ()" where is the first 8 chars of the hex hash. Or maybe go back to Uri Herrera solution and color code everybody, but this is hard on accessibility, which I care about. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404261] New: The network error (and all other possible runtime issues) box is nearly invisible
https://bugs.kde.org/show_bug.cgi?id=404261 Bug ID: 404261 Summary: The network error (and all other possible runtime issues) box is nearly invisible Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- Because it uses an SVG for the icon and it gets scaled down, the line get so fine it becomes 90% transparent. Drawing the icon using QPainter+QSvgRenderer or QtQuick.Shape would help solve the issue. Good error handling is pointless when invisible... -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404260] New: The contact list element have alignment issues
https://bugs.kde.org/show_bug.cgi?id=404260 Bug ID: 404260 Summary: The contact list element have alignment issues Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- The text is top aligned instead of centered. (reported on Telegram) -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404259] New: When a page from the pagerow is added/removed, the chat is no longer aligned
https://bugs.kde.org/show_bug.cgi?id=404259 Bug ID: 404259 Summary: When a page from the pagerow is added/removed, the chat is no longer aligned Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- It can also be downright out of sight too. This is because it is rendered during the page change animation and the size changed by the time it is done rendering, and this doesn't triggers a repaint. Still, it's a rather major bug because you have to rotate the phone or resize the window to get rid of it -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404258] New: The "answer" button regressed
https://bugs.kde.org/show_bug.cgi?id=404258 Bug ID: 404258 Summary: The "answer" button regressed Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- I don't know why, maybe Qt, maybe dring, maybe me, but it was there a few weeks ago and now it's always marked as unavailable for no reason. The logic hasn't been modified in many years. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404113] Clicking on a contact in the contacts column does not navigate anywhere
https://bugs.kde.org/show_bug.cgi?id=404113 --- Comment #3 from Emmanuel Lepage Vallée --- It works on Android, that's the mitigation. But the bug is in the PageRow and it's getting rewritten, so I wait for this. I can fix /that/, but it will regress the other one (the main actions) and I rather have those working on desktop. On mobile I added a Kirigami.Settings.isMobile and "fixed" it, which broke the main actions. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404257] New: All "online" labels are hardcoded
https://bugs.kde.org/show_bug.cgi?id=404257 Bug ID: 404257 Summary: All "online" labels are hardcoded Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- * The profile * The toolbar * The sidebar -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404256] New: The Emoji chatbox is not working on Android
https://bugs.kde.org/show_bug.cgi?id=404256 Bug ID: 404256 Summary: The Emoji chatbox is not working on Android Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- The emojis are not aligned within their button, so the end up invisible. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404254] New: Finger scrolling on Android is nearly unusable
https://bugs.kde.org/show_bug.cgi?id=404254 Bug ID: 404254 Summary: Finger scrolling on Android is nearly unusable Product: ring-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elv1...@gmail.com Reporter: elv1...@gmail.com Target Milestone: --- Because of the pagerow taking all input in the "x" direction, scolling the chat in the "y" and pressing the bubbles taking "clicks", the input handling gets confused and doesn't behave properly. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404113] Clicking on a contact in the contacts column does not navigate anywhere
https://bugs.kde.org/show_bug.cgi?id=404113 --- Comment #1 from Emmanuel Lepage Vallée --- This was mitigated last week, but will benefit from the C++ rewrite of the kirigami.pagerow. Right now Banji has JavaScript code to rewrite the pagestack because adding and removing pages such as chat isn't as well supported as the documentation make it seem. This is a side effect of these bugs (setting the current index stops working). -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 383718] file collisions with already installed libringclient
https://bugs.kde.org/show_bug.cgi?id=383718 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Emmanuel Lepage Vallée --- There was an hard fork to solve this issue. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404112] "Scroll to bottom" button should animate the scroll rather than just jumping there with no transition
https://bugs.kde.org/show_bug.cgi?id=404112 --- Comment #3 from Emmanuel Lepage Vallée --- Cross fading would work -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404023] Wizard (all pages) back button is not left-aligned
https://bugs.kde.org/show_bug.cgi?id=404023 --- Comment #6 from Emmanuel Lepage Vallée --- > There is no reason to have the drawer accessible while the user is doing the > wizard. To quit? (assuming quit is fixed) -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404019] Logo is low resolution and pixellated in the wizard
https://bugs.kde.org/show_bug.cgi?id=404019 --- Comment #6 from Emmanuel Lepage Vallée --- It's great, but it was designed for all GNU Ring clients. If Ring-KDE (or whatever name it ends up with) and Banji have the same icon, this will be weird. Banji is a chat app, Ring-KDE is a VoIP app. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 404114] When on the main view, back button doesn't look enabled even when it is
https://bugs.kde.org/show_bug.cgi?id=404114 Emmanuel Lepage Vallée changed: What|Removed |Added Product|ring-kde|frameworks-kirigami Component|general |general Assignee|elv1...@gmail.com |notm...@gmail.com Target Milestone|--- |Not decided Version|unspecified |Master --- Comment #1 from Emmanuel Lepage Vallée --- Moving the bug to Kirigami, this is a widget implicitly provided by Kirigami. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404112] "Scroll to bottom" button should animate the scroll rather than just jumping there with no transition
https://bugs.kde.org/show_bug.cgi?id=404112 --- Comment #1 from Emmanuel Lepage Vallée --- That would require loading all bubbles in between, if there's many of them the performance impact will be brutal on mobile. Can we come up with an animation that doesn't accidentally loads 1 QObject? Maybe something like Telegram with rounded grey rectangles. It's fine to animate the scroll when they are already loaded, but loading potentially thousands of element for an animation doesn't sound like a good idea. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404009] Welcome screen: search field element is not positioned properly by default, but fixes itself after deleting the last character in a different search field
https://bugs.kde.org/show_bug.cgi?id=404009 --- Comment #3 from Emmanuel Lepage Vallée --- (it is a bug, not arguing that) In Ring-KDE, when mobile wasn't really a priority, the welcome page was stretched to fill the whole window (all columns) and the search field was centered in the screen. The reason why this code was removed (and left half broken as it is right now) was that centering the search field doesn't leave enough space below it for the search results when the virtual keyboard is displayed. A more complex solution is probably needed. It cannot just be, oh, lets hide the welcome message when the keyboard appears" because the keyboard is auto-enabled. Leaving it at the top is also a bit weird. I wonder if the welcome screen should have 2 pages with a "next" or "got it" button when just go to the normal search page. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404012] Welcome screen: after increasing the width of the window, the light blue welcome text part obscures other things and cannot be hidden
https://bugs.kde.org/show_bug.cgi?id=404012 --- Comment #1 from Emmanuel Lepage Vallée --- Partially done, there is still corner cases -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404019] Logo is low resolution and pixellated in the wizard
https://bugs.kde.org/show_bug.cgi?id=404019 --- Comment #4 from Emmanuel Lepage Vallée --- done I still need a new logo -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404015] Wizard's first page: "Skip" button is mostly off the page
https://bugs.kde.org/show_bug.cgi?id=404015 --- Comment #2 from Emmanuel Lepage Vallée --- The skip button has been removed. This leaves more space so the issue isn't as bad (though not resolved yet, I did not work on that yet). The skip button makes sense in Ring-KDE because you can add accounts after the fact in the settings. Banji doesn't support that so skipping the wizard renders it unusable. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404038] Text chat: text entered in input field doesn't wrap and become a multi-line string
https://bugs.kde.org/show_bug.cgi?id=404038 --- Comment #1 from Emmanuel Lepage Vallée --- done -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404036] Text Chat: view doesn't automatically scroll to the bottom when new messages are sent or received
https://bugs.kde.org/show_bug.cgi?id=404036 --- Comment #1 from Emmanuel Lepage Vallée --- not very fast or scalable, but "done" -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404039] Text chat: bubbles should be limited to the width of the string inside them
https://bugs.kde.org/show_bug.cgi?id=404039 --- Comment #1 from Emmanuel Lepage Vallée --- Changes have been made but I fear I made it worst. There is a few corner case in need of a solution: ## The chat bubble is written in C++ Until 3 weeks ago, the minimum Qt version supported by Kirigami was 5.9. Qt 5.9 does not have the `Shape` module so the bubble had to use the `QQuickPaintedItem` module. 5.9 is no longer supported, so in theory this is no longer a problem. However the side still have to be determined from C++ because [while disabled for now] computing the position of a messages requires to know the size of all messsages above it and this can be multi-threaded. Storing the size is not working because it changes when you resize the window and it changes when multiple devices synchronize each other and new conversations are added. A middle ground would be to keep the code to determine the optimal size as a C++ "Metrics" object and use the QtQuick.Shape module for the rendering. I am also not sure if it would be faster or better. ## Date and metadata context: When searching or scrolling, the date and separators becomes relevant. Searching is a major pain point with Telegram because it lacks all temporal metadata when you search/scroll. If the user scrolls, either he/she is bored and want to see stuff moving or he/she is looking for something. So when the text is shorter than the date, it looks wrong. It looks even more wrong when the height is taller than the width. Vertically resizing the bubble is not possible because it makes scrolling impossible. But resizing horizontally is possible. When I did that, it had the bad side effect of "animation hangover" where too much moved on the screen. Adding "white" paddings on top and bottom and resize both horizontally and vertically made this worst. tl;dr; For now I kept a minimum width a bit bigger than the date. So this bug isn't resolved, it's just "not as bad as before". -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404023] Wizard (all pages) back button is not left-aligned
https://bugs.kde.org/show_bug.cgi?id=404023 --- Comment #4 from Emmanuel Lepage Vallée --- Oh, don't take it like that. That's a real bug, I am not arguing it, I was just referring why that weird space was added. In previous version of Kirigami, the handle was always there, you could not press back button without this space. On newer version it's moving around with no way to prevent it. Yes, you can force the toolbar **on the desktop mode**, but the `pageStack.globalToolBar.style` is ignored on mobile, so it isn't a solution either. It needs a proper fix and a proper way to detect when the space is necessary and when it is not. IMHO there should be a way to block the handle from getting there. A chat app is "naturally" bottom heavy and those controls get in the way (be it the main action button or the handle). For the Android APK, I had to delete the code from Kirigami for anything but the global toolbar because it was adding buttons on top of the chatbox. I mean, it's a real problem for Banji, the wizard button offset is just the tip of the iceberg. I understand the reason why Kirigami is bottom heavy and why it tries to fight you when you try to force the control to be at the top. However it really doesn't work in this case. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404023] Wizard (all pages) back button is not left-aligned
https://bugs.kde.org/show_bug.cgi?id=404023 --- Comment #2 from Emmanuel Lepage Vallée --- Technically it's because the Kirigami handle tends to move in that spot without prior notification and I mitigated the issue by adding that space. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404009] Welcome screen: search field element is not positioned properly by default, but fixes itself after deleting the last character in a different search field
https://bugs.kde.org/show_bug.cgi?id=404009 --- Comment #2 from Emmanuel Lepage Vallée --- I did not work on the welcome screen, I only modified the wizard -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404006] Welcome screen: text has no side margins
https://bugs.kde.org/show_bug.cgi?id=404006 --- Comment #4 from Emmanuel Lepage Vallée --- Ah, bugs that fix themselves, my job is now redundant ;) -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404006] Welcome screen: text has no side margins
https://bugs.kde.org/show_bug.cgi?id=404006 --- Comment #2 from Emmanuel Lepage Vallée --- Not sure about the fix, I didn't change anything. It's probably due to the window size being large enough to display the margins. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404025] Wizard create new account page: After clicking "Next", no progress is ever made
https://bugs.kde.org/show_bug.cgi?id=404025 --- Comment #1 from Emmanuel Lepage Vallée --- Does it still happen? Also which field were used (did you resgister an username, etc). Usually this was mostly working, at least most of the time. The C++ port was about that "most" part. I think if you clicked on something while it was creating the account it would change the QML state and get stuck. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404021] Wizard create new account page: spinner spins forever after typing a username
https://bugs.kde.org/show_bug.cgi?id=404021 --- Comment #1 from Emmanuel Lepage Vallée --- It might be fixed depending if this was due to the QML state mess or because it really fails to finish the lookup. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404013] Nothing on the left drawer works
https://bugs.kde.org/show_bug.cgi?id=404013 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Emmanuel Lepage Vallée --- Nothing is implemented. It still has the mockup actions. The "view contact details" is also using the mockup data. The sidebar is partially using some, but is now mostly using real data. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404008] Welcome screen: search field in toolbar doesn't look like a search field
https://bugs.kde.org/show_bug.cgi?id=404008 --- Comment #1 from Emmanuel Lepage Vallée --- I am a bit puzzled by this one, some /computer/ show the border and some don't. Regardless of the theme or color scheme. I did not investigate. searchbox.qml has border.width: 1 border.color: Kirigami.Theme.textColor -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404005] On desktop, window size is tall and skinny, as if it thinks my computer was a phone
https://bugs.kde.org/show_bug.cgi?id=404005 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Emmanuel Lepage Vallée --- Already fixed locally, the fix will be pushed along with the other wizard changes. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404004] After quitting, app doesn't exit cleanly
https://bugs.kde.org/show_bug.cgi?id=404004 --- Comment #1 from Emmanuel Lepage Vallée --- Known, quitting is not implemented at all yet. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 404004] After quitting, app doesn't exit cleanly
https://bugs.kde.org/show_bug.cgi?id=404004 Emmanuel Lepage Vallée changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 403097] Quick Open Search can't search by folder name
https://bugs.kde.org/show_bug.cgi?id=403097 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||elv1...@gmail.com --- Comment #1 from Emmanuel Lepage Vallée --- I confirm this regression happens on 18.12 Another little regression is that if no file is selected in the quick open, a new untitled file is selected while it would previously be equivalent to "switch to the last used file" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 402082] Directly using `modelData` in combobox isn't safe
https://bugs.kde.org/show_bug.cgi?id=402082 --- Comment #2 from Emmanuel Lepage Vallée --- In my limited testing, this works text: controlRoot.textRole != undefined ? model[controlRoot.textRole] || "": ( Array.isArray(controlRoot.model) ? modelData[controlRoot.textRole] : modelData ) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 402082] New: Directly using `modelData` isn't safe
https://bugs.kde.org/show_bug.cgi?id=402082 Bug ID: 402082 Summary: Directly using `modelData` isn't safe Product: frameworks-qqc2-desktop-style Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: --- modelData isn't always present. At least when I pass some totally fine models to the ComboBox, the content isn't visible when using qqc2-desktop-style and it is displayed in other themes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 401812] Kirigami.DelegateRecycler in CardsGridView breaks model with roleNames
https://bugs.kde.org/show_bug.cgi?id=401812 --- Comment #1 from Emmanuel Lepage Vallée --- Apparently this can be mitigated using `model.roleName` instead of `roleName`. Still, it should be a drop-in replacement so it is still a bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 401995] New: Kirigami.ListItemDragHandle could be useful if it supported GridViews too
https://bugs.kde.org/show_bug.cgi?id=401995 Bug ID: 401995 Summary: Kirigami.ListItemDragHandle could be useful if it supported GridViews too Product: frameworks-kirigami Version: 5.53.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided Changing the code of ListItemDragHandle to use QtObject instead `property ListView listView` already makes most of it "just work", but it has some corner cases. Same use case as the list, but in a grid. Grids are better for multimedia assets because for the same number of pixel, you see better. Also, it's pretty -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 401993] New: The delegate recycler have a different geometry then "raw" delegates
https://bugs.kde.org/show_bug.cgi?id=401993
Bug ID: 401993
Summary: The delegate recycler have a different geometry then
"raw" delegates
Product: frameworks-kirigami
Version: 5.53.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: elv1...@gmail.com
Target Milestone: Not decided
SUMMARY
import QtQuick 2.7
import org.kde.kirigami 2.5 as Kirigami
import QtQuick.Layouts 1.0
Kirigami.CardsListView {
ListModel {
id: topLevel
ListElement {name: "One"}
ListElement {name: "Two"}
ListElement {name: "Three"}
}
ListModel {
id: secondLevel
ListElement {name: "Alpha"}
ListElement {name: "Beta"}
ListElement {name: "Gamma"}
}
model: topLevel
delegate: Kirigami.Card {
width: parent.width
height: content.height
ColumnLayout {
id: content
height: implicitHeight
Text { text: model.name; height: 40}
ListView {
model: secondLevel
interactive: false
height: contentHeight
delegate: Rectangle {color:"red"; width: 42; height: 42}
}
}
}
}
STEPS TO REPRODUCE
1. Use the example above with and without recycler and witness the different
result
OBSERVED RESULT / EXPECTED RESULT
https://imgur.com/a/QVmOtLj
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kirigami] [Bug 401812] New: Kirigami.DelegateRecycler in CardsGridView breaks model with roleNames
https://bugs.kde.org/show_bug.cgi?id=401812 Bug ID: 401812 Summary: Kirigami.DelegateRecycler in CardsGridView breaks model with roleNames Product: frameworks-kirigami Version: 5.52.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided SUMMARY Many "ReferenceError: propertyName is not defined" errors are printed. STEPS TO REPRODUCE 1. Use CardsGridView with a model 2. Create a delagte using roles other than display OBSERVED RESULT It does not work. Many "ReferenceError: propertyName is not defined" errors are printed. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: N/A MacOS: N/A Linux/KDE Plasma: Gentoo (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: 5.52 Qt Version: 5.11.2 ADDITIONAL INFORMATION Removing `default property alias delegate: root._delegateComponent` from CardsGridView.qml fixes the problem -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 400605] Dial tones do not always work when dialing voicemail mailbox
https://bugs.kde.org/show_bug.cgi?id=400605 --- Comment #8 from Emmanuel Lepage Vallée --- Maybe you could `diff` the 2 files and get an idea what went wrong. Otherwise I assume i can close this bug? The old config dialog will be gone in v3.2 to make way for the one compatible with Android and Plasma mobile. Maybe I can work out something with the KDE VDG to make it less confusing. I don't want to go down the rabbit hole of making templates per provider. It is too hard to maintain and will always fall out of sync with their changes. SIP is a very flexible, but complex, protocol. Just for DTMF, there is 3 totally incompatible modes (ok, 2.5 modes, analog and RTP are close). And yet, it's one of the simplest part of it all. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 400605] Dial tones do not always work when dialing voicemail mailbox
https://bugs.kde.org/show_bug.cgi?id=400605 --- Comment #6 from Emmanuel Lepage Vallée --- Umm, it makes little sense. You you try to move the ~/.config/ring/dring.yml from the working machine to the not working one (with backup, of course). The way AppImage works is that they ship all dependencies internally. In theory, it should behave exactly the same on all systems (beside things like screen resolution, DPI and color scheme, of course). This probably fall into "there is too many config variables because each SIP provider do things differently and users get lost" category. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 400605] Dial tones do not always work when dialing voicemail mailbox
https://bugs.kde.org/show_bug.cgi?id=400605 --- Comment #4 from Emmanuel Lepage Vallée --- Are both systems using Ring-KDE 3.0? Did you use the AppImage or the system packages? If you didn't use the AppImage, try the AppImage on both systems (make sure to kill all `dring` process and ring-kde first or it wont start). If it works on one system and not the other one and the only change is the ring-daemon version, then the bug must be reported at ring.cx. -- You are receiving this mail because: You are watching all bug changes.
[ring-kde] [Bug 400605] Dial tones do not always work when dialing voicemail mailbox
https://bugs.kde.org/show_bug.cgi?id=400605 Emmanuel Lepage Vallée changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Emmanuel Lepage Vallée --- Have you tried to toggle between RTP and SIP DTMF modes? For some providers, one work and the other doesn't. Not saying this isn't a bug, these features come from the ring-daemon and that part of the code has decayed in recent years. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 397525] New: The multi-cursor branch crashes when Vi mode is started
https://bugs.kde.org/show_bug.cgi?id=397525 Bug ID: 397525 Summary: The multi-cursor branch crashes when Vi mode is started Product: frameworks-ktexteditor Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: multicursor Assignee: m...@svenbrauch.de Reporter: elv1...@gmail.com Target Milestone: --- Infinite recursion and stack overflow: #0 0x755a7cc0 in vfprintf () from /lib64/libc.so.6 #1 0x755aad63 in buffered_vfprintf () from /lib64/libc.so.6 #2 0x755a7e25 in vfprintf () from /lib64/libc.so.6 #3 0x756578b0 in __fprintf_chk () from /lib64/libc.so.6 #4 0x75ebf59d in qDefaultMessageHandler(QtMsgType, QMessageLogContext const&, QString const&) () from /usr/lib64/libQt5Core.so.5 #5 0x75eba0a7 in qt_message_print(QtMsgType, QMessageLogContext const&, QString const&) () from /usr/lib64/libQt5Core.so.5 #6 0x75ebbff8 in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) () from /usr/lib64/libQt5Core.so.5 #7 0x75f9ce30 in QDebug::~QDebug() () from /usr/lib64/libQt5Core.so.5 #8 0x77b31bba in KateMultiSelection::addSelectionInternal (this=0x4f739c8, newSelection=[(40, 48) -> (40, 49)], newCursor=[40, 49]) at /home/lepagee/archive/ktexteditor/src/view/katemulticursor.cpp:947 #9 0x77b32239 in KateMultiSelection::setSelectionBlock (this=0x4f739c8, encompassedBlock=[(40, 48) -> (40, 49)], cursorEdge=KateMultiCursor::Right) at /home/lepagee/archive/ktexteditor/src/view/katemulticursor.cpp:991 #10 0x77aeb9e0 in KTextEditor::ViewPrivate::toAlignedBlock (this=0x4f6c1d0, fill=false) at /home/lepagee/archive/ktexteditor/src/view/kateview.cpp:2326 #11 0x77aeb592 in KTextEditor::ViewPrivate::setBlockSelection (this=0x4f6c1d0) at /home/lepagee/archive/ktexteditor/src/view/kateview.cpp:2293 #12 0x77be132f in KateVi::VisualViMode::updateSelection (this=0x4cd2530) at /home/lepagee/archive/ktexteditor/src/vimode/modes/visualvimode.cpp:251 #13 0x77c2be05 in KateVi::VisualViMode::qt_static_metacall (_o=0x4cd2530, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7f802110) at /home/lepagee/archive/ktexteditor/build/src/KF5TextEditor_autogen/7WFH7WAJAT/moc_visualvimode.cpp:72 #14 0x76098953 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #15 0x77c3cd9e in KTextEditor::View::selectionChanged (this=0x4f6c1d0, _t1=0x4f6c1d0) at /home/lepagee/archive/ktexteditor/build/src/KF5TextEditor_autogen/OGSBNZGFXN/moc_view.cpp:439 #16 0x77b32f2d in KateMultiSelection::notifySelectionChanged (this=0x4f739c8) at /home/lepagee/archive/ktexteditor/src/view/katemulticursor.cpp:1116 #17 0x77b3225d in KateMultiSelection::setSelectionBlock (this=0x4f739c8, encompassedBlock=[(40, 48) -> (40, 49)], cursorEdge=KateMultiCursor::Right) at /home/lepagee/archive/ktexteditor/src/view/katemulticursor.cpp:993 #18 0x77aeb9e0 in KTextEditor::ViewPrivate::toAlignedBlock (this=0x4f6c1d0, fill=false) at /home/lepagee/archive/ktexteditor/src/view/kateview.cpp:2326 #19 0x77aeb592 in KTextEditor::ViewPrivate::setBlockSelection (this=0x4f6c1d0) at /home/lepagee/archive/ktexteditor/src/view/kateview.cpp:2293 #20 0x77be132f in KateVi::VisualViMode::updateSelection (this=0x4cd2530) at /home/lepagee/archive/ktexteditor/src/vimode/modes/visualvimode.cpp:251 #21 0x77c2be05 in KateVi::VisualViMode::qt_static_metacall (_o=0x4cd2530, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7f802490) at /home/lepagee/archive/ktexteditor/build/src/KF5TextEditor_autogen/7WFH7WAJAT/moc_visualvimode.cpp:72 #22 0x76098953 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #23 0x77c3cd9e in KTextEditor::View::selectionChanged (this=0x4f6c1d0, _t1=0x4f6c1d0) at /home/lepagee/archive/ktexteditor/build/src/KF5TextEditor_autogen/OGSBNZGFXN/moc_view.cpp:439 #24 0x77b32f2d in KateMultiSelection::notifySelectionChanged (this=0x4f739c8) at /home/lepagee/archive/ktexteditor/src/view/katemulticursor.cpp:1116 #25 0x77b3225d in KateMultiSelection::setSelectionBlock (this=0x4f739c8, encompassedBlock=[(40, 48) -> (40, 49)], cursorEdge=KateMultiCursor::Right) at /home/lepagee/archive/ktexteditor/src/view/katemulticursor.cpp:993 #26 0x77aeb9e0 in KTextEditor::ViewPrivate::toAlignedBlock (this=0x4f6c1d0, fill=false) at /home/lepagee/archive/ktexteditor/src/view/kateview.cpp:2326 #27 0x77aeb592 in KTextEditor::ViewPrivate::setBlockSelection (this=0x4f6c1d0) at /home/lepagee/archive/ktexteditor/src/view/kateview.cpp:2293 #28 0x77be132f in KateVi::VisualViMode::updateSelection (this=0x4cd2530) at /home/lepagee/archive/ktexteditor/src/vimode/modes/visualvimode.cpp:251 #29
[frameworks-kauth] [Bug 397517] New: When kauth is installed in a system prefix and in a user one, make install breaks
https://bugs.kde.org/show_bug.cgi?id=397517 Bug ID: 397517 Summary: When kauth is installed in a system prefix and in a user one, make install breaks Product: frameworks-kauth Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: elv1...@gmail.com Target Milestone: --- If kauth is installed in /usr and a framework is installed in a prefix, this happens: -- Installing: /usr/share/polkit-1/actions/org.kde.ktexteditor.katetextbuffer.policy CMake Error at src/cmake_install.cmake:121 (file): file INSTALL cannot copy file "/home/lepagee/archive/ktexteditor/build/src/org.kde.ktexteditor.katetextbuffer.policy" to "/usr/share/polkit-1/actions/org.kde.ktexteditor.katetextbuffer.policy". Call Stack (most recent call first): cmake_install.cmake:72 (include) If kauth is also in the prefix, then the policy is installed somewhere polkit can't find. So in both case, it's broken. `make install` should always allow root-less install when a prefix is used. Also installing polkit files where they wont be used is also pointless. So I guess the "solution" is to not install those files and print a warning when either kauth or any framework using it is in a prefix. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 397237] kwindowsystem is broken when compiled in static mode
https://bugs.kde.org/show_bug.cgi?id=397237 --- Comment #1 from Emmanuel Lepage Vallée --- As a side note, a more flexible alternative is to ship the plugins as QtPlugins as qmake do it for xcb (from the moc): Q_IMPORT_PLUGIN(QXcbIntegrationPlugin) Q_IMPORT_PLUGIN(QtQuick2Plugin) Q_IMPORT_PLUGIN(QtQuickControls1Plugin) Q_IMPORT_PLUGIN(QtQuickControls2Plugin) Q_IMPORT_PLUGIN(QtQuick2WindowPlugin) Q_IMPORT_PLUGIN(QEvdevKeyboardPlugin) Q_IMPORT_PLUGIN(QEvdevMousePlugin) Q_IMPORT_PLUGIN(QtQuickLayoutsPlugin) Q_IMPORT_PLUGIN(QtQuickTemplates2Plugin) Q_IMPORT_PLUGIN(QJpegPlugin) Q_IMPORT_PLUGIN(QSvgPlugin) Q_IMPORT_PLUGIN(QSvgIconPlugin) Q_IMPORT_PLUGIN(QXcbGlxIntegrationPlugin) Q_IMPORT_PLUGIN(QtGraphicalEffectsPlugin) Q_IMPORT_PLUGIN(QtGraphicalEffectsPrivatePlugin) Q_IMPORT_PLUGIN(QtQmlModelsPlugin) Q_IMPORT_PLUGIN(KirigamiPlugin) Q_IMPORT_PLUGIN(QQc2DesktopStylePlugin) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 397237] New: kwindowsystem is broken when compiled in static mode
https://bugs.kde.org/show_bug.cgi?id=397237 Bug ID: 397237 Summary: kwindowsystem is broken when compiled in static mode Product: frameworks-kwindowsystem Version: 5.48.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: elv1...@gmail.com Target Milestone: --- When compiled as a static plugin, as required by compiling kirigami as a qt plugin (until I submit patch to disable this dependency). It install a few plugins like: lib64/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugin.so as shared objects. Those objects cannot be used in static mode and thus kirigami doesn't work past commit: commit ad404dd929626f3556b4bf776d2df71f0d11d9fe Author: Marco Martin Date: Tue Apr 17 13:52:47 2018 +0200 watch the tabletMode from KWin Summary: Add api in the C++ library that watches the tablet mode property exposed from KWin. use dbus, but only on linux,bsd etc, not on Android, Windows etc. connect it to Settings.isMobile which was already used for it (even tough it introduces a naming inconsistence, but needed for retrocompatibility) Test Plan: tested to switch on the fly on Wayland with the kwin tablet mode sensor working Reviewers: #plasma, #kirigami, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: ngraham, plasma-devel Tags: #plasma, #kirigami Differential Revision: https://phabricator.kde.org/D10112 commit f5cd75acadf4254144c975437d3022f460669a64 mitigate the issue but is not directly usable on embedded Linux or static AppImages. When built with BUILD_SHARED_LIBS OFF, kwindowsystem need to select X11 or WayLand at compile time and not use plugins. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396414] There is an usability issue in mobile swipe item
https://bugs.kde.org/show_bug.cgi?id=396414 --- Comment #3 from Emmanuel Lepage Vallée --- > hmm, what it is? could you elaborate what this should do? This can wait for next week with VDG people? Right now that was one of the issue raised when I a/b tested Ring-KDE at my local hackerspace. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396412] Improve the new sidebar concept for desktop mode
https://bugs.kde.org/show_bug.cgi?id=396412 --- Comment #3 from Emmanuel Lepage Vallée --- I will take a look, I am back from vacation today. For the next week I will work on integrating the changes. Thanks for fixing these issues. If you can also take a look at the header one, hopefully I will be able to release 3.0.1 during Akademy with less custom code. See ya at Akademy (I am already in VIE) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396418] New: Add a canvas with auto-hiding area like Android
https://bugs.kde.org/show_bug.cgi?id=396418 Bug ID: 396418 Summary: Add a canvas with auto-hiding area like Android Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided In other mobile OS, you have a Canvas element with top, bottom, left and right components that can be hidden when you press on the canvas or after a delay. On desktopm they become visible when you move the mouse. Such component would be useful for camera or video chat apps like Ring-KDE. It is currently hardcoded, but could be upstreamed as a generic kirigami component -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396417] New: It is hard to recover size in the global drawer
https://bugs.kde.org/show_bug.cgi?id=396417 Bug ID: 396417 Summary: It is hard to recover size in the global drawer Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided In the global drawer, there is the name of the application in the drawer header. This is all and well, but when more space is required in the drawer, it is nicer to get rid of it dynamically instead of having a scrollable drawer. As of recently, getting to disable the header icon and app name is possible, but the space wasn't fully recovered. Also getting a QtQuick.Layout2 based element to take the full height can be made to work, but it definitely doesn't "just works" when you use `Layout.fillHeight: true`. In both case, you can dark magic around the issues using Voodoo, but the code is ugly and it should not be necessary. tl;dr: going from having the header to not having the header while using the full drawer height should work and it currently doesn't. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396416] New: The mobile swipe item handles have issues with different sized entries
https://bugs.kde.org/show_bug.cgi?id=396416 Bug ID: 396416 Summary: The mobile swipe item handles have issues with different sized entries Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided (disclaimer: This is a summary of a meeting discussion) When using a list of swipe item with inconsistent height, the handles become all over the place instead of vertically aligned. This is because taller elements have a different kind of handle than the smaller one. While equally sized elements are always preferred, it isn't always practical. For example, if a Ring-KDE account goes down, it need to be very explicit and an (/!\) emblem is added to the list and it increases the height a bit. The point being it doesn't render correctly and it should. If I should find a better way to display the account list with consistent size is parallel to this bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396414] New: There is an usability issue in mobile swipe item
https://bugs.kde.org/show_bug.cgi?id=396414 Bug ID: 396414 Summary: There is an usability issue in mobile swipe item Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided (disclaimer: This is a summary of a meeting discussion) When using swipe item, you get a list of action represented as icons. On the desktop, you can have a tooltip and the user kind of expect them. On the mobile, you may or may not be able to hold the icon pressed, but this is hard to discover. The users seem scare to click on actions where they are not sure what the icon does. Given the worst case scenario in Ring-KDE is doing a phone call by accident, the user just ignore the actions because they are scared. Some ways to showing the action text (label) either by displaying the actions vertically, a popup or anything else would be needed to fix this perceived problem. More discussions are needed with the VDG about this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 396413] New: Add a way to disable SwipeItem actions when editing
https://bugs.kde.org/show_bug.cgi?id=396413 Bug ID: 396413 Summary: Add a way to disable SwipeItem actions when editing Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: elv1...@gmail.com Target Milestone: Not decided (disclaimer: This is a summary of a meeting discussion) When adding an "edit" mode to an item, there is an annoying regression since Kirigami switched from a swipe action to a mouse hover action on the desktop. If you change the swipe item component to add some TextEntry or buttons, they keep moving around when you move the mouse. Some way to tell the swipe delegate to stop doing magic while the item is locked in edit mode is required to fix this UX regression. -- You are receiving this mail because: You are watching all bug changes.
