Launchpad has imported 22 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1725499.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
Launchpad has imported 20 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=101229.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://he
Public bug reported:
Sound works okay but the internal mic doesn't work.
When I plug in headset, the mic on headset also doens't work.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux
Do you mean the screen doesn't light up, or the touchpad is
unresponsive?
Certainly the attached files suggest the second screen is not seen as
connected or powered on.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Statu
** Bug watch added: Red Hat Bugzilla #1725499
https://bugzilla.redhat.com/show_bug.cgi?id=1725499
** Also affects: xserver-xorg-video-ati (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1725499
Importance: Unknown
Status: Unknown
** Also affects: xserver-xorg-video-ati (U
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) 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)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulse
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) 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)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulse
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) 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)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulse
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) 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)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulse
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) 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)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulse
I understand the concern but would personally prefer keeping it as-is.
It's better to have a paper trail than to hide any history of what came
before.
I'm happy to manually set bug 1663528 to Won't Fix again for bionic.
--
You received this bug notification because you are a member of Ubuntu
Tou
Here I've decoded your EDID using 'xxd' and then 'edid-decode':
EDID version: 1.3
Manufacturer: SAM Model 509 Serial Number 1
Made in week 48 of 2008
Digital display
Maximum image size: 16 cm x 9 cm
Gamma: 2.20
RGB color display
First detailed timing is preferred timing
Display x,y Chromaticity:
To be absolutely sure you would need to:
1. Convert the display's EDID into binary from hex:
00004c2d09050100
30120103801009780aee91a3544c9926
0f5054bdef80714f8100814081809500
950fb3000101023a801871382d40582c
** Changed in: nouveau
Status: Confirmed => Unknown
** Bug watch added: gitlab.freedesktop.org/mesa/drm/issues #12
https://gitlab.freedesktop.org/mesa/drm/issues/12
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to li
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/mesa/drm/issue
** Changed in: python3-defaults (Debian)
Status: Unknown => Fix Released
--
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/bugs/1840510
Title:
Please enable PGO an
** Changed in: systemd
Status: Unknown => 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/1833193
Title:
systemd-networkd fails to apply static IPv4 whe
** Changed in: systemd
Status: Unknown => 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/1845909
Title:
IPv6 link local address is assigned even when
Hmm, I don't have any systems left with systemd-shim installed, so I
can't do a "real world" test of this. The test case is the description
seems reasonable, so if that passes, I would consider this bug fixed. :)
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Tou
> The lack of events is not the issue
I'm not saying it is. But you seem to have it under control; I was just
offering my opinion.
--
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
This bug was fixed in the package linux - 4.15.0-65.74
---
linux (4.15.0-65.74) bionic; urgency=medium
* bionic/linux: 4.15.0-65.74 -proposed tracker (LP: #1844403)
* arm64: large modules fail to load (LP: #1841109)
- arm64/kernel: kaslr: reduce module randomization range to
The lack of events is not the issue. We see all the events from the
kernel that we would expect to see during a resize, and we see the same
number (and type) of events on both the passing and the failing
instances.
The problem is that if udev processes the sda1 event first then, at
least some of
Hello Kees, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
a version of systemd with this change was accepted into bionic in error
and has now been withdrawn. a test case is needed here before it's
accepted properly.
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a
Hello Ryan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Also affects: systemd (Ubuntu Eoan)
Importance: High
Assignee: Dan Streetman (ddstreet)
Status: Triaged
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
--
Y
Hello Damiön, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello errors.ubuntu.com, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello bugproxy, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Bug watch added: Debian Bug tracker #934812
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812
** Also affects: python3-defaults (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812
Importance: Unknown
Status: Unknown
--
You received this bug notificatio
> You're proposing retriggering events and _then_ waiting
I'm proposing make sure that the uevent(s) for the specific partition
you're interested in have started processing before you start waiting,
which is what the retriggering does.
But it could be a kernel bug, sure.
--
You received this bu
Public bug reported:
Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and
screen - all in one)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
Nonf
best to close then
** Changed in: mesa (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503426
Title:
package libgl1-mesa-glx 10.
still the same with 18.04.3/19.04?
** Package changed: mesa (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bu
Setting up libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1) ...
update-alternatives: error: cannot stat file
'/usr/bin/java/jdk-9.0.4/bin/jar': Not a directory
dpkg: error processing package libegl1-mesa:amd64 (--configure):
subprocess installed post-installation script returned error exit status
closing as it's reported to be caused by overheating
** Changed in: mesa (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/881526
Title
Hello Ryan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hello Damiön, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Kees, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hello errors.ubuntu.com, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello bugproxy, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Frank, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
*** This bug is a duplicate of bug 1753796 ***
https://bugs.launchpad.net/bugs/1753796
** This bug has been marked a duplicate of bug 1753796
Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre-release)
--
You received this bug notification because you are a member of Ubuntu
I have the same problem with a lenovo V110 and ALC236.
I don't see an option to invert the channel or even mute permanently a
channel.
Kernel 5.2.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https
Public bug reported:
1. llvm 9 has been released, but mesa in the repo still uses llvm 8.
2. llvm 9 bitcode libs for OpenCL cause llvm-8-based mesa to fail because their
file format has changed
3. There was a bug in llvm-8-based mesa in disco that caused the OpenCL
compiler to hang on the kernel
this bug lacks a clear SRU test case for bionic (there is obviously no
4.4 kernel in 18.04).
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sy
Your system seems not to be quite updated. What if you do:
sudo apt update
sudo apt upgrade
** Changed in: ibus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https:
Public bug reported:
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
What expected:
Hold down the volume up or down button on a keyboard. The sound level gradually
increases to a maximum or decreases to a minimum.
What happened instead:
The sound level decreases or
I don't think we're looking for a way to wait for udev. For this bug to
present, udev has to have processed all of the available events (i.e.
there's nothing left to wait for), and have done so incorrectly
(probably as a result of its interaction with the Azure kernel, as this
doesn't reproduce on
> @ddstreet It seems to work as expected in Eoan!
excellent! now I need to figure out (again) which upstream commit fixes
this, as I know I found it before but apparently forgot to include the
info in this bug...
--
You received this bug notification because you are a member of Ubuntu
Touch see
I would also point out not only is the recursive interpretation of
--install-suggests incorrect, it is internally inconsistent.
apt-get --dry-run remove --purge -o APT::AutoRemove::Suggests-
Important=0 --auto-remove geda geda-utils geda-examples kicad kicad-doc-
en librecad oregano qelectrotech x
Can you provide networkd conf file(s) and steps to reproduce the issue
please?
--
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/1845909
Title:
IPv6 link local address is ass
The claim that it does what it says it does is false.
What it, in fact does, is consider suggested packages of OTHER packages
as a dependency for installing. This recursive behavior is not
advertised and not acceptable. For that behavior, one should have to
use an option such as --install-sugg
This was determined to be a bug in the WSL1 ELF loader and fix is
inbound from the WSL side.
https://github.com/microsoft/WSL/issues/4461#issuecomment-536023805
Please close on Ubuntu.
** Bug watch added: github.com/microsoft/WSL/issues #4461
https://github.com/microsoft/WSL/issues/4461
--
Y
** Bug watch added: github.com/systemd/systemd/issues #12886
https://github.com/systemd/systemd/issues/12886
** Also affects: systemd via
https://github.com/systemd/systemd/issues/12886
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
Public bug reported:
We sometimes have people come and go, leaving behind
old crontab files that, when they return, and are given
the same username, no longer have the correct uid.
This can cause cron to crash when it has the old crontab
file on its orphans list. Below's a lightly-edited
backtrace
I think that is the correct way to wait for udev to process a specific
device's changes.
--
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/1834875
Title:
cloud-init growpart
Could you please attach the file /etc/apport/crashdb.conf to your bug
report? Thanks in advance.
** Changed in: apport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1846006
Title:
package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
packa
Don't know how to remove the bug - but it fixed itself after a reboot
:shrug:
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bu
Public bug reported:
The PC keeps giving that there is a bug and tells to report it
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ibus-gtk3:amd64 1.5.11-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-62-generic x86_64
ApportVersion: 2.20
Hi apologies if this is the wrong thread. Just wanted to report I see
this issue on the Raspberry Pi build of Ubuntu MATE 16.04 running `mate-
control-center` 1.16.1-1~xenial4.0 and `systemd` 229-4ubuntu21.22.
I see resolution failures using `sudo` afterwards so even though it
still works, stdout
Public bug reported:
Release: Ubunto 18.04.3 LTS
Expected Behaviour:
Sound to come out of the speakers
Actual Behaviour:
No sound.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
Uname: Linux 4.15.0-64-gen
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-control-center (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
http
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
http
Hmm looks like https://github.com/systemd/systemd/issues/11458
** Bug watch added: github.com/systemd/systemd/issues #11458
https://github.com/systemd/systemd/issues/11458
** Also affects: systemd via
https://github.com/systemd/systemd/issues/11458
Importance: Unknown
Status: Unkn
** Changed in: systemd
Status: Unknown => 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/1832754
Title:
"shutdown[1]: Failed to wait for process: Proto
Thanks! that clarifies it - I think this is a bug upstream with
systemd.
> if I set "dhcp4: no" explicit when confiugring static addressing, it
behaves as expected
are you sure? that isn't what I would expect, it seems the problem is
networkd doesn't adjust the address lifetime when networkd is
Dan, are you asking for that to get more debugging information, or are
you suggesting that as a fix for this?
(I'm yet to be convinced that this isn't a regression in (the
kernel|src:systemd), so I don't think that we should have to run _any_
additional commands to address this.)
--
You received
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided => High
--
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/1773148
Title:
/lib/systemd/systemd-
journald:6:f
** Bug watch added: github.com/systemd/systemd/issues #8155
https://github.com/systemd/systemd/issues/8155
** Also affects: systemd via
https://github.com/systemd/systemd/issues/8155
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a membe
@Daniel @Sebastien the upload generally looks good, but I'm slightly worried
about the Launchpad-Bugs-Fixed: including the bug number of 1663528 - which has
been reverted as part of the upload. We don't really have good ways to tag a
bug as 'fix reverted' via the LP changelog parsing, and when w
Apparently the 237-3ubuntu10.10 upload got overwritten by a security upload,
too, thus the fix is still not present in systemd.
I'm preparing a new upload and intend to fix this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Released => In Progress
--
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/1776626
Title:
[18.10 FEAT] Support 4k sec
Pretty sure you need to actually try what I suggested in comment 40, but
of course use the specific dev/partition you're missing the udev symlink
for.
e.g. if you need the symlink for /dev/sda1 then instead of:
$ growpart /dev/sda 1 ; udevadm settle ; ls /dev/disk/by-uuid/$UUID
you should do
$
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373413
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373414
--
You received this bug notification because yo
The following
rsync -v -a -r -W -p -o -g -t --delete --stats
--exclude=".*"
--exclude="/snap*"
~
/media/$USER/USB-128GB-3/
>bkp_log
copies all contents of home folder each time it is run.
The expectation is that only changed files will be copied and replaced
on the target.
This is reproduc
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373411
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373411
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/
Hello peterzay,
IF you are facing something like:
https://unix.stackexchange.com/questions/85993/why-rsync-attempts-to-
copy-file-that-is-already-up-to-date
Then I would recommend reading the 1st answer to that question, which
explains why and when rsync would try to re-sync everything again.
I
** Changed in: pulseaudio (Ubuntu Xenial)
Status: In Progress => Triaged
** Changed in: pulseaudio (Ubuntu Bionic)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubu
** Description changed:
[Impact]
We would like to include a cloud_id/$name parameter to the user-agent
string that is sent to https://motd.ubuntu.com. This will allow the
server part of motd.ubuntu.com to serve cloud-specific content if one is
available.
+ [Test Case]
+ a) confirm
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Balint Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
- I'm preemptively filing this bug in case this isn't uploaded before the
- feature freeze.
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but
Oh, I didn't notice that apport sent this to alsa-driver. Reassigning
since I believe this to be a kernel regression.
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Clock disappeared from panel. Everything else is OK
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1283610
Title:
indicator-datetime-service crashed with SIGABR
Public bug reported:
On eoan, after an initial startup / login, if an application crashes and
I click "report", I get a prompt saying the crash is reported and to
check the web page open in the browser to see if I have any additional
information.. except it never opens a page. The dialog just disa
@ddstreet True, but it ran fine when running the test locally with standard lxd
virt on amd64, so I did not want to skip it on all containers.
I'll be happy to merge it away when the Salsa PR lands in Debian and gets
merged to Ubuntu.
--
You received this bug notification because you are a memb
How can I check if the hardware is really sending faulty data or if it
is just incorrectly parsed?
** Also affects: xrandr (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to q
Emm, I think the issue I referenced above is an incorrect one.
https://github.com/systemd/systemd/issues/9890
&
https://github.com/systemd/systemd/pull/11423
I think `debian/patches/networkd-honour-LinkLocalAddressing.patch` might
be an incorrect backport of this upstream bug.
** Bug watch added
Thanks. I think the relevant update was:
Start-Date: 2019-09-21 17:34:40
Commandline: apt install paprefs
Requested-By: david (1000)
Install: gnome-icon-theme:amd64 (3.12.0-1ubuntu3, automatic), paprefs:amd64
(0.9.10-2), pulseaudio-module-zeroconf:amd64 (1:8.0-0ubuntu3.10, automatic),
libgladem
Hi Daniel - see attached
Cheers
*Your reason and your passion are the rudder and the sails of your
seafaring soul.*
*Kahlil Gibran*
On Mon, Sep 30, 2019 at 6:36 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> That's strange -- version 1:8.0-0ubuntu3.10 was actually released last
Yes the kernel log (CurrentDmesg.txt) suggests a disk is faulty so you
should replace that before doing anything else...
Then if the screen flickering persists please attach a video of the
problem here so we can better understand what you mean.
** Package changed: xorg (Ubuntu) => ubuntu
--
You
Repro instructions:
- (Enable systemd-networkd debug logging)
- Start a server with its interface configured with DHCP
- In the netplan config, configure the interface wtih static addressing, using
the exact same address as it already has gotten from DHCP
- Either wait for the initial DHCP lease t
The kernel log suggests the nouveau kernel driver is having trouble:
[ 5703.539644] nouveau :00:0d.0: bus: MMIO write of 052a0001 FAULT at 00b000
[ 5704.875835] nouveau :00:0d.0: bus: MMIO write of 05270001 FAULT at 00b010
[ 5705.738769] nouveau :00:0d.0: bus: MMIO write of 05270001 FA
That's strange -- version 1:8.0-0ubuntu3.10 was actually released last
year on 2018-05-03. So if you're experiencing a new problem then maybe
pulseaudio is not the cause.
Please attach the file:
/var/log/apt/history.log
so we can find out...
** Changed in: pulseaudio (Ubuntu)
Status:
This bug was fixed in the package initramfs-tools - 0.122ubuntu8.15
---
initramfs-tools (0.122ubuntu8.15) xenial; urgency=medium
* hook-functions: include ehci-platform from HWE kernel.
(LP: #1842284)
-- Ike Panhc Wed, 04 Sep 2019 15:24:58 +0800
** Changed in: initramfs-too
The verification of the Stable Release Update for initramfs-tools 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
This bug was fixed in the package openssl - 1.1.1b-1ubuntu2.4
---
openssl (1.1.1b-1ubuntu2.4) disco; urgency=medium
* Import libraries/restart-without-asking as used in postinst, to
prevent failure to configure the package without debconf database.
LP: #1832919
-- Dimitri
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/comments/6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1772512
Title:
Unable to install i386 an
1 - 100 of 129 matches
Mail list logo
