Re: Fwd: Debian 11 Xfce panel Network Manager applet has disappeared
David Christensen writes: > Forwarded Message > Subject: Re: Debian 11 Xfce panel Network Manager applet has disappeared > Date: Wed, 17 Apr 2024 11:38:49 -0700 > From: David Christensen > To: Gareth Evans > > On 4/17/24 03:47, Gareth Evans wrote: >> On Wed 17/04/2024 at 09:18, David Christensen >> wrote: >>> On 4/16/24 08:56, Gareth Evans wrote: On 16 Apr 2024, at 00:18, David Christensen wrote: > On 4/15/24 09:21, Gareth Evans wrote: >>> On Sun 14/04/2024 at 13:29, David Christensen wrote: >>> ... >>> I have used the Xfce panel Network Manager applet for many years. >>> Tonight, I noticed that it has disappeared (!). >>> ... > 2024-04-15 16:08:23 dpchrist@laalaa ~ > $ ps aux | grep nm-applet > dpchrist1518 0.1 0.2 426500 35380 ?Sl 16:06 0:00 > nm-applet > dpchrist1940 0.0 0.0 3240 644 pts/0S+ 16:15 0:00 grep > nm-applet > > 2024-04-15 16:15:12 dpchrist@laalaa ~ > $ nm-applet > > 2024-04-15 16:15:31 dpchrist@laalaa ~ > $ ps aux | grep nm-applet > dpchrist1518 0.1 0.2 426500 35380 ?Sl 16:06 0:00 > nm-applet > dpchrist1952 0.0 0.0 3240 644 pts/0S+ 16:15 0:00 grep > nm-applet That seems to show it's running from the outset, just not being displayed on the panel. Does rebooting (or logging out and in again) bring it back? >>> >>> >>> No. >> OK. You may have checked this already, but in case not, if I >> install XFCE and go to >> Settings > Session and Startup > Application Autostart >> there is an entry in the list called >> "Network (Manage your network connections)" > > > It is checked. > > >> which shows a tooltip of "command: nm-applet" > > > Command: nm-applet > > >> Might this somehow have become unset? >> I'm not sure if it's possible for GUI config helpers to become >> detached from actual settings - this seems to describe the relevant >> locations: >> https://unix.stackexchange.com/questions/669372/xfce4-session-and-startup-where-are-autostart-items-saved > > > 2024-04-17 11:21:06 dpchrist@laalaa ~ > $ grep nm-applet ~/.config/autostart > grep: /home/dpchrist/.config/autostart: No such file or directory > > 2024-04-17 11:33:11 dpchrist@laalaa ~ > $ find .config -name autostart > > 2024-04-17 11:33:22 dpchrist@laalaa ~ > $ > > > 2024-04-17 11:34:14 dpchrist@laalaa ~ > $ grep -r nm-applet /etc/xdg/autostart > /etc/xdg/autostart/nm-applet.desktop:Exec=nm-applet > /etc/xdg/autostart/nm-applet.desktop:X-GNOME-Bugzilla-Component=nm-applet > > > My WAG is that nm-applet is failing to start, but I have been unable > to find if and where any error message is reported. > What are the permissions on the nm-applet binary? maybe it doesn't have permission to execute, or the process which starts it doesn't have permission.
Re: Bluetooth sound problems playing from a web browser
Thanks, I tried it but it turns out to be a wifi/usb problem I think. Jan Krapivin writes: > Have you tried a LIVE-version of another Linux distribution? It will > be interesting to compare. > > вс, 7 апр. 2024 г. в 22:30, Richmond : > > Richmond writes: > > > Richmond writes: > > > >> When playing videos in a web browser, and sending the sound to > a > >> bluetooth speaker (amazon echo) I get playback problems; > stuttering, > >> sound quality reduction to AM radio level or lower). These > things can > >> clear up after a minute or two, or be reduced. > >> > >> When playing from nvlc however I get no such problems. (I > haven't > >> tried vlc so I am not sure if it is just that it is a command > line). > >> > >> I have tried google-chrome and firefox-esr. > >> > >> Perhaps there is some other browser which will work? Maybe I > need to > >> isolate the process from the browser? I tried pop-out picture > on you > >> tube and it improved but there was still stuttering. > > > > I installed Falkon and Konqueror. I tried Falkon and it worked > fine, no > > sound problems. But then I tried Google-chrome again and that > was > > working fine too, and so was Firefox-esr. The problems have > gone away > > and even rebooting doesn't bring them back. Maybe one of those > browsers > > brought a better library with it. > > These problems have come back again. I have tried rebooting. I > tried > sending the same audio from an android phone and it works fine. > How do I > find out what the problems is? I cannot see errors in journalctl >
Re: Bluetooth sound problems playing from a web browser
Lee writes: > On Sun, Apr 7, 2024 at 3:30 PM Richmond wrote: >> >> Richmond writes: >> >> > Richmond writes: >> > >> >> When playing videos in a web browser, and sending the sound to a >> >> bluetooth speaker (amazon echo) I get playback problems; >> >> stuttering, sound quality reduction to AM radio level or >> >> lower). These things can clear up after a minute or two, or be >> >> reduced. >> >> >> >> When playing from nvlc however I get no such problems. (I haven't >> >> tried vlc so I am not sure if it is just that it is a command >> >> line). >> >> >> >> I have tried google-chrome and firefox-esr. >> >> >> >> Perhaps there is some other browser which will work? Maybe I need >> >> to isolate the process from the browser? I tried pop-out picture >> >> on you tube and it improved but there was still stuttering. >> > >> > I installed Falkon and Konqueror. I tried Falkon and it worked >> > fine, no sound problems. But then I tried Google-chrome again and >> > that was working fine too, and so was Firefox-esr. The problems >> > have gone away and even rebooting doesn't bring them back. Maybe >> > one of those browsers brought a better library with it. >> >> These problems have come back again. > > So unless you've updated or installed new hardware or software it's > probably not a firmware/software issue. > >> I have tried rebooting. I tried sending the same audio from an >> android phone and it works fine. How do I find out what the problems >> is? I cannot see errors in journalctl > > It's possible that wifi or usb 3.0 could be interfering with your > bluetooth speakers - eg > https://www.zdnet.com/article/usb-3-and-usb-c-devices-can-cause-problems-with-wi-fi-and-bluetooth-connections-but-theres-a-solution/ Thanks, I think this is the answer! I was having no problems today but noticed that the PC was connected to 5Ghz. Sometimes it connects at 2.4Ghz. When I disabled 5Ghz and forced the PC to use 2.4Ghz the problem came back. So now all I need to do is seperate those services and/or tie the PC to 5Ghz. The PC is a laptop but I never move it from the desktop. I am using a USB mouse and USB keyboard adapter to an old IBM keyboard. > https://sortatechy.com/spot-and-fix-bluetooth-interference-with-wifi/ > > If your PC is using wireless and can use a 5Ghz channel, try moving > your PC wireless to a 5Ghz channel first. If you PC only supports > 2.4Gh wireless you can install linssid > https://packages.debian.org/bookworm/linssid and pick a relatively > unused channel for your PC wireless. Or just try channels 1, 6 and 11 > and see if any of those makes a difference.. > > If you're using a USB 3.0 device on your PC try turning it off or > moving it to a USB 2.0 port and see if that fixes the bluetooth > interference. > > Regards, Lee
Re: Bluetooth sound problems playing from a web browser
Richmond writes: > Richmond writes: > >> When playing videos in a web browser, and sending the sound to a >> bluetooth speaker (amazon echo) I get playback problems; stuttering, >> sound quality reduction to AM radio level or lower). These things can >> clear up after a minute or two, or be reduced. >> >> When playing from nvlc however I get no such problems. (I haven't >> tried vlc so I am not sure if it is just that it is a command line). >> >> I have tried google-chrome and firefox-esr. >> >> Perhaps there is some other browser which will work? Maybe I need to >> isolate the process from the browser? I tried pop-out picture on you >> tube and it improved but there was still stuttering. > > I installed Falkon and Konqueror. I tried Falkon and it worked fine, no > sound problems. But then I tried Google-chrome again and that was > working fine too, and so was Firefox-esr. The problems have gone away > and even rebooting doesn't bring them back. Maybe one of those browsers > brought a better library with it. These problems have come back again. I have tried rebooting. I tried sending the same audio from an android phone and it works fine. How do I find out what the problems is? I cannot see errors in journalctl
Re: Bluetooth sound problems playing from a web browser
Richmond writes: > When playing videos in a web browser, and sending the sound to a > bluetooth speaker (amazon echo) I get playback problems; stuttering, > sound quality reduction to AM radio level or lower). These things can > clear up after a minute or two, or be reduced. > > When playing from nvlc however I get no such problems. (I haven't > tried vlc so I am not sure if it is just that it is a command line). > > I have tried google-chrome and firefox-esr. > > Perhaps there is some other browser which will work? Maybe I need to > isolate the process from the browser? I tried pop-out picture on you > tube and it improved but there was still stuttering. I installed Falkon and Konqueror. I tried Falkon and it worked fine, no sound problems. But then I tried Google-chrome again and that was working fine too, and so was Firefox-esr. The problems have gone away and even rebooting doesn't bring them back. Maybe one of those browsers brought a better library with it.
Bluetooth sound problems playing from a web browser
When playing videos in a web browser, and sending the sound to a bluetooth speaker (amazon echo) I get playback problems; stuttering, sound quality reduction to AM radio level or lower). These things can clear up after a minute or two, or be reduced. When playing from nvlc however I get no such problems. (I haven't tried vlc so I am not sure if it is just that it is a command line). I have tried google-chrome and firefox-esr. Perhaps there is some other browser which will work? Maybe I need to isolate the process from the browser? I tried pop-out picture on you tube and it improved but there was still stuttering.
Re: making Debian secure by default
Lee writes: > > oof. Are there instructions somewhere on how to make Debian secure by > default? > > Thanks, Lee I always thought it strange that debian has no firewall on by default. Why not offer to enable one during installation? Opensuse offers to enable one and offers to allow ssh.
Re: hexchat being discontinued?
Default User writes: > :( > > Well, it seems that hexchat is being discontinued. > IMHO, it is/was the only IRC client that was actually usable. > > Any recommendations for a GOOD alternative? > > You could try Pidgin. It's in the Debian repo. It has various protocols of which irc is just one. It's a bit confusing because you have to go to the 'buddy' menu to join an irc channel.
Re: Unidentified flying subject!
Charles Curley writes: > On Fri, 09 Feb 2024 04:30:14 + > Richmond wrote: > >> So you need to store a lot of data and then verify that it has written >> with 'diff'. > > Yeah. > > I've been thinking about this. Yeah, I know: dangerous. > > What I would do is write a function to write 4096 bytes of repeating > data, the data being the block number being written to. So the first > block is all zeros, the second all ones, etc.. For convenience they > would be 64 bit unsigned ints. > > And, given the block number, a function to verify that block number N > is full of Ns and nothing else. > > By doing it this way, we don't have to keep copies of what we've > written. We only have to keep track of which block got written to which > LBA so we can go back and check it later. > > Now, divide the drive in half. Write block zero there. Divide the two > halves each in half, and write blocks one and two. Divide again, and > write blocks three through five. Etc., a nice binary division. > > Every once in a while, I would go back and verify the blocks already > written. Maybe every time I subdivide again. > > If we're really lucky, and the perpetrators really stupid, the 0th block > will fail, and we have instant proof that the drive is a failure. > We don't care why the drive is failing, only that the 0th block (which > is clearly not at the end of the drive) has failed. > > Here's a conjecture: This was designed to get people who use FAT and > NTFS. I know that FAT starts writing at the beginning of the partition, > and goes from there. This is because floppy disks (remember them?) have > track 0 at the outside, which is far more reliable than the tracks at > the hub simply because each each flux reversal is longer. So the first > 64G should be fine; only after you get past there do you see bad > sectors. I believe NTFS does similarly. > > But I don't think that's what they're doing. Other operating systems > have put the root directory and file allocation table (or equivalent) > in the middle of the disk (for faster access), Apple DOS for one. > mkfs.extX write blocks all over the place. > > I think that they are re-allocating sectors on the fly, regardless of > the LBA, until they run out of real sectors. So we write 64G+ of my > 4096 byte blocks. It'll take a while, but who cares? > > If Gibson is correct that these things only have 64 gig of real memory, > and my arithmetic is correct, we should start seeing failures after > writing 16777216 of my 4096 blocks. > > Of course, these things might allocate larger sectors than 4096 bytes. > In which case we'll hit the limit sooner. I tried validrive on a 64G drive and it was very fast to run. Another older drive with 32G was much slower. This is due to the design of drives expecting to be written to sequentially. Note this in the FAQ: "Q:How much of the storage of a drive does ValiDrive test? "A:ValiDrive's drive map contains 32 x 16 squares. So it tests 576 evenly-spaced 4k byte regions of any drive for a total of 2,359,296 bytes, or about 2.36 megabytes. If a drive contains internal RAM caching, ValiDrive will detect that and may increase its testing region size, as necessary, to bypass such caching; but this is not commonly encountered. " This would be considerably quicker than your 64G write, and also cause less wear. But you need a friend with Windows to run it. :)
Re: Unidentified subject!
Charles Curley writes: > On Thu, 08 Feb 2024 18:02:36 -0500 > Stefan Monnier wrote: > >> > Test it with Validrive. >> > https://www.grc.com/validrive.htm >> >> Looks like proprietary software for Windows. > > badblocks, available in a Debian repo near you, might be a suitable > replacement. I am not sure badblocks would do the same thing. "The drive appears to be the 1 or 2 terabyte drive you purchased. You plug it into your computer and everything looks fine. You can even copy files to the drive; as many as you want. And when you look at the drive's contents the files are there. But what's insidious is that the files' contents may have never been stored. " So you need to store a lot of data and then verify that it has written with 'diff'.
Re: Unidentified subject!
gene heskett writes: > Well the 2T memory everybody was curious about 3 weeks ago got here early. > > From dmesg after plugging one in: > [629240.916163] usb 1-2: new high-speed USB device number 39 using xhci_hcd > [629241.066221] usb 1-2: New USB device found, idVendor=048d, > idProduct=1234, bcdDevice= 2.00 > [629241.066234] usb 1-2: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [629241.066239] usb 1-2: Product: Disk 3.0 > [629241.066242] usb 1-2: Manufacturer: USB > [629241.066246] usb 1-2: SerialNumber: 2697241127107725123 > [629241.069485] usb-storage 1-2:1.0: USB Mass Storage device detected > [629241.074187] scsi host37: usb-storage 1-2:1.0 > [629242.100738] scsi 37:0:0:0: Direct-Access SSD 3.0 > 2.00 PQ: 0 ANSI: 4 > [629242.100959] sd 37:0:0:0: Attached scsi generic sg13 type 0 > [629242.101190] sd 37:0:0:0: [sdm] 409600 512-byte logical blocks: > (2.10 TB/1.91 TiB) > [629242.101289] sd 37:0:0:0: [sdm] Write Protect is off > [629242.101290] sd 37:0:0:0: [sdm] Mode Sense: 03 00 00 00 > [629242.101409] sd 37:0:0:0: [sdm] No Caching mode page found > [629242.101410] sd 37:0:0:0: [sdm] Assuming drive cache: write through > [629242.103927] sdm: sdm1 > [629242.104047] sd 37:0:0:0: [sdm] Attached SCSI disk > gene@coyote: > > Looks like a reasonable facsimile of a 2T disk to me. > > Cheers, Gene Heskett, CET. Test it with Validrive. https://www.grc.com/validrive.htm
Re: what keyboard do you use?
hw writes: > On Fri, 2024-02-02 at 20:09 -0600, Nate Bargmann wrote: >> [...] >> I have several of the now classic IBM Model M keyboards I procured in >> the '90s. Modern BIOSes don't like them even with a PS/2 to USB >> adapter so I gave up on them. > > They might work with a so-called active adapter. IIRC it has > something to do with the adpater suppling power. With some research > and an investment of like $5, you can probably still use your > keyboards. > Yes, I am using an IBM keyboard right now via usb into a laptop, with this adapter: https://www.amazon.co.uk/dp/B07FLD3T8T
man page for cut
In the man page for cut it says: -b, --bytes=LIST select only these bytes But there is no equals sign in the actual syntax: echo hello|cut -b 2-5 ello echo hello|cut -b=2-5 cut: invalid byte/character position ‘=2-5’ Try 'cut --help' for more information. Why is this? (An example paints a thousand words).
Re: GRUB -- Debian overrides? Or maybe I just don't understand it well...
It's not ideal, but what I did when I had two disks and two operating systems was I installed two grubs, one for each OS, one on each MBR. I then used the BIOS menu to choose which disk to boot. This means each OS updates its own grub instance.
Re: differences among amd64 and i386
fuf writes: > Good day! Near a half month ago I bought a comp. made into 2011 year > and didn't knew which Debian12 to put: i386 or amd64?, chose i386 as > thought that old comp. didn't take amd64. i386-netinst Debian 12 was > being installed perfectly, and later I could to read a disk owned to > the comp.: CPU Support Processor Intel Sandy Bridge (Dual core / Quad > core) (optional) TDP 35W / 45W Core Chips PCH Intel® HM65 Memory > Technology DDR3 1333 MHz Memory DDR3 SO-DIMM X 2 slots Maximum 8 GB In > BIOS I had read: Memory 2GB, Processor Speed ~2GHz, Disk 320GB. > > I installed amd64-netinst Debian 12 but the bare base (for speed) > hoping after to add all necessary. Of course nothing couldn't . > Third time I have installed Xfce and all to be suggested. Now > comp. is having 3 Debian 12 and 1 swap partition 4GB. I don't > notice differences among amd64 and i386 but think to pick among > this. Give advice, what better please? I will add memory if the spare > slots are, but maybe all busy? There are 2 slots only. Also, is > there any simplest way to increase the font at the "bare base" at once > after login? Thanks all. --fuf If you use: sudo dmidecode -t memory It will show you how much memory is in each slot, and the maximum memory. I am finding my PC with 2 Gigabytes of RAM performs better with 386 os, but some things don't work like app images, TOR browser. This link suggests for example Seamonkey requires 2 GB RAM for the 32-bit version 3 GB RAM for the 64-bit version https://www.seamonkey-project.org/en/doc/system-requirements
Re: IMPORTANT: do NOT upgrade to new stable point release
Greg Wooledge writes: > On Sat, Dec 09, 2023 at 07:18:20PM +, Michael Kjörling wrote: >> If you upgraded this morning, then I would expect that you are okay >> for now. > > That doesn't appear to be true. > >> Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 >> the bug is present in kernel Debian package version 6.1.64-1. If you >> are on 6.1.55-1 (current Bookworm stable per last night) you _likely_ >> aren't affected. > > This is the kernel I got this morning: > > ii linux-image-6.1.0-14-amd64 6.1.64-1 amd64 Linux 6.1 for 64-bit PCs > (signed) > > This is the current result of looking for a newer one: > > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Based on the warnings given here, I rebooted to the prior kernel: > > unicorn:~$ uname -a Linux unicorn 6.1.0-13-amd64 #1 SMP > PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux > > I guess I'll wait and see what happens next. I upgraded some time today to a December kernel. I have now gone back to September 29 kernel. But is there a way to tell what if anything got corrupted? I am using a 32 bit system and ext4. I booted this: 6.1.0-13-686-pae #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) i686 GNU/Linux then: aptitude remove linux-image-6.1.0-14-686-pae
Re: it: perhaps? gmail issues.
In this article Google seems to think using standard webmail works with a screen reader. https://support.google.com/mail/answer/90559 It advises to turn on keyboard shortcuts. I suppose another option would be to use another webmail service to pick up email from gmail. Karen Lewellen wrote: > Hi folks, > Admit my hands are shaking a bit as I write. > This morning google began circulating a plan to force standard gmail > on users still keeping basic html gmail...in spite of posts on their > own accessibility list from members around the world experiencing > disabilities who still need basic html. > I personally have a great deal of content, for work and otherwise in > this inbox. > making it worse for me is that one must solve a captcha to prove > yourself, something I physically cannot do. > so, thinking of Debian shells or Ubuntu ones, how would you find a > path to gmail firmly? > Thanks, > Karen > >
Re: UFW/GFW Doesn't start up after running previously
marathon writes: > On Sat, Nov 18, 2023 at 07:49:32AM -0700, Charles Curley wrote: >> On Sat, 18 Nov 2023 08:25:10 -0500 >> marathon wrote: >> >> > Using Debian Bookworm, on Lenovo X280 laptop. Each time after cold >> > startup or from suspend, I've found the ufw software is turned off >> > and blocks all network activity in that state. >> >> How do you know it is turned off? Please show the exact command you are >> using, including leading and trailing command line prompts. > > When I launch Gufw it's off. I'm not starting it via console but with the > GUI. This is a vanilla Debian install, and ufw/Gufw from the Debian repos. > It should just work. I have no idea whats going on under the hood, I'm a > simple user of the product. > >> ufw is a tool for setting up and managing a firewall. It is not the >> firewall itself. To find out if your firewall is active, run >> >> iptables -n -L >> >> If you see this, you have no firewall at all, you are wide open, and >> should run some ifw command to bring the firewall up: > > It works fine when its turned on manually, past experience using it on > Debian this would never happen. Once installed and started it should keep on > running across cold reboots and/or suspend. > >> root@chaffee:~# iptables -n -L > > snip > >> If you see anything else, you may have a working firewall. As I don't > > It's called ufw not ifw. I have it set on the default settings which stops > inbound but allows outbound. I need input from someone using this tool. It's > available in the repos for those that don't want to screw around with > scripts etc. I am using it on a Debian 10 system. You might look in ufw.conf cat /etc/ufw/ufw.conf # /etc/ufw/ufw.conf # # Set to yes to start on boot. If setting this remotely, be sure to add a rule # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp' ENABLED=yes # Please use the 'ufw' command to set the loglevel. Eg: 'ufw logging medium'. # See 'man ufw' for details. LOGLEVEL=low When I run ufw status Status: active To Action From -- -- 22/tcp ALLOW 192.168.1.0/24 systemctl status ufw ● ufw.service - Uncomplicated firewall Loaded: loaded (/lib/systemd/system/ufw.service; enabled; vendor preset: enabled) Active: active (exited) since Sun 2023-11-19 15:45:15 GMT; 20min ago Docs: man:ufw(8) Process: 219 ExecStart=/lib/ufw/ufw-init start quiet (code=exited, status=0/SUCCESS) Main PID: 219 (code=exited, status=0/SUCCESS)
Re: Panic again any idea
Schwibinger Michael wrote: > Good morning > I did ask one year ago > but no answer here or in the www. > Debian has panic(=no booting) after update to 11. > Thank You for help > > Regards > Sophie > Boot from a rescue disk and look at the logs, or take a photograph of the screen when the error occurs. If you manage to boot from a rescue disk you could re-install grub. Probably it hasn't mounted the right disk.
Segmentation fault in Chromium
I received a segmentation fault from chromium. Would it be logged anywhere? I searched journalctl but no mention of it. Chromium 117.0.5938.132 built on Debian 11.7, running on Debian 11.7 5.10.0-25-amd64 #1 SMP Debian 5.10.191-1 (2023-08-16) x86_64 GNU/Linux I expect such things cannot be logged but it would be good to find out what it is.
Re: Looking for a good "default" font (small 'L' vs. capital 'i' problem)
debian-u...@howorth.org.uk wrote: > Cindy Sue Causey wrote: >> My own mind went to the place of thinking sans serif was about those >> very lines. I just didn't make it to thinking that would make it hard >> to find any alternate in that family. My long time preference is >> developer-weary-eye-friendly fonts-anonymous-pro for whatever >> applications will accept it. Found it accidentally a few years ago. >> Its differences are noticeable enough that I instantly miss it on new >> operating system installs. The "apt-cache show" description for >> fonts-anonymous-pro specifically references both 0 v. O and I v. l v. >> 1: "Description-en: fixed width font designed for coders This package >> contains two Font Families. - Anonymous Pro - Anonomous Pro Minus . >> 'Anonymous Pro' is a family of four fixed-width fonts designed >> especially with coding in mind. Characters that could be mistaken for >> one another (O, 0, I, l, 1, etc.) have distinct shapes to make them >> easier to tell apart in the context of source code. > Terminal fonts tend to be fixed width since that's a property of > terminals. Fixed width fonts tend to have serifs because it's easier > to make the spacing look more even between inherently narrow > characters and inherently wide ones using details like serifs. So > finding a sans serif font amongst terminal fonts is likely a difficult > cause. The font I have in Gnome terminal is called 'Monospace'. It doesn't have serifs generally, but there is on I and l, and on J. And the 0 has a dot in it. The Gnome Tweaks program has a font selector which shows 'The quick brown fox jumps over the lazy dog', searching for 'sans' I found only 'Noto Sans Mono Regular' which distinguished the I and l.
Strange visual effects with Gnome
I installed Debian 12 on a laptop. I found that when the mouse was moved up to the top menu bar it disappeared. If I managed to click on the menu the mouse was invisible over the menu too. Also I noticed the letter A from activities was missing. You will forgive me I hope for installing OpenSUSE 15.5, but I still see some problems with fonts although the mouse is always visible. Hardware Class: graphics card Model: "ATI RV515/M54 [Mobility Radeon X1400]" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x7145 "RV515/M54 [Mobility Radeon X1400]" SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x2002 Driver: "radeon" Driver Modules: "radeon" vendor_id : GenuineIntel cpu family: 6 model : 15 model name: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz It's a Dell Inspiron 9400. What can I do? I would install Debian 11 or 10 if I thought it would improve the situation but I am not sure where the problem lies.
Re: Fan speed and control
Emanuel Berg writes: > Richmond wrote: > >> Smart fan control is enabled in the CMOS > > Complementary metal–oxide–semiconductor, AKA sea-moss? > > https://en.wikipedia.org/wiki/CMOS > > The CMOS BIOS: > > https://en.wikipedia.org/wiki/Nonvolatile_BIOS_memory > I meant CMOS settings. https://www.ifixit.com/Wiki/Motherboard_CMOS_Configuration_and_Setup >> for both CPU and System. Is there something I can use which >> will automatically configure fan speed? > > I'm not aware of a way to do this from software, but you can > do this with the UEFI (modern-day BIOS) for PWM and DC fans. > But you knew that ... Well no I didn't know that. I don't have a modern day UEFI. But I concluded that there is some control of the fan from the fact that Windows 10 does it, and that the fan speed is lower in the winter even with Debian. But I suppose that could be the BIOS. > > A bunch of monitoring functions mostly based on sensors(1) > > https://dataswamp.org/~incal/conf/.zsh/temp > > "My name is Bugs, as in bunny - and tech that listens." Thanks.
Fan speed and control
I've noticed that the fan speed with Debian is much faster than the fan speed with Windows 10. I doubt very much that this is because Windows 10 is doing less processing. The fan speed with Windows 10 seems to vary quite a lot, where as Debian is consistently high when the room temperature is up around 23C as it is now. /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed Output from 'sensors': acpitz-acpi-0 Adapter: ACPI interface temp1:+34.0°C (crit = +90.0°C) Smart fan control is enabled in the CMOS for both CPU and System. Is there something I can use which will automatically configure fan speed?
Re: root password of debian live cd?
Timothy M Butterworth writes: > On Tue, May 30, 2023 at 2:03 AM hlyg wrote: > > > On 5/30/23 12:37, to...@tuxteam.de wrote: > > > > This seems to have been discussed like eight years ago: > > > > https://lists.debian.org/debian-live/2015/05/msg00081.html > > > > Perhaps it should go into a FAQ. > > > > Cheers > > > Thank tomas! > > many packages break because of empty password? some other distro > have no > password for live cd, they don't break? > > i have tried latest deb11 live cd for i386/gnome, live or Live > aren't > correct passwords > > > The Live CD has no root password you have to use sudo. Someone here suggested using live-config as a command line parameter in Grub. https://forums.debian.net/viewtopic.php?t=102937 If you are logged in as user you can use: sudo bash To get a root command prompt and set the root passwd using passwd
Re: nvidia package 340xx
Hans writes: > Am Samstag, 20. Mai 2023, 19:15:18 CEST schrieb Richmond: > >> Hans writes: > > >> > >> As far as I remember the problem in Nvidia does not support kernels > >> above 4. This is why my laptop is stuck on Debian 10, although I > did > >> wonder if Debian 11 can run with kernel 4. > >> > >> (Nouveaux is no good to me). > > > Hi Richmond, > > > regarding to debian/sid the package supports kernels up to 6.2. > > > However, there are some issues, so it will segfault any > qt-windowmangers (at the moment) and got some security issues. > > > I succcessfully could build the sources with kernel-headers 6.0.1-9 > (which with former kernels later than 5.10-22 did not work). > > > But sadly in the end I did not succced at all, as it did not load the > kernel modul and additionally it breaked my acceleration from the > inbuilt gpu of the intel processor. > > > So it was more a disappointment. On the other hand it could be, I > made some mistakes and should upgrade additional libs from unstable. > > > There is another thing, I also might done wrong (I wrote about some > weeks ago in this forum): lspci says it is > > > NVIDIA Corporation GF119M [Quadro NVS 4200M] (rev a1) > > > and nvidia-detect (and some other sources, are telling me, that for > this chipset NOT 340xx but 390xx should be used. > > > Thisis wrong, as I could prove, that only 340xx (with kernel 5.10-22) > is working. Installing 390xx, the kernel says: Wrong module, you have > to use 340xx. > > > This is the state at the moment. As I have only this laptop and no > spare harddrive at the moment, I could not install debian/unstable > for testing purposes. Maybe some time I will, or maybe some other guy > will do it. > > > Hope this makes some things clearer. Not really, but I found this website which says the driver supports kernels "up to" 5.4 which I guess means up to and including. https://nvidia.custhelp.com/app/answers/detail/a_id/3142/ But debian seems to drop after debian 10 because kernel is 5.10 ? https://wiki.debian.org/NvidiaGraphicsDrivers I see here someone has patched the drivers: https://github.com/MeowIce/nvidia-legacy :-? Ubuntu 20.04 supports kernel 5.4 until 2025. So I might try that after debian 10 expires. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel My card: nvidia-detect Detected NVIDIA GPUs: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) Checking card: NVIDIA Corporation G86M [GeForce 8400M GS] (rev a1) Your card is only supported up to the 340 legacy drivers series. It is recommended to install the nvidia-legacy-340xx-driver package.
Re: nvidia package 340xx
"Marlin S. Petre" writes: > On 5/20/23 1:15 PM, Richmond wrote: >> As far as I remember the problem in Nvidia does not support kernels >> above 4. This is why my laptop is stuck on Debian 10, although I did >> wonder if Debian 11 can run with kernel 4. >> >> (Nouveaux is no good to me). >> > I am using the "nvidia-tesla-450-driver" on Debian 12 bookworm. You > need to install the linux-headers package that matches your kernel version > in order for the nvidia driver to build into the kernel. For Bullseye amd64, > I think this would be "linux-headers-5.10.0-22-amd64". For Bookworm, it is > "linux-headers-6.1.0-9-amd64". > > If a point release of stable ships with a different kernel version, I > learned that I > needed to install the headers package that matched, or the driver > would build > for the old kernel. > > Regards, > Marlin I am referring to the legacy 340 driver which OP is using and I am using. Nvidia doesn't support that driver above kernel 4. Tesla 450 doesn't look like legacy to me, it's in the Debian 11 repo.
Re: nvidia package 340xx
Hans writes: > Dear debian team, > > I just discovered the "nividia-legacy-340xx"-packages in debian sid. > > However, as they were in buster, but NOT in bullseye, NOR in bookworm, > I wonder, if there is a chance, they will transfer from testing to > bookworm some day. > > I tested them on bookworm, and they built (what a pleasent > surprise!!), but I could not load them on actual bookworm kernel > 6.1.0.9. Ok, this might be, that some other libs needed by the driver, > are incompatible, because they need libs from sid, but that does not > matter for me. > > My question is more: Will these packages be transferred to testing > some day and then from testing to stable? Or will they (when > transferred to testing) NEVER be transferred to stable (until the next > big release, of course). > > What is the policy with those (unfree and third party packages )and > what are the chances at all? > > Thanks for your help, oh and thank you for the people, who got this > package buildable! > > Best regards > > Hans As far as I remember the problem in Nvidia does not support kernels above 4. This is why my laptop is stuck on Debian 10, although I did wonder if Debian 11 can run with kernel 4. (Nouveaux is no good to me).
Gnome: The Videos application quits when clicking on Activities
I've noticed several times, when I am listening to an mp3 using the application 'Videos' that if I click on Activities to put the system into the view showing each task as a miniture window, that the Videos application abruptly quits. How can I find an error message for that? I've switched to useing Rythmbox for the time being but I think Videos is the default mp3 application.
Re: Am I infected with a rootkit?
It's a long shot, but does either computer have wifi? Is it secured with wpa2?
Re: Where has the Gnome hot corner setting gone?
Richmond wrote: > Cindy Sue Causey writes: > >> On 3/29/23, Richmond wrote: >>> I thought I had disabled hot corners, but occasionally, if I select and >>> swipe in the location bar of my browser, it activates hot corner. When I >>> went back to check the setting which was in "multitasking" before, that >>> tab has gone. Where is the hot corner setting now? >> >> Hi.. I've taken a poke at this via an Internet search. I originally >> missed you declaring GNOME in the subject line. That brings up this: >> >> gsettings set org.gnome.desktop.interface enable-hot-corners false >> >> That's a tweak on where they're telling the user on this webpage to >> enter "true": >> >> https://askubuntu.com/questions/1259451/how-to-enable-to-hot-corners-function-on-lubuntu20-04 >> >> Maybe once you set that, gsettings can be used to adjust it from >> there? I tried that command on my setup. It didn't complain since I do >> have one or more GNOME packages installed. Mine's currently set to >> "true" with no obvious GUI to set up what actions go with the 4 >> corners. >> >> Because you mentioned this was affecting your browser usage, maybe >> this explains what happened there: >> >> https://haydenjames.io/ubuntu-22-04-install-gnome-extensions-manager-workaround/ >> >> It's saying that Firefox, for one, is no longer compatible in that >> operating system. >> >> With some more searching, I encountered gnome-shell-extensions and >> gnome-shell-extension-manager. Those may or may not help, but they do >> exist and are specifically mentioned with respect to toggling hot >> corners. >> >> Searching for those two and Debian as keywords keeps trying to point >> users to outside websites. I don't know why it would since it looks >> like the same packages are available through Debian's own apt package >> manager. >> >> WARNING: I was going to test drive the extension manager, but >> gnome-shell-extensions by itself wants to install 201 new packages at >> 125MB download, 488MB of additional space used. Maybe next time. >> >> If anyone gets curious about hot corners, apparently not all desktops >> offer them and/or they store hot corners access in varying settings >> locations. Best bet might be to specify the desktop environment in >> searches. >> >> "apt-get search" pulls up an applet for Budgie. Anything else with hot >> corners apparently has them included as one piece of an inclusive >> "goodies" type package. >> >> Me? I tried it, maybe when I was trapped using Mint's LiveDVD. The >> experience lasted about 90 seconds. My mouse usage is too erratic, >> moves around the screen too much so the otherwise helpful effect got >> old really quick. >> >> Cindy :) > That's interesting because when I entered this: > > gsettings get org.gnome.desktop.interface enable-hot-corners > > it said: > > false > > Which means I have disabled it, and the effect I saw must have been a > bug. But it is hard to recreate. It happens from time to time though, I > am using a trackball mouse so zooming to the top right can happen quite > easily. > I find it easy to recreate now. Just press and hold the left mouse button, then whizz up to the top left corner, and it goes into whatever mode, even though hot corners are disabled.
Re: Where has the Gnome hot corner setting gone?
Cindy Sue Causey writes: > On 3/29/23, Richmond wrote: >> I thought I had disabled hot corners, but occasionally, if I select and >> swipe in the location bar of my browser, it activates hot corner. When I >> went back to check the setting which was in "multitasking" before, that >> tab has gone. Where is the hot corner setting now? > > > Hi.. I've taken a poke at this via an Internet search. I originally > missed you declaring GNOME in the subject line. That brings up this: > > gsettings set org.gnome.desktop.interface enable-hot-corners false > > That's a tweak on where they're telling the user on this webpage to > enter "true": > > https://askubuntu.com/questions/1259451/how-to-enable-to-hot-corners-function-on-lubuntu20-04 > > Maybe once you set that, gsettings can be used to adjust it from > there? I tried that command on my setup. It didn't complain since I do > have one or more GNOME packages installed. Mine's currently set to > "true" with no obvious GUI to set up what actions go with the 4 > corners. > > Because you mentioned this was affecting your browser usage, maybe > this explains what happened there: > > https://haydenjames.io/ubuntu-22-04-install-gnome-extensions-manager-workaround/ > > It's saying that Firefox, for one, is no longer compatible in that > operating system. > > With some more searching, I encountered gnome-shell-extensions and > gnome-shell-extension-manager. Those may or may not help, but they do > exist and are specifically mentioned with respect to toggling hot > corners. > > Searching for those two and Debian as keywords keeps trying to point > users to outside websites. I don't know why it would since it looks > like the same packages are available through Debian's own apt package > manager. > > WARNING: I was going to test drive the extension manager, but > gnome-shell-extensions by itself wants to install 201 new packages at > 125MB download, 488MB of additional space used. Maybe next time. > > If anyone gets curious about hot corners, apparently not all desktops > offer them and/or they store hot corners access in varying settings > locations. Best bet might be to specify the desktop environment in > searches. > > "apt-get search" pulls up an applet for Budgie. Anything else with hot > corners apparently has them included as one piece of an inclusive > "goodies" type package. > > Me? I tried it, maybe when I was trapped using Mint's LiveDVD. The > experience lasted about 90 seconds. My mouse usage is too erratic, > moves around the screen too much so the otherwise helpful effect got > old really quick. > > Cindy :) That's interesting because when I entered this: gsettings get org.gnome.desktop.interface enable-hot-corners it said: false Which means I have disabled it, and the effect I saw must have been a bug. But it is hard to recreate. It happens from time to time though, I am using a trackball mouse so zooming to the top right can happen quite easily.
Where has the Gnome hot corner setting gone?
I thought I had disabled hot corners, but occasionally, if I select and swipe in the location bar of my browser, it activates hot corner. When I went back to check the setting which was in "multitasking" before, that tab has gone. Where is the hot corner setting now?
Re: Playing Card Symbols
debian-u...@howorth.org.uk writes: >> I tried this in rxvt(-unicode), xterm, and lxterm (which is apparently >> part of the xterm package -- never heard of it before!). > > It's lxterminal, not lxterm, and it's part of LXDE so I'm surprised if > it's bundled with xterm. > lxterm and lxterminal are two different things. lxterm, and uxterm, are wrappers for xterm.
Re: Which takes priority, ipv4, or ipv6?
Vincent Lefevre writes: > On 2023-03-27 12:48:13 +0100, Richmond wrote: >> I have configured an ipv6 tunnel. If I visit this site: >> >> http://ip6.me/ >> >> The "normal" test shows my ipv4 address, and the: >> >> http://ip6only.me/ >> >> shows the ipv6 address. >> >> However if I switch my DNS from opendns to the one provided by my ISP >> and then run the "normal" test it shows the ipv6. >> >> The note says: >> >> (preference depends on your OS/client) >> >> So how is the preference determined? It seems to be determined by the >> DNS, but why or how do I tell for example with host -v? > > It appears to be random (based on past tests). > > But one can set the preference via "/etc/gai.conf". In particular: > > #For sites which prefer IPv4 connections change the last line to > # > #precedence :::0:0/96 100 > > I had to uncomment this line in the past when I had IPv6 issues. I uncommented the table and changed the 2002 to 2001 and that seems to have prioritized ipv6 but it's a bit of guesswork for me: precedence ::1/128 50 precedence ::/0 40 precedence 2001::/16 30 precedence ::/96 20 precedence :::0:0/96 10 Now if I go to google.com for example, ipvfoo (extension for chromium) tells me I am using ipv6.
Re: Which takes priority, ipv4, or ipv6?
Jeremy Ardley writes: > On 27/3/23 19:48, Richmond wrote: >> >> So how is the preference determined? It seems to be determined by the >> DNS, but why or how do I tell for example with host -v? > > When you as a DNS about a hostname it can return an A record and/or an > record. > > The A record is IPv4 and the record is IPv6 > > When you get both it is then up to your application to choose IPv4 or > IPv6 for the connection. > > If either fails the application will then try the other before finally > failing. > > You need a DNS that can return A and records, and an application > that can use either. > > I have noticed in my debian LAN that utilities such as ssh prefer IPv6 > and if that is not possible will use IPv4 Both DNS return records. I am not sure why this choice of DNS should make a difference. host -v ip6.me |grep IN 9306IN 2001:4838:0:1b::201 host -v ip6.me 8.8.8.8|grep IN 10800 IN 2001:4838:0:1b::201 host -v ip6.me 79.79.79.78|grep IN 300 IN 2001:4838:0:1b::201
Which takes priority, ipv4, or ipv6?
I have configured an ipv6 tunnel. If I visit this site: http://ip6.me/ The "normal" test shows my ipv4 address, and the: http://ip6only.me/ shows the ipv6 address. However if I switch my DNS from opendns to the one provided by my ISP and then run the "normal" test it shows the ipv6. The note says: (preference depends on your OS/client) So how is the preference determined? It seems to be determined by the DNS, but why or how do I tell for example with host -v?
Re: should CLI have a nice UI today?
cor...@free.fr writes: > Hello, > > Should CLI (command line interface) have a nice UI library? > today web dev has so many libraries that make web pages with > rich/colorful interactive views. > But CLI is still in dull mode. That should be improved in these days. > for example, run "df -h" we got the statistics with plain text. But > web statistics for cloud storage (GCP,AWS etc) are chart like, which > give people more intuitive feeling. > > Thanks > Corey H. I was very impressed with the signal meter in nmtui which I had not used before until yesterday. It has those chunky graphic characters like Teletext used to be. This sort of thing (I can't do it justice): וּכּ
Re: Windows Subsystem for Linux Debian
didier gaumet writes: > Le 07/03/2023 à 21:17, Richmond a écrit : >> I have Debian 11 on Windows Subsystem for Linux, but it is using a >> version 4 kernel. (I have established that it is debian 11 by looking in >> /etc/issue, and /etc/apt/sources). The Kernel says it is Microsoft: >> 4.4.0-19041-Microsoft #2311-Microsoft >> So I guess this is not really a kernel? as the version is a Windows >> version number, although I am on Windows 19045.2604. >> Who supports Debian 11 for WSL? It is in the Microsoft Store. Why is >> it >> on version 4 kernel? > > Hello, > > Warning: I do not use WSL1/WSL2 > but I would say that your Debian was installed as a WSL1 distro > (typical 4.4 pseudo linux kernel (translator, sort of)) and you could > migrate it to WSL2 (5.15 kernel presently, in a Hyper-V VM). > https://learn.microsoft.com/en-us/windows/wsl/compare-versions > https://superuser.com/questions/1628023/check-wsl-version-1-or-2-inside-the-linux-installation > https://learn.microsoft.com/en-us/windows/wsl/kernel-release-notes It seems I had not upgraded to WSL2. I thought I had. Now I have done that I am on the right kernel. 5.15.90.1-microsoft-standard-WSL2 #1
Windows Subsystem for Linux Debian
I have Debian 11 on Windows Subsystem for Linux, but it is using a version 4 kernel. (I have established that it is debian 11 by looking in /etc/issue, and /etc/apt/sources). The Kernel says it is Microsoft: 4.4.0-19041-Microsoft #2311-Microsoft So I guess this is not really a kernel? as the version is a Windows version number, although I am on Windows 19045.2604. Who supports Debian 11 for WSL? It is in the Microsoft Store. Why is it on version 4 kernel?
Re: Need help to install gnucobol
Amine Derk writes: > Hello, > > I'm trying to use debian for the first time. and I'm not able to > install Gnucobol. > > aderkaoua@LAPTOP-6B841S0M:~$ sudo apt-get install gnucobol > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > E: Unable to locate package gnucobol > > please advise? > > Amine. > Cobol Developer > 571 234 9827 I compiled gnu-cobol and have it working. I obtained: gnucobol-3.1.2.tar.xz tar axvf gnucobol-3.1.2.tar.xz cd gnucobol-3.1.2 ./configure make Probably there were errors which I fixed by installing things. See how far you get.
Re: kernel errors
Max Nikulin writes: > On 05/02/2023 03:12, Richmond wrote: >> The errors about sr0 come before the stuff about resume. > > Does the following command generate similar errors (taken from initrd > scripts, UUID is intentionally not from the set of existing > partitions)? > > blkid -l -t UUID=---- -o device > > I would try it at first in normally running system. Perhaps some > caches may be involved preventing query to the optical drive. I have > no bright idea how to cause drop to initrd shell to try the command > there, perhaps root=... kernel command line parameter may be removed > or changed to non-existing device from grub prompt. > > I am unsure which particular command from initrd scans devices, my > guess may be wrong. It didn't produce any output.
Re: kernel errors
Richmond wrote: > David Wright writes: > >> On Sat 04 Feb 2023 at 17:38:25 (+0000), Richmond wrote: >>> David Wright writes: >>>> On Sat 04 Feb 2023 at 12:37:27 (+), Richmond wrote: >>>>> Max Nikulin writes: >>>>>> On 03/02/2023 01:47, Richmond wrote: >>>>>>> It might be a good way for someone to reproduce the error on some >>>>>>> other >>>>>>> machine. I have no problems with the CD/DVD writer and have used it a >>>>>>> few times recently. >>>>>> Do you see the same errors if kernel command line is edited from grub >>>>>> to pass non-existing UUID specified in the resume=UUID=... argument? >>>>>> It might be a quick way to reproduce the issue. >>>>> I looked in grub but couldn't see any resume parameter. I think the way >>>>> things work has changed, and this is hidden away somewhere. >>>> There are hundreds and hundreds of kernel command-line parameters, >>>> so I'm not sure how you expect to see any evidence of each one in >>>> Grub's configuration. >>> We were talking about editing from grub during boot time, not looking in >>> grubs configuration. >> You wrote: "I looked in grub". >> >> My interpretation: "I looked in grub.cfg by typing 'E' on one or more >> of the entries in Grub's blue screen when booting the computer". >> > I see. Max (and you) mean add the resume parameter, not edit an existing one. > I > was looking for an existing one. I will try this. > It worked, I recreated the error, including the stuff about sr0. The errors about sr0 come before the stuff about resume.
Re: kernel errors
David Wright writes: > On Sat 04 Feb 2023 at 17:38:25 (+), Richmond wrote: >> David Wright writes: >> > On Sat 04 Feb 2023 at 12:37:27 (+), Richmond wrote: >> >> Max Nikulin writes: >> >> > On 03/02/2023 01:47, Richmond wrote: >> >> >> It might be a good way for someone to reproduce the error on some >> >> >> other >> >> >> machine. I have no problems with the CD/DVD writer and have used it a >> >> >> few times recently. >> >> > >> >> > Do you see the same errors if kernel command line is edited from grub >> >> > to pass non-existing UUID specified in the resume=UUID=... argument? >> >> > It might be a quick way to reproduce the issue. >> >> >> >> I looked in grub but couldn't see any resume parameter. I think the way >> >> things work has changed, and this is hidden away somewhere. >> > >> > There are hundreds and hundreds of kernel command-line parameters, >> > so I'm not sure how you expect to see any evidence of each one in >> > Grub's configuration. >> >> We were talking about editing from grub during boot time, not looking in >> grubs configuration. > > You wrote: "I looked in grub". > > My interpretation: "I looked in grub.cfg by typing 'E' on one or more > of the entries in Grub's blue screen when booting the computer". > I see. Max (and you) mean add the resume parameter, not edit an existing one. I was looking for an existing one. I will try this.
Re: kernel errors
David Wright writes: > On Sat 04 Feb 2023 at 12:37:27 (+), Richmond wrote: >> Max Nikulin writes: >> > On 03/02/2023 01:47, Richmond wrote: >> >> It might be a good way for someone to reproduce the error on some >> >> other >> >> machine. I have no problems with the CD/DVD writer and have used it a >> >> few times recently. >> > >> > Do you see the same errors if kernel command line is edited from grub >> > to pass non-existing UUID specified in the resume=UUID=... argument? >> > It might be a quick way to reproduce the issue. >> >> I looked in grub but couldn't see any resume parameter. I think the way >> things work has changed, and this is hidden away somewhere. > > There are hundreds and hundreds of kernel command-line parameters, > so I'm not sure how you expect to see any evidence of each one in > Grub's configuration. We were talking about editing from grub during boot time, not looking in grubs configuration.
Re: kernel errors
Max Nikulin writes: > On 03/02/2023 01:47, Richmond wrote: >> It might be a good way for someone to reproduce the error on some >> other >> machine. I have no problems with the CD/DVD writer and have used it a >> few times recently. > > Do you see the same errors if kernel command line is edited from grub > to pass non-existing UUID specified in the resume=UUID=... argument? > It might be a quick way to reproduce the issue. I looked in grub but couldn't see any resume parameter. I think the way things work has changed, and this is hidden away somewhere. > > Is it realistic that usually optical drives are skipped during UUID > searches, but specific driver exposes a wrong property, so the device > is considered as a regular disk drive? I don't know.
Re: kernel errors
"Thomas Schmitt" writes:
> Hi,
>
> Richmond wrote:
>> /tmp/initrd21/scripts/local:[ "${quiet?}" != "y" ] && log_begin_msg
>> "Running /scripts/local-block"
>> [...]
>> local_block()
>> {
>>[ "${quiet?}" != "y" ] && log_begin_msg "Running /scripts/local-block"
>>run_scripts /scripts/local-block "$@"
>> [...]
>> Then later this, which would explain the delays: (The video shows
>> "waiting for suspend/resume device")
>> [...]
>> log_begin_msg "Waiting for ${name}"
>> [...]
>> while true; do
>> sleep 1
>> time_elapsed="$(time_elapsed)"
>>
>> local_block "${dev_id}"
>
> I remember to have seen this code under
> https://sources.debian.org/src/initramfs-tools/unstable/
> when i looked for occurences of "local-block". (This URL is currently not
> working for me.)
> I did not find any built-in runs of programs like blkid or lsblk. Thus i
> concluded that such runs would be in files of /scripts/local-block or other
> local customization of the initrd.
>
> We are most probably at the right spot of initramfs-tools.
> Maybe the script which runs blkid or alike has vanished during the recent
> reconstruction of the initrd which fixed the problems ?
I didn't need to reconstruct initrd to cause the problems. As far as I
remember all I did was destroy the swap space, having commented-it-out
of fstab. So I imagin that the scripts are the same. But I could test
that as suggested by Max Nikulin by altering the resume parameter from
grub before booting.
>
> Does fgrep find anything about "blkid" in /tmp/initrd21 ?
I did it like this:
find /tmp/initrd21/ -print|xargs grep -i blkid|less
/tmp/initrd21/usr/lib/udev/rules.d/60-persistent-storage.rules:
IMPORT{builtin}="blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}"
/tmp/initrd21/usr/lib/udev/rules.d/60-persistent-storage.rules:
IMPORT{builtin}="blkid --noraid"
/tmp/initrd21/usr/lib/udev/rules.d/60-persistent-storage.rules:KERNEL!="sr*",
IMPORT{builtin}="blkid"
/tmp/initrd21/usr/lib/udev/rules.d/60-persistent-storage-dm.rules:IMPORT{builtin}="blkid"
/tmp/initrd21/scripts/functions:# blkid has a more complete list of
file systems,
/tmp/initrd21/scripts/functions:FSTYPE=$(blkid -o value -s TYPE
"${FS}") || return
/tmp/initrd21/scripts/functions:DEV="$(blkid -l -t "$DEV" -o
device)" || return 1
/tmp/initrd21/scripts/local:# device in /dev and isn't resolvable by blkid
(e.g. mtd0)
Re: kernel errors
"Thomas Schmitt" writes:
> Hi,
>
> Richmond wrote:
>> No local block. :-?
>
> Maybe you can find our from where the message comes:
>
> grep -r 'Running.*scripts.*local-block' /tmp/initrd21
>
>
grep -r 'Running.*scripts.*local-block' /tmp/initrd21
/tmp/initrd21/scripts/local:[ "${quiet?}" != "y" ] && log_begin_msg
"Running /scripts/local-block"
This contains:
===
local_block()
{
[ "${quiet?}" != "y" ] && log_begin_msg "Running /scripts/local-block"
run_scripts /scripts/local-block "$@"
[ "$quiet" != "y" ] && log_end_msg
}
===
Then later this, which would explain the delays: (The video shows
"waiting for suspend/resume device")
===
# If the root device hasn't shown up yet, give it a little while
# to allow for asynchronous device discovery (e.g. USB). We
# also need to keep invoking the local-block scripts in case
# there are devices stacked on top of those.
if ! real_dev=$(resolve_device "${dev_id}") ||
! get_fstype "${real_dev}" >/dev/null; then
log_begin_msg "Waiting for ${name}"
# Timeout is max(30, rootdelay) seconds (approximately)
slumber=30
if [ "${ROOTDELAY:-0}" -gt $slumber ]; then
slumber=$ROOTDELAY
fi
while true; do
sleep 1
time_elapsed="$(time_elapsed)"
local_block "${dev_id}"
# If mdadm's local-block script counts the
# number of times it is run, make sure to
# run it the expected number of times.
while true; do
if [ -f /run/count.mdadm.initrd ]; then
count="$(cat /run/count.mdadm.initrd)"
elif [ -n "${count}" ]; then
# mdadm script deleted it; put it back
count=$((count + 1))
echo "${count}" >/run/count.mdadm.initrd
else
:
Re: kernel errors
David Wright writes: > On Thu 02 Feb 2023 at 21:58:54 (+), Richmond wrote: >> "Thomas Schmitt" writes: >> > >> > (If not there, then in the /scripts/local-block directory of the initrd ?) >> >> I don't know how I would look in that. Is it in RAM at boot time? > >Choose your kernel ↓↓Pick any name > > $ unmkinitramfs /boot/initrd.img-5.10.0-21-amd64 /tmp/initrd21 > cpio: etc/console-setup/null: Cannot mknod: Operation not permitted > $ ls -GlgR /tmp/initrd21/main/scripts/ > /tmp/initrd21/main/scripts/: > total 48 > -rw-r--r-- 1 11152 Jan 14 2021 functions > drwxr-xr-x 2 4096 Feb 2 18:45 init-bottom > drwxr-xr-x 2 4096 Feb 2 18:45 init-top > -rw-r--r-- 1 5303 Jan 14 2021 local > drwxr-xr-x 2 4096 Feb 2 18:45 local-block > drwxr-xr-x 2 4096 Feb 2 18:45 local-bottom > drwxr-xr-x 2 4096 Feb 2 18:45 local-premount > drwxr-xr-x 2 4096 Feb 2 18:45 local-top > -rw-r--r-- 1 3093 Jan 14 2021 nfs > > /tmp/initrd21/main/scripts/init-bottom: > total 8 > -rw-r--r-- 1 77 Jan 23 21:46 ORDER > -rwxr-xr-x 1 611 Aug 7 08:25 udev > > /tmp/initrd21/main/scripts/init-top: > total 20 > -rw-r--r-- 1 314 Jan 23 21:46 ORDER > -rwxr-xr-x 1 384 Jan 14 2021 all_generic_ide > -rwxr-xr-x 1 296 Jan 14 2021 blacklist > -rwxr-xr-x 1 167 Jan 14 2021 keymap > -rwxr-xr-x 1 568 Aug 7 08:25 udev > > /tmp/initrd21/main/scripts/local-block: > total 8 > -rw-r--r-- 1 82 Jan 23 21:46 ORDER > -rwxr-xr-x 1 246 Feb 1 2022 cryptroot > > /tmp/initrd21/main/scripts/local-bottom: > total 20 > -rw-r--r-- 1 336 Jan 23 21:46 ORDER > -rwxr-xr-x 1 253 Feb 1 2022 cryptgnupg-sc > -rwxr-xr-x 1 449 Feb 1 2022 cryptopensc > -rwxr-xr-x 1 307 Feb 1 2022 cryptroot > -rwxr-xr-x 1 345 Nov 2 16:46 ntfs_3g > > /tmp/initrd21/main/scripts/local-premount: > total 12 > -rw-r--r-- 1 165 Jan 23 21:46 ORDER > -rwxr-xr-x 1 226 Nov 2 16:46 ntfs_3g > -rwxr-xr-x 1 863 Jan 14 2021 resume > > /tmp/initrd21/main/scripts/local-top: > total 20 > -rw-r--r-- 1 162 Jan 23 21:46 ORDER > -rwxr-xr-x 1 757 Feb 1 2022 cryptopensc > -rwxr-xr-x 1 8630 Feb 1 2022 cryptroot > $ > > This is a desktop with random-key swap, so no resume. > There are encrypted partitions present. YMMV. > > Cheers, > David. ~$ unmkinitramfs /boot/initrd.img-5.10.0-21-amd64 /tmp/initrd21 ~$ find /tmp/initrd21/ -print|grep "local-block" ~$ find /tmp/initrd21/ -print|grep "local" /tmp/initrd21/usr/local /tmp/initrd21/usr/local/share /tmp/initrd21/usr/local/share/fonts /tmp/initrd21/usr/local/share/fonts/.uuid /tmp/initrd21/scripts/local-bottom /tmp/initrd21/scripts/local-bottom/ntfs_3g /tmp/initrd21/scripts/local-bottom/ORDER /tmp/initrd21/scripts/local /tmp/initrd21/scripts/local-premount /tmp/initrd21/scripts/local-premount/ntfs_3g /tmp/initrd21/scripts/local-premount/ORDER /tmp/initrd21/scripts/local-premount/resume No local block. :-? find /tmp/initrd21/ -print|grep local|grep block No output here.
Re: kernel errors
Michel Verdier writes: > Le 2 février 2023 Richmond a écrit : > >> There is no such file. Earlier I ran this: >> >> find / -print|grep "scripts/local-block" >> >> and it found nothing, which led me to believe it is some temporary file... >>> >>> (If not there, then in the /scripts/local-block directory of the initrd ?) > > its part of initramfs-tools to build initrd when you use cryptsetup, > mdadm, etc > > $ locate local-block > /usr/share/initramfs-tools/scripts/local-block > /usr/share/initramfs-tools/scripts/local-block/cryptroot > > $ apt-file search /usr/share/initramfs-tools/scripts/local-block > cryptsetup-initramfs: /usr/share/initramfs-tools/scripts/local-block/cryptroot > lvm2: /usr/share/initramfs-tools/scripts/local-block/lvm2 > mdadm: /usr/share/initramfs-tools/scripts/local-block/mdadm > osk-sdl: /usr/share/initramfs-tools/scripts/local-block/osk-sdl sudo locate local-block produced no output. sudo apt-file search /usr/share/initramfs-tools/scripts/local-block cryptsetup-initramfs: /usr/share/initramfs-tools/scripts/local-block/cryptroot lvm2: /usr/share/initramfs-tools/scripts/local-block/lvm2 mdadm: /usr/share/initramfs-tools/scripts/local-block/mdadm osk-sdl: /usr/share/initramfs-tools/scripts/local-block/osk-sdl I don't have an encrypted file system. sudo aptitude show cryptsetup-initramfs|grep State State: not installed sudo aptitude show lvm2|grep State State: not installed sudo aptitude show mdadm|grep State State: not installed sudo aptitude show osk-sdl|grep State State: not installed
Re: kernel errors
"Thomas Schmitt" writes: > Indeed. But why should only the kernel be brain damaged ? > > (I expect some generic UUID searcher for block devices. Probably the sr > devices are near the end of its iteration. So one would not see any > protest in the log if the UUID is found on the device which is tried > earlier.) It crossed my mind that someone could conceivably be using the Universal Disk Format on a DVD RW. > Still missing is the code which wants to inspect sr. I tried to learn > about /scripts/local-block in initramfs-tools. Regrettably it seems to > be about a local customization of the initrd, which is not done by > initramfs-tools but by its customers. > A search for "local-block" in Debian's source collection by > https://codesearch.debian.net/search?q=local-block > did not yield good candidates. > > Do you see something related to resume in the output of > ls /usr/share/initramfs-tools/scripts/local-block There is no such file. Earlier I ran this: find / -print|grep "scripts/local-block" and it found nothing, which led me to believe it is some temporary file... > > (If not there, then in the /scripts/local-block directory of the initrd ?) I don't know how I would look in that. Is it in RAM at boot time? In the log which appears on the screen it says: Begin: Waiting for suspend/resume device ... Begin: Running /scripts/local-block ... done. random: crng init done /scripts/local-block ... done. Then this last line was repeated 17 times and much time was spent. Then it gave up.
Re: kernel errors - SOLVED
piorunz writes: > On 02/02/2023 14:05, Richmond wrote: >> After I did this, the errors went away. >> I don't know why the errors reference sr0, it's a mystery. > > They will most likely come back, this error is related to optical > drive, nothing to do with swap space. Perhaps the system was looking for resume space on sr0? It seems a strange thing to do. But also it is quite a coincidence if the errors occur when the resume space is messed up, and they go away when it is fixed. That has happened twice. It might be a good way for someone to reproduce the error on some other machine. I have no problems with the CD/DVD writer and have used it a few times recently.
Re: kernel errors - SOLVED
Richmond writes: > It may be a coincidence but yesterday I installed some > libguestfs-tools. Now I see errors when booting, which also appear in > /var/log/messages: > > kernel: [9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result: > hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s > kernel: [9.507009] sr 3:0:0:0: [sr0] tag#12 Sense Key : Not Ready > [current] > kernel: [9.507146] sr 3:0:0:0: [sr0] tag#12 Add. Sense: Medium not > present - tray closed > kernel: [9.507304] sr 3:0:0:0: [sr0] tag#12 CDB: Read(10) 28 00 00 07 ff > fc 00 00 02 00 > kernel: [9.507731] sr 3:0:0:0: [sr0] tag#31 unaligned transfer > kernel: [9.513520] sr 3:0:0:0: [sr0] tag#13 unaligned transfer > kernel: [9.529995] sr 3:0:0:0: [sr0] tag#14 unaligned transfer These errors started occurring again. This time I knew what I had done, I commented out a line in fstab referencing a swap space, because the system had two swap spaces defined and I wanted to use one for something else. What I overlooked was that this swap space was also the resume space. During the boot there were other messages which did not appear in the journal so I filmed them with a smart phone: Running /scripts/local-block.. These occurred over and over, but allowed me to find this site: https://tipstricks.itmatrix.eu/solving-the-running-scripts-local-block-loop-while-booting-in-linux/ Which explained the problem and how to fix it. I had already edited: /etc/initramfs-tools/conf.d/resume To use the other swap space. But this did not help because I missed this crucial step: sudo update-initramfs -u After I did this, the errors went away. I don't know why the errors reference sr0, it's a mystery.
Re: kernel errors
Richmond writes: > "Thomas Schmitt" writes: > >> Hi, >> >> i wrote: >>> > If you have some blank optical medium, then try whether the emitter of >>> > the read attempt can be discouraged if the drive is perceived as offering >>> > just one block of 2048 bytes. >> >> Richmond wrote: >>> I don't know how to do that. Do you mean make a DVD with 1 block of data? >> >> Just put in a blank CD-R, CD-RW, DVD-R, DVD+R, or unformatted blank DVD-RW. >> The size perception will change to >> VENDOR MODEL SIZE PHY-SEC LOG-SEC >> HL-DT-ST HL-DT-ST_DVDRAM_GH15F 204820482048 >> >> Pull it out again, and this state will persist until you put in a medium >> which is readable, or until you reboot. >> > > I put in a blank DVD+RW. > > lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr* > VENDOR MODEL SIZE PHY-SEC LOG-SEC > HL-DT-ST HL-DT-ST_DVDRAM_GH15F 204820482048 > > It has stayed like this after I removed it. I tried this on the same PC, but OpenSUSE 15.2, kernel 5.3 and putting the blank disk in did not change the values, it still showed 512.
Re: kernel errors
"Thomas Schmitt" writes: > Hi, > > i wrote: >> > If you have some blank optical medium, then try whether the emitter of >> > the read attempt can be discouraged if the drive is perceived as offering >> > just one block of 2048 bytes. > > Richmond wrote: >> I don't know how to do that. Do you mean make a DVD with 1 block of data? > > Just put in a blank CD-R, CD-RW, DVD-R, DVD+R, or unformatted blank DVD-RW. > The size perception will change to > VENDOR MODEL SIZE PHY-SEC LOG-SEC > HL-DT-ST HL-DT-ST_DVDRAM_GH15F 204820482048 > > Pull it out again, and this state will persist until you put in a medium > which is readable, or until you reboot. > I put in a blank DVD+RW. lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr* VENDOR MODEL SIZE PHY-SEC LOG-SEC HL-DT-ST HL-DT-ST_DVDRAM_GH15F 204820482048 It has stayed like this after I removed it.
Re: kernel errors
"Thomas Schmitt" writes: > I assume that you will see the same result there. lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr* VENDOR MODEL SIZE PHY-SEC LOG-SEC HL-DT-ST HL-DT-ST_DVDRAM_GH15F 1073741312 512 512 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux > > If you have some blank optical medium, then try whether the emitter of > the read attempt can be discouraged if the drive is perceived as offering > just one block of 2048 bytes. I don't know how to do that. Do you mean make a DVD with 1 block of data? > There are many motivations to read the start of the device and fewer to > read its end. One reason to read the end is the GPT backup header, which > would sit 512 bytes before the end. > The main GPT header block is at byte 512 of the storage device. I am not using GPT on any systems. They all have ext4 root partitions.
Re: kernel errors
"Thomas Schmitt" writes: > > Are users of Debian 10 (actually of kernel 4.19) here who are willing to > run > lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr* > directly after booting with empty drive tray ? lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr* VENDOR MODELSIZE PHY-SEC LOG-SEC TSSTcorp TSSTcorp_DVD+_-RW_TS-L632H 1073741312 512 512 4.19.0-23-amd64 #1 SMP Debian 4.19.269-1 (2022-12-20) x86_64 GNU/Linux This is a laptop where I rarely use the CD/DVD. Note it is not the same computer as was getting errors before, that was debian 11.
Re: Ctrl-C ignored after pasting a long text in an X terminal emulator
Greg Wooledge wrote: > On Mon, Jan 23, 2023 at 01:51:08PM +0000, Richmond wrote: >> I didn't test it for the reason I stated. I think it would be better for >> OP to test it as he won't do any more damage than he has already done. > Here's how you can reproduce the problem without having to worry > about execution of the pasted text as commands: > > 1) Import some text into the paste buffer (xclip -i < somefile). > 2) Open an xterm. > 3) From the xterm, run "xeyes" or any other X client program, no ampersand. > 4) Paste text into the xterm. > 5) Try Ctrl keys. Observe that none of them work. > 6) Close the xterm using the window manager controls. > >> I have come across occasions where ctrl-c doesn't work but ctrl-z does >> however. > Sure, in a terminal that's in a normal state, that happens all the time, > if something is ignoring SIGINT. The entire point of this thread is > that when the input buffer of the pty behind the xterm fills up, none > of the signals that are generated by keyboard input in a terminal work > any longer. The only resort is to close the xterm. > No that wasn't the entire point of the thread. The OP didn't know the cause, it was presumed by David Wright that it was caused by the buffer filling up. But it could have been caused by some spurious character in the file, e.g. ctrl-s.
Re: kernel errors
David Wright writes: > On Mon 23 Jan 2023 at 13:34:50 (+), Richmond wrote: >> It may be a coincidence but yesterday I installed some >> libguestfs-tools. Now I see errors when booting, which also appear in >> /var/log/messages: >> >> kernel: [ 9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result: >> hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s >> kernel: [9.507009] sr 3:0:0:0: [sr0] tag#12 Sense Key : Not Ready >> [current] >> kernel: [9.507146] sr 3:0:0:0: [sr0] tag#12 Add. Sense: Medium not >> present - tray closed >> kernel: [9.507304] sr 3:0:0:0: [sr0] tag#12 CDB: Read(10) 28 00 00 07 ff >> fc 00 00 02 00 >> kernel: [9.507731] sr 3:0:0:0: [sr0] tag#31 unaligned transfer >> kernel: [9.513520] sr 3:0:0:0: [sr0] tag#13 unaligned transfer >> kernel: [9.529995] sr 3:0:0:0: [sr0] tag#14 unaligned transfer >> kernel: [ 9.602797] sr 3:0:0:0: [sr0] tag#3 FAILED Result: >> hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s >> kernel: [9.608514] sr 3:0:0:0: [sr0] tag#3 Sense Key : Not Ready >> [current] >> kernel: [9.614297] sr 3:0:0:0: [sr0] tag#3 Add. Sense: Medium not >> present - tray closed >> kernel: [9.620170] sr 3:0:0:0: [sr0] tag#3 CDB: Read(10) 28 00 00 00 00 >> 00 00 00 02 00 >> kernel: [9.631993] sr 3:0:0:0: [sr0] tag#4 unaligned transfer >> kernel: [9.650464] sr 3:0:0:0: [sr0] tag#5 unaligned transfer >> >> I removed the toos, and also disabled udiskd or udisk2d: >> >> systemctl stop udisks2.service >> systemctl disable udisks2.service >> >> But the errors are still occuring. How can I stop them? >> >> Installing the tools did some strange things like regenerating the grub >> menu. > > When you've removed the packages, keep a copy of your grub.cfg for > comparison and then reconfigure grub (grub-mkconfig). See if the > messages go away. The messages didn't go away. And I tried to reconfigure swap and resume, and got more errors, so I reinstalled the system, formatting the root partition. > > Did you have something strange in your optical drive when you > installed these tools, in anticipation of using the latter on > the former? No, but I did have a usb stick plugged in, and it had ChromeOS Flex on it. In fact that appeared on the grub menu yesterday and I tried to boot ChromeOS Flex from it. That was no doubt a big mistake.
Re: kernel errors
Sven Joachim writes: > On 2023-01-23 16:13 +0000, Richmond wrote: > >> I put a dvd in and mounted it. Then rebooted. I saw these messages: >> >> [ 756.539018] pktcdvd: pktcdvd0: writer mapped to sr0 >> [3.744658] sr 3:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram >> cd/rw xa/form2 cdda tray >> [ 19.585098] pktcdvd: pktcdvd0: writer mapped to sr0 >> >> Then removed the DVD and rebooted, back to these: >> >> [4.006759] sr 3:0:0:0: [sr0] scsi3-mmc drive: 40x/40x writer dvd-ram >> cd/rw xa/form2 cdda tray >> [9.434955] sr 3:0:0:0: [sr0] tag#1 FAILED Result: hostbyte=DID_OK >> driverbyte=DRIVER_SENSE cmd_age=2s >> [9.439990] sr 3:0:0:0: [sr0] tag#1 Sense Key : Not Ready [current] >> [9.444968] sr 3:0:0:0: [sr0] tag#1 Add. Sense: Medium not present - >> tray closed >> [9.449918] sr 3:0:0:0: [sr0] tag#1 CDB: Read(10) 28 00 00 07 ff fc 00 >> 00 02 00 >> [9.459897] sr 3:0:0:0: [sr0] tag#18 unaligned transfer >> >> I am starting to consider re-installing, although everything is working, >> I don't like the look of it. Perhaps I should just re-install the >> kernel? > > This would most likely not help. Instead you should try to figure out > what process is trying to read from your empty drive, and why. > Consulting journalctl might help with that. > > Cheers, >Sven re-installing kernel didn't work. I looked in journalctl and saw this: kernel: PM: Image not found (code -22) It's looking for a resume from hibernate maybe. So then it became apparent that the kernel parameter to resume is a disk by id which looks different from the ones in /etc/fstab. I am not sure how that came about.
Re: kernel errors
"Thomas Schmitt" writes: > Hi, > > Richmond wrote: >> kernel: [9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result: >> hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s >> kernel: [9.507009] sr 3:0:0:0: [sr0] tag#12 Sense Key : Not Ready >> [current] >> kernel: [9.507146] sr 3:0:0:0: [sr0] tag#12 Add. Sense: Medium not >> present - tray closed >> kernel: [9.507304] sr 3:0:0:0: [sr0] tag#12 CDB: Read(10) 28 00 00 07 ff >> fc 00 00 02 00 > > Your optical drive gets asked for 2 blocks iand answers that there is no > medium recognized in the tray. The request was to read from block 0x07fffc > = 524284 = 1023.9921875 MiB = 1 GiB - 4 KiB. > This is not a usual medium capcity. So i wonder from where the caller had > that block address. > > >> kernel: [9.507731] sr 3:0:0:0: [sr0] tag#31 unaligned transfer > > I wonder what might have caused this. But this line brings me to > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948358 > where pior...@gmail.com tried to get this processed as bug of udev. > No solution was found. > > >> kernel: [9.602797] sr 3:0:0:0: [sr0] tag#3 FAILED Result: >> hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s >> kernel: [9.608514] sr 3:0:0:0: [sr0] tag#3 Sense Key : Not Ready >> [current] >> kernel: [9.614297] sr 3:0:0:0: [sr0] tag#3 Add. Sense: Medium not >> present - tray closed >> kernel: [9.620170] sr 3:0:0:0: [sr0] tag#3 CDB: Read(10) 28 00 00 00 00 >> 00 00 00 02 00 > > This read attempt wanted to get 2 blocks from block address 0. > More plausible as a wild guess, than 1 GiB - 4 KiB. > > > What happens if you give the drive a readable DVD ? > Maybe the software which issues the READ commands shows up with some more > enlightening complaint. > > > Have a nice day :) > > Thomas I put a dvd in and mounted it. Then rebooted. I saw these messages: [ 756.539018] pktcdvd: pktcdvd0: writer mapped to sr0 [3.744658] sr 3:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray [ 19.585098] pktcdvd: pktcdvd0: writer mapped to sr0 Then removed the DVD and rebooted, back to these: [4.006759] sr 3:0:0:0: [sr0] scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray [9.434955] sr 3:0:0:0: [sr0] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s [9.439990] sr 3:0:0:0: [sr0] tag#1 Sense Key : Not Ready [current] [9.444968] sr 3:0:0:0: [sr0] tag#1 Add. Sense: Medium not present - tray closed [9.449918] sr 3:0:0:0: [sr0] tag#1 CDB: Read(10) 28 00 00 07 ff fc 00 00 02 00 [9.459897] sr 3:0:0:0: [sr0] tag#18 unaligned transfer I am starting to consider re-installing, although everything is working, I don't like the look of it. Perhaps I should just re-install the kernel?
Re: Ctrl-C ignored after pasting a long text in an X terminal emulator
Greg Wooledge writes: > It doesn't work, presumably for the same reason that Ctrl-C doesn't work. > The xterm's pty's input buffer is full, and it simply ignores all keyboard > input from that point forward. > > (Are people not actually *testing* these things before proposing them?) I didn't test it for the reason I stated. I think it would be better for OP to test it as he won't do any more damage than he has already done. I have come across occasions where ctrl-c doesn't work but ctrl-z does however.
kernel errors
It may be a coincidence but yesterday I installed some libguestfs-tools. Now I see errors when booting, which also appear in /var/log/messages: kernel: [9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s kernel: [9.507009] sr 3:0:0:0: [sr0] tag#12 Sense Key : Not Ready [current] kernel: [9.507146] sr 3:0:0:0: [sr0] tag#12 Add. Sense: Medium not present - tray closed kernel: [9.507304] sr 3:0:0:0: [sr0] tag#12 CDB: Read(10) 28 00 00 07 ff fc 00 00 02 00 kernel: [9.507731] sr 3:0:0:0: [sr0] tag#31 unaligned transfer kernel: [9.513520] sr 3:0:0:0: [sr0] tag#13 unaligned transfer kernel: [9.529995] sr 3:0:0:0: [sr0] tag#14 unaligned transfer kernel: [9.602797] sr 3:0:0:0: [sr0] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s kernel: [9.608514] sr 3:0:0:0: [sr0] tag#3 Sense Key : Not Ready [current] kernel: [9.614297] sr 3:0:0:0: [sr0] tag#3 Add. Sense: Medium not present - tray closed kernel: [9.620170] sr 3:0:0:0: [sr0] tag#3 CDB: Read(10) 28 00 00 00 00 00 00 00 02 00 kernel: [9.631993] sr 3:0:0:0: [sr0] tag#4 unaligned transfer kernel: [9.650464] sr 3:0:0:0: [sr0] tag#5 unaligned transfer I removed the toos, and also disabled udiskd or udisk2d: systemctl stop udisks2.service systemctl disable udisks2.service But the errors are still occuring. How can I stop them? Installing the tools did some strange things like regenerating the grub menu.
Re: Ctrl-C ignored after pasting a long text in an X terminal emulator
Vincent Lefevre wrote: > The following issue is reproducible in several terminals, e.g. xterm > and GNOME Terminal, and several shells, e.g. bash and zsh. > > 1. From the shell in an X terminal emulator, run an X application > in foreground, e.g. emacs-gtk or xterm. > > 2. Paste a long text (e.g. the contents of /usr/share/doc/libc6/copyright > to choose an example every one has) in the terminal. Actually, only > the beginning of the text appears in the terminal. > > 3. Type Ctrl-C (one or several times) in the terminal. > But nothing happens. You could try pressing ctrl-z at this point to send the application into background. fg would bring it into foreground again. I am not going to send that document into a terminal. It has asterisks in it, what would happen if there were a line break and the next characters were rm * ?
Bitlbee user
Why is there a user called bitlbee on my system (nologin) when bitlbee is not installed? Also there is a user saned but sane is not installed.
Re: I've noticed a general protection fault
Richmond writes: > This occurs during shutdown. I've also noticed occasional delays "a stop > job is running". These occur when I am using a desktop > environment. Currently I am using gnome. > > kernel: traps: dconf worker[2353] general protection fault > ip:7fe4564ec4a6 sp:7fe448e31090 error:0 in > libc-2.31.so[7fe4564d3000+15a000] 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux These errors started on 5th January, but kernel 5.10.0-20 has been in since December 26th. Debian 11. Gnome.
I've noticed a general protection fault
This occurs during shutdown. I've also noticed occasional delays "a stop job is running". These occur when I am using a desktop environment. Currently I am using gnome. kernel: traps: dconf worker[2353] general protection fault ip:7fe4564ec4a6 sp:7fe448e31090 error:0 in libc-2.31.so[7fe4564d3000+15a000]
Re: Seamonkey
David Wright wrote: > On Fri 18 Nov 2022 at 19:37:24 (+0800), Richard Jones wrote: >> There doesn't seem to be a seamonkey package for Debian stable. Am I >> mistaken? or is there a reason for it to not be supported? >> >> I'm presuming I can download and install from the seamonkey site but >> want to check whether that is a bad idea--compatibility, security, >> whatever > https://wiki.debian.org/Seamonkey > may help. > > Cheers, > David. > That looks out of date to me. You can download an official build. And it updates itself. https://www.seamonkey-project.org/releases/#official Although I put it into /usr/local/seamonkey and protect it from self-updating using permissions.
Re: debian freezing
Pierre Frenkiel writes: > Has anybody a solution? > I saw this problem with the nouveau video driver, and the solution was to use the nvidia driver.
Re: Screenshot with Gnome
Curt writes: > On 2022-07-26, Greg Wooledge wrote: >> On Tue, Jul 26, 2022 at 05:03:09PM +0300, Antti Talsta wrote: >>> On Tue, Jul 26, 2022 at 12:40:53PM +0100, Richmond wrote: >>> > I am trying to take a screenshot of a selected area. >>> > I think something is broken. Maybe there is another utility? >>> >>> scrot >> >> I second this. scrot is what I use for screenshots, either full or >> partial. (Note: I don't use GNOME. Just fvwm.) >> >> > > For a brief, but horrible second I thought it was an expletive. So did I. But I tried it and it didn't quite work. I've now found out that my menu item is actually calling xfce4-screenshooter so that's probably why it doesn't work, and this works: gnome-screenshot -i
Screenshot with Gnome
I am trying to take a screenshot of a selected area. The Wiki here: https://wiki.debian.org/ScreenShots says I can use "take screenshot" from the menu. On my menu I have "screenshot" but it doesn't work (although I think it used to) it just displays a tiny box which I cannot make larger. Assuming the command line is: gnome-screenshot -a -d 20 I tried this but the mouse pointer immediately changes to a cross and I cannot change tasks, so all I can do is photo the terminal window. I think something is broken. Maybe there is another utility?
Re: Bug 895378 has been fixed on Ubuntu, will it get to Debian?
Richmond writes: > This bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895378 > > sky2: sky2: did not recover correctly after waking up from S3 > > seems to be fixed on Ubuntu here: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921 > > Will this fix get to Debian? I guess it will go up to kernel maintainers > and down again but I don't know how this works. Fixed with this kernel command line parameter: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash sky2.disable_msi=1" in file /etc/default/grub run: update-grub
Re: Editing the DNS with Network Manager Non Root
David Christensen writes: > On 5/15/22 06:53, Richmond wrote: >> David Christensen writes: >>> On 5/14/22 05:57, Richmond wrote: >>>> writes: >>>>> On Sat, May 14, 2022 at 10:50:46AM +0100, Richmond wrote: > >>>>>> Is there a debian package for this? : >>>>>> >>>>>> https://aur.archlinux.org/packages/xfce-polkit >>>>>> >>>>>> "A simple PolicyKit authentication agent for XFCE" > >>> My Debian 11 Xfce has the following, installed by >>> debian-11.3.0-amd64-netinst.iso: >>> >>> 2022-05-14 15:13:47 root@laalaa ~ # dpkg-query -l '*polkit*' >>> Desired=Unknown/Install/Remove/Purge/Hold >>> | >>> >>> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend >>> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name >>> Version Architecture Description >>> +++-===---=> >>> ii gir1.2-polkit-1.0 0.105-31+deb11u1 amd64 GObject >>> introspec> >>> un gir1.2-polkitagent-1.0 (no description a> ii >>> libpolkit-agent-1-0:amd64 0.105-31+deb11u1 amd64 PolicyKit Authent> ii >>> libpolkit-gobject-1-0:amd64 0.105-31+deb11u1 amd64 PolicyKit Authori> >>> un polkit-1-auth-agent (no description a> >> >> I got it working! that's the good news, the bad news is I am not sure >> how. I installed all the packages above (except polkit-1-auth-agent >> which seems to be an unreal package) but it still didn't work. Then I >> went into synaptic (which incidentally did not prompt for a password) >> and searched for xfce and found some packages relating to the panel >> which were not installed, nor part of the xfce meta package. Also I >> installed policykit-1-gnome which unfortunately doesn't come up on >> searches for polkit. I think this last one may be the culprit but not >> sure. >> Thanks for your help, and the others. > > > I would say "you are welcome", but it sounds like your system is in a > crumbling state. I would backup/ check-in, pull the OS drive, insert > a fresh OS drive, do a fresh install, and check-out/ restore/ > reconfigure. > > > David It isn't in a crumbling state, it just had a missing package. And this was probably due to an undeclared dependence.
Re: Editing the DNS with Network Manager Non Root
David Christensen writes: > On 5/14/22 05:57, Richmond wrote: >> writes: >> >>> On Sat, May 14, 2022 at 10:50:46AM +0100, Richmond wrote: >>>> Richmond writes: >>>> >>>>> David Christensen writes: >>> >>> [...] >>> >>>>> I expect there is some component of xfce4 which is supposed to >>>>> prompt for the root password. Perhaps it is not installed. I don't >>>>> know what it is called. >>>> >>>> Is there a debian package for this? : >>>> >>>> https://aur.archlinux.org/packages/xfce-polkit >>>> >>>> "A simple PolicyKit authentication agent for XFCE" >>> >>> There seem to be several options [1]. Gksu, some polkit thingy... >>> Blame my search engine if it fails ;-) >>> >>> >>> Cheers >>> >>> [1] https://forum.xfce.org/viewtopic.php?id=11728 Gksu is a frontend >> for su which a developer would apply to an app as I understand it. I >> am dealing with an applet, so I cannot edit its icon and put a >> wrapper in. Some polkit thingy would be xfce-polkit I think, but I >> found no debian package. > > > I do not see a package specifically for Xfce, but I do see one for > MATE: > > 2022-05-14 15:11:15 root@laalaa ~ # apt-cache search policy kit | sort > | grep polkit gir1.2-polkit-1.0 - GObject introspection data for > PolicyKit libpolkit-agent-1-0 - PolicyKit Authentication Agent API > libpolkit-agent-1-dev - PolicyKit Authentication Agent API - > development files libpolkit-gobject-1-0 - PolicyKit Authorization API > libpolkit-gobject-1-dev - PolicyKit Authorization API - development > files libpolkit-qt5-1-1 - PolicyKit-qt5-1 library libpolkit-qt5-1-dev > - PolicyKit-qt5-1 development files lxpolkit - LXDE PolicyKit > authentication agent mate-polkit - MATE authentication agent for > PolicyKit-1 mate-polkit-bin - MATE authentication agent for > PolicyKit-1 (executable wrapper script) mate-polkit-common - MATE > authentication agent for PolicyKit-1 (common files) polkit-kde-agent-1 > - KDE dialogs for PolicyKit ukui-polkit - UKUI authentication agent > for PolicyKit-1 > > > > My Debian 11 Xfce has the following, installed by > debian-11.3.0-amd64-netinst.iso: > > 2022-05-14 15:13:47 root@laalaa ~ # dpkg-query -l '*polkit*' > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name > Version Architecture Description > +++-===---=> > ii gir1.2-polkit-1.0 0.105-31+deb11u1 amd64 GObject > introspec> > un gir1.2-polkitagent-1.0 (no description a> ii > libpolkit-agent-1-0:amd64 0.105-31+deb11u1 amd64 PolicyKit Authent> ii > libpolkit-gobject-1-0:amd64 0.105-31+deb11u1 amd64 PolicyKit Authori> > un polkit-1-auth-agent (no description a> I got it working! that's the good news, the bad news is I am not sure how. I installed all the packages above (except polkit-1-auth-agent which seems to be an unreal package) but it still didn't work. Then I went into synaptic (which incidentally did not prompt for a password) and searched for xfce and found some packages relating to the panel which were not installed, nor part of the xfce meta package. Also I installed policykit-1-gnome which unfortunately doesn't come up on searches for polkit. I think this last one may be the culprit but not sure. Thanks for your help, and the others.
Re: Editing the DNS with Network Manager Non Root
writes: > On Sat, May 14, 2022 at 10:50:46AM +0100, Richmond wrote: >> Richmond writes: >> >> > David Christensen writes: > > [...] > >> > I expect there is some component of xfce4 which is supposed to prompt >> > for the root password. Perhaps it is not installed. I don't know what >> > it is called. >> >> Is there a debian package for this? : >> >> https://aur.archlinux.org/packages/xfce-polkit >> >> "A simple PolicyKit authentication agent for XFCE" > > There seem to be several options [1]. Gksu, some polkit thingy... > Blame my search engine if it fails ;-) > > > Cheers > > [1] https://forum.xfce.org/viewtopic.php?id=11728 Gksu is a frontend for su which a developer would apply to an app as I understand it. I am dealing with an applet, so I cannot edit its icon and put a wrapper in. Some polkit thingy would be xfce-polkit I think, but I found no debian package.
Re: Editing the DNS with Network Manager Non Root
Richmond writes: > David Christensen writes: > >> On 5/13/22 09:02, Richmond wrote: >>> David Christensen writes: >>>> On 5/12/22 07:17, Richmond wrote: >>>>> David Christensen writes: >>>>>> On 5/11/22 06:55, Richmond wrote: >>>>>>> I have a network manager applet on my xfce4 desktop. I am logged >>>>>>> in as a non root user, and I can select edit connections and >>>>>>> change the IPv4 settings to DHCP address only and then put in a >>>>>>> DNS, then save. If I look at /etc/resolv.conf though nothing has >>>>>>> changed. Restarting networking or rebooting makes no >>>>>>> difference. Perhaps this menu option should only appear for >>>>>>> root, or should cause an error message for non root users? >> >>>> If I choose "Automatic (DHCP) addresses only", the labels for the >>>> second and third settings change. Putting in some test data: >>>> >>>> Additional static addresses -> Add: Address -> 192.168.123.45 >>>>Netmask -> 255.255.255.0 Gateway -> 192.168.5.1 >>>> >>>> DNS servers -> 192.168.123.45,192.168.123.67 >>>> >>>> Search domains -> frunobulax.org >>>> >>>> DHCP client ID -> empty >>>> >>>> Require IPv4 addressing for this connection to complete -> >>>> unchecked >>>> >>>> >>>> I then click "Save". >>>> >>>> >>>> I then enter the root password in the pop-up that opens. >>>> >>>> >>>> I then close the "Network Connections" window and reboot. >>>> >>>> 2022-05-12 16:10:25 dpchrist@laalaa ~ $ ls -l /etc/resolv.conf >>>> -rw-r--r-- 1 root root 104 May 12 16:09 /etc/resolv.conf >>>> >>>> 2022-05-12 16:10:34 dpchrist@laalaa ~ $ cat /etc/resolv.conf # >>>> Generated by NetworkManager search frunobulax.org nameserver >>>> 192.168.123.45 nameserver 192.168.123.67 >>>> >>>> >>>> Is this the results you expect? >> >>> I didn't put in a search domain, netmask, or gateway. >> >> >> Put them in and try again. Without crawling the code, we have no >> idea what actually matters. >> >> >>> I didn't get prompted for root access. Perhaps that is the problem? >> >> >> I would suspect it indicates that Network Manager does not think your >> network settings changed. >> >> >>> stat /etc/resolv.conf shows that the file has been updated but its >>> content doesn't change. >> >> >> My /etc/resolv.conf did not change after running Network Manager; it >> changed after rebooting. (Is the former a bug or a feature?) >> >> >> What happens if you create a new connection and use the Manual >> method? >> >> >> If all else fails -- backup, pull the OS disk, insert a blank disk, >> do a fresh install, and restore. Keep meticulous records. Use a >> version control system. Learn a scripting language and automate >> sysadmin chores. >> >> >> David > > I switched to the mate desktop, and the procedure works, i.e. it > prompts for a root password and updates resolv.conf, after > disconnecting and reconnecting the network. > > I expect there is some component of xfce4 which is supposed to prompt > for the root password. Perhaps it is not installed. I don't know what > it is called. Is there a debian package for this? : https://aur.archlinux.org/packages/xfce-polkit "A simple PolicyKit authentication agent for XFCE"
Re: Editing the DNS with Network Manager Non Root
David Christensen writes: > On 5/13/22 09:02, Richmond wrote: >> David Christensen writes: >>> On 5/12/22 07:17, Richmond wrote: >>>> David Christensen writes: >>>>> On 5/11/22 06:55, Richmond wrote: >>>>>> I have a network manager applet on my xfce4 desktop. I am logged in as a >>>>>> non root user, and I can select edit connections and change the IPv4 >>>>>> settings to DHCP address only and then put in a DNS, then save. If I >>>>>> look at /etc/resolv.conf though nothing has changed. Restarting >>>>>> networking or rebooting makes no difference. Perhaps this menu option >>>>>> should only appear for root, or should cause an error message for non >>>>>> root users? > >>> If I choose "Automatic (DHCP) addresses only", the labels for the >>> second and third settings change. Putting in some test data: >>> >>> Additional static addresses -> Add: >>> Address -> 192.168.123.45 >>> Netmask -> 255.255.255.0 >>> Gateway -> 192.168.5.1 >>> >>> DNS servers -> 192.168.123.45,192.168.123.67 >>> >>> Search domains -> frunobulax.org >>> >>> DHCP client ID -> empty >>> >>> Require IPv4 addressing for this connection to complete -> unchecked >>> >>> >>> I then click "Save". >>> >>> >>> I then enter the root password in the pop-up that opens. >>> >>> >>> I then close the "Network Connections" window and reboot. >>> >>> 2022-05-12 16:10:25 dpchrist@laalaa ~ >>> $ ls -l /etc/resolv.conf >>> -rw-r--r-- 1 root root 104 May 12 16:09 /etc/resolv.conf >>> >>> 2022-05-12 16:10:34 dpchrist@laalaa ~ >>> $ cat /etc/resolv.conf >>> # Generated by NetworkManager >>> search frunobulax.org >>> nameserver 192.168.123.45 >>> nameserver 192.168.123.67 >>> >>> >>> Is this the results you expect? > >> I didn't put in a search domain, netmask, or gateway. > > > Put them in and try again. Without crawling the code, we have no idea > what actually matters. > > >> I didn't get prompted for root access. Perhaps that is the problem? > > > I would suspect it indicates that Network Manager does not think your > network settings changed. > > >> stat /etc/resolv.conf shows that the file has been updated but its >> content doesn't change. > > > My /etc/resolv.conf did not change after running Network Manager; it > changed after rebooting. (Is the former a bug or a feature?) > > > What happens if you create a new connection and use the Manual method? > > > If all else fails -- backup, pull the OS disk, insert a blank disk, do > a fresh install, and restore. Keep meticulous records. Use a version > control system. Learn a scripting language and automate sysadmin chores. > > > David I switched to the mate desktop, and the procedure works, i.e. it prompts for a root password and updates resolv.conf, after disconnecting and reconnecting the network. I expect there is some component of xfce4 which is supposed to prompt for the root password. Perhaps it is not installed. I don't know what it is called.
Re: Editing the DNS with Network Manager Non Root
David Christensen writes:
> On 5/12/22 07:17, Richmond wrote:
>> David Christensen writes:
>>
>>> On 5/11/22 06:55, Richmond wrote:
>>>> I have a network manager applet on my xfce4 desktop. I am logged in as a
>>>> non root user, and I can select edit connections and change the IPv4
>>>> settings to DHCP address only and then put in a DNS, then save. If I
>>>> look at /etc/resolv.conf though nothing has changed. Restarting
>>>> networking or rebooting makes no difference. Perhaps this menu option
>>>> should only appear for root, or should cause an error message for non
>>>> root users?
>>>
>>>
>>> I typically need to enter the root password whenever I make changes
>>> via the Xfce NetworkManager Applet.
>>>
>>>
>>> Please run and post:
>>>
>>> $ cat /etc/debian_version ; uname -a
>>>
>>> $ ls -l /etc/resolv.conf
>>>
>>> $ cat /etc/resolv.conf
>>>
>>>
>>> David
>> 11.3
>> Linux marvin 5.16.0-0.bpo.3-amd64 #1 SMP PREEMPT Debian
>> 5.16.11-1~bpo11+1 (2022-03-02) x86_64 GNU/Linux
>> -rw-r--r-- 1 root root 79 May 12 15:15 /etc/resolv.conf
>> # Generated by NetworkManager
>> nameserver 192.168.1.1
>> nameserver fe80::1%enp2s0
>> That address 192.168.1.1 is not what I usually have, I was
>> experimenting, trying to find out if my router is vulnerable to the DNS
>> spoofing reported recently.
>
>
> The date and time on resolve.conf show that it is current.
Yes, it is very odd. I have just gone through this process again, and it
does update the timestamp, but does not apply changes...
>
>
> "nameserver 192.168.1.1" looks plausible.
I put it in there, it is the address of my router, the gateway, which
responds to DNS queries but merely passes them to the address it has
obtained through DHCP. The only way I found to get an address into
resolv (other than editing it obviously) was by logging into the desktop
as root, which I rarely do.
>
>
> I am using a Debian 11 desktop with Xfce:
>
> 2022-05-12 15:58:09 dpchrist@laalaa ~
> $ echo "'$PS1'"
> '\n\D{%Y-%m-%d %H:%M:%S} \u@\h \w\n\$ '
>
> 2022-05-12 15:58:19 dpchrist@laalaa ~
> $ cat /etc/debian_version ; uname -a
> 11.3
> Linux laalaa 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29)
> x86_64 GNU/Linux
>
> 2022-05-12 15:58:27 dpchrist@laalaa ~
> $ ls -l /etc/resolv.conf
> -rw-r--r-- 1 root root 83 May 12 11:06 /etc/resolv.conf
>
> 2022-05-12 15:58:33 dpchrist@laalaa ~
> $ cat /etc/resolv.conf
> # Generated by NetworkManager
> search tracy.holgerdanske.com
> nameserver 192.168.5.1
>
>
> If I right-click the Xfce NetworkManager Applet and choose Edit
> Connections, I get a window "Network Connections":
>
> Ethernet
>Wired connection 1
>
> If I double-click "Wired connection 1", I get a windows "Editing Wired
> connection 1". If I select the tab IPv4 Settings, there is a
> drop-down list labeled "Methods".
>
> - It is currently set to "Automatic (DHCP)". The remaining settings are:
>
> Additional static addresses -> empty
>
> Additional DNS servers -> empty
>
> Additional Search domains -> empty
>
> DHCP client ID -> empty
>
> Require IPv4 addressing for this connection to complete -> unchecked
>
>
> If I choose "Automatic (DHCP) addresses only", the labels for the
> second and third settings change. Putting in some test data:
>
> Additional static addresses -> Add:
> Address -> 192.168.123.45
> Netmask -> 255.255.255.0
> Gateway -> 192.168.5.1
>
> DNS servers -> 192.168.123.45,192.168.123.67
>
> Search domains -> frunobulax.org
>
> DHCP client ID -> empty
>
> Require IPv4 addressing for this connection to complete -> unchecked
>
>
> I then click "Save".
>
>
> I then enter the root password in the pop-up that opens.
>
>
> I then close the "Network Connections" window and reboot.
>
> 2022-05-12 16:10:25 dpchrist@laalaa ~
> $ ls -l /etc/resolv.conf
> -rw-r--r-- 1 root root 104 May 12 16:09 /etc/resolv.conf
>
> 2022-05-12 16:10:34 dpchrist@laalaa ~
> $ cat /etc/resolv.conf
> # Generated by NetworkManager
> search frunobulax.org
> nameserver 192.168.123.45
> nameserver 192.168.123.67
>
>
> Is this the results you expect?
>
>
> David
I didn't put in a search domain, netmask, or gateway.
I didn't get prompted for root access. Perhaps that is the problem?
stat /etc/resolv.conf shows that the file has been updated but its
content doesn't change.
Re: Editing the DNS with Network Manager Non Root
David Christensen writes: > On 5/11/22 06:55, Richmond wrote: >> I have a network manager applet on my xfce4 desktop. I am logged in as a >> non root user, and I can select edit connections and change the IPv4 >> settings to DHCP address only and then put in a DNS, then save. If I >> look at /etc/resolv.conf though nothing has changed. Restarting >> networking or rebooting makes no difference. Perhaps this menu option >> should only appear for root, or should cause an error message for non >> root users? > > > I typically need to enter the root password whenever I make changes > via the Xfce NetworkManager Applet. > > > Please run and post: > > $ cat /etc/debian_version ; uname -a > > $ ls -l /etc/resolv.conf > > $ cat /etc/resolv.conf > > > David 11.3 Linux marvin 5.16.0-0.bpo.3-amd64 #1 SMP PREEMPT Debian 5.16.11-1~bpo11+1 (2022-03-02) x86_64 GNU/Linux -rw-r--r-- 1 root root 79 May 12 15:15 /etc/resolv.conf # Generated by NetworkManager nameserver 192.168.1.1 nameserver fe80::1%enp2s0 That address 192.168.1.1 is not what I usually have, I was experimenting, trying to find out if my router is vulnerable to the DNS spoofing reported recently.
Editing the DNS with Network Manager Non Root
I have a network manager applet on my xfce4 desktop. I am logged in as a non root user, and I can select edit connections and change the IPv4 settings to DHCP address only and then put in a DNS, then save. If I look at /etc/resolv.conf though nothing has changed. Restarting networking or rebooting makes no difference. Perhaps this menu option should only appear for root, or should cause an error message for non root users?
Bug 895378 has been fixed on Ubuntu, will it get to Debian?
This bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895378 sky2: sky2: did not recover correctly after waking up from S3 seems to be fixed on Ubuntu here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921 Will this fix get to Debian? I guess it will go up to kernel maintainers and down again but I don't know how this works.
Re: xfce suspend not working
Richmond writes: > I was using MATE but I installed xfce. When I select the suspend button > a message appears saying suspend in 30 seconds. If I click suspend the > screen locks. If I wait the system does not suspend. If I log in again > an error message says suspend failed timeout reached. > > There seem to be conflicting settings available for example in power > management and in session management for lock before suspend. I tried > using slim instead of lightdm but this has removed the suspend options. > > What I want is for the system to suspend to ram if it is left > unattended, and to suspend to ram when I request it to do so, and in > both cases to lock the screen so that it is locked on return from > suspend. How do I do this with XFCE (4?) ? I think I have fixed it. It was caused by the mate-screensaver dialog running.
xfce suspend not working
I was using MATE but I installed xfce. When I select the suspend button a message appears saying suspend in 30 seconds. If I click suspend the screen locks. If I wait the system does not suspend. If I log in again an error message says suspend failed timeout reached. There seem to be conflicting settings available for example in power management and in session management for lock before suspend. I tried using slim instead of lightdm but this has removed the suspend options. What I want is for the system to suspend to ram if it is left unattended, and to suspend to ram when I request it to do so, and in both cases to lock the screen so that it is locked on return from suspend. How do I do this with XFCE (4?) ?
Re: linux kernel and nvidia - never ending story
didier gaumet writes: > Le mardi 08 mars 2022 à 12:12 +0000, Richmond a écrit : > [...] >> I don't know if there are >> any distributions other than debian which still support kernel 4. > > A RHEL 8 clone (Almalinux, Rocky Linux...) should do: kernel is blocked > to 4.18 until EOL in 2029 (end of full support may 2024, other support > unspecified right now) Thanks. It looks like there are plenty of distros I have never heard of to choose from: https://distrowatch.com/search.php?pkg=linux=similar=4.18=InLatest#pkgsearch https://distrowatch.com/search.php?pkg=linux=similar=4.19=InLatest#pkgsearch But it will be difficult because not all the ones I have tried in the past have managed to cope with the additional tv-out feature that I want to use with nvidia-settings. Now that I have it working I fear to change it.
Re: Problems with custom install of MATE
Richard Owlett writes: > As I have a very low data cap and wish to avoid some "recommended" > components I have done: > 1. a text mode install [including "standard utilities"] using >debian-11.2.0-amd64-netinst.iso . > 2. apt-get --no-install-recommends install mate-desktop-environment > 3. apt-get install xinit > 4. apt-get --no-install-recommends install xorg gparted synaptic pluma > > Between those steps were searches/fixes for some things that didn't > run as expected. > > Current questions/problems include: > 1. Why do I have to manually run startx at each boot? > 2. Although menu entries for gparted and pluma appear as expected, there >appears to be no way to launch synaptic. > 3. Although connected to internet [i.e. apt-get runs correctly], the >appropriate icon does not appear on MATE's taskbar. > 4. I'll be installing SeaMonkey but have forgotten how to have it appear >on appropriate Applications sub-menu. > > I've done it all before but can't find my references. > Help please. > TIA 1. Probably you don't have a display manager. Mate uses light display manager, and it is configured here: /etc/systemd/system/display-manager.service But there is a script or procedure for configuring it. Probably just install lightdm.
Re: linux kernel and nvidia - never ending story
Hans writes: > Dear list, > > how find the correct words, without being upset or stepping on > someones feet. But I believe, debian hates Nvidia, and debian does > not want, to use Nvidia. > > I am now for a long time using debian and also using nvidia graphic > cards for almost the same long time. > > But whenever debian ships a new kernel version, the proprietrary > nvidia kernel modules can not be built. If lucky, there is a patch for > it after months. > > Yes, modern Nvidia cards are supported, but using an older notebook > you can not change the graphics card. > > But this is not a problem of Nvidia, not IMO it is a problem with the > kernel developers. Suddenly, with a kernel the gcc was updated, oh, > now the kernel module does not want it any more. Wtf? Or, with the new > kernel, the kernel module crashes during building, but builds > perfectly at the older kernel. > > And suddenly the kernel modul of nvidia disappears completely from the > repo, problems solved? Get lost, you foolish users with old hardware, > buy new hardware! What??? > > Oh, and when someone says: Hey, use the nouveau driver, then tell him, > nouveau is not working. > > I have several older notebooks, that my customers use. They worked > perfectly with the proprietrary driver from Nvidia. But after update > to bullseye, it was hardly get them running again. And why? They have > an old graphics card in their notebooks, and they use Nvidia cards, > specially the legacy 340xx. > > But: > > 1. no problem, Install nvidia kernel 340xx, oh no, it is no more in > the repo, but > > 2. no problem, hey, use nouveau, oh no, nouveau crashes and freezes X, > but > > 3. no problem, build just the downloaded 340xx from buster, oh no, > does not build, wrong gcc installed, gcc to new, but > > 4. no problem, just downgrade gcc to the old one, oh no, many other > packages need to be deinstalled, too, but > > 5. no problem, just do it, oh no, does not build with the latest > kernel, but > > 6. no problem, just downgrade the kernel, too, oh no, no kernel from > bullseye is working, but > > 7. no problem, just reactivate buster and install latest kernel from > buster, and oh yes, > > 8. old kernel from buster let build 340xx, but oh no, kernel old... > > Well, I and these procedures are now accompanies me since years. New > kernel, and building fails. Youu feel lost, you feel anger, can you > believe me? > > In earlier times, debian potato and so, there were always prebuild > kernel modules for graphic cards, Nvidia or AMD or whatever. Today > these are gone, and people with older cards are lost. IMO here debian > lost a lots of its quality. > > I thought a long time, if I should write this, and maybe I have not > found the correct words. I do not want to harsh anyone or attack > anyone, you know what I mean. > > But I felt in my heart, I had to say it. > > Please apologize, if someone is feeling agry about me now, this was > not intended. And thanks for reading this. > I am in the same position as you. One of my laptops has an old Nvidia card, so it is stuck on debian 10. But this isn't unique to debian, it also applies to OpenSUSE which I also have on there dual booting, and that cannot be upgraded either. It has to stay on the version 4 kernel, and from what I read at the time this is because Nvidia will not support later kernels 5+ . So it is ok until long term support ends, but then I don't know what to do. Nouveau is unstable. I don't know if there are any distributions other than debian which still support kernel 4.
Re: Google smtp and pop
Marc Auslander writes: > Google has now said they are pulling the plug on userid/password > authentication for apps. > > I use fetchmail and exim4 to get and send mail. Neither, AFAIK, > supports OAUTH2. I'm also still on stretch but will update if I have > to. > > So what suggestions does anyone have for dealing with OAUTH2 access to > gmail? It doesn't say that. Signing into your google account is not the same as signing into a pop3/smtp/imap server. You will be able to use app passwords for that. https://support.google.com/accounts/answer/6010255
Re: a stop job is running for user manager
David Wright writes: > On Fri 18 Feb 2022 at 21:13:16 (+), Richmond wrote: >> Махно writes: >> > 2022-02-18, pn, 03:28 David Wright rašė: >> >> On Thu 17 Feb 2022 at 13:44:46 (+), Richmond wrote: >> >> > David Wright writes: >> >> > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> >> > >> Since upgrading to Debian 11 I sometimes see "a stop job is running >> >> > >> for >> >> > >> user manager..." on shutdown and it waits 90 seconds. The last >> >> > >> comment >> >> > >> in this thread says "Installing systemd from backsports solved this >> >> > >> issue." >> >> > >> >> >> > >> https://forums.debian.net/viewtopic.php?t=150080 >> >> > >> >> >> > >> I guess that means a backport from testing. Is that a good idea? >> >> > > >> >> > > No, it's not. >> >> > > >> >> > > testing: 250.3-2 >> >> > > >> >> > > BULLSEYE backports: 250.3-2~bpo11+1 >> >> > > >> >> > > The latter is lovingly crafted to suit your installed libraries. >> >> > > The former depends on bookworm/testing's libraries. >> >> > >> >> > Thanks, I see my mistake, I thought bullseye-backports meant backports >> >> > from bullseye, but it means *to* bullseye. However when I tried it, apt >> >> > says it will remove 92 packages which doesn't sound right to me. Is it >> >> > supposed to do that? I had to include libsystemd0 for dependencies. >> >> > >> >> > sudo apt install libsystemd0/bullseye-backports >> >> > systemd/bullseye-backports >> >> > >> >> > The following packages will be upgraded: >> >> > libsystemd0 systemd >> >> > 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. >> >> > Need to get 5,167 kB of archives. >> >> > After this operation, 383 MB disk space will be freed. >> >> > Do you want to continue? [Y/n] n >> >> > Abort. >> >> >> >> For me, the effect is very much smaller, and I don't think I'd miss >> >> most of what it wants to remove. The difference may be because you run >> >> a DE and I don't. (I've made no attempt to analyse the output below.) >> >> >> >> The obvious alternative is either put up with the delay, or research >> >> what might be causing it. There's a link near the top of the page you >> >> referenced, with discussions that might help, though bear in mind that >> >> shortening the timeout or hammering the three finger salute aren't >> >> solutions. >> >> >> >> Perhaps backports isn't really a solution, either. There's no >> >> explanation or justification given by ddebbb. >> >> >> >> $ apt-get -s install systemd/bullseye-backports >> >> [ … ] >> >> 2 upgraded, 1 newly installed, 9 to remove and 0 not upgraded. >> >> [ … ] >> >> $ >> >> > Hello! I would suggest that you report this issue to Debian BTS by >> > using the reportbug program. Also, i think you should wait for a >> > person, responsible for the maintenance of this package and wait for >> > an answer. >> >> Perhaps. Yesterday I found a site that suggested removing entries from >> ~/.config/autostart/ >> >> There were a few in there for applications I no longer have installed, >> so I removed them, and I am monitoring to see if I see the shutdown >> delay again. It maybe relates to a gnome bug which was not fixed in >> Mate. It is hard to tell from journalctl which error if any relates to >> the delay. > > That seems like a step in the right direction. A quick question: > do you logout before you shutdown or not? It might be possible to > observe whether the delay is during logoff or shutdown. > > (It's not directly relevant, but when running bullseye in 512MB, > it helps to kill the browser, terminate X, logout, and shutdown > in turn, because the agressive parallelism of systemd works against > you with such limited memory.) > That autostart removal didn't work. So far this problem has occured only when shutting down an open session, although I don't think there necessarily needs to be any application open. Next I will try what you say (logoff) and see if there is any delay. Another option is to use startx rather than a display manager, although I think I may have tried that. Another option is to use a different, or no, desktop env. and try to close in by the process of elimination, Dr Watson.
Re: a stop job is running for user manager
Махно writes: > Hello! I would suggest that you report this issue to Debian BTS by > using the reportbug program. Also, i think you should wait for a > person, responsible for the maintenance of this package and wait for > an answer. Perhaps. Yesterday I found a site that suggested removing entries from ~/.config/autostart/ There were a few in there for applications I no longer have installed, so I removed them, and I am monitoring to see if I see the shutdown delay again. It maybe relates to a gnome bug which was not fixed in Mate. It is hard to tell from journalctl which error if any relates to the delay. > > 2022-02-18, pn, 03:28 David Wright rašė: >> >> On Thu 17 Feb 2022 at 13:44:46 (+), Richmond wrote: >> > David Wright writes: >> > > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> > >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> > >> user manager..." on shutdown and it waits 90 seconds. The last comment >> > >> in this thread says "Installing systemd from backsports solved this >> > >> issue." >> > >> >> > >> https://forums.debian.net/viewtopic.php?t=150080 >> > >> >> > >> I guess that means a backport from testing. Is that a good idea? >> > > >> > > No, it's not. >> > > >> > > testing: 250.3-2 >> > > >> > > BULLSEYE backports: 250.3-2~bpo11+1 >> > > >> > > The latter is lovingly crafted to suit your installed libraries. >> > > The former depends on bookworm/testing's libraries. >> > >> > Thanks, I see my mistake, I thought bullseye-backports meant backports >> > from bullseye, but it means *to* bullseye. However when I tried it, apt >> > says it will remove 92 packages which doesn't sound right to me. Is it >> > supposed to do that? I had to include libsystemd0 for dependencies. >> > >> > sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports >> > >> > The following packages will be upgraded: >> > libsystemd0 systemd >> > 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. >> > Need to get 5,167 kB of archives. >> > After this operation, 383 MB disk space will be freed. >> > Do you want to continue? [Y/n] n >> > Abort. >> >> For me, the effect is very much smaller, and I don't think I'd miss >> most of what it wants to remove. The difference may be because you run >> a DE and I don't. (I've made no attempt to analyse the output below.) >> >> The obvious alternative is either put up with the delay, or research >> what might be causing it. There's a link near the top of the page you >> referenced, with discussions that might help, though bear in mind that >> shortening the timeout or hammering the three finger salute aren't solutions. >> >> Perhaps backports isn't really a solution, either. There's no >> explanation or justification given by ddebbb. >> >> $ apt-get -s install systemd/bullseye-backports >> NOTE: This is only a simulation! >> apt-get needs root privileges for real execution. >> Keep also in mind that locking is deactivated, >> so don't depend on the relevance to the real current situation! >> Reading package lists... Done >> Building dependency tree... Done >> Reading state information... Done >> Selected version '250.3-2~bpo11+1' (Debian Backports:bullseye-backports >> [amd64]) for 'systemd' >> Selected version '250.3-2~bpo11+1' (Debian Backports:bullseye-backports >> [amd64]) for 'libsystemd0' because of 'systemd' >> The following packages were automatically installed and are no longer >> required: >> colord-data gparted-common libcolorhug2 libgusb2 libjim0.79 libmbim-glib4 >> libmbim-proxy libpipewire-0.3-0 >> libpipewire-0.3-modules libqmi-glib5 libqmi-proxy libspa-0.2-modules >> pipewire pipewire-bin usb-modeswitch >> usb-modeswitch-data xdg-desktop-portal >> Use 'apt autoremove' to remove them. >> The following additional packages will be installed: >> dbus-x11 libsystemd0 >> Suggested packages: >> systemd-container libtss2-esys-3.0.2-0 libtss2-mu0 libtss2-rc0 policykit-1 >> Recommended packages: >> systemd-timesyncd | time-daemon >> The following packages will be REMOVED: >> colord dbus-user-session gparted libnss-systemd libpam-systemd >> modemmanager policykit-1 systemd-timesyncd >> xdg-desktop-portal-gtk >> The following NEW packages will be installed: >> d
Re: a stop job is running for user manager
David Wright writes: > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> user manager..." on shutdown and it waits 90 seconds. The last comment >> in this thread says "Installing systemd from backsports solved this issue." >> >> https://forums.debian.net/viewtopic.php?t=150080 >> >> I guess that means a backport from testing. Is that a good idea? > > No, it's not. > > testing: 250.3-2 > > BULLSEYE backports: 250.3-2~bpo11+1 > > The latter is lovingly crafted to suit your installed libraries. > The former depends on bookworm/testing's libraries. > > Cheers, > David. Here are the packages it says it wants to remove. Note: mate-desktop-environment: The following packages will be REMOVED: baloo-kf5 dbus-user-session dolphin gnome-software gstreamer1.0-plugins-good:i386 gufw kaccounts-providers kactivitymanagerd kde-cli-tools kdeconnect keditbookmarks kinit kio kio-extras kpackagelauncherqml libasound2-plugins:i386 libavahi-client3:i386 libcups2:i386 libdbus-1-3:i386 libfaudio0:i386 libkf5auth-dev libkf5auth5 libkf5authcore5 libkf5baloowidgets-bin libkf5baloowidgets5 libkf5bookmarks-dev libkf5bookmarks5 libkf5configwidgets-dev libkf5configwidgets5 libkf5declarative5 libkf5iconthemes-bin libkf5iconthemes-dev libkf5iconthemes5 libkf5kcmutils-dev libkf5kcmutils5 libkf5kio-dev libkf5kiocore5 libkf5kiofilewidgets5 libkf5kiogui5 libkf5kiowidgets5 libkf5newstuff5 libkf5newstuffcore5 libkf5notifyconfig-dev libkf5notifyconfig5 libkf5parts-plugins libkf5parts5 libkf5plasma5 libkf5plasmaquick5 libkf5purpose-bin libkf5purpose-dev libkf5purpose5 libkf5quickaddons5 libkf5textwidgets5 libkf5wallet-bin libkf5xmlgui-dev libkf5xmlgui5 libnss-systemd libpam-systemd libpcap0.8:i386 libpolkit-qt5-1-1 libpulse0:i386 libsane1:i386 libsdl2-2.0-0:i386 libsystemd0:i386 libwine:i386 lightdm mate-applet-brisk-menu mate-applets mate-control-center mate-desktop-environment mate-desktop-environment-core mate-panel mate-polkit mate-power-manager mate-settings-daemon modemmanager network-manager network-manager-gnome packagekit packagekit-tools plasma-framework policykit-1 qml-module-org-kde-kconfig qml-module-org-kde-kquickcontrols qml-module-org-kde-kquickcontrolsaddons qml-module-org-kde-newstuff qml-module-org-kde-purpose rtkit synaptic systemd-timesyncd task-mate-desktop wine32:i386
Re: a stop job is running for user manager
David Wright writes: > On Thu 17 Feb 2022 at 01:00:30 (+), Richmond wrote: >> Since upgrading to Debian 11 I sometimes see "a stop job is running for >> user manager..." on shutdown and it waits 90 seconds. The last comment >> in this thread says "Installing systemd from backsports solved this issue." >> >> https://forums.debian.net/viewtopic.php?t=150080 >> >> I guess that means a backport from testing. Is that a good idea? > > No, it's not. > > testing: 250.3-2 > > BULLSEYE backports: 250.3-2~bpo11+1 > > The latter is lovingly crafted to suit your installed libraries. > The former depends on bookworm/testing's libraries. > Thanks, I see my mistake, I thought bullseye-backports meant backports from bullseye, but it means *to* bullseye. However when I tried it, apt says it will remove 92 packages which doesn't sound right to me. Is it supposed to do that? I had to include libsystemd0 for dependencies. sudo apt install libsystemd0/bullseye-backports systemd/bullseye-backports The following packages will be upgraded: libsystemd0 systemd 2 upgraded, 0 newly installed, 92 to remove and 0 not upgraded. Need to get 5,167 kB of archives. After this operation, 383 MB disk space will be freed. Do you want to continue? [Y/n] n Abort.
Re: Chromium security updates
Richmond writes: > Now trying: > > gn gen out/Default "--args=is_debug=false symbol_level=0 > blink_symbol_level=0 v8_symbol_level=0 is_official_build=true > chrome_pgo_phase = 0" > I've built this version and it is working well. As the problem with chromium is caused by the debian build tools, perhaps it can be provided from the stable version build as an appimage? Or perhaps it can be built without the build tools and just provided for selected architecture?
Re: Chromium security updates
Christian Britz writes: > On 2022-01-24 12:44 UTC+0100, Richmond wrote: > >>> I've built Version 100.0.4845.0 (Developer Build) (64-bit) and it seems >>> to be working fine here on debian 10. >> >> Not OK actually, it is very slow. > > The reason are probably enabled debug options. > > Personally I am not satisfied with the security support for any browser > included in Debian, I just use original Firefox and Chrome (and > Thunderbird), which are easy to install. If you don't like/trust Google > but want to use a Chromium based browser, you might consider using > ungoogled-chromium. I used: gn gen out/Default "--args=is_debug=false symbol_level=0 blink_symbol_level=0 v8_symbol_level=0" But it seems slow on tweetdeck with high cpu usage.
Re: Chromium security updates
Richmond writes: > Salvatore Bonaccorso writes: > >> Hi, >> >> On Fri, Jan 21, 2022 at 07:20:26PM +0100, Andrei POPESCU wrote: >>> On Jo, 20 ian 22, 00:08:52, Richmond wrote: >>> > I see debian 10's chromium is currently on version 90.0.4430.212 >>> > (Developer Build), whereas google-chrome is on Version 97.0.4692.99 >>> > (Official Build) (64-bit). Does that mean it is out of date and has >>> > security vulnerabilities? >>> > >>> > https://chromereleases.googleblog.com/search/label/Stable%20updates >>> >>> The plan was: >>> >>> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#browser-security >>> >>> Unfortunately both Firefox and Chromium proved to be much more of a >>> challenge then expected at the time of releasing Debian 10 "buster" (now >>> oldstable). >>> >>> Firefox appears to be in slightly better shape (updated version >>> available in bullseye/stable, still pending for buster/oldstable). >> >> In fact support for chromium in oldstable has been discontinued, see >> https://lists.debian.org/debian-security-announce/2022/msg00012.html . >> >> Regards, >> Salvatore > > I've built Version 100.0.4845.0 (Developer Build) (64-bit) and it seems > to be working fine here on debian 10. Not OK actually, it is very slow.
Re: Chromium security updates
Salvatore Bonaccorso writes: > Hi, > > On Fri, Jan 21, 2022 at 07:20:26PM +0100, Andrei POPESCU wrote: >> On Jo, 20 ian 22, 00:08:52, Richmond wrote: >> > I see debian 10's chromium is currently on version 90.0.4430.212 >> > (Developer Build), whereas google-chrome is on Version 97.0.4692.99 >> > (Official Build) (64-bit). Does that mean it is out of date and has >> > security vulnerabilities? >> > >> > https://chromereleases.googleblog.com/search/label/Stable%20updates >> >> The plan was: >> >> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#browser-security >> >> Unfortunately both Firefox and Chromium proved to be much more of a >> challenge then expected at the time of releasing Debian 10 "buster" (now >> oldstable). >> >> Firefox appears to be in slightly better shape (updated version >> available in bullseye/stable, still pending for buster/oldstable). > > In fact support for chromium in oldstable has been discontinued, see > https://lists.debian.org/debian-security-announce/2022/msg00012.html . > > Regards, > Salvatore I've built Version 100.0.4845.0 (Developer Build) (64-bit) and it seems to be working fine here on debian 10.
Re: Chromium security updates
The Wanderer writes: > On 2022-01-19 at 19:08, Richmond wrote: > >> I see debian 10's chromium is currently on version 90.0.4430.212 >> (Developer Build), whereas google-chrome is on Version 97.0.4692.99 >> (Official Build) (64-bit). Does that mean it is out of date and has >> security vulnerabilities? > > Roughly speaking, yes, but there's background and context here. > > First up: the version of Chromium in Debian stable, like that of every > other package in stable, will remain unchanged until such a time as a > new Debian point release is made. However, there may be updated versions > made available in stable-backports in the meantime. (I do not use > stable-backports myself, so anyone who knows better than I do may feel > free to clarify, amplify, or correct on this.) > > Recent-ish-ly, there was discussion about dropping Chromium from Debian > entirely (except for the version in stable, which would remain unchanged > and quickly become stale), because the packagers couldn't keep up with > updating the packaged version against the upstream releases, and as such > vulnerable versions were being shipped for too long anyway. If I recall > correctly and my archives are accurate, the chromium package actually > *was* dropped from Debian testing at that point, with the most recent > release before the drop having been 93.0.4577.82. > > I followed parts of that discussion, and from what I can tell, the > outcome of it was that more people stepped forward and took up > maintenance of the Debian packages for Chromium. Version 97.0.4692.71 is > now in Debian testing, and I understand that a stable-backports build > was pending, as of the last word in the part of the discussion I was > following (about a week ago now); that version, or a successor, should > make it into an updated version of Debian stable at some point. > > That may not help very much for now, but it should give hope for the > future on this front, as well as bring relief that at least things > aren't going to be ending up getting that much worse. Thanks. I have belatedly discovered the wiki https://wiki.debian.org/Chromium which suggests https://wiki.debian.org/ungoogled-chromium which is also out of date. :)
Chromium security updates
I see debian 10's chromium is currently on version 90.0.4430.212 (Developer Build), whereas google-chrome is on Version 97.0.4692.99 (Official Build) (64-bit). Does that mean it is out of date and has security vulnerabilities? https://chromereleases.googleblog.com/search/label/Stable%20updates Debian 10 is supported until 2024. https://wiki.debian.org/LTS
Re: cooperative.co.uk has address 127.0.0.1
Greg Wooledge writes: > On Tue, Jan 18, 2022 at 01:19:58PM +0000, Richmond wrote: >> Why do I see this? >> >> host cooperative.co.uk >> cooperative.co.uk has address 127.0.0.1 > > Because whoever set up that DNS zone made an error. > > unicorn:~$ host cooperative.co.uk > cooperative.co.uk has address 127.0.0.1 Thanks for your reply and others. It doesn't seem like an appropriate use of the address to me, and I stared in disbelief when I saw it, thinking something had gone wrong. Even, for example, example.com has its own ip address. Or perhaps they should have returned an error like an.invalid. I guess they want to discourage its use but also prevent anyone grabbing it.
Re: Usenet access.
pe...@easthope.ca writes: > Hi, > > Can anyone suggest an alternative to Google Groups for access to > sci.electronics.repair. I'd be happy to pay a small subscription for > access without tedious complications. > > Thx, ... P. news.aioe.org has it
cooperative.co.uk has address 127.0.0.1
Why do I see this? host cooperative.co.uk cooperative.co.uk has address 127.0.0.1 host cooperative.co.uk 1.1.1.1 Using domain server: Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases: cooperative.co.uk has address 127.0.0.1 cat /etc/hosts|grep -i coop This has nothing to do with debian other than that I am using debian, but I am not sure where else I would ask.
