given back tests, the one remaining failing test
virtualbox/6.0.14-dfsg-1 (amd64)
doesn't look like it is Python specific.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
** Summary changed:
- Xorg freeze
+ 2500u random freeze during usage
** Summary changed:
- 2500u random freeze during usage
+ ryzen 2500u random freeze during usage
** Summary changed:
- ryzen 2500u random freeze during usage
+ ryzen 2500u random Xorg freeze
--
You received this bug
I have the same problem with audacious, on UbuntuStudio 18.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1808710
Title:
!xcb_xlib_threads_sequence_lost error with
I finally got around to reporting this upstream as
https://sourceware.org/bugzilla/show_bug.cgi?id=25215
** Bug watch added: Sourceware.org Bugzilla #25215
https://sourceware.org/bugzilla/show_bug.cgi?id=25215
--
You received this bug notification because you are a member of Ubuntu
Touch
I am sorry you have an issue with python on Ubuntu.
By policy, Ubuntu does not blindly upgrade toolchains to point releases in
an LTS release, but we go through extensive validation with rebuild and
autopkgtests across all of our supported 6 architectures, which is usually
in excess of upstream
All autopkgtests for the newly accepted glib2.0 (2.62.2-2~ubuntu19.10.1) for
eoan have finished running.
The following regressions have been reported in tests triggered by the package:
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (arm64)
sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386)
cairo/unknown
All autopkgtests for the newly accepted glib2.0 (2.62.2-2~ubuntu19.10.1) for
eoan have finished running.
The following regressions have been reported in tests triggered by the package:
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (arm64)
sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386)
cairo/unknown
All autopkgtests for the newly accepted glib2.0 (2.62.2-2~ubuntu19.10.1) for
eoan have finished running.
The following regressions have been reported in tests triggered by the package:
indicator-session/17.3.20+19.10.20190921-0ubuntu1 (arm64)
sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386)
cairo/unknown
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
Python 2 is very near EOL & thus Debian & Ubuntu have been working to
remove it as much as possible; ie. getting packages that use python
ported to use python3 instead, with only security fixes the exception.
All autopkgtests for the newly accepted glib2.0 (2.56.4-0ubuntu0.18.04.5) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
cairo/unknown (armhf)
firefox/70.0.1+build1-0ubuntu0.18.04.1
Public bug reported:
Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version
this version broke my scripts and get me segmentation fault each time I trying
to do something.
IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so
why I have .15 and in RC1
You have been subscribed to a public bug:
Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version
this version broke my scripts and get me segmentation fault each time I trying
to do something.
IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so
why I have
All autopkgtests for the newly accepted python3.7 (3.7.5-2~19.10) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
libreoffice/1:6.3.3-0ubuntu0.19.10.1 (s390x)
virtualbox/6.0.14-dfsg-1 (amd64)
ros-ros-comm/1.14.3+ds1-5build2 (amd64)
Public bug reported:
I was trying to install vscode and the command crashes.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libprocps6:amd64 2:3.3.12-3ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion:
Łukasz, thank you very much for accepting the package into bionic-
proposed. I confirm that the updated binary package libqt5printsupport5
fixes the problem. I also updated other libqt5* packages available in
bionic-proposed, and did not notice any obvious regressions.
However, I would like to
I thought we were going to some effort to reduce the number of systems
where resolveconf was going to be used, or even remove it from the
distro entirely.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Interesting. But the code is still incorrect, with my patch correcting it,
so I guess we'll see how it goes. I can either fix it locally or go elsewhere,
but I'm hoping it's simply fixed in the distribution.
Thanks for the pointer.
--
You received this bug notification because you are a member
I think this is a dup of bug 1745463, which might not be the answer you
were hoping for.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1853164
Title:
systemd:
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Focal)
Status: New => Triaged
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
All autopkgtests for the newly accepted qtbase-opensource-src
(5.9.5+dfsg-0ubuntu2.4) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
kcoreaddons/unknown (armhf)
killbots/unknown (armhf)
kfind/unknown (armhf)
For those with Sony headphones, and who are affected by this annoying
bug, the attached "headphones" Perl script is a partial workaround.
You'll need to edit it for the bluetooth address of your headphones. Run
it after switching your headphones on and they connect, and it sets
A2DP.
**
Can this please be re-opened? Daniel van Vugt marked it as "won't fix"
in comment #14 due to Ubuntu 17.10 being end of life, but numerous
people are still encountering the problem with more recent versions. I'm
encountering it on Ubuntu 19.10 and a new Sony WH-1000XM3.
If this bug can't be
Public bug reported:
The monitor U2414H is not detected by Ubuntu, the graphics card
displayed in settings is llvmpipe (LLVM 8.0, 256 bits). I believe it
should be "Intel Iris Plus Graphics", which is what shows up in Windows
Device Manager (my device is set up to dual boot).
ProblemType: Bug
This bug was fixed in the package glib2.0 - 2.63.1-2
---
glib2.0 (2.63.1-2) experimental; urgency=medium
* d/p/Revert-glocalfileinfo-Only-return-file-mode-not-type-as-U.patch:
Revert "glocalfileinfo: Only return file mode, not type, as UNIX_MODE
attribute" This reverts
Bug #1844853 was explicitly verified (comment #15). Didn't observe any
unexpected behavior due to the glib2.0 upgrade.
** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-done-eoan
--
You received this bug notification because you are a
Bug #1844853 was explicitly verified (comment #15). Didn't observe any
unexpected behavior due to the glib2.0 upgrade.
** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-done-eoan
--
You received this bug notification because you are a
I verified the test case using
- version 2.62.2-2~ubuntu19.10.1 of libglib2.0-{0,bin,data} from
eoan-proposed
- version 1.5.21-1~exp2ubuntu2.1 of the ibus packages from
ppa:ubuntu-security-proposed/ppa
Could successfully input Bangla characters in Kate using ibus-avro.
** Tags removed:
Hello Adam, or anyone else affected,
Accepted glib2.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.56.4-0ubuntu0.18.04.5 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
Volume increasing or decreasing doesn't work.
I can only toggle sound on (= 100%) and off (= 0%).
What I found out is that the Master channel seems to have no effect for
volume adjustments, but the PCM channel does. If the sound is muted, PCM
is set to 0 and therefore the
Public bug reported:
no sound !
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse: Error:
Normally, as this is not really a high-impact bug, I would be a bit
reluctant to accept it as an SRU. Since every SRU introduces risks,
especially if it's in a big core package like qtbase. But since I see
there's activity here (and testers available) + the patch is rather
straightforward, then oh
Hello Maciej, or anyone else affected,
Accepted qtbase-opensource-src into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/qtbase-opensource-src/5.9.5+dfsg-0ubuntu2.4 in a few hours, and then in
the -proposed repository.
Please help us by
Hello errors.ubuntu.com, or anyone else affected,
Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.2-2~ubuntu19.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Adam, or anyone else affected,
Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.2-2~ubuntu19.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Iain, or anyone else affected,
Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.2-2~ubuntu19.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
35 matches
Mail list logo
