** Summary changed:
- Smeared top panel and hint tips on Plank and browser icon
+ Corrupt/skewed gnome-shell panel rendering
** Tags added: radeon
** Summary changed:
- Corrupt/skewed gnome-shell panel rendering
+ [radeon] Corrupt/skewed gnome-shell panel rendering
** Package changed: xorg
Ok, I'll have a look at it; I only backported the Eoan fix to Bionic
--
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/1805183
Title:
systemd-resolved constantly restarts on
No file /etc/network/interfaces in ubuntu-19.10-beta-desktop-amd64.iso.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1844763
Title:
file /etc/network/interfaces
** Changed in: mir (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1843754
Title:
mir ftbfs in eoan (ppc64el)
Status in mir
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1845825
When reporting bugs in the future please use apport by using 'ubuntu-
** Changed in: fedora
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1048203
Title:
(CVE-2012-4412) glibc: strcoll() integer overflow
Sorry I lost track of this bug. The attachment in comment #7 shows:
HDMI-1 connected 1920x1080+1366+0 (0x8b) normal (normal left inverted
right x axis y axis) 160mm x 90mm
So the hardware is indeed reporting itself as ~7.2 inches. This is a
hardware fault (incorrect EDID data?) I have seen
** Changed in: mutter (Ubuntu)
Status: Expired => New
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Expired => Confirmed
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Oddly i have had the same issue and I today i was getting annoyed so i
went to wifi and switched from my 5G to 2.4 and it has been solid since.
I will update if anything changes. Can finally not have to run a
constant ping to keep it alive. on 5G when running a constant ping that
would prevent the
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Tags added: next-ddstreet systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I just tested this and it works fine. Maybe your problem is that you
have your bootscript path set to "/usr/bin/local/" (which doesn't exist
by default) when you meant "/usr/local/bin" (which does exist)?
In any case this seems invalid.
** Changed in: systemd (Ubuntu)
Status: New =>
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Tags added: next-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1843352
Title:
systemd package version 237-3ubuntu10.28
** Tags added: next-ddstreet
--
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/1839290
Title:
systemd doesn't restart a service after crashes
Status in systemd package in
** Changed in: systemd (Ubuntu Disco)
Status: New => Fix Released
--
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/1839290
Title:
systemd doesn't restart a service
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
--
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/1839290
Title:
systemd doesn't restart
> masking Apparmor test only on arm
er, the is_container check is enough (although just ignores the
problem), you don't need to also check for arm.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@stan thanks for testing on Disco.
if anyone can please test the package on Bionic, that would be
appreciated, this fix won't be released until someone affected by this
problem tests the proposed fix and verifies it fixes it.
--
You received this bug notification because you are a member of
** Also affects: systemd via
https://github.com/systemd/systemd/issues/12490
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Tags added: systemd
--
You received this bug notification because you
I marked this as invalid, but if you do believe there is a bug I missed
please feel free to reopen to clarify.
--
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/1836461
Title:
> DirectoryMode=0777
so, you might misunderstand what this parameter does; with the mount and
automount units, it sets the mode *only* for directories that need to be
created *up to* the actual mountpoint. So if you had:
[Mount]
What=/dev/disk/by-label/some-label
** Changed in: gnome-online-accounts (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1805426
Title:
Not able to log in
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
** Description changed:
[Impact]
Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
Attaching test-snapd-pulseaudio and test-snapd-audio-record snaps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1781428
Title:
please enable snap mediation support
** Description changed:
+ [Impact]
+ Ubuntu 16.10 added rudimentary snap support to disable audio recording if the
connecting process was a snap. By Ubuntu 18.04, something changed in the build
resulting in 'Enable Snappy support: no' with audio recording no longer being
mediated by pulseaudio
** Attachment added: "test-snapd-audio-record_1_amd64.snap"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+attachment/5292539/+files/test-snapd-audio-record_1_amd64.snap
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Description changed:
+
+ # Original summary: pulseaudio built with --enable-snappy but 'Enable
+ Snappy support: no'
+
+ # Original description
+
From https://launchpadlibrarian.net/377100864/buildlog_ubuntu-cosmic-
amd64.pulseaudio_1%3A12.0-1ubuntu1_BUILDING.txt.gz:
...
Public bug reported:
no
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-164-generic 4.4.0-164.192
Uname: Linux 4.8.0-040800-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Fri Sep 27 18:57:03 2019
ErrorMessage: run-parts:
The problem is with active calendar of my Google account. Everything
works very well with Nextcloud.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1843627
Any progress here? systemd-resolved has plus that it's integrated with
DNS options from systemd-networkd, but for end user it has many issues,
especially related to DNSSEC.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
1. Using Ubuntu 19.10
2. Shutdown system
3. System get stuck at the windows with this messages:
i2c_designware.o: controller timed out
i2c_hid: failed to change power settings.
It might not be related to the shutdown not happening, still that's the
only clue I have.
I
** Changed in: gdb (Ubuntu)
Assignee: (unassigned) => Manoj Iyer (manjo)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1845494
Title:
gdb 8.1-0ubuntu3.1 freezes before
34 matches
Mail list logo
