omprog is quite hard to confine correctly in a way that is still usable
for all cases. Whatever you do, it would be best to deal with local
overrides, and not change the main profile shipped by the rsyslog
package.
That being said, I don't know of a way to override the flag: the current
override m
Hello Rico, or anyone else affected,
Accepted libreoffice into oracular-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libreoffice/4:24.8.4-0ubuntu0.24.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new pack
The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that y
The verification of the Stable Release Update for gnome-settings-daemon
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that y
libreoffice autopkgtest failed on amd64[1], I retriggered it.
1. https://ubuntu-archive-team.ubuntu.com/proposed-
migration/oracular/update_excuses.html#evolution-data-server
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data
Thanks for the verification, Alessandro. The test plan however also asks
for execution on intel hardware:
> Install the updates, test desktop use and some basic games etc on at
least AMD and Intel hw.
I will therefore flip the verification tags back to verification-needed for
that reason. Once
Oracular has one regression, and multiple tests in a running state which
I suspect is an incorrect state, given that this package was uploaded
weeks ago.
I've seen this a lot in my shift, particularly with oracular
autopkgtests so far. I'll retrigger the "fake" running tests, and looks
like the fa
Public bug reported:
I'm not sure of the package in this bug, so I selected mutter and will
let you decide.
I was running xorg, but decided to give wayland a try. I logged out,
logged in into a wayland session, adjusted my screen resolution and
scaling to my liking, and thought that was it.
But
Hello Timo, or anyone else affected,
Accepted mesa into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/24.2.8-1ubuntu1~24.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hello Timo, or anyone else affected,
Accepted llvm-toolchain-19 into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-19/1:19.1.1-1ubuntu1~24.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing thi
(b) is ok, I saw the error on our favorite arch (armhf) :)
(c) is minor, as LP will build it just fine, so up to you if you want to
fix it.
+1 from me
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpa
NEW review for spirv-llvm-translator-19.
TL;DR I'm just not sure if the symbols overrides is necessary.
This is a backport from oracular. The diff is:
diff --git a/debian/control b/debian/control
index d6f07f3..b6a6be7 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Uploaders:
The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enc
The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enc
The verification of the Stable Release Update for lp-solve has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
The verification of the Stable Release Update for evince has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
> and verified that when overwriting the currently opened PDF the view
refreshes accordingly.
Thank you for not missing this extra verification step, which was only
outlined in the "Where problems could occur" section.
--
You received this bug notification because you are a member of Desktop
Pac
The verification of the Stable Release Update for udisks2 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
While checking the diff, in noble we see that the patch had some cruft
left over:
$ cat debian/patches/nvme-disk-size.patch |diffstat
b/src/udiskslinuxdevice.c.orig | 462
I don't see how this could affec
The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The autopkgtests have cleared.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/2086214
Title:
[SRU] libreoffice 24.2.7 for noble
Status in libreoffice package in Ubuntu:
Fix Rel
This was uploaded/sponsored, unsubscribing sponsors.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2084405
Title:
Not show 6GHz info at the "Supported Frequencies"
Stat
Hello Alexis, or anyone else affected,
Accepted gnome-calendar into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
calendar/46.1-0ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Denison, or anyone else affected,
Accepted adsys into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.14.3~24.04 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello David, or anyone else affected,
Accepted adsys into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.14.3~22.04 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
Hello David, or anyone else affected,
Accepted adsys into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.14.3~24.04 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
Hello Denison, or anyone else affected,
Accepted adsys into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.14.3~22.04 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Denison, or anyone else affected,
Accepted adsys into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.14.3~24.04 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Hello Denison, or anyone else affected,
Accepted adsys into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/adsys/0.14.3~22.04 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Thanks for the new upload, it addresses (b) and (c). Do you have an
update on (a)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2081968
Title:
[SRU] Add support for DCONF usb settings
(I'm starting to get timeouts when adding comments to this bug, so I'll
stop with the verification ones. Please assume that I performed the
verification as stated in comment #63 and I release a package here).
I verified audit 1:3.1.2-2.1build1.1 from noble proposed according to
comment #63.
--
Y
I verified apache2 2.4.58-1ubuntu8.5 from noble proposed according to
comment #63.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/2083480
Title:
SRU: no-change rebuild to pick up chang
I verified acl 2.3.2-1build1.1 from noble proposed according to comment
#63.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/2083480
Title:
SRU: no-change rebuild to pick up changed bui
There are many packages here. To facilitate the verification, this is the
recipe:
- autopkgtests green
- on ppc64el/s390x build logs, we want -fno-omit-frame-pointer to be ABSENT
- on all other 64bit architecture build logs, we want -fno-omit-frame-pointer
to be PRESENT
--
You received this bug
a) What happens if an older adsys receives a policy that sets these new
dconf usb settings? Will it be ignored, will it crash, or something
else? I think this should be part of the test plan, or if automated
tests check for this scenario, then just add a note stating so.
The two other comments I
Thanks for the updated testing!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2080602
Title:
[regression] GNOME 46/47 dropped support for Xilinx Mali graphics
Status in Mutter:
Fix
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that yo
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that yo
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that yo
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that yo
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that yo
The verification of the Stable Release Update for gnome-control-center
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that yo
mutter is a critical package in ubuntu, I would have expected the test
plan to also include a test on non-xilinx boards, specifically amd64,
and also on xorg.
Could someone please also go over the test plan on amd64 xorg/wayland
combinations? This would help reduce the risks highlighted in the bug
The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
This is pending the resolution of the malcontent MIR[1], as gnome-
control-center is currently showing a component mismatch migration block
on noble.
1.
https://bugs.launchpad.net/ubuntu/+source/malcontent/+bug/2077641/comments/9
--
You received this bug notification because you are a member of
Thanks for the detailed verification, Nathan, specially comments #3 and
#7. And I agree that if the failed test is not a regression from this
SRU, it shouldn't block it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center
autopkgtests green so far
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2083657
Title:
Remove oem-flavour.cfg for the OEM kernel retirement
Status in OEM Priority Proj
Hello Shih-Yuan, or anyone else affected,
Accepted ubuntu-drivers-common into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-
common/1:0.9.6.2~0.22.04.8 in a few hours, and then in the -proposed
repository.
Please help us by test
> more about 14)
>
> the oem metapackages will surely get updated too, but we shouldn't wait for
> that to happen to block this
> hotfix for a rather academic scenario
Agreed, let's just not forget about it should the oem package ever get
another update.
** Changed in: ubuntu-drivers-common (U
> However the content in /etc/default/grub.d/oem-flavour.cfg for the later OEM
> images from right now or OEM
> metapackages in OEM archives for jammy should only contain
> 'GRUB_FLAVOUR_ORDER=generic'.
I actually confirmed this, by installing oem-somerville-lapras-
meta=22.04~ubuntu1 on jammy
** Also affects: alsa-utils (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: alsa-utils (Ubuntu Plucky)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils
I'm learning with you here, Nathan. I'm asking around what's the
project's approach to creating new branches and such, because we need an
upstream branch for oracular now, so that ubuntu/master can become
plucky.
** Also affects: software-properties (Ubuntu Oracular)
Importance: Undecided
I checked the build logs of boost1.83 on ppc64el and s390x and compared
1.83.0-2.1ubuntu3 with 1.83.0-2.1ubuntu3.1:
1.83.0-2.1ubuntu3: -fno-omit-frame-pointer seen
1.83.0-2.1ubuntu3.1: that flag was not present
--
You received this bug notification because you are a member of Desktop
Packages,
9) dpkg -S can return multiple packages in one line, and also over
multiple lines, depending on what matches.
Example for one line with multiple packages:
$ dpkg -S /etc/grub.d
tuned, fwupd, grub-common, memtest86+: /etc/grub.d
And multiple lines:
$ dpkg -S grub.d
grub-common: /etc/grub.d/20_linu
sudo would definitely drop it, unless otherwise specified. mount with
nfs4 + krb5 keeps it, and I can see debugging information.
Just to be sure, start with setting that variable before running kinit,
just to confirm you would see the debug output.
--
You received this bug notification because y
It looks like libneon27 uses mit kerberos, so you can try exporting this
variable in the process's environment to see if you can get more logs:
KRB5_TRACE=/dev/stderr (or a file)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to neon27 in U
The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
@corradoventu, your apt-cache policy does not show noble-proposed, i.e.,
it doesn't show 90ubuntu2 which has the fix. What do you mean?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://b
The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
The noble verification tags were changed to done, but I don't see the
noble verification in a comment in this bug.
Changing noble tag back to verification-needed.
** Tags removed: verification-done-noble
** Tags added: verification-needed-noble
--
You received this bug notification because you
The verification of the Stable Release Update for gnome-shell-extension-
appindicator has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In th
No idea what the alsa-driver task is about here, looks like it was a
mistake. Removing.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Invalid
** No longer affects: alsa-driver (Ubuntu)
** Tags added: server-todo
--
You received this bug notification because you are a member o
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Title:
Add SoundWire devices to alsa-info reported in ACPI
Status in alsa-utils package in Ubuntu:
New
Status in alsa-utils
The patch looks fine from a feature freeze point of view, but we are
very close to final freeze, and I would feel better sponsoring this if
it had approval from the release team. I left a comment in the PR, and
also it needs fixing for the oracular version.
--
You received this bug notification b
** Merge proposal linked:
https://code.launchpad.net/~mschiu77/ubuntu/+source/alsa-utils/+git/alsa-utils/+merge/472762
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2073552
Titl
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
The verification of the Stable Release Update for xdg-desktop-portal has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
The verification of the Stable Release Update for adsys has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
Please follow the instructions from
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078246/comments/2
and only change the verification tags to done after successfully
completing the test plan with the package in proposed for the affected
ubuntu releases.
** Tags removed: verification-done-ja
Please follow the instructions from comments #2 and #3 above and only
change the verification tags to done after successfully completing the
test plan with the package in proposed for the affected ubuntu releases.
** Tags removed: verification-done-jammy verification-done-noble
** Tags added: ver
Please follow the instructions from comments #3 and #4 and only change
the verification tags to done after successfully completing the test
plan with the package in proposed for the affected ubuntu releases.
** Tags removed: verification-done-jammy verification-done-noble
** Tags added: verificat
I'm sorry, but I don't see in the comment above anything resembling the
agreed-upon test plan for this SRU:
"""
1. Create a policy with no dconf rule and make sure it applies to the user or
the machiune under test
2. Login on the machine
Without the patched version the following error is display
This didn't work for me:
sudo apt install opensc-pkcs11
sudo snap refresh --edge firefox
sudo snap connect firefox:pcscd
cp /usr/lib/*/opensc-pkcs11.so $HOME/snap/firefox/common
I need to use a proprietary module, called libaetpkss.so.3.5.4112, from
safesign. It works in chrome (deb), and
The current apparmor profile for digikam in oracular has these rules:
/usr/lib/x86_64-linux-gnu/qt5/libexec/QtWebEngineProcess cx ->
&digikam//QtWebEngineProcess,
/usr/lib/aarch64-linux-gnu/qt5/libexec/QtWebEngineProcess cx ->
&digikam//QtWebEngineProcess,
/usr/lib/arm-linux-gnueabihf/qt5/
This was uploaded.
** Changed in: pppconfig (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pppconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2078254
Title:
ftbfs: UTF-8 "\xAB" does
Finally, and pardon my ignorance, but could /dev/dri/card0 be used for
non-graphical things, like servers doing gpu calculations? And in that
case, removing it could break that workload?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubu
During boot, when does exactly "/bin/rm /dev/dri/card0" run? Would that
run in the initrd environment? I ask because of comment #37, which said
they lost the display during the luks password prompt. Although I
believe that's because of the workaround they were using then, which was
to disable simpl
This regression potential concerns me, thank you for raising it:
"""
Removing the simpledrm card is only safe when it's not being used. If somehow a
machine wasn't using the installed Nvidia driver then there could be a risk of
deleting the only working display.
"""
It may be obvious to you that
Allesandro, subscribing you to this bug because of your PR at
https://github.com/mquinson/po4a/pull/515
I'm willing to upload pppconfig with the debdiff you provided in the
debian bug, and also po4a with the patch in your github PR[2], to
unblock this FTBFS in Oracular. I can do follow-up uploads
Probably needs Fix (debdiff) proposed in Debb #1072606
** Bug watch added: Debian Bug tracker #1072606
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072606
** Also affects: pppconfig (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072606
Importance: Unknown
St
1 - 100 of 577 matches
Mail list logo
