chewy74 wrote:So I'm not sure what else to do... Can I force the upgrade somehow?

There is no "force". If your packages list is correct the upgrade will happen.
Could you show the output that you get when you run "sudo apt-get update"? You seem to have missed that out when you posted.

Also, show the output of "apt-cache policy" (sudo not required for apt-cache).

The given instructions (and this thread in general) are for the last official wheezy image release. If your sources look like that, you should know enough of what you're doing to get the install you want.

I'll post my method in a new thread as it relates to creating a new image as opposed to upgrading ; but I had real difficulties with the Wheezy / Jessie upgrade. I would recommend backing up any files you have on your wheezy card and starting with a fresh Jessie .img ; a lot quicker and pain free. What I wanted was a ' light Jessie ' that would would fit on a 4Gb card as some of the clubs / schools I'm involved with have a few ModelB / 4Gb setups ; removing wolfram / Libreoffice was part of my plan. Anyways gave up on update path after a few crashes / failed attempts and managed to create a 4Gb Jessie with MineCraftPi / Sonic-Pi / Scratch etc , figured Wolfram and word processing wasn't going to be essential in that package

I followed the instructions (also big thanks for the hint regarding nginx/php-fpm/fastcgi !) but it seems some things are not finally okay so far (sorted from 1 = small issue to 3 = big trouble):

1) How can I check if I´m already using the new GUI (GTK+3)?
2) Could not "cp /usr/share/themes/PiX ~/.themes -ax" because there is no theme "PiX"! How can I fix this?
3) I have three cron´s running at boot time (in fact a load more, but those 3 are the only one not working). Everyone´s doing a specific thing, but the only pattern I could detect is: They all are network related.
- job 1 should mount a CIFS share,
- job 2 should start the tightvncserver and
- job 3 run´s a CURL at PushingBox.com.
They are ALL not working. Running manually when the system has started is fine. What can I check? Timeouts for network etc.?

Could someone please explain this?
I used Unix-like systems since decades and never happened to see a "cp" backwards-syntax working.
I just opened the man page of cp on my Pi to be sure: It tells the usual usage pattern:

,
with several variants of the arguments depending if they are single filenames or directories, but never does the options follow the args.
This puzzles me really hard. Can somebody please explain this?

POSIX says that options must precede other arguments, and many non-GNU systems require that. However, GNU getopt normally permits options to appear anywhere. The special argument "--" can be used to indicate that all remaining arguments are not options.

Of course it makes no difference to the behaviour whether "-ax" is specified first or last. The problem in the first post of this thread was that two of the options were spelled with a Unicode en dash "–" instead of an ASCII hyphen "-". So copy-pasting those options will fail, but re-typing them will work.

To be more specific on my question #1:
I have e.g. Synaptics Package Manager which is almost completely black when running. It worked (nice new GUI) for some time meanwhile, but after a few reboots -> back to "defect GUI"

Second new UI problem:
I don´t have the wicd and clipit plugins anymore on lxpanel. They are not listed as plugins when trying to configure lxpanel. Content of plugins folder:

@e-raser:
The black background bug is seen in all applications that use GTK+3 (kweb3, for example). Some window themes are somehow broken. I suppose you are using Clearlooks. Run lxappearance and select another theme, Adwaita or PIX do work.

Minimal Kiosk Browser (kweb)
Slim, fast webkit browser with support for audio+video+playlists+youtube+pdf+download
Optional fullscreen kiosk mode and command interface for embedded applications
Includes omxplayerGUI, an X front end for omxplayer

@gkreidl:
1) No I was using Mist.
2) I don´t have the PIX, which is one of my problems posted above... How to install it?
3) Same on Clearlooks, so you were right.
4) Using Adwaita for the moment, working with my "black application(s)" - thx!

Very obscure. Also the ejecter-plugin not showing up. Anyway, one problem left (the GUI one).

Update: And gone away after a reboot. The config (/home/pi/.config/lxpanel/LXDE/panel) has not been changed; but the tray plugin (aka "notification center"?) isn´t available anymore.

Problem even getting worse: Applications starting in tray are not showing up there anymore... horrible!

When doing a "lxpanelctl restart" all the missed apps are visible for half a second. Then lxpanel get´s loaded and finally everything missing (wicd, clipit, other apps starting minimized to tray) is away again.

When killing all lxpanels (sudo lxpanel exit, then checking via top/htop) and running "lxpanel" from a cli, a lxpanel with a completely other setting is shown: e.g. the wicd+clipit and my other "start minimized to tray-applications". I assume because it is using a standard profile. Starting with "lxpanel -p LXDE &" I get my profile with the missing parts. Output says:

Thanks! It helped a lil bit... made a comparison; I´m only missing the ejecter.so.
Can you send it over to me? Would save me a lot of time (downloading Raspbian Jessie image, installing it in a VM, grabbing the file, ...)