On 12/07/2025 01:28, Thomas Schmitt wrote:
Whatever, the Debian question is whether "apt upgrade" changed this EFI
setting forth and back.
Is fwupd running on this machine? It might be direct update of firmware
either of the machine or of the dock station unrelated to .deb packages
and apt.
The fact that it works with Linux lets me think
that the failure with EFI and GRUB is not an intended security feature.
---
Whatever, the Debian question is whether "apt upgrade" changed this EFI
setting forth and back.
One could acc
Sent with Proton Mail secure email.
On Friday, 11 July 2025 at 14:41, Thomas Schmitt wrote:
> Hi,
>
> Wolf wrote:
>
> > > > My default settings in EFI was Thunderbolt security: OFF.
> > > > Today, I changed security from OFF to "User Authorization" and now
> > > > keyboard is working.
> > >
Hi,
Wolf wrote:
> > > My default settings in EFI was Thunderbolt security: OFF.
> > > Today, I changed security from OFF to "User Authorization" and now
> > > keyboard is working.
> > > I tested changing back from "User Authorization" to OFF and the keyboard
> > > became unusable again.
I wrote:
On 11/07/2025 02:13, Thomas Schmitt wrote:
Wolf wrote:
My default settings in EFI was Thunderbolt security: OFF.
Today, I changed security from OFF to "User Authorization" and now keyboard
is working.
I tested changing back from "User Authorization" to OFF and the keyboard
became unusable again.
Hi,
Wolf wrote:
> My default settings in EFI was Thunderbolt security: OFF.
> Today, I changed security from OFF to "User Authorization" and now keyboard
> is working.
> I tested changing back from "User Authorization" to OFF and the keyboard
> became unusable again.
(So Thunderbolt is off, not t
u find a way to undo these settings ?
General question:
I wonder how could the lengthy upgrade of 2025-07-04 07:41:06 fix the
problem. Which package from there would be suspicious to counter-fiddle
with EFI ?
(And is Wicked Uncle Ernie a Debian Developer meanwhile ?)
Have a nice day :)
Thomas
he mouse worked well, but two days later, after the
> > another upgrade
> >
> > -
> > Start-Date: 2025-07-06 09:27:29
> > Commandline: apt upgrade
> > Requested-By: g (1000)
> >
Clumsy and inefficient:
>(I'm subscribed there. No need to Cc: me.)
Clean and efficient:
>> Reply-To: debian-user@lists.debian.org
> https://lists.debian.org/debian-user/
> does not deliver a page, although ping lists.debian.org works fine.
Works for me. Either a transient pr
0a1~20250704212032,
> 142.0a1~20250705211551), firmware-sof-signed:amd64 (2025.01-1, 2025.05-1),
> mobile-broadband-provider-info:amd64 (20240407-1, 20250613-2)
> End-Date: 2025-07-06 09:27:35
> --------
> -
>
> the keyboard and t
er other system updates, the the keyboard and the mouse are
> working again during boot, and so on: the on/off cycle repeats.
If the keyboard would only fail to work while GRUB is running, then the
package name for the bug report would be "grub2".
But if you cannot get the computer's
>
> On 9 Jul 2025, at 17:30, Greg wrote:
>
> On 2025-07-09, Nicolas George wrote:
>> Felix Miata (HE12025-07-09):
>>> This may have nothing to do with Debian or any OS. It could be either
>>> firmware in
>>> the motherboard
>>
>> Nit: the firmware in the motherboard is an operating system.
On 2025-07-09, Nicolas George wrote:
> Felix Miata (HE12025-07-09):
>> This may have nothing to do with Debian or any OS. It could be either
>> firmware in
>> the motherboard
>
> Nit: the firmware in the motherboard is an operating system.
Is the firmware in the motherboard otherwise referred to
Felix Miata (HE12025-07-09):
> This may have nothing to do with Debian or any OS. It could be either
> firmware in
> the motherboard
Nit: the firmware in the motherboard is an operating system.
Regards,
--
Nicolas George
Wolf composed on 2025-07-09 08:34 (UTC):
> I need to identify a package to fill a bug report and I need help for that.
> On my laptop (Debian unstable) I'm using external illuminated keyboard and
> mouse connected to
> - Dell dock connected via thunderbolt
> or
> - U2
Wolf (HE12025-07-09):
> After some system updates, the keyboard and the mouse become unusable
> (and the keyboard is not illuminated) during boot: I cannot access
> BIOS and cannot select grub entries.
> Then, once system started, both keyboard and mouse become usable.
What you describe is an issu
Hi,
I need to identify a package to fill a bug report and I need help for that.
On my laptop (Debian unstable) I'm using external illuminated keyboard and
mouse connected to
- Dell dock connected via thunderbolt
or
- U2724de Dell monitor also connected via thunderbolt
After some s
Hans wrote:
> For my own purposes I want to build a package with my own content.
> It will content several wordlists I created and need them as package, when I
> build a live image.
>
> All wordlists shall be in /usr/share/wordlists1/.
>
> Now my question: Is it cor
Dear list,
I have a general question to package building.
For my own purposes I want to build a package with my own content.
It will content several wordlists I created and need them as package, when I
build a live image.
All wordlists shall be in /usr/share/wordlists1/.
Now my question: Is
On 15/06/2025 23:08, tomas wrote:
On Sun, Jun 15, 2025 at 11:33:09AM -0400, Greg Wooledge wrote:
According to the apt.conf(5) man page:
Pre-Invoke, Post-Invoke
[...]
That's clear as mud. What is "list notation"?
[...]
Aaah. I guess they mean Perl-y lists, like ["foo", "bar", "baz"]
On Sun 15 Jun 2025 at 13:33:41 (-0400), Greg Wooledge wrote:
> On Sun, Jun 15, 2025 at 12:14:30 -0500, David Wright wrote:
> > Well, I just plagiarised /etc/apt/apt.conf.d/99needrestart:
> >
> > $ cat /etc/apt/apt.conf.d/99redogrub
> > DPkg::Post-Invoke {"test -x /var/local/bin/redo && /var/l
On Sun, Jun 15, 2025 at 12:14:30 -0500, David Wright wrote:
> Well, I just plagiarised /etc/apt/apt.conf.d/99needrestart:
>
> $ cat /etc/apt/apt.conf.d/99redogrub
> DPkg::Post-Invoke {"test -x /var/local/bin/redo && /var/local/bin/redo ||
> true"; };
> $
>
> and wrote /var/local/bin/redo
still open: is there in fact a straightforward way for a user, not
> > > the package maintainer, to tell the package management system: "If and
> > > only if your operation touched package x, also do this one thing
> > > locally."? I can think of about a mill
On Sun 15 Jun 2025 at 11:33:09 (-0400), Greg Wooledge wrote:
> On Sun, Jun 15, 2025 at 11:07:41 -0400, Boyan Penkov wrote:
> > So ultimately, my problem is addressed; however, the larger question
> > is still open: is there in fact a straightforward way for a user, not
> > t
On Sun, Jun 15, 2025 at 06:08:08PM +0200, to...@tuxteam.de wrote:
[...]
> Aaah. I guess they mean Perl-y lists, like ["foo", "bar", "baz"].
Gah, no. That'd make an array ref. I wanted to write ("foo", "bar", "baz").
Cheers
--
t
signature.asc
Description: PGP signature
On Sun, Jun 15, 2025 at 11:33:09AM -0400, Greg Wooledge wrote:
> On Sun, Jun 15, 2025 at 11:07:41 -0400, Boyan Penkov wrote:
> > So ultimately, my problem is addressed; however, the larger question
> > is still open: is there in fact a straightforward way for a user, not
> > t
stion
> > is still open: is there in fact a straightforward way for a user, not
> > the package maintainer, to tell the package management system: "If and
> > only if your operation touched package x, also do this one thing
> > locally."? I can think of about a m
On Sun, Jun 15, 2025 at 11:07:41 -0400, Boyan Penkov wrote:
> So ultimately, my problem is addressed; however, the larger question
> is still open: is there in fact a straightforward way for a user, not
> the package maintainer, to tell the package management system: "If and
which was "Does this run after every apt invocation, or only
the one that touched the relevant package?" David Wright and the
wanderer both suggest a workaround, which essentially comes down to
wrapping apt in another script that's something like:
```
apt dist-upgrade
if /boot/
On Sun 15 Jun 2025 at 06:23:20 (-0400), The Wanderer wrote:
> On 2025-06-15 at 04:01, to...@tuxteam.de wrote:
> > OK, here is the screwdriver (from man apt.conf(5)):
> >
> >Pre-Invoke, Post-Invoke
> >This is a list of shell commands to run before/after
> >invoking
On 15/06/2025 00:10, Boyan Penkov wrote:
Hello folks,
I'm wiring to ask how to get apt to run a script after a particular
package is installed or updated. Am I looking for dpkg-triggers or
some apt conf?
Specifically, I have GRUB installed to *every* drive, with the
expectation that al
would boil down to
"write a shell script and use that as the command"), or a way for a
command running independent of apt to *detect* whether such an update
has happened, that doesn't look like it would satisfy the need.
I know there are ways for one package to react to the update
'm wiring to ask how to get apt to run a script after a particular
> >> package is installed or updated. Am I looking for dpkg-triggers or
> >> some apt conf?
> >>
> >> Specifically, I have GRUB installed to *every* drive, with the
> >> expectation th
On Sun, Jun 15, 2025 at 7:45 AM Nicholas Geovanis
wrote:
>
>
>
> On Sat, Jun 14, 2025, 9:15 PM Boyan Penkov wrote:
>>
>> Hello folks,
>>
>> I'm wiring to ask how to get apt to run a script after a particular
>> package is installed or updated. Am
On Sat, Jun 14, 2025, 9:15 PM Boyan Penkov wrote:
> Hello folks,
>
> I'm wiring to ask how to get apt to run a script after a particular
> package is installed or updated. Am I looking for dpkg-triggers or
> some apt conf?
>
> Specifically, I have GRUB installed
Hello folks,
I'm wiring to ask how to get apt to run a script after a particular
package is installed or updated. Am I looking for dpkg-triggers or
some apt conf?
Specifically, I have GRUB installed to *every* drive, with the
expectation that all but one drives can fail and the machine
On 2025-06-09 16:24:41 +0200, Thomas Hochstein wrote:
> Rules are updated by the sa-update service, started e.g. by
> | systemctl enable --now spamassassin-maintenance.timer
> | systemctl start spamassassin-maintenance.service
>
> Doing that, the scores are up to date:
> | thh@angmar:~$ grep RCVD_
On 2025-06-09 13:50:52 +0200, Nicolas George wrote:
> Vincent Lefevre (HE12025-06-09):
> > Jun 09 13:07:48 joooj spamd[164780]: check: dns_block_rule
> > RCVD_IN_VALIDITY_RPBL_BLOCKED hit, creating
> > /root/.spamassassin/dnsblock_bl.score.senderscore.com
>
> A system service accessing files in
Hi,
On Tue, Jun 10, 2025 at 09:34:33AM +0200, Vincent Lefevre wrote:
> On 2025-06-09 16:24:41 +0200, Thomas Hochstein wrote:
> > | thh@angmar:~$ grep RCVD_IN_VALIDITY
> > /var/lib/spamassassin/4.01/updates_spamassassin_org/50_scores.cf
> > | score RCVD_IN_VALIDITY_CERTIFIED 0
> > | score RCVD
Vincent Lefevre wrote:
> Is the spamassassin Debian package unsafe to use in stable?
>
> The issue is that things related to spam evolves rapidly, but
> Debian stable is... stable.
Debian stable already has the current version of SpamAssassin:
| News and Announcements
|
|
Vincent Lefevre (HE12025-06-09):
> Jun 09 13:07:48 joooj spamd[164780]: check: dns_block_rule
> RCVD_IN_VALIDITY_RPBL_BLOCKED hit, creating
> /root/.spamassassin/dnsblock_bl.score.senderscore.com
A system service accessing files in the personal directory of root?
There is something seriously wro
On 2025-06-09 08:03:58 +, Andy Smith wrote:
> sa-update already picked it up:
>
> $ grep RCVD_IN_VALIDITY
> /var/lib/spamassassin/4.01/updates_spamassassin_org/50_scores.cf
> score RCVD_IN_VALIDITY_CERTIFIED 0
> score RCVD_IN_VALIDITY_SAFE 0
> score RCVD_IN_VALIDITY_RPBL 0
> #score RCVD_
On Mon, Jun 09, 2025 at 08:07:37AM +, Andy Smith wrote:
> On Mon, Jun 09, 2025 at 08:03:58AM +, Andy Smith wrote:
> > On Mon, Jun 09, 2025 at 01:18:37AM +0200, Vincent Lefevre wrote:
> > > Is the spamassassin Debian package unsafe to use in stable?
> >
> > I
On Mon, Jun 09, 2025 at 08:03:58AM +, Andy Smith wrote:
> On Mon, Jun 09, 2025 at 01:18:37AM +0200, Vincent Lefevre wrote:
> > Is the spamassassin Debian package unsafe to use in stable?
>
> I think so. I think the general expectation of spamassassin is that you
> use a
Hi,
On Mon, Jun 09, 2025 at 01:18:37AM +0200, Vincent Lefevre wrote:
> Is the spamassassin Debian package unsafe to use in stable?
I think so. I think the general expectation of spamassassin is that you
use a release for a long time.
> The issue is that things related to spam evolves r
On 2025-06-09 02:58:07 +0200, Santiago Vila wrote:
> El 9/6/25 a las 1:18, Vincent Lefevre escribió:
> > Is the spamassassin Debian package unsafe to use in stable?
> >
> > The issue is that things related to spam evolves rapidly, but
> > Debian stable is... stabl
El 9/6/25 a las 1:18, Vincent Lefevre escribió:
Is the spamassassin Debian package unsafe to use in stable?
The issue is that things related to spam evolves rapidly, but
Debian stable is... stable.
Look at the version numbers:
spamassassin | 4.0.1-1~deb12u1| stable
Is the spamassassin Debian package unsafe to use in stable?
The issue is that things related to spam evolves rapidly, but
Debian stable is... stable. So its rules become obsolete, such as
those that generate
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED
RCVD_IN_VALIDITY_RPBL_BLOCKED
ide a config file where we can write which
> package should be held, using a format that allows comments).
I didn't check Bookworm, but:
# grep RETT /etc/os-release
PRETTY_NAME="Debian GNU/Linux trixie/sid"
# aptitude search zypp
p libzypp-bin - openSUSE/SLES package
>> echo "PKGNAME hold" | sudo dpkg --set-selections
> is that the same as apt-mark hold PKGNAME
Reminds me that I wish we could add a comment describing why it's on
hold (or alternatively, provide a config file where we can write which
package should be held, using a for
nd grub-efi-$arch do the configuration to use one of those
> binaries to make your system bootable.
I can confirm that installing grub-pc-bin did not keep the machine from
booting today. :))
I should have looked into the Debian package descriptions for GRUB five
days earlier when i learn
Thomas wrote:
>
>i am trying to reproduce a problem of grub-mkrescue. For that i need
>the directories
> /usr/lib/grub/i386-pc
> /usr/lib/grub/i386-efi
>alongside the already installed
> /usr/lib/grub/x86_64-efi
>in order to get an ISO for legacy BIOS and EFI together.
>Gentoo and Arch obviously
ia/packages/g/grub2/control-2.06-13deb12u1
says
Package: grub-pc-bin
...
This package contains GRUB modules that have been built for use with the
traditional PC/BIOS architecture. It can be installed in parallel with
other flavours, but will not automatically install GRUB as the
Thomas Schmitt wrote:
> Hi,
>
> i am trying to reproduce a problem of grub-mkrescue. For that i need
> the directories
> /usr/lib/grub/i386-pc
> /usr/lib/grub/i386-efi
> alongside the already installed
> /usr/lib/grub/x86_64-efi
> in order to get an ISO for legacy BIOS and EFI together.
> G
Hi,
i am trying to reproduce a problem of grub-mkrescue. For that i need
the directories
/usr/lib/grub/i386-pc
/usr/lib/grub/i386-efi
alongside the already installed
/usr/lib/grub/x86_64-efi
in order to get an ISO for legacy BIOS and EFI together.
Gentoo and Arch obviously can have this. I'm
Federico Kircheis wrote:
> I'm using the kotlin package since I wanted to use the kotlinc compiler, and
> noticed that it lists following packages as dependencies
>
> * ant
> * libmaven-compiler-plugin-java
> * libmaven-plugin-tools-java
> * libmaven3-core-java
&g
Hello,
I'm using the kotlin package since I wanted to use the kotlinc compiler,
and noticed that it lists following packages as dependencies
* ant
* libmaven-compiler-plugin-java
* libmaven-plugin-tools-java
* libmaven3-core-java
I'm not using ant or maven, so this instal
On Tue, May 13, 2025 at 09:38:39 +, Andrew M.A. Cater wrote:
> On Tue, May 13, 2025 at 11:32:20AM +0200, Bernard wrote:
> > Hi to Everyone,
> >
> > This being done, I first thought that I could possibly succeed in just
> > upgrading my Buster system to its last update, which I did, successfull
On Tue, May 13, 2025 at 11:32:20AM +0200, Bernard wrote:
> Hi to Everyone,
>
> This being done, I first thought that I could possibly succeed in just
> upgrading my Buster system to its last update, which I did, successfully…
> unfortunately this did not change the faulty behaviour of vlc.
>
> No
s dated dec 6 2020… => they are already in place, same date.
So, I suppose that there is no need to re-install, since it is likely
that the library file package did get re-installed when re-installing
vlc.
I don't know, because the install process does more than just unpack
the archive—but exa
for libc6 and libc-bin at the moment (assuming
> > > > you haven't already upgraded them in the last 30 hours or so), and
> > > > that could update timestamps. And anyway, I suspect the timestamp
> > > > on /etc/ld.so.cache might not be very meaningful,
refresh it.
/*I could suggest that you re-install…*/
(four lines dated dec 6 2020… => they are already in place, same date.
So, I suppose that there is no need to re-install, since it is likely
that the library file package did get re-installed when re-installing
vlc.
I don't know, bec
Bernard writes:
> which reminds me that, in the installation process of ‘ISPY/AgentDVR’
> packages, Video Acceleration was mentioned as a compulsory step, with
> a warning that it could eventually affect some other applications ; I
> had replied ‘Y’, because I thought it was easily reversible.
>
amir alavi wrote:
> Package: ffmpeg
> Version: 7:7.1.1-1+b1
> Package: intel-media-va-driver-non-free
> Version: 25.1.4+ds1-1
> Dear Maintainers,
> I am encountering an issue when attempting to convert files using ffmpeg with
> the hevc_qsv encoder (Intel QuickS
Package: ffmpeg
Version: 7:7.1.1-1+b1
Package: intel-media-va-driver-non-free
Version: 25.1.4+ds1-1
Dear Maintainers,
I am encountering an issue when attempting to convert files using ffmpeg with
the hevc_qsv encoder (Intel QuickSync) on Debian Trixie.
Previously, I was able to perform similar
you haven't already upgraded them in the last 30 hours or so), and
> > that could update timestamps. And anyway, I suspect the timestamp
> > on /etc/ld.so.cache might not be very meaningful, as other things
> > might refresh it.
>
> /*I could suggest that you re-install…*/
lready in place, same date.
So, I suppose that there is no need to re-install, since it is likely
that the library file package did get re-installed when re-installing vlc.
…/*about linux links libraries… you might check the modification
timestamps of those /etc files to see whet
On Wed 30 Apr 2025 at 16:53:43 (+0200), Bernard wrote:
> On 30/04/2025 01:34, David Wright wrote:
> > And at that point, I would have looked again at ls -ult
> > to see whether anything had changed.
> > Well, running vlc at about the same time as reinstalling it
> > makes sure that any data you col
On 30/04/2025 01:34, David Wright wrote:
Bernard wrote:
And at that point, I would have looked again at ls -ult
to see whether anything had changed.
Well, running vlc at about the same time as reinstalling it
makes sure that any data you collect is as ambiguous as possible.
So, I just test
On Tue 29 Apr 2025 at 13:39:23 (+0200), Bernard wrote:
> bd@debian-stretch:/usr/local/lib$ ls -l
> [ … ]
> 10 april must be the date I installed that awful ISPY/Agent package
> 17 april 2023 must be the date of install of my current Bullseye
>
> then :
>
> bd@debian-st
root 17 10 avril 17:59 libva.so.2 -> libva.so.2.2200.0
-rwxr-xr-x 1 root root 953408 10 avril 17:59 libva.so.2.2200.0
drwxr-xr-x 2 root root 4096 10 avril 17:59 pkgconfig
drwxr-xr-x 3 root root 4096 17 avril 2023 python3.9
10 april must be the date I installed that awful ISPY/Agent package
gt;
> # This system was installed using small removable media
> # (e.g. netinst, live or single CD). The matching "deb cdrom"
> # entries were disabled at the end of the installation process.
> # For information about how to configure apt package sources,
> # see the sources.list
On Tue 22 Apr 2025 at 14:48:01 (+0200), Bernard wrote:
> On 21/04/2025 22:02, David Wright wrote:
> > I think you should post your /etc/apt/sources.list here before
> > taking further actions.
>
> Here it is, dated 22apr2023 : Date shows that I musn't have updated
> it, even though I thought I had
process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
On Mon 21 Apr 2025 at 18:03:04 (+0200), Bernard wrote:
> I did reply to your message, sending the output of suggested aptitude
> search below... but my reply does not appear to the list messages,
> maybe because there were too many lines in it. In any case, I didn't
> find anything meaningfull to m
Hi David,
I did reply to your message, sending the output of suggested aptitude
search below... but my reply does not appear to the list messages, maybe
because there were too many lines in it. In any case, I didn't find
anything meaningfull to me... which doesn't mean that there was nothing..
On Mon, 21 Apr 2025 17:44:30 +0200
Bernard wrote:
Hello Bernard,
>One of these complainers got a reply, advising to install/re-install
>libavcodec58… which seems to have solved his problem. I tested the same
I had a similar problem with Pale Moon no longer playing videos.
Re-installing libavc
I have now completely de-installed and removed the ISPY package (also
known as ‘AgentDVR’), according to the process explained on their site.
Next, I have checked the install log file that had been generated by
this previous install process :
/var/log/agentdvr_setup.log (1156 lines)
which
s
2.4.62-1~deb11 - Serveur HTTP Apache - utilit
i appimagelauncher 3.0.0-alpha-4- (installed locally) -
ldnp-built package
i base-files 11.1+deb11u9 Debian:11.11/oldstable [amd64] 11.1+deb11u11 -
divers fichiers du système d
i bind9-dnsutils 1:9.16.48-1 Debian-Security:11/oldstable-s
1:9.16.5
On 19/04/2025 15:39, David wrote:
On Sat, 19 Apr 2025 at 04:21, David Wright wrote:
You could run a command like:
$ aptitude search "?narrow(?installed,?not(?archive(stable)))"
to see whether all the packages on your system originate in bookworm.
Doesn't this pattern match "oldstable'? M
On Sat, 19 Apr 2025 at 04:21, David Wright wrote:
> You could run a command like:
>
> $ aptitude search "?narrow(?installed,?not(?archive(stable)))"
>
> to see whether all the packages on your system originate in bookworm.
If that command produces any output, then adding a custom format
argume
ncrease this or that… ? It won’t pose problem to your
> system, but it might affect some components... (Y/N) »
>
> I then replied « Y », in the reasoning that I could, in case of
> problem, reverse the situation in removing and purging the ISPY
> package.
>
> As previously said, VLC
>> The ispy software is something well known, which is available for
>> Windows, Mac and Linux. It drives several well known "spy cameras",
>> that is, cameras that spy anything unusual in your garden when there
>> is no-one at home. If you google search "ispy", you get several pages
>> of answers
Bernard wrote:
> On 18/04/2025 15:37, songbird wrote:
> > wrote:
> >> On Thu, Apr 17, 2025 at 04:32:26PM +0200, Bernard wrote:
> >>> Hi to Everyone !
> >>>
> >>> vlc 3.0.21 (Vetinari) – Debian 11
> >>>
> >>> ⇒ vlc no longer reckognises nor plays mp4 files ; it now only
> >>> plays their audio
,
reverse the situation in removing and purging the ISPY package.
As previously said, VLC now disfunctions. Maybe something else will also
dysfunction, but I haven’t yet come across such finding.
Once installed, ISPY seemed to work, but I soon found that it wasn’t
what I had expected, so I decided to
On 18/04/2025 15:37, songbird wrote:
wrote:
On Thu, Apr 17, 2025 at 04:32:26PM +0200, Bernard wrote:
Hi to Everyone !
vlc 3.0.21 (Vetinari) – Debian 11
⇒ vlc no longer reckognises nor plays mp4 files ; it now only plays their
audio part :
« Codec non pris en charge:VLC ne peut pas décoder
wrote:
> On Thu, Apr 17, 2025 at 04:32:26PM +0200, Bernard wrote:
>> Hi to Everyone !
>>
>> vlc 3.0.21 (Vetinari) – Debian 11
>>
>> ⇒ vlc no longer reckognises nor plays mp4 files ; it now only plays their
>> audio part :
>>
>> « Codec non pris en charge:VLC ne peut pas décoder le format « h264
On Thu, Apr 17, 2025 at 04:32:26PM +0200, Bernard wrote:
> Hi to Everyone !
>
> vlc 3.0.21 (Vetinari) – Debian 11
>
> ⇒ vlc no longer reckognises nor plays mp4 files ; it now only plays their
> audio part :
>
> « Codec non pris en charge:VLC ne peut pas décoder le format « h264 » (H264
> - MPEG-
On Tue, Apr 01, 2025 at 19:54:19 -0400, Timothy M Butterworth wrote:
> Try running `sudo apt info kde-config-mobile-networking` and see what the
> info says.
You don't even need sudo for that.
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32
/usr/share/perl/5.32 /usr/local/lib/site_perl) at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
The Debian package "libdigest-sha-perl" appears to be what I need:
2025-04-02 15:54:17 root@laalaa ~
# a
gt; # perl -e 'use Digest::SHA256'
> Can't locate Digest/SHA256.pm in @INC (you may need to install the
> The Debian package "libdigest-sha-perl" appears to be what I need:
> # apt-cache search SHA | grep 256 | grep -i perl
> libdigest-sha-perl - Perl extension f
On Thu, Apr 3, 2025, 6:38 AM wrote:
> Greg Wooledge wrote:
> > On Wed, Apr 02, 2025 at 16:07:36 -0700, David Christensen wrote:
>
> FWIW, it seems that the author of the older package has died. :(
>
You know I can't help it, every time I see something like that I think of
Ian Murdock.
:SHA
>
> Digest::SHA256 appears to be much, much older and probably abandoned.
FWIW, it seems that the author of the older package has died. :(
On Wed, Apr 02, 2025 at 16:07:36 -0700, David Christensen wrote:
> But installing libdigest-sha-perl does not provide Digest::SHA256:
They are different modules.
https://metacpan.org/pod/Digest::SHA256
https://metacpan.org/pod/Digest::SHA
Digest::SHA256 appears to be much, much older and probabl
On 4/2/25 16:18, Greg Wooledge wrote:
On Wed, Apr 02, 2025 at 16:07:36 -0700, David Christensen wrote:
But installing libdigest-sha-perl does not provide Digest::SHA256:
They are different modules.
https://metacpan.org/pod/Digest::SHA256
https://metacpan.org/pod/Digest::SHA
Digest::SHA256 ap
On Tue, Apr 1, 2025 at 2:37 PM Hans wrote:
> Hi,
>
> just a question: today I stumbled over the package "kde-config-mobile-
> networking" and installed it. But I saw no change of my system. I even did
> not
> find any change in kde-systemsettings. Is this an
Hi,
just a question: today I stumbled over the package "kde-config-mobile-
networking" and installed it. But I saw no change of my system. I even did not
find any change in kde-systemsettings. Is this an older and unneeded package?
Network-manager is already creating a connection to
On 01/04/2025 16:01, Hans wrote:
Hi,
just a question: today I stumbled over the package "kde-config-mobile-
networking" and installed it. But I saw no change of my system. I even did not
find any change in kde-systemsettings. Is this an older and unneeded package?
Network-manager
On Tue, Mar 25, 2025 at 12:27 AM Xiyue Deng wrote:
>
> Nicolas George writes:
>
> > Barry Newberger (HE12025-03-24):
> >> package: dpkg
> >> version: 1.21.22 (amd64)
> >>
> >> Using Discover update following error occurred:
> >>
&
Nicolas George writes:
> Barry Newberger (HE12025-03-24):
>> package: dpkg
>> version: 1.21.22 (amd64)
>>
>> Using Discover update following error occurred:
>>
>> Package failed to install:Error while installing package:
>> installed linux-image-6.
1 - 100 of 6492 matches
Mail list logo
