On Sat, Sep 18, 2021 at 10:14:39PM -0300, Dedeco Balaco wrote:
> My window manager is Mate Desktop. The terminal i most use is its own.
> And i use vim a lot,
> After the upgrade, when i quit vim, the terminal title becomes empty,
> instead of returning to the default title "Terminal".
The real
Em 18/09/2021 22:49, Jeremy Hendricks escreveu:
> I apologize for assuming you upgraded from 9 to 11 directly (skipping
> 10). It’s a common misconception that is acceptable.
>
No problem. Actually, my first try to update was directly from a not
completely updated Debian 9 to the current
> > number of files that was opened with it, when it was launched.
> >
> > After the upgrade, when i quit vim, the terminal title becomes
> > empty, instead of returning to the default title "Terminal".
> >
> > Why is this happening? A bug in Vim? In mate-terminal? Or in Debian
> 11?
> >
>
>
; After the upgrade, when i quit vim, the terminal title becomes
> empty, instead of returning to the default title "Terminal".
>
> Why is this happening? A bug in Vim? In mate-terminal? Or in Debian 11?
>
tle
> shows the name of the file currently being edited, and the number of files
> that was opened with it, when it was launched.
>
> After the upgrade, when i quit vim, the terminal title becomes empty,
> instead of returning to the default title "Terminal".
>
> Why is this happening? A bug in Vim? In mate-terminal? Or in Debian 11?
>
the name of the file currently being edited, and the number of
files that was opened with it, when it was launched.
After the upgrade, when i quit vim, the terminal title becomes empty,
instead of returning to the default title "Terminal".
Why is this happening? A bug in Vim? In mat
- Mail original -
> De: "patrick jollant"
> À: debian-user-french@lists.debian.org
> Envoyé: Lundi 13 Septembre 2021 11:56:02
> Objet: Bug : Evince - Impression PDF freezes
> Bonjour,
> ne sachant où exposer le problème, j'ai ouvert un sujet sur ce forum
Bonjour,
- supprimer le paquet ipp-usb me paraît une mauvaise idée car c'est une
dépendance:
didier@hp-notebook14:~$ apt rdepends ipp-usb
ipp-usb
Reverse Depends:
Recommande: cups-daemon
Recommande: libsane1
Recommande: sane-airscan
Ton unique imprimante-scanner peut être détectée
Bonjour,
ne sachant où exposer le problème, j'ai ouvert un sujet sur ce forum
https://debian-facile.org/viewtopic.php?pid=366818#p366818
après différentes recherches, il apparaîtrait qu'il s'agisse réellement d'un bug
Le numériseur pose également problème.
Si vous désirez plus d'informations
On Sun 12 Sep 2021 at 18:26:57 +0200, l0f...@tuta.io wrote:
> Hi,
>
> 12 sept. 2021, 12:45 de bouncingc...@gmail.com:
>
> > Also, as an additional confirmation ...
> > On the above bug page:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> >
Hi,
12 sept. 2021, 12:45 de bouncingc...@gmail.com:
> Also, as an additional confirmation ...
> On the above bug page:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> the second link is the package name "sudo", which goes to
> https://bugs.debian.org/cgi-
On Du, 12 sep 21, 07:54:32, Steve Dondley wrote:
>
> > Using free(dom) software sometimes require you invest resources in some
> > other way, depending on the particular issue and how important it is to
> > you ;)
>
> Agreed. But the package manager will have a much easier time than me at
>
Debian is interested in *all* issues affecting a user. The triager will
help sort it out.
If it is a Debian bug, the fix woudld be applied in unstable and work
its way through the system. The same happens with an upstream fix.
So would I just be wasting my time and everyone else's
Using free(dom) software sometimes require you invest resources in some
other way, depending on the particular issue and how important it is to
you ;)
Agreed. But the package manager will have a much easier time than me at
nailing down the problem and do it in much less time. I've already
On Sun 12 Sep 2021 at 20:45:13 +1000, David wrote:
> On Sun, 12 Sept 2021 at 20:20, wrote:
> > 12 sept. 2021, 10:00 de scdbac...@gmx.net:
> > > l0f...@tuta.io wrote:
> > >
> > >> By the way, how can one see that a bug is closed and not open please?
>
On Sat 11 Sep 2021 at 22:40:32 -0400, Steve Dondley wrote:
> First, thanks to everyone here and the Debian community, an amazing project.
>
> Running bullseye with package roundcube. I believe I have found a bug that
> I'd like to report.
>
> I am using reportbug to report it
On Sb, 11 sep 21, 22:40:32, Steve Dondley wrote:
> First, thanks to everyone here and the Debian community, an amazing project.
>
> Running bullseye with package roundcube. I believe I have found a bug that
> I'd like to report.
>
> I am using reportbug to report it. Wh
On Sun, 12 Sept 2021 at 20:20, wrote:
> 12 sept. 2021, 10:00 de scdbac...@gmx.net:
> > l0f...@tuta.io wrote:
> >
> >> By the way, how can one see that a bug is closed and not open please?
> >> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
&
Hi,
12 sept. 2021, 10:00 de scdbac...@gmx.net:
> l0f...@tuta.io wrote:
>
>> By the way, how can one see that a bug is closed and not open please?
>> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
>>
> I think you can recognize it by the "Done:&qu
Hi,
l0f...@tuta.io wrote:
> By the way, how can one see that a bug is closed and not open please?
> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
I think you can recognize it by the "Done:" header on the web page:
Done: Marc Haber
I see it in an old bug
Hi,
11 sept. 2021, 18:52 de a...@cityscape.co.uk:
> It's your submission; you can close it, In fact, any user can clos
> it.
>
By the way, how can one see that a bug is closed and not open please?
For example, I know that the bug #958402 [1] has been closed because I received
First, thanks to everyone here and the Debian community, an amazing
project.
Running bullseye with package roundcube. I believe I have found a bug
that I'd like to report.
I am using reportbug to report it. When doing so, I got this message:
Your version (1.4.11+dfsg.1-4) of roundcube
rts (Xirinacs)
<°((( ><
Missatge de Blackhold del dia dl., 30
d’ag. 2021 a les 22:37:
>
> Hola,
> Doncs rere la consulta que he "solventat" avui utilitzant un altre
> entorn d'escriptori, m'agradaria poguer reportar el bug aquest que
> m'he trobat.
>
> Mentre
Hola,
Doncs rere la consulta que he "solventat" avui utilitzant un altre
entorn d'escriptori, m'agradaria poguer reportar el bug aquest que
m'he trobat.
Mentre investigava no he trobat cap error, ni els paquets de dades
semblaven erronis, simplement el comportament era que el
Hi,
solon wrote:
> > Seems to me that installing targetcli-fb should really also install
> > and activate the at boot service by default?
> I'm not really certain if this is the right package to
> file a bug for, for the reasons I mentioned earlier.
Well, an improvement wish
Hi,
filing a bug towards targetcli seems futile, as it is not packaged by
Debian any more.
https://tracker.debian.org/pkg/targetcli
brings me to
https://tracker.debian.org/news/826155/removed-130pre41ga55d018-3-from-unstable/
which says
"the following package(s) have been removed
Hello all,
New to debian lists, though not to linux.
Im unsure where and how to post a bug, or whether it really is a bug as
I can't really find other specific debian cases of it and if it is a
bug, I would expect more reports of the problem,
I have an iscsi config setup with targetcli
Hi,
On 2021-07-25 4:36 p.m., to...@tuxteam.de wrote:
> On Sun, Jul 25, 2021 at 04:27:36PM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>> Hi,
>>
>> On 2021-07-25 3:41 p.m., to...@tuxteam.de wrote:
>>> On Sun, Jul 25, 2021 at 03:36:32PM -0400, Polyna-Maude Racicot-Summerside
>>> wrote:
On Sun, Jul 25, 2021 at 04:27:36PM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-07-25 3:41 p.m., to...@tuxteam.de wrote:
> > On Sun, Jul 25, 2021 at 03:36:32PM -0400, Polyna-Maude Racicot-Summerside
> > wrote:
> >> Hi !
> >> I'm doing a Debian partial mirror using debmirror.
>
Hi,
On 2021-07-25 3:41 p.m., to...@tuxteam.de wrote:
> On Sun, Jul 25, 2021 at 03:36:32PM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>> Hi !
>> I'm doing a Debian partial mirror using debmirror.
>> After around 65%, it fails saying "can't write file is read-only".
>> I unmount the
On Sun, Jul 25, 2021 at 03:36:32PM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi !
> I'm doing a Debian partial mirror using debmirror.
> After around 65%, it fails saying "can't write file is read-only".
> I unmount the partition.
> Mount it back (external hard drive).
> And now it goes
Hi !
I'm doing a Debian partial mirror using debmirror.
After around 65%, it fails saying "can't write file is read-only".
I unmount the partition.
Mount it back (external hard drive).
And now it goes great...
Someone ever had a similar problem ?
--
Polyna-Maude R.-Summerside
-Be smart, Be
Perhaps it should be said that personal use of gpg and the use that a
system administrator makes of it and key-ing are different use-cases. So we
might expect fewer assumptions to hold and greater mystery :-)
On Sat, Jun 26, 2021, 1:53 PM wrote:
> On Sat, Jun 26, 2021 at 08:42:26AM -0400, Cindy
On Sat, Jun 26, 2021 at 08:42:26AM -0400, Cindy Sue Causey wrote:
> On 6/26/21, Andrei POPESCU wrote:
[...]
> > Well, it makes perfect sense if you remember that "everything is a
> > file", even if there are exceptions (e.g. network devices).
>
>
> Hopefully I'm reading this right. While on
On 6/26/21, Andrei POPESCU wrote:
>> Andrei, thanks for having picked up my problem and having cared for the
>> release notes to comment on it, and also for supposedly having motivated
>> Julian Andres Klose to publish a very helpful blog post on the related
>> subject. Brad Rogers here in the
On 26.06.21 11:54, Andrei POPESCU wrote:
(...)
Very good points, all appreciated.
Feel free to suggest patches for it through bugs against the harden-doc
package, or merge requests in Salsa if the Maintainer is accepting them.
I'll do so. I decided, motivated also by observing how you are
On Jo, 24 iun 21, 16:42:34, Marco Möller wrote:
> On 21.06.21 07:58, Andrei POPESCU wrote:
> > On Du, 20 iun 21, 10:20:42, Andrei POPESCU wrote:
> > > Package: release-notes
> > > X-Debbugs-Cc: debian-user@lists.debian.org, a...@packages.debian.org
> > >
> > > On Sb, 19 iun 21, 22:07:35, Marco
On 21.06.21 07:58, Andrei POPESCU wrote:
On Du, 20 iun 21, 10:20:42, Andrei POPESCU wrote:
Package: release-notes
X-Debbugs-Cc: debian-user@lists.debian.org, a...@packages.debian.org
On Sb, 19 iun 21, 22:07:35, Marco Möller wrote:
Command apt-key and its man page say that apt-key is
On Fri 11 Jun 2021 at 14:01:02 (+), Kanto Andria wrote:
> First post here on this lists. I know about the the IP set of commands, BUT
> my concern is about the ifconfig one.I have 2 Debian 10 Buster systems and I
> have the same behavior - reading the man page did not give the specific
>
On Du, 20 iun 21, 10:20:42, Andrei POPESCU wrote:
> Package: release-notes
> X-Debbugs-Cc: debian-user@lists.debian.org, a...@packages.debian.org
>
> On Sb, 19 iun 21, 22:07:35, Marco Möller wrote:
> >
> > Command apt-key and its man page say that apt-key is deprecated, but do not
> > suggest an
Package: release-notes
X-Debbugs-Cc: debian-user@lists.debian.org, a...@packages.debian.org
On Sb, 19 iun 21, 22:07:35, Marco Möller wrote:
>
> Command apt-key and its man page say that apt-key is deprecated, but do not
> suggest an instead recommended tool. It is only mentioned that keys would
There is no way to tell that you didn't mean to look up a name in
DNS.
> Why the IP is reset to a public IP here belonging to OVH?
That's what it resolved to.
This is not a bug.
The bigger issue here is that ifconfig has been deprecated for 10+
years and whatever you are trying to do with it y
Hi.
On Fri, Jun 11, 2021 at 02:01:02PM +, Kanto Andria wrote:
> dada@Jradebian:~$ sudo ifconfig enp0s31f6 stats
There's no "stats" option to ifconfig, at least according to the source
of version 1.60+git20180626.aebd88e.
But what a quick test does show me, is that in my
Hello,
First post here on this lists. I know about the the IP set of commands, BUT my
concern is about the ifconfig one.I have 2 Debian 10 Buster systems and I have
the same behavior - reading the man page did not give the specific options
dada@Jradebian:~$ sudo ifconfig enp0s31f6
hello,
> Il peut manquer un extern dans un fichier d'entête. C'est la différence
> entre les C récents et le C89.
bingo! je viens d'utiliser ctags pour aller placer des extern devant
chaque symboles affichés dans la stderr et ca fonctionne parfaitement!
merci Basille! du coup j'ajoute une
soucis
<<. chroot ~/local/machines/alpine-latest /bin/sh
apk update
apk add git musl-dev
git clone git://bitreich.org/ploot
cd ploot
make
je pourrais m'arrêter là mais y'a peut-être bug et cas échéant
j'aimerais le remonter. par contre je n'ai presque pas fai
latest /bin/sh
apk update
apk add git musl-dev
git clone git://bitreich.org/ploot
cd ploot
make
je pourrais m'arrêter là mais y'a peut-être bug et cas échéant
j'aimerais le remonter. par contre je n'ai presque pas fait de C pendant
les 25 dernières années et je ne sais pa
sl-dev
git clone git://bitreich.org/ploot
cd ploot
make
je pourrais m'arrêter là mais y'a peut-être bug et cas échéant
j'aimerais le remonter. par contre je n'ai presque pas fait de C pendant
les 25 dernières années et je ne sais pas trop quoi verifier pour
qualifier le bug. une idée?
ploot
make
je pourrais m'arrêter là mais y'a peut-être bug et cas échéant
j'aimerais le remonter. par contre je n'ai presque pas fait de C pendant
les 25 dernières années et je ne sais pas trop quoi verifier pour
qualifier le bug. une idée?
cordialement,
marc
On Fri, May 21, 2021 at 06:47:17PM -0400, Mohamud Ali wrote:
> dictionory
> Sorry, command-not-found has crashed! Please file a bug report at:
> http://www.debian.org/Bugs/Reporting
> Please include the following information with the report:
>
> command-not-found version: 0.
command spelling??
L
-Original Message-
From: Mohamud Ali [mailto:khtos...@icloud.com]
Sent: Friday, May 21, 2021 3:47 PM
To: debian-user@lists.debian.org
Subject: Bug reportin
dictionory
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs
On Fri, May 21, 2021 at 06:47:17PM -0400, Mohamud Ali wrote:
> Python version: 3.9.1 final 0
> Distributor ID: Kali
> Description: Kali GNU/Linux Rolling
Please report this to your operating system's support team, not to
Debian's user mailing list, or any other place.
dictionory
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs/Reporting
Please include the following information with the report:
command-not-found version: 0.3
Python version: 3.9.1 final 0
Distributor ID: Kali
Description:Kali GNU/Linux Rolling
I always use my guide to install samba.
I wanna add string to /etc/bind/named.conf
> include "/var/lib/samba/bind-dns/named.conf"
but no this file in new debian version (last I add on 10.2)
I added manually,
> dlz "AD DNS Zone" { database "dlopen
>
my solution if you are novice).
I would rather live with the warnings unless I actually had a GPU which
needs this firmware. Don't know if you can actually buy these yet.
> Look like the bug are the 5.10.0-6-amd64 kernel.
No, it is in the firmware-amd-graphics package. A bug report against
th
On 4/18/21 12:31 PM, Robbi Nespu wrote:
I hope my guess is right. It on recently added on kernel up stream, I
can see the log here
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu
--
Email : Robbi Nespu
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E
are novice).
Look like the bug are the 5.10.0-6-amd64 kernel.
--
Email : Robbi Nespu
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc
I am using bullseye and when I perform an update (apt-get dist-upgrade) to
the system I get get the following messages. I'm not sure if this is an
intramfs-tools issue or a firmware-amd-graphics issue. I have the latest
version firmware-amd-graphics installed.
Processing triggers for
David Wright wrote:
> On Tue 13 Apr 2021 at 00:49:48 (+0200), deloptes wrote:
>> Kent West wrote:
>>
>>
>> Perhaps you try locking the session of the first user and see what
>> happens - if the second has access to the audio.
>
> It would also be interesting to know what happens when the
Nicholas Geovanis wrote:
>
> The most interesting question to me:
> Has doc or first-principles failed so badly that we resort to
> experimentation again?
Yes, in the sense that there are too many ways for this to
legally exist to be able to say: "package foo is causing this,
and you can either
On Wed, Apr 14, 2021, 11:20 AM David Wright
wrote:
> On Tue 13 Apr 2021 at 00:49:48 (+0200), deloptes wrote:
> > Kent West wrote:
> >
> > > I did some experimentation afterwards, and have discovered that if
>
> > Perhaps you try locking the session of the first user and see what
> happens
On Tue 13 Apr 2021 at 00:49:48 (+0200), deloptes wrote:
> Kent West wrote:
>
> > I did some experimentation afterwards, and have discovered that if
> > user X mutes the mic, the mic then seems to be "owned" by user X, and
> > no one and no OS can seem to unmute it. I was using the machine as
> >
Dan Ritter wrote:
> q4os appears to be a Debian derivative, so presumably they would
> know better than we as to what is going on. I can't find a
> mailing list, but I do see a forum at
> https://www.q4os.org/forum/
>
> I'm going to guess that they will want a better explanation of
> the
John Hunter wrote:
> Hi,
>
> [ 952jmdh ]
>
> I have just installed q4os-3.14-x64-tde.r4.iso as an upgrade to an existing
> laptop. The installation (admin user) account has been estabished OK. When I
> try to log into a proper user account (tied to my old work account)
> tdestartupconfig
Hi,
[ 952jmdh ]
I have just installed q4os-3.14-x64-tde.r4.iso as an upgrade to an
existing laptop. The installation (admin user) account has been
estabished OK. When I try to log into a proper user account (tied to my
old work account) tdestartupconfig complains and goes tits-up. I have
On Tue, Apr 13, 2021 at 12:49:48AM +0200, deloptes wrote:
> Kent West wrote:
>
> > I did some experimentation afterwards, and have discovered that if
> > user X mutes the mic, the mic then seems to be "owned" by user X, and
> > no one and no OS can seem to unmute it. I was using the machine as
>
Kent West wrote:
> I did some experimentation afterwards, and have discovered that if
> user X mutes the mic, the mic then seems to be "owned" by user X, and
> no one and no OS can seem to unmute it. I was using the machine as
> user Y, which is why I couldn't unmute it, and when I handed the
>
n't unmute it, and when I handed the
laptop to the hardware tech, logged in as user X, bingo! He umuted it.
I don't know if this would be a kernel package bug, or an X package
bug, or a keyboard-input package bug, or an audio-package bug, or
Any ideas?
Thanks!
--
Kent West<&
David Wright wrote:
> AIUI you really want to avoid using accented characters or any sort
> of composition in your username and password. The reason is that if
> your computer gets set in any unexpected language setting (or unset),
> you might not be able to login at all, and unable to correct
On Sat 10 Apr 2021 at 19:11:15 (-0400), mcgarrett wrote:
> > On April 10, 2021 at 5:53 PM laurent aerens
> > wrote:
> >
> > Package: unknown
> >
> > Version: debian 9 - 10
> >
> > Severity: minor
> >
> > When I type accent marks (¨^´`) in the terminal followed by a letter
>
On Sat 10 Apr 2021 at 23:53:27 (+0200), laurent aerens wrote:
> Package: unknown
>
> Version: debian 9 - 10
>
> Severity: minor
>
> When I type accent marks (¨^´`) in the terminal followed by a letter
> (that does not match with the accent) (for example ^ and the letter n)
> nothing happens and
On Sat, Apr 10, 2021 at 11:53:27PM +0200, laurent aerens wrote:
> Package: unknown
>
> Version: debian 9 - 10
>
> Severity: minor
This looks like you're attempting to generate headers for a bug report,
except that you're writing to debian-user rather than to the bug tracking
sys
> On April 10, 2021 at 5:53 PM laurent aerens wrote:
>
>
> Package: unknown
>
> Version: debian 9 - 10
>
> Severity: minor
>
> When I type accent marks (¨^´`) in the terminal followed by a letter
> (that does not match with the accent) (for example ^ and the letter n)
>
Package: unknown
Version: debian 9 - 10
Severity: minor
When I type accent marks (¨^´`) in the terminal followed by a letter
(that does not match with the accent) (for example ^ and the letter n)
nothing happens and the keystrokes get ignored.
Typing an accent mark and a space allows you
. Contact me over the phone I don't teus this my isp +552122366155 +552121796156
i want them on jail for the rest of they life's what they did to me and other person here is unacceptable
Enviado via UOL Mail
_
Assunto: Re: Which package for bug report?
De
On 3/27/21, mshr wrote:
> Hello,
(...)
> Despite turning bluetooth off, it turns itself back on after the laptop
> wakes from sleep.
> I'm using the plasma desktop, installed from the initial installation media.
> What package should this bug relate to?
Hi, I suppose you should fi
Hello,
I'd like to report a bug for Debian testing (bullseye/sid).
Despite turning bluetooth off, it turns itself back on after the laptop wakes
from sleep.
I'm using the plasma desktop, installed from the initial installation media.
What package should this bug relate to?
Thank you.
On 21.03.2021 12:40, Andrei POPESCU wrote:
[Bcc: debian-boot]
Dear Debian-User subscribers,
The Release Notes editor is asking whether this is still an issue for
bullseye (i.e. if the patch to Debian Installer mentioned below was
applied in the meantime).
It will be a while until I get to
to do the same for 'emergency.service' as well (or
> instead), since this service is started *automatically* in case of
> certain errors (see systemd.special(7)) or if you add 'emergency' to the
> kernel command line (e.g. if you can't fix your system via the 'rescue'
> service).
&g
Hello,
I'm writing to you, because I don't know precisely what package is
responsible for bug- connman?, iw?,openresolv?
I've just installed Buster with mini.iso. Due to age of my PC and small
resources I tried to make my install as slim as possible.
So I went with Openbox and decided to use
On Sun, 14 Mar 2021 21:20:39 -0400
Jude DaShiell wrote:
> Why is frobtads missing from debian repositories? The frobtads package
> makes it possible for those living outside of g.u.i. land to play tads
> games on the console.
frobtads is in Debian non-free, in Sid and Jessie:
On Sun, Mar 14, 2021 at 21:20:39 -0400, Jude DaShiell wrote:
> Why is frobtads missing from debian repositories?
Looking at the tracker, the package is held back by "failure to build from
source" bugs, which are considered RC critical:
https://bugs.debian.org/cgi-bin/bugreport.c
Why is frobtads missing from debian repositories? The frobtads package
makes it possible for those living outside of g.u.i. land to play tads
games on the console.
On Sat, Mar 13, 2021 at 03:01:45AM -0500, Michael Grant wrote:
> > I'd say it is a Linode problem, unless you run custom kernel modules.
> > It looks like a "memory" corruption to me and since it is virtualized
> > system,
> > you should check if host system is ok.
> > Memory in quotes because
> I'd say it is a Linode problem, unless you run custom kernel modules.
> It looks like a "memory" corruption to me and since it is virtualized system,
> you should check if host system is ok.
> Memory in quotes because this issue could be also related to a storage
> sub-system (local or network
On 13.03.2021 11:31, Michael Grant wrote:
I'm seeing lots of errors like this in my kern.log on 2 of 3 of my
deban Linodes running testing on Linode's provided kerne 5.10.13. Is
this a problem in Debian or is this a Linode issue?
Mar 12 19:32:18 strange kernel: [10849.820363] BUG: Bad page
I'm seeing lots of errors like this in my kern.log on 2 of 3 of my
deban Linodes running testing on Linode's provided kerne 5.10.13. Is
this a problem in Debian or is this a Linode issue?
Mar 12 19:32:18 strange kernel: [10849.820363] BUG: Bad page state in process
kworker/0:3 pfn:10902f
Mar
gt; address failed with -5
>
>
> I wanted to file a bug but were discouraged because one should name the
> related package. Those who do not know the related package shall reach out to
> the mailing list.
>
> So here am I. Could you please help me to find out which package is
>
>
> > since 26th of February I have problems with the DisplayPort outputs
> > of my Lenovo ThinkPad T470p. If I use the notebooks output I can get
> > one external monitor to function but daisy chaining does not work. If
> > I use the output of the docking station, the external monitors do not
>
failed with -5
>
>
> I wanted to file a bug but were discouraged because one should name
> the related package. Those who do not know the related package shall
> reach out to the mailing list.
>
> So here am I. Could you please help me to find out which package is
> affected
.
At boot, betwenen GRUB and disk encryption, there is a error message that
reads relevant:
[drm:drm_dp_send_link_address [drm_kms_helper]] *ERROR* Sending link
address failed with -5
I wanted to file a bug but were discouraged because one should name the
related package. Those who do
On 3/3/2021 11:53 PM, Charles Curley wrote:
On Tue, 2 Mar 2021 18:47:16 +
Brian wrote:
Major improvement, thank you! I did have to answer some questions on
the way through, but did get a good connection.
Good. As I tried to indicate, the priority at which d-i is run affects
which
On Tue, 2 Mar 2021 18:47:16 +
Brian wrote:
> > Major improvement, thank you! I did have to answer some questions on
> > the way through, but did get a good connection.
>
> Good. As I tried to indicate, the priority at which d-i is run affects
> which questions are asked. Otherwise you get
On Tue 02 Mar 2021 at 10:45:54 -0700, Charles Curley wrote:
> On Tue, 2 Mar 2021 10:25:02 +
> Brian wrote:
>
> > I wonder if this line is sufficient? Based on what works for me at
> > priority critucal:
> >
> > d-i netcfg/wireless_show_essids select manual
> > d-i netcfg/wireless_essid
On Tue, 2 Mar 2021 10:25:02 +
Brian wrote:
> I wonder if this line is sufficient? Based on what works for me at
> priority critucal:
>
> d-i netcfg/wireless_show_essids select manual
> d-i netcfg/wireless_essid string Curleynet2
> d-i netcfg/wireless_security_type select wpa
> d-i
On Mon 01 Mar 2021 at 16:27:48 -0700, Charles Curley wrote:
[...]
> ### Description: Wireless network type for ${iface}:
> # Choose WEP/Open if the network is open or secured with WEP.
> # Choose WPA/WPA2 if the network is protected with WPA/WPA2 PSK
> # (Pre-Shared Key).
> # d-i
fails.
I have the syslog files from both a sucessful manual configuration and
from a failure, but have not attached them here.
So, is there an error in my preseed file, or have I hit a bug in d-i?
And if the latter, under what package should I file it?
Preseed wireless interfa
Ohh, this packages hasn't been update for so long.
If no objection, I will upload the current git snapshot.
Tiezhu Yang 于2021年2月24日周三 上午11:15写道：
>
> (1) Background
> Source: luajit
> Version: luajit_2.1.0~beta3+dfsg-5.3_mips64el.deb
> Severity: important
> Link:
(1) Background
Source: luajit
Version: luajit_2.1.0~beta3+dfsg-5.3_mips64el.deb
Severity: important
Link: https://packages.debian.org/sid/luajit
(2) Description of problem
When I build bcc, there exists the following build error:
[ 34%] Generating bcc.o
/usr/bin/luajit:
On Tue, 23 Feb 2021 22:19:03 +0100
Marco Möller wrote:
> Obviously, the in Step 2 entered (wrong) password (for "A") is stored
> and without further interactive consultation automatically used as
> the input for the password authentication of "B".
> Is this a
601 - 700 of 8562 matches
Mail list logo
