Re: startx xauth fails after upgrade to Bullseye 11.3

I seem to have rediscovered Debian bug 889720 xauth crashes when directory name matches host name https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720 (Feb 2018) So, nothing to do with the Bullseye upgrade. I must have created that directory-matching-hostname in the process of setting up for t

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 10:38:10PM +0100, Brian wrote: > On Wed 30 Mar 2022 at 21:50:53 +0200, to...@tuxteam.de wrote: > > > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > > > > > On Wed, Mar 30, 2022 at 05:35:12PM +02

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 05:55:11PM -0400, Michael Stone wrote: > On Wed, Mar 30, 2022 at 10:38:10PM +0100, Brian wrote: > > Perhaps? Perhaps what? Perhaps it is a lie? freedesktop conceals > > the truth and peddles false information purposefully? > > Some people get excessively worked up over thin

Re: startx xauth fails after upgrade to Bullseye 11.3

Larry Doolittle composed on 2022-03-30 19:31 (UTC-0700): > Felix Miata wrote: >> Is the problem avoided if you login via a display manager (gdm, sddm, >> lightdm, >> etc.) instead of using startx? > Beats me. I don't have any software like that installed. You could install one. Try LightDM.

Re: Upgrade from Buster to Bullsye: what to do about source.list for buster-backports

On Wed, Mar 30, 2022 at 19:00 Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 06:53:26PM -0500, Tom Browder wrote: > > I've been following the update guide and only have one apt source.list > left > > to handle: buster-backports: Thanks so much, Greg! -Tom

Re: Does this happen often with sid?

On 3/29/22 3:16 PM, Joe wrote: On Tue, 29 Mar 2022 14:36:55 -0400 Chuck Zmudzinski wrote: I do like synaptic also because it saves a history of all the changes that it makes to the system. The apt tools also do this, but in a more user-hostile way. See /var/log/apt/history.log. This ma

Re: Predictable Network Interface Names

On Wednesday, 30 March 2022 18:31:36 EDT Michael Stone wrote: > On Wed, Mar 30, 2022 at 06:19:17PM -0400, Greg Wooledge wrote: > >It's like you haven't even read this thread. > > of course I have > > >Predictable interface names *do* sometimes change. And when that > >happens, it's a huge deal,

Re: Upgrade from Buster to Bullsye: what to do about source.list for buster-backports

On Wed, Mar 30, 2022 at 06:53:26PM -0500, Tom Browder wrote: > I've been following the update guide and only have one apt source.list left > to handle: buster-backports: > > Do I change it to bullseye-backports or just comment the line out? Comment it out, and only add bullseye-backports (later)

Upgrade from Buster to Bullsye: what to do about source.list for buster-backports

I've been following the update guide and only have one apt source.list left to handle: buster-backports: Do I change it to bullseye-backports or just comment the line out? Thanks. -Tom

Re: startx xauth fails after upgrade to Bullseye 11.3

Felix - Felix Miata wrote: > Is the problem avoided if you login via a display manager (gdm, sddm, lightdm, > etc.) instead of using startx? Beats me. I don't have any software like that installed. Would they run xauth before or after cd'ing to my home directory? - Larry P.S. Sorry about b

Re: Predictable Network Interface Names

> Some people get excessively worked up over things like interface names > and like to throw around strong words for dramatic effect. Just ignore > the noise. I've just come to accept that the actual interface name is going to be some bizarre name. So I look it up, and then promptly rename it

Re: Running Steam Proton Games with primusrun

On Wed, Mar 30, 2022 at 5:41 PM Jonathan Marquardt wrote: > On Tue, Mar 29, 2022 at 01:24:50PM -0500, Paul Johnson wrote: > > I'd recommend using pvkrun instead of primusrun if available. > > Gives me the same error messages :( > > > This looks like you're somehow missing nvidia-glx. > > $ apt s

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022, 5:32 PM Michael Stone wrote: > On Wed, Mar 30, 2022 at 06:19:17PM -0400, Greg Wooledge wrote: > >It's like you haven't even read this thread. > > of course I have > > >Predictable interface names *do* sometimes change. And when that happens, > >it's a huge deal, because all

Re: Running Steam Proton Games with primusrun

On Sun, Mar 27, 2022 at 12:34:07PM -, Curt wrote: > TL;DR (everything) but this bug? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876033 I am not sure. None of the solutions described there worked for me. There isn't even a libgl1-nvidia-glx package for bullseye.

Re: Running Steam Proton Games with primusrun

On Tue, Mar 29, 2022 at 01:24:50PM -0500, Paul Johnson wrote: > I'd recommend using pvkrun instead of primusrun if available. Gives me the same error messages :( > This looks like you're somehow missing nvidia-glx. $ apt search nvidia-glx Sorting... Done Full Text Search... Done libegl-nvidia0/

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 06:19:17PM -0400, Greg Wooledge wrote: It's like you haven't even read this thread. of course I have Predictable interface names *do* sometimes change. And when that happens, it's a huge deal, because all of the configuration files are set up for the old name. Things

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 05:55:11PM -0400, Michael Stone wrote: > For most consumer sytems the interface name matters not one bit, because > it's auto-discovered on install, will never change, and there's little > likelihood that another interface will be added. It's like you haven't even read this

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 10:38:10PM +0100, Brian wrote: Perhaps? Perhaps what? Perhaps it is a lie? freedesktop conceals the truth and peddles false information purposefully? Some people get excessively worked up over things like interface names and like to throw around strong words for dramati

Re: Predictable Network Interface Names

On Wed 30 Mar 2022 at 21:50:53 +0200, to...@tuxteam.de wrote: > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > > > On Wed, Mar 30, 2022 at 05:35:12PM +0200, basti wrote: > > > > as I can read here [1] network names shoul

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 04:00:42PM -0500, Nicholas Geovanis wrote: > Does anyone here know how the BSD-derived "free" unices handle this > situation? I haven't used OpenBSD in several years, but the last time I used it, it went something like this: The OpenBSD kernel has drivers for lots of diffe

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022, 2:15 PM Brian wrote: > On Wed 30 Mar 2022 at 14:39:33 -0400, Greg Wooledge wrote: > > > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > > Yes. You've now seen direct evidence of the lie. I guess

Re: startx xauth fails after upgrade to Bullseye 11.3

Larry Doolittle composed on 2022-03-30 08:57 (UTC-0700): > The xauth segfault is definitely real and > a problem for me. Is the problem avoided if you login via a display manager (gdm, sddm, lightdm, etc.) instead of using startx? -- Evolution as taught in public schools is, like religion,

Potential DNS leak with Wireguard + iwd + resolvconf

Hi, My wireless interface is controlled via iwd (EnableNetworkConfiguration=true, NameResolvingService=resolvconf), and I have a wireguard VPN used to remotely access my private network, managed via e/n/i / ifupdown (using wg-quick). In /etc/wireguard/wg0.conf, I have a "DNS=xxx.xxx.xxx.xxx" line,

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > On Wed, Mar 30, 2022 at 05:35:12PM +0200, basti wrote: > > > as I can read here [1] network names should be stable. > > > (Stable interface names even when hardware is added or

Re: Predictable Network Interface Names

Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > That's good advice, but are MAC addresses memorable? > > Doesn't matter. You can choose a memorable name. The MAC address is > simply the data point you place in the config file, so the system knows > this is the

Re: Predictable Network Interface Names

Le 30/03/2022 à 21:15, Brian a écrit : = which goes into some detail. Thanks. Very informative. As the second link says: The resulting reality is that your PCI based names are only stable if you change no hardware in the s

Re: Predictable Network Interface Names

On Wed 30 Mar 2022 at 14:39:33 -0400, Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > Yes. You've now seen direct evidence of the lie. I guess I won't need > > > to post links to the wiki articles

Re: Predictable Network Interface Names

Le 30/03/2022 à 20:39, Greg Wooledge a écrit : Doesn't matter. You can choose a memorable name. The MAC address is simply the data point you place in the config file, so the system knows this is the interface you're talking about. unicorn:~$ cat /etc/systemd/network/10-lan0.link [Match] MACAd

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > Yes. You've now seen direct evidence of the lie. I guess I won't need > > to post links to the wiki articles that say the same thing you've already > > observed. > > I would be

Surgical instruments supply

We are manufacturer all kinds dental surgical and beauty instruments then supply to the others countries if you are interested in our instruments please contact with us we can provide you our best quality with good price

Re: Predictable Network Interface Names

On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 05:35:12PM +0200, basti wrote: > > as I can read here [1] network names should be stable. > > (Stable interface names even when hardware is added or removed) > > > [1] > > https://www.freedesktop.org/wiki/Softwa

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 05:35:12PM +0200, basti wrote: > as I can read here [1] network names should be stable. > (Stable interface names even when hardware is added or removed) > [1] > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Sorry, but you've been lie

Predictable Network Interface Names

Hello, as I can read here [1] network names should be stable. (Stable interface names even when hardware is added or removed) First of all I have multiple PCIe NIC in a server. What I see now is: When I add or remove a PCIe card (USB card) the name is changed from enp5s3 to enp6s3 and back

Re: startx xauth fails after upgrade to Bullseye 11.3

Esteemed Debian experts and maintainers - On Sun, Mar 27, 2022 at 11:26:37PM -0700, Larry Doolittle wrote: > On Sun, Mar 27, 2022 at 10:45:03PM -0700, Larry Doolittle wrote: > > I just upgraded my first machine from 11.2 to 11.3. > > xauth fails in the context of startx. > Workaround: create an em

Re: installing on Lenovo Ideapad 3

>> Unfortunately now the install doesn't detect an Ethernet card and gives >> me a long list of driver choices and I will have to figure out which one >> this laptop needs. > > Maybe a binary module is missing? Did you try an "unofficial" image with > non-free components? +1; Months ago, the in

Re: Debian 11.3 kernel panics on Epyc 7281 CPU

> Our servers were running Debian 10 without any issues > We have been trying to do a fresh install of debian 11.3 on exactly the > same hardware. The install works without any errors but on rebooting the > system fails with kernel panics > > By adding init=/bin/bash from within grub works and we

Re: mngtmpaddr IP

It's already disabled for all and eth0 as well. On Tue, Mar 29, 2022 at 12:53 PM Jevin Gala wrote: > Hi, > > I am un-able to find how to disable mngtmpaddr IPv6 IP in Debian 11 in a > KVM VPS. > > /proc/sys/net/ipv6/conf/default/use_tempaddr file shows 0 but it's still > assigning mngtmpaddr IP

Re: installing on Lenovo Ideapad 3 now working

On Wed, Mar 30, 2022 at 11:56:55AM +0200, Thomas Schmitt wrote: [...] > For those who do not trust themselves to choose the right /dev/sdX > i have prepared a script which asks for plugging in the USB stick > and then uses the newly appeared device file in the output of lsblk. > > https://wiki

Re: installing on Lenovo Ideapad 3 now working

Hi, Andrew M.A. Cater wrote: > > dd if=[iso] of=/dev/sdX bs=4M oflag=sync status=progress to...@tuxteam.de wrote: > Yes, thereabouts. [...] For those who do not trust themselves to choose the right /dev/sdX i have prepared a script which asks for plugging in the USB stick and then uses the newly

Re: installing on Lenovo Ideapad 3 now working

On Wed, Mar 30, 2022 at 08:43:06AM +, Andrew M.A. Cater wrote: [...] > So, something close to: > > Where sdX is the drive your USB shows up as when you do a dmesg > > dd if=[iso] of=/dev/sdX bs=4M oflag=sync status=progress Yes, thereabouts. The difference with my proposal is you are usin

Re: installing on Lenovo Ideapad 3 now working

On Wed, Mar 30, 2022 at 07:14:39AM +0200, to...@tuxteam.de wrote: > On Tue, Mar 29, 2022 at 08:31:38PM +0100, Brian wrote: > > On Tue 29 Mar 2022 at 20:57:48 +0200, to...@tuxteam.de wrote: > > [...] > > > > One of the caveats with dd (or cat, or...) is that you might > > > be tempted to pull the

Re: Out of memory killer misconfigured?

On Tue, 2022-03-29 at 19:39 +0100, piorunz wrote: > On 29/03/2022 10:56, Sven Hoexter wrote: > > > The in kernel oom killing is a constant issue. If you look through the > > lwn.net articles of the past years there is work done to improve the > > situation, but I believe that's not in a default se