10 years after the initial bug report and it looks like I'm experiencing
the same bug.
In my case, I'm trying to print some pages that are 11" x 17" but it is
received at the printer as US Letter size. I did confirm that
/etc/papersize contains "letter", and changing that to "A4" also changes
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu9
---
accountsservice (0.6.55-0ubuntu9) eoan; urgency=medium
* debian/patches/0010-set-language.patch:
- Simplify logic when to set language and formats (LP: #1842349).
* debian/control:
- Change Maintainer
Using reboot did more of the same. At this point the Xenial version is
16.04.4 - we have a snapshot from 2019-05-28. unattended-upgrades was
at 0.90ubuntu0.9 but salt config management upgrades to
1.1ubuntu1.18.04.7~16.04.3 once the machine has salt installed. We
pretty much update a symlink
It went further but still failed to update - here it is via the dbus
shutdown command you supplied:
### unattended-upgrades.log:
2019-09-13 14:09:43,981 INFO Initial blacklisted packages:
2019-09-13 14:09:43,982 INFO Initial whitelisted packages:
2019-09-13 14:09:43,982 INFO Starting unattended
Disabling the Werror use workarounds the glib depreciation but hits a vapigen
error, ricotz shared that patch as a 'crude hack, just to have it built'
https://paste.debian.net/plain/1100570
Unsure if we want to go this way or if there is a better/nicer way to
fix it ... Robert you have more
I've been told that this is planned for the 3.7.5 release of python3.7 in
18.04. The release schedule for that is here:
https://www.python.org/dev/peps/pep-0537/#id4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
To clarify, that's the release schedule for python 3.7.5.
The pgo/lto change for arm64 is already in the 19.10 Ubuntu release of
python3 (3.7.4), so once the 3.7.5 version is released upstream, then
Debian will update to it, then Ubuntu 19.10 (or 20.04) will update to
it, then it will be
** Changed in: bluez (Ubuntu)
Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1620636
Title:
Fails to pair
** Changed in: dee (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dee in Ubuntu.
https://bugs.launchpad.net/bugs/1843730
Title:
dee ftbfs in eoan (all architectures)
** Changed in: bluez (Ubuntu)
Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1731467
Title:
Cannot pair BLE
Based on comment #12, and other comments from other duplicate cases,
I'll summarize here in a better (and consolidated way) how to reproduce
the issue, how to mitigate it using the dummy workaround, and how to fix
it (with the backports/merge requests). At the end I might provide a PPA
asking for
*** This bug is a duplicate of bug 1815101 ***
https://bugs.launchpad.net/bugs/1815101
The following 3 bugs:
https://bugs.launchpad.net/bugs/1815101
https://bugs.launchpad.net/bugs/1819074
https://bugs.launchpad.net/bugs/1810583
Have the same root cause: the fact that systemd-network messes
The following 3 bugs:
https://bugs.launchpad.net/bugs/1815101
https://bugs.launchpad.net/bugs/1819074
https://bugs.launchpad.net/bugs/1810583
Have the same root cause: the fact that systemd-network messes with
secondary IP addresses in NICs managed by systemd.
I'm marking all other cases as a
Some of the subcomponents of the pyperformance suite:
https://github.com/python/pyperformance/tree/master/pyperformance/benchmarks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
> This is worth about 30% performance.
can you share some performance tests used to measure this improvement?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/ubuntu/+source/libsecret/0.18.8-2
** Changed in: libsecret (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsecret in Ubuntu.
@vorlon Testing 243 goes better than expected, I may able to prepare it
for FFe instead of 242 so Eoan would be in sync with Fedora.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: libsecret (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsecret in Ubuntu.
https://bugs.launchpad.net/bugs/1843750
Title:
libsecret ftbfs in eoan
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
This issue occurs only on Xorg session (ubuntu 19.04).
No problem on Wayland session.
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
** Tags added: id-5d6fb9fb2ac215651795ec78
--
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/1843755
Title:
[FFe] Please accept systemd 242 to Eoan
Status in systemd
** Tags added: id-5d7aa5d50ab4905dcdc54c44
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1843812
Title:
apt info "please use the '-a' switch"
Status in apt package in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evolution-data-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Looks like this has been fixed in keepalived 2.x (detection of missing
vip) - https://github.com/acassen/keepalived/issues/836 - but the patch
is embedded with a whole load others that were merged at once so might
be hard to backport.
** Bug watch added: github.com/acassen/keepalived/issues #836
** Changed in: ubuntu-themes (Ubuntu)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/721786
Title:
(Non-overlay) scroll-bar
Public bug reported:
Ubuntu creates /etc/environment and directory /etc/environment.d.
pam_env.so only reads /etc/environment, but not recursively
/etc/environment.d/
You'll have to add any files created within /etc/environment.d/ as an
additional line to your pam_env.so pam configuration. This
Public bug reported:
GtkSpinButton consists of a (typically numeric) input field, followed by
a '-' and finally a '+' sign. The width of the '+' sign shrinks a little
bit when you open the right-click context menu of the input field. It
shouldn't, it should have a constant width.
Happens with
@vorlon: I agree that upgrading to v242 comes with risks, but the risk
fairly hard to assess exactly.
One measure can be the number of upstream stable backports and this is
as follows:
rbalint@yogi:~/projects/deb/systemd.git$ git describe
github-stable/v242-stable
v242-108-gf875dced33
** Package changed: linux-signed-hwe (Ubuntu) => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1843869
Title:
System crashes randomly each time with different
You have been subscribed to a public bug:
Description:Ubuntu 16.04.6 LTS
Release:16.04
Package version: 7.7+13ubuntu3.1
Fresh system install with Ubuntu 16.04 crashes the system after some
time. We are running high CPU intensive jobs, but CPU usage never
crosses 80%.
ProblemType:
Thanks for reporting this issue - this sounds like it might be suitable
as a StableReleaseUpdate - in particular the Regressions section
https://wiki.ubuntu.com/StableReleaseUpdates#Regressions sounds relevant
in this case. Could you please adapt this bug report following the
template in
Summary D vs E:
- no suffix
=> works equally in both releases
=> same opcodes in all .code segments
- suffix "w"
=> works equally in both releases
=> opcodes in .code32/.code64 differ from .code16 (660f..)
=> .code16 matches the non-suffix opcodes (0f..)
- suffix "l"
=> failures in
Result Disco:
### Testing suffix '' ###
.code16
push %gs
push %fs
pop %gs
pop %fs
.code32
push %gs
push %fs
pop %gs
pop %fs
.code64
push %gs
push %fs
pop %gs
pop %fs
push.out: file format elf64-x86-64
Disassembly of section .text:
<.text>:
0: 0f a8
Result Eoan:
### Testing suffix '' ###
.code16
push %gs
push %fs
pop %gs
pop %fs
.code32
push %gs
push %fs
pop %gs
pop %fs
.code64
push %gs
push %fs
pop %gs
pop %fs
push.out: file format elf64-x86-64
Disassembly of section .text:
<.text>:
0: 0f a8
Slightly extending on that test by Valentine I really think this is a change in
binutils behavior.
Attaching a script to test which I then will add logs from Disco (older 2.32)
and Eoan (2.32.51).
The script does:
- test pop/push with suffixes "" w l q
- test this in code 16/32/64 blocks
**
35 matches
Mail list logo
