Re: Install Debian 10 amd64 onto USB flash drive with and for Macintosh
On 9/2/21 5:37 PM, David Wright wrote: On Wed 01 Sep 2021 at 16:00:13 (-0700), David Christensen wrote: [three long posts] That was very useful. I've condensed it into a file (attached) for my own use. The footnotes are notes, guesses and queries. I tried to file a bug report against the debian-installer complaining about the "Install" option not allowing me to choose where to put GRUB, thereby breaking macOS; but I don't see it yet on bugs.debian.org. STFW there are some resources for installing Debian onto a Macintosh internal SSD, but nothing recent for installing Debian onto a Macintosh external drive -- USB, SD card, or Thunderbolt. My main question is — there are three identical listings taken at different times; all say: # mount | grep '.dev.sd' /dev/sdb3 on / type ext4 (rw,relatime,errors=remount-ro) /dev/sdb1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro) and yet two are labelled as wrong, and the third as correct. Thank you for your sharp eyes. Without repeating those many hours of unpleasant work to confirm or deny the console sessions and/or the intermediate conclusions, at this point it does appear that I misread the output from the first two runs of the following command in my post of 9/1/21 4:00 PM: # mount | grep '.dev.sd' As always, I will have to be careful when making decisions based upon a single letter. RTFM mount(8), it talks about feeding UUID's into mount as command-line arguments; but I do not see a way to have mount output UUID's (?). I found the device letters a bit confusing when you're running the rescue system. AFAICT, sda is always the SSD. So I was perplexed by "Rescue operations -> Execute shell in /dev/sda3" because your SSD only appeared to have two partitions in the OP. The Debian Installer sessions were manually transcribed, and could easily contain typographical errors. What seems to be missing from the account is any consideration of the so-called NVRAM variables, about which I know nothing. My Debian posts did not include my prior ordeals making a bootable macOS installation USB flash drive, logging out of Apple services, erasing the SSD, resetting NVRAM, installing macOS Big Sur, etc., per the following Apple URL's and lots more STFW: https://support.apple.com/en-us/HT201372 https://support.apple.com/en-us/HT201065 https://support.apple.com/en-us/HT208496 (I never did figure out how to do a Secure Erase of the SSD.) I'm still working through how hiding the EFI/debian tree makes the option-less booting suddenly work, but then, I don't know how closely the Option key corresponds to pressing F12 on, say, a Dell PC, which is how you set the device boot order. (I haven't touched a Mac since the last century when they were in a little AiO box.) The contents of the SSD ESP filesystem are not ideal and I still do not understand how the MacBook Pro firmware finds and/or chooses between boot loaders. David
Re: Why ``color_prompt`` is only set for ``xterm``?
On 03/09/2021 01:34, David Wright wrote: (I use my own customisations for distinct colours on each host, and inverse colours for root's prompt.) Can you please share your root prompt invocation? Thanks! -- With kindest regards, piorunz. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Why ``color_prompt`` is only set for ``xterm``?
On Thu, Sep 2, 2021, 7:34 PM David Wright wrote > > (I use my own customisations for distinct colours on each host, > and inverse colours for root's prompt.) > Good idea :-) For some reason putting "root:" there doesn't save me 100% of the time :-) Cheers, > David. > >
Re: Install Debian 10 amd64 onto USB flash drive with and for Macintosh
On Wed 01 Sep 2021 at 16:00:13 (-0700), David Christensen wrote: [three long posts] That was very useful. I've condensed it into a file (attached) for my own use. The footnotes are notes, guesses and queries. My main question is — there are three identical listings taken at different times; all say: > # mount | grep '.dev.sd' > /dev/sdb3 on / type ext4 (rw,relatime,errors=remount-ro) > /dev/sdb1 on /boot/efi type vfat > (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro) and yet two are labelled as wrong, and the third as correct. I found the device letters a bit confusing when you're running the rescue system. AFAICT, sda is always the SSD. So I was perplexed by "Rescue operations -> Execute shell in /dev/sda3" because your SSD only appeared to have two partitions in the OP. What seems to be missing from the account is any consideration of the so-called NVRAM variables, about which I know nothing. I'm still working through how hiding the EFI/debian tree makes the option-less booting suddenly work, but then, I don't know how closely the Option key corresponds to pressing F12 on, say, a Dell PC, which is how you set the device boot order. (I haven't touched a Mac since the last century when they were in a little AiO box.) Cheers, David. Post 1 (31 Aug 2021 15:31:43 -0700) Option boot with d-i inserted: Select an EFI Boot disk (unclear whether SSD vs USB, or USB's bootx64.efi vs grubx64.efi) Install buster onto newly inserted USB → "buster-mac" Debian tree for ESP (silently) onto SSD's ESP¹ Boot with USB inserted (twice): SSD's ESP debian tree points to USB buster-mac runs Boot without USB inserted: SSD's ESP Debian tree points to USB Grub> Option boot without USB inserted: Sees SSD MacBook firmware starts macOS Command-R boot: MacBook firmware stuff Boot with USB inserted: SSD's ESP Debian tree points to USB buster-mac runs again fdisk shows Mac OS on sdX2, buster-mac on sdX3 SSD's ESP is mounted at /boot/efi SSD's ESP contains APPLE and debian Post 2 (31 Aug 2021 17:39:37 -0700) Option boot with USB inserted: Still sees only SSD Boot with USB inserted (perhaps continuing from Option boot): buster-mac runs Listing of d-i's ESP with bootx64.efi² and grubx64.efi USB's ESP is empty Repeat listing of SSD's ESP Ruminations on copying files³ Post 3 (1 Sep 2021 16:00:13 -0700) Boot Rescue with d-i inserted: Insert USB Select USB's / as root filesystem Execute a shell in sda3⁴ Edit /etc/fstab to mount USB's ESP, not SSD's Mount USB's ESP Install Grub, choosing USB's ESP Boot with d-i and USB inserted: Something⁵ displays a Grub menu buster-mac selected and runs Boot with USB inserted: buster-mac selected and runs Reports "Mount device for /boot/efi is wrong⁶ -- still using internal SSD, not USB flash drive." Boot Rescue with d-i inserted: Insert USB Select USB's / as root filesystem Install Grub, forcing "Removable media path"⁷ Boot with d-i and USB inserted: Something⁵ displays a Grub menu buster-mac selected and runs Boot with USB inserted: buster-mac selected and runs Reports "Wrong⁶ -- internal SSD ESP is mounted at /boot/efi." Option boot with USB inserted: Sees SSD and EFI Boot⁸ EFI Boot selection starts buster-mac Reports success after the same listing as the two "failures" Boot with or without USB inserted: macOS runs, buster-mac never runs Option boot with USB inserted: Sees SSD and EFI Boot⁸ EFI Boot selection starts buster-mac Mount SSD's ESP Move the SSD's ESP debian tree, leaving the APPLE one Boot with USB inserted: buster-mac runs (no Option/selection needed now) Listing USB's ESP, identical to a standard Debian installation's Listing of fstab mentions sdd in the comments, rather than sdc⁹ ¹ Not the desired result, of course ² I think bootx64.efi might be the secure boot shim? ³ Copying EFI files might not be enough: what about NVRAM variables? ⁴ Does sda3 exist (on the SSD)? ⁵ Presumably USB ESP could do this, and perhaps SSD ESP as well ⁶ Not sure why: buster-mac has sdb3 on / and sdb1 on /boot/efi Both these are on sdb which is the USB There are three identical lists from mount | grep '.dev.sd' ⁷ Is this these three files? /boot/efi/EFI/BOOT/* ⁸ How different is this selection screen from the very first one? ⁹ Was sdc the firmware stick during the original installation?
Re: Monthly FAQ for Debian-user mailing list
On Thu 02 Sep 2021 at 09:46:33 (+), Andrew M.A. Cater wrote: > On Wed, Sep 01, 2021 at 08:12:06PM +0300, Andrei POPESCU wrote: > > On Mi, 01 sep 21, 12:32:19, Andrew M.A. Cater wrote: > > > debian-user is a mailing list provided for support for Debian users, > > > and to facilitate discussion on relevant topics. > > > > > > Some guidelines which may help explain how the list works: > > > > > > * The language on this mailing list is English. There may be other > > > mailing > > > lists that are language-specific for example debian-user-french > > > > It might be good advertising to also mention other languages here, e.g > > go through the list of languages in alphabetic order, or something like > > that ;) > > I'd be quite happy to do (poor) translations into French/Italian and Spanish > for the respective user lists :) Another thing to maintain. > Many of the smaller lists have become > magnets for spam postings, unfortunately - and there's probably a case > for asking the listmasters to discontinue them. The advantages of the link I posted are: . self-maintaining (by the linkmasters), . as that page contains links to each other list's archives, users can form an instant judgement as to their usefulness by clicking on a recent month. Cheers, David.
Re: Why ``color_prompt`` is only set for ``xterm``?
On Fri 03 Sep 2021 at 03:15:13 (+0300), IL Ka wrote: > .bashrc on bullseye contains following lines > > ``` > # set a fancy prompt (non-color, unless we know we "want" color) > case "$TERM" in > xterm-color|*-256color) color_prompt=yes;; > esac > ``` > > So we only have colors in the terminal emulator, but not in virtual > linux console. > > This could be fixed by one more hardcode > `` > xterm-color|*-256color|linux) color_prompt=yes;; > `` > > But more robust way is something like: > ``` > if [ -x /usr/bin/tput ] && [ `/usr/bin/tput colors` -gt 1 ]; then > color_prompt=yes > fi > ``` I'm not on bullseye yet, but buster's /etc/skel/.bashrc contains: # uncomment for a colored prompt, if the terminal has the capability; turned # off by default to not distract the user: the focus in a terminal window # should be on the output of commands, not on the prompt #force_color_prompt=yes Have you tried removing the last # ? (I use my own customisations for distinct colours on each host, and inverse colours for root's prompt.) Cheers, David.
Re: masked service file
On 2021-09-03 00:21, Brian wrote: On Fri 03 Sep 2021 at 00:03:08 +0100, mick crane wrote: On 2021-09-02 23:28, Brian wrote: [...] > Please go back and read your very first post. You asked three questions. > Which one has not been answered? Please understand you are talking to an idiot, you have to say things slowly for example if saned.service is >/dev/null why is it there at all ? That's a foutth question. We assume the other three questions have been addressed to your satisfaction. We aim for a happy user :). The fourth question and its answer was also touched on earlier. The file's presence allows all the instances spawned by saned@.service to be managed. additional questions then: Scanning with xsane is quite zippy but scanbd/press button is noticeably slower to kick off. Could this be to do with not passing options to scanimage ? can I take options from xSane to give to scanbd/scanimage ? are there reasons to use scanadf instead of scanimage? mick -- Key ID4BFEBB31
Why ``color_prompt`` is only set for ``xterm``?
Hi .bashrc on bullseye contains following lines ``` # set a fancy prompt (non-color, unless we know we "want" color) case "$TERM" in xterm-color|*-256color) color_prompt=yes;; esac ``` So we only have colors in the terminal emulator, but not in virtual linux console. This could be fixed by one more hardcode `` xterm-color|*-256color|linux) color_prompt=yes;; `` But more robust way is something like: ``` if [ -x /usr/bin/tput ] && [ `/usr/bin/tput colors` -gt 1 ]; then color_prompt=yes fi ``` I do not know how much people care about console these days, but why have hardcode if we can check the number of colors? Ilya.
Re: masked service file
On Fri 03 Sep 2021 at 00:03:08 +0100, mick crane wrote: > On 2021-09-02 23:28, Brian wrote: [...] > > Please go back and read your very first post. You asked three questions. > > Which one has not been answered? > > Please understand you are talking to an idiot, you have to say things slowly > for example if saned.service is >/dev/null why is it there at all ? That's a foutth question. We assume the other three questions have been addressed to your satisfaction. We aim for a happy user :). The fourth question and its answer was also touched on earlier. The file's presence allows all the instances spawned by saned@.service to be managed. -- Brian.
Re: masked service file
On 2021-09-02 23:28, Brian wrote: On Thu 02 Sep 2021 at 21:06:59 +0100, mick crane wrote: On 2021-09-02 17:57, Brian wrote: > Regarding Greg Wooledge's exhortations to provide information about > an issue: You were asked explicity to provide some; you never did. > As it happens, I do not think the problems you have encountered > have anything to do with saned. You have picked the wrong target. What does this even mean "You have picked the wrong target"? I've got one guy battering me for specifics when it should be clear what I'm saying. I've got another guy intimating I'm an idiot. I was quite happy when you could work stuff out from the documentation but then this systemd came along now I haven't a clue what's going on. Please go back and read your very first post. You asked three questions. Which one has not been answered? Please understand you are talking to an idiot, you have to say things slowly for example if saned.service is >/dev/null why is it there at all ? mick -- Key ID4BFEBB31
Re: QEMU guests can ping but can't access host
On Thu, 02 Sep 2021 16:09:23 -0500 "David Palacio" wrote: > Hi, > > > If you copied a disk image (.qcow2 extension) over, but not the > > setup files that Virtual Machine Manager (VMM) uses > > (in /etc/libvirt), then Windows is on a new machine, and can have > > conniptions over it. Go into Windows' device manager (or whatever > > they're calling it this week) and see if it is finding all its > > hardware correctly. > > The VM virtual network hardware is working. It can access the > internet. It can't access only the host, either on the virtual > network ip or the physical network ip. I have since removed the old > guest image and replaced it with a new installation on a new VM > configuration. The same behavior is also seen on a new Linux VM > running the Debian Bullseye Live KDE CD. OK, then that's not the issue. > > What program are you using to try to contact the host? > > I noticed the problem first with Windows Explorer to access the samba > share. It simply timesout after a minute or two. Then I have tried > ping and a browser. Pinging the host works and the host responds. > Then I used nc to test connections like this: nc -lp 8080 On the host > and point a guest browser to http://hostip:8080/ but nc never > receives anything. That sounds suspiciously like firewall ports aren't open. > > > You may also have a firewall issue, as you say. On the host, please > > run whatever you use as a firewall control program and check to see > > if the relevant port(s) is open. > > I have to point out I haven't touched anything regarding firewall > since installation, however I have attached the output of iptables > and nft in this message. > > > You may find it useful to open a terminal and, as root, run > > > > tail -f /var/log/syslog > > > > and, while that is sitting there, try contacting the host again. If > > the firewall is blocking you, you'll see it in syslog. > > Neither syslog nor journalctl display anything related at the time > this problem happens. > > > If nothing obvious jumps out at you, let us know which program(s) > > you are using to control your firewall (shorewall, ufw, gufw, > > etc.), and we will see if someone familiar with that program can > > help. > > I don't `control` my firewall. It's all Debian's default and the > installed Debian packages defaults, like libvirt, which adds some > firewall rules automatically. Attached are the outputs of `iptables > -L`, `nft list tables` and `nft list table tablename`. I looked at the ntf listings you provided. I am completely new to nft and nftables, so I may have missed something. I don't see any ports open on the guest network (192.168.122.0/24). So I suspect that's the problem. Now we need an nftables guru to chime in. I did find examples on the Web, but none of them looked like it was exactly what you needed. Sorry I can't help further. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: masked service file
On Thu 02 Sep 2021 at 21:06:59 +0100, mick crane wrote: > On 2021-09-02 17:57, Brian wrote: > > > Regarding Greg Wooledge's exhortations to provide information about > > an issue: You were asked explicity to provide some; you never did. > > As it happens, I do not think the problems you have encountered > > have anything to do with saned. You have picked the wrong target. > > What does this even mean "You have picked the wrong target"? > I've got one guy battering me for specifics when it should be clear what I'm > saying. > I've got another guy intimating I'm an idiot. > I was quite happy when you could work stuff out from the documentation but > then this systemd came along > now I haven't a clue what's going on. Please go back and read your very first post. You asked three questions. Which one has not been answered? -- Brian.
cups no puedo ingresar
Hola amigos. Tengo Debian bullseye kde y he cambiado unas configuraciones de cups por lo cual me pidió mi usuario root y se reinició. Ahora no puedo ingresar a localhost:631 me dice "localhost rechazó la conexión" No tengo firewall instalado
Re: QEMU guests can ping but can't access host
On Thu, Sep 2, 2021, at 2:09 PM, Charles Curley wrote: > On Thu, 02 Sep 2021 12:43:41 -0500 > "David Palacio" wrote: > > > Good day, > > > > I have recently installed Debian testing around its alpha release > > state. Previously I had a working Windows 10 QEMU guest with access > > to the host Samba shares in a previous Debian testing install. I > > copied the Windows 10 disk image over to the new Debian install and > > set it up to run again but it no longer could connect to the host. It > > can ping it and the host responds to the ping but any access attempt > > to the host on a TCP port is dropped. This too happens to any new > > virtual machine I create from scratch, including Linux VMs. I have no > > idea what has changed on the host. I suspect it may be the firewall > > but I'm no network admin and I know very little outside of > > network-manager and /etc/network/interfaces. > > > > I use virtual machine manager to create and run my virtual machines. Hi, > If you copied a disk image (.qcow2 extension) over, but not the setup > files that Virtual Machine Manager (VMM) uses (in /etc/libvirt), then > Windows is on a new machine, and can have conniptions over it. Go into > Windows' device manager (or whatever they're calling it this week) and > see if it is finding all its hardware correctly. The VM virtual network hardware is working. It can access the internet. It can't access only the host, either on the virtual network ip or the physical network ip. I have since removed the old guest image and replaced it with a new installation on a new VM configuration. The same behavior is also seen on a new Linux VM running the Debian Bullseye Live KDE CD. > What program are you using to try to contact the host? I noticed the problem first with Windows Explorer to access the samba share. It simply timesout after a minute or two. Then I have tried ping and a browser. Pinging the host works and the host responds. Then I used nc to test connections like this: nc -lp 8080 On the host and point a guest browser to http://hostip:8080/ but nc never receives anything. > You may also have a firewall issue, as you say. On the host, please run > whatever you use as a firewall control program and check to see if the > relevant port(s) is open. I have to point out I haven't touched anything regarding firewall since installation, however I have attached the output of iptables and nft in this message. > You may find it useful to open a terminal and, as root, run > > tail -f /var/log/syslog > > and, while that is sitting there, try contacting the host again. If the > firewall is blocking you, you'll see it in syslog. Neither syslog nor journalctl display anything related at the time this problem happens. > If nothing obvious jumps out at you, let us know which program(s) you > are using to control your firewall (shorewall, ufw, gufw, etc.), and we > will see if someone familiar with that program can help. I don't `control` my firewall. It's all Debian's default and the installed Debian packages defaults, like libvirt, which adds some firewall rules automatically. Attached are the outputs of `iptables -L`, `nft list tables` and `nft list table tablename`. > -- > Does anybody read signatures any more? > > https://charlescurley.com > https://charlescurley.com/blog/ > > nft.table.mangle Description: Binary data nft.table.nat Description: Binary data nft.table.filter Description: Binary data nft.table.firewalld Description: Binary data nft.tables Description: Binary data iptables Description: Binary data virsh.net-dumpxml.default Description: Binary data
[WAS Re: Telegram Systray Icon] WORKAROUND: Use light theme/alternate icons
On Thu, Sep 02, 2021 at 10:01:24PM +0100, piorunz wrote: > On 02/09/2021 21:30, Miguel A. Vallejo wrote: > > Oh. You Are running UNSTABLE version of Debian. And just installed a > > program outside of Debian, from third party website. You must know what > > you are doing. > > > > I know what I'm doing, thank you. > > That's great. > > > I know how to report bugs, but sometimes it is difficult to guess from > > what package the bug comes from. That's the reason I ask in a user list. > > Well, you gave us no chance, your original post didn't even said that > you are running UNSTABLE with third party package from outside of > Debian. Actually, it didn't said anything about your configuration, > system, and affected package. > > > > > Anyway I found the problem. It is a bug in KDE: > > https://bugs.kde.org/show_bug.cgi?id=418996 > > Great! > Please file a bug there referencing Debian - all the others appear to reference Arch - and a note that the workaround of using the light theme works or doesn't. With every good wish, as ever, Andy Cater > -- > > With kindest regards, piorunz. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org > ⠈⠳⣄ >
Re: Telegram Systray Icon
On 02/09/2021 21:30, Miguel A. Vallejo wrote: Oh. You Are running UNSTABLE version of Debian. And just installed a program outside of Debian, from third party website. You must know what you are doing. I know what I'm doing, thank you. That's great. I know how to report bugs, but sometimes it is difficult to guess from what package the bug comes from. That's the reason I ask in a user list. Well, you gave us no chance, your original post didn't even said that you are running UNSTABLE with third party package from outside of Debian. Actually, it didn't said anything about your configuration, system, and affected package. Anyway I found the problem. It is a bug in KDE: https://bugs.kde.org/show_bug.cgi?id=418996 Great! -- With kindest regards, piorunz. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Telegram Systray Icon
> Oh. You Are running UNSTABLE version of Debian. And just installed a > program outside of Debian, from third party website. You must know what > you are doing. I know what I'm doing, thank you. > Also you must then know how to report bugs like this, I > understand. Otherwise you shouldn't be running UNSTABLE version of Debian. > I know how to report bugs, but sometimes it is difficult to guess from what package the bug comes from. That's the reason I ask in a user list. Anyway I found the problem. It is a bug in KDE: https://bugs.kde.org/show_bug.cgi?id=418996 Good night
Re: Telegram Systray Icon
On 02/09/2021 19:23, Miguel A. Vallejo wrote: I thought it was clear, but I was wrong. Telegram from website ( version 3.0.1 ), running in KDE under Unstable. Oh. You Are running UNSTABLE version of Debian. And just installed a program outside of Debian, from third party website. You must know what you are doing. Also you must then know how to report bugs like this, I understand. Otherwise you shouldn't be running UNSTABLE version of Debian. Everything was ok until Bullseye came out and a tsunami of new packages arrived to Unstable. Of course, that is normal with UNSTABLE system, especially after recent stable release. Since that moment the icon disappeared. Dissect bug, report to Debian developers, and revert your system snapshot to previous version. Mark affected, bugged versions of packages in apt preferences so they are being avoided, awaiting new, upgraded versions. Everything seems to work fine, except for that icon. No errors, nothing suspicious, neither in logs or running Telegram from command line. Just no icon. Thanks in advance You are welcome. -- With kindest regards, piorunz. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: GLIBCXX_3.4.29
Op 02-09-2021 om 20:32 schreef Paul van der Vlis: Hallo, Iemand vroeg me een computer te bouwen voor iets wat Pixinsight heet: https://pixinsight.com/sysreq/ Punt is dat dit GLIBCXX_3.4.29 nodig heeft, en Debian 11 biedt 3.4.28 als ik me niet vergis (zie onder). Vreemd, want alle andere system requirements zijn geen enkel probleem. En ze zeggen dat het prima werkt onder Ubuntu 18.04.1, Fedora 29, en RedHat 7.5. Dat lijken me toch geen nieuwe systemen! Weet iemand er hier meer? Groet, Paul root@server:/etc/monit/conf-enabled# strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX GLIBCXX_3.4 GLIBCXX_3.4.1 GLIBCXX_3.4.2 GLIBCXX_3.4.3 GLIBCXX_3.4.4 GLIBCXX_3.4.5 GLIBCXX_3.4.6 GLIBCXX_3.4.7 GLIBCXX_3.4.8 GLIBCXX_3.4.9 GLIBCXX_3.4.10 GLIBCXX_3.4.11 GLIBCXX_3.4.12 GLIBCXX_3.4.13 GLIBCXX_3.4.14 GLIBCXX_3.4.15 GLIBCXX_3.4.16 GLIBCXX_3.4.17 GLIBCXX_3.4.18 GLIBCXX_3.4.19 GLIBCXX_3.4.20 GLIBCXX_3.4.21 GLIBCXX_3.4.22 GLIBCXX_3.4.23 GLIBCXX_3.4.24 GLIBCXX_3.4.25 GLIBCXX_3.4.26 GLIBCXX_3.4.27 GLIBCXX_3.4.28 GLIBCXX_DEBUG_MESSAGE_LENGTH root@server:/etc/monit/conf-enabled# Dat klopt wel volgens mij. De nieuwe testing versie heeft vorige week een update gehad van libstdc++6: libstdc++6 (10.2.1-6) to 11.2.0-3. En dan heb je ook gcc-11-base nodig. Hiermee krijg ik dit rijtje: GLIBCXX_3.4 GLIBCXX_3.4.1 GLIBCXX_3.4.2 GLIBCXX_3.4.3 GLIBCXX_3.4.4 GLIBCXX_3.4.5 GLIBCXX_3.4.6 GLIBCXX_3.4.7 GLIBCXX_3.4.8 GLIBCXX_3.4.9 GLIBCXX_3.4.10 GLIBCXX_3.4.11 GLIBCXX_3.4.12 GLIBCXX_3.4.13 GLIBCXX_3.4.14 GLIBCXX_3.4.15 GLIBCXX_3.4.16 GLIBCXX_3.4.17 GLIBCXX_3.4.18 GLIBCXX_3.4.19 GLIBCXX_3.4.20 GLIBCXX_3.4.21 GLIBCXX_3.4.22 GLIBCXX_3.4.23 GLIBCXX_3.4.24 GLIBCXX_3.4.25 GLIBCXX_3.4.26 GLIBCXX_3.4.27 GLIBCXX_3.4.28 GLIBCXX_3.4.29 GLIBCXX_DEBUG_MESSAGE_LENGTH Groet, Henk.
Re: masked service file
On 2021-09-02 17:57, Brian wrote: Regarding Greg Wooledge's exhortations to provide information about an issue: You were asked explicity to provide some; you never did. As it happens, I do not think the problems you have encountered have anything to do with saned. You have picked the wrong target. What does this even mean "You have picked the wrong target"? I've got one guy battering me for specifics when it should be clear what I'm saying. I've got another guy intimating I'm an idiot. I was quite happy when you could work stuff out from the documentation but then this systemd came along now I haven't a clue what's going on. mick -- Key ID4BFEBB31
Re: icewm anomaly after bullseye upgrade
Thanks to those who chimed in! My focus today is on those lines in ~/.icewm/preferences that specify fonts for the task bar. I have in mind such statements as: NormalTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18" ActiveTaskBarFontNameXft="DejaVuSans-Bold,sans-serif:size=18" I suspect the syntax of my lines does not represent actual fonts that are available on this machine. Can anyone provide a critique of that syntax? -- ...a society must incorporate the rationalizing power symbolized by scientific knowledge, for otherwise it will be a fatally split society- split between a powerful elite and the disenfranchised mass. To this we add now: an irrational elite is the most dangerous of all. Holton, Gerald. 1985. On the Integrity of Science: The Issues Since Bronowski. Leonardo 18 (4), Special Issue: Jacob Bronowski: A Retrospective (1985): 229-232.
Re: QEMU guests can ping but can't access host
On Thu, 02 Sep 2021 12:43:41 -0500 "David Palacio" wrote: > Good day, > > I have recently installed Debian testing around its alpha release > state. Previously I had a working Windows 10 QEMU guest with access > to the host Samba shares in a previous Debian testing install. I > copied the Windows 10 disk image over to the new Debian install and > set it up to run again but it no longer could connect to the host. It > can ping it and the host responds to the ping but any access attempt > to the host on a TCP port is dropped. This too happens to any new > virtual machine I create from scratch, including Linux VMs. I have no > idea what has changed on the host. I suspect it may be the firewall > but I'm no network admin and I know very little outside of > network-manager and /etc/network/interfaces. > > I use virtual machine manager to create and run my virtual machines. If you copied a disk image (.qcow2 extension) over, but not the setup files that Virtual Machine Manager (VMM) uses (in /etc/libvirt), then Windows is on a new machine, and can have conniptions over it. Go into Windows' device manager (or whatever they're calling it this week) and see if it is finding all its hardware correctly. What program are you using to try to contact the host? You may also have a firewall issue, as you say. On the host, please run whatever you use as a firewall control program and check to see if the relevant port(s) is open. You may find it useful to open a terminal and, as root, run tail -f /var/log/syslog and, while that is sitting there, try contacting the host again. If the firewall is blocking you, you'll see it in syslog. If nothing obvious jumps out at you, let us know which program(s) you are using to control your firewall (shorewall, ufw, gufw, etc.), and we will see if someone familiar with that program can help. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Telegram Systray Icon
On Thu, Sep 02, 2021 at 08:23:43PM +0200, Miguel A. Vallejo wrote: > I thought it was clear, but I was wrong. > > Telegram from website ( version 3.0.1 ), running in KDE under Unstable. > Everything was ok until Bullseye came out and a tsunami of new packages > arrived to Unstable. Since that moment the icon disappeared. Everything > seems to work fine, except for that icon. No errors, nothing suspicious, > neither in logs or running Telegram from command line. Just no icon. > > Thanks in advance How long had you been running Unstable? You could have expected a significant churn when a new stable gets released - especially when there's been a freeze for a while. This is another good argument for using release names in /etc/apt/sources.list - no nasty surprises / flag days when there are major changes. I suspect that reinstalling the .deb might well install the icon in the right place - have you tried seearching for it / checking permissions? All the very best, as ever, Andy Cater
GLIBCXX_3.4.29
Hallo, Iemand vroeg me een computer te bouwen voor iets wat Pixinsight heet: https://pixinsight.com/sysreq/ Punt is dat dit GLIBCXX_3.4.29 nodig heeft, en Debian 11 biedt 3.4.28 als ik me niet vergis (zie onder). Vreemd, want alle andere system requirements zijn geen enkel probleem. En ze zeggen dat het prima werkt onder Ubuntu 18.04.1, Fedora 29, en RedHat 7.5. Dat lijken me toch geen nieuwe systemen! Weet iemand er hier meer? Groet, Paul root@server:/etc/monit/conf-enabled# strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX GLIBCXX_3.4 GLIBCXX_3.4.1 GLIBCXX_3.4.2 GLIBCXX_3.4.3 GLIBCXX_3.4.4 GLIBCXX_3.4.5 GLIBCXX_3.4.6 GLIBCXX_3.4.7 GLIBCXX_3.4.8 GLIBCXX_3.4.9 GLIBCXX_3.4.10 GLIBCXX_3.4.11 GLIBCXX_3.4.12 GLIBCXX_3.4.13 GLIBCXX_3.4.14 GLIBCXX_3.4.15 GLIBCXX_3.4.16 GLIBCXX_3.4.17 GLIBCXX_3.4.18 GLIBCXX_3.4.19 GLIBCXX_3.4.20 GLIBCXX_3.4.21 GLIBCXX_3.4.22 GLIBCXX_3.4.23 GLIBCXX_3.4.24 GLIBCXX_3.4.25 GLIBCXX_3.4.26 GLIBCXX_3.4.27 GLIBCXX_3.4.28 GLIBCXX_DEBUG_MESSAGE_LENGTH root@server:/etc/monit/conf-enabled# -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/
Re: Telegram Systray Icon
I thought it was clear, but I was wrong. Telegram from website ( version 3.0.1 ), running in KDE under Unstable. Everything was ok until Bullseye came out and a tsunami of new packages arrived to Unstable. Since that moment the icon disappeared. Everything seems to work fine, except for that icon. No errors, nothing suspicious, neither in logs or running Telegram from command line. Just no icon. Thanks in advance
Re: Telegram Systray Icon
On 02/09/2021 18:53, Miguel A. Vallejo wrote: Hello! Since the new Debian release and after a ton of new packages arrived to Unstable I noticed the system tray icon for Telegram desktop does not appear... or at least it appear completely black. See attached image. Is it a Debian problem or a Telegram problem? Any ideas? Thank you Hi, You didn't provide any system details. We don't even know what version of Telegram you use, and how did you install it. You can have apt version, snap version, version directly from their website, and so on. No idea. No info about desktop environment you use. Sorry, can't help you. Also, Telegram icon works perfectly for me in Bullseye, see screenshot attached. -- With kindest regards, piorunz. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Bullseye sddm autologin [SOLUCIONADO]
El 23/8/21 a las 10:36, Debian escribió: Buen día. En dos sistemas distintos, la actualización de buster a bullseye se ha cargado el inicio automático (auto login) de sddm en la sesión del usuario predefinido. La configuración de /etc/sddm.conf sgue siendo la que funcionaba con buster: [Autologin] # Whether sddm should automatically log back into sessions when they exit Relogin=false # Name of session file for autologin session (if empty try last logged in) Session= # Username for autologin session User=javier Bullseye es demasiado nuevo, y no encuentro informes similares en la web. Gracias. JAP Buenas tardes. Luego de darle varias vueltas al asunto, y toparme hoy con este reporte de "bug" https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1816923.html le encontré el pelo al huevo. La configuración de /etc/sddm.conf debe ser: [Autologin] # Whether sddm should automatically log back into sessions when they exit Relogin=false # Name of session file for autologin session (if empty try last logged in) Session=lxqt # Username for autologin session User=javier El nombre de sesión NO PUEDE QUEDAR EN BLANCO; en mi caso, lxqt. En "buster", eso estaba en blanco e iniciaba automáticamente la última utilizada. De de hecho, es la única disponible; me gusta LXQt porque usa muy pocos recursos y las dos máquinas en cuestión, sólo tienen cargado LXQt; nada de Plasma, nada de Gnome. Al parecer, con "buyllseye" es necesario sí o sí indicar el nombre de sesión sobre la cual se quiere iniciar, aunque haya disponible una sola en el sistema. Por lo que la opción por defecto "(if empty try last logged in)" no está funcionando. Muchas gracias. JAP
Telegram Systray Icon
Hello! Since the new Debian release and after a ton of new packages arrived to Unstable I noticed the system tray icon for Telegram desktop does not appear... or at least it appear completely black. See attached image. Is it a Debian problem or a Telegram problem? Any ideas? Thank you
QEMU guests can ping but can't access host
Good day, I have recently installed Debian testing around its alpha release state. Previously I had a working Windows 10 QEMU guest with access to the host Samba shares in a previous Debian testing install. I copied the Windows 10 disk image over to the new Debian install and set it up to run again but it no longer could connect to the host. It can ping it and the host responds to the ping but any access attempt to the host on a TCP port is dropped. This too happens to any new virtual machine I create from scratch, including Linux VMs. I have no idea what has changed on the host. I suspect it may be the firewall but I'm no network admin and I know very little outside of network-manager and /etc/network/interfaces. I use virtual machine manager to create and run my virtual machines. Please help and thank you for reading.
Re: masked service file
On Thu 02 Sep 2021 at 17:05:10 +0100, mick crane wrote: > On 2021-09-02 16:22, Greg Wooledge wrote: > > On Thu, Sep 02, 2021 at 04:13:34PM +0100, mick crane wrote: > > > I'll just presume you are grumpy because you have had the jab. > > > > Please stop. > > > > Take a breath. In. Out. > > > > Now: what is the problem you're experiencing? Start with a high level > > description: "My scanner doesn't work", for example. > > > > After that introduction, give the background information. Tell us what > > version of Debian you're using, what model the scanner is (assuming it's > > a scanner problem), and what software you've installed to try to make > > it work. > > > > After that, tell us the *specific* details about your problem. What > > actions are you taking, and what results do you get? Tell us the exact > > commands you're running, and paste their actual output into the email. > > If there are relevant log file snippets, paste those into the email. > > > > (I understand that identifying which information is relevant is an art > > form. Mistakes are OK. Do your best, and if someone asks for more > > information, be prepared to include that in a follow-up email.) > > my original question was a request for self help information as to why a > service would be masked. You have been given the reason for the masking: saned.service is an empty file. See the manual for systemd.unit. If a unit file is empty (i.e. has the file size 0) or is symlinked to /dev/null, its configuration will not be loaded and it appears with a load state of "masked", and cannot be activated. Use this as an effective way to fully disable a unit, making it impossible to start it even manually. The masking is intentional. It is by design. Your question is a decent one, but understanding why it isn't of any consquence to managing the saned service needs to be grasped. > I'm guessing that masking saned service is part of scanbd installation > because of using inetd or something. It is nothing to do with inetd. saned.service is not intended to be used for managing saned. That is the job of saned.socket (in conjunction with saned@service). systemctl stop saned.socket systemctl start saned.socket > As previously mentioned I was getting so many error messages (Bookworm) that > I couldn't fathom that reverted installation to Bullseye and everything so > far is working again. > Which is what we want. > mick Regarding Greg Wooledge's exhortations to provide information about an issue: You were asked explicity to provide some; you never did. As it happens, I do not think the problems you have encountered have anything to do with saned. You have picked the wrong target. -- Brian. > -- > Key ID4BFEBB31 >
Re: ping6 impossible/très lent depuis Debian sid et bullseye
Cédric Boutillier a écrit : > Bonjour, Bonsoir, > J'ai depuis peu une Freebox Delta, qui propose une passerelle ipv6. > Depuis mes machines Debian, la résolution des noms en ipv6 marche > correctement, mais pas de ping6, traceroute6 : ça tourne dans le vide. > Le ping et traceroute en v4 fonctionnent correctement avec des temps qui > semblent raisonnables. > > Faire une connexion ssh vers un hote qui a une ipv6 prend plusieurs > minutes pour aboutir. (en forçant l'ipv4 avec ssh -4, c'est immédiat). > > par exemple : > > traceroute6 master.debian.org > traceroute to master.debian.org (2001:41b8:202:deb:216:36ff:fe40:4001), 30 > hops max, 80 byte packets > 1 * * * > 2 * * * > 3 * * * > [...] > 30 * * * > > ping6 master.debian.org > PING master.debian.org(master.debian.org > (2001:41b8:202:deb:216:36ff:fe40:4001)) 56 data bytes > [et après ça attend dans le vide] Y a-t-il une passerelle définie ? Quel est le retour de la commande route -A inet6 ? Comment sont définies les adresses ? Statiques ou dynamiques ? Et si dynamiques, par quoi ? Le routage IPv6 est un truc délirant, certains outils se débrouillant avec des adresses locales, d'autres non (j'ai déjà vu des OS se débrouiller avec une passerelle en fe80:..., d'autres refusent catégoriquement.). Typiquement, chez moi, ça donne ça : hilbert:[~] > /sbin/route -A inet6 Table de routage IPv6 du noyau DestinationNext Hop Flag Met Ref Use If localhost/128 [::] U256 1 0 lo 2001:7a8:a8ed:10::/64 [::] UAe 256 22 0 enp5s0 fe80::/64 [::] U256 1 0 enp5s0 [::]/0 fe80::6a05:caff:fe02:b259 UGDAe 1024 24 0 enp5s0 localhost/128 [::] Un 0 21 0 lo 2001:7a8:a8ed:10:d65d:64ff:feb4:9a3b/128 [::] Un 0 4 0 enp5s0 fe80::d65d:64ff:feb4:9a3b/128 [::] Un 0 3 0 enp5s0 ff00::/8 [::] U256 6 0 enp5s0 [::]/0 [::] !n -1 1 0 lo La MTU est de 1500. CEPENDANT !... Cependant, je passe par un routeur NetBSD pour router différemment IPv4 et IPv6 (oui, j'ai un FAI de type Internet pour les ploucs...) et ce routeur envoie IPv4 directement sur l'interface wm2 (MTU de 1500) et IPv6 sur bridge0 (MTU 1335) associant tap0 et tap1 (MTU 1335). Le routeur se débrouille pour ne pas avoir de problème de MTU quitte à fragmenter les paquets IPv6. Le 1335 provient de la valeur optimale du paquet OpenVPN tap, je n'entre pas dans les détails. Je ne pencherai pas ici pour un problème de MTU, mais pour un problème de routage ou de configuration automatique IPv6. Bien cordialement, JKB
Re: colors messed up after X screen lock (buster with xfce)
I found at least a workaround: I installed and use xscreensaver for locking the screen. Unlike light-locker that xfce uses by default, xscreensaver doesn't seem to mess with the colormap. I should add: I am using nominally the same installation of debian 10 on two computers with very different hardware, a desktop and a laptop. Only the desktop computer is giving me the problems described earlier in this thread. Roland
Re: masked service file
On 2021-09-02 16:22, Greg Wooledge wrote: On Thu, Sep 02, 2021 at 04:13:34PM +0100, mick crane wrote: I'll just presume you are grumpy because you have had the jab. Please stop. Take a breath. In. Out. Now: what is the problem you're experiencing? Start with a high level description: "My scanner doesn't work", for example. After that introduction, give the background information. Tell us what version of Debian you're using, what model the scanner is (assuming it's a scanner problem), and what software you've installed to try to make it work. After that, tell us the *specific* details about your problem. What actions are you taking, and what results do you get? Tell us the exact commands you're running, and paste their actual output into the email. If there are relevant log file snippets, paste those into the email. (I understand that identifying which information is relevant is an art form. Mistakes are OK. Do your best, and if someone asks for more information, be prepared to include that in a follow-up email.) my original question was a request for self help information as to why a service would be masked. I'm guessing that masking saned service is part of scanbd installation because of using inetd or something. As previously mentioned I was getting so many error messages (Bookworm) that I couldn't fathom that reverted installation to Bullseye and everything so far is working again. Which is what we want. mick -- Key ID4BFEBB31
Re: masked service file
On Thu, Sep 02, 2021 at 04:13:34PM +0100, mick crane wrote: > I'll just presume you are grumpy because you have had the jab. Please stop. Take a breath. In. Out. Now: what is the problem you're experiencing? Start with a high level description: "My scanner doesn't work", for example. After that introduction, give the background information. Tell us what version of Debian you're using, what model the scanner is (assuming it's a scanner problem), and what software you've installed to try to make it work. After that, tell us the *specific* details about your problem. What actions are you taking, and what results do you get? Tell us the exact commands you're running, and paste their actual output into the email. If there are relevant log file snippets, paste those into the email. (I understand that identifying which information is relevant is an art form. Mistakes are OK. Do your best, and if someone asks for more information, be prepared to include that in a follow-up email.)
Re: ping6 impossible/très lent depuis Debian sid et bullseye
Bonjour Le 02/09/2021 à 15:21, Cédric Boutillier a écrit : Bonjour, J'ai depuis peu une Freebox Delta, qui propose une passerelle ipv6. Depuis mes machines Debian, la résolution des noms en ipv6 marche correctement, mais pas de ping6, traceroute6 : ça tourne dans le vide. Le ping et traceroute en v4 fonctionnent correctement avec des temps qui semblent raisonnables. Faire une connexion ssh vers un hote qui a une ipv6 prend plusieurs minutes pour aboutir. (en forçant l'ipv4 avec ssh -4, c'est immédiat). par exemple : traceroute6 master.debian.org traceroute to master.debian.org (2001:41b8:202:deb:216:36ff:fe40:4001), 30 hops max, 80 byte packets 1 * * * 2 * * * 3 * * * [...] 30 * * * ping6 master.debian.org PING master.debian.org(master.debian.org (2001:41b8:202:deb:216:36ff:fe40:4001)) 56 data bytes [et après ça attend dans le vide] ssh -vvv people.debian.org OpenSSH_8.4p1 Debian-6, OpenSSL 1.1.1l 24 Aug 2021 debug1: Reading configuration data /home/boutil/.ssh/config debug1: /home/boutil/.ssh/config line 6: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/boutil/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/boutil/.ssh/known_hosts2' debug1: auto-mux: Trying existing master debug1: Control socket "/tmp/bou...@people.debian.org:22" does not exist debug2: resolving "people.debian.org" port 22 debug2: ssh_connect_direct debug1: Connecting to people.debian.org [2607:f8f0:614:1::1274:67] port 22. [c'est l'étape qui bloque, après plusieur minutes d'attente ça déroule] J'ai essayé de deux portables Debian sid, un serveur arm et un raspberry pi bullseye, même résultat. Je pensais que c'était ma freebox qui bloque, mais le ping6 et traceroute6 marchent sans probleme depuis un mac... Les portables utilisent networkmanager. Je suis loin d'être un champion du réseau. Est-ce que quelqu'un aurait une piste à me donner pour trouver la source du problème et éventuellement y remédier ? Merci d'avance pour votre aide. Joue avec la MTU, 1492 passe pour moi. -- Daniel
Re: masked service file
On 2021-09-02 10:53, Curt wrote: On 2021-09-01, mick crane wrote: On 2021-09-01 16:22, Greg Wooledge wrote: On Wed, Sep 01, 2021 at 04:06:37PM +0100, mick crane wrote: On 2021-09-01 15:15, Brian wrote: > * saned is socket activated. > * saned@.service manages saned instances. > * saned.service is masked because it is an empty file. > * The file is empty to allow all instances to be managed together. Sounds informative. Maybe thie Brian person knows a thing or two about saned and you should consider listening. bit presumptive of you It's not presumptive, it's empirical. Our veteran participants get a sense of who knows what about what over time, observationally (and who, of course, inversely, is totally full of shit). As always, separating the wheat from the chaff is left as the traditional human exercise. It is presumptive as I have considered Brian's responses helpful and informative. I'll just presume you are grumpy because you have had the jab. mick -- Key ID4BFEBB31
ping6 impossible/très lent depuis Debian sid et bullseye
Bonjour, J'ai depuis peu une Freebox Delta, qui propose une passerelle ipv6. Depuis mes machines Debian, la résolution des noms en ipv6 marche correctement, mais pas de ping6, traceroute6 : ça tourne dans le vide. Le ping et traceroute en v4 fonctionnent correctement avec des temps qui semblent raisonnables. Faire une connexion ssh vers un hote qui a une ipv6 prend plusieurs minutes pour aboutir. (en forçant l'ipv4 avec ssh -4, c'est immédiat). par exemple : traceroute6 master.debian.org traceroute to master.debian.org (2001:41b8:202:deb:216:36ff:fe40:4001), 30 hops max, 80 byte packets 1 * * * 2 * * * 3 * * * [...] 30 * * * ping6 master.debian.org PING master.debian.org(master.debian.org (2001:41b8:202:deb:216:36ff:fe40:4001)) 56 data bytes [et après ça attend dans le vide] ssh -vvv people.debian.org OpenSSH_8.4p1 Debian-6, OpenSSL 1.1.1l 24 Aug 2021 debug1: Reading configuration data /home/boutil/.ssh/config debug1: /home/boutil/.ssh/config line 6: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/boutil/.ssh/known_hosts' debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/boutil/.ssh/known_hosts2' debug1: auto-mux: Trying existing master debug1: Control socket "/tmp/bou...@people.debian.org:22" does not exist debug2: resolving "people.debian.org" port 22 debug2: ssh_connect_direct debug1: Connecting to people.debian.org [2607:f8f0:614:1::1274:67] port 22. [c'est l'étape qui bloque, après plusieur minutes d'attente ça déroule] J'ai essayé de deux portables Debian sid, un serveur arm et un raspberry pi bullseye, même résultat. Je pensais que c'était ma freebox qui bloque, mais le ping6 et traceroute6 marchent sans probleme depuis un mac... Les portables utilisent networkmanager. Je suis loin d'être un champion du réseau. Est-ce que quelqu'un aurait une piste à me donner pour trouver la source du problème et éventuellement y remédier ? Merci d'avance pour votre aide. Cordialement, Cédric
Re: Get Terminal to Echo line in buffer on backspace
On Thu, Sep 02, 2021 at 05:44:33AM +0200, Thomas Anderson wrote: > Thanks for the insightful replies. > > I think I am getting closer to a solution. > > Wouldn't it be possible to bind the "redraw-current-line" to the delete > (ASCII DEL), i.e. Alt 127?? > > And, just add that to my user's bash file? It would go in ~/.inputrc by preference. But you *could* wrap it in "bind" and put it in ~/.bashrc instead, if for some reason you wanted it to be more complicated, or to be done only in bash and not in other programs which use readline. > I am thinking out loud, not sure this would work. Me either. Try It And See.
Re: masked service file
On 2021-09-01, mick crane wrote: > On 2021-09-01 16:22, Greg Wooledge wrote: >> On Wed, Sep 01, 2021 at 04:06:37PM +0100, mick crane wrote: >>> On 2021-09-01 15:15, Brian wrote: >>> > * saned is socket activated. >>> > * saned@.service manages saned instances. >>> > * saned.service is masked because it is an empty file. >>> > * The file is empty to allow all instances to be managed together. >> >> Sounds informative. Maybe thie Brian person knows a thing or two about >> saned and you should consider listening. > > bit presumptive of you > > It's not presumptive, it's empirical. Our veteran participants get a sense of who knows what about what over time, observationally (and who, of course, inversely, is totally full of shit). As always, separating the wheat from the chaff is left as the traditional human exercise.
Re: Monthly FAQ for Debian-user mailing list
On Wed, Sep 01, 2021 at 08:12:06PM +0300, Andrei POPESCU wrote: > On Mi, 01 sep 21, 12:32:19, Andrew M.A. Cater wrote: > > debian-user is a mailing list provided for support for Debian users, > > and to facilitate discussion on relevant topics. > > > > Some guidelines which may help explain how the list works: > > > > * The language on this mailing list is English. There may be other mailing > > lists that are language-specific for example debian-user-french > > It might be good advertising to also mention other languages here, e.g > go through the list of languages in alphabetic order, or something like > that ;) > > Kind regards, > Andrei > -- > http://wiki.debian.org/FAQsFromDebianUser I'd be quite happy to do (poor) translations into French/Italian and Spanish for the respective user lists :) Many of the smaller lists have become magnets for spam postings, unfortunately - and there's probably a case for asking the listmasters to discontinue them. All the very best, as ever, Andy Cater
knoda5
Bonjour à tous, Pour ceux qui seraient intéressés, je viens de forker knoda ici (trop d'erreurs de compilation, pas de réponse du développeur aux patches soumis) : https://github.com/JKBert knoda5 est un frontend de base de données. Compile actuellement sous testing avec mysql/mariadb, postgresql et sqlite3. dbase et xbase semblent poser des problèmes de compilation et je n'ai pas eu le temps ni la patience de corriger pour l'instant. Cordialement, JKB
