Hi,
crypto-policies is not supported on Ubuntu: it requires deep integration
with the packages and their configurations. This integration doesn't
exist and is unlikely to ever exist outside of redhat-based
distributions because of how tight it has to be. Past uses of crypto-
policies on Ubuntu
** Description changed:
Shoogle is not compatible with new python-googleapi releases. It is also
low-popcon ( https://qa.debian.org/popcon.php?package=shoogle ). There
has been one upstream version uploaded to debian in 2017 and then only
fixes by the packager.
The package seems
** Description changed:
Pydrive has been replaced by pydrive2 and it depends on python-
oauth2client which we'd like to remove as it is deprecated,
unmaintained, and is preventing some migrations.
Please remove pydrive so that we can continue with the removal.
Note that pydrive2
Public bug reported:
Pydrive has been replaced by pydrive2 and it depends on python-
oauth2client which we'd like to remove as it is deprecated,
unmaintained, and is preventing some migrations.
Please remove pydrive so that we can continue with the removal.
Note that pydrive2 also uses
Public bug reported:
Shoogle is not compatible with new python-googleapi releases. It is also
low-popcon ( https://qa.debian.org/popcon.php?package=shoogle ). There
has been one upstream version uploaded to debian in 2017 and then only
fixes by the packager.
The package seems moderately active
Shoogle hasn't been updated in several years and I wouldn't be surprised
there are compatibility issues with new python versions.
I was actually coming here to ask for its removal as it's not compatible
with new python-googleapi (which had not been updated in several years
either). The
Also, removal would only apply for Oracular (the development version),
not Noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062999
Title:
Errors during install
To manage notifications about
Noble will not use 3.2.1. Only oracular will.
Unfortunately, I don't have a very good answer about how to get this fix
in Noble as quickly as possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi and thanks for the patch.
Process-wise, the changes should land in oracular first and I don't
think I changed anything regarding that, even in my merge proposal for
3.2.1. I think we can integrate your patch in oracular in the version
that follows the 3.2.1 merge (I'd prefer not to respin my
** Changed in: openssl (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297025
Title:
Either the changelog.gz is missing or there is an erroneous link
Attaching 20 seconds of strace output for my case.
This actually lead me to look at /var/log/unattended-
upgrades/unattended-upgrades-shutdown.log and I Noticed the following:
2024-01-18 15:01:16,996 WARNING - SIGTERM or SIGHUP received, stopping
unattended-upgrades only if it is running
Also, note that out of my three stuck processes, it seems got unstuck.
Can't tell why however.
I also talked about running out of space but I don't think that was the
issue: it was the reason I looked at the machine but it wasn't related
to unattended-upgrades.
--
You received this bug
I have 10 backtraces with python3-dbg installed and therefore more
complete backtraces (but I wouldn't call them very readable). I'm going
to attach them here (.tar.xz archive which extracts in the current
directory).
** Attachment added: "unattended-upgrades-bt.tar.xz"
I'm seeing very different traces. Sorry. :)
I have processes which appear stuck and which have been using more than
11 weeks of CPU time over the past 132 days. No idea if it was in only
one run (I think I looked at CPU time less than 132 days ago, and even
less than 11 weeks ago, so it probably
The reason I want to remove the code is that it wasn't meant for
Desktop. It works on Desktop when using wayland but this is was
definitely not the intent back then. As I say in
https://code.launchpad.net/~adrien/ubuntu/+source/openssl/+git/openssl/+merge/466581
, I don't think the postinst can
** Description changed:
Unstable has openssl 3.2.1 which is need to fix some tests for nodejs
and some features for cryptsetup and is a good step to 3.3 for 24.10.
+
+ Merge request:
+
https://code.launchpad.net/~adrien/ubuntu/+source/openssl/+git/openssl/+merge/466581
--
You received
** Changed in: openssl (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058017
Title:
openssl is not LTO-safe
To manage notifications about this bug go to:
Public bug reported:
Unstable has openssl 3.2.1 which is need to fix some tests for nodejs
and some features for cryptsetup and is a good step to 3.3 for 24.10.
** Affects: openssl (Ubuntu)
Importance: High
Assignee: Adrien Nader (adrien)
Status: In Progress
--
You received
I did some archeology because I'm trying to get rid of the Ubuntu delta
compared to Debian.
I think the code change in 1.0.0e-2ubuntu3 is problematic. No blame: the
shell script was already hairy and difficult to understand and in order
to spot that, I had to identify a chunk of dead code, remove
Public bug reported:
Please remove eso-midas.
eso-midas FTBFS on all architectures due to a crash when running its
testuite (which it does during package building), this is the issue
described in https://bugs.launchpad.net/ubuntu/+source/eso-
midas/+bug/2058971 . It was first noticed with time_t
For reference, backtrace of the issue (I've inserted a call to gdb for
"prepa.exe" in the "inmidas" shell script. There are tons of fortify
warnings during build. Also, note that the Debian maintainer disabled
implicit function declarations, citing that the code is very old, and
indeed, it started
Removed the request to badtest this (it was denied anyway).
** Description changed:
Autopkgtests for request-tracker4 (and 5 it seems) fail on all arches
and due to the recent changes around test environments and the use of
all-proposed, it's difficult to identify which package change is
Build now fails on all arches with
# of pixels used = 843920 from 1,1 to 880,959 (in pixels)
FITS file newVIMOS.fits will have 4 extensions
*** buffer overflow detected ***: terminated
This is the same issue as back in March when this bug was created (I had seen
the issue and found
AFAIU there is no issue in the package at the moment so I'll close the
report. Thanks for investigating and trying the package reinstallation.
(Also, Alex, impressive intuition!)
** Changed in: openssl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
** Changed in: openssl (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297025
Title:
Either the changelog.gz is missing or there is an erroneous link in
I plan to work on this during the OO cycle. It's an issue inherited from
Debian AFAIU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1297025
Title:
Either the changelog.gz is missing or there is an
*** This bug is a duplicate of bug 1297025 ***
https://bugs.launchpad.net/bugs/1297025
** This bug has been marked a duplicate of bug 1297025
Either the changelog.gz is missing or there is an erroneous link in the
libssl1.0.0 package
--
You received this bug notification because you are
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062118
Title:
autopkgtests fail on s390x (segfault)
To manage notifications about this bug go to:
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062119
Title:
autopkgtests fail on ppc64el
To manage notifications about this bug go to:
** Changed in: gnutls28 (Ubuntu)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062018
Title:
[FFe] gnutls28: merge 3.8.5-2 and backport RSAES-PKCS1-v1_5 fix
To
** Changed in: openssl (Ubuntu)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062167
Title:
[FFe] openssl: post-3.0.13 changes from git
To manage notifications about
Note that there is a CVE fix in there too. It's low-severity because
it's only unbounded memory growth but it's quite easy to trigger and I
think that anyone who has a webserver with TLS 1.3 will want it patched.
Therefore there should be an upload of this at least.
--
You received this bug
Public bug reported:
I would like to have the most recent openssl version possible in Noble.
For that I am requesting to upload all the commits in the openssl-3.0
branch that follow 3.0.13 which is already in the archive.
I would like to include 3.0.14 afterwards if feasible. Having the most
Public bug reported:
Please allow the merge and upload of
https://code.launchpad.net/~adrien-n/ubuntu/+source/gnutls28/+git/gnutls28/+merge/464535
.
I made the commit message there quite complete so I'm basically copying
that here. In a few words, this is meant to include as many fixes
Matching MR is up:
https://code.launchpad.net/~adrien-n/ubuntu/+source/libtracefs/+git/libtracefs/+merge/464434
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051925
Title:
[MIR] promote libtracefs
** Changed in: libtracefs (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055309
Title:
No test suite run at built time nor as autopkgtest
To manage
I just got test results on amd64 and arm64.
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-adrien-n-noble-
libtracefs-mir/noble/amd64/libt/libtracefs/20240416_142558_e8175@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-adrien-n-noble-
libtracefs-mir/noble/arm64/libt
Still working on it. I'm only cleaning up the changes but I've been
having issues with the autopkgtest infrastructure since the beginning of
the week (if I trigger tests within "too" quickly, the testbed setup
fails).
Status is:
- amd64 and arm64 pass,
- ppc64el fails with 2, 3, or 4 failures,
-
I'm working on this and mostly finishing the changes. I think all
comments in Christian's messages are addressed.
Tests work. Valgrind tests are used and not too slow. Tests and build
must run in VMs and not containers. I have published the changes in a
PPA ( https://launchpad.net/~adrien-n
** Changed in: libtracefs (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien-n)
** Changed in: libtracefs (Ubuntu)
Status: New => In Progress
** Changed in: libtracefs (Ubuntu)
Milestone: None => ubuntu-24.04
--
You received this bug notification because you are
I carried this forward.
In a Noble LXD container, the test setup doesn't work.
In a Noble LXD VM, three tests fail: tracefs_iterate_snapshot_events, ,
and uprobes.
The first and second tests fail because they try to sched_setaffinity()
across 8 cores which the VM host has but the VM itself has
I'm going to target this to 24.10 as it's the first time it will be
possible to "solve" it. As far as I understand, there will probably be
performance loss with 3.3 compared to 1.1 but it's going to be a long
tail rather than a few big changes which have been included in 3.1, 3.2
and 3.3.
Btw,
** Also affects: openssl (Ubuntu Noble)
Importance: Undecided
Status: Confirmed
** Also affects: openssl (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu
Due to openssl's release schedule, 24.04 Noble Numbat will still use
3.0. It will be 3.0.13 unless a 3.0.14 is released very soon.
After Noble Numbat is released, I will work on openssl 3.3 for the
subsequent Ubuntu release. It is not yet released but will be soon so I
might start with beta/RC.
** Description changed:
+ NOTE: THIS IS AN ATTEMPT AT INCLUDING A BACKDOOR. THIS IS LEFT FOR
+ HISTORICAL PURPOSES ONLY AND MUST NOT BE DONE.
+
+
Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)
Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
was
I had forgotten about this bug. Thanks for bringing this up and let me
close this.
** Changed in: xz-utils (Ubuntu)
Status: New => Invalid
** Description changed:
+ NOTE: THE VERSION MENTIONED HERE HAS BEEN BACKDOORED.
+ I am keeping the text below unchanged due to its possible
I'll dive deeper into this. The timing collides with the t64 transition
so that makes me curious. Moreover, Debian reverted to 5.4.5 so the
situation where we're on 5.6.0 doesn't match Debian either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Autopkgtests for request-tracker4 (and 5 it seems) fail on all arches
and due to the recent changes around test environments and the use of
all-proposed, it's difficult to identify which package change is
responsible.
I actually see some passes on amd64 and arm64 but due to
This is currently blocking texlive-bin, fftw3, python3-defaults,
readline, ghostscript; all on armhf only. I think the previous build
(before a no-change rebuild against cfitsio) was passing on other
arches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
eso-midas fails to build from source on all architectures at the moment,
and the issue is reproducible locally.
The failure looks like:
# of pixels used = 843920 from 1,1 to 880,959 (in pixels)
FITS file newVIMOS.fits will have 4 extensions
*** buffer overflow
Public bug reported:
pyxplot fails to build from source on all architectures at the moment,
and the issue is reproducible locally.
The failure looks like:
python3 makeFigureEps.py ../bin/pyxplot
# Best fit parameters were:
# -
a1 = -1.2602846
a3 =
** Changed in: openssl (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056593
Title:
[FFE] FIPS compatibility patches
To manage notifications about
** Changed in: openssl (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058017
Title:
openssl is not LTO-safe
To manage notifications about this
** Description changed:
tl;dr: since it's too much work to make openssl LTO-safe, upstream
doesn't see it as a goal and doesn't test it, and there are probably no
performance gains to LTO for this package.
Openssl is an old project and the codebase wasn't written with aliasing
rules
** Description changed:
tl;dr: since it's too much work to make openssl LTO-safe, upstream
doesn't see it as a goal and doesn't test it, and there are probably no
performance gains to LTO for this package.
Openssl is an old project and the codebase wasn't written with aliasing
rules
to
create
+ the keys. This means that encoding tests run with the wrong library context,
+ which always uses the default provider.
- The link for the MR is at
+ These changes are now included in a larger MR with other changes in the
+ same package version:
+
https://code.launchpad.net
** Changed in: openssl (Ubuntu)
Milestone: None => ubuntu-24.04
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien-n)
** Changed in: openssl (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member
I did some additional tests too in a noble container.
With/without the env var to set the file location, including with the
file missing, with/without the env var to force FIPS mode, and using
values 0, 1, 42, -42, a.
By the way, note that access to these environment variables uses
** Summary changed:
- [FFe] openssl is not LTO-safe
+ openssl is not LTO-safe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058017
Title:
openssl is not LTO-safe
To manage notifications about
** Description changed:
tl;dr: since it's too much work to make openssl LTO-safe, upstream
doesn't see it as a goal and doesn't test it, and there are probably no
performance gains to LTO for this package.
Openssl is an old project and the codebase wasn't written with aliasing
rules
** Summary changed:
- openssl is not LTO-safe
+ [FFe] openssl is not LTO-safe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058017
Title:
[FFe] openssl is not LTO-safe
To manage notifications
Public bug reported:
tl;dr: since it's too much work to make openssl LTO-safe, upstream
doesn't see it as a goal and doesn't test it, and there are probably no
performance gains to LTO for this package.
Openssl is an old project and the codebase wasn't written with aliasing
rules in mind. There
Thanks a lot for looking at this. The issue seems fixed on my machine.
There are currently several changes being prepared for openssl and I
think I'd rather batch them considering the state of the CI queue but
this will definitely go into Noble. Thanks again.
--
You received this bug
Hey,
I think everything in the gnutls/ directory should be allowed: there can
be profiles with arbitrary names (or at least alnum I guess) which
define priority/configuration strings that can be used by gnutls
applications. I'm not aware of anything else that typically goes there
but I haven't
There are several reasons a program can skip loading the openssl
configuration unfortunately: env vars pointing to another file, apparmor
preventing loading, library initilization skipping it, ...
Is the program that ignores the openssl configuration file in the Ubuntu
archive? Or public?
--
Thanks for continued investigation.
A reproducer would be valuable as it would allow me to verify
independently the patch is effective, within the limits of the
understanding of the situation of course and that can be especially
time-consuming when not having access to the remote server. :/
A
Graham pointed out that the upload was actually to unstable and
therefore autosync'ed already!
I'm going to keep the bug open until it migrates due to the possibility
of some testsuite failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Xz-utils 5.6.0 was released last Friday. It features a much faster
decompression code on all platforms but on x86_64 in particular, it is
60% faster in my testing. It also aligns better current practices of
enabling multi-threading by default (always with a default memory
Thanks for the report. I am reluctant to backport this as I'm not sure
it makes a lot of sense system-wide. Curl upstream didn't seem happy
with enabling this work-around even in 2021. It seems the reason to
integrate this would be to be able to ignore this despite curl not
ignoring it nor
** Changed in: openssl (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: apache (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (857636).
Old bug...
I think the error comes from
base-passwd függőségek: libc6 (>= 2.8); ám:
libc6 rendszeren lévő verziója 2.8~20080505-0ubuntu9
which translates to
base-passwd függőségek: libc6 (>= 2.8); ám:
libc6 rendszeren lévő verziója 2.8~20080505-0ubuntu9
And then bash pre-depends on libc6 >=
I'm not seeing that behaviour on a 23.04 system and I expect it to be
the same since 22.04 at least. As such I'm going to mark this as Fix
Released.
** Changed in: openssl (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Changed in: openssl (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (857636).
https://bugs.launchpad.net/bugs/795355
Title:
Intermittent SSL connection faults when
Perhaps the title should be changed, as it also affects imap folders.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106737
Title:
Renaming folder to same name but different case not allowed
To
@osomon any news on the key request for Ubuntu ? I'm hitting usage
limits randomly with the generic "geoclue" key which makes redshift not
work sometimes. It's the same error as @heap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also filed (and fixed!) in Arch Linux:
https://bugs.archlinux.org/task/63073
A build switch was introduced in Vim 8.1.1529, so vim can be built with
--disable-canberra.
Commit
https://github.com/vim/vim/commit/21606676d9ebc6f159c56ee90733e5d5720ab3d7
Even though it is technically "no X", I
Note that this is not limited to metadata_csum_seed, other "recently"
added ext4 features cannot be used on the system partition (and maybe
the whole system disk, if you have other ext4 partitions there with such
features).
At least confirmed to not work with GRUB:
- metadata_csum_seed
-
The bug is still present in version 2.04-1ubuntu26.6 in focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844012
Title:
grub2 doesn't recognize ext4 with metadata_csum_seed enabled
To manage
** Bug watch added: Debian Bug tracker #866603
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866603
** Also affects: grub2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866603
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Bug watch added: git.jami.net/savoirfairelinux/ring-daemon/issues #264
https://git.jami.net/savoirfairelinux/ring-daemon/issues/264
** Also affects: mesa via
https://git.jami.net/savoirfairelinux/ring-daemon/issues/264
Importance: Unknown
Status: Unknown
** Also affects: ring
I will.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887107
Title:
Missing entry for timezone database when setting timezone via the text
search
To manage notifications about this bug go to:
After some quick investigation, I found that gnome-control-center pulls
its data directly from the zone.tab file, just like Paul Eggert warned
against doing in the comment I quoted above.
in tz.h (https://github.com/GNOME/gnome-control-
*** This bug is a duplicate of bug 1884307 ***
https://bugs.launchpad.net/bugs/1884307
I don't think this is correct to mark this as a duplicate of bug
#1884307. #1884307 is a bug at the installation of Ubuntu Mate, and for
all we know, this might pull from a different database than the bug I
I did a little bit more digging. Perhaps this comment would help explain
why there is a problem:
https://github.com/eggert/tz/commit/45dcf69b45087cff50282d4da64b86a7d705ddf3#commitcomment-4602830
In release v2013e "America/Montreal" was removed from the zone.tab file,
and incorrect programs may
I want to point out that the tzdata discussion (which I continued, but
should not have) seems to be irrelevant in the case of ubiquity, which
has the proper city of Montreal, but under a misspelled name.
My main point here is that the database contains a lot of misspellings.
--
You received
Upping this again.
There is a Mont-real entry, which is not an official name for the city.
This should be corrected to either Montréal or Montreal (preferably the
first).
> However, this turned out to not be true and Montreal timezone was removed
> from tzdata database.
This is not quite
Public bug reported:
I can't find Montreal in the timezone search box, even though it is
present in the /usr/share/zoneinfo database.
What I did:
Settings > Time & Date > Time Zone > Click in the search box and start typing
Mont...
What I expected:
Autocompletion.
What happened:
No completion
Hello,
I just solved it by using the info in this link : https://kicad-
pcb.org/download/ubuntu/
In the end it means upgrading to Kicad 5.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767652
Hello every one. I hqve the same issue with the following configuration
:
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename: bionic
Package: 4.0.7+dfsg1-1ubuntu2
It is on a jetson nano from NVIDIA.
How can we know if there are any update ?
I tried
For the record I recently noticed the 30 leaked processes started taking
all my CPU (all at the same time, maybe when an update was downloaded).
They were all running in infinite loop and I couldn't see the "sleep 60"
in their children any more in htop. I didn't investigate more as I had
to
I just noticed hundreds of chromium.launcher processes running on my
machine with `sleep 60` and found that it's because of this fix. Looks
like this background process is started but nerver stopped? nor does it
checks if it's already running. This is especially visible in my case
because I'm
ure -qDEB_HOST_MULTIARCH", which returns only
"x86_64-linux-gnu".
However, does 'ModulePath "xxx"' line really mater here ?
Best regards,
Adrien
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
I would like to point that this issue has not been solved as of 2020
(Version 3.30). Thanks for reading!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/158483
Title:
evince mishandles duplex
Hello,
4:19.04.3-0ubuntu2.1 fixed the bug for me too.
Thank you !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849455
Title:
[SRU] Externally-opened files no longer open in existing window
To
** Patch added: "cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lexicon/+bug/1825049/+attachment/525/+files/cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825049
I fixed the issue observed in Cosmic as observed with
http://paste.ubuntu.com/p/VfDDrbR9qF/
The update debdiff for Cosmic is attached after my post. The one for
Bionic can stay at it is, since the package is building properly in this
case.
About your question for the tests. I assume you are
** Attachment added: "Fix for Cosmic"
https://bugs.launchpad.net/ubuntu/+source/lexicon/+bug/1825049/+attachment/5259385/+files/fix-dnsimple-cosmic-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am a maintainer of the Lexicon project, and want to propose a SRU for
Lexicon 2.2.1 on Bionic and Lexicon 2.7.0 on Cosmic to fix that issue.
[Impact]
* Due to an undisclosed bug in Lexicon on the DNSimple provider, the creation
of new DNS records
on DNSimple is not possible anymore since
** Attachment added: "Fix for Bionic"
https://bugs.launchpad.net/ubuntu/+source/lexicon/+bug/1825049/+attachment/5259384/+files/fix-dnsimple-bionic-debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
I've the same issue like Benjamin Curtiss..
As Ubuntu 14.04 will be soon EOL, it's complicated that we can't upgrade
the OS from 14.04 to 16.04 right now..
I don't have postfix installed neither old init.d scripts on my server.
--
You received this bug notification because you are a
1 - 100 of 1849 matches
Mail list logo
