Search Results for 'ppa'

[Member fungalnet]

same image reburned, all I did is dist-upgrade and adding a kernel

The following packages were automatically installed and are no longer required:
  cpp-6 dh-python libaudio2 libicu57 libisl15 libllvm3.9 libllvm5.0 libmng1 libmpfr4 libntfs-3g871
  libperl5.24 libpython3.5-minimal libpython3.5-stdlib libqtcore4 libqtgui4 libvte-common libvte9
  libwayland-egl1-mesa libxfont1 perl-modules-5.24 python3-distutils python3-lib2to3 python3.5
  python3.5-minimal qtcore4-l10n
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  dict libcap2-bin libdns-export1100 libfribidi0 libgdbm-compat4 libicu-le-hb0 libicu60 libindicator3-7
  libisc-export169 libisl19 libllvm6.0 libmaa4 libncurses6 libncursesw6 libprocps7 librecode0 libtinfo6
  libwayland-egl1 parted recode wamerican
The following packages will be upgraded:
  adwaita-icon-theme antix-libs apt apt-transport-https apt-utils base-passwd bash bash-completion
  binutils binutils-common binutils-x86-64-linux-gnu bsdmainutils bsdutils build-essential cli-aptix
  cli-installer-antix cli-shell-utils conky conky-std console-data console-setup console-setup-linux
  cpanminus cpp cpp-6 cpp-7 cron dbus dbus-x11 dconf-gsettings-backend dconf-service debconf
  debconf-i18n debconf-utils debianutils desktop-defaults-core-antix dh-python dirmngr distro-info-data
  dosfstools dpkg e2fslibs e2fsprogs eudev fdisk file findutils fontconfig fontconfig-config g++ g++-7
  gcc gcc-6-base gcc-7 gcc-7-base gcc-8-base gdisk gettext-base git git-man glib-networking
  glib-networking-common glib-networking-services gnome-icon-theme gnupg gnupg-agent gnupg-l10n
  gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv grub-common grub-pc
  grub-pc-bin grub2-common gsettings-desktop-schemas gtk-update-icon-cache gtk2-engines-pixbuf
  hicolor-icon-theme ifupdown inxi iproute2 isc-dhcp-client isc-dhcp-common iso-codes iso-snapshot-antix
  iso-template-antix kbd keyboard-configuration less libapparmor1 libapt-inst2.0 libapt-pkg5.0 libasan4
  libasound2 libasound2-data libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data libatomic1 libatspi2.0-0
  libaudit-common libaudit1 libavahi-client3 libavahi-common-data libavahi-common3 libbinutils libblkid1
  libbsd0 libc-bin libc-dev-bin libc-l10n libc6 libc6-dev libcairo-gobject2 libcairo2 libcap-ng0
  libcc1-0 libcilkrts5 libcom-err2 libcomerr2 libcpan-distnameinfo-perl libcups2 libcurl3-gnutls
  libcurses-perl libdatrie1 libdbus-1-3 libdconf1 libdebconfclient0 libdrm-amdgpu1 libdrm-common
  libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libedit2 libegl-mesa0 libegl1 libegl1-mesa
  libelf1 liberror-perl libeudev1 libevdev2 libexif12 libext2fs2 libfdisk1 libfile-pushd-perl libfm-data
  libfm-extra4 libfm-gtk-data libfm-gtk4 libfm-modules libfm4 libfontconfig1 libgbm1 libgcc-7-dev
  libgcc1 libgcrypt20 libgdbm5 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgif7 libgl1 libgl1-mesa-dri
  libgl1-mesa-glx libglapi-mesa libglib-perl libglib2.0-0 libglibmm-2.4-1v5 libglvnd0 libglx-mesa0
  libglx0 libgmp10 libgnutls30 libgomp1 libgpg-error0 libgraphite2-3 libgtk-3-0 libgtk-3-common
  libgtk2.0-0 libgtk2.0-common libharfbuzz0b libidn11 libimlib2 libinput-bin libinput10 libisl15 libitm1
  libjson-glib-1.0-0 libjson-glib-1.0-common liblcms2-2 libldap-2.4-2 libldap-common libllvm3.9
  libllvm5.0 liblognorm5 liblsan0 liblz4-1 liblzo2-2 libmagic-mgc libmagic1 libmodule-cpanfile-perl
  libmount1 libmpdec2 libmpfr6 libmpx2 libncurses5 libncursesw5 libnetfilter-conntrack3 libnewt0.52
  libnghttp2-14 libnpth0 libobrender32v5 libobt2v5 libp11-kit0 libpango-1.0-0 libpangocairo-1.0-0
  libpangoft2-1.0-0 libpangoxft-1.0-0 libparted-fs-resize0 libparted2 libpciaccess0 libpcre2-8-0
  libperl5.26 libpng16-16 libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libpopt0
  libprocps6 libproxy1v5 libpsl5 libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib libqtcore4
  libqtgui4 libquadmath0 libreadline5 libreadline7 librtmp1 libsasl2-2 libsasl2-modules-db libseccomp2
  libselinux1 libsemanage-common libsemanage1 libsepol1 libsigc++-2.0-0v5 libsigsegv2 libslang2
  libsmartcols1 libsoup-gnome2.4-1 libsoup2.4-1 libsqlite3-0 libss2 libssl1.0.2 libssl1.1
  libstdc++-7-dev libstdc++6 libsystemd0 libtasn1-6 libthai-data libthai0 libtiff5 libtinfo5 libtsan0
  libubsan0 libunistring2 libuuid1 libvte-2.91-0 libvte-2.91-common libvte9 libwacom-common libwacom2
  libwayland-client0 libwayland-cursor0 libwayland-egl1-mesa libwayland-server0 libx11-6 libx11-data
  libx11-xcb1 libxapian30 libxatracker2 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0
  libxcb-render0 libxcb-shape0 libxcb-shm0 libxcb-sync1 libxcb-xfixes0 libxcb1 libxfont2 libxft2
  libxkbcommon0 libxml2 libxshmfence1 libzstd1 lightdm-gtk-greeter linux-compiler-gcc-7-x86
  linux-libc-dev live-usb-maker locales make man-db mime-support mount multiarch-support nano
  ncurses-base ncurses-bin neofetch openbox patch pcmanfm pcmciautils perl perl-base perl-modules-5.26
  pinentry-curses policykit-1 procps psmisc python3 python3-distutils python3-lib2to3 python3-minimal
  python3.6 python3.6-minimal qtcore4-l10n readline-common remaster-antix rsyslog sed sensible-utils
  squashfs-tools sudo synaptic tar tor tzdata ucf util-linux wget whiptail whois x11-apps
  x11-session-utils x11-utils x11-xkb-utils x11-xserver-utils xarchiver xfonts-utils xfsprogs xinit
  xserver-xorg-input-libinput xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-radeon
  xterm zlib1g
367 upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
Need to get 13.7 MB/258 MB of archives.
After this operation, 127 MB of additional disk space will be used.
Do you want to continue? [Y/n] n

anti-X - Adélie - obarun - systemd Free Space

[Member stevesr0]

hi dolphin_oracle and fungalnet,

so these are the correct repositories (except for the absence of the deb-src) and the paucity of security updates is apparently normal for right now…

Thanks.

I guess this is solved (if someone can add that for me).

stevesr0

[Member stevesr0]

Hi malanrich,

thanks for the suggestion. I did look at that site and it led me to explore the touchpad software in linux. Three tools are mentioned that are involved with touchpad configuration (evdev, synaptics and libinput). I have all of them installed on my system.

When I run xinput –list, it states that I have a Synaptics touchpad.

My problem is apparently due to a known bug in the synaptics software (xserver-xorg-input-synaptics) related to multitouch. My touchpad has three buttons below it. Whether multitouch is required for these to work properly, I don’t know

MY options are to attempt to fix the problem by editing the synaptics configuration file or to remove the synaptics package and switch to using libinput instead.

However, I have read that libinput doesn’t offer all the features that synaptics does.

Having just started to learn about this configuration, I am unclear how best to proceed. I haven’t seen a gui to make the configuration easy, and I would greatly appreciate advice from anyone(s) who has(have) dealt with this problem.

Thanks in advance.

stevesr0

Hi just getting back into linux systems:

used the USB live boot to wipe and just install to a drive on a laptop system

can boot the first time from the drive {didn’t so anything special jut used the vanilla installer and used whole drive as test}

so now upon a boot from the single HD on the system i can get the xserver {it boots like the live USB}

then reboot and no Xserver or a failed Xserver I am presented with a low res screen version and no input devices {it would appear}

so no mouse or Keyboard function :

NOW :

if i boot the live USB access the system drive root and edit /etc/inittab so that the default runlevel is 3

id:3:initdefault:

the system boots to the command prompt and i have mouse and keyboard access.
this all tells me it’s an Xorg problem – this system is an AMD A10 {old}

but i’m left scratching my head as to WHY it will boot the first time – so the drive will boot {and Xserver will work} the first time after an install from the live USB.

this leads me down the rabbit hole of the Xorg.conf file ..

the Xorg.conf file doesn’t exist any more ?? {apparently} so how am I meant to find out what is going wrong???
i can look at the /var/log/xorg.0.log and it says that the config is derived by udev?

so how do i see the udev {hopefully not the systemd virus version} log ?

I STRONGLY suspect that this is why there is a problem on the second boot –
if i am in the operational environment {on the first boot before it fails} and i run the command

df -h

there is a Udev filesystem – this is not present {of course on the live USB system}
I think when a user boots from the HD the first time the sys generates an Xorg configuration and sets that to the udev section
then when booting again the udev Xorg section is wrecking the Xserver.

I little frustrating it seems humanity has fallen a long way – there is no docs even on the {so called} ‘internet’ that ref to any of this?
I can’t seem to find much info at all

————–

TLDR:

Install from the USB to a Drive
Can boot from that drive once {first boot} {everything is fine}
will not boot the second time – Xorg xserver seems to be broken
Xorg config doesn’t exist?
how do i see the config of the Xserver if it’s being configured by Udev?

———-

anyone that has any hints or help thank you it might help someone else with Xorg issues.

my issue seems to be very similar to this issue:

https://superuser.com/questions/503617/xorg-input-devices-fail-without-udev

for me this is obviously related to how udev wants to have control & configuration of system devices.

with the systemd virus controlling udev then it has full live control of the whole system. if humanity wants that then sure – but i think that there should be other options also – so now i have to try to generate an Xorg.conf {i guess}

• This topic was modified 4 years, 10 months ago by kve. Reason: texterrors
• This topic was modified 4 years, 10 months ago by kve.

[Anonymous]

Your takeaway from that example may be different from mine. Here’s my assessment (and I don’t claim this is absolutely correct):
If your python program, your “it”, is intended to support touch/mobile usage, you probably want the (not from debian) up-to-date version of the kivy libraries. If “it” does use those, and is packaged for use on debian/antiX, the “dragging in all sorts of extra stuff” must include re-packaging and redistributing those kivy libraries or creating a setup mechnism which demands python pip as a prerequisite, retrieving the libraries from the web as needed (yuk, as a potential user, pip is a showstopper. Like, if i was inclined to trust and use unvetted PPAs, i should be using ubuntu. or maybe archlinux + AUR). The status quo probably can’t change until someone interested (and blessed by debian bureaucracy) steps up, decides to maintain up-to-date debian packages for kivy. Instead, within debian ecosphere I’m noticing attention toward touch-enabled apps that utilize/depend DE-proprietary libraries.

[Member stevesr0]

I am also experiencing a long boot time (5 minutes)on one of my computers with 17.1 (vs 24 seconds with 16.1). I also see a tpm (trusted platform module) error. My UUIDs in fstab and by blkid are identical. I also have a black screen (?no backlight) for most of that time.

My boot option editing doesn’t seem to take properly. I tried eliminating quiet and splash options and used xorg=intel without any change.

Except, after editing and rebooting several times, now I seem to go only to a console login. Startx doesn’t work. There is a message about lacking an xauthority file.

When it was launching to a desktop, the system worked ok.

I have wacom digitizer on this computer. Version 16.1 didn’t apparently detect or load that, while 17.1 does, so I suspect that it may be related to the initialization of the wacom files. (The Xorg.log file goes from 68 seconds at one point while working on the serial wacom driver to 312-319 seconds before then starting on the wacom stylus.

Apparently, the OP’s computer doesn’t have a wacom digitizer…

Hope that suggests something.

Steve

[Anonymous]

a game program can be tiny, like 100kb or less.
Snake sprite can be displayed as ascii characters in terminal, or with ncurses ui, or it can have fancier ui based on pygame.
For the dueling (against an opponent) feature, might need to checkout games-n-tutorials titled “tron”, not “snake”.
Anyhow, here are some leads

tutorial https://pythonspot.com/snake-with-pygame/ and https://www.youtube.com/watch?v=4MUcUhL0tMw

many ready to run variations of the snakegame https://www.pygame.org/tags/snake

also
https://github.com/tancredi/python-console-snake/tree/master/snake
http://www.grantjenks.com/docs/freegames/#snake
https://github.com/PPastorF/python-snake/blob/master/snake.py

[Forum Admin dolphin_oracle]

Well, here’s the thing.

The question you posted over at MX Forums, while I imagine was completely innocent in your case, is very reminiscent of other trollish type posts that apparently had the goal of pitting one group against the other. The mods might have been overzealous in locking the thread, but its from past experience. The mods are not perfect.

We also go out of our way to not attempt to steal users from antiX. and vice versa in the case of antiX pulling users from MX. Rather we try to direct folks to what they want. Often folks come to antiX and immediately throw Xfce on it and wonder why it doesn’t work like MX. And vice versa with folks putting one of the window managers on MX and not getting the antiX experience.

Talking about MX/antiX vs. Ubuntu/puppy/whatever, that would not likely earn the mod’s ire. Or even asking about differences. But your post had the feel of asking folks to convince you to switch. And that we try not to do.

Moving on, if you think antiX and MX are very similar, well you’re right. We make no effort to hide the fact that MX is based on antiX (in our case, a heavily modified antiX-core as a matter of fact). The prime differences are in the desktop environment (xfce vs. the windows managers in antiX), the mx-tools (which isn’t as great a difference as it once was because many of those tools have also come to antiX :happy: ) and the package repositories (mx uses a tremendous amount of packages backported to debian stable and antiX operates a “nosystemd” repo of debian packages redone so they don’t depend on systemd). there are some other choices that affect memory footprint, but those are the big ones.

Incidentally, for those that may come to this thread later, the MX manual is in the menu (as MX-Manual) and does not require an internet connection to view (it’s an on-disk pdf). The installers on antiX and MX are also functionally identical, and once updated isos come out, they will actually be identical (as we just spent a lot of time re-unifying code), and yes, there are further improvements to the efi boots for certain hardware.

[Member sleekmason]

Indeed! Meant to get this up here. Ran into a re-install I had to take care of:)

The 4.17 release is a major release among major releases, with tons of code removed and other new features.

Per Phoronix,

– A huge DRM subsystem update with AMDGPU DC by default for all capable GPUs, Intel Cannonlake graphics are stable, AMD WattMan, Intel HDCP, and more.

– Initial NVIDIA Tegra “Xavier” SoC support for this new high-performance ARM chip with Volta graphics.

– Eight obsolete CPU architectures were removed resulting in a code savings of about a half million lines.

– POWER4 CPU support is being dropped too as part of a separate pull. The POWER4 support was already broken since 2016 with no one apparently noticing until now.

– IBM s390 is still working on its Spectre defense.

– Continued maturing of the RISC-V architecture code.

– A new CPU architecture port for Linux 4.17 is the Andes NDS32 architecture.

– The Linux Kernel Memory Consistency Model has been formalized for Linux 4.17.

– Fixes for the Macintosh PowerBook 100 series.. Yes, with the Motorola processors from the early 90’s.

– The new ACPI TAD driver for some interesting wake-up/alarm functionality as well as other CPUFreq and power management updates.

– PhoenixRC flight controller support.

– Multi-touch support for the Razer Blade Stealth.

– Thunderbolt USB/SL4 security level support.

– USB Type-C support improvements.

– Lost and Found support for F2FS along with performance enhancements and other work.

– EXT4 gets protection for maliciously crafted container images.

– Lazy time support for XFS.

– Btrfs gets a no SSD spread option and other improvements.

– New sound drivers plus USB Audio Class 3.0 support.

– Linux 4.17 staging has shed some weight (lots of lines of code).

– Various other PCI, crypto, and more updates as well as SPARC and BMC updates.
—
The 4.18rc release will have an improvement for the schedutil governor. Looking forward to that when it’s out.

[Member Jesse]

I chose yes “enable realtime process priority” (I have chosen both yes and no on various installations on this same system; bad habit of reinstalling when I bork my system)

Interestingly, I have no trouble running jackd on its own, real-time or otherwise, in antiX, from the a Terminal.

I have also, on previous installations, installed the KXStudio repos and used Cadence without issue. But, the KX repos are a cluster-f**k of PPA’s and such. I would much rather use vanilla antiX/Debian if possible.

rainydayshirts.bandcamp.com | Audio
rainydayshirts.deviantart.com | Visual

[Member seaken64]

When I was setting up this old P-III I found out that I needed to compile a driver for the sound card. AntiX-14 had the necessary libraries and I was able to get it to work. I had tried antiX-16 and the video was messed up. on antiX-13 the video was fine but the sound wouldn’t work. So I landed on antiX-14 and it’s been working good. Now I wish I had not run the dist-upgrade. Oh well, I guess this is part of learning about Linux.

While the system does work, there are some anomalies after doing the dist-upgrade and installing SMTube. Here’s a few things I’ve noticed so far:

The repositories have changed to “stretch”, instead of the previous “Jessie”.

The ROX Terminal will not launch from several of the menu buttons. Other terminal based apps also will not launch from the menu. But I can launch the Root Terminal from the menu and I can launch ROX Term from SpaceFM and the SpaceFM desktop icon.

All of the setup files that are usually launched from the control center fail to load. “Edit Fluxbox Settings”, “Edit jwm Settings”, “Preferred Applications”, “User Desktop-Session”. All of these do not have any associated files for editing.

There appears to be some permissions issue and apparently the dist-upgrade made a few changes to the system and the control center and menus are now not properly linked.

USB automount is not working. The USB drives are recognized after a fresh boot but if all the drives are removed then no USB keys will be recognized when inserted. A reboot is required to get the USB drives back.

Should I re-install using the original version 14 disk? Or can I fix these things by editing some setup files?

Thanks,
Sean

[Member ramchip]

*STOP PRESS* Thanks sleek, but I have discovered that the checksum of the downloaded iso does NOT match the one published on https://antixlinux.com/download/.
The first two bytes of my checksum are “be12” and the website gives “14f3”.
Ok, it’s my fault for not checking earlier!
So, I shall try the whole thing again and see if it the works as expected.
I find it amazing that the system was bootable given that the iso was a bad download.

My apologies for reporting an apparently fictitious fault.
Thanks again to all who contributed in this forum.
Btw, Dave, that quote by the unknown author is very funny!

[Member ramchip]

Yes, fatmac, various programs can be accessed from Menu without any problems.
Although, I’m disappointed with the weird behaviour generally.
Specifically, when I try to shutdown, I click ‘Logout’, then ‘OK’ to confirm logout.
Momentarily, I can see a console screen full of startup information (“Welcome to AntiX”, etc.) and a login prompt, before the login splash screen reappears.
The image displayed is a deserted station platform and a train with unnatural light beams.
Incidentally, this is in monochrome, not the coloured version I recall from the installation screen.
I can repeat this loop and never shutdown or call it a day and hit the power switch.
Apparently, no controlled shutdown is available.
I can’t use the AntiX side of this machine for anything important until this is fixed.

Regarding the viability of the download, I have the DVD here.
It was made on 12th April and contains the file antiX-17.1.386-full.iso.
If there is a method to verify this file is 100% valid, please let me know.
Certainly, the burning software verified it to be a faithful copy.

I think some gremlin is preventing this old (but still useful) system from performing as it should and hopefully it’s a simple fix. Having a few years of experience with Ubuntu I’m fairly confident. Some pointers to help iron out these post-installation problems would be much appreciated.

Surely, the failure of radeon_agp_init is a big clue. Could someone shed light on that, please?

Yes, dolphin_oracle, the rox-icewm is there and when I logged-in I had the colour splash screen!
However, the shutdown failure persists, it’s stuck in a login loop. What next?

[Member stevesr0]

@Bobc,

Thanks for suggestion.

I am a dmesg ignoramus.

I looked thru it just know and nothing obvious jumped out. I need to read up about dmesg messages…

Parenthetically, I looked up my laptop and it apparently is 64-bit capable, so I tried booting the full 64-bit 17.1 version. It booted in ~ 5 minutes, like the 32-bit version and looks the same.

Once up, it seems to run adequately fast from the USB 2.0 connection.

[Member SleepyD]

I setup the system for Testing when I installed it. The system had a bunch of updates when it first booted up. No PPAs. I typed in the command caprea and nothing happened.