Re: Tiling display support
Oh, thanks, I've reread specs. It says 'refresh rate up to 240Hz', but for full resolution it's 5120 x 1440 | 60 Hz. There is LG, which promises 3840 x 2160 144Hz. I'll be more careful. Which LG model offers 144 Hz at 3480 x 2160? Because I am shopping for a high-refresh 4k device right now, and I haven't run across any model like that from LG. Mark (Preferably 32-inch.)
Re: Problemes amb automysqlbackup combinat amb un "locale" en català
Doncs jo ho entenc com un bug del propi locale. Voleu dir que som l'única llengua que es troba en aquesta situació? Com a primer plantejament caldria considerar la correcció del locale per tal que un date +%B retorni el mes sense preposició. En 2n terme, com diu l'Eloi, té tota la pinta que l'script es podria millorar. La opció menys intrusiva pero encara prou generalista, donat que veig que l'script no fa servei noms absoluts del programa date, crec que seria: - crear un wrapper local per a la comanda date que: - si el pare és aquest script de backup en qüestió li assignes un locale que sàpigues que funcioni. - Si no, res - seguidament, s'invoca el programa date habitual Amb una bona configuració del PATH, entenc que hauria de funcionar. El ds., 19 des. 2020, 20.57, Eloi va escriure: > Comento entre solucions i retallo part del missatge > > El 19/12/20 a les 19:48, ores...@riseup.net ha escrit: > > Benvolguda llista, a veure si em podeu ajudar en una cosa: > > > > [...] > > > > Fent una mica de recerca he pogut deduir l'origen del problema i fins i > > tot sabria solucionar-lo, però voldria saber si hi ha alguna manera > > millor de la que jo penso. M'explico: > > > > "automysqlbackup" és un script situat a /usr/sbin. Les línies rellevants > > d'aquest script són les següents: > > > > > > DATE=`date +%Y-%m-%d_%Hh%Mm`# Datestamp e.g > > 2002-09-21 > > DOW=`date +%A` # Day of > > the week e.g. Monday > > DNOW=`date +%u` # Day number of > > the week 1 to 7 where 1 represents Monday > > DOM=`date +%d` # Date > > of the Month e.g. 27 > > M=`date +%B`# Month > > e.g January > > W=`date +%V`# Week > > Number e.g 37 > > > > ... > > > > # Monthly Full Backup of all Databases > > (...) > > dbdump "$MDB" "$BACKUPDIR/monthly/$MDB/${MDB}_$DATE.$M.$MDB.sql" > > > > > > O sigui que usa "dbdump" (que és una funció definida en un altre lloc de > > l'script i acaba usant "mysqldump") amb un nom de fitxer que expandeix > > la variable "$M", la qual és el resultat de "date +%B" que, en un > > sistema amb locale en català donarà "de desembre" si l'executeu avui, > > per exemple. > > Crec que part del problema pot venir, precisament, d'aquesta la funció > dbdump (no uso mysql i no ho puc verificar). Tenir espais en blanc a > noms de fitxer, tot i que en general és bona pràctica evitar-los, no > hauria de ser un problema sempre i quan s'escapin correctament les > variables. En aquest sentit, l'ús de les cometes dobles és correcte en > aquest punt, i el nom del fitxer (així com el del directori) haurien de > ser tolerants. > > Em fa la fila que, en algun lloc de la funció shell dbdump, hi haurà un > $2 en lloc d'un "$2" a l'hora d'escriure el fitxer de sortida. A menys > que se sàpiga del cert que no hi haurà espais en blanc o que precisament > interessi que els espais impliquin una separació d'elements, tota > referència a una variable de shell jo la posaria entre cometes dobles > (compte, que les simples signifiquen quelcom ben diferent!) > > > Tal i com ho veig jo, podria fer el següent: > > > > 1) Canviar el "locale" del sistema, el problema és que és un servidor > > que córre un Moodle i si canvio el locale del sistema hi ha algunes > > cosetes del moodle que surten en anglès. > > No necessites canviar el locale del sistema, només el del propi shell, > ja sigui cridant-lo passant com a prefix: > > LC_ALL=C automysqlbackup > > En general, per a scripts de backups que usen dates no és mala idea, > especialment si s'usen noms literals de mes o del dia de la setmana, > cosa que personalment evito perquè pots acabar amb una col·lecció de > còpies amb noms inconsistents entre elles si s'han generat amb locales > diferents > > > 2) Canviar l'script del automysqlbackup per tal que no posi el nom del > > mes, el posi sense espai o alguna cosa semblant. El problema que hi veig > > és que ho hauria de refer en cada actualització del automysqlbackup. No > > em sembla una bona idea. > Jo obriria un bug, precisament per evitar el que deia en en paràgraf > anterior > > 3) Potser podria fer un terme mig i crear una configuració "local" del > > automysqlbackup, que no es veuria sobreescrita en actualitzar el paquet, > > i que forcés un "locale" anglès en executar-se. Potser és la millor > > manera però, ni que sigui per curiositat, hi ha alguna manera > > d'arreglar-ho preservant el nom del mes en català? Com ho faríeu > > vosaltres? > > Pots crear un shell on preparis configuracions, com la del locale, i fer > servir aquest script. Fins i tot podries arribar a donar-li el mateix > nom i posar-lo en una
Re: Mysterious Clementine dependency on libgcrypt.so.11
deloptes writes: > Anssi Saari wrote: > >> Never mind, old libmtp in /usr/local was the problem. Note to self, >> these should be cleaned up sometimes... > > One good advise is to isolate custom builds and follow the rule > 1. if possible build debian package That doesn't do much by itself. > 2. if not possible isolate in dedicated "prefix" for example /opt/clementine > in this case create a startup script with PATH and LD_LIBRARY_PATH Possible. I've gotten into the habit of installing self built stuff under /usr/local and non-free binaries under /opt. Or actually I put my huge library of two AppImages under /opt too. I've thought about installing "environment modules" since that's what we use at work to manage what version of what software is in $PATH etc. Looks like it's even packaged for Debian as environment-modules. But kind of overkill for my purposes and we have people to maintain that at work so it's not like I'm familiar with it. > 3. keep track of such customizations As I only have two places to check so keeping track isn't a problem. Remembering to remove old stuff is, even Debian packages. Trying to figure out this problem I removed over 100 packages that were from oldstable (i.e. Stretch) and no longer in Buster. Mostly libs that had no dependencies to anything so probably stuff that was really old.
Re: Cloud-init in Debian
You might have better luck asking on debian-cloud: https://lists.debian.org/debian-cloud/ On December 19, 2020 4:31:22 PM CST, James Allsopp wrote: >Hi, >Does anyone have an example or tutorial for using cloud-init with >debian >images. I'm currently trying to do terraform with kvm, but struggling >as >although terraform picks up the cloud-init, the fqdn and the ssh key >isn't >working. I'm trying to use this image >https://cdimage.debian.org/cdimage/cloud/buster/20201214-484/debian-10-genericcloud-amd64-20201214-484.qcow2 >I'm not entirely sure if this is the correct image or not? >A lot of the instructions online are for ubuntu or red hat. >Thanks >James
Re: Problemes amb automysqlbackup combinat amb un "locale" en català
Jo ho faig amb admidb, i programo les còpies a /etc/cron.daily/... Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 19/12/20 a les 19:48, ores...@riseup.net ha escrit: > Benvolguda llista, a veure si em podeu ajudar en una cosa: > > Uso automysqlbackup per fer les còpies de seguretat d'una base de dades. > Tot funciona correctament excepte els backups mensuals, atès que tinc el > locale del sistema en català i la majoria de mesos tenen un espai en el > nom, cosa que fa que el backup falli. Com a mostra, aquest és el llistat > del directori on van a parar els backups mensuals: > > root@circuits:/home/automysqlbackup/monthly/moodle# ll > total 26052 > -rw--- 1 root root 12393310 d’ag. 1 06:25 > moodle_2020-08-01_06h25m.d’agost.moodle.sql.gz > -rw--- 1 root root0 de set. 1 06:25 > moodle_2020-09-01_06h25m.de > -rw--- 1 root root 14282383 d’oct.1 06:25 > moodle_2020-10-01_06h25m.d’octubre.moodle.sql.gz > -rw--- 1 root root0 de nov. 1 06:25 > moodle_2020-11-01_06h25m.de > -rw--- 1 root root0 de des. 1 06:25 > moodle_2020-12-01_06h25m.de > > Veieu? Només s'han creat bé els d'agost i octubre perquè aquests mesos > l'article va apostrofat i no hi ha espais en blanc en el nom. > > Fent una mica de recerca he pogut deduir l'origen del problema i fins i > tot sabria solucionar-lo, però voldria saber si hi ha alguna manera > millor de la que jo penso. M'explico: > > "automysqlbackup" és un script situat a /usr/sbin. Les línies rellevants > d'aquest script són les següents: > > > DATE=`date +%Y-%m-%d_%Hh%Mm`# Datestamp e.g > 2002-09-21 > DOW=`date +%A` # Day of > the week e.g. Monday > DNOW=`date +%u` # Day number of > the week 1 to 7 where 1 represents Monday > DOM=`date +%d` # Date > of the Month e.g. 27 > M=`date +%B`# Month > e.g January > W=`date +%V`# Week > Number e.g 37 > > ... > > # Monthly Full Backup of all Databases > (...) > dbdump "$MDB" "$BACKUPDIR/monthly/$MDB/${MDB}_$DATE.$M.$MDB.sql" > > > O sigui que usa "dbdump" (que és una funció definida en un altre lloc de > l'script i acaba usant "mysqldump") amb un nom de fitxer que expandeix > la variable "$M", la qual és el resultat de "date +%B" que, en un > sistema amb locale en català donarà "de desembre" si l'executeu avui, > per exemple. > > Tal i com ho veig jo, podria fer el següent: > > 1) Canviar el "locale" del sistema, el problema és que és un servidor > que córre un Moodle i si canvio el locale del sistema hi ha algunes > cosetes del moodle que surten en anglès. > > 2) Canviar l'script del automysqlbackup per tal que no posi el nom del > mes, el posi sense espai o alguna cosa semblant. El problema que hi veig > és que ho hauria de refer en cada actualització del automysqlbackup. No > em sembla una bona idea. > > 3) Potser podria fer un terme mig i crear una configuració "local" del > automysqlbackup, que no es veuria sobreescrita en actualitzar el paquet, > i que forcés un "locale" anglès en executar-se. Potser és la millor > manera però, ni que sigui per curiositat, hi ha alguna manera > d'arreglar-ho preservant el nom del mes en català? Com ho faríeu > vosaltres? > > Gràcies! > > Orestes. >
Re: Nieuwste versie tcl, sqlite en DB Browser
On Sat, Dec 19, 2020 at 05:56:07PM +0100, Cecil Westerhof wrote: > Ik gebruik tcl en SQLite veel en DB Browser regelmatig. Ik zit erover > te denken om te zorgen dat ik de nieuwste versies op mijn systeem heb. > Ik kan me voorstellen dat het voor anderen ook interessant kan zijn. > Hoe moeilijk zou het zijn om die packages te maken en op te laten > nemen in de Debian tree? Vergelijkbaar met schaatsen. Het is iets wat een best grote groep mensen kan leren. Groeten Geert Stappers -- Silence is hard to parse
Re: Tiling display support
George Shuklin wrote: > On 12/18/20 9:55 PM, Dan Ritter wrote: > > George Shuklin wrote: > > > I continue to choose hardware carefully, and the next issue (I found a lot > > > on it) is support for tiling displays. They uses multiple streams inside > > > DisplayPort to achieve high resolution with high frame rate. It's called > > > MST > > > (vs classic single SST), and I found few people complaining about issues > > > with it. All those complains are relatively old (2+ years). > > > > > > Does someone run desktop with 4k screen and high frame rate (150 fps+)? > > > What > > > monitor and gpu are you using? Are you having any issues? > > > > There are no 4K 150Hz monitors currently commercially available. > > > > There are some 4K 120Hz monitors, starting at $800 or so. > > > > What is your use case? > > > > -dsr- > > Oh, thanks, I've reread specs. It says 'refresh rate up to 240Hz', but for > full resolution it's 5120 x 1440 | 60 Hz. There is LG, which promises 3840 x > 2160 144Hz. I'll be more careful. > > Anyway, my concern is MST support in Linux. Or, can 4k 120Hz fit through a > single DP (SST mode)? The Radeon 6900XT has DisplayPort 1.4. The NVidia 2080GTX has DisplayPort 1.4. DP 1.4 supports 4K at 120Hz. DP 2.0 has not yet shown up. What are you trying to do? -dsr-
Cloud-init in Debian
Hi, Does anyone have an example or tutorial for using cloud-init with debian images. I'm currently trying to do terraform with kvm, but struggling as although terraform picks up the cloud-init, the fqdn and the ssh key isn't working. I'm trying to use this image https://cdimage.debian.org/cdimage/cloud/buster/20201214-484/debian-10-genericcloud-amd64-20201214-484.qcow2 I'm not entirely sure if this is the correct image or not? A lot of the instructions online are for ubuntu or red hat. Thanks James
Re: Mysterious Clementine dependency on libgcrypt.so.11
Anssi Saari wrote: > Never mind, old libmtp in /usr/local was the problem. Note to self, > these should be cleaned up sometimes... One good advise is to isolate custom builds and follow the rule 1. if possible build debian package 2. if not possible isolate in dedicated "prefix" for example /opt/clementine in this case create a startup script with PATH and LD_LIBRARY_PATH 3. keep track of such customizations
Re: Debian 10 64bit
Brian wrote: > In what way does it rock? It hasn't any focus on Debian. Examples > welcome. Not on Debian, but it explains programs, subsystems and configurations much better. AFAIR it was discussed once here. What I was reading there, because the info I found on debian was confusing, outdated or unstructured udev - ArchWiki udisks - ArchWiki NetworkManager - ArchWiki CPU frequency scaling - ArchWiki GRUB - ArchWiki GPT fdisk - ArchWiki PulseAudio - ArchWiki Bluetooth - ArchWiki etc. For me personally it worked always like following. Some details and understanding required (example GPT when moving to UEFI). Debian Wiki explains how to configure and use Debian with GPT and UEFI. ArchWiki gives all technical details on the subject. It really rocks, but I mean the combination of the two.
Re: NULL pointer dereference
On 19.12.2020 21:13, Grzesiek Sójka wrote: Hi there, I found the following in my "server" log: == BUG: unable to handle kernel NULL pointer dereference at 0008 PGD 0 P4D 0 Oops: [#2] SMP PTI CPU: 5 PID: 12441 Comm: awk Tainted: G D 4.19.0-13-amd64 #1 Debian 4.19.160-2 Hardware name: FUJITSU D3162-B1/D3162-B1, BIOS V4.6.5.3 R1.23.0 for D3162-B1x 12/01/2014 RIP: 0010:unmap_page_range+0x561/0xa60 Code: 80 00 00 00 01 e8 4f 2b 01 00 49 8b 07 f6 c4 80 0f 84 0e 03 00 00 4c 89 ff e8 6b 91 fe ff 85 c0 0f 88 e6 02 00 00 49 8b 46 28 <8b> 50 08 8d 4a 01 89 48 08 4c 89 7c d0 10 3b 48 0c 0f 84 d2 00 00 RSP: 0018:9c3a49167cd0 EFLAGS: 00010206 RAX: RBX: 8e2f47a83a10 RCX: 0001 RDX: RSI: RDI: 8e2f7dd2 RBP: 7faa2ed43000 R08: R09: 8e2ef8ae1c70 R10: 8e2f9e5df000 R11: R12: 7faa2ed42000 R13: 00014fd44025 R14: 9c3a49167dd0 R15: d073853f5100 FS: () GS:8e2f7e14() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0008 CR3: 00015020a003 CR4: 000606e0 Call Trace: unmap_vmas+0x7f/0xb0 exit_mmap+0xaa/0x180 mmput+0x54/0x130 do_exit+0x33f/0xbb0 ? handle_mm_fault+0xd6/0x200 do_group_exit+0x3a/0xa0 __x64_sys_exit_group+0x14/0x20 do_syscall_64+0x53/0x110 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7faa2eaa99d6 Code: Bad RIP value. RSP: 002b:7ffd860931d8 EFLAGS: 0246 ORIG_RAX: 00e7 RAX: ffda RBX: 7faa2eb9a760 RCX: 7faa2eaa99d6 RDX: RSI: 003c RDI: RBP: R08: 00e7 R09: ff80 R10: 7ffd86093096 R11: 0246 R12: 7faa2eb9a760 R13: 0001 R14: 7faa2eba3428 R15: Modules linked in: ppp_deflate cfg80211 rfkill 8021q garp stp mrp llc ppp_async crc_ccitt ppp_generic slhc nfsd auth_rpcgss nfs_acl lockd grace sunrpc xt_nat nft_chain_nat_ipv4 nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ipt_REJECT nf_reject_ipv4 nft_limit xt_limit xt_tcpudp nft_compat x_tables nft_counter nf_tables nfnetlink binfmt_misc bonding sch5636 sch56xx_common rc_it913x_v1 it913x af9033 dvb_usb_af9035 dvb_usb_v2 dvb_core rc_core snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_rapl i915 x86_pkg_temp_thermal snd_hda_intel intel_powerclamp snd_hda_codec coretemp snd_hda_core snd_hwdep snd_pcm xhci_pci ehci_pci ahci snd_timer xhci_hcd drm_kms_helper ehci_hcd libahci kvm snd mei_wdt tg3 iTCO_wdt irqbypass mei_me e1000e drm libata usbcore iTCO_vendor_support soundcore lpc_ich libphy mei i2c_algo_bit usb_common mfd_core crct10dif_pclmul crc32_pclmul ppdev ghash_clmulni_intel sg i2c_i801 intel_cstate evdev intel_uncore pcc_cpufreq video parport_pc button intel_rapl_perf pcspkr parport ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sd_mod crc32c_intel aacraid aesni_intel aes_x86_64 crypto_simd scsi_mod cryptd glue_helper thermal fan CR2: 0008 ---[ end trace 1f0672175c6e1ff0 ]--- RIP: 0010:unmap_page_range+0x55d/0xa60 Code: ff 83 ac 84 80 00 00 00 01 e8 4f 2b 01 00 49 8b 07 f6 c4 80 0f 84 0e 03 00 00 4c 89 ff e8 6b 91 fe ff 85 c0 0f 88 e6 02 00 00 <49> 8b 46 28 8b 50 08 8d 4a 01 89 48 08 4c 89 7c d0 10 3b 48 0c 0f RSP: 0018:9c3a43a67cd0 EFLAGS: 00010202 RAX: 0004 RBX: 8e2f47a0deb0 RCX: 0001 RDX: RSI: RDI: 8e2f7dd2 RBP: 7f9f121d7000 R08: R09: 8e2f6a6e09c0 R10: 8e2f9e5df000 R11: R12: 7f9f121d6000 R13: 00081e49f025 R14: 9c3a43a67dd0 R15: d073a07927c0 FS: () GS:8e2f7e14() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7faa2eaa99ac CR3: 00015020a003 CR4: 000606e0 Fixing recursive fault but reboot is needed! This is not the first time, so I suspect a persistent problem. I have no idea how to look for the solution. Any suggestions?? If this is recurring error, was it identical in terms of codes, trace and register data? If it is not identical I suggest to start by checking RAM (and partially a CPU) with Memtest86+ [1] It will be good to know if hardware is fine anyway. Leave the test running overnight or longer. A 10 or so test passes should be enough to tell if RAM is good. Next I'd check official Fujitsu website for BIOS\BMC\Firmware updates for your server\motherboard and update to latest version available. It could be complicated and dangerous process, so be sure to first check out any relevant technical advisories from Fujitsu, that are available for your server system and official guides on update process. [1] https://www.memtest.org/ -- With
Re: Tiling display support
On 12/18/20 9:55 PM, Dan Ritter wrote: George Shuklin wrote: I continue to choose hardware carefully, and the next issue (I found a lot on it) is support for tiling displays. They uses multiple streams inside DisplayPort to achieve high resolution with high frame rate. It's called MST (vs classic single SST), and I found few people complaining about issues with it. All those complains are relatively old (2+ years). Does someone run desktop with 4k screen and high frame rate (150 fps+)? What monitor and gpu are you using? Are you having any issues? There are no 4K 150Hz monitors currently commercially available. There are some 4K 120Hz monitors, starting at $800 or so. What is your use case? -dsr- Oh, thanks, I've reread specs. It says 'refresh rate up to 240Hz', but for full resolution it's 5120 x 1440 | 60 Hz. There is LG, which promises 3840 x 2160 144Hz. I'll be more careful. Anyway, my concern is MST support in Linux. Or, can 4k 120Hz fit through a single DP (SST mode)?
Re: "Service restarts being deferred"
On Sat, Dec 19 2020 at 06:34:35 PM, Jesper Dybdal wrote: > On 2020-12-19 17:14, Dan Ritter wrote: >> Jesper Dybdal wrote: >>> I run Buster with unattended updates configured to allow reboots. >>> >>> Sometimes after an update, the log contains: >>> Service restarts being deferred: ??systemctl restart systemd-logind.service ??systemctl restart unattended-upgrades.service >>> I don't understand why these services are not restarted, if necessary >>> through a reboot. >>> >>> I want my system to be able to run truly unattended for a long time, so >>> necessary restarts should be done without waiting for manual intervention.?? >>> And if the restarts are not necessary, why are they there at all, though >>> deferred? >>> >>> So what have I misunderstood? >> In your /etc/apt/apt.conf.d, edit a file named 50unattended-upgrades >> >> // Automatically reboot *WITHOUT CONFIRMATION* if >> // the file /var/run/reboot-required is found after the upgrade >> Unattended-Upgrade::Automatic-Reboot "true"; >> >> // Automatically reboot even if there are users currently logged >> // in. >> Unattended-Upgrade::Automatic-Reboot-WithUsers "true"; >> >> Without those two lines, you get the behavior you currently >> have. >> >> Not everyone wants automatic reboots; not everyone wants >> automatic reboots even with someone logged in. > > Thanks. > I already have Automatic-Reboot set, and it correctly causes reboot > after for instance kernel upgrades. > I do not have Automatic-Reboot-WithUsers set, since I did not imagine > it would make a difference when there actually are no users logged in. > But I'll try setting it also and see if that somehow makes a difference. >From the documentation of Automatic-Reboot, it only has effect for updates that result in the /var/run/reboot-required file being created. For service restarts, the needrestart configuration would be a better place to start. The comments in /etc/needrestart/needrestart.conf are instructive: # do not restart oneshot services, see also #862840 qr(^apt-daily\.service$) => 0, qr(^apt-daily-upgrade\.service$) => 0, qr(^unattended-upgrades\.service$) => 0, # don't restart systemd-logind, see #798097 qr(^systemd-logind) => 0, Do go through those bug reports and experiment at a safe time before changing things here. -- regards, kushal
Re: Debian 10 64bit
On Fri 18 Dec 2020 at 13:05:26 (-0500), Jerry Mellon wrote: > I installed the Debian 10 64bit from the disks(16) that I purchased. No > down load from outside involved. > PS Not trying to cause a problem, just telling you what I had to todo. I'm sure you're posting in good faith. The problem is that we don't know anything about your system without your telling us, and when what you report doesn't seem likely, then it helps if you would post some uninterpreted evidence. That's why I asked you to post the output of this command: ls --full-time /etc/sudoers /etc/sudoers.d/ The dates and sizes of the files will help us determine whether the /etc/sudoers file has been edited, and by whom¹. Since around the time of squeeze, this file should never require editing on 99% of Debian systems, on account of its last line and the existence of the /etc/sudoers.d/ directory. If you don't post some evidence like that, then it's difficult for me to believe other than that you misunderstood the choices you made with the root password/ability for root to login, and tried to compensate by using, unfortunately, the wrong commands and actions, which made it harder to understand the problem. ¹ Note that it is always most helpful to cut and paste the actual commands and their responses into your posts, obviously mangling any confidential bits. Cheers, David.
Re: NULL pointer dereference
On 12/19/20 8:43 PM, David Christensen wrote: > > Which Debian? Buster, up to date > Which kernel? cat /proc/version Linux version 4.19.0-13-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.160-2 (2020-11-28) > Did you follow the instructions and reboot? Yes, reboot does not help Greg
Re: Problemes amb automysqlbackup combinat amb un "locale" en català
Comento entre solucions i retallo part del missatge El 19/12/20 a les 19:48, ores...@riseup.net ha escrit: Benvolguda llista, a veure si em podeu ajudar en una cosa: [...] Fent una mica de recerca he pogut deduir l'origen del problema i fins i tot sabria solucionar-lo, però voldria saber si hi ha alguna manera millor de la que jo penso. M'explico: "automysqlbackup" és un script situat a /usr/sbin. Les línies rellevants d'aquest script són les següents: DATE=`date +%Y-%m-%d_%Hh%Mm`# Datestamp e.g 2002-09-21 DOW=`date +%A` # Day of the week e.g. Monday DNOW=`date +%u` # Day number of the week 1 to 7 where 1 represents Monday DOM=`date +%d` # Date of the Month e.g. 27 M=`date +%B`# Month e.g January W=`date +%V`# Week Number e.g 37 ... # Monthly Full Backup of all Databases (...) dbdump "$MDB" "$BACKUPDIR/monthly/$MDB/${MDB}_$DATE.$M.$MDB.sql" O sigui que usa "dbdump" (que és una funció definida en un altre lloc de l'script i acaba usant "mysqldump") amb un nom de fitxer que expandeix la variable "$M", la qual és el resultat de "date +%B" que, en un sistema amb locale en català donarà "de desembre" si l'executeu avui, per exemple. Crec que part del problema pot venir, precisament, d'aquesta la funció dbdump (no uso mysql i no ho puc verificar). Tenir espais en blanc a noms de fitxer, tot i que en general és bona pràctica evitar-los, no hauria de ser un problema sempre i quan s'escapin correctament les variables. En aquest sentit, l'ús de les cometes dobles és correcte en aquest punt, i el nom del fitxer (així com el del directori) haurien de ser tolerants. Em fa la fila que, en algun lloc de la funció shell dbdump, hi haurà un $2 en lloc d'un "$2" a l'hora d'escriure el fitxer de sortida. A menys que se sàpiga del cert que no hi haurà espais en blanc o que precisament interessi que els espais impliquin una separació d'elements, tota referència a una variable de shell jo la posaria entre cometes dobles (compte, que les simples signifiquen quelcom ben diferent!) Tal i com ho veig jo, podria fer el següent: 1) Canviar el "locale" del sistema, el problema és que és un servidor que córre un Moodle i si canvio el locale del sistema hi ha algunes cosetes del moodle que surten en anglès. No necessites canviar el locale del sistema, només el del propi shell, ja sigui cridant-lo passant com a prefix: LC_ALL=C automysqlbackup En general, per a scripts de backups que usen dates no és mala idea, especialment si s'usen noms literals de mes o del dia de la setmana, cosa que personalment evito perquè pots acabar amb una col·lecció de còpies amb noms inconsistents entre elles si s'han generat amb locales diferents 2) Canviar l'script del automysqlbackup per tal que no posi el nom del mes, el posi sense espai o alguna cosa semblant. El problema que hi veig és que ho hauria de refer en cada actualització del automysqlbackup. No em sembla una bona idea. Jo obriria un bug, precisament per evitar el que deia en en paràgraf anterior 3) Potser podria fer un terme mig i crear una configuració "local" del automysqlbackup, que no es veuria sobreescrita en actualitzar el paquet, i que forcés un "locale" anglès en executar-se. Potser és la millor manera però, ni que sigui per curiositat, hi ha alguna manera d'arreglar-ho preservant el nom del mes en català? Com ho faríeu vosaltres? Pots crear un shell on preparis configuracions, com la del locale, i fer servir aquest script. Fins i tot podries arribar a donar-li el mateix nom i posar-lo en una ubicació amb major prioritat al path (cosa que personalment no m'agrada), sempre que l'script es cridi sense ruta absoluta. En el teu cas podria ser una cosa tan simple com això: #!/bin/sh export LC_ALL=C automysqlbackup "$@" Pel que fa a poder mantenir els noms dels mesos en català, una altra alternativa seria tocar el teu locale (no en tinc experiència ni sabria dir fins a quin punt és realment viable i/o prudent) i modificar els mesos per tal que s'escriguin sense l'article, és a dir, "maig" en lloc de "de maig". Gràcies! Orestes.
Re: NULL pointer dereference
On 2020-12-19 08:13, Grzesiek Sójka wrote: Hi there, I found the following in my "server" log: == BUG: unable to handle kernel NULL pointer dereference at 0008 PGD 0 P4D 0 Oops: [#2] SMP PTI CPU: 5 PID: 12441 Comm: awk Tainted: G D 4.19.0-13-amd64 #1 Debian 4.19.160-2 Hardware name: FUJITSU D3162-B1/D3162-B1, BIOS V4.6.5.3 R1.23.0 for D3162-B1x 12/01/2014 RIP: 0010:unmap_page_range+0x561/0xa60 Code: 80 00 00 00 01 e8 4f 2b 01 00 49 8b 07 f6 c4 80 0f 84 0e 03 00 00 4c 89 ff e8 6b 91 fe ff 85 c0 0f 88 e6 02 00 00 49 8b 46 28 <8b> 50 08 8d 4a 01 89 48 08 4c 89 7c d0 10 3b 48 0c 0f 84 d2 00 00 RSP: 0018:9c3a49167cd0 EFLAGS: 00010206 RAX: RBX: 8e2f47a83a10 RCX: 0001 RDX: RSI: RDI: 8e2f7dd2 RBP: 7faa2ed43000 R08: R09: 8e2ef8ae1c70 R10: 8e2f9e5df000 R11: R12: 7faa2ed42000 R13: 00014fd44025 R14: 9c3a49167dd0 R15: d073853f5100 FS: () GS:8e2f7e14() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0008 CR3: 00015020a003 CR4: 000606e0 Call Trace: unmap_vmas+0x7f/0xb0 exit_mmap+0xaa/0x180 mmput+0x54/0x130 do_exit+0x33f/0xbb0 ? handle_mm_fault+0xd6/0x200 do_group_exit+0x3a/0xa0 __x64_sys_exit_group+0x14/0x20 do_syscall_64+0x53/0x110 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7faa2eaa99d6 Code: Bad RIP value. RSP: 002b:7ffd860931d8 EFLAGS: 0246 ORIG_RAX: 00e7 RAX: ffda RBX: 7faa2eb9a760 RCX: 7faa2eaa99d6 RDX: RSI: 003c RDI: RBP: R08: 00e7 R09: ff80 R10: 7ffd86093096 R11: 0246 R12: 7faa2eb9a760 R13: 0001 R14: 7faa2eba3428 R15: Modules linked in: ppp_deflate cfg80211 rfkill 8021q garp stp mrp llc ppp_async crc_ccitt ppp_generic slhc nfsd auth_rpcgss nfs_acl lockd grace sunrpc xt_nat nft_chain_nat_ipv4 nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ipt_REJECT nf_reject_ipv4 nft_limit xt_limit xt_tcpudp nft_compat x_tables nft_counter nf_tables nfnetlink binfmt_misc bonding sch5636 sch56xx_common rc_it913x_v1 it913x af9033 dvb_usb_af9035 dvb_usb_v2 dvb_core rc_core snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_rapl i915 x86_pkg_temp_thermal snd_hda_intel intel_powerclamp snd_hda_codec coretemp snd_hda_core snd_hwdep snd_pcm xhci_pci ehci_pci ahci snd_timer xhci_hcd drm_kms_helper ehci_hcd libahci kvm snd mei_wdt tg3 iTCO_wdt irqbypass mei_me e1000e drm libata usbcore iTCO_vendor_support soundcore lpc_ich libphy mei i2c_algo_bit usb_common mfd_core crct10dif_pclmul crc32_pclmul ppdev ghash_clmulni_intel sg i2c_i801 intel_cstate evdev intel_uncore pcc_cpufreq video parport_pc button intel_rapl_perf pcspkr parport ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sd_mod crc32c_intel aacraid aesni_intel aes_x86_64 crypto_simd scsi_mod cryptd glue_helper thermal fan CR2: 0008 ---[ end trace 1f0672175c6e1ff0 ]--- RIP: 0010:unmap_page_range+0x55d/0xa60 Code: ff 83 ac 84 80 00 00 00 01 e8 4f 2b 01 00 49 8b 07 f6 c4 80 0f 84 0e 03 00 00 4c 89 ff e8 6b 91 fe ff 85 c0 0f 88 e6 02 00 00 <49> 8b 46 28 8b 50 08 8d 4a 01 89 48 08 4c 89 7c d0 10 3b 48 0c 0f RSP: 0018:9c3a43a67cd0 EFLAGS: 00010202 RAX: 0004 RBX: 8e2f47a0deb0 RCX: 0001 RDX: RSI: RDI: 8e2f7dd2 RBP: 7f9f121d7000 R08: R09: 8e2f6a6e09c0 R10: 8e2f9e5df000 R11: R12: 7f9f121d6000 R13: 00081e49f025 R14: 9c3a43a67dd0 R15: d073a07927c0 FS: () GS:8e2f7e14() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7faa2eaa99ac CR3: 00015020a003 CR4: 000606e0 Fixing recursive fault but reboot is needed! This is not the first time, so I suspect a persistent problem. I have no idea how to look for the solution. Any suggestions?? Just in case: # lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset
Re: Debian 10 64bit
On Sat 19 Dec 2020 at 09:43:02 +0100, to...@tuxteam.de wrote: > On Sat, Dec 19, 2020 at 12:01:14AM +0100, deloptes wrote: > > [...] > > > Also I find very helpful the ArchLinux Wiki if I want to know how things > > work in general. They tend to have a bit better (sorry Debian) concept of > > documentation. > > https://wiki.archlinux.org/index.php/Table_of_contents > > As a staunch Debian fanboi myself: the ArchLinux Wiki rocks! In what way does it rock? It hasn't any focus on Debian. Examples welcome. > The nice part about free software and the attitude behind it is that > there's no need to be sorry if "someone else" is better than "us" at > some thing. Enjoy that and offer them whatever it is what you can do > better in exchange. Agreed. -- Brian.
Problemes amb automysqlbackup combinat amb un "locale" en català
Benvolguda llista, a veure si em podeu ajudar en una cosa: Uso automysqlbackup per fer les còpies de seguretat d'una base de dades. Tot funciona correctament excepte els backups mensuals, atès que tinc el locale del sistema en català i la majoria de mesos tenen un espai en el nom, cosa que fa que el backup falli. Com a mostra, aquest és el llistat del directori on van a parar els backups mensuals: root@circuits:/home/automysqlbackup/monthly/moodle# ll total 26052 -rw--- 1 root root 12393310 d’ag. 1 06:25 moodle_2020-08-01_06h25m.d’agost.moodle.sql.gz -rw--- 1 root root0 de set. 1 06:25 moodle_2020-09-01_06h25m.de -rw--- 1 root root 14282383 d’oct.1 06:25 moodle_2020-10-01_06h25m.d’octubre.moodle.sql.gz -rw--- 1 root root0 de nov. 1 06:25 moodle_2020-11-01_06h25m.de -rw--- 1 root root0 de des. 1 06:25 moodle_2020-12-01_06h25m.de Veieu? Només s'han creat bé els d'agost i octubre perquè aquests mesos l'article va apostrofat i no hi ha espais en blanc en el nom. Fent una mica de recerca he pogut deduir l'origen del problema i fins i tot sabria solucionar-lo, però voldria saber si hi ha alguna manera millor de la que jo penso. M'explico: "automysqlbackup" és un script situat a /usr/sbin. Les línies rellevants d'aquest script són les següents: DATE=`date +%Y-%m-%d_%Hh%Mm`# Datestamp e.g 2002-09-21 DOW=`date +%A` # Day of the week e.g. Monday DNOW=`date +%u` # Day number of the week 1 to 7 where 1 represents Monday DOM=`date +%d` # Date of the Month e.g. 27 M=`date +%B`# Month e.g January W=`date +%V`# Week Number e.g 37 ... # Monthly Full Backup of all Databases (...) dbdump "$MDB" "$BACKUPDIR/monthly/$MDB/${MDB}_$DATE.$M.$MDB.sql" O sigui que usa "dbdump" (que és una funció definida en un altre lloc de l'script i acaba usant "mysqldump") amb un nom de fitxer que expandeix la variable "$M", la qual és el resultat de "date +%B" que, en un sistema amb locale en català donarà "de desembre" si l'executeu avui, per exemple. Tal i com ho veig jo, podria fer el següent: 1) Canviar el "locale" del sistema, el problema és que és un servidor que córre un Moodle i si canvio el locale del sistema hi ha algunes cosetes del moodle que surten en anglès. 2) Canviar l'script del automysqlbackup per tal que no posi el nom del mes, el posi sense espai o alguna cosa semblant. El problema que hi veig és que ho hauria de refer en cada actualització del automysqlbackup. No em sembla una bona idea. 3) Potser podria fer un terme mig i crear una configuració "local" del automysqlbackup, que no es veuria sobreescrita en actualitzar el paquet, i que forcés un "locale" anglès en executar-se. Potser és la millor manera però, ni que sigui per curiositat, hi ha alguna manera d'arreglar-ho preservant el nom del mes en català? Com ho faríeu vosaltres? Gràcies! Orestes.
Re: "Service restarts being deferred"
On 2020-12-19 17:14, Dan Ritter wrote: Jesper Dybdal wrote: I run Buster with unattended updates configured to allow reboots. Sometimes after an update, the log contains: Service restarts being deferred: ??systemctl restart systemd-logind.service ??systemctl restart unattended-upgrades.service I don't understand why these services are not restarted, if necessary through a reboot. I want my system to be able to run truly unattended for a long time, so necessary restarts should be done without waiting for manual intervention.?? And if the restarts are not necessary, why are they there at all, though deferred? So what have I misunderstood? In your /etc/apt/apt.conf.d, edit a file named 50unattended-upgrades // Automatically reboot *WITHOUT CONFIRMATION* if // the file /var/run/reboot-required is found after the upgrade Unattended-Upgrade::Automatic-Reboot "true"; // Automatically reboot even if there are users currently logged // in. Unattended-Upgrade::Automatic-Reboot-WithUsers "true"; Without those two lines, you get the behavior you currently have. Not everyone wants automatic reboots; not everyone wants automatic reboots even with someone logged in. Thanks. I already have Automatic-Reboot set, and it correctly causes reboot after for instance kernel upgrades. I do not have Automatic-Reboot-WithUsers set, since I did not imagine it would make a difference when there actually are no users logged in. But I'll try setting it also and see if that somehow makes a difference. -- Jesper Dybdal https://www.dybdal.dk
Re: /bin/sh naar bash i.p.v. dash linken
Ik had helemaal niet gereageerd. :'-( Richard Lucassen writes: > On Wed, 25 Nov 2020 10:52:57 +0100 > Cecil Westerhof wrote: > >> Ik heb er zelf nooit last van gehad, maar door een vraag van iemand >> anders kwam ik erachter dat sh een link is naar dash. Is er een >> mogelijk heid om bij installatie sh naar bash te laten verwijzen? > > ln -sf /bin/bash /bin/sh Dat kan niet na een upgrade terug worden gezet door Debian? > zou ik zeggen, Na installatie dan. Maar verwijs in je eigen scripts > gewoon naar /bin/bash als je bash wilt, dan ben je niet meer > afhankelijk van het feit van hoe de /bin/sh staat. Ik gebruik in mijn (bash) scripts altijd (dat is meer portable): #!/usr/bin/env bash Zelf heb ik het probleem dus ook niet. Liep er tegenaan in een andere groep waar iemand er over 'klaagde'. -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof
Nieuwste versie tcl, sqlite en DB Browser
Ik gebruik tcl en SQLite veel en DB Browser regelmatig. Ik zit erover te denken om te zorgen dat ik de nieuwste versies op mijn systeem heb. Ik kan me voorstellen dat het voor anderen ook interessant kan zijn. Hoe moeilijk zou het zijn om die packages te maken en op te laten nemen in de Debian tree? -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof
Re: Can't print: /var/spool/lpd
On Sat 19 Dec 2020 at 07:05:24 -0300, riveravaldez wrote: > On 12/12/20, Brian wrote: > > On Fri 11 Dec 2020 at 21:33:42 -0300, riveravaldez wrote: > > > >> Hi, I'm having an issue with a Brother HL-3150CDN printer on Debian > >> Testing. > > > > You do not say, so we will assume there is a USB connection. The device > > probably does IPP-over-USB; you will want to read > > > > https://wiki.debian.org/CUPSDriverlessPrinting > > Thanks for your answer, Brian, certainly I'd forget to specify it: > The connection is not USB, it's a network connection (Ethernet), the printer > is connected to the router and through the router I have access to it from > various computers in the house. Ok. That rules out one avenue of exploration. > In the 'Add Printer' page/step, CUPS offers me three options: > 1. Brother HL-3150CDN series - IPP Everywhere > 2. Brother HL-3150CDN seriesm fully driverless, cups-filters 1.28.6 (en) > 3. Brother HL-3150CDN series CUPS (en) > The first and second work fine. Good. This illustrates that a user with a modern Brother printer does not need a non-free Brother driver. > The third one appears twice, and seems to be > generated by the installation of the official drivers from Brother (I tried > both > options with similar result: the printer doesn't seems to receive the > job/printing order). The entries in the "Add Printer" display will have nothing to do with whether the Brother drivers are installed. They will be to do with the URIs discovered and given on the second page of the CUPS web interface. The job not getting to the printer is probably a URI issue. Please give the output of 'lpinfo -v'. > http://localhost:631/jobs/ once said: > > processing since > Sat Dec 19 06:47:26 2020 > "No se ha podido localizar la impresora "BRN30055CA838C7"." > > Which means: "Couldn't find the printer "BR..." A URI or network issue. > But almost always just show the job as "completed". The job is regarded as completed if the filters complete successfully. Looks like they have. [...] > > The installation of this package goes smoothly on my i386 machine. > > Well, here I have those errors. I've tried creating manually the folder: > /var/spool/lpd/hl3150cdn > Which I had to do as root. > Once the folder is created, I reinstalled the packages, and the errors didn't > appeared no more: Jobs will be correctly processed whether or not /var/spool/lpd/hl3150cdn exists. All you have to do is 'mkdir /var/spool/lpd/' because it is this directory the lpr package is looking for. But it is not needed anyway. Brother is at least twenty years behind the times with the packages it distributes. I ask you - lpd in ths day and age? > $ sudo apt-get install --reinstall ./hl3150cdnlpr-1.1.2-1.i386.deb > Reading package lists... Done > Building dependency tree > Reading state information... Done > Note, selecting 'hl3150cdnlpr:i386' instead of > './hl3150cdnlpr-1.1.2-1.i386.deb' > 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 11 not upgraded. > After this operation, 0 B of additional disk space will be used. > Get:1 /(...)/hl3150cdnlpr-1.1.2-1.i386.deb hl3150cdnlpr i386 1.1.2-1 [695 kB] > (Reading database ... 152529 files and directories currently installed.) > Preparing to unpack .../hl3150cdnlpr-1.1.2-1.i386.deb ... > Unpacking hl3150cdnlpr:i386 (1.1.2-1) over (1.1.2-1) ... > Setting up hl3150cdnlpr:i386 (1.1.2-1) ... > > So, no errors. But: > > $ sudo ls -a /var/spool/lpd/hl3150cdn/ > . .. > > So, maybe the installation can't put anything there because the folder > was created > by root? No. It's a bit of Brother nonsense to want /var/spool/lpd/ created. [...] > But no matter the jobs appearing as "completed", the printer doesn't > activates and it doesn't print, so, any idea? Let's also have what you get for 'lpstat -t' and 'lpstat -l -e'. -- Brian.
Re: Mysterious Clementine dependency on libgcrypt.so.11
The Wanderer writes: > As a start to troubleshooting: where did you install this from? The > Debian archives, or somewhere else? Never mind, old libmtp in /usr/local was the problem. Note to self, these should be cleaned up sometimes...
NULL pointer dereference
Hi there, I found the following in my "server" log: == BUG: unable to handle kernel NULL pointer dereference at 0008 PGD 0 P4D 0 Oops: [#2] SMP PTI CPU: 5 PID: 12441 Comm: awk Tainted: G D 4.19.0-13-amd64 #1 Debian 4.19.160-2 Hardware name: FUJITSU D3162-B1/D3162-B1, BIOS V4.6.5.3 R1.23.0 for D3162-B1x 12/01/2014 RIP: 0010:unmap_page_range+0x561/0xa60 Code: 80 00 00 00 01 e8 4f 2b 01 00 49 8b 07 f6 c4 80 0f 84 0e 03 00 00 4c 89 ff e8 6b 91 fe ff 85 c0 0f 88 e6 02 00 00 49 8b 46 28 <8b> 50 08 8d 4a 01 89 48 08 4c 89 7c d0 10 3b 48 0c 0f 84 d2 00 00 RSP: 0018:9c3a49167cd0 EFLAGS: 00010206 RAX: RBX: 8e2f47a83a10 RCX: 0001 RDX: RSI: RDI: 8e2f7dd2 RBP: 7faa2ed43000 R08: R09: 8e2ef8ae1c70 R10: 8e2f9e5df000 R11: R12: 7faa2ed42000 R13: 00014fd44025 R14: 9c3a49167dd0 R15: d073853f5100 FS: () GS:8e2f7e14() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0008 CR3: 00015020a003 CR4: 000606e0 Call Trace: unmap_vmas+0x7f/0xb0 exit_mmap+0xaa/0x180 mmput+0x54/0x130 do_exit+0x33f/0xbb0 ? handle_mm_fault+0xd6/0x200 do_group_exit+0x3a/0xa0 __x64_sys_exit_group+0x14/0x20 do_syscall_64+0x53/0x110 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7faa2eaa99d6 Code: Bad RIP value. RSP: 002b:7ffd860931d8 EFLAGS: 0246 ORIG_RAX: 00e7 RAX: ffda RBX: 7faa2eb9a760 RCX: 7faa2eaa99d6 RDX: RSI: 003c RDI: RBP: R08: 00e7 R09: ff80 R10: 7ffd86093096 R11: 0246 R12: 7faa2eb9a760 R13: 0001 R14: 7faa2eba3428 R15: Modules linked in: ppp_deflate cfg80211 rfkill 8021q garp stp mrp llc ppp_async crc_ccitt ppp_generic slhc nfsd auth_rpcgss nfs_acl lockd grace sunrpc xt_nat nft_chain_nat_ipv4 nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ipt_REJECT nf_reject_ipv4 nft_limit xt_limit xt_tcpudp nft_compat x_tables nft_counter nf_tables nfnetlink binfmt_misc bonding sch5636 sch56xx_common rc_it913x_v1 it913x af9033 dvb_usb_af9035 dvb_usb_v2 dvb_core rc_core snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_rapl i915 x86_pkg_temp_thermal snd_hda_intel intel_powerclamp snd_hda_codec coretemp snd_hda_core snd_hwdep snd_pcm xhci_pci ehci_pci ahci snd_timer xhci_hcd drm_kms_helper ehci_hcd libahci kvm snd mei_wdt tg3 iTCO_wdt irqbypass mei_me e1000e drm libata usbcore iTCO_vendor_support soundcore lpc_ich libphy mei i2c_algo_bit usb_common mfd_core crct10dif_pclmul crc32_pclmul ppdev ghash_clmulni_intel sg i2c_i801 intel_cstate evdev intel_uncore pcc_cpufreq video parport_pc button intel_rapl_perf pcspkr parport ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb sd_mod crc32c_intel aacraid aesni_intel aes_x86_64 crypto_simd scsi_mod cryptd glue_helper thermal fan CR2: 0008 ---[ end trace 1f0672175c6e1ff0 ]--- RIP: 0010:unmap_page_range+0x55d/0xa60 Code: ff 83 ac 84 80 00 00 00 01 e8 4f 2b 01 00 49 8b 07 f6 c4 80 0f 84 0e 03 00 00 4c 89 ff e8 6b 91 fe ff 85 c0 0f 88 e6 02 00 00 <49> 8b 46 28 8b 50 08 8d 4a 01 89 48 08 4c 89 7c d0 10 3b 48 0c 0f RSP: 0018:9c3a43a67cd0 EFLAGS: 00010202 RAX: 0004 RBX: 8e2f47a0deb0 RCX: 0001 RDX: RSI: RDI: 8e2f7dd2 RBP: 7f9f121d7000 R08: R09: 8e2f6a6e09c0 R10: 8e2f9e5df000 R11: R12: 7f9f121d6000 R13: 00081e49f025 R14: 9c3a43a67dd0 R15: d073a07927c0 FS: () GS:8e2f7e14() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7faa2eaa99ac CR3: 00015020a003 CR4: 000606e0 Fixing recursive fault but reboot is needed! This is not the first time, so I suspect a persistent problem. I have no idea how to look for the solution. Any suggestions?? Just in case: # lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04) 00:19.0 Ethernet controller:
Re: "Service restarts being deferred"
Jesper Dybdal wrote: > I run Buster with unattended updates configured to allow reboots. > > Sometimes after an update, the log contains: > > > Service restarts being deferred: > > ??systemctl restart systemd-logind.service > > ??systemctl restart unattended-upgrades.service > > I don't understand why these services are not restarted, if necessary > through a reboot. > > I want my system to be able to run truly unattended for a long time, so > necessary restarts should be done without waiting for manual intervention.?? > And if the restarts are not necessary, why are they there at all, though > deferred? > > So what have I misunderstood? In your /etc/apt/apt.conf.d, edit a file named 50unattended-upgrades // Automatically reboot *WITHOUT CONFIRMATION* if // the file /var/run/reboot-required is found after the upgrade Unattended-Upgrade::Automatic-Reboot "true"; // Automatically reboot even if there are users currently logged // in. Unattended-Upgrade::Automatic-Reboot-WithUsers "true"; Without those two lines, you get the behavior you currently have. Not everyone wants automatic reboots; not everyone wants automatic reboots even with someone logged in. -dsr-
"Service restarts being deferred"
I run Buster with unattended updates configured to allow reboots. Sometimes after an update, the log contains: Service restarts being deferred: systemctl restart systemd-logind.service systemctl restart unattended-upgrades.service I don't understand why these services are not restarted, if necessary through a reboot. I want my system to be able to run truly unattended for a long time, so necessary restarts should be done without waiting for manual intervention. And if the restarts are not necessary, why are they there at all, though deferred? So what have I misunderstood? -- Jesper Dybdal https://www.dybdal.dk
Re: Mysterious Clementine dependency on libgcrypt.so.11
On 2020-12-19 at 09:14, Anssi Saari wrote: > I installed clementine music player today but it refuses to run, > complaining: > > clementine: error while loading shared libraries: libgcrypt.so.11: > cannot open shared object file: No such file or directory > > Um, well, libgrypt.so.11 hasn't been Debian for a bunch of versions > and on other Debian 10 systems there's no such dependency so it's a > problem with my system somehow. As a start to troubleshooting: where did you install this from? The Debian archives, or somewhere else? Which repositories are you tracking? I track testing + stable, and I see: $ apt-cache policy clementine clementine: Installed: (none) Candidate: 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1 Version table: 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1 900 900 http://ftp.us.debian.org/debian testing/main amd64 Packages 1.3.1+git609-g623a53681+dfsg-1 800 800 http://ftp.us.debian.org/debian stable/main amd64 Package I haven't been able to find the dependency chain which would link clementine to libgcrypt*. However, when I download the package with 'apt-get download clementine' and examine the binary, I get: $ ldd clementine_1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1_amd64/usr/bin/clementine | grep libgcrypt libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7f5f4b742000) which matches the libgcrypt* version available in current testing. At a glance, I'd suspect that you've somehow installed a version of clementine which doesn't match the Debian version you're running, but I don't have enough information yet to say beyond that. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Mysterious Clementine dependency on libgcrypt.so.11
I installed clementine music player today but it refuses to run, complaining: clementine: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory Um, well, libgrypt.so.11 hasn't been Debian for a bunch of versions and on other Debian 10 systems there's no such dependency so it's a problem with my system somehow. A symlink like libgcrypt.so.11 -> /lib/x86_64-linux-gnu/libgcrypt.so.20 at least makes Clementine run but what's the real fix?
Re: Extraction de CDs
Salut, Jean-Philippe MENGUAL writes: > J'aimerais extraire les musiques d'un CD que j'ai depuis pas mal de > temps, acheté dans le commerce. J'utilise asunder qui, en Jessie, > récupérait bien les métadonnées (album, titre, artiste). Mais plus > maintenant, ni en Buster, ni en Sid. Sauriez-vous comment le > configurer pour retrouver ces infos? Ou une alternative qui fait mieux > les choses? abcde en ligne de commandes. Il va chercher sur cddb et musicbrainz. Il faut tripoter un peu le fichier de conf pour qu’il cherche sur les deux serveurs, voire d’autres. -- Raphaël www.leclavierquibave.fr
Re: Tiling display support
On 2020-12-19 03:52, Joe wrote: On Fri, 18 Dec 2020 23:55:09 +0100 deloptes wrote: Dan Ritter wrote: >> Does someone run desktop with 4k screen and high frame rate (150 >> fps+)? What monitor and gpu are you using? Are you having any >> issues? > > > There are no 4K 150Hz monitors currently commercially available. OP is asking about 150+FPS and you are talking about 150Hz. I am not convinced it is the same It is if interlace is not used, not if interlace is used. For broadcast television, there is never enough bandwidth, so interlace is used which halves the required bandwidth for very little visual degradation. With a stationary picture such as a computer display, interlace is not used, as it makes a stationary picture appear to jitter vertically. So interlaced 1080i at 50 or 60Hz has a frame rate of 25 or 30 FPS, while progressive 1080p at 50 or 60Hz has a frame rate of 50 or 60 FPS. I'm not sure I understand. Why are we talking about interlaced video? That doesn't seem to be relevant unless I'm missing something. There are plenty of 4k 120Hz and 144Hz monitors on the market right now. I am currently only running dual 60Hz 4K monitors right now with an AMD RX580 GPU each connected via Display Port 1.2 I believe a single Displayport (version 1.3) can support 4K 120 or 144Hz. There may be some useful information at this link https://en.wikipedia.org/wiki/DisplayPort#Resolution_and_refresh_frequency_limits I regret that I don't know anything about MST or SST. Hopefully someone can help you more. I'm interested to learn what you figure out. --- Steven Mainor 0x9477C19B.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
No success trying to get vinagre (Gnome Remote Desktop Viewer) to work with Raspberry Pi (RealVNC server)
I posted the following to the Gnome Reddit and receive no response, so I'm wondering if anyone here has been able to get this combination working. --- I've been trying to get Vinagre 3.22.0 on my Debian Gnome 3.38.2 desktop (already installed dependency) to work with the RealVNC server installed and running on a Raspberry Pi 4 running the latest up-to-date Raspberry Pi OS. The VNC connection works with the RealVNC viewer but it has a long EULA (non-libre) and is not well integrated (theming, etc.) into the Gnome desktop. So far Vinagre has resisted all of my efforts to get it to talk to the VNC server running on the Pi and each time I try I immediately get an error dialog that the connection was closed. I presume this is an authentication issue since the RealVNC viewer has a dialog for me to enter the username and password. The minimal help file for Vinagre makes mention of a .vnc file but does not explain or reference the format such a file should take. I was able to export the connection information from RealVNC viewer into a .vnc file, but Vinagre cannot use it. First it errored that there was no group in the key file so I created a group and then it errored that the group was not appropriately named Connections, so I fixed that and now immediately get the dialog that the connection was closed. --- At first I thought of RDP and had installed xrdp on the Pi and I seemed to get a connection to it from Vinagre but would only get a cyan screen and a gray box in the center, reminiscent of Motif apps that would freeze and not update the UI from long, long ago. Web searches showed that the gray box was supposed to be a login to the desktop, but the dialog never rendered even waiting for many minutes. Then I read a blog post that asserted the xrdp was interfered with by the RealVNC server being installed so I opted to try in instead and removed xrdp and its associated packages. Now, if I could get xrdp to work with Vinagre, I'd probably be quite happy with that. The aforementioned blog post discussed removing the realvnc* packages to allow xrdp to work, so perhaps that is worth a try. TIA - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: Can't print: /var/spool/lpd
On 12/14/20, Greg Wooledge wrote: > > For future requests, you can get English messages by overriding the LANG > (or LC_ALL) variable. > > LC_ALL=C apt-get whatever > > or, if you're in a csh/tcsh shell, or if you're using sudo: > > env LC_ALL=C apt-get whatever Thanks A LOT, Greg! Didn't knew that could be done. Very (very) useful! I'm already using it. Kind regards!
Re: Can't print: /var/spool/lpd
On 12/12/20, Brian wrote: > On Fri 11 Dec 2020 at 21:33:42 -0300, riveravaldez wrote: > >> Hi, I'm having an issue with a Brother HL-3150CDN printer on Debian >> Testing. > > You do not say, so we will assume there is a USB connection. The device > probably does IPP-over-USB; you will want to read > > https://wiki.debian.org/CUPSDriverlessPrinting Thanks for your answer, Brian, certainly I'd forget to specify it: The connection is not USB, it's a network connection (Ethernet), the printer is connected to the router and through the router I have access to it from various computers in the house. In the 'Add Printer' page/step, CUPS offers me three options: 1. Brother HL-3150CDN series - IPP Everywhere 2. Brother HL-3150CDN seriesm fully driverless, cups-filters 1.28.6 (en) 3. Brother HL-3150CDN series CUPS (en) The first and second work fine. The third one appears twice, and seems to be generated by the installation of the official drivers from Brother (I tried both options with similar result: the printer doesn't seems to receive the job/printing order). http://localhost:631/jobs/ once said: processing since Sat Dec 19 06:47:26 2020 "No se ha podido localizar la impresora "BRN30055CA838C7"." Which means: "Couldn't find the printer "BR..." But almost always just show the job as "completed". >> The printer functions with the drivers CUPS offers by default, but the >> official Brother's drivers has some options that I need to work with >> the equipment. > > An interesting comment. Debian will have set uo a print queue for the > printer. Please give the output of > > lpoptions -p PRINT_Q_NAME -l $ lpoptions -p Brother_HL-3150CDN_series -l PageSize/Media Size: *A4 Letter Legal Executive A5 A6 B5 JISB5 JISB6 EnvDL EnvC5 Env10 EnvMonarch Br3x5 FanFoldGermanLegal EnvPRC5Rotated Postcard EnvYou4 EnvChou3 210x270mm 195x270mm 184x260mm 197x273mm Duplex/Two-Sided: DuplexTumble DuplexNoTumble *None BRInputSlot/Paper Source: *AutoSelect Tray1 Manual BRResolution/Print Quality: *600dpi 600x2400dpi BRMonoColor/Color / Mono: *Auto FullColor Mono BRMediaType/Media Type: *Plain Thin Thick Thicker BOND Env EnvThick EnvThin Recycled Label Glossy PostCard BRColorMatching/Color Mode: *Normal Vivid None BRGray/Improve Gray Color: *OFF ON BREnhanceBlkPrt/Enhance Black Printing: *OFF ON BRTonerSaveMode/Toner Save Mode: OFF *ON BRImproveOutput/Improve Print Output: *OFF BRLessPaperCurl BRFixIntensity BRSkipBlank/Skip Blank Page: *OFF ON BRBrightness/Brightness: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRContrast/Contrast: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRRed/Red: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRGreen/Green: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRBlue/Blue: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRSaturation/Saturation: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 >> I was able to install these drivers some time ago, but now they didn't >> seem to work. >> >> The two file to install are: >> hl3150cdnlpr-1.1.2-1.i386.deb >> hl3150cdncupswrapper-1.1.4-0.i386.deb >> >> Both for 32-bits, so, I did the: >> $ sudo dpkg --add-architecture i386 >> $ sudo apt-get update >> >> And then used apt-get to install them. >> The packages get installed but didn't seem to send the data to the >> printer at printing time. >> Any idea how to diagnose this? >> >> The only error I'd saw until now is when I install the lpr package: >> >> $ sudo apt-get install ./hl3150cdnlpr-1.1.2-1.i386.deb >> (...) >> mkdir: no se puede crear el directorio «/var/spool/lpd/hl3150cdn»: No >> existe el fichero o el directorio >> chown: no se puede acceder a '/var/spool/lpd/hl3150cdn': No existe el >> fichero o el directorio >> chgrp: no se puede acceder a '/var/spool/lpd/hl3150cdn': No existe el >> fichero o el directorio >> chmod: no se puede acceder a '/var/spool/lpd/hl3150cdn': No existe el >> fichero o el directorio > > The installation of this package goes smoothly on my i386 machine. Well, here I have those errors. I've tried creating manually the folder: /var/spool/lpd/hl3150cdn Which I had to do as root. Once the folder is created, I reinstalled the packages, and the errors didn't appeared no more: $ sudo apt-get install --reinstall ./hl3150cdnlpr-1.1.2-1.i386.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'hl3150cdnlpr:i386' instead of './hl3150cdnlpr-1.1.2-1.i386.deb' 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 11 not upgraded. After this operation, 0 B
Re: [1/2HS] un virus Mirai offensif pour Linux
Bonjour, 18 déc. 2020 à 20:31 de ajh.val...@free.fr: > Info à prendre avec précaution, est-ce vrai ? > > L'application Ventoy, qui créé des clés USB bootable avec les ISO de > Linux, contiendrait le virus Mirai qui cible Linux. > > Y a t-il un réel danger ? > Pas de réponse ferme et tranchée mais quelques pistes de réflexion : * Ce n'est pas complètement nouveau (avril a minima) * Quelques "issues" ont été publiées sur le Github officiel à ce sujet * Le développeur en parle lui-même sur la page de téléchargement en tant que "faux-positifs" (ce n'est pas une preuve évidemment) * Certains internautes ont visiblement réussi à faire corriger certains "faux-positifs" auprès d'éditeurs AV. Sauf manque de sérieux ou mensonge, cela n'aurait pas été possible si c'était un vrai malware * J'ose espérer que plus d'AV sonneraient s'il s'agissait vraiment d'un Mirai... NB : Je constate que ClamAV détecte ventoy-1.0.30-linux.tar.gz et ventoy-1.0.30-livecd.iso sous la signature Unix.Trojan.Mirai-7640640-0. Il pourrait être intéressant de discuter du sujet (si pas déjà fait) sur une de leurs listes de diffusion... Sources : * https://github.com/ventoy/Ventoy/issues/31 * https://github.com/ventoy/Ventoy/issues/371 * https://github.com/ventoy/Ventoy/issues/468 * https://github.com/ventoy/Ventoy/releases/tag/v1.0.30 * https://virusscan.jotti.org/fr-FR/filescanjob/zbspdtr2ml * https://virusscan.jotti.org/fr-FR/filescanjob/0z1do6tv6r l0f4r0
Re: Tiling display support
On Fri, 18 Dec 2020 23:55:09 +0100 deloptes wrote: > Dan Ritter wrote: > > >> Does someone run desktop with 4k screen and high frame rate (150 > >> fps+)? What monitor and gpu are you using? Are you having any > >> issues? > > > > > > There are no 4K 150Hz monitors currently commercially available. > > OP is asking about 150+FPS and you are talking about 150Hz. I am not > convinced it is the same > It is if interlace is not used, not if interlace is used. For broadcast television, there is never enough bandwidth, so interlace is used which halves the required bandwidth for very little visual degradation. With a stationary picture such as a computer display, interlace is not used, as it makes a stationary picture appear to jitter vertically. So interlaced 1080i at 50 or 60Hz has a frame rate of 25 or 30 FPS, while progressive 1080p at 50 or 60Hz has a frame rate of 50 or 60 FPS. -- Joe
Re: Debian 10 64bit
On Sat, Dec 19, 2020 at 12:01:14AM +0100, deloptes wrote: [...] > Also I find very helpful the ArchLinux Wiki if I want to know how things > work in general. They tend to have a bit better (sorry Debian) concept of > documentation. > https://wiki.archlinux.org/index.php/Table_of_contents As a staunch Debian fanboi myself: the ArchLinux Wiki rocks! The nice part about free software and the attitude behind it is that there's no need to be sorry if "someone else" is better than "us" at some thing. Enjoy that and offer them whatever it is what you can do better in exchange. Cheers - t signature.asc Description: Digital signature