STICKY: Jessie (now defunct and replaced with Stretch) Q&A

[gcorwin]

I just downloaded and imaged an SD card for Jessie and inserted it into a new RPI 3. It seems to boot, and I am pretty sure it's getting an IP, but there isn't an HDMI signal. Any suggestions?

[DirkS]

I just downloaded and imaged an SD card for Jessie and inserted it into a new RPI 3. It seems to boot, and I am pretty sure it's getting an IP, but there isn't an HDMI signal. Any suggestions?

This a Q&A thread. Post a new topic in troubleshooting

[owaizshareef]

I am building a raspbery pi cluster.
new os (raspbian jeaasy),
i have to create drives and make it available so that slave nodes can access the drive.

Previously in raspbian whezzy -
Command "sudo service rpcbind start" , "sudo update-rc.d rpcbind enable"
was used.
but it dosent work any more,
any one having experience in this pls help

[rpdom]

I am building a raspbery pi cluster.
new os (raspbian jeaasy),
i have to create drives and make it available so that slave nodes can access the drive.

Previously in raspbian whezzy -
Command "sudo service rpcbind start" , "sudo update-rc.d rpcbind enable"
was used.
but it dosent work any more,
any one having experience in this pls help

Again, this is a Q&A about the Jessie release, not a general Troubleshooting post.

I suggest you start a new topic in the troubleshooting forum and give some more information about your problem.
For example, you say "it doesn't work". How? What errors/messages do you get?

Include that information (and anything else that you might think is relevant) in your new post and people will try to help you.

[rchoppin]

Just downloaded the latest jessie desktop distribution and
booted it up on my mod 2 B. The desktop came up but would not
respond to keyboard or mouse. This seems to be because my
firmware had not been updated. The solution was to ssh in and
use rpi-update to update the firmware. This is not acceptable for
naive users. The boot process should a) check for obsolete firmware,
b) prompt for update and c) update the firmware. rpi-update is, I
think already included with the distribution. This is the sort of creeping
accumulation of minor irritations that turn away the naive users that
the system is supposed to be supporting.

[ShiftPlusOne]

Just downloaded the latest jessie desktop distribution and
booted it up on my mod 2 B. The desktop came up but would not
respond to keyboard or mouse. This seems to be because my
firmware had not been updated. The solution was to ssh in and
use rpi-update to update the firmware. This is not acceptable for
naive users. The boot process should a) check for obsolete firmware,
b) prompt for update and c) update the firmware. rpi-update is, I
think already included with the distribution. This is the sort of creeping
accumulation of minor irritations that turn away the naive users that
the system is supposed to be supporting.

I've seen a few other people report the issue. It's not because the firmware 'has not been updated'. The image includes the appropriate firmware and rpi-update is a debugging/testing tool only.
viewtopic.php?f=66&t=150117
It's also not a NOOBS issue, but the thread is relevant otherwise.

I am not able to reproduce the issue, but if somebody does see it, the output of 'sudo journalctl' and 'dmesg' would be helpful.

[jaydenzou]

got pi3 with jessie

suppose that jessie will support webgl on chromium , but i try for a hard day and fail

would u mind share some resource about that

appreciated


what i have done ,bellow:
1. raspbian-config to enable gl-drive
2. install chromium 50 and "config:flags " to ignore the blacklist
3. run the testing website which require webgl, http://api.maiyajia.com/diaoke

[kusti8]

got pi3 with jessie

suppose that jessie will support webgl on chromium , but i try for a hard day and fail

would u mind share some resource about that

appreciated


what i have done ,bellow:
1. raspbian-config to enable gl-drive
2. install chromium 50 and "config:flags " to ignore the blacklist
3. run the testing website which require webgl, http://api.maiyajia.com/diaoke

Remove the flag from /etc/chromium-browser/default

[embeddeding]

Hello.
i use raspbian whezzy from many times.but now i want to use raspbian jessie.at first boot i can't Expand Filesystem .

[texy]

Hi,
if you are using the latest raspbian image :
https://www.raspberrypi.org/blog/anothe ... -raspbian/
the file system is automatically expanded on the first boot.

Texy

[gl82uk]

hey guys

is the chromium still supported in jessie ?

as I'm having issues installig it on the raspbian jessie

[DirkS]

hey guys

is the chromium still supported in jessie ?

as I'm having issues installig it on the raspbian jessie

viewtopic.php?t=121195

[mjjj]

Hi I have install Rasbian Jessie, and it work OK.
I need to know how to load an application automatically when you start Raspbian?

Thanks

[benramadan]

Hi all

I am getting stuck in a login greeter loop in lightdm in Jessie 4.4. I have tried everything I could find by way of public solutions, to no avail.

My exact steps:

• Downloaded and flashed Jessie 4.4 image from https://www.raspberrypi.org/downloads/raspbian
• Boot, log into shell as user pi

• Code: Select all

  $ sudo apt-get update

• Code: Select all

  $ sudo apt-get install lightdm

• Code: Select all

  $ sudo raspi-config

• Choose 3. Boot Options
• Choose 'Desktop GUI, automatically logged in as 'pi' user'
• Save and reboot

The resulting boot into lightdm shows the greeter, and the correct pi user credentials loop me back to the greeter. Incorrect credentials result in an authentication error as expected.

root has not stolen ownership of any of the . files in my home directory:

Code: Select all

$ ls -al ~
total 40
drwxr-xr-x 2 pi   pi   4096 Jul 11 23:42 .
drwxr-xr-x 3 root root 4096 May 27 11:09 ..
-rw------- 1 pi   pi    516 Jul 11 23:44 .bash_history
-rw-r--r-- 1 pi   pi    220 May 27 11:09 .bash_logout
-rw-r--r-- 1 pi   pi   3512 May 27 11:09 .bashrc
-rw-r--r-- 1 pi   pi     55 Jul 11 21:36 .dmrc
-rw-r--r-- 1 pi   pi    675 May 27 11:09 .profile
-rw------- 1 pi   pi    112 Jul 11 23:42 .Xauthority
-rw------- 1 pi   pi    253 Jul 11 23:42 .xsession-errors
-rw------- 1 pi   pi    253 Jul 11 23:41 .xsession-errors.old

/tmp is 777:

Code: Select all

$ ls -al /tmp
total 28
drwxrwxrwt  7 root root 4096 Jul 11 23:44 .
drwxr-xr-x 21 root root 4096 Jul 11 21:35 ..
drwxrwxrwt  2 root root 4096 Jul 11 23:44 .font-unix
drwxrwxrwt  2 root root 4096 Jul 11 23:44 .ICE-unix
drwxrwxrwt  2 root root 4096 Jul 11 23:44 .Test-unix
drwxrwxrwt  2 root root 4096 Jul 12 19:48 .X11-unix
drwxrwxrwt  2 root root 4096 Jul 11 23:44 .XIM-unix

lightdm.conf has these changes:

Code: Select all

$ grep "^[^#]" /etc/lightdm/lightdm.conf
[LightDM]
autologin-user=pi
[SeatDefaults]
autologin-user=pi
[XDMCPServer]
[VNCServer]

The same behaviour if I start lightdm from command line

Code: Select all

$ sudo service lightdm start

The following appears in ~/.xsession-errors

Code: Select all

$ cat ~/.xsession-errors
Xsession: X session started for pi at Tue 12 Jul 20:12:32 UTC 2016
Xsession: unable to start X session --- no "/home/pi/.xsession" file, no 
"/home/pi/.Xsession" file, no session managers, no window managers, and no 
terminal emulators found; aborting.

So I did:

Code: Select all

$ touch ~/.xsession ~/.Xsession

Then the next time lightdm started, it created a set of user directories:

Code: Select all

$ ls -al ~
total 80
drwxr-xr-x 11 pi   pi   4096 Jul 12 20:18 .
drwxr-xr-x  3 root root 4096 May 27 11:09 ..
-rw-------  1 pi   pi   2506 Jul 12 20:15 .bash_history
-rw-r--r--  1 pi   pi    220 May 27 11:09 .bash_logout
-rw-r--r--  1 pi   pi   3512 May 27 11:09 .bashrc
drwx------  2 pi   pi   4096 Jul 12 20:16 .config
drwxr-xr-x  2 pi   pi   4096 Jul 12 20:16 Desktop
-rw-r--r--  1 pi   pi     55 Jul 11 21:36 .dmrc
drwxr-xr-x  2 pi   pi   4096 Jul 12 20:16 Documents
drwxr-xr-x  2 pi   pi   4096 Jul 12 20:16 Downloads
-rw-------  1 pi   pi     39 Jul 12 19:49 .lesshst
drwxr-xr-x  2 pi   pi   4096 Jul 12 20:16 Music
drwxr-xr-x  2 pi   pi   4096 Jul 12 20:16 Pictures
-rw-r--r--  1 pi   pi    675 May 27 11:09 .profile
drwxr-xr-x  2 pi   pi   4096 Jul 12 20:16 Public
drwxr-xr-x  2 pi   pi   4096 Jul 12 20:16 Templates
drwxr-xr-x  2 pi   pi   4096 Jul 12 20:16 Videos
-rw-------  1 pi   pi    112 Jul 12 20:16 .Xauthority
-rw-r--r--  1 pi   pi      0 Jul 12 20:14 .xsession
-rw-r--r--  1 pi   pi      0 Jul 12 20:14 .Xsession
-rw-------  1 pi   pi     67 Jul 12 20:16 .xsession-errors
-rw-------  1 pi   pi     67 Jul 12 20:16 .xsession-errors.old

Now:

Code: Select all

$ cat .xsession-errors
Xsession: X session started for pi at Tue 12 Jul 20:16:38 UTC 2016

HOWEVER - the same behaviour persists. No autologin, and looping back to the greeter when I enter the right credentials.

I am out of ideas. Can anybody reproduce this at all or have any other ideas?

Many thanks
Ben

[kamikaze]

Hello. is there any chance to see Qt 5.7 in repository?

[ShiftPlusOne]

Hello. is there any chance to see Qt 5.7 in repository?

Very unlikely. It's not even in Sid in Debian yet.

[Jex]

can jessie operate with composite tv (for raspberry pi 3)

[rpdom]

can jessie operate with composite tv (for raspberry pi 3)

Yes. The 3.5mm A/V socket has stereo audio and composite video output on it.

You will need a special (TRRS) cable to connect it to a TV. Unfortunately these come in at least three different types, only one of which is compatible with the Pi 2 and Pi 3. Look for one that says it works with a Pi (I think ones that work with a Zune are the same type).

[Jex]

Sir can a rca cable having the inner led of the composite is shorted with red the next one is gnd and the two outer are yellow and white... how would i connect it to my tv?

[Metasyntactic]

So, I updated from Wheezy to Jessie and I was really excited to see that it already had VNC baked in to the distro image. That said, I've been having a lot of issues with getting it to work properly. I've enabled VNC in RPI configuration but I find that it's not actually running on start and I'm not sure why. It'll run the first time I click enable but, if I reboot, the VNC server icon will appear on the taskbar and I don't appear to be able to connect to the pi short of starting a VNC server manually. It still shows as enabled in the config window but I can't connect. I've also tried enabling VNC via command line but it just doesn't seem to stick after reboot. If I disable VNC, reboot, then reenable, it will work fine until I reboot again.

Not sure what I'm missing here and it seems the change to Jessie was recent enough that all my google searches return instructions for setting up VNC on wheezy.

Would REALLY appreciate any advice people have.

[sconemad]

Would REALLY appreciate any advice people have.

Have you done a package update recently? This sounds a lot like an issue that was fixed just after the raspbian pixel release.

[Metasyntactic]

Would REALLY appreciate any advice people have.

Have you done a package update recently? This sounds a lot like an issue that was fixed just after the raspbian pixel release.

I installed Jessie yesterday, would the package update not be included in the recent build?

[fruitoftheloom]

Would REALLY appreciate any advice people have.

Have you done a package update recently? This sounds a lot like an issue that was fixed just after the raspbian pixel release.

I installed Jessie yesterday, would the package update not be included in the recent build?

The last release was 23/09/2016 and Raspbian Jessie has regular updates;

Code: Select all

sudo apt-get update
sudo apt-get dist-upgrade

[Metasyntactic]

The last release was 23/09/2016 and Raspbian Jessie has regular updates;

Code: Select all

sudo apt-get update
sudo apt-get dist-upgrade

That ended up being exactly what the problem was. Thank you!

[levelcrow]

At this point in development, does it appear like Raspbian Stretch is going to be much faster than Raspbian Jessie? Are there any major changes that the developers are willing to reveal?

Around what time is Raspbian going to be released? Does it look like there's going to be a significant delay from the Debian release, like with Jessie?

Is there any chance the open source VC4 is going to be turned on by default for Raspbian Stretch? Is it unrealistic to expect any better desktop performance in the future?