Since my question wasn’t answered. I figured I’d repost it here.
Hello everyone! I’m having trouble with Mudita Center. I’m on Linux, to be more specific, Bazzite which is fork of Fedora I believe. I can’t connect my phone to Mudita Center. It asks me to allow for USB access, then asks for a password. Tried the PIN number on the phone, tried my admin password for the computer and nothing works. So I’m kind of at my wits end here. Is there anyone here that uses Linux that could help me? I’m getting very frustrated.
2 Likes
I don’t know about Fedora but, on Debian, your user needs to be part of the “dialout” group (which enable direct access to USB communication).
My first guess is that there’s a similar group on Fedora.
1 Like
i use linux mint (ubuntu) with no problem
4 Likes
@jasonmm1979 Is this the same problem:
I had this issue, and this is what fixed it:
-Go to the location of the Mudita-Center.appimage in your file browser (/downloads in my case)
-Right clicked an empty spot/area in the folder and selected “Open Terminal Here”
-Run this chmod line I got from @jordan :
chmod +x Mudita-Center.appimage
2 Likes
What worked for me was to enable “USB debugging mode” in the Developer options on the Kompakt, and then connect it to my computer. (search around on the forum about how to do this if you’re not sure what I’m talking about)
1 Like
I use Elementary OS.
Took me long time to find the way to get connected to the Center.
-unlock the phone
- connect via USB
- Execute MCenter
- Choose the device
- Wait, it’s slow
Work for me.
1 Like
Hey, just did this yesterday on Bazzite. Here’s what I had to do:
Open up the Terminal and run:
grep -E '^dialout:' /usr/lib/group | sudo tee -a /etc/group
That will make the dialout group available for adding to your user:
sudo usermod -a -G dialout <YOUR USERNAME>
(I had already tried the chmod command from above, but it still wouldn’t work until I ran these two other commands)
Good luck!
3 Likes
Hi,
I tried on fedora 43 workstation.
This command returns the error.
grep: /usr/lib/group: No such file or directory
grep -E '^dialout:' /usr/lib/group | sudo tee -a /etc/group
1 Like
The new version of the Center didn’t work on my old Elementary OS.
But couldn’t update the OS cause my Mackbook was too old (2007).
Tryed other distri on it but nothing worked correctly.
So I have now a 2017 MacBook with Pop OS on it that work really great.
Haven’t tried the Center yet cause the new version is buggy, even on PC or Mac. So I’m waiting for a correction.
1 Like
@ramamohan , some distributions don’t have a /usr/lib/group. OpenSuse also doesn’t. Here’s how I fixed it.
Sorry, I’m getting blocked from providing any useful information by the forum software. Probably this is either discourse or a CDN WAF rule or something. I get 403 errors every time I try to post or edit the name of the directory after sudo tee -a in your failed command. I’ll add what I can but @urszula or the forum devs may need to fix this by elevating my permissions level or adjusting something in the WAF or security settings.
1 Like
- I checked whether dialout was already present in the directory I mentioned in my last post.
> grep dialout <that directory I can't post the name of>
dialout:x:<numbers>:<not_my_username>
- I granted my username membership in that group
> sudo usermod -a -G dialout <username> - I attempted to use Mudita Center again with the same error.
- I confirmed my username was associated with the dialout group. I noticed in the process that different commands produced different results.
# the return from these indicates my username has dialout membership
> grep dialout <that directory I can't post the name of>
dialout:x:<numbers>:<not_my_username>,<username>
> getent group dialout
<username>
> id <username>
<username>
# these return only the group specific to my <username>, indicating the current user doesn't have `dialout` membership
> groups
<username>
id -nG
<username>
- I rebooted. when the new session started, all four commands indicated I had dialout group membership, and Mudita Center worked as expected.
1 Like
I have reached out to the team about this.
1 Like
@weekday_warrior This was our team’s response:
Installing the Mudita Center AppImage on Linux often requires setting the correct file permissions or bypassing the Electron sandbox.
The issue described likely relates to manually configuring udev rules or user groups for USB access, which can vary by distribution and sometimes triggers web application firewall blocks on support forums when posting file paths like /etc/udev/rules.d/.
1. Make the AppImage Executable
- Right-click the downloaded
Mudita-Center.AppImagefile and select Properties. - Go to the Permissions tab and check the box that says “Allow executing file as program”.
- Verification: Double-click the file; if it launches, your installation is complete.
2. Bypass the Sandbox (If the app won’t open) If nothing happens when you click the executable, you are likely encountering a known Linux sandbox permission issue.
- Open your terminal and navigate to the folder containing your downloaded AppImage.
- Run the application by executing the following command:
./Mudita-Center.AppImage --no-sandbox. - Verification: The Mudita Center graphical interface should immediately open on your screen.
3. Alternative: Use an AppImage Manager
thanks! When I post or edit a post which includes / etc / group as a single string, the forum (or CDN or WAF or whatever) pops up a 403.
in case it helps with root causing the issue, after I type that in, the software does two weird things:
- this red text shows up at bottom right
- the page pops up the following error:
Draft is being edited in another window. Please reload this page.
1 Like
Are we talking about Mudita Center now? Or are you referring to something that’s happening on the FORUM? Cuz I’m a little confused 
Adding the active user to the dialout group wasn’t directly included in the dev’s walkthrough, though they mentioned it obliquely. Seems to be unblocking most people, once they’ve gotten past making the appimage executable.
1 Like
This post describes how the forum bug shows up for me. This bug was blocking me from explaining how to work around the MC issue.
Sorry I wasn’t clearer about that!
1 Like