Well despite the ambiguity, I knew what you meant...

Get well soon.

Good lawwwddd....

Well...  in Debian at least, "testing" will always point to testing, whereas the codename will point to testing while the distribution is testing, but to stable once it goes stable.

So when I said "testing" I mean just that and used the word "equivalent" with reference to ASCII being equivalent to Debian testing, not being based upon it (in terms of same versions, etc).

So it would seem that Devuan will effectively still be a "derivative" rather than a fork for the next release.  It doesn't surprise me, as I've always thought that completely forking an entire distribution, especially one the size of Debian, was gonig to be a momentous task.

My last post was in response to this:

Linux Mint is also "not free" (using your terminology), the firmware is already installed.

Then just use Linux Mint, until you're ready to tackle this problem again (if at all)?  Debian or Devuan are not the same as the Debian derivatives like Ubuntu and Mint which are completely pre-configured as install-able live systems and ready to run "out of the box".

You're also running "ASCII" which is the equivalent to the Debian testing branch.  This is not a finished, stable release.

When it comes to device firmware, "non-free" is often unavoidable.  It's likely that many of the devices in your computer are pre-loaded with proprietary firmware (such as the system BIOS or EFI/UEFI).  The only difference between this firmware and the firmware you install from the repositories is that the former is already flashed to the device, the latter is loaded from userspace.

Yes it's "non free" code, but but it's not executable by your OS, it runs on the device itself.

You already had a closed source realtek firmware installed and simply added the radeon firmware needed for your hardware to fucntion.  The alternative is to buy different hardware, not change OS.

Any warnings or errors in your Xorg log file? (/var/log/Xorg.0.log)

Also have a look at ~/.xsession-errors

And finally, run VLC from a terminal emulator and see if it spits any errors when it happens...

Looks like the firmware is now installed.  Reboot and then check your dmesg again to see if that same error appears.

By the way, the answer to your question in this locked thread: http://dev1galaxy.org/viewtopic.php?pid=5934#p5934

Is in my last post.  Though I suggest just installing aptitude.

Do the same for libpulse0.

How about checking why it's installed?

$ aptitude why libsystemd0

Works here as described.  You're right that the man page gives options for pictures, but the --picture option itself is omitted.  You could drop the author a mail.

gnomeVFS is not GVfs.  To cut a long story short this is legacy ghome 2.x stuff, you don't need it, but not installing gstreamer0.10-gnomevfs will free up 599kB...

It depends on some gconf packages, those will be much larger, but it's likely other packages depend on them as well.

What will help you is a reverse depends lookup, e.g.

$ apt-cache --installed rdepends gstreamer0.10-gnomevfs

Or

$ aptitude why gstreamer0.10-gnomevfs

This will tell you why a certain package is installed.

Also I assume you've disabled recommends and suggests in your apt configuration to cut down on crap?

Yes, that's what I was referring to.  Bleachbit is a "cleaner", so it deals with dotfiles, etc, not the package management system.

As far as I know it's not going to remove unwanted deb packages for you and resolve dependencies.  Thus I'm not entirely sure how it will make Midori browser, "lighter".

To remove unwanted deb packages there is an autoremove option to apt or apt-get, another package manager front end, aptitude, is also good at cleaning up unwanted cruft.  It might help you "slim down" your installations.