Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

owner of /tmp/printer #2137

Closed
4noxx opened this issue Nov 2, 2019 · 2 comments
Closed

owner of /tmp/printer #2137

4noxx opened this issue Nov 2, 2019 · 2 comments

Comments

@4noxx
Copy link

4noxx commented Nov 2, 2019

hello,

i have problem to set /tmp/printer as source.
it seems there is a problem with the rights.
actually it is pi:pi
if i change this to root:root, it works. repetier can
connect. but, after reboot i ve the same problem.
/tmp/printer pi:pi again.

@klipper-gitissuebot
Copy link

Hi @4noxx,

It did not look like there was a Klipper log file attached to this ticket. The log file has been engineered to answer common questions the Klipper developers have about the software and its environment (software version, hardware type, configuration, event timing, and hundreds of other questions).

Unfortunately, too many people have opened tickets without providing the log. That consumes developer time; time that would be better spent enhancing the software. If this ticket references an event that has occurred while running the software then the Klipper log must be attached to this ticket. Otherwise, this ticket will be automatically closed in a few days.

For information on obtaining the Klipper log file see: https://github.com/KevinOConnor/klipper/blob/master/docs/Contact.md

The log can still be attached to this ticket - just add a comment and attach the log to that comment.

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

@klipper-gitissuebot
Copy link

It appears the Klipper log file was not provided.
I'm closing this now, sorry. Feel free to attach the log to this ticket sometime in the future, or create a new issue once you can provide the log file.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants