Re: What should I put inside the file called wlan0?

[Markus Schönhaber]

01.03.22, 06:04 +0100, Stella Ashburne:


Sent: Tuesday, March 01, 2022 at 7:18 AM
From: "Brian" 
To: debian-user@lists.debian.org
Subject: Re: What should I put inside the file called wlan0?

Om all my systems:

brian@5740:~$ ls -l /etc/network/interfaces
-rw-r--r-- 1 root root 475 Nov  3 19:23 /etc/network/interfaces


So the default chmod value of /etc/network/interfaces is 475 ?


No, 475 is the file's size.
The numeric value for the permission "-rw-r--r--" is 0644.
stat /etc/network/interfaces
will show you that.

--
Regards
  mks

cups

[Malcolm McQueen]

I use the standard cups system which has been working fine.
But it now stalls showing a status of now fails with a status of:
Processing - "The printer is in use."
The printer is a Canon MG3600.
And this works correctly from another (Mac) computer on the LAN.
Restarting cups did no good as did reinstalling it.
I'd appreciate advice.

Malcolm

Re: Re : Re: Afficher la phrase de passe pour LVM-encrypt au boot

[Aurélien Roux]

Salut,

Merci à tous les deux pour l'astuce, mais je dois passer la passphrase 
au boot, lorsque le volume qui va être monté dans /home est decrypté. 
Donc pas moyen d'utiliser le widget en question, ni même d'avoir un 
utilitaire à côté, voire même juste un tty, puisque home n'est pas 
encore monté, j'imagine que je ne peux pas encore me logger.


A plus tard.
ORL

Re: Re :Re: Grisbi.

[Sébastien NOBILI]

Bonjour Sylvie,

Le 2022-02-28 19:43, Sylvie TARDIVEL a écrit :
Merci pour les informations, mais j'ai un autre soucis. Je ne parviens 
plus à utiliser mon ordinateur portable. Je mets le bon mot de passe, 
mais il ne le reconnait pas et je n'accède plus à rien.


Ça va devenir compliqué de gérer ça à distance :D
Pour vous sortir de l'impasse et vous mettre sur les rails, vous
pouvez essayer de vous rapprocher d'un groupe local d'utilisateurs.

Vous en trouverez une liste là : https://aful.org/gul/liste

Sébastien

Re: What should I put inside the file called wlan0?

[tomas]

On Mon, Feb 28, 2022 at 11:18:25PM +, Brian wrote:

[...]

> Om all my systems:
> 
> brian@5740:~$ ls -l /etc/network/interfaces
> -rw-r--r-- 1 root root 475 Nov  3 19:23 /etc/network/interfaces

That's absolutely right. I already posted a correction, but it
doesn't seem to have made it through.

Sorry for that brain fart.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: What should I put inside the file called wlan0?

[tomas]

On Mon, Feb 28, 2022 at 10:43:52PM +0100, Stella Ashburne wrote:
> Dearie

[...]

> According to Debian Wiki WiFi How To Use 
> (https://wiki.debian.org/WiFi/HowToUse), the reason for doing the split is:
> 
> (sic) Restrict the permissions of /etc/network/interfaces, to prevent 
> pre-shared key (PSK) disclosure

I see. As others have already noted in this thread, your WiFi PSK
isn't usually a high-value secret; besides, if someone has access
to your computer, she typically has more valuable things to look
for.

One might construct scenarios: having a quick look at your laptop
in the bar while you are in the restroom, then stealing your bandwidth
(or doing nasty things from your access point's IP). But hey.

That said, you're your network's boss, so it's on you to decide.
There might be reasons to not reveal it (or, let's be realistic, to
make access to it a bit more difficult).

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Authentication failed after su-

[Stella Ashburne]

Dearie

> Sent: Tuesday, March 01, 2022 at 5:47 AM
> From: "Bob McGowan" 
> To: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
> On 2/28/22 13:09, Dan Ritter wrote:
> > sudo su - -l -c "rest of the line"
> 
> Some comments on this, without knowing just how it failed:
> 
> 1.  There is no reason I can see to using both 'sudo' and 'su' 
> together.  By default, they both let you run a command as the root user.
> 
Thanks for the clarification.

> 2.  Using both '-' and '-l' with su is redundant, they do almost (per 
> the man page) the same thing.  The man page suggests '-l' is better due 
> to reduced side effects.
> 
I wonder what "side effects" they may be.

> 3.  The -c option provides a means to tell su to run a specific 
> command.  So the string 'rest of the line' generates an error stating 
> 'command not found' if run as is.  You need to supply this part of the 
> line so processing can be duplicated and evaluated.
> 
Thanks once again.

> If I insert an 'echo' before the word 'rest', there is no error.
> 
Noted.

> Hence, the actual error is needed, as well as the actual command being run.
> 
The actual command is actually lifted from Debian Wiki 
(https://wiki.debian.org/WiFi/HowToUse). It is:

su -l -c "wpa_passphrase myssid my_very_secret_passphrase > 
/etc/wpa_supplicant/wpa_supplicant.conf"

In a terminal, I typed:

username@hostname:~$ su -l -c "wpa_passphrase JupiterRising 1234567890 > 
/etc/wpa_supplicant/wpa_supplicant.conf"
Password: 
su: Authentication failure
username@hostname:~$

The error message is Authentication failure.

Please note that I have chosen not to create a root password during the process 
of installing Debian 11.

Best regards.

Stella

Re: Startx works, but sddm/lightdm/xdm doesn't

[John Goerzen]

On Mon, Feb 28 2022, Felix Miata wrote:

>> However, removing modesetting_drv.so from
>> /usr/lib/xorg/modules/drivers did.  That solved the problem.
>
>> But it didn't switch to nouveau; it went to fbdev.
>
> You likely created a new problem. modesetting_drv.so is the default DIX for 
> AMD,
> Intel and NVidia GPUs. fbdev is unaccelerated, and won't support most common
> widescreen display modes. Some apps won't run on it. I don't think Gnome will 
> even
> start using it. Using fbdev you can expect your PC to feel like it's running a
> single core at 233MHz instead of 2000MHz or more on multiple cores.

I was afraid of this, yes.

> I don't know that I've ever migrated an installation using SDDM to another PC
> using a majorly different GPU. I use TDM or KDM3 on most installations, with a
> rare few on LightDM or SDDM, whose themes I always have extreme negative
> appreciation for.

Somehow the Live CDs must be doing something that works here.  I guess
it might be interesting to see what Debian Live KDE does on this box!

John

Re: Authentication failed after su-

[Stella Ashburne]

Dearie

> Sent: Tuesday, March 01, 2022 at 7:13 AM
> From: "Dan Ritter" 
> To: "Stella Ashburne" 
> Cc: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
> >
> > In a terminal, I typed:
> >
> > username@hostname:~$ su -l -c "wpa_passphrase JupiterRising 1234567890 > 
> > /etc/wpa_supplicant/wpa_supplicant.conf"
> > Password:
> > su: Authentication failure
>
> That means that you failed to give the root password.
>
I disabled the root password during the process of installing Debian 11.

What should I do to resolve the issue?

Best regards.

Stella

Re: What should I put inside the file called wlan0?

[Stella Ashburne]

Dear Ash

> Sent: Tuesday, March 01, 2022 at 5:36 AM
> From: "Ash Joubert" 
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
>
> qrencode -s 20 -o wifi.png "WIFI:S:Your Wifi SSID;T:WPA;P:Your Wifi
> Passphrase;;"
>
Thanks for the tip.

Best regards.

Stella

Re: What should I put inside the file called wlan0?

[Stella Ashburne]

Dearie

> Sent: Tuesday, March 01, 2022 at 7:18 AM
> From: "Brian" 
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
> Om all my systems:
>
> brian@5740:~$ ls -l /etc/network/interfaces
> -rw-r--r-- 1 root root 475 Nov  3 19:23 /etc/network/interfaces
>
So the default chmod value of /etc/network/interfaces is 475 ?

Best regards.

Stella

Re: Startx works, but sddm/lightdm/xdm doesn't

[Felix Miata]

John Goerzen composed on 2022-02-28 22:11 (UTC-0600):

> Interestingly, purging xserver-xorg-video-nouveau didn't change
> anything. 

That means you must have been /using/ the modesetting DIX driver.

> However, removing modesetting_drv.so from
> /usr/lib/xorg/modules/drivers did.  That solved the problem.

> But it didn't switch to nouveau; it went to fbdev.

You likely created a new problem. modesetting_drv.so is the default DIX for AMD,
Intel and NVidia GPUs. fbdev is unaccelerated, and won't support most common
widescreen display modes. Some apps won't run on it. I don't think Gnome will 
even
start using it. Using fbdev you can expect your PC to feel like it's running a
single core at 233MHz instead of 2000MHz or more on multiple cores.

I don't know that I've ever migrated an installation using SDDM to another PC
using a majorly different GPU. I use TDM or KDM3 on most installations, with a
rare few on LightDM or SDDM, whose themes I always have extreme negative
appreciation for.
-- 
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

Re: Startx works, but sddm/lightdm/xdm doesn't

[John Goerzen]

On Mon, Feb 28 2022, Felix Miata wrote:

> There are two nouveau drivers:
>
>   kernel device
>   display device
>   modesetting
>   nouveau
>
> Both possible full-function display device drivers depend on the nouveau 
> kernel
> driver (module). inxi -Gayz will show both. Try switching from the one in 
> current
> use to the other. Adding or purging xserver-xorg-video-nouveau is typically 
> the
> simplest way to switch between them. /etc/X11/xorg.conf.d/ can also be used to
> make the switch by explicitly declaring the chosen driver. The in-use display
> driver is announced in roughly half the lines in each Xorg.#.log.

Interestingly, purging xserver-xorg-video-nouveau didn't change
anything.  However, removing modesetting_drv.so from
/usr/lib/xorg/modules/drivers did.  That solved the problem.

But it didn't switch to nouveau; it went to fbdev.

But, since I also want to boot this drive on other machines that need
it, I can't just leave it that way.  It also leaves open the question of
why it worked fine in startx, or after logging in with sddm, which is
darn weird to me.

> Try disabling Plymouth, appending one of the following to the end of the linu 
> line
> after striking the E key at the Grub menu:

Thanks for the tip; no change there (I wasn't using the graphical stuff
anyhow).

> If none help, try appending your display's native mode & refresh instead, 
> e.g.:
>
>   video=1920x1080@60
>
> If this works, likely an edit to /etc/default/grub about graphics handling or
> theme, and regeneration of /boot/grub/grub.cfg, is indicated.

It's also already getting that right from EDID, so I'm pretty sure
that's not the issue.

Thanks again!

John

Re: Startx works, but sddm/lightdm/xdm doesn't

[Nicholas Geovanis]

On Mon, Feb 28, 2022, 3:43 PM John Goerzen  wrote:

> Hi,
>
> I have a system with a GeForce 1050 Ti on bullseye.
>
> On this system, if I log in as a regular user and run startx, everything
> works fine; KDE Plasma comes up and it's all good.
>
> But sddm doesn't work.  In fact, when it starts, it causes my monitor to
> go "no signal".  Oddly, though, if I can log in blindly, then once I hit
> enter after putting in my password, KDE will come up and work like it
> should.
>
> I also tried lightdm and xdm.  Both of them also had "no signal" when
> starting.
>
> It is using the nouveau driver.  There are no errors in Xorg.0.log,
> journalctl, dmesg, syslog, or the xsession log.  lspci doesn't show any
> other graphics adapter.  xrandr on the sddm session shows it detected
> the appropriate output at the appropriate resolution.  Xorg.0.log looks
> completely appropriate; detecting devices, setting them up, etc.
>
> If I boot the same drive on a different box with Intel graphics, sddm
> works fine.
>
> This is a fresh bullseye install.
>
> A am utterly baffled; I'd think at least xdm should work!
>

I had something similar happen with Debian 8 a long time ago. It turned out
to be because the driver/firmware/grafx-chipset had the wrong idea about
the monitor's available resolutions and modes. It was using too high a
resolution.

Thanks,
>
> John
>
>

Re: XFCE: ALT-F1 shows the wrong menu on Debian 11

[José Luis González]

On Mon, 28 Feb 2022 22:44:18 +
Ralph Katz  wrote:

> On 2/27/22 14:32, José Luis González wrote:
> > Hi,

Hi,

> > Upon upgrading to Debian 11, the ALT+F1 key, which is assigned as a
> > shortcut to xfce4-popup-applicationsmenu, according to XFCE's settings,
> > no longer shows the applications menu and instead the app menu button
> > on my panel appears pressed without the menu unfolded. A second key
> > press shows the CTRL-ESC (xfdesktop --menu) menu, not the app menu.
> > 
> > What's going on? I'm suffering from the same in both machines I have
> > with Debian 11.
> > 
> > 
> 
> 
> On my Bullseye 11.2 XFCE Dell laptop, I need Fn-ALT-F1 to do that even 
> though ALT-F1 is specified in Settings -> Keyboard -> Application Shortcuts.

I just tried this and it doesn't work for me (nothing happens when I
add Fn).

Re: Startx works, but sddm/lightdm/xdm doesn't

[Felix Miata]

John Goerzen composed on 2022-02-28 15:43 (UTC-0600):

> I have a system with a GeForce 1050 Ti on bullseye.

> On this system, if I log in as a regular user and run startx, everything
> works fine; KDE Plasma comes up and it's all good.

> But sddm doesn't work.  In fact, when it starts, it causes my monitor to
> go "no signal".  Oddly, though, if I can log in blindly, then once I hit
> enter after putting in my password, KDE will come up and work like it
> should.

> I also tried lightdm and xdm.  Both of them also had "no signal" when
> starting.

> It is using the nouveau driver. 

There are two nouveau drivers:

kernel device
display device
modesetting
nouveau

Both possible full-function display device drivers depend on the nouveau kernel
driver (module). inxi -Gayz will show both. Try switching from the one in 
current
use to the other. Adding or purging xserver-xorg-video-nouveau is typically the
simplest way to switch between them. /etc/X11/xorg.conf.d/ can also be used to
make the switch by explicitly declaring the chosen driver. The in-use display
driver is announced in roughly half the lines in each Xorg.#.log.

> There are no errors in Xorg.0.log,
> journalctl, dmesg, syslog, or the xsession log.  lspci doesn't show any
> other graphics adapter.  xrandr on the sddm session shows it detected
> the appropriate output at the appropriate resolution.  Xorg.0.log looks
> completely appropriate; detecting devices, setting them up, etc.

> If I boot the same drive on a different box with Intel graphics, sddm
> works fine.

> This is a fresh bullseye install.

> A am utterly baffled; I'd think at least xdm should work!
Try disabling Plymouth, appending one of the following to the end of the linu 
line
after striking the E key at the Grub menu:

plymouth=0
noplymouth
plymouth.enable=0

If none help, try appending your display's native mode & refresh instead, e.g.:

video=1920x1080@60

If this works, likely an edit to /etc/default/grub about graphics handling or
theme, and regeneration of /boot/grub/grub.cfg, is indicated.
-- 
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

Re: What should I put inside the file called wlan0?

[Brian]

On Tue 01 Mar 2022 at 10:36:54 +1300, Ash Joubert wrote:

> On 01/03/2022 09:25, Nicolas George wrote:
> > In typical domestic settings, the wifi password is on a post-it near the
> > access point, safe from neighbors but convenient for guests.
> 
> For even greater convenience, especially for those of us who inflict long
> randomly-generated passphrases on our guests, you can provide a QR code that
> works with most mobile devices:
> 
> qrencode -s 20 -o wifi.png "WIFI:S:Your Wifi SSID;T:WPA;P:Your Wifi
> Passphrase;;"

Very nice. Does that work when the code is onscreen and/or printed on
paper?

-- 
Brian.

Re: What should I put inside the file called wlan0?

[Brian]

On Mon 28 Feb 2022 at 21:25:01 +0100, Nicolas George wrote:

> Stella Ashburne (12022-02-28):
> > I quote from Debian Wiki (https://wiki.debian.org/WiFi/HowToUse) :
> > 
> > "Restrict the permissions of /etc/network/interfaces, to prevent pre-shared 
> > key (PSK) disclosure (alternatively use a separate config file such as 
> > /etc/network/interfaces.d/wlan0 on newer Debian versions): "
> 
> First, ask yourself: Do you really need to protect your wifi password
> from the users of your own computer?

Aren't you assuming the machine is always in a safe environment?

> In typical domestic settings, the wifi password is on a post-it near the
> access point, safe from neighbors but convenient for guests.

My guests' eyes glaze over when they are given a 63 character random 
passphrase to type in :). Then they put me to the trouble of mailing
to them.

-- 
Brian.

Re: Authentication failed after su-

[Bob McGowan]

On 2/28/22 13:09, Dan Ritter wrote:

sudo su - -l -c "rest of the line"


Some comments on this, without knowing just how it failed:

1.  There is no reason I can see to using both 'sudo' and 'su' 
together.  By default, they both let you run a command as the root user.


2.  Using both '-' and '-l' with su is redundant, they do almost (per 
the man page) the same thing.  The man page suggests '-l' is better due 
to reduced side effects.


3.  The -c option provides a means to tell su to run a specific 
command.  So the string 'rest of the line' generates an error stating 
'command not found' if run as is.  You need to supply this part of the 
line so processing can be duplicated and evaluated.


If I insert an 'echo' before the word 'rest', there is no error.

Hence, the actual error is needed, as well as the actual command being run.

Bob

Re: Authentication failed after su-

[Dan Ritter]

Stella Ashburne wrote: 
> > Sent: Tuesday, March 01, 2022 at 5:09 AM
> > From: "Dan Ritter" 
> > To: "Stella Ashburne" 
> > Cc: debian-user@lists.debian.org
> > Subject: Re: Authentication failed after su-
> >
> > Stella Ashburne wrote:
> > > sudo su - -l -c "rest of the line"
> > >
> > > It didn't work
> >
> > Copy and paste the actual error; they contain real information
> > to help us figure out what is happening.
> 
> In a terminal, I typed:
> 
> username@hostname:~$ su -l -c "wpa_passphrase JupiterRising 1234567890 > 
> /etc/wpa_supplicant/wpa_supplicant.conf"
> Password:
> su: Authentication failure

That means that you failed to give the root password.

-dsr-

Re: systemd user@###.service failure causing 90 sec delays during boot, login

[Nicholas Geovanis]

On Mon, Feb 28, 2022 at 4:45 PM KCB Leigh  wrote:

> I installed Debian 11 (Bullseye) with GNOME 3.38.5 (Wayland), LINUX kernel
> Linux version 5.10.0-11-amd64 (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110,
> GNU ld 2.35.2) #1 SMP Debian 5.10.92-1 (2022-01-18) on a USB stick, and am
> using it with an ACER Aspire 514 laptop.
>
> This operating system has worked excellently for months, but for the last
> 2 days has suddenly been taking a very long time to boot.  The cause of the
> delay can be seen from the syslog:
>

Hi -
A shot in the dark:
Make sure that name resolution is working the same now as it was before the
problem.
That could include some or all of these:
Order of name resolution in the /etc/resolv.conf file.
Sources of name-service information in the /etc/nsswitch.conf file.
Loss of network contact with a responsive DNS server which makes a
difference.


> 
> I would be very grateful for any information about how to resolve this
> (apart from re-installing the system) or even any reference that might give
> information about how I might resolve this problem.  (I have looked at the
> systemd.service man page, but although I have experience with the unix
> command line, I have only been using Debian since Nov. 2021 & am not
> familiar with its system administration, & I could find no information
> there about this problem.)
>
>

Re: systemd user@###.service failure causing 90 sec delays during boot, login

[Greg Wooledge]

On Mon, Feb 28, 2022 at 10:28:49PM +, KCB Leigh wrote:
> This operating system has worked excellently for months, but for the last 2 
> days has suddenly been taking a very long time to boot.  The cause of the 
> delay can be seen from the syslog:

Obvious question 1: what changed 2 days ago?

> Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Main process 
> exited, code=exited, status=1/FAILURE
> Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing 
> process 1144 (gpgconf) with signal SIGKILL.

That UID is extremely low.  Do you intentionally use users with UIDs in
the 119 range, perhaps because of interoperability with some other system
on your network?  Or because of a /home file system that has been migrated
from a different OS?

I would check to see which user(s) are defined with this UID.  Maybe there's
a collision.

awk -F: '$3 == 119' /etc/passwd

That should show them all, if they're all defined in /etc/passwd.  If you've
got NIS or LDAP or something like that, then you may want to check there
as well.  I could easily see a new package being installed, which creates
a new user, which grabs the first unused UID from the users in /etc/passwd,
but doesn't realize that UID 119 is actually used in your network password
database.

> Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing 
> process 1145 (awk) with signal SIGKILL.
> Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing 
> process 1174 (dirmngr) with signal SIGKILL.

Certainly looks like you're actually logging in with this UID.

Another thing I'd check, just based on past messages that I've seen here,
is the ownership/permissions of the / directory.

ls -ld /

It should be owned by root, group root, and have 755 perms.  If that
ownership gets changed for some reason, it causes all kinds of mess.

Re: What should I put inside the file called wlan0?

[Brian]

On Mon 28 Feb 2022 at 21:17:25 +0100, Stella Ashburne wrote:

> Dearie,
> 
> > Sent: Tuesday, March 01, 2022 at 4:08 AM
> > From: "Brian" 
> > To: debian-user@lists.debian.org
> > Subject: Re: What should I put inside the file called wlan0?
> >
> >
> > You do not want just anyone to read /etc/network/interfaces?
> >
> >   chmod 600 /etc/network/interfaces
> >
> That's the recommended step in said Wiki.
> 
> What's the default chmod value of /etc/network/interfaces?

Om all my systems:

brian@5740:~$ ls -l /etc/network/interfaces
-rw-r--r-- 1 root root 475 Nov  3 19:23 /etc/network/interfaces

-- 
Brian.

Re : Re: Afficher la phrase de passe pour LVM-encrypt au boot

[k6dedijon]

Cette astuce fonctionne assez souvent.

Autre piste, il existe un widget "indicateur de clavier" qui se place dans la 
tableau de bord et qui indique si Verr Num et/ou Verr Maj sont activés ou nom.
Attention, parfois il se place dans la boite à miniature dans laquelle il est 
peu visible.
La solution consiste à en mettre un autre dans la tableau de bord, puis à 
masquer celui de la boite à miniature.

Bon courage
Cassis


- Mail d'origine -
De: elguero eric 
À: debian-user-french@lists.debian.org
Envoyé: Mon, 28 Feb 2022 10:17:12 +0100 (CET)
Objet: Re: Afficher la phrase de passe pour LVM-encrypt au boot



un truc qui marche (parfois) : tu tapes
le mot de passe dans un éditeur puis
tu le copies/colles dans la fenêtre ou
le terminale qui le demande.


Le lundi 28 février 2022, 08:21:25 UTC+1, ORL  a écrit : 





Salut,

J'utilise lvm-encrypt sur mon laptop, mais il commence à présenter des 
faiblesses sur certaines touches, et je loupe régulièrement ma 
passphrase sans savoir pourquoi. Par ailleurs, il n'affiche pas si Caps 
Lock est locké ou non, donc un peu galère.

Est-ce qu'il est possible de faire en sorte que le mot de passe que je 
tape soit affiché (plutôt que de mettre des étoiles) ? Parce qu'en 
pratique, je ne taperai pas ce mot de passe si quelqu'un regarde par 
dessus mon épaule (c'est pas trop mon contexte) ? Ou a minima de 
switcher pour voir ce que j'ai tapé ?

Merci.

Re: XFCE: ALT-F1 shows the wrong menu on Debian 11

[Ralph Katz]

On 2/27/22 14:32, José Luis González wrote:

Hi,

Upon upgrading to Debian 11, the ALT+F1 key, which is assigned as a
shortcut to xfce4-popup-applicationsmenu, according to XFCE's settings,
no longer shows the applications menu and instead the app menu button
on my panel appears pressed without the menu unfolded. A second key
press shows the CTRL-ESC (xfdesktop --menu) menu, not the app menu.

What's going on? I'm suffering from the same in both machines I have
with Debian 11.





On my Bullseye 11.2 XFCE Dell laptop, I need Fn-ALT-F1 to do that even 
though ALT-F1 is specified in Settings -> Keyboard -> Application Shortcuts.


Hope this helps.

Ralph

Re: What should I put inside the file called wlan0?

[Ash Joubert]

On 01/03/2022 09:25, Nicolas George wrote:

In typical domestic settings, the wifi password is on a post-it near the
access point, safe from neighbors but convenient for guests.


For even greater convenience, especially for those of us who inflict 
long randomly-generated passphrases on our guests, you can provide a QR 
code that works with most mobile devices:


qrencode -s 20 -o wifi.png "WIFI:S:Your Wifi SSID;T:WPA;P:Your Wifi 
Passphrase;;"


Kind regards,

--
Ash Joubert 
Director
Transient Software Limited 
New Zealand

systemd user@###.service failure causing 90 sec delays during boot, login

[KCB Leigh]

I installed Debian 11 (Bullseye) with GNOME 3.38.5 (Wayland), LINUX kernel 
Linux version 5.10.0-11-amd64 (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld 
2.35.2) #1 SMP Debian 5.10.92-1 (2022-01-18) on a USB stick, and am using it 
with an ACER Aspire 514 laptop.

This operating system has worked excellently for months, but for the last 2 
days has suddenly been taking a very long time to boot.  The cause of the delay 
can be seen from the syslog:

Feb 28 10:09:30 cpe-67-241-65-193 systemd[1]: Started GNOME Display Manager.
    (The above is the last line on the verbose boot log printed on screen 
during boot process)
    (omitted next lines from network manager, & kernel, about setting up 
network & loading audio firmware, etc.)
Feb 28 10:09:31 cpe-67-241-65-193 systemd[1]: Created slice User Slice of UID 
119.
Feb 28 10:09:31 cpe-67-241-65-193 systemd[1]: Starting User Runtime Directory 
/run/user/119...
Feb 28 10:09:31 cpe-67-241-65-193 systemd[1]: Finished User Runtime Directory 
/run/user/119.
Feb 28 10:09:31 cpe-67-241-65-193 systemd[1]: Starting User Manager for UID 
119...
...
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Main process 
exited, code=exited, status=1/FAILURE
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 
1144 (gpgconf) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 
1145 (awk) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 
1174 (dirmngr) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 
1144 (gpgconf) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 
1145 (awk) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 
1174 (dirmngr) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Failed with 
result 'exit-code'.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Unit process 
1174 (dirmngr) remains running after unit stopped.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: Failed to start User Manager for 
UID 119.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: Started Session c1 of user 
Debian-gdm.

    The login screen appeared at 10:11:09:

Feb 28 10:11:09 cpe-67-241-65-193 systemd[1]: Startup finished in 51.017s 
(kernel) + 1min 48.624s (userspace) = 2min 39.642s.

The same 90 sec delay then occurs again after any user enters his password (at 
10:11:46):

Feb 28 10:11:46 cpe-67-241-65-193 systemd[1]: Created slice User Slice of UID 
1003.
Feb 28 10:11:46 cpe-67-241-65-193 systemd[1]: Starting User Runtime Directory 
/run/user/1003...
Feb 28 10:11:46 cpe-67-241-65-193 systemd[1]: Finished User Runtime Directory 
/run/user/1003.
Feb 28 10:11:46 cpe-67-241-65-193 systemd[1]: Starting User Manager for UID 
1003...

Feb 28 10:13:16 cpe-67-241-65-193 systemd[1]: user@1003.service: Main process 
exited, code=exited, status=1/FAILURE
 (as above)
Feb 28 10:13:16 cpe-67-241-65-193 systemd[1]: Failed to start User Manager for 
UID 1003.
Feb 28 10:13:16 cpe-67-241-65-193 systemd[1]: Started Session 2 of user kcl.

The first 90 sec. delay only occurs on initial startup, & the second only when 
any user logs in (the problem is not particular to UID1003, but occurs for all 
UIDs 100[0-5].  Once the machine has booted & the user is logged in, it 
functions normally with no observable problems.

I do not know what  caused this, but it occurred right after I:
   > allowed the installation of the latest software update (some lib files, 
the names of which I unfortunately did not record)
   > installed the ufw firewall package.

I would be very grateful for any information about how to resolve this (apart 
from re-installing the system) or even any reference that might give 
information about how I might resolve this problem.  (I have looked at the 
systemd.service man page, but although I have experience with the unix command 
line, I have only been using Debian since Nov. 2021 & am not familiar with its 
system administration, & I could find no information there about this problem.)

Re: Authentication failed after su-

[Stella Ashburne]

Dearie

> Sent: Tuesday, March 01, 2022 at 5:09 AM
> From: "Dan Ritter" 
> To: "Stella Ashburne" 
> Cc: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
> Stella Ashburne wrote:
> > sudo su - -l -c "rest of the line"
> >
> > It didn't work
>
> Copy and paste the actual error; they contain real information
> to help us figure out what is happening.
>

To avoid confusion, I shall use the original example provided by Debian Wiki 
(https://wiki.debian.org/WiFi/HowToUse) which is:

su -l -c "wpa_passphrase myssid my_very_secret_passphrase > 
/etc/wpa_supplicant/wpa_supplicant.conf"

In a terminal, I typed:

username@hostname:~$ su -l -c "wpa_passphrase JupiterRising 1234567890 > 
/etc/wpa_supplicant/wpa_supplicant.conf"
Password:
su: Authentication failure

The output is Authentication failure

Best regards.

Stella

Re: What should I put inside the file called wlan0?

[Stella Ashburne]

Dearie

> Sent: Tuesday, March 01, 2022 at 4:21 AM
> From: to...@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
> On Mon, Feb 28, 2022 at 09:20:07PM +0100, to...@tuxteam.de wrote:
>
> [...]
>
> > (in Debian, at least) /etc/network/interfaces is only root-readable. So
>
If that's the case, why would Debian Wiki recommend to chmod as follows?

# chmod 0600 /etc/network/interfaces

(source: https://wiki.debian.org/WiFi/HowToUse)

Best regards.

Stella

Re: What should I put inside the file called wlan0?

[Stella Ashburne]

Dearie

> Sent: Tuesday, March 01, 2022 at 4:20 AM
> From: to...@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
>
> However, if I remember your original post correctly, there were security
> reasons mentioned (about a possibly world readable /etc/network/interfaces,
> and splitting out an .../interfaces.d/wlan0 as a fix), Note that by default
> (in Debian, at least) /etc/network/interfaces is only root-readable. So
> this wouldn't be the reason you'd want to do the split (there are other
> valid reasons, though).
>
According to Debian Wiki WiFi How To Use 
(https://wiki.debian.org/WiFi/HowToUse), the reason for doing the split is:

(sic) Restrict the permissions of /etc/network/interfaces, to prevent 
pre-shared key (PSK) disclosure

Best regards.

Stella

Startx works, but sddm/lightdm/xdm doesn't

[John Goerzen]

Hi,

I have a system with a GeForce 1050 Ti on bullseye.

On this system, if I log in as a regular user and run startx, everything
works fine; KDE Plasma comes up and it's all good.

But sddm doesn't work.  In fact, when it starts, it causes my monitor to
go "no signal".  Oddly, though, if I can log in blindly, then once I hit
enter after putting in my password, KDE will come up and work like it
should.

I also tried lightdm and xdm.  Both of them also had "no signal" when
starting.

It is using the nouveau driver.  There are no errors in Xorg.0.log,
journalctl, dmesg, syslog, or the xsession log.  lspci doesn't show any
other graphics adapter.  xrandr on the sddm session shows it detected
the appropriate output at the appropriate resolution.  Xorg.0.log looks
completely appropriate; detecting devices, setting them up, etc.

If I boot the same drive on a different box with Intel graphics, sddm
works fine.

This is a fresh bullseye install.

A am utterly baffled; I'd think at least xdm should work!

Thanks,

John

Re: Authentication failed after su-

[Dan Ritter]

Stella Ashburne wrote: 
> sudo su - -l -c "rest of the line"
> 
> It didn't work

Copy and paste the actual error; they contain real information
to help us figure out what is happening.

-dsr-

Re: Probleem met bijlage in Thunderbird

[Paul van der Vlis]

Op 21-02-2022 om 16:57 schreef Diederik de Haas:

On maandag 21 februari 2022 15:59:49 CET Paul van der Vlis wrote:

[  143.814165] thunderbird[3486]: segfault at 0 ip 7f01008dce47 sp
7fffcb4e7880 error 6 in libxul.so[7f00fd72+4f32000]
[  143.814173] Code: 1f 40 00 48 83 ec 08 80 3d d5 08 60 04 00 74 02 58
c3 c6 05 ca 08 60 04 01 48 8d 05 f9 0f 15 03 48 8b 0d bc f5 55 04 48 89
01  04 25 00 00 00 00 8f 01 00 00 e8 21 dd e4 fc 66 0f 1f 84 00 00


Een segfault is een bug dat gerapporteerd dient te worden


Maar het is wel een erg vage segfault...
Hij treed op de ene machine op, en op de andere niet.

De machine waar hij wel optreedt heeft ECC memory, zou het daarmee te 
maken kunnen hebben?  Lijkt me niet.


Groet,
Paul


--
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl/

Re: What should I put inside the file called wlan0?

[Nicolas George]

Stella Ashburne (12022-02-28):
> I quote from Debian Wiki (https://wiki.debian.org/WiFi/HowToUse) :
> 
> "Restrict the permissions of /etc/network/interfaces, to prevent pre-shared 
> key (PSK) disclosure (alternatively use a separate config file such as 
> /etc/network/interfaces.d/wlan0 on newer Debian versions): "

First, ask yourself: Do you really need to protect your wifi password
from the users of your own computer?

In typical domestic settings, the wifi password is on a post-it near the
access point, safe from neighbors but convenient for guests.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: What should I put inside the file called wlan0?

[tomas]

On Mon, Feb 28, 2022 at 09:20:07PM +0100, to...@tuxteam.de wrote:

[...]

> (in Debian, at least) /etc/network/interfaces is only root-readable. So

This is wrong (note to self: double-check things. Gah). Sorry for any
confusion.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: What should I put inside the file called wlan0?

[tomas]

On Mon, Feb 28, 2022 at 08:59:03PM +0100, Stella Ashburne wrote:
> Dearie,
> 
> Thanks for your reply.
> 
> > Sent: Tuesday, March 01, 2022 at 3:10 AM
> > From: to...@tuxteam.de
> > To: debian-user@lists.debian.org
> > Subject: Re: What should I put inside the file called wlan0?
> >
> >
> > So if you have this in your /etc/network/interfaces somewhere:
> >
> >   ...
> >   ## Bahn ICE
> >   iface wlan0 inet dhcp
> > wireless-essid WIFIonICE
> > wireless-mode Auto
> >   ...
> >
> > (it's actually my current setting, BTW :) you could swap that
> > out to some file under interfaces.d.
> 
> The contents of my current /etc/network/interfaces file are:
> 
> # The primary network interface
> allow-hotplug wlp3s0
> iface wlp7s0 inet static
> wpa-ssid JupiterRising
> wpa-psk {a long string of alphanumeric characters}
> address 192.168.1.99/24
> gateway 192.168.1.1
> # dns-* options are implemented by the resolvconf package, if 
> installed
> dns-nameservers 1.1.1.1 8.8.8.8
> 
> Are you saying that I can cut out the above contents and paste them into a 
> file called wlp7s0 (whose path is /etc/network/interfaces.d/)?

That's how I read that man page, yes (disclaimer: I haven't actually
tried).

However, if I remember your original post correctly, there were security
reasons mentioned (about a possibly world readable /etc/network/interfaces,
and splitting out an .../interfaces.d/wlan0 as a fix), Note that by default
(in Debian, at least) /etc/network/interfaces is only root-readable. So
this wouldn't be the reason you'd want to do the split (there are other
valid reasons, though).

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: What should I put inside the file called wlan0?

[Stella Ashburne]

Dearie,

> Sent: Tuesday, March 01, 2022 at 4:08 AM
> From: "Brian" 
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
>
> You do not want just anyone to read /etc/network/interfaces?
>
>   chmod 600 /etc/network/interfaces
>
That's the recommended step in said Wiki.

What's the default chmod value of /etc/network/interfaces?

Best regards.

Stella

Re: Authentication failed after su-

[Stella Ashburne]

Dearie

Thanks for your offer of help; however.

> Sent: Tuesday, March 01, 2022 at 3:10 AM
> From: "Andrew M.A. Cater" 
> To: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
>
> If you use sudo: prefix the above command with sudo
>
> It may be that you need
>
> su - -l -c "rest of the line"
>
> su alone doesn't always get you root equivalent: the default changed a while
> ago now so su - is needed.

Firstly, I tried the command:

sudo su - -l -c "rest of the line"

It didn't work

Next, I tried:

sudo su- -l -c "rest of the line"

It didn't work either

On the third try, I typed:

sudo -i

followed by "rest of the line" (I ignored -l -c because if I included them, the 
"rest of the line" wouldn't be executed. Besides I don't know what the 
arguments -l -c stand for.)

Alternatively, one could type:

sudo su


Best regards.

Stella

Re: What should I put inside the file called wlan0?

[Brian]

On Mon 28 Feb 2022 at 19:49:32 +0100, Stella Ashburne wrote:

> I quote from Debian Wiki (https://wiki.debian.org/WiFi/HowToUse) :
> 
> "Restrict the permissions of /etc/network/interfaces, to prevent pre-shared 
> key (PSK) disclosure (alternatively use a separate config file such as 
> /etc/network/interfaces.d/wlan0 on newer Debian versions): "
> 
> What should I put in the file called wlan0? Said wiki does not provide 
> examples.

You do not want just anyone to read /etc/network/interfaces?

  chmod 600 /etc/network/interfaces

-- 
Brian.

Re: What should I put inside the file called wlan0?

[Stella Ashburne]

Dearie,

Thanks for your reply.

> Sent: Tuesday, March 01, 2022 at 3:10 AM
> From: to...@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
>
> So if you have this in your /etc/network/interfaces somewhere:
>
>   ...
>   ## Bahn ICE
>   iface wlan0 inet dhcp
> wireless-essid WIFIonICE
> wireless-mode Auto
>   ...
>
> (it's actually my current setting, BTW :) you could swap that
> out to some file under interfaces.d.

The contents of my current /etc/network/interfaces file are:

# The primary network interface
allow-hotplug wlp3s0
iface wlp7s0 inet static
wpa-ssid JupiterRising
wpa-psk {a long string of alphanumeric characters}
address 192.168.1.99/24
gateway 192.168.1.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 1.1.1.1 8.8.8.8

Are you saying that I can cut out the above contents and paste them into a file 
called wlp7s0 (whose path is /etc/network/interfaces.d/)?

Best regards.

Stella

Re: Re (2): Archiving on optical media

[John Conover]

pe...@easthope.ca writes:
> From: rhkra...@gmail.com
> Date: Mon, 28 Feb 2022 09:52:35 -0500
> > What has been your experience with reliability of SD cards for backup?
> 
> My explanation was ambiguous.  =8~|  The primary medium here is SD.  
> The backup is optical. 
> 
> The oldest SD card I have was purchased about 2012.  The label was 
> NextTech. Purchased via eBay from a seller in Ontario or Quebec.  It's 
> been reformatted 2 or 3 times over the years and still works.  =8~)  
> Recently parts of some files disappeared or showed garbled 
> information. The card has served better than I expected.  Probably due 
> for retirement.  =8~)
> 
> Since 2012 I've purchased three Kingston 8 GB SDs.  Two are used in 
> mobile phones; one is system store in a OLPC XO 1.5.  Those SDs 
> continue to work with no apparent difficulties.
> 
> General policy.  Buy only name brands: Kingston, SanDisk, Lexar & etc. 
> Buy only from local businesses maintaining a reputation in the 
> marketplace.  Noname cards only waste time and money.
>

Also, make sure the SD manufacturing technology has wear
leveling. Many cheap SDs do NOT. (They are manufactured in out dated
facilities.)

If used for backups, write the file, then write the check sum of the
file, (perhaps using something linke md5sum(1),) to the disk, with the
same file name plus an extension, so that md5sum can be used to check
the integrity of the data before installing the backup.

For long term archival data, use a new SD, and write once, (perhaps on
multiple SDs, for file reconstruction; any corrupt file on one SD can
probably be retrieved from another SD.) Store at STP for the plastics.

> 
> Regardless of reliability of a specific medium, data preservation 
> comes from a good backup system.  =8~)
>

John

-- 

John Conover, cono...@panix.com, http://www.johncon.com/

Re: Authentication failed after su-

[Andrew M.A. Cater]

On Mon, Feb 28, 2022 at 07:54:39PM +0100, Stella Ashburne wrote:
> According to https://wiki.debian.org/WiFi/HowToUse,
> 
> "Use the WPA passphrase to calculate the correct WPA PSK hash for your SSID 
> by altering the following example"
> 
> the command to type is
> 
> su -l -c "wpa_passphrase myssid my_very_secret_passphrase > 
> /etc/wpa_supplicant/wpa_supplicant.conf"
> 
> The output of the terminal is: Authentication failed
> 
> Any solution(s) please?
> 
> Best regards.
> 
> Stella
>

If you use sudo: prefix the above command with sudo

It may be that you need

su - -l -c "rest of the line"

su alone doesn't always get you root equivalent: the default changed a while
ago now so su - is needed.

All the very best, as ever,

Andy Cater 

Re: What should I put inside the file called wlan0?

[tomas]

On Mon, Feb 28, 2022 at 07:49:32PM +0100, Stella Ashburne wrote:
> I quote from Debian Wiki (https://wiki.debian.org/WiFi/HowToUse) :
> 
> "Restrict the permissions of /etc/network/interfaces, to prevent pre-shared 
> key (PSK) disclosure (alternatively use a separate config file such as 
> /etc/network/interfaces.d/wlan0 on newer Debian versions): "
> 
> What should I put in the file called wlan0? Said wiki does not provide 
> examples.

man 5 interfaces provides the relevant bits: by default, the files
in interfaces.d are (textually) included in interfaces. So each
of those files can basically have a "snippet" of what you would
put in interfaces (to avoid losing sanity, whole stanzas seem
recommendable).

So if you have this in your /etc/network/interfaces somewhere:

  ...
  ## Bahn ICE
  iface wlan0 inet dhcp
wireless-essid WIFIonICE
wireless-mode Auto
  ...

(it's actually my current setting, BTW :) you could swap that
out to some file under interfaces.d.

Cheers
-- 
t


signature.asc
Description: PGP signature

Authentication failed after su-

[Stella Ashburne]

According to https://wiki.debian.org/WiFi/HowToUse,

"Use the WPA passphrase to calculate the correct WPA PSK hash for your SSID by 
altering the following example"

the command to type is

su -l -c "wpa_passphrase myssid my_very_secret_passphrase > 
/etc/wpa_supplicant/wpa_supplicant.conf"

The output of the terminal is: Authentication failed

Any solution(s) please?

Best regards.

Stella

What should I put inside the file called wlan0?

[Stella Ashburne]

I quote from Debian Wiki (https://wiki.debian.org/WiFi/HowToUse) :

"Restrict the permissions of /etc/network/interfaces, to prevent pre-shared key 
(PSK) disclosure (alternatively use a separate config file such as 
/etc/network/interfaces.d/wlan0 on newer Debian versions): "

What should I put in the file called wlan0? Said wiki does not provide examples.

Best regards.

Stella

Re: getting a regular user to dump core when a program crashes

[songbird]

Greg Wooledge wrote:
...
> Well, that's interesting.  You *can* specify an absolute directory by
> this mechanism.  I guess I learned something today.

  :)


> So, what exactly was the complaint?  That songbird shot themselves in
> the foot by specifying an absolute directory for core dumps that wasn't
> writable by the user generating the core dumps?  Well, don't do that.

  um, no, go back and read my initial post.


  songbird

Re (2): Archiving on optical media

[peter]

From: rhkra...@gmail.com
Date: Mon, 28 Feb 2022 09:52:35 -0500
> What has been your experience with reliability of SD cards for backup?

My explanation was ambiguous.  =8~|  The primary medium here is SD.  
The backup is optical. 

The oldest SD card I have was purchased about 2012.  The label was 
NextTech. Purchased via eBay from a seller in Ontario or Quebec.  It's 
been reformatted 2 or 3 times over the years and still works.  =8~)  
Recently parts of some files disappeared or showed garbled 
information. The card has served better than I expected.  Probably due 
for retirement.  =8~)

Since 2012 I've purchased three Kingston 8 GB SDs.  Two are used in 
mobile phones; one is system store in a OLPC XO 1.5.  Those SDs 
continue to work with no apparent difficulties.

General policy.  Buy only name brands: Kingston, SanDisk, Lexar & etc. 
Buy only from local businesses maintaining a reputation in the 
marketplace.  Noname cards only waste time and money. 

Regardless of reliability of a specific medium, data preservation 
comes from a good backup system.  =8~)

Regards,... P.





-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W

Re (2): Archiving on optical media

[peter]

From:   "Thomas Schmitt" 
Date:   Mon, 28 Feb 2022 08:55:40 +0100
> Beware of "Combo" drives. Make sure the product description mentions
> _write_ speed for BD-RE and BD-R, not only read speed for BD-ROM.
> ("Combo" drives are usually a bit cheaper than real BD burners.)

Critical point, thanks.

> Buy from a seller who takes defective or wrongly chosen hardware back
> without offering much resistance.

First stop will be PC Galore which mostly sells used equipment.  
They're knowledgeable and honest. If nothing there is suitable will go 
to the big retailers where sales clerks can be unhelpful.

> The quality of new drives varies much more individually than by the
> brand or manufacturer. (Even 80 EUR are not enough to pay for a
> convincing quality management in the factory.)

Your instructions in 2019 were used with a DVD burner at work.
Completely effective.  Thanks.  The current interest is to establish 
backups at home.

Considering the earlier experience and modest quantity of data (< 2 
GB) another DVD drive might be adequate.  Will see what is at PC 
Galore.

Thx, ... P.

-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W

Re: getting a regular user to dump core when a program crashes

[Greg Wooledge]

On Mon, Feb 28, 2022 at 11:41:27AM -0500, The Wanderer wrote:
> By default, yes, that's the case. However, from songbird's original
> post:
> 
>  i have the following set in my /etc/sysctl.conf:
>  
>  # core file location and file name format
>  kernel.core_pattern=/crash/core.%u.%E.%p
> 
> That appears to be a kernel parameter which defines the path and
> filename of the core file.
> 
> I imagine that this was set in order to be able to specify a filename
> other than the default, with relevant information about the dumping
> process (and avoiding the problem of multiple such files overwriting one
> another), and that the syntax of the kernel parameter in question is
> such that you have to specify the full path to the file.

OK... let's see.  I tried several dead end man pages (why the hell
don't they have comprehensive SEE ALSO sections?!).  Then gave up, then
decided to try "man -k sysctl".  This led me to discover that there is
a sysctl(2) page in addition to sysctl(8) (the latter does NOT link
to the former).

sysctl(2) mentions core_pattern and says to see core(5).

core(5) says:

   By default, a core dump file is  named  core,  but  the  /proc/sys/ker‐
   nel/core_pattern file (since Linux 2.6 and 2.4.21) can be set to define
   a template that is used to name core dump files.  The template can con‐
   tain  % specifiers which are substituted by the following values when a
   core file is created:

No mention is made of specifying *directories* by this mechanism, except
for the %E specifier, which is documented as:

   %E  Pathname of executable, with slashes ('/') replaced by exclama‐
   tion marks ('!') (since Linux 3.0).

Funny how they went out of their way to change slashes to a different
character, isn't it.

But songbird appears to believe that one can put *actual* slashes in this
kernel config file, and have them be treated as an absolute pathname.
Despite this not being mentioned in the man page as far as I could see,
and despite defying all of my experience with core files.

So let's test whether this works.  My testing is occurring on bullseye
running this kernel:

unicorn:~$ uname -r
5.10.0-11-amd64

And here's the test:

unicorn:~$ sudo sh -c 'echo /tmp/core > /proc/sys/kernel/core_pattern'
[sudo] password for greg: 
unicorn:~$ ls -ld core
ls: cannot access 'core': No such file or directory
unicorn:~$ ./coredump
Segmentation fault (core dumped)
unicorn:~$ ls -ld core /tmp/core
ls: cannot access 'core': No such file or directory
-rw--- 1 greg greg 249856 Feb 28 12:16 /tmp/core

Well, that's interesting.  You *can* specify an absolute directory by
this mechanism.  I guess I learned something today.

So, what exactly was the complaint?  That songbird shot themselves in
the foot by specifying an absolute directory for core dumps that wasn't
writable by the user generating the core dumps?  Well, don't do that.

Re: getting a regular user to dump core when a program crashes

[Reco]

Hi.

On Mon, Feb 28, 2022 at 11:41:27AM -0500, The Wanderer wrote:
> On 2022-02-28 at 11:35, Greg Wooledge wrote:
> 
> > On Mon, Feb 28, 2022 at 11:25:13AM -0500, songbird wrote:
> >
> >> >> me@ant(14)~$ ulimit -a
> >> >> real-time non-blocking time  (microseconds, -R) unlimited
> >> >> core file size  (blocks, -c) unlimited
> >> 
> >>   i had accomplished the ulimit change already, but the lack of 
> >> the proper permission on the output directory meant that a core
> >> file would not be generated.
> > 
> > What is an "output directory"?  Core files are dumped in the process's
> > *working* directory, which is "where you are when you run it".
> 
> By default, yes, that's the case. However, from songbird's original
> post:
> 
>  i have the following set in my /etc/sysctl.conf:
>  
>  # core file location and file name format
>  kernel.core_pattern=/crash/core.%u.%E.%p
> 
> That appears to be a kernel parameter which defines the path and
> filename of the core file.

It can do that too. Quoting the relevant part of the kernel's
documentation (admin-guide/sysctl/kernel.rst.gz) :

If the first character of the pattern is a '|', the kernel will treat
the rest of the pattern as a command to run.  The core dump will be
written to the standard input of that program instead of to a file.


For instance, one can use systemd-coredump (needs a package installed,
though) to write backtraces to journald.
Or, one can specify /dev/null in kernel.core_pattern, thus preventing
core dumps from creating regardless of user's shell limits.


> and that the syntax of the kernel parameter in question is
> such that you have to specify the full path to the file.

When used in such way, it's also prevents user's processes to spam an
entire filesystem with coredumps.

Reco

Re: getting a regular user to dump core when a program crashes

[songbird]

The Wanderer wrote:
> On 2022-02-28 at 11:35, Greg Wooledge wrote:
>> On Mon, Feb 28, 2022 at 11:25:13AM -0500, songbird wrote:
>>
>>> >> me@ant(14)~$ ulimit -a
>>> >> real-time non-blocking time  (microseconds, -R) unlimited
>>> >> core file size  (blocks, -c) unlimited
>>>=20
>>>   i had accomplished the ulimit change already, but the lack of=20
>>> the proper permission on the output directory meant that a core
>>> file would not be generated.
>>=20
>> What is an "output directory"?  Core files are dumped in the process's
>> *working* directory, which is "where you are when you run it".
>
> By default, yes, that's the case. However, from songbird's original
> post:
>
> i have the following set in my /etc/sysctl.conf:
>=20
> # core file location and file name format
> kernel.core_pattern=3D/crash/core.%u.%E.%p
>
> That appears to be a kernel parameter which defines the path and
> filename of the core file.

  yes!  i don't know which process is crashing to cause 
the lockup.  it is nice if all core files from crashes are 
located in one spot so i can find them without having to 
hunt for them.  this may not really work if the process isn't
actually dumping core, but we'll see if i can figure out 
which one it is.


> I imagine that this was set in order to be able to specify a filename
> other than the default, with relevant information about the dumping
> process (and avoiding the problem of multiple such files overwriting one
> another), and that the syntax of the kernel parameter in question is
> such that you have to specify the full path to the file.


  songbird

Re: Grisbi.

[Sébastien NOBILI]

Sylvie,

Attention de bien garder la liste en copie de vos réponses (ça permettra 
à

d'autres membres d'intervenir dans la discussion).

Le 2022-02-28 13:58, Sylvie TARDIVEL a écrit :
J'ai fait un essai de télécharger le paquet source 
[grisbi_2.0.5-1.debian.tar.xz]. Ensuite, j'ai un message "Que doit 
faire Firefox avec ce fichier ?" "Ouvrir" est sélectionner par défaut. 
Je fais OK et c'est à partir de là que je ne sais plus quoi faire.


Ça c'est l'archive avec le code source. C'est utile aux développeurs.

Pour installer un paquet dans Debian, il faut utiliser le gestionnaire 
de paquets.

C'est une application qui permet d'installer/désinstaller des logiciels.

Il y en a plusieurs. Ce que je vais proposer ne correspondra peut-être 
pas à

ce que vous avez à disposition sur votre système.

Si votre bureau affiche "Activités" dans le coin en haut à gauche, alors 
placez

votre souris dessus.

Ensuite tapez "logiciels". Normalement vous devriez trouver une 
application (qui
s'appelle "logiciels") qui vous permettra de chercher Grisbi et 
l'installer.


Si vous ne trouvez pas "logiciels", vous pouvez essayer "synaptic". Là 
aussi vous

pourrez chercher et installer Grisbi.

Si aucun des deux ne fonctionne, alors on essayera de trouver autre 
chose.


Sébastien

Re: getting a regular user to dump core when a program crashes

[The Wanderer]

On 2022-02-28 at 11:35, Greg Wooledge wrote:

> On Mon, Feb 28, 2022 at 11:25:13AM -0500, songbird wrote:
>
>> >> me@ant(14)~$ ulimit -a
>> >> real-time non-blocking time  (microseconds, -R) unlimited
>> >> core file size  (blocks, -c) unlimited
>> 
>>   i had accomplished the ulimit change already, but the lack of 
>> the proper permission on the output directory meant that a core
>> file would not be generated.
> 
> What is an "output directory"?  Core files are dumped in the process's
> *working* directory, which is "where you are when you run it".

By default, yes, that's the case. However, from songbird's original
post:

 i have the following set in my /etc/sysctl.conf:
 
 # core file location and file name format
 kernel.core_pattern=/crash/core.%u.%E.%p

That appears to be a kernel parameter which defines the path and
filename of the core file.

I imagine that this was set in order to be able to specify a filename
other than the default, with relevant information about the dumping
process (and avoiding the problem of multiple such files overwriting one
another), and that the syntax of the kernel parameter in question is
such that you have to specify the full path to the file.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Archiving on SD cards (was: Re: Archiving on optical media; was Re: Archiving content of a directory on a DVD-R.)

[Chris Ramsden]

Monday, February 28, 2022, 2:52:35 PM, rhkramer wrote:

> On Monday, February 28, 2022 12:37:49 AM pe...@easthope.ca wrote:
>> Backing data in a 4 or 16 GB SD card is a modest requirement.
>> PC Galore might have a drive in stock.  http://www.pcgalore.com/
> What has been your experience with reliability of SD cards for backup?

Mine has been bad. I have accumulated several dead SD cards, yet over many 
years, I can think of only one USB memory device failing. 
 
USB and SD memory devices are based on similar (if not identical) flash 
technology, are they not? 
 
Under this assumption, I'd guess that the USB interface is rather more robust 
than that found in SD cards. SD cards seem to be fine if installed and left 
there (IP cameras, dashcams, phones) but fail when handled. And yes, I am aware 
of ESD (electrostatic discharge) issues and take steps to minimize risk. 
 
I wouldn't trust my data to SD cards.   
-- 
Regards,
Chris

Re: getting a regular user to dump core when a program crashes

[Greg Wooledge]

On Mon, Feb 28, 2022 at 11:25:13AM -0500, songbird wrote:
> >> me@ant(14)~$ ulimit -a
> >> real-time non-blocking time  (microseconds, -R) unlimited
> >> core file size  (blocks, -c) unlimited
> 
>   i had accomplished the ulimit change already, but the lack of 
> the proper permission on the output directory meant that a core
> file would not be generated.

What is an "output directory"?  Core files are dumped in the process's
*working* directory, which is "where you are when you run it".  Quite
often that will be $HOME, unless you opened a shell and changed
directory somewhere else, before running a command.  Or unless the
process is invoked by a dot-desktop file that specifies a special
working directory.  Or a systemd unit file is written which specifies
a WorkingDirectory= in it.  And so on.

unicorn:~$ cat coredump.c
main() {
char *ptr = 0;
*ptr = 'x';
return 0;
}
unicorn:~$ gcc -o coredump coredump.c
coredump.c:1:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
1 | main() {
  | ^~~~
unicorn:~$ cd tmp
unicorn:~/tmp$ ../coredump >/var/tmp/outputfile
Segmentation fault (core dumped)
unicorn:~/tmp$ ls -ld core
-rw--- 1 greg greg 249856 Feb 28 11:33 core

Here, the process's binary file lives in /home/greg, its working directory
is /home/greg/tmp, and its stdout has been redirected to a file in
/var/tmp.  The core file goes in /home/greg/tmp, the working directory.

Re: getting a regular user to dump core when a program crashes

[songbird]

Greg Wooledge wrote:
...
> Just put 'ulimit -c unlimited' into the appropriate dot file to put
> things back to how they used to be.
>
> This changed a *really* long time ago.  I don't know exactly when, or
> how.  It pissed me off too, but it's the norm now, because everything
> has been dumbed down for the common user.
>
> unicorn:~$ grep ulimit .profile 
> ulimit -c unlimited   # Argh!  Since when does this default to 0?
>
>
> For me, .profile is the correct file, because I login on a console and
> use startx.  If you login via a GUI DM, some other file will be the
> correct one (possibly .xsessionrc but I haven't tested it).


did you miss this?

>> me@ant(14)~$ ulimit -a
>> real-time non-blocking time  (microseconds, -R) unlimited
>> core file size  (blocks, -c) unlimited

  i had accomplished the ulimit change already, but the lack of 
the proper permission on the output directory meant that a core
file would not be generated.

  also, i wanted to make sure that all programs running would
be able to dump core upon crashing because i have some kind of
strange lock up going on and i'm not sure what it is coming 
from.  so i want all processes for all users to be able to
be able to be recorded if it happens again.  just trying to 
catch this if i can.  it happens once in a while.  not too 
often.


  songbird

Re: getting a regular user to dump core when a program crashes

[Greg Wooledge]

On Mon, Feb 28, 2022 at 10:01:05AM -0500, songbird wrote:
> 
> i had some fun trying to figure out why a regular user could not
> dump a core file

Just put 'ulimit -c unlimited' into the appropriate dot file to put
things back to how they used to be.

This changed a *really* long time ago.  I don't know exactly when, or
how.  It pissed me off too, but it's the norm now, because everything
has been dumbed down for the common user.

unicorn:~$ grep ulimit .profile 
ulimit -c unlimited # Argh!  Since when does this default to 0?


For me, .profile is the correct file, because I login on a console and
use startx.  If you login via a GUI DM, some other file will be the
correct one (possibly .xsessionrc but I haven't tested it).

Re: VM windows, toujours et encore

[BERTRAND Joël]

NoSpam a écrit :
> Mais as tu essayé avec le driver ide en lieu et place de virtio ou sata ?

Oui ;-)

Même motif, même punition.

La, je suis en train d'essayer sans accélération matérielle (QEMU TCG).
Ça met mon i9 à terre... et :

"Votre ordinateur a besoin d'un pilote de media qui est manquant." et
gnagnagna et gnagnagna...

J'ai testé IDE (pas SATA) et sans KVM.

JKB

getting a regular user to dump core when a program crashes

[songbird]

i had some fun trying to figure out why a regular user could not
dump a core file and i had all the settings figured out.  since it
was a silly and obvious thing but it stumped me for a bit i 
figured it would be worth sharing.  :)


the answer is at the end...


using Debian testing.


i have my kernel boot line set to:

systemd.dump_core=true


i have these lines in /etc/security/limits.conf:

roothardcoreunlimited
rootsoftcoreunlimited
*   softcoreunlimited
*   hardcoreunlimited


i have the following set in my /etc/sysctl.conf:

# core file location and file name format
kernel.core_pattern=/crash/core.%u.%E.%p


if i run a program with a known issue (divide by zero) the
core file shows up where it should be if the program is run
by root, but not when a normal user runs it.


what am i missing or what have i screwed up?

root(17)~# ./f
Floating point exception (core dumped)
root(18)~# ls /crash
total 112
-rw--- 1 root root 282624 Feb 28 09:32 'core.0.!root!f.2123'



none of my .bashrc/.profile or etc have anything limited in them
for core file dumps


$ ulimit -a
ulimit -a
real-time non-blocking time  (microseconds, -R) unlimited
core file size  (blocks, -c) unlimited
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 30998
max locked memory   (kbytes, -l) 1000392
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 30998
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited


turns out it was as simple as the directory permissions on
/crash.

once i set those to allow the proper access then the crashes
would show up.  for some reason i thought that a crashing
program would have systemd or root handling the saving of 
the core file and so a user would not need special access
to where the core file was landing.


$ ls /crash
total 228
-rw--- 1 root root 282624 Feb 28 09:48 'core.0.!root!f.2537'
-rw--- 1 me   me   282624 Feb 28 09:49 'core.1000.!home!me!f.2546'


  songbird

Re: VM windows, toujours et encore

[BERTRAND Joël]

m...@ekimia.fr a écrit :
> 
> Le 28/02/2022 à 14:57, BERTRAND Joël a écrit :
>> m...@ekimia.fr a écrit :
>>>
>>> Bonjour ,
>>>
>>> Si cela peut te dépanner , on utilisee une VM virtualBox W10 toute prete
>>> , les débutants aiment.
>>>
>>> https://ekimia.fr/windows10vm/
>> Je vais essayer. Ça se passe comment pour les licences ?
>>
>> JKB
> 
> Il n'y en a pas et ce n'est fonctionnellement pas nécessaire d'en mettre
> une , mais tu peux en trouver sur rakuten a 1€
> 

Si je peux utiliser les miennes, ça me va.

JKB

Archiving on SD cards (was: Re: Archiving on optical media; was Re: Archiving content of a directory on a DVD-R.)

[rhkramer]

On Monday, February 28, 2022 12:37:49 AM pe...@easthope.ca wrote:
> Backing data in a 4 or 16 GB SD card is a modest requirement.
> PC Galore might have a drive in stock.  http://www.pcgalore.com/

What has been your experience with reliability of SD cards for backup?

Re: VM windows, toujours et encore

[didier gaumet]

Je ne peux pas t'apporter de solution magique mais compte-tenu de tes
déboires, potentiellement tout indice est bon à prendre:
j'ai luen diagonale mais en gros un gars qui voulait passer de W7
(émulé KVM) à W10 se vautrait systématiquement jusqu'à ce qu'il change
le type de proc pour un plus basique et désactive l'accel matérielle
(Qemu sans KVM) durant la migration. Il a donc pu migrer et a ensuite
rétabli sa conf d'origine (proc d'origine et KVM)
https://ubuntuforums.org/showthread.php?t=2289210

Re: VM windows, toujours et encore

[NoSpam]

Mais as tu essayé avec le driver ide en lieu et place de virtio ou sata ?

Le 28/02/2022 à 14:44, BERTRAND Joël a écrit :

NoSpam a écrit :

Peut être ceci peu aider

https://simgunz.org/posts/2021-12-12-boot-windows-partition-from-linux-kvm/

Ben non... Mais merci tout de même.

Récapitulons.

J'ai sur mon poste de travail VirtualBox et virt-manager. Sur une
machine de dev que je viens de redémarrer , j'ai un XEN (Dom0 NetBSD
avec 16 Go de mémoire et un i7 4790.).

Toutes ces virtualisations fonctionnent. Dans Virtualbox et
virt-manager, j'ai un eComStation et du Win7 embedded (entre autres, il
y a aussi du XP et des trucs plus bizarres à base de L4). Sur mon xen,
j'ai une foultitude de machines de test en domU (NetBSD, OpenBSD,
Devuan, Windows 7). Mon XEN est capable d'utiliser des disques réseaux
ou des disques locaux. J'ai tenté l'installation de W10 sur les deux
(disques réseau et disques locaux). Je viens de vérifier, tous ces OS
sont capables de démarrer soit en BIOS soit en EFI.

Sur toutes ces machines (xen, kvm et virtualbox), j'arrive à installer
sans aucun problème toutes les versions de W7 que j'ai sous la main (32
bits, 64 bits, embedded 64 bits). Je suis incapable d'installer W10 ou
de migrer de 7 à 10. Naturellement, j'ai les CD originaux avec les
licences. Là, je suis en train de télécharger un Windows 8.1 depuis chez
Microsoft pour essayer d'installer cette version, il paraît que le soft
de Cadence fonctionne sous 8.1, mais je suis dans ma campagne avec un
débit internet très limité (200 ko/s). J'aurai peut-être l'image iso
tard ce soir.

W10, quelle que soit la machine virtuelle me répond toujours qu'il n'y
a pas de disque utilisable, que les disques soient configurés en SATA ou
en Virtio. Même avec le passthrough de XEN, W10 refuse de s'installer,
il manque toujours un fichu pilote. Je ne peux pas installer les drivers
virtio (même en ligne de commande, ça échoue). Si encore je savais quel
était ce pilote, on avancerait. Tout ce que je comprends, c'est qu'il ne
trouve pas de disque, mais pourquoi donc ? Dans le cas où je tente une
mise à jour de W7 vers 10, le disque est partitionné et formaté par W7
qui s'en contente !

Je comprends qu'il faille un pilote pour un disque en virtio, mais pas
pour un disque en SATA. J'ai essayé tous les chipsets, du 440 au Q35, le
résultat est toujours le même. J'ai viré toutes les choses bizarres
comme les ballons de mémoire, même résultat.

Bref, je n'arrive pas à isoler le problème et je ne vois pas ce que ma
configuration aurait de spécial. Plus je lis la doc sur internet et plus
je me dis que je fais tout correctement. J'ai ressorti XEN parce que je
voulais voir si l'image sur un disque local fonctionnait mieux, ce n'est
pas le cas. Il ne faut quand même pas un pilote spécifique pour un CPU
virtuel ?

Bien cordialement,

JKB

Re: VM windows, toujours et encore

[mm]

Le 28/02/2022 à 14:57, BERTRAND Joël a écrit :

m...@ekimia.fr a écrit :


Bonjour ,

Si cela peut te dépanner , on utilisee une VM virtualBox W10 toute prete
, les débutants aiment.

https://ekimia.fr/windows10vm/

Je vais essayer. Ça se passe comment pour les licences ?

JKB


Il n'y en a pas et ce n'est fonctionnellement pas nécessaire d'en mettre 
une , mais tu peux en trouver sur rakuten a 1€


--
--
Michel Memeteau

Ekimia ( https://ekimia.fr )

Directeur

tel:0624808051

Address :
620 avenue de la roche fourcade
13400 Aubagne
France

Re: VM windows, toujours et encore

[BERTRAND Joël]

m...@ekimia.fr a écrit :
> 
> Le 28/02/2022 à 13:13, BERTRAND Joël a écrit :
>>
>> Mais j'aimerais bien. Que ce soit sous VirtualBox ou virt-manager, le
>> résultat est le même : il manque toujours un pilote sans savoir lequel.
> 
> 
> Bonjour ,
> 
> Si cela peut te dépanner , on utiliser une VM virtualBox W10 toute Prete
> , les débutants aiment.
> 
> https://ekimia.fr/windows10vm/

Je vais essayer. Ça se passe comment pour les licences ?

JKB

Re: VM windows, toujours et encore

[mm]

Le 28/02/2022 à 13:13, BERTRAND Joël a écrit :


Mais j'aimerais bien. Que ce soit sous VirtualBox ou virt-manager, le
résultat est le même : il manque toujours un pilote sans savoir lequel.



Bonjour ,

Si cela peut te dépanner , on utiliser une VM virtualBox W10 toute Prete 
, les débutants aiment.


https://ekimia.fr/windows10vm/

--
--
Michel Memeteau

Ekimia ( https://ekimia.fr )

Directeur

tel:0624808051

Address :
620 avenue de la roche fourcade
13400 Aubagne
France

Re: VM windows, toujours et encore

[BERTRAND Joël]

NoSpam a écrit :
> Peut être ceci peu aider
> 
> https://simgunz.org/posts/2021-12-12-boot-windows-partition-from-linux-kvm/

Ben non... Mais merci tout de même.

Récapitulons.

J'ai sur mon poste de travail VirtualBox et virt-manager. Sur une
machine de dev que je viens de redémarrer , j'ai un XEN (Dom0 NetBSD
avec 16 Go de mémoire et un i7 4790.).

Toutes ces virtualisations fonctionnent. Dans Virtualbox et
virt-manager, j'ai un eComStation et du Win7 embedded (entre autres, il
y a aussi du XP et des trucs plus bizarres à base de L4). Sur mon xen,
j'ai une foultitude de machines de test en domU (NetBSD, OpenBSD,
Devuan, Windows 7). Mon XEN est capable d'utiliser des disques réseaux
ou des disques locaux. J'ai tenté l'installation de W10 sur les deux
(disques réseau et disques locaux). Je viens de vérifier, tous ces OS
sont capables de démarrer soit en BIOS soit en EFI.

Sur toutes ces machines (xen, kvm et virtualbox), j'arrive à installer
sans aucun problème toutes les versions de W7 que j'ai sous la main (32
bits, 64 bits, embedded 64 bits). Je suis incapable d'installer W10 ou
de migrer de 7 à 10. Naturellement, j'ai les CD originaux avec les
licences. Là, je suis en train de télécharger un Windows 8.1 depuis chez
Microsoft pour essayer d'installer cette version, il paraît que le soft
de Cadence fonctionne sous 8.1, mais je suis dans ma campagne avec un
débit internet très limité (200 ko/s). J'aurai peut-être l'image iso
tard ce soir.

W10, quelle que soit la machine virtuelle me répond toujours qu'il n'y
a pas de disque utilisable, que les disques soient configurés en SATA ou
en Virtio. Même avec le passthrough de XEN, W10 refuse de s'installer,
il manque toujours un fichu pilote. Je ne peux pas installer les drivers
virtio (même en ligne de commande, ça échoue). Si encore je savais quel
était ce pilote, on avancerait. Tout ce que je comprends, c'est qu'il ne
trouve pas de disque, mais pourquoi donc ? Dans le cas où je tente une
mise à jour de W7 vers 10, le disque est partitionné et formaté par W7
qui s'en contente !

Je comprends qu'il faille un pilote pour un disque en virtio, mais pas
pour un disque en SATA. J'ai essayé tous les chipsets, du 440 au Q35, le
résultat est toujours le même. J'ai viré toutes les choses bizarres
comme les ballons de mémoire, même résultat.

Bref, je n'arrive pas à isoler le problème et je ne vois pas ce que ma
configuration aurait de spécial. Plus je lis la doc sur internet et plus
je me dis que je fais tout correctement. J'ai ressorti XEN parce que je
voulais voir si l'image sur un disque local fonctionnait mieux, ce n'est
pas le cas. Il ne faut quand même pas un pilote spécifique pour un CPU
virtuel ?

Bien cordialement,

JKB

Re: VM windows, toujours et encore

[NoSpam]

Peut être ceci peu aider

https://simgunz.org/posts/2021-12-12-boot-windows-partition-from-linux-kvm/

Le 28/02/2022 à 13:55, NoSpam a écrit :


Le 28/02/2022 à 13:45, BERTRAND Joël a écrit :

NoSpam a écrit :

As tu téléchargé l'iso virtio-drivers ?

https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md 


Oui.

J'ai essayé les iso suivantes :

virtio-win-0.1.172.iso
virtio-win-0.1.208.iso
virtio-win-0.1.215.iso

Même motif, même punition.


As tu installé les virtio-guest.exe dans la VM W7 avant de migrer ? 
Aussi de certaines lectures, lorsque W10 est installé à partir de 
l'ISO il faut avoir en parallèle le CD virtio afin de rajouter les 
drivers, je ne sais pas si tu l'as installé ainsi.


Toujours est il que mon W10 tourne avec les drivers SCSI sans avoir eu 
besoin d'utiliser l'ISO virtio. Essaye:


. W7 => ide puis passe en SCSI
. Installe les drivers guest de github
. Update en W10

Si tu as déjà la VM W10:

. passe en ide
. Installe les drivers guest de github
. passe en SCSI

Re: VM windows, toujours et encore

[NoSpam]

Le 28/02/2022 à 13:45, BERTRAND Joël a écrit :

NoSpam a écrit :

As tu téléchargé l'iso virtio-drivers ?

https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md

Oui.

J'ai essayé les iso suivantes :

virtio-win-0.1.172.iso
virtio-win-0.1.208.iso
virtio-win-0.1.215.iso

Même motif, même punition.


As tu installé les virtio-guest.exe dans la VM W7 avant de migrer ? 
Aussi de certaines lectures, lorsque W10 est installé à partir de l'ISO 
il faut avoir en parallèle le CD virtio afin de rajouter les drivers, je 
ne sais pas si tu l'as installé ainsi.


Toujours est il que mon W10 tourne avec les drivers SCSI sans avoir eu 
besoin d'utiliser l'ISO virtio. Essaye:


. W7 => ide puis passe en SCSI
. Installe les drivers guest de github
. Update en W10

Si tu as déjà la VM W10:

. passe en ide
. Installe les drivers guest de github
. passe en SCSI

--
Daniel

Re: VM windows, toujours et encore

[BERTRAND Joël]

NoSpam a écrit :
> As tu téléchargé l'iso virtio-drivers ?
> 
> https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md

Oui.

J'ai essayé les iso suivantes :

virtio-win-0.1.172.iso
virtio-win-0.1.208.iso
virtio-win-0.1.215.iso

Même motif, même punition.

JKB

Re: Grisbi.

[Sébastien NOBILI]

Bonjour Sylvie,

Si ce n'est pas déjà fait, je vous conseille de vous abonner à cette 
liste pour être sûre de
recevoir les réponses (ici les gens ont l'habitude de répondre à la 
liste et donc on risque

de vous perdre en route).

Ça se passe là : https://lists.debian.org/debian-user-french/


On 2/28/22 17:53, Sylvie TARDIVEL wrote:

Bonjour.
Je souhaite télécharger Grisbi sur un ordinateur portable sous Debian,
mais je ne comprends pas comment l'enregistrer.


Grisbi (version 2) est disponible dans Debian. Pour l'installer, il 
"suffit" d'installer

le paquet "grisbi".

Est-ce que vous savez installer un paquet en utilisant le gestionnaire 
de paquets du système ?


Sébastien

Re: VM windows, toujours et encore

[NoSpam]

As tu téléchargé l'iso virtio-drivers ?

https://github.com/virtio-win/virtio-win-pkg-scripts/blob/master/README.md

Je viens de modifier ma VM W10 d'ide en virtio => no boot device found. 
En SATA prcontre, c'est OK


Le 28/02/2022 à 13:13, BERTRAND Joël a écrit :

ajh-valmer a écrit :

On Monday 28 February 2022 12:22:36 BERTRAND Joël wrote:

J'ai réussi à installer un Windows 7 64 bits (un vrai avec une licence)
dans kvm/qemu.
JKB

Je ne réponds pas au problème, désolé,
quitte à payer la licence, autant installer Windows 10,
ça peut augmenter les chances de réussite.

Mais j'aimerais bien. Que ce soit sous VirtualBox ou virt-manager, le
résultat est le même : il manque toujours un pilote sans savoir lequel.

Le problème est peut-être que les images sont en NFS, mais je ne vois
pas trop pourquoi.

JKB

Re: VM windows, toujours et encore

[BERTRAND Joël]

ajh-valmer a écrit :
> On Monday 28 February 2022 12:22:36 BERTRAND Joël wrote:
>> J'ai réussi à installer un Windows 7 64 bits (un vrai avec une licence)
>> dans kvm/qemu. 
>>  JKB
> 
> Je ne réponds pas au problème, désolé,
> quitte à payer la licence, autant installer Windows 10,
> ça peut augmenter les chances de réussite.

Mais j'aimerais bien. Que ce soit sous VirtualBox ou virt-manager, le
résultat est le même : il manque toujours un pilote sans savoir lequel.

Le problème est peut-être que les images sont en NFS, mais je ne vois
pas trop pourquoi.

JKB

Re: VM windows, toujours et encore

[NoSpam]

J'avais une VM W7 en veille: j'ai modifié le type de disk en virtio via 
virt-manager et ai démarré la VM. Aucun problème, Windows a installé les 
drivers Red Hat VirtIO SCSI Controller et SCSI Disk Device.


Je vais modifier une VM W10 et réaliser la même opération et reviendrai 
donner le résultat.


Le 28/02/2022 à 12:31, NoSpam a écrit :
Bonjour. J'ai réalisé x fois cette manipulation (W7 => W10) sans jamais 
rencontrer de problème, la différence est que je suis toujours en ide.


Le 28/02/2022 à 12:22, BERTRAND Joël a écrit :

Bonjour à tous,

Je suis vraiment désolé de revenir avec ce sujet, mais je patine...

J'ai réussi à installer un Windows 7 64 bits (un vrai avec une 
licence)

dans kvm/qemu. Disques en SATA (parce que virtio n'est pas reconnu
correctement, je suppose que c'est lié au fait que l'image de la VM est
sur un disque NFS). La machine est fonctionnelle.

Je tente maintenant une mise à jours vers Windows 10. Et j'ai à 
nouveau

le message "il manque un pilote, gnagnagna...". Mais  LEQUEL ?
Les disques sont toujours en SATA et rien n'a changé depuis la VM W7 qui
tourne dans la même configuration !... Comment avancer sur le problème ?

Bien cordialement,

JKB

Re: VM windows, toujours et encore

[BERTRAND Joël]

NoSpam a écrit :
> Bonjour. J'ai réalisé x fois cette manipulation (W7 => W10) sans jamais
> rencontrer de problème, la différence est que je suis toujours en ide.

Bonjour,

Là, c'est du SATA qui est exportée par la VM et je ne vois pas quel est
ce fichu driver qui pourrait manquer ! Je suis en train de disjoncter,
j'ai besoin de faire tourner un soft qui ne tourne pas sous W7 (on se
demande bien pourquoi, merci Cadence !).

JKB

Re: VM windows, toujours et encore

[ajh-valmer]

On Monday 28 February 2022 12:22:36 BERTRAND Joël wrote:
> J'ai réussi à installer un Windows 7 64 bits (un vrai avec une licence)
> dans kvm/qemu. 
>   JKB

Je ne réponds pas au problème, désolé,
quitte à payer la licence, autant installer Windows 10,
ça peut augmenter les chances de réussite.

Re: Grisbi.

[Grégoire Scano]

Bonjour Sylvie,

la liste debian-l10n-french est consacrée à la traduction de Debian en
français, je redirige donc ton message vers la liste debian-user-french
dédiée à l'aide les utilisateurs et dont les membres pourront sûrement
t'aider.

Merci de ne pas m'inclure dans le fil de discussion,
Grégoire

On 2/28/22 17:53, Sylvie TARDIVEL wrote:
> Bonjour.
> Je souhaite télécharger Grisbi sur un ordinateur portable sous Debian,
> mais je ne comprends pas comment l'enregistrer.
> Pouvez-vous m'aider, s'il vous plaît ?
> Salutations.
> Sylvie Tardivel.

Re: VM windows, toujours et encore

[NoSpam]

Bonjour. J'ai réalisé x fois cette manipulation (W7 => W10) sans jamais 
rencontrer de problème, la différence est que je suis toujours en ide.


Le 28/02/2022 à 12:22, BERTRAND Joël a écrit :

Bonjour à tous,

Je suis vraiment désolé de revenir avec ce sujet, mais je patine...

J'ai réussi à installer un Windows 7 64 bits (un vrai avec une licence)
dans kvm/qemu. Disques en SATA (parce que virtio n'est pas reconnu
correctement, je suppose que c'est lié au fait que l'image de la VM est
sur un disque NFS). La machine est fonctionnelle.

Je tente maintenant une mise à jours vers Windows 10. Et j'ai à nouveau
le message "il manque un pilote, gnagnagna...". Mais  LEQUEL ?
Les disques sont toujours en SATA et rien n'a changé depuis la VM W7 qui
tourne dans la même configuration !... Comment avancer sur le problème ?

Bien cordialement,

JKB

VM windows, toujours et encore

[BERTRAND Joël]

Bonjour à tous,

Je suis vraiment désolé de revenir avec ce sujet, mais je patine...

J'ai réussi à installer un Windows 7 64 bits (un vrai avec une licence)
dans kvm/qemu. Disques en SATA (parce que virtio n'est pas reconnu
correctement, je suppose que c'est lié au fait que l'image de la VM est
sur un disque NFS). La machine est fonctionnelle.

Je tente maintenant une mise à jours vers Windows 10. Et j'ai à nouveau
le message "il manque un pilote, gnagnagna...". Mais  LEQUEL ?
Les disques sont toujours en SATA et rien n'a changé depuis la VM W7 qui
tourne dans la même configuration !... Comment avancer sur le problème ?

Bien cordialement,

JKB

Re: Afficher la phrase de passe pour LVM-encrypt au boot

[elguero eric]

un truc qui marche (parfois) : tu tapes
le mot de passe dans un éditeur puis
tu le copies/colles dans la fenêtre ou
le terminale qui le demande.


Le lundi 28 février 2022, 08:21:25 UTC+1, ORL  a écrit : 





Salut,

J'utilise lvm-encrypt sur mon laptop, mais il commence à présenter des 
faiblesses sur certaines touches, et je loupe régulièrement ma 
passphrase sans savoir pourquoi. Par ailleurs, il n'affiche pas si Caps 
Lock est locké ou non, donc un peu galère.

Est-ce qu'il est possible de faire en sorte que le mot de passe que je 
tape soit affiché (plutôt que de mettre des étoiles) ? Parce qu'en 
pratique, je ne taperai pas ce mot de passe si quelqu'un regarde par 
dessus mon épaule (c'est pas trop mon contexte) ? Ou a minima de 
switcher pour voir ce que j'ai tapé ?

Merci.