Browsers crashing in Bullseye armhf

[Bruce Kerr]

Hi, I have both Chromium and Epiphany browsers crashing randomly in
Bullseye running on Acer A500 tegra 2 tablet with kerenl 5.8.3.

The version of Chromium on bullseye is 83.

I also have Buster with Chromium 79 and same kernel and all works fine,
including epiphany.

I suspect it is a common lib used by both but dont have a clue where to
start, I havent coded for over 10 years and even longer on linux so would
appreciate a headsup on where to start?

Thanks
Bruce

Re: What to choose for Core i5 64 bits?

[deloptes]

Contmultipart/mixed;
boundary="Add_By_Label_Mail_Nextpart_001"
X-Complaints-To: use...@dough.gmane.org
X-Gmane-NNTP-Posting-Host: chello062178025100.9.11.vie.surfer.at
User-Agent: KNode/0.10.9
X-Rc-Virus: 2007-09-13_01
X-Rc-Spam: 2008-11-04_01
Resent-Message-ID: 
Resent-From: debian-user@lists.debian.org
X-Mailing-List:  archive/latest/576674
X-Loop: debian-user@lists.debian.org
List-Id: 
List-Post: 
List-Help: 
List-Subscribe: 
List-Unsubscribe: 

Precedence: list
Resent-Sender: debian-user-requ...@lists.debian.org
Resent-Date: Thu, 13 May 2010 09:17:25 + (UTC)

Aaron Toponce wrote:

> To eac
--Add_By_Label_Mail_Nextpart_001
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit

h their own. I for one want to get my money out of my hardware. If
> you don't want a 64-bit system, then why did you pay for it?

I can witness exactly what you've written after migrating to 64bit kernel
and os. It's faster and safer on the same machine with 2GB RAM.

thanks for the argumentation


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/hsgg29$npg$1...@dough.gmane.org

Re: /sbin -> usr/sbin

[Charles Plessy]

Le Sat, Jul 11, 2020 at 12:10:07AM +0200, BERTRAND Joël a écrit :
> 
>   Je viens d'installer une debian/testing toute fraîche sur un portable
> Toshiba et j'ai été surpris de trouver dans / des liens vers /usr :

Bonjour Bertrand,

c'est dans les notes de publication:

https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.fr.html#merged-usr

Bonne fin de semaine,

Charles

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Akano, Uruma, Okinawa, Japan

Re: /sbin -> usr/sbin

[l0f4r0]

Bonjour,

11 juil. 2020 à 00:10 de joel.bertr...@systella.fr:

>  Quel est l'intérêt d'une telle chose ? Normalement, un système doit
> pouvoir booter avec un / minimal et n'a pas besoin de /usr. Cela
> signifie même que ce système ne serait plus bootable si /usr était sur
> une partition séparée (mount est dans /usr/bin/ alors que dans une
> installation plus ancienne, il est dans /bin qui n'est pas un lien vers
> /usr/bin).
>
>  J'avoue que je ne saisis pas le pourquoi du comment de ce mélange. Je
> suis donc preneur de toute explication.
>
C'est normal, il s'agit d'une nouveauté depuis Buster :

* 
https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-new.fr.html
(cf. "/usr fusionné pour les nouvelles installations")

* https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/(en 
anglais)

Bonne fin de soirée !
l0f4r0

Re: /sbin -> usr/sbin

[etienne . mollier]

Bonjour Joël,

BERTRAND Joël, on 2020-07-11 00:10:07 +0200:
>   Je viens d'installer une debian/testing toute fraîche sur un portable
> Toshiba et j'ai été surpris de trouver dans / des liens vers /usr :

Ce comportement provient du paquet "usrmerge" dont quelques
détails sont accessibles depuis le wiki:

https://wiki.debian.org/UsrMerge

En Debian Testing, debootstrap va installer usrmerge par défaut.
Je ne sais pas si ce comportement est réglable dans les images
ISO alpha, mais je crois que ces approches devraient être
possibles:

  - en partant de Debian Buster, faire une upgrade vers bullseye
en spécifiant éventuellement "usrmerge-" pour être sûr que
le paquet ne va pas s'installer,

  - ou alors effectuer une installation manuelle de Debian
testing via debootstrap avec l'option qui va bien:

# debootstrap --no-merged-usr bullseye /mnt/target/

>   Quel est l'intérêt d'une telle chose ? Normalement, un système doit
> pouvoir booter avec un / minimal et n'a pas besoin de /usr. Cela
> signifie même que ce système ne serait plus bootable si /usr était sur
> une partition séparée (mount est dans /usr/bin/ alors que dans une
> installation plus ancienne, il est dans /bin qui n'est pas un lien vers
> /usr/bin).
> 
>   J'avoue que je ne saisis pas le pourquoi du comment de ce mélange. Je
> suis donc preneur de toute explication.

Je ne suis pas allé regarder en détail (il y a de la lecture),
mais les liens suivants (en anglais) devraient vous fournir des
éléments de réponse, si ça peut éclairer votre lanterne:

https://lists.debian.org/debian-devel/2018/11/msg00374.html
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/

En survolant ces deux pages, de ce que je comprends, ça permet
avant tout d'améliorer l'intéropérabilité entre les divers
Unices qui se sont multipliés dans la nature.

Amicalement,
-- 
Étienne Mollier 
Old rsa/3072: 5ab1 4edf 63bb ccff 8b54  2fa9 59da 56fe fff3 882d
New rsa/4096: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/6, please excuse my verbosity.


signature.asc
Description: PGP signature

Chamada de atividades para Debian Day Brasil 2020 onlne

[Paulo Henrique de Lima Santana]

Olá,

Este ano a Comunidade Debian Brasil promoverá um evento online durante
dois dias para celebrar o 27º aniversário do Projeto Debian. O Debian
Day Brasil 2020 online acontecerá nos dias 15 e 16 agosto e será
transmitido pelo canal Debian Brasil no YouTube.

Estamos com uma chamada de atividades aberta para receber propostas da
comunidade. Você pode enviar propostas de atividades relacionadas ao
Debian até às 23:59 do dia 26 de julho de 2020.

Teremos 3 tipos de atividades.

* Palestras longas: palestra expositiva, com tempo de 50 minutos de
duração, incluindo o tempo para responder perguntas.
* Palestras curtas: palestra expositiva, com tempo de 20 minutos de
duração, incluindo o tempo para responder perguntas.
* Oficina: atividade para mão na massa, com duração a definir.

Para enviar sua proposta, acesse o formulário abaixo:

https://form.curitibalivre.org.br/index.php/329429

Abraços,

-- 
Paulo Henrique de Lima Santana (phls)
Curitiba - Brasil
Debian Developer
Diretor do Instituto para Conservação de Tecnologias Livres
Site: http://www.phls.com.br
GNU/Linux user: 228719  GPG ID: 0443C450



signature.asc
Description: OpenPGP digital signature

Re: Logitech C310 rule in /etc/udev/rules.d/25-webcam.rules?

[Dan Ritter]

John Conover wrote: 
> udevadm info -a -p $(udevadm info -q path -n /dev/video0):
> 
>   looking at device 
> '//devices/pci:00/:00:1a.7/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1.4/1-1.4.1.4:1.0/video4linux/video0':
> KERNEL=="video0"
> SUBSYSTEM=="video4linux"
> DRIVER==""
> ATTR{index}=="0"
> ATTR{dev_debug}=="0"
> ATTR{name}=="UVC Camera (046d:081b)"
> 
> /etc/udev/rules.d/25-webcam.rules:
> 
> KERNEL=="video[0-9]*", \
> SUBSYSTEM=="video4linux", \
> SUBSYSTEMS=="usb", \
> ATTRS{idVendor}=="046d", \
> ATTRS{idProduct}=="081b", \
> SYMLINK+="video-webcam"
> 
> erratically fails, with /dev/video-webcam ln -s to /dev/video0, and
> the camera on /dev/video1, (after PNP.)
> 
> Is "SUBSYSTEMS=="usb"" the issue in the rule?


 SUBSYSTEM
   Match the subsystem of the event device.

 SUBSYSTEMS
   Search the devpath upwards for a matching device subsystem name.

I've seen lots of rules use SUBSYSTEM and none use SUBSYSTEMS. 

I don't think you need to specify KERNEL, either. Just let the
SYMLINK+= create the /dev/video-webcam for you.

-dsr-

/sbin -> usr/sbin

[BERTRAND Joël]

Bonjour à tous,

Je viens d'installer une debian/testing toute fraîche sur un portable
Toshiba et j'ai été surpris de trouver dans / des liens vers /usr :

danielle@nietzsche:/$ ls -al | grep ^l
lrwxrwxrwx   1 root root 7 juil. 10 14:20 bin -> usr/bin
lrwxrwxrwx   1 root root29 juil. 10 14:35 initrd.img ->
boot/initrd.img-5.7.0-1-amd64
lrwxrwxrwx   1 root root29 juil. 10 14:25 initrd.img.old ->
boot/initrd.img-5.6.0-2-amd64
lrwxrwxrwx   1 root root 7 juil. 10 14:20 lib -> usr/lib
lrwxrwxrwx   1 root root 9 juil. 10 14:20 lib32 -> usr/lib32
lrwxrwxrwx   1 root root 9 juil. 10 14:20 lib64 -> usr/lib64
lrwxrwxrwx   1 root root10 juil. 10 14:20 libx32 -> usr/libx32
lrwxrwxrwx   1 root root 8 juil. 10 14:20 sbin -> usr/sbin
lrwxrwxrwx   1 root root26 juil. 10 14:35 vmlinuz ->
boot/vmlinuz-5.7.0-1-amd64
lrwxrwxrwx   1 root root26 juil. 10 14:25 vmlinuz.old ->
boot/vmlinuz-5.6.0-2-amd64
danielle@nietzsche:/$

Quel est l'intérêt d'une telle chose ? Normalement, un système doit
pouvoir booter avec un / minimal et n'a pas besoin de /usr. Cela
signifie même que ce système ne serait plus bootable si /usr était sur
une partition séparée (mount est dans /usr/bin/ alors que dans une
installation plus ancienne, il est dans /bin qui n'est pas un lien vers
/usr/bin).

J'avoue que je ne saisis pas le pourquoi du comment de ce mélange. Je
suis donc preneur de toute explication.

Bien cordialement,

JKB

Logitech C310 rule in /etc/udev/rules.d/25-webcam.rules?

[John Conover]

udevadm info -a -p $(udevadm info -q path -n /dev/video0):

  looking at device 
'//devices/pci:00/:00:1a.7/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1.4/1-1.4.1.4:1.0/video4linux/video0':
KERNEL=="video0"
SUBSYSTEM=="video4linux"
DRIVER==""
ATTR{index}=="0"
ATTR{dev_debug}=="0"
ATTR{name}=="UVC Camera (046d:081b)"

/etc/udev/rules.d/25-webcam.rules:

KERNEL=="video[0-9]*", \
SUBSYSTEM=="video4linux", \
SUBSYSTEMS=="usb", \
ATTRS{idVendor}=="046d", \
ATTRS{idProduct}=="081b", \
SYMLINK+="video-webcam"

erratically fails, with /dev/video-webcam ln -s to /dev/video0, and
the camera on /dev/video1, (after PNP.)

Is "SUBSYSTEMS=="usb"" the issue in the rule?

Thanks,

John

-- 

John Conover, cono...@rahul.net, http://www.johncon.com/

Re: Buster boot messages

[Klaus Jantzen]

On 7/10/20 4:14 PM, Sven Hartge wrote:

Klaus Jantzen  wrote:

On 7/10/20 11:48 AM, Sven Hartge wrote:

Klaus Jantzen  wrote:

the first messages that appear on the screen during the boot process
seem to be messages from the BIOS;
they have a different format than the subsequent messages from buster
and they begin with 'ACPI  '.
As they disappear so fast, I cannot read them.
Where are these messages logged or what should I do to log these messages?

"journalctl -b" will have the messages from the most recent boot.

Thanks for the pointer.
These are the messages I was looking for:
=
AMD-Vi: Unable to write to IOMMU perf counter.
ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], 
AE_NOT_FOUND (201810/psargs-330)
ACPI Error: Method parse/execution failed \_SB.PCI0.GPP0.VGA.LCD._BCM, 
AE_NOT_FOUND (20180810/psparse-516)
ACPI Error: Evaluating _BCM failed (20180810/video-370)
Failed to start Show Plymouth Boot Screen.
==
Do I have a problem with my system?

No. The ACPI tables in PCs are usually shoddy and produce many warnings
by the strict parser in the Kernel.

Windows also often experiences the same parse errors, but decides to
hide them deep in the Event Log.

Both operations system work around the these errors, anticipating the
bad craftsmanship of the mainboard/system manufacturers.

Unless you have very specific problems which you explicitly can link to
such errors, I would not worry.

Sometimes a BIOS/Firmware update fixes some errors, but don't get your
hopes up.

Grüße
Sven.


Thank you. That was helpful.

--

K.D.J.

Re: off-topic - assunto thunderbird

[Jack Jr.]

No meu Thunderbird também não aparece o campo "assunto". A diferença é 
que não aparece para remover (como está lá, não tem como retirar).


Todos os outros campos aparecem. Realmente o campo assunto sumiu ali das 
opções de habiliar/desabilitar.



Jack Pogorelsky Jr.
Engenheiro Mecânico
Tel/WhatsApp: +55 (51) 982017877
E-mail: j...@sulmail.com
Website: sulmail.com/pogorelsky

Em 10/07/2020 11:35, Vitor Hugo escreveu:

Bom dia;

Não funcionou, simplesmente sumiu o campo "Assunto" do menu, acredito 
que seja problema na compilação ou bug do software.


Em 10/07/2020 11:26, Fabio Augusto De Muzio Tobich escreveu:

Bom dia,

Vitor, aqui [1] tem uma situação que parece ser similar a sua, não 
conseguiram
resolver o problema mas encontraram uma alternativa para trazer a 
coluna de

volta, veja se isto te ajuda:

   [1] https://bugzilla-dev.allizom.org/show_bug.cgi?id=1609391

Att.

Em 10/07/2020 10:45, Vitor Hugo escreveu:

https://ibb.co/NpmsJSs

Em 10/07/2020 10:28, henrique escreveu:
   Se você clicar na barra de colunas de campos, aparece uma lista 
de campos a serem exibidos/ocultos. Só escolher.


  Em quarta-feira, 8 de julho de 2020 07:55:28 BRT, Vitor Hugo 
 escreveu:

     Bom dia;

Faz algum tempo que o meu Mozilla Thunderbird não apresenta as 
mensagens

o campo assunto, existe algum lugar para ele ser ativado/desativado?

Re: /etc/default/grub doesn't exist, what to do?

[David Wright]

On Fri 10 Jul 2020 at 02:39:08 (-0400), Borden Rhodes wrote:
> > Please tell us the output of:
> > dpkg -l | grep -i grub
> 
> Sorry for missing this. Please see below:
> 
> # dpkg -l | grep -i grub
> ii grub-common 2.04-8 amd64
> ii grub-efi-amd64-bin 2.04-8 amd64
> ii grub-efi-amd64-signed 1+2.04+8 amd64
> rc grub-imageboot 0.6 all
> ii grub2-common 2.04-8 amd64

Mine:

ii grub-common 2.02+dfsg1-20
ii grub-efi-amd64 2.02+dfsg1-20
ii grub-efi-amd64-bin 2.02+dfsg1-20
ii grub-efi-amd64-signed 1+2.02+dfsg1+20
ii grub-rescue-pc 2.02+dfsg1-20
ii grub2-common 2.02+dfsg1-20

> > The package grub2-common has the file:
> > /usr/share/grub/default/grub
> > Which is the default /etc/default/grub file
> 
> Thank you for this. I figured there was such a template file but I didn't know
> where to look. It would be nice to have this added to
> https://wiki.debian.org/Grub so people know how to reconstruct a fresh
> template file if theirs gets destroyed (or, in my case, uninstalled)
> 
> > The actual package which creates /etc/default/grub in the d-i is
> > one of grub-pc and the packages it conflicts with, viz:
> > grub (<< 0.97-54), grub-coreboot, grub-efi-amd64, grub-efi-ia32,
> > grub-ieee1275, grub-legacy, grub-xen
> 
> So that might be the explanation. I removed grub-efi-amd64 to install
> grub-efi-amd64-signed. The latter doesn't appear to create its own
> /etc/default/grub file.
> 
> Is this a bug that I should report or is this by design?

It's a misunderstanding. You removed grub-efi-amd64 *in order to*
install grub-efi-amd64-signed. You would be asked why?

> > To find out which, either look at dpkg -l or type
> > $ grep -B2 'Creating config file /etc/def' /var/log/installer/syslog
> > if you're a member of group adm.
> 
> I think this file has long since been deleted. I think I installed Debian on
> this machine when I got it over 2 years ago.

Apr  4 01:17:15 in-target: Setting up efibootmgr (15-1) ...
Apr  4 01:17:15 in-target: Setting up mokutil (0.3.0+1538710437.fb6250f-1) ...
Apr  4 01:17:15 in-target: Setting up grub-efi-amd64-signed (1+2.02+dfsg1+20) 
...
Apr  4 01:17:15 in-target: Setting up grub2-common (2.02+dfsg1-20) ...
Apr  4 01:17:15 in-target: Setting up shim-signed-common 
(1.33+15+1533136590.3beb971-7) ...
Apr  4 01:17:15 in-target: No DKMS packages installed: not changing Secure Boot 
validation state.
Apr  4 01:17:15 in-target: Setting up grub-efi-amd64-bin (2.02+dfsg1-20) ...
Apr  4 01:17:16 in-target: Setting up shim-unsigned (15+1533136590.3beb971-7) 
...
Apr  4 01:17:16 in-target: Setting up grub-efi-amd64 (2.02+dfsg1-20) ...
Apr  4 01:17:16 in-target: 
Apr  4 01:17:16 in-target: Creating config file /etc/default/grub with new 
version
Apr  4 01:17:16 in-target: Setting up shim-helpers-amd64-signed 
(1+15+1533136590.3beb971+7) ...
Apr  4 01:17:16 in-target: Setting up shim-signed:amd64 
(1.33+15+1533136590.3beb971-7) ...
Apr  4 01:17:16 in-target: Processing triggers for man-db (2.8.5-2) ...
Apr  4 01:17:17 grub-installer: info: Additionally installing shim-signed to go 
with grub-efi-amd64

That's a longer extract to include more of the grub packages being
installed by d-i; amongst them grub-efi-amd64-signed as well as grub-efi-amd64.

Cheers,
David.

Re: X starting but nothing shows on the screen

[Tony Rowe]

On Mon, May 10, 2010 at 09:42:07PM +0200, Sven Joachim wrote:
> Contenmultipart/mixed;
>   boundary="Add_By_Label_Mail_Nextpart_001"-GMX-Trusted: 0
> X-Rc-Virus: 2007-09-13_01
> X-Rc-Spam: 2008-11-04_01
> Resent-Message-ID: 
> Resent-From: debian-user@lists.debian.org
> X-Mailing-List:  archive/latest/576438
> X-Loop: debian-user@lists.debian.org
> List-Id: 
> List-Post: 
> List-Help: 
> List-Subscribe: 
> 
> List-Unsubscribe: 
> 
> Precedence: list
> Resent-Sender: debian-user-requ...@lists.debian.org
> Resent-Date: Mon, 10 May 2010 19:42:20 + (UTC)
> 
> On 2010-05-08 12:42 +0200, Ólafur Je
> --Add_By_Label_Mail_Nextpart_001
> Content-Type: text/plain;
> Content-Transfer-Encoding: 8bit
> 
> ns Sigurðsson wrote:
> 
> > Hello, I have a strange problem.
[...]

You seem to be writing in 2010, or at least your mail is being 
sorted-by-date on my machine as though you were.

> 
> This is indeed very strange.

Yes. :)

Tony

> Sven

Re: X starting but nothing shows on the screen

[Nicholas Geovanis]

On Fri, Jul 10, 2020, 10:37 AM Sven Joachim  wrote:

> Contenmultipart/mixed;
> boundary="Add_By_Label_Mail_Nextpart_001"-GMX-Trusted: 0
> X-Rc-Virus: 2007-09-13_01
> X-Rc-Spam: 2008-11-04_01
> Resent-Message-ID: 
> Resent-From: debian-user@lists.debian.org
> X-Mailing-List:  archive/latest/576438
> X-Loop: debian-user@lists.debian.org
> List-Id: 
> List-Post: 
> List-Help: 
> List-Subscribe:  ?subject=subscribe>
> List-Unsubscribe:  ?subject=unsubscribe>
> Precedence: list
> Resent-Sender: debian-user-requ...@lists.debian.org
> Resent-Date: Mon, 10 May 2010 19:42:20 + (UTC)
>
> On 2010-05-08 12:42 +0200, Ólafur Je
> --Add_By_Label_Mail_Nextpart_001
> Content-Type: text/plain;
> Content-Transfer-Encoding: 8bit
>
> ns Sigurðsson wrote:
>
> > Hello, I have a strange problem.
> >
> > If X is started from gdm at bootup or with /etc/init.d/gdm start then
> > it starts (I know this since it beeps when it is up and running) but
> > nothing shows on the screen. The same thing happens when I use startx
> > and I have icewm in my .xinitrc. But if I have no .xinitrc file and I
> > use startx then Gnome comes up fine.
>
> This is indeed very strange.
>

This has happened to me a couple times in the past with Debian, and simply
turning up the display brightness showed everything normal. Strange indeed
;-)

Sven
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/87eihjr1bk@turtle.gmx.de
>
>
>

Re: X starting but nothing shows on the screen

[Sven Joachim]

Contenmultipart/mixed;
boundary="Add_By_Label_Mail_Nextpart_001"-GMX-Trusted: 0
X-Rc-Virus: 2007-09-13_01
X-Rc-Spam: 2008-11-04_01
Resent-Message-ID: 
Resent-From: debian-user@lists.debian.org
X-Mailing-List:  archive/latest/576438
X-Loop: debian-user@lists.debian.org
List-Id: 
List-Post: 
List-Help: 
List-Subscribe: 
List-Unsubscribe: 

Precedence: list
Resent-Sender: debian-user-requ...@lists.debian.org
Resent-Date: Mon, 10 May 2010 19:42:20 + (UTC)

On 2010-05-08 12:42 +0200, Ólafur Je
--Add_By_Label_Mail_Nextpart_001
Content-Type: text/plain;
Content-Transfer-Encoding: 8bit

ns Sigurðsson wrote:

> Hello, I have a strange problem.
>
> If X is started from gdm at bootup or with /etc/init.d/gdm start then
> it starts (I know this since it beeps when it is up and running) but
> nothing shows on the screen. The same thing happens when I use startx
> and I have icewm in my .xinitrc. But if I have no .xinitrc file and I
> use startx then Gnome comes up fine.

This is indeed very strange.

> I am using sid and have just made an upgrade to my system (I hadn't
> done a upgrade in quite a while and did an upgrade a few days ago then
> my problems started) so it is up to date.
>
> Any ideas on what could be wrong here?

No, but please show the kernel version, what graphics card you have and
your /etc/X11/xorg.conf if it exists.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87eihjr1bk@turtle.gmx.de

Re: off-topic - assunto thunderbird

[Vitor Hugo]

Bom dia;

Não funcionou, simplesmente sumiu o campo "Assunto" do menu, acredito 
que seja problema na compilação ou bug do software.


Em 10/07/2020 11:26, Fabio Augusto De Muzio Tobich escreveu:

Bom dia,

Vitor, aqui [1] tem uma situação que parece ser similar a sua, não conseguiram
resolver o problema mas encontraram uma alternativa para trazer a coluna de
volta, veja se isto te ajuda:

   [1] https://bugzilla-dev.allizom.org/show_bug.cgi?id=1609391

Att.

Em 10/07/2020 10:45, Vitor Hugo escreveu:

https://ibb.co/NpmsJSs

Em 10/07/2020 10:28, henrique escreveu:

   Se você clicar na barra de colunas de campos, aparece uma lista de campos a 
serem exibidos/ocultos. Só escolher.

  Em quarta-feira, 8 de julho de 2020 07:55:28 BRT, Vitor Hugo 
 escreveu:
     Bom dia;

Faz algum tempo que o meu Mozilla Thunderbird não apresenta as mensagens
o campo assunto, existe algum lugar para ele ser ativado/desativado?

Re: off-topic - assunto thunderbird

[Fabio Augusto De Muzio Tobich]

Bom dia,

Vitor, aqui [1] tem uma situação que parece ser similar a sua, não conseguiram
resolver o problema mas encontraram uma alternativa para trazer a coluna de
volta, veja se isto te ajuda:

  [1] https://bugzilla-dev.allizom.org/show_bug.cgi?id=1609391

Att.

Em 10/07/2020 10:45, Vitor Hugo escreveu:
> https://ibb.co/NpmsJSs
> 
> Em 10/07/2020 10:28, henrique escreveu:
>>   Se você clicar na barra de colunas de campos, aparece uma lista de campos 
>> a serem exibidos/ocultos. Só escolher.
>>
>>  Em quarta-feira, 8 de julho de 2020 07:55:28 BRT, Vitor Hugo 
>>  escreveu:
>>     Bom dia;
>>
>> Faz algum tempo que o meu Mozilla Thunderbird não apresenta as mensagens
>> o campo assunto, existe algum lugar para ele ser ativado/desativado?
>>
>>    
> 

-- 
⢀⣴⠾⠻⢶⣦⠀ Fabio A. De Muzio Tobich
⣾⠁⢰⠒⠀⣿⡁ 9730 4066 E5AE FAC2 2683
⢿⡄⠘⠷⠚⠋⠀ D03D 4FB3 B4D3 7EF6 3B2E
⠈⠳⣄  GPG:rsa4096/7EF63B2E

Re: Deluged setup instructions/help

[Intense Red]

> Checking the /etc/default/deluged file would be recommended as well.

   That just contains a switch to enable the daemon (already done to no 
effect).

> In case you (the OP) end up writing a .service file (system or user) to
> replace the init script kindly attach it to a wishlist bug for inclusion in
> the package

   Good idea! I'll submit such a wishlist 'bug' when I get a handle on this.

-- 
"War is peace, freedom is slavery, and ignorance is strength." -- George 
Orwell.

Re: off-topic - assunto thunderbird

[Vitor Hugo]

https://ibb.co/NpmsJSs

Em 10/07/2020 10:28, henrique escreveu:

  Se você clicar na barra de colunas de campos, aparece uma lista de campos a 
serem exibidos/ocultos. Só escolher.

 Em quarta-feira, 8 de julho de 2020 07:55:28 BRT, Vitor Hugo 
 escreveu:
  
  Bom dia;


Faz algum tempo que o meu Mozilla Thunderbird não apresenta as mensagens
o campo assunto, existe algum lugar para ele ser ativado/desativado?

   

Re: Buster boot messages

[Sven Hartge]

Klaus Jantzen  wrote:
> On 7/10/20 11:48 AM, Sven Hartge wrote:
>> Klaus Jantzen  wrote:

>>> the first messages that appear on the screen during the boot process
>>> seem to be messages from the BIOS;
>>> they have a different format than the subsequent messages from buster
>>> and they begin with 'ACPI  '.
>>> As they disappear so fast, I cannot read them.
>>> Where are these messages logged or what should I do to log these messages?

>> "journalctl -b" will have the messages from the most recent boot.

> Thanks for the pointer.

> These are the messages I was looking for:

> =

> AMD-Vi: Unable to write to IOMMU perf counter.

> ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], 
> AE_NOT_FOUND (201810/psargs-330)
> ACPI Error: Method parse/execution failed \_SB.PCI0.GPP0.VGA.LCD._BCM, 
> AE_NOT_FOUND (20180810/psparse-516)
> ACPI Error: Evaluating _BCM failed (20180810/video-370)

> Failed to start Show Plymouth Boot Screen.

> ==

> Do I have a problem with my system?

No. The ACPI tables in PCs are usually shoddy and produce many warnings
by the strict parser in the Kernel.

Windows also often experiences the same parse errors, but decides to
hide them deep in the Event Log.

Both operations system work around the these errors, anticipating the
bad craftsmanship of the mainboard/system manufacturers.

Unless you have very specific problems which you explicitly can link to
such errors, I would not worry.

Sometimes a BIOS/Firmware update fixes some errors, but don't get your
hopes up.

Grüße
Sven.

-- 
Sigmentation fault. Core dumped.

Re: off-topic - assunto thunderbird

[Vitor Hugo]

https://ibb.co/NpmsJSs

Em 10/07/2020 10:28, henrique escreveu:

  Se você clicar na barra de colunas de campos, aparece uma lista de campos a 
serem exibidos/ocultos. Só escolher.

 Em quarta-feira, 8 de julho de 2020 07:55:28 BRT, Vitor Hugo 
 escreveu:
  
  Bom dia;


Faz algum tempo que o meu Mozilla Thunderbird não apresenta as mensagens
o campo assunto, existe algum lugar para ele ser ativado/desativado?

   

Re: Buster boot messages

[Klaus Jantzen]

On 7/10/20 11:48 AM, Sven Hartge wrote:

Klaus Jantzen  wrote:


the first messages that appear on the screen during the boot process
seem to be messages from the BIOS;
they have a different format than the subsequent messages from buster
and they begin with 'ACPI  '.
As they disappear so fast, I cannot read them.
Where are these messages logged or what should I do to log these messages?

"journalctl -b" will have the messages from the most recent boot.

S!


Thanks for the pointer.

These are the messages I was looking for:

=

AMD-Vi: Unable to write to IOMMU perf counter.

ACPI BIOS Error (bug): Could not resolve 
[\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (201810/psargs-330)
ACPI Error: Method parse/execution failed \_SB.PCI0.GPP0.VGA.LCD._BCM, 
AE_NOT_FOUND (20180810/psparse-516)

ACPI Error: Evaluating _BCM failed (20180810/video-370)

Failed to start Show Plymouth Boot Screen.

==

Do I have a problem with my system?

--

K.D.J.

Re: Lost usb wifi device

[Gregory Sharp]

 On Wednesday, July 8, 2020, 08:38:54 PM EDT, Dan Ritter 
 wrote:
Gregory Sharp wrote:
> Hi all,
>
> My usb wifi connection has been working for two years, and it just stopped 
> and can't figure out why. This is on Debian testing. Help!
>

If you boot with a Debian stable live-USB or similar, does it work?

--
Yes, it seems to. I didn't go as far as to configure it to make it actually 
work, but it does show up when I type "ip link".
-Greg
  

Re: off-topic - assunto thunderbird

[henrique]

 Se você clicar na barra de colunas de campos, aparece uma lista de campos a 
serem exibidos/ocultos. Só escolher. 

Em quarta-feira, 8 de julho de 2020 07:55:28 BRT, Vitor Hugo 
 escreveu:  
 
 Bom dia;

Faz algum tempo que o meu Mozilla Thunderbird não apresenta as mensagens 
o campo assunto, existe algum lugar para ele ser ativado/desativado?

  

Re: Deluged setup instructions/help

[Intense Red]

>  may I ask whether there is anything about deluge/deluged in particular that
> makes you want to use it?

   My default is to use the transmission package but that has a documented bug 
in which some torrents cause an "invalid argument" error. 

> Or is it just the one you've used before, so you thought you'd stick
> to something familiar?

 I've used deluge a couple of Debian versions ago I thought I'd give that 
another try. However, it seems the documentation available online and/or the 
package's packaging isn't what I remember.

-- 
"Behind the ostensible government sits enthroned an invisible government owing 
no allegiance and acknowledging no responsibility to the people. To destroy 
this invisible government, to befoul this unholy alliance between corrupt 
business and corrupt politics is the first task of statesmanship." -- President 
Theodore Roosevelt.

Re: off-topic - assunto thunderbird

[Vitor Hugo]

Bom dia;

Não aparece o campo assunto no Thunderbird, estou pesquisando parece ser 
algum bug mas não encontro a solução, simplesmente o campo assunto das 
mensagens sumiram sem explicação o que dificulta muito ler os e-mails.


Em 09/07/2020 16:16, Jack Jr. escreveu:

A onde que não aparece o "assunto"? Nas respostas?

Jack Pogorelsky Jr.
Engenheiro Mecânico
Tel/WhatsApp: +55 (51) 982017877
E-mail: j...@sulmail.com
Website: sulmail.com/pogorelsky

Em 08/07/2020 07:22, Vitor Hugo escreveu:

Bom dia;

Faz algum tempo que o meu Mozilla Thunderbird não apresenta as 
mensagens o campo assunto, existe algum lugar para ele ser 
ativado/desativado?

Re: Using .XCompose

[davidson]

On Thu, 9 Jul 2020 davidson wrote:

I have conducted an experiment with the following ~/.XCompose file,
and tried to document it relatively thoroughly below.

[snip]


%% THREE XCOMPOSE RULES to test

$ cat ~/.XCompose
include "%L"
   : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) 
(U0D19)

   : "✄"  # (U2704) white scissors, h/t David Wright
 : "ARGA WARGA IN THE DARGA instead of Z"


[snip]

There is a mistake here. A missing step.


%% ARGA WARGA

The third rule ('Z' => "ARGA WARGA...Z") was easiest to test:

1. Open the application. (If necessary, navigate to a text entry field.)


STEP 1-AND-A-HALF. Hold down the Shift key.


2. (While under "us" keyboard layout) strike the key labeled "Z" on my
   standard US laptop keyboard
3. Observe whether

 ARGA WARGA IN THE DARGA instead of Z

   is printed.

The two terminal emulators passed this test. The graphical web browsers 
failed

in an interesting way. Instead of displaying

ARGA WARGA IN THE DARGA instead of Z

in the text entry field, they displayed just

A


--
You won't feel the collar if you don't go anywhere.

Re: Deluged setup instructions/help

[Andrei POPESCU]

On Vi, 10 iul 20, 09:40:48, davidson wrote:
> On Fri, 10 Jul 2020 Intense Red wrote:
> 
> > but nothing for current versions of Debian and many of the guides suggest
> > doing all sorts of "odd" things (like creating /etc/systemd/system/
> > deluged.service files
> 
> Well, in a way that isn't odd at all. Creating such files one way or
> another is pretty damn normal. But sure, creating them all on your
> lonesome, by writing them from scratch is pretty damn weird.

According to https://packages.debian.org/buster/all/deluged/filelist the 
package contains an init script. Checking the /etc/default/deluged file 
would be recommended as well.

In case you (the OP) end up writing a .service file (system or user) to 
replace the init script kindly attach it to a wishlist bug for inclusion 
in the package or at least for others to find it.

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


signature.asc
Description: PGP signature

Re: Que fait apt ?

[NoSpam]

Bonjour

Le 10/07/2020 à 11:28, Bernard Isambert a écrit :

Le 09/07/2020 à 23:17, l0f...@tuta.io a écrit :

Bonjour,

9 juil. 2020 à 22:48 de b...@taranig.net:


Le 09/07/2020 à 17:04, Jean-Marc a écrit :


Ce que tu décris mérite peut-être un rapport de bug.


Il va falloir que je fasse apt install reportbug.


Déjà fait depuis octobre 2016 visiblement :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839546


Oui, en effet. Il m'avait échappé au milier des 276 "normal bugs; 
unclassified". Malheureusement, il n'y a pas de réponse. Du moment 
qu'on paut vivre avec, c'est pas grave.


Ajoute ta pierre à l'édifice et relance le bug en signalant ton 
problème. Si personne ne le fait cela ne risque pas de faire bouger le bug !


--
Daniel

Re: Buster boot messages

[Brian]

On Fri 10 Jul 2020 at 09:52:26 +0200, Klaus Jantzen wrote:

> Hi,
> 
> the first messages that appear on the screen during the boot process seem to
> be messages from the BIOS;
> 
> they have a different format than the subsequent messages from buster and
> they begin with 'ACPI  '.
> 
> As they disappear so fast, I cannot read them.
> 
> Where are these messages logged or what should I do to log these messages?

Try the journalctl command.

-- 
Brian.

Re: Buster boot messages

[Sven Hartge]

Klaus Jantzen  wrote:

> the first messages that appear on the screen during the boot process 
> seem to be messages from the BIOS;

> they have a different format than the subsequent messages from buster 
> and they begin with 'ACPI  '.

> As they disappear so fast, I cannot read them.

> Where are these messages logged or what should I do to log these messages?

"journalctl -b" will have the messages from the most recent boot.

S!

-- 
Sigmentation fault. Core dumped.

Re: Deluged setup instructions/help

[davidson]

On Fri, 10 Jul 2020 Intense Red wrote:

  I want to set up a deluged server on Debian stable.


I don't know anything about deluge. I am idly curious.

Given how many bittorrent clients there are to choose from, may I ask
whether there is anything about deluge/deluged in particular that
makes you want to use it?

Or is it just the one you've used before, so you thought you'd stick
to something familiar?

You are perfectly free to ignore these questions if you'd rather stick
closer to the subject of your concern.


Installing the relevant packages


Name them. Which ones?


there are zero -- none, nada, zilch! -- instructions or example
config files.


There's a man page for deluged. That's not zero. You are exaggerating.

And the latest entry in

  /usr/share/doc/deluged/NEWS.Debian.gz

takes up a screen-and-a-half full of text in my console. That's quite
a lot of news, even if it is ten years old. (I downloaded the
package. I'm not installing it. Just curious.)

Also,

 $ apt-cache show deluged
 [...]
 Description-en: bittorrent client written in Python/PyGTK (daemon)
  Deluge is a full-featured, multi-platform, multi-interface
  BitTorrent client using libtorrent-rasterbar in it's backend and
  featuring multiple user-interfaces: GTK+, web and console.
  .
  It has been designed using the client-server model with a daemon
  process that handles all the bittorrent activity. The Deluge daemon
  is able to run on headless machines with the user-interfaces being
  able to connect remotely from any platform.
  .
  You may want to install this package to run the daemon application
  on a remote server and connect to it from any user-interface.

  See: http://dev.deluge-torrent.org/wiki/UserGuide/ThinClient>
   ^
 [...]
 Homepage: http://www.deluge-torrent.org/

Don't get me wrong. I'm not claiming the documentation is great. Or
complete. Maybe it is, maybe it aint.

I wouldn't know, haven't attempted to follow it, and I'm quite happy
with a different bittorent client (which at times has itself had some
pretty spotty documentation), so I have no plans to do so.

But docs for this package (and related packages) are not non-existent.


  From my perspective deluged nor deluge-web does not install itself
in any sort of a working or bare-bones configuration which is the
norm for debian- packaged programs.

Looking on the web there are a ton of various "guides" to install
deluged,


Er, the web never forgets. So that's always how its going to be. 90%
of everything is crap, and most of the rest is going to be obsolete
cruft too.

So you check out the developer's current website first. Look for
guides there first.

You query your distribution's packaging tools for its location if
you're at all unsure. And so on. Read its posted FAQ. And so on.

Did you do that first? Where *did* you look first? (If you used a
search engine first thing off the bat, don't even answer. Shame on
you. PEBKAC.)


but nothing for current versions of Debian and many of the guides suggest
doing all sorts of "odd" things (like creating /etc/systemd/system/
deluged.service files


Well, in a way that isn't odd at all. Creating such files one way or
another is pretty damn normal. But sure, creating them all on your
lonesome, by writing them from scratch is pretty damn weird.

Good for you, for noticing that you were reading inappropriate
docs, and knowing that you shouldn't blindly follow them.


and other lower-level tasks that it seems normal Debian packages
already do.

  Questions:

Can anyone suggest a recent/up-to-date guide on how to get a running
deluged up and running?


Suggest? Sure. Already have. I pointed you to the developer's own
website. Like some kind of genius.

I do not, and cannot, vouch for its effectiveness though. If something
seems off to you about the developer's own site, then that's some
news.

Post the link and be specific about the issue. Because that would be
useful information.


Does this lack of basic documentation/example config files


Assumes facts not in evidence, Your Honor.


mean a bug report should be filed against deluged?


If it really isn't there, sure.

Good luck.

--
You won't feel the collar if you don't go anywhere.

Re: Que fait apt ?

[Bernard Isambert]

Le 09/07/2020 à 23:17, l0f...@tuta.io a écrit :

Bonjour,

9 juil. 2020 à 22:48 de b...@taranig.net:


Le 09/07/2020 à 17:04, Jean-Marc a écrit :


Ce que tu décris mérite peut-être un rapport de bug.


Il va falloir que je fasse apt install reportbug.


Déjà fait depuis octobre 2016 visiblement :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839546


Oui, en effet. Il m'avait échappé au milier des 276 "normal bugs; 
unclassified". Malheureusement, il n'y a pas de réponse. Du moment qu'on 
paut vivre avec, c'est pas grave.


Merci.


Bonne soirée
l0f4r0




--
Bernard.
25 ans d'utilisation de Debian. Comme le temps passe...

Using .XCompose

[Ajith R]

Hi,

Thanks for your experiment. The fact that it works atleast in some applications 
gives hope. 

I copied your exact sentences to my compose file. 

In Konsole the command cat ~/.XCompose gives the result:

include "%L" 
  : "ങ്ങ" # Ajith's auto-geminate rule, (U0D19) => (U0D19) (U0D4D) 
(U0D19)
   : "✄"  # (U2704) white scissors, h/t David Wright
                : "ARGA WARGA IN THE DARGA instead of Z"

Next, I issued setxkbmap -layout us, just to make sure that the layout is us.

I used konsole and UXterm to test Z. The test failed with Z remaining 
unchanged. 

So, as Zeenan says, there is something fundamentally wrong in my system. I have 
to find that and correct it or reinstall everything.

I tried in another computer with Debian and KDE. The Z gets replaced by the 
first letter in replacement string, while nothing happens in Xterm.

Is KDE the problem? I checked IceWM and got the same result.

> into what appears (to my utterly ignorant eye) to be a "freshly
> synthetic" glyph

That "freshly synthetic" glyph would be the geminate form.


> firefox-esr issued the following errors, which appear to be explanatory:
> (firefox-esr:11619): Gtk-WARNING **: 16:27:05.630: GTK+ supports to output 
> one char only:

This means that all softwares that use Gtk will behave similarly?




> NB: If, like me, you occasionally confuse the Ctrl key with the
> compose key, then keep in mind that when testing this rule in a
> terminal emulator, that typing Ctrl-s (presumably by accident) may
> well stop the terminal from echoing entered characters to the display
> until you enter Ctrl-q to resume normal terminal operation. (That is
> to say, Ctrl-s doesn't "break your keyboard", it only pauses your
> terminal's printout to the display until you resume it with Ctrl-q.)


Thanks for pointing this out. I don't think I have done so because Konsole 
flashes the message that I have suspended display when I press Ctrl S. I would 
have noticed it.


Thanks a lot for your detailed explanations,
ajith

Re: Whats chances of getting libTLSv1.3 for stretch

[tomas]

On Thu, Jul 09, 2020 at 01:12:00PM -0400, Gene Heskett wrote:

[...]

> I like the old kmail, which is what TDE gives me [...]

> There may be folks who can tie me for the minimum mouse clicks to handle 
> their email [...]

That would be mutt users. Or Gnus. Or RMAIL ;-D

Cheers
-- t


signature.asc
Description: Digital signature

Lost sound upgrading to kernel 5.7.0-1-amd64 on Debian testing

[Eric S Fraga]

Just a heads up: yesterday, I decided to upgrade all of my packages.  I
know: what a silly thing to do when having the computer working is
critical for work.  Anyway...

My system is mostly Debian testing (with a couple of bits from sid).  In
upgrading, I lost sound completely.  I spent a few hours trying to sort
this out, playing with pulseaudio, alsamixer, ...  Eventually, I
rebooted with the older kernel (version 5.6.0-1-amd64) which sorted
(some) things out.  I have sound again although only through my HDMI
display, not through the headphones, but that's enough for now.

-- 
Eric S Fraga via Emacs 28.0.50 & org 9.3.7 on Debian bullseye/sid

Re: Buster boot messages

[Zoltán Herman]

hi,
phone videorecord?



Klaus Jantzen  ezt írta (időpont: 2020. júl. 10.,
P 9:52):

> Hi,
>
> the first messages that appear on the screen during the boot process
> seem to be messages from the BIOS;
>
> they have a different format than the subsequent messages from buster
> and they begin with 'ACPI  '.
>
> As they disappear so fast, I cannot read them.
>
> Where are these messages logged or what should I do to log these messages?
>
> --
>
> K.D.J.
>
>

Buster boot messages

[Klaus Jantzen]

Hi,

the first messages that appear on the screen during the boot process 
seem to be messages from the BIOS;


they have a different format than the subsequent messages from buster 
and they begin with 'ACPI  '.


As they disappear so fast, I cannot read them.

Where are these messages logged or what should I do to log these messages?

--

K.D.J.

Re: /etc/default/grub doesn't exist, what to do?

[Borden Rhodes]

> Please tell us the output of:
> dpkg -l | grep -i grub

Sorry for missing this. Please see below:

# dpkg -l | grep -i grub
ii grub-common 2.04-8 amd64
ii grub-efi-amd64-bin 2.04-8 amd64
ii grub-efi-amd64-signed 1+2.04+8 amd64
rc grub-imageboot 0.6 all
ii grub2-common 2.04-8 amd64

> The package grub2-common has the file:
> /usr/share/grub/default/grub
> Which is the default /etc/default/grub file

Thank you for this. I figured there was such a template file but I didn't know
where to look. It would be nice to have this added to
https://wiki.debian.org/Grub so people know how to reconstruct a fresh
template file if theirs gets destroyed (or, in my case, uninstalled)

> The actual package which creates /etc/default/grub in the d-i is
> one of grub-pc and the packages it conflicts with, viz:
> grub (<< 0.97-54), grub-coreboot, grub-efi-amd64, grub-efi-ia32,
> grub-ieee1275, grub-legacy, grub-xen

So that might be the explanation. I removed grub-efi-amd64 to install
grub-efi-amd64-signed. The latter doesn't appear to create its own
/etc/default/grub file.

Is this a bug that I should report or is this by design?

> To find out which, either look at dpkg -l or type
> $ grep -B2 'Creating config file /etc/def' /var/log/installer/syslog
> if you're a member of group adm.

I think this file has long since been deleted. I think I installed Debian on
this machine when I got it over 2 years ago.