On Mon, 24 Apr 2023 at 14:05, James Addison wrote:
>
> However: I do have problems playing an MP4 video file with the
> 'default' video output driver selected. Maybe that is the same issue
> with VAAPI.. or maybe something else. I'll spend some time to check,
> I t
On Sun, 23 Apr 2023 at 00:28, Nicholas D Steeves wrote:
>
> You're welcome! Also, yes, your hypothesis about DVB support being lost
> when the Debian packages adapted to upstream's waf-to-meson change was
> correct. The way always screen for this type of thing is using the
> "elpa-git-timemachin
Package: libgtk-3-0
Followup-For: Bug #1034289
X-Debbugs-Cc: giuseppe.bilo...@gmail.com
Hi Giuseppe,
If possible: can you share some more information about your use-case for XIM
as an input method (either with Inkscape in particular, or more generally on
the relevant system(s)).
Thanks,
James
Followup-For: Bug #1034289
X-Debbugs-Cc: giuseppe.bilo...@gmail.com, debian-multime...@lists.debian.org
Control: reassign -1 libgtk-3-0
Control: affects -1 inkscape
Control: tags -1 patch
After testing the patch (that is based on a suggestion in an upstream GTK bug
discussion thread[1]), I can con
Package: inkscape
Version: 1.2.2-2+b1
Followup-For: Bug #1034289
After installing a fresh Debian bookworm system and installing the 'inkscape'
package (version 1.2.2-2+b1), I can confirm that this issue is reproducible; it
can be found by running:
$ GTK_IM_MODULE=xim inkscape
... and from ther
b.gnome.org/GNOME/gtk/-/issues/2560
[2] - https://gitlab.gnome.org/GNOME/gtk/-/issues/2560#note_757809
Description: gdkwindow: allow frame paint events to occur for non-toplevel
windows
.
Partially-reverts upstream commit fc569f1ac6ff108afc17f7f439480273826af3a6.
Author: James Addison
Bug: https://g
Source: mpv
Followup-For: Bug #1026060
X-Debbugs-Cc: s...@debian.org
Thanks, Nicholas!
Although I don't have a DVB device to test with locally, the fix makes sense
to me, and I'm glad to read from Alf's report that it is working.
Regards,
James
Source: mpv
Followup-For: Bug #1026060
X-Debbugs-Cc: patchesthomas@web.de, alf.debian...@gmx.de
Hi,
I haven't 100% confirmed this, but from some inspection it looks like DVB
support may be disabled-by-default based on the meson options[1] in the source
package for mpv.
The upstream source be
Package: python3-sphinx
Followup-For: Bug #998059
X-Debbugs-Cc: la...@debian.org
Control: found -1 4.5.0
Control: notfound -1 5.0.0
Dear Maintainer,
My updated understanding is that this issue was fixed[1] in version 5.0.0 of
Sphinx.
I've documented[2] the process I followed using 'git bisect' t
Followup-For: Bug #994274
X-Debbugs-Cc: lu...@schwaighofer.name, pk...@debian.org, timo.lindf...@iki.fi
Hi Lukas, Philipp, Timo,
Does reverting the removal[1] of 'efisetjmp.h' from 'efi.h' in src:gnu-efi
produce successful results?
That occurred between gnu-efi versions 3.0.9 and 3.0.13 if I rea
Followup-For: Bug #973414
X-Debbugs-Cc: fierel...@gmail.com
On Mon, 3 Apr 2023 23:07:35 +0200, Fierelier wrote:
> * In terms of confusion: I think using the Rust i586 toolchain, and
> building for i586 with Rust might be less confusing, because altering
> the i686 definitions for rustc will make i
es
> > > that only process the packages detected by lintian.
On Mon, 20 Mar 2023 12:05:24 +, James Addison wrote:
> > That's not a bad idea. Are there any reasons that that might _not_ be a
> > good
> > idea before filing a wishlist bug? (performance, implicat
Package: release-notes
Followup-For: Bug #1033564
X-Debbugs-Cc: anar...@debian.org
Hi Antoine - this seems related to - perhaps an extension of? - some discussion
on Salsa: https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/142
(I'll admit that I don't tend to use 'pipx' either. I
Package: rustc
Followup-For: Bug #973414
X-Debbugs-Cc: fierel...@gmail.com
Hi Fierelier - thanks for your previous comment, here's my reply, slightly
later than I'd hoped:
On Wed, 29 Mar 2023 00:10:52 +0200, Fierelier wrote:
> - issue 1: i386, i486, i586, i686 are considered as Pentium 4 in LLVM,
ebian is viable on baseline hardware.
.
Ref: https://wiki.debian.org/ArchitectureSpecificsMemo#i386-1
Author: James Addison
Last-Update: Wed 29 Mar 18:24:38 BST 2023
Bug: https://bugs.debian.org/973414
Forwarded: not-needed
X-Not-Forwarded-Because: upstream consensus on i686 differs
---
---
rustc-1.63.0+dfsg1.o
Package: rustc
Followup-For: Bug #973414
X-Debbugs-Cc: fierel...@gmail.com
After a few false starts, I've built libstd-rust-dev:i386 targeting i686 in the
way I'd expected (and to clarify: the interpretation I'm using is to match
Debian's baseline and a strict-ish reading of what P6 / i686 was whe
Hi Brendon (and with the relevant Debian bug thread on cc),
I've uploaded a copy of the packaged quadrilateralcowboy game source -
with some small modifications and fixes, including ARM64 support - to
the 'mentors.debian.net' pre-review site at
https://mentors.debian.net/package/quadrilateralcowbo
Package: lintian
Followup-For: Bug #1033294
X-Debbugs-Cc: patrice.dur...@gmail.com, debian...@lists.debian.org
As guidance for potential contributors: it looks like the logic for the
existing 'python-module-in-wrong-location' check (mentioned in the mailing list
thread) is here:
https://sources.d
Package: rustc
Followup-For: Bug #973414
> Today I plan to rebuild rustc on Debian i386 with RUSTC_FLAGS (different to
> RUSTFLAGS) configured for i686 during the build. That's inspired by a comment
> here: https://github.com/rust-lang/rust/pull/31110#issuecomment-174327810
>
> To implement that
Package: dpkg-dev
Followup-For: Bug #1021292
X-Debbugs-Cc: woo...@wookware.org, debian-de...@lists.debian.org
> We decided that the best thing to do was create a new hardening flags
> feature called 'branch' to add to the existing set. This enables
> -mbranch-protection=standard on arm64, and
> -f
Package: wnpp
Severity: wishlist
* Package name: edit-tf
Version : 1.0.0
Upstream Contact: Simon Rawles
* URL : https://edit.tf/
* License : GPL-3
Programming Lang: HTML, JavaScript
Description : teletext frame editor for use within web browsers
edit-t
acher wrote:
>
> On 2023-03-25 19:56:32 +, James Addison wrote:
> > Source: libass
> > Version: 1:0.17.1-1
> > Followup-For: Bug #1033381
> > Control: retitle -1 libass: nasm: use i386-baseline compatible NOP alignment
> > Control: tags -1 patch
> >
Package: rustc
Followup-For: Bug #973414
> On Fri, 24 Mar 2023 14:23:18 +, James wrote:
> > In particular, one area to look at:
> >
> >
> > https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L70
>
> Line range correction:
>
>
> https://g
Followup-For: Bug #973414
On Fri, 24 Mar 2023 14:23:18 +, James wrote:
> In particular, one area to look at:
>
>
> https://github.com/llvm/llvm-project/blob/llvmorg-14.0.6/clang/lib/Driver/ToolChains/Arch/X86.cpp#L25-L70
Line range correction:
https://github.com/llvm/llvm-project/blob/
On Fri, 24 Mar 2023 at 13:50, Helmut Grohne wrote:
>
> Thank you very much for your review and the attention to detail. I
> concur with your observation and have updated the patch accordingly.
> This part slipped my testing, because I never tried the clean target and
> most cross builds never clea
Package: rustc
Followup-For: Bug #973414
X-Debbugs-Cc: martin-eric.rac...@iki.fi, fierel...@gmail.com, s...@debian.org,
ru...@packages.debian.org
I've been trying to track down 'NOPL' opcodes in Debian's i386 bookworm archive
and many of the affected cases appear Rust and/or LLVM-related.
The si
Source: libselinux
Followup-For: Bug #1022964
X-Debbugs-Cc: hel...@subdivi.de
Hi Helmut,
Could you check whether the patch is missing a 'call ruby_env' line in the
debian/rules 'override_dh_auto_clean' target?
(it looks like it could be, but I may be mistaken)
Thanks,
James
Followup-For: Bug #1005863
Control: affects -1 = sudo
Source: x265
Version: 3.5-2
Severity: wishlist
Dear Maintainer,
The use of nasm 'ALIGNMODE p6'[1] in upstream's x265 source results in the nasm
assembler emitting multi-byte no-op (NOPL) instructions that are not compatible
with all systems within Debian's i386 baseline (for example: Geode LX doe
Package: apt
Severity: wishlist
Similar to the way that 'apt changelog ' displays the changelog for a
given package -- and downloads the relevant entries if they are not available
locally -- it could be convenient to allow users to review dpkg-parsechangelog
compatible NEWS.Debian.gz history for p
Followup-For: Bug #1005886
X-Debbugs-Cc: powe...@gmail.com
Control: reassign -1 cdimage.debian.org
Control: retitle -1 cdimage.debian.org: bookworm net-install CD hangs on
"Detecting Network Hardware"
Sorry (both to you Tony, and also the Debian CD team) for confusion and wasting
time - I mistake
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: elb...@debian.org
Control: severity -1 serious
Increasing this bug's severity to a release-critical, based on mailing list
discussion[1].
Paul: bug #1005863 has most of the relevant context for Debian, although I'd
recommend the foll
Followup-For: Bug #1032351
Control: archive -1
Followup-For: Bug #1032347
Control: archive -1
Followup-For: Bug #1005863
X-Debbugs-Cc: ballo...@debian.org
Control: reassign -1 binutils 2.38-1
Reassigning this from package 'gcc' to 'binutils':
It looks like it is GNU binutils[1] (and in particular, the GNU assembler)
that is responsible for producing the assembly opcodes for a binary compi
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: p...@debian.org, ballo...@debian.org
Dear Maintainer and Éric-Martin (with Bill on carbon copy),
Please find linked below a previous release note from Debian 9.0 (stretch)
that we could use to provide relevant user guidance:
https:/
On Mon, 20 Mar 2023 at 07:22, Bastian Blank wrote:
>
> On Sun, Mar 19, 2023 at 11:47:21PM +, James Addison wrote:
> > Would it be fair to raise the severity of this bug to a release-critical
> > level?
>
> No, it would be fair to remove Geode LX from the set of suppor
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: debian-...@lists.debian.org, debian-rele...@lists.debian.org,
debian-pol...@lists.debian.org
Hi folks,
Bug #1005863 describes a gcc-11 behaviour that results in software that exits
ungracefully on Geode LX i686 hardware. Despite self-repo
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: martin-eric.rac...@iki.fi
> So my guess is that approximately 6-7% of i386 packages in bookworm _that
> contain binaries or shared libraries_ are susceptible to this bug.
...
> It's also a larger number of packages than we could expect ind
Followup-For: Bug #1032347
X-Debbugs-Cc: gunna...@debian.org
Hi Gunnar - although we agreed to close this bug, I'd like to add a message
about your comment:
> At some point of time, when configuring the keyboard configuration on
> the system level, you apparently set that value. To see how it co
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: martin-eric.rac...@iki.fi
Ok; I should have realised that scanning the entire contents of the i386
bookworm archive for particular opcodes across _all_ files on a single machine
seemed to complete surprisingly quickly..
Please find attached
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: martin-eric.rac...@iki.fi
Control: affects -1 + sudo
> That's three potential positives; in total, the check ran on approximately
> thirty-two thousand (32340, to be more precise) packages.
My apologies: there was a bug in the script to run
Package: gcc-11
Followup-For: Bug #1005863
X-Debbugs-Cc: martin-eric.rac...@iki.fi
Control: affects -1 - sudo net-tools
Control: affects -1 + libjavascriptcoregtk-4.0-18
Control: affects -1 + gobjc++-12-x86-64-linux-gnu
Control: affects -1 + libfsapfs-dev
Dear Maintainer and Martin-Éric,
Using a
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: martin-eric.rac...@iki.fi
I've used the following commands to confirm that the i386 sudo/1.9.9-1 package
contains the bugreport-relevant NOPL opcode:
# obtain an archived copy of the affected binary package
$ wget2
http://snapsh
Package: wnpp
Followup-For: Bug #1026277
Control: tags -1 - help pending
Based on developing a better understanding of Debian's usertags, I don't think
that the 'help' and 'pending' tags currently apply here, so I'm going to remove
them from the bug. Reasoning below:
* my interpretation of 'pe
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: martin-eric.rac...@iki.fi
Hi Martin-Éric - I intended to send my previous comment to you, but forgot to
add you to on carbon-copy.
Roughly speaking: I'm wondering whether there is a way that we can scan i386
architecture packages in
Package: release-notes
Followup-For: Bug #1033065
X-Debbugs-Cc: 1005...@bugs.debian.org
Control: affects 1005863 net-tools
Control: tags -1 moreinfo
> While a kernel compiled for Geode LX (essentially a basic i686 without the
> optional CPU features) still ships in Debian, many packages enforce C
Followup-For: Bug #1031909
Control: tags -1 patch
Package: python3-tk
Followup-For: Bug #1031909
Dear Maintainer,
Please find a merge request on Salsa to resolve this issue for future versions
of python3-tk at
https://salsa.debian.org/cpython-team/python3-stdlib/-/merge_requests/5
This has been tested by installing the previous version of the
Package: debian-cd
Followup-For: Bug #1031696
On Wed, 15 Mar 2023 00:04:28 +, James Addison wrote:
> I haven't (have not) been able to install Debian from FAT32-based media
> created
> using file-copy from either of these two approaches.
> In both cases d-i integrity ch
Followup-For: Bug #1031696
On Mon, 13 Mar 2023 01:04:26 +, James Addison wrote:
> I've been able to build local NETINST ISO images successfully using the merged
> changes (thanks, Steve), and was also able to file-copy them to a FAT32
> filesystem and successfully boot from th
Followup-For: Bug #960727
Control: block -1 by 1031909
Source: pylint
Followup-For: Bug #1032544
X-Debbugs-Cc: w...@wrar.name, lu...@debian.org
> This may be related, or just a duplicate, to #1032043, fixed in the newer
> version which is already in testing.
Yep, agreed that the updated testing package upload fixes this.
(it looks like the testing d
Followup-For: Bug #1000955
Control: severity -1 normal
A summary of a side-discussion between Filippo and myself about this bug:
* Although the bug doesn't appear reproducible today, the cause hasn't been
confirmed.
* We both agreed that it makes sense for bugs to continue to stay open u
Followup-For: Bug #1031696
Control: tags -1 - moreinfo
I've been able to build local NETINST ISO images successfully using the merged
changes (thanks, Steve), and was also able to file-copy them to a FAT32
filesystem and successfully boot from that into Debian Installer using QEMU.
Building imag
Package: debian-cd
Followup-For: Bug #1031696
> >Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS
> >achieve the desired result for both documentation and firmware files, without
> >requiring any other changes?
> No, then I expect we'll simply end up with duplicate copies
Followup-For: Bug #1031696
Thinking aloud: as an alternative, would adding the '-f' flag to MKISOFS
achieve the desired result for both documentation and firmware files, without
requiring any other changes?
(I'll mention as context that there are symlinks in the debian-faq tarball
that is used as
Package: debian-cd
Followup-For: Bug #1031696
X-Debbugs-Cc: scdbac...@gmx.net
Please find below a proposed update to the commit message under discussion:
nonfree-firmware: when creating on-disc firmware links, use the same link
creation logic as archive-area links
This changeset swi
Package: debian-cd
Followup-For: Bug #1031696
Thank you again Thomas.
I've opened a merge request at
https://salsa.debian.org/images-team/debian-cd/-/merge_requests/30
My Debian mirror is still under construction, hence the 'draft' status for
the merge request (to indicate that I'm not certain
Followup-For: Bug #1031696
On Sat, 11 Mar 2023 18:10:22 +0100, Thomas Schmitt wrote:
> ifneq (,$(filter i386 amd64 arm64 hppa,$(ARCHES)))
> Surely i386, amd64, and arm64 get their published Debian ISOs made
> by xorriso.
I think your expectation is correct there, yes: looking further into the
Followup-For: Bug #1031696
On Sat, 11 Mar 2023 12:16:47 +0100, Thomas Schmitt wrote:
> This could be achieved by a bunch of hard links instead of the symbolic
> links. In /firmware of firmware-bookworm-DI-alpha1-amd64-netinst.iso
> i see only symbolic links to data files. So replacing symlinks by
Package: nodejs
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@mirbsd.de
On Thu, 02 Feb 2023 01:56:10 +, Thorsten wrote:
> I consider this an architecture-specific release-critical bug. Maybe
> having a reproducer and access to a porterbox will allow a nodejs
> maintainer to track this down.
B
Package: nodejs
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@debian.org
Guidance received from the V8 project (a vendored dependency in the upstream
NodeJS codebase) on the v8-dev mailing list is, in summary/interpretation:
* It is not yet safe to increase the stack size limit on ARM64 systems
Package: debian-cd
Followup-For: Bug #1031696
Hi Pete - could you check my understanding of your paragraph:
> In short, if this issue is left unaddressed, bookworm will be
> introducing a *regression* compared to bullseye, in that it will no
> longer be possible to perform a Debian installation
Package: debian-cd
Followup-For: Bug #1031696
On Sat, 11 Mar 2023 03:31:50 +, Pete wrote:
> Just going to add, in case you wonder why it shouldn't be up to the
> software that is mounting the ISO to sort out symbolic links and just
> duplicate content, that neither Windows File Explorer nor
Followup-For: Bug #1031696
X-Debbugs-Cc: p...@akeo.ie
Control: reassign -1 debian-cd
Control: tags -1 moreinfo
I forgot to mention: thanks, Pete, for testing this UEFI file transposition
support
with bookworm's d-i alpha 2.
We're all volunteers and I'm no expert with the CD image build process,
Followup-For: Bug #1005886
Control: reassign -1 debian-cd
Control: retitle -1 debian-cd: bookworm net-install CD hangs on "Detecting
Network Hardware"
Package: cdimage.debian.org
Followup-For: Bug #1031696
X-Debbugs-Cc: p...@akeo.ie
My best guess at the moment is that the relevant section of the CD image
preparation scripts is:
https://salsa.debian.org/images-team/debian-cd/-/blob/5aebb6794a3b8b2393663fb643e35eb8e510c9a4/tools/make_disc_trees.p
Followup-For: Bug #1026062
Control: reassign -1 libpackagekitqt5-1 1.1.0-1
Control: retitle -1 packagekit-qt: use-after-free in PackageKit::Transaction
Control: affects -1 kded5
Control: forwarded -1 https://github.com/PackageKit/PackageKit-Qt/issues/42
Control: tags -1 fixed-upstream
Followup-For: Bug #1032351
X-Debbugs-Cc: bi...@debian.org
On Tue, 7 Mar 2023 14:43:16 +0100, Michael Biebl wrote:
>
> Am 06.03.23 um 13:31 schrieb James Addison:
> > Various other user-context systemd files appear to be missing; I don't think
> > those were removed from t
Source: installation-guide
Followup-For: Bug #1031738
I'm attempting to rephrase the documentation related to this bug in a merge
request on Salsa:
https://salsa.debian.org/installer-team/installation-guide/-/merge_requests/24/
If anyone would like to review the suggested changes there (or even
Package: python3-dateutil
Followup-For: Bug #1003044
X-Debbugs-Cc: debian-le...@lists.debian.org
(adding debian-legal on cc for any sanity-checks available)
To recap: we have a bug, #1003044, that is rated 'grave', and so it is
considered release-critical for Debian bookworm, although without a w
Source: installation-guide
Followup-For: Bug #1031738
Control: tags -1 patch
Please note: the patch previously offered here isn't suitable; it turns out
that the param limits described in it (32 for Linux, 128 for User Mode Linux)
apply only to the number of argument items that are passed to the '
Followup-For: Bug #1032347
On Mon, 6 Mar 2023 13:40:30 +0100, Gunnar wrote:
> So what is it on your system which causes 'compose:lwin' to be set
> behind the scenes? Since I can't reproduce the issue, I doubt it is
> gnome-control-center.
Thanks for reconfirming. I now believe (and have update
Package: wireplumber
Followup-For: Bug #1032351
Control: close -1
After rebooting the system, sound is available again.
Various other user-context systemd files appear to be missing; I don't think
those were removed from the system manually, but nor can I confirm yet what
the cause was (if I can,
Package: wireplumber
Followup-For: Bug #1032351
Package 'dbus-user-session' is-and-was also present on the system:
$ apt list dbus-user-session
Listing... Done
dbus-user-session/testing,now 1.14.6-1 amd64 [installed]
However, some of the systemd user files were missing from the filesystem.
Package: nodejs
Followup-For: Bug #1030284
Echoing some notes and findings from the GitHub issue thread:
* https://crbug.com/405338 seems inaccessible to at least two people
* https://codereview.chromium.org/555943003 was initially proposed to resolve
that bug
* https://codereview.chr
x27;compose:none' doesn't seem to be declared[1] as a valid
xkeyboard-config option.
> James Addison wrote:
> > I agree that '@as []' is written to the 'xkb-options' config entry
> > momentarily after disabling the Compose Key.
> >
> > Ho
Followup-For: Bug #1003044
On Tue, 21 Feb 2023 14:46:01 -0500, morph wrote:
> On Sun, Jan 29, 2023 at 9:45 AM Felix Geyer wrote:
> > How exactly does this break matplotlib?
> it produces output on stderr, which many tools consider it an error
> and fails build.
On Fri, 3 Mar 2023 15:05:03 -0500,
Package: gnome-control-center
Followup-For: Bug #1032347
Gunnar Hjalmarsson wrote:
> James Addison wrote:
> > To explain another way: although disabling the 'Compose Key' using
> > the keyboard panel takes effect in the current session, it is
> > restored to the
Followup-For: Bug #1028743
Control: tags -1 fixed-upstream
Note for maintainers: the patch attached to this bug has been merged into the
upstream 'release-0.12' branch and is included in the 0.12.5 release.
(so hopefully it is possible to drop the patch from packaging for that version
onwards)
T
Followup-For: Bug #1032351
On Sat, 4 Mar 2023 17:40:24 +0100, Michael wrote:
> Is dbus-user-session / libpam-systemd installed?
Yes, both of those packages:
$ apt list dbus-user-session libpam-systemd
Listing... Done
dbus-user-session/testing,now 1.14.6-1 amd64 [installed,automatic]
libp
Followup-For: Bug #1030284
There is one part of this patch that worries me, and it is the line:
> -//See issue crbug.com/405338
I'm not able to access that bug: neither anonymously nor when logged into my
gmail account. The comment would seem to indicate that it contains relevant
context ab
Package: wireplumber
Version: 0.4.13-1
Severity: normal
Dear Maintainer,
On this Debian 12 (bookworm) system, sound output in the GNOME and Wayland
desktop environment became unavailable recently.
The only output device listed in the 'Sound' panel of gnome-control-center
is 'Dummy Output'; howev
Followup-For: Bug #1032347
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/910#note_1688598
Package: gnome-control-center
Followup-For: Bug #1032347
It looks like this could be the same issue as reported in #1027003, except for
a different key within the same settings panel.
Package: gnome-control-center
Version: 1:43.4.1-1
Severity: normal
Dear Maintainer,
The 'Keyboard' panel in gnome-control-center allows configuration of 'Special
Character Entry' keys, and on my system this currently displays two entries:
- Alternative Characters Key (value: Disabled)
- Comp
Package: python3-django-hyperkitty
Followup-For: Bug #1031928
X-Debbugs-Cc: h...@hjp.at
> Can I change the severity of the bug?
You should be able to do that, yes: by placing BTS (bug tracking system)
control commands (as 'pseudoheaders') at the start of your email messages to
bug threads: https:
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: gunna...@debian.org
On Fri, 3 Mar 2023 15:10:30 +0100, Gunnar wrote:
> On 2023-03-03 13:21, James Addison wrote:
> > I also noticed that some of gnome-desktop's default locale-to-input-source
> > mappi
Package: pulseaudio
Followup-For: Bug #1032255
Control: retitle -1 pulseaudio: application restart required to restore sound
Control: severity -1 normal
Control: tags -1 moreinfo
Hi Dave,
Are there any clues (error messages, service start/stops, or things like that)
in the affected system's journ
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
I also noticed that some of gnome-desktop's default locale-to-input-source
mappings provide multiple entries, delimited by the '+' character:
https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/43.2/libgnome-desktop/default-input-sources.h#
Package: python3-django-hyperkitty
Followup-For: Bug #1031928
X-Debbugs-Cc: h...@hjp.at
Hi Peter - one more thought from me:
Would you be willing to send your patch to the upstream hyperkitty project[1]
as well? (likely as a merge request on their GitLab instance)
Since we've found the conditio
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
(comment to bug-thread only)
If it's true that the cause is that 'tasksel' and 'gnome-initial-setup'
are mismatched, then we could apply a fix in either one.
Given that we have an existing patch available for 'gnome-initial-desktop',
I've
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: s...@debian.org, z...@debian.org, ken...@xdump.org,
yy.y.ja...@gmail.com, iwama...@debian.org, gunna...@debian.org,
debian-i...@lists.debian.org, debian-japan...@lists.debian.org,
m...@packages.debian.org, ibus-an...@packages
Package: python3-django-hyperkitty
Followup-For: Bug #1031928
Control: tags -1 - moreinfo
Control: tags -1 + confirmed
Control: severity -1 important
On Thu, 2 Mar 2023 20:30:04 +0100, Peter J. Holzer wrote:
> On 2023-03-02 19:53:12 +0100, Peter J. Holzer wrote:
> > So it seems that my suspicion t
necessarily long path through this. I'd been
looking for a reason to try the latest Debian installer (and may have learned
one or two things about it along the way, but I'll save any of that for
separate threads).
On Wed, 01 Mar 2023 16:47:22 + James Addison wrote:
> 2. select &
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: ken...@xdump.org
On Thu, 02 Mar 2023 22:07:16 +0900 Kentaro Hayashi wrote:
> On Wed, 01 Mar 2023 16:47:22 +0000 James Addison wrote:
> > My plan is to:
> >
> > 1. run the graphical d-i install of a
Source: partman-base
Followup-For: Bug #370487
On Thu, 02 Mar 2023 13:35:29 +, James wrote:
> If the user selects 'undo', or if 'no' is selected and the operator continues
> from the second step, then the user is taken back to the 'partition disks'
> menu without any changes being written to
Source: partman-base
Followup-For: Bug #370487
X-Debbugs-Cc: geye...@googlemail.com
Oops: I provided an update earlier today on this bug that you reported in 2006,
but I forgot to cc your email address, Thomas. Please find my previous comment
in the bug thread.
Source: partman-base
Followup-For: Bug #370487
Hi Thomas,
I discovered this bug while wondering about some of the default options during
the disk partition configuration steps (also known as the 'partman' component)
in the Debian 12 (bookworm) alpha 2 installer.
Since disk partition configuratio
301 - 400 of 533 matches
Mail list logo
