Hi Mr. Bean.

Just to be sure, I downloaded the 32 bit version and installed it. I ran all updates, rebooted, and all of the shutdown options are working...so I'm not sure what could be the problem.

You might try reinstalling obsession-logout to see if that helps...not sure if it will. I'll give an alternative at the end of this post.

I don't think that font warning should have anything to do with it; however, it appears that the .font.conf file is causing a problem. I tried running obsession-logout from the terminal, and I got the same message as you (even though all of my shutdown options are working). I then looked in the ~/.config/fontconfig/ folder, and that file already exists there...so I just deleted the .fonts.conf file from the Home folder. After doing that, I tried it all again, and the error message was gone.

If you're unsure how to do that, just open your file manager. Right click on an empty space, and choose "Show hidden files". Then look for the file called .fonts.conf and click on it one time to highlight it. After highlighting it, click on Edit in the tool bar and then click Remove.

As to Docky...I mentioned earlier that what you're experiencing is a well-known and long-standing bug with Docky. I don't know a fix for it...sorry. Perhaps someone else here may know of one? If so, please feel free to post it!

The application gmrun is in the 32 bit version and 64 bit versions that I downloaded...it's one of the items at the top of the right-click menu, but it's named as "Run command".  Try clicking on that, and a small window will open in the center of your screen. Type in the word docky, and hit Enter on your keyboard, and Docky should start again. Sorry that I couldn't be more help with that problem.

Now...if fixing that font error and reinstalling obsession-logout doesn't help, here's a possible fix for you...it may not be what you prefer, but it will at least hopefully get you back to being able to Shutdown, reboot, etc. This is actually the method that I included with Miyo-i3, and I'm considering using it in future versions of MiyoLinux...haven't decided yet though. Anyway...

ALTERNATIVE SHUTDOWN OPTIONS

Edited to add: before anything else...let's try something first. The following command should reboot your computer, so only do this when you're ready to try a reboot. If this works, then proceed with the rest of the instructions...

Open your terminal, and copy and paste the following command to see if it will reboot your computer...

dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart

...then hit Enter on your keyboard.

If that rebooted your computer, proceed with the following instructions.

Open the right-click menu, and go to...

Advanced > Obmenu-Generator > Menu Schema

When that opens, scroll to the bottom of the file, and you should see these lines...

## This uses the 'oblogout' menu
    {item => ['obsession-logout', 'Exit', 'exit']},
]

Now...put your cursor at the end of the line...

{item => ['obsession-logout', 'Exit', 'exit']},

...and hit Enter on your keyboard. That should put a space between that line and the ] symbol below it. So it should now look like this...

## This uses the 'oblogout' menu
    {item => ['obsession-logout', 'Exit', 'exit']},

]

Now...in that empty space that you just created, copy and paste the following into it...

{begin_cat => ['Exit', 'exit']},
    {item => ['openbox --exit',  'Logout',  'gnome-logout']},
    {item => ['dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate',  'Hibernate',  'gnome-session-hibernate']},
    {item => ['dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart', 'Reboot', 'gtk-refresh']},
    {item => ['dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop', 'Shutdown', 'gnome-shutdown']},
{end_cat => undef},

MAKE SURE THE...
]
...SYMBOL IS BELOW THOSE LINES!

So, the bottom of the Menu Schema file should now look like this...

    ## This uses the 'oblogout' menu
    {item => ['obsession-logout', 'Exit', 'exit']},
    {begin_cat => ['Exit', 'exit']},
    {item => ['openbox --exit',  'Logout',  'gnome-logout']},
    {item => ['dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate',  'Hibernate',  'gnome-session-hibernate']},
    {item => ['dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart', 'Restart', 'gtk-refresh']},
    {item => ['dbus-send --system --print-reply --dest="org.freedesktop.ConsoleKit" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop', 'Shutdown', 'gnome-shutdown']},
    {end_cat => undef},
]

Save and close the file.

At this time, you will have two exit options in your right-click menu. The ones that we just added requires you to hover your mouse cursor over the word Exit, and it will give you the following options...

Logout
Hibernate (I didn't check, but you might have to install the package called hibernate if you use this)
Reboot
Shutdown

Clicking on any of those options will immediately go into effect...If they work, and you're happy with that, then you can open that same file again, and comment out the other original Exit option...just put a # symbol in front of the following line...

{item => ['obsession-logout', 'Exit', 'exit']},

...so that it looks like this...

#{item => ['obsession-logout', 'Exit', 'exit']},

Then save and close the file again, and you'll only have the new Exit options in your menu.

This may not be your preferred answer, but hopefully it will help as a last resort.

Okay. I downloaded and installed Miyo XTRA Jessie. Upgraded it to Ascii and rebooted.

No menu as expected.

Tried the first of the two terminal commands given in the Release Notes...and it failed.

Tried it again, and it failed. That sent me ballistic, and I was about to go into total demolition mode...

...but then...

I realized I hadn't connected to the internet after the reboot.

Connected to the internet, ran the two commands, and the menu was back.

Okay. Hmmm...

Oh no...did the instructions not work (that I gave in the Release Notes) regarding how to fix the menu if a user upgrades to Ascii (by issuing two commands in the terminal)?

I'm only asking, because if the directions that I gave in the Release Notes don't work now for some reason, I'd like to know.

During my testing, I tried upgrades to Ascii several times, and the instructions worked each time.

I'm just glad to hear that you got it back though! 

...and I hate to be the bearer of bad news (?) , but I just uploaded Ascii versions to Sourceforge. DOH!!!

Thanks again! Take care!

Miyo XTRA Ascii is now available if anyone is interested.

https://sourceforge.net/projects/miyoli … e/Openbox/

Sorry for cutting in fsr, but I wanted to report...

I'm writing this from a freshly installed Miyo-XTRA-Ascii 64 bit, and the keyboard shortcuts in question are working on it too...so both 32 bit and 64 bit versions are producing the desired effects as to the keyboard shortcuts that fungus has pointed out. At this time, I'm not sure why they don't work on Jessie builds of Miyo.

I have a little more testing to do, and if all goes well, I will upload the new XTRA-Ascii versions to Sourceforge sometime tomorrow...IF! LOL!

Thanks for pointing this out fungus. As I said...I'm not much of a keyboard-shortcut user, so I would have never noticed this in my testing. I guess that shows a shortcoming in me and my "developer status"... LOLOLOLOLOLOLOL!!!

I'm using the installer-base and snapshot-base versions included in the Ascii repos on the XTRA Ascii versions that I'm making now.

Now see...when I look at stuff like this, I want to have a nervous jerkdown.  

http://www.palemoon.org/redist.shtml

Out of curiosity, I tried those keyboard shortcuts while I was building the latest Miyo-XTRA Ascii 32 bit. They worked during the build. I didn't think to try it after I installed it.

Altoid,

Do you have gksu installed?

If so, can you open the terminal and enter...

gksu linssid

(not sure if that's the right command...use whatever command you used with su)

Does it work that way?

If it does, you could change the Exec= command for it in /usr/share/applications

Exec=gksu linssid

(or gksu "whatever-the-command-is")

Okay...I figured out why the terminal in i3 wasn't showing me the dependency errors. I had a brain jerkdown last night and forgot what I did in the Openbox trial installation.

I made a very...VERY basic Openbox installation to test it on. I didn't have anything but the basic right-click menu. So what I did was open PCManFM with the terminal from that menu. That terminal was the one that I left open, and it was that terminal that was showing me the dependency errors.

Once PCManFM was open, I navigated to the Downloads folder and opened a terminal there to make the MuseScore .appimage executable. Then, everytime I clicked on the .appimage to try and open it, the original terminal would show me the dependency error(s).

I just now removed one of the dependencies for the .appimage in i3 and tried it following those steps, and it worked the same. The original terminal showed the missing dependency.

This isn't ideal, but if anyone reads this thread because you're having trouble opening an .appimage in MiyoLinux, follow these steps...

1. Open your terminal and use it to open PCManFM

Leave that terminal open.

2. Navigate to the .appimage and open another terminal in that folder to make it executable

I also right-clicked the .appimage and changed its Execute permission to Anyone

3.  Double-click the .appimage

You'll be asked if you want to Execute it. Click Execute.

4.  The original terminal will show you the missing dependency

It may show something like...

/tmp/.mount_VwG71Z/bin/mscore-portable: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directory

The "libpulse.so.0" is the missing dependency. However, the leading "libpulse" is what is needed to be installed. I used Synaptic to search for and install each dependency. For example: libpulse0 was the name of the actual dependency as shown in Synaptic.

With MuseScore, it took 5 dependencies...I had to click the .appimage 5 times to find each one. After finding and installing the dependencies, it opened. WHEW!

Sounds like a lot, but it only took a couple of minutes...if that long.

Edited to add: I went back and edited my original instructions in case a reader doesn't make it this far in the thread.

devuan_dk_fan,

OY! i3 doesn't work like Openbox as far as showing me the missing dependencies!

Now I remember why Openbox is my first choice with i3 second. LOLOLOL!!!

I didn't get the "errors" in i3's terminal like I did in Openbox. However, here are the dependencies (and the few items they pull in) that you'll need to install according to how they are shown in Synaptic...

libvorbisfile3
libsndfile1 (this will actually pull in the third "libvorbis" dependency)
libpulse0
libxslt1.1
liborc-0.4-0

After installing those dependencies (I used Synaptic), the MuseScore .appimage will open in i3.    Make sure to read my post above about the possible need for PulseAudio...

Now I have to figure out why i3's terminal doesn't show the errors like the Openbox terminal...

devuan_dk_fan,

I just got the MuseScore Appimage to work in the Openbox version of MiyoLinux. It should work in the i3 version too. Here's what I did...read all of this before proceeding.

VERY IMPORTANT: OPEN PCMANFM WITH YOUR TERMINAL, AND LEAVE THAT TERMINAL OPEN DURING THE WHOLE PROCESS.

1. I downloaded the .appimage and made it executable by opening another terminal in the Downloads folder and used the command...

chmod u+x MuseScore*.AppImage

Just to be sure (since I've never used an .appimage before, I right-clicked the .appimage, went to properties, and changed the Execute permissions to "Anyone".

I then double clicked the .appimage. The open terminal showed me the initial error. I was missing libvorbis something-or-other. That's what was throwing me off a few days ago, because it was showing something like libvorbis.so.3 (don't quote me on that). When I searched previously for those items from the list you provided, I was searching for libvorbis.so.3...that's why nothing was showing up for me when I searched the other day.

2. I opened Synaptic, and I searched for libvorbis.

I was given a result. Unfortunately, I didn't pay attention initially, because this was all hit-n-miss for me. Here are the items that are now installed with libvorbis in their names...I can't remember which one I initially installed, but the other two were pulled in with it.

libvorbis0a
libvorbisenc2
libvorbisfile3

3. Double-clicked the .appimage, and got another error of a missing dependency. This happened 3 more times (a total of 5 times). Each time, I searched Synaptic for the leading verbage of the missing dependency. Here's what I installed in addition to the libvorbis item(s)....

libsndfile1
liborc-0.4-0
libpulse0
libxslt1.1

After installing those dependencies, I double-clicked the .appimage, and it opened.

I didn't go any further to see if it would play, because I don't know a thing about it . MiyoLinux doesn't include PulseAudio by default, so if you're still on Miyo-i3, you may have to install PulseAudio or try Geoff 42's tip.