On 27/08/2024 00:08, Tim Woodall wrote:
The emails
to control and to the bugs themselves all worked, it's only the emails
to the subscribe address that seem to have vanished.
It precisely describes my experience as well.
On Mon, 26 Aug 2024, Jonathan Dowland wrote:
On Mon Aug 26, 2024 at 9:08 AM BST, Tim Woodall wrote:
Is there some magic needed to subscribe to bug updates?
…
I've managed to do this in the past. Not sure what I've done wrong or
has changed.
Can you outline what you tried
On Mon Aug 26, 2024 at 9:08 AM BST, Tim Woodall wrote:
> Is there some magic needed to subscribe to bug updates?
…
> I've managed to do this in the past. Not sure what I've done wrong or
> has changed.
Can you outline what you tried this time?
--
Please do not CC me
Is there some magic needed to subscribe to bug updates?
I added patches for three trixie RC bugs at the weekend and tried to
subscribe to uodates but I didn't get the subscribe confirmation email.
Do I need the word subscribe in subject or body perhaps?
debian.org/Bugs/Developer says su
Recent Windows updates caused certain bootloaders to make the blacklist, I
just had an argument that went like: why wasn't there a shim update when MS
announced this in April?
And then someone kept insisting that when the Secure Boot feature was designed
Linux distributors did not na
This is known issue in the apt-mirror [1]
You can use apt-mirror2 [2] which fixes all known apt-mirror issues
[1] https://github.com/apt-mirror/apt-mirror/issues/144
[2] https://gitlab.com/apt-mirror2/apt-mirror2
--
Best regards, Yuri Konotopov
On Mon, Jun 3, 2024 at 8:52 PM wrote:
> On 6/3/24 09:40, Tom Browder wrote:
> > I keep getting emails concerning the serious kernel vulnerability in
> > kernels 5.14 through 6.6.
> >
> > I have not seen any updates and uname -a shows: 6.1.0-13-amd64
> On 6/3/24 0
On 6/3/24 15:06, Greg Wooledge wrote:
On Mon, Jun 03, 2024 at 02:18:40PM -0400, e...@gmx.us wrote:
eben@cerberus:~$ apt-cache policy linux-image-amd64
linux-image-amd64:
Installed: (none)
Candidate: 6.1.90-1
What am I doing wrong?
You haven't installed the linux-image-amd64 metapackag
On Mon, Jun 03, 2024 at 02:18:40PM -0400, e...@gmx.us wrote:
> eben@cerberus:~$ apt-cache policy linux-image-amd64
> linux-image-amd64:
> Installed: (none)
> Candidate: 6.1.90-1
> What am I doing wrong?
You haven't installed the linux-image-amd64 metapackage, which means
you will not be offer
On 6/3/24 09:40, Tom Browder wrote:
I keep getting emails concerning the serious kernel vulnerability in
kernels 5.14 through 6.6.
I have not seen any updates and uname -a shows: 6.1.0-13-amd64
On 6/3/24 09:40, Tom Browder wrote:
I keep getting emails concerning the serious kernel
On 3 Jun 2024 11:29 -0500, from tom.brow...@gmail.com (Tom Browder):
> Thanks for your concern and help.
You're welcome. Glad you got it sorted.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
On Mon, Jun 3, 2024 at 09:15 Michael Kjörling <2695bd53d...@ewoof.net>
wrote:
> On 3 Jun 2024 08:40 -0500, from tom.brow...@gmail.com (Tom Browder):
> > I keep getting emails concerning the serious kernel vulnerability in
> > kernels 5.14 through 6.6.
> >
> > I ha
rity.debian.org bookworm-security/main amd64 Packages
> 100 /var/lib/dpkg/status
> 6.1.76-1 500
> 500 https://mirror.debian.example/debian bookworm/main amd64 Packages
> 6.1.67-1 500
> 500 https://mirror.debian.example/debian bookworm-updates/main amd6
On Mon, Jun 3, 2024 at 09:15 Michael Kjörling <2695bd53d...@ewoof.net>
wrote:
...
> > I have not seen any updates and uname -a shows: 6.1.0-13-amd64
>
...
> Something's broken on your end.
...
Check your apt pins to ensure that you're not
> blocking too much.
T
On 3 Jun 2024 08:40 -0500, from tom.brow...@gmail.com (Tom Browder):
> I keep getting emails concerning the serious kernel vulnerability in
> kernels 5.14 through 6.6.
>
> I have not seen any updates and uname -a shows: 6.1.0-13-amd64
Something's broken on your end.
Bookworm is
I keep getting emails concerning the serious kernel vulnerability in
kernels 5.14 through 6.6.
I have not seen any updates and uname -a shows: 6.1.0-13-amd64
Anyone concerned?
-Tom
my config file has a single repo
deb-src https://deb.debian.org/debian bookworm-updates main contrib non-free
non-free-firmware
the following is what i get
it seems the bookworm-updates sources file has no line "Files:"
apt-mirror@odroid2:~$ apt-mirror /etc/apt/mirror.list
Down
grub wrapper) was in fact never called during that update
sequence! (Therefore Gnome's handling of updates is off the hook.)
Perhaps it was because of some bad dkms and linux-headers interaction.
Some module failed to build, which cascaded into leaving the kernel and
headers packages int
Ds in all
> > menuentries, as expected.
> >
> > (Kernel were the two most recent stable ones: 6.1.0-17 and -18.)
> >
> > This leads me to suspect that my grub.cfg might have been damaged in the way
> > described above because update-grub might have been called in s
have been damaged in the way
> described above because update-grub might have been called in some unusual,
> limited execution environment. I'd very recently powered off my system and
> let the default "install pending software updates" option checked by
> accident, which
might have been damaged in the
way described above because update-grub might have been called in some
unusual, limited execution environment. I'd very recently powered off my
system and let the default "install pending software updates" option
checked by accident, which caused
In case of GNOME, you might try the following
gsettings set org.gnome.software download-updates false
(gnome-software used packagekitd internally)
OpenPGP_signature.asc
Description: OpenPGP digital signature
On 29/01/2024 04:24, Greg Wooledge wrote:
On Sun, Jan 28, 2024 at 03:57:30PM -0500, Stefan Monnier wrote:
systemctl mask packagekit
I don't think you're looking at the right thing. "packagekit" seems
to be an interface to dbus. By itself, it doesn't do what you think
it does.
Perhaps
UPDATE-INFO MIGHT HAVE
CHANGED
// Whenever dpkg is called we might have different updates
// i.e. if an user removes a package that had an update
DPkg::Post-Invoke {
"/usr/bin/test -e
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service &&
/usr/bin/test -S /var/run/dbus
Am So, Jan 28, 2024 at 16:31:02 -0500 schrieb Stefan Monnier:
the thing you don't want done. Is "unattended-upgrades" installed by
any chance?
Hmm yep, it is!
So that's it?
Well, you can look in /var/log/unattended-upgrades/ for the log files.
„dpkg-reconfigure unattended-upgrades” will
On Sun, Jan 28, 2024 at 04:31:02PM -0500, Stefan Monnier wrote:
> > There is probably some other package that's *using* packagekit to do
> > the thing you don't want done. Is "unattended-upgrades" installed by
> > any chance?
>
> Hmm yep, it is!
> So that's it?
> I self-inflicted this by inst
> I don't think you're looking at the right thing. "packagekit" seems
> to be an interface to dbus. By itself, it doesn't do what you think
> it does.
Aha!
> There is probably some other package that's *using* packagekit to do
> the thing you don't want done. Is "unattended-upgrades" installed
On Sun, Jan 28, 2024 at 03:57:30PM -0500, Stefan Monnier wrote:
> >> How can I stop those downloads?
> >>
> >> Currently, I did
> >>
> >> systemctl mask packagekit
I don't think you're looking at the right thing. "packagekit" seems
to be an interface to dbus. By itself, it doesn't do what
Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
#
which is why I masked it instead. In any case, I'd rather find a way to
say precisely what I mean (i.e. "don't download updat
On Sun, 28 Jan 2024 14:10:46 -0500
Stefan Monnier wrote:
> How can I stop those downloads?
>
> Currently, I did
>
> systemctl mask packagekit
Well, you might just get rid of the package.
apt purge packagekit
should do it.
Less drastic, to simply shut down the current daemon,
systemctl
Apparently, there's now a thing called `packagekit` whose daemon seems
to like to download updates "in the background" for me.
Thanks, but no, thanks. This tends to occur at inopportune times for me
and it's not far enough "in the background", so it gets in t
On 07.01.24 20:33, songbird wrote:
i see you've solved your issue, but i just wanted to
point out that it works and is ok for people who want to
try it out.
Says who?
Richard Rosner wrote:
> So, since for whatever reason Grub seems to be broken beyond repair, I
> today tried to just replace it with rEFInd. Installation succeeded
> without any trouble. But when I start my system, rEFInd just asks me if
> I want to boot with fwupd or with the still very broken
On 04.01.24 19:49, Richard Rosner wrote:
On 04.01.24 19:02, David Wright wrote:
Could you post the new grub.cfg file, so that people running testing,
and following along the thread later, can see how boot-repair fixed it?
Cheers,
David.
Let's hope the mailing list let's this go through.
It d
On 07.01.24 18:07, David Wright wrote:
I compared your new grub.cfg with mine (suitably decimated and edited)
and the significant differences are very few; extra modules are loaded:
cryptodisk, luks2, gcry_rijndael, gcry_rijndael and gcry_sha256.
Myset root='hd0,gpt5' is replaced by
set ro
On Thu 04 Jan 2024 at 19:49:43 (+0100), Richard Rosner wrote:
> On 04.01.24 19:02, David Wright wrote:
> > Could you post the new grub.cfg file, so that people running testing,
> > and following along the thread later, can see how boot-repair fixed it?
>
> Keep in mind, this is based on the assump
On Thu, Jan 4, 2024 at 6:18 PM Joel Roth wrote:
>
> On Thu, Jan 04, 2024 at 06:19:01PM +0100, Richard Rosner wrote:
> > In theory, it should
> > be as simple as refind-install. So the only reason I could guess to be the
> > reason would be that rEFInd might not be capable of handling LUKS, which
>
On 04.01.24 19:02, David Wright wrote:
Could you post the new grub.cfg file, so that people running testing,
and following along the thread later, can see how boot-repair fixed it?
Cheers,
David.
Let's hope the mailing list let's this go through.
Keep in mind, this is based on the assumption
On Wed 03 Jan 2024 at 22:00:20 (+0100), Richard Rosner wrote:
> On 03.01.24 21:04, Eddie wrote:
> > On 1/3/24 14:23, Richard Rosner wrote:
> > > So, since for whatever reason Grub seems to be broken beyond
> > > repair, I today tried to just replace it with rEFInd.
> > > Installation succeeded with
On Thu, Jan 04, 2024 at 06:19:01PM +0100, Richard Rosner wrote:
> In theory, it should
> be as simple as refind-install. So the only reason I could guess to be the
> reason would be that rEFInd might not be capable of handling LUKS, which
> would be quite disappointing.
My experiences are with va
Well, that was a bust. I accidentally didn't just format the EFI
partition, but deleted it. So I re-created it with the help of disks and
gparted (to leave the first 3 MB empty, I remeber that being a fix added
kinda recently to combat bad BIOS/EFI implementations, since Windows is
doing the sa
You should really re-read the FAQ that was sent in just two days ago...
On January 4, 2024 11:58:28 AM GMT+01:00, Jeffrey Walton
wrote:
>On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner wrote:
>>
>> Wow, what a bunch of unhelpful comments.
>>
>> First, if it wasn't for Eddie recommending boot-repa
On Thu, Jan 4, 2024 at 2:45 AM Richard Rosner wrote:
>
> Wow, what a bunch of unhelpful comments.
>
> First, if it wasn't for Eddie recommending boot-repair, "broken beyond
> repair" in fact was the very fitting term.
Here was Eddie's comment" I have had very good results using
"Boot-Repair" sof
Good to know that it should be possible. But as mentioned, these symbols
only offer me to boot from grub or fwupd. F2 also doesn't show that much
more, it merely gives me the option to boot into the BIOS settings. Maybe
I'll have to completely purge all Grub packages, wipe the existing EFI
partitio
On 1/4/24 02:45, Richard Rosner wrote:
Wow, what a bunch of unhelpful comments.
First, if it wasn't for Eddie recommending boot-repair, "broken beyond
repair" in fact was the very fitting term.
Second, have you maybe considered that I've already read the home page
of rEFInd and came to the s
On Wed, Jan 03, 2024 at 08:23:29PM +0100, Richard Rosner wrote:
> So, since for whatever reason Grub seems to be broken beyond repair, I today
> tried to just replace it with rEFInd. Installation succeeded without any
> trouble. But when I start my system, rEFInd just asks me if I want to boot
> wi
I have kept the referral to the old problem in the topic for a reason. Been
there, done that. I'm not entirely sure how, but boot-repair was the only
thing that was able to fix Grub. Before that I've reinstalled it countless
times, thanks.
But since this is very much not an answer to the question
Wow, what a bunch of unhelpful comments.
First, if it wasn't for Eddie recommending boot-repair, "broken beyond
repair" in fact was the very fitting term.
Second, have you maybe considered that I've already read the home page of
rEFInd and came to the same conclusion? Besides the fact that the pa
On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner
wrote:
> So, since for whatever reason Grub seems to be broken beyond repair,
>
I am not sure what you mean by "broken beyond repair." I have no issues
with Grub on Debian 12 on AMD64. I had no issues with Grub on Debian 11 or
Debian 10 on AMD64 eith
On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner wrote:
>
> So, since for whatever reason Grub seems to be broken beyond repair,
I seriously doubt this is the case. I'm guessing the problem lies elsewhere.
> I today tried to just replace it with rEFInd. Installation succeeded without
> any trouble
Thanks, this actually did the job. I don't know what it was, but my
guess is it was the step "purge Grub before reinstalling it".
PS: rewrote to the old subject, as this is clearly an answer to the
original problem, as it doesn't have anything to do with replacing Grub
all together.
On 03.0
I have had very good results using "Boot-Repair" software to recover
Grub difficulties.
Eddie
On 1/3/24 14:23, Richard Rosner wrote:
So, since for whatever reason Grub seems to be broken beyond repair, I
today tried to just replace it with rEFInd. Installation succeeded
without any trouble. B
So, since for whatever reason Grub seems to be broken beyond repair, I
today tried to just replace it with rEFInd. Installation succeeded
without any trouble. But when I start my system, rEFInd just asks me if
I want to boot with fwupd or with the still very broken Grub. Am I
missing something?
On 01.01.24 21:20, Richard Rosner wrote:
On 01.01.24 20:30, David Wright wrote:
On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
On 01.01.24 18:13, David Wright wrote:
I can boot by hand, but since this is all archived anyways and it's
uneccessarily difficult to find some sort of
On 01.01.24 20:30, David Wright wrote:
On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
On 01.01.24 18:13, David Wright wrote:
I can boot by hand, but since this is all archived anyways and it's
uneccessarily difficult to find some sort of guide how to even do
this, it might as we
On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
> On 01.01.24 18:13, David Wright wrote:
> > On Mon 01 Jan 2024 at 17:55:29 (+0100), Richard Rosner wrote:
> > > On January 1, 2024 5:43:12 PM GMT+01:00, David Wright wrote:
> > >
> > > > Like this?
> > > >
> > > > └─sda6
I can boot by hand, but since this is all archived anyways and it's
uneccessarily difficult to find some sort of guide how to even do this,
it might as well be a documentation for users having such troubles in
the future.
Also, besides the way that I have no clue how it would have to look like
On Mon 01 Jan 2024 at 17:55:29 (+0100), Richard Rosner wrote:
> On January 1, 2024 5:43:12 PM GMT+01:00, David Wright
> wrote:
>
> >Like this?
> >
> > └─sda6 8:60 406.2G 0 part
> >└─luks-f3fbb9ba-a556-406c-b276-555e3e8577bc 254:10 406.2G
Yes, exactly. Is there a way to show that from inside Grub? Lsblk and blkid
aren't available there?
On January 1, 2024 5:43:12 PM GMT+01:00, David Wright
wrote:
>Like this?
>
> └─sda6 8:60 406.2G 0 part
>└─luks-f3fbb9ba-a556-406c-b276-555e3e
On Mon 01 Jan 2024 at 17:37:44 (+0100), Richard Rosner wrote:
> So, I found a way to manually mount luks partition in Grub and boot from it.
>
> What I did to get there:
> set root=(hd0,gpt2)
> cryptomount -a
>
> This gave me the unencrypted version of the root partition as (crypto1)
>
> set roo
So, I found a way to manually mount luks partition in Grub and boot from it.
What I did to get there:
set root=(hd0,gpt2)
cryptomount -a
This gave me the unencrypted version of the root partition as (crypto1)
set root=(crypto1)
linux /vmlinuz root=/dev/mapper/luks-UUID
initrd /initrd.img
boot
T
I do not see an answer to my questions.
> On Jan 1, 2024, at 11:52, Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>
> On 1 Jan 2024 11:46 +0100, from rich...@rosner-online.de (Richard Rosner):
>> I'm not sure what you meant with "rescue mode", but I've reinstalled
>> grub anyways. The log of
On 1 Jan 2024 11:46 +0100, from rich...@rosner-online.de (Richard Rosner):
> I'm not sure what you meant with "rescue mode", but I've reinstalled
> grub anyways. The log of it doesn't look good though. Quite a bunch
> of errors. The result also is the same.
Please review the posts in the thread st
I'm not sure what you meant with "rescue mode", but I've reinstalled grub
anyways. The log of it doesn't look good though. Quite a bunch of errors. The
result also is the same.
https://pastes.io/nvmlsxghlm
> On Jan 1, 2024, at 11:03, Michael Kjörling <2695bd53d...@ewoof.net> wrote:
>
> On 1
On 29 Dec 2023 23:29 +0100, from rich...@rosner-online.de (Richard Rosner):
> For a fraction of a second it shows something about slot 0 open, that's it.
Well, that means that GRUB at least succeeds in opening the LUKS
container. That's good; it means that we can rule out that part of the
chain as
As far as I can tell, /boot and /boot/grub are the same filesystem. After all,
I didn't really do anything custom. Just your default LUKS installation with
the boot efi stuff on sda1/sdb1/whatever, LUKS on 2 and LUKS encrypted swap on
3.
I did make a video. Nothing that's not showing up always.
On 29 Dec 2023 18:56 +0100, from rich...@rosner-online.de (Richard Rosner):
> Hey, I have quite the strange issue. After updating a bunch of
> packages today [1], mostly related to systemd, gstreamer and udev,
> and restarting my device, it no longer boots. I have an encrypted
> system. So I do get
Hey, I have quite the strange issue. After updating a bunch of packages today
[1], mostly related to systemd, gstreamer and udev, and restarting my device,
it no longer boots. I have an encrypted system. So I do get asked for my
decryption password as usual, but a few seconds later, instead of c
Hi Debian users,
I have a computer running Gnome 43.6 that does not show notification
when updates are available. It was working a few months ago, but can not
tell when it stops working.
Questions:
- How can I bring back available update notifications?
- Do you think it deserves a bug report
On 2023-05-19 23:32, Gary Dale wrote:
I'm running Debian/Bookworm on an ASUS FA506IC laptop. It's got an AMD
Ryzen processor but an NVidia graphics card that provides me with
great evidence for why I had previously avoided NVidia cards. I'm
running Bookworm because I couldn't get it work on Bul
Share with the Debian community
the X server logs of "Debian" and "systemrescuecd".
Groeten
Geert Stappers
First is the log from a session that failed. Below is a log from a
previous session that worked. Sorry, didn't get one from a
systemrescuecd session - I thought I'd copied it to a n
On Mon, May 22, 2023 at 12:36 AM wrote:
> On Sun, May 21, 2023 at 03:16:56PM -0400, Gary Dale wrote:
>
> [...]
>
> > I purged lightdm, rebooted and re-installed it but got the same errors.
> >
> > I don't believe this is a problem with lightdm because it is also
> happening
> > with gdm3 and sddm
On Sun, May 21, 2023 at 03:16:56PM -0400, Gary Dale wrote:
[...]
> I purged lightdm, rebooted and re-installed it but got the same errors.
>
> I don't believe this is a problem with lightdm because it is also happening
> with gdm3 and sddm [...]
Right: most probably it is the X server failing.
On Sun, May 21, 2023 at 03:16:56PM -0400, Gary Dale wrote:
> On 2023-05-19 23:32, Gary Dale wrote:
> > I'm running Debian/Bookworm on an ASUS FA506IC laptop. It's got an AMD
> > Ryzen processor but an NVidia graphics card that provides me with great
> > evidence for why I had previously avoided NVi
On 2023-05-19 23:32, Gary Dale wrote:
I'm running Debian/Bookworm on an ASUS FA506IC laptop. It's got an AMD
Ryzen processor but an NVidia graphics card that provides me with
great evidence for why I had previously avoided NVidia cards. I'm
running Bookworm because I couldn't get it work on Bul
I'm running Debian/Bookworm on an ASUS FA506IC laptop. It's got an AMD
Ryzen processor but an NVidia graphics card that provides me with great
evidence for why I had previously avoided NVidia cards. I'm running
Bookworm because I couldn't get it work on Bullseye.
It'd been running OK with the
ble, and I've been told to stick to only Debian updates. What, if
> anything, happens to the updates advertised by XFCE? Do they go into Sid?
> Testing?
I'd recommend [1] or, for the more technical description,
[2].
In a nutshell, software (major) versions don't change
On Wed, 22 Feb 2023 22:20:39 +
ghe2001 wrote:
> What, if anything, happens to the updates advertised by XFCE? Do
> they go into Sid? Testing?
Eventually. Debian seems to do things by the upstream release. Right
now, XFCE for Bookworm/testing is 4.18, Bullseye/stable 4.16.
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I use XFCE4 for my GUI desktop, and I subscribe to XFCE's discussion list. I
see lots of posts on the list about XFCE things being updated, but I run
stable, and I've been told to stick to only Debian updates. What, if anything,
happ
On Mon, Jan 30, 2023 at 12:59 PM Georgi Naplatanov wrote:
> On 1/28/23 12:04, Timothy M Butterworth wrote:
> > All,
> >
> > I just upgraded to the 1/28/23 updates to KF5 102 and now I have no
> > audio devices found. My USB headset is plugged in but KDE does not see
&
On 1/28/23 12:04, Timothy M Butterworth wrote:
All,
I just upgraded to the 1/28/23 updates to KF5 102 and now I have no
audio devices found. My USB headset is plugged in but KDE does not see it.
lsusb lists my USB headphones:
Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540
On Sun, Jan 29, 2023 at 12:59 PM Brad Rogers wrote:
> On Sun, 29 Jan 2023 12:11:33 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I did not try a new user. I did try deleting "~/.config/pulseaudio"
>
> Sorry to say, I've reached the limit of my knowledge on the subject.
> :-(
>
> -
On Sun, 29 Jan 2023 12:11:33 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I did not try a new user. I did try deleting "~/.config/pulseaudio"
Sorry to say, I've reached the limit of my knowledge on the subject.
:-(
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
On Sun, Jan 29, 2023 at 12:11 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
>
>
> On Sun, Jan 29, 2023 at 7:55 AM Brad Rogers wrote:
>
>> On Sun, 29 Jan 2023 07:22:02 -0500
>> Timothy M Butterworth wrote:
>>
>> Hello Timothy,
>>
>> >I upgraded to 5.27beta so far no new issue
On Sun, Jan 29, 2023 at 7:55 AM Brad Rogers wrote:
> On Sun, 29 Jan 2023 07:22:02 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I upgraded to 5.27beta so far no new issues. I just installed Wayland
>
> Good to know. Thanks for the info.
>
> >so I can try it out. My sound cards ar
On Sun, 29 Jan 2023 07:22:02 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I upgraded to 5.27beta so far no new issues. I just installed Wayland
Good to know. Thanks for the info.
>so I can try it out. My sound cards are still not working though.
Have you tried;
(a) checking volume lev
On Sun, Jan 29, 2023 at 5:19 AM Brad Rogers wrote:
> On Sat, 28 Jan 2023 10:41:38 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I am looking forward to 5.27beta! It has a lot of good improvements.
>
> As I suggested, the migration to testing has started today. I'm holding
> off f
On Sat, 28 Jan 2023 10:41:38 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I am looking forward to 5.27beta! It has a lot of good improvements.
As I suggested, the migration to testing has started today. I'm holding
off for a few days to be sure (well, as sure as I can be) that
everything
On Sat, Jan 28, 2023 at 7:50 AM Brad Rogers wrote:
> On Sat, 28 Jan 2023 05:04:59 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >This appears to be a KDE issue. Is anyone else having this problem?
> >Please note the problem started after installing KF5-102 and a reboot.
>
> KDE Pla
for those running the testing distribution:
just thought i would put this out there for those here
who are heavy python users who might not be aware of how
this transition is going (seems to be mostly ok for now
but i'm sure some people who are doing strange things
might find it needs some wo
On Sat, 28 Jan 2023 05:04:59 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>This appears to be a KDE issue. Is anyone else having this problem?
>Please note the problem started after installing KF5-102 and a reboot.
KDE Plasma is undergoing big changes ATM. Soon(1) Plasma 5.27beta
(2) will
On Sat, 28 Jan 2023 07:37:01 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I forgot to mention that I am using Bookworm.
It *was* in the subject header. :-)
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately
On Sat, Jan 28, 2023 at 5:04 AM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
> All,
>
> I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio
> devices found. My USB headset is plugged in but KDE does not see it.
>
I forgot to me
All,
I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio
devices found. My USB headset is plugged in but KDE does not see it.
lsusb lists my USB headphones:
Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540
lspci lists my audio devices
04:00.5 Multimedia
Debian-user is a mailing list provided for support for Debian users,
and to facilitate discussion on relevant topics.
Some guidelines which may help explain how the list works:
* The language on this mailing list is English. There may be other mailing
lists that are language-specific, for exa
For those interested, I reported this upstream:
https://github.com/PackageKit/PackageKit/issues/590
Yvan
OpenPGP_signature
Description: OpenPGP digital signature
Yvan Masson wrote:
[snip]
>
> Indeed, in a perfect setup, system should make a snapshot before
> updates are applied (see 6. in systemd.offline-updates manpage, note
> that I have not heard it is done yet by any distribution by default),
> and revert the changes if the updat
distinction
between downloading the update(s) and installing them, which APT
supports already. No need to reboot into a special mode to perform
the install.
Yes APT can do that. Offline update also ensures that :
- the computer is not used while applying updates
- the computer is rebooted just af
strange issues or crashes due to conflicts in
> libraries versions ([1] is a KDE article that very briefly explaining
> this). In an another article I could not find anymore, someone from KDE
> explains that they receive many bug reports where issues comes from system
> update without reb
re, someone from KDE
explains that they receive many bug reports where issues comes from
system update without reboot (I would also be interested to know what is
"many" here).
Indeed, in a perfect setup, system should make a snapshot before updates
are applied (see 6. in systemd.offlin
1 - 100 of 1881 matches
Mail list logo
