t down.After
> that, I tried to off that button by pressing the button for 6-7 seconds but
> after powering on next time, it shows a CMOS error and then laptop gets
> started with battery 0%(even if it was charged 100% before).
>
> Note that I installed Debian 3 days ago.How to rep
after powering on next time, it shows a CMOS error and then laptop gets
started with battery 0%(even if it was charged 100% before).
Note that I installed Debian 3 days ago.How to report the bug?
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
Hi,
I had similar issue, but when on my device i put pin, then I do not
have to put it anywhere in Debian.
Best regards,
Łukasz
On 23.08.2024 20:26, Nikita Yurchyk wrote:
bluetooth 5.77-1 (testing/trixie) doesn't show/ask pin dialog window
like bluetooth 5.66-1+deb12u2 (bookworm). ju
bluetooth 5.77-1 (testing/trixie) doesn't show/ask pin dialog window like
bluetooth 5.66-1+deb12u2 (bookworm). just saying br-connection-unknown,
sometimes Authentication failed.
On 08/08/2024 23:21, Hans wrote:
Although I owe several Samsung devices, they are all different models. So the
kernel will recognize each different.
lsusb reports vendor ID. If 2 devices have same number, but different
manufacturer strings then "Sasmsung" is a device vendor b
Hi,
On Thu, Aug 08, 2024 at 06:00:53PM +0200, Geert Stappers wrote:
> On Thu, Aug 08, 2024 at 05:27:58PM +0200, Hans wrote:
> > 2024-08-07T13:11:14.047647+02:00 protheus2 kernel: [ 2649.347054] usb
> > 2-1.1: Manufacturer: Sasmsung
> >
> > As we know, it should be "Samsung" not "Sasmsung". I bel
On Thu, Aug 08, 2024 at 05:27:58PM +0200, Hans wrote:
> Dear list,
>
> I discovered a little typo bug, which might not be important, but maybe one
> knows, which
> developer can be informed.
>
> Wheh connecting a mobile fdrom Samsung to my computer, the message in
>
Thank you for the info. Filed a bugreport.
Best
Hans
> Kernel messages come kernel package, e.g. linux-image-4.19.0-27-amd64.
>
> Groeten
> Geert Stappers
Hans wrote:
> Wheh connecting a mobile fdrom Samsung to my computer, the message in
> /var/log/syslog
> tells:
>
>
> 2024-08-07T13:11:14.047644+02:00 protheus2 kernel: [ 2649.347050] usb 2-1.1:
> Product:
> MSM8952
> 2024-08-07T13:11:14.047647+02:00 protheus2 kernel: [ 2649.347054] usb 2-1.
Hi Andy, I am quite not sure. I filed a bugreport to the kernel team, as it is
only a little typo and does no harm, they can drop it or fix it.
Hmm, your idea came also in my mind already, but I did not check for it.
Although I owe several Samsung devices, they are all different models. So the
Dear list,
I discovered a little typo bug, which mightnot be important, but maybe one
knows, which
developer can be informed.
Wheh connecting a mobile fdrom Samsung to my computer, the message in
/var/log/syslog
tells:
2024-08-07T13:11:14.047644+02:00 protheus2 kernel: [ 2649.347050] usb 2
Hi!
I have not package problems; it is a something else. This problem was showed up
in my Debian 12.2.0-14 system, with core: 6.1.0-23-amd64. It's running in VPS,
which is using VMware. So, I was built Xdisplay, for Joomla configuration, and
this was working perfectly. But some day later, the X
inet6 fe80::5054:ff:fe95:9109/64 scope link proto kernel_ll
> > valid_lft forever preferred_lft forever
> >
> >
> > # journalctl | grep -i ipv6
> > Jul 31 20:06:07 debsid1 kernel: Segment Routing with IPv6
> > Jul 31 20:06:07 debsid1 kernel: In-situ OAM (I
able to reproduce at your side? You can verify this on
VirtualBox even without DHCPv6 server. In normal circumstances you
should get timeout on dhclient but the BUG causes that Debian
should end immediately without timeout and with the error
mentioned in the first post in syslog.
v6
On Wednesday, 31-07-2024 at 18:15 Łukasz Kalamłacki wrote:
Hi,
Are you able to reproduce at your side? You can verify this on
VirtualBox even without DHCPv6 server. In normal circumstances you
should get timeout on dhclient but the BUG causes that Debian
should end imm
AM) with IPv6
Jul 31 20:41:06 debsid1 kernel: mip6: Mobile IPv6
On Wednesday, 31-07-2024 at 18:15 Łukasz Kalamłacki wrote:
Hi,
Are you able to reproduce at your side? You can verify this on
VirtualBox even without DHCPv6 server. In normal circumstances you
should get timeout on dhclient but
ld you try to reproduce on VirtualBox at your side. You do not
need
> dhcpv6 server. In normal behavior you should get timeout, but this
bug will
> cause quick end with error from the first post.
>
> Best regards,
> Łukasz
>
> śr., 31 lip 2024 o 10:35 Andrew M.A. Cater n
Hi,
I had besides sid also trixie sources but I bet that with only sid the
result will be the same.
Could you try to reproduce on VirtualBox at your side. You do not need
dhcpv6 server. In normal behavior you should get timeout, but this bug will
cause quick end with error from the first post
OK, I will give that a try and post back.
George.
On Wednesday, 31-07-2024 at 18:15 Łukasz Kalamłacki wrote:
Hi,
Are you able to reproduce at your side? You can verify this on
VirtualBox even without DHCPv6 server. In normal circumstances you
should get timeout on dhclient but the BUG
Hi,
Are you able to reproduce at your side? You can verify this on VirtualBox
even without DHCPv6 server. In normal circumstances you should get timeout
on dhclient but the BUG causes that Debian should end immediately without
timeout and with the error mentioned in the first post in syslog.
So
Łukasz,
I wonder if the issue is that you are missing "non-free-firmware" which
provides the non-free drivers for things like sound, network and WiFI devices?
(Hopefully you only have 'sid' sources and no sources for other versions, for
example 'bookworm' or 'backports')
It could help to at l
On Wed, Jul 31, 2024 at 08:33:28AM +0200, Łukasz Kalamłacki wrote:
> Hi,
>
> I added only this to sources list:
>
> deb http://deb.debian.org/debian/ sid main contrib non-free
>
> and nothing else
>
> Best regards,
> Łukasz
>
So that was the _only_ line in your /etc/apt/sources.list at that p
Hi,
Yes I tried that also with the same result.
Best regards,
Łukasz
śr., 31 lip 2024 o 01:09 Jeffrey Walton napisał(a):
> On Tue, Jul 30, 2024 at 7:00 PM Łukasz Kalamłacki
> wrote:
> >
> >
> > I detected and issue with Debian SID and DHCP for IPv6.
> >
> > In my network I use DHCPv6 server w
Hi,
I added only this to sources list:
deb http://deb.debian.org/debian/ sid main contrib non-free
and nothing else
Best regards,
Łukasz
śr., 31 lip 2024 o 00:50 George at Clug napisał(a):
>
>
> On Wednesday, 31-07-2024 at 06:01 Łukasz Kalamłacki wrote:
> > Hello,
> >
> >
> > I detected and
On Tue, Jul 30, 2024 at 7:00 PM Łukasz Kalamłacki wrote:
>
>
> I detected and issue with Debian SID and DHCP for IPv6.
>
> In my network I use DHCPv6 server which works fine on stable versions of
> Debian or Trixie but when I add to sources.list sid source and do update
> and upgrade I get and err
On Wednesday, 31-07-2024 at 06:01 Łukasz Kalamłacki wrote:
> Hello,
>
>
> I detected and issue with Debian SID and DHCP for IPv6.
>
>
> In my network I use DHCPv6 server which works fine on stable versions of
> Debian or Trixie but when I add to sources.list sid source and do update
Pleas
Hello,
I detected and issue with Debian SID and DHCP for IPv6.
In my network I use DHCPv6 server which works fine on stable versions of
Debian or Trixie but when I add to sources.list sid source and do update
and upgrade I get and error that:
"Link local ipv6 for interface is not configure
On 2024-07-29, Thomas Schmitt wrote:
> https://www.debian.org/Bugs/Reporting
> "Sending the bug report via e-mail"
> (about 30 lines down the page)
> "An Example Bug Report"
> (another 30 lines down the page)
Still the first and recommended way is to
Hi,
Ian Molton wrote:
> Perhaps someone can help me with the bug tracker?
If i have to submit a bug, then i use the e-mail way.
See:
https://www.debian.org/Bugs/Reporting
"Sending the bug report via e-mail"
(about 30 lines down the page)
"An Example Bug Report"
On 2024-07-28, Ian Molton wrote:
> Perhaps someone can help me with the bug tracker?
Install the package reportbug. It's as easy as writing a mail.
Hi,
Thanks for your reply,
I'm afraid I've always found the bug tracker a very inaccessible thing.
Despite having a decent amount of technical knowledge, I find it
daunting, and a jarring thing to cope with mentally.
This is why i come to the mailing lists to seek help, but a
On Fri Jul 26, 2024 at 10:47 AM BST, Nicolas George wrote:
> Now maybe you fix your MUA configuration to not omit “Re: ”.
What would that achieve?
--
Please do not CC me for listmail.
👱🏻 Jonathan Dowland
✎j...@debian.org
🔗 https://jmtd.net
ncement being made, someone will need
to spend the time to write up a summary and submit it as a bug against
the cryptroot-initramfs package. (perhaps the cryptroot-initramfs
maintainers decide the bug better belongs to another component: bugs can
be re-assigned after filing with ease).
>From t
Hi,
On Fri, Jul 26, 2024 at 10:35:03AM +0100, Ian Molton wrote:
> Should this be reported somewhere else? Any devs reading this?
Yes, if you think there is a bug it should be reported in
bugs.debian.org. The "reportbug" program may help.
This mailing list is mostly for user sup
On Fri, Jul 26, 2024 at 11:05:45PM +0100, Ian Molton wrote:
> Really helpful. Thanks for that.
C'm on Ian.
On another post you complained about the community falling to pieces.
There are many causes for it. This is one.
I know -- the poster you're replying to can be very caustic (sometimes,
in m
Really helpful. Thanks for that.
Really makes one feel part of the community.
Ian Molton (12024-07-26):
> Now what?
Now maybe you fix your MUA configuration to not omit “Re: ”.
Regards,
--
Nicolas George
Now what?
Should this be reported somewhere else? Any devs reading this?
booted and I again unlocked it via the (keyboard) console.
This resulted in a clean boot with no untoward errors.
I shut it down, and rebooted, and now it boots successfully even if I
unlock it via the ssh connection.
I feel like this is a bug in cryptroot-initramfs - surely it would be
On Tue, Jul 16, 2024 at 05:49:47AM GMT, Richard Bostrom wrote:
> /etc/resolv.conf does not block out pornography
It isn't supposed to.
You may block specific domains by adding lines like
0.0.0.0www.google.com
in /etc/hosts. The second part is the domain to block, the first is the IP
add
On 16/07/2024 15:13, to...@tuxteam.de wrote:
Richard Bostrom wrote:
Bug in my opinion.
/etc/resolv.conf does not block out pornography
[...]
I'd put it in other words: DNS doesn't serve porn :-)
Are you sure that no troll have put some funny ASCII-art in their txt
records?
On 7/16/24 02:06, Richard Bostrom wrote:
Bug in my opinion.
/etc/resolv.conf does not block out pornography
That is not its job.
Yours sincerely
Richardh Bostrom
Sent with Proton Mail <https://proton.me/> secure email.
Cheers, Gene Heskett, CET.
--
"There are four boxes
On Tue, Jul 16, 2024 at 03:32:36AM -0400, Dan Ritter wrote:
> Richard Bostrom wrote:
> > Bug in my opinion.
> >
> > /etc/resolv.conf does not block out pornography
>
>
> /etc/resolv.conf is where you configure one or more DNS servers.
> Three is usually optima
Richard Bostrom wrote:
> Bug in my opinion.
>
> /etc/resolv.conf does not block out pornography
/etc/resolv.conf is where you configure one or more DNS servers.
Three is usually optimal.
If you choose DNS servers that resolve everything, you get
everything. If you choose DNS serve
Bug in my opinion.
/etc/resolv.conf does not block out pornography
Yours sincerely
Richardh Bostrom
Sent with [Proton Mail](https://proton.me/) secure email.
On 7/14/24 00:57, Richard Bostrom wrote:
Executing this script halts it after the tar with the following message.
--
#!/bin/sh
tar -zcvf bak.tar.gz /home/user/Documents &&
gpg -r backup@user.local -e bak.tar.gz &&
rm -rf bak.tar.gz &&
rsync -vac --delete /home/user/Documents/bak.tar.gz.gpg /medi
Richard Bostrom (12024-07-14):
> tar -zcvf bak.tar.gz /home/user/Documents &&
Information missing: what is the current directory.
> gpg -r backup@user.local -e bak.tar.gz &&
> rm -rf bak.tar.gz &&
> rsync -vac --delete /home/user/Documents/bak.tar.gz.gpg /media/user/6548-2136
> &&rm -rf bak.tar
Executing this script halts it after the tar with the following message.
--
#!/bin/sh
tar -zcvf bak.tar.gz /home/user/Documents &&
gpg -r backup@user.local -e bak.tar.gz &&
rm -rf bak.tar.gz &&
rsync -vac --delete /home/user/Documents/bak.tar.gz.gpg /media/user/6548-2136
&&rm -rf bak.tar.gz.gpg
вс, 30 июн. 2024 г. в 17:23, Uno Qualsiasi :
>
> Buongiorno vi contatto per segnalare un problema nel processo di
> installazione di debian 12.5.0 dvd iso 32 bit, ossia che quando arriva al
> momento di eseguire “grub-install” su disco primario mi fa errore. Su
> qualsiasi pf 32 bit lo provi è f
On 30 Jun 2024 09:11 +0200, from unoqualsiasi...@icloud.com (Uno Qualsiasi):
> Buongiorno vi contatto per segnalare un problema nel processo di
> installazione di debian 12.5.0 dvd iso 32 bit, ossia che quando arriva al
> momento di eseguire “grub-install” su disco primario mi fa errore. Su
> qu
Buongiorno vi contatto per segnalare un problema nel processo di installazione
di debian 12.5.0 dvd iso 32 bit, ossia che quando arriva al momento di eseguire
“grub-install” su disco primario mi fa errore. Su qualsiasi pf 32 bit lo provi
è fa lo stesso problema.
Inviato da Uno qualsiasi
Daniel Rodriguez writes:
> The solution of the post to this issue is to update the kernel from
> 6.1.0-13 -> 6.1.0.18; however, my kernel is a later version:
> 6.1.0-21-amd64, so I am stuck for solving this issue. Do you have any
> idea about what may be happening and/or how to solve it?
I wonde
**
> [/usr/src/linux-headers-6.1.0-21-common/scripts/Makefile.modfinal:63:
> /var/lib/dkms/nvidia-current/525.147.05/build/nvidia-peermem.ko] Error 127
> make[3]: *** Deleting file
> '/var/lib/dkms/nvidia-current/525.147.05/build/nvidia-peermem.ko'
>
The post
<https://fo
On Thu, Jun 13, 2024 at 06:59:49AM +0200, Kamil Jońca wrote:
> to...@tuxteam.de writes:
[...]
> > and of course, if you are using a desktop environment and NetworkManager
> > or systemd-networkd, it's probably better to go with the flow and let
> > them do.
>
> About year ago none of them was ab
to...@tuxteam.de writes:
> On Thu, Jun 13, 2024 at 06:30:27AM +0200, to...@tuxteam.de wrote:
>
> [following up on myself, bad style, I know]
>
>> For my laptop, I very much prefer to say "sudo ifup eth0" than to
>> say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :)
>
> and of course, if you are usin
On Thu, Jun 13, 2024 at 06:30:27AM +0200, to...@tuxteam.de wrote:
[following up on myself, bad style, I know]
> For my laptop, I very much prefer to say "sudo ifup eth0" than to
> say "sudo ifup en0ps&&@*#!☠" thankyouverymuch :)
and of course, if you are using a desktop environment and NetworkMa
On Wed, Jun 12, 2024 at 03:16:41PM -0400, Greg Wooledge wrote:
> On Wed, Jun 12, 2024 at 09:01:44PM +0200, to...@tuxteam.de wrote:
[...]
> > Mine loks like this:
> >
> > GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"
>
> People who are thinking of doing this should take a moment to consider
bian defaults to. So question is,
> can this be disabled on Proxmox? But with this hint, it should be
> easy enough to figure out if this can be deactivated on the affected
> systems, and if not the bug reports must be against these issues, as
> Debian itself doesn't do such thing
On Wed, Jun 12, 2024 at 09:01:44PM +0200, to...@tuxteam.de wrote:
> No need. You can have your traditional names (I do). Just add
> "net.ifnames=0" (if necessry separated by a space, should
> other stuff be already there) to your GRUB_CMDLINE_LINUX_DEFAULT
> in your /etc/default/grub, then ru updat
On Wed, Jun 12, 2024 at 02:30:40PM -0400, Roy J. Tellason, Sr. wrote:
> On Wednesday 12 June 2024 06:54:54 am Richard wrote:
> > But also, just
> > searching the web for this topic, you should have come across this
> > answering your questions: https://wiki.debian.org/NetworkInterfaceNames
> >
>
On Wednesday 12 June 2024 06:54:54 am Richard wrote:
> But also, just
> searching the web for this topic, you should have come across this
> answering your questions: https://wiki.debian.org/NetworkInterfaceNames
>
Wow. Just wow...
That sort of thing just drives me crazy! :-)
I can see sticki
this be
disabled on Proxmox? But with this hint, it should be easy enough to figure
out if this can be deactivated on the affected systems, and if not the bug
reports must be against these issues, as Debian itself doesn't do such
things. If it is an issue with Debian preventing the disablement,
them to take this up with the upstream devs themselves, so by the
> time Trixie is being released, it may already be included.
>
> But besides that, what you describe in the first link sounds to me not like a
> bug, but as a well thought-through decision. Network adapter names like eth0
ie is being released, it may already be included.
But besides that, what you describe in the first link sounds to me not like
a bug, but as a well thought-through decision. Network adapter names like
eth0 have been dropped with Debian 11 (I think, maybe even 10). So don't
get your hopes up too hi
Hello,
This bug, or a close relative, has already been reported in
https://github.com/raspberrypi/bookworm-feedback/issues/239
as 'Predictable network names broken for ASIX USB ethernet in kernel 6.6.20'
I added a comment reporting my experience in Proxmox here:
https://github.com/r
ould be a fix for this or at least a way to handle this case with a much
> clearer error message. So I'll probably open a bug report for the package
> and the maintainer can decide if that should be forwarded upstream. Such a
> rather trivial case shouldn't be resulting in such fa
On 26/04/2024 12:56, David Wright wrote:
On Fri 26 Apr 2024 at 11:27:24 (+0900), John Crawley wrote:
Innocent question: what difference does the comment make vs just ending the
file with an empty line?
Nothing for the computer, but visibility for me.
Say you print the file on paper. All you
On 26/04/2024 10:56, David Wright wrote:
Editor examples: a windowed emacs buffer has a ≣ decoration at the
extreme left edge after the last line of text, so that you can
distinguish an absence of lines from empty lines.
Perhaps that decoration should be explicitly enabled. However it
reminded
can't handle the case that crypttab ends in the
> > > line
> > > of the last entry and not in a new line character. I think there either
> > > should be a fix for this or at least a way to handle this case with a much
> > > clearer error message. So I'l
acter. I think there either
should be a fix for this or at least a way to handle this case with a much
clearer error message. So I'll probably open a bug report for the package
and the maintainer can decide if that should be forwarded upstream. Such a
rather trivial case shouldn't be re
; should be a fix for this or at least a way to handle this case with a much
> clearer error message. So I'll probably open a bug report for the package
> and the maintainer can decide if that should be forwarded upstream. Such a
> rather trivial case shouldn't be resulting in
with a much
clearer error message. So I'll probably open a bug report for the package
and the maintainer can decide if that should be forwarded upstream. Such a
rather trivial case shouldn't be resulting in such fatal errors.
Best
Richard
On Wed, Apr 24, 2024, 14:23 Michel Verdier wr
Hello Hans,
this is exactly what I did. To be precise, I followed this guide [1], with
the difference that instead of "crypt" I used the actual name, luks-
(Disks thanksfully shows everything relevant). It's not the first time I'm
doing this. Yet I experience the errors mentioned. Sure, I'm not usi
gt; luks,keyscript=/bin/cat
initramfs extract line from /etc/crypttab to create its own crypttab
as you have seen in main/cryptroot/crypttab, and only for rootfs, not for
swap
> Now, is this a bug in the package or am I missing something? And how do I
> create a working initramfs now?
swap
Am Dienstag, 23. April 2024, 22:26:17 CEST schrieb Richard:
Hi Richard,
this is, what I am doing when this happens:
1. booting into a live system (any new is working, I prefer kali-linux)
2. If you are using encrypted filesystems, open it. But you have to name it
like it is named in /
etc/crypt
thout
mounting the swap partition to try to run "update-initramfs -ck all" from
there. But now it even refuses to find the root partition in crypttab.
Now, is this a bug in the package or am I missing something? And how do I
create a working initramfs now?
Best
Richard
> For what I understood the problem was fixed in 6.8, but I'm using
> debian 12 that will never use that so much new kernel I guess, could
> you help me to report officially the bug so that the upstream channel
> will correct it by the 6.1.0-22 version ?
Bookwom backports has linu
ss-ea
For what I understood the problem was fixed in 6.8, but I'm using debian 12
that will never use that so much new kernel I guess, could you help me to
report officially the bug so that the upstream channel will correct it by
the 6.1.0-22 version ?
Thank you very much!
On 2 Apr 2024 10:27 +0200, from jch...@student.ethz.ch (Jonathan Chung):
> Can someone help me to file a bug report?
https://www.debian.org/Bugs/Reporting
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
getting to grips with this bug
>>> (actually multiple bugs), and it looks like a fix may be forthcoming,
>>> though not sure at the time of writing if there may be some further
>>> polishing first
>>>
>>> https://github.com/openzfs/zfs/pull/16019
&g
On 3/25/24 15:05, Gareth Evans wrote:
On Fri 22/03/2024 at 21:01, Gareth Evans wrote:
As anyone interested can see from the ref to #15933 in the below, there seems
to have been considerable effort in getting to grips with this bug (actually
multiple bugs), and it looks like a fix may be
On Fri 22/03/2024 at 21:01, Gareth Evans wrote:
> As anyone interested can see from the ref to #15933 in the below, there seems
> to have been considerable effort in getting to grips with this bug (actually
> multiple bugs), and it looks like a fix may be forthcoming, though not sure
s to have tested
> extensively, considered the issue closed after upgrade to openzfs 2.2.2
>
> https://bugs.gentoo.org/917224#c26
>
> I wonder if the 2.2.3 issue is similar/related, or perhaps there are multiple
> triggers.
>
> Watching with interest.
>
> Best wishes,
&g
package.
Thanks for you help.
apt-file shows au0828.ko comes in the linux-image-* packages. So report
the bug for the one you use.
Hi,
I have a possible kernel regression for a usb-dvb tuner card. I know
the error in dmesg points to kernel : au0828 but I am not sure what
package this belongs to. I think it belongs to v4l(video for linux) but
I am still not sure what specific v4l package.
Thanks for you help.
Hi,
Since the upgrade of the Pango library to 1.52 in Debian/unstable, I'm
seeing an annoying bug in gnuplot with the wxt terminal. The issue can
be reproduced with the following command:
echo 'set terminal wxt; plot x' | gnuplot -persist
A window appears, but it is not drawn a
On Tue Feb 27, 2024 at 7:12 AM GMT, Frank Weißer wrote:
> So we are at my original question: Which package to file a bug report ?
Package "debian-installer", I think; and/or submit an installation report,
which can be done with reportbug against the "installation-report&qu
On Tue 27/02/2024 at 22:52, David Christensen wrote:
> ...
> These appear to be the ZFS packages for the available Debian releases:
>
> https://packages.debian.org/buster/zfs-dkms
>
> busterzfs-dkms (0.7.12-2+deb10u2)
> buster-backports zfs-dkms (2.0.3-9~bpo10+1)
> bul
On 2/26/24 20:52, Gareth Evans wrote:
Replied to OP by mistake, reposting to list.
On Sun 25/02/2024 at 05:34, David Christensen wrote:
debian-user:
Is Debian 12.5.0 amd64 affected by OpenZFS bug #15526?
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64
Marco Moock:
Am Fri, 23 Feb 2024 13:59:41 +0100
schrieb Frank Weißer :
The installer does format it as ext4, but shows ext2 and places that
in fstab, what ends up in emergency mode. That's why I'm here
That is definitely a bug.
So we are at my original question: Which package
On Tue 27/02/2024 at 04:52, Gareth Evans wrote:
> https://github.com/openzfs/zfs/issues/15933
>
> seems to suggest that or a similar issue is still ongoing with Open ZFS
> 2.2.3 ...
I wonder if that might be a regression, since what I think is the same issue as
openzfs #15526 appeared to be re
Replied to OP by mistake, reposting to list.
On Sun 25/02/2024 at 05:34, David Christensen wrote:
> debian-user:
>
> Is Debian 12.5.0 amd64 affected by OpenZFS bug #15526?
>
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netins
debian-user:
Is Debian 12.5.0 amd64 affected by OpenZFS bug #15526?
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso
https://packages.debian.org/bookworm/zfs-dkms
https://github.com/openzfs/zfs/issues/15526
David
u format it manually?
> >
> The installer does format it as ext4, but shows ext2 and places that
> in fstab, what ends up in emergency mode. That's why I'm here
That is definitely a bug.
Am Fri, 23 Feb 2024 14:47:41 -0500
schrieb James Klaas :
> "Generic PCL 6/PCL XL Printer Foomatic/pxlcolor (recommended)"
Do you know the file that provides that?
If so, you apt-file search "file" to find the package that provides it.
I was going to submit a bug for this but I don't know what package I
should report the bug against.
Debian bugreport says:
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem. If you don't know what
p
1 - 100 of 1806 matches
Mail list logo
