Here are some foreseeable and preventable ones.
> AFAICT the only thing really different about "the bug"
> (#1057967/#1057969) is that it comes right after a bug that made a lot
> of noise (bug#1057843), so people have temporarily lost faith.
No faith lost on my part. And bug
x system, like all sufficiently
complex software systems, is chuck full of bugs, many of which can
indeed have disastrous effects if they manifest under the
"right" circumstances.
AFAICT the only thing really different about "the bug"
(#1057967/#1057969) is that it comes right after a
;> ...but that one most probably won't be attached via a Broadcom to the 'net.
Tomas: Servers are most usually not connected through wifi alone. But
"the bug" (#1057967/#1057969) won't only disable the wifi adapter, but
would probably make the running computer largely u
On Wed, Dec 13, 2023 at 10:33:15AM -0500, Greg Wooledge wrote:
[...]
> Perhaps I'm reading it incorrectly, but I still feel it's wise to wait
> a little while and see if any more problems pop up, if stability is
> important to you. I also salute the courage of those who've tested
> these recent
On Wed, 2023-12-13 at 10:10 -0500, Greg Wooledge wrote:
> If it's a remote server to which you have limited
> or no physical access, booting a kernel that may "just be unusable"
> (enough to prevent editing GRUB menus and rebooting) could be a disaster.
Which is what happened a few years ago to me
t.
Who knows, though :)
My superficial understanding, after skimming through the bug report,
is that problems could be triggered just by *loading* one of the
affected wifi driver modules. This would happen for any machine that
has one of the "right" kinds of wifi hardware, even if t
oting) could be a disaster.
>
> ...but that one most probably won't be attached via a Broadcom to the 'net.
>
> Who knows, though :)
My superficial understanding, after skimming through the bug report,
is that problems could be triggered just by *loading* one of the
affected
On Wed, Dec 13, 2023 at 10:10:37AM -0500, Greg Wooledge wrote:
> On Wed, Dec 13, 2023 at 09:56:46AM -0500, Stefan Monnier wrote:
> > If so, then IIUC the answer is a resounding "YES, it is safe!".
> > It just may be unusable, so you may have to downgrade to 6.1.0-13 until
> > the problem is fixed.
On Wed, Dec 13, 2023 at 09:56:46AM -0500, Stefan Monnier wrote:
> If so, then IIUC the answer is a resounding "YES, it is safe!".
> It just may be unusable, so you may have to downgrade to 6.1.0-13 until
> the problem is fixed.
>
> That's a very different issue from the ext4 corruption problem in
gt; Though unless I'm misunderstanding, just having a wi-fi (used or not) is
>> > > enough to trigger the bug. Please correct me if I'm wrong.
>> >
>> > "the bug"?
>> >
>> > What's this bug you're referring to?
>>
On 13 Dec 2023 16:23 +0900, from j...@bunsenlabs.org (John Crawley):
>> |Debian Bug report logs - #1057967
>> |Found in version linux/6.1.66-1
>> |Fixed in version linux/6.1.67-1
>
> Good to know, but as of now (Wed 13 Dec 07:20:59 UTC 2023):
> [...]
> Have to wait a few more hours I suppose.
It
On 13/12/2023 15:24, Geert Stappers wrote:
An attempt to get beyond FUD
|Debian Bug report logs - #1057967
|linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely
unusable version graph
|Package: src:linux; Maintainer for src:linux is Debian Kernel Team
;
|Affects: src:
it.
> > > > Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> > > > enough to trigger the bug. Please correct me if I'm wrong.
> > >
> > > "the bug"?
> > >
> > > What's this b
used or not) is
> > > enough to trigger the bug. Please correct me if I'm wrong.
> >
> > "the bug"?
> >
> > What's this bug you're referring to?
>
> Perhaps:
>
> https://lists.debian.org/debian-user/2023/12/msg
Can anyone please explain:
1. Why upgrades of stable into a potentially seriously compromised state were
allowed to continue, twice, rather than pulling the upgrades? or...
2. Why the best temporary solution isn't to revert the kernel to the last known
good version so upgrades-other-than-kernel
On Tue 12 Dec 2023 at 23:05:49 (-0500), Stefan Monnier wrote:
> > Well, the machine in question has a wi-fi but I don't plan on using it.
> > Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> > enough to trigger the bug. Please correct me
> Well, the machine in question has a wi-fi but I don't plan on using it.
> Though unless I'm misunderstanding, just having a wi-fi (used or not) is
> enough to trigger the bug. Please correct me if I'm wrong.
"the bug"?
What's this bug you're referring to?
Stefan
It is a MATE problem regrading two, possibly related issues. I was thinking
mate-desktop-environment, but maybe that is wrong. Maybe it is
mate-desktop-common or something else.
It has to do with:
(1) the panel placement; Limits on which displays it allows me to place the
panel; and,
(2) the i
On Thu, 05 Oct 2017, Sergey Storm wrote:
> Hello. I have a problem with keyboard input and I don't know what
> package the bug is in. Bugreport gave me this email address for
> assistance. Help me please.
> I use two languages and switch them using ctrl+shift. But combinations
Hello. I have a problem with keyboard input and I don't know what package
the bug is in. Bugreport gave me this email address for assistance. Help me
please.
I use two languages and switch them using ctrl+shift. But combinations
ctrl+shift+'any letter' do not correctly work either
he symptom, then we wouldn't improve Linux user
space. We only could fix a bug by knowing the bug. Just manipulating the
hardware is not a good way. The easiest way perhaps is to compare the
running services and software versions from a Suse install, that doesn't
cause this issue, with the
ipplan-*/debian/postinst needs some love :-)
I guess it is outdated and should be fixed.
This requires knowlage of ucf and debconf
(see man ucf)
2012/7/21 Gary Dale :
> On 21/07/12 01:12 PM, vykuntam srinivas wrote:
>
> hi all,
>
> i am trying fix the bug #618388 of ipplan .
On Sat, 21 Jul 2012 22:42:58 +0530, vykuntam srinivas wrote:
> hi all,
Hi, but please, *no html posts*, re-thanks...
(...)
> *Selecting previously unselected package ipplan. (Reading database ...
> 138089 files and directories currently installed.)* * Unpacking ipplan
> (from ipplan_4.92a-2.1_a
On 21/07/12 01:12 PM, vykuntam srinivas wrote:
hi all,
i am trying fix the bug #618388
<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618388> of ipplan .I
installed the missing package ( libphp-phplayersmenu which was
mentioned in the bug),After that i had installed ipplan.
hi all,
i am trying fix the bug
#618388<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618388>of
ipplan .I installed the missing package ( libphp-phplayersmenu
which
was mentioned in the bug),After that i had installed ipplan.At the time
of installation a blue window appeare
Julian Gilbey wrote:
Brief summary:
I have Debian testing installed on /dev/hda2, which is my default
startup option
I have Debian unstable installed on /dev/hda3
I have Windows installed on /dev/hda1
I am using grub, installed on the MBR of /dev/hda (and I installed it
from the testing version
Before I report this bug, I'd like to hear an opinion on whether this
is likely to be:
(1) a bug in grub
(2) a bug in some kernel
(3) a silly user error (in which case I'll go fix it and pretend this
never happened!)
Brief summary:
I have Debian testing installed on /dev/hda2, which is my def
27 matches
Mail list logo
