Re: Stratégie de partitionnement
Bonjour, La partition /boot/efi est surtout utile quand on utilise un système uefi. Elle doit être impérativement de type vfat, parce que la majorité des systèmes uefi ne gère que ce type de partition pour savoir sur quoi booter. :) En fait, quand la machine est en mode uefi, elle ne se sert pas du petit secteur de boot qu'on installait autrefois dans la partition au début du disque. Concernant la partition racine sur un volume de type étendu, ça n'a pas vraiment d'incidence, si je me trompe pas, les volumes étendu permettent seulement de ne pas être limité en nombre de partition puisque sur un disque en MBR, on est limité par défaut à 4 partitions primaires. Il ne me semble pas qu'il y ait d'autres avantages/inconvénient au partitions étendus. Enfin, concernant le swap, il est vrai que le fait d'utiliser un fichier plutôt qu'une partition est considéré comme moins "fiable". J'ai jamais vraiment comparé ceci dit. En espérant que ça aide, Jerem Le 18/06/2022 à 03:17, Pierre ESTREM a écrit : Bonjour, Dessous je vous présente le retour de 'fdisk -l' appliqué à l'image d'une distro (sur clé usb) et destinée aux déficients visuels (base Mint) : Device Boot Start End Sectors Size Id Type aciah-linux.img1 * 2048 1050623 1048576 512M b W95 FAT32 aciah-linux.img2 1052670 60063743 59011074 28,1G 5 Extended aciah-linux.img5 1052672 60063743 59011072 28,1G 83 Linux Je me pose diverses questions. GRUB2 est situé dans le MBR. Quel(s) intérêt(s) a-t-on de faire que la partition 1 contenant /boot/efi soit de type vfat ? Pourquoi avoir mis la racine (partition ext4) dans une unité logique (n°5) ? Je constate que le swap est en fait un fichier dans la racine (à la mode W$). Ca doit bien ralentir le système ? Je m'emploie à faire de la racine une partition primaire (n°2) plutôt qu'une unité logique. Un conseil ? Merci à ceux qui auront pris le temps de me lire sur ce sujet... ardu. pierre estrem
Re: memtest86
Felix Miata composed on 2022-06-15 07:26 (UTC-0400):
> I don't even try to use FOSS memtest86+ on UEFI PCs. Instead, I use the free
> version of the proprietary memtest86 from https://www.memtest86.com/. I run it
> from this Grub stanza in /boot/grub/custom.cfg on my fastest/newest x86_64 PC:
> menuentry "memtest86 7.4 EFI" {
> search --no-floppy --label --set=root TM8P01ESP
> chainloader /mt74x64.efi
> }
IIRC, to get mt74x64.efi, and later mt83x64.efi, I had to loop mount the free to
download bootable .iso and copy it off to a Grub-visible location. mt83x64.efi
does work on my 11th Gen i5-11400 loaded from Grub-efi as above:
Clk: 4235MHz
L1 cache: 80K 468.40 GB/s
L2 cache: 512K 95.10 GB/s
L3 cache: 12288K 48.46 GB/s
DDR4 2400: 15.7G 23.81 GB/s
> That menu entry is pointing to the FAT32 ESP partition, which has the
> filesystem
> label TM8P01ESP.
>
> The current free version is much newer than 7.4.
--
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
Stratégie de partitionnement
Bonjour, Dessous je vous présente le retour de 'fdisk -l' appliqué à l'image d'une distro (sur clé usb) et destinée aux déficients visuels (base Mint) : Device Boot Start End Sectors Size Id Type aciah-linux.img1 * 2048 1050623 1048576 512M b W95 FAT32 aciah-linux.img2 1052670 60063743 59011074 28,1G 5 Extended aciah-linux.img5 1052672 60063743 59011072 28,1G 83 Linux Je me pose diverses questions. GRUB2 est situé dans le MBR. Quel(s) intérêt(s) a-t-on de faire que la partition 1 contenant /boot/efi soit de type vfat ? Pourquoi avoir mis la racine (partition ext4) dans une unité logique (n°5) ? Je constate que le swap est en fait un fichier dans la racine (à la mode W$). Ca doit bien ralentir le système ? Je m'emploie à faire de la racine une partition primaire (n°2) plutôt qu'une unité logique. Un conseil ? Merci à ceux qui auront pris le temps de me lire sur ce sujet... ardu. pierre estrem
Re: debian-user message size limit
On 2022-06-17 19:01, Gareth Evans wrote: On 17 Jun 2022, at 23:25, Bijan Soleymani wrote: Actually I didn't store the emails from some point in 2004 through part of 2008. So I can't say when the limit was lowered but at least from 2009 until now there hasn't been anything over 101KB (103,424 bytes). Bijan Thanks for taking the time and effort to do that and letting us know. G No worries! I love extrapolating from data. Actually it just occurred to me that I scanned the sizes, based on the filesizes of the Maildir files on my mail server, and not the actual sizes of the messages as sent to the list. So taking the largest message from 2009-2022 that was: 103,384 bytes long And finding it on the list archive: https://marc.info/?l=debian-user=125432953215932 And downloading the raw message the size was actually: 99,925 bytes So I guess the limit is likely 100 decimal kB. 100,000 bytes. Bijan
Re: debian-user message size limit
> On 17 Jun 2022, at 23:25, Bijan Soleymani wrote: > > On 2022-06-17 18:20, Bijan Soleymani wrote: >>> On 2022-06-17 11:24, Gareth Evans wrote: >>> Is there a limit for message size on debian-user? >> I checked the data. I have been subscribed since 2003, though I >> haven't been active for a lot of that period. > > Actually I didn't store the emails from some point in 2004 through part of > 2008. > > So I can't say when the limit was lowered but at least from 2009 until now > there hasn't been anything over 101KB (103,424 bytes). > > Bijan > Thanks for taking the time and effort to do that and letting us know. G
Re: debian-user message size limit
On 2022-06-17 18:20, Bijan Soleymani wrote: On 2022-06-17 11:24, Gareth Evans wrote: Is there a limit for message size on debian-user? I checked the data. I have been subscribed since 2003, though I haven't been active for a lot of that period. Actually I didn't store the emails from some point in 2004 through part of 2008. So I can't say when the limit was lowered but at least from 2009 until now there hasn't been anything over 101KB (103,424 bytes). Bijan
Re: debian-user message size limit
On 2022-06-17 11:24, Gareth Evans wrote: Is there a limit for message size on debian-user? I checked the data. I have been subscribed since 2003, though I haven't been active for a lot of that period. In 2003 there were a handful of larger messages (largest 154KB). But since then there hasn't been anything above 100KB (maybe one or two just under 101KB, one in 2009 was 103,384 bytes, this was the largest since 2003). My guess is if in almost 20 years there haven't been any messages 101KB and above, that's the limit. Bijan
Re: user perms
On 6/17/22 16:29, Anssi Saari wrote: gene heskett writes: I just did all that, so now I have an /etc/rc.local but not an rc-local but he changes from rc.local to rc-local in the middle. confusing. So which is it. I originally created an rc.local, changed it to rc-local, and back with mv. The script file is /etc/rc.local but the systemd service name is rc-local. Now, I'm not aware of who heyu runs as, probably gene since I'm the one running it and there is no user heyu. Now, 2 new questions: So what do I put in this rc.local to allow me, gene, to use /dev/ttyUSB0, which has the cm11a on the other side of an fdti adaptor? Since you seem to have the expected permissions for /dev/ttyUSB0 and /dev/ttyUSB1 maybe you could just add gene and nut users to the dialout group? adduser gene dialout and adduser nut dialout. But if you really want to use rc.local then setting the group to nut for the UPS line /dev/ttyUSB1 would work, so just chgrp nut /dev/ttyUSB1 And then chgrp gene /dev/ttyUSB0 Hope it helps! Absolutely the magic twanger Anssi. I put it all in rc.local, or in /etc/group then ran rc.local for S, checked the devices were changed, restarted nut-server and nut-client, works as expected, then ran "heyu info" as me and got the expected response. Finally, someone was not afraid to answer my questions. Thank you Anssi, take care and stay well. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: debian-user message size limit
On Fri 17 Jun 2022, at 20:00, Brian wrote: > On Fri 17 Jun 2022 at 16:24:54 +0100, Gareth Evans wrote: > >> Is there a limit for message size on debian-user? >> >> I can't find any such info on >> >> https://lists.debian.org/ >> >> https://www.debian.org/MailingLists/ >> >> https://lists.debian.org/debian-user/ >> >> but a couple of recent large-ish messages (one ~270K with two >> screenshots, one 70K with log output) have neither got through nor >> bounced back. >> >> It would be helpful to know what it is if there is one. > > Don't expect Listmaster to rush here and tell us :), > > According to mutt, one of the mails you sent earlier today is 70K > in size: > > https://lists.debian.org/debian-user/2022/06/msg00586.html > > Do you hear anyone complaining? You did not. The bandwidth usage is > low and time to download it is minuscule. The wheels are greased in > -user. > > However, you cheated and put a log file inline. Naughty :). Good > sense reigns in -user, however, so no one begrudges it. > > You know that attachments of ~270K and 70K do not get through. For the record, I had thought the log excerpts in the 70K email were likely to be just about acceptable inline - there was no attempt to send a ~70K attachment. Perhaps there should (or shouldn't) have been. I would find it difficult to consider 70K "large". With no guidance on the issues in eg monthly FAQ, this creates ambiguity and uncertainty. There was quite a delay in both the 70K email and the message size limit question getting back to me, such that I thought both may have been dropped or held - first the former, hence the latter, and then still an unusually long wait. But such is email sometimes. The lack of dropped/held feedback [1] (if messages even are held) along with ambiguity around message/attachment sizes, makes it difficult to judge what to do and when, if anything. Best wishes, Gareth [1] "Another known limitation in our mailing list software is that most rejected e-mails get silently dropped, so the user has no real indication on what went wrong." https://www.debian.org/MailingLists/ > Try > ~50K next time and be aware that compression with gzip or xz is a > option. Text files compress well. > > If 50K is rejected, no harm is done. Try again to find the upper > limit. > > Attacments to a mailing list like -user are an efficient us of its > services. Ephemeral info on other sites isn't of any value to users > in the future. > > -- > Brian.
Re: user perms
gene heskett writes: > I just did all that, so now I have an /etc/rc.local but not an rc-local > but he changes from rc.local to rc-local in the middle. confusing. > > So which is it. I originally created an rc.local, changed it to > rc-local, and back with mv. The script file is /etc/rc.local but the systemd service name is rc-local. > Now, I'm not aware of who heyu runs as, probably gene since I'm the > one running it and there is no user heyu. > > Now, 2 new questions: > > So what do I put in this rc.local to allow me, gene, to use /dev/ttyUSB0, > which has the cm11a on the other side of an fdti adaptor? Since you seem to have the expected permissions for /dev/ttyUSB0 and /dev/ttyUSB1 maybe you could just add gene and nut users to the dialout group? adduser gene dialout and adduser nut dialout. But if you really want to use rc.local then setting the group to nut for the UPS line /dev/ttyUSB1 would work, so just chgrp nut /dev/ttyUSB1 And then chgrp gene /dev/ttyUSB0 Hope it helps!
Re: debian-user message size limit
On Fri, 17 Jun 2022 21:28:15 +0200 Nicolas George wrote: > Brian (12022-06-17): > > Attacments to a mailing list like -user are an efficient us of its > > services. > > Multiplying the storage space taken by an attachment by the thousands of > users subscribed to this mailing list, most of them being not > interested, is really not what I would call an efficient use of > resources. If administrators are feeling that particular strain, there are facilities like paste-it, imgur, and any number of others which could help. There is always the risk of loss of data with that approach, however, which reduces the said efficiency of the list. Always best to keep all related material together, at the one resource to be available to those who may not be interested in a particular issue now, but may well see it as a priority in the future. For the sake of efficiency. Cheers! David.
Re: debian-user message size limit
On Fri 17 Jun 2022 at 21:28:15 +0200, Nicolas George wrote: > Brian (12022-06-17): > > Attacments to a mailing list like -user are an efficient us of its > > services. > > Multiplying the storage space taken by an attachment by the thousands of > users subscribed to this mailing list, most of them being not > interested, is really not what I would call an efficient use of > resources. You mean like the 70K email I cited? That mail lasted 3s on my system. No storage space usedd. Besides whic, I have no great desire to explore the storage capabilities and needs of 9,999 users. -- Brian.
Re: digikam import fails
On Fri, Jun 17, 2022 at 06:29:52PM +0100, Eric S Fraga wrote: > On Thursday, 16 Jun 2022 at 21:27, Roy J. Tellason, Sr. wrote: > > I must be missing something here... > > > > When I plug in my camera to a US port, it shows up on the desktop, at > > which point I can mount it. Then I can access it and copy/move stuff > > to wherever, using mc or whatever utility you like. Why is some > > special program needed for this? > > Unfortunately because many cameras do not implement USB file store > access, only MTP (media transfer protocol?). If they provide file store > access, life is simple. I can chose that in my camera's menu (memory, MTP, auto, something else I forgot). I chose memory and "download" the stuff with rsync. Works a charm. Oh, I have no DE, so I mount the cam explicitly. I don't like things auto-mounting. But I'm weird :) Cheers -- t signature.asc Description: PGP signature
Re: digikam import fails
On Fri, Jun 17, 2022 at 01:09:39PM +0100, Brian wrote: > On Fri 17 Jun 2022 at 13:57:00 +0200, to...@tuxteam.de wrote: [...] > > Perhaps I was over-sensitive. My apologies in that case. > > I do not think apologies are necessary. The reminder to attempt > really helpful and tolerant responses is well taken. But they aren't wrong, either :-) Cheers & thanks for helping people -- tomás > > -- > Brian. > signature.asc Description: PGP signature
Re: digikam import fails
On Fri, Jun 17, 2022 at 09:32:43AM -0400, gene heskett wrote: > On 6/17/22 08:25, Andrew M.A. Cater wrote: > > On Fri, Jun 17, 2022 at 08:05:16AM -0400, gene heskett wrote: > > > On 6/17/22 01:02, to...@tuxteam.de wrote: > > > > On Thu, Jun 16, 2022 at 08:39:19PM +0100, Brian wrote: > > > > > > > > [...] > > The point about being poitve and constructive rather than snarky is a more > > general one. > > > > > > Cheers > > > I agree 100%. This whole nightmare was started by the installer silently > > > installing brltty and orca, assuming I was blind just because it found a > > > plugged in fdti usb<->serial adapter, and by the time I had killed the > > > noise, the log was still being spammed about 30 lines per keystroke and > > > the system uptime was in hours. And the reboot was locked up by not > > > finding > > > brltty, so that was about the first 25 re-installs. It was the only way > > > to reboot. > > > > > Early on in your 25 reinstalls, I and others suggested you unplug the serial > > leads and try again. Once you were able to do that, you got a more usual > > install where that option is skipped. > > > > > And I'm catching hell because I didn't trace down my USB tree and unplug > > > everything during the install. > > > > > As above: you were advised to do this - when you finally did, it worked as > > expected. Andrew is right on this one. One has to be fair to both sides, and it is true that you stubbornly refused to try the advice offered to you. There always are reasons... > It also required I put these 87 yo knees on the floor and crawl around > under the table to trace which cable was which. That gets complex > when there are over 20 of them and 2 external hubs in 32 years of > detrius [...] ...possibly valid ones, but railing at the d-i seems unfair: if some wacko USB device steals the ID of a Braille terminal, there's nothing the d-i can do about that. Even in doubt, the machine should switch to assistive tech mode, otherwise a blind person wouldn't stand a chance. It's a decision you, the engineer, would take exactly that way, I suppose. [...] > I would rebut that it is, the d-i could interrogate and discover that > whatever was beyond either of those adapters was not a braille tty. > But no, it finds the adapter and assumes its feeding a braille tty. But that's exactly what it does. That's what those USB IDs are for. Most probably one of those USB-serial adapters is lying through its pins. Another possibility is that the database UDEV consults is wrong. An lsusb might shed light on that. But not railing at things and people :) Cheers -- t signature.asc Description: PGP signature
Re: debian-user message size limit
Brian (12022-06-17): > Attacments to a mailing list like -user are an efficient us of its > services. Multiplying the storage space taken by an attachment by the thousands of users subscribed to this mailing list, most of them being not interested, is really not what I would call an efficient use of resources. -- Nicolas George signature.asc Description: PGP signature
Re: debian-user message size limit
On Fri 17 Jun 2022 at 16:24:54 +0100, Gareth Evans wrote: > Is there a limit for message size on debian-user? > > I can't find any such info on > > https://lists.debian.org/ > > https://www.debian.org/MailingLists/ > > https://lists.debian.org/debian-user/ > > but a couple of recent large-ish messages (one ~270K with two > screenshots, one 70K with log output) have neither got through nor > bounced back. > > It would be helpful to know what it is if there is one. Don't expect Listmaster to rush here and tell us :), According to mutt, one of the mails you sent earlier today is 70K in size: https://lists.debian.org/debian-user/2022/06/msg00586.html Do you hear anyone complaining? You did not. The bandwidth usage is low and time to download it is minuscule. The wheels are greased in -user. However, you cheated and put a log file inline. Naughty :). Good sense reigns in -user, however, so no one begrudges it. You know that attachments of ~270K and 70K do not get through. Try ~50K next time and be aware that compression with gzip or xz is a option. Text files compress well. If 50K is rejected, no harm is done. Try again to find the upper limit. Attacments to a mailing list like -user are an efficient us of its services. Ephemeral info on other sites isn't of any value to users in the future. -- Brian.
Re: digikam import fails
On 6/17/22 12:40, Roy J. Tellason, Sr. wrote: On Thursday 16 June 2022 09:45:21 pm gene heskett wrote: I must be missing something here... When I plug in my camera to a US port, it shows up on the desktop, at which point I can mount it. Then I can access it and copy/move stuff to wherever, using mc or whatever utility you like. Why is some special program needed for this? Probably the desktop Roy, I'm using xfce4. So am I... Humm, bears investigating, in due time. Thanks Roy. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: digikam import fails
On Thursday, 16 Jun 2022 at 21:27, Roy J. Tellason, Sr. wrote: > I must be missing something here... > > When I plug in my camera to a US port, it shows up on the desktop, at > which point I can mount it. Then I can access it and copy/move stuff > to wherever, using mc or whatever utility you like. Why is some > special program needed for this? Unfortunately because many cameras do not implement USB file store access, only MTP (media transfer protocol?). If they provide file store access, life is simple. -- Eric S Fraga via gnus (Emacs 29.0.50 2022-06-12) on Debian 11.3
Re: debian-user message size limit
Gareth Evans (12022-06-17): > but a couple of recent large-ish messages (one ~270K with two > screenshots, one 70K with log output) have neither got through nor > bounced back. “Avoid sending large attachments.” https://www.debian.org/MailingLists/ This is not specific to Debian, most Libre Software mailing-list I know have a similar policy. It is inefficient and annoying for recipients. Put your screenshots on some transient hosting site. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: debian-user message size limit
> On 17 Jun 2022, at 17:51, Nicolas George wrote: > > Gareth Evans (12022-06-17): >> but a couple of recent large-ish messages (one ~270K with two >> screenshots, one 70K with log output) have neither got through nor >> bounced back. > > “Avoid sending large attachments.” > > https://www.debian.org/MailingLists/ > > This is not specific to Debian, most Libre Software mailing-list I know > have a similar policy. It is inefficient and annoying for recipients. > Put your screenshots on some transient hosting site. > > Regards, > > -- > Nicolas George > Thank you both - I'll try that next time. Gareth
Re: memtest86+ on 12th gen intel
On 6/13/2022 12:27 PM, Bijan Soleymani wrote: Here's a post on the issues with memtest86+ (the free software version) and UEFI: https://askubuntu.com/questions/917961/can-i-boot-memtest86-if-im-using-uefi Sorry for the spam, looks like they just added UEFI support last week: https://www.memtest.org/ "Changelog * Rewrite code for UEFI 32 & 64 bits" Bijan Nothing worked. Both memtest86 and memtest86+ with grub or standalone boot did not work on my core-i312100. I suspect it is a display driver problem. My regular bullseye install itself had this blank screen problem. Only upgrading to kernel 5.16 from backport got my system working. Memtest is having very similar issues. With grub both versions of memtest removes menu and backgroud splash screen shows and no more activity. With boot USB, BIOS flashscreen, black screen, nothing more. If anyone got this working on a 12th gen core i3/5/7, please follow up and let me know how you got it working. Please copy me in your post, if it is while (aka months) before you see this and followup. Regards Ramesh
Re: debian-user message size limit
On 6/17/22, Gareth Evans wrote: > Is there a limit for message size on debian-user? > > I can't find any such info on > > https://lists.debian.org/ > > https://www.debian.org/MailingLists/ > > https://lists.debian.org/debian-user/ > > but a couple of recent large-ish messages (one ~270K with two screenshots, > one 70K with log output) have neither got through nor bounced back. > > It would be helpful to know what it is if there is one. I don't know if there's a list size limit or not, but maybe your submission is sitting in moderation because it's not the norm? As an alternative, list members have previously hosted their images on trustworthy image hosts. I'm out of touch with what might qualify as that these days, though. Similar has been done for large text files, too. Pastebin type hosts fit that need. In fact, Debian had a version of it for its own packages not too long ago. The caveat for either of the above is that there's often a self-destruct mode that is based on either time length or click views. That's understandably about wear and tear on the host's server(s). Best wishes on what you're trying to fix. Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: How to change lightdm background in bullseye? (additional: weird stat behaviour)
Am Thu, 16 Jun 2022 23:26:38 + schrieb Lee : > > [greeter] > > background=/usr/share/xfce4/backdrops/foo.png > > user-background=/usr/share/xfce4/backdrops/foo.png > > Do those files exist? There's no /usr/share/xfce4/backdrops/ on my machine.. No, these files don't exist ;-) I changed the name to foo.png in the email because the original name contained information I didn't want to share. But yes, the directory exists (initial install was Debian 8) and the files referenced also exist. > This works for me > $ cat lightdm-gtk-greeter.conf > [greeter] > background = /usr/share/desktop-base/spacefun-theme/login/background.svg My original file /etc/lightdm/lightdm-gtk-greeter.conf actually contained a lot of lines with comments about the options. I copied only the relevant stuff (what I _believed_ was relevant) into the email. > Try installing lightdm-gtk-greeter-settings > I get a lot of error messages but it did change the background for me. It works. The settings editor removed everything else from the file and now there's only those two lines left. I'm really curious to find out what in the original file caused problems. I'll restore it from my backup and check that. Thanks! Christoph
debian-user message size limit
Is there a limit for message size on debian-user? I can't find any such info on https://lists.debian.org/ https://www.debian.org/MailingLists/ https://lists.debian.org/debian-user/ but a couple of recent large-ish messages (one ~270K with two screenshots, one 70K with log output) have neither got through nor bounced back. It would be helpful to know what it is if there is one. Thanks, Gareth
Re: digikam import fails
On 2022-06-17, gene heskett wrote: >> >> When I plug in my camera to a US port, it shows up on the desktop, >> at which point I can mount it. Then I can access it and copy/move >> stuff to wherever, using mc or whatever utility you like. Why is >> some special program needed for this? > Probably the desktop Roy, I'm using xfce4. I would like to point out my simple technique for exchanging files with other devices on the same LAN. I haven't been following these very Proustian threads of yours (Proustian in terms of *length*), so I'm unaware how many photos you're wanting to download from your phone (this solution may not scale for the movement of a great number of files), but snapdrop.net in a browser on both the sending and receiving device has worked for me here on occasion (of course, as you're well aware, I don't adhere to the high hacker standards of some of our more venerable correspondents). It all happens locally with Javascript, if ever you would want to try it out. À bientôt, C > Cheers, Gene Heskett.
Re: digikam import fails
On Thursday 16 June 2022 09:45:21 pm gene heskett wrote: > > I must be missing something here... > > > > When I plug in my camera to a US port, it shows up on the desktop, at > > which point I can mount it. Then I can access it and copy/move stuff to > > wherever, using mc or whatever utility you like. Why is some special > > program needed for this? > Probably the desktop Roy, I'm using xfce4. > So am I... -- Member of the toughest, meanest, deadliest, most unrelenting -- and ablest -- form of life in this section of space, a critter that can be killed but can't be tamed. --Robert A. Heinlein, "The Puppet Masters" - Information is more dangerous than cannon to a society ruled by lies. --James M Dakin
Re: Printing problem (was snapshot.debian.org)
On Mon 6 Jun 2022, at 20:03, Gareth Evans wrote: > On Mon 6 Jun 2022, at 17:45, Gareth Evans wrote: >> Recent message with screenshots didn't get through (at least yet) - >> text below, plus another observation. >> >> On Mon 6 Jun 2022, at 16:53, Gareth Evans wrote: >>> On Mon 6 Jun 2022, at 16:23, Eduardo M KALINOWSKI >>> wrote: On 06/06/2022 10:48, Gareth Evans wrote: > Not sure what's happened though as it worked perfectly with both > auto-detected and manually-added printer profiles from Bullseye until a > week or two ago. My logs suggest no update to system-config-printer. I > did change the printer's hostname (on printer console) but both the > printer and laptop have been restarted several times since then, printers > re-added and re-auto-detected etc. In my case it never worked any other way. But I never dug very deep to try to find out why. > Why should adding via the command line work, but not via > system-config-printer or localhost:631? I guess adding it in CUPS web interface (localhost:631) should work, if the exact same parameters are selected: the ipp:// url and the "CUPS PPD generator" (selected by "-m everywhere" option) as opposed to "cups-filters PPD generator". That might be the explanation (at least for my case). From what I understand from https://wiki.debian.org/CUPSDriverlessPrinting , there are those two options, and "The cups-filters PPD generator is used by default with cups-browsed". In theory either should work, but there's probably some quirk in the printer and some small difference between the two methods. -- Tchurin-tchurin-tchun-clain! -- Chapolim Eduardo M KALINOWSKI edua...@kalinowski.com.br >>> >>> When adding a printer with system-config-printer, it is detected and >>> listed under "Network Printer" in the list (when expanded) (twice). I >>> currently see what's in the screenshots attached, but sometimes the >>> "IPP network printer via DNS-SD" connection option changes to something >>> involving AppSocket/... at the beginning. >>> >>> There seem to be different connections available at different times. >>> >>> Any ideas why that should be? >>> >>> It seems to me that something has changed. Given the problem was the >>> same with an identical printer on a different network, I guess it's >>> something to do with CUPS (or its config) rather than the printer >>> itself misbehaving. I had factory-reset it a couple of days ago. >>> >>> Thanks, >>> Gareth >>> >>> >>> Attachments: >>> * Screenshot at 2022-06-06 16-39-52.png >>> * Screenshot at 2022-06-06 16-40-03.png >> >> $ driverless list >> DEBUG: Started ippfind (PID 95003) >> "driverless:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" en >> "Brother" "Brother MFC-L2740DW series, driverless, cups-filters 1.28.7" >> "MFG:Brother;MDL:MFC-L2740DW series;CMD:PWGRaster,AppleRaster,URF,PWG;" >> "driverless-fax:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" >> en "Brother" "Brother MFC-L2740DW series, Fax, driverless, cups-filters >> 1.28.7" "MFG:Brother;MDL:MFC-L2740DW >> series;CMD:PWGRaster,AppleRaster,URF,PWG;" >> DEBUG: ippfind (PID 95003) exited with no errors. >> >> The error log except attached earlier includes: >> >> [line no] log text >> [30] D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-is-accepting-jobs >> boolean true >> D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state enum idle >> D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state-reasons keyword >> none >> D [06/Jun/2022:13:32:04 +0100] [Job 6] end-of-attributes-tag >> D [06/Jun/2022:13:32:04 +0100] [Job 6] IPP/2.0 Get-Job-Attributes #22 >> D [06/Jun/2022:13:32:04 +0100] [Job 6] operation-attributes-tag >> >> D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-charset charset utf-8 >> D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-natural-language >> naturalLanguage en-gb >> D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-uri uri >> ipp://mfcl2740dw.local:631/ipp/faxout >> >> ^^ >> >>Fax >> >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82 >> >> D [06/Jun/2022:13:32:04 +0100] [Job 6] unsupported-attributes-tag >> >> D [06/Jun/2022:13:32:04 +0100] [Job 6] requested-attributes keyword >> job-media-sheets-completed >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-attributes-tag >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82 >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-impressions-completed >> integer 0 >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-name nameWithoutLanguage >> Test Page >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-originating-user-name >> nameWithoutLanguage user >> D
Re: [EXTERNAL] Re: Does DEBIAN BullsEye has FIPS package available
On Thu, Jun 16, 2022 at 11:58:50PM -0400, Bijan Soleymani wrote: There may be user space components too. I don't know if Debian still ships with openssl or another SSL library now but openssl specifically can be compiled in some FIPS compatibility mode. That's not currently true; as far as I know there's no way to make debian FIPS certified until (maybe) openssl FIPS 3.0 is certified, and some as-yet unknown steps are taken for the as-yet unreleased bookworm.
Re: Frozen mouse and keyboard
Thanks Brad for your contribution. I don't think anything can be done with the keyboard when the freeze occurs. On 15:41, Wed, 15 Jun 2022 Brad Rogers On Wed, 15 Jun 2022 15:15:35 +0100 > Joe wrote: > > Hello Joe, > > >Also try Ctrl-Alt-F3 > >to see if a console is reachable as X might have problems. > > Unlikely: OP reported keyboard is frozen, too. > > -- > Regards _ > / ) "The blindingly obvious is never immediately apparent" > / _)rad "Is it only me that has a working delete key?" > I'm in need of your help now > Burn - Judgement Centre >
Re: Frozen mouse and keyboard
On Fri, 17 Jun 2022 14:23:53 +0100 Mick Ab wrote: > Thanks very much, David, for your help. > > Unfortunately it is not possible to log in to the PC from elsewhere. > > As to most of your other points, they will have to wait for another > similar freeze. > > I was not able to check logs because, subsequent to the freezing, the > PC had to be rebooted due to a mains power cut and the journald > system does not persist across boots. > > Assuming you're not really tight on disc space, you can fix that, at least for the duration of the problem. https://computingforgeeks.com/preserve-systemd-journals-logging-with-persistent-storage/ For reference: https://lists.debian.org/debian-devel/2020/02/msg0.html -- Joe
Re: digikam import fails
On 6/17/22 08:25, Andrew M.A. Cater wrote: On Fri, Jun 17, 2022 at 08:05:16AM -0400, gene heskett wrote: On 6/17/22 01:02, to...@tuxteam.de wrote: On Thu, Jun 16, 2022 at 08:39:19PM +0100, Brian wrote: [...] The point about being poitve and constructive rather than snarky is a more general one. Cheers I agree 100%. This whole nightmare was started by the installer silently installing brltty and orca, assuming I was blind just because it found a plugged in fdti usb<->serial adapter, and by the time I had killed the noise, the log was still being spammed about 30 lines per keystroke and the system uptime was in hours. And the reboot was locked up by not finding brltty, so that was about the first 25 re-installs. It was the only way to reboot. Early on in your 25 reinstalls, I and others suggested you unplug the serial leads and try again. Once you were able to do that, you got a more usual install where that option is skipped. And I'm catching hell because I didn't trace down my USB tree and unplug everything during the install. As above: you were advised to do this - when you finally did, it worked as expected. It also required I put these 87 yo knees on the floor and crawl around under the table to trace which cable was which. That gets complex when there are over 20 of them and 2 external hubs in 32 years of detrius because the i-robot can't even get thru the door into this childs bedroom I appropriated for a den in '89 when I married the owner of this house. We had 31 great years, but her ashes are in a pretty vase, sitting on her piano now. COPD is not a gentle way to die, I was there. I squawk about the d-i and the reaction here was as if I had gored and killed the last ox on the planet. It's not d-i's fault in that sense - it's an interaction between serial device detection and the need for a braille TTY - but that's tickles a fairly small subset of installs at best. You happened to fall foul of it and a simple solution that you could carry out - because you are sighted - resolved it for you. I would rebut that it is, the d-i could interrogate and discover that whatever was beyond either of those adapters was not a braille tty. But no, it finds the adapter and assumes its feeding a braille tty. Bad dog, no biscuit. I never went any where near that line in the installers menu on any of those installs. I have met, on a different mailing list, the person that was done for, and have not mentioned the frustration this has caused me to him. He has enough chutzpah for 10 folks, trying to run OpenSCAD by listening to orca in German which I assume it speaks better than the broken English it used for me. I can do nothing but admire him for trying... He, I'm sure, did not ask to be blinded. I, likewise, did not ask to be frustrated. This last install I chose not to install kde, intending to install tde, but it will not install on bullseye. Broken dependencies. Take that up with the TDE folks - we can't help you, though if you were better able to show us exactly what you mean, one of us might try. Its been reported on their list. I am far from the only one complaining. But it does work for some, so the magic twanger hasn't been found yet. TDE is not the only failure. What is now linuxcnc was originally an NIST project to modernize american manufacturing in the '60's, named EMC then but the accounting firm claimed copyright so it had to be renamed, originally public domain, but now rewritten largely in python, but python3 is moving so fast since Guido stepped away that we can't keep up with it. Works on buster just fine, with a realtime kernel of course. We, the linux people are not fixing bugs, but adding more bugs in the name of eye candy. You did write earlier that you'd managed to install GNOME as well as xfce gnome environment, but not one of its desktops, the environment is installed. That was install #31, So I chose xfce4 for #32 because it runs fine on 5 other machines here. And digikam, if I boot from the other drive, also with 11-3 on it, but running kde, works flawlessly there. But despite pulling in 261 other bit and pieces of kde on this drive when it was told to install digikam, apt did not pull in enough dependencies to make importing from a camera work. I had to pull the battery, then the card and plug it into a reader, find it in gimp, load and save the picture I wanted someplace else. So I got the pix I wanted. I built this machine to use, not fight with a broken installer and now the package manager. Is there some option I can set in synaptic to make it fully resolve the missing dependencies? The installer isn't broken - without sight of the dependencies we can't help, I think. I understand the frustration - I really do - but the rest of us following on the list need information that isn't forthcoming in order to be more helpful. Sometimes you might have to resort to a command line apt/apt-get or aptitude to resolve whether or not synaptic is at fault in the
Re: Frozen mouse and keyboard
Thanks very much, David, for your help. Unfortunately it is not possible to log in to the PC from elsewhere. As to most of your other points, they will have to wait for another similar freeze. I was not able to check logs because, subsequent to the freezing, the PC had to be rebooted due to a mains power cut and the journald system does not persist across boots. On 19:36, Wed, 15 Jun 2022 David Wright On Wed 15 Jun 2022 at 09:21:58 (+0100), Mick Ab wrote: > > I have a fairly new desktop PC running Debian 11. Recently there have > been > > a few occasions when the PC has failed to > > be woken up in the morning after being left overnight. The mouse and > > keyboard are frozen. Sometimes the monitor appears to be off and on > > one occasion it was on. > > Like others, I would try logging in over the network to see if > that is still up. > > Apart from that, I would take a careful look at the BIOS settings > under Power Management. > > Assuming your mouse and keyboard are USB or unwired, perhaps > the USB ports are powering down too? If you plug in a USB stick, > does it light up as normal? > > If there's an ethernet card, is the light still on? Does it > react to (un)plugging? > > Disks spinning? > > How long did the logs keep updating during the night? > > IOW just how dead is the machine? > > > A hard reboot has been used to reset the PC, but it is not a good idea to > > keep doing that. > > Modern filesystems/journals etc are pretty forgiving. > Modern hardware should be unharmed by the experience. > (Unlike back in the days of parking disk heads.) > > Cheers, > David. > >
Re: digikam import fails
On Fri, Jun 17, 2022 at 08:05:16AM -0400, gene heskett wrote: > On 6/17/22 01:02, to...@tuxteam.de wrote: > > On Thu, Jun 16, 2022 at 08:39:19PM +0100, Brian wrote: > > > > [...] The point about being poitve and constructive rather than snarky is a more general one. > > > > Cheers > I agree 100%. This whole nightmare was started by the installer silently > installing brltty and orca, assuming I was blind just because it found a > plugged in fdti usb<->serial adapter, and by the time I had killed the > noise, the log was still being spammed about 30 lines per keystroke and > the system uptime was in hours. And the reboot was locked up by not finding > brltty, so that was about the first 25 re-installs. It was the only way > to reboot. > Early on in your 25 reinstalls, I and others suggested you unplug the serial leads and try again. Once you were able to do that, you got a more usual install where that option is skipped. > And I'm catching hell because I didn't trace down my USB tree and unplug > everything during the install. > As above: you were advised to do this - when you finally did, it worked as expected. > I squawk about the d-i and the reaction here was if I had gored and > killed the last ox on the planet. > It's not d-i's fault in that sense - it's an interaction between serial device detection and the need for a braille TTY - but that's tickles a fairly small subset of installs at best. You happened to fall foul of it and a simple solution that you could carry out - because you are sighted - resolved it for you. > I never went any where near that line in the installers menu on any of > those installs. I have met, on a different mailing list, the person that > was done for, and have not mentioned the frustration this has caused me > to him. He has enough chutzpah for 10 folks, trying to run OpenSCAD by > listening to orca in German which I assume it speaks better than the > broken English it used for me. I can do nothing but admire him for trying... > > He, I'm sure, did not ask to be blinded. I, likewise, did not ask to be > frustrated. This last install I chose not to install kde, intending to > install tde, but it will not install on bullseye. Broken dependencies. > Take that up with the TDE folks - we can't help you, though if you were better able to show us exactly what you mean, one of us might try. You did write earlier that you'd managed to install GNOME as well as xfce > That was install #31, > > So I chose xfce4 for #32 because it runs fine on 5 other machines here. > And digikam, if I boot from the other drive, also with 11-3 on it, but > running kde, works flawlessly there. But despite pulling in 261 other > bit and pieces of kde on this drive when it was told to install digikam, > apt did not pull in enough dependencies to make importing from a camera > work. I had to pull the battery, then the card and plug it into a reader, > find it in gimp, load and save the picture I wanted someplace else. So > I got the pix I wanted. > > I built this machine to use, not fight with a broken installer and now > the package manager. Is there some option I can set in synaptic to make > it fully resolve the missing dependencies? The installer isn't broken - without sight of the dependencies we can't help, I think. I understand the frustration - I really do - but the rest of us following on the list need information that isn't forthcoming in order to be more helpful. Sometimes you might have to resort to a command line apt/apt-get or aptitude to resolve whether or not synaptic is at fault in the information it's showing you. > > That's today's first question as I strive to make this machine usable. > Again. > > Thank you. > > Cheers, Gene Heskett. > -- Cheers - and with every good wish, Andy Cater > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author, 1940) > If we desire respect for the law, we must first make the law respectable. > - Louis D. Brandeis >
Re: digikam import fails
On Fri 17 Jun 2022 at 13:57:00 +0200, to...@tuxteam.de wrote: > On Fri, Jun 17, 2022 at 12:53:02PM +0100, Brian wrote: > > On Fri 17 Jun 2022 at 06:59:11 +0200, to...@tuxteam.de wrote: > > > > > On Thu, Jun 16, 2022 at 08:39:19PM +0100, Brian wrote: > > > > > > [...] > > > > > > > Is this the first time you have tried this? > > > > > > > > Go for another 32 times and you could get success :). > > > > > > > > Just a suggestion, in the light of your recent experiences. > > > > > > This is unnecessarily rude. If you can't cope with how some > > > folks ask for help here (shit happens! -- it happens to me > > > too), it'd be better to shut up instead of pouring snark on > > > others. That'd make this a better place. > > > > I thought the smiley wouls have taken the edge off the remark. > > Perhaps I was over-sensitive. My apologies in that case. I do not think apologies are necessary. The reminder to attempt really helpful and tolerant responses is well taken. -- Brian.
Re: digikam import fails
On 6/17/22 01:02, to...@tuxteam.de wrote: On Thu, Jun 16, 2022 at 08:39:19PM +0100, Brian wrote: [...] Is this the first time you have tried this? Go for another 32 times and you could get success :). Just a suggestion, in the light of your recent experiences. This is unnecessarily rude. If you can't cope with how some folks ask for help here (shit happens! -- it happens to me too), it'd be better to shut up instead of pouring snark on others. That'd make this a better place. Cheers I agree 100%. This whole nightmare was started by the installer silently installing brltty and orca, assuming I was blind just because it found a plugged in fdti usb<->serial adapter, and by the time I had killed the noise, the log was still being spammed about 30 lines per keystroke and the system uptime was in hours. And the reboot was locked up by not finding brltty, so that was about the first 25 re-installs. It was the only way to reboot. And I'm catching hell because I didn't trace down my USB tree and unplug everything during the install. I squawk about the d-i and the reaction here was if I had gored and killed the last ox on the planet. I never went any where near that line in the installers menu on any of those installs. I have met, on a different mailing list, the person that was done for, and have not mentioned the frustration this has caused me to him. He has enough chutzpah for 10 folks, trying to run OpenSCAD by listening to orca in German which I assume it speaks better than the broken English it used for me. I can do nothing but admire him for trying... He, I'm sure, did not ask to be blinded. I, likewise, did not ask to be frustrated. This last install I chose not to install kde, intending to install tde, but it will not install on bullseye. Broken dependencies. That was install #31, So I chose xfce4 for #32 because it runs fine on 5 other machines here. And digikam, if I boot from the other drive, also with 11-3 on it, but running kde, works flawlessly there. But despite pulling in 261 other bit and pieces of kde on this drive when it was told to install digikam, apt did not pull in enough dependencies to make importing from a camera work. I had to pull the battery, then the card and plug it into a reader, find it in gimp, load and save the picture I wanted someplace else. So I got the pix I wanted. I built this machine to use, not fight with a broken installer and now the package manager. Is there some option I can set in synaptic to make it fully resolve the missing dependencies? That's today's first question as I strive to make this machine usable. Again. Thank you. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: digikam import fails
On Fri, Jun 17, 2022 at 12:53:02PM +0100, Brian wrote: > On Fri 17 Jun 2022 at 06:59:11 +0200, to...@tuxteam.de wrote: > > > On Thu, Jun 16, 2022 at 08:39:19PM +0100, Brian wrote: > > > > [...] > > > > > Is this the first time you have tried this? > > > > > > Go for another 32 times and you could get success :). > > > > > > Just a suggestion, in the light of your recent experiences. > > > > This is unnecessarily rude. If you can't cope with how some > > folks ask for help here (shit happens! -- it happens to me > > too), it'd be better to shut up instead of pouring snark on > > others. That'd make this a better place. > > I thought the smiley wouls have taken the edge off the remark. Perhaps I was over-sensitive. My apologies in that case. Cheers -- t signature.asc Description: PGP signature
Re: digikam import fails
On Fri 17 Jun 2022 at 06:59:11 +0200, to...@tuxteam.de wrote: > On Thu, Jun 16, 2022 at 08:39:19PM +0100, Brian wrote: > > [...] > > > Is this the first time you have tried this? > > > > Go for another 32 times and you could get success :). > > > > Just a suggestion, in the light of your recent experiences. > > This is unnecessarily rude. If you can't cope with how some > folks ask for help here (shit happens! -- it happens to me > too), it'd be better to shut up instead of pouring snark on > others. That'd make this a better place. I thought the smiley wouls have taken the edge off the remark. -- Brian.
Re: non installed printer can not be removed
On Thu 16 Jun 2022 at 23:13:11 +0200, Hans wrote: > Hi folks, > > I am struggeling with a little problem, I can not explain. > > A friend of mine uses a printer (Samsung SL-C480FW), which is connected to > the > router with wireless. However, although there are no drivers and no ppd-files > installed, the printer is seen by cups (and also by system-printer-config) > but > can not be used (think, because the missing ppd-file). Give 'ls -l /etc/cups/ppd'. > When this is installed, udev-entries and so on are set, then the printer is > seen for example with ipp://192.168.*.*. > > However, printing does not work, although the printer gets data, but then > hangs. I believe, this is a driver problem (because this appeared, since my > friend got a new router (FritzBox). > > I hope, for this I will find a solution, so hints are welcome, buut not the > reason for this thread. > > Much more I am interested, to know, why I can not delete the printer in CUPS > or system-config-printer? Any printer I add, can be deleted, but the last > entry can not be deleted. The cups-browsed docs and our wiki should help with this. > What is wrong? Why does the kernel see the correct printer, and where does it > get its information? It is not connected at the USB-port, so no information > could be taken from this. The kernel is not involved in printer dicsovery. mdns/DNS-sd is. -- Brian.
Re: How to change lightdm background in bullseye? (additional: weird stat behaviour)
On 16/06/2022 06:47, Christoph K. wrote: Procedure: 1. touch test.txt 2. stat test.txt -> correct access time from touch 3. cat test.txt 4. stat test.txt -> access time changed due to cat - fine 5. cat test.txt 6. stat test.txt -> still the same access time as in step 4 - caching? 7. reboot 8. cat test.txt 9. stat test.txt -> STILL the same access time as in step 4 - WTF? Expectations: 1) After a reboot there is no cache to read from. 2) The cat command accesses the file. 3) Stat shows the time of "cat" in the access time stamp. But 3) does not happen. More precisely: It only happens sometimes. Question 3: Could someone please explain to me what's going on here with stat? Looks like the relatime option, which has been the default for some time: https://www.linuxquestions.org/questions/linux-hardware-18/what-does-mount-option-relatime-4175575024/ -- Não tenha pressa, mas não perca tempo --José Saramago Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: virtualbox kernel modules?
On Fri, Jun 17, 2022 at 12:45 AM Keith Bainbridge wrote: > > > On 17/6/22 00:08, Boyan Penkov wrote: > > On Thu, Jun 16, 2022 at 12:09 AM Keith Bainbridge > > wrote: > >>> Cheers! > >> > >> Good afternoon Boyan > >> > >> What happened when you installed to 2 suggested items? > > Hey Keith -- yes, thanks for the pointer; you're absolutely correct... > > Somehow linux-image-headers was not installed on this machine. Once > > it was, cleaned some stuff up, and this problem went away... > > > > Of course, question for the DMs, then -- why not make the headers a > > dependency of virtualbox-dkms? Oops, I mean to send this to the list as well.. > > > > Thanks kindly! > > Been there before. > > Yes, it should be a required package for VBox. Perhaps we should record > this where such difficulties go, but I can never remember the list name > when I want it (like now). > > Frankly, it's part of the reason I prefer LinuxMint Debian. A lot more > user packages are installed by default. > > > By the bye, it's good form to reply to the list, not just the responder. > Yes, you're right -- wrong button on this end... Anyway, thanks kindly, and cheers! > -- > All the best > > Keith Bainbridge > > keithrbaugro...@gmail.com > -- Boyan Penkov
