On Sb, 20 iun 20, 08:54:52, Matt Zagrabelny wrote:
> Greetings d-u,
>
> I have a new-ish laptop and a pair of the function keys (screen
> brighter/dimmer) are mapped to the wrong function (mic mute/unmute).
Are you using the correct keyboard layout?
You could try 'dpkg-reconfigure
[it's likely you are not subscribed, sorry for the Cc: in case you are]
On Sb, 20 iun 20, 07:58:33, gilleswicki wrote:
> Hello, I found a bug on my system and tried to report it using the
> reportbug software. But as I don't know which packet is the cause of
> the bug, following the
Hi Matt Zagrabelny,
On Sat, 20 Jun 2020 08:54:52 -0500
Matt Zagrabelny wrote:
> Greetings d-u,
>
> I have a new-ish laptop and a pair of the function keys (screen
> brighter/dimmer) are mapped to the wrong function (mic mute/unmute).
>
> Where should I look to file the b
Greetings d-u,
I have a new-ish laptop and a pair of the function keys (screen
brighter/dimmer) are mapped to the wrong function (mic mute/unmute).
Where should I look to file the bug?
I'm aware it is ACPI related, but I do not have any packages installed
that have "acpi" in the pa
Hello, I found a bug on my system and tried to report it using the reportbug
software. But as I don't know which packet is the cause of the bug, following
the procedure of the reportbug software, I write here to ask what I should do.
My bug is that when I try to change the brightness
Le mardi 16 juin 2020 à 14:26 +0200, Helio Loureiro a écrit :
> esse desejo de não conversar sobre os problemas.
Adoro conversar. Mas esta lista não é o espaço para isso, é grosseiro
para com os demais.
--
+55 (61) 3546 7191 gTalk: xmpp:leand...@jabber.org
+55 (61) 99302 2691
problemas desaparecem. Como
> mágica.
>
> E sim com meu conhecimento eu poderia facilmente criar o pacote e
> corrigir, mas não é esse ponto. Nunca foi.
>
> O ponto é que não há esforço no mundo que possa vencer a estupidez humana,
> e como o Paul admitiu por fora do bug report
poderia facilmente criar o pacote e
corrigir, mas não é esse ponto. Nunca foi.
O ponto é que não há esforço no mundo que possa vencer a estupidez
humana, e como o Paul admitiu por fora do bug report (eu que copiei
pra dentro dele), realmente erraram. Mas não admitiram. E ainda
arrumar o erro
.
O ponto é que não há esforço no mundo que possa vencer a estupidez
humana, e como o Paul admitiu por fora do bug report (eu que copiei
pra dentro dele), realmente erraram. Mas não admitiram. E ainda
arrumar o erro??? Ai, ai, ai... Ninguém viu, ninguém liga. Então
melhor outra pessoa resolver
. Como
mágica.
E sim com meu conhecimento eu poderia facilmente criar o pacote e corrigir,
mas não é esse ponto. Nunca foi.
O ponto é que não há esforço no mundo que possa vencer a estupidez humana,
e como o Paul admitiu por fora do bug report (eu que copiei pra dentro
dele), realmente erraram. Mas
Le lundi 15 juin 2020 à 17:48 -0300, Lucky Linux a écrit :
> Esse STF é bonzinho. Tá até demorando e titubeando demais pra botar
> a fascistada na cadeia.
Vamos parar por aqui.
> Jamais você, por tão pouco e tão justo.
É a esperança sempre frustrada pelas revoluções.
--
+55 (61) 3546 7191
Esse STF é bonzinho. Tá até demorando e titubeando demais pra botar a
fascistada na cadeia.
Jamais você, por tão pouco e tão justo.
Em 15/06/2020 14:46, Leandro Guimarães Faria Corcete DUTRA escreveu:
Le lundi 15 juin 2020 à 19:43 +0200, Helio Loureiro a écrit :
apenas eu que fico indignado
Le lundi 15 juin 2020 à 15:53 -0300, Jack Jr. a écrit :
> essa lista é apenas para elogios.
Não, é para apoio mútuo, inclusive se tiver algum desenvolvedor Debian
disposto a ajudar a tutorear novatos. Não é para reclamar de gente que
nem faz parte dela.
--
+55 (61) 3546 7191
Não, mas essa lista é apenas para elogios.
Jack Pogorelsky Jr.
Engenheiro Mecânico
Tel/WhatsApp: +55 (51) 985010082
E-mail: j...@sulmail.com
Website: sulmail.com/pogorelsky
Em 15/06/2020 14:43, Helio Loureiro escreveu:
E estou achando incrível isso. Sou apenas eu que fico indignado com
Le lundi 15 juin 2020 à 19:43 +0200, Helio Loureiro a écrit :
> apenas eu que fico indignado com pacotes sendo removidos por erros
> humanos e não corrigidos?
Não. Mas, se eu tivesse tua competência e tempo livre para reclamar,
viraria desenvolvedor Debian e corrigiria. Não é a indignação, é a
E estou achando incrível isso. Sou apenas eu que fico indignado com
pacotes sendo removidos por erros humanos e não corrigidos?
Best Regards,
Helio Loureiro
http://helio.loureiro.eng.br
http://br.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro
On Mon, 15 Jun 2020 at 19:38, Helio
Manterei minhas lives de sertanejo somente para mim.
Best Regards,
Helio Loureiro
http://helio.loureiro.eng.br
http://br.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro
On Mon, 15 Jun 2020 at 19:29, Leandro Guimarães Faria Corcete DUTRA <
l...@dutras.org> wrote:
> Le lundi 15
Le lundi 15 juin 2020 à 12:49 -0300, Lucas Castro a écrit :
> é meio desnecessário e inútil fazer esses comentário e "celebrações".
Melhor ignorar. Quem reclama pode virar desenvolvedor Debian e ajudar
a mudar. Ou mudar de distribuição. Publicar nesta lista, que nada tem
a ver, é até falta de
e senti falta. Fui olhar o motivo de ter
> sido removido e li todo o bug report. Então pensei em ajudar o debian
> fazendo novamente do zero o código que faltava uma vez que na época eu
> tinha tempo pra isso. Daí comecei a mexer nos fontes e descubro que o que
> foi escrito nos bug re
e comentar e o faço aqui.
>
> Esse foi um pacote que eu uso e senti falta. Fui olhar o motivo de ter
> sido removido e li todo o bug report. Então pensei em ajudar o debian
> fazendo novamente do zero o código que faltava uma vez que na época eu
> tinha tempo pra isso. Daí comecei
ter sido removido e li todo o bug report. Então pensei em ajudar o
debian fazendo novamente do zero o código que faltava uma vez que na
época eu tinha tempo pra isso. Daí comecei a mexer nos fontes e
descubro que o que foi escrito nos bug reports não fazia nenhum
sentido. Quem o criou não
Favor, não enviar mensagem diretas.
Envie para a lista apenas.
On 6/15/20 8:29 AM, Helio Loureiro wrote:
Fora o seguinte ponto que esqueci de comentar e o faço aqui.
Esse foi um pacote que eu uso e senti falta. Fui olhar o motivo de
ter sido removido e li todo o bug report. Então pensei
Fora o seguinte ponto que esqueci de comentar e o faço aqui.
Esse foi um pacote que eu uso e senti falta. Fui olhar o motivo de ter
sido removido e li todo o bug report. Então pensei em ajudar o debian
fazendo novamente do zero o código que faltava uma vez que na época eu
tinha tempo pra isso
Esse é o ponto do bug report. O pacote foi removido erroneamente. Ao
invés de simplesmente reverter isso, é preciso que seja feito todo o
trabalho de envio como um novo pacote.
Beira ao absurdo. É o "sei que errei, mas não sou eu quem vai arrumar".
E vou manter esse bug aberto até
Hélio,
acho que deveria dar uma olhada no que o "Paul Gevers" falou sobre o
bug/pacote em 2 de Julho de 2018,
"""
As the package isn't in Debian anymore, the bug is closed. However, any
Debian maintainer (and via sponsoring
Le jeudi 11 juin 2020 à 16:02 +0200, Helio Loureiro a écrit :
> E continua lá...
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901321
Concordo com a resposta do antigo mantenedor. E creio que a d-u-p
não ajudará nisso.
--
/¯\
\ / +55 (61) 3546 7191 x
E continua lá...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901321
Best Regards,
Helio Loureiro
http://helio.loureiro.eng.br
http://br.linkedin.com/in/helioloureiro
http://twitter.com/helioloureiro
On Mon, May 25, 2020 at 10:04:45PM +0200, Marco Möller wrote:
Even worth, apt is one out of a very few priority reasons to use Debian, or?
When I first used Debian, 20 years ago, apt(-get) was indeed one of the
primary reasons to use Debian. But back then it did not have Recommends:
nor
On Lu, 25 mai 20, 22:04:45, Marco Möller wrote:
> If installing (default parameters in use: with recommends) a package, and
> right afterwards removing it, then the by recommendation drawn in packages
> do not become removed automatically.
This behaviour is intended and controlled by the
> > only to the current install command. The result of a subsequent remove
> > command will depend on the state of the dependency graph as a whole at
> > the time.
> >
>
> So, no "undo" is in apt available, its database does not store sufficient
> informa
Marco M??ller wrote:
> So, no "undo" is in apt available, its database does not store sufficient
> information for it. :-( This is what I see as a severe bug.
There is no undo for apt. There is uninstall, and purge.
Suppose you install Feeblix, which recommends libfoo, and
graph as a whole at
the time.
So, no "undo" is in apt available, its database does not store
sufficient information for it. :-( This is what I see as a severe bug.
Not your fault, thanks for your input! I have had hope for a moment that
there would exist some "undo"
missing the simple step how to return to the former
> > > > system state after having tested a package. Otherwise this is a bug.
> > > > To me it appears to be a severe bug, as apt is not managing the
> > > > packages in my system as expected.
> >
> > [...]
do not become removed automatically. The system is swelling
with no more wanted packages!
I hope I am simply missing the simple step how to return to the former
system state after having tested a package. Otherwise this is a bug.
To me it appears to be a severe bug, as apt is not managing
do not become removed automatically. The system is swelling
> > with no more wanted packages!
> > I hope I am simply missing the simple step how to return to the former
> > system state after having tested a package. Otherwise this is a bug.
> > To me it appears to be a severe bug,
ackages!
> I hope I am simply missing the simple step how to return to the former
> system state after having tested a package. Otherwise this is a bug.
> To me it appears to be a severe bug, as apt is not managing the
> packages in my system as expected.
>
>
> Commandline
On 2020-05-25 at 16:04, Marco Möller wrote:
> If installing (default parameters in use: with recommends) a package,
> and right afterwards removing it, then the by recommendation drawn
> in packages do not become removed automatically. The system is
> swelling with no more wanted packages!
If
to the former
system state after having tested a package. Otherwise this is a bug. To
me it appears to be a severe bug, as apt is not managing the packages in
my system as expected.
Commandline: apt install deborphan
Install: deborphan:amd64 (1.7.33), dialog:amd64 (1.3-20190808-1, automatic
On Thu, 30 Apr 2020 15:13:29 +0300
deuxb...@gmail.com wrote:
> hello,
> i would like to report a bug on Debian.
> fresh install on my system (Chuwi minibook) - trying to shutdown causes
> reboot (windows works without a problem).
Thank you! Please use the reportbug' tool:
https://ww
hello,
i would like to report a bug on Debian.
fresh install on my system (Chuwi minibook) - trying to shutdown causes
reboot (windows works without a problem).
thank you
fait qu'elle dl sa sauvegarde, comme je me suis retrouvé avec la box
d'un autre et qu'il a falllu tous reconfigurer à la mano, sauf authentification
PPPO
On souhaite que celui là façe pas de bétisses ...
Voila un bug notable, pas la peine de mettre des programmes de controle, si
quand je dis
fwupd is worth noting: https://en.wikipedia.org/wiki/Fwupd
and not only does it manage PC firmwares (UEFI) but peripheral cards
firmwares too
but it is far from widely adopted :-(
instead of "Buster", which has
> been the stable distribustion since July 6th 2019.
If it's just the name of the stable distribution it doesn't matter, the
general principle is still the same.
Anyway, if you find anything outdated/wrong/missing you could report a
bug against the 'debian
Hi there,
On Sat, 28 Mar 2020, rba777 wrote:
...
[ 0.457794] ACPI BIOS Error (bug): Failure creating named object
[\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
[ 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20190816/psobject-220)
...
Using apt and apt
Jude DaShiell wrote:
>
> Does any Linux app exist to let systems know when bios updates become
> available for the bios running on those systems?
No. It would require a mechanism supported by each manufacturer,
and they tend not to even be consistent on their own websites.
Server manufacturers
On Sat, 28 Mar 2020, Darac Marjal wrote:
> Date: Sat, 28 Mar 2020 06:55:55
> From: Darac Marjal
> To: debian-user@lists.debian.org
> Subject: Re: Question regarding an ACPI BIOS Error (bug)
>
>
> On 28/03/2020 09:35, rba...@protonmail.ch wrote:
> > Hi all, I've been re
I: Added _OSI(Linux-HPI-Hybrid-Graphics)
These aren't errors; these ones are just informative.
> [ 0.457794] ACPI BIOS Error (bug): Failure creating named object
> [\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
> [ 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name
Error (bug): Failure creating named object
[\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323)
[ 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20190816/psobject-220)
[ 0.457805] ACPI: Skipping parse of AML opcode: OpcodeName unavailable
(0x0014)
[ 0.457807
Le samedi 21 mars 2020, 14:10:53 CET Bernard Schoenacker a écrit :
> - Mail original -
>
> > De: "MERLIN Philippe"
> > À: debian-user-french@lists.debian.org
> > Envoyé: Samedi 21 Mars 2020 14:06:28
> > Objet: Écrire un rapport de Bug
> >
Bonjour.
Si le problème c'est l'activation du HDMI, tu peux probablement tenter
de blacklister le module "snd_hda_codec_hdmi".
Concernant ta demande initiale, j'aurai tendance faire ce bogue contre
le noyau puisque les pilotes audio, même si provenant du projet alsa,
sont intégrés dans le
un rapport de Bug mais je ne sais
pas sélectionner le "coupable", Alsa, Kernel, Systemd ou .
Si vous avez eu la patience de lire ce message et que vous avez une suggestion
je suis preneur.
Philippe Merlin
- Mail original -
> De: "MERLIN Philippe"
> À: debian-user-french@lists.debian.org
> Envoyé: Samedi 21 Mars 2020 14:06:28
> Objet: Écrire un rapport de Bug
>
> Bonjour,
> Je suis l'heureux utilisateur d'un Pc portable Lenovo W520, ce
> portable
&
Hi,
I'm having a problem after an update some weeks ago, every few minutes the
pc is freezing for a while and after it recover, it seem to be the same as
writte on this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
I'm getting also the same errors:
[50928.830285] GpuWatchdog[27129
Thanks for passing that along, Didar. It shows my cert is OK as well.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689
Hi,
This post is informational:
Lets Encrypt discovered a bug in their CA software (boulder) related to CAA
checking code. They have decided to revoke a subset of certificates issued on
March 4, 2020.
More information:
https://arstechnica.com/information-technology/2020/03/lets-encrypt-revoking
On Mon, Mar 02, 2020 at 01:14:59PM +1030, heman wrote:
> hi Tomas, thanks for the response, pretty sure the docker image was the
> official debian:buster from dockerhub. I'll double check.
>
> I hadn't thought of looking for an issue reporting link on dockerhub, as I
> figured it would be part
On Sun, Feb 23, 2020 at 11:40:36PM +1030, heman wrote:
I've read https://www.debian.org/Bugs/Reporting
but it is still completely unclear to me how I can report what I
consider to be a bug or flaw with the debian docker image, as it is
not a package, but a container image created from multiple
On Sun, Feb 23, 2020 at 11:40:36PM +1030, heman wrote:
> Hi,
>
> I've read https://www.debian.org/Bugs/Reporting
> but it is still completely unclear to me how I can report what I
> consider to be a bug or flaw with the debian docker image [...]
That depends on where you got thi
Hi,
I've read https://www.debian.org/Bugs/Reporting
but it is still completely unclear to me how I can report what I
consider to be a bug or flaw with the debian docker image, as it is
not a package, but a container image created from multiple packages.
(from reading the page at the above URL
Hi folks,
We'll have a Bug Squashing Party in Gothenburg (Sweden) on Sunday March
29, organized as part of Foss-North's Community Day [0]. The event will
be held at Viktoriahuset [1] (courtesy of the Inbyggd Frihet project),
close to the old town. Please use the wiki for registration
Hi folks,
We'll have a Bug Squashing Party in Gothenburg (Sweden) on Sunday March
29, organized as part of Foss-North's Community Day [0]. The event will
be held at Viktoriahuset [1] (courtesy of the Inbyggd Frihet project),
close to the old town. Please use the wiki for registration
Please take a look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949471 . I have
reported it as a bug in open-infrastructure-system-build , but I don't
think the problem is in this component; I think the problem is in one of
the components that it installs ( maybe ca-certificates
topology in‐ formation. This aligns to a
> multiple of the physical block size in a way that
> guarantees optimal performance
>
>
> 1. Probably parted detected physical sector size as 512
> instead of 4096? Why?
>
> 2. Even if par
physical sector is 512 instead of
> 4096, why start from 65535 and not from 65536? What is the logic
> behind? How using odd multiplier can improve performance?
>
> Is it a bug in parted or I am missing something?
Bug #923561 has a long discussion about alignment and optimal transfer
siz
Le 04/12/2019 à 13:15, Sergey Spiridonov a écrit :
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: 82DD924B-BF0E-40FF-9037-1FD4E7307D26
Device Start End Sectors Size Type
Kamil Jońca composed on 2019-11-27 22:31 (UTC+0100):
>...X.org 1.20.4 driver: modesetting...
To switch to nouveau from modesetting could be as simple as installing
xserver-xorg-video-nouveau. If it's already installed, you may need to specify
it
in /etc/X11/xorg.conf.d/50-device.conf to
Felix Miata writes:
> Kamil Jońca composed on 2019-11-27 21:35 (UTC+0100):
>
>> Felix Miata writes:
>
>>> Kamil Jońca composed on 2019-11-27 19:23 (UTC+0100):
>>
There is debian box
>
>>> Which Debian version?
>
>> sid.
>
> I don't have Sid on my box with G84.
> ...
>>> # inxi -V |
Kamil Jońca composed on 2019-11-27 21:35 (UTC+0100):
> Felix Miata writes:
>> Kamil Jońca composed on 2019-11-27 19:23 (UTC+0100):
>
>>> There is debian box
>> Which Debian version?
> sid.
I don't have Sid on my box with G84.
...
>> # inxi -V | head -n1
>> inxi 3.0.37-00 (2019-11-19)
>> #
ller: NVIDIA Corporation G84 [GeForce 8600 GT]
>> (rev a1)
>> --8<---cut here---end--->8---
>> in it.
>
>> I have feeling that graphic drivers have bug, but I am not sure:
>> My simple test:
>> ebook-viewer anthing.e
<---cut here---end--->8---
> in it.
> I have feeling that graphic drivers have bug, but I am not sure:
> My simple test:
> ebook-viewer anthing.epub
What provides ebook viewer? aptitude search ebook shows me nothing by that name.
...
> Th
There is debian box with:
--8<---cut here---start->8---
08:00.0 VGA compatible controller: NVIDIA Corporation G84 [GeForce 8600 GT]
(rev a1)
--8<---cut here---end--->8---
in it.
I have feeling that graphic driv
Am Montag, 25. November 2019, 20:07:56 CET schrieb Goran Delcev:
Hi Goran,
this bug is known since almost 2 years. I reported it in the list, sent a
bugreport tzo
powerdevil (and askeds the list, which package might be responsible for it),
but got
no solution. People told me, the kernel
Hi Julian,
Quoting sj...@uranus.uni-freiburg.de (2019-11-21 11:39:14)
> if it (from around June 28th) still matters for somebody: I
> re-installed my whole system and I couldn't re-recognise the behaviour
> described. I also can't remember having changed anything in the
> "deeper settings of
Hi,
if it (from around June 28th) still matters for somebody: I re-installed my
whole system and I couldn't re-recognise the behaviour described. I also can't
remember having changed anything in the "deeper settings of the system"…
However, best regards,
Julian Schreck
--
> Hi,
>
> Julian
Eero Volotinen wrote:
> Any clue why systemctl start snort is not running start section of init
> script? (if start is already run once?)
Don't use the snort package from the Debian repository, it is ancient
(last upload was in 2015) and might as well be orphaned or better yet
removed from
mmand systemctl restart snort
> Sounds like a bug?
>Eero
That could be a bug. On the other hand, "killed" implies that it may
not have had the opportunity to perform a clean shutdown, perhaps
leaving behind a PID file or some other cruft that must be cleaned up
prior to the nex
Hi,
Any clue why systemctl start snort is not running start section of init
script? (if start is already run once?)
For example, if snort daemon is killed then only way to start it is run
command systemctl restart snort
Sounds like a bug?
Eero
Peter Ehlert writes:
> SOLVED
Thank You Very Much, Peter^^^
(because that is very important part in installing i think)
Sincerely,
--
^고맙습니다 _地平天成_ 감사합니다_^))//
SOLVED
add this to /etc/NetworkManager/NetworkManager.conf
per bug #835553
[device]
wifi.scan-rand-mac-address=no
That worked for me with a Ralink Technology, Corp. RT5370 Wireless
Adapter on Debian Stretch. Thank you very much.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842422#40
On Sat, 9 Nov 2019, Peter Ehlert wrote:
> Date: Sat, 9 Nov 2019 13:28:02
> From: Peter Ehlert
> To: debian-user@lists.debian.org
> Subject: Re: Debian Installer Bug -Wifi driver not installed
> Resent-Date: Sat, 9 Nov 2019 18:45:09 + (UTC)
> Resent-From: debian-use
On 11/9/19 9:25 AM, Patrick Bartek wrote:
On Sat, 9 Nov 2019 06:16:17 -0800
Peter Ehlert wrote:
I have a desktop computer running Debian Buster Mate that I want to move
to a different location and use Wifi.
Using a cheap USB dongle NetworkManager Applet detects the device, lets
me select
On Sat, 9 Nov 2019 06:16:17 -0800
Peter Ehlert wrote:
> I have a desktop computer running Debian Buster Mate that I want to move
> to a different location and use Wifi.
> Using a cheap USB dongle NetworkManager Applet detects the device, lets
> me select from available networks, accepts
I have a desktop computer running Debian Buster Mate that I want to move
to a different location and use Wifi.
Using a cheap USB dongle NetworkManager Applet detects the device, lets
me select from available networks, accepts password, but will not
connect..and after a few moments it closes..
I have a desktop computer running Debian Buster Mate that I want to move
to a different location and use Wifi.
Using a cheap USB dongle NetworkManager Applet detects the device, lets
me select from available networks, accepts password, but will not
connect..and after a few moments it closes..
Le 28/10/2019 à 09:14, Andy Smith a écrit :
I will take a guess that the switching of the iptables commands to
use the nftables framework has somehow caused this iptable_filter
module to not be loaded even though the firewall still works.
Correct.
Is it a bug that loading rules
On Sb, 14 sep 19, 04:20:42, Yoann LE BARS wrote:
>
> Well, I think this patch should probably be added to the package. Can
> anyone tell me what I should do to propose this patch? Should I open a
> bug issue on Debian bug tracker, then send the patch? Should I do
> someth
On Sb, 14 sep 19, 04:00:08, Yoann LE BARS wrote:
>
> But as it is the first time I propose some workaround to a bug, I want
> to make sure I have done what is needed. So, can anyone confirm my
> message is sufficient of if I should do something more?
Depends on what you mean by
this change permanent by adding those
modules to a file in /etc/modules-load.d/.
I will take a guess that the switching of the iptables commands to
use the nftables framework has somehow caused this iptable_filter
module to not be loaded even though the firewall still works.
Is it a bug that loading rules
Hi,
it seems systemd-networkd of the Buster distribution does not work
reliable on some of my systems.
Can you help me to further analyze the problem in front of bug creation?
Short summary:
If an interface uses static addresses and the cable is unplugged and
plugged in again, the interface does
Hi, I installed Debian 10 on my old laptop (BIOS mode) using the
unsupported firmware iso.
I noticed that using the Graphical installer it fails connecting to the
wifi.
Using the classic ncurses installer, it connects successfully.
I checked also with the latest firmware-10.1.0-amd64-netinst.iso
you have yet another desktop installed and
available to select? you don't mention if you've actually
installed another desktop that should show up in the menu
or not.
so it may not actually be a bug because there is nothing
else to select.
2. There is no sound. The alsamixer and the Gnome
tually
installed another desktop that should show up in the menu
or not.
so it may not actually be a bug because there is nothing
else to select.
> 2. There is no sound. The alsamixer and the Gnome sound tool show only
> an HDMI option but my monitor has no speakers. If I reboot to Stretch
Two problems after a distribution upgrade to Buster
1. At login window after boot up the desktop selection is locked a
Gnome. That is, if the symbol to change the desktop selection is
selected a list of available desktops is displayed with a dot indicating
Gnome is the current selections.
a bug I have not seen in Debian bug tracker system:
when I tried to launch FFADO-mixer, it failed to load (see log at the
end of this message).
I have asked for help on FFADO mailing list:
https://sourceforge.net/p/ffado/mailman/ffado-user/?viewmonth=201909=11
Jonathan Whoithe has
Hello everybody out there!
I am using Debian 10 :
$ cat /etc/debian_version
10.1
I am using Ardour 5 from standard distribution repositories:
$ aptitude versions ardour
i 1:5.12.0-3stable
900
I have experimented bug #874598
Package: apt
Severity: wishlist
On Ma, 06 aug 19, 16:22:34, Keith Bainbridge wrote:
>
> I found a simple guide at
>
>
> https://www.linuxbabe.com/debian/install-latest-virtualbox-6-0-10-debian-10-buster
>
>
> In summary:
> Create new sources file:
> sudo nano
Reco wrote:
> lsinitramfs /boot/initrd.img* | grep ttf$
Hmm here it does not find anything, but plymouth is in the initram
When looking for ttf
grep
ttf -r /etc/initramfs-tools /usr/share/initramfs-tools/
/usr/share/lintian/overrides
/usr/share/initramfs-tools/hooks/plymouth: if
[
On Sun, Jul 28, 2019 at 01:54:01PM +0200, deloptes wrote:
> Reco wrote:
>
> > plymouth, maybe? You know, that fancy bootloader program?
>
> yes I know and use it - much better than 80s dos style boot up screen,
> but ... perhaps needs a check out of curiosity.
>
> Do you know how/where to check
Reco wrote:
> plymouth, maybe? You know, that fancy bootloader program?
>
yes I know and use it - much better than 80s dos style boot up screen,
but ... perhaps needs a check out of curiosity.
Do you know how/where to check this?
thanks in advance
regards
801 - 900 of 8562 matches
Mail list logo
