This bug was fixed in the package initramfs-tools - 0.131ubuntu16
---
initramfs-tools (0.131ubuntu16) disco; urgency=medium
* scripts/functions: include a new option to skip enslaved network
devices. (LP: #1802591)
Include the new variable NETWORK_SKIP_ENSLAVED. When set
this will be fixed via the hwe backport
** Also affects: xorg-server-hwe-18.04 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server-hwe-18.04 (Ubuntu Disco)
Status: New => Invalid
** Changed in: xorg-server-hwe-18.04 (Ubuntu Cosmic)
Status: New =>
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10739
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-19591
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6488
--
You received this bug notification because you are a member of Ubuntu
Touch
bionic has 18.2.2 now
** Changed in: mesa (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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/1770271
Title:
VegaM
I'm assuming this is fixed in mesa 18.2.2 in cosmic, which also landed
bionic last night
if not, feel free to reopen
** Changed in: mesa (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The annotated tag, glibc-2.29 has been created
at e7c9e41bb2407b0150997b382b49a5f3bb579bf9 (tag)
The verification of the Stable Release Update for kmod has completed
successfully and the package has now been 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 encounter a
This bug was fixed in the package kmod - 24-1ubuntu3.2
---
kmod (24-1ubuntu3.2) bionic; urgency=medium
* Add i2c_i801 back to d/modprobe.d/blacklist.conf again due to regressions.
(LP: #1802689, #1802135)
-- Michael Hudson-Doyle Tue, 13 Nov 2018
10:54:37 +1300
** Changed
This bug was fixed in the package kmod - 24-1ubuntu3.2
---
kmod (24-1ubuntu3.2) bionic; urgency=medium
* Add i2c_i801 back to d/modprobe.d/blacklist.conf again due to regressions.
(LP: #1802689, #1802135)
-- Michael Hudson-Doyle Tue, 13 Nov 2018
10:54:37 +1300
** Changed
This bug was fixed in the package xserver-xorg-input-evdev-hwe-18.04 -
1:2.10.6-1~18.04.1
---
xserver-xorg-input-evdev-hwe-18.04 (1:2.10.6-1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:15 +0200
This bug was fixed in the package xserver-xorg-video-qxl-hwe-18.04 -
0.1.5-2build2~18.04.1
---
xserver-xorg-video-qxl-hwe-18.04 (0.1.5-2build2~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:27
This bug was fixed in the package llvm-toolchain-7 -
1:7-3~ubuntu0.18.04.1
---
llvm-toolchain-7 (1:7-3~ubuntu0.18.04.1) bionic; urgency=medium
* Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Thu, 22 Nov 2018 16:30:14 +0200
** Changed in:
This bug was fixed in the package libclc -
0.2.0+git20180917-2~ubuntu0.18.04.1
---
libclc (0.2.0+git20180917-2~ubuntu0.18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Thu, 11 Oct 2018 11:32:39 +0300
** Changed in:
This bug was fixed in the package xorg-hwe-18.04 -
1:7.7+19ubuntu8~18.04.1
---
xorg-hwe-18.04 (1:7.7+19ubuntu8~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:10 +0200
** Changed in:
This bug was fixed in the package xserver-xorg-video-vmware-hwe-18.04 -
1:13.3.0-2build1~18.04.1
---
xserver-xorg-video-vmware-hwe-18.04 (1:13.3.0-2build1~18.04.1) bionic;
urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018
This bug was fixed in the package xserver-xorg-video-dummy-hwe-18.04 -
1:0.3.8-1build3~18.04.1
---
xserver-xorg-video-dummy-hwe-18.04 (1:0.3.8-1build3~18.04.1) bionic;
urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Fri, 14 Dec 2018
This bug was fixed in the package xserver-xorg-video-fbdev-hwe-18.04 -
1:0.5.0-1ubuntu1~18.04.1
---
xserver-xorg-video-fbdev-hwe-18.04 (1:0.5.0-1ubuntu1~18.04.1) bionic;
urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018
This bug was fixed in the package xserver-xorg-video-nouveau-hwe-18.04 -
1:1.0.15-3~18.04.1
---
xserver-xorg-video-nouveau-hwe-18.04 (1:1.0.15-3~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:25
This bug was fixed in the package xserver-xorg-video-vesa-hwe-18.04 -
1:2.4.0-1~18.04.1
---
xserver-xorg-video-vesa-hwe-18.04 (1:2.4.0-1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:28 +0200
**
*** This bug is a duplicate of bug 1725628 ***
https://bugs.launchpad.net/bugs/1725628
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1725628, so is being marked as such.
This bug was fixed in the package xserver-xorg-video-ati-hwe-18.04 -
1:18.1.0-1~18.04.1
---
xserver-xorg-video-ati-hwe-18.04 (1:18.1.0-1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:23 +0200
**
This bug was fixed in the package xserver-xorg-video-amdgpu-hwe-18.04 -
18.1.0-1~18.04.1
---
xserver-xorg-video-amdgpu-hwe-18.04 (18.1.0-1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:21 +0200
This bug was fixed in the package xserver-xorg-input-libinput-hwe-18.04
- 0.28.1-1~18.04.1
---
xserver-xorg-input-libinput-hwe-18.04 (0.28.1-1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:18
This bug was fixed in the package xserver-xorg-input-synaptics-hwe-18.04
- 1.9.1-1ubuntu1~18.04.1
---
xserver-xorg-input-synaptics-hwe-18.04 (1.9.1-1ubuntu1~18.04.1) bionic;
urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1
---
mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
* intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924)
-- Timo Aaltonen Thu, 29
This bug was fixed in the package xserver-xorg-input-joystick-hwe-18.04
- 1:1.6.3-1build1~18.04.1
---
xserver-xorg-input-joystick-hwe-18.04 (1:1.6.3-1build1~18.04.1) bionic;
urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov
This bug was fixed in the package libdrm - 2.4.95-1~18.04.1
---
libdrm (2.4.95-1~18.04.1) bionic; urgency=medium
* Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597)
libdrm (2.4.95-1) unstable; urgency=medium
[ Timo Aaltonen ]
* rules, control: Switch to meson.
This bug was fixed in the package xf86-input-wacom-hwe-18.04 -
1:0.36.1-0ubuntu1~18.04.1
---
xf86-input-wacom-hwe-18.04 (1:0.36.1-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:14 +0200
This bug was fixed in the package xorg-server-hwe-18.04 -
2:1.20.1-3ubuntu2.1~18.04.1
---
xorg-server-hwe-18.04 (2:1.20.1-3ubuntu2.1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
-- Timo Aaltonen Tue, 27 Nov 2018 19:27:12 +0200
**
This bug was fixed in the package wayland - 1.16.0-1ubuntu1.1~18.04.1
---
wayland (1.16.0-1ubuntu1.1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
wayland (1.16.0-1ubuntu1.1) cosmic; urgency=medium
* control: Bump Breaks/Replaces again
The verification of the Stable Release Update for cairo has completed
successfully and the package has now been 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 encounter a
This bug was fixed in the package cairo - 1.15.10-2ubuntu0.1
---
cairo (1.15.10-2ubuntu0.1) bionic; urgency=medium
* debian/patches/git_adobe_cmykcolors.patch:
- "Revert "Correctly decode Adobe CMYK JPEGs in PDF export"
From further testing and investigation it appears
*** This bug is a duplicate of bug 1725628 ***
https://bugs.launchpad.net/bugs/1725628
Public bug reported:
new to Linux. can understand what the problem. please help me out.
thank you
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.5
ProcVersionSignature:
This bug was fixed in the package wayland - 1.16.0-1ubuntu1.1~18.04.1
---
wayland (1.16.0-1ubuntu1.1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
wayland (1.16.0-1ubuntu1.1) cosmic; urgency=medium
* control: Bump Breaks/Replaces again
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1
---
mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
* intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924)
-- Timo Aaltonen Thu, 29
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1
---
mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
* intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924)
-- Timo Aaltonen Thu, 29
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.1
---
mesa (18.2.2-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport for 18.04.2 HWE stack update. (LP: #1798597)
* intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924)
-- Timo Aaltonen Thu, 29
This bug was fixed in the package libdrm - 2.4.95-1~18.04.1
---
libdrm (2.4.95-1~18.04.1) bionic; urgency=medium
* Backport to bionic for 18.04.2 HWE stack update. (LP: #1798597)
libdrm (2.4.95-1) unstable; urgency=medium
[ Timo Aaltonen ]
* rules, control: Switch to meson.
The verification of the Stable Release Update for llvm-toolchain-7 has
completed successfully and the package has now been 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
Thanks. So the problem does seem to be with the Nvidia driver.
You might want to start by trying to uninstall "i386" packages like:
sudo dpkg -P libnvidia-gl-390:i386 libgl1-mesa-dri:i386
and if that doesn't clear it up then:
sudo apt --fix-broken install
--
You received this bug
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mesa (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
This can't be a good answer.
For external software providers, if they want to ship a program linked
against libreadline, and support it on multiple LTS versions of Ubuntu
(from 14.04 to 18.04), this makes it impossible for them.
There's no way they can force a link against libreadline5, unless
Possible dup with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813683
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1812095
Title:
console login loop after
frederick@graphMetrix-1:~$ sudo apt install --reinstall libwayland-server0
[sudo] password for frederick:
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have
Hmm, thanks. That list shows the problematic package libwayland-
server0:i386 is not installed (any more). But you do have the correct
one libwayland-server0:amd64.
Can you please run this command:
sudo apt install --reinstall libwayland-server0
and send us the output you see?
--
You
It looks like maybe the Nvidia driver has pulled in some i386
dependencies despite being amd64 itself.
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Incomplete
--
You
** Attachment added: "Thanks Daniel!"
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1814197/+attachment/5234949/+files/allpackages.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
Can you please run this command:
dpkg -l > allpackages.txt
and then send us the resulting file 'allpackages.txt'?
** Changed in: wayland (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1814197
Title:
package libwayland-server0 1.16.0-1ubuntu1.1 failed to
Public bug reported:
Trying to install nvidia-driver-390 on Dell XPS 15 6570
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libwayland-server0 1.16.0-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
Uname: Linux 4.18.0-14-generic x86_64
NonfreeKernelModules:
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1813663, so it is being marked as such. Please
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
This might be a different issue, but your kernel log is also getting
flooded with error messages about the touchpad(?)
https://launchpadlibrarian.net/409195699/CurrentDmesg.txt
** Summary changed:
- gnome-shell eats 100% cpu when seconds display is on and screen is locked
+ [nvidia] gnome-shell
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
If you have any gnome-shell extensions loaded, please uninstall (don't
just disable) them and tell us if that fixes the problem.
Please also run:
apport-collect 1814098
because this bug is missing some information since it was reported to
the wrong component.
** Package changed: xorg
** Changed in: libunistring (Debian)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunistring in Ubuntu.
https://bugs.launchpad.net/bugs/1813587
Title:
libunistring ftbfs on 18.04 LTS
** Changed in: gnome-control-center (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1745032
Title:
AC adapter
Ubuntu server here on a box that serves as NAS. I would have been toast
had I not already setup SSH. Confirmed issue with both:
linux-image-4.15.0-44-generic
linux-image-4.15.0-45-generic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Augustin,
What version of ubuntu have you tested?
Can you please paste here the output of the command
apt-cache policy linux-image-generic upower gnome-control-center gnome-shell
Are you also using a fixed kernel?
** Changed in: upower (Ubuntu Bionic)
Status: In Progress => Fix
Hi! Sorry to bother here but I wanted to attract your attention to the
following bug, in case you could consider dropping the type ahead patch
in future updates:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1592177
--
You received this bug notification because you are a member of
Hello Matthias, or anyone else affected,
Accepted pygobject into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pygobject/3.26.1-2ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Today, as often, I installed Ubuntu to a new Linux user, coming from Windows.
Everything is great and well designed, intuitive, and quick ... then ... this
lady began to feel confortable and wanted to quickly jump to the photo named
"IMG232.jpg"; so she started to type "IMG" on her folder,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
You have been subscribed to a public bug:
On Ubuntu 16.04.2: The statemachine of the "Open With" dialogue in is
defective. To open this dialogue reightclick a file, click "properties"
and select "Open With" tab.
The behaviour of the button "Set as default" is correct. After clicking
that button,
autopkgtest regression failure analysis/justifications for bionic:
systemd/s390x - failing since last november.
gvfs/s390x - failing since 2017.
snapd/s390x - flaky test that fails more than 1/2 the time since forever.
snapd/ppc64el - same as s390x
for cosmic:
gvfs/s390x - almost always
** Changed in: curl (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/311029
Title:
curl and pycurl is not compiled with
the issue is rather an hardware/corruption one than a package bug
** Changed in: poppler (Ubuntu)
Importance: Undecided => Low
** Changed in: poppler (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
For autopkgtest regression failure analysis/justification, please see
bug 1811471 (since this sru contains patches for this and that bug)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
Public bug reported:
Crash Report when resuming from sleep.
Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223
This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M,
driver 390.77
The crash log doesn't have much info in it IMO, but I uploaded here
** Information type changed from Private Security to Public
--
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/1813921
Title:
The ubuntu doesn't work when there is a second
I've tested the proposed updates and it seems to work with one minor
caveat: If I unplug and plug the AC adapter, it takes a little while for
the system to notice the change if it's near full charge (around 2
minutes). I think it's only a minor inconvenience.
I've also tested that it properly
Bionic verified too
ii systemd 237-3ubuntu10.12
amd64system and service manager
$ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
30
$ dig +noall +answer +noedns testing.irongiantdesign.com @127.0.0.53 | wc -l
30
**
Bionic verified
ii systemd 237-3ubuntu10.12 amd64 system and service manager
$ ping testing.irongiantdesign.com
PING testing.irongiantdesign.com (253.0.0.6) 56(84) bytes of data.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
Public bug reported:
problem with ubuntu 16.04 on an external disk, read only. Then i used
grub-customizer. now i try to do again the updates.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: poppler-utils 0.41.0-0ubuntu1.11
ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic
Cosmic Verified
ii systemd 239-7ubuntu10.7 amd64
system and service manager
ping testing.irongiantdesign.com
PING testing.irongiantdesign.com (253.0.0.15) 56(84) bytes of data.
** Tags removed: verification-needed-cosmic
** Tags added:
Cosmic Verified
ii systemd 239-7ubuntu10.7 amd64
system and service manager
#EDNS query
$ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
30
#No EDNS query falling back to TCP
$ dig +noall +answer +noedns
Could somebody please test the version of apport from cosmic-proposed?
I'd prefer somebody affected by the bug verified that the new version of
the package works for them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: jtreg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libcommons-lang3-java (Ubuntu)
Importance: Undecided
Status: New
** Also affects: testng (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gradle (Ubuntu)
Importance:
Public bug reported:
When I lock my machine on the latest ubuntu version 4.15.0-44-generic,
it turns my display completely black and unresponsive. This is only when
I have my dock (with external displays in). After it freezes however,
removing the dock has no effect. Booting back into
Sorry I realized this bug is misleading with the version listed, the bug
is for version: 4.15.0-44-generic. I am booted into 43 to fix the
problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
On Thu, Jan 31, 2019 at 01:48:06PM -, Mantas Kriaučiūnas wrote:
> Steve Langasek (vorlon), yes lots of Ubuntu users, including me have
> lots of containers (based on ubuntu-minimal - Ubuntu developers created
> "Minimal" LXC container image without rsyslog package by default), see
>
Note that 'rls-bb-notfixing' is a statement that the Foundations Team
does not intend to work on this SRU. It is not a statement that an SRU
would be rejected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in
i just tried out the daily build of
http://cdimage.ubuntu.com/daily-live/pending/disco-desktop-amd64.iso
from 2019-01-31 07:45 to pxe boot wihout using the "systemd.mask=tmp.mount"
workaround...
but i still goes straight to maintenance mode.
is the fix not included to the daily build yet?
--
mupdftoraster is part of cups-filters. If it is missing for you, run
sudo apt install --reinstall cups-filters
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1813432
Title:
more clues related to comment #9
if I run alsamixer I can toggle AUTO-MUTE from ENABLED to DISABLED and the
SOUND SETTINGS
Choose a device for sound output switches between headphones output and Analog
Stereo Output.
I did this 4-5 rapidly and now it seems that the SOUND SETTINGS Choose a
Same problem ubuntu 18.04
ran pavucontrol and saw "line-out (unplugged)"
plug in my headphones and "line-out unplugged" changed to: line-out
(plugged in)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in
Ubuntu Mate 18.04.1, same problem with linux-image-4.15.0-44-generic and
linux-image-4.15.0-45-generic
If I switch back to linux-image-4.15.0-43-generic I can succesfully login to
TTY.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The issue is with libarchive, installed libarchive-tools and trying to
extract the archive with bsdtar gives that
'# bsdtar -xf TestWavFile.7z
TestWavFile/Sweep_1Hz_44000Hz_-3dBFS_30s.wav: 7-Zip bad CRC: 0x5f2fe0a4 should
be 0x2a268c5a
TestWavFile/Sweep_1Hz_48000Hz_-3dBFS_30s.wav: 7-Zip bad CRC:
Reported upstream https://github.com/libarchive/libarchive/issues/1129
** Changed in: libarchive (Ubuntu)
Importance: Undecided => High
** Changed in: libarchive (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
You have been subscribed to a public bug:
Nautilus corrupts 7z archive files when extracting via 'Extract here' context
menu.
Extractions completes without errors, but the files are corrupted (mangled
bytes, wrong size).
This does happen only when extracting with 'Extract here' context menu
Could someone describe a test case using the backend which we could use
to test that the feature is working if we enable it to bionic (the 'curl
--version' output tells us that the backend is enabled but it would be
good to also check that it's actually correctly working)
--
You received this
Please try to print with
lp -d duplex -o fit-to-page -o pdftops-renderer=XXX
with XXX bring "hybrid", "gs", "pdftops", "pdftocairo", ...
Does this work?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Public bug reported:
on my laptop (xiaomi notebook pro), ubuntu 18.10 amd64, standart ubuntu desktop
(gnome-shell), no application running
just activate second display in gnome tweak, let it lock itself
the fan is going fast, simply moving the mouse and the fan slow down.
wrote a simple script
Hello Victor, 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.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, 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.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
After processing system update by:
apt-get clean && apt-get autoclean && apt-get autoremove && apt-get update &&
apt-get upgrade && apt-get dist-upgrade && reboot
ssh server stops starting at system boot.
It starts after doing:
mkdir /var/run/sshd
chmod 0755 /var/run/sshd
Hello Victor, or anyone else affected,
Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, or anyone else affected,
Accepted systemd into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
1 - 100 of 153 matches
Mail list logo