It will help to add whatever stack trace was submitted to the xen
mailing list, to this bug report.
** Package changed: linux-meta-hwe (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confir
** Changed in: linux-firmware (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829737
Title:
Bluetooth: hci0: request failed to create LE connection: status
Hello,
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
dpkg -l clamav-freshclam | cat
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-
insta
Public bug reported:
after a sleep & resume cycle, the desktop wallpaper has a darker color,
as if a black layer was applied to it with some transparency.
if I restart and log in, the wallpaper is the original color
my expectation is that the desktop wallpaper image should have the same,
unchang
** Description changed:
Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in
a fully updated Ubuntu 16.04 desktop,
To reproduce on any Ubuntu 16.04 classic (Xenial):
#fwupdmgr refresh
failed to update metadata: Failed to parse XML: Mismatched XML
The core s
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829812
Title:
Regression for ubuntu_bpf test case in 5.0.0-16
To man
Maybe it goes like this:
then window receives focus scrolling content is shifted either
by horizontally or vertically. >:]
Slow text should be usually a first sign that something is
wrong. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On 2019-05-21 05:37:09, Mark wrote:
> Actually, is the microcode loaded at all?
>
> # cat /sys/devices/system/cpu/cpu0/microcode/version
> cat: /sys/devices/system/cpu/cpu0/microcode/version: No such file or
> directory
That's odd. Try replacing cpu0 with cpu* to see if a version file exists
fo
> 2. The behavior you expected.
Fast text.
> 3. The behavior you actually encountered (in as much detail as
possible).
Hardware overheats. This is considered abnormal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
trying to install ubuntu, error message something like
failed to install 'grub'...
Will not boot
desktop provided to try and solve problem or reinstall
the second time of trying
please help
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVe
hello,
appreciate if anyone can help me with this, I'm getting more than 3
emails per min its crazy :(
This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows the state
of the program at the time the error occurre
** Changed in: xfce (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/1829671
Title:
Alt + TAB + Shift TAB fixes momentum physics >:]
To manage notifications a
** Description changed:
Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in
a fully updated Ubuntu 16.04 desktop,
- To reproduce on any Ubuntu 16.04 classic:
+ To reproduce on any Ubuntu 16.04 classic (Xenial):
#fwupdmgr refresh
failed to update metadata: Failed
Public bug reported:
Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in
a fully updated Ubuntu 16.04 desktop,
To reproduce on any Ubuntu 16.04 classic:
#fwupdmgr refresh
failed to update metadata: Failed to parse XML: Mismatched XML
The core snap `uefi-fw-tools` used in Ub
On 2019-05-21 05:28:18, Mark wrote:
> > If that doesn't work, can you try to boot with 'mitigations=off'
> > passed on the kernel command line?
>
> on the other hand, mitigations=off did cut it!
> I guess now we're to find which of the mitigations is causing it? Do
> you have a hint? Which are al
PS,
#dmesg | grep microcode
#
returns nothing on the ubuntu hwe-edge kernel with mitigations=off
(=problematic ucode otherwise loaded)
Actually, is the microcode loaded at all?
# cat /sys/devices/system/cpu/cpu0/microcode/version
cat: /sys/devices/system/cpu/cpu0/microcode/version: No such fi
This bug was fixed in the package apport - 2.20.11-0ubuntu2
---
apport (2.20.11-0ubuntu2) eoan; urgency=medium
* test/test_backend_apt_dpkg.py: as of r3211 an error is not raised if the
binary is not found. Cherry picked from upstream r3248.
* backends/packaging-apt-dpkg.py: w
Tyler,
> Can you try to boot with the latest Ubuntu kernel, with the
problematic microcode, using 'mds=off' on the kernel command line? (Note
that it is 'off' instead of 'no')
I tried with mds=off, but no avail.
> If that doesn't work, can you try to boot with 'mitigations=off'
passed on the ker
This bug was fixed in the package apport - 2.20.11-0ubuntu2
---
apport (2.20.11-0ubuntu2) eoan; urgency=medium
* test/test_backend_apt_dpkg.py: as of r3211 an error is not raised if the
binary is not found. Cherry picked from upstream r3248.
* backends/packaging-apt-dpkg.py: w
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 1829812
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
This test will failed to build on 5.0.0-16 Disco.
5.0.0-16 Disco + 5.0.0-15 source code - build OK
5.0.0-16 Disco + 5.0.0-16 source code - Failed
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
gcc -o
/hom
Mark, one more request for now. You say that you can boot up a non-
Ubuntu kernel with the problematic microcode. Can you boot up one of
those kernels and then verify the microcode revision with the following
command:
$ sudo cat /sys/devices/system/cpu/cpu0/microcode/version
Please paste the re
Simon, can you post the contents of /proc/cpuinfo as well? It'd help
with tracking down which processors might be affected by this. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829620
Title:
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794
[Expired for libinput (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libinput (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821
shut down windos and rebooted Ubuntu.
No Sound
As SU ran echo 1 > parameters/dump_coef
Speaker sound works for about 10 seconds.
The following is the report from alsa-info
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran on:
After the sound quit I ran Alsa-info and got the following:
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran on: Tue May 21 03:48:17 UTC 2019
!!Linux Distribution
!!--
Ubuntu 19.04 \n \l DISTRIB_ID=Ubuntu DIS
I found this issue on B-hwe 4.18, node "gonzo" (passed on another node
amaura)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812988
Title:
ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_k
This is something that's failing for a while (was affected by bug
1802443, and then this one since 4.18.0-13.14~18.04.1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802495
Title:
lttng-smoke test
** Changed in: gnome-shell (Ubuntu)
Importance: Low => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829651
Title:
Caps Lock indicator on screen
To manage notifications about this bug
In theory, adding model=auto (comment #3) doesn't affect your sound
driver since even without model=auto, the audio driver doesn't apply any
fixup models to your machine.
Please do a test:
cd /sys/module/snd_hda_codec
sudo su
echo 1 > parameters/dump_coef
Then test your speaker, when the speaker
Update: The patches have been merged to drm-tip:
https://cgit.freedesktop.org/drm-
tip/commit/?id=1a74fc0b3f49a0603f230b6f087da33bda3d7c66.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714178
Title:
Attach file openstack-sru-19.1.1.txt.
** Attachment added: "openstack-sru-19.1.1.txt"
https://bugs.launchpad.net/bugs/1828637/+attachment/5265184/+files/openstack-sru-19.1.1.txt
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new feature
Attach file azure-sru-19.1.1.txt.
** Attachment added: "azure-sru-19.1.1.txt"
https://bugs.launchpad.net/bugs/1828637/+attachment/5265183/+files/azure-sru-19.1.1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Attach file ec2-sru-19.1.1.txt.
** Attachment added: "ec2-sru-19.1.1.txt"
https://bugs.launchpad.net/bugs/1828637/+attachment/5265181/+files/ec2-sru-19.1.1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Attach file gce-sru-19.1.1.txt.
** Attachment added: "gce-sru-19.1.1.txt"
https://bugs.launchpad.net/bugs/1828637/+attachment/5265182/+files/gce-sru-19.1.1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
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"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
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
Please be sure to only report one problem per bug. We will make this bug
about the first problem you report only.
** Summary changed:
- misc. problems
+ problem with login to user account. Keeps going back to login window
--
You received this bug notification because you are a member of Ubuntu
Thanks, but we will need more data points. We need to know at least one
kernel version which does not have the bug (if a version exists). And
then we need to know the earliest version where the bug was introduced.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Yes those messages themselves are safe, but I think they may suggest the
kernel got stuck for a while (somewhere, anywhere). And that would
correlate with this bug.
If there were any other kernel log messages around that time then please
paste them here.
--
You received this bug notification bec
I can't see anything else in that log which might explain the freeze.
First, if you have any nonstandard gnome-shell extensions installed then
please uninstall them.
Next, please follow the steps in comment #4 in case the freeze is a
crash, of something.
--
You received this bug notification be
Someone probably needs to find a relevant upstream Xorg bug link to see
where/if it is being discussed there.
This is not the place where Xorg developers discuss such things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
BIOS Information
Vendor: Dell Inc.
Version: 1.1.5
Release Date: 04/03/2018
Address: 0xF
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
PNP is supported
I can't see any reason for the dock going permanently missing in that
log. It might be a good idea if anyone experiencing this problem opens a
new bug with all the required attachments, by running:
ubuntu-bug gnome-shell
which will do it automatically.
--
You received this bug notification be
Another reboot from Ubuntu back to Ubuntu and the Headset is still
silent, BUT now the speaker sound works. Connecting and disconnecting
the headset now has no effect on speaker sound except to mute when the
headset is plugged in. I apologize for scattershot troubleshooting.
--
You received this
** Tags added: disco eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702151
Title:
gnome-shell crashed with SIGSEGV in
g_type_check_instance_is_fundamentally_a() from g_object_ref() from
st_
On Intel ICL-Y SDP(alpha):
Before patched
short idle: 13.46w
long idle: 12.94w
s2idle: 12.67w
After patched:
short idle: 13.45w
long idle: 13.06w
s2idle: 12.87w
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Correction. The sound through the speakers only lasts for about 10
seconds. When I plug the headset in there still no sound in the
headset, but when I unplug the headset the sound through the speakers
resumes but then quits after about 10 seconds.
--
You received this bug notification because y
In accordance with this: https://docs.slackware.com/howtos:hardware
:audio_and_snd-hda-intel#how_to_find_the_right_options
I ran this: sudo echo "options snd-hda-intel model=auto" >
/etc/modprobe.d/snd-hda-intel.conf and rebooted.
That resulted in both the speakers and headphones working. But in
Public bug reported:
Don't have details about the issue!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Compos
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1829805
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827967
Title:
There are 4 HDMI/Displayport audio output listed in s
** Attachment added: "Screenshot_eoan_2019-05-20_20:27:48.png"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1829805/+attachment/5265149/+files/Screenshot_eoan_2019-05-20_20%3A27%3A48.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Context: The live environment appears to function properly and install
proceeds as expected with no noticeable errors.
Expected results: After a system reboot the virtual machine enters the
graphical environment
Actual Results: After rebooting the virtual machine a kernel pa
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
F
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe (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/1829756
Ti
I'll point out that munbi is seeing this hit using the following CPU sig
and microcode revision:
sig=0x306c3, pf=0x10, revision=0x27
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829255
Title:
S
Hello and thanks for the bug report. We hate to hear that you're seeing
such a performance hit on your application when the MDS mitigations are
enabled. Unfortunately, we are simply following Intel's
recommendations[1] for mitigating MDS attacks. The kernel changes are
relatively simple and the ove
Public bug reported:
a) problem with login to user account. Keeps going back to login window
b) screen freeze after suspension. amdgup needs update
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0
** Attachment added: "Add dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1829784/+attachment/5265133/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829784
Hi, thanks for the report, the 0514 release was supposed to be unchanged
from the 0507 beta, but was not.
There is also supposed to be an update for Sandy Bridge forthcoming.
** Changed in: intel-microcode (Ubuntu)
Status: New => In Progress
** Changed in: intel-microcode (Ubuntu)
As
Hello, I noticed several problems in the logs:
First, it appears the filesystems may have problems:
[86759.038651] EXT4-fs (dm-0): error count: 13
[86759.038661] EXT4-fs (dm-0): initial error at 1504970654:
ext4_journal_start_sb:327
[86759.038665] EXT4-fs (dm-0): last error at 1505132213: ext4_p
Same here in Ubuntu 18.04.
Monitor manager and other gnome extensions are disappearing from the top panel.
Alt-F2 r, like other said, helps to get them back. Extensions are still running
though when the bug appears.
I noticed this behavior some time ago, maybe 3-4 months ago, after an
upgrade bu
Hello, it looks like you had trouble connecting to WiFi, and perhaps
other hardware problems:
May 20 11:20:44 ubuntu wpa_supplicant[1323]: wlp1s0: SME: Trying to
authenticate with 92:2a:a8:9a:a4:98 (SSID='srh-welcome' freq=2437 MHz)
May 20 11:20:44 ubuntu kernel: [ 669.922382] wlp1s0: authentica
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829745
Title:
3.20190514.0ubuntu0 actually contains version 20190507 Release
To m
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Hello, this appears to be using a freshclam and clamav installed outside
of the packaging system. I suggest using the packaged versions of these
tools. If that's not an option for whatever reason, then the clamav
community would be a better place to ask for help.
Thanks
--
You received this bug
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.
Hello, it looked like you had some problems connecting to wifi -- and
perhaps other hardware problems as well. I hope this helps:
[ 2164.414923] wlp1s0: deauthenticating from 26:0d:65:1e:76:1d by local choice
(Reason: 3=DEAUTH_LEAVING)
[ 2164.541523] wlp1s0: authenticate with 5c:99:60:97:1a:d0
[
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug by Seth Arnold (seth-arnold):
intel-microcode 3.20190514.0ubuntu0 contents does not match
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files but
rather seems to be version 20190507 acco
I have almost the same problem.
i run ubuntu 14.04 and for me its linux 4.4.0-146 that starts normal
148 only give the purple ubutu screen, but nothing after that
148 recovery stops after initial RAM disk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
I have found a code for Goodix fingerprint sensor. That code is mainly
written for Android devices. I have tried to compile it for Ubuntu
19.04. This code would be helpful to write a new driver. This code is
written for the SPI interface. It would be useful if someone can try to
rewrite this code f
I have found a code for Goodix fingerprint sensor. That code is mainly
written for Android devices. I have tried to compile it for Ubuntu
19.04. This code would be helpful to write a new driver.
https://github.com/adnanjee/Goodix-GF3208
--
You received this bug notification because you are a mem
** Changed in: mesa
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753677
Title:
es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display
To manage notificati
** Changed in: evince
Status: Unknown => 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/1829785
Title:
Evince: ∞ not found
To manage notifications about this bug go to:
https://b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gimp (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/1810557
Title:
GIMP
** 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 --
+ boot-testi
Hm so it sounds like snapd's behaviour is what Dimitri is asking for
here? Has this changed in snapd recently (note that this behaviour was
observed during the disco release sprint, so April 2019).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: gcc-4.8 (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/1322784
Title:
Firefox crashes in flag_qsort during spellchecker initialization on
Bug report refers to the bbc plug-in which no longer exists
Closing as report is no longer valid
** Changed in: totem (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
In comment 28, the freeze happened just before taking the log, yet the
last log entry was from ~1 minute earlier, so it doesn't look like there
were any relevant log entries.
However just now I had a freeze, and there are some messages in dmesg:
[10980.231902] perf: interrupt took too long (2512
Take care, current kernel 4.15.0-1036.38 still not bootable with EFI.
** Changed in: linux-raspi2 (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/b
** Changed in: ubuntu-advantage-script
Status: Unknown => 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/1829788
Title:
backtrace on attach: KeyError: 'effectiveTo'
To manage not
It's committed in the disco packaging repository, but not uploaded. I
planned on bundling that change with other changes in an SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735071
Title:
Ctrl
** Merge proposal linked:
https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/366862
** Merge proposal linked:
https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/366863
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Sebastien, though the Russians the same symbol in mathematics for the
infinity, the infinity symbol ∞ itself is not Cyrillic. Have you tested
their solution, whatever it may be, simply to make sure that that's the
same issue?
--
You received this bug notification because you are a member of Ubun
Correct, the qrt script needed to catch up to the config changes that
have landed in the 4.4, 4.15, and 4.18 kernel branches. I've done this
in https://git.launchpad.net/qa-regression-
testing/commit/?id=fca40854ff8d65c1fb4a19f57a8e541e3655aab9 .
Closing tasks, thanks.
** Changed in: qa-regressio
OK, I've attached the requested info from my system. It goes back 4
days, so it should include the period when it stopped working.
Unfortunately I can't tell you exactly when that was - having the dock
autohide means it's pretty much hidden until I need it.
** Attachment added: "currentjournal.txt
also on 18.04.02 LTS, also other people mentioned in comments
https://askubuntu.com/questions/114429/default-save-directory-for-gnome-
screenshot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977228
T
@Sebastien Bacher, another screenshot of "Volume mute" attached. Caps
Lock indicator also should be "on screen" looks like other indicators.
not on top bar or anywhere else. for example when Caps Lock is on bright
white A logo in the box, and when Caps Lock is off gray crossed A looks
like the volu
Hi. i am expecting a Caps Lock indicator by default (without need of
usage any 3rd party app which are not working proper tested few) like
the screenshot of Volume indicator as an example i attached. thanks.
** Attachment added: "example - Volume indicator on screen"
https://bugs.launchpad.net
Thank you for your reply and for looking into this issue. I will contact
Lenovo but I won't get my hopes up. Operating the dock w/o MAC
passthrough is luckily not a big deal for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
$ grep BINFMT_AOUT /boot/config-4.18.0-2[01]-generic
/boot/config-4.18.0-20-generic:CONFIG_BINFMT_AOUT=m
/boot/config-4.18.0-21-generic:# CONFIG_BINFMT_AOUT is not set
Marking cosmic as verification-done.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You
This bug was fixed in the package mdadm - 4.1-2ubuntu2
---
mdadm (4.1-2ubuntu2) eoan; urgency=medium
* Drop broken and unused init scripts in favor of native systemd units,
which can cause failure to reconfigure mdadm package under certain
confiment types. LP: #1829325
--
Mark, thanks for all the testing. Unfortunately, I asked Steve to have
you try the wrong 'mds=' option.
Can you try to boot with the latest Ubuntu kernel, with the problematic
microcode, using 'mds=off' on the kernel command line? (Note that it is
'off' instead of 'no')
If that doesn't work, can
Could you add your journalctl log to the bug?
3.32.1 is also in disco-proposed so it would be good to also test if the
problem exist there/is really with gnome-shell
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New => Inc
The issue has been reported upstream in
https://gitlab.gnome.org/GNOME/evince/issues/1116
** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1116
https://gitlab.gnome.org/GNOME/evince/issues/1116
** Changed in: evince (Ubuntu)
Status: New => Triaged
** Also affects: evince via
1 - 100 of 573 matches
Mail list logo
