Also hit here on a near-vanilla 18.04 install; snap docker auto-updated
and fell down, and stayed down until manually reloaded.
$ snap changes
ID Status Spawn Ready Summary
10 Doneyesterday at 23:06 EST yesterday at 23:06 EST Auto-refresh snap
"docke
** 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 --
kernel-sta
Public bug reported:
--ubuntu release :
lsb_release -d
Description:Ubuntu 18.04.3 LTS
-- package :
apt show linux-firmware 2>&1 | grep -i "version:\|package:"
Package: linux-firmware
Version: 1.173.12
--hardware :
lspci -vnn | grep irel
03:00.0 Network controller [0280]: Intel Corporation Wi
Removing packages from focal:
zope.ucol 1.0.2-2ubuntu12 in focal
python-zope.ucol 1.0.2-2ubuntu12 in focal amd64
python-zope.ucol 1.0.2-2ubuntu12 in focal arm64
python-zope.ucol 1.0.2-2ubuntu12 in focal armhf
python-zope.ucol 1
Public bug reported:
Please sync dbconfig-common 2.0.13 (main) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Fix MySQL and MariaDB different ALTER syntax whenever specifying the
authentication plugin together with the password.
[ Rafael David T
Dave in comment #10 you said "load on the ARM during transfers (my hunch
is, if anything is affected, it'll be the latter - I vaguely recall
forum posts about improvements on the ARM load during large USB
transactions)." Were the systems checked for load during the transfer
tests?
Additionally, wo
This bug was fixed in the package dbconfig-common - 2.0.13
Sponsored for Rafael David Tinoco (rafaeldtinoco)
---
dbconfig-common (2.0.13) unstable; urgency=medium
* Update Korean, thanks Changwoo Ryu (Closes: #935060)
* Update Spanish, thanks jonatan porras
* Update Russian, tha
Well, regardless of whether snap docker was already installed prior to
change 33, it was at that auto-refresh when the issue actually began,
not before.
No docker tools we have would have pulled in docker snap automatically,
and we had not changed a thing on the server for days.
--
You received
the same output is on the ubuntu manpages:
https://manpages.ubuntu.com/manpages/eoan/man8/VBoxService.8.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851177
Title:
VBoxService: error: VbglR3I
I can confirm that systemd 237-3ubuntu10.33 fixes this issue for me on
bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
*** This bug is a duplicate of bug 1851936 ***
https://bugs.launchpad.net/bugs/1851936
Public bug reported:
I just upgraded to focal from eoan, and I'm now getting a "You've
launched an older version of Firefox" dialog when I try to launch
firefox.
This prevents me from using my existing pro
*** This bug is a duplicate of bug 1851936 ***
https://bugs.launchpad.net/bugs/1851936
An upgraded profile's compatibility.ini:
[Compatibility]
LastVersion=70.0.1_20191031000133/20191031000133
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/firefox
LastAppDir=/usr/lib/firefox/browser
--
*** This bug is a duplicate of bug 1851936 ***
https://bugs.launchpad.net/bugs/1851936
My existing profile's compatibility.ini:
[Compatibility]
LastVersion=70.0.1_20191031091608/20191031091608
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/firefox
LastAppDir=/usr/lib/firefox/browser
--
** Summary changed:
- bionic/linux-aws-5.0: -proposed tracker
+ bionic/linux-aws-5.0: 5.0.0-1022.25~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Ke
Public bug reported:
Whether the menu is open to zoom in, go to full screen, etc., the menu
spawns correctly with all of the buttons properly rendered, but there is
a white box behind the menu.
To elaborate, I have a fresh install copy of Ubuntu 20.04 development
branch on VirtualBox with the sta
** Description changed:
+ [Impact]
+ The DKMS package won't work with new kernels on bionic.
+
+ [Test case]
+ Install and load the modules.
+
+ [Regression potential]
+ This might break the functioning of the module.
+
+ ---
+
Testing failed on:
- amd64:
Public bug reported:
While performing an upgrade from ubuntu 16.04 lts to 18.04 lts, some
third party entries in the source.list are initially disabled, and
thereafter ubuntu minimal isn't found. And this stops the upgrading
procedure.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-
*** This bug is a duplicate of bug 1851936 ***
https://bugs.launchpad.net/bugs/1851936
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 1851936, so it is being marked as such. Please look
** 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 --
kernel-sta
*** This bug is a duplicate of bug 1851936 ***
https://bugs.launchpad.net/bugs/1851936
It looks to me like the focal version was built before the eoan version,
which means firefox (reasonably, but incorrectly) detects a downgrade.
--
You received this bug notification because you are a membe
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been fix
This bug was fixed in the package oss4 - 4.2-build2010-5ubuntu5
---
oss4 (4.2-build2010-5ubuntu5) focal; urgency=medium
* Use M= instead of SUBDIRS= on debian/oss4-dkms.dkms.in (LP:
#1848590)
-- Thadeu Lima de Souza Cascardo Thu, 14 Nov
2019 13:11:48 -0300
** Changed in: oss4 (
Thank you for your bug report. I confirmed that this can be reproduced
on Ubuntu 18.04. On Ubuntu 19.10 that seems to be partially fixed, but
there still are some problems. I've added a BugWatch to the related
issue in upstream
** Bug watch added: github.com/Guake/guake/issues #1311
https://git
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Cha
*** This bug is a duplicate of bug 1847361 ***
https://bugs.launchpad.net/bugs/1847361
Hi Louis,
this is a known, but complex and probably very (very) long running issue.
I recently discussed it on the KVM Forum and we had a mail thread about it.
Read the full background on bug 1847361 - I'll
Public bug reported:
I boot from ZFS since the begin of the year. I have a multi-boot situation with:
- Ubuntu 19.10 with Virtualbox booting from ZFS
- Ubuntu Mate 19.10 with QEMO/KVM booting from ZFS
- Ubuntu 19.10 booting from ext4
I have two problems with zfs:
- the last update of zfs failed,
** Attachment added: "opelt.lshw.xml"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852794/+attachment/5305764/+files/opelt.lshw.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852794
T
Public bug reported:
One of our Dell R630 machines in our CI environment won't boot with the
4.4.0-168.197 kernel in xenial.
I've confirmed that it does boot with 4.4.0-166.195, but it won't boot
with neither 4.4.0-168.197 nor 4.4.0-169.198. I haven't tried with
4.4.0-167.196, but I'll see if I c
** Attachment added: "natasha.lshw.xml"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852794/+attachment/5305763/+files/natasha.lshw.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185279
** 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/1849569
Title:
ktap 0.4+git20160427-1ubuntu3 ADT test failure with linux-hwe-edge
5.3.0-19.20~18.04.2
To manage notifications ab
** Tags added: xenial2bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852792
Title:
ubuntu minimal not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
** Description changed:
I boot from ZFS since the begin of the year. I have a multi-boot situation
with:
- Ubuntu 19.10 with Virtualbox booting from ZFS
- Ubuntu Mate 19.10 with QEMO/KVM booting from ZFS
- Ubuntu 19.10 booting from ext4
I have two problems with zfs:
- the last upda
Public bug reported:
My install hangs when trying to erase and install a new 19.10. There
were problems in the old install. Will burn a new usb and try again
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux
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 1852794
and then change the status of the bug to 'Confirmed'.
If, due to the nature
I found this bug report because I have the same issue, but I think it's
because the interface is "UP". When I try the same "set" command on a
"DOWN" interface, it's successful. My issue is figuring out how to run
the set command during the boot process on the eth0 interface, before it
comes up. Net
> I think "zfs mount -a" should NOT try to mount datasets with
> mountpoint "/"
There is no need for this to be (confusingly, IMHO) special-cased in
zpool mount.
You should set canmount=noauto on your root filesystems (the ones with
mountpoint=/). The initramfs handles mounting the selected root
** Description changed:
I boot from ZFS since the begin of the year. I have a multi-boot situation
with:
- Ubuntu 19.10 with Virtualbox booting from ZFS
- - Ubuntu Mate 19.10 with QEMO/KVM booting from ZFS
+ - Ubuntu Mate 19.10 with QEMU/KVM booting from ZFS
- Ubuntu 19.10 booting from ext4
Public bug reported:
About 1 time in 5 the system either fails to suspend or fails to resume.
Problem introduced by update to 19.10, where mem sleep at least works
(sometimes).
19.04 couldn't actually get into mem sleep at all. It just ended up in
some medium-power state from which it could (usu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in Ubuntu 19.04 and Ubuntu 19.10, and is fixed in development version of
Ubuntu (the guake version that contained the fix is Guake 3.3.3)
If you need a fix fo
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been fix
>From bug 1852790, the issue appears to be that the focal version was
built before the eoan version. My current profile's compatibility.ini
(from eoan):
[Compatibility]
LastVersion=70.0.1_20191031091608/20191031091608
LastOSABI=Linux_x86_64-gcc3
LastPlatformDir=/usr/lib/firefox
LastAppDir=/usr/li
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Cha
A workaround which I've just used is to replace LastVersion in your
profile's compatibility.ini with the one that the current version of
firefox uses (70.0.1_20191031000133/20191031000133).
(I suspect in the short term this could be fixed by a no-change rebuild
of firefox.)
--
You received this
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been fix
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been fix
If your laptop still freeze when loading javascript try this
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511019/comments/8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1345820
Title:
My l
** 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 --
kernel-sta
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 1852799
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Summary changed:
- bionic/linux-azure-5.3: -proposed tracker
+ bionic/linux-azure-5.3: 5.3.0-1008.9~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical
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/1852797
Title:
Hangs on suspend/resume
To manage notifica
Public bug reported:
In linux-modules-5.3.0-19-generic and earlier, on bionic, modules were
signed (note "signat: PKCS#7"):
$ modinfo /lib/modules/5.3.0-19-generic/kernel/arch/x86/kernel/cpuid.ko
filename: /lib/modules/5.3.0-19-generic/kernel/arch/x86/kernel/cpuid.ko
license:GPL
des
** 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 --
kernel-sta
Can confirm that this problem still exist on the latest LTS release.
I tested connecting to enterprise network with enabled and required PMF (
Protected Management Frames / Management Protected Frames or 802.11w ) on
Ubuntu 18.04.3 LTS (with all updates) - all attempts failed, when the PMF was
Hey Sebastien.
I can't create a bug report of the issue. But I have figured out what
happens when I add the second monitor as I have more icons on the desktop.
My laptop is running in a resolution of 1920 x 1080 and my second
monitor runs at 4096 x 2160 (4k). When I connect the monitor my icons
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpa (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/1827757
Title:
PMF
T
Not attaching logs since I can't boot the affected kernels, and this is
a packaging issue.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Summary changed:
- vmtests: test_ip_output failing in vlan tests on eoan
+ networkd pads interface MTU by 4 bytes for vlan even when told not to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184623
I note that although this bug is marked as "opinion", it finally got
fixed some years later. You're welcome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768786
Title:
Accumulating kernels is crue
Tests were performed with Intel Dual Band Wireless-AC 7265 card.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827757
Title:
PMF
To manage notifications about this bug go to:
https://bugs.launchpa
Public bug reported:
there is no reason to have kernel squashfs per flavour, and even
standalone.
They are not used to installed into target.
People who want to provide custom kernel, would use custom
(kernel+initrd) combo, which has a cloud-utils-copymods hook to copy
mods from initrd to live s
** 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
** 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
** 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
** 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 --
kernel-sta
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Cha
Public bug reported:
I noticed that after the switch to a snap in eoan, in a case where I
knew I had manually shut down chromium cleanly, I got an error on
restart saying that it had not been shut down cleanly. Digging around
on the filesystem led me to realize that a snap refresh had happened an
Removing packages from focal:
zope.structuredtext 3.5.1-0ubuntu3 in focal
python-zope.structuredtext 3.5.1-0ubuntu3 in focal amd64
python-zope.structuredtext 3.5.1-0ubuntu3 in focal arm64
python-zope.structuredtext 3.5.1-0ubuntu3 in focal armh
Public bug reported:
zope.structuredtext is only built for python2, and has no uploads since
2011. It has no reverse-dependencies but build-depends on van.pydeb,
which has been removed from Debian. We should remove this package from
focal.
** Affects: zope.structuredtext (Ubuntu)
Importance:
Removing packages from focal:
zope.tal 3.5.2-0ubuntu4 in focal
python-zope.tal 3.5.2-0ubuntu4 in focal amd64
python-zope.tal 3.5.2-0ubuntu4 in focal arm64
python-zope.tal 3.5.2-0ubuntu4 in focal armhf
python-zope.tal 3.5.2-0ubu
Public bug reported:
zope.processlifetime is only built for python2, and has no uploads since
2011. It has no reverse-dependencies but build-depends on van.pydeb,
which has been removed from Debian. We should remove this package from
focal.
** Affects: zope.processlifetime (Ubuntu)
Importanc
This issue should be fixed with Catfish 1.4.6
Xfce: Open directories with the preferred file manager (Xfce #14483)
** Changed in: catfish (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852173
Title:
GUI applications with root access don't open
To manage notifications about th
Public bug reported:
zope.size is only built for python2, and has no uploads since 2012. It
has no reverse-dependencies but build-depends on van.pydeb, which has
been removed from Debian. We should remove this package from focal.
** Affects: zope.size (Ubuntu)
Importance: Undecided
Removing packages from focal:
zope.size 3.5.0-0ubuntu2 in focal
python-zope.size 3.5.0-0ubuntu2 in focal amd64
python-zope.size 3.5.0-0ubuntu2 in focal arm64
python-zope.size 3.5.0-0ubuntu2 in focal armhf
python-zope.size 3.5.0
Removing packages from focal:
zope.tales 3.5.3-0ubuntu1 in focal
python-zope.tales 3.5.3-0ubuntu1 in focal amd64
python-zope.tales 3.5.3-0ubuntu1 in focal arm64
python-zope.tales 3.5.3-0ubuntu1 in focal armhf
python-zope.tales
** 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 --
kernel-sta
** 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 --
kernel-sta
> This looks to be related to networkd:
sorry, I didn't read comments before posting, you found it already :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846232
Title:
networkd pads interface MT
** Description changed:
+ [Impact]
+ The DKMS package won't work with new kernels on bionic.
+
+ [Test case]
+ Install and load the modules.
+
+ [Regression potential]
+ This might break the functioning of the module.
+
+ ---
+
Testing failed on:
- ppc64el
I believe this is due to
https://github.com/systemd/systemd/commit/4b151b71320bbee1549afcbad5554a40d90d63b4
and probably is
https://github.com/systemd/systemd/issues/12552
fixed by
https://github.com/systemd/systemd/pull/12574/commits
which prevents the automatic mtu bump when MTUBytes is specifi
** 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 --
kernel-sta
The LTS is not buggy but it looks like there was some corruption on your
download or image written, from the log
kernel: [ 343.443412] SQUASHFS error: zlib decompression failed, data
probably corrupt
Closing since a new image worked fine and it's an actual installer bug
** Changed in: ubiquity
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in upstream in Guake 3.0.6. The fixed version shipped with Ubuntu 19.04.
It won't be fixed in previous versions of Ubuntu because the package
doesn't fit the r
I wonder what the thought process was that led to disabling user resize
of this window in the first place. As with the absence of the other
window controls there's no reason for it at all, and simply not doing so
would have prevented this bug from being application-breaking.
--
You received this
(In reply to Eric Williams from comment #59)
> (In reply to Christoph Laeubrich from comment #57)
> > Also occurs under recent OSes, sometimes at startup, sometimes after
> > running a while
> >
> > Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64 GNU/Linux
> > ldd (Debian GLIBC 2.24-11+deb9u4) 2.24
dpkg shows
libgtk-3-0:amd 3.22.11-1amd64GTK+ graphical user interface lib
libgtk-3-0:i38 3.22.11-1i386 GTK+ graphical user interface lib
libgtk2.0-0:am 2.24.31-2amd64GTK+ graphical user interface lib
libgtk2.0-0:i3 2.24.31-2i386 GTK+ graphical user i
Public bug reported:
I have described my problems here:
https://askubuntu.com/questions/1186588/no-sound-except-popping-noises-on-my-hp-aio-realtek-alc225-for-all-linux-distr
I still have no sound (ubuntu 19.10). Thanks in advance
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1
still there with ubuntu 19.10 everything & freshly upgraded
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847896
Title:
Unable to shutdown or restart from log-in screen
To manage notifications abo
I can't attach any logs, since the system doesn't boot up enough to show
anything useful.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
zope.password is only built for python2, and has no uploads since 2011.
It has no reverse-dependencies but build-depends on van.pydeb, which has
been removed from Debian. We should remove this package from focal.
** Affects: zope.password (Ubuntu)
Importance: Undecided
Moving to grub2 and marking incomplete as no information regarding the
version of Ubuntu being used has been given.
** Package changed: ubuntu => grub2 (Ubuntu)
** Description changed:
en una instalación dual windows 10 aparece como una opción en el grub
pero al querer iniciarlo la barra de
Same for me as of this today: logging off, then navigating through the
menu in the right upper screen corner till the turn-off button and then
clicking it produces no effect in eoan.
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Committed => In Progress
--
You received this bug notific
This bug was fixed in the package monitoring-plugins - 2.2-6ubuntu1
---
monitoring-plugins (2.2-6ubuntu1) focal; urgency=medium
* d/p/exclude-tmpfs-squashfs-tracefs.patch: Ignore artificial filesystems
that trigger false-positive DISK CRITICAL checks due to reporting as at
1
Removing packages from focal:
zope.processlifetime 1.0-0ubuntu7 in focal
python-zope.processlifetime 1.0-0ubuntu7 in focal amd64
python-zope.processlifetime 1.0-0ubuntu7 in focal arm64
python-zope.processlifetime 1.0-0ubuntu7 in focal armhf
Public bug reported:
When I resume the system, the screensaver always re-locks itself about 5
minutes after resume, despite me being active on the system.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xfce4-screensaver 0.1.8-1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname:
Public bug reported:
Hi,
Firstly, I opened this bug report on Mozilla Firefox's Bugzilla page
(https://bugzilla.mozilla.org/show_bug.cgi?id=1595524)
It turned out that bug didn't completely belong to them.
This bug is just a simple wrong translation.
This string, "Yeni bir pencere aç" needs to
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
The fix has not yet been released but is in a period of testing. Did you
follow the instructions in comment #15? The updated package is in
-proposed and will be for a *minimum* of seven days from the date of
comment #15.
If you want to test whether the update works for you then please follow
the i
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
401 - 500 of 599 matches
Mail list logo
