** Summary changed:
- Crash on install, with ZFS enabled (running on Virtualbox 6.0.14)
+ ZFS - Failed to mount /target
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification
I checked on Ubuntu 18.04 upgraded to 21/11/2019, that means virtualbox
5.2.32. It works perfect now. Problem solved! Virtual machines in
NatNetwork mode accesing internet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I checked on Ubuntu 18.04 upgraded to 21/11/2019, that means virtualbox
5.2.32. It works perfect now. Problem solved! Virtual machines with
NatNetwork mode accesing internet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: jacksum (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701028
Title:
Jacksum -h option missing source help_en.txt
To manage notifications
This was broken for me in the latest bionic 18.04-3, with or without
backports.
A work around seems to be to switch konqueror's Default Web Browser
Engine to the KHTML renderer in Settings::Configure Konqueror::General.
That makes the bug this one: KDE Bugtracking System – Bug 377084.
A partial
Please ignore the #36, the boot.scr in the http://cdimage.ubuntu.com
/ubuntu-server/eoan/daily-preinstalled/20191122/ has some problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848790
Title
A background worker process is crashed. dmesg line:
[110854.430928] traps: icinga2[17383] general protection ip:7f403c6f4edc
sp:7f40365cfe40 error:0 in libpthread-2.23.so[7f403c6e8000+18000]
icinga use newer libboost, i checked the libbost source, just some backport
changes lines.
We disable the
Thanks for info, very helpful!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900901
Title:
Steam overlay does not work due to GCC-4.6 issues
To manage notifications about this bug go to:
Could you tell us the detailed steps to install the desktop on the rpi4
board? Since we only released the server version, there is no desktop in
the server version.
And the detailed steps to reproduce this issue.
Then we will setup the same environment to debug this issue.
--
You received
Can you please try this kernel:
https://people.canonical.com/~khfeng/lp1849721-4/
Which included this commit:
commit 0c8432236dea20a95f68fa17989ea3f8af0186a5
Author: Aaron Ma
Date: Thu Nov 14 03:12:47 2019 +0800
HID: i2c-hid: fix no irq after reset on raydium 3118
On some ThinkPad
** Summary changed:
- Wifi randomly drops out
+ Wifi drops out at large bandwidth usage
** Description changed:
System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov
12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
- Problem: Wifi randomly drops out. For example, I
Public bug reported:
Opened Discover for downloads and one package downloaded and installed
but two others were not installed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: discover (not installed)
ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
Uname: Linux 4.15.0-70-generic
USB issue with 4GB maxmem seems to be fixed.
2560x1440 resolution issue not fixed.
Cannot run glxinfo to get video driver information (immediate crash)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[ 20.005106] ieee80211 phy0: brcmf_cfg80211_scan: Connecting:
status (3)
[ 22.175638] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI
infoframe
[ 35.824432] [drm:vc4_crtc_mode_set_nofb
Have instability with the 1013 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852035
Title:
Cannot use full resolution (2560x1440) of Dell U2715H
To manage notifications about this bug go
[ 22.661761] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI
infoframe
[ 39.686565] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI
infoframe
[ 70.888208] v3d fec0.v3d: MMU error from client L2T (0) at 0x4f41000,
pte invalid
[ 70.898755] kernel BUG at
Is secure boot enabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836440
Title:
RTL8723BS wifi not working
To manage notifications about this bug go to:
Public bug reported:
Notice the bug and fix mentioned in
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1772921
is, somehow 're-broken' in eoan. Possibly because of:
https://pagure.io/freeipa/c/78652a52f083bac5238f9e0a6520e0e448dadabe
The result is none of the directional glyphs
This is currently an issue in 19.10's systemd (version 242). By default,
unless services are configured to set LimitMEMLOCK, they will have 64k
as their memlock limit (though oddly, systemd bumped its own memlock
limit higher than previous versions have used). The only processes not
affected are
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837580
Title:
Paul F, if you think you have found a bug, then you need to make a new,
separate bug report under a new bug number, because your hardware is
different and you are not discussing a regression in kernel 4.13.0-43,
which is what this particular bug was about.
Here are some instructions for reporting
Still a problem on Eoan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075923
Title:
nautilus hangs copying large directories from a samba share
To manage notifications about this bug go to:
** Attachment added: "tearing-1.mp4"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307224/+files/tearing-1.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853094
** Attachment added: "tearing-2.mp4"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5307225/+files/tearing-2.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853094
@Akshay,
Does it 100% happen? Did you login through keyboard/ssh connection/usb-
serial console? Last could you please try the Image of #36.
thx.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Unleavened,
This is the image with the new kernel. http://cdimage.ubuntu.com/ubuntu-
server/eoan/daily-preinstalled/20191122/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848790
Title:
USB
Verification:
ubuntu@bionic:~$ sudo kexec -p /boot/vmlinuz-`uname -r`
--initrd=/boot/initrd.img-`uname -r` --reuse-cmdline
ubuntu@bionic:~$ echo 1 | sudo tee /proc/sys/kernel/sysrq
1
ubuntu@bionic:~$ echo c | sudo tee /proc/sysrq-trigger
c
[ 164.962517] sysrq: SysRq : Trigger a crash
[
bionic verification:
GNU GRUB version 2.02
Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions. ESC at any time exits.
** Description changed:
https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506
[Availability]
There is an on-going MIR for a package whose ndctl is a dependency:
pmdk (LP: #1790856)
* Package exists since bionic (-updates) in universe:
61.2-0ubuntu1~18.04.1 |
Afternotes: I only noticed the bug shortly after upgrading from Ubuntu
16.04 to Ubuntu 18.04
Seems like 16.04 didn't yet use systemd-resolved, but dnsmasq, which
only returned ipv4 addresses.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello Torel and Juliet,
If possible, could you please test the PPA above with either Bionic
and/or Disco and make sure the packages fix the issue ? I'm preparing
bdctl to be in "main" pocket for 20.04:
https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506
and having this case fix would
Public bug reported:
I've got an ethernet-device that only has a configured ipv4 address, and
some auto-generated link-local (aka "scope link") ipv6 address.
Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
DNS-server listening on 127.0.0.53) for this host's hostname gets
** Changed in: ndctl (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: ndctl (Ubuntu Disco)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ndctl/+git/ndctl/+merge/375930
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't
Not sure if that applies here, but "fe80::a8bb:ccff:fedd:eeff" is not a
valid ipv6 address on this machine.
instead try "fe80::a8bb:ccff:fedd:eeff%ens3"
The problem might be with "systemd-resolved" which happily serves
"fe80::a8bb:ccff:fedd:eeff" as an ipv6 address of this machine.
I stumbled
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/ndctl/+git/ndctl/+merge/375929
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't
A PPA containing the fixes (Disco and Bionic) will be available here:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1811785
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853657
Title:
librsvg 2.44.15 FTBFS in focal
To manage notifications about this bug go to:
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to
host (256 byte) labels
This issue is fixed by:
commit 9c6aae5
Author: Dan Williams
Date: Tue Jan 15 01:51:45 2019
ndctl/init-labels: Fix label slot accounting per UEFI 2.7
Quoting from Linux kernel commit
It fixes an issue introduced by :
Patch: bdaec95463ca
In version v58
And the fix (9c6aae5) was introduced in v64.
$ rmadison ndctl
ndctl | 61.2-0ubuntu1~18.04.1 | bionic-updates/universe | source, amd64
ndctl | 63-1.3| disco/universe | source, amd64,
arm64, armhf,
When using dax:
(k)rafaeldtinoco@emulated:~$ sudo mount -o dax /dev/pmem0p1 /mnt
(k)rafaeldtinoco@emulated:~$ mount | grep -i mnt
/dev/pmem0p1 on /mnt type ext4 (rw,relatime,dax,stripe=512)
(k)rafaeldtinoco@emulated:~$ dd if=/dev/zero of=./teste bs=1M count=1024
1024+0 records in
1024+0 records
** Changed in: stress-ng (Ubuntu Bionic)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807732
Title:
lots of "fail" and "error" messages
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853666
Title:
Battery will not charge on Toshiba
I saw this as well after rebooting.
I was able to manually mount my home folder using the command this
generates:
mount | grep rpool/USERDATA/ | head -1 | \
awk -F '_' '{print $2}' | awk -v user=$USER \
'{print "sudo zfs mount rpool/USERDATA/" user "_"$1}'
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zsys (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853667
Title:
Public bug reported:
Description:Ubuntu 19.10
Release:19.10
The contents of my Home folder have been replaced/disappeared.
ls now brings back:
Desktop, Documents, Downloads, Music, Pictures, Public, Templates,
Videos.
The original contents of my home folder still existed at some
Public bug reported:
Since I have switched from Windows 10 to Ubuntu, my battery will no
longer charge. The battery shows 0% charge and says Estimating. Ubuntu
appears to detect removing the battery as the battery indicator
disappears and reappears upon replacing the battery. Unplugging the AC
Public bug reported:
The driver installed just fine and wifi is working but bluetooth does
not.
I will gladly provide further debugging information.
Ubuntu 19.10
** Affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
> Pardon my ignorance about the Launchpad bug metadata states,
> but: is there going to be an update for Ubuntu Disco fixing
> this issue?
Given that Eoan has now been released, and there is not an isolated bug
fix for Disco, it is unlikely that an update will be pushed to Disco for
this issue.
** Changed in: software-properties (Ubuntu)
Status: New => Fix Released
** Changed in: software-properties (Ubuntu)
Milestone: ubuntu-17.08 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: software-properties (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687122
Title:
/usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
This is a good XML template for a VM emulating nvdimms.
** Attachment added: "emulated_vm.xml"
https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506/+attachment/5307204/+files/emulated_vm.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can confirm the problem still exists with Ubuntu 19.10, all up-to-date.
Where can I dig to debug?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612916
Title:
[Tohsiba Portege Z20T-C]
(k)rafaeldtinoco@emulated:~$ sudo ndctl enable-dimm all
enabled 2 nmems
(k)rafaeldtinoco@emulated:~$ sudo ndctl list -D
[
{
"dev":"nmem1",
"id":"8680-57341200",
"handle":2,
"phys_id":0,
"flag_failed_arm":true
},
{
"dev":"nmem0",
"id":"8680-56341200",
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: linux (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux (Ubuntu Cosmic)
Status: New => Invalid
** Changed in: linux (Ubuntu Disco)
Status: New => Invalid
** Changed in: lvm2 (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: lvm2
Public bug reported:
This happened on a Raspberry Pi 4 on which I had installed the arm64
image from http://cdimage.ubuntu.com/ubuntu-server/eoan/daily-
preinstalled/20191122/. Its worth noting I also encountered a crash with
cloud-init, bug 1853660, so maybe everything wasn't set up properly
The problem manifested in 19.04 before the upgrade. I had hoped 19.10
would fix. The issue is intermittent. Logging out or rebooting fixes
for a time. Launching favorited apps from the Icon Task List always
works, so problem has been easy to ignore. This is the first Ubuntu bug
I have ever
** Tags removed: need-duplicate-check
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853660
Title:
cloud-init crashed with
Follow-up patch that updates the vendored crates in the source tarball
accordingly.
** Patch added: "cssparser-update-vendored-crates.patch"
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+attachment/5307180/+files/cssparser-update-vendored-crates.patch
--
You received this
Patch for the upstream commit
(https://gitlab.gnome.org/GNOME/librsvg/commit/de26c4d8).
** Patch added: "upstream-de26c4d8.patch"
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+attachment/5307179/+files/upstream-de26c4d8.patch
--
You received this bug notification because
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Build log with the above two patches applied, unit tests fail.
** Attachment added:
"buildlog_ubuntu-focal-amd64.librsvg_2.44.15-1ubuntu1_ppa8_BUILDING.txt.gz"
Public bug reported:
focal currently has rustc 1.38 (1.38.0+dfsg0.2+llvm-0ubuntu1), and
librsvg 2.44.15 fails to build from source with this version. It built
fine with rustc 1.37 (although there was a unit test failure on ppc64el,
which prevented it from leaving focal-proposed, see
Public bug reported:
I found this crash file on a Raspberry Pi 4 on which I had installed the
arm64 image from http://cdimage.ubuntu.com/ubuntu-server/eoan/daily-
preinstalled/20191122/.
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: cloud-init 19.2-36-g059d049c-0ubuntu3
** Package changed: compiz-plugins-main (Ubuntu) => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Private bug reported:
ORDER PERCOCET ONLINE:
https://redditpharmacy.com/product-category/buy-percocet-online/
I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm
switching workspaces, it occasionally locks up (becoming more frequent). Most
of the time, I'm going
** Also affects: lttng-modules (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: lttng-modules (Ubuntu Bionic)
Status: New => In Progress
** Changed in: lttng-modules (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: lttng-modules (Ubuntu Bionic)
Also builds fine with 5.0.0-30-generic.
$ sudo dkms build r8168/8.045.08 -k 5.0.0-30-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area.
make -j1 KERNELRELEASE=5.0.0-30-generic -C /lib/modules/5.0.0-30-generic/build
Finally, builds fine with 4.15.0-68-generic.
$ sudo dkms build r8168/8.045.08 -k 4.15.0-68-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area..
make -j1 KERNELRELEASE=4.15.0-68-generic -C
/lib/modules/4.15.0-68-generic/build
** Changed in: lttng-modules (Ubuntu)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: lttng-modules (Ubuntu)
Status: New => In Progress
** Description changed:
+ [Impact]
+ The DKMS package won't work with new kernels on bionic.
+
+ [Test case]
+ Install and load
I've sponsored an upload from Paolo to address this issue. I've asked
him to fill in the SRU template and I'm hoping that he's able to do that
before the SRU team gets to the upload.
** Changed in: ndiswrapper (Ubuntu Bionic)
Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Paolo Pisati
bionic version works fine with linux-hwe-edge-5.3.0-23-generic
Unpacking r8168-dkms (8.045.08-2ubuntu1) over (8.045.08-2) ...
Setting up r8168-dkms (8.045.08-2ubuntu1) ...
Loading new r8168-8.045.08 DKMS files...
Building for 5.3.0-21-generic 5.3.0-23-generic
Module build for kernel
I've sponsored an upload from Paolo to address this issue in Bionic.
I've asked him to fill in the SRU template and I'm hoping that he's able
to do that before the SRU team gets to the upload.
** Also affects: xtables-addons (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed
Sorry Thadeu but Paolo had already passed me a debdiff to sponsor for
this bug.
** Changed in: ndiswrapper (Ubuntu Bionic)
Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Paolo Pisati
(p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've sponsored an upload from Paolo to address this issue. I've asked
him to fill in the SRU template and I'm hoping that he's able to do that
before the SRU team gets to the upload.
** Also affects: dahdi-linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in:
Unpacking r8168-dkms (8.045.08-2ubuntu1) over (8.045.08-2) ...
Setting up r8168-dkms (8.045.08-2ubuntu1) ...
Loading new r8168-8.045.08 DKMS files...
Building for 5.3.0-21-generic 5.3.0-23-generic
Module build for kernel 5.3.0-21-generic was skipped since the
kernel headers for this kernel does
Has it been broken since you upgraded 28 days ago or just recently?
If the latter what do you install or remove at or around the time of the
breakage?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
disco verification:
GNU GRUB version 2.02
Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists possible
device or file completions.
Hello,
If you understand my frustration, you should understand how
frustrating and uninformative "Segmentation fault error" is.
This is my issue. there is segmentation fault when trying to ingest
records to the database, that is why trace shows error in
ingestIncremental function.
The tool is
Yes, with several 4.x kernels and even with kernel 5.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687910
Title:
[Lenovo W520] Linux Freezing Issue At Boot
To manage notifications about this
I too found this bug with Ubuntu 18.04 LTS on Nvidia Jetson TX2 system.
Running ffplay :
ffplay /dev/video0
produces:
dbus[9467]: arguments to dbus_message_new_method_call() were incorrect,
assertion "path != NULL" failed in file ../../../dbus/dbus-message.c line 1362.
This is normally a bug
I found that the problem only happens when the "virtio" device model is used in
both pfSense internal and UBUNTU interfaces.
I tested all combinations and get the following results:
pfSense
default confinada UBUNTU result
virtio virtio virtioERR
virtio virtio rtl8139 OK
Question link > https://askubuntu.com/questions/1190609/eye-strain-and-
nausea-when-running-18-04-1-on-intel-i915-graphics
I have eye strain and headaches using Ubuntu which I believe is caused
by temporal dithering being enabled. I have posted on AskUbuntu and it
was suggested I update this bug
@nio-wiklund, @mwhudson : Thanks for your replies.
@nio-wiklund : Your solution would probably do the trick, but has the
inconvenient of indiscriminately replacing a string with another in the
whole image, hence possibly in places where it's not desired.
I think I will rather do one of those two
FYI: I got message from sbeattie that security will take a look at the
backports for these qemu fixes.
For libvirt we can check again then if the types got updated, and if no
one did I can send something there as well.
--
You received this bug notification because you are a member of Ubuntu
Hey, I was able to find that the bug was fixed in v5.4-rc1. I haven't been able
to find the commit that fixes the issue though. Trying to run:
$ make -j`nproc` deb-pkg
Gives me the error: make: *** No rule to make target 'nproc'. Stop.
--
You received this bug notification because you are a
I made some more tests and found that ICMP packets are NAT'ed OK
independent of the device model used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853489
Title:
Ignoring the default NAT when
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
Hui Wang - I tried your proposed solution. Post rebooting the system
freezes at login after I type in my password.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848790
Title:
USB not working under
** Patch added: "fix for bionic"
https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1837889/+attachment/5307176/+files/ndiswrapper_1.60-6ubuntu0.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://errors.ubuntu.com/problem/07b782dcfeb6404740f227f16789748f68ff9b8b
shows no instances post 18.10, and there are no other similar crash
signatures shown on https://errors.ubuntu.com/?package=dpkg=week,
so I'm going to presume this is resolved for 19.04 and later.
** Changed in: dpkg
** Also affects: ndiswrapper (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: ndiswrapper (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: ndiswrapper (Ubuntu Bionic)
Status: New => In Progress
--
You
** Also affects: ndiswrapper (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+ ndiswrapper-dkms won't build with linux-hwe-edge 5.3 kernels.
+
+ [Test case]
+ Build the dkms successfully.
+ Install linux-hwe-edge, then install ndiswrapper-dkms.
+
I am seeing this too on an AMD EPYC 7352 24-Core processor. Removing
amd64-microcode 3.20191021.1ubuntu0.18.04.2 fixed the cyclic reboot
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853614
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: amd64-microcode (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853614
** Changed in: dpkg (Ubuntu Bionic)
Status: Fix Released => Triaged
** Changed in: dpkg (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512322
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
1 - 100 of 408 matches
Mail list logo
