On Mon, Dec 11, 2023 at 04:31:22AM +0100, Stella Ashburne wrote:
> Hi Michael
>
> > Sent: Sunday, December 10, 2023 at 9:29 PM
> > From: "Michael Kjörling" <2695bd53d...@ewoof.net>
> > To: debian-user@lists.debian.org
> > Subject: Re: Need clarifications about how to deal with the installed
> > p
On Mon, Dec 11, 2023 at 03:32:55AM +0100, Stella Ashburne wrote:
> Hi Greg
>
> > Sent: Sunday, December 10, 2023 at 11:08 PM
> > From: "Greg Wooledge"
> > To: debian-user@lists.debian.org
> > Subject: Re: Need clarifications about how to deal with the installed
> > problematic kernel, linux-imag
Hello everybody
I can confirm the same problems. At first I thought the network problem
was due to proprietary Broadcom driver because network connectivity was
the most obvious problem.
However, most problems persisted after removing the driver. I do not
have any other proprietary or custom kerne
Hi Greg
> Sent: Monday, December 11, 2023 at 11:27 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
>
> Well, the question is what you want.
*snip* *
On Mon, Dec 11, 2023 at 04:31:22AM +0100, Stella Ashburne wrote:
> Someone on a social media platform stated that there are only two "canonical"
> [sic] ways to verify the version of Debian installed on a system. They are:
>
> uname -a
>
> /proc/version
>
> Do you agree with the above statement
> Sent: Monday, December 11, 2023 at 11:05 AM
> From: "Yves Bellefeuille"
> To: debian-user@lists.debian.org
> Subject: Re: Debian 12.3 image release delayed
>
> Is the problem solved? Is it safe to upgrade?
According to Steve McIntyre, it is.
Click the following link to read his announcement:
Hi Michael
> Sent: Sunday, December 10, 2023 at 9:29 PM
> From: "Michael Kjörling" <2695bd53d...@ewoof.net>
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
>
> This combinatio
On Mon, Dec 11, 2023 at 02:53:07AM +, Albretch Mueller wrote:
> echo "abc123" > file.txt
> ftype=$(file --brief file.txt)
> echo "// __ \$ftype: |${ftype}|"
> ftypelen=${#ftype}
> echo "// __ \$ftypelen: |${ftypelen}|"
>
> # removing spaces ...
> ftype2=$(echo "${ftype}" | tr --complement --sq
I was expecting a follow-up to yesterday's announcement that the 12.3
image had a data corruption bug.
Is the problem solved? Is it safe to upgrade?
--
Yves Bellefeuille
On Mon, Dec 11, 2023 at 03:26:16AM +0100, Stella Ashburne wrote:
> What command did you use? Was it
>
> sudo dpkg -i linux-image-amd64_6.1.55-1_amd64.deb
Yes.
On Mon, Dec 11, 2023 at 03:32:55AM +0100, Stella Ashburne wrote:
> As of writing this reply, there's a new point release, 12.4.0
>
> Wha
echo "abc123" > file.txt
ftype=$(file --brief file.txt)
echo "// __ \$ftype: |${ftype}|"
ftypelen=${#ftype}
echo "// __ \$ftypelen: |${ftypelen}|"
# removing spaces ...
ftype2=$(echo "${ftype}" | tr --complement --squeeze-repeats
'[A-Za-z0-9.]' '_');
echo "// __ \$ftype2: |${ftype2}|"
ftype2len=${
On 11/12/2023 06:12, Charles Curley wrote:
Sorry. I had already stopped the apt-daily-upgrade.timer, which
triggers the unattended upgrade service. (The couldn't give them
similar names to act as a mnemonic?) This refers to disabling the
unattended upgrade service.
I have not tested it, but fr
Hi Greg
> Sent: Sunday, December 10, 2023 at 11:08 PM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
>
> Note that purging 6.1.0-14 will also remove t
Hi Greg
> Sent: Monday, December 11, 2023 at 2:06 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
>
> In order to avoid having to remember to re-ins
Hi guys
> Sent: Monday, December 11, 2023 at 9:17 AM
> From: "Steve McIntyre" <93...@debian.org>
> To: debian-user@lists.debian.org
> Subject: 12.4.0 point release published
>
> Hi folks,
>
> The new 12.4.0 point release is now out. It contains the needed fixes
> for the ext4 data corruption bug (
wrote:
> On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
>> wrote:
there is rarely a need to e-mail me directly.
>> ...
>> > That's why I cringe when people name executables "foo.sh". What do you
>> > do when you decide to rewrite the thing in C (or Rust, or whatever)?
>> >
>> > Do
Hi folks,
The new 12.4.0 point release is now out. It contains the needed fixes
for the ext4 data corruption bug (https://bugs.debian.org/1057843).
It's now safe to upgrade as normal, panic over.
Many thanks to all the people who spent all of their weekend making
this happen...
--
Steve McInty
Dan Ritter wrote:
> Stefan Monnier wrote:
>> On my trusty Thinkpad X30, upgrades are sufficiently taxing that having
>> them run unexpectedly can be a real problem, so I tried to prevent
>> unattended upgrades a few months ago.
>
>
> I have always preferred the apticron package, which by default
>
> Finally, occasionally I need to cleanly dump html, this one seems a bit
> simpler:
>
> text/html; lynx -stdin -dump -width=$COLS; copiousoutput; compose=vim %s
I meant "cleanly _view_ html ..."
On 12/10/23 15:48, Stephen P. Molnar wrote:
On 12/10/2023 01:22 PM, gene heskett wrote:
On 12/10/23 10:47, Stephen P. Molnar wrote:
I have just reinstalled Bookworm.
Unfortunately, when I tru tto use synaptic I get the following error:
E: The package brscan4 needs to be reinstalled, but I c
On Sun, 10 Dec 2023 17:27:39 -0500
Greg Wooledge wrote:
> >
> > Thanks. I will disable as well.
>
> Disable *what*? Disabling a .service unit which is triggered by a
> timer event isn't going to stop it from running.
Sorry. I had already stopped the apt-daily-upgrade.timer, which
triggers t
> Second, how do I fix this so that mutt uses feh to display images?
Here is my mailcap entry, which works for me - had to deal with
annoying filename munging by mutt, and getting the "close the viewer"
bit working - this is quite a few years ago and now I can't even
remember why the ; test=test -
I confirm that 6.1.66-1 (6.1.0-15) severely breaks my
amd64/bookworm/gnome physical machine, which runs fine with 6.1.52-1 and
6.1.55-1.
Am 10.12.23 um 20:24 schrieb Andrew M.A. Cater:
> On Sun, Dec 10, 2023 at 08:02:03PM +0100, Kevin Price wrote:
>> Am 09.12.23 um 19:09 schrieb Dan Ritter:
>>> Th
On Sun, Dec 10, 2023 at 02:10:43PM -0700, Charles Curley wrote:
> On Sun, 10 Dec 2023 14:51:48 -0600
> David Wright wrote:
>
> > I think it might be worth googling and reading "three levels of off"
> > (with the quotes).
> >
> > 1. You can stop a service. That simply terminates the running
> >
On Sun, Dec 10, 2023 at 02:27:38PM -0700, Charles Curley wrote:
> On Sat, 9 Dec 2023 13:09:23 -0500
> Dan Ritter wrote:
>
> > https://fulda.social/@Ganneff/111551628003050712
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
> >
> > The new kernel release is reported to contain
On Sat, 9 Dec 2023 13:09:23 -0500
Dan Ritter wrote:
> https://fulda.social/@Ganneff/111551628003050712
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843
>
> The new kernel release is reported to contain an ext4 data
> corruption bug. It's prudent not to upgrade, or if you have
> sta
On Sun, 10 Dec 2023 14:51:48 -0600
David Wright wrote:
> I think it might be worth googling and reading "three levels of off"
> (with the quotes).
>
> 1. You can stop a service. That simply terminates the running
> instance of the service and does little else. If due to some form
> o
Stefan Monnier wrote:
> On my trusty Thinkpad X30, upgrades are sufficiently taxing that having
> them run unexpectedly can be a real problem, so I tried to prevent
> unattended upgrades a few months ago.
I have always preferred the apticron package, which by default
updates daily and sends an e
On Sun 10 Dec 2023 at 13:39:50 (-0700), Charles Curley wrote:
> On Sun, 10 Dec 2023 14:17:36 -0600
> David Wright wrote:
>
> > Why is the service loaded, enabled and enabled then? Don't you need
> > to disable or mask it? Presumably it sits there, dead, all day
> > normally, and pops up at an app
Sent from my iPad
> On Dec 10, 2023, at 3:05 PM, David Wright wrote:
>
> On Fri 08 Dec 2023 at 16:29:12 (-0500), Paul M Foster wrote:
>>> On Fri, Dec 08, 2023 at 11:04:54AM -0600, David Wright wrote:
>>> On Fri 08 Dec 2023 at 11:56:12 (-0500), Paul M Foster wrote:
I'm on Debian boo
On 12/10/2023 01:22 PM, gene heskett wrote:
On 12/10/23 10:47, Stephen P. Molnar wrote:
I have just reinstalled Bookworm.
Unfortunately, when I tru tto use synaptic I get the following error:
E: The package brscan4 needs to be reinstalled, but I can't find an
archive for it.
E: Internal er
On Sun, 10 Dec 2023 14:17:36 -0600
David Wright wrote:
> Why is the service loaded, enabled and enabled then? Don't you need
> to disable or mask it? Presumably it sits there, dead, all day
> normally, and pops up at an appropriate time.
As I understand things, start and stop are for immediate c
On Sun 10 Dec 2023 at 11:00:37 (-0700), Charles Curley wrote:
> On Sun, 10 Dec 2023 16:11:44 +
> Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>
> > On 10 Dec 2023 08:49 -0700, from charlescur...@charlescurley.com
> > (Charles Curley): [...]
> >
> > Exactly how did you "shut down" unatte
On Sun 10 Dec 2023 at 19:48:29 (+0100), to...@tuxteam.de wrote:
> On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> > wrote:
> > ...
> > > That's why I cringe when people name executables "foo.sh". What do you
> > > do when you decide to rewrite the thing in C (or Rust, or whatever)?
> >
On Fri 08 Dec 2023 at 16:29:12 (-0500), Paul M Foster wrote:
> On Fri, Dec 08, 2023 at 11:04:54AM -0600, David Wright wrote:
> > On Fri 08 Dec 2023 at 11:56:12 (-0500), Paul M Foster wrote:
> > >
> > > I'm on Debian bookworm, using neomutt for email. Where there is an image
> > > to
> > > view, v
Please start new threads when sidelining into silly arguments.
The "IMPORTANT: do NOT upgrade" thread is getting cluttered with
useless junk making it hard to determine the current status of the
problem.
Also, use a new thread, don't just change the subject line. Some
threading mail readers foll
On Sun, Dec 10, 2023 at 01:36:52PM -0600, Nicholas Geovanis wrote:
> On Sun, Dec 10, 2023, 12:47 PM Curt wrote:
[...]
> > It is the notion of simultaneity itself (the now of now) that is
> > relative rather than universal.
> >
>
> I thought metaphysics was off-topic for this group. Moderators!!
On Sun, Dec 10, 2023, 12:47 PM Curt wrote:
> On 2023-12-10, Gary Dale wrote:
> >
> > On 2023-12-10 12:24, Greg Wooledge wrote:
> >> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> >>> On 2023-12-10, Andrew M.A. Cater wrote:
> "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
> >
On Sun, Dec 10, 2023 at 08:02:03PM +0100, Kevin Price wrote:
> Am 09.12.23 um 19:09 schrieb Dan Ritter:
> > The new kernel release is reported to contain an ext4 data
> > corruption bug. It's prudent not to upgrade, or if you have
> > started to upgrade, not to reboot, until a new kernel release
>
Am 09.12.23 um 19:09 schrieb Dan Ritter:
> The new kernel release is reported to contain an ext4 data
> corruption bug. It's prudent not to upgrade, or if you have
> started to upgrade, not to reboot, until a new kernel release
> is prepared.
Thanks for your announcement. I'm running out of time t
On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> wrote:
> ...
> > That's why I cringe when people name executables "foo.sh". What do you
> > do when you decide to rewrite the thing in C (or Rust, or whatever)?
> >
> > Do you go over all calling sites and change the caller's code?
>
>
On 2023-12-10, Gary Dale wrote:
>
> On 2023-12-10 12:24, Greg Wooledge wrote:
>> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
>>> On 2023-12-10, Andrew M.A. Cater wrote:
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
>>> You mean in the Zulu Time Zone (as I am all at sea)?
>>
wrote:
...
> That's why I cringe when people name executables "foo.sh". What do you
> do when you decide to rewrite the thing in C (or Rust, or whatever)?
>
> Do you go over all calling sites and change the caller's code?
no, i would just consider it a transition or a change
in versions. :)
On 2023-12-10 11:56, Andrew M.A. Cater wrote:
On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote:
On 2023-12-09 14:18, Michael Kjörling wrote:
On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou):
I just upgraded to Bookworm this morning. I did reboot a couple of
times b
On 12/10/23 10:47, Stephen P. Molnar wrote:
I have just reinstalled Bookworm.
Unfortunately, when I tru tto use synaptic I get the following error:
E: The package brscan4 needs to be reinstalled, but I can't find an
archive for it.
E: Internal error opening cache (1). Please report.
Unfortun
On Sun, 10 Dec 2023 23:59:04 +0700
Max Nikulin wrote:
> On 10/12/2023 22:49, Charles Curley wrote:
> [...]
>
> systemctl status apt-daily-upgrade.timer
>
root@issola:~# systemctl status apt-daily-upgrade.timer
● apt-daily-upgrade.timer - Daily apt upgrade and clean activities
Loaded: l
On Sun, Dec 10, 2023 at 10:08:21AM -0500, Greg Wooledge wrote:
> On Sun, Dec 10, 2023 at 01:41:14PM +, Andrew M.A. Cater wrote:
> > That will work: you might also want to apt-get purge
> > linux-image-6.1.0-14-amd64
> > but you've done the main thing.
>
> Note that purging 6.1.0-14 will also
On Sun, 10 Dec 2023 16:11:44 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> On 10 Dec 2023 08:49 -0700, from charlescur...@charlescurley.com
> (Charles Curley): [...]
>
> Exactly how did you "shut down" unattended-upgrades?
>
root@chaffee:/etc/dhcp# systemctl stop unattended-upgrade
On 2023-12-10 12:24, Greg Wooledge wrote:
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
On 2023-12-10, Andrew M.A. Cater wrote:
"Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
You mean in the Zulu Time Zone (as I am all at sea)?
Use "date -u" to see current UTC time. That sho
Hello,
Am 10.12.2023 um 17:58 schrieb Stephen P. Molnar:
I appreciated the suggestion, but it didn't solve the problem with
Synaptic.
On 12/10/2023 11:03 AM, Arno Lehmann wrote:
Hi all,
Am 10.12.2023 um 16:53 schrieb to...@tuxteam.de:
On Sun, Dec 10, 2023 at 10:47:09AM -0500, Stephen P. Mo
Andy writes:
> This fails with leap seconds, potentially, and also TAI astronomical
> time seems to be its own animal.
TAI isn't good enough for the astronomers.
https://en.wikipedia.org/wiki/Terrestrial_Time
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On Sun, Dec 10, 2023 at 05:20:40PM +, Andrew M.A. Cater wrote:
> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> > On 2023-12-10, Andrew M.A. Cater wrote:
> > >
> > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
> >
> > You mean in the Zulu Time Zone (as I am all at sea)?
> >
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> On 2023-12-10, Andrew M.A. Cater wrote:
> >
> > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
>
> You mean in the Zulu Time Zone (as I am all at sea)?
Use "date -u" to see current UTC time. That should be sufficient to
let you know
> I double checked this morning. All machines had unattended upgrades
> shut off as of yesterday evening, well before the
> unattended-uogrades ran.
On my trusty Thinkpad X30, upgrades are sufficiently taxing that having
them run unexpectedly can be a real problem, so I tried to prevent
unattende
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote:
> On 2023-12-10, Andrew M.A. Cater wrote:
> >
> > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
>
> You mean in the Zulu Time Zone (as I am all at sea)?
>
> > Andy
> > (amaca...@debian.org)
> >
> >
>
Not this again :) GMT (was) the
to...@tuxteam.de [2023-12-10 17:47:41] wrote:
> You ssh in as root (or serial port)?
I do over the serial port, but over SSH, I always login as myself first
and then `su -` to root.
> Perhaps it's a "user session" thingy playing games on you?
Could be,
Stefan
On 2023-12-10, Andrew M.A. Cater wrote:
>
> "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023
You mean in the Zulu Time Zone (as I am all at sea)?
> Andy
> (amaca...@debian.org)
>
>
On 10/12/2023 22:49, Charles Curley wrote:
root@issola:/var# systemctl status unattended-upgrades.service
systemctl status apt-daily-upgrade.timer
I appreciated the suggestion, but it didn't solve the problem with Synaptic.
On 12/10/2023 11:03 AM, Arno Lehmann wrote:
Hi all,
Am 10.12.2023 um 16:53 schrieb to...@tuxteam.de:
On Sun, Dec 10, 2023 at 10:47:09AM -0500, Stephen P. Molnar wrote:
I have just reinstalled Bookworm.
Unfortunatel
On 2023-12-10, wrote:
>
>
> On Sun, Dec 10, 2023 at 06:04:05PM +0200, y...@vienna.at wrote:
>>
>> ! Missing number, treated as zero.
>>
>> \protect
>> l.59 ...reMathSymbol\mho {\mathord}{lasy}{"30}
>> "
>> uppsi
>> what does thar mean?
>
> That TeX was expecting a number at some place and f
On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote:
> On 2023-12-09 14:18, Michael Kjörling wrote:
> > On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou):
> > > I just upgraded to Bookworm this morning. I did reboot a couple of
> > > times but there seems to be no problem (
On 2023-12-09 14:18, Michael Kjörling wrote:
On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou):
I just upgraded to Bookworm this morning. I did reboot a couple of
times but there seems to be no problem (yet). Is there anything I
should look for or do other than rebooting?
If
On Sun, Dec 10, 2023 at 04:40:20PM +, Eric S Fraga wrote:
> On Sunday, 10 Dec 2023 at 18:22, y...@vienna.at wrote:
> > There is nothing like \mho 0r /mho or {\mho} anywhere in the text
>
> That may be but it was in the snippet of the error message you posted.
> Maybe post more context
Ye
On Sun, Dec 10, 2023 at 11:42:42AM -0500, Stefan Monnier wrote:
> Stanislav Vlasov [2023-12-10 21:16:54] wrote:
> > In /media/ disks mounts by GUI. Stefan use root in gui login.
>
> Except:
> - I never do a "GUI login" as root.
> - "This is on a headless ARM board running Debian stable".
> I acc
Stanislav Vlasov [2023-12-10 21:16:54] wrote:
> In /media/ disks mounts by GUI. Stefan use root in gui login.
Except:
- I never do a "GUI login" as root.
- "This is on a headless ARM board running Debian stable".
I access it via SSH (and occasionally serial port).
Stefan
On Sunday, 10 Dec 2023 at 18:22, y...@vienna.at wrote:
> There is nothing like \mho 0r /mho or {\mho} anywhere in the text
That may be but it was in the snippet of the error message you posted.
Maybe post more context (e.g. line in your actual LaTeX where error
occurs) and/or ask on a LaTeX l
Max Nikulin [2023-12-10 21:49:46] wrote:
> On 10/12/2023 02:49, Stefan Monnier wrote:
>> "magically" mounted as
>> `/media/root/`.
> [...]
>> Any idea who/what does that, and how/where I can control it?
>
> This path is used by udisks, however I am unsure what may cause
> automounting for root.
>
>
On Sun, Dec 10, 2023 at 04:15:22PM -, Curt wrote:
> On 2023-12-09, Eric S Fraga wrote:
> > On Friday, 8 Dec 2023 at 17:06, Pocket wrote:
> >> In Unix and Linux there isn't a file extension, that is a microsoft
> >> invention.
> >
> > Predates MS by years. Systems like RSTS/E on PDP-11s, just
On Sun, 10 Dec 2023 16:11:22 +
Eric S Fraga wrote:
Untested but shouldn't the \mho be within braces, {\mho}?
--
Eric S Fraga via gnus (Emacs 30.0.50 2023-09-14) on Debian 12.2
There is nothing like \mho 0r /mho or {\mho} anywhere in the text
2023-12-10 19:49 GMT+05:00, Max Nikulin :
> On 10/12/2023 02:49, Stefan Monnier wrote:
>> "magically" mounted as
>> `/media/root/`.
> [...]
>> Any idea who/what does that, and how/where I can control it?
>
> This path is used by udisks, however I am unsure what may cause
> automounting for root.
>
On 2023-12-09, Eric S Fraga wrote:
> On Friday, 8 Dec 2023 at 17:06, Pocket wrote:
>> In Unix and Linux there isn't a file extension, that is a microsoft
>> invention.
>
> Predates MS by years. Systems like RSTS/E on PDP-11s, just to name one.
They certainly are convenient.
I must be stupid o
On 10 Dec 2023 08:49 -0700, from charlescur...@charlescurley.com (Charles
Curley):
> Due to the recent traffic about the defective kernel in Bookworm
> (12.3), I shut down unattended-upgrades on all my machines (Bookworm
> and Bullseye). To my surprise, three of them ran unattended-upgrades
> anyw
Untested but shouldn't the \mho be within braces, {\mho}?
--
Eric S Fraga via gnus (Emacs 30.0.50 2023-09-14) on Debian 12.2
On Sun, Dec 10, 2023 at 06:04:05PM +0200, y...@vienna.at wrote:
> "
>
> ! Missing number, treated as zero.
>
> \protect
> l.59 ...reMathSymbol\mho {\mathord}{lasy}{"30}
> "
> uppsi
> what does thar mean?
That TeX was expecting a number at some place and found something
else (probably this \pr
"
! Missing number, treated as zero.
\protect
l.59 ...reMathSymbol\mho {\mathord}{lasy}{"30}
"
uppsi
what does thar mean?
Hi all,
Am 10.12.2023 um 16:53 schrieb to...@tuxteam.de:
On Sun, Dec 10, 2023 at 10:47:09AM -0500, Stephen P. Molnar wrote:
I have just reinstalled Bookworm.
Unfortunately, when I tru tto use synaptic I get the following error:
E: The package brscan4 needs to be reinstalled, but I can't find
On Sun, Dec 10, 2023 at 10:47:09AM -0500, Stephen P. Molnar wrote:
> I have just reinstalled Bookworm.
>
> Unfortunately, when I tru tto use synaptic I get the following error:
>
> E: The package brscan4 needs to be reinstalled, but I can't find an archive
> for it.
brscan4 is not in the officia
On 9 Dec 2023, at 19:18, Michael Kjörling wrote:
> If you are on 6.1.55-1 (or earlier), just hold off on
> upgrades for now; and if you need to upgrade something else, take
> great care for now to ensure that no Linux kernel packages get
> upgraded to any version < 6.1.66, and preferably not < 6.1
Due to the recent traffic about the defective kernel in Bookworm
(12.3), I shut down unattended-upgrades on all my machines (Bookworm
and Bullseye). To my surprise, three of them ran unattended-upgrades
anyway.
One of them is Bullseye, so it was a harmless error. But still….
The two Bookworm mach
I have just reinstalled Bookworm.
Unfortunately, when I tru tto use synaptic I get the following error:
E: The package brscan4 needs to be reinstalled, but I can't find an
archive for it.
E: Internal error opening cache (1). Please report.
Unfortunately, Google has not been of any help.
A so
On Sun, Dec 10, 2023 at 01:41:14PM +, Andrew M.A. Cater wrote:
> That will work: you might also want to apt-get purge
> linux-image-6.1.0-14-amd64
> but you've done the main thing.
Note that purging 6.1.0-14 will also remove the linux-image-amd64
metapackage, which has a hard dependency on it
On 10/12/2023 02:49, Stefan Monnier wrote:
"magically" mounted as
`/media/root/`.
[...]
Any idea who/what does that, and how/where I can control it?
This path is used by udisks, however I am unsure what may cause
automounting for root.
I would check
udisksctl dump
udevadm info --q
On Sat, Dec 9, 2023, 1:50 PM Stefan Monnier
wrote:
> Recently I noticed some unused ext4 filesystems (i.e. filesystems that
> aren't in /etc/fstab, that I normally don't mount, typically because
> they're snapshots or backups) "magically" mounted as
> `/media/root/`.
>
> This is on a headless ARM
On Sun, Dec 10, 2023 at 02:38:34PM +0100, Mario Marietto wrote:
> Hello to everyone.
>
> I'm using Devuan 5 for arm32 on my ARM chromebook and I've just tried to
> update the system,but I failed.
>
Hi Mario,
You're on your own for two reasons: one is that relatively few of us
will be running on
Am 10.12.2023 um 14:38:34 Uhr schrieb Mario Marietto:
> http://deb.devuan.org/merged/dists/daedalus-updates/InRelease is not
> valid yet (invalid for another 8744d 7h 58min 21s). Updates for this
> repository will not be applied.
Is your date correct on your machine?
On Sun, Dec 10, 2023 at 01:48:52PM +0100, Stella Ashburne wrote:
> Hi,
>
> I am using Debian Bookworm, the current stable release with the whole SSD
> being encrypted with LUKS2. After decryption, the file system of the logical
> volume is ext4.
>
> This is what happened to my computer many hou
Hello to everyone.
I'm using Devuan 5 for arm32 on my ARM chromebook and I've just tried to
update the system,but I failed.
This is the sources.list file that I'm using :
deb http://pkg.bunsenlabs.org/debian beryllium main
deb http://deb.devuan.org/merged daedalus main
deb http://deb.d
On 10 Dec 2023 13:48 +0100, from rewe...@gmx.com (Stella Ashburne):
> I highlight linux-image-6.1.0-13-amd64 and press Enter.
>
> After supply the decryption password and entering my desktop
> environment, I did the following:
>
> cat /etc/debian_user
> *Result* is 12.3, even though I boot using
Hi,
I am using Debian Bookworm, the current stable release with the whole SSD being
encrypted with LUKS2. After decryption, the file system of the logical volume
is ext4.
This is what happened to my computer many hours ago.
My device upgraded to the latest kernel, linux-image-6.1.0-14-amd64 an
I have installed Debian Bookworm on X13 with AMD Ryzen 7840U and
microphone is not working. It shows inactive.
I use KDE and installed pipewire. The mic did not work since base install.
Any advise?
$ inxi -A Audio: Device-1: AMD Rembrandt Radeon High Definition Audio
driver: snd_hda_intel Dev
90 matches
Mail list logo
