login
+-

HTML ezBlock

Bluestar Linux - Overview

 

Bluestar is a GNU/Linux operating system, built to provide the following features:

 

  • Up-to-date 64-bit Kernel version - 4.14.x
  • Archlinux32-based 32-bit release - 4.14.x
  • Fast (optimized for performance)
  • Wide Variety of Applications - Always Current Versions
  • Full Development / Desktop / Multimedia Environment
  • Arch Linux Based Distribution
  •  

    Sourceforge.net

    Open Invention Network

    Facebook Page

     

    Live Media Default User Accounts

    Screenshot


    UserBox

    Welcome, Guest.
    Please login or register.
     
     
     
    Forgot your password?

    Recent Posts

    Pages: [1] 2 3 ... 10
    3
    From the Administrator / Installation Tip for Transferring Network Configuration
    « Last post by admin on January 09, 2018, 06:03:50 PM »
    After booting up the live system and before starting up the installer, you must set up your networking. By default, your wireless security is set to "Store password for this user only".

    During installation, your network settings are in fact transferred to your new system, however if your wireless security is set to "Store password for this user only", your WEP or WPA key will not be stored in your network config and will not be transferred to the new installation even though the device and SSID information is.

    To ensure that your new system's networking is configured exactly like that of the live system at the time of installation, make sure to edit your wireless connection and set security to "Store password for all users". This will add your security key to the config file (/etc/NetworkManager/system-connections/your_network_name) which will in turn be transferred during installation to your new system.

    Ignore this if it matters to you that passwords are compartmentalised - normally they aren't since typically there will be only one network device for internet access on any given system and all users will be using the same security anyway.

    Cheers
    6
    From the Administrator / Pamac Issue - i686
    « Last post by admin on December 21, 2017, 06:56:09 PM »
    It looks like the pamac issue is/was related to polkit. The x86_64 version was updated 12/15, which is why the problem suddenly cleared up on that date. I'm guessing the issue appeared after the 12/13 update of kauth. Unfortunately, those of you running the arch32-based i686 release are probably still seeing the problem. I was able to clear it up on my own local i686 installation by installing the polkit version currently in the testing repository. If any of you would like to do the same, you can download it using this link:

    https://32.arlm.tyzoid.com/i686/testing/polkit-0.113+34+g29ba7af-1.0-i686.pkg.tar.xz

    Install using 'pacman -U filename'.

    Otherwise, you will have to simply wait it out. I'm certain a fairly hefty i686 update is due to be pushed within a couple of days which will include the new version of polkit (as well as KDE and the 4.14.6 kernel). So you won't have a long wait if you decide to just use pacman directly for a few days.

    Another alternative is to install kalu-kde. It seems to have been impervious to this version-mismatch issue. If you do, remember to copy /usr/share/applications/kalu.desktop to /etc/xdg/autostart to have it start automatically on boot up. Personally, I prefer using kalu when I use a graphical updater, which is why I initially missed the pamac issue.

    Cheers
    7
    From the Administrator / Pamac Issue & Wine-staging (i686) Issue
    « Last post by admin on December 18, 2017, 02:57:21 PM »
    OK. I've pushed a new build of pamac and pamac-tray-appindicator to the bluestar repositories. The latest version is now 6.2.2-1. I could find no obvious reason for its sudden recent failure other than that a recent KDE update and a rebuild seems to have fixed it. I have some suspicion that kauth was the culprit, but I can;t prove it. Pamac is officially Manjaro software, not basic Arch, and Manjaro has their own release schedule, so it's entirely possible this issue wasn't even noticed in the Manjaro environment. There certainly weren't any bug reports other than a comment posted to the AUR page for pamac - the maintainer's response was 'go talk to the developers'. Nothing else was posted.

    In any case, after installation, please check your preferences. The format of the new /etc/pamac.conf file has changed, and the default values are probably not what you want - 6 hour interval, no AUR check, no AUR builds.

    In other news, the archlinux32.org support folks finally fixed wine-staging, so now everything installs as expected. For those who are so inclined, you can now re-order your repositories in pacman.conf, placing bluestar at the bottom of the list where it belongs. This only applies to those of you with a 32-bit installation.

    Cheers
    8
    From the Administrator / Pamac Issue
    « Last post by admin on December 16, 2017, 02:07:20 PM »
    I am aware that there is currently an issue with the pamac package manager, and specifically with the updater. I'm working on it.

    Meanwhile, I've downgraded the package version in the bluestar repository to v6.2.1-1, which appears to be the last version that still works. If you're experiencing problems with pamac, simply reinstall it:

    Code: [Select]
    sudo pacman -Syy
    sudo pacman -S pamac pamac-tray-appindicator

    And reboot.

    The downgraded version will be installed.

    Cheers
    9
    From the Administrator / pgp key issue - i686
    « Last post by admin on December 13, 2017, 12:28:35 PM »
    For those of you using the i686 release, you're probably still running into pgp key issues when you perform an update:

    Code: [Select]
    downloading required keys...
    error: key "77BEA194A234FF8F" could not be looked up remotely
    error: required key missing from keyring
    error: failed to commit transaction (unexpected error)
    Errors occurred, no packages were upgraded.

    To resolve this issue until the arch32 team sorts this out, do the following:

    Code: [Select]
    $ sudo pacman-key --init
    $ sudo pacman-key --populate

    Then rerun your update.

    Cheers
    Pages: [1] 2 3 ... 10
    Powered by EzPortal