Choose style:

Author Topic: Last 2 Installation Issues to Resolve [Solved]  (Read 1426 times)

0 Members and 1 Guest are viewing this topic.

Offline starchase

  • Jr. Member
  • **
  • Posts: 50
  • Karma: 1
  • New Forum User, Old Old Forum User
    • View Profile
  • Peppermint version(s): Peppermint 9
Last 2 Installation Issues to Resolve [Solved]
« on: January 20, 2015, 06:15:37 pm »
I've got Peppermint 5 installed, just updated the netbook, and have 2 niggling issues

Scanning for btrfs file systems and lost the power button in the system tray.

When the machine cold boots it takes a brief time to scan for a btrfs file system.  Is this normal?  I did see anther thread where the poster was told he could do something to remove this but it didn't make a difference to his start up, but I wonder if this is something that the OS should be doing.

And now, for an undisclosed reason, the power graphic that was in the far right corner of the system tray is gone and the option to restore it is not in the "add/remove Panel items" applet.  I know the Menu button can be used and select log-off and that brings up the same list if commands.  Is there a way to bring back the systray power button?

John
« Last Edit: January 21, 2015, 05:52:15 pm by starchase »
Asus Eee PC 1025C, Intel Atom N2600 Dual Core 1.6GHz, 1GB DDR3, 320 GB HDD, Peppermint 9

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 25451
  • Karma: 2798
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 8R, 9, and 9R
Re: Last 2 Installation Issues to Resolv
« Reply #1 on: January 20, 2015, 06:27:03 pm »
Scanning for the btrfs filesystem is normal, but if you're not using btrfs you can remove the btrfs-tools package which will get rid of that message:
Code: [Select]
sudo apt-get remove --purge btrfs-tools
====================================================================

Replacing the system tray power button - can you post the contents of:
Code: [Select]
gedit ~/.config/lxpanel/Peppermint/panels/panel
remember Linux commands ARE case sensitive .. so that's a capital P in Peppermint ;)

here's how that file should END, if you want to go ahead and edit it yourself (ie. the following is just the last 2 sections of the file, not the entire contents)
Code: [Select]
Plugin {
    type = dclock
    Config {
        ClockFmt=%R
        TooltipFmt=%A %x
        BoldFont=0
        IconOnly=0
        CenterText=0
    }
}

Plugin {
    type = launchbar
    Config {
        Button {
            id=peppermint-logout.desktop
        }
    }
}
then you'll need to log off/on before the button will show up.



HINT -
For reference there's a default copy of that file at
/usr/share/lxpanel/profile/Peppermint/panels/panel
but DO NOT edit or delete that copy .. only ever edit the copy in your home folder.
« Last Edit: January 21, 2015, 06:02:04 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline starchase

  • Jr. Member
  • **
  • Posts: 50
  • Karma: 1
  • New Forum User, Old Old Forum User
    • View Profile
  • Peppermint version(s): Peppermint 9
Re: Last 2 Installation Issues to Resolve [Solved]
« Reply #2 on: January 21, 2015, 05:55:32 pm »
Those two things did the trick.  Some of the last part of the config file was missing so adding what you gave me brought back the power button icon.  And there is no more message about scanning for the aforementiond file system.

Thanks a lot!

John
Asus Eee PC 1025C, Intel Atom N2600 Dual Core 1.6GHz, 1GB DDR3, 320 GB HDD, Peppermint 9

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 25451
  • Karma: 2798
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 8R, 9, and 9R
Re: Last 2 Installation Issues to Resolve [Solved]
« Reply #3 on: January 21, 2015, 06:00:18 pm »
You're most welcome .. thanks for marking the topic solved :)
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec