Re: hangs at boot
On Thu, 2022-12-01 at 01:36 +0100, jd wrote: > On 2022-11-30 18:52, Hans wrote: > > Am Mittwoch, 30. November 2022, 18:33:49 CET schrieb jd: > > > > Try to deinstall cups and remove any usb cameras. I had had the problem, > > that > > cups detected an usb camera as a printer and then stopped booting. > > > I tried removing all cups packages, then it just stalled at Unattended > upgrades shutdown instead. > > So I tried disabling that, and now it stalls at Hostname Service. > > I'm guessing there's some underlying issue that hasn't got anything to > do with these services but I have no idea what it might be. The above, and presumably 'remote CUPS printers' in the earlier post, involve the network and related services like DNS or DHCP. -- Tixy
Re: Logout at apt upgrade
>> The one application I do avoid upgrading while it's running is >> Firefox, but that's mainly because it occasionally gives a new >> startup screen after an upgrade, and I want to read what it says. > > I take the risk and watch the thing going down in flames. I > admit that it gives me a strange feeling of satisfaction (I > might be a bit perverse, dunno). Last time this happened to me, Firefox insisted on restarting in the middle of a sequence of questions where I had already spent a fair bit of time filling things, so I was *really* annoyed but against all odds Firefox managed to restore the *full* state, including the content of the not-yet-submitted text boxes. Stefan
Re: Logout at apt upgrade
On Wed, Nov 30, 2022 at 02:36:57PM -0600, David Wright wrote: [...] > The only reasons I'd close down X are (a) a dist-upgrade from > oldstable to stable (and the like), That I do, too. > and (b) dpkg-reconfigure > console-setup and keyboard-configuration after I've been > tinkering with /etc/console-setup/remap.inc (which is > currently two years old). The latter may now be cargo-cult, but > I think it was advised in the past. I can't say much about that. > Like you, I admit to being an fvwm user (since 1996; never used > anything else). I actually had a panoramic round trip: twm, a bit of olwm (what can you do with 4 megabytes of RAM?), fvwm, several strange things in between, Gnome DE (with Metacity), then XFCE, then a couple of tiling WMs. So I *do* know for sure that fvwm is made for me :-) > The one application I do avoid upgrading while it's running is > Firefox, but that's mainly because it occasionally gives a new > startup screen after an upgrade, and I want to read what it says. I take the risk and watch the thing going down in flames. I admit that it gives me a strange feeling of satisfaction (I might be a bit perverse, dunno). > > Oh, something I forgot: besides no DM, my init system is still > > SysV. This might or might not contribute to stability through > > simplicity. > > No stability problems here with systemd. Nor with udev (apparently > from the same stable, sorry for the pun) [...] Udev I do have: a laptop with Linux and no udev is most probably no fun, I think. > And not forgetting the robustness of ext4, that allegedly > "unfashionable" filesystem. My most frequent cause of "crashes", > by far, is powercuts. Yay for ext4 :-) Cheeers -- t signature.asc Description: PGP signature
Re: hangs at boot
On Wed 30 Nov 2022 at 19:38:05 (-0500), Greg Wooledge wrote: > On Thu, Dec 01, 2022 at 01:36:05AM +0100, jd wrote: > > On 2022-11-30 18:52, Hans wrote: > > > Am Mittwoch, 30. November 2022, 18:33:49 CET schrieb jd: > > > > > > Try to deinstall cups and remove any usb cameras. I had had the problem, > > > that > > > cups detected an usb camera as a printer and then stopped booting. > > > > > > I tried removing all cups packages, then it just stalled at Unattended > > upgrades shutdown instead. > > > > So I tried disabling that, and now it stalls at Hostname Service. > > > > I'm guessing there's some underlying issue that hasn't got anything to do > > with these services but I have no idea what it might be. > > Have you considered the possibility it's *not* hung, but is in fact > booted and working? > > Have you tried pressing Enter a few times to see if a new login prompt > gets printed? Quite often I lose my Login: or Password: prompt, caused by something having the effect of sending Ctrl-A Ctrl-K to the console—a minor inconvenience that I've never bothered to investigate. But I've never managed to lose both the /etc/issue output and the Login: line. If pressing Enter doesn't work, it might be that the "main" VC is broken; perhaps try switching to another VC with Alt-→ and seeing if a Login: prompt appears there. OTOH perhaps the /sbin/agetty is completely screwed up. Cheers, David.
Re: hangs at boot
On Wed 30 Nov 2022 at 18:33:49 (+0100), jd wrote: > > I just installed debian 11, it keeps hanging at boot at the same place. > > It gets to > > [ OK ] Started Make remote CUPS printers available locally > > and then it hangs. I don't know where I should even begin to look in > order to diagnose this, anyone got any ideas? You could try booting into single-user mode, which shouldn't start many of the services. Then check out the logs from the previous boots to see what happened. Cheers, David.
Re: hangs at boot
On Thu, Dec 01, 2022 at 01:36:05AM +0100, jd wrote: > > On 2022-11-30 18:52, Hans wrote: > > Am Mittwoch, 30. November 2022, 18:33:49 CET schrieb jd: > > > > Try to deinstall cups and remove any usb cameras. I had had the problem, > > that > > cups detected an usb camera as a printer and then stopped booting. > > > I tried removing all cups packages, then it just stalled at Unattended > upgrades shutdown instead. > > So I tried disabling that, and now it stalls at Hostname Service. > > I'm guessing there's some underlying issue that hasn't got anything to do > with these services but I have no idea what it might be. Have you considered the possibility it's *not* hung, but is in fact booted and working? Have you tried pressing Enter a few times to see if a new login prompt gets printed?
Re: hangs at boot
On 2022-11-30 18:52, Hans wrote: Am Mittwoch, 30. November 2022, 18:33:49 CET schrieb jd: Try to deinstall cups and remove any usb cameras. I had had the problem, that cups detected an usb camera as a printer and then stopped booting. I tried removing all cups packages, then it just stalled at Unattended upgrades shutdown instead. So I tried disabling that, and now it stalls at Hostname Service. I'm guessing there's some underlying issue that hasn't got anything to do with these services but I have no idea what it might be. The camera was a noname one, and I do not own it any more. Just an idea Good luck! Thanks cheers jd
Nettoyage du spam : novembre 2022
Bonjour, Comme nous sommes en décembre, il est désormais possible de traiter les archives du mois de novembre 2022 des listes francophones. N'oubliez bien sûr pas d'ajouter votre nom à la liste des relecteurs pour que nous sachions où nous en sommes. Détails du processus de nettoyage du spam sur : https://wiki.debian.org/I18n/FrenchSpamClean Jean-Pierre Giraud
Re: tbird AND javamail both broken
On Tue 29 Nov 2022, at 16:52, David Wright wrote:
> On Sat 26 Nov 2022 at 19:45:37 (+), Gareth Evans wrote:
>> On Sat 26 Nov 2022, at 16:01, David Wright wrote:
>>> On Sat 19 Nov 2022 at 20:38:46 (+), Gareth Evans wrote:
On Sat 19 Nov 2022, at 20:15, Gareth Evans wrote:
[...]
> I'm not sure this is a Tb bug, just perhaps a "purist" way of doing
> things ...
I had assumed no blank line preceding a boundary was required as Tb still
processes the boundary without one, but
https://www.rfc-editor.org/rfc/rfc2049.html#page-15
suggests this is in fact a requirement. So perhaps a bug.
>>> I don't see where the RFC talks about blank lines.
>> It doesn't, save for one mention in the appendix, and that was sort of my
>> point...
>>> The text part of my emails (where they include an attachment) end
>>> as usual with the characters "David.", and that Newline
>>> is the last character of mine. It's then followed by another
>>> Newline which is the start of the Unique Boundary Marker.
>>> David.BOUNDARY MARKER
>>>↑ ↑↑ ↑
>>>minemarker's
>>> That pair of Newlines give the appearance of a blank line, which
>>> you assume is necessary.
>> Well... I meant "suggests" literally, because...
>> At the time of writing the message you refer to above, I had taken the
>> Appendix A example in RFC2049 ("[MIME] ... Conformance criteria and
>> examples") to be prescriptive by example (a "conformance example"!), given
>> blank line requirements are less than definitively spelt out there.
>> RFC1521, obsoleted by 2049, includes:
>> " 7.2 ... Each part
>> starts with an encapsulation boundary, and then contains a body part
>> consisting of header area, *a blank line*, and a body area ...
>> NO header fields are actually required in body parts. A body part that
>> starts with a blank line, therefore, is allowed ..."
>> https://www.rfc-editor.org/rfc/rfc1521
>
> Yes, but my post responded to, and only concerned, what lies between
> the end of the body area and the next boundary marker, whereas your
> quotation here from RFC1521 (which I haven't consulted) is about the
> beginning of the body area and any header preceding it.
Sorry, the point I was getting at didn't quite emerge!
I meant the fact that there are blank lines in the example
https://www.rfc-editor.org/rfc/rfc2049#page-15
before each boundary, as well as after all of the part field headers, it being
a conformance example, initially suggested requirement to me. But I now
realise that the example's blank lines before the part boundaries are there for
readability purposes, and form part of the sections including the text
preceding them. So the example leaves that at least for the reader to
interpret correctly.
I discovered last night that the BNF for the formal definitions, which you have
to string together to generate a blank line from concatenating CRLFs, appears
in RFC 2046. This isn't named or linked to in 2049's Abstract, as the other
docs in the latest MIME "set" are. I was skimming a bit and didn't see the
other references to it.
>> but this text does not appear in RFC2049, where the notion is merely implied
>> in a bracketed note in an example in an appendix, which also contains the
>> only appearance of "blank".
>> "Appendx A -- A Complex Multipart Example
>> [...]
>> --unique-boundary-1
>> ... Some text appears here ...
>> *[Note that the blank between the boundary and the start
>>of the text in this part means no header fields were
>>given* [...]
>
> Yes, there must be a blank line there because it either terminates
> this part's header fields (as shown next), or indicates that
> there are no header fields for this part (as shown above).
>> There are blank lines between part header fields and content - but this
>> requirement is implied rather than specified in terms, as it is in 1521.
>
> But surely you just quoted the specification:
>> " 7.2 ...
>> and then contains a body part
>> consisting of header area, *a blank line*, and a body area ...
That quote was from 1521:
>> RFC1521, obsoleted by 2049, includes:
>> " 7.2 ... Each part ..."
- whereas afaics, 2049 only offers the note in Appendix A, from which the
necessity for a blank line following part headers can be deduced, but you have
to think about it, and know that it needs to be thought about. I thought the
idea of RFCs was at least partly to explain things as well as specify. If so,
I don't think RFC2049 does this as well as 1521.
> (presumably that's your *emphasis* added).
Yes, I should have noted it.
>> I read somewhere else (which I now can't find) that a boundary must be
>> preceded by a CRLF, which is considered part of the boundary - but not
>> necessarily a blank line.
>
> It's in the next appendix:
Thank you.
> Appendix B -- Changes from RFC 1521, 1522, and 1590
>
> These documents are a revision of RFC 1521, 1522, and 1590. For the
> convenience
Re: Logout at apt upgrade
On Wed 30 Nov 2022 at 08:42:41 (+0100), to...@tuxteam.de wrote: > On Wed, Nov 30, 2022 at 12:36:43AM -0500, Felix Miata wrote: > > > I learned many many moons ago to not trust any update/upgrade process to not > > interfere with a running X session. I usually close apps I don't want data > > lost > > from before beginning an upgrade process. That usually means I log all the > > way out > > of X entirely, then start the upgrade from a vtty. The only reasons I'd close down X are (a) a dist-upgrade from oldstable to stable (and the like), and (b) dpkg-reconfigure console-setup and keyboard-configuration after I've been tinkering with /etc/console-setup/remap.inc (which is currently two years old). The latter may now be cargo-cult, but I think it was advised in the past. Like you, I admit to being an fvwm user (since 1996; never used anything else). The one application I do avoid upgrading while it's running is Firefox, but that's mainly because it occasionally gives a new startup screen after an upgrade, and I want to read what it says. > > What I have noticed in Debian that I do not at all like, is when I boot to > > multi-user.target for the specific purpose of apt or apt-get upgrading, > > even when > > systemctl get-default returns multi-user.target, that if the DM is > > upgraded, X > > gets started shortly following. :( This is above my paygrade (and I don't run a DM), but could this follow from Debian's policy (occasionally complained about), that installing a daemon will start it immediately at the end of the process of installation? > Oh, something I forgot: besides no DM, my init system is still > SysV. This might or might not contribute to stability through > simplicity. No stability problems here with systemd. Nor with udev (apparently from the same stable, sorry for the pun), which someone mentioned this morning. In my experience, the only time udev might have been blamed was during the lenny/squeeze transition, where mixing lenny kernels with squeeze's udev was specifically warned against in the Release Notes (which too many don't seem to read). That transition looks about the time that udev hitched its wagon to systemd (first mention of systemd in its changelog, default rules moved from /etc into /lib), but it could have been coincidental. > My important apps (Emacs, then Emacs, then dunno ;-) don't lose > data "just because the system goes down", so I'm pretty relaxed. And not forgetting the robustness of ext4, that allegedly "unfashionable" filesystem. My most frequent cause of "crashes", by far, is powercuts. > Still, it never happened to me, and I dist-upgrade roughly once > a week. Same here, but running stable, so I normally only have to "dist-" when the kernel is upgraded. Otherwise I upgrade within a few hours of packages hitting the mirrors. Cheers, David.
Re: Logout at apt upgrade
On 11/30/22, to...@tuxteam.de wrote: > On Wed, Nov 30, 2022 at 12:36:43AM -0500, Felix Miata wrote: > > [...] > >> What I have noticed in Debian that I do not at all like, is when I boot >> to >> multi-user.target for the specific purpose of apt or apt-get upgrading, >> even when >> systemctl get-default returns multi-user.target, that if the DM is >> upgraded, X >> gets started shortly following. :( > > Oh, something I forgot: besides no DM, my init system is still > SysV. This might or might not contribute to stability through > simplicity. I'm on SystemD and bounce between XFCE4 and LXQt. Mine has never done anything like this in many years of playing with anything Linux. At this second, I have bits of GNOME installed for themes. In the past, I've had more than that, but I must have moved away from those packages. A quick "apt-mark showinstall" says pinentry-gnome3 is the only GNOME3 named package currently installed. > My important apps (Emacs, then Emacs, then dunno ;-) don't lose > data "just because the system goes down", so I'm pretty relaxed. Once in a very rare while, upgrade will stall until I say yes or no when it asks if I want to restart exim and a second program that I can't remember. > Still, it never happened to me, and I dist-upgrade roughly once > a week. I run "apt-get upgrade". It will take me a few days to remember to do so, but I'll try both "apt upgrade" and dist-upgrade. Dist-upgrade was already a to-do item. Will be my first use of that one so who knows what else might possibly go wrong... or not. Wondering out loud as I exit Stage Right: Is there any kind of trace/strace or whatever that fancy deal is to see if that outputs anything? Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
RE: AHR Expo 2023Attendees list
Hi - Hope you are doing great, Are you interested to purchase the list? If yes, reply back as Send Pricing and Counts. Regards Catherine From: Catherine Gates Sent: Tuesday, November 22, 2022 9:27 AM To: debian-user@lists.debian.org Subject: AHR Expo 2023Attendees list I am reaching out because... Are you interested in purchasing AHR Expo 2023 Updated Attendees Database? Target Audience: - Contractors, Consulting Engineers, Mechanical Engineers, Architects, Wholesalers/Distributors, Importers/Exporters, Manufacturers Reps, OEM Designers & Engineers, Facility Engineers, Building Operations Managers, Publishers/Editors, HVACR Educators/Students, Public Utilities, Government Agencies, Purchasing Departments, Testing & Certification, Research & Development, Design/Build... Record in the list contains: Contact Name, Job Title, Company/Business Name, Complete Mailing Address, email, Telephone/Fax Number, Website/URL, Revenue, Employee Size, SIC Code, Industry. If you are interested to purchase reply back as "Send Counts and Pricing". Thank you Catherine Gates Marketing Director P.S If you're not interested, don't worry - I will not email you again about any of this!
Re: hangs at boot
Am Mittwoch, 30. November 2022, 18:33:49 CET schrieb jd: Try to deinstall cups and remove any usb cameras. I had had the problem, that cups detected an usb camera as a printer and then stopped booting. The camera was a noname one, and I do not own it any more. Just an idea Good luck! Hans > Hi! > > I just installed debian 11, it keeps hanging at boot at the same place. > > It gets to > > [ OK ] Started Make remote CUPS printers available locally > > and then it hangs. I don't know where I should even begin to look in > order to diagnose this, anyone got any ideas? > > > cheers > > jd
hangs at boot
Hi! I just installed debian 11, it keeps hanging at boot at the same place. It gets to [ OK ] Started Make remote CUPS printers available locally and then it hangs. I don't know where I should even begin to look in order to diagnose this, anyone got any ideas? cheers jd
Re: Copier plusieurs ISO sur une clé USB pour installer Debian
Bonjour, De mémoire ventoy n'aime pas les noms d'image ISO avec des espaces. Si c'est la cas il suffit de les enlever. Pour l'histoire mbr/gpt, il faut que le bios soi configuré de la même façon que la clé. Et enfin, pour le secure boot, il faut ajouter le secure boot de la clé depuis le bios si tu veux booter en mode secure boot Le 30 novembre 2022 10:05:17 GMT+01:00, Olivier a écrit : >Le mar. 29 nov. 2022 à 23:05, Jean Bernon a écrit : >> >> Sur cette machine est-ce qu'au moins le menu Ventoy s'affiche ou est-ce que >> ça bloque quand tu veux lancer un iso ? >Le menu Ventoy ne s'affiche pas: >j'ai un message fugace "invalid image" (de mémoire) à la place > >> Dans le 1er cas il peut y avoir un blocage au niveau de la configuration HP >> du boot . J'ai un vague souvenir de problème avec certains modèles HP qui >> bootent obstinément sur Windows. Pour savoir si le problème vient de Ventoy, >> as-tu essayé une clé usb simple avec un seul iso sur cette machine ? >> >La machine arrive à booter sur une clé "normale": c'est grâce à cette >méthode que j'ai pu installer Bullseye. >Une autre machine arrive à booter sur la clé Ventoy. > >Il y a visiblement une spécificité sur cette combinaison clé+machine >qui ne me saute pas aux yeux. >Un coup d'oeil rapide sur les 350 tickets ouverts sur le site github >de Ventoy ne m'a pas inspiré. > -- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
Re: Configuration conseillée de la console d'un serveur [RESOLU]
Après avoir installé les paquets console-setup et console-data, l'affichage et la saisie via la console semblent corrects. L'absence de ces paquets est peut-être consécutive au fichier preseed.cfg que j'ai utilisé pour initialiser cette machine: ce fichier preseed.cfg contient un tas de paramètres pour localiser la machine mais j'ai l'impression qu'ils sont ignorés pour une raison qui m'échappe. Le lun. 28 nov. 2022 à 21:22, Étienne Mollier a écrit : > > Bonjour Olivier, > > Olivier, on 2022-11-28: > > J'ai dernièrement installé un serveur Bullseye. > > Je m'y connecte très sporadiquement en direct (VGA/DVI + clavier) et > > par SSH le reste du temps. > > > > Je me rends aujourd'hui que sur ce serveur, les espaces insécables > > (produits par apt, par exemple) sont mal affichés en SSH (à la place > > de l'espace j'ai un caractère à la noix) mais correctement affichés > > quand je me connecte en direct (VGA+clavier). > > > > Avez-vous une documentation de référence sur la configuration de la > > console d'un serveur (sans interface graphique) ? > > Le réglage manquant n'est peut-être pas que du côté de la > console système. L'environnement de lancement du terminal qui > lui même va lancer le client ssh peut interférer. Si je lance > un xterm sans support de l'utf-8, j'ai: > > $ DEBFULLNAME='Étienne Mollier' LANG=C xterm > > [… changement de fenêtre …] > > (C)$ echo "$DEBFULLNAME" > Ãtienne Mollier > > Alors qu'avec support d'utf-8, j'observe plutôt: > > $ DEBFULLNAME='Étienne Mollier' LANG=C.UTF-8 xterm > > [… changement de fenêtre …] > > (C.UTF-8)$ echo "$DEBFULLNAME" > Étienne Mollier > > Je ne sais pas si c'est bien ça le problème, mais si ça peut > donner une piste… > > Bonne journée, :) > -- > Étienne Mollier > Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da > Sent from /dev/pts/2, please excuse my verbosity. > On air: RPWL - 3 Lights
Re: Debian-Installer: clavier US ou configuration manuelle ?
La piste PXE est effectivement très intéressante car elle supprime des étapes : je pense que je vais la suivre car j'ai déjà des éléments pour l'implémenter et lien fourni donne des repères. Même si c'est dommage d'en acheter un rien que pour ça, je pense que je vais aussi acheter un clavier USB US International. Le mer. 30 nov. 2022 à 10:44, Thomas Parmelan a écrit : > > Le lundi 28 novembre 2022 à 09:23, d'après > Olivier : > > > Je lance l'installation, en sélectionnant dans l'installeur Debian, > > les options Advanced Options puis Automated Install > > puis en fournissant l'URL de mon fichier preseed.cfg. > > Option C : faire démarrer l'ordinateur à installer en PXE, avec un > fichier de configuration PXE donnant l'URL du fichier preseed en > paramètre à l'installateur Debian. Il n'y a donc plus besoin de l'entrer > manuellement ;-) > > Plus d'informations => https://wiki.debian.org/PXEBootInstall > > -- > Thomas Parmelan >
Re: Exploring grep-dctrl
Le 11/30/22 à 4:02 PM, Yassine Chaouche a écrit : But even then, translation files might contain more than one entry for same package, maybe one for each (version x architecture) product. For eg.: $ grep-dctrl winbind -s Description-en /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_trusty-security_main_i18n_Translation-en Description-en: Samba winbind client library - development files Samba is an implementation of the SMB/CIFS protocol for Unix systems, providing support for cross-platform file and printer sharing with Microsoft Windows, OS X, and other Unix systems. . This package provides the development files (static library and headers) required for building applications against libwbclient, a library for client applications that interact via the winbind pipe protocol with a Samba winbind server. Description-en: Samba winbind client library Samba is an implementation of the SMB/CIFS protocol for Unix systems, providing support for cross-platform file and printer sharing with Microsoft Windows, OS X, and other Unix systems. . This package provides a library for client applications that interact via the winbind pipe protocol with a Samba winbind server. Description-en: SMB/CIFS file, print, and login server for Unix Samba is an implementation of the SMB/CIFS protocol for Unix systems, providing support for cross-platform file and printer sharing with Microsoft Windows, OS X, and other Unix systems. Samba can also function as an NT4-style domain controller, and can integrate with both NT4 domains and Active Directory realms as a member server. . This package provides the components necessary to use Samba as a stand-alone file and print server or as an NT4 or Active Directory domain controller. For use in an NT4 domain or Active Directory realm, you will also need the winbind package. . This package is not required for connecting to existing SMB/CIFS servers (see smbclient) or for mounting remote filesystems (see cifs-utils). Description-en: service to resolve user and group information from Windows NT servers Samba is an implementation of the SMB/CIFS protocol for Unix systems, providing support for cross-platform file sharing with Microsoft Windows, OS X, and other Unix systems. Samba can also function as a domain controller or member server in both NT4-style and Active Directory domains. . This package provides winbindd, a daemon which integrates authentication and directory service (user/group lookup) mechanisms from a Windows domain on a Linux system. . Winbind based user/group lookups via /etc/nsswitch.conf can be enabled via the libnss-winbind package. Winbind based Windows domain authentication can be enabled via the libpam-winbind package. $ Woops! I was missing -PX flags, all good now. $ grep-dctrl -PX winbind -s Description-en /var/lib/ Description-en: service to resolve user and group information from Windows NT se Samba is an implementation of the SMB/CIFS protocol for Unix systems, providing support for cross-platform file sharing with Microsoft Windows, OS X, and other Unix systems. Samba can also function as a domain controller or member server in both NT4-style and Active Directory domains. . This package provides winbindd, a daemon which integrates authentication and directory service (user/group lookup) mechanisms from a Windows domain on a Linux system. . Winbind based user/group lookups via /etc/nsswitch.conf can be enabled via the libnss-winbind package. Winbind based Windows domain authentication can be enabled via the libpam-winbind package. $ -- Yassine -- sysadm 57 33
Re: Exploring grep-dctrl
Le 11/29/22 à 5:48 PM, David Wright a écrit :
Please don't post HTML, but text.
Sorry, I thought my messages were multipart.
I just realized they were not after your message.
I'll have to fine-tune my MUA (thunderbird).
For the moment, I changed it to text only.
On Sun 27 Nov 2022 at 17:25:45 (+0100), Yassine Chaouche wrote:
I tried to achieve the same w/o using apt-cache, but couldn't.
My failed attempts were :
1/
16:37:50 ~ -1- $ grep-dctrl -PX syslog-summary
/var/lib/apt/lists/*_Packages
Those are the wrong files for the descriptions; you want *_Translation-en
Cheers,
David.
Thanks!
Now I only need to find a way to exit grep-dctrl on first match.
Skimming through the manpage I didn't find anything related,
except for -q which also disables printing.
I'm thinking about turning a single grep-dctrl call with multiple files
into a loop that would end after first grep-dctrl success exit code,
something like :
function package.describe2 {
for file in /var/lib/apt/lists/*_Translation-en
do
grep-dctrl -s Description-en "$1" "$file" && printf "%64s : %s\n" "$file" "$?"
&& break
done
}
But even then, translation files might contain more than one entry for same
package,
maybe one for each (version x architecture) product.
For eg.:
$ grep-dctrl winbind -s Description-en
/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_trusty-security_main_i18n_Translation-en
Description-en: Samba winbind client library - development files
Samba is an implementation of the SMB/CIFS protocol for Unix systems,
providing support for cross-platform file and printer sharing with
Microsoft Windows, OS X, and other Unix systems.
.
This package provides the development files (static library and headers)
required for building applications against libwbclient, a library for client
applications that interact via the winbind pipe protocol with a Samba
winbind server.
Description-en: Samba winbind client library
Samba is an implementation of the SMB/CIFS protocol for Unix systems,
providing support for cross-platform file and printer sharing with
Microsoft Windows, OS X, and other Unix systems.
.
This package provides a library for client applications that interact
via the winbind pipe protocol with a Samba winbind server.
Description-en: SMB/CIFS file, print, and login server for Unix
Samba is an implementation of the SMB/CIFS protocol for Unix systems,
providing support for cross-platform file and printer sharing with
Microsoft Windows, OS X, and other Unix systems. Samba can also function
as an NT4-style domain controller, and can integrate with both NT4 domains
and Active Directory realms as a member server.
.
This package provides the components necessary to use Samba as a stand-alone
file and print server or as an NT4 or Active Directory domain controller.
For use in an NT4 domain or Active Directory realm, you will also need the
winbind package.
.
This package is not required for connecting to existing SMB/CIFS servers
(see smbclient) or for mounting remote filesystems (see cifs-utils).
Description-en: service to resolve user and group information from Windows NT
servers
Samba is an implementation of the SMB/CIFS protocol for Unix systems,
providing support for cross-platform file sharing with Microsoft Windows, OS X,
and other Unix systems. Samba can also function as a domain controller
or member server in both NT4-style and Active Directory domains.
.
This package provides winbindd, a daemon which integrates authentication
and directory service (user/group lookup) mechanisms from a Windows
domain on a Linux system.
.
Winbind based user/group lookups via /etc/nsswitch.conf can be enabled via
the libnss-winbind package. Winbind based Windows domain authentication can
be enabled via the libpam-winbind package.
$
Should I just continue hacking around until I get desired results
(maybe process output with awk)
or is there a better approach to this? (reaching grep-dctrl limits)
Best,
--
Yassine -- sysadm
Re: Logout at apt upgrade
Happened once again. This time I think the culprit was udev (but I cannot be too sure). Among the updated package nothing should have killed X: beyond udev there was a bunch of libreoffice and related (not using right now), zathura (not using), not much more, at the very least, nothing that looked susceptible to trigger a session crash. Loïc
Re: Logout at apt upgrade
On Wed, Nov 30, 2022 at 06:16:04AM +0100, to...@tuxteam.de wrote: > FWIW it never happened to me. But: I'm on a pretty minimal system by > today's standards (X, Fvwm). The only application behaving strangely > after a dist-upgrade is... the browser, Firefix: "Ohmigod, something > funny happened, I'll have to close this tab, I'm sooo sorry". Whenever I do an "apt-get upgrade" and see a browser update incoming, I close that browser before the download finishes, to avoid that situation. As as matter of fact, that's happening this morning, as there's a new google-chrome-stable package today. There hasn't been an fvwm update since 2018 according to the Debian changelog, so that's just not an issue at the moment. If there's an update to X, I let it apply while my X session is still running, and then think about whether I want to restart the X session afterward, or just wait for some other package update that requires a reboot, and let it happen then.
Re: Logout at apt upgrade
On 11/30/22, to...@tuxteam.de wrote: > On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote: >> Am 29.11.2022 um 23:35 schrieb Loïc Grenié: >> > when I apt upgrade my system, I often (one every three, more >> > or less) find myself brutally logged out of the window system, >> > with systemd services painfully restarting (or failing to restart). >> > The only way I can recover is usually to reboot. >> >> Yes, i see similar problem, amd AFAICT it is somewhat related to my use >> of GNOME3. They insist on restarting the system for almost all package >> updates, but sometimes, i refuse to and keep the machine running without >> updating it. I am aware, this could cause troubles on the security-side. >> That is why i am keeping a long list of system-backups. > > FWIW it never happened to me. But: I'm on a pretty minimal system by > today's standards (X, Fvwm). The only application behaving strangely > after a dist-upgrade is... the browser, Firefix: "Ohmigod, something > funny happened, I'll have to close this tab, I'm sooo sorry". > > So it seems to be related to Gnome's love for complexity, yes (any > KDE/XFCE users out there?) XFCE user here - it's never happened to me. Then again, I use the synaptic package manager instead of apt upgrade so that might have something to do with it. And the needrestart package plays very nicely with the synaptic package manager - after updating software I get a popup offering to restart processes whose files were just updated Regards, Lee
Re: debian stretch wine
mattias: > Ãr verkligen wine 5.1x det lägsta för stretch? Enl. https://packages.debian.org/search?keywords=wine=names=all=all sÃ¥ har stretch v1.8.7, ska du ha 5.0.3 är den anpassad till bullseye. > GÃ¥r inte uppgradera dÃ¥ hälften av speglarna är döda Finns det Ã¥tminstonde en spegel sÃ¥ gÃ¥r att uppgradera. Listan finns här: https://www.debian.org/mirror/list UmeÃ¥ verkar ha stretch: http://ftp.acc.umu.se/debian/dists/stretch/ > Men gÃ¥r väll inte ta wine frÃ¥n debian 10 och köra in? Normalt sett inte pga. beroenden. Du kan prova med att bygga frÃ¥n källkod, se längst ned pÃ¥: https://wiki.winehq.org/Download Hälsningar, /Karl Hammar
Re: Debian-Installer: clavier US ou configuration manuelle ?
On 11/30/22 10:37, Thomas Parmelan wrote: Le lundi 28 novembre 2022 à 09:23, d'après Olivier : Je lance l'installation, en sélectionnant dans l'installeur Debian, les options Advanced Options puis Automated Install puis en fournissant l'URL de mon fichier preseed.cfg. Option C : faire démarrer l'ordinateur à installer en PXE, avec un fichier de configuration PXE donnant l'URL du fichier preseed en paramètre à l'installateur Debian. Il n'y a donc plus besoin de l'entrer manuellement ;-) Plus d'informations => https://wiki.debian.org/PXEBootInstall Une alternative que j'avais pratiqué autrefois est de générer la carte du clavier dans le noyau avant sa recompilation. Le noyau ainsi modifié (assez facilement) a un clavier en dur adapté. J'ai oublié les détails, mais il y a dix ans c'était assez facile. -- Basile Starynkevitch (only mine opinions / les opinions sont miennes uniquement) 92340 Bourg-la-Reine, France web page: starynkevitch.net/Basile/
Re: Logout at apt upgrade
Jeffrey Walton writes: > KDE works as expected. Yep. > God bless those who have stuck with GNOME after the change to GNOME3. > They have the tolerance of saints. I have to agree. I did get Gnome 3 to somewhere I kinda liked but when an updated wiped my customizations, it was time to say good bye to Gnome and upgrade to KDE.
Re: Debian-Installer: clavier US ou configuration manuelle ?
Le lundi 28 novembre 2022 à 09:23, d'après Olivier : > Je lance l'installation, en sélectionnant dans l'installeur Debian, > les options Advanced Options puis Automated Install > puis en fournissant l'URL de mon fichier preseed.cfg. Option C : faire démarrer l'ordinateur à installer en PXE, avec un fichier de configuration PXE donnant l'URL du fichier preseed en paramètre à l'installateur Debian. Il n'y a donc plus besoin de l'entrer manuellement ;-) Plus d'informations => https://wiki.debian.org/PXEBootInstall -- Thomas Parmelan
Re: Logout at apt upgrade
Thanks Tomas, and thanks to all those responded, On Wed, Nov 30, 2022 at 06:16, Tomas wrote: > On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote: > > Am 29.11.2022 um 23:35 schrieb Loïc Grenié: > > > when I apt upgrade my system, I often (one every three, more > > > or less) find myself brutally logged out of the window system, > > > with systemd services painfully restarting (or failing to restart). > > > The only way I can recover is usually to reboot. > > > > Yes, i see similar problem, amd AFAICT it is somewhat related to my use > > of GNOME3. They insist on restarting the system for almost all package > > updates, but sometimes, i refuse to and keep the machine running without > > updating it. I am aware, this could cause troubles on the security-side. > > That is why i am keeping a long list of system-backups. > > FWIW it never happened to me. But: I'm on a pretty minimal system by > today's standards (X, Fvwm). The only application behaving strangely > after a dist-upgrade is... the browser, Firefix: "Ohmigod, something > funny happened, I'll have to close this tab, I'm sooo sorry". > I'm using icebox with a dm. As far as I can tell this is not related to dm upgrade, nor to icebox upgrade. I agree that firefox used to say "something funny happened", but unfortunately it's just killed as everything else each time (and, then, I have to reboot). Fortunately, the programs I use do save their data regularly, so that I don't lose anything more than time in the process. Loïc
Re: Copier plusieurs ISO sur une clé USB pour installer Debian
Le mar. 29 nov. 2022 à 23:05, Jean Bernon a écrit : > > Sur cette machine est-ce qu'au moins le menu Ventoy s'affiche ou est-ce que > ça bloque quand tu veux lancer un iso ? Le menu Ventoy ne s'affiche pas: j'ai un message fugace "invalid image" (de mémoire) à la place > Dans le 1er cas il peut y avoir un blocage au niveau de la configuration HP > du boot . J'ai un vague souvenir de problème avec certains modèles HP qui > bootent obstinément sur Windows. Pour savoir si le problème vient de Ventoy, > as-tu essayé une clé usb simple avec un seul iso sur cette machine ? > La machine arrive à booter sur une clé "normale": c'est grâce à cette méthode que j'ai pu installer Bullseye. Une autre machine arrive à booter sur la clé Ventoy. Il y a visiblement une spécificité sur cette combinaison clé+machine qui ne me saute pas aux yeux. Un coup d'oeil rapide sur les 350 tickets ouverts sur le site github de Ventoy ne m'a pas inspiré.
debian stretch wine
Jaja jag vet att stretch är tämligen gammaltMen har inget valÄr verkligen wine 5.1x det lägsta för stretch?Går inte uppgradera då hälften av speglarna är dödaMen går väll inte ta wine från debian 10 och köra in? Skickades från E-post för Windows
