Re: recent Trixie upgrade removed nfs client
On 2024-04-30 10:58, Brad Rogers wrote: On Tue, 30 Apr 2024 09:51:01 -0400 Gary Dale wrote: Hello Gary, Not looking for a solution. Just reporting a spate of oddities I've encountered lately. As Erwan says, this is 'normal'. Especially ATM due to the t64 transition. As you've found out, paying attention to removals is a Good Idea(tm). Sometimes those removals cannot be avoided. Of course, removal of 'library' to be replaced with 'libraryt64' is absolutely fine. If the upgrade wants to remove (say) half of the base packages of KDE, waiting a few days would be prudent. :-D You may also notice quite a few packages being reported as "local or obsolete". This is expected as certain packages have had to be removed from testing to enable a smoother flow of the transition. Many will return in due course. I do know of one exception, however; deborphan has bee removed from testing and, as things stand, it looks like it might be permanent - I fully understand why, but I shall mourn its passing, as I find it to be quite handy for weeding out cruft. Yes but: both gdb and nfs-client installed fine. Moreover, the nfs-client doesn't appear to be a dependency of any of the massive load of files updated lately. The gdb package however is but for some reason apt didn't want to install it. The point is that apt didn't handle the situation reasonably. If it wanted a package that was installable, should it not have installed it? And while nfs-client isn't a dependency of other installed packages, why should autoremove remove it? It's status of not being a dependency didn't change. There are lots of packages that aren't depended on by other packages that I have installed (e.g. every end-user application). Shouldn't autoremove only offer to remove packages that used to be a dependency but aren't currently (i.e. their status has changed)?
Re: strange colors during boot
i'll have to see if i can borrow a vga monitor On Tue, 30 Apr 2024, Marco Moock wrote: > Am 30.04.2024 um 18:33:24 Uhr schrieb fxkl4...@protonmail.com: > >> i use a vga to hdmi converter > > Test it without it. > > -- > Gruß > Marco > > Send unsolicited bulk mail to 1714494804mu...@cartoonies.org >
Re: strange colors during boot
Am 30.04.2024 um 18:33:24 Uhr schrieb fxkl4...@protonmail.com: > i use a vga to hdmi converter Test it without it. -- Gruß Marco Send unsolicited bulk mail to 1714494804mu...@cartoonies.org
strange colors during boot
i set up bullseye on an old machine that has builtin vga display i use a vga to hdmi converter i don't know if that is relevant during boot everything works ok i see the grub screen and then initial ramdisk they are black background and white foreground it is, i think, when it finishes the initial ramdisk that the color changes the foreground color stays white but the background changes it changes to different colors each time i boot, green, purple, pink, ... some combination are impossible to read where should i look for the culprit
Re: large complaint / very urgent
On 29/04/2024 08:13, to...@tuxteam.de wrote: But in the wrong direction, in many ways. Please forward this mail to the Debian department; Update and Upgrade There is no "Debian department" -- this is a volunteer project. Help out! Please do not feed the troll. His place is in ignore filter. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: recent Trixie upgrade removed nfs client
Gary Dale wrote: > I'm running Trixie on an AMD64 system. > > Yesterday after doing my usual morning full-upgrade, I rebooted because > there were a lot of Plasma-related updates. When I logged in, I found I > wasn't connected to my file server shares. I eventually traced this down > to a lack of nfs software on my workstation. Reinstalling nfs-client > fixed this. > > I guess I need to pay closer attention to what autoremove tells me it's > going to remove, but I'm confused as to why it would remove nfs-client & > related packages. > > This follows a couple of previous full-upgrades that were having > problems. The first, a few days ago, was stopped by gdb not being > available. However, it installed fine manually (apt install gdb). I > don't see why apt full-upgrade didn't do this automatically as a > dependency for whatever package needed it. > > The second was blocked by the lack of a lcl-qt5 or lcl-gtk5 library. I > can see this as legitimate because it looks like you don't need both so > the package manager lets you decide which you want. > > Not looking for a solution. Just reporting a spate of oddities I've > encountered lately. the on-going time_t transitions may be causing some packages to be removed for a while as dependencies get adjusted. i've currently not been doing full upgrades because there are many Mate packages that would be removed. songbird
Re: Debian does not load zfs automatically at boot and strange messages displayed on the screen...
Am 30.04.2024 um 16:48 schrieb Mario Marietto: > Probably this is not the proper method to do it ? Done it in vm's and on bare metal many times. Never ran into your kind of problems. :-( Here is the guide, i suggest: https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/index.html#installation
Re: recent Trixie upgrade removed nfs client
On Tue, 30 Apr 2024 09:51:01 -0400
Gary Dale wrote:
Hello Gary,
>Not looking for a solution. Just reporting a spate of oddities I've
>encountered lately.
As Erwan says, this is 'normal'. Especially ATM due to the t64
transition.
As you've found out, paying attention to removals is a Good Idea(tm).
Sometimes those removals cannot be avoided. Of course, removal of
'library' to be replaced with 'libraryt64' is absolutely fine.
If the upgrade wants to remove (say) half of the base packages of KDE,
waiting a few days would be prudent. :-D
You may also notice quite a few packages being reported as "local or
obsolete". This is expected as certain packages have had to be removed
from testing to enable a smoother flow of the transition. Many will
return in due course. I do know of one exception, however; deborphan
has bee removed from testing and, as things stand, it looks like it
might be permanent - I fully understand why, but I shall mourn its
passing, as I find it to be quite handy for weeding out cruft.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
He looked the wrong way at a policeman
I Predict A Riot - Kaiser Chiefs
pgpNgF_iNx5wu.pgp
Description: OpenPGP digital signature
Debian does not load zfs automatically at boot and strange messages displayed on the screen...
Hello to everyone. I've just installed Debian 12 (netinstall version with ssh server + web server) as guest os on top of Windows 11 using qemu + whpx. These are the parameters that I've used : I:\OS\vms\qemu\qemu-system-x86_64.exe -machine q35 -accel whpx -cpu kvm64,hv_relaxed,hv_time,hv_synic -m 8G -vga std -audiodev dsound,id=snd0 -device ich9-intel-hda -device hda-duplex,audiodev=snd0 -hda "I:\Backup\Linux\Debian.img" -drive file=\\.\PhysicalDrive5 -drive file=\\.\PhysicalDrive6 -drive file=\\.\PhysicalDrive8 -rtc base=localtime -device usb-ehci,id=usb,bus=pcie.0,addr=0x3 -device usb-tablet -device usb-kbd -smbios type=2 -nodefaults -netdev user,id=net0 -device e1000,netdev=net0,id=net0,mac=52:54:00:11:22:33 -device ich9-ahci,id=sata -bios "I:\OS\vms\qemu\OVMF_combined.fd" Actually it has two problems : 1) I've added the module zfs to /etc/modules because I want to autoload zfs as soon as Debian makes the booting,but it does not work. Probably this is not the proper method to do it ? 2) As you can see on the attached picture,I see a lot of strange messages on the screen ; I don't understand why they happen,but I would like to suppress them. [image: 2024-04-30 16 42 44.png] -- Mario.
Re: recent Trixie upgrade removed nfs client
On Tue, Apr 30, 2024 at 03:51:01PM CEST, Gary Dale said: > I'm running Trixie on an AMD64 system. > > Yesterday after doing my usual morning full-upgrade, I rebooted because > there were a lot of Plasma-related updates. When I logged in, I found I > wasn't connected to my file server shares. I eventually traced this down to > a lack of nfs software on my workstation. Reinstalling nfs-client fixed > this. > > I guess I need to pay closer attention to what autoremove tells me it's > going to remove, but I'm confused as to why it would remove nfs-client & > related packages. > > This follows a couple of previous full-upgrades that were having problems. > The first, a few days ago, was stopped by gdb not being available. However, > it installed fine manually (apt install gdb). I don't see why apt > full-upgrade didn't do this automatically as a dependency for whatever > package needed it. > > The second was blocked by the lack of a lcl-qt5 or lcl-gtk5 library. I can > see this as legitimate because it looks like you don't need both so the > package manager lets you decide which you want. > > Not looking for a solution. Just reporting a spate of oddities I've > encountered lately. > Trixie is undergoing major transitions. You must be careful and check what each upgrade will want to uninstall, but it is normal for a "testing" distribution. In those cases I use the curses interface of aptitude to check which upgrade will remove another package that I want, and limit my upgrades to the one that do not break my system. Usually some days later it is Ok (sometimes week for major transitions) -- Erwan
recent Trixie upgrade removed nfs client
I'm running Trixie on an AMD64 system. Yesterday after doing my usual morning full-upgrade, I rebooted because there were a lot of Plasma-related updates. When I logged in, I found I wasn't connected to my file server shares. I eventually traced this down to a lack of nfs software on my workstation. Reinstalling nfs-client fixed this. I guess I need to pay closer attention to what autoremove tells me it's going to remove, but I'm confused as to why it would remove nfs-client & related packages. This follows a couple of previous full-upgrades that were having problems. The first, a few days ago, was stopped by gdb not being available. However, it installed fine manually (apt install gdb). I don't see why apt full-upgrade didn't do this automatically as a dependency for whatever package needed it. The second was blocked by the lack of a lcl-qt5 or lcl-gtk5 library. I can see this as legitimate because it looks like you don't need both so the package manager lets you decide which you want. Not looking for a solution. Just reporting a spate of oddities I've encountered lately.
Re: speaker-test: no correct sound output on LFE and others speakers
Hi, > Basically I've the same issue described here: > https://askubuntu.com/questions/1180389/speaker-test-returns-all-6-channels-to-front-speakers > > The speaker-test program is provided by the alsa-utils package. I'm using > Debian 12 Bookworm, I've no ~/.asoundrc file. My /proc/asound/cards returns: > > ~$ cat /proc/asound/cards > 0 [SB ]: HDA-Intel - HDA ATI SB > HDA ATI SB at 0xfe40 irq 16 > 1 [NVidia ]: HDA-Intel - HDA NVidia > HDA NVidia at 0xfe08 irq 57 > > I've 5.1 speakers the LOGITECH Z906 audio system plugged to the PC via 3 > jacks (left/right), (Center/Subwoofer), (Rear left/ Rear right). I assume your cabling is right and your SB soundcard has surround out (3 jacks as you describe it, and not mic and line out for instance). The labels on the jacks would confirm that, so would the user manual of your motherboard or sound card. > The issue is that speaker-test doesn't play sound to the correct speaker. If > I run: > > ~$ speaker-test -Dplug:surround51 -c6 -s3 -f75 > > The sound comes from (Center), (Front right), (Rear left) and (Rear right) > speakers instead (Front right) only. What's bothering me is that you get sound from multiple speakers while instructing out on only one. The usual issues of these setups with surround analog out are: - channel mapping issues (driver/hardware mismatch) - software downmixing to stereo There are other usual issues with surrount digital out but this is not your setup. You can have a look at [1] for software fixes on this. [1] https://alsa.opensrc.org/SurroundSound Thanks, Alex
