Re: advanced scripting problems - or wrong approach?

[David Christensen]

On 6/2/24 21:35, DdB wrote:

Am 02.06.2024 um 02:41 schrieb DdB:

Will share my findings, once i made more progress...


Here is what i've got before utilizing it:



datakanja@PBuster-NFox:/mnt/tmp$ cat test
#!/bin/bash -e
# testing usefulness of coprocess to control host and backup machine from a 
single script.
# beware: do not use subprocesses or pipes, as that will confuse the pipes 
setup by coproc!
# At this point, this interface may not be very flexible
# but trying to follow best practices for using coproc in bash scripts
# todo (deferred): how to handle stderr inside coproc?
# todo (deferred): what, if coproc dies unexpectedly?

# setting up the coprocess:
stdout_to_ssh_stdin=5 # arbitrary choice outside the range of used file 
desciptors
stdin_from_ssh_stdout=6

coproc SSH { bash; } # for testing purposes, i refrain from really 
involving ssh just yet and replace it with bash:

# save filedescriptors by duplicating them:
eval "exec ${stdin_from_ssh_stdout}<&${SSH[0]} 
${stdout_to_ssh_stdin}>&${SSH[1]}"
echo The PID of the coproc is: $SSH_PID # possibly useful for inspection

unique_eof_delimirer=""
line=""
# collect the output available and print it locally (synchonous):
function print-immediate-output () {
while IFS= read -r -u "${stdin_from_ssh_stdout}" line
do
if [[ "${line:0-5:5}" == "$unique_eof_delimirer" ]] # currently, 
the length is fixed
then
line="${line%}"
if [[ ! -z $line ]]
then
printf '%s\n' "$line"
fi
break
fi
printf '%s\n' "$line"
done
}

# send a single command via ssh and print output locally
function send-single-ssh-command () {
printf '%s\n' "$@" >&"${stdout_to_ssh_stdin}"
printf '%s\n' "echo '"$unique_eof_delimirer"'" 
>&"${stdout_to_ssh_stdin}"
print-immediate-output
}


send-single-ssh-command "find . -maxdepth 1 -name [a-z]\*" # more or less a 
standard command, that succeeds
send-single-ssh-command "ls nothin" # more or less a standard command, that 
fails

# tearing down the coprocess:
printf "%s\n" "exit" >&"${stdout_to_ssh_stdin}" # not interested in any 
more output (probably none)
wait
# Descriptors must be closed to prevent leaking.
eval "exec ${stdin_from_ssh_stdout}<&- ${stdout_to_ssh_stdin}>-"

echo "waited for the coproc to end gracefully, done"

datakanja@PBuster-NFox:/mnt/tmp$ ./test
The PID of the coproc is: 28154
./test
./out
ls: Zugriff auf 'nothin' nicht möglich: Datei oder Verzeichnis nicht gefunden
waited for the coproc to end gracefully, done
datakanja@PBuster-NFox:/mnt/tmp$



"test" is both a program and a shell builtin.  I suggest that you pick 
another, non-keyword, name for your script.



I suggest adding the Bash option "-u' (nounset).


Your file descriptor duplication, redirection, etc., seems overly 
complex.  Would not it be easier to use the coproc handles directly?


2024-06-03 08:49:41 dpchrist@laalaa ~/sandbox/bash
$ nl coproc-demo
 1  #!/usr/bin/env bash
 2  # $Id: coproc-demo,v 1.3 2024/06/03 15:49:36 dpchrist Exp $
 3  set -e
 4  set -u
 5  coproc COPROC { bash ; }
 6  echo 'echo "hello, world!"' >&"${COPROC[1]}"
 7  read -r reply <&"${COPROC[0]}"
 8  echo $reply
 9  echo "exit" >&"${COPROC[1]}"
10  wait $COPROC_PID

2024-06-03 08:49:44 dpchrist@laalaa ~/sandbox/bash
$ bash -x coproc-demo
+ set -e
+ set -u
+ echo 'echo "hello, world!"'
+ bash
+ read -r reply
+ echo hello, 'world!'
hello, world!
+ echo exit
+ wait 4229


David

Re: advanced scripting problems - or wrong approach?

[Jonathan Dowland]

On Sat Jun 1, 2024 at 8:20 AM BST, DdB wrote:
> for years have i been using a self-made backup script, that did mount a
> drive via USB, performed all kinds of plausibility checks, before
> actually backing up incrementally. Finally verifying success and logging
> the activities while kicking the ISB drive out.

I'd keep using this for now, if I were you, and work on
implementing/fixing a replacement at the same time, and only stop doing
the simple solution when the newer solution has reached the same level
of reliability.

-- 
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: advanced scripting problems - or wrong approach?

[DdB]

Am 02.06.2024 um 02:41 schrieb DdB:
> Will share my findings, once i made more progress...

Here is what i've got before utilizing it:


> datakanja@PBuster-NFox:/mnt/tmp$ cat test 
> #!/bin/bash -e
> # testing usefulness of coprocess to control host and backup machine from a 
> single script.
> # beware: do not use subprocesses or pipes, as that will confuse the pipes 
> setup by coproc!
> # At this point, this interface may not be very flexible
> # but trying to follow best practices for using coproc in bash scripts
> # todo (deferred): how to handle stderr inside coproc?
> # todo (deferred): what, if coproc dies unexpectedly?
> 
>   # setting up the coprocess:
>   stdout_to_ssh_stdin=5 # arbitrary choice outside the range of used file 
> desciptors
>   stdin_from_ssh_stdout=6
> 
>   coproc SSH { bash; } # for testing purposes, i refrain from really 
> involving ssh just yet and replace it with bash:
> 
>   # save filedescriptors by duplicating them:
>   eval "exec ${stdin_from_ssh_stdout}<&${SSH[0]} 
> ${stdout_to_ssh_stdin}>&${SSH[1]}"
>   echo The PID of the coproc is: $SSH_PID # possibly useful for inspection
> 
> unique_eof_delimirer=""
> line=""
> # collect the output available and print it locally (synchonous):
> function print-immediate-output () {
>   while IFS= read -r -u "${stdin_from_ssh_stdout}" line
>   do
>   if [[ "${line:0-5:5}" == "$unique_eof_delimirer" ]] # currently, 
> the length is fixed
>   then
>   line="${line%}"
>   if [[ ! -z $line ]]
>   then
>   printf '%s\n' "$line"
>   fi
>   break
>   fi 
>   printf '%s\n' "$line"
>   done
> }
> 
> # send a single command via ssh and print output locally
> function send-single-ssh-command () {
>   printf '%s\n' "$@" >&"${stdout_to_ssh_stdin}"
>   printf '%s\n' "echo '"$unique_eof_delimirer"'" 
> >&"${stdout_to_ssh_stdin}"
>   print-immediate-output
> }
> 
> 
> send-single-ssh-command "find . -maxdepth 1 -name [a-z]\*" # more or less a 
> standard command, that succeeds
> send-single-ssh-command "ls nothin" # more or less a standard command, that 
> fails
> 
>   # tearing down the coprocess:
>   printf "%s\n" "exit" >&"${stdout_to_ssh_stdin}" # not interested in any 
> more output (probably none)
>   wait
>   # Descriptors must be closed to prevent leaking.
>   eval "exec ${stdin_from_ssh_stdout}<&- ${stdout_to_ssh_stdin}>-"
> 
>   echo "waited for the coproc to end gracefully, done"
> 
> datakanja@PBuster-NFox:/mnt/tmp$ ./test
> The PID of the coproc is: 28154
> ./test
> ./out
> ls: Zugriff auf 'nothin' nicht möglich: Datei oder Verzeichnis nicht gefunden
> waited for the coproc to end gracefully, done
> datakanja@PBuster-NFox:/mnt/tmp$ 

Re: advanced scripting problems - or wrong approach?

[DdB]

Am 01.06.2024 um 16:01 schrieb Greg Wooledge:
>> i get the output from ls, but then the thing is hanging indefinitely,
>> apparently not reaching the exit line. :(
> Your first while loop never terminates.  "while read ..." continues
> running until read returns a nonzero exit status, either due to an
> error or EOF.  Your coproc never returns EOF, so the "while read"
> loop just keeps waiting for the next line of output from ls.
> 
> If you're going to communicate with a long-running process that can
> return multiple lines of output per line of input, then you have
> three choices:
> 
>   1) Arrange for some way to communicate how many lines, or bytes,
>  of output are going to be given.
> 
>   2) Send a terminator line (or byte sequence) of some kind that
>  indicates "end of current data set".
> 
>   3) Give up and assume the end of the data set after a certain amount
>  of time has elapsed with no new output arriving.  (This is usually
>  not the best choice.)
> 
> These same design issues occur in any kind of network communication, too.
> Imagine an IMAP client or something, which holds open a network connection
> to its IMAP server.  The client asks for the body of an email message,
> but needs to keep the connection open afterward so that it can ask for
> more things later.  The server has to be able to send the message back
> without closing the connection at the end.  Therefore, the IMAP protocol
> needs some way to "encapsulate" each server response, so the client
> knows when it has received the full message.

WOW!
Just wow, Greg, thank you so much!

After receiving such a wonderful hint/explanation, i did verify it being
correct and got overwhelmed with good feelings, as it allows me to learn
and experiment some more, heading in the direction of possibly solving
my initial problem.

Will share my findings, once i made more progress...

With appreciation, respect, admiration and love.
DdB

Re: advanced scripting problems - or wrong approach?

[David Christensen]

On 6/1/24 00:20, DdB wrote:

Hello,

for years have i been using a self-made backup script, that did mount a
drive via USB, performed all kinds of plausibility checks, before
actually backing up incrementally. Finally verifying success and logging
the activities while kicking the ISB drive out.

Since a few months, i do have a real backup server instead, connecting
to it via ssh i was able to have 2 terminals open and back up manually.
Last time, i introduced a mistake by accident and since, i am trying to
automate the whole thing once again, but that is difficult, as the load
on the net is huge, mbuffer is useful in that regard. So i was intending
to have just one script for all the operations using coproc to
coordinate the 2 servers.

But weird things are going on, i cant reliably communicate between host
and backup server, at least not automatically.

Searching the web, i found:
https://github.com/reconquest/coproc.bash/blob/master/REFERENCE.md
But i was unable to get this to work, which seems to indicate, that i am
misunderstanding something.
The only success i had was to "talk" to a chess engine in a coprocess,
which did go well. But neither bash nor ssh are cooperating, i may have
timing issues with the pipes or some other side effects.

How can i describe? For example if i start this:

#!/bin/bash -e

coproc { bash; }
exec 5<&${COPROC[0]} 6>&${COPROC[1]}
fd=5

echo "ls" >&6
while IFS= read -ru $fd line
do
 printf '%s\n' "$line"
done

printf "%s\n" "sleep 3;exit" >&6
while IFS= read -ru $fd line
do
 printf '%s\n' "$line"
done

exec 5<&- 6>&-

wait
echo waited, done


i get the output from ls, but then the thing is hanging indefinitely,
apparently not reaching the exit line. :(

Anyone who can share his experience to advance my experimenting?
DdB




https://en.wikipedia.org/wiki/XY_problem


Please define the root problem you are trying to solve.


David

Re: advanced scripting problems - or wrong approach?

[Greg Wooledge]

On Sat, Jun 01, 2024 at 09:20:59AM +0200, DdB wrote:
> > #!/bin/bash -e
> > 
> > coproc { bash; }
> > exec 5<&${COPROC[0]} 6>&${COPROC[1]}
> > fd=5
> > 
> > echo "ls" >&6
> > while IFS= read -ru $fd line
> > do
> > printf '%s\n' "$line"
> > done
> > 
> > printf "%s\n" "sleep 3;exit" >&6
> > while IFS= read -ru $fd line
> > do
> > printf '%s\n' "$line"
> > done
> > 
> > exec 5<&- 6>&-
> > 
> > wait
> > echo waited, done
> 
> i get the output from ls, but then the thing is hanging indefinitely,
> apparently not reaching the exit line. :(

Your first while loop never terminates.  "while read ..." continues
running until read returns a nonzero exit status, either due to an
error or EOF.  Your coproc never returns EOF, so the "while read"
loop just keeps waiting for the next line of output from ls.

If you're going to communicate with a long-running process that can
return multiple lines of output per line of input, then you have
three choices:

  1) Arrange for some way to communicate how many lines, or bytes,
 of output are going to be given.

  2) Send a terminator line (or byte sequence) of some kind that
 indicates "end of current data set".

  3) Give up and assume the end of the data set after a certain amount
 of time has elapsed with no new output arriving.  (This is usually
 not the best choice.)

These same design issues occur in any kind of network communication, too.
Imagine an IMAP client or something, which holds open a network connection
to its IMAP server.  The client asks for the body of an email message,
but needs to keep the connection open afterward so that it can ask for
more things later.  The server has to be able to send the message back
without closing the connection at the end.  Therefore, the IMAP protocol
needs some way to "encapsulate" each server response, so the client
knows when it has received the full message.

Re: advanced scripting problems - or wrong approach?

[tomas]

On Sat, Jun 01, 2024 at 10:53:45AM +0200, DdB wrote:
> Am 01.06.2024 um 09:20 schrieb DdB:
> > Hello,
> > 
> I get it: you wouldnt trust my scripts.

That wasn't the point. I'm just not in the situation to
debug it at the moment.

> Thats fine with me. But my
> experience is quite different: Software, i prefer using is such, that i
> keep control.

Definitely -- that's why I concoct my backup scripts myself.
I was rather commenting at the concrete construction (that
is: concurrent processes communicating over two way pipes),
which seems somewhat fragile to me. If you haven't async
primitives, as in the shell, you might bump into deadlocks
sooner rather than later :-)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: advanced scripting problems - or wrong approach?

[DdB]

Am 01.06.2024 um 09:20 schrieb DdB:
> Hello,
> 
I get it: you wouldnt trust my scripts. Thats fine with me. But my
experience is quite different: Software, i prefer using is such, that i
keep control. And because backup means different things to different
people, i did not bother to explain, what i meant. (btw: i use rsync in
other places, but for backups, i do prefer zfs snapshots.)
The whole content is irrelevant to some extent. I dared to say what i want:
Stop doing backups manually and get my backup routine back, therefore
i'd love to have a single script doing exactly what i want in the exact
order i want, and as the backup takes more than one hour, i thought an
asynchronous process ould be appropriate...

Re: advanced scripting problems - or wrong approach?

[tomas]

On Sat, Jun 01, 2024 at 08:20:08AM +, Michael Kjörling wrote:
> On 1 Jun 2024 10:11 +0200, from to...@tuxteam.de:
> >> for years have i been using a self-made backup script [...]
> > 
> > I won't get into that -- I can't even fathom why you'd need coproc
> > for a backup script. I tend to keep things simple -- they tend to
> > thank me in failing less often and in more understandable ways.
> 
> I agree. There are plenty enough of ready-made backup solutions to
> cater to different needs that making one's own shouldn't be needed.

(Full disclosure: I do mine with a shell script wrapped around
rsync, and using its wonderful "dir-merge" feature to fine tune
what to leave out).

[...]

> > I didn't try your script, but may be there is a "\n" missing down
> > there?
> > 
> >>> printf "%s\n" "sleep 3;exit" >&6
> >  ^^^
>   ^^

Good catch, thanks Michael -- to DdB: please, disregard my hunch. I
didn't look closely enough.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: advanced scripting problems - or wrong approach?

[Michael Kjörling]

On 1 Jun 2024 10:11 +0200, from to...@tuxteam.de:
>> for years have i been using a self-made backup script [...]
> 
> I won't get into that -- I can't even fathom why you'd need coproc
> for a backup script. I tend to keep things simple -- they tend to
> thank me in failing less often and in more understandable ways.

I agree. There are plenty enough of ready-made backup solutions to
cater to different needs that making one's own shouldn't be needed.

Depending on the format you want your backup in, it's quite possible
that a simple rsync invocation would do. rsnapshot works on top of
rsync and gives you incremental backups with history. That's what I
use (plus some surrounding homegrown scripts, particularly one to
implement a more intelligent old backups purge policy than what
rsnapshot itself offers) and it has worked near perfectly for probably
a decade.


> I didn't try your script, but may be there is a "\n" missing down
> there?
> 
>>> printf "%s\n" "sleep 3;exit" >&6
>  ^^^
  ^^

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

Re: advanced scripting problems - or wrong approach?

[tomas]

On Sat, Jun 01, 2024 at 09:20:59AM +0200, DdB wrote:
> Hello,
> 
> for years have i been using a self-made backup script [...]

I won't get into that -- I can't even fathom why you'd need coproc
for a backup script. I tend to keep things simple -- they tend to
thank me in failing less often and in more understandable ways.

I didn't try your script, but may be there is a "\n" missing down
there?

> > printf "%s\n" "sleep 3;exit" >&6
 ^^^

That would be my first hunch.

Cheers
-- 
t


signature.asc
Description: PGP signature

advanced scripting problems - or wrong approach?

[DdB]

Hello,

for years have i been using a self-made backup script, that did mount a
drive via USB, performed all kinds of plausibility checks, before
actually backing up incrementally. Finally verifying success and logging
the activities while kicking the ISB drive out.

Since a few months, i do have a real backup server instead, connecting
to it via ssh i was able to have 2 terminals open and back up manually.
Last time, i introduced a mistake by accident and since, i am trying to
automate the whole thing once again, but that is difficult, as the load
on the net is huge, mbuffer is useful in that regard. So i was intending
to have just one script for all the operations using coproc to
coordinate the 2 servers.

But weird things are going on, i cant reliably communicate between host
and backup server, at least not automatically.

Searching the web, i found:
https://github.com/reconquest/coproc.bash/blob/master/REFERENCE.md
But i was unable to get this to work, which seems to indicate, that i am
misunderstanding something.
The only success i had was to "talk" to a chess engine in a coprocess,
which did go well. But neither bash nor ssh are cooperating, i may have
timing issues with the pipes or some other side effects.

How can i describe? For example if i start this:
> #!/bin/bash -e
> 
> coproc { bash; }
> exec 5<&${COPROC[0]} 6>&${COPROC[1]}
> fd=5
> 
> echo "ls" >&6
> while IFS= read -ru $fd line
> do
> printf '%s\n' "$line"
> done
> 
> printf "%s\n" "sleep 3;exit" >&6
> while IFS= read -ru $fd line
> do
> printf '%s\n' "$line"
> done
> 
> exec 5<&- 6>&-
> 
> wait
> echo waited, done

i get the output from ls, but then the thing is hanging indefinitely,
apparently not reaching the exit line. :(

Anyone who can share his experience to advance my experimenting?
DdB

Re: RE: Problems installing QEMU packages on Debian 12 (stable)

[Lukas Nagy]

Hi,

thanks for checking, in the end I solved this by switching mirrors from 
default http://deb.debian.org/debian to http://ftp.cz.debian.org/debian 
- after updating I got the correct version of QEMU package.


Maybe something was cached somewhere for several days, strange that I 
had to change the mirror.

Problems installing QEMU packages on Debian 12 (stable)

[Lukas Nagy]

Hi,

I am trying to make KVM/QEMU work on my Debian 12. I follow 
https://wiki.debian.org/KVM but I get stuck already on installation, 
because apt-get reports non-existent packages on debian repos.


I ran

sudo apt install qemu-system libvirt-daemon-system virt-manager

It resolves packages, but when fails on 404 on qemu / xen packages

Full output is here:

sudo apt install qemu-system libvirt-daemon-system virt-manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer 
required:

  libcapi20-3 libodbc2 libosmesa6 libz-mingw-w64
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  gir1.2-ayatanaappindicator3-0.1 gir1.2-gtk-vnc-2.0 
gir1.2-libosinfo-1.0 gir1.2-libvirt-glib-1.0 gir1.2-spiceclientglib-2.0 
gir1.2-spiceclientgtk-3.0 gir1.2-vte-2.91 gnutls-bin ibverbs-providers 
ipxe-qemu
  libcacard0 libcapstone4 libdaxctl1 libexecs0 libfdt1 libfmt9 
libgfapi0 libgfrpc0 libgfxdr0 libglusterfs0 libgtk-vnc-2.0-0 
libgvnc-1.0-0 libibverbs1 libiscsi7 libisoburn1 libndctl6 libnss-mymachines
  libphodav-3.0-0 libphodav-3.0-common libpmem1 librados2 librbd1 
librdmacm1 libspice-client-glib-2.0-8 libspice-client-gtk-3.0-5 
libspice-server1 libtpms0 liburing2 libusbredirhost1 libusbredirparser1
  libvdeplug2 libvirglrenderer1 libvirt-clients libvirt-daemon 
libvirt-daemon-config-network libvirt-daemon-config-nwfilter 
libvirt-daemon-driver-lxc libvirt-daemon-driver-qemu 
libvirt-daemon-driver-vbox
  libvirt-daemon-driver-xen libvirt-daemon-system-systemd 
libvirt-glib-1.0-0 libvirt-glib-1.0-data libvirt-l10n libvirt0 
libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1 
libxengnttab1
  libxenhypfs1 libxenmisc4.17 libxenstore4 libxentoolcore1 
libxentoollog1 libxml2-utils mdevctl netcat-openbsd ovmf python3-libvirt 
python3-libxml2 qemu-block-extra qemu-efi-aarch64 qemu-efi-arm
  qemu-system-arm qemu-system-common qemu-system-data qemu-system-gui 
qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-utils seabios spice-client-glib-usb-acl-helper
  swtpm swtpm-libs swtpm-tools systemd-container virt-viewer virtinst 
xorriso

Suggested packages:
  libvirt-clients-qemu libvirt-login-shell 
libvirt-daemon-driver-storage-gluster 
libvirt-daemon-driver-storage-iscsi-direct 
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs 
numad auditd
  nfs-common open-iscsi pm-utils systemtap zfsutils samba vde2 trousers 
python3-guestfs ssh-askpass xorriso-tcltk jigit cdck

The following NEW packages will be installed:
  gir1.2-ayatanaappindicator3-0.1 gir1.2-gtk-vnc-2.0 
gir1.2-libosinfo-1.0 gir1.2-libvirt-glib-1.0 gir1.2-spiceclientglib-2.0 
gir1.2-spiceclientgtk-3.0 gir1.2-vte-2.91 gnutls-bin ibverbs-providers 
ipxe-qemu
  libcacard0 libcapstone4 libdaxctl1 libexecs0 libfdt1 libfmt9 
libgfapi0 libgfrpc0 libgfxdr0 libglusterfs0 libgtk-vnc-2.0-0 
libgvnc-1.0-0 libibverbs1 libiscsi7 libisoburn1 libndctl6 libnss-mymachines
  libphodav-3.0-0 libphodav-3.0-common libpmem1 librados2 librbd1 
librdmacm1 libspice-client-glib-2.0-8 libspice-client-gtk-3.0-5 
libspice-server1 libtpms0 liburing2 libusbredirhost1 libusbredirparser1
  libvdeplug2 libvirglrenderer1 libvirt-clients libvirt-daemon 
libvirt-daemon-config-network libvirt-daemon-config-nwfilter 
libvirt-daemon-driver-lxc libvirt-daemon-driver-qemu 
libvirt-daemon-driver-vbox
  libvirt-daemon-driver-xen libvirt-daemon-system 
libvirt-daemon-system-systemd libvirt-glib-1.0-0 libvirt-glib-1.0-data 
libvirt-l10n libvirt0 libxencall1 libxendevicemodel1 libxenevtchn1 
libxenforeignmemory1
  libxengnttab1 libxenhypfs1 libxenmisc4.17 libxenstore4 
libxentoolcore1 libxentoollog1 libxml2-utils mdevctl netcat-openbsd ovmf 
python3-libvirt python3-libxml2 qemu-block-extra qemu-efi-aarch64 
qemu-efi-arm
  qemu-system qemu-system-arm qemu-system-common qemu-system-data 
qemu-system-gui qemu-system-mips qemu-system-misc qemu-system-ppc 
qemu-system-sparc qemu-system-x86 qemu-utils seabios
  spice-client-glib-usb-acl-helper swtpm swtpm-libs swtpm-tools 
systemd-container virt-manager virt-viewer virtinst xorriso

0 upgraded, 96 newly installed, 0 to remove and 0 not upgraded.
Need to get 97,7 MB/143 MB of archives.
After this operation, 974 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://deb.debian.org/debian bookworm/main amd64 gnutls-bin amd64 
3.7.9-2+deb12u1

  404  Not Found [IP: 2a04:4e42:41::644 80]
Err:2 http://deb.debian.org/debian bookworm/main amd64 systemd-container 
amd64 252.19-1~deb12u1

  404  Not Found [IP: 2a04:4e42:41::644 80]
Err:3 http://deb.debian.org/debian bookworm/main amd64 libnss-mymachines 
amd64 252.19-1~deb12u1

  404  Not Found [IP: 2a04:4e42:41::644 80]
Err:4 http://deb.debian.org/debian bookworm/main amd64 libxentoolcore1 
amd64 4.17.2+76-ge1f9cb16e2-1~deb12u1

  404  Not Found [IP: 2a04:4e42:41::644 

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Thanks, I tried it but it turns out to be a wifi/usb problem I think.

Jan Krapivin  writes:

> Have you tried a LIVE-version of another Linux distribution? It will
> be interesting to compare.
>
> вс, 7 апр. 2024 г. в 22:30, Richmond :
>
> Richmond  writes:
>
> > Richmond  writes:
> >
> >> When playing videos in a web browser, and sending the sound to
> a
> >> bluetooth speaker (amazon echo) I get playback problems;
> stuttering,
> >> sound quality reduction to AM radio level or lower). These
> things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I
> haven't
> >> tried vlc so I am not sure if it is just that it is a command
> line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I
> need to
> >> isolate the process from the browser? I tried pop-out picture
> on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked
> fine, no
> > sound problems. But then I tried Google-chrome again and that
> was
> > working fine too, and so was Firefox-esr. The problems have
> gone away
> > and even rebooting doesn't bring them back. Maybe one of those
> browsers
> > brought a better library with it.
>
> These problems have come back again. I have tried rebooting. I
> tried
> sending the same audio from an android phone and it works fine.
> How do I
> find out what the problems is? I cannot see errors in journalctl
>

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Lee  writes:

> On Sun, Apr 7, 2024 at 3:30 PM Richmond wrote:
>>
>> Richmond writes:
>>
>> > Richmond writes:
>> >
>> >> When playing videos in a web browser, and sending the sound to a
>> >> bluetooth speaker (amazon echo) I get playback problems;
>> >> stuttering, sound quality reduction to AM radio level or
>> >> lower). These things can clear up after a minute or two, or be
>> >> reduced.
>> >>
>> >> When playing from nvlc however I get no such problems. (I haven't
>> >> tried vlc so I am not sure if it is just that it is a command
>> >> line).
>> >>
>> >> I have tried google-chrome and firefox-esr.
>> >>
>> >> Perhaps there is some other browser which will work? Maybe I need
>> >> to isolate the process from the browser? I tried pop-out picture
>> >> on you tube and it improved but there was still stuttering.
>> >
>> > I installed Falkon and Konqueror. I tried Falkon and it worked
>> > fine, no sound problems. But then I tried Google-chrome again and
>> > that was working fine too, and so was Firefox-esr. The problems
>> > have gone away and even rebooting doesn't bring them back. Maybe
>> > one of those browsers brought a better library with it.
>>
>> These problems have come back again.
>
> So unless you've updated or installed new hardware or software it's
> probably not a firmware/software issue.
>
>> I have tried rebooting. I tried sending the same audio from an
>> android phone and it works fine. How do I find out what the problems
>> is? I cannot see errors in journalctl
>
> It's possible that wifi or usb 3.0 could be interfering with your
> bluetooth speakers - eg
> https://www.zdnet.com/article/usb-3-and-usb-c-devices-can-cause-problems-with-wi-fi-and-bluetooth-connections-but-theres-a-solution/

Thanks, I think this is the answer! I was having no problems today but
noticed that the PC was connected to 5Ghz. Sometimes it connects at
2.4Ghz. When I disabled 5Ghz and forced the PC to use 2.4Ghz the problem
came back. So now all I need to do is seperate those services and/or tie
the PC to 5Ghz.

The PC is a laptop but I never move it from the desktop. I am using a
USB mouse and USB keyboard adapter to an old IBM keyboard.

> https://sortatechy.com/spot-and-fix-bluetooth-interference-with-wifi/
>
> If your PC is using wireless and can use a 5Ghz channel, try moving
> your PC wireless to a 5Ghz channel first.  If you PC only supports
> 2.4Gh wireless you can install linssid
> https://packages.debian.org/bookworm/linssid and pick a relatively
> unused channel for your PC wireless.  Or just try channels 1, 6 and 11
> and see if any of those makes a difference..
>
> If you're using a USB 3.0 device on your PC try turning it off or
> moving it to a USB 2.0 port and see if that fixes the bluetooth
> interference.
>
> Regards, Lee

Re: Bluetooth sound problems playing from a web browser

[Lee]

On Sun, Apr 7, 2024 at 3:30 PM Richmond wrote:
>
> Richmond writes:
>
> > Richmond writes:
> >
> >> When playing videos in a web browser, and sending the sound to a
> >> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> >> sound quality reduction to AM radio level or lower). These things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I haven't
> >> tried vlc so I am not sure if it is just that it is a command line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I need to
> >> isolate the process from the browser? I tried pop-out picture on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> > sound problems. But then I tried Google-chrome again and that was
> > working fine too, and so was Firefox-esr. The problems have gone away
> > and even rebooting doesn't bring them back. Maybe one of those browsers
> > brought a better library with it.
>
> These problems have come back again.

So unless you've updated or installed new hardware or software it's
probably not a firmware/software issue.

> I have tried rebooting. I tried
> sending the same audio from an android phone and it works fine. How do I
> find out what the problems is? I cannot see errors in journalctl

It's possible that wifi or usb 3.0 could be interfering with your
bluetooth speakers - eg
https://www.zdnet.com/article/usb-3-and-usb-c-devices-can-cause-problems-with-wi-fi-and-bluetooth-connections-but-theres-a-solution/
https://sortatechy.com/spot-and-fix-bluetooth-interference-with-wifi/

If your PC is using wireless and can use a 5Ghz channel, try moving
your PC wireless to a 5Ghz channel first.
If you PC only supports 2.4Gh wireless you can install linssid
  https://packages.debian.org/bookworm/linssid
and pick a relatively unused channel for your PC wireless.  Or just
try channels 1, 6 and 11 and see if any of those makes a difference..

If you're using a USB 3.0 device on your PC try turning it off or
moving it to a USB 2.0 port and see if that fixes the bluetooth
interference.

Regards,
Lee

Re: Bluetooth sound problems playing from a web browser

[Jan Krapivin]

Have you tried a LIVE-version of another Linux distribution? It will be
interesting to compare.

вс, 7 апр. 2024 г. в 22:30, Richmond :

> Richmond  writes:
>
> > Richmond  writes:
> >
> >> When playing videos in a web browser, and sending the sound to a
> >> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> >> sound quality reduction to AM radio level or lower). These things can
> >> clear up after a minute or two, or be reduced.
> >>
> >> When playing from nvlc however I get no such problems. (I haven't
> >> tried vlc so I am not sure if it is just that it is a command line).
> >>
> >> I have tried google-chrome and firefox-esr.
> >>
> >> Perhaps there is some other browser which will work? Maybe I need to
> >> isolate the process from the browser? I tried pop-out picture on you
> >> tube and it improved but there was still stuttering.
> >
> > I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> > sound problems. But then I tried Google-chrome again and that was
> > working fine too, and so was Firefox-esr. The problems have gone away
> > and even rebooting doesn't bring them back. Maybe one of those browsers
> > brought a better library with it.
>
> These problems have come back again. I have tried rebooting. I tried
> sending the same audio from an android phone and it works fine. How do I
> find out what the problems is? I cannot see errors in journalctl
>
>

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Richmond  writes:

> Richmond  writes:
>
>> When playing videos in a web browser, and sending the sound to a
>> bluetooth speaker (amazon echo) I get playback problems; stuttering,
>> sound quality reduction to AM radio level or lower). These things can
>> clear up after a minute or two, or be reduced.
>>
>> When playing from nvlc however I get no such problems. (I haven't
>> tried vlc so I am not sure if it is just that it is a command line).
>>
>> I have tried google-chrome and firefox-esr.
>>
>> Perhaps there is some other browser which will work? Maybe I need to
>> isolate the process from the browser? I tried pop-out picture on you
>> tube and it improved but there was still stuttering.
>
> I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
> sound problems. But then I tried Google-chrome again and that was
> working fine too, and so was Firefox-esr. The problems have gone away
> and even rebooting doesn't bring them back. Maybe one of those browsers
> brought a better library with it.

These problems have come back again. I have tried rebooting. I tried
sending the same audio from an android phone and it works fine. How do I
find out what the problems is? I cannot see errors in journalctl

Re: Bluetooth sound problems playing from a web browser

[Richmond]

Richmond  writes:

> When playing videos in a web browser, and sending the sound to a
> bluetooth speaker (amazon echo) I get playback problems; stuttering,
> sound quality reduction to AM radio level or lower). These things can
> clear up after a minute or two, or be reduced.
>
> When playing from nvlc however I get no such problems. (I haven't
> tried vlc so I am not sure if it is just that it is a command line).
>
> I have tried google-chrome and firefox-esr.
>
> Perhaps there is some other browser which will work? Maybe I need to
> isolate the process from the browser? I tried pop-out picture on you
> tube and it improved but there was still stuttering.

I installed Falkon and Konqueror. I tried Falkon and it worked fine, no
sound problems. But then I tried Google-chrome again and that was
working fine too, and so was Firefox-esr. The problems have gone away
and even rebooting doesn't bring them back. Maybe one of those browsers
brought a better library with it.

Bluetooth sound problems playing from a web browser

[Richmond]

When playing videos in a web browser, and sending the sound to a
bluetooth speaker (amazon echo) I get playback problems; stuttering,
sound quality reduction to AM radio level or lower). These things can
clear up after a minute or two, or be reduced.

When playing from nvlc however I get no such problems. (I haven't tried
vlc so I am not sure if it is just that it is a command line).

I have tried google-chrome and firefox-esr.

Perhaps there is some other browser which will work? Maybe I need to
isolate the process from the browser? I tried pop-out picture on you
tube and it improved but there was still stuttering.

Anaconda-navigator installation problems

[Gary L. Roach]

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-18-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD CAICOS
Manufacturer: MSI
Product Name: MS-7974
System Version: 1.0

I have been trying to get the Anaconda Navigator to work for a month 
with no success. I keep getting the following message when trying to 
start the the program:


(base) root@debian:/usr/share/bash-completion/completions# 
anaconda-navigator
2024-03-21 11:45:36,089 - WARNING 
linux_scaling.get_scaling_factor_using_dbus:32

An exception occurred during fetching list of system display settings.

qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even 
though it was

found.
This application failed to start because no Qt platform plugin could be 
initialized

. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, minimal, minimalegl, offscreen, 
vnc, webgl,

xcb.

Aborted (core dumped)

Any help will be sincerely appreciated.

Gary R.

Re: Bluetooth sound problems Debian 12 GNOME

[Charles Curley]

On Mon, 18 Mar 2024 13:32:18 +0300
Jan Krapivin  wrote:

> Small problem is that LTS Kernel 6.1 doesn’t support this device, so
> I have used Liquorix kernel, which I have installed earlier. Though,
> I don’t need this kernel, as it haven’t helped me with sound
> interrupts, which was my hope at first.

I'm glad you reached a solution. You might also check the backports
kernel, which is currently linux-image-6.6.13+bpo-amd64
6.6.13-1~bpo12+1.

-- 
Does anybody read signatures any more?

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

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

Good news. Looks like I have solved the problem. As a last resort I have
bought another one wi-fi receiver, third one. It has *Realtek RTL8763BW*
chip
<https://www.realtek.com/en/products/communications-network-ics/item/rtl8763b>
and *two antennas*. And finally all works fine. I have spent some hours,
using Bluetooth headphones, waiting for problems, but they hadn’t occur.
Small problem is that LTS Kernel 6.1 doesn’t support this device, so I have
used Liquorix kernel, which I have installed earlier. Though, I don’t need
this kernel, as it haven’t helped me with sound interrupts, which was my
hope at first. So… I bought more old Wi-fi receiver with *Realtek
RTL8761BUV* chip with antenna and it also works fine, and also works with
stable 6.1 kernel.

I am glad that situation found its resolution, though it is strange for me
that USB-dongle Bluetooth receiver (I don’t know the exact model) and
receiver on an internal wi-fi adapter (AX 210) have worked so poorly both.
Though I was in the distance not more than 2 meters from receiver.

Thanks for help

пт, 15 мар. 2024 г. в 05:21, Max Nikulin :

> On 14/03/2024 19:06, Jan Krapivin wrote:
> >
> > What do you think about QUANT parameter in */pw-top/*? Can it influence
> > sound quality? I wasn't able to change it with
> >
> > pw-metadata -n settings 0 clock.force-quantum 2048
>
> Sorry, my experience with tuning PipeWire is limited to switching audio
> profiles (A2DP codecs, HSF) from UI.
>
> I think in you case it would be more productive to enable debug logs
> either in bluetoothd or PipeWire to find either the host or the device
> drops or lost connections causing pauses till reconnect.
>
>
>

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 14/03/2024 19:06, Jan Krapivin wrote:


What do you think about QUANT parameter in */pw-top/*? Can it influence 
sound quality? I wasn't able to change it with


pw-metadata -n settings 0 clock.force-quantum 2048


Sorry, my experience with tuning PipeWire is limited to switching audio 
profiles (A2DP codecs, HSF) from UI.


I think in you case it would be more productive to enable debug logs 
either in bluetoothd or PipeWire to find either the host or the device 
drops or lost connections causing pauses till reconnect.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

> You may try to discriminate hardware/software issues when you comparing
> different laptops by booting various live images (GNOME, xfce, etc.).
>

 I will try... Thank you.

What do you think about QUANT parameter in *pw-top*? Can it influence sound
quality? I wasn't able to change it with

*pw-metadata -n settings 0 clock.force-quantum 2048*

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 13/03/2024 17:43, Jan Krapivin wrote:
While watching */pactl subscribe /*command output, i have noticed that 
there was a change from sink 414 to sink 213 when sound interrupt occurred


"Event 'change' on sink-input #414

Can this information be of any help?


It is expected due to


Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb pipewire-pulse[1359]: mod.protocol-pulse: client 
0x58b39dbbea40 [GNOME Settings]: ERROR command:-1 (invalid) tag:358 error:25 
(Input/output error)
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) config/udev: 
removing device Haylou W1 (AVRCP)


journalctl running with root privileges may provide more details.

You may try to discriminate hardware/software issues when you comparing 
different laptops by booting various live images (GNOME, xfce, etc.). I 
admit that it is inconvenient since it may require at least a half of an 
hour to test each variant and regular working environment is unavailable.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

> Run the command as root, but you already have enough keywords to search
> in bug reports and discussions related to PipeWire and pulseaudio. The
> latter may have some workarounds for specific models of headphones.


Thanks, i will try to research this topic.


> PipeWire mailing list or forum may be a better place to discuss the issue.
>

OK

While watching *pactl subscribe *command output, i have noticed that there
was a change from sink 414 to sink 213 when sound interrupt occurred

"Event 'change' on sink-input #414
Event 'change' on sink-input #414
Event 'change' on sink-input #414
Event 'change' on sink-input #213
Event 'change' on sink-input #213
Event 'change' on sink-input #213"

Can this information be of any help?

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 12/03/2024 03:48, Jan Krapivin wrote:


"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem 
not available: AT+XIAOMI=1,1,102,85,88,27,174"


Just a wild guess, unlikely it is true. Headphones might report battery 
charge level using a vendor protocol extension. 85 and 88 are decreasing 
in later messages.


Sound stream may be interrupted when headphones decide to balance 
battery discharge by switching device that communicates with laptop.


Perhaps messages related to input devices are different because it is 
Wayland session while I use KDE with X11 session, so in my case 
messages are "Watching system buttons" instead of "KEYBOARD...".


You may use --since and --until journalctl options to get system logs 
for the same time intervals you posted.

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 12/03/2024 03:48, Jan Krapivin wrote:


As for journald i have a lot of such errors, but they don't influence 
the audio quality:


"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem 
not available: AT+XIAOMI=1,1,102,85,88,27,174"


Headphones might expect some response to some of these command and might 
drop connection otherwise.



journalctl -f
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.


Run the command as root, but you already have enough keywords to search 
in bug reports and discussions related to PipeWire and pulseaudio. The 
latter may have some workarounds for specific models of headphones.



Mar 11 23:14:11 deb gsd-media-keys[1744]: Unable to get default sink
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb gsd-media-keys[1744]: Unable to get default sink
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) event25 - Haylou W1 
(AVRCP): device removed
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (**) Option "fd" "78"
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) UnloadModule: 
"libinput"
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (II) systemd-logind: 
releasing fd for 13:89
Mar 11 23:14:11 deb /usr/libexec/gdm-x-session[1449]: (EE) systemd-logind: 
failed to release device: Device not taken
Mar 11 23:14:12 deb wireplumber[1357]: set volume 74 failed for transport 
/org/bluez/hci0/dev_9C_19_C2_1B_A7_25/sep4/fd1 (No such property 'Volume')
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (II) config/udev: Adding 
input device Haylou W1 (AVRCP) (/dev/input/event25)
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (**) Haylou W1 (AVRCP): Applying 
InputClass "libinput keyboard catchall"
Mar 11 23:14:14 deb /usr/libexec/gdm-x-session[1449]: (II) Using input driver 
'libinput' for 'Haylou W1 (AVRCP)'


So device disappears for some reason. Perhaps driver receives something 
unexpected, perhaps headphone do not receive something they expect.



Mar 11 23:24:28 deb /usr/libexec/gdm-x-session[1449]: (II) XINPUT: Adding extended input 
device "Haylou W1 (AVRCP)" (type: KEYBOARD, id 20)


Check if similar lines are logged on Mint. KEYBOARD looks a bit strange, 
but perhaps it is normal for GNOME.


PipeWire mailing list or forum may be a better place to discuss the issue.

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

It is strange. I can see in a Debian mailing list an answer

- *From*: Ottavio Caruso 
- *Date*: Mon, 11 Mar 2024 16:50:45 +

"Not sure if this is your case, I had the same problem but I upgraded from
11 to 12. The transition from pulse to pipewire was not smooth. So I nuked
anything *pulse* and *bluetooth* and reinstalled from scratch using the
Debian guide:

https://wiki.debian.org/PipeWire

Is this a brand new installation or an upgrade?"

But i can't see it in my mailbox


*ANSWER*


No, this is a clean new installation. And it looks like i have the
same problem on another laptop with Debian 12 XFCE (Pulseaudio).

But the problem is with *TWO* headsets, so i am in question whats
happening with Debian, because Linux Mint and Android works fine...





пн, 11 мар. 2024 г. в 23:48, Jan Krapivin :

> Hello again. I have used *pactl subscribe *command and i think that in
> the moment of sound interrupt there are the corresponding lines:
>
> "Event 'remove' on sink-input #353
> Event 'new' on sink-input #358
> Event 'change' on sink-input #358"
>
> As for journald i have a lot of such errors, but they don't influence the
> audio quality:
>
> "Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem
> not available: AT+XIAOMI=1,1,102,85,88,27,174"
>
> There are some other mentions of the bluetooth/headphones, but they don't
> meet the moment of sound issues. Full journald -f log is in an attachment.
>
> I must say that i had an opportunity today to test a laptop with Debian 12
> XFCE laptop with Pulseaudio and the problem is the same there. But, as i
> said, on a laptop with Linux Mint XFCE everything is fine. That's strange.
> What is the main difference between Linux Mint and Debian here..?
>
> I also tried Liquorix 6.7 kernel but it didn't help.
>
> Thanks.
>

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

Hello again. I have used *pactl subscribe *command and i think that in the
moment of sound interrupt there are the corresponding lines:

"Event 'remove' on sink-input #353
Event 'new' on sink-input #358
Event 'change' on sink-input #358"

As for journald i have a lot of such errors, but they don't influence the
audio quality:

"Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem
not available: AT+XIAOMI=1,1,102,85,88,27,174"

There are some other mentions of the bluetooth/headphones, but they don't
meet the moment of sound issues. Full journald -f log is in an attachment.

I must say that i had an opportunity today to test a laptop with Debian 12
XFCE laptop with Pulseaudio and the problem is the same there. But, as i
said, on a laptop with Linux Mint XFCE everything is fine. That's strange.
What is the main difference between Linux Mint and Debian here..?

I also tried Liquorix 6.7 kernel but it didn't help.

Thanks.
journalctl -f
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
Mar 11 21:28:16 deb wireplumber[1357]: RFCOMM receive command but modem not 
available: AT+BTRH?
Mar 11 21:28:16 deb wireplumber[1357]: RFCOMM receive command but modem not 
available: AT+XIAOMI=1,1,102,100,100,27,174
Mar 11 21:29:21 deb systemd[1331]: Started 
app-gnome-gnome\x2dterminal-6829.scope - Application launched by gsd-media-keys.
Mar 11 21:29:21 deb dbus-daemon[1367]: [session uid=1000 pid=1367] Activating 
via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.131' (uid=1000 pid=6829 
comm="gnome-terminal")
Mar 11 21:29:21 deb systemd[1331]: Starting gnome-terminal-server.service - 
GNOME Terminal Server...
Mar 11 21:29:22 deb dbus-daemon[1367]: [session uid=1000 pid=1367] Successfully 
activated service 'org.gnome.Terminal'
Mar 11 21:29:22 deb systemd[1331]: Started gnome-terminal-server.service - 
GNOME Terminal Server.
Mar 11 21:29:22 deb systemd[1331]: Started 
vte-spawn-82cf01f4-467e-44e1-b0e3-19af9cb02a2a.scope - VTE child process 6864 
launched by gnome-terminal-server process 6834.
Mar 11 21:30:27 deb systemd[1331]: Started 
app-gnome-gnome\x2dterminal-7042.scope - Application launched by gsd-media-keys.
Mar 11 21:30:27 deb systemd[1331]: Started 
vte-spawn-6e59a663-467e-40c5-9553-ad6b513aeecb.scope - VTE child process 7048 
launched by gnome-terminal-server process 6834.
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Changing 
wallpaper...
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Current wallpaper 
"a2.jpg"
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Wallpapers in 
queue: 8
Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Next slide in 600 
seconds.
Mar 11 21:41:51 deb gnome-shell[1624]: JS ERROR: Gio.DBusError: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 
“IconAccessibleDesc”
   
_promisify/proto[asyncFunc]/

Re: Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

пн, 11 мар. 2024 г. в 07:50, Max Nikulin :

>
> Are there anything in journalctl output (executed as root) around these
> events?
>

I guess that no, but i will recheck.


> Is XFCE configured to use pulseaudio or PipeWire as GNOME?
>

Pulseaudio


> Another option might be LC3 codec from Bluetooth LE (5.2 Basic Audio
> Profile) if it is supported by the headphones.
>

Unfortunately it's not supported.


> Either a software/hardware bug or some piece of software disables power
> saving for handsfree/headset profiles to achieve low latency, but for
> A2DP device tries to sleep after some period of time.
>

 Hm, i will try to research that, thank you.

Arch Linux wiki pages have long troubleshooting sections.
>

Yes, I saw but found nothing relatable to my view.

Last resort might be dumping bluetooth traffic, but perhaps it is better
> to ask in some mailing list or forum more close to Bluetooth stack
> developers.
>

I have installed Wireshark, but somehow i can't find bluetooth connection
to capture
(https://forums.debian.net/viewtopic.php?p=795020#p795020)

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

Please, respond to the mailing list.

On 11/03/2024 11:50, Max Nikulin wrote:

https://wiki.debian.org/BluetoothUser/a2dp

Last resort might be dumping bluetooth traffic


The link above has an example

dumpcap -i bluetooth0

Another tool is

hcidump -w /tmp/bt.pcap

However at first I would check logs using journalctl. Maybe debug should 
be enabled for bluez and PipeWire.

Re: Bluetooth sound problems Debian 12 GNOME

[Max Nikulin]

On 10/03/2024 21:07, Jan Krapivin wrote:
Hello! I have a problem with sound quality when using bluetooth 
headphones on Debian 12 GNOME.


Every ~20 minutes, sometimes less, sometimes more, sound interrupts for 
a 1-5 seconds with complete silence.


Are there anything in journalctl output (executed as root) around these 
events?


At first I thought that problem can be in the headphones, though it have 
worked fine with Android phone and Linux Mint XFCE on a other laptop.


Is XFCE configured to use pulseaudio or PipeWire as GNOME?

So I bought another headphones with support of different codecs: SBC, 
AAC, and AptX.


Another option might be LC3 codec from Bluetooth LE (5.2 Basic Audio 
Profile) if it is supported by the headphones.


Though in mSBC there are no interruptions. I wonder why mSBC works fine 
and SBC no..?


Either a software/hardware bug or some piece of software disables power 
saving for handsfree/headset profiles to achieve low latency, but for 
A2DP device tries to sleep after some period of time. At least SBC 
allows to decrease bitrate if connection is unreliable. I have read 
somewhere that current drivers can not increase bitrate without 
reconnection. It is just speculations, do not take it too serious.


Arch Linux wiki pages have long troubleshooting sections. Debian ones 
are partially outdated:

https://wiki.debian.org/BluetoothUser
https://wiki.debian.org/BluetoothUser/a2dp

Last resort might be dumping bluetooth traffic, but perhaps it is better 
to ask in some mailing list or forum more close to Bluetooth stack 
developers.

Bluetooth sound problems Debian 12 GNOME

[Jan Krapivin]

Hello! I have a problem with sound quality when using bluetooth headphones
on Debian 12 GNOME.

Every ~20 minutes, sometimes less, sometimes more, sound interrupts for a
1-5 seconds with complete silence.

At first I thought that problem can be in the headphones, though it have
worked fine with Android phone and Linux Mint XFCE on a other laptop.

So I bought another headphones with support of different codecs: SBC, AAC,
and AptX.

And I have the same problem, but now I hear not only silence but also a
crackling, when sound interrupts.

I tried different codecs, including AAC (
https://forums.debian.net/viewtopic.php?p=777598#p777598). But the problem
prevails.

Yes, I must of course mention that there is absolutely no problems, when
using non-bluetooth devices like speakers, headphones etc.

The only workaround is to use HSP mSBC codec in Heandsfree mode, but the
sound is awful.

Though in mSBC there are no interruptions. I wonder why mSBC works fine and
SBC no..?


My system is (inxi)

Bluetooth:

Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8

bus-ID: 1-10:3 chip-ID: 8087:0032 class-ID: e001

Report: hciconfig ID: hci0 rfk-id: 0 state: up address: 

Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff

link-mode: peripheral accept service-classes: rendering, capturing, object

transfer, audio, telephony


Audio:

Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel

Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel

Device-3: Creative Sound Blaster Play! 3 type: USB

driver: hid-generic,snd-usb-audio,usbhid

API: ALSA v: k6.1.0-18-amd64 status: kernel-api

Server-1: PipeWire v: 0.3.65 status: active


What have i tried?

Creating choppy-under-load.conf file in
/home/ja/.config/pipewire/pipewire-pulse.conf.d/ with


“context.properties = {

default.clock.quantum = 8192

default.clock.min-quantum = 8192

}”


Creating switch-on-connect.conf file with


pulse.cmd = [

{ cmd = "load-module" args = "module-always-sink" flags = [ ] }

{ cmd = "load-module" args = "module-switch-on-connect" }

]


Unfortunately I have no ideas what to try further as I am not a
power-user/techy.

I have tried to use PulseAudio, pipe-wire media session and not
Wireplumber, backported version of PipeWire, but all these attempts left me
with GDM/Gnome removed from the system! As Gnome now have
Pipewire/Wireplumber as dependency.

I want to try all options possible (if any) before I ditch Gnome in favour
of DE, that supports Pulseaudio.

P.S. I have tried two different bluetooth hardware modules, one on a Wi-fi
chip and one USB-stick, with no difference.

Re: a couple rpi problems

[Mike McClain]

On Mon, Mar 04, 2024 at 11:41:07PM +, ghe2001 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> rpi5 and 4, standard Debian clone OS
>
> 1) The 5, pi5.slsware.lan, keeps sending me email saying,
> "*** SECURITY information for pi5 ***"
> and
> "pi5 : Mar  4 15:40:14 : root : unable to resolve host pi5: Name or service 
> not known"
> I have no idea why it's complaining or what's bent.

mike@DevuanPI4b:~> cat /etc/hostname
MikesDevuanPI
mike@DevuanPI4b:~> cat /etc/hosts

127.0.0.1   MikesDevuanPI


> 2) On both the 4 and 5, 'needrestart' says I'm running on an old kernel and 
> tells me that a reboot will start the newer version.  But it's just kidding 
> -- I reboot and I get the same message again.  The 4's been doing that for a 
> long time, and I've just let it keep running the old kernel because I'm 
> afraid I might break something if I try to delete the old kernel.  But I just 
> got the 5 a few days ago, it's doing the same thing, and I'd like to get this 
> dealt with.

I've never seen that either and have 2 RPI4bs running Devuan daedalus on this 
one,
Rasbian bookworm on the other.

I assume you ran apt update & apt upgrade before reboot.

One thing I have noticed is that reboot and 'shutdown -h now'
then toggling the power, don't always give the same results.

> --
> Glenn English

Be well,
Mike
--
For more information, please reread.

Re: a couple rpi problems

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


On Monday, March 4th, 2024 at 9:26 PM, Jeffrey Walton  
wrote:

> Here's what one looks like for a host named 'raptor' after the Intel ISA:

Yeah, I put it in there when I understood what it was looking for.  When I went 
to computer school, there was no Internet or IP anything, so I didn't know that 
"resolve" meant "what's your IP address" (I hit vi real quick to add an IP to 
hosts -- everybody seems to be happy with their resolution now).

Any thoughts on my kernel replacement notice problem?

--
Glenn English

-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAnBYJl5qQICZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC
rIwyAAAKfQgAygPy80F4EiZzWgfFviPK7woPLTJt0a/cfWKy9hWb7HAJJal5
iJCu5ptloZ0mbwKQehmfMlJK/Qfp4wIwhCm0X/Z5Ye4OqlJ972YQn/RyJZjO
QdrO4UjJ2biTqcc84iHjfeR9qBB/VTXZosLVM9Nd6Sl23fYckp7GQpAtYkNT
WVjz16rUT0t3xeXr7QXaSo2x/MMY2qcldRROxDZVAa8oH74HC5P4+mAC3EB7
Srk0ZKfu2IBFVurp8LbyzuEQVL3c5CdkYXNS3P/nc3Tl27S+yDN98Q5zrREL
iV7eMHdbw/QXzSVvbNxt0fZM5Bg3KLYmcgYp8LhiEwjBezRakt/UYw==
=OGEg
-END PGP SIGNATURE-

Re: a couple rpi problems

[Jeffrey Walton]

On Mon, Mar 4, 2024 at 11:07 PM ghe2001  wrote:
>
> On Monday, March 4th, 2024 at 5:01 PM, Greg Wooledge  
> wrote:
> [...]
> > So, "pi5" appears to be your hostname.
>
> Yup.
>
> > It can't resolve its own hostname. You're probably missing a line in
> > your /etc/hosts file.
>
> Oh!  It wants the IP!  You're right -- pi5 isn't in there.  Thanks.

Here's what one looks like for a host named 'raptor' after the Intel ISA:

$ cat /etc/hosts
# Loopback entries; do not change.
# For historical reasons, localhost precedes localhost.localdomain:
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4

# 127.0.1.1 is often used for the FQDN of the machine
127.0.1.1   raptor.home.arpa raptor

# The following lines are desirable for IPv6 capable hosts
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

Re: a couple rpi problems

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256








On Monday, March 4th, 2024 at 5:01 PM, Greg Wooledge  wrote:

> On Mon, Mar 04, 2024 at 11:41:07PM +, ghe2001 wrote:
> 
> > 1) The 5, pi5.slsware.lan, keeps sending me email saying,
> > 
> > "*** SECURITY information for pi5 ***"
> 
> 
> So, "pi5" appears to be your hostname.

Yup.

> It can't resolve its own hostname. You're probably missing a line in
> your /etc/hosts file.

Oh!  It wants the IP!  You're right -- pi5 isn't in there.  Thanks.

--
Glenn English

-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAnBYJl5mNYCZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC
rIwyAAANBwgAq7nMSAqNTRA7YRx9vW/7JkI/ely4QL6xYUrQ9g7+JWLvi5Do
Qu2vfEKrPuidVahKp3YRcXMNXIryAKS9mO5ghUieiEUMTSH3M+aXiSC7m3CO
Xu7qR5YPdKRM58iMkxHLN2IW2ioDGWAkQo9IdKxFNQvKP7KDhGleWmscFtjC
nbD7kfkKZNShC3s/woEdctrqx2HlJQrbcU4pm6VUNsX0xAL71xPV/jro1Tr3
zPEnAy1Gq5VbcspMShUngaKEFn686GLlyaTaVR5ZWZJZOpEeRf2K/Qf8fZSt
sR/orl0tSGZO2BJdGrZUu9vjkdNwHiSMLC7wkiKU9HdtM58f7PtYRw==
=u7/T
-END PGP SIGNATURE-

Re: a couple rpi problems

[Greg Wooledge]

On Mon, Mar 04, 2024 at 11:41:07PM +, ghe2001 wrote:
> 1) The 5, pi5.slsware.lan, keeps sending me email saying, 
> 
> "*** SECURITY information for pi5 ***" 

So, "pi5" appears to be your hostname.

> "pi5 : Mar  4 15:40:14 : root : unable to resolve host pi5: Name or service 
> not known"
> 
> I have no idea why it's complaining or what's bent.  

It can't resolve its own hostname.  You're probably missing a line in
your /etc/hosts file.

a couple rpi problems

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

rpi5 and 4, standard Debian clone OS

1) The 5, pi5.slsware.lan, keeps sending me email saying, 

"*** SECURITY information for pi5 ***" 

and 

"pi5 : Mar  4 15:40:14 : root : unable to resolve host pi5: Name or service not 
known"

I have no idea why it's complaining or what's bent.  


2) On both the 4 and 5, 'needrestart' says I'm running on an old kernel and 
tells me that a reboot will start the newer version.  But it's just kidding -- 
I reboot and I get the same message again.  The 4's been doing that for a long 
time, and I've just let it keep running the old kernel because I'm afraid I 
might break something if I try to delete the old kernel.  But I just got the 5 
a few days ago, it's doing the same thing, and I'd like to get this dealt with.

IIRC (I'm 81, and that's no longer a given), I never saw this with the rpi2s or 
3s or the real Debian boxen. 

Any thoughts/suggestions would be appreciated...

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

wsBzBAEBCAAnBYJl5lv0CZDmyitW0WqrdxYhBMRG7aHlwXhPX67r9+bKK1bR
aqt3AAAKKwf/QpSQ5LbO3FflxshXl0s+7TZWnW1dWw3XmWHuhuLM904ie6vL
DdaZWr2C/7ZuVN0iKvwpX5Z+8AwtyUTNfrxV7yMKvZw+Gzuc8ZZ2NN/7oGI4
7o8Ua/OXYlwIeKVL8agb3frMvz7Flsh3C9eOqvv7WJTmhkLE23ZKN84VHPcz
GpaSi/K7l6bpHDrC50F1HvgtYzGZIp7bJVY930+IRv1BYLJI7EwLDiC5JjeN
37T1s/Ul7460FFM0J49LMZYUEQKkWqBPw8wqf6zK0WNJ8DYJ6dHA+6Hqf6Xz
CZyPRL2E1Zd0wAtrHPrl+JMHxfMblwyZMu0vkI+h6HHzfbcaEkwMBg==
=BPuV
-END PGP SIGNATURE-

Problems with `pactl load-module module-loopback'

[Rodolfo Medina]

Hi all.

Without pipewire I didn't manage to pair and connect my bluetooth
headset/microphone to my Debian 12 so I installed pipewire while pulseaudio was
already there.  So now both pulseaudio and pipewire are installed.  Now when I
do:

 $ pactl load-module module-loopback latency_msec=5

a terrible noise suddenly comes, and if I want to stop it with

 $ pactl exit

I get the error message `exit failure: connection refused'.  I searched around
but didn't find so far any solution.  Please help whoever can.

Thanks in advance,

Rodolfo

Problems with `pactl' after replacing pulseaudio with pipewire

[Rodolfo Medina]

In order to have my headset bluetooth microphone detected by Debian 12 I
removed pulseaudio and in its place installed pipewire.  Only, since then, when
I do

 $ pactl load-module module-loopback latency_msec=5

a terrible continuous noise comes up, and besides when I do

 $ pactl exit

I get the error message `exit failure: connection refused'.  I searched around
but didn't find so far any solution.  Please help whoever can.

Thanks in advance,

Rodolfo

Problems with password entry [WAS Re: Debian 12.4.0]

[Andrew M.A. Cater]

On Sun, Dec 17, 2023 at 01:39:34AM +0100, Kevin Price wrote:
> Am 14.12.23 um 23:01 schrieb David Sawyer:
> > I use the password that I wrote down it is not accepted.
> 
> Keyboard layout? We've seen that with the kernel that comes with 12.4.0.
> -- 

Hi Kevin,

There is no obvious reason why there should be any substantive change between
the non-buggy kernel in 12.2 (6.1.0-13), the buggy kernel with the potential
file corruption issue that led to 12.4 (6.1.0-14), and the kernel that fixed
this file corruption issue that had been identified (6.1.0-15).

Immediately afer 6.1.0-15 had been issued, the upstream stable kernel
maintainers noted a separate kernel regression to do with certain wireless
chip sets which could also cause reboot/lock up issues. That led to an
upstream stable kernel minor point release as 6.1.67.

That is the issue that led to bug reports from you. 

*That* kernel fix, which went through a full test cycle in Debian, is in
Debian kernel version 6.1.0-16 wiich is the current kernel in 12.4
(available from the stable-updates repository).

[See also the Debian wiki at https://wiki.debian.org/SourcesList for the
Bookworm /etc/apt/sources.list entries]

Any possible keyboard issues are entirely orthogonal to any recent kernel
issues, I think.

For an installed value of one and as a counter-example where It Works
For Me (TM), I've been through each of the above kernels, including
the buggy one, with no change in keyboard layout.

> Kevin Price
>

With every good wish, as ever,

Andy Cater 

Re: balenaEtcher installation problems

[Gary L. Roach]

On 11/9/23 18:22, Jeffrey Walton wrote:

On Thu, Nov 9, 2023 at 8:47 PM Gary L. Roach  wrote:

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-13-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD CAICOS
Manufacturer: MSI
Product Name: MS-7974
System Version: 1.0

I have been trying to install balenaEtcher for 2 days but can't get rid of the 
following errors :

ERROR:ozone_platform_x11.cc(247)] Missing X server or $DISPLAY
[10145:1109/120137.666202:ERROR:env.cc(226)] The platform failed to initialize. 
 Exiting

I have tried everything I could find with google searches to no avail. My 
$DISPLAY variable is blank which may be the source of the problem.But what 
should it contain?

I know that the information I am giving is a bit sketchy but is the best I can 
do at this point. There are lots of fixes listed on the internet but none of 
them work. I am using the .deb file down loaded from the balena web page and 
installing it with dpkg -i .

Any help will be sincerely appreciated.

Try `export DISPLAY=":0.0"`.

Jeff


I just solved the problem. I was missing 4 dependencies. One must use 
the .deb file not the appimage file and run dpkg -I  and 
install the missing items.


I hope this helps others

Thanks

Gary R

Re: balenaEtcher installation problems

[Jeffrey Walton]

On Thu, Nov 9, 2023 at 8:47 PM Gary L. Roach  wrote:
>
> Operating System: Debian GNU/Linux 12
> KDE Plasma Version: 5.27.5
> KDE Frameworks Version: 5.103.0
> Qt Version: 5.15.8
> Kernel Version: 6.1.0-13-amd64 (64-bit)
> Graphics Platform: Wayland
> Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
> Memory: 31.2 GiB of RAM
> Graphics Processor: AMD CAICOS
> Manufacturer: MSI
> Product Name: MS-7974
> System Version: 1.0
>
> I have been trying to install balenaEtcher for 2 days but can't get rid of 
> the following errors :
>
> ERROR:ozone_platform_x11.cc(247)] Missing X server or $DISPLAY
> [10145:1109/120137.666202:ERROR:env.cc(226)] The platform failed to 
> initialize.  Exiting
>
> I have tried everything I could find with google searches to no avail. My 
> $DISPLAY variable is blank which may be the source of the problem.But what 
> should it contain?
>
> I know that the information I am giving is a bit sketchy but is the best I 
> can do at this point. There are lots of fixes listed on the internet but none 
> of them work. I am using the .deb file down loaded from the balena web page 
> and installing it with dpkg -i .
>
> Any help will be sincerely appreciated.

Try `export DISPLAY=":0.0"`.

Jeff

balenaEtcher installation problems

[Gary L. Roach]

Operating System: Debian GNU/Linux 12
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-13-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD CAICOS
Manufacturer: MSI
Product Name: MS-7974
System Version: 1.0

I have been trying to install balenaEtcher for 2 days but can't get rid 
of the following errors :


*ERROR:ozone_platform_x11.cc(247)] Missing X server or $DISPLAY
[10145:1109/120137.666202:ERROR:env.cc(226)] The platform failed to 
initialize.  Exiting*


I have tried everything I could find with google searches to no avail. 
My $DISPLAY variable is blank which may be the source of the problem.But 
what should it contain?


I know that the information I am giving is a bit sketchy but is the best 
I can do at this point. There are lots of fixes listed on the internet 
but none of them work. I am using the .deb file down loaded from the 
balena web page and installing it with dpkg -i .


Any help will be sincerely appreciated.

Gary R.

Re: selinux causing problems

[Tixy]

On Tue, 2023-10-31 at 18:36 +1300, Alex King wrote:
> Now it seems that selinux is active again, and even when I try to set 
> selinux=0 to disable it, it is still running and spamming the logs with 
> messages like
> 
> logrotate.service: Failed to read SELinux context of 
> '/lib/systemd/system/logrotate.service', ignoring: Operation not permitted
> 
> 
> How should I disable selinux?

I'm guessing here, but perhaps selinux _is_ disabled but things are
still trying to use it and producing error messages. Have you tried
uninstalled the 'apparmour' package? I remember doing this in years
past when it first started getting installed and putting noise on boot
screen and in logs.

-- 
Tixy

selinux causing problems

[Alex King]

Does anyone know how to disable selinux?

I had selinux installed on this system a long time ago.  Recently I 
believe apparmor was active (and therefore selinux not active).  Today I 
upgraded to Debian 12.


apparmor was preventing named (bind9) from running; whatever I did, it 
was denying read to a file (/usr/share/dns/root.hints).  So I disabled 
apparmor by setting apparmor=0 on the boot command line.


Now it seems that selinux is active again, and even when I try to set 
selinux=0 to disable it, it is still running and spamming the logs with 
messages like


logrotate.service: Failed to read SELinux context of 
'/lib/systemd/system/logrotate.service', ignoring: Operation not permitted



How should I disable selinux?  I followed the suggestion in the man page 
(man selinux: To properly disable SELinux, it is recommended to use the 
selinux=0 kernel boot option).  This does not seem to work.


Any help greatly appreciated.

Thanks,
Alex


# lsb_release  -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 12 (bookworm)
Release:12
Codename:   bookworm

# cat /proc/version
Linux version 6.1.0-13-686-pae (debian-ker...@lists.debian.org) (gcc-12 
(Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29)


# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-686-pae root=/dev/mapper/main-root ro 
quiet apparmor=0 selinux=0


# sestatus
SELinux status: enabled
SELinuxfs mount:/sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: default
Current mode:   permissive
Mode from config file:  disabled
Policy MLS status:  disabled
Policy deny_unknown status: denied
Memory protection checking: actual (secure)
Max kernel policy version:  33

Re: a couple of problems after upgrading to bookworm

[John Covici]

hmm, I thought I had this correct, but I will recheck and try again.
Thanks for the hint.

On Sun, 23 Jul 2023 09:35:44 -0400,
Greg Wooledge wrote:
> 
> On Sun, Jul 23, 2023 at 09:27:18AM -0400, John Covici wrote:
> > i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1_27.bin
> > failed with error -2 ...:  4 Time(s)
> > 
> > Where can I find this firmware -- isn't it in the firmware-linux-free
> > package?
> 
> unicorn:~$ dpkg -S /lib/firmware/i915/skl_dmc_ver1_27.bin
> firmware-misc-nonfree: /lib/firmware/i915/skl_dmc_ver1_27.bin
> 
> Remember, in bookworm, the non-free firmware has moved to a newly
> created section in the repositories.  Make sure your sources.list
> has been updated appropriately.
> 

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: a couple of problems after upgrading to bookworm

[Greg Wooledge]

On Sun, Jul 23, 2023 at 09:27:18AM -0400, John Covici wrote:
> i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1_27.bin
> failed with error -2 ...:  4 Time(s)
> 
> Where can I find this firmware -- isn't it in the firmware-linux-free
> package?

unicorn:~$ dpkg -S /lib/firmware/i915/skl_dmc_ver1_27.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_dmc_ver1_27.bin

Remember, in bookworm, the non-free firmware has moved to a newly
created section in the repositories.  Make sure your sources.list
has been updated appropriately.

a couple of problems after upgrading to bookworm

[John Covici]

Hi.  I upgraded to bookworm and it went pretty well, but I have some
strange errors (what's a not strange error).

I use logwatch and I am getting apache2 level error and then a number
of times, but I cannot find what its complaining about.  I did not get
these under bullseye.  I am running with kernel 6.1.0-10.

Also, I am getting the following:

i915 :00:02.0: Direct firmware load for i915/skl_dmc_ver1_27.bin
failed with error -2 ...:  4 Time(s)

Where can I find this firmware -- isn't it in the firmware-linux-free
package?


Thanks in advance for any suggestions.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: Upgrade to Debian 11 and still have the same problems.

[David Wright]

On Mon 17 Jul 2023 at 10:58:43 (-0400), Default User wrote:
> On Sun, 2023-07-16 at 17:21 -0400, Maureen L Thomas wrote:
> > So I have been snooping around the system and found this message in
> > the lshw command:
> >  *-generic DISABLED
> >  description: Wireless interface
> >  product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
> >  vendor: Realtek Semiconductor Co., Ltd.
> >  physical id: 0
> >  bus info: pci@:02:00.0
> >  logical name: wlp2s0
> >  version: ff
> >  serial: 3e:c2:77:77:6a:31
> >  width: 32 bits
> >  clock: 66MHz
> >  capabilities: bus_master vga_palette cap_list ethernet physical
> > wireless
> >  configuration: broadcast=yes driver=rtw_8821ce driverversion=5.10.0-
> > 23-amd64 firmware=N/A latency=255 link=no maxlatency=255 mingnt=255
> > multicast=yes wireless=IEEE 802.11
> >  resources: irq:129 ioport:d000(size=256) memory:df00-df00
> > 
> > Could this be part of the problem.  I have no wifi so that is part of
> > the problem.  This is Disabled so how do I enable it?   
> 
> I don't mean to butt in,

Don't worry—that's what we all do on a mailing list.

> but just wanted to give you some
> reassurance/encouragement.  The wireless adapter you have certainly
> should work (barring a hardware problem).  I have the same exact one,
> and it works fine!  
> 
> I am running Debian 12 (Bookworm) now, but the setup was upgraded in
> 2023-06 from Debian 11 (Bullseye).  It worked fine on Debian 11
> (Bullseye), at least under Debian 11.6. 
> 
> >From my current setup:
> 
> lshw:
> . . . 
>  *-network DISABLED
> description: Wireless interface
> product: RTL8821CE 802.11ac PCIe Wireless Network
> Adapter
> vendor: Realtek Semiconductor Co., Ltd.
> physical id: 0
> bus info: pci@:02:00.0
> logical name: wlp2s0
> version: 00
> serial: xx:xx:xx:xx:xx:xx
> width: 64 bits
> clock: 33MHz
> capabilities: pm msi pciexpress bus_master cap_list
> ethernet physical wireless
> configuration: broadcast=yes driver=rtw_8821ce
> driverversion=6.1.0-10-amd64 firmware=N/A latency=0 link=no

Can you confirm that firmware has been loaded onto your system:

  # dmesg | grep -B1 -A2 rtl8821

(ie, the binary blob, not the .deb package). IOW, does firmware=N/A
merely mean Not Applicable, because the device doesn't need or load it.

> multicast=yes wireless=IEEE 802.11
> resources: irq:135 ioport:3000(size=256)
> memory:7080-7080 
> . . . 
> 
> from lsmod:
> . . . 
> rtw88_8821c90112  1 rtw88_8821ce
> rtw88_pci  28672  1 rtw88_8821ce
> . . . 
> rtw88_core192512  2 rtw88_pci,rtw88_8821c
> . . . 
> 
> And firmware-realtek is installed.
> 
> >From sudo aptitude show firmware-realtek:
> Package: firmware-realtek
> Version: 20230210-5
> State: installed
> Automatically installed: no
> Multi-Arch: foreign
> Priority: optional
> Section: non-free-firmware/kernel
> Maintainer: Debian Kernel Team 
> Architecture: all
> Uncompressed Size: 7,046 k
> Suggests: initramfs-tools
> Description: Binary firmware for Realtek wired/wifi/BT adapters
>  This package contains the binary firmware for Realtek Ethernet, wifi
> and Bluetooth adapters
>  supported by various drivers. 
>  
>  Contents: 
> . . . 
> * Realtek RTL8821C Bluetooth config (rtl_bt/rtl8821c_config.bin,
> rtl_bt/rtl8821a_config.bin) 
>  * Realtek RTL8821C Bluetooth firmware (rtl_bt/rtl8821c_fw.bin) 
> . . . 
> 
> However, I am puzzled as to why aptitude says firmware-realtek is:
> State: installed
> Automatically installed: no
> since I never installed it manually, the wireless adapter just worked
> "right out of the box".
> 
> Note: Debian 11 was originally installed using using the Debian 11.6
> "nonfree" iso.  

As you used the nonfree/firmare ISO, the d-i detected the wifi device
and installed the appropriate firmware, included on the ISO, to make
it work. This typically happens just before installation-report and
popularity-contest, and the latter's question. The package appears
to be "manual" rather than "auto" because AIUI the d-i is installing
it, not APT.

I have no idea how the OP installed their system, whether they did it
through wifi, and which ISO they used. (Nor what "the /same/ problems"
are in the Subject line). Even if the original installation was done
with wifi, the fate that befalls the wifi configuration depends on
the choices made in the task selector. My beef has always been that
choosing a non-DE installation, as I do, results in the wifi
configuration being removed moments before the d-i reboots.

Cheers,
David.

Re: Upgrade to Debian 11 and still have the same problems.

[Peter Hillier-Brook]

On 17/07/2023 15:58, Default User wrote:

On Sun, 2023-07-16 at 17:21 -0400, Maureen L Thomas wrote:

So I have been snooping around the system and found this message in
the lshw command:
  *-generic DISABLED
  description: Wireless interface
  product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
  vendor: Realtek Semiconductor Co., Ltd.
  physical id: 0
  bus info: pci@:02:00.0
  logical name: wlp2s0
  version: ff
  serial: 3e:c2:77:77:6a:31
  width: 32 bits
  clock: 66MHz
  capabilities: bus_master vga_palette cap_list ethernet physical
wireless
  configuration: broadcast=yes driver=rtw_8821ce driverversion=5.10.0-
23-amd64 firmware=N/A latency=255 link=no maxlatency=255 mingnt=255
multicast=yes wireless=IEEE 802.11
  resources: irq:129 ioport:d000(size=256) memory:df00-df00

Could this be part of the problem.  I have no wifi so that is part of
the problem.  This is Disabled so how do I enable it?
Thank you guys for being patient with this old lady..
Moe
  
  




Hi, Maureen!

I don't mean to butt in, but just wanted to give you some
reassurance/encouragement.  The wireless adapter you have certainly
should work (barring a hardware problem).  I have the same exact one,
and it works fine!

I am running Debian 12 (Bookworm) now, but the setup was upgraded in
2023-06 from Debian 11 (Bullseye).  It worked fine on Debian 11
(Bullseye), at least under Debian 11.6.


From my current setup:


lshw:
. . .
  *-network DISABLED
 description: Wireless interface
 product: RTL8821CE 802.11ac PCIe Wireless Network
Adapter
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: xx:xx:xx:xx:xx:xx
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
ethernet physical wireless
 configuration: broadcast=yes driver=rtw_8821ce
driverversion=6.1.0-10-amd64 firmware=N/A latency=0 link=no
multicast=yes wireless=IEEE 802.11
 resources: irq:135 ioport:3000(size=256)
memory:7080-7080
. . .

from lsmod:
. . .
rtw88_8821c90112  1 rtw88_8821ce
rtw88_pci  28672  1 rtw88_8821ce
. . .
rtw88_core192512  2 rtw88_pci,rtw88_8821c
. . .

And firmware-realtek is installed.


From sudo aptitude show firmware-realtek:

Package: firmware-realtek
Version: 20230210-5
State: installed
Automatically installed: no
Multi-Arch: foreign
Priority: optional
Section: non-free-firmware/kernel
Maintainer: Debian Kernel Team 
Architecture: all
Uncompressed Size: 7,046 k
Suggests: initramfs-tools
Description: Binary firmware for Realtek wired/wifi/BT adapters
  This package contains the binary firmware for Realtek Ethernet, wifi
and Bluetooth adapters
  supported by various drivers.
  
  Contents:

. . .
* Realtek RTL8821C Bluetooth config (rtl_bt/rtl8821c_config.bin,
rtl_bt/rtl8821a_config.bin)
  * Realtek RTL8821C Bluetooth firmware (rtl_bt/rtl8821c_fw.bin)
. . .

However, I am puzzled as to why aptitude says firmware-realtek is:
State: installed
Automatically installed: no
since I never installed it manually, the wireless adapter just worked
"right out of the box".

Note: Debian 11 was originally installed using using the Debian 11.6
"nonfree" iso.

Hope this helps. Otherwise, feel free to disregard.

For what it's worth, I lost my wifi connection (via a USB Realtek 
adaptor) a couple of days ago and finally woke up enough to swap the USB 
adaptor to another USB port. So no diagnosis, but it works. Maybe this 
will do the same for you, Maureen. Oh! and I re-installed the 
realtek-firmware package, but I suspect that is a red herring.


Peter HB

Re: Upgrade to Debian 11 and still have the same problems.

[Default User]

On Sun, 2023-07-16 at 17:21 -0400, Maureen L Thomas wrote:
> So I have been snooping around the system and found this message in
> the lshw command:
>  *-generic DISABLED
>  description: Wireless interface
>  product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
>  vendor: Realtek Semiconductor Co., Ltd.
>  physical id: 0
>  bus info: pci@:02:00.0
>  logical name: wlp2s0
>  version: ff
>  serial: 3e:c2:77:77:6a:31
>  width: 32 bits
>  clock: 66MHz
>  capabilities: bus_master vga_palette cap_list ethernet physical
> wireless
>  configuration: broadcast=yes driver=rtw_8821ce driverversion=5.10.0-
> 23-amd64 firmware=N/A latency=255 link=no maxlatency=255 mingnt=255
> multicast=yes wireless=IEEE 802.11
>  resources: irq:129 ioport:d000(size=256) memory:df00-df00
> 
> Could this be part of the problem.  I have no wifi so that is part of
> the problem.  This is Disabled so how do I enable it?   
> Thank you guys for being patient with this old lady..
> Moe
>  
>  



Hi, Maureen! 

I don't mean to butt in, but just wanted to give you some
reassurance/encouragement.  The wireless adapter you have certainly
should work (barring a hardware problem).  I have the same exact one,
and it works fine!  

I am running Debian 12 (Bookworm) now, but the setup was upgraded in
2023-06 from Debian 11 (Bullseye).  It worked fine on Debian 11
(Bullseye), at least under Debian 11.6. 

>From my current setup:

lshw:
. . . 
 *-network DISABLED
description: Wireless interface
product: RTL8821CE 802.11ac PCIe Wireless Network
Adapter
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@:02:00.0
logical name: wlp2s0
version: 00
serial: xx:xx:xx:xx:xx:xx
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
ethernet physical wireless
configuration: broadcast=yes driver=rtw_8821ce
driverversion=6.1.0-10-amd64 firmware=N/A latency=0 link=no
multicast=yes wireless=IEEE 802.11
resources: irq:135 ioport:3000(size=256)
memory:7080-7080 
. . . 

from lsmod:
. . . 
rtw88_8821c90112  1 rtw88_8821ce
rtw88_pci  28672  1 rtw88_8821ce
. . . 
rtw88_core192512  2 rtw88_pci,rtw88_8821c
. . . 

And firmware-realtek is installed.

>From sudo aptitude show firmware-realtek:
Package: firmware-realtek
Version: 20230210-5
State: installed
Automatically installed: no
Multi-Arch: foreign
Priority: optional
Section: non-free-firmware/kernel
Maintainer: Debian Kernel Team 
Architecture: all
Uncompressed Size: 7,046 k
Suggests: initramfs-tools
Description: Binary firmware for Realtek wired/wifi/BT adapters
 This package contains the binary firmware for Realtek Ethernet, wifi
and Bluetooth adapters
 supported by various drivers. 
 
 Contents: 
. . . 
* Realtek RTL8821C Bluetooth config (rtl_bt/rtl8821c_config.bin,
rtl_bt/rtl8821a_config.bin) 
 * Realtek RTL8821C Bluetooth firmware (rtl_bt/rtl8821c_fw.bin) 
. . . 

However, I am puzzled as to why aptitude says firmware-realtek is:
State: installed
Automatically installed: no
since I never installed it manually, the wireless adapter just worked
"right out of the box".

Note: Debian 11 was originally installed using using the Debian 11.6
"nonfree" iso.  

Hope this helps. Otherwise, feel free to disregard.

Re: Upgrade to Debian 11 and still have the same problems.

[Jeffrey Walton]

On Sun, Jul 16, 2023 at 5:22 PM Maureen L Thomas  wrote:
>
> So I have been snooping around the system and found this message in the lshw 
> command:
>
> *-generic DISABLED
>
> description: Wireless interface
>
> product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
>
> vendor: Realtek Semiconductor Co., Ltd.
>
> physical id: 0
>
> bus info: pci@:02:00.0
>
> logical name: wlp2s0
>
> version: ff
>
> serial: 3e:c2:77:77:6a:31
>
> width: 32 bits
>
> clock: 66MHz
>
> capabilities: bus_master vga_palette cap_list ethernet physical wireless
>
> configuration: broadcast=yes driver=rtw_8821ce driverversion=5.10.0-23-amd64 
> firmware=N/A latency=255 link=no maxlatency=255 mingnt=255 multicast=yes 
> wireless=IEEE 802.11
>
> resources: irq:129 ioport:d000(size=256) memory:df00-df00
>
> Could this be part of the problem.  I have no wifi so that is part of the 
> problem.  This is Disabled so how do I enable it?
>
> Thank you guys for being patient with this old lady..

See the part about non-free-firmware at https://wiki.debian.org/DebianUpgrade .

Jeff

Re: Upgrade to Debian 11 and still have the same problems.

[David Wright]

On Sun 16 Jul 2023 at 17:21:37 (-0400), Maureen L Thomas wrote:
> So I have been snooping around the system and found this message in
> the lshw command:
> 
> *-generic DISABLED
> description: Wireless interface
> product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
> vendor: Realtek Semiconductor Co., Ltd.
> physical id: 0
> bus info: pci@:02:00.0
> logical name: wlp2s0
> version: ff
> serial: 3e:c2:77:77:6a:31
> width: 32 bits
> clock: 66MHz
> capabilities: bus_master vga_palette cap_list ethernet physical wireless
> configuration: broadcast=yes driver=rtw_8821ce
> driverversion=5.10.0-23-amd64 firmware=N/A latency=255 link=no



> maxlatency=255 mingnt=255 multicast=yes wireless=IEEE 802.11
> resources: irq:129 ioport:d000(size=256) memory:df00-df00
> 
> Could this be part of the problem.  I have no wifi so that is part of
> the problem. This is Disabled so how do I enable it?

Have you installed the package firmware-realtek?

Cheers,
David.

Upgrade to Debian 11 and still have the same problems.

[Maureen L Thomas]

So I have been snooping around the system and found this message in the 
lshw command:


*-generic DISABLED

description: Wireless interface

product: RTL8821CE 802.11ac PCIe Wireless Network Adapter

vendor: Realtek Semiconductor Co., Ltd.

physical id: 0

bus info: pci@:02:00.0

logical name: wlp2s0

version: ff

serial: 3e:c2:77:77:6a:31

width: 32 bits

clock: 66MHz

capabilities: bus_master vga_palette cap_list ethernet physical wireless

configuration: broadcast=yes driver=rtw_8821ce 
driverversion=5.10.0-23-amd64 firmware=N/A latency=255 link=no 
maxlatency=255 mingnt=255 multicast=yes wireless=IEEE 802.11


resources: irq:129 ioport:d000(size=256) memory:df00-df00


Could this be part of the problem.  I have no wifi so that is part of 
the problem. This is Disabled so how do I enable it?


Thank you guys for being patient with this old lady..

Moe

Re: qt.network.ssl problems (OT?)

[Patrick Wiseman]

On Tue, Jun 20, 2023 at 5:30 PM gene heskett  wrote:

>
> I have no idea about the creality clone, but klipper runs perfectly fine
> on a bananapi-m5 w/4gigs of dram in front of the printer.  klipper
> itself is a 2 part thing, one part replacing the usually crippled marlin
> in the printers controller, by reflashing the controller card, the other
> part massages the gcode on the way to the printer enhancing the printers
> speed among other advantages.
>
> Turns out that the K1 printer is Klipper under the hood and there's a way
to hack it to gain full access (so I don't need the broken app).

Cheers
Patrick

Re: qt.network.ssl problems (OT?)

[gene heskett]

On 6/20/23 15:00, Patrick Wiseman wrote:

On Tue, Jun 20, 2023 at 2:18 PM Patrick Wiseman  wrote:


On Tue, Jun 20, 2023, 2:02 PM gene heskett  wrote:


On 6/20/23 13:33, Patrick Wiseman wrote:

Hello, all:

This may be a little off-topic, in which case, apologies, but there's so
much knowledge here, maybe someone can help.

I recently acquired a Creality 3D printer, and Creality has supplied an
AppImage to operate it. When I execute it, I get these errors and a
segmentation fault:

qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
Segmentation fault

Googling suggests this is a common problem for developers using Qt, but

I

didn't find any obvious solution. Help would be much appreciated.

Patrick


That AppImage is probably a copyright violation copy of an old and
outdated klipper, Please install and use the real thing, many bugs have
been treated since it was forked and put under their proprietary
umbrella. I have an S1 coming tomorrow, but it will get run by the real
thing.



Thanks , but the AppImage is what it is and the firmware on the K1 printer
is also what it is. Anything else I can do?





An acquaintance tells me it runs fine on Linux Mint 21.1 so what's
different about Debian 12 (bookworm)? And isn't an AppImage supposed to run
anywhere?

Patrick


I have no idea about the creality clone, but klipper runs perfectly fine 
on a bananapi-m5 w/4gigs of dram in front of the printer.  klipper 
itself is a 2 part thing, one part replacing the usually crippled marlin 
in the printers controller, by reflashing the controller card, the other 
part massages the gcode on the way to the printer enhancing the printers 
speed among other advantages.




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

Re: qt.network.ssl problems (OT?)

[Patrick Wiseman]

On Tue, Jun 20, 2023 at 2:18 PM Patrick Wiseman  wrote:

> On Tue, Jun 20, 2023, 2:02 PM gene heskett  wrote:
>
>> On 6/20/23 13:33, Patrick Wiseman wrote:
>> > Hello, all:
>> >
>> > This may be a little off-topic, in which case, apologies, but there's so
>> > much knowledge here, maybe someone can help.
>> >
>> > I recently acquired a Creality 3D printer, and Creality has supplied an
>> > AppImage to operate it. When I execute it, I get these errors and a
>> > segmentation fault:
>> >
>> > qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
>> > qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
>> > Segmentation fault
>> >
>> > Googling suggests this is a common problem for developers using Qt, but
>> I
>> > didn't find any obvious solution. Help would be much appreciated.
>> >
>> > Patrick
>>
>> That AppImage is probably a copyright violation copy of an old and
>> outdated klipper, Please install and use the real thing, many bugs have
>> been treated since it was forked and put under their proprietary
>> umbrella. I have an S1 coming tomorrow, but it will get run by the real
>> thing.
>>
>
> Thanks , but the AppImage is what it is and the firmware on the K1 printer
> is also what it is. Anything else I can do?
>
>>
>>
An acquaintance tells me it runs fine on Linux Mint 21.1 so what's
different about Debian 12 (bookworm)? And isn't an AppImage supposed to run
anywhere?

Patrick

Re: qt.network.ssl problems (OT?)

[Patrick Wiseman]

On Tue, Jun 20, 2023, 2:02 PM gene heskett  wrote:

> On 6/20/23 13:33, Patrick Wiseman wrote:
> > Hello, all:
> >
> > This may be a little off-topic, in which case, apologies, but there's so
> > much knowledge here, maybe someone can help.
> >
> > I recently acquired a Creality 3D printer, and Creality has supplied an
> > AppImage to operate it. When I execute it, I get these errors and a
> > segmentation fault:
> >
> > qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
> > qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
> > Segmentation fault
> >
> > Googling suggests this is a common problem for developers using Qt, but I
> > didn't find any obvious solution. Help would be much appreciated.
> >
> > Patrick
>
> That AppImage is probably a copyright violation copy of an old and
> outdated klipper, Please install and use the real thing, many bugs have
> been treated since it was forked and put under their proprietary
> umbrella. I have an S1 coming tomorrow, but it will get run by the real
> thing.
>

Thanks , but the AppImage is what it is and the firmware on the K1 printer
is also what it is. Anything else I can do?

Patrick


>

Re: qt.network.ssl problems (OT?)

[gene heskett]

On 6/20/23 13:33, Patrick Wiseman wrote:

Hello, all:

This may be a little off-topic, in which case, apologies, but there's so
much knowledge here, maybe someone can help.

I recently acquired a Creality 3D printer, and Creality has supplied an
AppImage to operate it. When I execute it, I get these errors and a
segmentation fault:

qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
Segmentation fault

Googling suggests this is a common problem for developers using Qt, but I
didn't find any obvious solution. Help would be much appreciated.

Patrick


That AppImage is probably a copyright violation copy of an old and 
outdated klipper, Please install and use the real thing, many bugs have 
been treated since it was forked and put under their proprietary 
umbrella. I have an S1 coming tomorrow, but it will get run by the real 
thing.


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

qt.network.ssl problems (OT?)

[Patrick Wiseman]

Hello, all:

This may be a little off-topic, in which case, apologies, but there's so
much knowledge here, maybe someone can help.

I recently acquired a Creality 3D printer, and Creality has supplied an
AppImage to operate it. When I execute it, I get these errors and a
segmentation fault:

qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
Segmentation fault

Googling suggests this is a common problem for developers using Qt, but I
didn't find any obvious solution. Help would be much appreciated.

Patrick

Re: [Debian 12 Issue] Black Screen after starting X11. Cant log in into Graphical Environments. Either DEs or WMs. AMD Radeon GPU problems

[Michel Verdier]

Le 18 juin 2023 Paul Gerdes a écrit :

> i get these messages:
> "grep: /var/log/Xorg.*: No such file or directory"
> "grep: /var/log/Xorg: No such file or directory"
>
> looks like there is no log file for X11

Did you also try to start X with startx from a tty ?

Can you provide
find /etc/ | grep xorg

And from your login user
grep EE ~/.local/share/xorg/Xorg.*
grep WW ~/.local/share/xorg/Xorg.*
cat ~/.bash_profile
cat ~/.xserverrc
cat ~/.xsession
cat ~/.xsession-errors

Re: [Debian 12 Issue] Black Screen after starting X11. Cant log in into Graphical Environments. Either DEs or WMs. AMD Radeon GPU problems

[Michel Verdier]

On 2023-06-17, Paul Gerdes wrote:

> Hi i have a problem with Debian 12 after Installation.
> Every time i try to log in to the Desktop Environment or WM my Screen goes
> black. The PC completely freezes and i cant switch to another TTY.

Did you check X logs ? With something like

grep EE /var/log/Xorg.*
grep WW /var/log/Xorg.*

[Debian 12 Issue] Black Screen after starting X11. Cant log in into Graphical Environments. Either DEs or WMs. AMD Radeon GPU problems

[Paul Gerdes]

Hi i have a problem with Debian 12 after Installation.
Every time i try to log in to the Desktop Environment or WM my Screen goes
black. The PC completely freezes and i cant switch to another TTY.

I reinstalled Debian 12 a few times via netinstall. Tried different Desktop
Environments and WMs. The Installation runs through without any issues.
Running Debian without graphical environment (Terminal only TTY) is running
fine. Installing packages via apt is also fine. As soon as i install a DE
or WM and restart the machine, the screen goes black (after showing the
boot screen). I cant log in to any Desktop.
I also tried booting the Live ISOs of Debian 12 Gnome and XFCE edition. And
Fedora Workstation 38 Live ISO. All of them have the same issues.

I found out that Linux runs fine when i took the AMD GPU out of the PC.
Running Linux only with internal Intel GPU. As soon as i put the AMD GPU
back in its starting to freeze / black out again.

Drivers and Firmware are installed following this wiki:
https://wiki.debian.org/AtiHowTo

The Systems Specs are:
Mainboard MSI CSM-Q87M-E43 (MS-7830)
Intel i5-4570
Graphics AMD Radeon R9 390 (Powercolor)
16 GB Ram Corsair DDR3-1333
SSD Gigabyte GP-GS 500GB

I had no issues with Windows 10 on this machine. 3D games and everything
runs fine.

Re: Problems apache2-data package with http repositories

[James Addison]

Hi Hervé and debian-user-french,

My apologies: I do not speak French but I see a connection between two
threads here with:

https://lists.debian.org/debian-user-french/2023/01/msg00079.html

So this issue has occurred at least twice and appears to be related to
pattern-matching safety checks performed by Sophos software on HTTP
downloads.

I would recommend collecting the "pattern version" information from
the error messages, and contacting Sophos support with those and the
URL of the Apache2 package that is prevented from download.

The apache2-data .deb file looks OK to me when I download it: I don't
see any deeply-nested archives inside it.

Regards,
James

Re: Perl, cpan Path problems

[Andy Smith]

Hello,

On Sat, Jan 28, 2023 at 05:17:51PM -0500, Greg Wooledge wrote:
> Debian provides many perl packages, so you have two paths to choose
> from here: you can try to find the package in Debian, and use that,
> or you can try to build it yourself.
> 
> On a Debian 11 system, I get this result:
> 
> unicorn:~$ apt-cache search --names-only perl xml simple

[…]

> Your Debian 10 system may have a different version of this package, or
> it might have the package under a different name, or it might not have
> it at all.  That's why I showed how I discovered the name.  You can
> follow the same basic steps.

Some useful knowledge for finding Perl modules on Debian is that
'::' in the module name will be replaced by '/' in the file path,
and the final file will have '.pm' on the end.

So unless Perl changes dramatically in the future, XML::Simple will
ship a file with "XML/Simple.pm" in the path, which is very amenable
to an "apt-file search".

That will still throw up a bunch of results a lot like what you got
with the apt-cache search. Out of those it's usually easy to tell
which is the one, as in Debian the Perl module package names are
currently formed of:

'lib' + (lower cased module name with every '::' changed to '-') + '-perl'

So, in this case, libxml-simple-perl.

> When you download the source from CPAN and try to build it, it'll probably
> spew a list of missing dependencies.  Then you have to look for each of
> those missing dependencies, either as Debian packages, or as source code
> from CPAN that you have to build by hand.

"cpanminus" that I mentioned earlier will download, build, test and
install a module and all of its dependencies into a specified
directory tree so it can easily be kept separate from the system,
and updated as needed. It's very convenient, though of course not as
nice as having the packaging already done. 

As OP doesn't seem to be familiar enough with Perl on Debian to work
out how to find if modules are already installed or available, it
may be a bit of a leap anyway.

As you say, all the other options only get more complicated from there.

Cheers,
Andy

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

AW: Perl, cpan Path problems

[Maurizio Caloro]

Running, meny thanks!

-Ursprüngliche Nachricht-
Von: Greg Wooledge  
Gesendet: Samstag, 28. Januar 2023 23:18
An: debian-user@lists.debian.org
Betreff: Re: Perl, cpan Path problems

On Sat, Jan 28, 2023 at 10:47:01PM +0100, Maurizio Caloro wrote:
> also
> 
> root: ~/.cpan/build/Perl-Critic-1.148-2# perl -e "use XML::Simple "

I'm only going to focus on this ONE part of your mail, because the whole
thing is just too much for me.

Let's suppose that your goal is to write (or use) a perl script that needs
the XML::Simple package.

Debian provides many perl packages, so you have two paths to choose from
here: you can try to find the package in Debian, and use that, or you can
try to build it yourself.

On a Debian 11 system, I get this result:

unicorn:~$ apt-cache search --names-only perl xml simple
libtest-xml-simple-perl - Perl testing framework for XML data
libxml-atom-simplefeed-perl - Perl module for generation of Atom syndication
feeds libxml-libxml-simple-perl - Perl module that uses the XML::LibXML
parser for XML structures libxml-opml-simplegen-perl - module for creating
OPML using XML::Simple libxml-rss-simplegen-perl - Perl module for easily
writing RSS files libxml-simple-perl - Perl module for reading and writing
XML libxml-simpleobject-enhanced-perl - Perl module which enhances
libxml-simpleobject-perl libxml-simpleobject-libxml-perl - Simple oo
representation of an XML::LibXML DOM object libxml-simpleobject-perl -
Objectoriented Perl interface to a parsed XML::Parser tree
libxml-writer-simple-perl - simple API to create XML files

Buried in the middle of that result is the libxml-simple-perl package, which
I'm going to guess is the correct one.

Now that I know its name, I can also check its version:

unicorn:~$ apt-cache show libxml-simple-perl | grep Version
Version: 2.25-1

So, if version 2.25 of XML::Simple is acceptable, then I can simply install
that (using apt or apt-get or aptitude or whichever tool I prefer).

Your Debian 10 system may have a different version of this package, or it
might have the package under a different name, or it might not have it at
all.  That's why I showed how I discovered the name.  You can follow the
same basic steps.

If you wish to build a package from CPAN yourself (either because Debian
doesn't have the package at all, or because the package in Debian is not a
suitable version), it can get REALLY messy.  This is not the path that I
prefer.

When you download the source from CPAN and try to build it, it'll probably
spew a list of missing dependencies.  Then you have to look for each of
those missing dependencies, either as Debian packages, or as source code
from CPAN that you have to build by hand.

Each dependent package may have additional dependencies of its own,
recursively,  It's not a lot of fun.

So, anyway... long story short?  Figure out what you're actually trying to
do, and then do *only* that.  Want to run a script that uses XML::Simple?
Install libxml-simple-perl (or whatever it is on Debian 10, though it's
probably the same), and see if that's good enough.

Don't borrow trouble by looking for some all-encompassing knowledge of all
things perl/CPAN on Debian.  You don't need to know how to install every
conceivable CPAN package.  Just get the one package you need.

Re: Perl, cpan Path problems

[Greg Wooledge]

On Sat, Jan 28, 2023 at 10:47:01PM +0100, Maurizio Caloro wrote:
> also 
> 
> root: ~/.cpan/build/Perl-Critic-1.148-2# perl -e "use XML::Simple "

I'm only going to focus on this ONE part of your mail, because the whole
thing is just too much for me.

Let's suppose that your goal is to write (or use) a perl script that
needs the XML::Simple package.

Debian provides many perl packages, so you have two paths to choose
from here: you can try to find the package in Debian, and use that,
or you can try to build it yourself.

On a Debian 11 system, I get this result:

unicorn:~$ apt-cache search --names-only perl xml simple
libtest-xml-simple-perl - Perl testing framework for XML data
libxml-atom-simplefeed-perl - Perl module for generation of Atom syndication 
feeds
libxml-libxml-simple-perl - Perl module that uses the XML::LibXML parser for 
XML structures
libxml-opml-simplegen-perl - module for creating OPML using XML::Simple
libxml-rss-simplegen-perl - Perl module for easily writing RSS files
libxml-simple-perl - Perl module for reading and writing XML
libxml-simpleobject-enhanced-perl - Perl module which enhances 
libxml-simpleobject-perl
libxml-simpleobject-libxml-perl - Simple oo representation of an XML::LibXML 
DOM object
libxml-simpleobject-perl - Objectoriented Perl interface to a parsed 
XML::Parser tree
libxml-writer-simple-perl - simple API to create XML files

Buried in the middle of that result is the libxml-simple-perl package,
which I'm going to guess is the correct one.

Now that I know its name, I can also check its version:

unicorn:~$ apt-cache show libxml-simple-perl | grep Version
Version: 2.25-1

So, if version 2.25 of XML::Simple is acceptable, then I can simply install
that (using apt or apt-get or aptitude or whichever tool I prefer).

Your Debian 10 system may have a different version of this package, or
it might have the package under a different name, or it might not have
it at all.  That's why I showed how I discovered the name.  You can
follow the same basic steps.

If you wish to build a package from CPAN yourself (either because Debian
doesn't have the package at all, or because the package in Debian is not
a suitable version), it can get REALLY messy.  This is not the path that
I prefer.

When you download the source from CPAN and try to build it, it'll probably
spew a list of missing dependencies.  Then you have to look for each of
those missing dependencies, either as Debian packages, or as source code
from CPAN that you have to build by hand.

Each dependent package may have additional dependencies of its own,
recursively,  It's not a lot of fun.

So, anyway... long story short?  Figure out what you're actually trying
to do, and then do *only* that.  Want to run a script that uses XML::Simple?
Install libxml-simple-perl (or whatever it is on Debian 10, though it's
probably the same), and see if that's good enough.

Don't borrow trouble by looking for some all-encompassing knowledge of
all things perl/CPAN on Debian.  You don't need to know how to install
every conceivable CPAN package.  Just get the one package you need.

Re: Perl, cpan Path problems

[Andy Smith]

Hi,

On Sat, Jan 28, 2023 at 10:47:01PM +0100, Maurizio Caloro wrote:
> root ~/.cpan/build/Perl-Critic-1.148-2# cpan Perl::OSType

Firstly, v1.010 of Perl::OSType is already included in default
Debian perl installs on Debian 10 (buster) and in fact that is the
latest version oif that module, so why are you trying to also
install it from CPAN? It will not give you a newer version of that
module.

$ perl -MPerl::OSType -E 'say $Perl::OSType::VERSION'
1.010

Secondly, once you do come to need some non-included Perl module (or
a newer version of an included one), you'll have an easier time
using "cpanminus", which you can install as a Debian package. After
you've done that:

# cpanm --local-lib=/path/to/your/libs Whatever::Module

This will then download, build and install Whatever::Module (and any
dependencies) into /path/to/your/libs/.

"cpanminus" is much nicer to use than "cpan". See its web page at
https://metacpan.org/pod/App::cpanminus for full details.

Cheers,
Andy

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

Perl, cpan Path problems

[Maurizio Caloro]

Hello

 

Here iam running with Debian 10.13, and please i need little Support

 

 

-

 

i think me cpan and perl have any problems, please what are the right path
for PERL_LIB?`

how i can reinstall cpan or Perl so that i can install Cpan/Perl packages?

 

this always i have executed

> $ cpan o conf init

 

thanks for any possible help

root ~/.cpan/build/Perl-Critic-1.148-2# cpan Perl::OSType

Loading internal logger. Log::Log4perl recommended for better logging

Reading '/root/.cpan/Metadata'

  Database was generated on Sat, 28 Jan 2023 18:54:01 GMT

Running install for module 'Perl::OSType'

Checksum for
/root/.cpan/sources/authors/id/D/DA/DAGOLDEN/Perl-OSType-1.010.tar.gz ok

'YAML' not installed, will not store persistent state

The content of '/root/.cpan/build/Perl-OSType-1.010-1/META.yml' is not a
HASH reference. Cannot use it.

Configuring D/DA/DAGOLDEN/Perl-OSType-1.010.tar.gz with Makefile.PL

Checking if your kit is complete...

Looks good

 

Warning: PERL_LIB (/usr/share/perl/5.28) seems not to be a perl library
directory

(strict.pm not found) at /etc/perl/ExtUtils/MM_Unix.pm line 1948.

 

Generating a Unix-style Makefile

Writing Makefile for Perl::OSType

  DAGOLDEN/Perl-OSType-1.010.tar.gz

  /usr/bin/perl Makefile.PL INSTALLDIRS=site -- OK

Running make for D/DA/DAGOLDEN/Perl-OSType-1.010.tar.gz

The content of '/root/.cpan/build/Perl-OSType-1.010-1/META.yml' is not a
HASH reference. Cannot use it.

Could not read metadata file. Falling back to other methods to determine
prerequisites

cp lib/Perl/OSType.pm blib/lib/Perl/OSType.pm

Manifying 1 pod document

  DAGOLDEN/Perl-OSType-1.010.tar.gz

  /usr/bin/make -- OK

Running make test for DAGOLDEN/Perl-OSType-1.010.tar.gz

PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM"
"-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0,
'blib/lib', 'blib/arch')" t/*.t

Can't locate Benchmark.pm in @INC (you may need to install the Benchmark
module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at
/usr/local/share/perl/5.28.1/TAP/Parser/Aggregator.pm line 5.

BEGIN failed--compilation aborted at
/usr/local/share/perl/5.28.1/TAP/Parser/Aggregator.pm line 5.

Compilation failed in require at
/usr/local/share/perl/5.28.1/Test/Harness.pm line 12.

BEGIN failed--compilation aborted at
/usr/local/share/perl/5.28.1/Test/Harness.pm line 12.

Compilation failed in require.

BEGIN failed--compilation aborted.

make: *** [Makefile:778: test_dynamic] Error 2

  DAGOLDEN/Perl-OSType-1.010.tar.gz

  /usr/bin/make test -- NOT OK

//hint// to see the cpan-testers results for installing this module, try:

  reports DAGOLDEN/Perl-OSType-1.010.tar.gz

root@ ~/.cpan/build/Perl-Critic-1.148-2#

 

--

 

root:~/.cpan/build/Perl-Critic-1.148-2# cpan install XML::Simple

Loading internal logger. Log::Log4perl recommended for better logging

Reading '/root/.cpan/Metadata'

  Database was generated on Sat, 28 Jan 2023 18:54:01 GMT

Running install for module 'XML::Simple'

Fetching with HTTP::Tiny:

https://cpan.org/authors/id/G/GR/GRANTM/XML-Simple-2.25.tar.gz

Fetching with HTTP::Tiny:

https://cpan.org/authors/id/G/GR/GRANTM/CHECKSUMS

Checksum for
/root/.cpan/sources/authors/id/G/GR/GRANTM/XML-Simple-2.25.tar.gz ok

'YAML' not installed, will not store persistent state

The content of '/root/.cpan/build/XML-Simple-2.25-0/META.yml' is not a HASH
reference. Cannot use it.

Configuring G/GR/GRANTM/XML-Simple-2.25.tar.gz with Makefile.PL

Checking if your kit is complete...

Looks good

Warning: PERL_LIB (/usr/share/perl/5.28) seems not to be a perl library
directory

(strict.pm not found) at /etc/perl/ExtUtils/MM_Unix.pm line 1948.

Generating a Unix-style Makefile

Writing Makefile for XML::Simple

  GRANTM/XML-Simple-2.25.tar.gz

  /usr/bin/perl Makefile.PL INSTALLDIRS=site -- OK

Running make for G/GR/GRANTM/XML-Simple-2.25.tar.gz

The content of '/root/.cpan/build/XML-Simple-2.25-0/META.yml' is not a HASH
reference. Cannot use it.

Could not read metadata file. Falling back to other methods to determine
prerequisites

cp lib/XML/Simple/FAQ.pod blib/lib/XML/Simple/FAQ.pod

cp lib/XML/Simple.pm blib/lib/XML/Simple.pm

Manifying 2 pod documents

  GRANTM/XML-Simple-2.25.tar.gz

  /usr/bin/make -- OK

Running make test for GRANTM/XML-Simple-2.25.tar.gz

PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM"
"-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(0,
'blib/lib', 'blib/arch')" t/*.t

Can't locate Benchmark.pm in @INC (you may need to install the Benchmark
module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1
/u

Re: Topic: Problems with USB Sticks

[tomas]

On Mon, Jan 23, 2023 at 06:18:40AM +0100, to...@tuxteam.de wrote:
> On Sun, Jan 22, 2023 at 03:48:35PM +, Schwibinger Michael wrote:
> > Hello group. Hello Joe.
> > Thank you again for your Email.
> > Sorry, I did bad asking.
> > How can I make an USB stick writable, please?
> 
> I think USB stick is broken. If you can write to other USB sticks,
> I am sure USB stick is broken.
> 
> If there are important data there, please, copy them to a safe
> place and don't use this USB stick for important things.

And oh, your mail provider, hotmail, is broken, too. It bounces my
mails to you.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Topic: Problems with USB Sticks

[tomas]

On Sun, Jan 22, 2023 at 03:48:35PM +, Schwibinger Michael wrote:
> Hello group. Hello Joe.
> Thank you again for your Email.
> Sorry, I did bad asking.
> How can I make an USB stick writable, please?

I think USB stick is broken. If you can write to other USB sticks,
I am sure USB stick is broken.

If there are important data there, please, copy them to a safe
place and don't use this USB stick for important things.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Topic: Problems with USB Sticks

[David Wright]

On Wed 11 Jan 2023 at 18:30:33 (+), Schwibinger Michael wrote:
> Hello Joe. Hello group.
> Thank you so much for your Emails.

This thread has been going nowhere for eight weeks now.

> How can I make an USB stick only readable but not writable?

Most sticks can't do this. Some SD cards (or their adapters)
can.

> How can I make an USB stick which is only readable again writable?

If you've tried advice already given, and failed, then you
probably can't.

1. Mount the stick and copy any information of value to somewhere
safe. You should already have done this in the course of normal backups.

2. If you need the information to be available on a stick,
and haven't got a spare one, buy a new one, and copy the
desired information onto it.

3. Destroy the old stick with a hammer to prevent any sensitive
information it contains falling into the wrong hands.

4. Dispose of the waste carefully, according to your jurisdiction.

5. Any stick can become partially or wholly unusable at any time,
so backups, backups, backups. (And perhaps buy several sticks.)

Cheers,
David.

AW: Topic: Problems with USB Sticks

[Schwibinger Michael]

Hello group. Hello Joe.
Thank you again for your Email.
Sorry, I did bad asking.
How can I make an USB stick writable, please?


Regards,
Sophie



Von: Joe 
Gesendet: Freitag, 30. Dezember 2022 21:49
An: debian-user@lists.debian.org 
Betreff: Re: Topic: Problems with USB Sticks

On Fri, 30 Dec 2022 21:16:31 +
debian-u...@howorth.org.uk wrote:

> > Hello group. Hello Joe.
> > Thank you for your Email.
> >
> > Sorry, I did bad asking.
> > So I split the question.
> >
> > 1
> > How can I repair USB stick which is readable but not writable?
> >
> > question 2
> > What did I do wrong to create this problem?
>
> You didn't tell us what you actually did, and especially which bits
> you think might be a mistake, so it's very difficult for us to answer
> this question.
>
> For example, you might have hit them with a hammer, or connected them
> to the wrong voltages, or washed them in a bath, or who knows what? Or
> you might have plugged them in correctly but used some sequence of
> commands that has caused a problem. But until you tell us what you
> did, we can't know which bit was wrong!
>

I mentioned probably the simplest thing: failing to unmount before
removal on a Windows machine. This sometimes causes problems which
cause Linux to refuse to mount the device read/write. Windows can
usually fix it, though I suppose there may be data loss. It's entirely
possible that doing the same thing on Linux would sometimes cause
similar problems.

--
Joe

Re: Problems with host sleeping

[Tom Browder]

On Tue, Jan 10, 2023 at 16:24 Ximo  wrote:

> Hi,
> Did you checked the hardware?


I'm continuing my attempts. I have successfully installed Debian 11 and
changed all the settings to stay awake 24/7.

It worked for a little over a day and just quit. I'm returning it to the
seller so he can fix the problem.

Thanks.

-Tom

AW: Topic: Problems with USB Sticks

[Schwibinger Michael]

Hello Cindy. Hello group.
Thank you for you email.

Sorry, I did it in a bad way describe.
I put the USB stick in, and I can see all files on the USB stick.
But I cannot destroy them.


Regards,
Sophie




Von: Cindy Sue Causey 
Gesendet: Samstag, 31. Dezember 2022 17:22
An: Debian Users 
Betreff: Re: Topic: Problems with USB Sticks

On 12/30/22, Joe  wrote:
> On Fri, 30 Dec 2022 21:16:31 +
> debian-u...@howorth.org.uk wrote:
>> >
>> > 1
>> > How can I repair USB stick which is readable but not writable?
>> >
>> > question 2
>> > What did I do wrong to create this problem?
>>
>> You didn't tell us what you actually did, and especially which bits
>> you think might be a mistake, so it's very difficult for us to answer
>> this question.
>>
>> For example, you might have hit them with a hammer, or connected them
>> to the wrong voltages, or washed them in a bath, or who knows what? Or
>> you might have plugged them in correctly but used some sequence of
>> commands that has caused a problem. But until you tell us what you
>> did, we can't know which bit was wrong!
>>
>
> I mentioned probably the simplest thing: failing to unmount before
> removal on a Windows machine. This sometimes causes problems which
> cause Linux to refuse to mount the device read/write. Windows can
> usually fix it, though I suppose there may be data loss. It's entirely
> possible that doing the same thing on Linux would sometimes cause
> similar problems.


Been there a couple times on a new secondhand hard drive this year.
Following tips regarding hiberfil.sys fixed it both times for me, but
the method comes with a harsh "this is your last ditch option" warning
about things like that data loss.

That's on a non-Linux system, by the way. Linux triggered the second
episode while while the affected partition was mounted only as a
resource for backing up images. It wasn't mounted as an operating
system.

There's a recovery partition that keeps getting mounted even though
I'm not touching it this week. I can't help wondering if that plays
some part in how that partition ended up locked down when it wasn't
used as the primary operating system..

Cindy :)
--
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

AW: Topic: Problems with USB Sticks

[Schwibinger Michael]

Hello Joe. Hello group.
Thank you so much for your Emails.

How can I make an USB stick only readable but not writable?
How can I make an USB stick which is only readable again writable?


Thank you.


Regards,
Sophie



Von: Joe 
Gesendet: Freitag, 30. Dezember 2022 21:49
An: debian-user@lists.debian.org 
Betreff: Re: Topic: Problems with USB Sticks

On Fri, 30 Dec 2022 21:16:31 +
debian-u...@howorth.org.uk wrote:

> > Hello group. Hello Joe.
> > Thank you for your Email.
> >
> > Sorry, I did bad asking.
> > So I split the question.
> >
> > 1
> > How can I repair USB stick which is readable but not writable?
> >
> > question 2
> > What did I do wrong to create this problem?
>
> You didn't tell us what you actually did, and especially which bits
> you think might be a mistake, so it's very difficult for us to answer
> this question.
>
> For example, you might have hit them with a hammer, or connected them
> to the wrong voltages, or washed them in a bath, or who knows what? Or
> you might have plugged them in correctly but used some sequence of
> commands that has caused a problem. But until you tell us what you
> did, we can't know which bit was wrong!
>

I mentioned probably the simplest thing: failing to unmount before
removal on a Windows machine. This sometimes causes problems which
cause Linux to refuse to mount the device read/write. Windows can
usually fix it, though I suppose there may be data loss. It's entirely
possible that doing the same thing on Linux would sometimes cause
similar problems.

--
Joe

AW: Topic: Problems with USB Sticks

[Schwibinger Michael]

Hello Joe. Hello group.
Thank you for your Email.

We have about 10 or 20 USB sticks, and nearly every day everything is working 
fine.
But now we have 1 stick which is not accepted.
We could find out, you can read files, but you cannot write on the stick and 
you cannot destroy on the stick.

How can we make this stick writable again?


Thank you.


Regards,
Sophie




Von: debian-u...@howorth.org.uk 
Gesendet: Freitag, 30. Dezember 2022 21:16
An: debian-user@lists.debian.org 
Betreff: Re: Topic: Problems with USB Sticks

> Hello group. Hello Joe.
> Thank you for your Email.
>
> Sorry, I did bad asking.
> So I split the question.
>
> 1
> How can I repair USB stick which is readable but not writable?
>
> question 2
> What did I do wrong to create this problem?

You didn't tell us what you actually did, and especially which bits you
think might be a mistake, so it's very difficult for us to answer this
question.

For example, you might have hit them with a hammer, or connected them
to the wrong voltages, or washed them in a bath, or who knows what? Or
you might have plugged them in correctly but used some sequence of
commands that has caused a problem. But until you tell us what you did,
we can't know which bit was wrong!

> Thank you.
>
> Regards,
> Sophie

Re: Problems with host sleeping

[Ximo]

Hi,

Did you checked the hardware?

Best regards,

El 10/01/2023 a las 22:44, Tom Browder escribió:
I just got a new PC and installed Deb 11 (nonfree) and cannot figure out 
how to keep it from powering down after some delay.


For instance, when in the middle of the install process I had to leave 
for "honey dos" and, when I returned, the computer was powered down. 
When I powered on again, I got an unexpected grub shell.


I have to leave for a the evening, but the CPU is AMD, ASUS motherboard, 
Corsair case. The build was from Silent PC. Details to follow, but I 
don't remember ever seeing that behavior before. it sure makes it hard 
to do an install in pieces.


Best regards,

-Tom

Problems with host sleeping

[Tom Browder]

I just got a new PC and installed Deb 11 (nonfree) and cannot figure out
how to keep it from powering down after some delay.

For instance, when in the middle of the install process I had to leave for
"honey dos" and, when I returned, the computer was powered down. When I
powered on again, I got an unexpected grub shell.

I have to leave for a the evening, but the CPU is AMD, ASUS motherboard,
Corsair case. The build was from Silent PC. Details to follow, but I don't
remember ever seeing that behavior before. it sure makes it hard to do an
install in pieces.

Best regards,

-Tom

Re: Topic: Problems with USB Sticks

[Cindy Sue Causey]

On 12/30/22, Joe  wrote:
> On Fri, 30 Dec 2022 21:16:31 +
> debian-u...@howorth.org.uk wrote:
>> >
>> > 1
>> > How can I repair USB stick which is readable but not writable?
>> >
>> > question 2
>> > What did I do wrong to create this problem?
>>
>> You didn't tell us what you actually did, and especially which bits
>> you think might be a mistake, so it's very difficult for us to answer
>> this question.
>>
>> For example, you might have hit them with a hammer, or connected them
>> to the wrong voltages, or washed them in a bath, or who knows what? Or
>> you might have plugged them in correctly but used some sequence of
>> commands that has caused a problem. But until you tell us what you
>> did, we can't know which bit was wrong!
>>
>
> I mentioned probably the simplest thing: failing to unmount before
> removal on a Windows machine. This sometimes causes problems which
> cause Linux to refuse to mount the device read/write. Windows can
> usually fix it, though I suppose there may be data loss. It's entirely
> possible that doing the same thing on Linux would sometimes cause
> similar problems.


Been there a couple times on a new secondhand hard drive this year.
Following tips regarding hiberfil.sys fixed it both times for me, but
the method comes with a harsh "this is your last ditch option" warning
about things like that data loss.

That's on a non-Linux system, by the way. Linux triggered the second
episode while while the affected partition was mounted only as a
resource for backing up images. It wasn't mounted as an operating
system.

There's a recovery partition that keeps getting mounted even though
I'm not touching it this week. I can't help wondering if that plays
some part in how that partition ended up locked down when it wasn't
used as the primary operating system..

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: Topic: Problems with USB Sticks

[Joe]

On Fri, 30 Dec 2022 21:16:31 +
debian-u...@howorth.org.uk wrote:

> > Hello group. Hello Joe.
> > Thank you for your Email.
> > 
> > Sorry, I did bad asking.
> > So I split the question.
> > 
> > 1
> > How can I repair USB stick which is readable but not writable?
> > 
> > question 2
> > What did I do wrong to create this problem?  
> 
> You didn't tell us what you actually did, and especially which bits
> you think might be a mistake, so it's very difficult for us to answer
> this question.
> 
> For example, you might have hit them with a hammer, or connected them
> to the wrong voltages, or washed them in a bath, or who knows what? Or
> you might have plugged them in correctly but used some sequence of
> commands that has caused a problem. But until you tell us what you
> did, we can't know which bit was wrong!
>  

I mentioned probably the simplest thing: failing to unmount before
removal on a Windows machine. This sometimes causes problems which
cause Linux to refuse to mount the device read/write. Windows can
usually fix it, though I suppose there may be data loss. It's entirely
possible that doing the same thing on Linux would sometimes cause
similar problems.

-- 
Joe

Re: Topic: Problems with USB Sticks

[debian-user]

> Hello group. Hello Joe.
> Thank you for your Email.
> 
> Sorry, I did bad asking.
> So I split the question.
> 
> 1
> How can I repair USB stick which is readable but not writable?
> 
> question 2
> What did I do wrong to create this problem?

You didn't tell us what you actually did, and especially which bits you
think might be a mistake, so it's very difficult for us to answer this
question.

For example, you might have hit them with a hammer, or connected them
to the wrong voltages, or washed them in a bath, or who knows what? Or
you might have plugged them in correctly but used some sequence of
commands that has caused a problem. But until you tell us what you did,
we can't know which bit was wrong!
 
> Thank you.
> 
> Regards,
> Sophie

AW: Topic: Problems with USB Sticks

[Schwibinger Michael]

Hello group. Hello Joe.
Thank you for your Email.

Sorry, I did bad asking.
So I split the question.

1
How can I repair USB stick which is readable but not writable?

question 2
What did I do wrong to create this problem?


Thank you.

Regards,
Sophie

Von: Joe 
Gesendet: Sonntag, 27. November 2022 16:05
An: debian-user@lists.debian.org 
Betreff: Re: Topic: Problems with USB Sticks

On Sun, 27 Nov 2022 13:38:21 +
Schwibinger Michael  wrote:

> Topic: Problems with USB Sticks
>
>
> Good Morning.
> We have about 20 USB Sticks. But we have trouble with some.
> I think we made mistakes.
> The easy problem, one stick is only readable. How can we make ist
> with Linux in terminal writable? If this is not possible, then how
> can we make the stick clean and use for write and read?
>
> Bigger problem:
> some sticks are not accepted by computer.
> Some are lights up, but terminal is not recognizing them.
> Others, there is no reaction bei putting in.
> Are they totally destroyed?
>
>
The first thing to try is, in a terminal:

sudo tail -f /var/log/syslog

(stop this listing using ctrl-C when you're finished)

 then look at the output when you plug in a stick. The messages will
 vary a bit, but you are basically looking for

a) many lines of output
b) that a USB device is recognised
c: that it is allocated a drive designation e.g. sdd
d) that any partitions are listed as e.g. sdd1, sdd2 etc.

The first three items are essential for the stick to work. If they
don't happen, something is broken. If the first two do not happen, the
stick is probably permanently broken. There may not be any partitions
on the stick, many sticks are formatted as one memory range, and do not
even have a partition table.

This should allow you to see which of your sticks are completely
destroyed, and which may be recoverable. There have been USB sticks
with a tiny read-only switch fitted, but I haven't seen one like that
for many years. If not, your read-only device may have a filesystem too
corrupt for the software to risk writing to. Also, Windows seems to be
able to leave sticks in this state if they were not properly unmounted.
If that is likely to have happened, it's possible that Windows can fix
it without reformatting.

Assuming a stick has been given a drive name, then fdisk should work on
it, and should show the size, any partitions and other data. fsck
should also work and show any filesystem corruption. fsck can probably
fix some of these sticks, though there will have been data loss due to
the corruption. If fsck shows errors but cannot fix them, it's time to
reformat the device, and no data will be recoverable.

Any stick which has been given a drive designation, and been formatted,
and still doesn't work properly is probably broken beyond repair.

--
Joe

Re: GPG problems

[Alain D D Williams]

On Sun, Dec 04, 2022 at 04:28:00PM +0200, Teemu Likonen wrote:
> * 2022-12-04 12:05:56+, Alain D. D. Williams wrote:
> 
> > Part of the problem is the hopeless message "Server indicated a
> > failure" which says little. Any idea how I could get something more
> > informative ?
> 
> You can change debug logging level. Edit ~/.gnupg/dirmngr.conf file and
> write something like this:
> 
> debug-level expert  #or: guru
> log-file /tmp/dirmngr-log.txt
> 
> Then kill dirmngr
> 
> $ gpgconf --kill dirmngr
> 
> and try key servers again. See the log file mentioned above.

Thanks ... it does not really help (I attach it).
The message is:

command 'KS_PUT' failed: Server indicated a failure 

I ran it with debugging on the Debian 11 machine where it works.

I put the PIv4 address for keys.openpgp.org into /etc/hosts - the Debian 10
machine has IPv6 that works, the Debian 11 machine is IPv4 only. No change.

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT 
Lecturer.
+44 (0) 787 668 0256  https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: 
https://www.phcomp.co.uk/Contact.html
#include 
2022-12-04 17:44:27 dirmngr[18851.0] permanently loaded certificates: 138
2022-12-04 17:44:27 dirmngr[18851.0] runtime cached certificates: 0
2022-12-04 17:44:27 dirmngr[18851.0]trusted certificates: 138 
(137,0,0,1)
2022-12-04 17:44:27 dirmngr[18851.6] handler for fd 6 started
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> # Home: /home/addw/.gnupg
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> # Config: 
/home/addw/.gnupg/dirmngr.conf
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> OK Dirmngr 2.2.27 at your 
service
2022-12-04 17:44:27 dirmngr[18851.6] connection from process 18850 (1000:1000)
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- GETINFO version
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> D 2.2.27
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> OK
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- KEYSERVER
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> S KEYSERVER 
hkps://keys.openpgp.org
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> OK
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- KS_PUT
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> INQUIRE KEYBLOCK
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- [ 44 20 98 33 04 60 ec 50 
1f 16 09 2b 06 01 04 01 ...(626 byte(s) skipped) ]
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- END
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> INQUIRE KEYBLOCK_INFO
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- D 
pub::256:22:BA366B977C06BAF7:1626099743:::%0Afpr:4D48D5BAF3736D50214AFC3FBA366B977C06BAF7:%0Auid:1626099743Alain
 D D Williams :::%0Auid:1670002234Alain D D 
Williams 
:::%0Asub::256:18:0315E84A964E21C9:1626099743:::%0Afpr:75F7570849B82972171A762C0315E84A964E21C9:%0A
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- END
2022-12-04 17:44:27 dirmngr[18851.6] command 'KS_PUT' failed: Server indicated 
a failure 
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> ERR 219 Server indicated a 
failure 
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 <- BYE
2022-12-04 17:44:27 dirmngr[18851.6] DBG: chan_6 -> OK closing connection
2022-12-04 17:44:27 dirmngr[18851.6] handler for fd 6 terminated
2022-12-04 17:55:27 dirmngr[18851.0] running scheduled tasks
2022-12-04 18:05:28 dirmngr[18851.0] running scheduled tasks
2022-12-04 18:15:28 dirmngr[18851.0] running scheduled tasks
2022-12-04 18:25:29 dirmngr[18851.0] running scheduled tasks
2022-12-04 18:33:58 dirmngr[18851.6] handler for fd 6 started
2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 -> # Home: /home/addw/.gnupg
2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 -> # Config: 
/home/addw/.gnupg/dirmngr.conf
2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 -> OK Dirmngr 2.2.27 at your 
service
2022-12-04 18:33:58 dirmngr[18851.6] connection from process 22347 (1000:1000)
2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 <- KILLDIRMNGR
2022-12-04 18:33:58 dirmngr[18851.6] DBG: chan_6 -> OK closing connection
2022-12-04 18:36:18 dirmngr[22361.0] permanently loaded certificates: 138
2022-12-04 18:36:18 dirmngr[22361.0] runtime cached certificates: 0
2022-12-04 18:36:18 dirmngr[22361.0]trusted certificates: 138 
(137,0,0,1)
2022-12-04 18:36:18 dirmngr[22361.6] handler for fd 6 started
2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 -> # Home: /home/addw/.gnupg
2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 -> # Config: 
/home/addw/.gnupg/dirmngr.conf
2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 -> OK Dirmngr 2.2.27 at your 
service
2022-12-04 18:36:18 dirmngr[22361.6] connection from process 22360 (1000:1000)
2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 <- GETINFO version
2022-12-04 18:36:18 dirmngr[22361.6] DBG: chan_6 -> D 2.2.27
2022-12-04 18:36:18 dirmngr[22361.6] 

Re: GPG problems

[Teemu Likonen]

* 2022-12-04 12:05:56+, Alain D. D. Williams wrote:

> Part of the problem is the hopeless message "Server indicated a
> failure" which says little. Any idea how I could get something more
> informative ?

You can change debug logging level. Edit ~/.gnupg/dirmngr.conf file and
write something like this:

debug-level expert  #or: guru
log-file /tmp/dirmngr-log.txt

Then kill dirmngr

$ gpgconf --kill dirmngr

and try key servers again. See the log file mentioned above.

-- 
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462


signature.asc
Description: PGP signature

Re: GPG problems

[Alain D D Williams]

On Sat, Dec 03, 2022 at 02:59:41PM -0500, Jeffrey Walton wrote:

> keys.openpgp.org should be operational. It responds to ping.
> 
> Also have a look at
> https://lists.gnupg.org/pipermail/gnupg-users/2021-June/065261.html .

No, that is not the issue. It works on Debian 11 but not Debian 10, both
attempts within a few minutes of each other, both connect to 
hkps://keys.openpgp.org

Both run the same version of gpg (GnuPG) 2.2.27
(I installed from backports on Debian 10)

gpg reports the version of libgcrypt On Debian 10 it is 1.8.4 on Debian 11 it
is 1.8.8 Could that be an issue ? I am reluctant to speculatively upgrade for
fear of breaking something else.

Part of the problem is the hopeless message "Server indicated a failure" which
says little. Any idea how I could get something more informative ?

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT 
Lecturer.
+44 (0) 787 668 0256  https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: 
https://www.phcomp.co.uk/Contact.html
#include 

Re: GPG problems

[Jeffrey Walton]

On Sat, Dec 3, 2022 at 12:42 PM Alain D D Williams  wrote:
>
> I am running Debian 10 (buster). I generated a new key that I wanted to 
> upload,
> but it fails:
>
> $ gpg --send-keys  0xBA366B977C06BAF7
> gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org
> gpg: keyserver send failed: Server indicated a failure
> gpg: keyserver send failed: Server indicated a failure
>
> I copied my ~/.gnupg to a Debian 11 (bullesys) machine, it works:
>
> $ gpg --send-keys  0xBA366B977C06BAF7
> gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org
> $
>
> Back on buster I grabbed the latest version:
> /etc/apt/sources.list:
> deb http://deb.debian.org/debian/ buster-backports main contrib 
> non-free
> # apt -V -t=buster-backports install gpg
>
> I killed the dirmngr daemon:
>
> # killall dirmngr
>
> I tried the send-keys again and got the same result, ie failure.
>
> Please: what should I do to fix this.

keys.openpgp.org should be operational. It responds to ping.

Also have a look at
https://lists.gnupg.org/pipermail/gnupg-users/2021-June/065261.html .

Jeff

GPG problems

[Alain D D Williams]

I am running Debian 10 (buster). I generated a new key that I wanted to upload,
but it fails:

$ gpg --send-keys  0xBA366B977C06BAF7
gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org
gpg: keyserver send failed: Server indicated a failure
gpg: keyserver send failed: Server indicated a failure

I copied my ~/.gnupg to a Debian 11 (bullesys) machine, it works:

$ gpg --send-keys  0xBA366B977C06BAF7
gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org
$ 

Back on buster I grabbed the latest version:
/etc/apt/sources.list:
deb http://deb.debian.org/debian/ buster-backports main contrib non-free
# apt -V -t=buster-backports install gpg

I killed the dirmngr daemon:

# killall dirmngr

I tried the send-keys again and got the same result, ie failure.

Please: what should I do to fix this.

Thanks in advance

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT 
Lecturer.
+44 (0) 787 668 0256  https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: 
https://www.phcomp.co.uk/Contact.html
#include 

Re: Topic: Problems with USB Sticks

[David]

On Mon, 28 Nov 2022 at 00:52, Schwibinger Michael  wrote:

> Good Morning.

Good morning Sophie,

If you find it easier to write in German than in English,
you can send your email questions to:
  debian-user-ger...@lists.debian.org

To join that mailing list, see here:
  https://lists.debian.org/debian-user-german/

If you prefer a different language, Debian has mailing
lists in many different languages.
You can find them all here:
  https://lists.debian.org/users.html

Re: Topic: Problems with USB Sticks

[Joe]

On Sun, 27 Nov 2022 13:38:21 +
Schwibinger Michael  wrote:

> Topic: Problems with USB Sticks
> 
> 
> Good Morning.
> We have about 20 USB Sticks. But we have trouble with some.
> I think we made mistakes.
> The easy problem, one stick is only readable. How can we make ist
> with Linux in terminal writable? If this is not possible, then how
> can we make the stick clean and use for write and read?
> 
> Bigger problem:
> some sticks are not accepted by computer.
> Some are lights up, but terminal is not recognizing them.
> Others, there is no reaction bei putting in.
> Are they totally destroyed?
> 
>
The first thing to try is, in a terminal:

sudo tail -f /var/log/syslog

(stop this listing using ctrl-C when you're finished)

 then look at the output when you plug in a stick. The messages will
 vary a bit, but you are basically looking for

a) many lines of output
b) that a USB device is recognised
c: that it is allocated a drive designation e.g. sdd
d) that any partitions are listed as e.g. sdd1, sdd2 etc.

The first three items are essential for the stick to work. If they
don't happen, something is broken. If the first two do not happen, the
stick is probably permanently broken. There may not be any partitions
on the stick, many sticks are formatted as one memory range, and do not
even have a partition table.

This should allow you to see which of your sticks are completely
destroyed, and which may be recoverable. There have been USB sticks
with a tiny read-only switch fitted, but I haven't seen one like that
for many years. If not, your read-only device may have a filesystem too
corrupt for the software to risk writing to. Also, Windows seems to be
able to leave sticks in this state if they were not properly unmounted.
If that is likely to have happened, it's possible that Windows can fix
it without reformatting.

Assuming a stick has been given a drive name, then fdisk should work on
it, and should show the size, any partitions and other data. fsck
should also work and show any filesystem corruption. fsck can probably
fix some of these sticks, though there will have been data loss due to
the corruption. If fsck shows errors but cannot fix them, it's time to
reformat the device, and no data will be recoverable.

Any stick which has been given a drive designation, and been formatted,
and still doesn't work properly is probably broken beyond repair.

-- 
Joe

Topic: Problems with USB Sticks

[Schwibinger Michael]

Topic: Problems with USB Sticks


Good Morning.
We have about 20 USB Sticks. But we have trouble with some.
I think we made mistakes.
The easy problem, one stick is only readable. How can we make ist with Linux in 
terminal writable?
If this is not possible, then how can we make the stick clean and use for write 
and read?

Bigger problem:
some sticks are not accepted by computer.
Some are lights up, but terminal is not recognizing them.
Others, there is no reaction bei putting in.
Are they totally destroyed?


Thank you.

Regards,
Sophie

Re: Problems with gv after upgrade

[Rodolfo Medina]

Charles Curley  writes:

> On Mon, 21 Nov 2022 16:40:53 +
> Rodolfo Medina  wrote:
>
>> My PS file is regularly read by evince, simply with
>> 
>>  $ evince file.ps
>> 
>> Instead, with gv, as I always did before:
>> 
>>  $ gv file.ps
>> 
>> the application starts but the file won't open
>
> Not enough. Show us *exactly* what you typed and the results.
> Paths, if any, and all. Everything. Start with the command prompt, and
> copy and paste to the next command prompt.
>
> E.g.:
>
> charles@hawk:~$ gv
> /home/charles/versioned/bare.metal/Linux-Complete-Backup-and-Recovery-HOWTO.ps
> & [1] 862194 charles@hawk:~$ [1]+ Done gv
> /home/charles/versioned/bare.metal/Linux-Complete-Backup-and-Recovery-HOWTO.ps
> charles@hawk:~$
>
> And then report what you saw. In this case, I saw the document opened
> in gv, and saw no errors in it.

Thanks.  But before I go on, it seems to be a known bug:

 https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=gv;dist=unstable

Can we hope it will be soon fixed?  (It also seems that the last gv release is
from 2013)

Rodolfo

Re: Problems with gv after upgrade

[Charles Curley]

On Mon, 21 Nov 2022 16:40:53 +
Rodolfo Medina  wrote:

> My PS file is regularly read by evince, simply with
> 
>  $ evince file.ps
> 
> Instead, with gv, as I always did before:
> 
>  $ gv file.ps
> 
> the application starts but the file won't open

Not enough. Show us *exactly* what you typed and the results.
Paths, if any, and all. Everything. Start with the command prompt, and
copy and paste to the next command prompt.

E.g.:

charles@hawk:~$ gv 
/home/charles/versioned/bare.metal/Linux-Complete-Backup-and-Recovery-HOWTO.ps &
[1] 862194
charles@hawk:~$ 
[1]+  Donegv 
/home/charles/versioned/bare.metal/Linux-Complete-Backup-and-Recovery-HOWTO.ps
charles@hawk:~$ 

And then report what you saw. In this case, I saw the document opened
in gv, and saw no errors in it.


-- 
Does anybody read signatures any more?

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

Re: Problems with gv after upgrade

[Rodolfo Medina]

Celejar  writes:

> On Mon, 21 Nov 2022 09:06:16 +
> Rodolfo Medina  wrote:
>
>> After upgrading to Unstable, gv does not read my PS files any more.  I
>> couldn't
>> find any help in Internet.  Please help, thanks in advance.
>
> You can do better than this - what command did you use? What error did
> you get?


My PS file is regularly read by evince, simply with

 $ evince file.ps

Instead, with gv, as I always did before:

 $ gv file.ps

the application starts but the file won't open: the same with

 $ flpsed file.ps

Either the printer won't work since upgrading: is it related?

Thanks,

Rodolfo

Re: Problems with gv after upgrade

[Celejar]

On Mon, 21 Nov 2022 09:06:16 +
Rodolfo Medina  wrote:

> Hi all.
> 
> After upgrading to Unstable, gv does not read my PS files any more.  I 
> couldn't
> find any help in Internet.  Please help, thanks in advance.

You can do better than this - what command did you use? What error did
you get?

> Rodolfo

-- 
Celejar