** Summary changed:
-
/usr/bin/Xwayland:6:present_vblank_notify:present_wnmd_flip_notify:present_wnmd_event_notify:xwl_present_sync_callback:ffi_call_unix64
+ Xwayland crashed with SIGABRT in present_vblank_notify() from
present_wnmd_flip_notify() from present_wnmd_event_notify() from
xwl_prese
I couldn't find any existing reports of this crash. Although bug 1811024
and bug 1811025 look related.
** Summary changed:
- Xwayland crashed with SIGABRT ending session upon DP monitor switch-away
+ Xwayland crashed with SIGSEGV in dixGetPrivate() from dixLookupPrivate() from
present_screen_pr
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.20.1-3ubuntu2.1, the problem page at
https://errors.ubuntu.com/problem/6d18e5ae44e375885a66a754cb0b86d1dd1d5eb3
contains
*** This bug is a duplicate of bug 1743736 ***
https://bugs.launchpad.net/bugs/1743736
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** This bug has been marked a duplicate of bug 1743736
In overview, windows from all workspaces are shown for the second display
(whe
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809885
Title:
Gnome-shell onscreen keyboard performance issues
To manage notifica
Thanks. If the directory /var/lib/systemd/rfkill does not exist then
that would be why Bluetooth is always on when you reboot. Because the
flag which is used to indicate that it should be off (soft blocked) is
missing.
Next we need to find out what component should be telling rfkill to save
the bl
** Summary changed:
- Evolution segfaults when NVidia driver is installed but not used
+ Apps segfault when NVidia driver is installed but not used
** Summary changed:
- Apps segfault when NVidia driver is installed but not used
+ Evolution segfaults when NVidia driver is installed but not used
Public bug reported:
Selecting previously unselected package geoip-database-contrib.
dpkg: considering removing geoip-database in favour of geoip-database-contrib
...
dpkg: yes, will remove geoip-database in favour of geoip-database-contrib
(Reading database ... 46544 files and directories curren
Oops, was meant for geoip-database-contrib. My bad.
** Package changed: geoip-database (Ubuntu) => geoip-database-contrib
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811029
Title:
Packa
I'm not yet convinced this is the same as bug 1730241.
The stack trace is different, and the above Xorg logs shows there is
Nvidia hardware:
[57.822] (II) NVIDIA(0): NVIDIA GPU GeForce 210 (GT218) at PCI:3:0:0 (GPU-0)
[57.822] (--) NVIDIA(0): Memory: 524288 kBytes
** This bug is no longe
*** This bug is a duplicate of bug 1810929 ***
https://bugs.launchpad.net/bugs/1810929
Moving to bug 1810929.
** This bug has been marked a duplicate of bug 1810929
totem crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
*** This bug is a duplicate of bug 1810929 ***
https://bugs.launchpad.net/bugs/1810929
preethi,
Please run:
lspci -k
and send us the output, so that we can see what GPUs (and drivers) you
are using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Here are the log files you requested
** Attachment added: "bacula-logs.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1790554/+attachment/5227826/+files/bacula-logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
and the output of the journalctl -xe command. Hope this helps.
Thank you
** Attachment added: "journalctl-output.txt"
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1790554/+attachment/5227827/+files/journalctl-output.txt
--
You received this bug notification because you are a member
If you can afford to wipe the disk then I would suggest a fresh install
of 18.04 instead.
Otherwise, next time the screen freezes, please reboot and then run:
journalctl -b-1 > prevboot.txt
and attach the file 'prevboot.txt' here.
--
You received this bug notification because you are a membe
In that case this is either a problem with the HDMI socket on the
computer or a kernel bug.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
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/1810097
Title:
HDMI is not recognized
To manage notificat
Even better, please:
1. Reproduce a failed boot, and then a successful boot immediately
after.
2. Run this command to collect the log from the previous failed boot:
journalctl -b-1 > failedboot.txt
and send us the resulting file 'failedboot.txt'.
--
You received this bug notification be
Good, it sounds like we are making progress and there are multiple bugs.
We can keep using this bug simply because the symptoms seem the same,
even though it's not bug 1727356 any more.
The message:
[ 3.713332] fb: switching to inteldrmfb from VESA VGA
is probably not relevant at all. It is norm
This looks odd: PulseAudio is not running, so of course you won't get
any sound:
!!Sound Servers on this system
!!
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - No
To try and fix that please add a line to /etc/pulse/daemon.conf:
realtime-s
Interestingly the same model laptop with the same Ubuntu release and the
same PulseAudio version is reported to partially work in bug 1788121.
I'm not sure "Pulseaudio fails to detect card" is the right description
here. What problems are you actually experiencing that make you think
PulseAudio ha
I was able to verify the fix works for bionic using maas 2.4.3. Am about
to install cosmic on the customer hardware to verify the fix there too.
I have run into a maybe-related issue with maas 2.5.0 filed separately
here: https://bugs.launchpad.net/maas/+bug/1811021
--
You received this bug noti
It looks like the compiler has failed!?
CC [M] /var/lib/dkms/nvidia-384/384.130/build/nvidia/nv-p2p.o
\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00�
scripts/Makefile.build:277: recipe for target
'/var/lib/dkms/nvidia-384/384.130/build/nvidia/nv-i2c.o' failed
make[2]: *** [/var/lib/d
Looks like a repeat of bug 1760876. But that's meant to be fixed
already!?
DKMS make.log for nvidia-390.77 for kernel 4.15.0-43-generic (x86_64)
gio 3 gen 2019, 13.02.14, CET
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-43-generic'
Makefile:975: "Cannot use CONFIG_STACK_VALIDATION=y
Still occurring in bug 1810406..!?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760876
Title:
DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y,
please install libelf-dev, libel
Yes, still present in 18.04.
** Changed in: thunar (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389964
Title:
Thunar's Open Terminal Here is missing the
Great idea. I didn't know you could get the recording from boots that were
done previously.
I reproduced a failed boot, and then a successful boot. Please find
attached "failedboot.txt" and just for fun, I recorded the successful boot
as well. It is attached as "successfulboot.txt"
Also find a
Same problem on Ubuntu 18.10 with both the repo 0.16.6712+dfsg1-3build1
version and the current Appimage 0.17 version.
OS: Ubuntu 18.10 x86_64
Kernel: 4.20.0-042000-generic
Packages: 2151 (dpkg), 26 (flatpak), 32 (snap)
Shell: bash 4.4.19
Resolution: 1680x1050, 1920x1200
DE: GNOME 3.30.1
WM:
$ freecad
FreeCAD 0.16, Libs: 0.16R
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2015
# ###
## # # # #
# ## # # # # #
# # # # # # # # # #
# # ##
Thanks. I can't yet see any failures in failedboot.txt. What's strange
is that it claims to be using Xorg and rendering on the 1280x800 laptop
screen successfully.
1. Please check again that you followed the steps in comment #10
exactly, and redo them.
2. Please also run this command:
find /e
The dmesg contains full of "System PCM: error: failed to commit stream
-110", no touchpad related message can be found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809841
Title:
Touchpad showing
V4L2 doesn't have anything to do with video decoding that I know of, but
maybe ARM is different...
Yes I think that should read "VAAPI", not "V4L2".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17996
Seems both statements are true :)
The above patches relate to parts of the Chromium source named V4L2. But
for the most efficient desktop video decoding you need to use VAAPI
(https://bugs.chromium.org/p/chromium/issues/detail?id=463440).
I'm not sure those two are related, or that the former can
More information about VP9 and other decoding in V4L2:
https://linuxtv.org/downloads/v4l-dvb-apis/uapi/v4l/extended-controls.html
I think that relates to Digital TV tuners only, and am not sure it
applies to machines that don't have any digital TV hardware attached.
--
You received this bug noti
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
For the commit mentioned in this test:
Test case #2 is a regression test for commit b469e7e47c8a
To get this into Bionic kernel, two other cherry-picks are needed:
1. cf6939e9 (fanotify: generalize fanotify_should_send_event())
2. 8c6d8147 (fsnotify: send path type events to group with supe
[Expired for glibc-doc-reference (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: glibc-doc-reference (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Hello Corey, or anyone else affected,
Accepted nova into queens-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo add-apt-r
For the commit mentioned in this test:
Test case #2 is a regression test for commit b469e7e47c8a
To get this into Bionic kernel, two other cherry-picks are needed:
1. 837a3934 (fanotify: generalize fanotify_should_send_event())
2. 60f7ed8c (fsnotify: send path type events to group with supe
The new version 1.52.5-0ubuntu18.04.1 seems to work well on bionic.
Strange I was unable to reproduce the original bug before installing it.
But after installing it, there is still no problem either.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811047
Title:
package linux-image-extra-4.4.0-141-generic (not installed) failed to
install/upgrade: unable to
Public bug reported:
dpkg: error processing archive
/var/cache/apt/archives/linux-image-extra-4.4.0-141-generic_4.4.0-141.167_amd64.deb
(--unpack):
unable to open
'/lib/modules/4.4.0-141-generic/kernel/drivers/atm/ambassador.ko.dpkg-new':
Operation not permitted
Errors were encountered while
** Changed in: revelation (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/573676
Title:
Crashes when saving to GVFS mounts
To manage notifications about th
** No longer affects: gjots2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739800
Title:
Please remove gnome-python from Ubuntu
To manage notifications about this bug go to:
https://bugs.
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/1811047
Title:
package linux-image-extra-4.4.0-141-generic
Thank you for reporting the bug.
Could you please try to reproduce it with a master build from
http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still
** Changed in: df-libreoffice
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797373
Title:
3D slide transitions don't work at all or tear when played + repeat
anim
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811048
Title:
package mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 failed to
install/upgrade: installed mysql-serve
Public bug reported:
password is not asking while installing
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.24-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architec
Public bug reported:
# apt install lxc-templates
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
busybox-static cloud-image-utils debootstrap dirmngr distro-info genisoimage
gnupg gnupg-l10n gn
Comment 10 being the reproduce a failed boot, then successful boot and save
the failed boot log?
On Tue, Jan 8, 2019 at 8:55 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Thanks. I can't yet see any failures in failedboot.txt. What's strange
> is that it claims to be using Xorg and
What about snaps that operate as a command line and an environment
variable? I set IPFS_PATH to /mnt/Shared/IPFS, but IPFS outputs a
"permission denied".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Ok, once you know you'll be able to verify it on Cosmic as well (by
successfully testing from the PPA) let me know.
We will then upload it as a real SRU which needs verification per [1].
[1]: https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a me
Public bug reported:
[Impact]
New Realtek ethernet chips don't work.
[Fix]
Add new IDs to r8169.ko.
[Test]
The r8169 is loaded for the Realtek ethernet chip.
It works, and I haven't seen any issues so far.
[Regression Potential]
Low. New IDs to existing driver, no functional change.
** Affect
Public bug reported:
[Impact]
New Realtek ethernet chips don't work.
[Fix]
Add new IDs to r8169.ko.
[Test]
The r8169 is loaded for the Realtek ethernet chip.
It works, and I haven't seen any issues so far.
[Regression Potential]
Low. New IDs to existing driver, no functional change.
** Affect
Public bug reported:
[Impact]
New Realtek ethernet chips don't work.
[Fix]
Add new IDs to r8169.ko.
[Test]
The r8169 is loaded for the Realtek ethernet chip.
It works, and I haven't seen any issues so far.
[Regression Potential]
Low. New IDs to existing driver, no functional change.
** Affect
** Tags added: originate-from-1788343 somerville
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811055
Title:
Support new Realtek ethernet chips
To manage notifications about this bug go to:
https:
To clarify, when the original problem was discovered in cosmic the CPU
usage was around 80%, and the fix made it less than 50% [1].
But now even without the fix (although in bionic, still using the same
hardware), CPU usage for the same test case is around 50%. So indeed the
main issue seems to be
This bug was fixed in the package grub2 - 2.02+dfsg1-5ubuntu9
---
grub2 (2.02+dfsg1-5ubuntu9) disco; urgency=medium
[ Steve Langasek ]
* debian/patches/quick-boot-lvm.patch: If we don't have writable
grubenv and we're on EFI, always show the menu. Closes LP: #1800722.
[ Ma
gnome-shell-extension-ubuntu-dock (64ubuntu1) disco; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release: 64
* dash, docking: remove Shell.GenericContainer.
[ Adolfo Jayme Barrientos ]
* Update Spanish translation.
[ franglais125 ]
* Settings.ui: Fix GtkEntry propert
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1811055
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1811053
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1811054
and then change the status of the bug to 'Confirmed'.
If, due to the nature
As discussed on IRC this would most likely be a Cloud Archive only patch on top.
Therefore we don't even need a new qemu bug for it, we can add a task here.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: New => Confirmed
--
For the actual change, you'd want to do this:
in qemu's debian/contol.in there are a bunch of Recommends and Depends like
this:
ipxe-qemu (>= 1.0.0+git-2013.c3d1e78-1~)
change all those in UCA to
ipxe-qemu (>= 1.0.0+git-20180124.fbe8c52d-0ubuntu2.1~)
That should avoid further issues with
Interesting, thanks Leonardo!
Tested on Bionic (4.15) and Disco (4.18).
Default:
sudo modprobe kvm_pr
modprobe: ERROR: could not insert 'kvm_pr': Input/output error
Added "disable_radix" to the guest kernel commandline and retried loading the
module again.
Bionic: Malformed early option 'disable
Public bug reported:
selftests: seccomp_bpf
[==] Running 64 tests from 1 test cases.
[ RUN ] global.mode_strict_support
[ OK ] global.mode_strict_support
[ RUN ] global.mode_strict_cannot_call_prctl
[ OK ] global.mode_st
Issue has returned with Kernel 4.15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609211
Title:
[Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at
all
To manage notifications a
401 - 468 of 468 matches
Mail list logo
