kaosx / core Goto Github PK

I always used ethernet in the last couple of months on my main machine.

Today a friend come by and reported broken WiFi on her KaOS, which I installed recently, so I plugged in my ethernet cable into her device and saw by then that my own WiFi is also not working.

I added a second WiFi chip via USB and that one did not work also.

WiFi not working means here that inxi and lsusb/lspci report healthy chips and the network manager won't allow/react when I try to enable WiFi. The button is simply not working and the hardware buttons neither.

Here is the system info from both laptops:

https://ptpb.pw/k7HR
https://ptpb.pw/71JQ

After startup, I have to switch to tty2, login, and start sddm service again:
systemctl restart sddm

No change made to the system configuration after install.

Running journalctl -xb shows:

Jul 26 20:06:09 photon sddm[437]: Failed to read display number from pipe
Jul 26 20:06:09 photon sddm[437]: Could not start Display server on vt 1

Please consider adding the Infinality patches to the freetype2 package as well as the corresponding patches to fontconfig and cairo. This is a (feature) request but in practice the gain in font rendering quality is so large that I consider it almost a bug to omit the patches in question. See the screenshot which shows a Konsole window before (left) and after (right) installing the freetype2-infinality package.

Up-to-date patches can be found in archfan's repository, a fork of bohoomil's invaluable work on the legacy Infinality patchset made compatible with Freetype 2.7+:
https://github.com/archfan/infinality_bundle

Note also the issue with glibc 2.25+ that probably affects building the standard fontconfig too:
archfan/infinality_bundle#9

Something goes wrong, if i install KaOS on BIOS, it works fine via UEFI:

GRUB doesnt appear on the first reboot, instead does a black screen, which say that there is no OS installed.

https://gist.github.com/anonymous/a186f372ed7b175f89bea0d7fec0a5ce

I'm having this issue with pckcp -e where it is deleting my makedepends entries inside of my PKGBUILD. It's not a blocker, because I can always edit the resulting file manually, but it seems like a small latent bug that should probably be squashed to avoid future confusion.

Here is my pckcp -v:

pckcp 0.85.6

In case it is needed, here is my hardware info:
https://gist.github.com/anonymous/ba3fb6a781384b541f921abe2b572398

Here is what the utility says:

Info:
  Header is clean.
Info (L.6):
  Variable 'makedepends' is clean.
Info (L.3):
  pkgrel is clean.
Info (L.5):
  arch is clean.
Warning:
  Variables 'depends' and 'makedepends' are empty. You should manually check if it is not a missing.
Info (L.31-35):
  package() function is present.

Remove all unneeded comments before save? [Y/n] Y
Modifications saved in PKGBUILD.new!

Example Input (PKGBUILD):

pkgname=cmocka
pkgver=1.0.1
pkgrel=1
pkgdesc="cmocka is an elegant unit testing framework for C with support for mock objects."
arch=('x86_64')
makedepends=('cmake>=2.8.0')
url="https://cmocka.org/"
license=('custom:Apache-2.0')
changelog=ChangeLog
source=(
  ${url}files/1.0/${pkgname}-${pkgver}.tar.xz
  LICENSE
)
md5sums=(
  'ed861e501a21a92b2af63e466df2015e'
  'e3fc50a88d0a364313df4b21ef20c29e'
)

build() {
  cd "${srcdir}/${pkgname}-${pkgver}"
  mkdir -p build && cd build
  cmake -DCMAKE_BUILD_TYPE=Release -DUNIT_TESTING=ON ..
  make
}

check() {
  cd "${srcdir}/${pkgname}-${pkgver}/build"
  make test
}

package(){
  cd "${srcdir}/${pkgname}-${pkgver}/build"
  make DESTDIR="${pkgdir}/" install
  install -Dm664 "${srcdir}/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/Apache-2.0"
}

Example Output:

pkgname=cmocka
pkgver=1.0.1
pkgrel=1
pkgdesc='cmocka is an elegant unit testing framework for C with support for mock objects.'
arch=('x86_64')
url='https://cmocka.org/'
license=('custom:Apache-2.0')
changelog='ChangeLog'
source=("${url}files/1.0/${pkgname}-${pkgver}.tar.xz"
        'LICENSE')
md5sums=('ed861e501a21a92b2af63e466df2015e'
         'e3fc50a88d0a364313df4b21ef20c29e')

build() {
  cd "${srcdir}/${pkgname}-${pkgver}"
  mkdir -p build && cd build
  cmake -DCMAKE_BUILD_TYPE=Release -DUNIT_TESTING=ON ..
  make
}


check() {
  cd "${srcdir}/${pkgname}-${pkgver}/build"
  make test
}


package() {
  cd "${srcdir}/${pkgname}-${pkgver}/build"
  make DESTDIR="${pkgdir}/" install
  install -Dm664 "${srcdir}/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/Apache-2.0"
}

I can't open Plasma (Wayland), where Plasma works well without any problems.
I get splash screen but after that I can see only my Mouse Pointer, there is blank screen, which is in blank color.
As soon as I installed Kaos, after I logged in and used plasma, I switched to Plasma (Wayland), but it crashed too many times where, I would see Kde Wallet for encrypting keys, which ever option I click on it would crash and take me to Login screen, even touchpad click isn't working in wayland (I checked it out in that two minutes to select a option for Kde Wallet), Iam using latest Kaos version i.e.,2016.04

I hade a log file in my /var/log/Xorg.0.log
I don't known whether it is related to this topic or not so i'm not posting it here.

With the last update on this package whenever is used the KCP-Center python script, it throws an error about being unable to verify the certificate from github. Downgrading the pkg ca-certificates to 20170717 makes the helper work without issues.

KaOS 2017.01. I can start a Wayland session from Live or an install without kde-next and build. When I add them this is what happens when I try to start Wayland: The desktop flashes twice then the screen goes to a working three dots and a > image that I have heard called a Breeze Icon. Then after a few seconds the screen goes black. If I leave System Settings open before logging out from a Plasma session and logging in to a Wayland session it appears in the black screen as does the Xscreensaver settings screen, but there is no desktop. The default theme set after adding kde-next and build is Midna, so I thought it was the theme. A breeze workspace theme with oxygen desktop theme previously worked in Wayland, but not now. The picture of InfoCenter was taken in a Plasma session, and the desktop theme shown in it is not what I used to try to start Wayland, I used Oxygen.

Hi I'm using an HP 15 AC650TU laptop with KaOS 2016 version. I have some problem connecting to the laptop using WiFi. To connect to the wifi I have to keep the wifi device close to the laptop or else it wont detect the wifi connection and even if i keep it close, it shows only one bar signal. Please help me. I can't use my laptop in public wifi places.

isl3890-firmware file listing is /pkg/usr/lib/firmware/isl3890/isl3890
Is this correct?

I think it's should be like /usr/lib/firmware/isl3890/isl3890

A tiny mistype (openvpn instead of nfs-utils) from the Kdialog message comming from the build package

'sudo systemctl start autofs.service' works OK
'sudo systemctl enable autofs.service' does not work:
Error: Failed to execute /usr/lib/systemd/systemd-sysv-install: No such file or directory
It looks like the script systemd-sysv-install is missing

Hi,

I noticed that your team still distributes MD5 checksums for the .iso images for KaOS at – for example – the following URL:

https://forum.kaosx.us/d/1936-test-cycle-2017-06-iso

May I kindly ask you to take a look at the following links?

https://en.wikipedia.org/wiki/Secure_Hash_Algorithms

gobolinux/LiveCD#8

MD5, SHA-0 and SHA1 are all vulnerable to collision attacks.
SHA256 (or SHA512) is now the standard (for the moment).
I highly recommend dropping the use of MD5 and replacing it with SHA256 (or SHA512), a signature and PGP key.
I also suggest removing all references to MD5 and SHA1 in the source code in your build system.
I am simply using Qubes OS as an excellent point of reference, which uses SHA256, SHA512, a signature and a PGP key.

https://www.qubes-os.org/security/verifying-signatures/

https://www.qubes-os.org/downloads/

Concerning the use of Bittorrent, could you please read this?

https://www.ghacks.net/2016/02/21/linux-mint-hacked-iso-images-compromised/

If you put the .iso image and corresponding SHA256 checksum file, signature and PGP key in a .zip file and distribute it immediately via Bittorrent BEFORE hosting it on a website, hackers will probably not be able to compromise the integrity of the .iso image, because the SHA256 checksum in the Bittorrent file is much harder to alter than one stored on a website. Furthermore, you then have the option of comparing the SHA256 value in the .torrent file with the value on the website. This goes even further than what most GNU/Linux distributions actually do….
“The reason is simple; popular torrents are distributed from several seeders and peers, and once they are in circulation, it is not possible to manipulate the data, say replace it with a hacked image.”

Kind regards,

Mark Rijckenberg

When querying any systemd manual page (journalctl, systemctl, systemd, etc) from the konsole (or any terminal), the text is showing with weird tabulations.

systemd man page:

Journalctl man page:

I have systemd 1:244-3 package installed.
Kernel: Linux pc 5.4.7-1 #1 SMP PREEMPT Wed Jan 1 12:02:35 UTC 2020 x86_64 GNU/Linux

PD: also the systemd-unit manual is missed.

el boton de cerrar secion en kaosx no me funciona y al querer cerrar la sesion se queda en pantalla negra.

Small feature request to use the worldwide timeserver pool for the systemd ntp-service instead of North America.

In Line 69:
Global: NTP_SERVERS="0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org"
Current: NTP_SERVERS="0.north-america.pool.ntp.org 1.north-america.pool.ntp.org 2.north-america.pool.ntp.org 3.north-america.pool.ntp.org"

As "The NTP Pool DNS system automatically picks time servers which are geographically close for you [...]" (Source) and that way f.e. Australian or European users can get faster time servers. The default for ntp is already in the same manner.

https://github.com/KaOSx/core/blob/master/libcap/PKGBUILD lists ''attr" as a dependency for libcap. That dependency was dropped a while back... Specifically libcap-2.25.

I'm building KDE with kdesrc-build tools and perl-json module is missing from repo.

At the moment a good workaround is use CPAN and build ourself.

A recent pacman -Syu upgrade that pulled in cpio 2.12 failed to commit because file /usr/share/man/man8/rmt.8.gz conflicted with a same named file owned by tar

I've opened up the issue on the KaOSx/main repo (issue #12) - don't know if this is the correct place or the /main repo.

Short summary:
When booting into EFI in VirtualBox, the 2015.04 ISO in live mode fails to start Xorg server.
When booted using BIOS, it does work.

The Xorg log is included in KaOSx/main#12.

KaOS 2015.04 ISO
Boost. Python error this process "userkf5/main.py srcipting running".
<class 'FileNotFoundError'>
[Errno 2] No such file or directory: '/etc/skel/yakukaerc'
Traceback:
File "/usr/lib/calamares/modules/userkf5/main.py", line 83, in run
(install_path, user, d, f))

File "/usr/lib/python3.4/shutil.py", line 245, in copy2
copyfile(src, dst, follow_symlinks=follow_symlinks)

File "/usr/lib/python3.4/shutil.py", line 108, in copyfile
with open(src, 'rb') as fsrc:

I have a small document has some pictures, but when viewing the document in pdf LyX closes. Returns the following error message in console "Error del bus (`core' generado)"

Thanks KaOS, demm