Marking charm task as invalid as this is a kernel issue with the xenial
release kernel.
Ubuntu/Linux bug task raised for further progression if updating to the
latest HWE kernel on Xenial is not an option.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Public bug reported:
Issue found on 4.15.0-1061-kvm, with KVM instance zeppo, moe.
The ubuntu_kvm_smoke_test will fail with:
uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:ee:15:c8.
Traces can be found in syslog.
systemd[1]: Started Daemon for generating UUIDs.
kernel: kaud
*** This bug is a duplicate of bug 1877024 ***
https://bugs.launchpad.net/bugs/1877024
** This bug has been marked a duplicate of bug 1877024
package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade:
unable to open '/usr/lib/libreoffice/share/gallery/environment.sdg.dpkg-new':
** Bug watch added: Debian Bug tracker #943874
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943874
** Also affects: pure-ftpd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943874
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu Focal)
Status: New => Won't Fix
** Changed in: mesa (Ubuntu Focal)
Assignee: (unassigned)
*** This bug is a duplicate of bug 1868520 ***
https://bugs.launchpad.net/bugs/1868520
** This bug has been marked a duplicate of bug 1868520
Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010
Has anybody tested using libmariadb3? There are no backwards
incompatible changes in libmariadb3 - MythTV should run just fine with
libmariadb3.
If there will be backwards incompatible updates the library will be
dumped to libmariadb3. If Oracle MySQL has now in libmysqlclient21
version 8.0.20 so
I think mine is the same. Problem with LVM2. Information as follows:
Setting up lvm2 (2.03.07-1ubuntu1) ...
update-initramfs: deferring update (trigger activated)
Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
invoke-rc.d: initscript lvm2-lvmpolld, action "restart" f
Verification completed across all UCA and Ubuntu series.
It would be good to get this released today - waiting on SRU team for
eoan release before releasing to the UCA pockets.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Bug watch added: Debian Bug tracker #960072
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960072
** Also affects: mailman3 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960072
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
*** This bug is a duplicate of bug 1877504 ***
https://bugs.launchpad.net/bugs/1877504
The bug started to trigger after an update to libmysqlclient21 from
8.0.19 to 8.0.20. This is Oracle MySQL being backwards incompatible with
any earlier version of MySQL or MariaDB. Please don't imply that t
The issue has to deal with how the package is build. Both arch-dependent
and arch-independent packages are built for amd64 now. However, the
build rule for arch-independent messes up the build for arch-dependent
(i.e. the part that libjniwebkit belongs to).
--
You received this bug notification b
I had another look at the entire thread at lore.kernel.org:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-email-na...@linux.ibm.com/T/#u
and think patch
"powerpc/ima: Fix secure boot rules in ima arch policy"
is the one that fixes 'powerpc/ima: fix secure boot rules in ima arc
*** This bug is a duplicate of bug 1855711 ***
https://bugs.launchpad.net/bugs/1855711
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880850
Title:
Ubuntu 20.04 keyboard doesn't work in
UCA bionic-rocky/proposed
$ apt-cache policy python3-neutron
python3-neutron:
Installed: 2:13.0.7-0ubuntu1~cloud1
Candidate: 2:13.0.7-0ubuntu1~cloud1
Version table:
*** 2:13.0.7-0ubuntu1~cloud1 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu
bionic-proposed/rocky/main amd6
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1277
https://gitlab.gnome.org/GNOME/mutter/-/issues/1277
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1277
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
Sorry for wrong configuration involved, the correct configure should be
: /usr/local/lib/xen/bin/qemu-system-i386 -->/usr/bin/qemu-system-i386
and bug reproduced with the new configuration.
Environment:
Host OS :Ubuntu20.04
Host kernel:5.4.0-29-generic
xen version:4.11.4-pre
Bug
** Description changed:
SRU Justification:
==
[Impact]
* Code that is using s390_pci_mmio_write/read system calls on a z15
(that comes with enhanced PCI load/store instructions), fails with
"Unable to handle kernel pointer dereference in virtual kernel address
s
I would suggest that you put proper debian/control conflicts for
libmysqlclient21 to signify that things that worked with
libmysqlclient20 might stop working. If libmysqlclient21 is incompatible
with libmysqlclient20 ways of doing things, it will automatically be
incompatible with any previous vers
** Description changed:
Description:
Add kernel enumeration support for AiA Enq* instructions.
Need GCC (either version 9 or 10) Intrinsic support, Intrinsic GCC
dependency
- Target Kernel: 5.7
+ Target Kernel: 5.8
Target ReleasE: 20.10
--
You received this bug notification be
*** This bug is a duplicate of bug 1738838 ***
https://bugs.launchpad.net/bugs/1738838
Thanks. That means it's not a hardware problem, and is definitely a
duplicate of bug 1738838.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
This bug existed yesterday on my Ubuntu 20.04. I probably had suspended
the laptop. A couple of days ago, it was working fine even after
suspending the laptop.
I haven't tried rebooting the laptop. Rebooting might work fine. But I
want a permanent fix. I don't think it's about the driver issue.
B
*** This bug is a duplicate of bug 1855711 ***
https://bugs.launchpad.net/bugs/1855711
Yes that is bug 1855711 which requires fixes in multiple components. See
also https://gitlab.gnome.org/World/ShellExtensions/desktop-
icons/-/issues/31
** Bug watch added:
gitlab.gnome.org/World/ShellExten
** Summary changed:
- Add keyboard navigation
+ Add keyboard navigation to desktop icons
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855711
Title:
Add keyboard navigation to desktop icons
To ma
*** This bug is a duplicate of bug 1738838 ***
https://bugs.launchpad.net/bugs/1738838
Output of rfkill:
ID TYPE DEVICE SOFT HARD
1 wlan phy0 unblocked unblocked
5 bluetooth hci0 unblocked unblocked
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1855711 ***
https://bugs.launchpad.net/bugs/1855711
No, I think https://bugs.launchpad.net/ubuntu/+source/gnome-shell-
extension-desktop-icons/+bug/1855711 is not my issue.
I mean to say, the keyboard doesn't work particularly on the desktop
icons. However,
** Bug watch added: KDE Bug Tracking System #407855
https://bugs.kde.org/show_bug.cgi?id=407855
** Changed in: kde-workspace
Importance: Undecided => Unknown
** Changed in: kde-workspace
Status: New => Unknown
** Changed in: kde-workspace
Remote watch: None => KDE Bug Tracking Syst
*** This bug is a duplicate of bug 1774902 ***
https://bugs.launchpad.net/bugs/1774902
** This bug has been marked a duplicate of bug 1774902
kubuntu - can't login with NFS $HOME
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: snapd (Ubuntu) => plasma-workspace (Ubuntu)
** Project changed: kde-baseapps => kde-workspace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774902
Title:
kubuntu - can't login
Public bug reported:
After clicking on the current Icon under Edit Laucher or under Whisker
Menu and getting the "Select an Icon" or "Select an icon" window with a
list of icons, if you click on any icons, they are rendered as black.
Happens regardless of theme and happens even with fresh users.
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875099
Title:
RTL8822BE Wifi [10ec:b822] subsystem [17aa:b
Ok Riccardo, could you - once you find the other issue - file a new bug then.
I'll take this bug here to drive the issue(s) identified to far to a conclusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Please attach your /var/log/apt/history.log so we can see what changed
on the 28th of May.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Chan
Please try without these extensions:
'unitylike-hot...@webgyerek.net',
'workspace-indica...@gnome-shell-extensions.gcampax.github.com',
'wsmat...@martin.zurowietz.de',
'launch-new-insta...@gnome-shell-extensions.gcampax.github.com',
'panel-...@berend.de.schouwer.gmail.com',
'dash-to-d...@micxgx.gm
The release notes have been fixed to document the need for -d until the
point release.
I categorically disagree that we should message an LTS-to-LTS upgrade,
prior to the first point release, as anything other than "development".
During each LTS cycle, we are routinely fixing critical upgrade bugs
Can you please remove "nomodeset" kernel parameter?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875200
Title:
[amdgpu] Entire
Note that I didn't add any kernel parameter, so my first guess would be
"iommu=pt" doesn't get passthrough right.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Tried 4.15.0-102, 5.4.0-33 and mailing kernel all three show similar
performance (~2100MB/s).
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/
And decide what's the next step based on the performance of mainline
kernel.
--
You received this bug notifi
Public bug reported:
not install proper restart os
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: phpmyadmin 4:4.9.5+dfsg1-2
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27
Archit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-screensaver (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/1880793
T
Public bug reported:
Mouse vendor: Elecom
Mouse name: Deft M-DT20R
S/N 99011158
S/N 9700261B
I have two sets of this model and both are not working any more.
Wireless USB mouse stopped working after 'sudo apt upgrade' on 0:00 UTC 28th
May 2020.
I also upgraded BIOS of ThinkStation P500 from A4KT8
I don't think it's a kernel issue. Some userspace process blocked the
suspend. Can you please test whether suspend works under Ubuntu live
USB?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
If the kernel still have the issue, please file an upstream bug at
https://bugs.freedesktop.org/
Product: xorg
Component: DRM/nouveau
** Changed in: linux (Ubuntu)
Status: Confirmed => Incom
** Tags added: sru-20200518
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764618
Title:
python-API test in ubuntu_lxc will fail on X-kvm kernel
To manage notifications about this bug go to:
https:
Public bug reported:
When I try to lock my screen (via termial/shortcut/menu icon) it the
screen flashes and screen lock fails to occur.
Error is:
[ 1174.050313] traps: gnome-shell[10135] general protection fault
ip:7f2facd9429a sp:7fff2117e168 error:0 in libc-2.31.so[7f2facc32000+178000]
[ 1196
[Expired for hylafax (Ubuntu) because there has been no activity for 60
days.]
** Changed in: hylafax (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/424250
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc7/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877670
Title:
[Acer Aspire R3-131T] Touchpad freezes and f
apport information
** Summary changed:
- When I do any screen lock action it screen fickers (lock fails)
+ When I do any screen lock action the screen flickers (and lock fails)
** Tags added: apport-collected
** Description changed:
When I look at dmesg it appears that screen lock is causing
apport information
** Attachment added: "XorgConf.txt"
https://bugs.launchpad.net/bugs/1880793/+attachment/5377650/+files/XorgConf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880793
Title:
apport information
** Attachment added: "GsettingsGnomePowerManager.txt"
https://bugs.launchpad.net/bugs/1880793/+attachment/5377646/+files/GsettingsGnomePowerManager.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1880793/+attachment/5377649/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880793
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1880793/+attachment/5377648/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "GsettingsGnomeLockdown.txt"
https://bugs.launchpad.net/bugs/1880793/+attachment/5377645/+files/GsettingsGnomeLockdown.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
apport information
** Attachment added: "GsettingsGnomeScreensaver.txt"
https://bugs.launchpad.net/bugs/1880793/+attachment/5377647/+files/GsettingsGnomeScreensaver.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1880793/+attachment/5377651/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880793
Title:
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1880793/+attachment/5377652/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880793
Ti
This is still failing with the kvm-unit-tests from upstream.
Note that with the upstream repo, you will have to split the vmx_nm_tests like
below:
https://kernel.ubuntu.com/git/ubuntu/kvm-unit-tests/commit/?h=disco&id=4671e4baaec6c968e626e9fc3557aa4581504586
--
You received this bug notificatio
awaiting feedback from the original reporter to confirm that these
particular commands are applicable to his install.
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Bankapur, can find any deauthenticating/disconnecting signature from
the log. Please attach one after the symptom reappears.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879612
Title:
Ralink RT5
BTW the power status on MAAS will be "OFF"
And since this KVM will be in "paused" state, it needs to be destroyed before
re-deploying, it seems this is why we constantly seeing deploying failures on
KVM nodes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Merge proposal linked:
https://code.launchpad.net/~vicamo/ubuntu/+source/backport-iwlwifi-dkms/+git/backport-iwlwifi-dkms/+merge/384690
** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
Assig
** Merge proposal linked:
https://code.launchpad.net/~vicamo/ubuntu/+source/backport-iwlwifi-dkms/+git/backport-iwlwifi-dkms/+merge/384690
** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
Status: New => In Progress
** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
Assignee: (
This issue can be reproduced with KVM nodes on our BareMetal MAAS
Step to reproduce:
1. Deploy a KVM node with Xenial / Bionic
2. sudo apt install gcc build-essential cpu-checker qemu-kvm git
3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/kvm-unit-tests/ -b disco
4. cd kvm-unit-tests
5. ./c
*** This bug is a duplicate of bug 1874662 ***
https://bugs.launchpad.net/bugs/1874662
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look
8324-0ubuntu2 is now in groovy with modaliases removed, so it won't be
pulled automatically from additional drivers from now on.
** Changed in: backport-iwlwifi-dkms (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubun
please also check effect of setting path ,as i installed ubuntu 20 3,4 time
when i instrall node angular or flutter ,screen stop to wake-up after suspend.
Before installation of this soft screen wake-up perfectly.
i never face same issue in ubuntu 18 in same machine.
--
You received this bug
8324-0ubuntu2 is now in groovy with modaliases removed, so it won't be
pulled automatically from additional drivers from now on.
** Changed in: backport-iwlwifi-dkms (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubun
please also check effect of setting path ,as i installed ubuntu 20 3,4
time when i instrall node angular or flutter ,screen stop to wake-up after
suspend.
Before installation of this soft screen wake-up perfectly.
i never face same issue in ubuntu 18 in same machine.
On Wed, May 27, 2020 at 9:4
Public bug reported:
I downloaded the iso using a torrent and as I started the installation
it crashed with an error saying that the medium is broken.
The USB stick used as an installation media works just fine with Windows
10 and Mageia (RPM based distro), but burning any iso of Ubuntu over
16.0
Difficulty to boot when processing "block device major 147"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/271254
Title:
[ffe] drbd doesn't start: "No response from the DRBD driver! Is the
mod
@Balint
Please try the below command:
1. $ acpi_listen => press power button
output: button/power PBTN 0080
It is for getting the power button string which is PBTN
2. $ sudo acpidbg -b "notify _SB.PBTN 0x80"; sudo acpidbg -b "notify _SB.PBTN
0x80"
To simulate two consecutive power
So another soft lockup. It was followed by a hard lockup on the next
reboot.
** Attachment added: "journal_log05272020.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865293/+attachment/5377634/+files/journal_log05272020.txt
--
You received this bug notification because you are a
@Balint
Please try the below command:
1. $ acpi_listen => press power button
output: button/power PBTN 0080
It is for getting the power button string which is PBTN
2. $ sudo acpidbg -b "notify _SB.PBTN 0x80"; sudo acpidbg -b "notify _SB.PBTN
0x80"
To simulate to consecutive power
*** This bug is a duplicate of bug 184 ***
https://bugs.launchpad.net/bugs/184
In future please don't attach crash files to bugs. Instead please report
them by running:
ubuntu-bug YOURFILE.crash
** Summary changed:
- when trying to lock my screen I always get: gnome-shell crashed
*** This bug is a duplicate of bug 184 ***
https://bugs.launchpad.net/bugs/184
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 184, so it is being marked as such. Please look
This led status is controlled by BIOS, not OS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881015
Title:
Fn Lock light does not come on to indicate when Fn Lock is enabled
To manage notification
** Summary changed:
- gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() when
using dash-to-panel
+ gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from
st_theme_node_paint_equal() from st_widget_recompute_style() from
st_widget_style_changed()
--
Yo
That sounds strange. Please look at /var/log/apt/history.log to see
what's uninstalling it. If you can't find the answer then please attach
the file here.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1873052, so it is being marked as such. Please look
That sounds strange. Please look at /var/log/apt/history.log to see
what's uninstalling it. If you can't find the answer then please the
file here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881009
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 run 'gnome-shell-extension-prefs' and ensure you don't have
multiple docks enabled.
** Package changed: xorg (Ubuntu) => gnome-shell-extension-dashtodock
(Ubuntu)
** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
Status: New => Incomplete
--
You received this bug notificati
*** This bug is a duplicate of bug 1738838 ***
https://bugs.launchpad.net/bugs/1738838
Looks like bug 1738838. But please also run 'rfkill' and paste the
output here so we can see if the hardware switch is off.
** Changed in: gnome-bluetooth (Ubuntu)
Status: New => Incomplete
** This
** Tags added: lock lock-screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877746
Title:
Lock screen not working
To manage notifications about this bug go to:
https://bugs.launchpad.net
Thanks. I am out of ideas but maybe subscribe to bug 1877746 too.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Tags added: lock lock-screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
*** This bug is a duplicate of bug 1855711 ***
https://bugs.launchpad.net/bugs/1855711
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1855711, so it is being marked as such. Please look
^^^
That's covered by bug 1873725, which is reported upstream so that one looks
like a pure gnome-shell bug, not related to ubuntu-dock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872268
Title:
Fix:
https://gitlab.com/es20490446e/noto-emoji-confs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859926
Title:
fonts-noto-color-emoji not making pretty emojis in google chrome
To manage notifica
Oh, sorry. I had to Google "German keyboard layout" to see that
keyboards with two Super keys do exist. I have never seen that before.
If you just want support for multiple simultaneous keys on the same
action then I will make this bug about that...
** Summary changed:
- Tweaks > Keyboard & Mo
** Description changed:
- this bug is for tracking purpose.
+ This patchset is for mainline kernel-5.8, after backporting to 5.6,
+ there is no need to change anything, but after backporting to 5.4
+ kernel, because of API differences, need to do some change to adapt
+ to 5.4 kernel's API. So ther
** Tags removed: verification-needed-eoan verification-needed-focal
** Tags added: verification-done-eoan verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874359
Title:
alsa/so
Thanks Steve. To be completely sure it's this bug we would need to see
the log message from the assertion failure (run journalctl), but it
looks likely to be this one.
When you say you removed "gstreamer", which packages do you mean?
--
You received this bug notification because you are a member
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag 'verification
Thank you for taking the time to file a bug report.
It seems that you are using a custom device_model_override
(coming from /usr/local/lib).
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
However, if yo
RTX 2080, same problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870736
Title:
[nvidia] Screen scaling 125% gives 200%
To manage notifications about this bug go to:
https://bugs.launchpad.net/
1 - 100 of 555 matches
Mail list logo
