Created attachment 182791 [details] BlockingAndMutingNotWorking SUMMARY In Mastadon we are able to block or mute users. However while using Tokodon we cannot block or mute users. There is no indication whether the blocking has succeeded or failed. What is the error code or error message if it has failed STEPS TO REPRODUCE 1. Launch Tokodon and navigate to either Home or Explore or Local or Global left navigation items. 2. Click on any post and then click on the three dots and select either Block or Mute the user. Please see the attached screenshot, "BlockingAndMutingNotWorking" with the items circled in yellow. 3. No notification is shown whether the user is blocked or not. OBSERVED RESULT On the Tokodon app there is no notification show with either success or failure. On the mastadon server which has the account, the user which has been blocked is not shown as blocked. Ditto for Muted users. EXPECTED RESULT The user should get blocked or muted. The same should be reflected on the Mastadon server where the account is present. If the action of blocking or muting is not successful then a popup with the appropriate message should be shown. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Linux LTS 6.12.32 KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.1 ADDITIONAL INFORMATION Tokodon should write something to the log or console within the application. Tokodon has neither.
Dont know if this will help or not in fixing this bug. The following is the error message that I receive in the terminal when I start Tokodon from the shell. qrc:/qt/qml/org/kde/kirigamiaddons/components/ConvergentContextMenu.qml:232:9: QML ActionsMenu: cannot show menu: parent is null qrc:/qt/qml/org/kde/kirigamiaddons/components/ConvergentContextMenu.qml:234:31: QML ActionsMenu: cannot show menu: parent is null qrc:/qt/qml/org/kde/kirigamiaddons/components/ConvergentContextMenu.qml:232:9: QML ActionsMenu: cannot show menu: parent is null qrc:/qt/qml/org/kde/kirigamiaddons/components/ConvergentContextMenu.qml:234:31: QML ActionsMenu: cannot show menu: parent is null qrc:/qt/qml/org/kde/tokodon/content/ui/PostDelegate/PostMenu.qml:186: TypeError: Property 'block' of object Account(0x59f7d06953c0) is not a function
> In Mastadon we are able to block or mute users. However while using Tokodon we cannot block or mute users. There is no indication whether the blocking has succeeded or failed. What is the error code or error message if it has failed I already fixed blocking in 25.04.3, however I didn't try muting. I'll double-check to make sure that's fixed too.
Also will it be possible for us to view and modify blocked users and muted users? Currently we have to Settings > Safety > Muted Users and Settings > Safety > Blocked Users to view the list. But we cannot modify this list. It would be good to have this in the main window Left Navigation below Bookmarks, Favorites, Lists.
Muting works for me, and blocking should work soon that 24.05.3 is tagging. I won't close this until I add unmute/unblock buttons on the management page though!
Git commit 4f09a6e861c0ce1d2f629654047b026bc0167a9e by Joshua Goins. Committed on 30/06/2025 at 20:20. Pushed by redstrate into branch 'master'. Add mute/block management on the safety page This allows you to manage your muted/blocked users without having to navigate to their profile first. M +40 -0 src/account/socialgraphmodel.cpp M +6 -0 src/account/socialgraphmodel.h M +12 -0 src/content/ui/SocialGraphPage.qml https://invent.kde.org/network/tokodon/-/commit/4f09a6e861c0ce1d2f629654047b026bc0167a9e
(In reply to Joshua Goins from comment #4) > Muting works for me, and blocking should work soon that 24.05.3 is tagging. > I won't close this until I add unmute/unblock buttons on the management page > though! Thanks. KDE rocks. Tokodon as a client for Mastadon rocks too.
I just updated to Tokodon 25.04.3. Muting works fine. However on blocking the user, the app crashes and the user is not blocked. I will try to replicate the issue to confirm the same. STEPS TO REPRODUCE 1. Launch Tokodon and navigate to Global left navigation items. 2. Click on post whose link is given below and then click on the three dots and select Mute the user. https://mastodon.social/@Chipper319/114809986119445410 DISCLAIMER: THE LINK IS NSFW AND FEATURES GAY PORNOGRAPHY. OPEN WITH CARE 3. The application crashed. I will try to run Tokodon from the terminal and see what I see over there. Is there a way that I can capture debug logs? Should I open a new bug for this? IMPORTANT: THE LINK GIVEN IN STEP 2 IS NOT SAFE FOR WORK AND DISPLAYS EXPLICIT MALE NUDITY. OPEN WITH CAUTION.
Created attachment 183025 [details] Tokodon_STDERR_STDOUT_Log The standard error and standard output log when Tokodon is run from the shell terminal. It has been posted so that debugging can be easier.
So I was able to replicate the issue and capture the standard error and standard output log. It is attached as Tokodon_STDERR_STDOUT_Log. Details are given below STEPS TO REPRODUCE 1. Launch Tokodon from the terminal by giving the command tokodon >& ~/tokodon.log 2. Navigate to Global left navigation items. 3. Click on a post and then click on the three dots and select Mute the user. 4. The application crashes with the error message in the terminal Segmentation fault (core dumped) OBSERVED RESULT Tokodon crashes with the error message Segmentation fault (core dumped). The user does not get blocked. EXPECTED RESULT The application should not throw a segmentation fault error. The user should get blocked. ADDITIONAL INFO I have set some Linux kernel hardening parameter, like init_on_alloc=1 init_on_free=1 and a few others. Could they be the cause of this crash? Also since I reported this bug the Linux kernel has been updated to version 6.12.35.
Created attachment 183026 [details] Tokodon_SystemD_JournalD_Log_EntriesForCrash As per my updates on Comment #9 (https://bugs.kde.org/show_bug.cgi?id=506374#c9), I repeated the STEPS TO REPRODUCE, but before this I ran the command journalctl --follow The output from JournalCTL is attached in this file. The behavior exactly as described in comment #9.