You are not logged in.
- Topics: Active | Unanswered
#226 Re: Freedom Hacks » Replacing sudo. » 2022-09-04 12:45:33
Hm, how would the following look in doas style?
(Capt. Obviuos does not want to compile as root)
$ ./configure
$ make
$ sudo make install#227 Re: Other Issues » [SOLVED] apt pinning 1001 / automatic package version downgrade » 2022-08-31 22:22:32
That's better- thanks a lot!
Good to know, that apt is still working as expected.
Quite sure I have had some trys using a=oldstable, but there must be another error incorporated.
$ apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
1001 http://ftp.de.debian.org/debian buster/contrib amd64 Packages
release v=10.12,o=Debian,a=oldstable,n=buster,l=Debian,c=contrib,b=amd64
origin ftp.de.debian.org
1001 http://ftp.de.debian.org/debian buster/non-free amd64 Packages
release v=10.12,o=Debian,a=oldstable,n=buster,l=Debian,c=non-free,b=amd64
origin ftp.de.debian.org
1001 http://ftp.de.debian.org/debian buster/main amd64 Packages
release v=10.12,o=Debian,a=oldstable,n=buster,l=Debian,c=main,b=amd64
origin ftp.de.debian.org
Pinned packages:#228 Re: Other Issues » [SOLVED] apt pinning 1001 / automatic package version downgrade » 2022-08-31 20:40:05
This is from debian bullseye, backdate target is buster. The chimaera image showed a comparable behaviour.
Thanks for looking!
$ cat /etc/apt/preferences{,.d/*}
Package: *
Pin: release a=buster
Pin-Priority: 1001
cat: '/etc/apt/preferences.d/*': No such file or directory
$ apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://ftp.de.debian.org/debian buster/contrib amd64 Packages
release v=10.12,o=Debian,a=oldstable,n=buster,l=Debian,c=contrib,b=amd64
origin ftp.de.debian.org
500 http://ftp.de.debian.org/debian buster/non-free amd64 Packages
release v=10.12,o=Debian,a=oldstable,n=buster,l=Debian,c=non-free,b=amd64
origin ftp.de.debian.org
500 http://ftp.de.debian.org/debian buster/main amd64 Packages
release v=10.12,o=Debian,a=oldstable,n=buster,l=Debian,c=main,b=amd64
origin ftp.de.debian.org
Pinned packages:
# some details and commands:
$ cat /etc/debian_version
11.4
$ cat sources.list
deb http://ftp.de.debian.org/debian/ buster main non-free contrib
$ apt update
Hit:1 http://ftp.de.debian.org/debian buster InRelease
All packages are up to date.
$ apt upgrade
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ apt list -a | grep linux-image-amd64/
linux-image-amd64/now 5.10.136-1 amd64 [installed,local]
linux-image-amd64/oldstable 4.19+105+deb10u15 amd64
$ apt install linux-image-amd64
linux-image-amd64 is already the newest version (5.10.136-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# downgrade single package:
$ apt -s install linux-image-amd64=4.19+105+deb10u15
0 upgraded, 1 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Inst linux-image-4.19.0-20-amd64 (4.19.235-1 Debian:10.12/oldstable [amd64])
Inst linux-image-amd64 [5.10.136-1] (4.19+105+deb10u15 Debian:10.12/oldstable [amd64])#229 Other Issues » [SOLVED] apt pinning 1001 / automatic package version downgrade » 2022-08-31 15:51:44
- delgado
- Replies: 5
Hi,
About ~18 month ago it was still possible to downgrade package versions by setting the releases pin priority to 1001. Applied with apt update - nice and easy.
Now, apt happly tells you, that the newest version of the package is installed. Have a cookie!
Is it possible to restore the previous behavoir?
Supplemental (not really part of the question, just how it happened)
The pin priority in /etc/apt/preferences is not applied directly. Checking with apt-cache policy, resulted in a values of "990 : 500 : 100" instead of "1001 : -1 : -10". Remarkable may be: Pin priority 1001 for 'force downgrade' is gone.
What's the purpose?
Distro downgrade (to try lcarsde). Sounds complicated, but it wasn't. The process was straight forward. At the time I moved a box from testing (bullseye) back to stable (buster):
Adjust /etc/apt/sources.list, pin the release to 1001 in /etc/apt/preferences, apt update; apt upgrade; apt dist-upgrade; reboot with the "new" 4.19 kernel.
That really impressed me! (later the box became bullseye again and is now chimaera)
Yesterday I tried the same with chimaere to beowulf and bullseye to buster. Countless variants of pinning and sources.list - nope.
#230 Re: Hardware & System Configuration » (T420, chimaera)(nvidia-legacy-390xx-driver) nvidia-persistenced error » 2022-08-30 13:23:51
Use option '--no-install-recommends' when you install the nvidia driver. This will prevent nvidia-persistenced from being installed
Now I'm feeling foolish - all the time wasted in the last two months on a pointless package.
Edit: There might be a take away for the OP:
If it's not working, just uninstall the whole nvidia-* to use the open souce driver nouveau. It's not worth the effort.
#231 Re: Hardware & System Configuration » (T420, chimaera)(nvidia-legacy-390xx-driver) nvidia-persistenced error » 2022-08-29 18:06:38
if you are lucky, it is just the package status:
/etc/init.d/nvidia-persistenced stop
apt-get upgrade
#232 Re: Other Issues » move Devuan to a bigger partition » 2022-08-29 14:03:55
Hi,
depending on the partition sizes, it could be an option to mount sda3 on "/home". Minimal effort and recommended anyway.
#233 Re: Other Issues » [SOLVED] How to Navigate Back to a Previous XFCE Session? » 2022-08-26 17:23:17
@alexkemp
The vt's have nothing to do with X, they are steady. The underlying process is a getty.
e.g. you can switch from X to vt3 with Alt-Ctrl-F3, but from a vt to vt3 with Alt-F3 (with or without Ctrl).
Another point of view is to see a vt as text console and a X as graphical console.
$ ps ax | grep getty
1781 tty1 Ss+ 0:00 /sbin/getty --noclear 38400 tty1
1782 tty2 Ss+ 0:00 /sbin/getty 38400 tty2
(...)
1786 tty6 Ss+ 0:00 /sbin/getty 38400 tty6"I also still do not know which program is supplying the Alt-F7 command."
Good question - never crossed my mind - vt's were present as far as I can think.
#234 Re: Installation » [SOLVED] Pi-Hole and Devuan Chimaera » 2022-08-20 07:41:14
root@chimaera:~# cat /etc/pihole/setupVars.conf PIHOLE_DNS_1=127.0.0.1#5335
I have the same line for PIHOLE_DNS_1. There is an unbound running on my machine, configured for port 5335 to resolve DNS (setup as described in https://forum.kuketz-blog.de/viewtopic.php?f=42&t=3067 (german)).
Did you try a "common" DNS server, like rbit suggested?
Or what is your local DNS resolver on port 5335 and is it working?
#235 Re: Installation » [SOLVED] Pi-Hole and Devuan Chimaera » 2022-08-19 19:57:14
Has anyone here at Dev1 installed/run Pi-Hole?
I'm running a pi-hole on chimaera, installed before migration.
(beside the adaption of the changed network device name) no further issues so far, but I'm not frequently updating.
#236 Re: Hardware & System Configuration » Persistently broken package » 2022-08-09 18:26:50
Seems too late to edit the previous post. The essence is:
To fix package nvidia-persistenced for apt do:
/etc/init.d/nvidia-persistenced stop && apt-get upgrade
#237 Re: Installation » Revised migration page on www » 2022-08-08 18:31:31
EDIT / mostly deleted.
Network setup for migration seems to rely on network-manager and NOT dhcp, to circumvent the device name change to eth0.
10 minutes later ... But that is not true for rrq's migration script.
Now I'm confused. I'll go for migration in chroot and look for the network afterwards.
#238 Re: Other Issues » Scribus - Daedalus » 2022-08-06 19:13:28
Hi,
Scribus from chimaera should work on daedalus too.
It should not hurt to have chimaera in source.list addionally. Someone disagrees? Any package will be superseeded by an existing daedalus package.
#239 Re: Installation » [SOLVED] Power button » 2022-08-05 12:25:51
Then acpid it is.
Thanks for clarifying the matter.
EDIT: It's working - solved.
#240 Installation » [SOLVED] Power button » 2022-08-04 20:16:40
- delgado
- Replies: 2
Hello,
after migration from bullseye to chimaera the power button stoped working - in terms of 'does not initiate system shut down'.
The usual suspect would be a *smart* deskop power manger, but there is no X. It is a headless mini-server on older Fujitsu hardware (consisting of AMD notebook components, fanless).
What can it be? A missing or unconfigured package through the update, acpi stuff, ...
Thanks in advance and regards.
#241 Re: Installation » Bullseye migration story » 2022-08-04 06:54:18
Well, hell is on fire, I started having DNS problems and therefore can't do any actions with apt.
Your network device name has changed with the migration. In my case ist was form enp1s0 in bullseye to eth0 in chimaera.
Did you look at ' /etc/network/interfaces' ? Or you may find affected files with, e.g.:
grep -r enp1s /etc/*EDIT: Of course, sometimes it's better to just start fresh.
#242 Re: Other Issues » gkrellm skin 'BadPixmap (invalid Pixmap parameter)' » 2022-07-26 20:27:26
Could you please post what pkgs you have installed for gkrellm including plug-ins?
$ dpkg -l | grep gkr | cut -c 5-21,44-55
gkrellkam 2.0.0-2
gkrellm 2.3.11-2
gkrellm-bfm 0.6.4-6.1
gkrellm-cpufreq 0.6.4-6.1
gkrellm-hdplop 0.9.11-3
gkrellm-reminder 2.0.0-3.1
gkrellm-tz 0.8-2+b1
gkrellmoon 0.6-7
gkrellshoot 0.4.4-3
gkrelltop 2.2.13-1.1
$ cat .gkrellm2/plugin_enable
gkrellmoon.sogkrellm looks comparabele to your screenshot. Pressing shift-pgup/down does no harm, as fsmithred reported.
Disabled are email and non-existing sensors. "Krell and LED updates per second" is set to 1. Program start-up took 2-4 seconds.
Maybe something in 'user-config'? - It has 144 lines, so just 22 for now.
Anything else that might help debugging?
$ head -22 .gkrellm2/user-config
### GKrellM user config. Auto written, do not edit (usually) ###
### Version 2.3.11 ###
enable_hostname 1
hostname_short 0
enable_sysname 0
mbmon_port 0
sticky_state 0
dock_type 0
decorated 0
skip_taskbar 0
skip_pager 0
above 0
below 0
track_gtk_theme_name 0
default_track_theme "Default"
save_position 0
chart_width 125
update_HZ 1
allow_multiple_instances 0
float_factor 1000
hostname sysname_mode 1
clock_cal clock_launch#243 Re: Other Issues » gkrellm skin 'BadPixmap (invalid Pixmap parameter)' » 2022-07-23 21:51:12
No error on my daedalus box. Maybe the package works for chimaera too?
Nice transparent theme.
#244 Re: Freedom Hacks » To permanently block installation of Pulseaudio. » 2022-07-19 19:33:46
Thanks Head_on_a_Stick!
#245 Re: Freedom Hacks » To permanently block installation of Pulseaudio. » 2022-07-17 18:31:50
I have multiarch enabled and apt wants to install pulsaudio:i386.
$ sudo apt-get -s install pulseaudio
(...)
Note, selecting 'pulseaudio:i386' instead of 'pulseaudio'
The following additional packages will be installed:
libaudit1:i386 (...) pulseaudio-utils:i386 rtkit:i386Is there a variant for multiarch?
#246 Re: Hardware & System Configuration » Persistently broken package » 2022-07-14 18:40:46
Hello,
it is a daedalus installation with the 470-nvidia-driver (470.129.06-6).
The driver finally seems to work, but the "nvidia-persistanced" error remained.
---------
edit / update: replicated installation, error and fix
Problem: apt does not 'fully install' nvidia-persistanced.
But: It will succeed, if nvidia-persistanced is not running.
$ /etc/init.d/nvidia-persistenced stop
$ apt-get upgrade And apt should be happy again.
---------
I leave the original post below, since it was posted and happend so on my box.
By now, I think I must have stoped the daemaon sometimes and forget about it.
end edit / update
----------
The following solved it in my case:
$ sudo rm /var/run/nvidia-persistenced/nvidia-persistenced.pid
$ sudo rm /var/run/nvidia-persistenced/socket
fixed it and
$ sudo apt-get upgradethen succeeded in finalising the post-install-script and starting nvidia-persistanced.
Done. 
Some remarks:
Probably, it is a good idea to gzip or move both files instead of deleting them.
It took some time to notice that it is just a daemon, that did not start.
$ /etc/init.d/nvidia-persistanced startgave an error message respective a pid-file. Messing around with it may or may not result in other hints, if the above does not work.
apt insists to start the daemon by itself, so if you managed to start the daemon, you have to stop it before doing "apt-get upgrade".
Hope this is helpful.
Regards
Board footer
