Skip to content
This repository has been archived by the owner on Jun 10, 2021. It is now read-only.

No session for pid xxxx #3

Open
Ibrahim3773 opened this issue Mar 9, 2019 · 15 comments
Open

No session for pid xxxx #3

Ibrahim3773 opened this issue Mar 9, 2019 · 15 comments

Comments

@Ibrahim3773
Copy link

"no session for pid" displays again and again after running the raspberry_pi_initial_setup.sh

@AnesBenmerzoug
Copy link
Owner

Could you give me more information?
For example which OS you're using.

After some googling I found these few links:

It could be that the update & upgrade step in raspberry_pi_initial_setup.sh could have update something that is causing that error to appear.

@Ibrahim3773
Copy link
Author

First of all, thank you so much for the quick response.

OS: 2018-05-27 Rasbian Stretch
Raspberry Pi 3B

The error is occurring when I run the command "sudo sevice dbus restart"
I have also tried to run this command before running the raspberry_pi_initial_setup.sh but i failed

@AnesBenmerzoug
Copy link
Owner

No worries, I noticed it on time so I had to reply.

Do you by any chance connect to your raspberry pi using vnc?
Does this error appear only after restarting dbus? Does it persist or does it go away?
Does it appear again if you restart the pi?

@Ibrahim3773
Copy link
Author

No, we are not connecting it using vnc.
Yes, This error appears whenever a restart the debus.
The error persists and periodically appears after every 1-2 minutes.
No, when we reboot the pi, the error doesn't appear.

@AnesBenmerzoug
Copy link
Owner

Hmm, that's interesting.

Another question, what happens if right after restarting the raspberry pi you try to restart the dbus service without running the raspberry_pi_initial_setup.sh script?

In that script a configuration file is copied from the repository into the /etc/dbus-1/system.d directory.
Could you try deleting it and restarting the dbus service again?

@Ibrahim3773
Copy link
Author

Same issue persists when I try to restart the dbus service after rebooting the raspberry pi.

I tried to restart the dbus service after deleting the "org.upwork.hidbluetooth.conf" file from "/etc/dbus-1/system.d" but the same error occurred again.

@AnesBenmerzoug
Copy link
Owner

Then I really don't know what could be causing this issue.

All I can suggest for now is to try to install a newer version of Raspian OS as
it seems that there a version that was released in November 2018 (https://www.raspberrypi.org/downloads/raspbian/)

I hope that you can solve this issue.

@Ibrahim3773
Copy link
Author

I have tried it on the new version but still the error persists. Thank you so much for your time. Can you please tell me the version of Raspbian you used to run this code successfully?

@AnesBenmerzoug
Copy link
Owner

This project has currently some issues and I am trying to improve it.
I was busy these past few months so I didn't touch it in a while.
Last time I ran it I used the latest version, which is the one I linked above.

@speicherspule
Copy link

Hey, i was sucessful in run scripts in command line mode(non graphical mode). but after that the program didnt work..

@AnesBenmerzoug
Copy link
Owner

@speicherspule Could you tell me exactly what you did and what happened? I might be able to help you if I have more information

@speicherspule
Copy link

IMG_20190320_191314
i'm using last RPi 3b+ with last raspbian and after running all the scripts, i connect bluetooth with my pc or phone and get this error.

@AnesBenmerzoug
Copy link
Owner

@speicherspule sorry for the late reply. I was busy the last few days.
This error is one I got quite a lot, but unfortunately I don't remember how I solved it.
It happened because you pressed a button from the interface without the connection being established so it timed out.
This project in it's current state is not quite functional and I would love to one day improve it.

@wrlu
Copy link

wrlu commented Oct 16, 2019

Hi, I have the same problem on my raspberry pi 4b. It seems that this is a problem on newly devices.

@ghost
Copy link

ghost commented Nov 11, 2020

Hi there, just wanted to chime in with my own problem to this.
I have a brand new raspberry pi 4 that I've set up. As I was planning on locking up the pi in a closet, I wanted VNC to work, but would not auto start so would need to SSH into it to send "vncserver :1" to then be able to VNC in.
To fix this I went into "crontab -e" and added "@reboot vncserver :1 -geometry 1600x900"

After setting this up, on launch I would get the error "No session for pid xxxx".
Issue was solved when I typed: mv /usr/bin/lxpolkit /usr/bin/lxpolkit.bak

EDIT: Solution was from here: meefik/linuxdeploy#978 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants