Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Jonathan Chung]

Hi, 

I think that the core problem which led to this also was on GRPCs side.
They should not tell users to compile their library but rather point
them to install it from their distros' packet manager
(https://grpc.io/docs/languages/cpp/quickstart/#install-grpc) if
possible. I will try to do the switch tonight as I just use GRPC as
library in a project and don't need to change anything in the GRPC
source.

Have a nice day,

Jonathan Chung

Am Mittwoch, dem 03.04.2024 um 08:35 +0200 schrieb Thomas Schmitt:
> Hi,
> 
> Chung  Jonathan wrote:
> > Yes, I think the local fix is the way to go.
> 
> I wrote:
> > > (You forgot to Cc: debian-user@lists.debian.org.
> > > Consider to send your mail to the list address, too. I too would
> > > then
> > > resend my following reply to the list.)
> 
> Since my "following reply" is quoted in Jonathan Chung's reply to the
> list
> i don't have to resend it. (I gave my opinion that the problem is not
> a
> bug in the context of Debian 12 or 13 and pointed to
> https://wiki.debian.org/BuildingTutorial for a private fix of the
> problem.)
> 
> 
> Jeffrey Walton wrote:
> > Your problem is one that plagues Linux. You compile and link
> > against
> > one version of a library, and then you runtime link against another
> > version.
> 
> This should not be a problem with a well maintained library which
> cares
> to stay ABI compatible with its older releases.
> In the present case it was a bug in the loading program pigz which
> prevented zlib from being usable.
> 
> 
> > I consider it a
> > security bug since essentially random libraries are being loaded at
> > runtime.
> > To fix the problem yourself, add an RPATH to your LDFLAGS when
> > building your program:
> >     -Wl,-rpath=/path/to/expected/libz -Wl,--enable-new-dtags
> 
> Well, this is nearly as unflexible as static compilation but does not
> seem to prevent the use of a replaced library at the given path.
> 
> Using .so files has its advantages and disadvantages. For a distro
> the
> advantage (without the pigz bug) is that customers of different
> versions
> of a library can be consolidated to using the newest available
> version.
> An advantage for the user is that bugs in a library can be fixed
> without
> the need for re-building all its customers.
> 
> 
> Have a nice day :)
> 
> Thomas
> 

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Thomas Schmitt]

Hi,

Chung  Jonathan wrote:
> Yes, I think the local fix is the way to go.

I wrote:
> > (You forgot to Cc: debian-user@lists.debian.org.
> > Consider to send your mail to the list address, too. I too would then
> > resend my following reply to the list.)

Since my "following reply" is quoted in Jonathan Chung's reply to the list
i don't have to resend it. (I gave my opinion that the problem is not a
bug in the context of Debian 12 or 13 and pointed to
https://wiki.debian.org/BuildingTutorial for a private fix of the problem.)


Jeffrey Walton wrote:
> Your problem is one that plagues Linux. You compile and link against
> one version of a library, and then you runtime link against another
> version.

This should not be a problem with a well maintained library which cares
to stay ABI compatible with its older releases.
In the present case it was a bug in the loading program pigz which
prevented zlib from being usable.


> I consider it a
> security bug since essentially random libraries are being loaded at
> runtime.
> To fix the problem yourself, add an RPATH to your LDFLAGS when
> building your program:
> -Wl,-rpath=/path/to/expected/libz -Wl,--enable-new-dtags

Well, this is nearly as unflexible as static compilation but does not
seem to prevent the use of a replaced library at the given path.

Using .so files has its advantages and disadvantages. For a distro the
advantage (without the pigz bug) is that customers of different versions
of a library can be consolidated to using the newest available version.
An advantage for the user is that bugs in a library can be fixed without
the need for re-building all its customers.


Have a nice day :)

Thomas

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Greg Wooledge]

On Tue, Apr 02, 2024 at 06:34:43PM -0400, Jeffrey Walton wrote:
> On Tue, Apr 2, 2024 at 6:24 PM Chung Jonathan  wrote:
> >
> > Dear Franco Martelli, dear Thomas Schmitt,
> >
> > Sorry for the potential duplication. This mail should now also go to the 
> > list.
> >
> > I believe I found the problem which was on my side. I do have libz.so.1.3, 
> > since I manually compiled grpc on my machine and this also uses a newer 
> > version of zlib appearently. So this is not a Debian problem but rather 
> > specific to my setup. A clean install in a VM indeed works as expected.
> > Do you still think a bug report is worth it?
> 
> Your problem is one that plagues Linux. You compile and link against
> one version of a library, and then you runtime link against another
> version. This should have been fixed for users a long time ago, but
> the folks responsible leave users to suffer it. I consider it a
> security bug since essentially random libraries are being loaded at
> runtime.
> 
> To fix the problem yourself, add an RPATH to your LDFLAGS when
> building your program:
> 
> -Wl,-rpath=/path/to/expected/libz -Wl,--enable-new-dtags
> 
> The loader will encounter the RPATH when loading your executable, and
> load the correct library for your program.

I've run into a variant of this issue myself.  I had compiled an
upstream version of Tcl, which builds a shared library named libtcl8.6.so
in the lib/ subdirectory of the --prefix used for ./configure, where
the default value of --prefix is /usr/local.

This places the shared library in /usr/local/lib which happens to be in
the default set of paths used by ldconfig and ld.so.  Which in turn
means that the locally built library gets used when running Debian's
packaged version of Tcl, taking priority over the version installed in
/usr/lib/x86_64-linux-gnu/ or whatver arch-specific directory is used.

In my case, the solution was to build my local version of Tcl with a
different --prefix.  Then there's nothing dropped into /usr/local/lib
and there's no conflict with the system's packages.

Of course, this is a particularly subtle problem that most users are not
going to be aware of.  It's specific to packages that build part of
themselves as a shared library, which immediately makes most programs
immune to it.  But when it *does* affect you, it can be tricky to
figure out what's happening.

It sounds like the OP's pigz issue was of a similar nature.  If this is
the case, then filing a Debian bug report isn't going to be helpful,
unless it's done as a sort of documentation for anyone else who runs
into the same problem in the future.

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Jeffrey Walton]

On Tue, Apr 2, 2024 at 6:24 PM Chung Jonathan  wrote:
>
> Dear Franco Martelli, dear Thomas Schmitt,
>
> Sorry for the potential duplication. This mail should now also go to the list.
>
> I believe I found the problem which was on my side. I do have libz.so.1.3, 
> since I manually compiled grpc on my machine and this also uses a newer 
> version of zlib appearently. So this is not a Debian problem but rather 
> specific to my setup. A clean install in a VM indeed works as expected.
> Do you still think a bug report is worth it?

Your problem is one that plagues Linux. You compile and link against
one version of a library, and then you runtime link against another
version. This should have been fixed for users a long time ago, but
the folks responsible leave users to suffer it. I consider it a
security bug since essentially random libraries are being loaded at
runtime.

To fix the problem yourself, add an RPATH to your LDFLAGS when
building your program:

-Wl,-rpath=/path/to/expected/libz -Wl,--enable-new-dtags

The loader will encounter the RPATH when loading your executable, and
load the correct library for your program.

Jeff

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Chung Jonathan]

Dear Franco Martelli, dear Thomas Schmitt,

Sorry for the potential duplication. This mail should now also go to the list.

I believe I found the problem which was on my side. I do have libz.so.1.3, 
since I manually compiled grpc on my machine and this also uses a newer version 
of zlib appearently. So this is not a Debian problem but rather specific to my 
setup. A clean install in a VM indeed works as expected.
Do you still think a bug report is worth it?

Thanks for your prompt responses,

Jonathan Chung

Am 02.04.2024 um 21:37 schrieb Chung Jonathan :

Dear Franco Martelli, dear Thomas Schmitt,

Yes, /etc/debian_version reports 12.5. However, as I have the docker sources as 
external repository those might have introduced an update to zlib. I will try 
to narrow it down and then open a subsequent bug report - possibly on a clean 
VM too.

The error first occurred as I installed a docker image. However, pigz --version 
also gave this error.

Thank you for pointing me to the correct directions,

Jonathan Chung

Am 02.04.2024 um 21:07 schrieb Franco Martelli :
On 02/04/24 at 10:27, Jonathan Chung wrote:
Dear sir or madam,
I'm new with Debian bug reporting and thus need some help with that.
pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
upstream https://github.com/madler/pigz/issues/111
Installing the version from sid resolves the issue which is clearly not
optimal. I think the fix should be backported.
Can someone help me to file a bug report?

To file a bug report use "reportbug pigz" and answer the questions… but I use 
regularly "pigz" in my backup scripts and I didn't notice nothing wrong ?_?
My installed version is:

~$ dpkg -l | grep pigz
ii  pigz 2.6-1  
   amd64Parallel Implementation of GZip

I just tested it and I've nothing to report:

~$ tar tf frankbck2.tgz --use-compress-program=pigz >/dev/null
~$ echo $?
0

Are you sure you are using Debian 12.5 ?

Kind regards.

--
Franco Martelli

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Chung Jonathan]

Dear Thomas Schmitt,

Yes, I think the local fix is the way to go. Probably even getting rid of the 
source of this, my manual GRPC install and replacing it with libgrpc++-dev. But 
that’s outside of this issue.

Yours,
Jonathan Chung

Am 02.04.2024 um 23:34 schrieb Thomas Schmitt :

Hi,

(You forgot to Cc: debian-user@lists.debian.org.
Consider to send your mail to the list address, too. I too would then
resend my following reply to the list.)

Chung  Jonathan wrote:
I do have libz.so.1.3,
since I manually compiled grpc on my machine and this also uses a newer
version of zlib appearently. [...]
Do you still think a bug report is worth it?

Rather not.

The original combination of pigz and zlib works in Debian 12. So it's
not a bug in that context.
The fact that it hampers upgrade to younger zlib is already addressed
by the version of pigz in "testing". So in the context of Debian 13 it
will be no bug either.

This leaves only the possibility to really ask for a backport for the
new feature that one can upgrade zlib before Debian offers it. But the
desired use case is near to the topic of "Frankendebian":
 https://wiki.debian.org/DontBreakDebian


If in urgent need for a fix, i expect that you would get more lucky by
patching the "stable" pigz package for your local use according to
 https://wiki.debian.org/BuildingTutorial
(patching is done in
 https://wiki.debian.org/BuildingTutorial#Edit_the_source_code
and as usual in Debian, there are more ways than this one to do it ...)


Have a nice day :)

Thomas

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Chung Jonathan]

Dear Franco Martelli, dear Thomas Schmitt,

Yes, /etc/debian_version reports 12.5. However, as I have the docker sources as 
external repository those might have introduced an update to zlib. I will try 
to narrow it down and then open a subsequent bug report - possibly on a clean 
VM too. 

The error first occurred as I installed a docker image. However, pigz --version 
also gave this error. 

Thank you for pointing me to the correct directions,

Jonathan Chung

> Am 02.04.2024 um 21:07 schrieb Franco Martelli :
> On 02/04/24 at 10:27, Jonathan Chung wrote:
>> Dear sir or madam,
>> I'm new with Debian bug reporting and thus need some help with that.
>> pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
>> upstream https://github.com/madler/pigz/issues/111
>> Installing the version from sid resolves the issue which is clearly not
>> optimal. I think the fix should be backported.
>> Can someone help me to file a bug report?
> 
> To file a bug report use "reportbug pigz" and answer the questions… but I use 
> regularly "pigz" in my backup scripts and I didn't notice nothing wrong ?_?
> My installed version is:
> 
> ~$ dpkg -l | grep pigz
> ii  pigz 2.6-1
>  amd64Parallel Implementation of GZip
> 
> I just tested it and I've nothing to report:
> 
> ~$ tar tf frankbck2.tgz --use-compress-program=pigz >/dev/null
> ~$ echo $?
> 0
> 
> Are you sure you are using Debian 12.5 ?
> 
> Kind regards.
> 
> --
> Franco Martelli

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Franco Martelli]

On 02/04/24 at 10:27, Jonathan Chung wrote:

Dear sir or madam,

I'm new with Debian bug reporting and thus need some help with that.
pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
upstream https://github.com/madler/pigz/issues/111

Installing the version from sid resolves the issue which is clearly not
optimal. I think the fix should be backported.

Can someone help me to file a bug report?



To file a bug report use "reportbug pigz" and answer the questions… but 
I use regularly "pigz" in my backup scripts and I didn't notice nothing 
wrong ?_?

My installed version is:

~$ dpkg -l | grep pigz
ii  pigz 2.6-1 
amd64Parallel Implementation of GZip


I just tested it and I've nothing to report:

~$ tar tf frankbck2.tgz --use-compress-program=pigz >/dev/null
~$ echo $?
0

Are you sure you are using Debian 12.5 ?

Kind regards.

--
Franco Martelli

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Charles Curley]

On Tue, 2 Apr 2024 10:27:33 +0200
Jonathan Chung  wrote:

> I'm new with Debian bug reporting and thus need some help with that.
> pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
> upstream https://github.com/madler/pigz/issues/111

Are you sure this is a bug and not a problem with your system? I am
also using pigz 2.6-1 on Debian 12.5, and I don't see it.

charles@hawk:~$ pigz --version
pigz 2.6
charles@hawk:~$ pre zlib pigz
pigz2.6-1   amd64
zlib1g  1:1.2.13.dfsg-1 amd64
zlib1g-dev  1:1.2.13.dfsg-1 amd64
charles@hawk:~$

What version of zlib are you running?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Thomas Schmitt]

Hi,

Jonathan Chung wrote:
> > pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
> > upstream https://github.com/madler/pigz/issues/111
> > Installing the version from sid resolves the issue which is clearly not
> > optimal. I think the fix should be backported.
> > Can someone help me to file a bug report?

Michael Kjörling wrote:
> https://www.debian.org/Bugs/Reporting

This covers the question "how", but not "what".
So my two cents:

"Backported" is probably the wrong wish.
  https://backports.debian.org/Contribute/
says:
  "Backports are about additional features that are only offered in a
   new version, not a replacement for getting fixes into stable - use
   stable-updates for that."

That would probably mean to patch the existing pigz package in Debian 12
by the upstream remedy
  "Make pigz compatible with two-component zlib version numbers. "
  https://github.com/madler/pigz/commit/907ca0763be4547a9b0cce8c105721748814974

pigz.c:
@@ -1333,7 +1333,7 @@ local long zlib_vernum(void) {
}
ver++;
} while (left);
-   return left < 2 ? num << (left << 2) : -1;
+   return left < 3 ? num << (left << 2) : -1;
 }

 // -- check value combination routines for parallel calculation --


The new state can already be seen in
  https://sources.debian.org/src/pigz/2.8-1/pigz.c/#L1339
The old state is in
  https://sources.debian.org/src/pigz/2.6-1/pigz.c/#L1317
But there the "// -- check ..." comment is missing in favor of a line
  #ifndef NOTHREAD
So a patch proposal would need some minor hand work.


There remains the question, though, why you run into zlib-1.3 on a
Debian "stable" system where the zlib version is "1:1.2.13.dfsg-1":
  https://tracker.debian.org/pkg/zlib


Have a nice day :)

Thomas

Re: How to file a Debian bug report? was: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Michael Kjörling]

On 2 Apr 2024 10:27 +0200, from jch...@student.ethz.ch (Jonathan Chung):
> Can someone help me to file a bug report?

https://www.debian.org/Bugs/Reporting

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

[Jonathan Chung]

Dear sir or madam,

I'm new with Debian bug reporting and thus need some help with that.
pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
upstream https://github.com/madler/pigz/issues/111

Installing the version from sid resolves the issue which is clearly not
optimal. I think the fix should be backported.

Can someone help me to file a bug report?

Re: error message for sda

[David Christensen]

On 6/6/22 22:17, Felix Miata wrote:

Bob Crochelt composed on 2022-06-06 17:02 (UTC-0700):


Running updated Debian on a pretty old iMac.  Seeing messages that complain 
about sda, only drive in the system:



190 Airflow_Temperature_Cel 0x0022   045   037   045Old_age   Always   
FAILING_NOW 55 (255 255 60 26 0)
194 Temperature_Celsius 0x0022   055   063   000Old_age   Always   
-   55 (0 19 0 0 0)
  
Old iMacs are hot running. 



Yikes!



Whether 55 is actually too hot for the drive really IMO should be checked with 
its manufacturer.



+1


Some of my drives report "Min/Max Temperature Limit":

HGST-40/70 Celsius
Maxtor  0/71 Celsius
Samsung 0/70 Celsius
Seagate 10/60 Celsius
Toshiba 10/60 Celsius
Western Digital -40/70 Celsius


Does anyone know the SMART definition for "Min/Max Temperature Limit"? 
Notably -- is it operational temperature limits, or non-operational limits?



David

Re: error message for sda

[Felix Miata]

Bob Crochelt composed on 2022-06-06 17:02 (UTC-0700):

> Running updated Debian on a pretty old iMac.  Seeing messages that complain 
> about sda, only drive in the system:

> 190 Airflow_Temperature_Cel 0x0022   045   037   045Old_age   Always   
> FAILING_NOW 55 (255 255 60 26 0)
> 194 Temperature_Celsius 0x0022   055   063   000Old_age   Always  
>  -   55 (0 19 0 0 0)
 
Old iMacs are hot running. Whether 55 is actually too hot for the drive
really IMO should be checked with its manufacturer.

# pinxi -Ma
Machine:
  Type: Desktop System: Apple product: iMac7,1 v: 1.0 serial: QP7440XDX89
Chassis: type: 13 v: Mac-F42386C8 serial: QP7440XDX89
  Mobo: Apple model: Mac-F42386C8 v: PVT serial: 1 UEFI: Apple
v: IM71.88Z.007A.B03.0803051705 date: 03/05/08
# inxi -D
Drives:
  Local Storage: total: 931.51 GiB used: 69.24 GiB (7.4%)
  ID-1: /dev/sda vendor: Seagate model: ST1000DM003-1SB10C size: 931.51 GiB
# smartctl -x /dev/sda | grep flow
190 Airflow_Temperature_Cel -O---K   069   043   040-31 (Min/Max 25/31)
...
# smartctl -x /dev/sda | grep e_Cel
190 Airflow_Temperature_Cel -O---K   046   043   040-54 (Min/Max 25/54)
194 Temperature_Celsius -O---K   054   021   000-54 (0 21 0 0 0)
# uptime
 00:51:35  up   0:50,  2 users,  load average: 0.07, 0.02, 0.00
# smartctl -x /dev/sda | grep emp
190 Airflow_Temperature_Cel -O---K   045   043   040-55 (Min/Max 25/55)
194 Temperature_Celsius -O---K   055   021   000-55 (0 21 0 0 0)
Current Temperature:55 Celsius
Power Cycle Min/Max Temperature: 26/55 Celsius
LifetimeMin/Max Temperature: 22/57 Celsius
Under/Over Temperature Limit Count:   0/0
0x03  0x028  4   0  ---  Read Recovery Attempts
0x05  =  =   =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1  55  ---  Current Temperature
0x05  0x010  1  46  ---  Average Short Term Temperature
0x05  0x018  1  48  ---  Average Long Term Temperature
0x05  0x020  1  57  ---  Highest Temperature
0x05  0x028  1  26  ---  Lowest Temperature
0x05  0x030  1  55  ---  Highest Average Short Term Temperature
0x05  0x038  1  43  ---  Lowest Average Short Term Temperature
0x05  0x040  1  50  ---  Highest Average Long Term Temperature
0x05  0x048  1  47  ---  Lowest Average Long Term Temperature
0x05  0x050  4   10240  ---  Time in Over-Temperature
0x05  0x058  1  55  ---  Specified Maximum Operating Temperature
0x05  0x060  4   0  ---  Time in Under-Temperature
0x05  0x068  1  13  ---  Specified Minimum Operating Temperature

# smartctl -x /dev/sda | grep e_Cel
190 Airflow_Temperature_Cel -O---K   044   043   040-56 (Min/Max 25/56)
194 Temperature_Celsius -O---K   056   021   000-56 (0 21 0 0 0)
# uptime
 01:01:58  up   1:00,  2 users,  load average: 0.02, 0.04, 0.00
# uptime
 01:15:10  up   1:13,  2 users,  load average: 0.00, 0.01, 0.00
# smartctl -x /dev/sda | grep e_Cel
190 Airflow_Temperature_Cel -O---K   043   043   040-57 (Min/Max 25/57)
194 Temperature_Celsius -O---K   057   021   000-57 (0 21 0 0 0)

10240 "Time in Over-Temperature" on this iMac is probably from its condition
when acquired. Its OEM HD was dead, and its cooling system was clogged.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: error message for sda

[David Christensen]

On 6/6/22 20:27, David wrote:

On Tue, 7 Jun 2022 at 10:03, Bob Crochelt  wrote:


   9 Power_On_Hours  0x0032   045   045   000Old_age   Always   
-   48690


Assuming the raw value is hours, that's about 5.5 years of power on time.


190 Airflow_Temperature_Cel 0x0022   045   037   045Old_age   Always   
FAILING_NOW 55 (255 255 60 26 0)
194 Temperature_Celsius 0x0022   055   063   000Old_age   Always   
-   55 (0 19 0 0 0)


Assuming the raw value is Celsius, that's somewhat warmer than ideal.
I would be looking at the airflow inside the machine and removing any dust.


I think this means its time to replace the hard drive,  any other thoughts?


That depends on your appetite for risk. I don't see anything else alarming
in the data you provided. But, that's because I am accustomed to having
several layers of backup available, so I can tolerate a high level of risk.



+1



Even when a hard drive is brand new, I make sure to have sufficient backup
copies of important data that I can recover whatever is important to me
if the drive fails.



+1


I experienced an enterprise HDD fail in under 1 month.  But, it was a 
factory sealed, new, previous generation model that likely sat on the 
shelf for a few years.



I have read, and have been told by knowledgeable disk drive manufacturer 
engineers, that a HDD sitting on a shelf for long periods is more likely 
to fail than a HDD idling for the same period.  To keep a drive working, 
keep it powered and spinning.



I am starting think that some combination of manufacturing date, 
Power_On_Hours, Total_LBAs_Written, and Total_LBAs_Read might predict 
eminent failure.




I have several personal machines and I run my hard drives to failure.
For example, the primary hard drive in this machine started failing self
test, due to read errors, at around 17000 hours. I did some recovery procedure
to remap the problem sectors, and the drive is now at 28000 hours
with no further problems.



+1


David

Re: error message for sda

[David]

On Tue, 7 Jun 2022 at 10:03, Bob Crochelt  wrote:

>   9 Power_On_Hours  0x0032   045   045   000Old_age   Always  
>  -   48690

Assuming the raw value is hours, that's about 5.5 years of power on time.

> 190 Airflow_Temperature_Cel 0x0022   045   037   045Old_age   Always   
> FAILING_NOW 55 (255 255 60 26 0)
> 194 Temperature_Celsius 0x0022   055   063   000Old_age   Always  
>  -   55 (0 19 0 0 0)

Assuming the raw value is Celsius, that's somewhat warmer than ideal.
I would be looking at the airflow inside the machine and removing any dust.

> I think this means its time to replace the hard drive,  any other thoughts?

That depends on your appetite for risk. I don't see anything else alarming
in the data you provided. But, that's because I am accustomed to having
several layers of backup available, so I can tolerate a high level of risk.

Even when a hard drive is brand new, I make sure to have sufficient backup
copies of important data that I can recover whatever is important to me
if the drive fails.

I have several personal machines and I run my hard drives to failure.
For example, the primary hard drive in this machine started failing self
test, due to read errors, at around 17000 hours. I did some recovery procedure
to remap the problem sectors, and the drive is now at 28000 hours
with no further problems.

Re: error message for sda

[David Christensen]

On 6/6/22 17:02, Bob Crochelt wrote:

Hi:
Running updated Debian on a pretty old iMac.  Seeing messages that complain 
about sda, only drive in the system:


> I think this means its time to replace the hard drive,  any other 
thoughts?



Interpreting smartctl output is tough.  Try to find manufacturer 
documentation that describes the SMART attributes, etc., for that 
specific make and model.



The most important SMART report line to look at is:

SMART overall-health self-assessment test result: PASSED


Please run the following command:

# smartctl -t long 


Run the following command until the test is done:

# smartctl -x '


Please post the complete, final SMART report.  There is much more 
information than you have posted below.




SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
   1 Raw_Read_Error_Rate 0x000e   100   253   006Old_age   Always   
-   0
   3 Spin_Up_Time0x0003   095   093   000Pre-fail  Always   
-   0
   4 Start_Stop_Count0x0032   093   093   020Old_age   Always   
-   7818
   5 Reallocated_Sector_Ct   0x0033   100   100   036Pre-fail  Always   
-   0
   7 Seek_Error_Rate 0x000f   087   060   030Pre-fail  Always   
-   521708297
   9 Power_On_Hours  0x0032   045   045   000Old_age   Always   
-   48690



I have an HDD with Power_On_Hours of 28k+.  It works.



10 Spin_Retry_Count0x0013   100   100   097Pre-fail  Always   - 
  0
12 Power_Cycle_Count   0x0032   098   098   020Old_age   Always   - 
  2325
187 Reported_Uncorrect  0x0032   100   100   000Old_age   Always   
-   0
189 High_Fly_Writes 0x003a   100   100   000Old_age   Always   
-   0
190 Airflow_Temperature_Cel 0x0022   045   037   045Old_age   Always   
FAILING_NOW 55 (255 255 60 26 0)



That looks like your drive is overheating.  Check cleanliness (e.g. 
dust) and cooling (fans, airflow restriction/ blockage).  If those are 
good, swap the drive with a known good drive, run the above commands, 
and post the results.




194 Temperature_Celsius 0x0022   055   063   000Old_age   Always   
-   55 (0 19 0 0 0)
195 Hardware_ECC_Recovered  0x001a   056   047   000Old_age   Always   
-   44745763



I have drives with worse numbers for Hardware_ECC_Recovered.  They work.



197 Current_Pending_Sector  0x0012   100   100   000Old_age   Always   
-   0
198 Offline_Uncorrectable   0x0010   100   100   000Old_age   Offline  
-   0
199 UDMA_CRC_Error_Count0x003e   200   200   000Old_age   Always   
-   0
200 Multi_Zone_Error_Rate   0x   100   253   000Old_age   Offline  
-   0
202 Data_Address_Mark_Errs  0x0032   100   253   000Old_age   Always   
-   0



David

error message for sda

[Bob Crochelt]

Hi:
Running updated Debian on a pretty old iMac.  Seeing messages that complain 
about sda, only drive in the system:

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x000e   100   253   006Old_age   Always   
-   0
  3 Spin_Up_Time0x0003   095   093   000Pre-fail  Always   
-   0
  4 Start_Stop_Count0x0032   093   093   020Old_age   Always   
-   7818
  5 Reallocated_Sector_Ct   0x0033   100   100   036Pre-fail  Always   
-   0
  7 Seek_Error_Rate 0x000f   087   060   030Pre-fail  Always   
-   521708297
  9 Power_On_Hours  0x0032   045   045   000Old_age   Always   
-   48690
10 Spin_Retry_Count0x0013   100   100   097Pre-fail  Always   - 
  0
12 Power_Cycle_Count   0x0032   098   098   020Old_age   Always   - 
  2325
187 Reported_Uncorrect  0x0032   100   100   000Old_age   Always   
-   0
189 High_Fly_Writes 0x003a   100   100   000Old_age   Always   
-   0
190 Airflow_Temperature_Cel 0x0022   045   037   045Old_age   Always   
FAILING_NOW 55 (255 255 60 26 0)
194 Temperature_Celsius 0x0022   055   063   000Old_age   Always   
-   55 (0 19 0 0 0)
195 Hardware_ECC_Recovered  0x001a   056   047   000Old_age   Always   
-   44745763
197 Current_Pending_Sector  0x0012   100   100   000Old_age   Always   
-   0
198 Offline_Uncorrectable   0x0010   100   100   000Old_age   Offline  
-   0
199 UDMA_CRC_Error_Count0x003e   200   200   000Old_age   Always   
-   0
200 Multi_Zone_Error_Rate   0x   100   253   000Old_age   Offline  
-   0
202 Data_Address_Mark_Errs  0x0032   100   253   000Old_age   Always   
-   0

I think this means its time to replace the hard drive,  any other thoughts?

thanks in advance, 

If more appropriate for another listh please advise.

Bob Crochelt

"Failed unmounting /var/cache" error message when shutting down

[Jorge P. de Morais Neto]

Hi.  This problem is some months old, and I have sent a similar message
on 20 Jan 2022 11:57:35 (UTC).  Since then I have slightly simplified my
Btrfs subvolume layout but the problem remains.

When I shutdown or halt my laptop, I get error messages like:

[FAILED] Failed unmounting /var/cache.
[⋮]
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Reached target Final Step.
 Starting halt...

My Nextcloud public folder has a screenshot from January:
https://cloud.disroot.org/s/MFaEoozaHHJjtbs

I suppose these Btrfs subvolumes do still get unmounted cleanly before
shutdown, because:
1. The success message "[  OK  ] Reached target Unmount All Filesystems."
2. When the laptop turns back on, I don't see any message about unclean
   filesystem.
3. In the output of ~smartctl -a /dev/nvme0n1~, the field "Unsafe
   Shutdowns" dos not increase.

Am I thinking correctly, and can I safely disregard those error messages?

For reference, I have attached the relevant excerpt from /etc/fstab

Kind regards
LABEL=SSD /   btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@rootfs   0   0
LABEL=SSD /var/backupsbtrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@var-bkp  0   0
LABEL=SSD /var/cache  btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@var-cch  0   0
LABEL=SSD /var/spool  btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@var-spl  0   0
LABEL=SSD /var/tmpbtrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@var-tmp  0   0
LABEL=HDD /var/logbtrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@var-log  0   0
LABEL=HDD /var/cache/apt/archives btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@apt-arch 0 0
LABEL=HDD /root   btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@~root0   0
LABEL=SSD /home   btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@home 0   0
LABEL=SSD /home/cache btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@home-cch 0   0
LABEL=HDD /home-HDD   btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@home 0   0
LABEL=HDD /home-HDD/cache btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@home-cch 0   0
LABEL=SSD /gnubtrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@guix-gnu 0   0
LABEL=SSD /var/guix   btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@guix-var 0   0
LABEL=SSD /usr/local btrfs 
noatime,space_cache=v2,compress=zstd:12,subvol=@usr-local   0   0
UUID=9550-C451  /boot/efi   vfatumask=0077  0   1
LABEL=HDD-swap none  swap  sw   
0   0

-- 
- Many people hate injustice but few check the facts; this causes more
  injustice.  Ask me about 
- I am Brazilian.  I hope my English is correct and I welcome feedback.
- Free Software Supporter: https://www.fsf.org/free-software-supporter
- If an email of mine arrives at your spam box, please notify me.

Re: unknown error message [Solved]

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


‐‐‐ Original Message ‐‐‐
On Friday, February 18, 2022 1:29 PM, Greg Wooledge  wrote:

> I believe I've also heard
> of this problem being triggered by gparted. Have you used gparted in
> the last few days?

Bingo.

I'd left gparted running after doing something to something a few days ago, and 
stopping it made apt work again.  Now the question becomes: What makes the web 
server fail going to just one of eleventy million sites when gparted is 
running?  I'm not interested enough to try to understand the 
gparted/kernel/Firefox/HTML source, but a maintainer might more interested than 
a mere user.

Thanks to all who answered.

--
Glenn English
-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAGBQJiEDKMACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDJ/9ggAx+/GfNGBDaKVH7OsW/Ib9fjyYfYGLLTvK0qPlfSZUT4oeMrc
+ROzeH0bz9thyZNDFWED3qiPf1uUYK4C4KUWPPhj6SmJB2M3SBmmVkOJwDV2
ws4NDVX2VMvGfH6u76tOAWUr5PAdwCrHIpssU02IHuDMDOjA8Uagh/E48qqB
MKJFYyyHB4bXRt3Tbov0IQY/Vo6n2Sn8FHUDhUci2uSM95GxCtiyvotACO7Q
edYJM7/oVlIuZY6qCiCLOn2/7Hwaxt4xm5F3q9kgDwSSBcmuONlmU9u/bZ6y
/dKnw8Zw8XCH79DoIu9CbmdkqPXy4cQyR2+OwRZaH96QFbdWEkvrcg==
=zgtC
-END PGP SIGNATURE-

Re: unknown error message

[Greg Wooledge]

On Fri, Feb 18, 2022 at 07:17:44PM +, ghe2001 wrote:
> Does anybody know what:
> 
> Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked
> 
> means?  What is '.mount' and what does 'masked' mean?

It's not ".mount".  It's "-.mount".  Specifically, it's a
systemd.mount(5) unit created to represent the root (/) file system.
The / is converted to a - in the unit name.

> I looked on the web and found a discussion involving something called 
> "zynthian."  My log repeats the sentence several times -- from syslog and 
> daemon.

I see this error reported on a pretty regular basis, but there isn't
a single cause for it.  I've heard of *several* different possible
sources.

> It happens only when I 'apt update'

That rings a bell, but I don't remember the precise details.  Are you
a synaptic user, by chance?  It might be a synaptic thing, either because
synaptic is currently running, or because it broke something.

Or... it could be something entirely different.  I believe I've also heard
of this problem being triggered by gparted.  Have you used gparted in
the last few days?

If you can't find an answer with Google, try the standard troubleshooting
steps.  Read the logs, check the status of everything, etc.

systemctl status -- -.mountwould be a good starting point.  Mine
says:

unicorn:~$ systemctl status -- -.mount
● -.mount - Root Mount
 Loaded: loaded (/etc/fstab; generated)
 Active: active (mounted) since Fri 2022-02-04 07:12:29 EST; 2 weeks 0 days>
  Where: /
   What: /dev/sda7
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)

Warning: some journal files were not opened due to insufficient permissions.

Of course, running it as root would give additional details.

Re: unknown error message

[David Wright]

On Fri 18 Feb 2022 at 19:17:44 (+), ghe2001 wrote:
> Does anybody know what:
> 
> Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked
> 
> means?  What is '.mount' and what does 'masked' mean?
> 
> I looked on the web and found a discussion involving something called 
> "zynthian."  My log repeats the sentence several times -- from syslog and 
> daemon.
> 
> It happens only when I 'apt update' -- I get to all other websites with no 
> trouble (including Debian).  When I ssh to the computers on my LAN in the 
> next room, they both get to the mirrors (one Debian, the other is 
> RaspberryPi).  All my computers are running an updated Buster.
> 
> All was working until a few days ago.
> 
> The web browser is Firefox-esr.

man systemctl
man systemd.unit
etc

Cheers,
David.

unknown error message

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Does anybody know what:

Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked

means?  What is '.mount' and what does 'masked' mean?

I looked on the web and found a discussion involving something called 
"zynthian."  My log repeats the sentence several times -- from syslog and 
daemon.

It happens only when I 'apt update' -- I get to all other websites with no 
trouble (including Debian).  When I ssh to the computers on my LAN in the next 
room, they both get to the mirrors (one Debian, the other is RaspberryPi).  All 
my computers are running an updated Buster.

All was working until a few days ago.

The web browser is Firefox-esr.

--
Glenn English


-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAGBQJiD/DXACEJEObKK1bRaqt3FiEExEbtoeXBeE9fruv35sor
VtFqq3dpmwgA4DK7+9n5rNb91SgQmsm5Pelo0mR4RUawat8w3mU+tBUXgEW3
RyM/5eC/LfHxOMMLSpNzk2w/pK7BECfWvO2yoeSqL/E4n+fFJSZ+yIpCk1/J
BdUKdiOSathUd0EEy5C/GQMwkJFFNd7dXo2m2DFsPRIEtm58vxe08S2Yf41j
6fW5BbVt8KXgndMPicrHJLT5DHgo21l9U0fhOWSpZwgRkWE6Dfdx5HHpZa0t
WWU3vdfcX3/hNp0kNe+Z0OpbwkK84MfeFS6/A0HATTeI4yvAW6YkBNeDaP5p
96hglujB9/934hq3bHFjU0g8+FBHhd7HPPChZInMEFcBkRrPY0RT1w==
=dKC/
-END PGP SIGNATURE-

Re: RESOLVED: Synaptic error message

[Richard Owlett]

On 06/27/2021 05:37 PM, Brian the PERFECT wrote:
""

Re: RESOLVED: Synaptic error message

[Brian]

On Sun 27 Jun 2021 at 16:00:12 -0500, Richard Owlett wrote:

> On 06/27/2021 12:50 PM, Darac Marjal wrote:
> > 
> > On 26/06/2021 15:20, Richard Owlett wrote:
> > > I have a empty machine on which I've done a default install of
> > > Debian 10.7.0 with MATE as my desktop. As I intend later to install
> > > some non-Debian software I wanted a local repository. To have a known
> > > base to start from I extracted the contents of dvd1.iso to a local
> > > directory.
> > > 
> > > My sources.list references it as:
> > > > deb [ Trusted=yes ] file:home/richard/DVDs/dvd1/ buster main
> > > > contrib  non-free
> > > 
> > > In Synaptic when I do Edit->Reload Package Information it responds:
> > > > The repository 'file://home/richard/DVDs/dvd1 buster Release' is not
> > > > signed.
> > > 
> > > 
> > > https://html.duckduckgo.com/html?q=%2B%22synaptic%22%20%2B%22repository%22%20%2B%22not%20signed%22%20site%3Adebian.org
> > > gives no useful information.
> > > 
> > > What do I do?
> > > What should I have read?
> > 
> > "man sources.list" will give you the format of the "deb ..." line. In
> > particular, it will tell you that the command for setting a repository
> > to trusted is "trusted", rather than "Trusted". Computers can be a
> > little TOO literal at times.
> > 
> 
> That works. I had had it lowercase but I was also chasing some other error
> and the page of examples I was following had it upper case. One of those
> cases where it would be nice to have a larger variety of examples on the man
> page.

What need is there for examples when the manual is clarity itself??

Under

 THE DEB AND DEB-SRC TYPES: OPTIONS

sources.list(5) has

  •Trusted (trusted) is a tri-state value...

and

  For simplicity we list the deb822 field name and provide the one-line
  name in brackets.  

You are using the one-line format.

-- 
Brian.

RESOLVED: Synaptic error message

[Richard Owlett]

On 06/27/2021 12:50 PM, Darac Marjal wrote:


On 26/06/2021 15:20, Richard Owlett wrote:

I have a empty machine on which I've done a default install of
Debian 10.7.0 with MATE as my desktop. As I intend later to install
some non-Debian software I wanted a local repository. To have a known
base to start from I extracted the contents of dvd1.iso to a local
directory.

My sources.list references it as:

deb [ Trusted=yes ] file:home/richard/DVDs/dvd1/ buster main
contrib  non-free


In Synaptic when I do Edit->Reload Package Information it responds:

The repository 'file://home/richard/DVDs/dvd1 buster Release' is not
signed.



https://html.duckduckgo.com/html?q=%2B%22synaptic%22%20%2B%22repository%22%20%2B%22not%20signed%22%20site%3Adebian.org
gives no useful information.

What do I do?
What should I have read?


"man sources.list" will give you the format of the "deb ..." line. In
particular, it will tell you that the command for setting a repository
to trusted is "trusted", rather than "Trusted". Computers can be a
little TOO literal at times.



That works. I had had it lowercase but I was also chasing some other 
error and the page of examples I was following had it upper case. One of 
those cases where it would be nice to have a larger variety of examples 
on the man page.


*THANK YOU*!

Re: Synaptic error message

[Darac Marjal]

On 26/06/2021 15:20, Richard Owlett wrote:
> I have a empty machine on which I've done a default install of
> Debian 10.7.0 with MATE as my desktop. As I intend later to install
> some non-Debian software I wanted a local repository. To have a known
> base to start from I extracted the contents of dvd1.iso to a local
> directory.
>
> My sources.list references it as:
>> deb [ Trusted=yes ] file:home/richard/DVDs/dvd1/ buster main
>> contrib  non-free
>
> In Synaptic when I do Edit->Reload Package Information it responds:
>> The repository 'file://home/richard/DVDs/dvd1 buster Release' is not
>> signed.
>
>
> https://html.duckduckgo.com/html?q=%2B%22synaptic%22%20%2B%22repository%22%20%2B%22not%20signed%22%20site%3Adebian.org
> gives no useful information.
>
> What do I do?
> What should I have read?

"man sources.list" will give you the format of the "deb ..." line. In
particular, it will tell you that the command for setting a repository
to trusted is "trusted", rather than "Trusted". Computers can be a
little TOO literal at times.


> TIA
>
>



OpenPGP_signature
Description: OpenPGP digital signature

Re: Synaptic error message

[rhkramer]

On Sunday, June 27, 2021 04:27:19 AM Joe wrote:
> There is no 'digital', it's all analogue with a poor signal/noise ratio.

Interesting -- thanks!

Nothing new below this line.

> And no, I'm not kidding. Some of the more obscure digital faults turn
> out to require actually looking at the data with a (real) oscilloscope,
> where its analogue nature can usually be seen very clearly.
> 
> Reflections, jitter, eye height, these are all analogue issues. I once
> fixed a fault where a particular simple logic IC had to come from a
> particular manufacturer, and someone had fitted one of the same type
> number but from a different manufacturer, that had a different input
> impedance. Real bleeding-edge, state-of-the-art hardware, that was.

Re: Synaptic error message

[Joe]

On Sat, 26 Jun 2021 19:11:25 +0100
Brian  wrote:


> 
> A choice between analogue and digital? You really were well off. We
> had to train carrier pigeons to peck out a message with their beaks
> and we needed to be adept at semaphore. Drum skills were a must.
> 

There is no 'digital', it's all analogue with a poor signal/noise ratio.

And no, I'm not kidding. Some of the more obscure digital faults turn
out to require actually looking at the data with a (real) oscilloscope,
where its analogue nature can usually be seen very clearly.

Reflections, jitter, eye height, these are all analogue issues. I once
fixed a fault where a particular simple logic IC had to come from a
particular manufacturer, and someone had fitted one of the same type
number but from a different manufacturer, that had a different input
impedance. Real bleeding-edge, state-of-the-art hardware, that was.

-- 
Joe

Re: Synaptic error message

[Andrei POPESCU]

On Sb, 26 iun 21, 19:11:25, Brian wrote:
> On Sat 26 Jun 2021 at 10:46:22 -0500, Richard Owlett wrote:
> 
> > This group keeps reading _INTO_ my questions things that aren't there.
> 
> This group also continues to answer the same questions you have asked
> time and time before :) and received responses to. Be grateful (and
> graceful).

Sound like things that should be added to some FAQ, maybe even a special 
section dedicated to Richard's questions :p

If only there was such a place that any subscriber could easily edit :p

(because of Poe's law I feel compelled to mention this is meant to be an 
attempt at humour, though Richard's questions do qualify as "frequent")

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Synaptic error message

[Brian]

On Sat 26 Jun 2021 at 10:46:22 -0500, Richard Owlett wrote:

> This group keeps reading _INTO_ my questions things that aren't there.

This group also continues to answer the same questions you have asked
time and time before :) and received responses to. Be grateful (and
graceful).

> I'm in my eight decade and was introduced to computers as an engineering
> undergrad in early 60's, back when they had 12AX7's and 5U4's -- well before
> 8080's. In the 80's I was writing 8080/8085 assembler code for embedded
> systems. I did not get to really get to explore *PERSONAL* computing
> (excluding a KIM, P.E.T., and Z80 based S100 systems) until I retired.

You had computers in your early days? How fortunate! We had to make
do with an abacus. The lucky ones had one powered by the new-fangled
electricity stuff - two electrodes stuck into a lemon. Code was writen
by punching holes into paper with a knitting needle.

> Mantra du jour: "If retirement isn't for learning, what use is it!"

Education?

> Back in 70's I got a job with a large mini-computer manufacturer *BECAUSE* I
> had no interest in things "digital". My expertise was analog! Old-enough
> timers might recognize ML5-5 as a significant mail stop.

A choice between analogue and digital? You really were well off. We had
to train carrier pigeons to peck out a message with their beaks and we
needed to be adept at semaphore. Drum skills were a must.

-- 
Brian.

Re: Synaptic error message

[Andrew M.A. Cater]

On Sat, Jun 26, 2021 at 10:46:22AM -0500, Richard Owlett wrote:
> On 06/26/2021 10:11 AM, Andrew M.A. Cater wrote:
> > On Sat, Jun 26, 2021 at 09:20:33AM -0500, Richard Owlett wrote:
> > > I have a empty machine on which I've done a default install of
> > > Debian 10.7.0 with MATE as my desktop. As I intend later to install some
> > > non-Debian software I wanted a local repository. To have a known base to
> > > start from I extracted the contents of dvd1.iso to a local directory.
> > > 
> > > My sources.list references it as:
> > > > deb [ Trusted=yes ] file:home/richard/DVDs/dvd1/ buster main 
> > > > contrib  non-free
> > > 
> > > In Synaptic when I do Edit->Reload Package Information it responds:
> > > > The repository 'file://home/richard/DVDs/dvd1 buster Release' is not 
> > > > signed.
> > > 
> > > 
> > > https://html.duckduckgo.com/html?q=%2B%22synaptic%22%20%2B%22repository%22%20%2B%22not%20signed%22%20site%3Adebian.org
> > > gives no useful information.
> > > 
> > > What do I do?
> > > What should I have read?
> > > TIA
> > > 
> > > 
> > 
> > Richard:
> > 
> > Maybe earlier messages on -user ? DVDs aren't normally signed repositories.
> > 
> > Various folk have suggested to you how to mount DVDs correctly and how to
> > use apt-cdrom to add the contents to apt.
> > 
> > Take the DVD, mount it, use apt-cdrom to index the contents and go from
> > there?
> > 
> > Synaptic may not be ideal: you might find that your use cases may be
> > better served by apt/aptitude which may allow you to better see what
> > you're doing.
> 
> This group keeps reading _INTO_ my questions things that aren't there.
> I'm in my eight decade and was introduced to computers as an engineering
> undergrad in early 60's, back when they had 12AX7's and 5U4's -- well before
> 8080's. In the 80's I was writing 8080/8085 assembler code for embedded
> systems. I did not get to really get to explore *PERSONAL* computing
> (excluding a KIM, P.E.T., and Z80 based S100 systems) until I retired.
> 
> Mantra du jour: "If retirement isn't for learning, what use is it!"
> 
> Back in 70's I got a job with a large mini-computer manufacturer *BECAUSE* I
> had no interest in things "digital". My expertise was analog! Old-enough
> timers might recognize ML5-5 as a significant mail stop.
> 
> mutter mutter mut...
> 
12AX7 and 5U4 - sounds like some good tubes for an analog RF amplifier
if nothing else (says this radio amateur). Between you and Gene, we 
should perhaps have a master class :) 

apt-cdrom should really work for you. I have a virtual machine set up
which ONLY has a DVD 1 attached and no GUI yet. Installed on an expert
install and minimal. That's as close as I can get to what you seem to 
be talking about :)

All best, as ever,

Andy Cater
> 
> 

Re: Synaptic error message

[Richard Owlett]

On 06/26/2021 10:11 AM, Andrew M.A. Cater wrote:

On Sat, Jun 26, 2021 at 09:20:33AM -0500, Richard Owlett wrote:

I have a empty machine on which I've done a default install of
Debian 10.7.0 with MATE as my desktop. As I intend later to install some
non-Debian software I wanted a local repository. To have a known base to
start from I extracted the contents of dvd1.iso to a local directory.

My sources.list references it as:

deb [ Trusted=yes ] file:home/richard/DVDs/dvd1/ buster main contrib  
non-free


In Synaptic when I do Edit->Reload Package Information it responds:

The repository 'file://home/richard/DVDs/dvd1 buster Release' is not signed.



https://html.duckduckgo.com/html?q=%2B%22synaptic%22%20%2B%22repository%22%20%2B%22not%20signed%22%20site%3Adebian.org
gives no useful information.

What do I do?
What should I have read?
TIA




Richard:

Maybe earlier messages on -user ? DVDs aren't normally signed repositories.

Various folk have suggested to you how to mount DVDs correctly and how to
use apt-cdrom to add the contents to apt.

Take the DVD, mount it, use apt-cdrom to index the contents and go from
there?

Synaptic may not be ideal: you might find that your use cases may be
better served by apt/aptitude which may allow you to better see what
you're doing.


This group keeps reading _INTO_ my questions things that aren't there.
I'm in my eight decade and was introduced to computers as an engineering 
undergrad in early 60's, back when they had 12AX7's and 5U4's -- well 
before 8080's. In the 80's I was writing 8080/8085 assembler code for 
embedded systems. I did not get to really get to explore *PERSONAL* 
computing (excluding a KIM, P.E.T., and Z80 based S100 systems) until I 
retired.


Mantra du jour: "If retirement isn't for learning, what use is it!"

Back in 70's I got a job with a large mini-computer manufacturer 
*BECAUSE* I had no interest in things "digital". My expertise was 
analog! Old-enough timers might recognize ML5-5 as a significant mail stop.


mutter mutter mut...

Re: Synaptic error message

[Andrew M.A. Cater]

On Sat, Jun 26, 2021 at 09:20:33AM -0500, Richard Owlett wrote:
> I have a empty machine on which I've done a default install of
> Debian 10.7.0 with MATE as my desktop. As I intend later to install some
> non-Debian software I wanted a local repository. To have a known base to
> start from I extracted the contents of dvd1.iso to a local directory.
> 
> My sources.list references it as:
> > deb [ Trusted=yes ] file:home/richard/DVDs/dvd1/ buster main contrib  
> > non-free
> 
> In Synaptic when I do Edit->Reload Package Information it responds:
> > The repository 'file://home/richard/DVDs/dvd1 buster Release' is not signed.
> 
> 
> https://html.duckduckgo.com/html?q=%2B%22synaptic%22%20%2B%22repository%22%20%2B%22not%20signed%22%20site%3Adebian.org
> gives no useful information.
> 
> What do I do?
> What should I have read?
> TIA
> 
> 

Richard:

Maybe earlier messages on -user ? DVDs aren't normally signed repositories.

Various folk have suggested to you how to mount DVDs correctly and how to 
use apt-cdrom to add the contents to apt.

Take the DVD, mount it, use apt-cdrom to index the contents and go from 
there? 

Synaptic may not be ideal: you might find that your use cases may be 
better served by apt/aptitude which may allow you to better see what 
you're doing.

All the very best, as ever,

Andy Cater

Synaptic error message

[Richard Owlett]

I have a empty machine on which I've done a default install of
Debian 10.7.0 with MATE as my desktop. As I intend later to install some 
non-Debian software I wanted a local repository. To have a known base to 
start from I extracted the contents of dvd1.iso to a local directory.


My sources.list references it as:

deb [ Trusted=yes ] file:home/richard/DVDs/dvd1/ buster main contrib  
non-free


In Synaptic when I do Edit->Reload Package Information it responds:

The repository 'file://home/richard/DVDs/dvd1 buster Release' is not signed.



https://html.duckduckgo.com/html?q=%2B%22synaptic%22%20%2B%22repository%22%20%2B%22not%20signed%22%20site%3Adebian.org 
gives no useful information.


What do I do?
What should I have read?
TIA

[SOLVED] python3.9 venv testing error message

[songbird]

  the mismatch of the version of distutils prevented it from
working so the solution was to upgrade distutils from unstable
and it works now.


  songbird

python3.9 venv testing error message

[songbird]

  as it is testing perhaps there is a temporary glitch in
the packages for python3.9, but it has been there for at
least a week if not longer.  oh, i do have python-is-python3
and there are no python2 programs anywhere on this system 
that i know of.


  when i run the command:

=
$ python -m venv env

  setting up virtual environment /home/me/src/salsa/env
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

Failing command: ['/home/me/src/salsa/env/bin/python', '-Im', 'ensurepip', 
'--upgrade', '--default-pip']

=


  the package mentioned is installed:


=

$ dpkg -l | grep python3-venv
ii  python3-venv 3.9.0-4amd64   
 pyvenv-3 binary for python3 (default python3 version)

=

  any ideas?  :)  thanks!


  songbird

Re: bash, find and error message question

[songbird]

David Wright wrote:
...
> My question would be:
>
> Which directory is your current directory—what does pwd say?
> After all, the error messages say "reading directory '.': Protocol error",
> and not knowing where you are is unsettling for any command.

  in the script i'm using a variable but the text of that
variable is the same as /home/me/pics/camera

  i've got the new version working instead where it uses
lsusb and greps for the camera ID line when it is actually
available.

  now i have to debug the rest of it which was working ok
before i made a few changes.  my eyes are tired, gonna take
a break for a while.  :)  thanks.  :)


  songbird

Re: bash, find and error message question

[songbird]

Reco wrote:
> songbird wrote:
...
>>   i don't care if it is returned, i just wonder why it isn't
>> redirected to /dev/null like i'm asking it to do.
>
> Because you're redirecting stderr of a wrong process.
> This one-liner should do it.
>
> find . -type f -exec printf %.0s. {} + 2>/dev/null | wc -m

  i don't know why, but for some reason i thought the
stderr would be passed through the entire series of
piped commands.  i've hit this before and it never 
clicked.  haha...

  i don't really do a lot of complicated things with find
very often and when i have i haven't had errors (my file 
systems are more predictable than fuser is and i don't do 
things via remote connections or external devices hardly 
ever).

  thanks!  :)  cheers.  off to take break...


  songbird

Re: bash, find and error message question

[David Wright]

On Sat 01 Feb 2020 at 13:38:55 (-0500), songbird wrote:
> Reco wrote:
> > On Sat, Feb 01, 2020 at 12:36:28PM -0500, songbird wrote:
> >> the directory is a mount point of a device in limbo.
> >> it is showing up as mounted but it really isn't (the
> >> device is turned off).
> > ...
> >> 
> >>   i just want the answer to be 0 or the number of files.
> >
> > Fuse does not work that way. If a userspace backend cannot perform its
> > function (in this case - a device is disconnected) - it's free to return
> > all kinds of error even on a simple opendir(3).
> >
> > Best you can do is to execute:
> >
> > fusermount -u /home/me/pics/camera
> 
>   i don't care if it is returned, i just wonder why it isn't
> redirected to /dev/null like i'm asking it to do.
> 
> 
> >>   i am using the above in a bash script so i don't want
> >> any error messages coming from the script itself unless
> >> i print them myself.
> >
> > If you need an answer whenever a camera is plugged on or not - why don't
> > you check for the device itself? I.e. lsusb and friends.
> 
>   i check via the mount command but as i've found out it
> isn't really reliable because in fact it is mounting something
> even if it isn't there.
> 
>   as it is i have to tell the camera to be unmounted via gio
> because when i plug the camera in the automounting happens
> even if i tell the system to not do anything.
> 
>   and yes, i'm annoyed at systems that don't do what you tell
> them to do.  the reason i'm writing this whole thing is because
> i dislike all the stupid assumptions and baked in crap that
> the camera manufacturer wants someone to jump through.  no.  the
> USB connection works as it should, leave me alone.  grrr!
> 
>   so i almost have my camera script done but there's these
> last niggling bits i'd like to iron out.
> 
>   thanks for the suggestion about lsusb.  that will at least
> get around the main PITA i'm hitting.  :)

My question would be:

Which directory is your current directory—what does pwd say?
After all, the error messages say "reading directory '.': Protocol error",
and not knowing where you are is unsettling for any command.

Cheers,
David.

Re: bash, find and error message question

[Reco]

On Sat, Feb 01, 2020 at 01:38:55PM -0500, songbird wrote:
> Reco wrote:
> > On Sat, Feb 01, 2020 at 12:36:28PM -0500, songbird wrote:
> >> the directory is a mount point of a device in limbo.
> >> it is showing up as mounted but it really isn't (the
> >> device is turned off).
> > ...
> >> 
> >>   i just want the answer to be 0 or the number of files.
> >
> > Fuse does not work that way. If a userspace backend cannot perform its
> > function (in this case - a device is disconnected) - it's free to return
> > all kinds of error even on a simple opendir(3).
> >
> > Best you can do is to execute:
> >
> > fusermount -u /home/me/pics/camera
> 
>   i don't care if it is returned, i just wonder why it isn't
> redirected to /dev/null like i'm asking it to do.

Because you're redirecting stderr of a wrong process.
This one-liner should do it.

find . -type f -exec printf %.0s. {} + 2>/dev/null | wc -m

Reco

Re: bash, find and error message question

[songbird]

Reco wrote:
> On Sat, Feb 01, 2020 at 12:36:28PM -0500, songbird wrote:
>> the directory is a mount point of a device in limbo.
>> it is showing up as mounted but it really isn't (the
>> device is turned off).
> ...
>> 
>>   i just want the answer to be 0 or the number of files.
>
> Fuse does not work that way. If a userspace backend cannot perform its
> function (in this case - a device is disconnected) - it's free to return
> all kinds of error even on a simple opendir(3).
>
> Best you can do is to execute:
>
> fusermount -u /home/me/pics/camera

  i don't care if it is returned, i just wonder why it isn't
redirected to /dev/null like i'm asking it to do.


>>   i am using the above in a bash script so i don't want
>> any error messages coming from the script itself unless
>> i print them myself.
>
> If you need an answer whenever a camera is plugged on or not - why don't
> you check for the device itself? I.e. lsusb and friends.

  i check via the mount command but as i've found out it
isn't really reliable because in fact it is mounting something
even if it isn't there.

  as it is i have to tell the camera to be unmounted via gio
because when i plug the camera in the automounting happens
even if i tell the system to not do anything.

  and yes, i'm annoyed at systems that don't do what you tell
them to do.  the reason i'm writing this whole thing is because
i dislike all the stupid assumptions and baked in crap that
the camera manufacturer wants someone to jump through.  no.  the
USB connection works as it should, leave me alone.  grrr!

  so i almost have my camera script done but there's these
last niggling bits i'd like to iron out.

  thanks for the suggestion about lsusb.  that will at least
get around the main PITA i'm hitting.  :)


  songbird

Re: bash, find and error message question

[Reco]

Hi.

On Sat, Feb 01, 2020 at 12:36:28PM -0500, songbird wrote:
> the directory is a mount point of a device in limbo.
> it is showing up as mounted but it really isn't (the
> device is turned off).
...
> 
>   i just want the answer to be 0 or the number of files.

Fuse does not work that way. If a userspace backend cannot perform its
function (in this case - a device is disconnected) - it's free to return
all kinds of error even on a simple opendir(3).

Best you can do is to execute:

fusermount -u /home/me/pics/camera

>   i am using the above in a bash script so i don't want
> any error messages coming from the script itself unless
> i print them myself.

If you need an answer whenever a camera is plugged on or not - why don't
you check for the device itself? I.e. lsusb and friends.

Reco

bash, find and error message question

[songbird]

  i'm trying to get the following search to give me the
answer and at the same time discard any error messages.

the directory is a mount point of a device in limbo.
it is showing up as mounted but it really isn't (the
device is turned off).

mtab says:
fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0
/dev/sdc1 /mb ext4 rw,relatime 0 0
gphotofs /home/me/pics/camera fuse.gphotofs 
rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0

(more on this mount/fuser stuff as a different question)

the directory is empty as it should be
but even a simple ls gives me the protocol error, but
at least the redirect functions as expected.

$ ls
ls: reading directory '.': Protocol error

$ ls 2>/dev/null
total 0


$ find . -type f -exec printf %.0s. {} + | wc -m
find: ‘.’: Protocol error
0
$ find . -type f -exec printf %.0s. {} + | wc -m 2>/dev/null
find: ‘.’: Protocol error
0

# at least this one does what i tell it to do...
$ find . -type f -exec printf %.0s. {} + | wc -m >/dev/null
find: ‘.’: Protocol error



  even if i try to wrap it up in a command or subshell it
still gives me the error message and i don't really care.

  i just want the answer to be 0 or the number of files.

  i am using the above in a bash script so i don't want
any error messages coming from the script itself unless
i print them myself.

  thanks!  :)


  songbird

Re: Synaptic error message -- how to respond

[David Wright]

On Thu 25 Apr 2019 at 04:40:12 (-0500), Richard Owlett wrote:
> On 04/25/2019 03:15 AM, Curt wrote:
> > On 2019-04-24, Mark Allums  wrote:
> > > > 
> > > > I see the error message but do not know what to do.
> > > > Thanks for pointers.
> > > > 
> > > Try rearranging your python(s) in your PATH.  I.e., swap py2 with py3.

It's certainly worth checking the $PATH but python shouldn't be in it.
It may be worth moving one's own bin to the end if at the beginning.
(I prefer not to override the system's binaries.)

> > > Or possibly your py3 version needs to be downgraded.

No, don't do that. Python versions 2 and 3 work alongside each other.
They have to: the system relies on python2, and most modern software
is written for python3. I would have a job remembering now how to
write in python2 now, even though all the paid work I ever did was
in the days of 2.

> > > Something about your python versions.
> > 
> > ConfigParser module has been revamped and renamed to configparser in Python 
> > 3.

Agreed, it does look as though the python version are screwed up.

> Knowing the history of this machine, this may just the tip of an
> iceberg.

Be reassured: we do not, and probably never will.

> I've a set of Debian 9.8 DVDs and generous amount of free
> disk space. It may be a time saver to do a fresh install. At least I
> would have a install in a known state.

And learn nothing about what it was you did wrong.

Cheers,
David.

Re: Synaptic error message -- how to respond

[David]

On Thu, 25 Apr 2019 at 07:43, Richard Owlett  wrote:
>
> > Preparing to unpack .../galternatives_0.13.5+nmu4+deb9u1_all.deb ...
>
> > File "/usr/bin/pyclean", line 63
>
> > except (IOError, OSError), e:
>
> > ^
>
> > SyntaxError: invalid syntax

On Thu, 25 Apr 2019 at 18:15, Curt  wrote:
> On 2019-04-24, Mark Allums  wrote:
> >
> > Something about your python versions.
>
> ConfigParser module has been revamped and renamed to configparser in Python 3.

A more concerning question is why /usr/bin/pyclean and friends
seem to be encountering Python 3 errors when they require Python 2
and invoke /usr/bin/python.

On Thu, 25 Apr 2019 at 19:40, Richard Owlett  wrote:
>
> Knowing the history of this machine, this may just the tip of an iceberg.
[...]
> It may be a time saver to do a fresh install.

I will be surprised if anyone tries to change your mind. I have other more
enjoyable things to do, so that will be the end of my contribution on this one.

Re: Synaptic error message -- how to respond

[Richard Owlett]

On 04/25/2019 03:15 AM, Curt wrote:

On 2019-04-24, Mark Allums  wrote:


I see the error message but do not know what to do.
Thanks for pointers.



Try rearranging your python(s) in your PATH.  I.e., swap py2 with py3.

Or possibly your py3 version needs to be downgraded.

Something about your python versions.

Mark




ConfigParser module has been revamped and renamed to configparser in Python 3.



Knowing the history of this machine, this may just the tip of an 
iceberg. I've a set of Debian 9.8 DVDs and generous amount of free disk 
space. It may be a time saver to do a fresh install. At least I would 
have a install in a known state.

Thank you.

Re: Synaptic error message -- how to respond

[Curt]

On 2019-04-24, Mark Allums  wrote:
>> 
>> I see the error message but do not know what to do.
>> Thanks for pointers.
>> 
>
> Try rearranging your python(s) in your PATH.  I.e., swap py2 with py3.
>
> Or possibly your py3 version needs to be downgraded.
>
> Something about your python versions.
>
> Mark
>
>

ConfigParser module has been revamped and renamed to configparser in Python 3.

-- 
The major, who had been a great fencer, did not believe in bravery, and spent
much time while we sat in the machines correcting my grammar. He had
complimented me on how I spoke Italian, and we talked together very easily. One
day I had said that Italian seemed such an easy language to me that I could not
take a great interest in it; everything was so easy to say. "Ah, yes," the
major said. "Why, then, do you not take up the use of grammar?" - "Another 
Country"

Re: Synaptic error message -- how to respond

[Mark Allums]

On 4/24/19 4:42 PM, Richard Owlett wrote:

On 04/24/2019 03:42 PM, Thomas D Dial wrote:

On Wed, 2019-04-24 at 10:42 -0500, Richard Owlett wrote:

I have repeatedly received the following error message:

E: galternatives: package is in a very bad inconsistent state;
you should  reinstall it before attempting configuration


I don't recall what triggered it last week. Today I wanted to install
"apt-rdepends" which displayed the above error message. I closed the
message window. The box next to apt-rdepends was colored green
indicating it had been successfully installed. I did a test run of it
and got reasonably looking output.

I attempt to reinstall "galternatives" and receive:

E: /var/cache/apt/archives/galternatives_0.13.5+nmu4+deb9u1_all.deb:
subprocess new pre-removal script returned error exit status 1
galternatives


What should I do next?


Look carefully at everything from the

"apt install --reinstall galternatives"

command to the end of the output from it. It shouldn't be all that long
but is likely to have diagnostic information you can use to identify and
correct the problem. If that doesn't clarify it enough, post the output,
  all of it. Many of us have seen install failures from time to time and
given enough output might have suggestions. Exit code from a script
bundled in the .deb file is too generic to be useful by itself.

Regards,
Tom Dial



Where the error is is fairly clear. But what to do about is not.
My interpretation is there a problem with the repository.

Not being sure how short the output would be I saved the output to a file.

My terminal session:

richard@fromdell:~$ su
Password: root@fromdell:/home/richard# apt install --reinstall 
galternatives > diagnostic


WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.


E: Sub-process /usr/bin/dpkg returned an error code (1)
root@fromdell:/home/richard#


The contents of file "diagnostic" is:

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 251 not 
upgraded.

3 not fully installed or removed.
Need to get 0 B/148 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 

(Reading database ... 5%
(Reading database ... 10%

[snip repetitive info]
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 176998 files and directories currently installed.)


Preparing to unpack .../galternatives_0.13.5+nmu4+deb9u1_all.deb ...



  File "/usr/bin/pyclean", line 63



    except (IOError, OSError), e:



 ^



SyntaxError: invalid syntax


dpkg: warning: subprocess old pre-removal script returned error exit 
status 1



dpkg: trying script from the new package instead ...



  File "/usr/bin/pyclean", line 63



    except (IOError, OSError), e:



 ^



SyntaxError: invalid syntax


dpkg: error processing archive 
/var/cache/apt/archives/galternatives_0.13.5+nmu4+deb9u1_all.deb 
(--unpack):



 subprocess new pre-removal script returned error exit status 1



Traceback (most recent call last):



  File "/usr/bin/pycompile", line 35, in 



    from debpython.version import SUPPORTED, debsorted, vrepr, \



  File "/usr/share/python/debpython/version.py", line 24, in 



    from ConfigParser import SafeConfigParser



ImportError: No module named 'ConfigParser'



dpkg: error while cleaning up:


 subprocess installed post-installation script returned error exit 
status 1



Errors were encountered while processing:



 /var/cache/apt/archives/galternatives_0.13.5+nmu4+deb9u1_all.deb



I see the error message but do not know what to do.
Thanks for pointers.



Try rearranging your python(s) in your PATH.  I.e., swap py2 with py3.

Or possibly your py3 version needs to be downgraded.

Something about your python versions.

Mark

Re: Synaptic error message -- how to respond

[Richard Owlett]

On 04/24/2019 03:42 PM, Thomas D Dial wrote:

On Wed, 2019-04-24 at 10:42 -0500, Richard Owlett wrote:

I have repeatedly received the following error message:

E: galternatives: package is in a very bad inconsistent state;
you should  reinstall it before attempting configuration


I don't recall what triggered it last week. Today I wanted to install
"apt-rdepends" which displayed the above error message. I closed the
message window. The box next to apt-rdepends was colored green
indicating it had been successfully installed. I did a test run of it
and got reasonably looking output.

I attempt to reinstall "galternatives" and receive:

E: /var/cache/apt/archives/galternatives_0.13.5+nmu4+deb9u1_all.deb:
subprocess new pre-removal script returned error exit status 1
galternatives


What should I do next?


Look carefully at everything from the

"apt install --reinstall galternatives"

command to the end of the output from it. It shouldn't be all that long
but is likely to have diagnostic information you can use to identify and
correct the problem. If that doesn't clarify it enough, post the output,
  all of it. Many of us have seen install failures from time to time and
given enough output might have suggestions. Exit code from a script
bundled in the .deb file is too generic to be useful by itself.

Regards,
Tom Dial



Where the error is is fairly clear. But what to do about is not.
My interpretation is there a problem with the repository.

Not being sure how short the output would be I saved the output to a file.

My terminal session:

richard@fromdell:~$ su
Password: 
root@fromdell:/home/richard# apt install --reinstall galternatives > diagnostic


WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

E: Sub-process /usr/bin/dpkg returned an error code (1)
root@fromdell:/home/richard#


The contents of file "diagnostic" is:

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 251 not upgraded.
3 not fully installed or removed.
Need to get 0 B/148 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 

(Reading database ... 5%
(Reading database ... 10%

[snip repetitive info]
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 176998 files and directories currently installed.)


Preparing to unpack .../galternatives_0.13.5+nmu4+deb9u1_all.deb ...



  File "/usr/bin/pyclean", line 63



except (IOError, OSError), e:



 ^



SyntaxError: invalid syntax



dpkg: warning: subprocess old pre-removal script returned error exit status 1



dpkg: trying script from the new package instead ...



  File "/usr/bin/pyclean", line 63



except (IOError, OSError), e:



 ^



SyntaxError: invalid syntax



dpkg: error processing archive 
/var/cache/apt/archives/galternatives_0.13.5+nmu4+deb9u1_all.deb (--unpack):



 subprocess new pre-removal script returned error exit status 1



Traceback (most recent call last):



  File "/usr/bin/pycompile", line 35, in 



from debpython.version import SUPPORTED, debsorted, vrepr, \



  File "/usr/share/python/debpython/version.py", line 24, in 



from ConfigParser import SafeConfigParser



ImportError: No module named 'ConfigParser'



dpkg: error while cleaning up:



 subprocess installed post-installation script returned error exit status 1



Errors were encountered while processing:



 /var/cache/apt/archives/galternatives_0.13.5+nmu4+deb9u1_all.deb



I see the error message but do not know what to do.
Thanks for pointers.

Re: Synaptic error message -- how to respond

[Thomas D Dial]

On Wed, 2019-04-24 at 10:42 -0500, Richard Owlett wrote:
> I have repeatedly received the following error message:
> > E: galternatives: package is in a very bad inconsistent state;
> > you should  reinstall it before attempting configuration
> 
> I don't recall what triggered it last week. Today I wanted to install 
> "apt-rdepends" which displayed the above error message. I closed the 
> message window. The box next to apt-rdepends was colored green 
> indicating it had been successfully installed. I did a test run of it 
> and got reasonably looking output.
> 
> I attempt to reinstall "galternatives" and receive:
> > E: /var/cache/apt/archives/galternatives_0.13.5+nmu4+deb9u1_all.deb:
> > subprocess new pre-removal script returned error exit status 1
> > galternatives
> 
> What should I do next?

Look carefully at everything from the 

"apt install --reinstall galternatives"

command to the end of the output from it. It shouldn't be all that long
but is likely to have diagnostic information you can use to identify and
correct the problem. If that doesn't clarify it enough, post the output,
 all of it. Many of us have seen install failures from time to time and
given enough output might have suggestions. Exit code from a script
bundled in the .deb file is too generic to be useful by itself.

Regards,
Tom Dial

> TIA
> 
> 
> 
> 

Synaptic error message -- how to respond

[Richard Owlett]

I have repeatedly received the following error message:

E: galternatives: package is in a very bad inconsistent state;
you should  reinstall it before attempting configuration


I don't recall what triggered it last week. Today I wanted to install 
"apt-rdepends" which displayed the above error message. I closed the 
message window. The box next to apt-rdepends was colored green 
indicating it had been successfully installed. I did a test run of it 
and got reasonably looking output.


I attempt to reinstall "galternatives" and receive:

E: /var/cache/apt/archives/galternatives_0.13.5+nmu4+deb9u1_all.deb:
subprocess new pre-removal script returned error exit status 1



What should I do next?
TIA

Re: Error Message

[Curt]

On 2019-04-11, Mark Fletcher  wrote:
> On Thu, Apr 11, 2019 at 07:03:08PM +0200, Michael Lee wrote:
>> Hello, I would like to know what I am supposed to do about this error
>> message. Would appreciate guidance.
>> M Lee
>
>> The repository 'http://ftp.de.debian.org/debian stretch/updates
 
It seems (after taking a quick gander) that that should be 'stretch-updates',
not stretch/updates (which doesn't exist).

Maybe this explains that (as they say here in French).

>
> Looking at the error message (the English part, I can't read the German) 
> I suspect the issue is the second part of the message, and the first 
> part complaining that ftp.de.debian.org doesn't have a Release file is 
> a red herring. It looks like ownership or permissions on your 
> /etc/apt/trusted.gpg file are dodgy. Have a look at ownership and 
> permissions on that file and, if it's not obvious to you what's wrong, 
> post here the output of ls -l /etc/apt/trusted.gpg and hopefully it will 
> be obvious to someone on here.
>
> Have you been making changes to your apt configuration recently? If you 
> have done anything in that area recently, describe that too as that may 
> have a bearing on the problem.
>
> HTH
>
> Mark
>
>


-- 
“Let us again pretend that life is a solid substance, shaped like a globe,
which we turn about in our fingers. Let us pretend that we can make out a plain
and logical story, so that when one matter is despatched--love for instance--
we go on, in an orderly manner, to the next.” - Virginia Woolf, The Waves

Re: Error Message

[Mark Fletcher]

On Thu, Apr 11, 2019 at 07:03:08PM +0200, Michael Lee wrote:
> Hello, I would like to know what I am supposed to do about this error
> message. Would appreciate guidance.
> M Lee

> 
> 
> Nicht alle Paketquellenindizes konnten heruntergeladen werden
> 
> Die Software-Paketquelle steht möglicherweise nicht mehr zur Verfügung oder 
> ist aufgrund von Netzwerkproblemen nicht erreichbar. Sofern für diese 
> Software-Paketquelle noch eine ältere Paketliste verfügbar ist, wird diese 
> verwendet. Anderenfalls wird diese Software-Paketquelle gänzlich ignoriert. 
> Bitte prüfen Sie Ihre Netzwerkverbindung und vergewissern Sie sich ebenfalls, 
> dass die Adresse der Software-Paketquelle korrekt in den Einstellungen 
> eingetragen ist.
> 
> 
> The repository 'http://ftp.de.debian.org/debian stretch/updates Release' does 
> not have a Release file.Updating from such a repository can't be done 
> securely, and is therefore disabled by default.See apt-secure(8) manpage for 
> repository creation and user configuration 
> details.http://ftp.de.debian.org/debian/dists/stretch-updates/InRelease: The 
> key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not 
> readable by user '_apt' executing 
> apt-key.http://ftp.de.debian.org/debian/dists/stretch/Release.gpg: The key(s) 
> in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable 
> by user '_apt' executing apt-key.
> 
> 

Looking at the error message (the English part, I can't read the German) 
I suspect the issue is the second part of the message, and the first 
part complaining that ftp.de.debian.org doesn't have a Release file is 
a red herring. It looks like ownership or permissions on your 
/etc/apt/trusted.gpg file are dodgy. Have a look at ownership and 
permissions on that file and, if it's not obvious to you what's wrong, 
post here the output of ls -l /etc/apt/trusted.gpg and hopefully it will 
be obvious to someone on here.

Have you been making changes to your apt configuration recently? If you 
have done anything in that area recently, describe that too as that may 
have a bearing on the problem.

HTH

Mark

Error Message

[Michael Lee]

Hello, I would like to know what I am supposed to do about this error
message. Would appreciate guidance.
M Lee

Nicht alle Paketquellenindizes konnten heruntergeladen werden

Die Software-Paketquelle steht möglicherweise nicht mehr zur Verfügung oder ist 
aufgrund von Netzwerkproblemen nicht erreichbar. Sofern für diese 
Software-Paketquelle noch eine ältere Paketliste verfügbar ist, wird diese 
verwendet. Anderenfalls wird diese Software-Paketquelle gänzlich ignoriert. 
Bitte prüfen Sie Ihre Netzwerkverbindung und vergewissern Sie sich ebenfalls, 
dass die Adresse der Software-Paketquelle korrekt in den Einstellungen 
eingetragen ist.


The repository 'http://ftp.de.debian.org/debian stretch/updates Release' does 
not have a Release file.Updating from such a repository can't be done securely, 
and is therefore disabled by default.See apt-secure(8) manpage for repository 
creation and user configuration 
details.http://ftp.de.debian.org/debian/dists/stretch-updates/InRelease: The 
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not 
readable by user '_apt' executing 
apt-key.http://ftp.de.debian.org/debian/dists/stretch/Release.gpg: The key(s) 
in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by 
user '_apt' executing apt-key.

Re: Suppress error message to log files

[Andy Smith]

Hi,

On Mon, Feb 04, 2019 at 02:42:51PM -0600, sel...@midwest.net wrote:
> Play one game and 
> 
> This entry found in /var/log/{messages,syslog,user.log}:
> Jan 26 00:55:23 debian quadrapassel[5542]: 
> ../../../../../gdk/x11/gdkwindow-x11.c:5611 
> drawable is not a native X11 window

[…]

> How do I suppress the posting of this "error".

Assuming rsyslog, you can make rsyslog ignore it and then it will never
be logged. For example:

$ cat /etc/rsyslog.d/ignore-quadrapassel-gdkwindow-spam.conf
if $programname == 'quadrapassel' then {
if $msg contains "drawable is not a native X11 window" then stop
}

Restart rsyslog afterwards:

# systemctl restart rsyslog

But probably it would be better to report the bug in
quadrapassel if it hasn't already been reported.

Cheers,
Andy

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

Suppress error message to log files

[selsyn]

Play one game and 

This entry found in /var/log/{messages,syslog,user.log}:
Jan 26 00:55:23 debian quadrapassel[5542]: 
../../../../../gdk/x11/gdkwindow-x11.c:5611 
drawable is not a native X11 window

# Size of messages file
jim:/var/log$   ls -lh messages
-rw-r- 1 root adm 250K Jan 28 13:58 messages

# Lines of duplicate error
jim:/var/log$  grep quadrapassel messages | wc -l 
1977 

# Remove the offending lines
jim:/var/log$  sed -i '/quadrapassel/d' messages

# New size 
jim:/var/log$  ls -lh messages
-rw-r- 1 root adm 13K Jan 28 14:02 messages

That's  (250K-13K) * 3  filling the log files per game.

How do I suppress the posting of this "error".

Re: Please help with error message

[deloptes]

Rodolfo Medina wrote:

> I'd always thought that `su' was Debian's and `sudo' was Ubuntu's...  :-)

No - both are linux and sudo is for the use to be able to use specific
commands. So in general I add sudo rule for my use for bash and it is done.
Alternatively add user to sudo group and you can use the factory rule

# Allow members of group sudo to execute any command
%sudo   ALL=(ALL:ALL) ALL

There is nothing like ubuntu or debian relationship here.

regards

Re: Please help with error message

[Rodolfo Medina]

deloptes  writes:

> Rodolfo Medina wrote:
>
>> Yes, if becoming root with with `su -' the error about what is the present
>> thread disappears...
>
> I guess sudo is always better to use


I'd always thought that `su' was Debian's and `sudo' was Ubuntu's...  :-)

Rodolfo

Re: Please help with error message

[Reco]

Hi.

On Tue, Aug 07, 2018 at 12:45:51PM +0200, Stephan Seitz wrote:
> On Di, Aug 07, 2018 at 01:18:59 +0300, Reco wrote:
> > > I never had your mentioned problems.
> > Either you have /sbin in your user's path, or you haven't run a single
> > apt-get all these years. There are other possibilities, of course,
> > though less flattering.
> 
> Bullshit again. You didn’t read the thread, did you?

Tsk-tsk. Personal attacks on debian-user, and it's not even a Friday.

> This is new behaviour in testing because Debian switched the source for the
> su binary.
> 
> Debian 9:
> stse@fsing:~$ echo $PATH
> /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> stse@fsing:~$ su
> Passwort:
> root@fsing /home/stse # echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> 
> Testing:
> [stse@osgiliath]: echo $PATH
> /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
> [stse@osgiliath]: su
> Passwort:
> osgiliath:/home/stse# echo $PATH
> /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
> 
> Testing with „ALWAYS_SET_PATH yes” in login.defs:
> [stse@osgiliath]: echo $PATH
> /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
> [stse@osgiliath]: su
> Passwort:
> osgiliath:/home/stse# echo $PATH
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> 
> I hope you see the difference.

So once again Debian aligned its behaviour with RHEL. Not the first
time, not the last. A interesting change, but a minor one.
All of us using 'su -' all these years are not affected.
Users of ordinary 'su' may suffer though.


> 
> > > „su” doesn’t change the working directory. So if you compile
> > > software as a user you can then type „make install” after su.
> > True. But this tidbit does not relate to this particular problem at all.
> 
> It does. Depending on your needs you could use „su” or „su -”.

And you're telling me to read the thread. How exactly apt-get's
behaviour depends on cwd?


> > > If you need to run an X11 program as root su preserved the DISPLAY
> > > variable.
> > And it also preserves $HOME. So any changed configuration file will be
> > owned by root. Not a big deal if you never try to run the program in
> 
> Only if the file never existed.

Or program's developer is trying being smart and writes changed
configuration in a different file followed by rename(2).

> 
> > > Luckily you can switch back to the old behaviour, but this should be
> > > the default.
> > Care to provide a Debian bug number that you filled on this particular
> > issue? Because rants on debian-user do not transform to patches by
> > themselves.
> 
> Which patches?

You're expressing a strong dislike of a certain change, but you're doing
so in a wrong place. An appropriate place for such dislikes is called
bugs.debian.org, and all the changes of behaviour are accepted in the
form of patches to source packages theres.


> > > As Linus would say: „Don’t break user behaviour! Give them an
> > > option to switch to a new one.”.
> > A recent kernel update (linux-4.9.110-3+deb9u1) begs to differ.
> > Two notable behaviour changes without any way to disable them.
> 
> Are these security changes? Then Linus permits it if there is no other way.
> By the way, what are these changes that are breaking user space?

Too lazy to read the changelog, eh?
Fix for CVE-2018-13405 breaks directory permissions.
Fix for CVE-2018-5390 changes TCP stack.

Reco

Re: Please help with error message

[Greg Wooledge]

On Tue, Aug 07, 2018 at 01:18:59PM +0300, Reco wrote:
> On Tue, Aug 07, 2018 at 12:01:02PM +0200, Stephan Seitz wrote:
> > On Di, Aug 07, 2018 at 12:35:32 +0300, Reco wrote:
> > > > rodolfo@sda6-acer:~$ su
> > > Don't. Do. That. Ever.
> > 
> > That’s bullshit. I did it all the time until Debian decided to break things.

> Either you have /sbin in your user's path, or you haven't run a single
> apt-get all these years. There are other possibilities, of course,
> though less flattering.

No, Stephan is correct.  In Debian stable, "su" with no arguments
changes PATH.  It has done so for years.  Decades, if I'm not mistaken.

Here, watch:

wooledg:~$ echo "$PATH"
/home/wooledg/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
wooledg:~$ su
Password: 
root@wooledg:/home/wooledg# echo "$PATH"
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

If testing/unstable has changed this behavior, then that's going to be
a HUGE thing to adjust to.  Has a bug been filed for it yet?

Re: Please help with error message

[mick crane]

On 2018-08-07 12:47, mick crane wrote:

On 2018-08-07 09:18, Stephan Seitz wrote:

On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:

$ echo $PATH
/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
rodolfo@sda6-acer:~$ su
Password:


You are using testing/unstable, aren’t you?




so where is user's path kept these days as it seems I might have set
user PATH to root PATH ?
and I should probably put it back as it was.
mick


OK seems set $PATH after su does change root PATH so things are as they 
were


--
Key ID4BFEBB31

Re: Please help with error message

[mick crane]

On 2018-08-07 09:18, Stephan Seitz wrote:

On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:

$ echo $PATH
/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
rodolfo@sda6-acer:~$ su
Password:


You are using testing/unstable, aren’t you?

The su binary was replaced with another one, and now Debian is
breaking user space again. :-(
Now su alone doesn’t change the path but keeps the user path. You have
to use „su -”.

 The util-linux implementation of /bin/su is now used, replacing the
 one previously supplied by src:shadow (shipped in login package), and
 bringing Debian in line with other modern distributions. The two
 implementations are very similar but have some minor differences (and
 there might be more that was not yet noticed ofcourse), e.g.

 - new 'su' (with no args, i.e. when preserving the environment) also
   preserves PATH and IFS, while old su would always reset PATH and IFS
   even in 'preserve environment' mode.
 - su '' (empty user string) used to give root, but now returns an 
error.

 - previously su only had one pam config, but now 'su -' is configured
   separately in /etc/pam.d/su-l

 The first difference is probably the most user visible one. Doing
 plain 'su' is a really bad idea for many reasons, so using 'su -' is
 strongly recommended to always get a newly set up environment similar
 to a normal login. If you want to restore behaviour more similar to
 the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.

Shade and sweet water!

Stephan


so where is user's path kept these days as it seems I might have set 
user PATH to root PATH ?

and I should probably put it back as it was.
mick
--
Key ID4BFEBB31

Re: Please help with error message

[mick crane]

On 2018-08-07 09:18, Stephan Seitz wrote:

On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:

$ echo $PATH
/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
rodolfo@sda6-acer:~$ su
Password:


You are using testing/unstable, aren’t you?

The su binary was replaced with another one, and now Debian is
breaking user space again. :-(
Now su alone doesn’t change the path but keeps the user path. You have
to use „su -”.

 The util-linux implementation of /bin/su is now used, replacing the
 one previously supplied by src:shadow (shipped in login package), and
 bringing Debian in line with other modern distributions. The two
 implementations are very similar but have some minor differences (and
 there might be more that was not yet noticed ofcourse), e.g.

 - new 'su' (with no args, i.e. when preserving the environment) also
   preserves PATH and IFS, while old su would always reset PATH and IFS
   even in 'preserve environment' mode.
 - su '' (empty user string) used to give root, but now returns an 
error.

 - previously su only had one pam config, but now 'su -' is configured
   separately in /etc/pam.d/su-l

 The first difference is probably the most user visible one. Doing
 plain 'su' is a really bad idea for many reasons, so using 'su -' is
 strongly recommended to always get a newly set up environment similar
 to a normal login. If you want to restore behaviour more similar to
 the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.

Shade and sweet water!

Stephan


Ah, Ok that explains why /sbin wasn't in what I thought was root's $PATH 
when su to find why ldconfig wasn't found for something or other.


cheers

mick






--
Key ID4BFEBB31

Re: Please help with error message

[deloptes]

Rodolfo Medina wrote:

> Yes, if becoming root with with `su -' the error about what is the present
> thread disappears...

I guess sudo is always better to use

Re: Please help with error message

[Stephan Seitz]

On Di, Aug 07, 2018 at 01:18:59 +0300, Reco wrote:

I never had your mentioned problems.

Either you have /sbin in your user's path, or you haven't run a single
apt-get all these years. There are other possibilities, of course,
though less flattering.


Bullshit again. You didn’t read the thread, did you?
This is new behaviour in testing because Debian switched the source for 
the su binary.


Debian 9:
stse@fsing:~$ echo $PATH
/home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
stse@fsing:~$ su
Passwort:
root@fsing /home/stse # echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Testing:
[stse@osgiliath]: echo $PATH
/home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
[stse@osgiliath]: su
Passwort:
osgiliath:/home/stse# echo $PATH
/home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin

Testing with „ALWAYS_SET_PATH yes” in login.defs:
[stse@osgiliath]: echo $PATH
/home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin
[stse@osgiliath]: su
Passwort:
osgiliath:/home/stse# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

I hope you see the difference.

„su” doesn’t change the working directory. So if you compile software 
as a user you can then type „make install” after su.

True. But this tidbit does not relate to this particular problem at all.


It does. Depending on your needs you could use „su” or „su -”.


Now it is simpler to compile as root user.

It was always 'simpler'. But not 'smarter'.


Doesn’t matter, security is always a compromise. If it gets to much work 
it will be reduced.


If you need to run an X11 program as root su preserved the DISPLAY 
variable.

And it also preserves $HOME. So any changed configuration file will be
owned by root. Not a big deal if you never try to run the program in


Only if the file never existed.

Luckily you can switch back to the old behaviour, but this should be 
the default.

Care to provide a Debian bug number that you filled on this particular
issue? Because rants on debian-user do not transform to patches by
themselves.


Which patches?


As Linus would say: „Don’t break user behaviour! Give them an
option to switch to a new one.”.

A recent kernel update (linux-4.9.110-3+deb9u1) begs to differ.
Two notable behaviour changes without any way to disable them.


Are these security changes? Then Linus permits it if there is no other 
way. By the way, what are these changes that are breaking user space?


Shade and sweet water!

Stephan

--
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |


smime.p7s
Description: S/MIME cryptographic signature

Re: Please help with error message

[Reco]

Hi.

On Tue, Aug 07, 2018 at 12:01:02PM +0200, Stephan Seitz wrote:
> On Di, Aug 07, 2018 at 12:35:32 +0300, Reco wrote:
> > > rodolfo@sda6-acer:~$ su
> > Don't. Do. That. Ever.
> 
> That’s bullshit. I did it all the time until Debian decided to break things.

It never hurts to check an appropriate manpage *before* calling BS.
In this case:

The su command is used to become another user during a login session.
Invoked without a username, su defaults to becoming the superuser. The
optional argument - may be used to provide an environment similar to
what the user would expect had the user logged in directly.


> I never had your mentioned problems.

Either you have /sbin in your user's path, or you haven't run a single
apt-get all these years. There are other possibilities, of course,
though less flattering.


> „su” doesn’t change the working directory. So if you compile software as a
> user you can then type „make install” after su.

True. But this tidbit does not relate to this particular problem at all.


> Now it is simpler to compile as root user.

It was always 'simpler'. But not 'smarter'.


> If you need to run an X11 program as root su preserved the DISPLAY variable.

And it also preserves $HOME. So any changed configuration file will be
owned by root. Not a big deal if you never try to run the program in
question as your user.


> Luckily you can switch back to the old behaviour, but this should be the
> default.

Care to provide a Debian bug number that you filled on this particular
issue? Because rants on debian-user do not transform to patches by
themselves.


> As Linus would say: „Don’t break user behaviour! Give them an
> option to switch to a new one.”.

A recent kernel update (linux-4.9.110-3+deb9u1) begs to differ.
Two notable behaviour changes without any way to disable them.

Reco

Re: Please help with error message

[Stephan Seitz]

On Di, Aug 07, 2018 at 12:35:32 +0300, Reco wrote:

rodolfo@sda6-acer:~$ su

Don't. Do. That. Ever.


That’s bullshit. I did it all the time until Debian decided to break 
things.


I never had your mentioned problems.

„su” doesn’t change the working directory. So if you compile software as 
a user you can then type „make install” after su. Now it is simpler to 
compile as root user.


If you need to run an X11 program as root su preserved the DISPLAY 
variable.


Luckily you can switch back to the old behaviour, but this should be the 
default. As Linus would say: „Don’t break user behaviour! Give them an 
option to switch to a new one.”.


Shade and sweet water!

Stephan

--
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |


smime.p7s
Description: S/MIME cryptographic signature

Re: Please help with error message

[Reco]

Hi.

On Tue, Aug 07, 2018 at 10:08:06AM +0200, Rodolfo Medina wrote:
> Reco  writes:
> 
> > On Tue, Aug 07, 2018 at 09:05:28AM +0200, Rodolfo Medina wrote:
> >> Some little problems after `full-upgrade' to Sid: no sound...  Besides, 
> >> when
> >> trying to install new packages, the following message appears:
> >> 
> >> # aptitude install alsaplayer-alsa pulseaudio 
> >> pulseaudio is already installed at the requested version (12.0-1)
> >> pulseaudio is already installed at the requested version (12.0-1)
> >> The following NEW packages will be installed:
> >>   alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
> >> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
> >> Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
> >> Do you want to continue? [Y/n/?] y
> >> dpkg: warning: 'ldconfig' not found in PATH or not executable
> >> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> >> dpkg: error: 2 expected programs not found in PATH or not executable
> >> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and 
> >> /sbin
> >> E: Sub-process /usr/bin/dpkg returned an error code (2)
> >> dpkg: warning: 'ldconfig' not found in PATH or not executable
> >> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> >> dpkg: error: 2 expected programs not found in PATH or not executable
> >> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and 
> >> /sbin
> >> 
> >> Please help...  I'm not expert.
> >
> > Your installation lacks /sbin/ldconfig and /sbin/start-stop-daemon from
> > "libc-bin" and "dpkg" packages respectively. Or root's $PATH lack
> > "/sbin" somehow.
> > Either way it's not normal, it's a little wonder that you're able to
> > boot or run any binary executable.
> >
> >
> > I'd start fixing this mess by checking root's $PATH:
> >
> > echo $PATH
> >
> > It literally should have this value:
> >
> > /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
> >
> > Next I'd try this:
> >
> > apt-get install --reinstall dpkg libc-bin
> 
> 
> Thanks...  I'm afraid it's bad...:

No, it's a honest mistake on your part, not a misconfigured system.


> $ echo $PATH
> /home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
> rodolfo@sda6-acer:~$ su

Don't. Do. That. Ever.

'su' without arguments preserves your current environment.
$PATH suffers from this (which is annoying or overall bad in this case),
but unforeseen side effects (including root-owned files in your $HOME)
start with a single X client that you'll run as root.

It's called 'su -'. Use it instead.

Reco

Re: Please help with error message

[Rodolfo Medina]

Stephan Seitz  writes:

> On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:
>>$ echo $PATH
>>/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>>rodolfo@sda6-acer:~$ su
>>Password:
>
> You are using testing/unstable, aren’t you?
>
> The su binary was replaced with another one, and now Debian is breaking user
> space again. :-(
> Now su alone doesn’t change the path but keeps the user path. You have to use
> „su -”.
>
>  The util-linux implementation of /bin/su is now used, replacing the
>  one previously supplied by src:shadow (shipped in login package), and
>  bringing Debian in line with other modern distributions. The two
>  implementations are very similar but have some minor differences (and
>  there might be more that was not yet noticed ofcourse), e.g.
>
>  - new 'su' (with no args, i.e. when preserving the environment) also
>preserves PATH and IFS, while old su would always reset PATH and IFS
>even in 'preserve environment' mode.
>  - su '' (empty user string) used to give root, but now returns an error.
>  - previously su only had one pam config, but now 'su -' is configured
>separately in /etc/pam.d/su-l
>
>  The first difference is probably the most user visible one. Doing
>  plain 'su' is a really bad idea for many reasons, so using 'su -' is
>  strongly recommended to always get a newly set up environment similar
>  to a normal login. If you want to restore behaviour more similar to
>  the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.


Yes, if becoming root with with `su -' the error about what is the present
thread disappears...

Rodolfo

Re: Please help with error message

[Stephan Seitz]

On Di, Aug 07, 2018 at 10:08:06 +0200, Rodolfo Medina wrote:

$ echo $PATH
/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
rodolfo@sda6-acer:~$ su
Password:


You are using testing/unstable, aren’t you?

The su binary was replaced with another one, and now Debian is breaking 
user space again. :-(
Now su alone doesn’t change the path but keeps the user path. You have to 
use „su -”.


 The util-linux implementation of /bin/su is now used, replacing the
 one previously supplied by src:shadow (shipped in login package), and
 bringing Debian in line with other modern distributions. The two
 implementations are very similar but have some minor differences (and
 there might be more that was not yet noticed ofcourse), e.g.

 - new 'su' (with no args, i.e. when preserving the environment) also
   preserves PATH and IFS, while old su would always reset PATH and IFS
   even in 'preserve environment' mode.
 - su '' (empty user string) used to give root, but now returns an error.
 - previously su only had one pam config, but now 'su -' is configured
   separately in /etc/pam.d/su-l

 The first difference is probably the most user visible one. Doing
 plain 'su' is a really bad idea for many reasons, so using 'su -' is
 strongly recommended to always get a newly set up environment similar
 to a normal login. If you want to restore behaviour more similar to
 the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.

Shade and sweet water!

Stephan

--
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |


smime.p7s
Description: S/MIME cryptographic signature

Re: Please help with error message

[Rodolfo Medina]

Markus Schönhaber  writes:

>> Please help...  I'm not expert.
>
> In that case, you shouldn't use sid...

I'm thinking of that now...  I'v been using Sid for years and never had
problems...

Rodolfo

Re: Please help with error message

[Rodolfo Medina]

Erik Christiansen  writes:

> On 07.08.18 09:05, Rodolfo Medina wrote:
>> dpkg: warning: 'ldconfig' not found in PATH or not executable
>> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
>> dpkg: error: 2 expected programs not found in PATH or not executable
>> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
>
> Looks like your root $PATH is mangled. Could you post the output from:
>
> # echo $PATH
>
> Here I have:
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>
> That's consistent with what you read:
>
>> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin
>> and /sbin
>
> If setting up a proper root $PATH isn't the simple fix, then we need:
>
> # type ldconfig
>
> Here I have:   ldconfig is /sbin/ldconfig
> which will be found in root's PATH.

# type ldconfig
bash: type: ldconfig: not found

Thanks

Rodolfo

Re: Please help with error message

[Rodolfo Medina]

Reco  writes:

> On Tue, Aug 07, 2018 at 09:05:28AM +0200, Rodolfo Medina wrote:
>> Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
>> trying to install new packages, the following message appears:
>> 
>> # aptitude install alsaplayer-alsa pulseaudio 
>> pulseaudio is already installed at the requested version (12.0-1)
>> pulseaudio is already installed at the requested version (12.0-1)
>> The following NEW packages will be installed:
>>   alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
>> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
>> Do you want to continue? [Y/n/?] y
>> dpkg: warning: 'ldconfig' not found in PATH or not executable
>> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
>> dpkg: error: 2 expected programs not found in PATH or not executable
>> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
>> E: Sub-process /usr/bin/dpkg returned an error code (2)
>> dpkg: warning: 'ldconfig' not found in PATH or not executable
>> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
>> dpkg: error: 2 expected programs not found in PATH or not executable
>> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
>> 
>> Please help...  I'm not expert.
>
> Your installation lacks /sbin/ldconfig and /sbin/start-stop-daemon from
> "libc-bin" and "dpkg" packages respectively. Or root's $PATH lack
> "/sbin" somehow.
> Either way it's not normal, it's a little wonder that you're able to
> boot or run any binary executable.
>
>
> I'd start fixing this mess by checking root's $PATH:
>
> echo $PATH
>
> It literally should have this value:
>
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>
> Next I'd try this:
>
> apt-get install --reinstall dpkg libc-bin


Thanks...  I'm afraid it's bad...:

$ echo $PATH
/home/rodolfo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
rodolfo@sda6-acer:~$ su
Password: 
root@sda6-acer:/home/rodolfo# apt-get install --reinstall dpkg libc-bin
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-3.16.0-4-686-pae linux-image-4.11.0-2-686-pae 
linux-image-4.12.0-1-686-pae linux-image-4.12.0-2-686-pae 
linux-image-4.9.0-3-686-pae
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/2,952 kB of archives.
After this operation, 0 B of additional disk space will be used.
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)


Thanks,

Rodolfo

Re: Please help with error message

[Erik Christiansen]

On 07.08.18 09:05, Rodolfo Medina wrote:
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

Looks like your root $PATH is mangled. Could you post the output from:

# echo $PATH

Here I have:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

That's consistent with what you read:

> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin
> and /sbin

If setting up a proper root $PATH isn't the simple fix, then we need:

# type ldconfig

Here I have:   ldconfig is /sbin/ldconfig
which will be found in root's PATH.

If "type" returns a full path to ldconfig, then we need the output of:

$ ls -l /sbin/ldconfig # Or wherever your's finds it.

Does it have execute permission for root?

If that doesn't hit any paydirt, it would be interesting to see if you
have an ldconfig anywhere at all:

$ locate ldconfig

Erik

Re: Please help with error message

[Markus Schönhaber]

Rodolfo Medina, Di 07 Aug 2018 09:05:28 CEST:

> Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
> trying to install new packages, the following message appears:
> 
> # aptitude install alsaplayer-alsa pulseaudio 
> pulseaudio is already installed at the requested version (12.0-1)
> pulseaudio is already installed at the requested version (12.0-1)
> The following NEW packages will be installed:
>   alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
> Do you want to continue? [Y/n/?] y
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
> E: Sub-process /usr/bin/dpkg returned an error code (2)
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

Did you check the value of PATH - as the message suggests?
Did you check that (/sbin/)ldconfig and (/sbin/)start-stop-daemon exist
and they are executable?

> Please help...  I'm not expert.

In that case, you shouldn't use sid...

-- 
Regards
  mks

Re: Please help with error message

[Reco]

Hi.

On Tue, Aug 07, 2018 at 09:05:28AM +0200, Rodolfo Medina wrote:
> Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
> trying to install new packages, the following message appears:
> 
> # aptitude install alsaplayer-alsa pulseaudio 
> pulseaudio is already installed at the requested version (12.0-1)
> pulseaudio is already installed at the requested version (12.0-1)
> The following NEW packages will be installed:
>   alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
> 0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
> Do you want to continue? [Y/n/?] y
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
> E: Sub-process /usr/bin/dpkg returned an error code (2)
> dpkg: warning: 'ldconfig' not found in PATH or not executable
> dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
> dpkg: error: 2 expected programs not found in PATH or not executable
> Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
> 
> Please help...  I'm not expert.

Your installation lacks /sbin/ldconfig and /sbin/start-stop-daemon from
"libc-bin" and "dpkg" packages respectively. Or root's $PATH lack
"/sbin" somehow.
Either way it's not normal, it's a little wonder that you're able to
boot or run any binary executable.


I'd start fixing this mess by checking root's $PATH:

echo $PATH

It literally should have this value:

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Next I'd try this:

apt-get install --reinstall dpkg libc-bin

Reco

Please help with error message

[Rodolfo Medina]

Some little problems after `full-upgrade' to Sid: no sound...  Besides, when
trying to install new packages, the following message appears:

# aptitude install alsaplayer-alsa pulseaudio 
pulseaudio is already installed at the requested version (12.0-1)
pulseaudio is already installed at the requested version (12.0-1)
The following NEW packages will be installed:
  alsaplayer-alsa alsaplayer-common{a} alsaplayer-gtk{a} libmikmod3{a} 
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/505 kB of archives. After unpacking 1,410 kB will be used.
Do you want to continue? [Y/n/?] y
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin

Please help...  I'm not expert.

Thanks in advance,

Rodolfo

Re: Wine error message

[Gour]

On Sat, 4 Aug 2018 07:55:05 -0400
Carl Fink  wrote:

> For years, my policy has been to use stable on servers and testing
> on workstations.

For servers i'ts pretty much clear, but in regard to testing vs unstable this
was decisive part for me: "Testing has more up-to-date software than Stable,
and it breaks less often than Unstable. But when it breaks, it might take a
long time for things to get rectified. Sometimes this could be days and it
could be months at times. It also does not have permanent security support."
(https://www.debian.org/doc/manuals/debian-faq/ch-choosing.html)


Sincerely,
Gour

-- 
Abandoning all attachment to the results of his activities,
ever satisfied and independent, he performs no fruitive action,
although engaged in all kinds of undertakings.

Re: Wine error message

[Carl Fink]

On 08/04/2018 07:51 AM, Gour wrote:

However, 'stable' is too old for me, although I'll probably put it on my
relative's machined and between 'testing' and 'unstable' I believe
that the latter is bette option.



For years, my policy has been to use stable on servers and testing
on workstations.
--

Carl Fink  c...@finknetwork.com
Thinking and logic and stuff at Reasonably Literate
http://reasonablyliterate.com

Re: Wine error message

[Gour]

On Sat, 4 Aug 2018 07:16:47 -0400
Carl Fink  wrote:

> If you're looking for a more stable system, maybe the "unstable"
> distribution of Debian is not an ideal choice?

Well, in the past I spent >10yrs with rolling distros (Gentoo & Arch) and
thought that Fedora might be good option providign newer packages and I had
good experience with smoooth upgrades between releases, bつt last incidents
were too much and I never experienced such thing with Debian.

However, 'stable' is too old for me, although I'll probably put it on my
relative's machined and between 'testing' and 'unstable' I believe
that the latter is bette option.


Sincerely,
Gour

-- 
One who is not disturbed in mind even amidst the threefold
miseries or elated when there is happiness, and who is free
from attachment, fear and anger, is called a sage of steady mind.

Re: Wine error message

[Carl Fink]

On 08/04/2018 06:58 AM, Gour wrote:

Few days ago I migrated from Fedora (fc28) where I had serious issues with
4.17.x kernel series experiencing system hangs several times per day when
leaving my machine unattended to Debian Sid where there are nothing similar (so
far).


If you're looking for a more stable system, maybe the "unstable"
distribution of Debian is not an ideal choice?
--
Carl Fink  c...@finknetwork.com
Thinking and logic and stuff at Reasonably Literate
http://reasonablyliterate.com

Re: Wine error message

[Gour]

On Mon, 23 Jul 2018 14:56:56 +0200
floris  wrote:

> The Wine version in Debian Stable is very old and unsupported. You
> should use the WineHQ packages or use the version from Backports

Thank you for helpful advice!

Few days ago I migrated from Fedora (fc28) where I had serious issues with
4.17.x kernel series experiencing system hangs several times per day when
leaving my machine unattended to Debian Sid where there are nothing similar (so
far).

However, I have a need to run several apps under Wine, but attempt to install
it on my x86_64 was an impossible mission - it seems that wine32 is broken.
Finally, after enabling WineHQ repo and installing from there, eveything is
fine. :-)


Sincerely,
Gour

-- 
There is no possibility of one's becoming a yogī, O Arjuna,
if one eats too much or eats too little, sleeps too much
or does not sleep enough.

Re: Wine error message

[floris]

Richard Owlett schreef op 2018-07-24 23:00:

On 07/23/2018 07:56 AM, floris wrote:

Richard Owlett schreef op 2018-07-21 17:02:

Just installed/used wine for first time ever.


The Wine version in Debian Stable is very old and unsupported. You 
should use the WineHQ packages or use the version from Backports



Did that
done dat
I've T shirt



Which wine version do you use?





I attempted to run an installer which asks a typical set of questions
to which I chose the defaults. It is setup to run a demo on
completion. The demo appears to run correctly. I ran the same
installer on a WinXP machine which appears to run identically.

I have two problems.
On exiting the installer nothing has actually been written to disk


Wine uses a hidden folder ~/.wine as it default location. Did you 
check that location?


Non-informative


Maybe I don't understand your "nothing has actually been written to 
disk"
But when I try the installer with the default settings, the program is 
installed in:


$WINEPREFIX/drive_c/users//Local Settings/Application Data/OLB
(C:\users\\Local Settings\Application Data\OLB)
OLBLite.801  PocketOnlineBible.801

and
$WINEPREFIX/drive_c/Program Files (x86)/Bible
(C:\Program Files (x86)\Bible)
Desktop.Idt  HelpEng.Chm  messages.eng  Paragrap.map  TutorEng.Chm
Dsp.wav  IconsOlbDel.ExeSDPath.TxtVIReadMe.Eng
Go.Bat   Install.Msg  Olb.Exe   Std.wav   WhatsNew.Eng







Second, early in the question asking phase, a message appears on my 
console:

$ err:trash:TRASH_MoveFileToBucket Couldn't move file


That is the message that prompted this post.
What is it trying to say?
Is there a catalog of Wine error messages (didn't find one)?



In Wine version 3.12 there isn't such message.


Oh *NO*
u answered question ???


Every two weeks there is a new wine version with a lot of bug fixes. 
Probably this bug is resolved.

Now only a "fixme" warning is printed:
0009:fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH 
unimplemented


To answer your "is there a catalog of Wine error messages?" question.
No, there isn't a list with "error x happend ->  the message means this 
-> you should do this"




You could read the FAQ, the manual and the forum on winehq.org if you 
look for error messages.


*SNICKER*

I was vainly attempting to determine that what I saw on my console was
a WINE or an APPLICATION error message.

It has been *YEARS* since I've actually used my WinXP machine. Don't
know how to copy/find appropriate file(s) on my WinXp machine in order
that WINE might attempt to execute.


---
Floris

Re: Wine error message

[Richard Owlett]

On 07/25/2018 04:04 AM, Curt wrote:

On 2018-07-24, Richard Owlett  wrote:


I was vainly attempting to determine that what I saw on my console was a
WINE or an APPLICATION error message.



Looks like it's coming from wine.

https://github.com/wine-mirror/wine/blob/master/dlls/shell32/trash.c

static BOOL TRASH_MoveFileToBucket(TRASH_BUCKET *pBucket, const char *unix_path)
{
 struct stat file_stat;
 char *trash_file_name = NULL;
 char *trash_path = NULL;
 BOOL ret = TRUE;

 if (lstat(unix_path, _stat)==-1)
 return FALSE;
 if (!file_good_for_bucket(pBucket, _stat))
 return FALSE;
 
 trash_file_name = create_trashinfo(pBucket->info_dir, unix_path);

 if (trash_file_name == NULL)
 return FALSE;
 
 trash_path = SHAlloc(strlen(pBucket->files_dir)+strlen(trash_file_name)+1);

 if (trash_path == NULL) goto error;
 lstrcpyA(trash_path, pBucket->files_dir);
 lstrcatA(trash_path, trash_file_name);
 
 if (rename(unix_path, trash_path)==0)

 {
 TRACE("rename succeeded\n");
 goto cleanup;
 }
 
 /* TODO: try to manually move the file */

ERR("Couldn't move file\n");
 **



Thank you.

Re: Wine error message

[Curt]

On 2018-07-24, Richard Owlett  wrote:
>
> I was vainly attempting to determine that what I saw on my console was a 
> WINE or an APPLICATION error message.
>

Looks like it's coming from wine.

https://github.com/wine-mirror/wine/blob/master/dlls/shell32/trash.c

static BOOL TRASH_MoveFileToBucket(TRASH_BUCKET *pBucket, const char *unix_path)
{
struct stat file_stat;
char *trash_file_name = NULL;
char *trash_path = NULL;
BOOL ret = TRUE;

if (lstat(unix_path, _stat)==-1)
return FALSE;
if (!file_good_for_bucket(pBucket, _stat))
return FALSE;

trash_file_name = create_trashinfo(pBucket->info_dir, unix_path);
if (trash_file_name == NULL)
return FALSE;

trash_path = SHAlloc(strlen(pBucket->files_dir)+strlen(trash_file_name)+1);
if (trash_path == NULL) goto error;
lstrcpyA(trash_path, pBucket->files_dir);
lstrcatA(trash_path, trash_file_name);

if (rename(unix_path, trash_path)==0)
{
TRACE("rename succeeded\n");
goto cleanup;
}

/* TODO: try to manually move the file */
ERR("Couldn't move file\n");
**

-- 
Boris sober and Boris drunk are such different people, they’ve never even met. 
-- Sergei Dovlatov, Pushkin Hills

Re: Wine error message

[Richard Owlett]

On 07/23/2018 07:56 AM, floris wrote:

Richard Owlett schreef op 2018-07-21 17:02:

Just installed/used wine for first time ever.


The Wine version in Debian Stable is very old and unsupported. You 
should use the WineHQ packages or use the version from Backports



Did that
done dat
I've T shirt





I attempted to run an installer which asks a typical set of questions
to which I chose the defaults. It is setup to run a demo on
completion. The demo appears to run correctly. I ran the same
installer on a WinXP machine which appears to run identically.

I have two problems.
On exiting the installer nothing has actually been written to disk


Wine uses a hidden folder ~/.wine as it default location. Did you check 
that location?


Non-informative



Second, early in the question asking phase, a message appears on my 
console:

$ err:trash:TRASH_MoveFileToBucket Couldn't move file


That is the message that prompted this post.
What is it trying to say?
Is there a catalog of Wine error messages (didn't find one)?



In Wine version 3.12 there isn't such message.


Oh *NO*
u answered question ???

You could read the FAQ, the manual and the forum on winehq.org if you 
look for error messages.


*SNICKER*

I was vainly attempting to determine that what I saw on my console was a 
WINE or an APPLICATION error message.


It has been *YEARS* since I've actually used my WinXP machine. Don't 
know how to copy/find appropriate file(s) on my WinXp machine in order 
that WINE might attempt to execute.

Re: Wine error message

[floris]

Richard Owlett schreef op 2018-07-21 17:02:

Just installed/used wine for first time ever.


The Wine version in Debian Stable is very old and unsupported. You 
should use the WineHQ packages or use the version from Backports




I attempted to run an installer which asks a typical set of questions
to which I chose the defaults. It is setup to run a demo on
completion. The demo appears to run correctly. I ran the same
installer on a WinXP machine which appears to run identically.

I have two problems.
On exiting the installer nothing has actually been written to disk


Wine uses a hidden folder ~/.wine as it default location. Did you check 
that location?


Second, early in the question asking phase, a message appears on my 
console:

$ err:trash:TRASH_MoveFileToBucket Couldn't move file


That is the message that prompted this post.
What is it trying to say?
Is there a catalog of Wine error messages (didn't find one)?



In Wine version 3.12 there isn't such message.
You could read the FAQ, the manual and the forum on winehq.org if you 
look for error messages.


---
Floris

Wine error message

[Richard Owlett]

Just installed/used wine for first time ever.
I attempted to run an installer which asks a typical set of questions to 
which I chose the defaults. It is setup to run a demo on completion. The 
demo appears to run correctly. I ran the same installer on a WinXP 
machine which appears to run identically.


I have two problems.
On exiting the installer nothing has actually been written to disk
Second, early in the question asking phase, a message appears on my console:

$ err:trash:TRASH_MoveFileToBucket Couldn't move file


That is the message that prompted this post.
What is it trying to say?
Is there a catalog of Wine error messages (didn't find one)?

I have reason to doubt the first problem is a bug in wine &/or Debian.
Long after the error message above appears, there is an *installer* 
warning that "a non wine program is being executed under wine". I 
suspect that the wine compliant version requires a paid unlock code - 
there are ambiguities on the website that I've already reported.


I suspect the error message quoted above is either a wine bug or 
something strange about my system.


The installer is [install_advance_5.40.00.00.exe] from 
[https://onlinebible.net/].


Comments?
TIA

Re: Synaptic error message -- indicates repository malfunction

[Richard Owlett]

On 02/19/2018 09:20 AM, Brad Rogers wrote:

On Mon, 19 Feb 2018 09:14:41 -0600
Richard Owlett  wrote:

Hello Richard,


I did 'apt-get update' followed by re-launching Synaptic.


What's wrong with Synaptic's "Reload" button?



I believe a wise guru has said:
"The blindingly obvious is never immediately apparent"

IOW Mr. Sánchez had mentioned 'apt-get update' ;/

Re: Synaptic error message -- indicates repository malfunction

[Brad Rogers]

On Mon, 19 Feb 2018 09:14:41 -0600
Richard Owlett  wrote:

Hello Richard,

>I did 'apt-get update' followed by re-launching Synaptic.

What's wrong with Synaptic's "Reload" button?

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Buy some love at the five and dime
You Have Placed A Chill In My Heart - Eurythmics


pgpQBBMaiNK9J.pgp
Description: OpenPGP digital signature

Re: Synaptic error message -- indicates repository malfunction

[Richard Owlett]

On 02/19/2018 08:57 AM, Roberto C. Sánchez wrote:

On Mon, Feb 19, 2018 at 08:44:26AM -0600, Richard Owlett wrote:

I just attempted to install kde-baseapps-bin via Synaptic.
I received a message stating

W: Failed to fetch 
http://security.debian.org/debian-security/pool/updates/main/p/poppler/libpoppler-qt5-1_0.48.0-2+deb9u1_i386.deb
   404  Not Found [*]



* is an IP address, deleted as I didn't know whose it was
Known problem?
Where should it be reported?


There is nothing to report:

$ apt-cache policy libpoppler-qt5-1
libpoppler-qt5-1:
   Installed: (none)
   Candidate: 0.48.0-2+deb9u2

The current version is 0.48.0-2+deb9u2 but your system thinks it is
0.48.0-2+deb9u1. You need to update your package cache (from the command
line it is 'apt-get update', I am not sure about synaptic).

Once the 0.48.0-2+deb9u2 package was uploaded the old version,
0.48.0-2+deb9u1, was not referred to by any Debian release and the
archive software eventually cleaned it out.

Regards,

-Roberto



I did 'apt-get update' followed by re-launching Synaptic.
Synaptic warned of me of a "a broken package", prompting me to fix it.
I did and then clicked "Apply".
Synaptic was now happy.
Thank you.
I'll be able to reboot shortly to see if all OK.

Re: Synaptic error message -- indicates repository malfunction

[Roberto C . Sánchez]

On Mon, Feb 19, 2018 at 08:44:26AM -0600, Richard Owlett wrote:
> I just attempted to install kde-baseapps-bin via Synaptic.
> I received a message stating
> > W: Failed to fetch 
> > http://security.debian.org/debian-security/pool/updates/main/p/poppler/libpoppler-qt5-1_0.48.0-2+deb9u1_i386.deb
> >   404  Not Found [*]
> 
> 
> * is an IP address, deleted as I didn't know whose it was
> Known problem?
> Where should it be reported?
> 
There is nothing to report:

$ apt-cache policy libpoppler-qt5-1
libpoppler-qt5-1:
  Installed: (none)
  Candidate: 0.48.0-2+deb9u2

The current version is 0.48.0-2+deb9u2 but your system thinks it is
0.48.0-2+deb9u1. You need to update your package cache (from the command
line it is 'apt-get update', I am not sure about synaptic).

Once the 0.48.0-2+deb9u2 package was uploaded the old version,
0.48.0-2+deb9u1, was not referred to by any Debian release and the
archive software eventually cleaned it out.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Synaptic error message -- indicates repository malfunction

[Richard Owlett]

I just attempted to install kde-baseapps-bin via Synaptic.
I received a message stating

W: Failed to fetch 
http://security.debian.org/debian-security/pool/updates/main/p/poppler/libpoppler-qt5-1_0.48.0-2+deb9u1_i386.deb
  404  Not Found [*]



* is an IP address, deleted as I didn't know whose it was
Known problem?
Where should it be reported?

Re: `Filter failed' no print error message

[Brian]

On Mon 27 Mar 2017 at 18:22:04 +0100, Rodolfo Medina wrote:

> Brian  writes:
> 
> > How about
> >
> >  cupsfilter /etc/nsswitch > out.prn ?
> >
> > That should give more than one line of output.
> >
> > (Unable to determine MIME type of "/etc/nsswitch" is perturbing).
> 
> In this case, the output is:
> 
>  cupsfilter: Unable to determine MIME type of "/etc/nsswitch".
> 
> on both machines...

I chose /etc/nsswitch because it is a *small* ASCII text file and any
output would not be too large to send here.

Try the cupsfilter commands with /etc/services or any other text file.
Also try PDFs.

-- 
Brian.

Re: `Filter failed' no print error message

[Rodolfo Medina]

Brian  writes:

> On Mon 27 Mar 2017 at 16:04:31 +0100, Rodolfo Medina wrote:
>
>> Brian  writes:
>> 
>> > Please would you repeat the command
>> >
>> >  cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo
>> > /etc/nsswitch -e > out.prn 2> log
>> >
>> > and post again.
>> 
>> Now they are both:
>> 
>> cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK
>> (040755/uid=0/gid=0).
>> cupsfilter: File "/usr/lib/cups/filter/commandtops" permissions OK
>> (040755/uid=0/gid=0).
>> cupsfilter: Unable to determine MIME type of "/etc/nsswitch".
>
> The output should be at least a screenful of text. Do you still get your
> previous output with
>
>  cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo
> /etc/nsswitch -e > out.prn ?
>
> That is, don't direct the error output to a file but to the screen.

Yes, same as previous...


> How about
>
>  cupsfilter /etc/nsswitch > out.prn ?
>
> That should give more than one line of output.
>
> (Unable to determine MIME type of "/etc/nsswitch" is perturbing).

In this case, the output is:

 cupsfilter: Unable to determine MIME type of "/etc/nsswitch".

on both machines...

Thanks,

Rodolfo

Re: `Filter failed' no print error message

[Brian]

On Mon 27 Mar 2017 at 16:04:31 +0100, Rodolfo Medina wrote:

> Brian  writes:
> 
> > Please would you repeat the command
> >
> >  cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo
> > /etc/nsswitch -e > out.prn 2> log
> >
> > and post again.
> 
> Now they are both:
> 
> cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK
> (040755/uid=0/gid=0).
> cupsfilter: File "/usr/lib/cups/filter/commandtops" permissions OK
> (040755/uid=0/gid=0).
> cupsfilter: Unable to determine MIME type of "/etc/nsswitch".

The output should be at least a screenful of text. Do you still get your
previous output with

 cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo 
/etc/nsswitch -e > out.prn ?

That is, don't direct the error output to a file but to the screen.

How about

 cupsfilter /etc/nsswitch > out.prn ?

That should give more than one line of output.

(Unable to determine MIME type of "/etc/nsswitch" is perturbing).

-- 
Brian.

Re: `Filter failed' no print error message

[Rodolfo Medina]

Brian  writes:

> On Mon 27 Mar 2017 at 14:29:31 +0100, Rodolfo Medina wrote:
>
>> Brian  writes:
>> 
>> > I suppose this is the printer:
>> >
>> >  http://www.samsung.com/uk/support/model/ML-1910/SEE
>> 
>> Rather this:
>> 
>>  http://www.samsung.com/uk/support/model/ML-1915/SEE
>
> It doesn't matter. You'll gat the same uld file for both.
>
>> > There is a "Downloads" section. Click "SEE MORE". You want to download
>> > "Printing & Scan Driver ver V1.00.06, Linux".
>> 
>> Thanks, I will.
>> 
>> 
>> >> > Please run
>> >> >
>> >> >  cupsfilter --list-filters -p /etc/cups/ppd/ -m printer/foo
>> >> >  -e > out.prn 2> log
>> >> >
>> >> > on both machines. A PDF or a text file would do for . Post the
>> >> > two logs you get.
>> >> 
>> >> I suppose you mean something like:
>> >> 
>> >>  # cupsfilter --list-filters -p
>> >> /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo  -e >
>> >> out.prn 2> log
>> >
>> > That's fine, but do not use the --list-filters option. In other words:
>> >
>> > cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo
>> > /etc/nsswitch -e > out.prn 2> log
>> >
>> > and post the logs.
>> >
>> >> , but what in place of `printer/foo' and ?
>> >
>> > printer/foo is ok. Use /etc/nsswitch for .
>> 
>> >From the non-working machine:
>> 
>> cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK
>> (040755/uid=0/gid=0).
>> cupsfilter: Unable to determine MIME type of "/etc/nsswitch".
>> 
>> 
>> , and from the working:
>> 
>> cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK
>> (040755/uid=0/gid=0).
>> cupsfilter: File "/usr/lib/cups/filter/commandtops" permissions OK
>> (040755/uid=0/gid=0).
>> cupsfilter: Unable to determine MIME type of "/etc/nsswitch".
>
> You were particlarly asked not to use the --list-filters switch.

In fact I didn't use it at all.


> Please would you repeat the command
>
>  cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo
> /etc/nsswitch -e > out.prn 2> log
>
> and post again.


Now they are both:

cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK
(040755/uid=0/gid=0).
cupsfilter: File "/usr/lib/cups/filter/commandtops" permissions OK
(040755/uid=0/gid=0).
cupsfilter: Unable to determine MIME type of "/etc/nsswitch".

Thanks,

Rodolfo

Re: `Filter failed' no print error message

[Brian]

On Mon 27 Mar 2017 at 14:29:31 +0100, Rodolfo Medina wrote:

> Brian  writes:
> 
> > I suppose this is the printer:
> >
> >  http://www.samsung.com/uk/support/model/ML-1910/SEE
> 
> Rather this:
> 
>  http://www.samsung.com/uk/support/model/ML-1915/SEE

It doesn't matter. You'll gat the same uld file for both.

> > There is a "Downloads" section. Click "SEE MORE". You want to download
> > "Printing & Scan Driver ver V1.00.06, Linux".
> 
> Thanks, I will.
> 
> 
> >> > Please run
> >> >
> >> >  cupsfilter --list-filters -p /etc/cups/ppd/ -m printer/foo
> >> >  -e > out.prn 2> log
> >> >
> >> > on both machines. A PDF or a text file would do for . Post the
> >> > two logs you get.
> >> 
> >> I suppose you mean something like:
> >> 
> >>  # cupsfilter --list-filters -p 
> >> /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo  -e > 
> >> out.prn 2> log
> >
> > That's fine, but do not use the --list-filters option. In other words:
> >
> > cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo
> > /etc/nsswitch -e > out.prn 2> log
> >
> > and post the logs.
> >
> >> , but what in place of `printer/foo' and ?
> >
> > printer/foo is ok. Use /etc/nsswitch for .
> 
> >From the non-working machine:
> 
> cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK 
> (040755/uid=0/gid=0).
> cupsfilter: Unable to determine MIME type of "/etc/nsswitch".
> 
> 
> , and from the working:
> 
> cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK 
> (040755/uid=0/gid=0).
> cupsfilter: File "/usr/lib/cups/filter/commandtops" permissions OK 
> (040755/uid=0/gid=0).
> cupsfilter: Unable to determine MIME type of "/etc/nsswitch".

You were particlarly asked not to use the --list-filters switch. Please
would you repeat the command

 cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo 
/etc/nsswitch -e > out.prn 2> log

and post again.

-- 
Brian.

Re: `Filter failed' no print error message

[Rodolfo Medina]

Brian  writes:

> I suppose this is the printer:
>
>  http://www.samsung.com/uk/support/model/ML-1910/SEE

Rather this:

 http://www.samsung.com/uk/support/model/ML-1915/SEE


> There is a "Downloads" section. Click "SEE MORE". You want to download
> "Printing & Scan Driver ver V1.00.06, Linux".

Thanks, I will.


>> > Please run
>> >
>> >  cupsfilter --list-filters -p /etc/cups/ppd/ -m printer/foo
>> >  -e > out.prn 2> log
>> >
>> > on both machines. A PDF or a text file would do for . Post the
>> > two logs you get.
>> 
>> I suppose you mean something like:
>> 
>>  # cupsfilter --list-filters -p 
>> /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo  -e > 
>> out.prn 2> log
>
> That's fine, but do not use the --list-filters option. In other words:
>
> cupsfilter -p /etc/cups/ppd/Samsung_ML-191x_252x_Series.ppd -m printer/foo
> /etc/nsswitch -e > out.prn 2> log
>
> and post the logs.
>
>> , but what in place of `printer/foo' and ?
>
> printer/foo is ok. Use /etc/nsswitch for .

>From the non-working machine:

cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK 
(040755/uid=0/gid=0).
cupsfilter: Unable to determine MIME type of "/etc/nsswitch".


, and from the working:

cupsfilter: File "/usr/lib/cups/filter/rastertosamsungspl" permissions OK 
(040755/uid=0/gid=0).
cupsfilter: File "/usr/lib/cups/filter/commandtops" permissions OK 
(040755/uid=0/gid=0).
cupsfilter: Unable to determine MIME type of "/etc/nsswitch".


Thanks,

Rodolfo