Mobileraker permission issue causes notification warning #436

Closed
opened 2024-02-06 09:27:42 +01:00 by shodanx2 · 7 comments
shodanx2 commented 2024-02-06 09:27:42 +01:00 (Migrated from github.com)

Linux Distribution

debian 12

What happened

Getting this error message in MainSail and on KlipperScreen

image

I have 6 instances installed

image

Installed with basically default settings these

Klipper
Moonraker
Mainsail
Fluidd
KlipperScreen
Crowsnest
OctoEverywhere
Mobileraker
Octoprint

What did you expect to happen

Not have the warning message

How to reproduce

Regular installation of moonraker

Additional information

Fix is simply to add the word

mobileraker

to each instance's file

/home/user/printer_1_data/moonraker.asvc

After a reboot, the message is gone

### Linux Distribution debian 12 ### What happened Getting this error message in MainSail and on KlipperScreen ![image](https://github.com/dw-0/kiauh/assets/10621885/8f91bf67-e661-45c1-a833-7f779dbd4d7c) I have 6 instances installed ![image](https://github.com/dw-0/kiauh/assets/10621885/71ddeea4-a678-4853-9c82-215dc594d9c2) Installed with basically default settings these Klipper Moonraker Mainsail Fluidd KlipperScreen Crowsnest OctoEverywhere Mobileraker Octoprint ### What did you expect to happen Not have the warning message ### How to reproduce Regular installation of moonraker ### Additional information Fix is simply to add the word mobileraker to each instance's file /home/user/printer_1_data/moonraker.asvc After a reboot, the message is gone
Tomblarom commented 2024-03-03 22:01:56 +01:00 (Migrated from github.com)

My moonraker.asvc looked like this. I highly suspect a new-line is missing somewhere :D
image

My `moonraker.asvc` looked like this. I highly suspect a new-line is missing somewhere :D ![image](https://github.com/dw-0/kiauh/assets/12703270/d7ac51dc-f908-40cb-ba5b-cdf3e308a543)
dw-0 commented 2024-03-23 19:51:09 +01:00 (Migrated from github.com)

I think that is something that should be handled by Mobileraker?
@Clon1998 are you aware of this or did you already resolved that issue?

I think that is something that should be handled by Mobileraker? @Clon1998 are you aware of this or did you already resolved that issue?
Clon1998 commented 2024-03-23 20:09:29 +01:00 (Migrated from github.com)

Hey,
yes that is on me. I was finally able to reproduce that issue and fix it.

Related to https://github.com/Clon1998/mobileraker_companion/issues/84.

TL;DR;
Re-run the installer.

Hey, yes that is on me. I was finally able to reproduce that issue and fix it. Related to https://github.com/Clon1998/mobileraker_companion/issues/84. TL;DR; Re-run the installer.
dw-0 commented 2024-03-23 20:44:28 +01:00 (Migrated from github.com)

Great! Thank you for the fast response!

Great! Thank you for the fast response!
shodanx2 commented 2024-03-23 21:46:32 +01:00 (Migrated from github.com)

Who decided to use invisible coding characters in a settings file !? 🤦

Who decided to use invisible coding characters in a settings file !? 🤦
dw-0 commented 2024-03-23 21:54:31 +01:00 (Migrated from github.com)

Who decided to use invisible coding characters in a settings file !? 🤦

Not sure what or who you are blaming exactly now, but using newline characters is quite common in text manipulation scenarios.

> Who decided to use invisible coding characters in a settings file !? 🤦 Not sure what or who you are blaming exactly now, but using newline characters is quite common in text manipulation scenarios.
shodanx2 commented 2024-03-23 22:15:36 +01:00 (Migrated from github.com)

It's a tongue in cheek dig at yaml, don't worry.

However EOF should be considered equivalent to EOL.

It's a tongue in cheek dig at yaml, don't worry. However EOF should be considered equivalent to EOL.
Sign in to join this conversation.