Re: biqu bx 3d printer ??

[Tixy]

On Fri, 2021-12-24 at 10:41 +1100, David wrote:
> On Thu, 23 Dec 2021 at 00:50, Tixy  wrote:
> 
> Hi Tixy,
> 
> After reading your several musings in this thread regarding
> USB verses serial interfaces for CNC machines (3D printer, etc),
> I thought I'd respond, because I think they are missing the mark.
> 
> > I guess it's possible to use a USB to serial chip in the
> > printer which then talks to a serial interface on the computer driving
> > the printer. But that is very clunky ...
> 
> I have a budget 3 axis CNC router and that's exactly how it operates.
> Apart from that, I'm not involved with the CNC world, but I get the
> impression that this is standard practice at all scales, for historical
> and practical reasons.

You have more experience than me, so am happy to accept this as a more
accurate view than mine :-) Though to not give up in the specific case
of the $subject printer, it would seem perverse for this Kickstarter
funded project to not use the USB interface built into the SoC they are
using and instead add extra silicon for USB.

As a footnote, I have two devices myself where there is an FTDI USB to
serial interface chip built into a device to provide USB connectivity.
One is a Shevaplug which has a circa 15 year old SoC in it. The second
is my own 8-bit computer system :-) though this is using the chip
version that provide an 8-bit parallel interface to the FIFO, so
setting baud rate on that device has no effect.

-- 
Tixy

Re: Firefox / dbus standard file browser application

[Andreas Ronnquist]

On Sun, 12 Dec 2021 17:24:47 +0100,
Andreas Ronnquist wrote:

>I'm Debian stable, Xfce desktop, and have recently gone from Chromium
>to firefox-esr.
>
>Now I discover that in Firefox, pressing "open containing folder" in
>the "downloaded files" list, opens Thunar, but I want it to open Caja
>which I use as default file browser. 
>
>I have already set it where I have found it in settings, as in
>the "default programs" dialog, and other places, but it seems like
>Firefox uses dbus to get which file browser to use.
>
>Where do I set dbus and Firefox to use Caja instead of Thunar?
>

I finally solved this by simply removing Thunar completely from my
install. Then finally firefox uses caja as wanted.

This unfortunately removes the Xfce task, but I install my needed
packages by hand, so I can live with that.

My problem is basically solved, but I would love to find a way to set
caja as default dbus filemanager without needing to uninstall thunar.

-- Andreas Rönnquist
mailingli...@gusnan.se
andr...@ronnquist.net

qmail package in bullseye

[황병희]

Hi, there is no qmail package in bullseye. what's wrong?
Bellow are my environments:

-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads)
Locale: LANG=ko_KR.UTF-8, LC_CTYPE=ko_KR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Sincerely, Byung-Hee

Re: qmail package in bullseye

[Roberto C . Sánchez]

It seems that netqmail (the package that provides qmail) was removed
last year:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961289

On Fri, Dec 24, 2021 at 09:58:11PM +0900, 황병희 wrote:
> Hi, there is no qmail package in bullseye. what's wrong?
> Bellow are my environments:
> 
> -- System Information:
> Debian Release: 11.2
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
> 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads)
> Locale: LANG=ko_KR.UTF-8, LC_CTYPE=ko_KR.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Sincerely, Byung-Hee
> 

-- 
Roberto C. Sánchez

Re: qmail package in bullseye

[Andy Smith]

Hello,

On Fri, Dec 24, 2021 at 09:58:11PM +0900, 황병희 wrote:
> Hi, there is no qmail package in bullseye. what's wrong?

It was removed from Debian in May 2020 and hasn't been in a release
since buster:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961289

If you still have interest, can maintain a package and can find a
Debian Developer to sponsor uploads you may be able to reintroduce
it.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: qmail package in bullseye

[Greg Wooledge]

On Fri, Dec 24, 2021 at 09:58:11PM +0900, 황병희 wrote:
> Hi, there is no qmail package in bullseye. what's wrong?

If you wish to use qmail, the recommended way to do it is:

1) Install equivs, and use it to build the "mta-local" package.
   There's an example file for it:
   /usr/share/doc/equivs/examples/mail-transport-agent.ctl
   Read the instructions in /usr/share/doc/equivs/README.Debian .

2) Install the mta-local package (.deb file).  If you've already got a
   different Debian MTA package installed, this should remove it.  Or,
   you can use dpkg --force-depends to remove it manually, before
   installing mta-local.

3) Build and install qmail from your preferred source tree.

4) Set up the symlink from /usr/sbin/sendmail to /var/qmail/bin/sendmail
   or wherever you placed the qmail programs.

5) Set up whatever method you prefer to start qmail at boot time.

The Debian packaging used to take care of those last two, but now it's
up to us.

Please note that the original qmail-smtpd is NOT good to use without
patching or replacing.  It was written in an era when spam was only
beginning to be a threat.  If you run qmail-smtpd on the Internet, you
WILL become a joe-job spam bouncer, and we don't want that.

If you're not up for the task of replacing qmail-smtpd, or restricting
it solely to trusted internal LAN traffic, then please don't run qmail.
It's not for everyone, and there are alternatives that would be a lot
simpler to set up.

Re: qmail package in bullseye

[황병희]

Andy Smith  writes:

> Hello,
>
> On Fri, Dec 24, 2021 at 09:58:11PM +0900, 황병희 wrote:
>> Hi, there is no qmail package in bullseye. what's wrong?
>
> It was removed from Debian in May 2020 and hasn't been in a release
> since buster:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961289
>
> If you still have interest, can maintain a package and can find a
> Debian Developer to sponsor uploads you may be able to reintroduce
> it.

Always i'm beginner in Debian. I was just curious about qmail
status. Thanks for information, Andy and Roberto ^^^

Sincerely, Byung-Hee 

Re: qmail package in bullseye

[황병희]

Dear Greg,

Greg Wooledge  writes:

> On Fri, Dec 24, 2021 at 09:58:11PM +0900, 황병희 wrote:
>> Hi, there is no qmail package in bullseye. what's wrong?
>
> If you wish to use qmail, the recommended way to do it is:
>
> 1) Install equivs, and use it to build the "mta-local" package.
>There's an example file for it:
>/usr/share/doc/equivs/examples/mail-transport-agent.ctl
>Read the instructions in /usr/share/doc/equivs/README.Debian .
>
> 2) Install the mta-local package (.deb file).  If you've already got a
>different Debian MTA package installed, this should remove it.  Or,
>you can use dpkg --force-depends to remove it manually, before
>installing mta-local.
>
> 3) Build and install qmail from your preferred source tree.
>
> 4) Set up the symlink from /usr/sbin/sendmail to /var/qmail/bin/sendmail
>or wherever you placed the qmail programs.
>
> 5) Set up whatever method you prefer to start qmail at boot time.
>
> The Debian packaging used to take care of those last two, but now it's
> up to us.
>
> Please note that the original qmail-smtpd is NOT good to use without
> patching or replacing.  It was written in an era when spam was only
> beginning to be a threat.  If you run qmail-smtpd on the Internet, you
> WILL become a joe-job spam bouncer, and we don't want that.
>
> If you're not up for the task of replacing qmail-smtpd, or restricting
> it solely to trusted internal LAN traffic, then please don't run qmail.
> It's not for everyone, and there are alternatives that would be a lot
> simpler to set up.

Thank you for very kind detail how-to, step-by-step. In honest, i did
want to do demonstration on QMTP with qmail. Anyway your article will
help me in the future!

Sincerely, QMTP fan Byung-Hee

Re: Identity Theft

[rhkramer]

On Thursday, December 23, 2021 04:26:54 PM Jeremy Ardley wrote:
> Getting back to the OP, on the scale of likelihood:
> 
> - zero probability a bad guy was sitting across the street to intercept
> his phone
> 
> - zero probability a carrier exchange was compromised by a non-state actor
> 
> - moderate probability the financial institution PBX was compromised
> 
> - good probability the OP computer *could* have been compromised - it's
> relatively easy but may not have happened

I don't think my computer is relevant -- the ObiHai VOIP device is a self 
contained device -- it doesn't need / use my computer for anything except:

   * many years ago, iirc, and occasionally since then, I've used it to go to 
an ObiHai web page to set up the ObiHai device, and specify the "provider" 
(Google Voice).  (Occasionally since then I've had to go back to that page and 
check or re-setup the device.)

   * if I want to do things like view the Google Voice phone log, I do that on 
a web page (on my computer).


> 
> My working theory is the financial institution PBX was compromised and a
> small percentage of inbound calls intercepted. It was the OP's bad luck
> to be one of those.

Re: qmail package in bullseye

[Georgi Naplatanov]

On 12/24/21 14:58, 황병희 wrote:
> Hi, there is no qmail package in bullseye. what's wrong?

The software seems unmaintained for a long time [1]. According to
wikipedia the last release is from 1998 and I think there was an
incompatibility with the qmail's license and Debian. I've never seen
qmail's binary packages in Debian. I think there were tools in Debian
which allowed users to compile qmail on their own.

If you are looking for SMTP you can look at Postfix and Exim.

Kind regards
Georgi

[1] - https://en.wikipedia.org/wiki/Qmail

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[Glenn]

99%+ this is a failing hard drive. If you value your data use ddrescue to 
transfer your failing drive to a new one as step one.   Then you can do further 
troubleshooting.
Besides smartctl tests what I do is boot a rescue disk such as sysrescuecd on a 
USB stick and then run 
dd_rescue -v /dev/sdX /dev/null
Any disk errors will become apparent. Make sure you understand dd_rescue read 
and write agrguments. You dont want to write to your disk!!

Good Luck
Glenn

On December 23, 2021 7:40:42 PM AST, David Christensen 
 wrote:
>On 12/23/21 1:51 PM, Heladu wrote:
>> Greetings,
>> I've been experiencing a lot of slowness in general when the system attempts
>> to read from the hard drive disk. I use Debian 10 Buster with the MATE 
>> desktop
>> environment and simple things like opening the calendar applet or right
>> clicking to open the context menu takes longer than usual. I noticed the LED
>> indicator than turns on when reading from the disk also took longer to turn
>> off, so I decided to inspect the logs and I ran into these entries:
>> 
>> Dec 23 22:33:24 sigma kernel: [ 1250.853537] ata6.00: exception Emask 0x0 
>> SAct
>> 0x4000 SErr 0x0 action 0x0
>> Dec 23 22:33:24 sigma kernel: [ 1250.853544] ata6.00: irq_stat 0x4008
>> Dec 23 22:33:24 sigma kernel: [ 1250.853550] ata6.00: failed command: READ
>> FPDMA QUEUED
>> Dec 23 22:33:24 sigma kernel: [ 1250.853559] ata6.00: cmd
>> 60/08:f0:10:96:2b/00:00:01:00:00/40 tag 30 ncq dma 4096 in
>> Dec 23 22:33:24 sigma kernel: [ 1250.853559]  res
>> 41/40:00:10:96:2b/00:00:01:00:00/00 Emask 0x409 (media error) 
>> Dec 23 22:33:24 sigma kernel: [ 1250.853563] ata6.00: status: { DRDY ERR }
>> Dec 23 22:33:24 sigma kernel: [ 1250.853566] ata6.00: error: { UNC }
>> Dec 23 22:33:24 sigma kernel: [ 1250.855102] ata6.00: configured for UDMA/133
>> Dec 23 22:33:24 sigma kernel: [ 1250.855121] sd 5:0:0:0: [sda] tag#30 FAILED
>> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>> Dec 23 22:33:24 sigma kernel: [ 1250.855126] sd 5:0:0:0: [sda] tag#30 Sense
>> Key : Medium Error [current]
>> Dec 23 22:33:24 sigma kernel: [ 1250.855130] sd 5:0:0:0: [sda] tag#30 Add.
>> Sense: Unrecovered read error - auto reallocate failed
>> Dec 23 22:33:24 sigma kernel: [ 1250.855135] sd 5:0:0:0: [sda] tag#30 CDB:
>> Read(10) 28 00 01 2b 96 10 00 00 08 00
>> Dec 23 22:33:24 sigma kernel: [ 1250.855139] print_req_error: I/O error, dev
>> sda, sector 19633680
>> Dec 23 22:33:24 sigma kernel: [ 1250.855162] ata6: EH complete
>> 
>> They happen every time the system experiences slow reads. Now, I did some
>> research and I've read some possible causes like a bad SATA cable or a
>> malfunctioning HDD or PSU. I booted from a Debian installer on an USB stick
>> and I ran fsck.ext4 to check the disk and it printed the partition was clean.
>> 
>> Given that fsck didn't print anything unusual, I decided to replace the SATA
>> cable. However, it's still happening.
>> 
>> The HDD is a 1TB 3.5" WD Blue SATA drive which was bought a year ago.
>> 
>> I'm certain this is not a software problem because I've been running the
>> system a whole year without any problem. Has anyone ever experienced this? Is
>> there a way I can reliably find the faulty component (HDD, PSU...) without
>> buying a new one and hoping that solves it?
>> 
>> Thank you very much in advance.
>
>
>I own a power supply tester, so I would start by testing the power supply.
>
>
>I suggest booting a memory test USB stick and letting it run for at 
>least one pass (better, 24 hours).  Either of these should work:
>
>https://www.memtest86.com/
>
>https://www.memtest.org/
>
>
>I suggest booting Debian and running a SMART long test:
>
># smartctl -t long /dev/sda
>
>
>Check the test every hour until complete:
>
># smartctl -x /dev/sda
>
>
>Please post the final smartctl(8) report.
>
>
>David
>

Re: Identity Theft

[Philippe LeCavalier]

On Fri, Dec 24, 2021, 09:57  wrote:

> On Thursday, December 23, 2021 04:26:54 PM Jeremy Ardley wrote:
> > Getting back to the OP, on the scale of likelihood:
> >
> > - zero probability a bad guy was sitting across the street to intercept
> > his phone
> >
> > - zero probability a carrier exchange was compromised by a non-state
> actor
> >
> > - moderate probability the financial institution PBX was compromised
> >
> > - good probability the OP computer *could* have been compromised - it's
> > relatively easy but may not have happened
>
> I don't think my computer is relevant -- the ObiHai VOIP device is a self
> contained device -- it doesn't need / use my computer for anything except:
>
>* many years ago, iirc, and occasionally since then, I've used it to go
> to
> an ObiHai web page to set up the ObiHai device, and specify the "provider"
> (Google Voice).  (Occasionally since then I've had to go back to that page
> and
> check or re-setup the device.)
>
>* if I want to do things like view the Google Voice phone log, I do
> that on
> a web page (on my computer).
>
>
> >
> > My working theory is the financial institution PBX was compromised and a
> > small percentage of inbound calls intercepted. It was the OP's bad luck
> > to be one of those.
>

It's a process. Always work from the most probable to the least. As
outlined, google is the least likely and you and devices you control are
the most likely. Vet one move on to the next. It's a simple process and as
long as you're thorough it's the best approach to draw a solid conclusion.

If the device isn't compromised (which, you saying so doesn't in any way
vet the device as safe and not compromised btw) then the desktop you got
the number from is the next step to vet. What OS are you running, what
endpoint security do you have...etc. next after that would be your home
network. What router/gateway/firewall do you have? What dns service do you
use (could be key imo)? So on and so forth until we find the smoking gun.
This would go all the way to speaking with a legit person at the financial
firm about their PBX which you will no doubt find huge degrees of
resistance.

One thing that breaks this process is the user making statements based on
previous knowledge or assumption like you just did about your obi device.
You have to vet aspects even if you know them to be clean. Your assumption
and emotion have no room in this process IF you want to find the truth.

Re: qmail package in bullseye

[Dan Ritter]

황병희 wrote: 
> > 3) Build and install qmail from your preferred source tree.

And I've seen your posts on the qmail list, so you should
definitely take their advice on which version to use.

> > 4) Set up the symlink from /usr/sbin/sendmail to /var/qmail/bin/sendmail
> >or wherever you placed the qmail programs.

Most of the source tree's install instructions will remind you
to do this.

> > 5) Set up whatever method you prefer to start qmail at boot time.

Note that Debian has daemontools, daemontools-run, and s6 (a
daemontools-like system) available in stable. These are slightly
different from the pure cr.yp.to instructions, but very easily
adaptable.


> > Please note that the original qmail-smtpd is NOT good to use without
> > patching or replacing.  It was written in an era when spam was only
> > beginning to be a threat.  If you run qmail-smtpd on the Internet, you
> > WILL become a joe-job spam bouncer, and we don't want that.

In particular, Debian has the mailfront package, which is Bruce
Guenter's qmail-compatible set of tools. From the description:

  It contains complete SMTP, QMQP, QMTP, and POP3 front-ends as well as
  an authentication module for IMAP.  The mail delivery front-ends also
  contain internal address filtering features. 

  Two SMTP back-ends are provided.  One delivers mail to qmail-queue,
  mimicking most of the behavior of qmail-smtpd, with the addition of
  support for SMTP AUTH.

This is most likely your best path forward. 

-dsr-

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[James Dutton]

On Thu, 23 Dec 2021 at 22:09, Heladu  wrote:
> Dec 23 22:33:24 sigma kernel: [ 1250.855130] sd 5:0:0:0: [sda] tag#30 Add.
> Sense: Unrecovered read error - auto reallocate failed
That is a faulty disk. Replace it. It has already lost the data stored
on one sector, and when this happens, more fail.
The "slow disk" you are experiencing is the disk trying to re-read a
faulty sector multiple times in the hope it will recover the data.
The disk will automatically try to relocate this data to a different
sector, and mark the bad one as bad.
This is the "reallocate" feature it mentions in the error message.
Except in this case, even though it tried to re-read the bad sector
multiple times in the hopes of recovering it, it failed to do so, thus
that sector's data is lost for-ever.
It is 100% a faulty disk, and 0% a cable problem.

Re: Identity Theft

[John Hasler]

 Philippe LeCavalier writes:
> If the device isn't compromised (which, you saying so doesn't in any
> way vet the device as safe and not compromised btw) then the desktop
> you got the number from is the next step to vet.

How do you explain the Google Voice log entries?
-- 
John Hasler 
j...@sugarbit.com
Elmwood, WI USA

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[rhkramer]

On Thursday, December 23, 2021 05:30:32 PM Alexander V. Makartsev wrote:
> You can review SMART attributes which keep track of device's health and
> metrics.
> This utility is part of "smartmontools" package.
> Run this one-liner to see values of relevant attributes:
>  $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
> Current|199 UDMA'

I'm not the OP, and not  very familiar with smartmon / smartctl, but I ran the 
recommended command on the two disks in my oldest system, and the results are 
posted below.  (Aside: at some point, in the near future, I'll read the 
relevant manpage to better understand that output.)

I also see the advice from Dave Christensen on additional tests to run and 
will try those in the near future, ideally next week.

/dev/sda is an SSD (which hold my system and doesn't get much writing), 
/dev/sdb is an HDD (which holds my "user data").

Should I be worried?

root@s19:~# smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197 
> Current|199 UDMA' 
>
  5 Reallocated_Sector_Ct   0x0033   100   100   036Pre-fail  Always   
-   0   
183 Runtime_Bad_Block   0x0032   100   100   000Old_age   Always   
-   0   
197 Current_Pending_Sector  0x0012   100   100   000Old_age   Always   
-   0   
199 UDMA_CRC_Error_Count0x003e   200   200   000Old_age   Always   
-   0   
root@s19:~# smartctl -A /dev/sdb | grep -E '5 Realloc|183 Runtime|197   
   
Current|199 UDMA'   
   
  5 Reallocated_Sector_Ct   0x0032   100   100   000Old_age   Always   
-   12  
root@s19:~#  

Re: Identity Theft

[Philippe LeCavalier]

On Fri, Dec 24, 2021, 10:26 John Hasler  wrote:

>  Philippe LeCavalier writes:
> > If the device isn't compromised (which, you saying so doesn't in any
> > way vet the device as safe and not compromised btw) then the desktop
> > you got the number from is the next step to vet.
>
> How do you explain the Google Voice log entries?
>

> Yes the legit number was called but randomly (so it appears) a imposter is
> answering while other times the legit company answers. That's the
> information we know for fact u less I'm mistaken.


So if you asked me to draw a conclusion and forego all the investigative
steps suggested which I do not recommend, I would say the two most probable
causes are a compromised PBX at the financial institute or sim card
cloning. Third on the list would be dns poisoning on the OPs gateway.

All 3 scenarios would have the log entries look legit.

Re: qmail package in bullseye

[ed neville]

On 2021-12-24 17:00+0200, Georgi Naplatanov wrote:
> On 12/24/21 14:58, 황병희 wrote:
> > Hi, there is no qmail package in bullseye. what's wrong?
> The software seems unmaintained for a long time [1]. According to
> wikipedia the last release is from 1998 and I think there was an
> incompatibility with the qmail's license and Debian. I've never seen
> qmail's binary packages in Debian. I think there were tools in Debian
> which allowed users to compile qmail on their own.
> 
> If you are looking for SMTP you can look at Postfix and Exim.

qmail is now public domain, so the licence shouldn't be a problem now.

  

qmail with JMS's patchset has been mostly just fine for me. However, if 
I were doing things again, I would suggest postfix since things like SSL 
are included and it follows some of the compartmentalised design of 
qmail.

Ed

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[Alexander V. Makartsev]

On 24.12.2021 20:31, rhkra...@gmail.com wrote:

...
/dev/sdb is an HDD (which holds my "user data").

Should I be worried?

root@s19:~# smartctl -A /dev/sdb | grep -E '5 Realloc|183 Runtime|197
Current|199 UDMA'
   5 Reallocated_Sector_Ct   0x0032   100   100   000Old_age   Always
-   12
root@s19:~#

Attribute #5 shows if the drive in question ever encountered and 
successfully remapped a 'bad block'. In your case it happened at least 
12 times.
They could've happen a few years ago, drive's firmware recovered from 
them and it was working fine ever since¹.
But they also could've happen recently within a few days and in that 
case the drive is failing and should be replaced ASAP.


For future investigation you should see full output of:
    # smartctl -A /dev/sdb

And also SMART logs, to see when was last media error encountered:
    # smartctl -l error /dev/sda

For now one thing is certain, your HDD had media errors, is not 
reliable² and you should have a good backup of data from it.
It's good idea to configure 'smartd' on all hosts to monitor health 
state of your drives and notify you by mail if something happened.



¹ I have a 320GB HDD for a five years with, I think, contaminated 
platter. When it tries to read from some LBA range it fails with media 
errors, but if I request to read past that LBA range it works fine.
As a workaround, I've repartitioned it effectively cutting off that 
faulty LBA range (around 50GB) and use it as a portable drive to carry 
some not important data and to store additional backup copies.

I always expect it to die, but it still works fine to this day.

² Any hardware, despite being new or old, could fail at any time. Always 
expect failure and have a good backup.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Can mount external CD but can't play or rip tracks

[Kete]

Hi,
I can't figure out if this is a permission error or what, but I have an 
external DVD drive connected by USB. It mounts in my /media directory, giving 
my user read permission, but it won't play in SMPlayer or mpv. cdparanoia is 
"Unable to open disc." I can see the files in my file browser.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

Re: 8 -> 9 update changing things

[Roy J. Tellason, Sr.]

On Wednesday 22 December 2021 11:21:47 am Dan Ritter wrote:
> Roy J. Tellason, Sr. wrote: 
> > On Monday 20 December 2021 10:09:56 am Roy J. Tellason, Sr. wrote:
> > > > > Suggestions as to where I might look for the problem?
> > > > 
> > > > In general, that message means that even if there is a copy of
> > > > the pulseaudio daemon running, it is not running with the right
> > > > userid and the X11 session you are running in doesn't know about
> > > > it.
> > > > 
> > > > Run "pulseaudio --start" and try again.
> > > 
> > > That did get the volume control as invoked from the Xfce applications 
> > > menu working,  all right.  Looking in the process table that I see under 
> > > KDE System Monitor (what I usually use to keep track of system loading) I 
> > > now see pulseaudio in there twice.  One shows the command you mention 
> > > here,  and the other one doesn't,  and says "daemonize=no".  I'm guessing 
> > > that's the problem,  where to fix it is another question.  Mousing over 
> > > it I also see "parent=systemd" for both of them...
> > > 
> > > Looking at "man systemd",  nothing jumps out at me with regard to where I 
> > > want to go from here.

?

> > With this having been done,  after restarting the virtualbox instance,  
> > sound is now working there also.  What I might need to fiddle with in terms 
> > of systemd is not at all clear to me,  though.  I don't know why this would 
> > have changed with the upgrade.

Yes,  it's things changing when I upgrade that bother me about all of this...

> > Any further thoughts on this? 
> 
> Since it just happened... I'll say that pulseaudio is easily on
> the same level of reliability as Windows 95. I decided to test
> out the advertised capability of a music player as a USB DAC. As
> soon as I got things plugged in, the pulseaudio daemon crashed.
> After I restarted it, the pulseeffects equalizer service froze. 
> After I restarted that, pulseeffects decided that it would be a
> good idea to use the USB microphone as both default input and
> output...

I don't know enough about what you're dealing with there to comment on this.
 
> It's currently working. But I'd so much rather have systems that
> didn't think that they should switch configurations
> automatically, since PA is so terrible at reading my mind.
> 
> Anyway, upgrade to bullseye.

I'll get there.  But before I continue with upgrades,  I intend to fix what's 
broken,  and maybe trim some of the fat out of the system as it stands,  so I 
don't end up having to download and upgrade stuff I don't use or don't want.

In my initial install,  I selected multiple desktop environments,  so I could 
try them out.  While I was fine with real early versions of KDE,  I don't like 
where they've gone with it so I don't use it as a desktop,  though I do use a 
few of the utilities.  I seem to be seeing bits of stuff running,  though,  
that shouldn't be.  And also from some of the other choices.  I need to clean 
that up a bit,  I think,  in addition to the above...

-- 
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space,  a critter that can
be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James 
M Dakin

Re: Can mount external CD but can't play or rip tracks

[Dan Ritter]

Kete wrote: 
> I can't figure out if this is a permission error or what, but I have an 
> external DVD drive connected by USB. It mounts in my /media directory, giving 
> my user read permission, but it won't play in SMPlayer or mpv. cdparanoia is 
> "Unable to open disc." I can see the files in my file browser.

There are two different things going on.

Some optical media have read-only filesystems on them. There are
several variants, but the important thing is that they get
mounted as part of your filesystem and they contain files and
directories. DVDs are like this.

Some optical media have audio data on them, in a CD format.
This is how music discs show up. Any tools which works on them
has to talk to the drive, not to the disc on the drive.

Some file browsers mix the two, and present CD audio tracks as
though they were files. They aren't, really.

Tell us:

1. What kind of disc are you using?

2. Exactly what errors are you getting?

Then we can help.

-dsr-

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[Heladu]

Hello,
First of all, thanks for the reply.

El vie, 24-12-2021 a las 03:30 +0500, Alexander V. Makartsev escribió:
>  You can review SMART attributes which keep track of device's health and
> metrics.
> This utility is part of "smartmontools" package.
> Run this one-liner to see values of relevant attributes:
> $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
> Current|199 UDMA'
> 
> Here is what they should like on perfectly fine hard drive:
> $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
> Current|199 UDMA'
>   5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail 
> Always   -   0
> 183 Runtime_Bad_Block   0x0032   100   100   000Old_age  
> Always   -   0
> 197 Current_Pending_Sector  0x0012   100   100   000Old_age  
> Always   -   0
> 199 UDMA_CRC_Error_Count0x003e   200   200   000Old_age  
> Always   -   0
> 
> Raw values are displayed on the right and they all zeroes. Post the output
> you got with next reply.
> You should backup or "ddrescue" your data from this drive and RMA\replace it
> or better switch to SSD disk.
> 

Well, I installed the package in question and ran the very same command you
said. However, the Runtime_Bad_Block attribute doesn't appear. Here's the
output:
$ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197 Current|199
UDMA'
  5 Reallocated_Sector_Ct   0x0033   200   200   140Pre-
fail  Always   -   0
197
Current_Pending_Sector  0x0032   200   200   000Old_age   Always   -  
 1
199
UDMA_CRC_Error_Count0x0032   200   200   000Old_age   Always   -  
 0

If I understood correctly what I read, this means there's one sector waiting
for remapping, right? And why doesn't the Runtime_Bad_Block attribute appear?

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[Heladu]

El jue, 23-12-2021 a las 18:12 -0500, Dan Ritter escribió:
> It's true a bad cable can cause this, but you swapped cables,
> so:
> 
> Back up the data immediately; this disk is failing.
> 
> If it is under warranty, you'll get a replacement. That can take
> weeks, though, so you should go buy another disk today.
> 
> Sorry.
> 
> -dsr-

Yeah, it's clearly a faulty disk. But I wonder why it has started to fail
"sooner". All HDDs I've had have lasted for at least 5 years... I guess I
wasn't lucky with this one.

Thanks for the reply.

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[Heladu]

Hello,
El vie, 24-12-2021 a las 15:23 +, James Dutton escribió:
> Except in this case, even though it tried to re-read the bad sector
> multiple times in the hopes of recovering it, it failed to do so, thus
> that sector's data is lost for-ever.

I see... Well, in that case I won't bother trying to fix it and get a new one
instead.

Thanks for the reply.

[SOLVED] Re: Desktop "locking".

[peter]

From: Andrei POPESCU 
Date: Tue, 14 Dec 2021 10:17:31 +0100
> Gnome is very likely using it's own thing (as per the description, 
> light-locker relies on lightdm while Gnome is using gdm3).

While keeping firefox, gedit and dependants, I removed every package
found with "gnome" in the name.  That left one gnome.

peter@joule:/home/peter$ dpkg -l | grep gnome
ii  libsoup-gnome2.4-1:i386   2.72.0-2
  i386 HTTP library implementation in C -- GNOME support library

The green button persisted.  With some luck, googling found this page.
https://superuser.com/questions/1084382/weston-screen-blanking

shutting off idle screens is a good idea but the green button is 
pointless. Therefore set idle-time and locking.  This is the current 
weston configuration here.

peter@joule:/home/peter$ cat .config/weston.ini
# joule:/home/peter/.config/weston.ini
[core]
xwayland=true
# Black display after 4 minutes of idleness.
idle-time=240

[xwayland]
path=/usr/bin/Xwayland

[shell]
# The display is not locked.  Don't show the pointless green button.
locking=false
allow-zap=true

Observation:
The title "Unlock your desktop" can be improved. I suggest "Unlock weston".

Regards,   ... P.

 
-- 
mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
   48.7693 N 123.3053 W

Re: Can mount external CD but can't play or rip tracks

[Thomas Schmitt]

Hi,

Kete wrote:
> > cdparanoia is "Unable to open disc."

The source search offers me two occasions
  
https://codesearch.debian.net/search?q=package%3Acdparanoia+Unable+to+open+disc
If there is really no text "Is there an audio CD in the drive?",
then it's
  
https://sources.debian.org/src/cdparanoia/3.10.2+debian-14/main.c/?hl=1041#L1041
I.e. cdda_open() did not return one of {0, -2 ... -6}.
The "cdda" in the function name indicates that this function looks for
CD-DA audio tracks, in contrast to CD-ROM data tracks.


Dan Ritter wrote:
> Some file browsers mix the two, and present CD audio tracks as
> though they were files. They aren't, really.

Indeed.

> 1. What kind of disc are you using?

To determine the CD track structure, put it into the drive (/dev/sr0 if
it is the only CD capable drive of the computer) and do:

  cdrskin dev=/dev/sr0 -minfo

which should report for CD-DA tracks something like:

  Track  Sess Type   Start Addr End Addr   Size
  ==
  1 1 Audio  0  3289   3290
  2 1 Audio  3290   6350   3061
  3 1 Audio  6351   7643   1293

and for a CD-ROM track something like:

  Track  Sess Type   Start Addr End Addr   Size
  ==
  1 1 Data   0  172027 172028

With

  wodim dev=/dev/sr0 -toc

it looks a bit more cryptic.
CD-DA is "control" 4:

  track:   1 lba: 0 (0) 00:02:00 adr: 1 control: 0 mode: -1
  track:   2 lba:  3290 (13160) 00:45:65 adr: 1 control: 0 mode: -1
  track:   3 lba:  6351 (25404) 01:26:51 adr: 1 control: 0 mode: -1

CD-ROM is "control" 0:

  track:   1 lba: 0 (0) 00:02:00 adr: 1 control: 4 mode: 1


Have a nice day :)

Thomas

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[Alexander V. Makartsev]

On 24.12.2021 22:44, Heladu wrote:

Hello,
First of all, thanks for the reply.

El vie, 24-12-2021 a las 03:30 +0500, Alexander V. Makartsev escribió:

  You can review SMART attributes which keep track of device's health and
metrics.
This utility is part of "smartmontools" package.
Run this one-liner to see values of relevant attributes:
 $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
Current|199 UDMA'

Here is what they should like on perfectly fine hard drive:
 $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
Current|199 UDMA'
   5 Reallocated_Sector_Ct   0x0033   100   100   010Pre-fail
Always   -   0
 183 Runtime_Bad_Block   0x0032   100   100   000Old_age
Always   -   0
 197 Current_Pending_Sector  0x0012   100   100   000Old_age
Always   -   0
 199 UDMA_CRC_Error_Count0x003e   200   200   000Old_age
Always   -   0

Raw values are displayed on the right and they all zeroes. Post the output
you got with next reply.
You should backup or "ddrescue" your data from this drive and RMA\replace it
or better switch to SSD disk.


Well, I installed the package in question and ran the very same command you
said. However, the Runtime_Bad_Block attribute doesn't appear. Here's the
output:
$ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197 Current|199
UDMA'
   5 Reallocated_Sector_Ct   0x0033   200   200   140Pre-
fail  Always   -   0
197
Current_Pending_Sector  0x0032   200   200   000Old_age   Always   -
  1
199
UDMA_CRC_Error_Count0x0032   200   200   000Old_age   Always   -
  0

If I understood correctly what I read, this means there's one sector waiting
for remapping, right?
That is correct. Drive's firmware should take care of it automatically 
or during short or extended self-tests.

I suggest to backup your data before performing any self-tests on the drive.
They are non-destructive by nature, but you never know what could happen 
and what was the initial cause for 'bad blocks' to appear.



And why doesn't the Runtime_Bad_Block attribute appear?

SMART attributes and functionality could be different, depending on 
manufacturer or\and model of the device.
My example was from HDD made by Seagate. Maybe it was a mistake on my 
part, suggesting a one-liner with 'grep', causing a confusion.



--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Can mount external CD but can't play or rip tracks

[Kete]

The CD started playing, and I was able to copy the tracks to my computer. 
However, I am not able to access the burner with Xfburn or Brasero. I am using 
an external DVD drive with write capabilities through USB. When I run 'cdrskin 
-v dev=/dev/sr0 -toc', I get 'cdrskin: status 2 BURN_DISC_EMPTY "There is no 
disc at all in the drive"'. The external drive is new, but it seems to need a 
lot of attention to get going. I'm in the cdrom group. The facl says I have rw.


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Friday, December 24, 2021 7:12 PM, Thomas Schmitt  wrote:

> Hi,
>
> Kete wrote:
>
> > > cdparanoia is "Unable to open disc."
>
> The source search offers me two occasions
> https://codesearch.debian.net/search?q=package%3Acdparanoia+Unable+to+open+disc
> If there is really no text "Is there an audio CD in the drive?",
> then it's
> https://sources.debian.org/src/cdparanoia/3.10.2+debian-14/main.c/?hl=1041#L1041
> I.e. cdda_open() did not return one of {0, -2 ... -6}.
> The "cdda" in the function name indicates that this function looks for
> CD-DA audio tracks, in contrast to CD-ROM data tracks.
>
> Dan Ritter wrote:
>
> > Some file browsers mix the two, and present CD audio tracks as
> > though they were files. They aren't, really.
>
> Indeed.
>
> > 1.  What kind of disc are you using?
>
> To determine the CD track structure, put it into the drive (/dev/sr0 if
> it is the only CD capable drive of the computer) and do:
>
> cdrskin dev=/dev/sr0 -minfo
>
> which should report for CD-DA tracks something like:
>
> Track Sess Type Start Addr End Addr Size
>
> 
>
>   1 1 Audio  0  3289   3290
>   2 1 Audio  3290   6350   3061
>   3 1 Audio  6351   7643   1293
>
>
> and for a CD-ROM track something like:
>
> Track Sess Type Start Addr End Addr Size
>
> ===
>
>   1 1 Data   0  172027 172028
>
>
> With
>
> wodim dev=/dev/sr0 -toc
>
> it looks a bit more cryptic.
> CD-DA is "control" 4:
>
> track: 1 lba: 0 ( 0) 00:02:00 adr: 1 control: 0 mode: -1
> track: 2 lba: 3290 ( 13160) 00:45:65 adr: 1 control: 0 mode: -1
> track: 3 lba: 6351 ( 25404) 01:26:51 adr: 1 control: 0 mode: -1
>
> CD-ROM is "control" 0:
>
> track: 1 lba: 0 ( 0) 00:02:00 adr: 1 control: 4 mode: 1
>
> Have a nice day :)
>
> Thomas

Re: Can mount external CD but can't play or rip tracks

[Thomas Schmitt]

Hi,

Kete wrote:
> The CD started playing, and I was able to copy the tracks to my computer.
> However, I am not able to access the burner with Xfburn or Brasero.

When a CD-ROM is mounted, then the burn programs are supposed to refrain
from accessing the drive.


> I am
> using an external DVD drive with write capabilities through USB. When I run
> 'cdrskin -v dev=/dev/sr0 -toc', I get 'cdrskin: status 2 BURN_DISC_EMPTY
> "There is no disc at all in the drive"'.

Is there perhaps another drive attached to your computer ?

What do you get from

  cdrskin --devices

which should list the accessible drives, like

  0  dev='/dev/sr0'  rwrw-- :  'HL-DT-ST'  'BDDVDRW GGC-H20L'
  1  dev='/dev/sr1'  rwrw-- :  'HL-DT-ST'  'DVDRAM GH24NSC0'

In order to have them all accessible, remove the CD so that it cannot be
mounted when you let cdrskin look for drives.


Have a nice day :)

Thomas

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[David Christensen]

On 12/24/21 7:31 AM, rhkra...@gmail.com wrote:

On Thursday, December 23, 2021 05:30:32 PM Alexander V. Makartsev wrote:

You can review SMART attributes which keep track of device's health and
metrics.
This utility is part of "smartmontools" package.
Run this one-liner to see values of relevant attributes:
  $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
Current|199 UDMA'


I'm not the OP, and not  very familiar with smartmon / smartctl, but I ran the
recommended command on the two disks in my oldest system, and the results are
posted below.  (Aside: at some point, in the near future, I'll read the
relevant manpage to better understand that output.)

I also see the advice from Dave Christensen on additional tests to run and
will try those in the near future, ideally next week.

/dev/sda is an SSD (which hold my system and doesn't get much writing),
/dev/sdb is an HDD (which holds my "user data").

Should I be worried?

root@s19:~# smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197

Current|199 UDMA'

   5 Reallocated_Sector_Ct   0x0033   100   100   036Pre-fail  Always
-   0
183 Runtime_Bad_Block   0x0032   100   100   000Old_age   Always
-   0
197 Current_Pending_Sector  0x0012   100   100   000Old_age   Always
-   0
199 UDMA_CRC_Error_Count0x003e   200   200   000Old_age   Always
-   0
root@s19:~# smartctl -A /dev/sdb | grep -E '5 Realloc|183 Runtime|197
Current|199 UDMA'
   5 Reallocated_Sector_Ct   0x0032   100   100   000Old_age   Always
-   12
root@s19:~#



Examining specific SMART parameters out of context may be useful for 
someone who is familiar with specific drives, but I suggest including 
the entire report when posting to a mailing list (I typically redact the 
serial number):


# smartctl -x /dev/sda

# smartctl -x /dev/sdb


While SMART reports are mostly standardized, each manufacturer may 
provide specific parameters and/or specific interpretations.  The whole 
report should include model number, hardware version, firmware version, 
etc., of the drive, which can be used to find a manufacturer document 
that explains these details.



David

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[David Christensen]

On 12/24/21 9:48 AM, Heladu wrote:

El jue, 23-12-2021 a las 18:12 -0500, Dan Ritter escribió:

It's true a bad cable can cause this, but you swapped cables,
so:

Back up the data immediately; this disk is failing.

If it is under warranty, you'll get a replacement. That can take
weeks, though, so you should go buy another disk today.

Sorry.

-dsr-


Yeah, it's clearly a faulty disk. 



Did you test the power supply, the memory, run a long SMART test, and 
correctly interpret the complete SMART report?  Did you double-check 
your conclusion somehow?



Computers are complicated beasts.  A fault in one portion can cause 
problems in another portion.  Bad power supplies are the worst -- they 
can cause anything and everything to malfunction, they can permanently 
damage other hardware, and they can cause electrical shock, 
electrocution, and/or fires.




But I wonder why it has started to fail
"sooner". All HDDs I've had have lasted for at least 5 years... I guess I
wasn't lucky with this one.

Thanks for the reply.



David

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[Thomas Schmitt]

Hi,

David Christensen wrote:
> Did you test the power supply, the memory, run a long SMART test, and
> correctly interpret the complete SMART report?

The following lines from the original post forward a message from the
drive's firmware.

Heladu wrote:
> > Dec 23 22:33:24 sigma kernel: [ 1250.855121] sd 5:0:0:0: [sda] tag#30 FAILED
> > Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > Dec 23 22:33:24 sigma kernel: [ 1250.855126] sd 5:0:0:0: [sda] tag#30 Sense
> > Key : Medium Error [current]
> > Dec 23 22:33:24 sigma kernel: [ 1250.855130] sd 5:0:0:0: [sda] tag#30 Add.
> > Sense: Unrecovered read error - auto reallocate failed
> > Dec 23 22:33:24 sigma kernel: [ 1250.855135] sd 5:0:0:0: [sda] tag#30 CDB:
> > Read(10) 28 00 01 2b 96 10 00 00 08 00

The drive answers to an SCSI READ command from the computer that its
storage medium caused an error. No problem outside the drive should
be able to cause this.


Have a nice day :)

Thomas

Re: Can mount external CD but can't play or rip tracks

[Kete]

Thanks. No, there are no other DVD drives. Here is the output of cdrskin:

0  dev='/dev/sr0'  rwrw-- :  'HL-DT-ST'  'DVD+-RW GSA-T21N'

The drive seems to need its bay held shut when trying to mount or burn a CD, 
but Xfburn can't get permission. Brasero stalls while trying to burn. Making an 
image with Brasero and trying to burn with wodim results in an image file too 
big. I guess I'll just have to return the drive and leave a review.

Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐

On Friday, December 24th, 2021 at 7:53 PM, Thomas Schmitt  
wrote:

> Is there perhaps another drive attached to your computer ?
>
> What do you get from
>
> cdrskin --devices
>
>
> In order to have them all accessible, remove the CD so that it cannot be
>
> mounted when you let cdrskin look for drives.

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[gene heskett]

On Friday, December 24, 2021 10:31:43 AM EST rhkra...@gmail.com wrote:
> On Thursday, December 23, 2021 05:30:32 PM Alexander V. Makartsev wrote:
> > You can review SMART attributes which keep track of device's health and
> > metrics.
> > This utility is part of "smartmontools" package.
> > 
> > Run this one-liner to see values of relevant attributes:
> >  $ sudo smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
> > 
> > Current|199 UDMA'
> 
> I'm not the OP, and not  very familiar with smartmon / smartctl, but I ran
> the recommended command on the two disks in my oldest system, and the
> results are posted below.  (Aside: at some point, in the near future, I'll
> read the relevant manpage to better understand that output.)
> 
> I also see the advice from Dave Christensen on additional tests to run and
> will try those in the near future, ideally next week.
> 
> /dev/sda is an SSD (which hold my system and doesn't get much writing),
> /dev/sdb is an HDD (which holds my "user data").
> 
> Should I be worried?
> 
> root@s19:~# smartctl -A /dev/sda | grep -E '5 Realloc|183 Runtime|197
> 
> > Current|199 UDMA'
> 
>   5 Reallocated_Sector_Ct   0x0033   100   100   036Pre-fail  Always
> -   0

Yes, and that 36 should be watched, any increase means that drive is on its 
way out. Usually quicker than next week. I'd replace it just for S&G, but 
today I'd replace it with an SSD, not spinning rust. Among other things the 
SSD is around 4x faster. I just had a new 2t spinning rust go belly up in the 
night, so I now boot from a 500G SSD, and put in 4 1T SSD's in a raid10 for
/home.

[...]

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Can mount external CD but can't play or rip tracks

[Thomas Schmitt]

Hi,

Kete wrote:
> No, there are no other DVD drives.

I struggle to make sense of the fact that some mount facility can make
some kind of files on the CD accessible, but that cdrskin reports
"There is no disc at all in the drive".

It would be explainable if cdrskin would report
  cdrskin: SORRY : Cannot open busy device '/dev/sr0'
and not give more infos than subsequent complaints about having no drive
to work with.


> I guess I'll just have to return the drive and leave a review.

Exchanging the drive is indeed a good way to distinguish drive problems
from software problems. (That's why i have a few of them.)

The problem with a honest review in this case is that drives tend to be
individually broken, rather than particular manufacturers or drive models
being of low quality.
(I have a bias against slim drives. But that costs me money in form of
full height USB boxes additional to full height BD drives.)


Have a nice day :)

Thomas

How to see the list of CRITICALLY vulnerable packages in Debian?

[maxwillb]

https://security-tracker.debian.org/tracker/status/release/stable

shows the list of packages currently considered vulnerable, but it does not 
show the severity.

For example, https://nvd.nist.gov/vuln/detail/CVE-2021-37973 has a CRITICAL 
severity but the Debian security tracker simply says "not assigned" (No dev so 
much as bothered to click on the 'NVD' link?)

Merry Christmas! 

-- 
Sent with https://mailfence.com  
Secure and private email

Re: Slow disk reads - exception Emask 0x0 SAct 0x6b0000 SErr 0x0 action 0x0

[David Christensen]

On 12/24/21 12:58 PM, Thomas Schmitt wrote:

Hi,

David Christensen wrote:

Did you test the power supply, the memory, run a long SMART test, and
correctly interpret the complete SMART report? >

The following lines from the original post forward a message from the
drive's firmware.

Heladu wrote:

Dec 23 22:33:24 sigma kernel: [ 1250.855121] sd 5:0:0:0: [sda] tag#30 FAILED
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Dec 23 22:33:24 sigma kernel: [ 1250.855126] sd 5:0:0:0: [sda] tag#30 Sense
Key : Medium Error [current]
Dec 23 22:33:24 sigma kernel: [ 1250.855130] sd 5:0:0:0: [sda] tag#30 Add.
Sense: Unrecovered read error - auto reallocate failed
Dec 23 22:33:24 sigma kernel: [ 1250.855135] sd 5:0:0:0: [sda] tag#30 CDB:
Read(10) 28 00 01 2b 96 10 00 00 08 00


The drive answers to an SCSI READ command from the computer that its
storage medium caused an error. No problem outside the drive should
be able to cause this.



Assuming a conventional desktop environment with no extremes or events, 
agreed.  But, I would still test the power supply, test the memory, run 
a long SMART test, and post the complete SMART report.  If the SMART 
overall-health self-assessment test result says "FAIL", then recycle the 
drive.  But if the result is "PASSED", then I would consider keeping it. 
 In any case, I would get more drives and set up RAID.



David

Re: qmail package in bullseye

[황병희]

Dan Ritter  writes:

> [...]
> In particular, Debian has the mailfront package, which is Bruce
> Guenter's qmail-compatible set of tools. From the description:
>
>   It contains complete SMTP, QMQP, QMTP, and POP3 front-ends as well as
>   an authentication module for IMAP.  The mail delivery front-ends also
>   contain internal address filtering features. 
>
>   Two SMTP back-ends are provided.  One delivers mail to qmail-queue,
>   mimicking most of the behavior of qmail-smtpd, with the addition of
>   support for SMTP AUTH.
>
> This is most likely your best path forward. 

Thanks Dan!

Sincerely, QMTP fan Byung-Hee

Re: doas 101 question

[David Robert Newman]

On 12/18/21 7:08 AM, Greg Wooledge wrote:


On Fri, Dec 17, 2021 at 09:20:59PM -0800, David Newman wrote:

Thanks for this. I get similar results where doas shows root's PATH -- but I
cannot execute a file called '/usr/local/sbin/s', which is owned by
root:root and has 0750 permissions, unless I specify the full path:

dnewman@coppi:~$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dnewman@coppi:~$ cat /etc/doas.conf
permit nopass setenv {
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin } dnewman
dnewman@coppi:~$ doas env | grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
dnewman@coppi:~$ doas s mailman3
doas: s: command not found
dnewman@coppi:~$ doas /usr/local/sbin/s mailman3
● mailman3.service - GNU Mailing List Manager
..

Same here, and it's not the permissions that are the issue.

unicorn:~$ PATH=/usr/local/bin:/usr/bin:/bin
unicorn:~$ type fdisk
bash: type: fdisk: not found
unicorn:~$ doas fdisk -l | head -n2
doas (greg@unicorn) password:
doas: fdisk: command not found
unicorn:~$ doas /sbin/fdisk -l | head -n2
doas (greg@unicorn) password:
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: TOSHIBA DT01ACA1

Looks like doas performs the search for the command *before* it sets
the environment.  You'd need to petition the developers to make a change
to the program's behavior in order to get what you want.  Most likely
this would need to be argued upstream, as I cannot imagine Debian writing
a local patch for that.  Not in a setuid program like this, and not after
the bullshit they pulled with su in buster.


I asked doas author Ted Unangst about this. His reply:


Sorry, only very limited env replacement can be done in setenv. root's 
environment isn't available before the switch.


Ergo, it is just as you suspected. This isn't an issue with OpenBSD 
because regular users's PATHs already include sbin directories. It is an 
issue with Debian because (a) a regular user's PATH doesn't include sbin 
directories and (b) the change in su behavior awhile back restricted 
access to some root privileges. It's not an issue with sudo, but for 
various reasons I'm more comfortable using doas.


My workaround was to add aliases for a few commands to my .bashrc file, 
e.g. (but not a real example):


alias ua='doas /usr/sbin/useradd'

Thanks for the sanity check.

dn