** Bug watch added: Red Hat Bugzilla #1786306
https://bugzilla.redhat.com/show_bug.cgi?id=1786306
** Also affects: chromium (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1786306
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Work-around
pip install --user setuptools
then set $PATH to include ~/.local/bin
** Also affects: python-setuptools (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896652
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
@david.here sorry there is nothing I can do to help you.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780994
Title:
Waylan
I got a "duplicate bug" warning when I tried to run:
ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1001.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780994
Title:
Wayland Crashes Immediately Afte
Oh, I'll do it for him. After all we have been through.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780994
Title:
Wayland Crashes Immediately After gdm or XDMCP Login
To manage notifications ab
18.04 GDM login screen now displays an exclamation mark as a caps lock
indicator.
The older GDM used a different icon but this is sufficient for me.
It is my opinion that this issue has been resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
gdm version 3.28.0-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734887
Title:
No caps lock indicator on login screen
To manage notifications about this bug go to:
https://bugs.launchpad.
I took lm-sensors out of the bug title because lm-sensors 1:3.4.0-4
works fine with an updated it87 driver.
$ sensors
it8686-isa-0a40
Adapter: ISA adapter
CPU Vcore:+0.77 V (min = +0.00 V, max = +3.06 V)
+3.3V:+3.39 V (min = +0.00 V, max = +5.05 V)
+12V:+12.38 V (min =
** Description changed:
+ Summary: Thermal sensors are not accessible due to being unsupported by
+ the it87.ko module in linux-image-extra which does not include the
+ it8686 model line among others..
+
+ Expected behavior:
+
+ $ journalctl | grep it87:
+ Apr 20 21:36:00 lakshmi kernel: it87: i
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740736
Title:
Driver it87 and lm_sensors are too old and don't support newer
chipsets (such as Z370).
T
I'm using the default that comes with 18.04
uname -svr
Linux 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018
The same IOMMU=pt
$ grep iommu /etc/default/grub
GRUB_CMDLINE_LINUX="iommu=pt"
Fixed 4.14.* on 17.10 (I didn't try the default 4.13.* kernel)
Last tested on 4.14.33-041433-g
Please see comment #4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758305
Title:
Panic during SyS_reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/li
I haven't seen this issue in a long time.
I'm still using the same graphics card but in another motherboard.
Gigabyte AX370-Gaming 5 BIOS F22, AMD Ryzen 5 2400G, Linux
4.15.0-13-generic, Ubuntu 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I no longer am using the motherboard, CPU and RAM that this happened on.
I am using 4.15.0-13-generic on 18.04 now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730374
Title:
NULL pointer derefer
The system in question here used to panic in numerous ways until I started
using iommu=pt
Now it appears to be stable.
The BIOS setting for IOMMU is "auto".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
--- smart-notifier-0.28.orig/doc/smart-notifier.1
+++ smart-notifier-0.28/doc/smart-notifier.1
@@ -28,7 +28,7 @@ This manual page documents briefly the
.\" TeX users may be more comfortable with the \fB\fP and
.\" \fI\fP escape sequences to invode bold face and italics,
.\
dmidecode output from BIOS F22
https://gist.github.com/mettacrawler/ed333ea4349f71c481892fe53eea6039
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759828
Title:
BUG: Bad page map in process SaveSc
@malachid can you please try booting with:
iommu=pt
and see if that works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759947
Title:
BUG: unable to handle kernel paging request at 2
I'm on the new BIOS. It requires iommu=pt
Even with older kernels like 4.14.31 this computer requires iommu=pt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759828
Title:
BUG: Bad page map in pro
** Description changed:
Note that this is from an AMD Ryzen 5 2600G
Also the BIOS firmware is a beta, but the previous version, which is the
last so-called stable version is in much worse shape. For instance it
misidentifies the RAM as having CAS 19 when it's really CAS 16. The beta
Public bug reported:
Note that this is from an AMD Ryzen 5 2600G
Also the BIOS firmware is a beta, but the previous version, which is the
last so-called stable version is in much worse shape. For instance it
misidentifies the RAM as having CAS 19 when it's really CAS 16. The beta
BIOS firmware d
Public bug reported:
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: device_shutdown+0xbb/0x200
PGD 0 P4D 0
Oops: 0002 [#1] SMP NOPTI
See the screenshot for more.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSigna
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730374
Title:
NULL pointer dereference during writeback
To manage notifications about this bug go to:
https://bugs.launchpad
** Description changed:
+ This could be part of CVE-2016-3070
+
Happened during dd of 40GB LV:
$ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo
I also used SIGUSR1 on the dd to monitor it occasionally. There was
other activity at the time as well.
It appears that an attempt was
It happened again.
$ uname -r
4.14.9-041409-generic
Dec 29 14:32:14 lakshmi kernel: BUG: unable to handle kernel NULL pointer
dereference at (null)
Dec 29 14:32:14 lakshmi kernel: IP: locked_inode_to_wb_and_lock_list+0x20/0x110
Dec 29 14:32:14 lakshmi kernel: PGD 0 P4D 0
Dec 29 14:32:
Re: But the inner PV is only for the guest to use - no?
The intent is that the inner PV is only for the guest to use. What has
happened for years and years is that unless you mask using
/etc/lvm/lvm.conf the host will vgscan the inner PV and vgchange it too.
Until 17.10 (possibly 17.04, I skipped
It's likely that this was either fixed upstream or the root cause is
from a patch that was put on the 4.13 kernels that the 4.14 kernels
don't have.
Nov 05 22:15:30 lakshmi kernel: Linux version 4.13.0-16-generic
(buildd@lcy01-02) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP
Wed Oc
** Description changed:
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
$ apt-cache policy udev
udev:
Installed: 234-2ubuntu12.1
Candidate: 234-2ubuntu12.1
Version table:
*** 234-2ubuntu12.1 500
500 http://us.archive.ubuntu.com/ubuntu artful-u
*** This bug is a duplicate of bug 1734887 ***
https://bugs.launchpad.net/bugs/1734887
** This bug has been marked a duplicate of bug 1734887
No caps lock indicator on login screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
Expected results: Pressing the Caps Lock key should cause an indicator
to appear on the login screen.
Actual results: Pressing the Caps Lock key does not cause the login
screen to change in any way.
Reproducing:
1. Install Ubuntu 17.10 Desktop ISO and log in, press Caps Loc
*** This bug is a duplicate of bug 1714301 ***
https://bugs.launchpad.net/bugs/1714301
If you are looking for newer bug reports with this issue try
LP: #1717152
LP: #1728181
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
If you are looking for newer bug reports with this issue try
LP: #1717152
LP: #1728181
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714301
Title:
systemd-networkd hangs my boot (wireless)
To mana
This bug may be a duplicate of LP #1717152
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728181
Title:
systemd-networkd-wait-online waits when devices are unmanaged
To manage notifications about t
I'm not using cloud-init. My network devices are not managed because I disabled
NetworkManager.service shortly after installing 17.10 on bare metal Nov 5, 2017
9:44 AM EDT. I think there were too many fires then and I didn't want to try
to convince NetworkManager to use a bridge. I just lived
This morning I found out that if I boot
linux-image-4.13.0-17-generic
I get a hang at
Nov 23 07:12:47 lakshmi NetworkManager[1795]: [1511439167.0455] manager:
rfkill: WWAN hardware radio set enabled
Nov 23 07:14:30 lakshmi systemd-networkd-wait-online[1454]: Event loop failed:
Connection timed o
This morning I found out that if I boot
linux-image-4.13.0-17-generic
I get a hang at
Nov 23 07:12:47 lakshmi NetworkManager[1795]: [1511439167.0455]
manager: rfkill: WWAN hardware radio set enabled
Nov 23 07:14:30 lakshmi systemd-networkd-wait-online[1454]: Event loop failed:
Connection timed
Installation of 4.14.2
https://gist.github.com/mettacrawler/7d60c8f51a19b506ea1cb575c2ed4032
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730374
Title:
NULL pointer dereference during writeback
T
The bug is still there in artful in this package version:
$ apt search lxcfs | grep lxcfs/
lxcfs/artful-updates,now 2.0.8-0ubuntu1~17.10.2 amd64 [installed]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
The bug is still in artful
$ apt search lxcfs | grep lxcfs/
lxcfs/artful-updates,now 2.0.8-0ubuntu1~17.10.2 amd64 [installed]
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14553
I was unable to reproduce this on 4.13 until Nov 23 when it happened
again.
This time the logs show that I was handling PDF files via Nautilus which
doesn't imply as much disk I/O as the previous 40G dd did.
A quote from:
https://patchwork.kernel.org/patch/9614361/
{{ I am able to reproduce the p
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy udev
udev:
Installed: 234-2ubuntu12.1
Candidate: 234-2ubuntu12.1
Version table:
*** 234-2ubuntu12.1 500
500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64
Pa
Eventually I'll have time to test the upstream kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730374
Title:
NULL pointer dereference during writeback
To manage notifications about this bug
I'd love to have time to work on this kernel bug but I have fires all
over the place with 17.10.
I have a dual-boot setup between 16.04 and 17.10. The 17.10 took over
nine minutes to boot originally. After finding out about
Debian_bug_867368 I got it to boot in over three minutes. It still gets
This also happens if the VM host is storing guests in LVM not only "real
disks". Example:
...
...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729626
Title:
AppArmor denies access to /sys/block/
Public bug reported:
Happened during dd of 40GB LV:
$ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo
I also used SIGUSR1 on the dd to monitor it occasionally. There was
other activity at the time as well.
It appears that an attempt was made to fix this in 4.10
https://patchwork.kernel.org/patch
Still happens with unity-webapps-service 2.5.0~+16.04.2016020
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1193647
Title:
ubuntu-webapps-update-index fails to parse multiline fields
To manage noti
Xorg crashed after 13 days 20 hours and 28 minutes of running. The root
cause is unknown to me; I can only trace it back to gnome-session-binary
running out of file descriptors and crashing on a SIGSEGV which cascades
until a nouveau driver message about receiving a signal occurs.
I don't know if
I'm almost on day 12 of using HWE kernel and Xorg now. No lock-ups.
$ lsb_release -d
Description:Ubuntu 16.04.3 LTS
$ uname -a
Linux lakshmi 4.10.0-37-generic #41~16.04.1-Ubuntu SMP Fri Oct 6 22:42:59 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
$ uptime
07:16:04 up 11 days, 21:29, 10 users, l
No lock-ups after 6 days of using HWE kernel and Xorg.
This includes the weekend when the activity level is high enough to
usually cause one or more lockups in the same day.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
According to the changelog for the hwe deb
apt changelog xserver-xorg-video-nouveau-hwe-16.04
New upstream release
Thu, 09 Mar 2017 11:46:23 +0200
The changelog for the default deb that comes with 16.04
apt changelog xserver-xorg-video-nouveau
... last update on ...
Thu, 03 Mar 2016 15:44:44 +020
Might not have changed a thing
Pre-hwe debs:
Oct 17 08:45:28 lakshmi kernel: [drm] Initialized nouveau 1.3.1 20120801
for :01:00.0 on minor 0
With hwe debs:
Oct 17 09:47:37 lakshmi kernel: [5.538623] [drm] Initialized nouveau
1.3.1 20120801 for :01:00.0 on minor 0
--
You received
To see if this has been fixed in newer versions I am now running after
having installed:
sudo apt-get install xserver-xorg-video-nouveau-hwe-16.04 xserver-xorg-
core-hwe-16.04 xserver-xorg-hwe-16.04 linux-generic-hwe-16.04 xserver-
xorg-input-libinput-hwe-16.04
Try this only at your own risk.
Ne
** Description changed:
- This is an intermittent issue.
+ This is an intermittent issue. Rumored to be fixed in Ubuntu 17.04
+ according to comments in bug 1645375
Oct 15 11:36:26 lakshmi kernel: nouveau :01:00.0: timeout at /build
/linux-
Pcn0xK/linux-4.4.0/drivers/gpu/drm/nouveau/
*** This bug is a duplicate of bug 1723758 ***
https://bugs.launchpad.net/bugs/1723758
** This bug has been marked a duplicate of bug 1723758
Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up (hangs)
--
You received this bug notification because you are a member of Ubunt
*** This bug is a duplicate of bug 1723758 ***
https://bugs.launchpad.net/bugs/1723758
** This bug has been marked a duplicate of bug 1723758
Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up (hangs)
--
You received this bug notification because you are a member of Ubunt
** Description changed:
This is an intermittent issue.
+
+ Oct 15 11:36:26 lakshmi kernel: nouveau :01:00.0: timeout at /build
+ /linux-
+
Pcn0xK/linux-4.4.0/drivers/gpu/drm/nouveau/nvkm/engine/fifo/chang84.c:111/g84_fifo_chan_engine_fini()!
+
ProblemType: Bug
DistroRelease: Ubuntu
*** This bug is a duplicate of bug 1723758 ***
https://bugs.launchpad.net/bugs/1723758
You should use ubuntu-bug to submit bug reports.
Please see
https://help.ubuntu.com/community/ReportingBugs#Reporting_non-crash_hardware_and_desktop_application_bugs
Thanks and Regards,
MC
** This bug has
** Bug watch added: Red Hat Bugzilla #1330355
https://bugzilla.redhat.com/show_bug.cgi?id=1330355
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=1330355
Importance: Unknown
Status: Unknown
** Bug watch added: freedesktop.org Bugzilla #93828
https://bugs
Public bug reported:
This is an intermittent issue.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
.tmp.unity_support_test.0:
.tmp.unity_support_test.
** Bug watch added: Red Hat Bugzilla #1330355
https://bugzilla.redhat.com/show_bug.cgi?id=1330355
** Changed in: xserver-xorg-video-nouveau (Fedora)
Remote watch: Red Hat Bugzilla #1350262 => Red Hat Bugzilla #1330355
** Package changed: xserver-xorg-video-nouveau (Fedora) => fedora
--
You
Oct 15 11:36:26 lakshmi kernel: nouveau :01:00.0: timeout at /build
/linux-
Pcn0xK/linux-4.4.0/drivers/gpu/drm/nouveau/nvkm/engine/fifo/chang84.c:111/g84_fifo_chan_engine_fini()!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Bug watch added: freedesktop.org Bugzilla #93828
https://bugs.freedesktop.org/show_bug.cgi?id=93828
** Also affects: nouveau via
https://bugs.freedesktop.org/show_bug.cgi?id=93828
Importance: Unknown
Status: Unknown
** Bug watch added: Red Hat Bugzilla #1350262
https://bugzi
This might be the same issue that was fixed in Bug #1654600
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/434835
Title:
unattended-upgrades hangs system on shutdown
To manage notifications about th
@pfalcon atop is run at midnight from cron, see the atop manual page for
details. This is why you get "spontaneous" crash dialogs about atop.
@raymii If you are on 16.04 you can fetch the update from Debian Sid.
Add two files:
$ cat /etc/apt/preferences.d/debian-atop
Explanation: This file is
I'm not going to hit the duplicate button but...
https://bugs.launchpad.net/ubuntu/+source/oneconf/+bug/1486450
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538668
Title:
No such file or directory
For Android cameras you must also unlock the screen before it will talk
to your computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400470
Title:
cannot download photos using shotwell via usb
This Debian wiki page https://wiki.debian.org/DebianInstaller/SataRaid
suggests that in /etc/default/grub
the line:
GRUB_DISABLE_LINUX_UUID=true
must be uncommented.
Has anyone tried that? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I was going to write a patch for "HEAD" but then I found out that
iriverter doesn't appear ever in Debian and I can't see it in Vivid
while doing causal checking.
The only use I had is that it quickly and easily got me a working
mencoder line like this:
mencoder infile.mp4 -o outfile.h300.avi -ov
Public bug reported:
- Install iriverter:
[14:31] [root@trololo ~]# aptitude install iriverter
The following NEW packages will be installed:
iriverter libswt-gtk-3-java{a} libswt-gtk-3-jni{a}
0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
(...)
Setting up libswt-gtk-3-jn
*** This bug is a duplicate of bug 1397617 ***
https://bugs.launchpad.net/bugs/1397617
** This bug has been marked a duplicate of bug 1397617
iriverter lacks package dependency libswt-cairo-gtk-3-jni
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just out of curiosity has anyone tried:
sudo apt-get install gnome-packagekit
gpk-update-viewer
as a work-around? When I get some time to play in a VM I'll do it
myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
@psusi - once you've installed on fake RAID and upgraded successfully a
few time, the effort to convert to Linux software RAID is significant.
I've side-stepped that for now by rebuilding grub 1.99-21ubuntu3.15
(from 12.04) on Ubuntu 14.04 and putting package holds on the resulting
debs. Maybe som
@Jan Henke - the titlebar resize menu item is not grayed out on my 14.04
system. I'm not using Xubuntu. I have the "ubuntu-desktop" meta package
installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Re comment #6
The reason this titlebar menu resize contraption exists is that it is
part of UI accessibility. You can use the keyboard to control the
resize procedure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Re comment #6
With a mouse or tracball etc. (not a touchscreen):
1. Right click on the title bar of the window to be resized.
2. A menu will pop up. Choose "resize" from it.
3. The pointer will jump (warp) to the center of the window.
4. Do not click yet. Move the pointer past the edge of the w
Some sample error messages:
$ sudo grub-install /dev/mapper/pdc_bdhbchffcb1
Installing for i386-pc platform.
grub-install: error: disk
`lvmid/PxjGc2-Eb10-CsLt-RPxa-s344-09ma-l4R47W/DpicMh-yvL3-zZVu-BmwD-5Cc9-PwRc-tAWnwT'
not found.
$ sudo grub-install /dev/mapper/vg0-lv0
Installing for i386-p
*** This bug is a duplicate of bug 1236951 ***
https://bugs.launchpad.net/bugs/1236951
** This bug has been marked a duplicate of bug 1236951
package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess
installed post-installation script returned error exit status 1
--
You
*** This bug is a duplicate of bug 1236951 ***
https://bugs.launchpad.net/bugs/1236951
** This bug has been marked a duplicate of bug 1236951
package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess
installed post-installation script returned error exit status 1
--
You
78 matches
Mail list logo
