Are these two separate installations, or do you have both desktops installed in one system? If they are separate, it might be worth comparing the package lists.

Did you install with a mirror or just from the dvd? If you didn't use a mirror, make sure your sources.list has

deb http://auto.mirror.devuan.org/merged/ jessie main

For xfburn, make sure gstreamer0.10-plugins-good is installed.

Check the other dirs in /usr/share/doc. It's possible that it was all removed to save space. My doc/mpv is full of files that have some content. A reinstall of mpv should fix it.

I don't know about gparted. What you describe is different from the other permission/authentication problems reported for gparted, but it might be related. (consolekit, policykit-1, policykit-1-gnome, libpam-ck-connector, udisks...)  If synaptic is installed, does that work ok?

An even easier solution than switching to gnewsense would be to avoid upgrading wheezy. Do they have any plans for a jessie release? And do they offer non-free wireless firmware? That would be a deal-breaker for a lot of people.

Here's what's in the current download from gnewsense.org:

There is no default firewall front-end installed in debian or devuan. There is iptables, but no rules are in place.  If you install some services that listen for connections, then you will have open ports. (examples: openssh-server, mysql-server, apache2, samba)

If you're behind a router, the router is being scanned, and unless you set up port-forwarding in the router, the outside world can't see the open ports on your computer.

sort -u  ~/.bash_history > temporary-file
cat temporary-file > ~/.bash_history
nl temporary-file > index_file

Use the index file for reference. You don't want to number the lines in .bash_history, but you do want a numbered list.
This will work until you reach the limit of bash_history, and the commands start scrolling off the top. See 'man bash' for the HISTSIZE setting if you want to change the number of lines that get saved. I don't remember what the default is - maybe 1000 or 2000.

The version of yad (0.38) in the ascii repo uses gtk3 and does not work will with refracta tools - buttons are off-screen. I made gtk2 verions in jessie, but they seem to be working fine in ascii -
http://distro.ibiblio.org/refracta/file … _packages/

Or, you could package them yourself. I already made the one or two small changes for gtk2.
https://git.devuan.org/fsmithred/yad

Make sure you have ascii-proposed-updates enabled in sources.list. Some of the security updates can be found there.

Use the full path. (without sudo)

export PATH="$PATH:/home/devur/scripts"

I'm not sure what the best solution is. One thing you could try is downgrading all those packages to the version you had previously. The deb packages can be found in /var/cache/apt/archives. But that could be messy.

If everything seems to be working, you might just leave it alone. Wait for us to do some work on ascii and then switch your sources from jessie to ascii and upgrade the rest of your packages so they are from the same release as the ones you just pulled from stretch. No guarantees that it won't be messy, too. But maybe it will work ok.

If you are adventurous and know your way around the package manager pretty well, you could try upgrading the rest of the system to ascii now. You will probably run into conflicts. Don't do it unless you are comfortable with the idea of solving those problems and would not mind reinstalling if it turns out badly.

jessie = jessie
ascii = stretch
beowulf = buster
ceres = sid

I don't know if it's related, but thunar has a similar bug. Sometimes it locks up when it's in detailed list view. If I catch it soon enough, I can press ctrl-1 or ctrl-3 to change to icon or simple list view or else close the window by clicking on the x in the corner. If I wait, it totally locks up and has to be killed from command line. It's a known bug in thunar that's been around for years.

Faster boot times. (no more 5-minute waits for a start job)
Predicatable interface names. (I know it's going to be eth0 unless I changed my hardware.)
An init system that's been well-tested. (I might switch to systemd once they're done developing it and it's had time to mature.)
An init system that knows it's an init system and is OK with that.

Probably more, but it's time to let the dogs out.