PCSX2 GPU hang

[Matthew McAllister]

Hi folks,

I've discovered that PCSX2 causes an Intel GPU hang on bullseye. The 
whole display manager has to be restarted after the crash.


I'm not sure if this occurs in bookworm. I would report the bug 
directly, but I don't know which maintainer would be the best to take a 
look at it. My guess is the package libgl1-mesa-dri:i386 is the culprit, 
but who knows.


If anyone can suggest who would be best to send this report to, I would 
appreciate it.


dmesg:
[147858.036318] i915 :00:02.0: [drm] Resetting rcs0 for preemption 
time out
[147858.036349] i915 :00:02.0: [drm] MTGS[102288] context reset due 
to GPU hang
[147858.048564] i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85df9e9d, 
in MTGS [102288]


glxinfo:
Vendor: Intel (0x8086)
Device: Mesa Intel(R) HD Graphics 620 (KBL GT2) (0x5916)
Version: 20.3.5
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2

-- System Information:
Debian Release: 11.1
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.12.0 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Re: SDDM doesn't show up at boot

[Cmdte Alpha Tigre Z]

El lun, 18 oct 2021 a las 12:07, David Wright
() escribió:
>
> On Sun 17 Oct 2021 at 17:12:54 (-0400), Cmdte Alpha Tigre Z wrote:
>
> > I was trying to set up the keyboard for the whole system
> > with "localectl set-x11-keymap pc105 us altgr-intl".  Before
> > that, it did not have the altgr-intl variant.
>
> On account of having run Debian a long time, I set up my keyboard
> using   dpkg-reconfigure keyboard-configuration, so I have no
> experience of running localectl. However, the man page says:
>
>  set-x11-keymap LAYOUT [MODEL [VARIANT [OPTIONS]]]
>  Set the system default keyboard mapping for X11 and the virtual
>  console. This takes a keyboard mapping name (such as "de" or
>  "us"), and possibly a model, variant, and options, see kbd(4) for
>  details. Unless --no-convert is passed, the selected setting is
>  also applied as the system console keyboard mapping, after
>  converting it to the closest matching console keyboard mapping.
>
> So might it be worth trying:
>
>   localectl set-x11-keymap us pc105 altgr-intl

Ups, I made a mistake writing the email, sorry.  I did write the command
right.  Thanks for the correction.

> Could you post the contents of /etc/default/keyboard after
> running each of the commands above. (It seems pointless for me to try
> to see the effects, as I don't use a DE, DM or "greeter".)

Before the command:
## KEYBOARD CONFIGURATION FILE
#
## Consult the keyboard(5) manual page.
#
#XKBMODEL="pc105"
#XKBLAYOUT="us"
#XKBVARIANT=""
#XKBOPTIONS=""
#
#BACKSPACE="guess"
#
(without the first column of #)

After the command:
#XKBMODEL=pc105
#XKBLAYOUT=us
#XKBVARIANT=altgr-intl
#BACKSPACE=guess
#
(without the #)

> Cheers,
> David.

Thanks for your reply.  Have a nice day.
-- 
Time zone: GMT-4

Re: Cannot install vlc on bullseye

[R. Ramesh]

The best expert opinion is fairly well summed up on the Debian wiki at
https://wiki.debian.org/DontBreakDebian  
  . The advice given above is fairly
blunt and matter of fact because the users and developers on this list have
seen this sort of thing lots of times before.

> Regards
> Ramesh
> 


With every good wish, as ever,

Andy Cater



Thanks for everyone's help. I systematically went through every package 
and moved them to debian version if apt allowed me to do so. At the end 
I only have acroread from dmo and everything else is from debian. I 
removed mythtv also to get to this point. Since this is my desktop, I do 
not need to install mythtv and will keep it as close to debian as possible.


I do not have the same freedom for three other (debian based) machines I 
have (2 frontend and one backend) and it is going to be a bit of 
struggle to get it right. However, fixing my desktop helped me to 
understand dependencies better.  So... hopefully, I will find the right 
combo of packages to keep it close enough to debian.


Ramesh

Re: Debian's branches and release model

[harryweaver]

19 Oct 2021, 05:29 by a...@cityscape.co.uk:

> On Mon 18 Oct 2021 at 20:51:04 +0200, harrywea...@tutanota.com wrote:
>
>>
>>
>> 19 Oct 2021, 03:13 by g...@wooledge.org:
>>
>> > On Mon, Oct 18, 2021 at 12:29:55PM -0400, Peter Hoist wrote:
>> >
>> >> I am enjoying Debian's testing branch as a reasonably stable and 
>> >> up-to-date
>> >> 'rolling' release,
>> >>
>> >
>> > It's not.
>> >
>> >> So the question is, why not cut a release branch every two years, and at
>> >> the same time keep the unstable/testing alive?
>> >>
>> >
>> > You misunderstand Debian's release model at a fundamental level.
>> >
>> > The purpose of testing, and even unstable, is not "to give our users a
>> > rolling release".  Your perception of them as such a thing is where the
>> > error lies.
>> >
>> > The purpose of unstable (and more recently, testing) is to prepare for
>> > the release of the next stable version.  Everything about them is geared
>> > toward that goal.
>> >
>> > Packages are uploaded to testing not because they've got that new package
>> > smell, and not because having higher version numbers increases your score.
>> > It's because the developers believe the newer package will add benefit
>> > to the next stable release.
>> >
>> > Let me say this again, to be clear: packages are uploaded to unstable
>> > because that's how they become eligible for the next stable release.
>> >
>> > The unstable and testing branches themselves are just places where you
>> > can go to test the next stable release before it happens, find the bugs,
>> > and report them.
>> >
>> > The "slushy" effect (unstable mostly freezing along with testing) is
>> > simply a side effect of the fact that All Of Debian is preparing for the
>> > next release.  All efforts are on fixing the release-critical bugs in
>> > the packages, so they don't get removed from testing (and therefore from
>> > the next stable release).  Uploading a new package to unstable during
>> > this time would backfire in multiple ways: not only does it take away
>> > developer time that could have been spent fixing the bugs in testing,
>> > but any chance of such a new unstable package migrating into testing
>> > during the freeze would throw everything off.
>> >
>> > If you want your raw-and-bloody new package stream to continue faster,
>> > you can help by reporting bugs, or even by offering fixes if your skill
>> > set allows it.
>> >
>> > Advocating for "hey, let's split the Debian developer community into two
>> > pieces right before a release" is not likely to achieve your goals.
>> >
>> And yet, given all that, I run a small business quite successfully, on
>> Unstable, because it's a darned sight more stable than Windows.
>>
>
> I am not sure that that criterion is sufficient to advocate unstable on
> critical systems. Comparisons with other OSs are always fraught. If it
> works for you, well and good.
>
This is a desktop operating system for a small business.
Any bugs which occur are almost always attended to within 24 hours, which is a 
damned sight faster than they are seen to in Testing.
I would never use Testing on a `critical system'.
If I were to run a server, I should employ Stable.
Testing is a waste of time for anything more than a staged evelopment process, 
which is what it's there for.
>> I can't remember the last time I got a window freeze on Unstable.
>> Testing a package, even before it is released into the Unstable
>> branch, appears to be quite rigorous.
>>
>
> I suspect the maintainer ensures the package meets quality control
> standards for inclusion in Debian. It is then bunged into unstable,
> bugs and all. If you think the maintainer rigorously checks out
> every aspect of the software, well ...
>
>From my experience in running Unstable, since XP came on the scene (when was 
>that, exactly?), that would appear to be the case.
Cheers!

Harry.

Re: SDDM doesn't show up at boot

[Cmdte Alpha Tigre Z]

El lun, 18 oct 2021 a las 5:51, Andrew M.A. Cater
() escribió:
> Hi,
>
> First things first: bring your machine up to date - there is now 10.11.
> [Or update to Debian 11 - but read release notes :) ]

Ok, I'm working on it.

> I think you may have two independent problems here: changing keyboard
> layout shouldn't cause problems with the X server.

I do not think that the problem is with the X server itself, but with SDDM.
See what I wrote here:

El dom, 17 oct 2021 a las 17:12, Cmdte Alpha Tigre Z
() escribió:
> Now, while writing this message, I tried it again and now
> the kernel reports a segmentation fault in "sddm-greeter"
> after it reads "/usr/share/xsessions/lxqt.desktop".  Of course,
> everything fails again leaving me with only the mouse cursor
> and a black screen.

The problem is with the "sddm-greeter".  SDDM itself
(I mean, "/usr/bin/sddm") is still running when this happens,
and I can see and move the cursor around.

> All best, as ever,
>
> Andy Cater

Thanks for your reply, have a nice day.

-- 
Time zone: GMT-4

Re: Recommended KVM box: HDMI (video), USB (mouse+kb+periferal), 4-port

[rhkramer]

On Monday, October 18, 2021 09:03:10 PM Tom Browder wrote:
> I am in the market for a new (or refurbished) KVM with the subject
> attributes.  I only need to support a single monitor, but reliability and
> holding video settings for each computer are important to me.
> 
> Reviews I've found online are terrible, but I would appreciate hearing from
> satisfied Debian KVM users.

I am using a Belkin SOHO 4-Port KVM Switch Box F1DS104J, bought used off ebay 
in January, 2020 for under $20.  Works fine, offhand I don't remember the specs 
-- I basically use 1920x1028 resolution with no recognizable deterioration in 
the video display.  

(Thank goodness I have a wooden desktop so I can knock on wood.  (I did buy 
two, have the 2nd as a spare.)

Recommended KVM box: HDMI (video), USB (mouse+kb+periferal), 4-port

[Tom Browder]

I am in the market for a new (or refurbished) KVM with the subject
attributes.  I only need to support a single monitor, but reliability and
holding video settings for each computer are important to me.

Reviews I've found online are terrible, but I would appreciate hearing from
satisfied Debian KVM users.

Thanks.

-Tom

Re: AMD OpenCL support

[piorunz]

On 18/10/2021 14:06, Linux-Fan wrote:


I use a Radeon Pro W5500.

AMDs website leads me to
https://www.amd.com/de/support/graphics/amd-radeon-6000-series/amd-radeon-6900-series/amd-radeon-rx-6900-xt

for your GPU and proposes to download "Radon(TM) Software for Linux
Driver for Ubuntu 20.04.3" which seems to be a different TGZ than what I
am using (it has 1290604 vs. 1292797).


I already tried that. Please see my post dated 17/10/2021, 22:59. I have
error:
dpkg: error processing package amdgpu-dkms (--configure):
 installed amdgpu-dkms package post-installation script subprocess
returned error exit status 10

I am kinda lost at the moment. :|

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Sata Hard drive testing

[Stefan Monnier]

> Essentially, I have been experienced data loss, where nodes become
> unreadable, when I try to "fix it" with fdisk, it says it moves unreadable
> to the trash, basically deleting data.

"it says"?  Can you clarify what is this "it"?

Drive-level errors of "unreadable data" normally lead to errors that
appear in the kernel log and say scary things and "read sense" and
include hex numbers showing the actual bytes of the SATA command sent.

I don't expect such error messages to say anything about a "trash".
So maybe your errors occur elsewhere.


Stefan

Re: users-admin qui plante sur debian 11

[Th.A.C]

Le 18/10/2021 à 21:38, hamster a écrit :

J'ai installé debian 11 avec le  bureau MATE et j'ai users-admin qui 
plante.


...

>> J'ai donc regardé quelle est la commande lancée par ce bouton, c'est

users-admin. Je l'ai donc lancée dans un terminal, et ca me répond :
(users-admin:38978): Liboobs-WARNING **: 21:26:54.766: There was an 
unknown error communicating with the backends: Failed to execute program 
org.freedesktop.SystemToolsBackends: Permission denied


La, je bloque. Mes recherches sur le web n'ont rien donné, donc si 
quelqu'un y voit un peu plus clair que moi je suis preneur.



tu as fais des recherches avec juste:
Failed to execute program org.freedesktop.SystemToolsBackends: 
Permission denied


on trouve plein de trucs qui tournent autour d'un problème de droits sur 
un executable.


Ce droit pouvant être lié à un problème de mauvais groupe comme ici:
https://forums.gentoo.org/viewtopic-t-1007656-start-0.html



et sinon, là ca ressemble bien à ton problème:
https://vk.com/@linux_windows_net-linux-mint-oshibka

voir surtout les 2 encadrés avec des commandes shell

Re: users-admin qui plante sur debian 11

[Bernard Schoenacker]

- Mail original -
> De: "hamster" 
> À: "ML Debian User French" 
> Envoyé: Lundi 18 Octobre 2021 21:38:44
> Objet: users-admin qui plante sur debian 11
> 
> Salut.
> 
> J'ai installé debian 11 avec le  bureau MATE et j'ai users-admin qui
> plante.
> 
> Quand je vais dans systeme --> administration --> utilisateurs et
> groupes ca m'ouvre une fenetre qui dit "la configuration n'a pas pu
> etre
> chargée, une erreur imprévue est survenue".
> 
> J'ai donc regardé quelle est la commande lancée par ce bouton, c'est
> users-admin. Je l'ai donc lancée dans un terminal, et ca me répond :
> (users-admin:38978): Liboobs-WARNING **: 21:26:54.766: There was an
> unknown error communicating with the backends: Failed to execute
> program
> org.freedesktop.SystemToolsBackends: Permission denied
> 
> La, je bloque. Mes recherches sur le web n'ont rien donné, donc si
> quelqu'un y voit un peu plus clair que moi je suis preneur.
> 
> Merci d'avance.
> 

Bonjour,

Serait-il possible de lancer l'application via le terminal en utilisant 
sudo ?

Merci

@+

Bernard

Re: Where is a list of kernel messages ?

[Andrew M.A. Cater]

On Tue, Oct 19, 2021 at 10:16:24AM +1300, C.T.F. Jansen wrote:
> Greetings,
> 
> Where is there a list of linux kernel messages ?
> So far not found on :
> 
>  - google
>  - Debian linux or kernel documentation, specifically linux-doc etc.
>  - not seem in /usr/share/doc
> 
>  - www.kernel.org
> 
> If they are there then it's time for the discovery process to be shortened.
> 
> Two messages that I'm interested in are :
> 
>kernel: [ 6997.564065] sd 3:0:0:0: [sdc] tag#3 data cmplt err -71 uas-tag
> 4 inflight: CMD
> 
>kernel: [ 6997.564108] usb 2-1.4: stat urb: status -71
> 
> The machine currently has  Debian 9 and a new disk dock and new internal
> hard disk set to go in the disk dock.
> The messages may be a result of the OS being too back level for the newer
> hardware. A Debian 11 implementation is in process.
> 
> Thanks.
> 
> frank.jan...@actrix.gen.nz, ZL2TTS
> 

Looking at it: it looks more like a USB speed mismatch or something like
that - is it a USB 3 dock plugged into a USB 2 port?

That from the first message.

Is the second message copied directly or retyped - should stat urb read stat
usb ?

All best,

Andy Cater

Re: Where is a list of kernel messages ?

[Christian Britz]

C.T.F. Jansen wrote:



Two messages that I'm interested in are :

    kernel: [ 6997.564065] sd 3:0:0:0: [sdc] tag#3 data cmplt err -71 
uas-tag 4 inflight: CMD


    kernel: [ 6997.564108] usb 2-1.4: stat urb: status -71


I did some Google research for you and must confirm that it is really 
hard to find some usefull information, but it seens that the status -71 
indicates an "USB Protocol Error", whatever that implies.


See https://bbs.archlinux.org/viewtopic.php?pid=1167716#p1167716

The disk dock is an USB drive?

Look around for more meaningfull messages in the kernel log near the 
quoted lines.


Regards,
Christian

Where is a list of kernel messages ?

[C.T.F. Jansen]

Greetings,

Where is there a list of linux kernel messages ?
So far not found on :

 - google
 - Debian linux or kernel documentation, specifically linux-doc etc.
 - not seem in /usr/share/doc

 - www.kernel.org

If they are there then it's time for the discovery process to be shortened.

Two messages that I'm interested in are :

   kernel: [ 6997.564065] sd 3:0:0:0: [sdc] tag#3 data cmplt err -71 
uas-tag 4 inflight: CMD


   kernel: [ 6997.564108] usb 2-1.4: stat urb: status -71

The machine currently has  Debian 9 and a new disk dock and new internal 
hard disk set to go in the disk dock.
The messages may be a result of the OS being too back level for the 
newer hardware. A Debian 11 implementation is in process.


Thanks.

frank.jan...@actrix.gen.nz, ZL2TTS

users-admin qui plante sur debian 11

[hamster]

Salut.

J'ai installé debian 11 avec le  bureau MATE et j'ai users-admin qui plante.

Quand je vais dans systeme --> administration --> utilisateurs et 
groupes ca m'ouvre une fenetre qui dit "la configuration n'a pas pu etre 
chargée, une erreur imprévue est survenue".


J'ai donc regardé quelle est la commande lancée par ce bouton, c'est 
users-admin. Je l'ai donc lancée dans un terminal, et ca me répond :
(users-admin:38978): Liboobs-WARNING **: 21:26:54.766: There was an 
unknown error communicating with the backends: Failed to execute program 
org.freedesktop.SystemToolsBackends: Permission denied


La, je bloque. Mes recherches sur le web n'ont rien donné, donc si 
quelqu'un y voit un peu plus clair que moi je suis preneur.


Merci d'avance.

Re: Debian's branches and release model

[Brian]

On Mon 18 Oct 2021 at 20:51:04 +0200, harrywea...@tutanota.com wrote:

> 
> 
> -- 
>  Sent with Tutanota, the secure & ad-free mailbox. 
> 
> 
> 
> 19 Oct 2021, 03:13 by g...@wooledge.org:
> 
> > On Mon, Oct 18, 2021 at 12:29:55PM -0400, Peter Hoist wrote:
> >
> >> I am enjoying Debian's testing branch as a reasonably stable and up-to-date
> >> 'rolling' release,
> >>
> >
> > It's not.
> >
> >> So the question is, why not cut a release branch every two years, and at
> >> the same time keep the unstable/testing alive?
> >>
> >
> > You misunderstand Debian's release model at a fundamental level.
> >
> > The purpose of testing, and even unstable, is not "to give our users a
> > rolling release".  Your perception of them as such a thing is where the
> > error lies.
> >
> > The purpose of unstable (and more recently, testing) is to prepare for
> > the release of the next stable version.  Everything about them is geared
> > toward that goal.
> >
> > Packages are uploaded to testing not because they've got that new package
> > smell, and not because having higher version numbers increases your score.
> > It's because the developers believe the newer package will add benefit
> > to the next stable release.
> >
> > Let me say this again, to be clear: packages are uploaded to unstable
> > because that's how they become eligible for the next stable release.
> >
> > The unstable and testing branches themselves are just places where you
> > can go to test the next stable release before it happens, find the bugs,
> > and report them.
> >
> > The "slushy" effect (unstable mostly freezing along with testing) is
> > simply a side effect of the fact that All Of Debian is preparing for the
> > next release.  All efforts are on fixing the release-critical bugs in
> > the packages, so they don't get removed from testing (and therefore from
> > the next stable release).  Uploading a new package to unstable during
> > this time would backfire in multiple ways: not only does it take away
> > developer time that could have been spent fixing the bugs in testing,
> > but any chance of such a new unstable package migrating into testing
> > during the freeze would throw everything off.
> >
> > If you want your raw-and-bloody new package stream to continue faster,
> > you can help by reporting bugs, or even by offering fixes if your skill
> > set allows it.
> >
> > Advocating for "hey, let's split the Debian developer community into two
> > pieces right before a release" is not likely to achieve your goals.
> >
> And yet, given all that, I run a small business quite successfully, on
> Unstable, because it's a darned sight more stable than Windows.

I am not sure that that criterion is sufficient to advocate unstable on
critical systems. Comparisons with other OSs are always fraught. If it
works for you, well and good.

> I can't remember the last time I got a window freeze on Unstable.
> Testing a package, even before it is released into the Unstable
> branch, appears to be quite rigorous.

I suspect the maintainer ensures the package meets quality control
standards for inclusion in Debian. It is then bunged into unstable,
bugs and all. If you think the maintainer rigorously checks out
every aspect of the software, well ...

-- 
Brian.

Re: Kvm disabled by bios

[Francesco Scaglione]

Le Mon, 18 Oct 2021 20:50:27 +0200,
"ajh-valmer"  a écrit :

> Bonsoir,
> 
> Au boot de Debian, j'ai ce message :
> "Kvm disabled by Bios"
> 
> Faut-il mettre le mode virtuel en mode Off ou On
> dans le bios ?
> 
> Merci.
> 
> ajh  Valmer
> 

Si vous ne faites pas de virtualisation, ça peut rester en "mode Off".

https://debian-facile.org/doc:systeme:kvm

Bonne soirée,
Francesco

Re: Debian's branches and release model

[harryweaver]

-- 
 Sent with Tutanota, the secure & ad-free mailbox. 



19 Oct 2021, 03:13 by g...@wooledge.org:

> On Mon, Oct 18, 2021 at 12:29:55PM -0400, Peter Hoist wrote:
>
>> I am enjoying Debian's testing branch as a reasonably stable and up-to-date
>> 'rolling' release,
>>
>
> It's not.
>
>> So the question is, why not cut a release branch every two years, and at
>> the same time keep the unstable/testing alive?
>>
>
> You misunderstand Debian's release model at a fundamental level.
>
> The purpose of testing, and even unstable, is not "to give our users a
> rolling release".  Your perception of them as such a thing is where the
> error lies.
>
> The purpose of unstable (and more recently, testing) is to prepare for
> the release of the next stable version.  Everything about them is geared
> toward that goal.
>
> Packages are uploaded to testing not because they've got that new package
> smell, and not because having higher version numbers increases your score.
> It's because the developers believe the newer package will add benefit
> to the next stable release.
>
> Let me say this again, to be clear: packages are uploaded to unstable
> because that's how they become eligible for the next stable release.
>
> The unstable and testing branches themselves are just places where you
> can go to test the next stable release before it happens, find the bugs,
> and report them.
>
> The "slushy" effect (unstable mostly freezing along with testing) is
> simply a side effect of the fact that All Of Debian is preparing for the
> next release.  All efforts are on fixing the release-critical bugs in
> the packages, so they don't get removed from testing (and therefore from
> the next stable release).  Uploading a new package to unstable during
> this time would backfire in multiple ways: not only does it take away
> developer time that could have been spent fixing the bugs in testing,
> but any chance of such a new unstable package migrating into testing
> during the freeze would throw everything off.
>
> If you want your raw-and-bloody new package stream to continue faster,
> you can help by reporting bugs, or even by offering fixes if your skill
> set allows it.
>
> Advocating for "hey, let's split the Debian developer community into two
> pieces right before a release" is not likely to achieve your goals.
>
And yet, given all that, I run a small business quite successfully, on 
Unstable, because it's a darned sight more stable than Windows.
I can't remember the last time I got a window freeze on Unstable.
Testing a package, even before it is released into the Unstable branch, appears 
to be quite rigorous.
Cheers!

Harry.

Kvm disabled by bios

[ajh-valmer]

Bonsoir,

Au boot de Debian, j'ai ce message :
"Kvm disabled by Bios"

Faut-il mettre le mode virtuel en mode Off ou On
dans le bios ?

Merci.

ajh  Valmer

Re: Sata Hard drive testing

[David Christensen]

On 10/18/21 9:25 AM, Thomas Anderson wrote:

Hello Gurus,

I have been having problems with a drive (non-SSD) for a while now, but 
I would like to "identify" the problem specifically, so that I may 
perhaps be able to get the drive replaced.


Essentially, I have been experienced data loss, where nodes become 
unreadable, when I try to "fix it" with fdisk, it says it moves 
unreadable to the trash, basically deleting data.


I have tried reformatting the drive, writing zeros to it, and then 
temporarily the drive looks fine; but it's not! it's as if the drive is 
some how decaying: where it looks good, but then when you go to use it, 
the data later becomes unreadable.


Is there any kind of test I can execute on this drive to show it needs 
to be replaced??


Thanks!



The canonical testing tool is the one made by the drive manufacturer. 
This is the definitive way to obtain a warranty RMA.  For example, Seagate:


https://www.seagate.com/support/downloads/seatools/


As suggested by other readers, smartctl(8) can be used to obtain 
information from the drive controller, direct the controller to perform 
short and/or long self-tests, etc..  If your drive is out of warranty, 
you want a second opinion, you want to do periodic monitoring/ logging, 
etc., this tool works well.



But before you blame the drive, you also have to eliminate the SATA 
interface (typically on the motherboard), the SATA cable, the power 
supply, and all connections.  This means you need at least two 
interfaces, two cables, and two drives; it is best to have a second 
computer with two interfaces to confirm.  Test all of the permutations, 
work up a truth table of results, and find the bad component(s) by a 
process of elimination.  Beware that you may have more than one bad 
component, and that the failures may be intermittent.



David

XOrg issues with Rage 128 Ultra graphics: No screens found.

[Alex McKeever]

Essentially, my screen can be found (I have an iMac G3 in which I’ve ran Sid 
on)… however it can’t find any usable configurations, and manually generating 
an XOrg configuration (editing it to give certain options) doesn’t help. Is 
this an XOrg, driver, or kernel issue?

I’d like to know as this doesn’t just apply to Debian Ports, but any modern 
Linux distribution such as VoidPPC and Adelie Linux.

Sent from my iPad

Re: Sata Hard drive testing

[basti]

Have a look at "smartctl". It will print some info about the drive and
can also "test" your drive known as S.M.A.R.T-test.

First of all i would have a look what "smartctl -a /dev/sdX" will say.

Am 18.10.21 um 18:25 schrieb Thomas Anderson:
> Hello Gurus,
> 
> I have been having problems with a drive (non-SSD) for a while now, but
> I would like to "identify" the problem specifically, so that I may
> perhaps be able to get the drive replaced.
> 
> Essentially, I have been experienced data loss, where nodes become
> unreadable, when I try to "fix it" with fdisk, it says it moves
> unreadable to the trash, basically deleting data.
> 
> I have tried reformatting the drive, writing zeros to it, and then
> temporarily the drive looks fine; but it's not! it's as if the drive is
> some how decaying: where it looks good, but then when you go to use it,
> the data later becomes unreadable.
> 
> Is there any kind of test I can execute on this drive to show it needs
> to be replaced??
> 
> Thanks!
> 

Re: Debian's branches and release model

[Dan Ritter]

Peter Hoist wrote: 
> I am enjoying Debian's testing branch as a reasonably stable and up-to-date
> 'rolling' release

That's not what it is.

> , and I have to say it satisfies all my desires, almost.
> So the question is, why not cut a release branch every two years, and at
> the same time keep the unstable/testing alive? Is it because debian
> developers think it's too much work to reconcile the differences later, so
> they prefer freezing?

The thing is this: testing is not a rolling release. It is not a
release. It is a process which will result in a release.

Testing is the pile of packages that managed to stay 10 days in unstable
without a new major bug, without making the system [more] uninstallable,
and didn't fail to build for any release architecture.

Eventually, work is done to make testing into a release. That process is
a set of freezes over several months, which allows developers to see what
needs to be fixed immediately. The final freeze produces a stable release.

>From the wiki page:

  Compared to stable and unstable, next-stable testing has the
  worst security update speed. Don't prefer testing if security is
  a concern. 

Basically, you're getting lucky. You should not depend on it.

-dsr-

Re: Sata Hard drive testing

[Thomas Anderson]

Cool, thanks Reco!

Will post again tomorrow =) Takes 987 minutes apparently.

On 10/18/21 6:52 PM, Reco wrote:

Hi.

On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:

I have been having problems with a drive (non-SSD) for a while now,
but I would like to "identify" the problem specifically, so that I may
perhaps be able to get the drive replaced.

Assuming it's SATA/IDE drive, all you need to do is:

apt install smartmontools
smartctl -t long 
# wait for the test to finish
smartctl -a 

Please post the output of the last command.

Reco

Re: Debian's branches and release model

[Greg Wooledge]

On Mon, Oct 18, 2021 at 12:29:55PM -0400, Peter Hoist wrote:
> I am enjoying Debian's testing branch as a reasonably stable and up-to-date
> 'rolling' release, 

It's not.

> So the question is, why not cut a release branch every two years, and at
> the same time keep the unstable/testing alive?

You misunderstand Debian's release model at a fundamental level.

The purpose of testing, and even unstable, is not "to give our users a
rolling release".  Your perception of them as such a thing is where the
error lies.

The purpose of unstable (and more recently, testing) is to prepare for
the release of the next stable version.  Everything about them is geared
toward that goal.

Packages are uploaded to testing not because they've got that new package
smell, and not because having higher version numbers increases your score.
It's because the developers believe the newer package will add benefit
to the next stable release.

Let me say this again, to be clear: packages are uploaded to unstable
because that's how they become eligible for the next stable release.

The unstable and testing branches themselves are just places where you
can go to test the next stable release before it happens, find the bugs,
and report them.

The "slushy" effect (unstable mostly freezing along with testing) is
simply a side effect of the fact that All Of Debian is preparing for the
next release.  All efforts are on fixing the release-critical bugs in
the packages, so they don't get removed from testing (and therefore from
the next stable release).  Uploading a new package to unstable during
this time would backfire in multiple ways: not only does it take away
developer time that could have been spent fixing the bugs in testing,
but any chance of such a new unstable package migrating into testing
during the freeze would throw everything off.

If you want your raw-and-bloody new package stream to continue faster,
you can help by reporting bugs, or even by offering fixes if your skill
set allows it.

Advocating for "hey, let's split the Debian developer community into two
pieces right before a release" is not likely to achieve your goals.

Re: Sata Hard drive testing

[Reco]

Hi.

On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
> I have been having problems with a drive (non-SSD) for a while now,
> but I would like to "identify" the problem specifically, so that I may
> perhaps be able to get the drive replaced.

Assuming it's SATA/IDE drive, all you need to do is:

apt install smartmontools
smartctl -t long 
# wait for the test to finish
smartctl -a 

Please post the output of the last command.

Reco

Re: Sata Hard drive testing

[Felix Miata]

Thomas Anderson composed on 2021-10-18 18:25 (UTC+0200):

> I have been having problems with a drive (non-SSD) for a while now, but 
> I would like to "identify" the problem specifically, so that I may 
> perhaps be able to get the drive replaced.

> Essentially, I have been experienced data loss, where nodes become 
> unreadable, when I try to "fix it" with fdisk, it says it moves 
> unreadable to the trash, basically deleting data.

> I have tried reformatting the drive, writing zeros to it, and then 
> temporarily the drive looks fine; but it's not! it's as if the drive is 
> some how decaying: where it looks good, but then when you go to use it, 
> the data later becomes unreadable.

> Is there any kind of test I can execute on this drive to show it needs 
> to be replaced??  
>   
>   
man smartctl
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Sata Hard drive testing

[Thomas Anderson]

Hello Gurus,

I have been having problems with a drive (non-SSD) for a while now, but 
I would like to "identify" the problem specifically, so that I may 
perhaps be able to get the drive replaced.


Essentially, I have been experienced data loss, where nodes become 
unreadable, when I try to "fix it" with fdisk, it says it moves 
unreadable to the trash, basically deleting data.


I have tried reformatting the drive, writing zeros to it, and then 
temporarily the drive looks fine; but it's not! it's as if the drive is 
some how decaying: where it looks good, but then when you go to use it, 
the data later becomes unreadable.


Is there any kind of test I can execute on this drive to show it needs 
to be replaced??


Thanks!

Debian's branches and release model

[Peter Hoist]

Hi,

I am enjoying Debian's testing branch as a reasonably stable and up-to-date
'rolling' release, and I have to say it satisfies all my desires, almost.
The one thing that bothers me is that every two years, the unstable/testing
branches are frozen to certain extent because of the stable releases. This
means the testing branch can be quite lagged behind upstream releases. One
example is gcc, with gcc-11 released almost 6 months ago, and it is still
not default in debian testing - I know it is being worked on right now and
probably only a couple days away, but still...

So the question is, why not cut a release branch every two years, and at
the same time keep the unstable/testing alive? Is it because debian
developers think it's too much work to reconcile the differences later, so
they prefer freezing?

Some ppl recommend arch for this reason, but I am already familiar with
apt's way of things, and would hold off switching before I have a better
understanding of the bigger picture.

I am certainly not qualified to make recommendations here, just wondering
what is the reason behind it and if there is some proposal to make testing
a better/closer 'rolling' release that ppl like me can enjoy better:)

cheers,

P

Re: SDDM doesn't show up at boot

[David Wright]

On Sun 17 Oct 2021 at 17:12:54 (-0400), Cmdte Alpha Tigre Z wrote:

> I was trying to set up the keyboard for the whole system
> with "localectl set-x11-keymap pc105 us altgr-intl".  Before
> that, it did not have the altgr-intl variant.

On account of having run Debian a long time, I set up my keyboard
using   dpkg-reconfigure keyboard-configuration, so I have no
experience of running localectl. However, the man page says:

 set-x11-keymap LAYOUT [MODEL [VARIANT [OPTIONS]]]
 Set the system default keyboard mapping for X11 and the virtual
 console. This takes a keyboard mapping name (such as "de" or
 "us"), and possibly a model, variant, and options, see kbd(4) for
 details. Unless --no-convert is passed, the selected setting is
 also applied as the system console keyboard mapping, after
 converting it to the closest matching console keyboard mapping.

So might it be worth trying:

  localectl set-x11-keymap us pc105 altgr-intl

> Later, I removed the "altgr-intl" option from "/etc/default/keyboard"
> and rebooted, and voilá... everything was back to normal and
> SDDM showed up at the end of the boot process.

Could you post the contents of /etc/default/keyboard after
running each of the commands above. (It seems pointless for me to try
to see the effects, as I don't use a DE, DM or "greeter".)

Cheers,
David.

Re: Disk partitioning phase of installation

[David Wright]

On Sat 16 Oct 2021 at 18:47:25 (+0100), Brian wrote:
> On Sat 16 Oct 2021 at 10:12:34 -0500, David Wright wrote:
> 
> [Lots of snipping]
> 
> > If you want to see a blow-by-blow example of the partitioner, you
> > could revisit this post from a while back. IIRC the thread exercises
> > most of the wrinkles that could occur if the user interface is
> > misunderstood.
> > 
> > https://lists.debian.org/debian-user/2015/02/msg00153.html
> > 
> > It's difficult to envisage a time when each and every d-i screen would
> > be documented at this sort of level. I've no idea what the "limits" are
> > of which you speak.
> 
> The Installer Guide dots many i's and crosses many t's. However,
> you yourself have  sent many fine text screeshots of the installer
> in action to -user.(I have never found out how they were produced).
> 
> One picture is worth..., etc. I wonder whether the Guide would
> benefit from an appendix showing something similar.

Expert install, step 1¹ is:

  ┌┤ [?] Load installer components from CD 
├┐   
  │ 
│   
  │ All components of the installer needed to complete the install will be 
loaded   │   
  │ automatically and are not listed here. Some other (optional) installer  
│   
  │ components are shown below. They are probably not necessary, but may be 
│   
  │ interesting to some users.  
│   
  │ 
│   
  │ Note that if you select a component that requires others, those components  
│   
  │ will also be loaded.
│   
  │ 
│   
  │ Installer components to load:   
│   
  │……………………………… 
│   
  │[*] network-console: Continue installation remotely using SSH
 ▒  │   
  │……………………………… 
│   
  │ 
│   
  │  
│   
  │ 
│   
  
└─┘
   

When you see the opportunity to execute this command, step 2 is:

  ┌┤ [?] Debian installer main menu ├┐  

  │  │  

  │ Choose the next step in the install process: │  

  │  │  

  │  ………………………   │  

  │  Detect network hardware │  

  │  Configure the network   │  

  │  Continue installation remotely using SSH ← I faked this line ²  │  

  │  Set up users and passwords  │  

  │  ………………………   │  

  │  │  

  └──┘  


  ┌┤ [!!] Continue installation remotely using SSH 
├┐   
  │ 
│   
  │ You need to set a password for remote access to the Debian installer. A 
│   
  │ malicious or unqualified user with access to the installer can have 
disastrous  │   
  │ results, so you should take care to choose a password that is not easy to   
│   
  │ guess. It should not be a word found in the dictionary, or a word that 
could be │   
  │ easily associated with you, like your middle name.  
│   
  │ 
│   
  │ This password is only used by the Debian installer, and will be discarded 
once  │   
  │ you finish the installation.
│   
  │ 
│   
  │ Remote installation password:   
│   
  │ 
│   
  │ _   
│   
  │

Re: sysrq over *USB*

[David Wright]

On Mon 18 Oct 2021 at 13:06:33 (+0200), Marc SCHAEFER wrote:
> On Fri, Oct 15, 2021 at 09:33:20PM -0500, Nicholas Geovanis wrote:
> > It's a side issue, not my main question, but If feel some details are
> > missing in
> > the "apu2 null modem" block-box there :-)
> 
> It may be that your e-mail client is not handling ASCII art properly,
> you can look at the correct version here:
> 
>https://lists.debian.org/debian-user/2021/10/msg00658.html

It's even simpler; their response at:

https://lists.debian.org/debian-user/2021/10/msg00665.html

that quotes your post, shows that they're reading technical list
emails in a proportional font, not a fixed one.

Cheers,
David.

Re: A .profile puzzle

[David Wright]

On Mon 18 Oct 2021 at 09:44:28 (-0400), Greg Wooledge wrote:
> On Mon, Oct 18, 2021 at 08:56:47AM -0400, Gene Heskett wrote:
> > On Monday 18 October 2021 07:17:05 Greg Wooledge wrote:
> > > On Mon, Oct 18, 2021 at 01:42:43AM -0400, Gene Heskett wrote:
> > > > On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
> > > > > * Gene Heskett  [21-10/17=Su 12:18 -0400]:
> > > > > > [...] opening a terminal hasn't called
> > > > > > a ". .profile" since about jessie [...]
> > > > >
> > > > > Check whether you *also* have either .bash_profile or
> > > > > .bash_login, because either of those supersedes .profile:
> > > > >
> > > > > ls -lA ~/.bash_{profile,login}
> > > >
> > > > Neither present, just .bashrc, and .bash_logout
> > >
> > > That's as expected, then.  Your .profile is not being read *now*
> > > because it's not supposed to be, if you use a Display Manager to
> > > login.
> > >
> > > Your .profile *used* to be read by terminals, because previously, your
> > > terminals had been configured to run login shells.  However, I'd bet
> > > it was *not* read by your session, meaning any changes to the
> > > environment would not be seen by graphical applications that you
> > > launched directly from your Desktop or your WM, without going through
> > > a terminal.
> > >
> > > Assuming you run a Debian X11 Session via a Display Manager, and also
> > > assuming you don't have a .xsession file, you probably want to
> > > configure your environment in ~/.xsessionrc (note the "rc" on the
> > > end).
> > 
> > That does not exist on that machine. I'll look into it a bit later, 
> > thanks Greg.
> 
> Create it.  Now it exists.  Tada!

You *just* got done saying all this stuff last week^H^H^H^Hyear.

https://lists.debian.org/debian-user/2020/08/msg00184.html

But thanks for yesterday's summary — I read it /with/ my beer.

Cheers,
David.

Re: Debian en un mòbil? Estàs de conya?

[Iker Bilbao]

Bones,

    Just avui rebo una enquesta de https://calyxos.org/features/

    https://www.surveylegend.com/s/3iiz

    El coneixeu? Encara que no sigui debian?

    SAX,

*Iker.*



On 8/10/21 9:40, Narcis Garcia wrote:

Fent chroot:

. es pot xifrar el dispositiu? Sí, sempre i quan el contenidor no sigui
un simple directori sinó una imatge de disc (muntada amb ploop). No sé
si l'assistent «Debian Kit» ajuda en això.

. firefox homologable i que funcioni i amb plugins de privacitat? Sí,
dins un contenidor.

. vpn's, tor? Sí.

. hotspot? No crec.


Per cert, no trobo res de Mobian a l'enciclopèdia.

Narcís.


El 7/10/21 a les 16:49, xavi ha escrit:

Hola,

Ho vaig fer servir durant un parell d'anys un mòbil amb ubuntu touch
(actualment em sembla que es diuen ubports: (https://ubports.com) . I
bueno, no vaig quedar gaire content. Coses que considerem molt bàsiques
en un dispositiu no acabaven de funcionar:

. No es podia xifrar el dispositiu.

. Malgrat el nom i que era un linux l'extra gran majoria dels programes
disponibles eren webapps bastant poc elaborades.

. Fer servir programes nadius de linux (via apt) o apps d'android (via
emulador) era bastant un cristo.

. Un aspecte important era que el navegador era molt i molt cutre. Molt.
Amb tots els respectes. Instal·lar un firefox i no dic ja un firefox amb
plugins de seguretat i etc era bastant una odisea.

. oblida't d'instal·lar-li whatsapp. De fet no es podia hasta per
llicència o algo així.

Entre les coses positives:

. funcionaven coses com Telegram, Signal...

. el client de correu era bastant presentable i diria que casi
homologable a k-9.

. era un sistema molt ràpid.

. comparat amb les alternatives existents (mobian), pot còrrer en
diversos dispositius i cada cop més.

Però tenia les mancances que us dic, que a mi al final me'l feia ja
inusable. Al final va petar el micro de l'OnePlus One on corria i
pensant-me que era un error de software vaig treure-li l'ubports per una
lineage, i fins ara.

Em sap greu rajar així d'un projecte molt maco portat per una gent trobo
que bastant genial. Però al final vaig acabar havent de tornar a
~android a l'espera de que tal va mobian en producció sobre pinephone.
Per si hi han usuaris per aquí, pregunto:

. es pot xifrar el dispositiu?

. firefox homologable i que funcioni i amb plugins de privacitat?

. vpn's, tor?

. hotspot?

Gràcies i salut :)

On 2021-10-07 13:55, Narcis Garcia wrote:

Jo no he provat mai el WhatsApp. Ja em sento còmode amb SMS, XMPP i el
correu electrònic.

Deu fer des del 2008 que disposo d'un telèfon Nokia N900, que ja portava
de fàbrica una distribució derivada de Debian (Maemo). Segueix
funcionant perfectament per a tot allò que faig en les meves
comunicacions (veu, Internet, etc.).

Entremig vaig fer servir una temporada un telèfon amb Android i, per a
suplir les mancances, li vaig instal·lar Ubuntu i Debian mitjançant
chroot. Això fins que es va morir l'aparell i vaig tornar a Maemo, que a
més a més va amb un derivat de Gnome 3 (Hildon).

Ni m'espia ni m'explota.

Ara em sembla que hi ha disponible la versió «Maemo Leste».


El 7/10/21 a les 13:17, Blackhold ha escrit:

molt interessant! a mi una de les coses que em tira enrere és el
punyetero whatsapp (també l'economia per comprar un telèfon
específic).

Per whatsapp a linux he vist això:

https://blog.desdelinux.net/como-usar-whatsapp-en-linux-con-pidgin/

No sé si algú ho ha provat

- Blackhold
http://blackhold.nusepas.com
@blackhold_
~> cal lluitar contra el fort per deixar de ser febles, i contra
nosaltres mateixos quan siguem forts (Xirinacs)
<°((( ><

Missatge de Joan  del dia dj., 7 d’oct. 2021 a
les 8:39:

Un vídeo de mitja hora:

https://saimei.ftp.acc.umu.se/pub/debian-meetings/2021/MiniDebConf-Regensburg/debian-on-a-smart-phone-are-you-serious.lq.webm


--
Joan Cervan i Andreu
http://personal.calbasi.net

"El meu paper no és transformar el món ni l'home sinó, potser, el de
ser útil, des del meu lloc, als pocs valors sense els quals un món no
val la pena viure'l" A. Camus

i pels que teniu fe:
"Déu no és la Veritat, la Veritat és Déu"
Gandhi

"Donar exemple no és la principal manera de influir sobre els altres;
es la única manera" Albert Einstein

“Lluitarem contra el fort mentre siguem febles i contra nosaltres
mateixos quan siguem forts” Lluís Maria Xirinacs

Re: [Sid] Firefox problem

[Celejar]

On Sun, 17 Oct 2021 10:55:45 +0200
Grzesiek  wrote:

> Hi there,
> 
> On some of machines I use, after opening of Firefox I get empty browser 
> window (with menus, decorations etc) but nothing else is displayed. Its 
> impossible to open menu, type address, etc. The only thing you can do is 
> to close the window. After changing display configuration (rotate to 
> portrait, adding external monitor..) it starts to work as expected. You 
> do not even need to reopen. Moreover, it looks that Firefox was running 
> ok all the time but nothing was displayed.
> After recent updates on some machines I get the same problem using 
> firefox-esr.
> The only error mesg I get is:
> ###!!! [Parent][RunMessage] Error: Channel closing: too late to 
> send/recv, messages will be lost

I don't know what that message means, but I frequently get a similar
message from Firefox, despite the fact that the program is (mostly)
functional.

###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, 
messages will be lost

Celejar

Re: Nftables/Conntrack: confusion ctmark/fwmark

[Olivier]

Dans [1], j'ai lu:
nft add rule inet classify output ip daddr 1.1.1.1 ct mark set numgen inc
mod 3 offset 390
nft add rule inet classify output ip daddr 1.1.1.1 meta mark set ct mark

Qui pourrait m'expliquer ces 2 lignes ?

[1] https://forums.gentoo.org/viewtopic-t-1136379-start-0.html

Le lun. 18 oct. 2021 à 16:17, Olivier  a écrit :

> Bonjour,
>
> Je découvre nftables sur une machine équipée de Bullseye.
>
> Sur cette machine j'ai les règles:
>
> # ip rule show
> 0: from all lookup local
> 0: from all fwmark 0x2 lookup link2
> 32766: from all lookup main
> 32767: from all lookup default
>
> J'aimerai que nftables ajoute une marque donnée pour le trafic non-marqué
> reçu sur une interface Ethernet donnée, auto-configurée par DHCP.
> Comment l'obtenir ?
>
> J'ai essayé (sans succès) où ens3.432 est le nom de l'interface
> (virtuelle) sur laquelle le trafic est reçu:
>
> add rule ip mangle input iifname "ens3.432" meta mark 0 log prefix
> "Rule42-A1" counter ct mark set 0x2
>
> La table mangle et sa chaine input sont définies par:
>
> table mangle {
> chain prerouting { type filter hook prerouting priority -150; }
> chain input { type filter hook input priority -150; }
> chain forward { type filter hook forward priority -150; }
> chain output { type route hook output priority -150; }
> chain postrouting { type filter hook postrouting priority -150; }
> }
>
> Dans les faits, j'observe que:
>
> - la règle mangle ci-dessus est exécutée car je elle figure dans les logs
> et la commande "conntrack -L -o id,extended" montre qu'une marque est
> appliquée sur le rafic avec l'émetteur
>
> - la réponse est émise vers l'émetteur avec la bonne adresse source mais
> une autre interface (celle par défaut).
>
> Ces deux observations me laissent pense que la règle "fwmark 0x2 lookup
> link2" est ignorée.
> Cette conviction est renforcée par le fait que quand je remplace cette
> règle par une règle basée sur l'IP source ("from 192.168.17.0/24 lookup
> link2"), l'émetteur reçoit la réponse via la bonne interface.
> Comme l'interface est configurée par DHCP, j'aimerai autant que possible
> ne pas utiliser de règle faisant intervenir des données que je ne maîtrise
> pas (ie celles fournies par le serveur DHCP).
>
> J'ai l'impression que:
> soit il y a une confusion de ma part entre les marques de conntrack et
> celles de nftables,
> soit il y a une erreur dans la définition de la chaine input ou sa table
> mangle,
> soit encore autre chose.
>
> Qui pourrait me mettre sur la bonne voie ?
>
> Slts
>
>
>

Nftables/Conntrack: confusion ctmark/fwmark

[Olivier]

Bonjour,

Je découvre nftables sur une machine équipée de Bullseye.

Sur cette machine j'ai les règles:

# ip rule show
0: from all lookup local
0: from all fwmark 0x2 lookup link2
32766: from all lookup main
32767: from all lookup default

J'aimerai que nftables ajoute une marque donnée pour le trafic non-marqué
reçu sur une interface Ethernet donnée, auto-configurée par DHCP.
Comment l'obtenir ?

J'ai essayé (sans succès) où ens3.432 est le nom de l'interface (virtuelle)
sur laquelle le trafic est reçu:

add rule ip mangle input iifname "ens3.432" meta mark 0 log prefix
"Rule42-A1" counter ct mark set 0x2

La table mangle et sa chaine input sont définies par:

table mangle {
chain prerouting { type filter hook prerouting priority -150; }
chain input { type filter hook input priority -150; }
chain forward { type filter hook forward priority -150; }
chain output { type route hook output priority -150; }
chain postrouting { type filter hook postrouting priority -150; }
}

Dans les faits, j'observe que:

- la règle mangle ci-dessus est exécutée car je elle figure dans les logs
et la commande "conntrack -L -o id,extended" montre qu'une marque est
appliquée sur le rafic avec l'émetteur

- la réponse est émise vers l'émetteur avec la bonne adresse source mais
une autre interface (celle par défaut).

Ces deux observations me laissent pense que la règle "fwmark 0x2 lookup
link2" est ignorée.
Cette conviction est renforcée par le fait que quand je remplace cette
règle par une règle basée sur l'IP source ("from 192.168.17.0/24 lookup
link2"), l'émetteur reçoit la réponse via la bonne interface.
Comme l'interface est configurée par DHCP, j'aimerai autant que possible ne
pas utiliser de règle faisant intervenir des données que je ne maîtrise pas
(ie celles fournies par le serveur DHCP).

J'ai l'impression que:
soit il y a une confusion de ma part entre les marques de conntrack et
celles de nftables,
soit il y a une erreur dans la définition de la chaine input ou sa table
mangle,
soit encore autre chose.

Qui pourrait me mettre sur la bonne voie ?

Slts

Re: A .profile puzzle

[Greg Wooledge]

On Mon, Oct 18, 2021 at 08:56:47AM -0400, Gene Heskett wrote:
> On Monday 18 October 2021 07:17:05 Greg Wooledge wrote:
> 
> > On Mon, Oct 18, 2021 at 01:42:43AM -0400, Gene Heskett wrote:
> > > On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
> > > > * Gene Heskett  [21-10/17=Su 12:18 -0400]:
> > > > > [...] opening a terminal hasn't called
> > > > > a ". .profile" since about jessie [...]
> > > >
> > > > Check whether you *also* have either .bash_profile or
> > > > .bash_login, because either of those supersedes .profile:
> > > >
> > > > ls -lA ~/.bash_{profile,login}
> > >
> > > Neither present, just .bashrc, and .bash_logout
> >
> > That's as expected, then.  Your .profile is not being read *now*
> > because it's not supposed to be, if you use a Display Manager to
> > login.
> >
> > Your .profile *used* to be read by terminals, because previously, your
> > terminals had been configured to run login shells.  However, I'd bet
> > it was *not* read by your session, meaning any changes to the
> > environment would not be seen by graphical applications that you
> > launched directly from your Desktop or your WM, without going through
> > a terminal.
> >
> > Assuming you run a Debian X11 Session via a Display Manager, and also
> > assuming you don't have a .xsession file, you probably want to
> > configure your environment in ~/.xsessionrc (note the "rc" on the
> > end).
> 
> That does not exist on that machine. I'll look into it a bit later, 
> thanks Greg.

Create it.  Now it exists.  Tada!

Re: Error installing texlive-base

[Victor Hugo Muñoz]

El lun, 18 oct 2021 a las 9:07, Andrei POPESCU
() escribió:
>
> On Vi, 15 oct 21, 10:39:54, Victor Hugo Muñoz wrote:
> >
> > Actually, yes. Why? Due to confinement, my home PC has also been my
> > office PC. And
> > since I had a working machine, decided to upgrade packages only if
> > strictly necessary.
>
> As you found out (the hard way), the "strictly necessary" isn't always
> obvious.
>
> > Although I have installed reportbug to watch out for reported issues,
> > upgrades in unstable
> > can break important things and that cost has not been acceptable for
> > me for a long time.
>
> Switch to stable then ;)
>
> You were already using packages older than latest stable, so what is the
> benefit of running (something that appeared to be) unstable?
>

Living? :-)

I mean, I guess we all have our pressures, work/family/etc., so in the
end it's a balance between
things, and the perceived time one has to fix things if they break.
>From the very beginning, when I started using Debian (back in potato
times)
I have run stable at work, and unstable at home, with periodic
updates. To try new features in advance, to try new software in
advance,
whatever. And eventually, less time to play, and a variable risk
disposition. Life is always complex, and computers are a part of it.

Victor

Re: wpa supplicant not starting - code 1...........

[Charlie]

On Mon, 18 Oct 2021 09:54:50 + Andrew Informed me about Re:
wpa supplicant not starting - code 1...

> On Mon, Oct 18, 2021 at 02:23:17PM +1100, Charlie wrote:
> > 
> > On Sat, 16 Oct 2021 12:23:47 -0400 Henning Informed me about
> > Re: wpa supplicant not starting - code 1...
> >   
> > > On Fri, Oct 15, 2021 at 12:39:41PM +1100, Charlie wrote:  
> > > > 
> > > > On Thu, 14 Oct 2021 12:31:16 -0400 Henning Informed me
> > > > about Re: wpa supplicant not starting - code 1...
> > > > 
> > > > > On Tue, Oct 12, 2021 at 12:14:05PM +1100, Charlie wrote:
> > > > > > 
> > > > > > From my keyboard:
> > > > > > 
> > > > > > Hello,
> > > > > > 
> > > > > > If someone has an idea about this error message
> > > > > > after suspend can you please give me a hint as to what is
> > > > > > causing it:
> > > > > > 
> > > > > > wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
> > > > > > run-parts: /etc/network/if-pre-up.d/wpasupplicant exited
> > > > > > with return code 1
> > > > > > 
> > > > > > Since Bullseye went stable on my Dell Inspiron laptop I
> > > > > > have had some problems. The above is the latest. It happens
> > > > > > randomly and there is no way of duplicating it.
> > > > > > 
> > > > > > I have googled this, but tried some of the suggestions
> > > > > > without getting wpa supplicant to work again except by
> > > > > > rebooting the laptop?
> > > > > > 
> > > > > > Can someone tell me what "code 1" is please?
> > > > > >   
> > > > > 
> > > > > 
> > > > > You clearly hacked together something unusual there. To being
> > > > > helped, you have to provide more information.
> > > > > Is there any log entry?
> > > > > Please post the pre-up script.
> > > > > Is there a particular reason why you configured the wifi this
> > > > > way?
> > > > > 
> > > > > -H
> > > > 
> > > > 
> > > > Absolutely standard vanilla install and use from Bulleye when
> > > > it was testing. It happened a couple of random times in testing
> > > > as well. But that was testing, so just rebooted.
> > > > 
> > > > No hacking done at all. Some mention on the web:
> > > > 
> > >   
> > > > https://forums.debian.net/viewtopic.php?f=5=145175
> > > >
> > > 
> > > Well,
> > > that is wifi configuration in /e/n/i
> > > Can you please then post the stanza for your wifi?
> > > 
> > > The code 1 is pretty generic.
> > > /etc/wpa_supplicant/ifupdown.sh pretty much
> > > throws an exit code 1 for all unsuccessful cases.
> > > 
> > >   
> > > > Not in any way applicable
> > > > 
> > > > Looked for fresher information, didn't find it.
> > > > 
> > > > Think it might be hardware.
> > > 
> > > That might be. I do have frequently trouble with an old
> > > powerbook pro. I think it is the power management causing
> > > trouble.
> > >   
> > > > 
> > > > Have had other hardware issues, so think this Dell laptop might
> > > > be a lemon. Ce la vie
> > > 
> > > Have you ever tried to use the network manager?
> > > For that you have to comment out the stanza for your
> > > wifi in /e/n/i
> > > 
> > >   
> > > > 
> > > > Thanks for your input.
> > > > 
> > > > PS, has worked since I rebooted just after making this inquiry.
> > > >   
> > > -- 
> > > Henning Follmann   | hfollm...@itcfollmann.com
> > >   
> > 
> > Hello Henning.
> > 
> > I have no idea what an e/n/i is. Am one of those
> > unfortunates that fixes a motor, removes the worn part, takes it to
> > a spare parts seller and shows them, because I have no idea what
> > they are called. Brings home the new one and fixes the motor.
> > 
> > I left school at 14 years of age. Am old now and memory is not all
> > that good. Googled e/n/i can't discover what it means.
> > 
> > I have tried network manager about 15 years or more, ago. Didn't
> > like it and never touched it again. Then for a short, full of
> > problems time, the other one as well. Don't recall its name.
> > Dropped that as well.
> > 
> > Anyway, I haven't had the wpa-supplicant problem again, so maybe it
> > was just a momentary glitch. I am always bemused by errors on my
> > computer, because I think that something which is all about
> > mathematics should just work. 2 and 2 can only make 4, not 5, not 6
> > or anything else? I obviously don't understand the coding in the
> > programs where the human error must enter the works.
> > 
> > So thanks for your help, but I can't complete what you ask.  
> 
> /etc/network/interfaces 
> 
> The place where networking is largely set up.
> 
> You may find that things have changed with setting up networking as
> you've moved from one release of Debian to the next.
> 
> All the very best, as ever,
> 
> Andy Cater

Thanks Andy,

I know that file:

[quote]

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo

Re: AMD OpenCL support

[Linux-Fan]

piorunz writes:


On 17/10/2021 23:31, Linux-Fan wrote:

Back then, I got it from
https://www.amd.com/en/support/professional-graphics/radeon-pro/radeon-pro- 
w5000-series/radeon-pro-w5500

under
"Radeon(TM) Pro Software for Enterprise on Ubuntu 20.04.2" and the
download still seems to point to a file with the same SHA-256 sum.

It could be worth trying the exact same version that I used?


Thanks for your reply.

I have Radeon 6900XT, which is different type of card. Not sure if
https://www.amd.com/en/support/professional-graphics/radeon-pro/radeon-pro- 
w5000-series/radeon-pro-w5500

will work for me?


I use a Radeon Pro W5500.

AMDs website leads me to
https://www.amd.com/de/support/graphics/amd-radeon-6000-series/amd-radeon-6900-series/amd-radeon-rx-6900-xt
for your GPU and proposes to download "Radon(TM) Software for Linux Driver  
for Ubuntu 20.04.3" which seems to be a different TGZ than what I am using  
(it has 1290604 vs. 1292797).


I cannot find the list of compatible GPUs for the particular package I have  
downloaded, the documentation only tells me about "Stack Variants" quoting  
from it (amdgpu graphis and compute stack 21.20 from the TGZ with 1292797):


| There are two major stack variants available for installation:
|
|  * Pro: recommended for use with Radeon Pro graphics products.
|  * All-Open: recommended for use with consumer products.

Hence it is clear that AMD proposes using the "amdgpu-pro" only with the  
"Radon Pro" graphics cards. Whether that also means that the driver is  
incompatible with "consumer products", I do not know.


Searching online yields these links:

* https://wiki.debian.org/AMDGPUDriverOnStretchAndBuster2
* https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-21-20

The second page indicates that "AMD Radeon™ RX 6900/6800/6700 Series  
Graphics" are compatible with the "Radeon(TM) Software for Linux(R) 21.20".  
Now whether that document is the correct one to correspond with my  
downloaded TGZ I cannot really tell. But if they match, it may as well  
indicate that it is possible to use that driver with your GPU, too.


HTH
Linux-Fan

öö

[...]


pgpQdJA4EUpZ6.pgp
Description: PGP signature

Re: A .profile puzzle

[Gene Heskett]

On Monday 18 October 2021 07:17:05 Greg Wooledge wrote:

> On Mon, Oct 18, 2021 at 01:42:43AM -0400, Gene Heskett wrote:
> > On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
> > > * Gene Heskett  [21-10/17=Su 12:18 -0400]:
> > > > [...] opening a terminal hasn't called
> > > > a ". .profile" since about jessie [...]
> > >
> > > Check whether you *also* have either .bash_profile or
> > > .bash_login, because either of those supersedes .profile:
> > >
> > > ls -lA ~/.bash_{profile,login}
> >
> > Neither present, just .bashrc, and .bash_logout
>
> That's as expected, then.  Your .profile is not being read *now*
> because it's not supposed to be, if you use a Display Manager to
> login.
>
> Your .profile *used* to be read by terminals, because previously, your
> terminals had been configured to run login shells.  However, I'd bet
> it was *not* read by your session, meaning any changes to the
> environment would not be seen by graphical applications that you
> launched directly from your Desktop or your WM, without going through
> a terminal.
>
> Assuming you run a Debian X11 Session via a Display Manager, and also
> assuming you don't have a .xsession file, you probably want to
> configure your environment in ~/.xsessionrc (note the "rc" on the
> end).

That does not exist on that machine. I'll look into it a bit later, 
thanks Greg.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: wpa supplicant not starting - code 1...........

[Charlie]

On Mon, 18 Oct 2021 07:29:36 -0400 Henning Informed me about
Re: wpa supplicant not starting - code 1...

> On Mon, Oct 18, 2021 at 02:23:17PM +1100, Charlie wrote:
> >   
> [...]
> 
> > 
> > Hello Henning.
> > 
> > I have no idea what an e/n/i is. Am one of those
> > unfortunates that fixes a motor, removes the worn part, takes it to
> > a spare parts seller and shows them, because I have no idea what
> > they are called. Brings home the new one and fixes the motor.
> > 
> > I left school at 14 years of age. Am old now and memory is not all
> > that good. Googled e/n/i can't discover what it means.  
> 
> It mainly means that I am a lazy bastard, and for somebody who
> complains all the time when people are not more explanatory in their
> posts, a hypocrite too.
> 
> /e/n/i = /etc/network/interfaces
> 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# auto enp1s0
iface enp1s0 inet dhcp

# Wildlife
# auto wlp2s0
iface wlp2s0 inet dhcp
wpa-ssid *
wpa-psk *

# Wildlife Belkin
# iface wlp2s0 inet dhcp
#   wpa-ssid ***
#   wpa-psk **

[end quote]

I have thought about commenting out the whole of:

# The primary network interface
# auto enp1s0
iface enp1s0 inet dhcp

However, if it slows down connecting to the net to leave it like this,
its hardly noticeable and quick to just bring it up if
wifi/wpa-supplicant doesn't work.

 As you say an annoyance when it doesn't do what one expects.
> > 
> > I have tried network manager about 15 years or more, ago. Didn't
> > like it and never touched it again. Then for a short, full of
> > problems time, the other one as well. Don't recall its name.
> > Dropped that as well.  
> 
> Yes, understandable, Network-Manager had and has its problems.
> But it has come a long way. It is worth looking at.
> 
> > 
> > Anyway, I haven't had the wpa-supplicant problem again, so maybe it
> > was just a momentary glitch. I am always bemused by errors on my
> > computer, because I think that something which is all about
> > mathematics should just work. 2 and 2 can only make 4, not 5, not 6
> > or anything else? I obviously don't understand the coding in the
> > programs where the human error must enter the works.
> > 
> > So thanks for your help, but I can't complete what you ask.
> > 
> > Just have to get on.  
> 
> Sure, if it works, there is no reason to invest more time
> into this (at most annoyance).
> 
> 
> > 
> > Charlie
> > --  
> 
> 
> -H
> 
> -- 
> Henning Follmann   | hfollm...@itcfollmann.com
> 


-- 
Registered Linux User:- 329524

***

I scarcely remember counting upon any Happiness—I look not for
it if it be not in the present hour—nothing startles me beyond
the Moment. The setting sun will always set me to rights—or if
a Sparrow come before my Window I take part in its existence
and pick about the Gravel. ---John Keats

***
Debian GNU/Linux - Magic indeed.

-

Re: wpa supplicant not starting - code 1...........

[Charlie]

On Mon, 18 Oct 2021 09:54:50 + Andrew Informed me about Re:
wpa supplicant not starting - code 1...

> On Mon, Oct 18, 2021 at 02:23:17PM +1100, Charlie wrote:
> > 
> > On Sat, 16 Oct 2021 12:23:47 -0400 Henning Informed me about
> > Re: wpa supplicant not starting - code 1...
> >   
> > > On Fri, Oct 15, 2021 at 12:39:41PM +1100, Charlie wrote:  
> > > > 
> > > > On Thu, 14 Oct 2021 12:31:16 -0400 Henning Informed me
> > > > about Re: wpa supplicant not starting - code 1...
> > > > 
> > > > > On Tue, Oct 12, 2021 at 12:14:05PM +1100, Charlie wrote:
> > > > > > 
> > > > > > From my keyboard:
> > > > > > 
> > > > > > Hello,
> > > > > > 
> > > > > > If someone has an idea about this error message
> > > > > > after suspend can you please give me a hint as to what is
> > > > > > causing it:
> > > > > > 
> > > > > > wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
> > > > > > run-parts: /etc/network/if-pre-up.d/wpasupplicant exited
> > > > > > with return code 1
> > > > > > 
> > > > > > Since Bullseye went stable on my Dell Inspiron laptop I
> > > > > > have had some problems. The above is the latest. It happens
> > > > > > randomly and there is no way of duplicating it.
> > > > > > 
> > > > > > I have googled this, but tried some of the suggestions
> > > > > > without getting wpa supplicant to work again except by
> > > > > > rebooting the laptop?
> > > > > > 
> > > > > > Can someone tell me what "code 1" is please?
> > > > > >   
> > > > > 
> > > > > 
> > > > > You clearly hacked together something unusual there. To being
> > > > > helped, you have to provide more information.
> > > > > Is there any log entry?
> > > > > Please post the pre-up script.
> > > > > Is there a particular reason why you configured the wifi this
> > > > > way?
> > > > > 
> > > > > -H
> > > > 
> > > > 
> > > > Absolutely standard vanilla install and use from Bulleye when
> > > > it was testing. It happened a couple of random times in testing
> > > > as well. But that was testing, so just rebooted.
> > > > 
> > > > No hacking done at all. Some mention on the web:
> > > > 
> > >   
> > > > https://forums.debian.net/viewtopic.php?f=5=145175
> > > >
> > > 
> > > Well,
> > > that is wifi configuration in /e/n/i
> > > Can you please then post the stanza for your wifi?
> > > 
> > > The code 1 is pretty generic.
> > > /etc/wpa_supplicant/ifupdown.sh pretty much
> > > throws an exit code 1 for all unsuccessful cases.
> > > 
> > >   
> > > > Not in any way applicable
> > > > 
> > > > Looked for fresher information, didn't find it.
> > > > 
> > > > Think it might be hardware.
> > > 
> > > That might be. I do have frequently trouble with an old
> > > powerbook pro. I think it is the power management causing
> > > trouble.
> > >   
> > > > 
> > > > Have had other hardware issues, so think this Dell laptop might
> > > > be a lemon. Ce la vie
> > > 
> > > Have you ever tried to use the network manager?
> > > For that you have to comment out the stanza for your
> > > wifi in /e/n/i
> > > 
> > >   
> > > > 
> > > > Thanks for your input.
> > > > 
> > > > PS, has worked since I rebooted just after making this inquiry.
> > > >   
> > > -- 
> > > Henning Follmann   | hfollm...@itcfollmann.com
> > >   
> > 
> > Hello Henning.
> > 
> > I have no idea what an e/n/i is. Am one of those
> > unfortunates that fixes a motor, removes the worn part, takes it to
> > a spare parts seller and shows them, because I have no idea what
> > they are called. Brings home the new one and fixes the motor.
> > 
> > I left school at 14 years of age. Am old now and memory is not all
> > that good. Googled e/n/i can't discover what it means.
> > 
> > I have tried network manager about 15 years or more, ago. Didn't
> > like it and never touched it again. Then for a short, full of
> > problems time, the other one as well. Don't recall its name.
> > Dropped that as well.
> > 
> > Anyway, I haven't had the wpa-supplicant problem again, so maybe it
> > was just a momentary glitch. I am always bemused by errors on my
> > computer, because I think that something which is all about
> > mathematics should just work. 2 and 2 can only make 4, not 5, not 6
> > or anything else? I obviously don't understand the coding in the
> > programs where the human error must enter the works.
> > 
> > So thanks for your help, but I can't complete what you ask.  
> 
> /etc/network/interfaces 
> 
> The place where networking is largely set up.
> 
> You may find that things have changed with setting up networking as
> you've moved from one release of Debian to the next.
> 
> All the very best, as ever,
> 
> Andy Cater

Thanks Andy,

I know that file:

[quote]

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo

Gtk-WARNING **: Theme parsing error: gtk-contained-dark.css

[Alexander V. Makartsev]

When I launch a GUI application, such as 'mousepad' or 'thunar' from a 
console, I get a warning:

    $ pkexec thunar

    (thunar:14366): Gtk-WARNING **: 16:25:21.434: Theme parsing error: 
gtk-contained-dark.css:2871:228: Missing closing bracket for :not()


    $ mousepad

    (mousepad:14624): Gtk-WARNING **: 16:45:35.868: Theme parsing 
error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()


    $ thunar

Notice, when I start 'thunar' as a normal user I don't get this warning, 
but when I launch 'mousepad' as a normal user I do get this warning.


Warning message is descriptive enough, so I've tried to find this 
'gtk-contained-dark.css' file and fix it by myself:

    # find / -name "gtk-contained-dark.css"
    find: ‘/var/lib/lxcfs/cgroup’: Input/output error
    /usr/share/themes/Bluebird/gtk-3.0/gtk-contained-dark.css
    #
I don't use "Bluebird" theme, so I've decided to simply uninstall 
'bluebird-gtk-theme' package, but it didn't helped.
Now, when I try to find 'gtk-contained-dark.css' file, it looks like I 
don't any files with that name:

    # find / -name "gtk-contained-dark.css"
    find: ‘/var/lib/lxcfs/cgroup’: Input/output error
    #
And there are no other packages exist that could provide a file with 
this name:

    $ apt-file find gtk-contained-dark.css
    bluebird-gtk-theme: 
/usr/share/themes/Bluebird/gtk-3.0/gtk-contained-dark.css

    $
Yet, the same warning message still being displayed every time.
I suspect there is some caching mechanism within GTK, that could cause 
this problem, but I can't find any information about that.

Can someone help me to resolve this mystery?

My system info:
    $ uname -a
    Linux hostname 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) 
x86_64 GNU/Linux

DE: Xfce 4.16 (xfwm4+lightdm)
Current theme: "Adapta-Nokto" (from 'adapta-gtk-theme' package)

--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: wpa supplicant not starting - code 1...........

[Henning Follmann]

On Mon, Oct 18, 2021 at 02:23:17PM +1100, Charlie wrote:
> 
[...]

> 
>   Hello Henning.
> 
>   I have no idea what an e/n/i is. Am one of those unfortunates
>   that fixes a motor, removes the worn part, takes it to a spare
>   parts seller and shows them, because I have no idea what they
>   are called. Brings home the new one and fixes the motor.
> 
> I left school at 14 years of age. Am old now and memory is not all that
> good. Googled e/n/i can't discover what it means.

It mainly means that I am a lazy bastard, and for somebody who complains
all the time when people are not more explanatory in their posts,
a hypocrite too.

/e/n/i = /etc/network/interfaces



> 
> I have tried network manager about 15 years or more, ago. Didn't like
> it and never touched it again. Then for a short, full of problems time,
> the other one as well. Don't recall its name. Dropped that as well.

Yes, understandable, Network-Manager had and has its problems.
But it has come a long way. It is worth looking at.

> 
> Anyway, I haven't had the wpa-supplicant problem again, so maybe it was
> just a momentary glitch. I am always bemused by errors on my computer,
> because I think that something which is all about mathematics should
> just work. 2 and 2 can only make 4, not 5, not 6 or anything else? I
> obviously don't understand the coding in the programs where the human
> error must enter the works.
> 
> So thanks for your help, but I can't complete what you ask.
> 
> Just have to get on.

Sure, if it works, there is no reason to invest more time
into this (at most annoyance).


> 
> Charlie
> --


-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: A .profile puzzle

[Greg Wooledge]

On Mon, Oct 18, 2021 at 01:42:43AM -0400, Gene Heskett wrote:
> On Monday 18 October 2021 01:12:42 Will Mengarini wrote:
> 
> > * Gene Heskett  [21-10/17=Su 12:18 -0400]:
> > > [...] opening a terminal hasn't called
> > > a ". .profile" since about jessie [...]
> >
> > Check whether you *also* have either .bash_profile or
> > .bash_login, because either of those supersedes .profile:
> >
> > ls -lA ~/.bash_{profile,login}
> 
> Neither present, just .bashrc, and .bash_logout

That's as expected, then.  Your .profile is not being read *now* because
it's not supposed to be, if you use a Display Manager to login.

Your .profile *used* to be read by terminals, because previously, your
terminals had been configured to run login shells.  However, I'd bet it
was *not* read by your session, meaning any changes to the environment
would not be seen by graphical applications that you launched directly
from your Desktop or your WM, without going through a terminal.

Assuming you run a Debian X11 Session via a Display Manager, and also
assuming you don't have a .xsession file, you probably want to configure
your environment in ~/.xsessionrc (note the "rc" on the end).

Re: sysrq over *USB*

[Marc SCHAEFER]

Hello,

On Fri, Oct 15, 2021 at 09:33:20PM -0500, Nicholas Geovanis wrote:
> It's a side issue, not my main question, but If feel some details are
> missing in
> the "apu2 null modem" block-box there :-)

It may be that your e-mail client is not handling ASCII art properly,
you can look at the correct version here:

   https://lists.debian.org/debian-user/2021/10/msg00658.html

Typically, the null modem is NOT the apu2.

> But don't you need to have a running getty now? Listening on the
> serial device file that should be associated with the USB source.

I have tested with a cu on both sides, so the port is "open" anyway, if
this is required.
 
> Interesting project though. Any involvement here with MIDI-over-USB?

No.

> Tschuss

[36 useless quote lines removed ]

Re: wpa supplicant not starting - code 1...........

[Andrew M.A. Cater]

On Mon, Oct 18, 2021 at 02:23:17PM +1100, Charlie wrote:
> 
>   On Sat, 16 Oct 2021 12:23:47 -0400 Henning Informed me about
>   Re: wpa supplicant not starting - code 1...
> 
> > On Fri, Oct 15, 2021 at 12:39:41PM +1100, Charlie wrote:
> > > 
> > >   On Thu, 14 Oct 2021 12:31:16 -0400 Henning Informed me about
> > >   Re: wpa supplicant not starting - code 1...
> > >   
> > > > On Tue, Oct 12, 2021 at 12:14:05PM +1100, Charlie wrote:  
> > > > > 
> > > > >   From my keyboard:
> > > > > 
> > > > >   Hello,
> > > > > 
> > > > >   If someone has an idea about this error message after
> > > > > suspend can you please give me a hint as to what is causing it:
> > > > > 
> > > > > wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
> > > > > run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with
> > > > > return code 1
> > > > > 
> > > > > Since Bullseye went stable on my Dell Inspiron laptop I have had
> > > > > some problems. The above is the latest. It happens randomly and
> > > > > there is no way of duplicating it.
> > > > > 
> > > > > I have googled this, but tried some of the suggestions without
> > > > > getting wpa supplicant to work again except by rebooting the
> > > > > laptop?
> > > > > 
> > > > > Can someone tell me what "code 1" is please?
> > > > > 
> > > > 
> > > > 
> > > > You clearly hacked together something unusual there. To being
> > > > helped, you have to provide more information.
> > > > Is there any log entry?
> > > > Please post the pre-up script.
> > > > Is there a particular reason why you configured the wifi this way?
> > > > 
> > > > -H  
> > > 
> > > 
> > > Absolutely standard vanilla install and use from Bulleye when it was
> > > testing. It happened a couple of random times in testing as well.
> > > But that was testing, so just rebooted.
> > > 
> > > No hacking done at all. Some mention on the web:
> > >   
> > 
> > > https://forums.debian.net/viewtopic.php?f=5=145175
> > >  
> > 
> > Well,
> > that is wifi configuration in /e/n/i
> > Can you please then post the stanza for your wifi?
> > 
> > The code 1 is pretty generic.
> > /etc/wpa_supplicant/ifupdown.sh pretty much
> > throws an exit code 1 for all unsuccessful cases.
> > 
> > 
> > > Not in any way applicable
> > > 
> > > Looked for fresher information, didn't find it.
> > > 
> > > Think it might be hardware.  
> > 
> > That might be. I do have frequently trouble with an old
> > powerbook pro. I think it is the power management causing
> > trouble.
> > 
> > > 
> > > Have had other hardware issues, so think this Dell laptop might be a
> > > lemon. Ce la vie  
> > 
> > Have you ever tried to use the network manager?
> > For that you have to comment out the stanza for your
> > wifi in /e/n/i
> > 
> > 
> > > 
> > > Thanks for your input.
> > > 
> > > PS, has worked since I rebooted just after making this inquiry.
> > > 
> > -- 
> > Henning Follmann   | hfollm...@itcfollmann.com
> > 
> 
>   Hello Henning.
> 
>   I have no idea what an e/n/i is. Am one of those unfortunates
>   that fixes a motor, removes the worn part, takes it to a spare
>   parts seller and shows them, because I have no idea what they
>   are called. Brings home the new one and fixes the motor.
> 
> I left school at 14 years of age. Am old now and memory is not all that
> good. Googled e/n/i can't discover what it means.
> 
> I have tried network manager about 15 years or more, ago. Didn't like
> it and never touched it again. Then for a short, full of problems time,
> the other one as well. Don't recall its name. Dropped that as well.
> 
> Anyway, I haven't had the wpa-supplicant problem again, so maybe it was
> just a momentary glitch. I am always bemused by errors on my computer,
> because I think that something which is all about mathematics should
> just work. 2 and 2 can only make 4, not 5, not 6 or anything else? I
> obviously don't understand the coding in the programs where the human
> error must enter the works.
> 
> So thanks for your help, but I can't complete what you ask.

/etc/network/interfaces 

The place where networking is largely set up.

You may find that things have changed with setting up networking as you've
moved from one release of Debian to the next.

All the very best, as ever,

Andy Cater


> 
> Just have to get on.
> 
> Charlie
> -- 
>   Registered Linux User:- 329524
> 
>   ***
> 
>   There is no treasure in the deep mountains; he who has no
>   desire for it finds it. ..ZEN SAYING
> 
>   ***
>   Debian GNU/Linux - Magic indeed.
> 
>   -
> 

Re: SDDM doesn't show up at boot

[Andrew M.A. Cater]

On Sun, Oct 17, 2021 at 07:52:29PM -0400, Cmdte Alpha Tigre Z wrote:
> Oh, I forgot to say: I'm using Debian 10.10 i386
> 
> El dom, 17 oct 2021 a las 17:12, Cmdte Alpha Tigre Z
> () escribió:
> >
> > Hi.
> >
> > I was trying to set up the keyboard for the whole system
> > with "localectl set-x11-keymap pc105 us altgr-intl".  Before
> > that, it did not have the altgr-intl variant.
> >
> > I have LXQt installed, with SDDM as the display manager.
> > After booting the PC again, SDDM was no longer showing up
> > when the PC finished starting.  Through some research
> > reading the systemd journal, I found that "sddm-greeter"
> > could not connect to the X server.
> >
> > I also found that, if I login at a virtual console as root and run:
> > "systemctl isolate multi-user.target" and then
> > "systemctl isolate graphical.target"
> > to try to reload the graphical system, then everything works fine
> > and SDDM shows up as normal.  It also allows me to use
> > the keyboard with the chosen configuration.
> >
> > Later, I removed the "altgr-intl" option from "/etc/default/keyboard"
> > and rebooted, and voilá... everything was back to normal and
> > SDDM showed up at the end of the boot process.
> >
> > I tried rebooting many times, changing some localization settings,
> > and the problem appeared exactly only when the "altgr-intl"
> > was enabled in "/etc/default/keyboard".  The keyboard works
> > well when you set it up through LXQt.
> >
> > Now, while writing this message, I tried it again and now
> > the kernel reports a segmentation fault in "sddm-greeter"
> > after it reads "/usr/share/xsessions/lxqt.desktop".  Of course,
> > everything fails again leaving me with only the mouse cursor
> > and a black screen.
> >
> > Before I go to report this as a bug, I wanted to know
> > if I am not the only one with this problem.
> >
> > Please, ¿could someone with LXQt and a little free time
> > tell me whether the system fails to start when adding
> > XKBVARIANT="altgr-intl" to "/etc/default/keyboard"
> > and then rebooting?  You can go back to normal behaviour
> > just logging in at a virtual console, removing the "altgr-intl"
> > part from "/etc/default/keyboard" and rebooting.
> >
> > Thanks in advance.
> 

Hi,

First things first: bring your machine up to date - there is now 10.11.
[Or update to Debian 11 - but read release notes :) ]

I think you may have two independent problems here: changing keyboard
layout shouldn't cause problems with the X server.

All best, as ever, 

Andy Cater